Structural Authorizations Overview

Overview

Structural authorizations are used to grant access to view information for personnel where HR has been implemented. Access is granted to a user implicitly by the user’s position on the organizational plan. Structural authorizations are not integrated into the standard authorization concept and structural authorization profiles are not the same as standard authorization profiles.

Example

The use of structural authorizations can be illustrated by the following example. A manager can typically view or maintain information on employees in her organizational unit but not employees in other organizational units. When an employee moves from one unit to another his previous manager will no longer be able to view or maintain information about them. Similarly if a manager moves from one unit to another she will be able to see the employees in her new unit.

About this Document

This document shows how to set up a very simple example of structural authorizations that are assigned to Organizational Units. All the steps of setting up a test environment are documented below so you can try it too. There are some gotchas and design considerations listed up front and some additional information listed in the many appendices at the end.

Graphical Overview of Structural Authorization Components and Setup

The graphic below shows the main components of structural authorizations at a high level. The setup of structural authorizations is more complex than regular security authorizations. None of the main setup steps can be omitted or incomplete. Structural authorizations setup is analogous to an electric circuit. If there is a break anywhere in the circuit structural authorizations it will not work.

Considerations for Structural Authorization Implementation

Gotchas

•    Setting up structural authorizations has some dependencies so follow the order of the steps in this document

for best results.

•    Structural authorization profiles are not related to standard security profiles in any way.

•    Unassigned Users: User IDs that have been linked to a Personnel Master Record via Infotype 105 MUST be

assigned a structural authorization profile regardless of whether they are assigned to a node on the

organizational plan or not. (See Appendix 3)

•   There is no way to trace structural authorization checks, and structural authorization checks that fail do not

show in SU53. The closest thing to a trace is the information available in OOSP by clicking on the Blue I icon

next to the profile. This lists the effect of the structural authorization when it is working.

•   The HR Main switch: Tolerance time of the authorization check (ADAYS) which is 15 by default did not affect

the structural authorizations in this example. In tests where a manger was moved from one organizational

unit to another the effect of the structural authorizations was immediate after running report RHPROFL0. The

manager can no longer see information for anyone in their old organizational unit.

Overall Design Considerations

1. What level of the organizational plan to assign structural authorizations – we use org units in this example. This allows managers in the same org unit and same level to see each other’s information. If this was not acceptable then a hybrid approach of organizational units and positions could be used. It seems most efficient to attach structural authorizations to the highest node on the organizational plan possible. Note that we create profiles with authorization for an organizational unit but we assign these profiles to positions.

2. As mentioned in Gotchas above unassigned users linked to personnel master records with access to HR transactions can see personnel data for any user. This has an impact on how you design both standard roles and also procedures for creating roles. One way to make sure that unintended access does not occur is to assign a dummy structural authorization to every user in the system with. The dummy structural authorization should be empty. It is possible to control this using infotype 105 as well. Any user ID that is not associated with a personnel master record will not be able to view other users information with the correct standard authorizations assigned to the User ID.

Steps to Implement Structural Authorizations

1. Turn on PD PA Switch

Tcode: OOPS

Action: Ensure value registered for PLOGI – ORGA is X. No other values need to be checked or changed.

Explanation: PD and PA sub modules of HR are not configured to share data by default in the SAP delivered system. This switch must be on for data to flow between both modules.

Additional Info: None

Gotcha:

•     Do not create your Organizational Plan without this switch on.

•     If you do, structural authorizations will not work and some org and infotype setup will not work.

•     ***You cannot turn the switch on and get structural authorizations on an organizational plan, that was

created while it was off, to work.***

2.  Turn on Structural Authorizations Main Switches

Tcode: OOAC

Action: Ensure values for the main authorization switches in HR are set to the following Values

Group        Sem. abbr.        Value abbr.        Description

AUTSW     ADAYS                15                          HR: tolerance time for authorization check

AUTSW     APPRO                0                            HR: Test procedures

AUTSW     NNNNN              0                           HR: Customer-specific authorization check

AUTSW     ORGIN                1                            HR: Master data

AUTSW     ORGPD                1                           HR: Structural authorization check

AUTSW     ORGXX               0                           HR: Master data – Extended check

AUTSW     PERNR               1                            HR: Master data – Personnel number check

Explanation: The SAP delivered system has similar values as above but PERNR = 0.

Gotcha: Make sure that ORGPD = 1 otherwise structural authorizations will not work.

Additional Info: Appendix 1

3. Create Organizational Plan

Tcode: PPOM_OLD

Action:

1. Create the root of your Organizational Plan

• Organizational Plan > Create

• Enter info and click Create

2. Create Organizational Units

• Select the Organizational branch you want to build on and click Create

• Fill in the abbreviations and names of the child structures (one level at a time) in the popup dialog box.

Example of the results:

3. Create and assign positions

• Click on Staff Assignments button

• Select the unit that the position will be part of, then click on Create Positions…

• In the popup dialog box select a job description in the Choose Describing Job field group, fill in the fields in the Position field group and save.

Example of the results:

4. Designate Chief Positions

• Select the Position which will be the manager’s position and Select Edit > Chief Position > Create

• Select the position in the Create Chief Position dialog box and click on Save

Results:

Notice the position Manager of BC now has a Hat next to it and the name of the Chief is listed below the Org Unit.

Explanation: Structural authorizations work based on this hierarchy (the Organizational Plan). This is the ‘structure’ in ‘structural’ authorizations.

Gotcha:

• Don’t start this step without first ensuring the PD PA switch is on (the first step in this document).

• If we want to use Manager’s Desktop we need to designate a position as Chief. The user(s) associated with this position will only be able to access Manager’s Desktop if their position is designated as Chief. Chief positions can have more than one person assigned, i.e. a single business unit can have more than one manager at the same level.

• SAP’s documentation indicates that performance may be adversely affected by the complexity of structural authorizations.

Additional Info: None

4. Create Personnel Master Record

Tcode: PA40

Action: Create a personnel master record and assign it to the organizational plan.

1. Ensure that Personnel no. field is empty. Select a hiring action from the bottom of the screen and Click on execute.

2. Enter basic data for the master record.

• Enter a Start Date (current date is fine).

• Enter Personnel Area, Employee Group and Subgroup.

• Enter the Position Number to assign this employee to a node on the organizational plan.

• Save

3. Enter more personal data.

• Enter First and Last Name

• Select Gender

• Enter SIN number 000000000

• Enter birthday

• Save

4. Enter Information on one more screen.

• Enter the Payer Area and Subarea

• Save.

5. End maintenance for this action

• Back out of the above screen

• Yes to this message

• Record the Personnel Number on the next screen

Results:

Explanation: User ID’s are not assigned directly to the organizational plan. The User Master Record (User ID) is relatively simple and is mostly used to give access to the SAP system. In SAP a personnel master record is created and assigned to the organizational plan. The Personnel Master Record is then linked to the User ID, which is the next step in building structural authorizations.

Gotcha:

• Ordinarily all personnel master records will be assigned to a node on the Organizational Plan. See Unassigned Users in the Gotchas in the Overview at the beginning of this document for more on this issue.

• The sequence of the screens in this action can vary

Additional Info: None

5. Create User ID’s

Tcode: SU01 or SU10 (Mass Create)

Action: Create users (Suggest creating users with a name similar to the Personnel Master employee name)

Explanation: User master records must exist before you can proceed to the next step.

Gotcha: If you use mass create make sure that request ‘with log’ and print or save the log so you know what the initial password is for each user.

Additional Info: None

6. Create Infotype 105

Tcode: PA30

Action: Create Infotype 105 for each Personnel Master Record

1. Enter Personnel ID, Info Type 105 and Subtype 0001.

2. Enter the User ID in the ID/Number field

Explanation: The user master record and the personnel number have to be linked because it is the personnel number that is associated with the Organizational Plan. When the user logs on SAP needs to know which personnel number is associated with that user ID in order to grant structural authorizations.

Gotcha: None

Additional Info: None

7. Create Structural Authorization Profiles

Tcode: OOSP

Action: Create structural authorization profiles and then define the details of the authorization profile.

1. Click new entry. Enter the authorization profile names, and descriptions. Click Save. (If you don’t save here you won’t be able to see the profile in the selection list of the next step)

Check the information for a profile e.g. Manager West.

Note: No organizational plan units are shown in the list.

2. Define the structural authorization profile.

• Select a profile and click on Authorization Maintenance on the left side

• Click on New Entry

• Enter the following:

Field                            Value

Profile:                        Select a structural authorization profile

No.                                Choose an interval e.g. 10

Plan vers.                   Select a plan version probably 01

Obj. type                     In this case we are securing by Org unit. Enter O

Object ID                     In this case we are securing by Org unit. So enter the Org unit number

Maintenance              Check this on

Eval.path                      Recommend O-S-P

Status vec                      Recommend 12

Depth                              Recommend no entry

Sign                                  Recommend no entry

Period                              Recommend no entry

Function module        Recommend no entry

Explanation: We are creating structural authorization profiles here. In order to limit a user’s access to information according to the structure of the organization plan, you must define the place on the organizational structure below which a user can see personnel information.

Gotcha: Check the info button on the profile to make sure that the profile a) gives access to something and b) gives access to the right thing.

Additional Info: Appendix 2

8. Create Infotype 1017

Tcode: PO10 (Organizational Unit) or PO13 (Position)

Action: Create Infotype 1017 for all relevant nodes on the Organizational Plan. In this case all Positions (Tcode PO13)

1. Select the position

2. Select the PD Profile infotype from the scrollable list and click on Create button

3. Enter the profile name in the Profile field and click on the Save button

Explanation: This infotype links the structural authorization profile to a node on the organizational plan. In our example we use PO13 to assign the authorization to a Position. Note we can assign the structural authorization profile to other types of nodes e.g. an organizational unit but we must use different transactions for each different node type.

Gotcha: This has to be done manually. SAP documentation may seem to indicate that report RHPROFL0 will do this, it doesn’t, this step must be done manually.

Additional Info: None

9. Assign Structural Authorization Profiles to User ID’s

Tcode: SE38

Action: Use report RHRPROFL0 to automatically assign the appropriate structural authorization profile to each User ID. This program will update the table in transaction OOSB.

1. Execute the report

2. Enter the following data, the Object ID should be the object ID for the root of the Organizational Plan.

Field                                                   Value

Organizational Unit                       O

Object ID                                           e.g.50000753

Evaluation Path                             PROFL0

Test Session                                     (check on)

Leave all other defaults as they are.

3. Execute in test mode

Note: The lights in the left margin of the report are yellow. This is because the assignment has NOT been made yet.

4. Back out of this screen. Uncheck Test Session and then Execute to have the changes made.

Note: The lights in the left margin of the report are green now. This indicates that the assignment has been made.

Explanation: This report assigns a structural authorization profile to the user ID based on the Organizational Plan. If we had not first completed all the main steps listed above this report would be empty. The report is a positive indicator that some of the steps to setup structural authorizations have been completed successfully. It is possible however, to have results with this report and yet have structural authorizations that do NOT work.

Gotcha:

• Don’t forget to execute the report with Test Session unchecked!

• This report should be run daily to update the authorizations of users based on changed made in the Organizational Plan.

• Ensure that the Infotype 1017 has been populated for all relevant nodes on the Organizational Plan.

Additional Info: None

10. Setup Regular Security

Tcode: PFCG

Action: Create regular security role and assign to User ID

1. Create a role that gives access to regular HR transactions for all employees. E.g. Time Entry CAT2, PA20, PR20 Enter expenses

2. Create a role that gives access to manager HR transactions. E.g. Time Approval CADO , PPMDT Managers Desktop, PR05 Approve Expenses

Explanation: Structural authorizations are used in addition to standard security. Setup two roles to do positive and negative tests.

Gotcha: None

Additional Info: None

Appendix 1

Authorization Main Switches

Gotcha: This is SAP delivered information. It is not that easy to understand. The bottom line is make sure the Structural authorization switch and the P_PERNR switch are on.

Maintain Authorization Main Switches

In this step you maintain the authorization switch and adapt, if necessary, the profile generator specifications. You must process the profile generator specifications if you intend to make changes to the main switch settings.

You can process the authorization main switch using transaction HR: Authorization main switch (OOAC).

Using the Auth.object check under transactions transaction (SU24) you maintain whether a transaction checks an authorization and/or whether the relevant authorizations are offered in the profile generator for maintenance.

The profile generator recognizes whether authorization objects are used in transactions using the legal check status. You can process this manually, also using the Auth.object check under transactions transaction (SU24). Also check the individual authorization objects under Process check status in all transactions. Ensure that the following check indicators are set:

• When you switch on the HR: Master data (P_ORGIN), HR: Master data – extended check (P_ORGXX) and HR: Master data – personnel number check (P_PERNR) authorization objects, you must set the relevant check/maintain check status in the primary transaction that accesses these objects. You recognize these in the standard system, because the check indicator is set to check/maintain (PP) for the HR: Master data (P_ORGIN) object. In addition to this, please note the example below.

• When you switch off the HR: Master data (P:ORGIN) authorization object, you must reset the check indicator for the HR: Master data (P_ORGIN) authorization object from check/maintain (PP) to check (P).

Example (1):

The HR: Master data (P_ORGIN) object is switched on, the HR: Master data – extended check (P_ORGXX) and Master data – personnel number check (P_PERNR) objects are switched off.

No customer action is necessary.

Example (2):

The HR:Master data – extended check (P_ORGXX) object is switched on, the HR: Master data (P_ORGIN) and HR: Master data – personnel number check (P_PERNR) objects are switched on. You must set the following check status:

For the HR:Master data – extended check (P_ORGXX) object, copy the default check indicator of the HR: Master data (P_ORGIN) object. Then change the check indicator of the HR: Master data (P_ORGIN) object from check/maintain (PP) to check (P). Leave the given check status for the HR: Master data – personnel number check (P_PERNR) object as it is.

Standard Settings

In the standard system the authorization main switches and settings are defined as follows:

Switch Setting

HR: Tolerance time of the authorization check (ADAYS)15

HR: Check procedure (APPRO) 0

HR: Customer authorization check (NNNNN) 0

HR: Master data (ORGIN) 1

HR: Structural authorization check (ORGPD) 1

HR: Master data – extended check (ORDXX) 0

HR: Master data – personnel number check (PERNR) 0

Further Notes

When you use a customer authorization object (P_PNNNN) you must maintain it in the Auth. object check under transactions transaction, analogous to the HR: Master data (P_ORGIN), HR: Master data – extended check (P_ORGXX) and HR: Master data – personnel number check (P_PERNR) objects.

Example:

When the switch is off for the HR: Master data (P_ORGIN) and HR: Master data – extended check (P_ORGXX) objects and is on for the customer object (PNNNN) and HR: Master data – personnel number check (P_PERNR) object, you must reset the check status for these – corresponding to the setting of the HR: Master data object (P_ORGIN) in the standard system – to check/maintain (PP), and for the HR: Master data (P_ORGIN) and HR: Master data – extended check (P_ORGXX) to check.

Appendix 2

PD Authorization configuration fields

Auth Profile:
Chose an authorization profile. For this example we always selected the authorization profile that we were editing. Gotcha: The profiles that have not been saved will not show in the list.
Line Number:
Enter a line number for each authorization. (Each line in this screen is a separate authorization.) This is a unique identifier for the authorization. Choose any number, we chose 10 for our first authorization. The second authorization would be 20…
Plan Version:
Specify the current Plan version. Usually 01 (the active plan)
Object Type:
Specify object type We used O for Organizational Unit but you can assign authorizations to positions tasks and standard tasks too.
Object ID:
Specify the object ID of the object in the Object ID field.
Maintenance:
Two types of function codes exist. A function codes with “maintaining” and a code with “non-maintaining” attributes. The maintenance function code is linked to T77FC and is activated by flagging the Maintenance field. If the Maintenance field is flagged, maintenance is possible for the authorized objects defined in the PD Profiles.
Evaluation Path:
Select path from the list of delivered evaluation paths.  Note: You can create a custom path via the IMG – “Maintain evaluation paths.” (O-S-P).
Status Vector:
Select the planning status (1-Active, 2-Planned, etc).
Depth:
Leave blank or specify the descending level of organizational units to access.
Sign: Controls access of structure direction. (+) or blank (default) Structure is viewed from root object and down. (-) Structure is viewed in reverse from root object.
Time Period:
Use this field if you want to restrict the auth. according to the validity period of the structure. If you select the entry D the authorization is limited to structures valid on the current day. Possible entries:Blank – All, D – Current Day, M – Current Month, Y – Current Year, P – Past, F – Future

Function Module:
This field allows you to specify a function module to determine the root object of the structural authorization. Possible entries: RH_GET_MANAGER_ASSIGNMENT (Determine organizational units for manager).This function module finds the root organizational unit with which the user is related via the position and relationship A012 (manages). RH_GET_ORG_ASSIGNMENT (Organizational assignment) This function module finds the root organizational unit to which the user is organizationally assigned.

Appendix 3

Assign Structural Authorization Profile to User ID Manually

Unassigned Users: User IDs that have been linked to a Personnel Master Record via Infotype 105 MUST be assigned a structural authorization profile regardless of whether they are assigned to a node on the organizational plan or not.

Why? Users in this situation will be able to see HR data for any Personnel Master Record as long as they have the standard authorization profiles that give access to transactions where HR data can be seen, and which give access to HR data to see other people’s data.

Solution: If the user is not on the Organizational Plan we need to assign the profile manually. If the user is assigned to a node on the Organizational Plan AND that node has a structural authorization profile assigned to it, we need to run report RHPROFL0 and we need to make sure the user does not log on. If the user is assigned to a node AND that node does not have a structural authorization profile assigned to it we need to assign the profile manually.

It is possible to assign a structural authorization directly to a user instead of having the profile assigned indirectly by virtue of the user’s assignment in the Organizational Plan and the structural authorization profile that is assigned to the same node as the user. This is not the recommended approach because it will require increased maintenance. Assigning one or more structural authorizations directly to a User ID means that we are not taking advantage of SAP delivered functionality which allows implicit assignment of HR authorizations. If this approach is used then when the user is promoted for example, maintenance will have to be done on both the Organizational Plan and in Transaction OOSB. Assigning structural authorizations to users may be useful for temporary assignments, or testing.

Tcode: OOSB

Action: Assign structural authorization profile (created in OOSP) to the UserID

1. Click on New Entries button and enter the Name of the user, the name of the profile the start date, end date. And save

2. Check to see that the profile is giving access to the appropriate Organizational units Positions etc…

Explanation: This is analogous to assigning a profile generator role to a user ID. SAP needs to know what structural authorization profiles a user takes advantage of .

Gotcha: You need to assign every user in the system at least one structural authorization profile including consultants. Create a dummy authorization profile and assign it.

Additional Info: start date, end date limit the validity of the authorization so if the authorization has an end date of June 30 then on July 01 they will no longer be able to see information on their subordinates.

Related Posts

• Wage Type Configuration in SAP HR
• G/L account Configuration in SAP
• SAP Payroll Schema. Functions , Rules and Operations – An overview
• New Personnel sub area creation and relevant groupings configurations.
• Garnishment in SAP

Step by step Process to create wage type in SAP HR with screen shorts:

Step1: Create Wage Type using Transaction: OH11

Select Copy and then enter the Country.

Enter the existing Wage Type in the left column and the new WT number. Before this we need to check the last WT number associated to an Infotype.

The following tables are updated when we create the WT.

T511      Wage Type Characteristics
T512T    Wage Type Text
T512W     Wage Type Valuation
T512Z     Wage Type Permissibility
T52DZ     Assign Customization Wage type to model wage type
T52EL     Wage Type Posting
T52EZ     Time Dependency of Wage Type Posting
T591B     Wage Type Dependent retroactive accounting trigger.

Step2: Enter the description for the WT using transaction “PDSY”

Step3: Check the WT Characteristics: Go to Transaction code SM30: V_T511

Step 4: Permissibility of Wage Type: V_511_B (T511)


Step 5: PCE V_512W_D (T512T, T512W): Select the Wage Type:


Step6: Wage Type Text – V_512W_T  (T512T, T512W)

Step7: Wage Type Permissibility V_T512Z (T512Z, T591B)

Related Posts

• Structural Authorizations in SAP HR with gotchas
• G/L account Configuration in SAP
• SAP Payroll Schema. Functions , Rules and Operations – An overview
• New Personnel sub area creation and relevant groupings configurations.
• Garnishment in SAP

Find the below path to General Ledger account creation in SAP:

SPRO Path:
Financial Accounting –> General Ledger Accounting–>GL Accounts–>Master Records–>GL Accounts Creation and Processing–> Edit GL Accounts(Individual Processing)–>(Centrally/`/Co Code) (FS00 /FSP0/ FSS0)

The GL accounts can either be created centrally or for a company specific or for a chart of account specific. By creating the GL Account centrally the GL account will get created in the company code as well as in a centralized COA and the GL accounts so crated in the COA can also be extended to other Company Codes. When GL accounts are created under a COA the same has to be extended to a company code for which the GL Account to be used.

Creation of GL account using FS00 (Centrally)
In this activity, you can edit the master record of a G/L account centrally in both the chart of accounts and company code specific areas.
You can process G/L account master records as follows:
• Edit
• Change
• Create
• Create with reference
• Block
• Delete, that is, set the deletion indicator

The account group determines the fields for the entry screens if you create or change a master record in the company code.

Open item management
Determines that open items are managed for this account.
Set up accounts with open item management if offsetting entries are to be assigned to the postings made to these accounts. Postings to these accounts represent incomplete transactions.

Creation of GL account using FSP0

Creation of GL account using FSS0

In case the option of copy Chart of Account is used (OBY7) is used then the GL accounts of source COA will be copied to the target COA.

Related Posts

• Structural Authorizations in SAP HR with gotchas
• Wage Type Configuration in SAP HR
• SAP Payroll Schema. Functions , Rules and Operations – An overview
• New Personnel sub area creation and relevant groupings configurations.
• Garnishment in SAP

How to read rules and Schemas

1.Structure of relationship in Rules and Schemas:
a)Schemas consist of Functions and Sub-schemas
b)Some functions have the rules attached to it as one of its parameter
c)Rules consist of a set of operations to perform some actions
d)Operations and Functions are the executable components


As per the diagram Set of Operations make a Rule which in turn attached to some functions and those functions embedded in Schemas or Sub-schemas (Inside the main schemas) to decide the flow of the payroll program.
Structure of a Schema:


Func: This column is used to give a function name.
Par1, Par2, Par3, Par4:
1. Function has maximum four parameters.
2. The function can have zero to four parameters as per the definition of the function.
3. Pressing F4 we can get the list of all the values which can be used as parameters.
4. For some functions in the first parameter is the name of the rule created.
5. These parameter values are predefined the function is being created.
D:
1. This column is used to comment and uncomment a function.
2. If (*) is being put then the line is commented and will not be executed in Payroll processing.
3. If nothing is given then the line would be executable.
Desc
1. In this column description for the function is being used.

Functions: Functions are used for;
• Performing some payroll computations (E.g. INEPF function calculates the PF amount of an employee during payroll run)
• Calling rules (E.g. P0045 function calls a rule INLN to compute the loan details of a personnel number).
• Getting data from Infotypes (E.g. P0581 will get the data from Infotype-581 for payroll processing).
• For some decisions. (E.g. IF & ENDIF function is used to execute as per the true and false decisions) etc.

Rules:
Rules are used for holding a set of operations for a particular requirement to be accomplished.

Attributes:
1. Program Class.
a. There are two program classes to be assigned to the rule while creating.
i. Payroll (C).
ii. Time (T).
2. Country Grouping.
a. For Payroll program class the country grouping should be mentioned. (E.g. 40 for India).
b. For Time management rule the country grouping should be (*).
3. Employee Sub-grouping.
a. All the wagetypes have an attribute of employee sub-grouping.
b. It varies client to client.
c. Value 3 means EE sub-grouping is 3.
d. Value * means all EE Sun-groupings.
4. Wagetypes.
a. The wagetype in the internal table which is meant to be processed by the rule.
b. If a value for Wagetype is being given then the particular wagetype is being queried for processing.
c. If **** has been given then all the wagetypes present in the particular internal table will be processed.
Structure of the Rule.

Frequently Used Internal Tables in PY Processing:

The Payroll driver uses lots of internal tables used for storing data temporarily in the program for processing. Some of the important internal tables are:

The structure of internal tables:

EE Sub-grouping:
1. The Wagetype is assigned to a particular Employee sub-group.
2. 3 is a particular employee subgroup for basic pay wagetype.
3. * value means for all EE sub-grouping.
Wagetype Code:
1. The Wagetype code number is the number assigned to a particular pay component.
Wagetype Description:
1. The description for the wagetype code.
NUM:
1. If there is a split for the wagetypes then this NUM field will make them different.
2. If A person’s basic salary is changed in the mid of the month then the wagetype will be split in two amounts with NUM = 01 and NUM = 02.
RTE:
1. The RTE column stores a value for;
a. Rate of interest.
b. Number of leave days.
c. Projection factor. Etc.
2. E.g. In the above diagram /401 wagetype has RTE value 10 which is the projection factor used for different calculations.
AMT:
1. This column possesses the amount of the particular wagetype.

Use of the internal tables:
1. The internal tables are being used for calculations on the NUM, RTE & AMT fields.
2. These internal tables are being read by the rules row by row.
3. The Calculation rule would be only processed for those wagetypes which are specified in the rule’s source code.
4. The row in the internal table containing the wagetype which has been defined in rule attributes will be placed in the header of the internal table for processing.
5. The processing would be as per the operations used in the rule.

Some important Operations & Functions:

• The editor for Operations and Functions is PE04.

• While the payroll driver encounters a function and operation it would call a subroutine written in the payroll driver.
• The subroutine name for the operation will be OP****, Where **** will be the name of the operation.

• For E.g. for Operation AMT the subroutine name would be OPAMT.

• The code written for the function will be found as a subroutine in payroll driver as FU****, where **** will be the name of the function.

• For E.g. for function INEPF the subroutine name would be FUINEPF.

Operations:

AMT:
1. This Operation would fetch the Amount of the wagetype queried in the rule, in the Variable AMT for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> AMT.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (AMT= 1000) will fetch the Amount of Wagetype 1000 into AMT.
7. Pressing F1 on the AMT Operation will provide the documentation.

RTE:
1. This Operation would fetch the Rate of the wagetype queried in the rule, in the Variable RTE for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> RTE.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (RTE= /401) will fetch the Rate of Wagetype /401 into RTE.
7. Pressing F1 on the RTE Operation will provide the documentation.

NUM:
1. This Operation would fetch the Split indicator of the wagetype queried in the rule, in the Variable NUM for processing.
2. The Syntax of the Operation is ZZZOVVVV.
3. ZZZ -> NUM.
4. O -> Operand.
5. VVV -> Value or Variable.
6. For E.g. (NUM= 1000) will fetch the Split indicator of Wagetype 1000 into NUM.
7. Pressing F1 on the NUM Operation will provide the documentation.

ADDWT:
1. This Operation will append one more row in the internal table (Processed by the rule).
2. After calculating an amount from a particular wagetype the amount can be assigned to another wagetype and append to the internal table.
3. For E.g. ADDWT 2050 will add the NUM, RTE, AMT calculated to the NUM, RTE & AMT of the wagetype 2050.
4. If the Wagetype 2050 is not there before in the internal table then NUM, RTE & AMT would be 0.
5. If any value of these three variables are present before then they will be added to the calculated ones.

Functions:

PIT:
1. This function will read the internal table IT (Input table).
2. The function will hold a rule as first parameter.

PRT:
1. This function will read the internal table RT (Results table).
2. The function will hold a rule as first parameter.

PDT:
1. This function will read the internal table IT (Input table).
2. The function will hold a rule as first parameter.

PORT:
1. This function will read the internal table ORT (Old results table).
2. The function will hold a rule as first parameter.

P0014:
1. This function will read the Infotype 0014 for processing.
2. The function will hold a rule as first parameter.

N.B.
The documentation for all the Operations and Function is being provided, which can be viewed in PE04 (Editor for Operation and Function).

Few examples and live scenarios on writing PCRs related to Time schema.

Scenario. 1

The employees in a company accrues 2.5 days of Privilege Leave (PL) per month . But if they go on Unpaid leave (Ex: Education leave) or there is unrecorded absences the accrual entitlement has to be  reduced. Actually if there is more than 10 days of Unpaid Leave and Unrecorded absences per month then the PL earned by an employee during the month is 0 else it is 2.5 Days

Environment

The organization has gone in for HR-Positive time keeping with clock-times and every employee has specific shift on any given day . The HR team runs time evaluation on a daily basis which basically compares the employee’s planned work schedule with actual attendance and decides on the employee’s attendance status . If there is no information from the employees on a working day the system marks him/her unrecorded absence. Also if there is authorized Unpaid leave (Study Leave) the HR Team enters the leave data in to the system

Implementation steps

Set Up Leave  Type – Education Leave as Unpaid leave and PL

Set up Time types

Set up PL Quota Configuration

Write PCR for Populating

Solutions Description

Configure Leave types :

IMG Path: Personnel Time Management–>Time  Data Recording and Administration–> Absences–>Absence CatalogàDefine Absence Types

Table : V_T554S

Following Leave types needs to be configured:

Absence  type Code :             0100

Description                            Privilege Leave

Absence type Code :               0401

Description                            Study  Leave

Determine Entry Screens and Time constraint classes

IMG Path: Personnel Time ManagementàTime  Data Recording and Administration àAbsencesàAbsence CatalogàDetermine  entry Screens and Time constraint class

Table : V_554S_O

Following Leave types needs to be configured:

Absence  type Code :                 0100
Screen Number                          2001
Att/Abs Indicator                      A
Absence type Code :                 0401
Screen Number                         2000
Att/Abs Indicator                     A

Absence Counting rules
IMG Path: Personnel Time ManagementàTime  Data Recording and Administration àAbsencesàAbsence CatalogàAbsence CountingàRules for Absence counting(New)àDefine Counting rules
Table : T556C
Following Counting rules needs to be configured:
Counting rules  :                  100
Description                          Counting rule for PL
Week Days                           Check all the days
Day Types                            Check all Day types
Holiday classes                    Check all Holiday classes
Counting class for PWS        Check all the Counting classes
Daily Work Schedule class   Check all
Planned  Hours=0                Check
Planned Hours > 0               Check
Condition for ATt/Absence  Check only  Full Day
Counting Hours/Days          Quota Multiplier ( 100%)
Rounding Rule                      ZA

Counting rule      :                401
Description                          Counting rule for Study Leave
Week Days                           Check all the days
Day Types                            Check only Day type=0
Holiday classes                    Check only Holiday class = 0
Counting class for PWS        Check all the Counting classes
Daily Work Schedule class   Check all
Planned  Hours=0                Do not check
Planned Hours > 0               Check
Condition for ATt/Absence         Check < 1 day as well as Full day
Counting Hours/Days                 Quota Multiplier ( 100%)
Rounding Rule                             ZA

Assign Counting rules to Absence types

IMG Path: Personnel Time Management–> Time  Data Recording and Administration –> AbsencesàAbsence Catalog–>Absence Counting–>Assign counting rules to absence types
Table : T556C
Counting rules need to be assigned to Absence types
Absence type                      0100
Counting rules  :                 100
Check ‘Quota Deduction’ Check box
Absence type                      0401
Counting rule      :              401
DO NOT check Quota deduction check box

Define Absence quota Types
IMG Path: Personnel Time Management–>Time  Data Recording and Administration –>Managing time accounts–>Time Quota Types–>Maintain Absence quota Types
Table : V_T556A
Create Absence Quota Types
Absence quota  type              10
Description                            Privilege Quota

Permit Generation of Quotas in Time Evaluation
IMG Path: Personnel Time Management–>Time  Data Recording and Administration –>Managing time accounts–>Calculating Absence quota entitlements–>Automatic accrual of Absence quotas
Table : V_556A_B
Absence quota  type              10
The Radio-button ‘Increase’ needs to be checked

Configure time types :
IMG Path: Personnel Time Management–>Time  Evaluation–>Time Evaluation settings–> Define Time types
Table : V_T555A
Following time type needs to be configured:
Time type Code :                   9P01
Description                            PL Quota Accrual Multiplier
Cumulate Day Balance           1
Cumulate Period Balance       1
Time type Code :                   9P18
Description                        Unrecorded Absences During Planned Working Hrs
Cumulate Day Balance           1
Cumulate Period Balance       1
Time type Code :                   9P22
Description                        Late Coming Hours
Cumulate Day Balance               1
Cumulate Period Balance            1
Time type Code :                    9P23
Description                        Early going hours
Cumulate Day Balance               1
Cumulate Period Balance           1
Time type Code :                    9P24
Description                        Unrecorded Gaps other than Late Coming / Early Going
Cumulate Day Balance               1
Cumulate Period Balance           1
Time type Code :                   9P26
Description                        Late Coming Hours(Processed)
Cumulate Day Balance               1
Cumulate Period Balance           1
Time type Code :                   9P27
Description                        Early going hours(Processed)
Cumulate Day Balance               1
Cumulate Period Balance           1
Time type Code :                   9P28
Description                        Unrecorded Gaps other than Late Coming / Early Going                   (Processed)
Cumulate Day Balance               1
Cumulate Period Balance            1
Time type Code :                   9P35
Description                        Total Unpaid absence in Days
Cumulate Day Balance               1
Cumulate Period Balance           1
Time type Code :                   9P36
Description                        Total Unrecorded absence in Days
Cumulate Day Balance               1
Cumulate Period Balance           1

Set Base Entitlements
IMG Path: Personnel Time Management–>Time  Data Recording and Administration –>Managing time accounts–>Calculating Absence quota entitlements–>Rules for Generating Absence QuotasàSet Base EntitlementsàBase Entitlement for Absence quota generation
Table : V_T559E
Absence quota  type                10
Entitlement (Constant)             2.5 Days
Related to Period                  Time Evaluation Period

Determine Validity & Deduction Period
IMG Path: Personnel Time Management–>Time  Data Recording and Administration –>Managing time accounts–>Calculating Absence quota entitlements–>Rules for Generating Absence QuotasàDetermine Validity & Deduction period
Table : V_T559D
Absence quota  type                10
Validity From                      Time Evaluation Period – Start
Validity End                        Time Evaluation Period-End
Deduction From Date          Validity End + 1 Day
Deduction to Date               Validity End + 999 Months

Define Generation Rules for Quota Selection
IMG Path: Personnel Time Management–>Time  Data Recording and Administration –>Managing time accounts–>Calculating Absence quota entitlements–>Rules for Generating Absence QuotasàDefine Generation rules for Quota Selection
Table : V_T559L
Absence quota  type                10
Accrual Period                     Time Evaluation Period
Accrual Entitlement
Multiplication with Time Balance
Period Balance                     9P01 (Time Type)
Transfer Time                      Upon Accrual

Define Quota Deduction rules

IMG Path: Personnel Time Management–>Time  Data Recording and Administration –>Managing time accounts–>Quota Deduction using attendance/Absence–>Define Deduction rules Using Attendance/Absence QuotasàDefine Deduction rules using Absence quotas
Table : V_556R_B
Deduction Rule                      100
Absence Quota Type              10
Other Data can be the default values

Assign Deduction rules to Counting rules

IMG Path: Personnel Time Management–>Time  Data Recording and Administration –>Managing time accounts–>Quota Deduction using attendance/Absence–>Define Deduction rules Using Attendance/Absence QuotasàAssign Deduction rules to Counting rules
Table : T556C
Counting Rule                       100
Deduction rule                      100

Describe Absence Valuation rules

IMG Path: Payroll International–>Absences–>Describe Absence Valuation rules
Table : V_T554L
Create two Valuation rules as follows :
01 Paid Leave
02 Unpaid Leave

Group Absences for Valuation

IMG Path: Payroll International–>Absences–>Group Absences for Absence Valuation
Table : V_554S_G
Following configuration needs to be done
LeaveType          Description                         Valuation Rule
0100                       Privilege Leave                 01
0401                       Study Leave                       02

Create Counting classes for Absence  Valuation

IMG Path: Payroll International–>Absences–>Valuation of Absences–>Create Counting classes–>Define Counting classes
Table : V_T554E
Following configuration needs to be done
Counting class   Description
01                           Paid Leave
02                           Unpaid Leave

Setup Counting classes for Absence  Valuation

IMG Path: Payroll International–>Absences–>Valuation of Absences–>Create Counting classes–>Set up counting classes for Absence valuation
Table : V_T554C

Following configuration needs to be done
AbsValGrpg        Valuation Rule   CC for Absences               Paid (Check Box)               Percentage

01                01                     01                         Check it                        100%

01                02                     02                         Do not Check it                 100%

Write following rules for PL Accrual

Rule ZI01:

This rule is written to compute the Unpaid absence days and store the same in Time type 9P35. In this context whenever an employee avails leave under leave type 0401 these leave days are stored in time type 9P35.This rule should be called by the function PTIP.(Refer Scenario 1)

The rule should be called as follows:

PTIP ZI01

Rule ZI02

This rule moves the unrecorded Absences to 9P36 from 9P63 .(Please refer Scenario 1)

This rule should be called as follows :

ACTIO ZI02

Rule ZI06

This rule is written to compute and Populate the time type 9P01 (PL Quota Multiplier). If period Balance of 9P35 and 9P36 is less than or equal to 10, the rule should move 1 to 9P01 else move 0 to 9P01

This rule should be called by function ACTIO and should be called just before CUMBT function

Scenario.2

Unrecorded Absences(Late Coming / Early going hours)

The employees have a specific planned work schedule and they need to clock-in to the work place at a particular time and are supposed be in the work spot for a specific number of working hours . If an employee clocks-in later than the planned start time  , then he should be penalized for ‘Late-Coming’ and if an employee clocks-out earlier than the planned work end time then he should be penalized for ‘Early going’. However there are physically challenged employees who are allowed to clock-out earlier than the planned end time for a specific number of minutes . The penalty for Late-coming or Early-going is not exactly the number of minutes the employee clocked-in late or clocked-out early , but rounded as per the business rules of the Organization. The penalty is in the form of deducting amount from the salary in Payroll , proportional to the ‘Late Coming’ / ‘Early Going’ minutes/ hours .

Environment

The organization has gone in for HR-Positive time keeping with clock-times and every employee has specific shift . The HR team runs time evaluation on a daily basis which basically compares the employee’s planned work schedule with actual attendance and decides on the employee’s attendance status .

Technical Interpretation

The employee’s time events are compared with the planned start time and planned end time of the scheduled shift . The time pairs are formed by the system on this basis . Whenever the unrecorded time pair exists with the start time of the time pair as same as start time of the planned shift then the duration of such time pair can be designated as Late Coming Hours . Similarly Whenever the unrecorded time pair exists with the End  time of the time pair as same as End time of the planned shift then the duration of such time pair can be designated as Early Going Hours

Solutions Description

Configure time types :

IMG Path: Personnel Time ManagementàTime  EvaluationàTime Evaluation settingsà Define Time types

Table : V_T555A

Following time type needs to be configured:

Time type Code :                              9P18

Description                                         Unrecorded Absences During Planned Working Hrs

Cumulate Day Balance                  1

Cumulate Period Balance             1

Time type Code :                              9P22

Description                                         Late Coming Hours

Cumulate Day Balance                  1

Cumulate Period Balance             1

Time type Code :                              9P23

Description                                         Early going hours

Cumulate Day Balance                  1

Cumulate Period Balance             1

Time type Code :                              9P24

Description                                         Unrecorded Gaps other than Late Coming / Early Going

Cumulate Day Balance                  1

Cumulate Period Balance             1

Time type Code :                              9P26

Description                                         Late Coming Hours(Processed)

Cumulate Day Balance                  1

Cumulate Period Balance             1

Time type Code :                              9P27

Description                                         Early going hours(Processed)

Cumulate Day Balance                  1

Cumulate Period Balance             1

Time type Code :                              9P28

Description                                         Unrecorded Gaps other than Late Coming / Early Going                                                                                   (Processed)

Cumulate Day Balance                  1

Cumulate Period Balance             1

Time type Code :                              9P63

Description                                         Temporary Time type used as variable

Cumulate Day Balance                  1

Cumulate Period Balance             1

Configure Rounding Rule

IMG Path: Personnel Time ManagementàTime Data Recording and Administrationà Absencesà Absence Catalogà Absence Countingà Rules for absence countingà DefineRounding rules for counted absences

Table : V_T559R

Set Time type determination

IMG Path: Personnel Time ManagementàTime  EvaluationàTime Evaluation with clock timesà Time data processingà Set Time Type Determination

Table : V_T555Z

The time type 9P18 has been configured as Unrecorded absence during planned working hours

Configure Maximum  Early Going hours for Handicapped employees

(Payroll Constant : ZIT01)

IMG Path: Personnel Time ManagementàTime  EvaluationàTime Evaluation with clock timesà Time in lieu & split leave à Maintain Constant

Maintain Master data  for Handicapped employees

For handicapped employees through Master data maintenance ‘Additional Indicator’ in Infotype 50 need to be maintained as ‘1′ .

Write following rules for computing the Late coming / Early going / Unrecorded gaps

Rule ZI03:

This rule is written to segregate the Late coming . Early going and other unrecorded gaps separately and also move the late coming hours to the time type 9P22. If the pair is early going pair the rule branches off to sub rule ZI05 and if the pair is unrecorded gaps then the rules branches off to sub rule ZI04

This rule is called by the function PTIP .

Rule ZI04

This rule moves the unrecorded gap hours to the time type 9P24.This rule is called by the rule ZI03

Rule ZI05.

This rule basically computes the early going hours . For handicapped employees this rule checks against the allowed limit of early going hours by looking at the Payroll constant ZIT01 . If the actual early going hours is less than the allowed hours then the early going is ignored else the hours of the time pair is passed onto the time type 9P23 .This rule is called by the rule ZI03

Rule ZI13

This rule rounds off the late coming and early going hours and also ensures that sum of Early going , Late coming and unrecorded gaps does not exceed the planned working hours .The rounded and processed Late coming Days, Early Going days and Unrecorded gap days are stored in the time types 9P26, 9P27 and 9P28 respectively. Finally sum of 9P26, 9P27 and 9P28 is passed on to the time wage type 9T28 for deduction of salary in Payroll.

This rule is called by the function ACTIO

Both these rules (ZI03 and ZI13) should be called in schema TM00 after the function TIMTP.

Related Posts

• Structural Authorizations in SAP HR with gotchas
• Wage Type Configuration in SAP HR
• G/L account Configuration in SAP
• New Personnel sub area creation and relevant groupings configurations.
• Garnishment in SAP

New Personnel sub area creation and relevant groupings configurations.

1) Create Personnel sub area for a Personnel Area

2) Pay scale Structure to Enterprise Structure

3) Personnel subarea to Primary Wage Types

4) Personnel subarea to Work schedules

5)Work schedules Use value 10 for all

6) Public holiday calendar

7) Assign PA/PERSONNEL SUBA REA to Tax Company code

Go to Payroll section –> US Payroll –> Tax –> Assign company to Personnel Area

Double click the relevant entries and assign the right company code on the next screen

Assignment Comments:

T5U0P: Assign tax company to personnel area

V_001P_M: Define Groupings for the Public Holiday Calendar

V_001P_N:Group Personnel Subareas for the Work Schedule

V_001P_C: Check Assignment of Pay Scale Structure to Enterprise Structure

V_001P_K: Personnel Subareas for Primary Wage Type

V_T001P: Personnel Subareas

Find the below Link with screen shorts.
create-psa-for-a-pa

Related Posts

• Structural Authorizations in SAP HR with gotchas
• Wage Type Configuration in SAP HR
• G/L account Configuration in SAP
• SAP Payroll Schema. Functions , Rules and Operations – An overview
• Garnishment in SAP

Q1. What is a garnishment?
A1. Garnishments are payroll deductions which differ from other types of deductions in that they are governed by goverment and judicial rules. They are compulsory for both the employee and employer. The employer generally is liable for 100% of the amount it fails to withhold pursuant to a garnishment order and penalties and punitive damages can be imposed for failure to properly comply with the terms and conditions of an order.

Q2. How is a garnishment initiated and what is the process?
A2. Generally, an employee experiences financial trouble and a court mandates an order that stipulates the deduction amount and frequency which is received by the employee’s HR department, the information is then entered into R/3, the amount is deducted when processing RPCALCU0, the vendor is paid via Third Party Remittance and the employee and vendors are notified of these deductions through automatically generated letters.

Q3. What types are garnishments are there?
A3. R/3 handles 5 main categories:
Support (child, spousal, and medical)
Creditor
Federal debts (student loans and administrative wage
garnishments (AWG))
Federal and State Tax Levies
Voluntary Garnishments

Q4. What is the difference between Exempt and Non-Exempt amounts?
A4. The exempt amount is the amount which cannot be taken to satisfy a
garnishment and the non-exempt amount is the amount that can be taken.

Q5. How is the exempt and non-exempt amounts calculated?
A5. Various rules apply based on the type and priority of the garnishment. There are Federal and State rules and the state rules will vary from state to state.

Q6. What if an employee has multiple garnishments?
A6. Garnishments are processed based on priority rules. Generally, child support orders have the highest priority, Federal Tax Levies have the second highest priority and then other types of garnishments are on a first come, first serve basis.

Infotypes -
Q7. What infotypes are used within R/3?
A7. There are three infotypes designated for garnishment processing.
IT0194 – Garnishment Document
IT0195 – Garnishment Order
IT0216 – Adjustments
The document information is entered on IT0194 and the actual deduction amount and frequency is entered on IT0195. The two infotypes are linked via a system generated internal number and you can have multiple orders (IT0195) for one document (IT0194) and these are linked via a system generated sequence number. Infotypes 0195 and 0216 can only be created once an IT0194 record has been created and saved. For processing purposes, RPCALCU0 reads IT0195.

Q8. How do I make changes to an existing Garnishment Order (IT0195)?
A8. With Edit -> Copy, you can make changes to the Order, but keep the same sequence number and maintain a history in the system. With selecting Change, you can make changes but no history is maintained. Also, a change can be made through creating a new IT0195 which maintains history, however a new sequence number is generated and the order is now processed as a separate order in R/3 and does not cumulate as part of the original order. IT0195 should always be accessed via IT0194 when making changes.

Q9. When should I use the Adjustment IT0216?
A9. IT0216 should be used to correct errors in RPCALCU0; additional deductions are required; to enter a new balance; refund from vendor; exceptional payments; separate calculation; calculate end date;
or stopped vendor payment.

Customizing

Q10. What are the relevant tables for Garnishment Processing?
A10. T5UG0 – Garnishment Order Types
T5UG1 – Garnishment Categories
T5UG2 – Adjustments to the Disposable Net
T5UG3 – Model for the Non-exempt amount
T5UG4 – Rules for calculation of Non-exempt amount
T5UG5 – Model Key and Text for Adjustments to the Disposable Net
T5UG6 – Government Rules for Service Charges
T5UG7 – Government Rules for 3PR
T5UG8 – Company Rules for 3PR
T5UG9 – Garnishment Default Values
T5UGA & T5UGB – Special Rules for the Calculation of the
Non-exempt amount
T5UGA – Rule Key/Names & Texts for special variables to
display on IT0195 screen
T5UGB – Sequence of Operations to be performed
T5UGC – Service Chg Rule Key and Text for Country/State/Document
category combination
T5UGD – Levy Form – Filing Status listed
T5UGE & T5UGF – Levy Form – Exempt amount and additional
exempt amount for each filing status
T5UGG – Company Rules for Service Charges
T5UGH – Levy Form – Forms Defined
T5UGI – Letters – Select Form & User exit for letter type
T5UGJ & T5UGK – Not Customizing Tables, used for the Printing
Request for the Notice and Answer Letters
T5UGL – Letters – Definition & location of user exit
T5UGM – Garnishment Originator on IT0194

Payroll Processing -
Q11. What are the wage types associated with Garnishments?
A11. /G00 – Disposable Net
/G01 – Gross for Garnishment
/G02 – Completely Non-exempt
/G03 – Garnishment Total Amount Deducted
MG10 trough MG70 delivered templates for Garnishments to be taken

Q12. What are the Garnishment Cluster Tables and what do they represent?
A12. GRDOC – corresponds to garnishment document (IT0194)
GRORD – corresponds to garnishment order (IT0195) or garnishment
adjustment (IT0216)
GRREC – actual deductions and wage types and also used to carry
forward results

Q13. Where are garnishments calculated in RPCALCU0?
A13. Garnishments are processed via the schema UGRN following the calculation of taxes (UTX0). The actual amount to be taken is
calculated with the function UGARN.

Q14. What is the main garnishment Include?
A14. The main garnishment include is RPCPIUU0 – forms called by
UGARN. Also of importance is RPCPIUF0 – function UGARN.
Quick Tips for Troubleshooting Garnishment Processing
Q1. What are some items to check when troubleshooting Garnishment Processing in R/3?
A1: Review the following:
o On IT0194, check the validity dates, determine what kind of garnishment, how many are involved and the status of the garnishment (e.g. active, pending).
o Check the IT0195 validity dates and note the Remit Rule, deduction amount, frequency and how many IT0195’s are involved.
o Review RPCLSTRU and the payroll dates in question, keep in mind the information found on IT0195 and the Garnishable period is from the beginning of the pay period to the actual check date. Garnishments are deducted based on the check date.
o Within the EE’s results, also check for wage types /G00, /G01, /G02 and /G03 and the wage type for the garnishment to see how much was deducted.
o Still within the EE’s results, review the GRORD record and check the limit, disposable net, month to date, deduction to vendor (DEVEN) and the deduction from infotype (DEINF).
o Multiple garnishment processing, be sure the system can legally take all the garnishments.
o Check schema UGRN for any customer modifications.
o Double check that Notes have been applied correctly and completely.
o Review the Garnishment History either via IT0194 or IT0195 which lists the actual deductions taken with the check date.
o Also via IT0194 or IT0195, you can view Customizing details (Environment -> Customizing details; 4.6C Extras -> Customizing Review)
o Both the Disposable Net and calculated Net Pay should be the same.
Q2. Why was an IT0216 record not processed?
A2. IT0216 can be edited/deleted before running payroll. If payroll is run and there is no wage type listed on IT0216, this record will not be read nor will it be posted to FI.

Q3. Why does a deduction occur after the initial balance has been met?
A3. It is most likely misconfiguration of the Ordre Category (table T5UG0). Usually, it is a State Levy that has been given the Order Category of a Federal Levy. A State Levy should have the Order Category ‘3? for Generic in table T5UG0. The order category ‘2? Levy only applies to a Federal Levy. Also, a Federal Levy will not stop when an initial balance is reached because by law, it can only be manually stopped by changing the status of IT0194 to ‘4? Released, once the company has received Form 668-D from the IRS. (Please Review Related Note 521735.)

Q4. How is General Disposable Net calculated?
A4. There are two ways to calculate general Disposable Net (/G00).Either start with the gross amount (/101) and subtract exempt amount or start with 0 and add up all the earning wage types to be included (e.g. M003). This is configured via PRCL 59, double check the values for the wage types in question for this PRCL. A useful tool for checking Processing Classes for wage types is program RPDLGA20 (choose the Output radio button ‘Tree Structure’).

Q5. How are garnishments and Arrears handled?
A5. Garnishments do not follow the same Arrears principles as other deductions. The arrears functionality for garnishments only refers to deductions within a particular month. If the total amount of a garnishment cannot be taken for the month, the remaining amount does not carry forward to the next month. The values for Arrears processing are set in table T51P6 and for all garnishment wage types, the value for Arrears should be a ‘4? and the Retro column should be blank in this table.(Please see Note 338841.)

Q6. Can Garnishment wage types be entered on a NAMC (IT0221)?
A6. No, Garnishment wage types cannot be entered on IT0221.There is a V0 split indicator that connects garnishment Wage types to garnishment tables and there is no V0 split on IT0221.

Q7. How are garnishmnents handled during Retroactive Accounting?
A7. Garnishments will not recalculate in a retrocalculation. The amount originally deducted continues to be carried forward. Consequently, no retroactive changes should be performed for garnishments. If changes need to be made, perform an EDIT – >COPY operation that will result in delimiting the IT0195 record.

Q8. What do I check for priority issues; double, incorrect or missing deductions?
A8. First check IT0194 and IT0195 and their validity dates and priority. Make sure the Rule in IT0195 was customized to do what is expected. Look at the Disposable Net and Non-exempt models.

Q9. What should I check if Payroll Abends within UGARN?
A9. Check the payroll results GRREC for a record without a wage type.

Q10. Is it possible to specify a percentage or portion of a wage type?
A10. At this time, the garnishment module does not offer a functionality that would allow specifying a percentage and/or portion of a wage type to be deducted other than from gross and net. The workaround is to create a special rule with the garnishment orders having different priorities and different IT0194 records.

BY Subbarao Pathangi…….

Related Posts

• Structural Authorizations in SAP HR with gotchas
• Wage Type Configuration in SAP HR
• G/L account Configuration in SAP
• SAP Payroll Schema. Functions , Rules and Operations – An overview
• New Personnel sub area creation and relevant groupings configurations.