SAP Payroll Schema. Functions , Rules and Operations – An overview

[welcomewiki]

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:

• Program Class.
  • a. There are two program classes to be assigned to the rule while creating.
  • i. Payroll (C).
  • ii. Time (T).
• 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 (*).
• 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.
• 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.

Similar Threads:

• How to read the date in Time management schema or in Payroll schema
• Topic 38: Schema (Overview)
• SAP HR Payroll Overview

[welcomewiki]

Wagetype Code:

• The Wagetype code number is the number assigned to a particular pay component.

Wagetype Description:

• 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:

• The RTE column stores a value for;
  
  • a. Rate of interest.
  • b. Number of leave days.
  • c. Projection factor. Etc.
• E.g. In the above diagram /401 wagetype has RTE value 10 which is the projection factor used for different calculations.

AMT:

• 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 forprocessing.
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:

• This Operation would fetch the Amount of the wagetype queried in the rule, in the Variable AMT for processing.
• The Syntax of the Operation is ZZZOVVVV.
• ZZZ -> AMT.
• O -> Operand.
• VVV -> Value or Variable.
• For E.g. (AMT= 1000) will fetch the Amount of Wagetype 1000 into AMT.
• 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.

[welcomewiki]

Functions:

• PIT:
  
  • This function will read the internal table IT (Input table).
  • The function will hold a rule as first parameter.
• PRT:
  • This function will read the internal table RT (Results table).
  • The function will hold a rule as first parameter.
• PDT:
  • This function will read the internal table IT (Input table).
  • The function will hold a rule as first parameter.
• PORT:
  • This function will read the internal table ORT (Old results table).
  • The function will hold a rule as first parameter.
• P0014:
  • This function will read the Infotype 0014 for processing.
  • 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.

[welcomewiki]

Please Download the Real time Scenarios

And Join us our 45 DAYS Online Training to Download 5000 Real time Screen shots.