Example: Posting-Relevant Information in the Payroll Result

The following basic conditions apply for an employee: Your employee is assigned to the Central Development master cost center The basic pay is 5,000.00 From January 01 January 15, the employee works for the Product Planning cost center for 50% of the time and for the master cost center for 50% of the time. From January 16 - January 31, your employee works for the Sales cost center (30%) and for the Quality assurance cost center (70%). On January 16, your employee receives a one-off payment of 100.00 from the Training cost center.

This affects the payroll results for the payroll month of January as follows: Work Center / Basic Pay Table (WPBP) WPBP Partial Period 01 02 Results Table (RT) Wage type Monthly salary (M020) Monthly salary (M020) One-off payment (M110) Bank transfer (/559) Cost Distribution Table (C0) WPBP Partial Period 01 02 02 SeqNr 01 01 02 Company Code 0001 0001 0001 Cost Center Product planning Sales and distribution Quality assurance Percent 50 30 70 WPBP Partial Period 01 02 02 0001 Cost Accounting Amount 2,400.00 2,600.00 100.00 5,100 From - To 01.01-15.01. 16.01-31.01. Company Code 0001 0001 Master Cost Center Central development Central development

Table of Cost Distribution from Different Infotypes (C1)

Cost Accounting 0001

Company codes 0001

Cost center Training

This information in the payroll results tables is evaluated by the Posting to Accounting component as follows: Posting Wage Type Monthly Salary (M020) for WPBP Partial Period 01: 1. The system reads the Monthly Salary wage type (M020) for work center 01 from the results table (RT). 2. The system reads the posting characteristics for the wage type in Customizing and identifies that this wage type is to be posted to an expense account. 3. The system checks whether there is an entry for this wage type in the Cost Distribution from Different Infotypes table (C1). This is not the case. 4. The system checks whether the entry for this wage type in the results table (RT) refers to a partial period in the Work Center Basic Pay table (WPBP) and identifies the partial period January 01 January 15. 5. The system checks whether cost distribution has been specified in the Cost Distribution table (C0) for this partial period and identifies a distribution of 50% to the Product Planning cost center. 6. The system posts 50% of the wage type amount to this cost center (1,200 to the Product Planning cost center). 7. The system checks whether the wage type amount has been distributed at 100%. This is not the case. For this reason, the system posts the remaining amount (50% = 1,200) to the master cost center for the employee (Central Development). The wage type amount is then completely posted. Posting Wage Type Monthly Salary (M020) for WPBP Partial Period 02: 1. The system reads the Monthly Salary wage type (M020) for work center 02 from the results table (RT). 2. The system reads the posting characteristics for the wage type in Customizing and identifies that this wage type is to be posted to an expense account. 3. The system checks whether there is an entry for this wage type in the Cost Distribution from Different Infotypes table (C1). This is not the case. 4. The system checks whether the entry for this wage type in the results table (RT) refers to a partial period in the Work Center Basic Pay table (WPBP) and identifies the partial period January 16 January 31. 5. The system checks whether cost distribution has been specified in the Cost Distribution table (C0) for this partial period and identifies a distribution of 30 % to the Quality Assurance cost center. 6. The system posts the wage type amount, which is distributed on a percentage basis, to the cost centers (780 to the Product Planning cost center and 1,820 to the Quality Assurance cost center). 7. The system checks whether the wage type amount has been distributed at 100%. This is the case. The wage type amount is then completely posted. Posting the One-Off Payment Wage Type (M110):

1. The system reads the One-Off Payment wage type (M110) from the results table (RT). 2. The system reads the posting characteristics for the wage type in Customizing and identifies that this wage type is to be posted to an expense account. 3. The system checks whether an entry for this wage type exists in the Cost Distribution from Different Infotypes table (C1) and identifies that the wage type amount is to be posted to the Training cost center. 4. The system posts the wage type amount to the cost center. Posting Bank Transfer Wage Type (/559) 1. The system reads the Bank Transfer wage type (/559) from the results table (RT). 2. The system reads the posting characteristics for the wage type in Customizing and identifies that this wage type is to be posted to a balance sheet account. 3. The system checks whether the entry for this wage type in the results table (RT) refers to a partial period in the Work Center Basic Pay table (WPBP). This is not the case. The system chooses the last partial period in the Work Center/Basic Pay table (WPBP) (16.01 31.01). 4. The system reads the company code 0001 from the partial period for the Work Center/Basic Pay table (WPBP) and posts the wage type amount to this company code. Posting Documents The system creates the following posting document for the described postings: Company code 0001 G/L account Salaries Salaries Salaries Salaries Salaries Wages and salaries to be paid Cost Center Product planning Central development Sales and distribution Quality assurance Training Debit 1,200.00 1,200.00 780.00 1820.00 100.00 5,100.00 Credit

SAP HR FI
FI/CO Posting - Retro's
If an employee has retro's going back a few months then wagetypes /551 and /552 are used to hold the differences. For an employee who has been overpaid by a substantial amount, /561 and /563 are used to recover the claim against the employee. In the month of the adjustment, /561 shows the total difference. If the employee's salary does not allow this full amount to be deducted then an additional amount will have to be claimed, which will be the difference between /551 and /560 - stored as /563.

Cost Center Hierarchy and Searching

If you wish to display, rather quickly, the whole cost center hierarchy, you can do so using the transaction code OKEN. If you wish to find a particular cost center, use the menu path Edit > Find and then enter your cost center. The hierarchy will just open up for this cost center. The structure shown, will be for a particular controlling area. You can change the controlling area by using the menu path: Edit > Settings

Cost Distribution - IT 0027

In most cases, an employee's cost will be based on the employee's home cost center, found on infotype0001. In some cases, it may be necessary to apportion these costs to more than one cost center. You can do so on IT 0027 - Cost Distribution. You can enter the company code, cost center and the percentage to be distributed amongst the entries. It is also possible to allocate costs across company codes. In order to do this, a posting variant must be set up to link the two company codes, and must be selected when creating the posting run.

Splitting FI posting documents by employee name

Ever wondered how to split accounting documents from Payroll to FICO by employee number - i.e. one document per employee? You'll need to fill in the text field in the 2nd user exit in RPCIPE00 with the current PERNR (employee number). The document will then be summarized at the employee level. The text field will form part of the key of summarization.

Reversing Posted Results

You may need to reverse posted payroll results at some point. You can do so by using transaction code PCP0 and select the run you want to reverse. Then use the menu path: Edit > Reversal > Reverse document. Once you have reversed the document you can then make the relevant changes and repost the corrected document. You can't reverse the posting for an individual employee. You need to reverse the whole document and then fix the issue or exclude the employee from the posting run and then repost the whole document.

Posting Wage Types with and without hours

Want to know how to post some wage types with hours and others without hours? You might have wage types that are being posted to FI/CO - some with hours posted and others without. You could create notional or dummy wage types which are the same as the source wage type - with or without the hours. You could decided to configure 1 of the 2 wage types - depending on what you required to be posted. See OSS note 111538. It details a very easy user exit which provides a solution for posting quantities.

Symbolic Accounts
Symbolic accounts are the link between the payroll and finance sections of SAP. Every wage type which posts from payroll to the finance section of SAP, needs to do so via a symbolic account that has been defined in table T52EK. So every posting wage type must be assigned to a symbolic account. Table T52EL_COMP is very useful when maintaining the mapping between wage types and symbolic accounts, it shows every wage type and where it points to. Wage types will only appear in this table if they are first entered into table T52EZ, which specifies which wage types should post to the finance section using date parameters. A symbolic account can have limitless wage types pointing at it, this means that if, for example, you have 3 wage types that post to the same GL account, they could all point to the same symbolic account. A wage type can point at more than one GL account, this is necessary when posting wage types such as Employers NIC and Employers Pension Contributions for example. The way to handle such cases is to have the same wage type posting to one GL account as a debit and another as a credit, hence not affecting the overall balance of the posting document. When specifying the link between symbolic accounts and GL accounts in the relevant IMG step, selecting Rules at the top of the screen gives you various options for your symbolic accounts. By selecting the check box Employee group, it is possible to use the same symbolic account to point at different GL accounts according to the Employee Grouping. This means that the same wage type can post to different GL accounts according to the Groupings specified in table T52EM and the rules specified in feature PPMOD. N.B. Only wage types that have the MOMAG (Account determination dependent on employee grouping) box selected in table T52EK will be dependent on Employee Grouping. By selecting the check box Debit/Credit, it is possible to have the same symbolic account pointing at a separate GL accounts for debits and credits. A word of warning however, if you are changing the rules for your symbolic accounts you will lose all your current entries mapping symbolic accounts to GL accounts, so be very sure of what you are doing and do not play around with this IMG step. A very useful tool when customizing the settings for the Payroll and FI integration is the Check Consistency of Customizing step of the IMG. This report shows which GL account each wage type will post to, if there are any wage types that are not pointing at a GL account via a symbolic account then the report will show ??????.If ?????? appears, then there is an error in the customizing and you will receive an error when you try and post the wage type. A common reason for ?????? appearing in the report when the configuration has been finished is that a symbolic account has been specified as an expense account in table T52EK, for example, but has been pointed at a balance sheet account in relevant step of the IMG.