HCM info

Salary account transfer - error in the first productive payroll run after going live during the year

The error occurs during the first payroll run after going live during the year and an associated payroll account transfer during the year in the period after 05/2020: Retroactive accounting date set by the system is before personal LOWEST retroactive accounting.

Note

A1 Message - Note 2811028: Runtime error RAISE_EXCEPTION when assigning confirmations

If you have collected A01.07.2019 confirmations from July 1st, 1 and assign them with the report Assignment of A1 inbound notifications (RPCA0HDXNUMX_IN), the runtime error RAISE_EXCEPTION occurs.

Instead of data record version 1.1.0 for A1 approvals, data record version 1.3.0 is incorrectly expected.

Note

A1 Notification - Note 2760390: Changes to the Data Collection and Transmission Ordinance

When checking the modules DBES (employer), DBAG (employer), DBBA_EO (location), company names with special characters such as B. "&" rejected.

However, this often occurs in company names (GmbH & Co. KG etc.). You can convert special characters in table T5D4UMS.

You can find everything else in the attached SAP note.

Note

DBA allocation of special payments

According to paragraphs 161 and 162 of the BMF letter of November 12, 2014 on the tax treatment of wages according to the DTA, the remaining wages that cannot be directly assigned are always based on the actual working days spent in Germany and abroad when assessing income tax and in the wage tax deduction procedure split within a calendar year.

In the case of special payments in particular (e.g. Christmas bonuses, royalties, bonuses) that are not directly attributable to the work abroad, a breakdown must be made according to the actual working days. So far, it was sufficient to make the allocation according to the agreed working days. SAP has published numerous model wage types and notes on this. The distribution is to be stored in infotype 0012. Up until the end of June 2017, corrections and adjustments were made to this topic. Many of the hints require manual rework and the comparison of schemes and calculation rules.

Details

Error in the derivation and allocation of cost components

A base cost component that does not come from the previous year is to be distributed over 12 months in a derived cost component. In addition, the occupation percentage of the person in question is <100%.

In the month of origin, the dependent cost component is correctly calculated on the reduced basic component (see table below). In the remaining months, the dependent cost component is reduced again by the staffing share.

Details

Printing of log entries in payroll

If desired, a log can be created during the billing run, which can be viewed at the end. It is also possible to output log entries for customer developments. In order for these to be displayed in tabular form, the things explained below must be observed.

Details

Error SPAU comparison

Note 2134534 "Modification logs for changes to the Public Section" from April 2134534, 16.04.2015, or the SAP basis support package mentioned in the note, causes an error in the SPAU comparison.

It is therefore recommended to install Note 2344014 "SPAU comparison for R2344014TR-CLAS deliveries - adjustments to the outdated SAP Notes deletes classes" version 3 from 2/28.07.16/XNUMX before importing further support packages, which fixes the error.

Personnel cost planning: error in the 2nd derivation of cost components whose basis is in the previous year

Initial situation:
If a cost component is derived from the previous year, cost components that have already been derived are no longer derived after the first derivation. So the 1nd level of the derivation.

For example:
If a cost component is derived from the previous year, cost components that have already been derived are no longer derived after the first derivation. So the 1nd level of the derivation.

Details

Personnel cost planning: error in the derivation of cost components based on the previous year

On the basis of the previous year's remuneration, a new cost component is to be derived as a percentage using a scenario. This derivation is based on the basic cost component in infotype 0666 (planning of personnel costs) from the previous year.

As soon as the base cost component is split and contains different amounts, only the last value is used for the calculation.

Details

Obligation to continue paying wages of regular supplements in the event of illness and holiday pay in accordance with

In recent months, the pension insurance auditors have increasingly checked surcharges for continued payment of wages in the event of illness and vacation pay. As a result, it was not uncommon for the audited companies to make additional social security payments!

We would like to point out the obligation to continue paying regular supplements (e.g. SFN supplements), combined with the resulting contribution liability in the event of illness and vacation.

The facts:

Section 1 of the Continued Remuneration Act (EntgFG) regulates the "principle of loss of wages", according to which the employee is to be paid as if he had worked during the absence.

Absences are e.g. e.g.:

  • Holiday
  • Vacation
  • incapacity to work
  • disease
  • The remuneration that the employee would have received without the absence must therefore continue to be paid (§2 and §4 EntgFG).

The following are to be remunerated:

  • Monthly, weekly, daily or hourly wage
  • SFN surcharges
  • piece rate
  • Danger and difficulty surcharges
  • Commissions
  • VL
  • Benefits in kind, such as B. free or reduced-price food and housing

but not:

  • Overtime pay (unless the collective agreement says otherwise)
  • trips
  • meal allowances
  • travel allowances
  • dirt allowances

The remuneration for each day of absence is based on the average earnings that the employee has received in the last 13 weeks during vacation or the last 12 months during illness before the start of the absence (excluding one-off benefits such as Christmas bonuses, vacation bonuses, gratuities and without reimbursement of travel expenses and trips). As a result, employers who pay the corresponding additional benefits are obliged to pay them even in the event of absences and thus to contribute accordingly.

The special feature of SFN surcharges is that the social security exemption limit up to an hourly wage of €25,00 only applies to hours that were actually worked, but not to hours that were not worked but were remunerated. The lack of inflow in the event of non-payment of these remunerations is not decisive for the accrual of the social security contributions (in contrast to wage tax, the inflow principle does not apply here) and therefore the pension insurance auditors collect the contributions retrospectively in the event of an audit, despite the fact that payments have not been made!

LM Consulting has introduced the average remuneration (both 13 weeks and 12 months) in various companies and in many projects. You should check whether the facts described above apply to you as soon as possible in order to be protected from unexpected surprises in the event of an examination.

SAP Note 2158101 - Display ELStAM - Information in infotype 0012

In infotype 0012 Steuerdaten D, the functionality is supplemented via this SAP note to display additional information on the ELStAM procedure. In detail, the following information is output:

  • General data
  • Infotype 0012 tax data
  • Additional information on tax class 6
  • Last announcement
  • time slice

This additional information can be called up using the ELStAM information pushbutton or using the menu options Goto -> ELStAM information in infotype 0012.

Note

SAP note 2205164 - ELStAM: Info from the FW - tax class 1 incorrectly for married people

In the ELSTER newsletter dated August 13.8.2015, 3, the financial authorities informed about an error in the delivery of ELStAM data with the monthly list for June, which was made available at the beginning of July. In certain cases, married employees who were in tax class 4, 5 or 01.01.2015 were assigned tax class 1 retrospectively from January 30.000, XNUMX. The press reported that around XNUMX employees nationwide were affected.

Note

SAP Note 2052333 - ELStAM logon not possible

An ELStAM registration is not possible despite a successful deregistration, which was carried out by your company or another company. In response to an enrollment, you will receive procedural note 552020203 - Note 552020203 - "Unable to enroll again - employee is already enrolled".

This is an error on the part of the financial administration. The employees who are incorrectly still registered in the ELStAM database cannot be identified by the tax authorities and therefore cannot be corrected.

It is only possible to use a workaround to generate the registration for the employee concerned if the situation described occurs. How to proceed is described in detail in the note below.

Note that the notice below is the Note 2050560 – “ELStAM improvements and corrections 28/2014” required! Depending on the patch level, this may require dependent notes.

Also compare Note 2052333 – ELStAM:
VH 552020203 "Registration not possible" although previous deregistration was confirmed.

SAP Note 1806182 – ESS LEA No Error Messages in ESS Leave Request

A change in the BADI method PROCESS_MESSAGES in the user exit PT_ABS_REQ means that no more messages are output. This can e.g. This can lead, for example, to applications for leave being made in excess of the available quota.

The vacation is then not posted, but there are no error messages. This system behavior only occurs if you have activated the above exit!

Note

Hiding the receipt date row causes problems when deleting receipts

If the document date field is hidden in the list entry, this leads to problems when deleting documents. If this is the case, the system reads the affected document type, in the example HOTL with the date 00.00.0000 read from the wage type assignment table, there is no entry with this date. This check is not carried out for all document types.

Note

Three important notes on the subject of AAG have recently been published

  1. If, for the U1 reimbursement, the aliquoting e.g. For example, the field type of downtime with the value 1 = calendar day was still transmitted in the DBAU module. If the BBG is exceeded and the reduction according to BBG is calculated at the same time, this leads to rejection of the reimbursement amount by certain health insurance companies in accordance with note 1835639 (changed procedure for limiting wages to BBG). These funds are of the opinion that the maximum reimbursement per calendar day may be EUR 198,33 (5950,00 / 30). The note allows the marking as a working day reduction, in these cases the health insurance companies may reimburse an amount higher than 198,33 euros. The hint 2011895 - AAG: Override type of downtime solves the problem.
  2. In the case of an employment ban, the reimbursement amount for the SV AG shares, which were initially determined on a monthly basis, is doubled for each split period in the reimbursement month. Although this is a rare phenomenon, the error is difficult to determine. The hint 1999975 - Employment ban: monthly SV-AG shares too high solves the problem.
  3. After importing the SP 74 under EHP 4, AAG notifications for the maternity benefit allowance (DBZU) and for incapacity for work (DBAU) are no longer created. The hint 2022778 - AAG notification creation: Incorrect check for reimbursement rate DBBT solves the problem.

Travel expenses deduction breakfast

Previously, the breakfast deduction could either be entered via the Deductions tab or entered directly in the hotel receipt as a numerical number of breakfasts. From 2014, the number of breakfasts/lunch/dinners in the additional information on the hotel receipt will no longer be entered. After importing the change in travel expenses law in 2014, SAP only recommends using the Deductions tab.

See also SAP Note 1902231
– Changes in the SAP travel expense report due to the 2014 travel expense reform.

Note

SAP Note 2006902 - ELStAM: Explanations of the procedural notes

The note lists the clearing house's most important procedural notes. In addition to the number and text, it is listed what this procedural note is about (diagnosis), how the ELStAM application reports deal with the note (system activity) and which activities result from this for the user (procedure). Note that depending on the company-specific processes and circumstances, additional or different procedures may be possible.

In the appendix you will find the original document of the current interface description with the procedural instructions. The messages (long texts) in the SAP system have also been enhanced with this note, as listed below. The adaptation of the long texts is only available with the HR Support Package for this SAP Note.

Note

Obligation to register for mini-jobs subject to pension insurance

If an employer has increased the regular monthly salary to more than 1 to 2013 euros for a 400-euro mini-job taken on before January 400, 450, this is a mini-job subject to pension insurance under the new law.

It is necessary for the employee to submit an application in good time if he or she does not want to pay contributions to the pension insurance. However, the mini-jobber can be exempted from the pension insurance obligation. It has retroactive effect at most until the first of the month in which the application was received by the employer.

Employer reporting obligation
The employer is obliged to inform the Minijob-Zentrale about the exemption within six weeks (42 calendar days) after receipt of the exemption application.

This also applies to cases in which employers increase or have already increased the regular monthly wages to more than 400 euros. The display takes place with the registration for social insurance, specifying the contribution group "5" in the pension insurance field. If the application for exemption from the pension insurance obligation is reported later, the exemption from the pension insurance obligation only takes effect after the end of the calendar month following the calendar month in which it was received.

There is also an obligation to report in cases in which there is no change in contribution groups. In cases in which an employment that was previously exempt from pension insurance is seamlessly transformed into an employment that is exempt from compulsory pension insurance, the existing contribution group “5” in the pension insurance does not change. However, it is stipulated by law that the employment relationship is canceled at the end of the calendar month before the increase in earnings to more than 400 euros with the notification reason "33" and is re-registered at the beginning of the following calendar month with the notification reason "13".

Employers who submit notifications on paper can use the “Notice of exemption from compulsory pension insurance” form for this purpose. The employer must keep a copy of this notification with the remuneration documents.

If we have newer knowledge regarding the system-side implementation of this case constellation, we will of course inform you about it.

SAP Note 2098254 - Extension collective note year change on 16.1.15

Last Friday, January 16.01.2015, 2116605, the collective notice for the turn of the year Germany was supplemented with the notice 2015 – ELStAM: Error XML schema XNUMX – no feedback. This note must be imported so that the ELStAM data can be transferred smoothly.

The note requires the installation of various dependent notes. Note 2106280 – ELStAM: Corrections and improvements 02/2015 is the only one that requires extensive manual preparatory work.

Also note the manual activities that may be necessary as described in the note under Solutions.

Note

EEL procedure - when using 2 absences for sickness (one with and without continued pay)

Many customers work with two absences to represent paid and unpaid sick leave periods. If you use the EEL procedure to reimburse employer expenses in the event of incapacity to work, you must note that the two illnesses are linked and that the entry period must be entered in infotype 651 from the start of the AU (including the reference part).

Details

New Year 2014

As every year at the turn of the year, there are a number of topics that change in the areas of tax, social security and other legal requirements for payroll and lead to adjustments in SAP® HCM. Below you will find an overview and references to further information from SAP®.

Tax - new program schedule
The new tax schedule takes the following changes into account: increase in the basic tax-free allowance to EUR 8354, the new assessment limits in social security and the increase in the partial amount of the pension flat-rate for pension insurance to 56%: Further changes are still possible.

Income tax certificate
A new form HR_DE_LSTB_14 with the current adjustments will be delivered. The M indicator is generated on the wage tax statement in accordance with the travel expense reform. In line 3 (gross wages), the wages that have been reclaimed and that were taxed at a reduced rate in the year of receipt are certified. In addition, in line 24 - 26 (contributions and allowances for health and long-term care insurance) for voluntarily and privately insured persons, the full contributions and allowances are always given, even if the wages are tax-free. The special certificate is no longer required, only the ElStAM certificate type is generated.

social insurance
As every year, the operands for social security will be adjusted on January 1.1.2014, 511 and updated in table TXNUMXK. More information in Note 1910310.

DEÜV - Reduction of the submission deadline for the annual report
There is no need to select the month of transmission; the annual reports are always transmitted in January. Payments with a March clause are transferred as a special report with submission reason 54.

AAG Subsidy Maternity Allowance
As of 2014, the maternity allowance allowance must be calculated automatically, since the option of applying for reimbursement using infotype 0700 is no longer available.

New initial procedure for the SV contribution statement in 2014
In preparation for the new electronic tax audit in the area of ​​social security, it is necessary for the statement of contributions to be reproducible. This is currently not the case if the contributions are determined and transferred before the final settlement. For this purpose, the statement of contributions will be stored in tables instead of just in TemSe files, as was previously the case.

Employer subsidy for privately insured persons
A change that does not affect the customizing of the system, but only affects the maintenance of the data, is the following: On January 1.1.2014st, 20, new legislation will come into force. Until now, it has been the general legal opinion of the health insurance companies that employees with private health insurance can demand an employer subsidy from their employer for their dependents who are voluntarily insured under statutory health insurance, provided that the amount of the employee’s employer subsidy has not yet been exhausted. With the judgment of the Federal Social Court of March 2013, 12 (Ref.: B 4 KR 11/XNUMX), the legal situation in such an insurance constellation has changed. The court has now decided that an employee with private health insurance has no legal entitlement to a proportionate employer subsidy for their health and long-term care insurance contributions for their relatives who have statutory health insurance.

Please also note the following SAP® notes:
1928910 change of year tax 2013/2014
1910310 Social security year change 2013/2014
1937809 KuG: Changes at the turn of the year 2013/2014
1888252 Reform of the travel expenses law as of January 01.01.2014st, XNUMX
1932389 Information about the turn of the year 2013/2014
1907424 New dataset version for statement of contributions from 2014
1924516 AAG reporting: New data record version 03
1900441 Subsidy MuSchG / message AAG: Use IT0700 with DBZU

Travel expense reform 2014

With effect from January 1.1.2014st, XNUMX extensive changes in travel expenses law come into force. The most important changes relate to the following points:

meal allowances
In the future, a flat-rate amount of EUR 12 will be charged as a flat-rate meal allowance for one-day trips over 8 hours and for multi-day trips on the day of arrival and departure, and EUR 24 for all full days on trips lasting several days. The previous staggering at 8, 12 and 24 hours is no longer applicable. The new meal allowances will be Note 1890802 delivered. The note can be imported with the appropriate support packages. After that, table V_T706V must be compared with client 000. Alternatively, the old rates can be delimited manually and the new flat rates imported via a report; a corresponding appendix is ​​included Note 1890802 attached.

In which Note 1950785 the calculation of the lump sum is regulated in more detail according to a statement by the Karlsruhe Regional Finance Office:

While the Federal Ministry of Finance assumes a regulation for multi-day trips, the Income Tax Act calculates a calendar day with a trip duration of exactly 24 hours with a tax-free meal allowance of 24 euros. When asked by the Oberfinanzdirektion Karlsruhe, the regulation in the Income Tax Act was described as decisive. The staggering for one-day trips is therefore three-tiered:

1. Travel duration from 00:01 minute to 08 hours (0 euro meal allowance)
2. Duration of travel from 08:01 to 23:59 hours (12 euros)
3. Travel time exactly 24 hours (24 euros)

Please note the following special feature Note 1949944: If the overnight stay takes place on the first or last day of the trip in a means of transport, a special document type must be created and maintained in this case, from which the system recognizes that an overnight stay took place.

If different meal rates are granted according to the company's internal travel policy, then the newly imported meal allowances must be updated accordingly and adjusted to the rates granted by the company.

The tax-free passenger flat rate will no longer apply. The previously tax-free flat-rate travel allowance for passengers will no longer apply from 1.1.2014/XNUMX/XNUMX.

Certification of provided meals in the income tax statement. If the employee is provided with meals for external activities, then the letter "M" must be noted on the wage tax certificate. This requires integration of travel accounting into payroll accounting, or alternatively, a wage type must be entered in payroll accounting. The model wage type MJ23, which replaces MJ20, is newly delivered. This triggers the letter "M" on the employee's tax statement.

Further information:

Import DEUEV version 2.51 for December payroll

Due to adjustments to the core test program, corrections are necessary as of December 1.12.2013, XNUMX. Please see the notice below for more information. The notice can be imported via advance correction.

Note: 1935400 - DEUEV: Version 2.51 of the joint circular

Delimitation of central objects of the company structure

The currently available support packages made it possible
delivered the HCM objects employee group and district, as well as personnel area and subarea
to demarcate. The ADMIN DELIM switch in T77S0 must be set to 'X' and the affected personnel areas etc. can then be restricted in terms of their validity.

This is useful if there are a number of entries that are no longer valid, particularly in the Organizational infotype
Assignment (0001) exists. The restriction directly affects the selection guides.

It is still not possible with central control elements, such as e.g. B. the assignment of operational
characteristic (establishment number, etc.) to make a time limitation.

The possibilities of differentiation are therefore limited for merger and demerger projects.

The following information must be observed:
Note: 1883014 – Validity period of HR objects
Note: 1881595 – Interface note (basis): validity period of HR objects
Note: 1882968 – Interface note (SAP_HR): validity period of HR objects

SEPA – special characters and purpose code

Note that the XML tree SEPA_CT delivered as an example does not exclude all "forbidden" special characters. The purpose codes for salary payments must be inserted into the XML tree via a new node. This is how it's done …

Details

Please also note our fixed price offer in the SEPA context. Here you will find the fixed price offer.

Maternity benefit allowance can only be recorded up to December 31.12.2013, 0700 using infotype XNUMX

The subtype BDZU of infotype 700 as the basis for reimbursement requests for maternity allowances paid can only be entered up to December 31.12.2013, 0014. A corresponding correction will be delivered by this date at the latest. i.e. It is necessary either to set up the automatic allowance calculation for the maternity allowance or to set it up at least rudimentarily to the extent that it is possible to enter a default wage type for the maternity allowance allowance using infotypes 0015 or XNUMX.
In this context, see SAP Note 1893400.

In this context, please also note our fixed price offer for changing the above situation further down in this newsletter.

Details

New data collection point Mobil ISC GmbH

The health insurance companies BKK Mobil Oil and BKK on site have set up a joint new data collection point. BKK Mobil Oil will start immediately and BKK on site from 01.01.2014, whereby data will also be accepted and forwarded from BITMARCK Service GmbH for another 6 months. In order to switch to SAP HCM, the current ITSG file must be imported using report RPUSVDD0. This means that the data is automatically sent correctly. No changes need to be made to the health insurance data.

For more information, please refer to SAP Note 1884351

Allocation obligation for one-off payments from time accounts

During audits by the social insurance, it is often criticized that no contribution is calculated for one-off payments from accrued time accounts, although a contribution is required here. Due to unclear details of the calculation, SAP had not previously offered a solution and only calculated the allocation for current payments. With SAP Note 1808841 a solution for this topic is now being delivered. In addition, numerous new wage types are delivered that enable an SI air calculation specifically for the assessment. The calculation can now be carried out. The solution is activated with the sub-application SVUM.

Change to the BBG check for the U1 reimbursement procedure - note 1819098

Up to now, a proportionate contribution assessment limit, which is attributable to sick days, was used to assess a possible cap on the reimbursement amount. In the future, it will first be checked whether the total wage exceeds the RV BBG. Only if this is the case does the continued payment have to be reduced. The new calculation is as follows:

According to the results of the meeting of the National Association of Statutory Health Insurance Funds on October 24.10.2012th, XNUMX, the procedure for limiting the continued payment of wages during the reimbursement period to the proportionate RV contribution assessment limit must be changed. Previously, the monthly assessment limit – reduced by the number of SI days in the reimbursement period – was used as the 'proportionate' PI contribution assessment limit. According to the National Association of Statutory Health Insurance Funds, however, it must first be checked whether the total wage exceeds the RV contribution assessment limit. Only if the limit is exceeded must the continued wages that are due for the reimbursement period be reduced by means of a proportionate calculation in relation to the wages. To do this, the 'proportional' PI assessment limit is calculated from the monthly assessment limit in the ratio:

continued wages : total wages

calculated.

If the continued salary exceeds this proportionate assessment limit, it will be reduced to the proportionate assessment limit. The same procedure should also be used to determine the employer's contributions to social security for the reimbursement period. Please also note the entire note:

ELStAM - Report RPUE2TD0 to check adjustments of IT12 as ALV GRID

Report RPUE2TD0 compares employees' tax data for a key date.

With this report it is possible to reconcile the data reported after registration before importing it into infotype 12.

The report is an auxiliary report for testing the data quality when introducing the ELStAM procedure.

In a cross-system evaluation, the ELStAM-relevant data of infotype Steuerdaten D (0012) is compared between the executing (test system for the ELStAM procedure) and the remote system (production system with tax cards).

In an evaluation within a system, the ELStAM-relevant data of infotype Steuerdaten D (0012) is compared before and after the key date. If the report is started with the key date of the employee's data registration at the clearing house, changes can be determined by the ELStAM notification in the old database.

The prerequisite is that the Customizing for the ELStAM procedure has been carried out and the participating employees have been registered with the clearing house.

Create a function with parameters

If you want to create a function with parameters, a second country assignment is important for the characteristics of the parameters. Only then can the function with the appropriate parameters be used syntactically correctly in a schema.

Details

ElStAM – Innovations in the procedure

Anyone who is already using ELStAM or plans to do so in the near future should have imported the current information. There are now numerous hints with small corrections to the process. Usually the start with ELStAM is relatively easy, problems often only arise during operation. Errors often occur, for example, when employees who have already been reported via ELStAM the last time they leave the company re-enter the company or when they change companies within a SAP® system from one company to another. A number of problems are particularly associated with that Note 1826553 - ELStAM: Corrections after the turn of the year 14/2013 solved.
This includes, for example, the following changes:

An employee is now only processed by the program "ELStAM: Create registrations and deregistrations" (RPCE2VD0_OUT) when all existing registrations, deregistrations and change of registrations have been processed. This prevents processes from being triggered without the current ones being finally processed and the data in infotype 0012 tax data being updated.

The new feature DE2AT now makes it possible to control whether tax class 6 is imported immediately or only in the following month if the employee is no longer authorized to access it.

Please note further information in the note mentioned and further notes on the subject of ELStAM in the SAP® Service Marketplace.

Important information on the subject of income tax

New tax program schedule The Federal Council has published a new tax program schedule in which the basic allowance has been increased to EUR 8.130,00. This change applies retrospectively to January 01.01.2013st, XNUMX, which is why a retrospective calculation after the installation of the Note 1817754 is required.
Those leaving in 2012 will receive a special instead of a general wage tax statement if ElStAM has not yet been introduced.
If an employee leaves a company in 2013 that has not yet introduced ElStAM, then special wage tax statements are created in SAP® HCM, which is a mistake. From 01.01.2013/0012/XNUMX it must be checked whether ElStAM is active, if not then the existence of the tax card must be checked as before in accordance with infotype XNUMX Steuer D. If this is available, then a general income tax certificate must be created. A correction is made with the Note 1812234. A cancellation of the notifications that have already been created and the generation of correct notifications can take place after the note has been installed.

First experience with ElStAM

Already at the beginning of the year, some customers started retrieving their tax data via ELStAM. In addition to some technical problems, which could be solved by installing SAP notes, the conversion of the work processes, such as e.g. B. the renewed retrieval of the data for additional payments after leaving, not insignificant. Anyone planning to start ElStAM should find out about the changeover in detail and plan training for the clerks at an early stage.

The changeover can take place in the course of 2013. The retrieval of the data and the update of the information type 0012 Steuer D via ElStAM begins with the changeover, retroactive accounting is not required.

Employee information is displayed so that they have the opportunity to extend tax allowances before retrieving the data. The tax authority is providing a form for the simplified extension of tax exemptions specifically for the 2013 conversion year.

SEPA conversion to SAP® HCM

The data carrier formats used in Europe for transfers will be standardized with the introduction of SEPA. For this, the IBAN number is mandatory as a uniform bank and account number. Therefore, all data in SAP® HCM that is used for payments must be provided with an IBAN number. In addition to the infotypes 0009 bank transfer, 0010 capital formation and some more, tables are also affected, such as B. the bank details of the health insurance companies and asset formation institutes. A report (RFIBANMD) is available for the changeover, which downloads and uploads the data to update it. The data download is provided with an IBAN using an external program before the upload to update the data takes place. The banks provide programs for filling the IBAN in this database, some of which can be used free of charge. The filling of all payment-relevant data with an IBAN number should be planned at an early stage, since in some cases the conversion cannot be carried out automatically and must be processed individually.

In order to be able to carry out a SEPA transfer, a payment method for the SEPA format must be created, which is entered in the payment-relevant data at the time of the changeover.

Addition and subtraction of wage types including the cost accounting split (cost allocation)

When adding and subtracting wage types, this should usually be done with split precision. Any existing cost accounting split is not taken into account. i.e. Wage types with different cost assignments are offset against each other although this is undesirable. To avoid this, the relevant wage types can be temporarily transferred to table AIT and returned to table IT after clearing has taken place. It must be ensured that the AIT is deleted again after processing, since the AIT is stored across periods. In the solution described here, this is solved with a customer-specific operation.

Otherwise, table AIT is often used in fictitious runs.