Thursday, November 29, 2012

Australia - Superannuation - Choice of Funds - T5QSC

Report: RPUSWCQ0
Tcode: PC00_M13_SWCQ

To configure the choice of funds dropdown used in IT 0220 - Superannuation, user must configure the values in table T5QSC.

However this table is not maintainable via SM30 and is maintained directly in Production via program. This is usually done by uploading a text or excel file.

Sample format:-
000 SCF1 31.12.9999 01.07.2006 SUPERCHOICE FUND1 12345678900000 12345678900 SPIN CODE

Wednesday, November 28, 2012

Australia - Payment Summary Override

PC13 > Payroll Australia > Subsequent activities > Annual > Other activities > Payment summaries/Group certificates

This transaction allows you to show amounts on the Payment Summary form during year end for the employee. It is used for scenarios where final payroll run were performed for end of financial year and there was additional payments to be made after that and needs to be reported in the Payment Summary form for that particular year.
No Reversal Flag - In scenarios, where payments are not in the payroll, such as data coming from legacy system, or manual payments made and not stored in CRT, this flag is ticked, so that no reversal takes place in the subsequent year's Payment Summary form.
If however the payment will be recorded in the following year's Payroll Period 1 payroll run, then the reversal is required to take place so that the amount will not be reported again in the following year's Payment Summary form. Then leave this flag as blank.

Australia - Country Modifiers

View: V_T5QGB

This view allows you to configure per Personnel Subaarea related ABN number, Employer Address, etc. This will appear in Australian forms.

Australia - Superannuation

There are many funds that employee can subscribed to in Superannuation.
The difference is determine from SAP configuration
  • SGC Fund
  • Non SGC fund
SGC Funds are calculated at the end of every month. Normally in Australia there are 26 payroll periods, so it is callculated every 2 payroll periods.
Non-SGC Funds are calculated every period.

Every quarterly, for an SGC Fund, it will calculate against the quarterly capping amount eligible for Superannuation.

Infotype 0220 - SuperAnnuation

Reportable Employer Superannuation Contributions (RESC)
This is a wagetype to store the contribution that's higher than 9%

Currently SGC is at 9%. This will slowly increase to 12% from 1 July 2019.

View: V_T5QSF
This is the main view to configure a Superannuation Fund

Australia - LSL calculation

Determine the number of years the employee has been in service as this determines the probability factor and other percentages.

(Accrued LSL hours * hourly rate)*(Probability factor) = Nominal Amount
Nominal Amount * Escalation Rate = Escalated amount
Escalated amount + Nominal Amount = Escalated Sub-total
Escalated Sub-total * Inflation rate = Inflation Amount
Inflation Amount + Escalated Sub-total = Inflation Sub-total

10 years - employee years of service = years to liability
Years to liability * Bond rate = Bond rate factor
Inflation Sub-Total * Bond rate factor + Inflation Sub-total = Total

Monday, November 26, 2012

Time - Feature QUOMO

Feature: QUOMO

Quota Type Selection Group is a feature that does further grouping

It is linked to V_T559L in this highlighted field.

Australia - Payroll Tax

Payroll Tax is a tax where employers pay for an Australian employee to the state. Accordingly, different state can have different rates (%) of payroll tax.

IMG > Payroll Australia > Taxation > Payroll Tax and Worker's Compensation

1. First you determine the State per Personnel Area (WERKS). This is done using a feature 13PWC
2. The second node allows you to maintain State and Description. For example, NSW - New South Wales, VIC - Victoria, QLD - Queensland, etc..
3. The third node, allows you to group which Wagetype is subjected to Payroll Tax and under which State. A function in the schema will total up these Wagetypes into /GPT. You can then write a payroll rule in the schema to execute /GPT X Constant (E.g. 5%) during the project implementation.

Australia - Employment Declaration Details to the Australian Taxation Office (ATO)

Employment Declaration Details to the Australian Taxation Office (ATO)

Report: RPCPBSQ0

IMG > Payroll Australia > ABS Interface/Employment Declaration Details > Employment Declaration Details to the Australian Taxation Office (ATO)

1. The first step is to specify a feature 13DEG that controls according to which Emp Group and Emp Subgroup, it is a FT - Full Time, PT - Part Time, CA - Casual

2. The second step is also a feature 13DSN to specify which Date Specification (IT0041) Type to store this date. For example, Y1

3. The third step is a feature 13DEN to specify which Date Specification (IT0041) Type to store this date. For example, Y3

Below is a sample output of this report. Use the download platform to download the file.

If the employee's IT0041 does not have the Y1 and Y3 date specs entered with data, then this report will show you 'No data available for your entries' message when you try to run it for an employee (F8).

Tuesday, November 20, 2012

Australia - Showing Retro lines for Superannuation in Payslip

Note 1310477 details that a switch HRAUQ PYSIP in table T77S0 has been created which allows you to activate or deactivate the minimum earnings check to be carried out in the IN-PERIOD or not.

  • ACTIVATE (X) to execute the minimum earnings check in the Current Period (In-Period).i.e., to bring delta superable earnings (OTE and WSE) from the retro period, into the Current Period (In-Period).
  • Or DE-ACTIVATE ( ) to execute the minimum Earnings check for SGC is done in the Retro Period (For-Period).

As the switch is deactivated, retro lines will appear in Payslip when there's changes to OTE that affects Superannuation calculations


Copying Wagetype - OH11

Tcode: OH11

This tcode is very useful and convenient to copy a wagetype to a new wagetype

Select the required Country Grouping and Wagetype Group
Then highlight the required wagetype, and enter at the right columns, the new wagetype number and text description and then click on the [Copy] button.

This screen will appear to indicate all the related tables are copied at one go.

Thursday, November 15, 2012

Singapore - /450 Wagetype

Wagetype /450 - E'YEE Compulsory Contr.

This wagetype contains YTD Employee's CPF Contribution. It will be shown at IR8A form under Deductions section

Evaluation Class 07 = 31

Tuesday, November 13, 2012

Wagetypes - Assignment to Wage Type Group - T52D7, T512Z

Table: T512Z
Table: T52D7

View: V_52D7_B

This view is used to configure which Infotype the wage type should appear for

View: V_T512Z

This view is used to configure whether it's possible to appear once or many times per Infotype screen for a particular wagetype

PPOME - Hierarchy Framework Enhancement - Hide Tabs at Details

I did some experimenting trying to learn how Hierarchy Framework for OM works. Currently I've just managed to hide some Details Tabs that appear after double clicking on the Org Unit object. In SAP Standard, there are 14 tabs that would be shown. I have made an enhancement into tcode: ZPPOME, that will only show 3 Details Tab upon selecting Org Unit object.

As seen here, a long list of Tabs appear as Details for the Org Unit object

IMG > Organizational Management > Hierarchy Framework > Integrate New Object Type > Display Object Type in Structural Overview Object

  1. Copy OME000 (Standard Object Manager Scenario) to ZOME000
  2. Create a copy of PPOME tcode into ZPPOME using tcode: SE93
  3. Copy OME0 scenario into ZOME0
4. Since all dependent configurations were also copied in above step, ZOME0 - Object Type O, will initially have about 14 rows. I deleted all the other records and left these in the configuration.

5. Run ZPPOME tcode and select an Org Unit. Now only 3 Tabs appear in the Details Tabs section.

HRSP53: OSS 1752068 - SGEDT Feature

In this OSS note, feature SGEDT is introduced with SFEXC return value. To enable the new CPF Apportion, Excess and Shortfall calculation method, set it as 20121001 so that Apportion begins effective 01.10.2012 payroll and Shortfall/Excess will be effective Jan 2013

Current behaviour:-
In Singapore payroll CPF is calculated for each period earnings. In yearend total ordinary wage (TOW) will be recalculated for that year and fresh AW ceiling will be calculated, based on it shortfall or excess CPF will be calculated on difference amount (AW ceiling).

Shortfall or excess is calculated by applying respective month rates on unpaid or paid AW amount respectively. Then normal rounding happens on shortfall or excess amount (round down for employee contribution and normal rounding for employer contribution).

New behaviour:-

a) Shortfall calculation:
CPF Shortfall = CPF on Total Wage ( OW Paid + AW Paid + AW Unpaid ) - CPF already paid

a) Excess calculation:
CPF Excess = CPF already paid - CPF on Total Wage ( OW Paid + AW to be paid )
This new method of shortfall and excess calculation avoids rounding of total CPF contribution twice (once during respective month CPF calculation and again during shortfall/excess CPF calculation). This solves $1 difference in Employee / Employer's CPF contribution.

Monday, November 12, 2012

Singapore - Mid Month Payroll Solution

SAP provides a mid-month payroll solution for Singapore.
The main table to be configured is T5R1P

Table: V_T5R1P

During a Payroll Run, enter MIDP as the Offcycle Reason

A sample of output or Payslip is as below. It can be decided that only Basic Pay Wages and CPF needs to split into 50% while an allowance is paid in full during mid-month.

The calculation takes place in Schema RCPF

After running Mid-Month Payroll, run Pre-DME (PC00_M25_CDTA) so that /559 Bank Transfer wagetypes are created into the Payroll Results
Then run Month-End Payroll by entering 'REGU' as the Offcycle Reason.
Noticed that the Month-End Payslip will indicate Mid-Month Pay Out as 720.00 after Pre-DME was run.

If you check Payroll Results, particularly the BT Cluster, two wagetypes are found:-
  • /559 Bank Transfer - during Mid Month Transfer
  • /558 Payment of Balance - during Month End


SE17 - General Table Display

What do you do if SE16 and SE11 keeps throwing run-time dumps and you need to view a particular table's content.

You can use the old school way, tcode SE17

Singapore Payroll CPF Related Wagetypes

/3LA = SGD 1000 ( 20% of SGD 5000 (cap) ) - Employee's contribution to CPF
/3LC = SGD 1800 ( 16% of SGD 5000 (cap) ) - Employer's contribution to CPF

/3OW = Last year's OW is used as projection for this year

/309 - AW paid to CPF

  • Calculated using last year's total OW
  • 2011 - Employee has SGD 3000 x 12 = SGD 36,000
  • So in year 2012, /309 will be calculated = SGD 85,000 (TW Cap) - SGD 36,000 = SGD 47,000
  • Typically done in Jan 2012, where we don't know what's the OW would be for that year
  • /309 = SGD 47,000

  • Calculated using current year's total OW
  • By year end we would know total OW
  • /309 will be calculated = SGD 85,000 (TW Cap) - SGD 48,000 = SGD 37,000
  • /309 = SGD 37,000
/310 - AW that's not paid to CPF. The amount of bonus that was not paid due to AW hitting cap.

/399 - Capping for OW - Typically SGD 5000 per month and updated in a constant T511K

/311 - Excess paid to CPF Employee
/312 - Excess paid to CPF Total
/313 - Excess paid to CPF Employer

Displaying Appendix in Forms

Report: RPCT8AR0_01

When running IR8A form, you will get Appendix 8A if you have Benefits in Kind (BiK) wagetypes and Appendix 8B if you have Employee Share Option Scheme in IT 0739.

After clicking on Print Preview to display the form, you need to press [Page Down] on the keyboard to display Appendix 8A or Appendix 8B. It will not appear by scrolling down using the scrollbar.

Sunday, November 11, 2012

Solving PG162 - Organizational Reassignment not permitted

During a Transfer Action or a Secondment Action, user is faced with the below error message. Organizational reassignment not permitted.

A quick search from table T100 reveals the error message is PG162

Having known that, do a quick search at Module Pool MP000000 for e162 and this will narrow down the reasons why the error was triggered

As seen, there could be two reasons:-
  1. The old personnel area's molga is not the same as the new personnel area
  2. PA0003-VIEKEN field was not the same with View ID returned from feature IVWID
One of the solution might be to run a program RPUPAV00 to populate the missing PA0003-VIEKEN for the employees
Program: RPUPAV00

PU03 - Change Payroll Status

When you try to change IT0003 of an employee via PA30, you will notice that there are many fields which are read-only and it seems impossible to change it. This is because usually those fields are updated by the system and not by the user.

Thus, in order to overwrite those fields, use:-

Tcode: PU03

Enter the employee number and execute F8.

The same screen is displayed except that the read-only fields are now modifiable.
Also the Delete Payroll correction button is enabled to remove the tick in the Payroll correction checkbox.

Another method of reaching the same screen through PA30, is to use the Menu Bar -> Utilities -> Change payroll status

Deleting Payroll Results

Tcode: PU01
Program: RPCDPU01

It is not recommended to delete any payroll results. However, in situations such as testing or accidental off-cycle payroll was run, this can be used.

Use transaction PU01 or execute program RPCDPU01. This transaction/program allows you to delete the payroll result per employee number.

Enter the employee number and press F8 to execute.
Select the payroll result shown and click on the Delete button

Payroll Area and Period Parameters - T549A and T549Q

Payroll Area is must know concept in SAP HR Payroll. It determines how many periods and from what start date and end date each period is. Payroll control record (maintained via tcode: PA03) will then be used to control the movement throughout the payroll area's periods.

In Malaysia and Singapore, payrolls are normally executed on a monthly basis. Therefore there usually will be Payroll Period that's named and mapped to the same month. However, do not be mistaken that 01.2012 means Jan.2012

  • [01.2012] - 01.01.2012 - 31.01.2012
  • [02.2012] - 01.02.2012 - 28.02.2012
So in order to understand clearly how a Payroll Area is built, review the configurations in these two tables (T549A) and (T549Q):-

Table: T549A
This table is used to link to the Period Parameters. It can be seen that the same 03 is used as the Period Parameter

Table: T549Q (Period Parameters)
This table shows that for Period Parameter 03, it has 52 periods for a calendar year, which means Payroll will be run on a weekly basis

Payroll - Retroactive Accounting

Used by SAP System automatically
In an employee's IT0003, there are 3 fields updated by SAP system if it detects there's a change in Master Data after payroll was run.
  1. Accounted to
  2. Earliest MD change
  3. chng.bonus
Through those fields, SAP determines which employee needs retroactive accountings and display the payroll results of those relevant payroll periods.

Applying a 'brick wall'
Using 'Earl.pers. RA date' field, we can apply a brick wall to tell the system on which date this employee can be retroactive to. This is normally filled in with the Go-Live date or is used during testing, so that retroactive processing that will take place can be predicted and controlled.

Below fields are used normally for leavers, where you will not need to run payroll for these employees anymore.
  1. Run payroll up to ( Used to run the last payment )
  2. Do not account after
Forced Retroactive processing

Sometimes, due to customizing changes that may affect payroll results in the past, you will need to force the system to process retroactive payroll for all employees, eventhough the system did not detect any changes in Master Data in the past or any employees that requires Payroll correction. This can be situations in which customizing was done in T510, T710 that affects IT0008, or CPF rates changes in T5R1C that needs to be backdated, or EPF percentage rate changes.

Thus, in order to execute this, at the Payroll Driver, enter the date into the 'Forced retro.accounting as of' field

SAP HR Payroll Process

SAP HR Payroll is basically controlled by 4 status of a Payroll Control Record. Payroll Control Record is tied to employee via IT0001.

Released for Payroll:
  • Payroll Control Record is now in 'Released for Payroll' status
  • Past and present HR Master Data is locked for those particular employees. However ,future dated changes in master data are permitted in your SAP system.
  • If the payroll is released from the “Exit” stage, the system rolls into the next payroll period, increases the payroll area period number by 1 in the Payroll Control Record (for example, from period 01/2012 to 02/2012).
Run Payroll:
  • You execute the payroll run for one payroll area, by running tcode PC00_M13_CALC for Australia
  • If errors occur, you will get a list of employees rejected during the payroll run. The system has stored the employees rejected during the payroll run in something called “Matchcode W”.
  • Only at this stage, PCL2 is actually updated
Released for Corrections:
  • Payroll Control Record is set to “Released for Correction”.
  • Past and present HR Master Data for those particular employees is now unlocked for corrections.
  • You should make appropriate corrections to fix the payroll errors for example adjusting data in IT0008, IT0014, IT0015, IT2010, etc..
  • Once you have made the appropriate corrections, you need to Release Payroll and Start Payroll using Matchcode W, which will only select the employees that were rejected during the previous payroll run.
  • You can cycle between the “Released for Corrections” and “Released for Payroll” stages as many times as necessary.
  • Employees who require corrections can be seen in their IT0003, where the checkbox for Payroll correction is ticked

Exit Payroll:
  • Payroll Control Record is set to Exit Payroll.
  • Past and present HR Master Data for those particular employees is now unlocked in your SAP system.
  • The payroll run is closed off for the particular period. You cannot go backwards in respect to payroll results.

Thursday, November 8, 2012

Report RPTQTA00 - Absence Quota Generation

Report: RPTQTA00
Tcode: PT_QTA00

Absence Quota Generation as the name implies, is to generate the absence quotas for the employees infotype IT2006 for a given period. The user normally enters the Start Date and End Date only to determine the interval to which the absence entitlements shall be generated.

The generation is based on customizing done in V_T559L, where:-
  • Applicability Tab -> Earliest Accrual (e.g. employees not yet confirmed will not have leaves accrued)
  • Accrual Period Tab -> Daily, Monthly, Calendar Year
  • Base Entitlement Tab -> 20 Days per year
  • Accrual Entitlement Tab -> Prorata/No prorata
  • Transfer Time Tab -> Other Period (Specify Period Parameters) / Upon Accrual / Transfer Package (whenever quota exceed this number it transfers, balance is retained for further accumulation)
T549R - Period Parameters, if there's a need to define custom Period Parameter with a defined unit (Hours/Months/Days) with a validity start date

No blanks for Processing Class 05 and 06

Remember do not leave wagetypes as blank in V_512W_D for:-

  • Processing Class 05
  • Processing Class 06

Otherwise, this will result in payroll dump due to Rule X006 and Rule Q030. Assign '0' to both of these processing class 05 and 06 if it's not used.

Changing Payroll Schema - Add New Line

Changing Payroll Schema

To enter a new line between line 150 and line 160, type c and press enter
Then at the same line, type a and press enter
The line would be copied as line 160 and the original line 160 has moved to line 170