SAP ABAP IMG Activity OHPSUSDEFER3 (Modify Payroll Schema, Subschema and Rule)
Hierarchy
☛SAP_HRCUS (Software Component) Sub component SAP_HRCUS of SAP_HR ⤷PY-US-PS (Application Component) Öffentlicher Dienst ⤷P10P1 (Package) HR Public Sector USA
Hypertext: Object Class - Class to which a document belongs.
Document Name
OHPSUSDEFER3
In this step, you create the subschema and rules that will be used to process deferred pay in your enterprise. Some of the scenarios in which you may need to adjust your schema (to meet various business requirements) are mentioned below.
The sample schemas and rules can be found in the SAPNet document.
Example
Employer related benefits/tax costs should be deferred.
Since the employer tax is a fixed percentage of the employee's pay with a ceiling on the tax, it is calculated directly using a rule. The employee's earned pay during the academic year is multiplied by that fixed percentage and stored. For example, you can store the amount in wage type 8404 for the employer Social Security contribution, and in wage type 8406 for the employer Medicare contribution. The rule must also check for any ceilings that might apply.
To track the amount for health plan, wage type 8R10 (copy of BR10) can be created in the schema by multiplying the employer contribution BR10 by 12/9 (pay periods in full year divided by pay period in academic year).
Track difference between earned and actually paid
The holdback amount, that is, the difference between dollar amount earned and dollar amount paid, can be calculated using a rule. For example, wage type PBAL can hold the difference between PSDC (gross salary earned) and PSDE (gross salary paid), PSOC can hold the difference between 8404 (Social Security tax earned) and /404 (Social Security tax paid), PMED can hold the difference between 8406 (Medicare tax earned) and /406 (Medicare tax paid), PHLT can hold the difference between 8R10 (health contribution earned) and BR10 (health contribution paid).
Transfers/Terminations
As the difference amount can be stored in wage types, depending on customer requirements rules can be written to handle the payout for transfers or terminations.
Requirements
Standard settings
Recommendation
As with other standard schemas, we strongly recommend that you do not modify payroll schema QP00 to meet the needs of your enterprise. Instead, we recommend that you copy this schema to the customer name range, then make any necessary modifications. This will ensure that any changes you make to your payroll schema are not lost upon upgrading to a higher release or applying legal change patches.
Moreover, for the sake of expedience, we recommend that you use a single number in the customer name range to replace the / found in the technical wage type name range. For example, copy /404 to 8404, /406 to 8406, and BR10 to 8R10.
Activities
Execute this IMG step.
On the following screen, select Copy.
Select a four-character name in the customer name range for the duplicate schema. Enter this name under To schema in the subsequent dialog box.
On the following screen, select Change. This will allow you to modify the copied schema, subschema and rules to the extent necessary.
Make any necessary modifications, then select Save.
Hierarchy 
SAP_HRCUS (Software Component) Sub component SAP_HRCUS of SAP_HR
PY-US-PS (Application Component) Öffentlicher Dienst
P10P1 (Package) HR Public Sector USA
IMG Activity 
Document 
History 
