First step to Understand a Payroll Schema Applies to: This article is relevant to SAP HCM module where Payroll is implemented. This applies to all SAP Releases. For more information; visit the Enterprise Resource Planning homepage. Summary This document is intended for those who are interested to know the basics of a payroll schema. The exercise in the article helps in understanding how a Payroll schema controls a Payroll driver program. Author: Sajimol C Company: Satyam Computer Services Limited Created on: 22 April 2009 Author Bio Sajimol is working with Satyam Computer Services Limited, Bangalore. She has around 5 years of experience as SAP HR Technical Consultant. 2009 SAP AG 1
Table of Contents Scope and Purpose of the Article...3 Pre-requisites...3 Create a Schema...3 Step1: Create schema ZT01...3 Step2: Edit schema ZT01...4 Step3: Create schema ZT02...5 Step4: Edit schema ZT02...5 Step5: Create schema ZT00...6 Create payroll control record...8 Run the Payroll Driver...8 Edit schema ZT02...10 Re-run the Payroll...11 Related Content...13 Disclaimer and Liability Notice...14 2009 SAP AG 2
Scope and Purpose of the Article This document can be used as a First Step to understand how a payroll schema controls a payroll driver program. The exercise detailed here gives a basic understanding on how to Create and Edit a schema, and how the payroll driver program responses to changes made in the schema. Pre-requisites The readers are expected to have a good understanding of Payroll process in SAP. Basic knowledge of following objects is helpful. 1. Payroll Area 2. Payroll Control Record 3. Payroll Driver program 4. Schema (Editor) Create a Schema The Payroll schema we are going to create is for an Organization TEST. Country grouping chosen is Australia. Naming Convention used is as follows: Z To represent a customer schema T First letter of the company name nn A unique sequence number Step1: Create schema ZT01 In this exercise we are going to copy SAP standard Payroll Accounting schema for Australia (Q000) into a custom schema ZT01. You can choose to copy any standard schema X000 where X stands for the Country code. For example U000(USA), D000(Germany), etc Transaction: PE01. Provide standard schema name, copy that into ZT01. The steps involved are explained with the screen shots below. 2009 SAP AG 3
Attributes for schema ZT01 is created automatically. Country grouping is assigned based on that of the parent schema and program class is by default C for Payroll. You can choose Country grouping * if it is applicable to All Countries. Step2: Edit schema ZT01 Transaction: PE01. Edit schema ZT01 to comment the line which calls the Payroll Initialization subschema QIN0. Subschema QIN0 is to initialize the payroll program. Comment the line COPY QIN0. A star in column D is to comment a line in the schema editor. Save schema ZT01. 2009 SAP AG 4
Step3: Create schema ZT02 Copy Payroll Initialization schema QIN0 to ZT02. Schema attributes are created automatically. Step4: Edit schema ZT02 Transaction: PE01. Edit schema ZT02 to uncomment the line CHECK ABR if it is commented. Save schema ZT02. CHECK ABR function performs the tasks: 1. Checks if the payroll period is set according to the schema. 2. Check if the payroll area has been released for payroll. If not, the payroll area is excluded. 3. Checks if there are future payroll results for the employee. If yes, payroll is not run for this Personnel number. 2009 SAP AG 5
Step5: Create schema ZT00 Check Schema can be executed check box. Save ZT00. Edit Source text. Add just two lines in ZT00. COPY ZT02 - ZT02 is copy of Initialization schema QIN0. In ZT02, Function CHECK ABR is made executable. COPY ZT01 - ZT01 is copy of main payroll schema Q000, where call to Initialization schema QIN0 is commented. 2009 SAP AG 6
Create Documentation for the Main schema. Save and Generate the schema ZT00. 2009 SAP AG 7
Create payroll control record Transaction: PA03. Payroll area chosen in this exercise is S1 TEST Payroll area Set the Payroll control record status to Released for Payroll and Save. Current Pay period is 13/2007 as per the control record. Run the Payroll Driver To run the Payroll driver program, Transaction PC00_ Mxx _CALC can be used. xx is the Country grouping code. For example PC00_M13_CALC is transaction to run payroll program for Australia. The SAP standard payroll driver program is RPCALCX0, where X is the Country code. For example driver program for the USA is RPCALCU0, for Australia it is RPCALCQ0, etc. This can be executed as any normal report program as well, using SE38 or SA38 transactions. The Variant is set as in below screen shot. Payroll driver is set to run for period 15/2007 for the given personnel number. Payroll area is S1 and payroll schema used is ZT00. Execute the program. 2009 SAP AG 8
Payroll log with Error message is displayed. Payroll period requested (15/2007) is incompatible with the period set in Payroll Control Record (13/2007). Note: If Test Run(no update) check box is selected in the payroll driver selection screen, this instructs the driver program to skip the check for control record. A simulation run will take place without any regard for the control record. 2009 SAP AG 9
Let us edit the schema to skip the check for payroll control record. Edit schema ZT02 Transaction PE01, Enter ZT02, Edit Source Text. Comment the line CHECK ABR. It is meant to check the Payroll Control record (PA03) for compatibility in case of real time payroll run. Save the schema. 2009 SAP AG 10
Re-run the Payroll Transaction: PC00_Mxx_CALC, xx being the Country grouping code. Select the same Variant as in the previous Run. Execute the program. Payroll successfully run for 15/2007 in spite of control record payroll period set to 13/2007. 2009 SAP AG 11
2009 SAP AG 12
Related Content SAP Online Help : http://help.sap.com SAP Developer Network: http://www.sdn.sap.com Helpful Ref: http://sap.ittoolbox.com For more information, visit the Enterprise Resource Planning homepage. 2009 SAP AG 13
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2009 SAP AG 14