SAP Human Capital Management

Week 9
Instructor Name:Khadija Shakil
Course Schedule
Su Unit 1 Payroll Overview
01

Su Unit 2 Payroll Data

02

Su Unit 3 Payroll Elements

03

Su Unit 4 Payroll Process

04

Su Unit 5 Payroll Reports

05

Su Unit 6 Post Payroll Results

06

Su Unit 7 Process Model

07
Unit 1 Payroll Overview
Payroll is the calculation of payment for work performed by each employee. Payroll comprises a number of work processes,
including the generation of payroll results and remuneration statements, implementation of bank transfers, and facilitation of
check payments.
Payroll also covers a number of subsequent activities, such as the posting of results to Financial Accounting (FI), and other
evaluations, such as for taxes.

Payroll Prerequisites:
A number of prerequisites must be met before you can enter and
process employee data in the system. SAP provides you with a series
of model entries, which you can adapt to meet the needs of your
particular enterprise.
Remuneration or wages are calculated in the following steps:
Calculation of remuneration elements
Calculation of statutory and voluntary deductions, which are country-specific
Remuneration elements, statutory deductions, and voluntary deductions are based on individual payments and deductions that
are calculated for an employee during a payroll period. The payments and deductions are stored as wage types and then
included in the payroll calculation.

types used in a payroll period.

The following payments can be included in the calculation of remuneration:
Basic pay
Bonuses
Vacation allowances
Christmas bonuses
Gratuities
If an employee participates in regular benefits such as health, insurance, savings plans as well additional benefits, such as a
company-owned apartment or company-sponsored day care services, this can lead to deductions from the employee's pay.

The wage types can be entered online or generated during the payroll run.
To determine the payment amount, statutory and voluntary
deductions, such as taxes and social insurance contributions, are taken
into account.
Deductions are calculated on the basis of gross values, such as the
total gross amount and the gross tax amount. For this reason, various
amounts are calculated during the payroll run, which are then used for
subsequent processing.
Both HR master data and a large number of Customizing table entries include a start and end date. The payroll program requires
these dates so that it can perform calculations for specific days and retroactive accounting for previous periods.

The system recognizes changes to payment infotypes and

triggers retroactive accounting.
For example, when you make changes to the master data for
earlier periods, the arrears are calculated automatically and

system recognizes retroactive accounting automatically, you

cannot change the payroll results manually.
If you change the HR master data for a period for which the payroll has already been run, the payroll must be run again for the
same period using the current values. This is known as retroactive accounting.
The periods for which the payroll has been completed and exited constitute the payroll past. If you make any changes to an
infotype associated with retroactive accounting, the Earliest MD Change field in the Payroll Status infotype (0003) is set to the
start date of the changed infotype. This ensures that retroactive accounting is automatically triggered up to the retroactive
accounting date when the next payroll is performed.
Unit 2 Payroll Data
 e,
leaving, and rehiring can take place.
Some of these events can be relevant to remuneration and they need to be tracked by updating the relevant infotypes. If these
events occur in the payroll past, they trigger retroactive accounting.
Events that can trigger retroactive accounting are as follows:
Hiring
Organizational reassignment
Deviations from the work schedule
Retroactive salary increase
Time sheet information received late
Retroactive hourly rate increase
A hiring action consists of a series of standard infotypes that are required for any country. Some infotypes, such as tax data, are
country-specific. If you set the user parameters for a particular country, such as 01 for Germany or 10 for the USA, the system
accesses the appropriate personnel actions, which include all the relevant country-specific infotypes.
Employee data may change in any payroll period due to transfers, substitutions, increase or decrease in basic pay, or simply
corrections.
You can create data or copy and change existing data to create new entries. At times, you need to enter data in a series of
infotypes while at other times, you need to access a single infotype

Deviations from the work schedule usually make up the largest share of tasks that are periodically performed in an HR
department. In the system, deviations take the form of time data, such as hours or days, or remuneration data. To ensure that
the correct amount of time and overtime payments is available, you must enter the data in the system at the right time.
Fast data entry increases the efficiency of data processing, because the same infotype record can be created and maintained for
more than one employee at the same time. This means that you do not need to enter a separate record for each individual
employee; you can use a single screen to enter the data for more than one employee simultaneously.
Various processing options are available, such as creating, changing, copying, deleting, and locking or unlocking records.
You can use any of the following ways to select the personnel numbers to be processed:
You can enter the personnel numbers directly on the fast entry screen.
You can list the personnel numbers yourself before maintaining the fast entry screen.
You can use a report to list the personnel numbers on the basis of specific search criteria.
You can choose your own selection criteria using Ad Hoc Query.
Unit 3 Payroll Elements
You can perform a payroll run at different times, for example, at the beginning of the month, and with different frequencies, such
as monthly. Payroll consists of different phases that take place sequentially. You can control payroll using various payroll areas
and payroll control records.
You must make the following settings in Customizing to perform a payroll run:
Payroll areas:
You define a payroll area to group employees for whom payroll is run at the same time, and who are paid on the same date. You
also define a payroll area to set the dates for the payroll period. A period parameter and a date modifier are assigned to each
payroll area.
Payroll periods:
You define a payroll period to represent the period for which a regular payroll is run. Payroll periods must be generated for each
combination of period parameters and date modifiers assigned to a payroll area. A payroll period is identified by a period number
and a year. The start and end dates for each period are defined; and the payday is calculated using a rule entered as a parameter.
Each period parameter is assigned to a time unit. The values for time units are defined as monthly, semi-monthly, weekly,
biweekly, every four weeks, and annually.
Control records:
You create a control record for every payroll area to control the individual stages of the payroll process.
You must create payroll areas if you want to run payroll for
employees at different times. For
example, if you want to pay employees on a monthly or
weekly basis, you must create at least
one monthly and one weekly payroll area.
Employees from different employee subgroups can belong
to the same payroll area. The only
criterion for grouping employees in the same payroll area
is that they should be paid for the
same period and on the same payment date.
You can use a payroll area as a selection criterion for many payroll processes. For example, you can use a payroll area to run
payroll, generate the remuneration statement, and create evaluation reports for the payroll run. If you want to select fewer
employees for a payroll run or other evaluations, you can use additional selection criteria, for example, the cost center, or the
employee subgroup.
However, such a selection is suitable only for test and simulation purposes, because the payroll control record is
not taken into account in the simulation run.
The ABKRS feature delivers a default value for the Payroll Area field in the Organizational Assignment infotype
(0001)
A payroll period determines the period for which a payroll result is created. The length of payroll periods can differ. For example,
a payroll period can be a month, a week, or fourteen days.
The exact start and end dates of payroll periods must be defined for payroll areas.
The payroll control record performs the following functions in
payroll:
It defines the payroll past for retroactive accounting.
It locks master data and time data so that no changes can be
made during the payroll process. The lock is valid for the payroll
past and the payroll present. Changes that affect future payroll
runs are still possible.
It defines the earliest possible retroactive accounting date for
each payroll area.
You must create a payroll control record in Customizing for
each payroll area.
You can find the payroll control record in the payroll menu for
When you create the payroll control record in your live system, ensure that the payroll period used to create the payroll control
record is one period before the period in which you want to go live. The payroll period is automatically incremented by one
period when you release the payroll for the payroll run. For example, if you want the SAP payroll system to go live in the
period 05 of the current year, you must enter the period 04 of the current year in the payroll control record.
Payroll Status Infotype:
The Payroll Status infotype (0003) is automatically created for each employee at the time of hiring. The Payroll Status infotype
infotype when performing a
payroll run, evaluating time, or making changes to the payroll past.
If you need to enter employee-specific information about Payroll or Time Management, you can update particular fields in the
infotype manually.
Earliest MD change:
If master data is changed for earlier payroll periods, the system
enters the appropriate date in this field. This date is deleted
after each completed payroll run. The program recognizes
whether and when payroll must be repeated to take master
data changes into account.
MD change:
The Earliest Master Data Change Bonus field is filled with a date
when master data is edited. This date is deleted during bonus
accounting and non-authorized manual checks (NAMC, only for the U.S.). As a result, the payroll
system can perform retroactive accounting optimally in connection with bonus accounting. This
field is used in a similar way to Earliest MD Change.
Payroll correction:
If a personnel number is rejected or you entered data during the correction phase of the payroll run, the payroll driver flags this
field. The employee is then entered in the correction run with this indicator. If the payroll is completed successfully, the indicator
is removed. If changes are made in Customizing, the Payroll correction indicator is not set.

The retroactive accounting limit determines the exact date until which the master data and time data can be changed in the
payroll past.
The retroactive accounting limit is based on the following values:
Per payroll area (Payroll control record):
Each payroll area has a payroll control record, which includes the earliest possible retroactive accounting date. The system cannot
perform retroactive accounting before this date.
Employee hiring date:
Retroactive accounting cannot be performed before an employee's hiring date.
Per employee ( Payroll Status infotype):
Each employee has a Payroll Status infotype, which includes the earliest personal retroactive accounting date.

If the date set for each payroll area differs from the date specified for the employee, the later date is used. The absolute
retroactive accounting limit for an employee is the hiring date.
Unit 4 Payroll Process
The payroll process in the SAP system includes the following steps:
1. Release the payroll.
2. Start the payroll run.
3. Check the results.
4. Perform corrections and repeat the payroll process until the payroll is error-free.
5. Exit the payroll.
During a payroll run, the payroll program reads the master data and time data infotypes. Any changes made to the master data or
time data during the payroll run can lead to inaccuracies in the payroll results. To avoid this, the system does not permit any
changes in the master data and time data that affect the payroll past and present. You must not run payroll master data
maintenance.
Functions of the Payroll Control Record
The payroll control record controls the payroll process.
Before you run an actual payroll, you can simulate the payroll
run. Simulating a payroll run enables you to display and print
remuneration statements in a test environment.
Simulating a payroll run offers the following advantages:
The system does not lock the master data and time data.
Release Payroll and Exit Payroll functions are not required.
The results of a simulated payroll run are not written to the
database; they can be viewed in the payroll log.
When payroll periods are counted in the payroll control record,
simulation runs are ignored.
The first step in processing payroll is to execute the Release Payroll function. If you choose the Release Payroll function from the
menu, the system prevents you from making any changes that affect the payroll past or present. This lock applies to the
personnel numbers included in the relevant payroll area. Changes that affect future payrolls can still be made.
You must execute the Release Payroll function before starting a payroll run. If the status of the payroll control record was
previously Exit Payroll , the Release Payroll function increases the period in the payroll control record by one.
After executing the Release Payroll function, you can execute the Start Payroll function. To start a payroll run, specify the payroll
area in both the Payroll period and Selection sections. The payroll area determines the payroll period with the exact dates and
personnel numbers that will be selected.
Before executing the Start Payroll function, ensure that a payroll control record exists.
When a live payroll is run, you do not need to enter the payroll period. The system uses the payroll area and the control record to
determine the payroll period automatically. For a simulation run, you can enter a different payroll period.
When starting a payroll, you need to specify the payroll schema in the General program control section on the Payroll driver
(international) screen. The payroll schema describes the sequence and the content of a program procedure. It consists of a list of
statements and links to subschemas and functions that are described in detail using parameters. The program processes the
specified calculation schema sequentially.
If you execute a retroactive run that the system does not recognize, you must make an entry in the Forced retro. accounting as of
field. For example, you need to make an entry in this field if there are changes in Customizing tables for the payroll past.
For a payroll simulation run, select the Test run (no update) checkbox. When the Test run flag is set, no changes are made to the
database and the UPD YES fuunction is overridden. This affects the newly generated schema. Therefore, you must not set this
flag for a regular payroll run.
You can choose to display the payroll log after the payroll run by selecting the Display log checkbox. In the payroll log, the payroll
results are displayed in a tree structure, which makes it easier for you to analyze and get an overview of the payroll results.
The payroll log presents the table of contents in the form of a tree structure. You can use the nodes within the tree structure to
access the required information. In addition, you can use the headers within the tree structure for help with troubleshooting and
navigation within the log. You can also expand or collapse individual nodes within the tree structure as per your requirements.
If you display a detailed view of a processing step, you can choose between input data, data processing, and output data within
the log. You can save your own personnel settings for the log tree and list as a variant.
If an error occurs when a personnel number is processed, the log is expanded at the appropriate place and the error message is
displayed (for example, "Division by zero not performed" ). This indicates that the Basic Pay infotype 0008 does not exist.
Matchcode W provides a list of all personnel numbers in the selected payroll area that have been rejected by the payroll run due
to incorrect data. This means that the payroll has not run successfully for them.
Personnel numbers are also included in Matchcode W if personnel data has been changed in the correction phase of the payroll
run.
You can execute the Check Result function to ensure that changes are not
made to payroll data if they affect the payroll past or present. This
function also locks the corresponding payroll accounting area to prevent
you from including it in a payroll run. This function enables you to check
the payroll results.
The Check Result function is optional and is not used in many cases. You
can reset this function by choosing Release Payroll .
If you choose Corrections , the infotype records assigned to the selected payroll area are released for correction. Choose this
function to change infotype data if personnel numbers are rejected during the payroll run. You can perform up to 99 correction
runs. After correcting the data, you must release the payroll. This locks the personnel records again. The last payroll period is not
increased.
You then choose Start Payroll to run payroll again for all the personnel numbers included in Matchcode W (that is, personnel
numbers for which the master data was changed). Choose search helps, and choose W (Payroll correction run). The Restrict Value
Range dialog box appears. To restrict the value range, you can enter one single personnel number or an interval range of
personnel numbers. The system only selects personnel numbers that lie within this range from Matchcode W . If you do not want
to restrict the value range, the system selects all the personnel numbers from Matchcode W to be included in the payroll.
The Exit Payroll function enables you to re-release infotypes so that they can be maintained for the payroll past and present. The
payroll area is then locked for the start of the payroll run. You cannot exit the payroll until the payroll has run successfully for all
the personnel numbers assigned to the payroll area ( Matchcode W is empty). If you try to exit the payroll while rejected
personnel numbers still exist, the system displays an error message. After exiting payroll, you can change data for the period in
question by performing retroactive accounting in a subsequent period.

Troubleshooting
Examples of problems that can occur during a payroll run:
Delayed time recording sheets
Retroactive employee transfer
Change in the payroll area
Missing Basic Pay infotype error
Planned Working Time infotype error
Payroll administration error
Partial period factoring
A problem can occur when time recording sheets arrive in the Payroll department after the payroll has been run for the payroll
period, but before being set to Exit Payroll .
If there is a delay in the arrival of a time recording sheet, perform the following steps:
1. Release the payroll run for corrections.
2. Enter the time data in the system.
3. Release the payroll again.
4. Run payroll using Matchcode W .
5. Check the results.
A scenario such as this can arise when, for example, the Personnel department enters a number of employee transfers that came
into force in June, after the payroll has been completed for that month, and new hires have been entered for July.
In case of employee transfers and new hires, perform the following steps:
1. Enter the changes in the master data for the month of June.
2. Run payroll for July, as normal.
3. The changes will be recognized by the system automatically within retroactive accounting and paid with the July payroll run.
Within the SAP system, personal data and many table entries are given start and end dates. This is necessary for calculations
involving exact dates, and also for performing retroactive accounting in previous periods
You have completed the payroll run for the current period. When you make changes to payment-related data in the payroll past,
you receive a notification that you are changing data in the payroll past and that this will trigger retroactive accounting. This
means that payroll must be run for this period again with the current values. This is known as retroactive
accounting.
All of the periods for which you have completed and exited payroll constitute the payroll past. If you maintain an infotype that is
relevant to retroactive accounting, the Earliest MD Change field in the Payroll Status infotype (0003) is set to the start date of the
changed infotype record. This ensures that retroactive accounting is automatically triggered up to this retroactive accounting
date when the next payroll run is performed.
In some countries, such as Germany, the payroll area is restricted and,
therefore, can only be changed at the end of a payroll period. If an employee
transfers to a different subgroup during a payroll period, for example, from
industrial to salaried employee, and a new payroll area is created, the payroll
area cannot be changed immediately.
The system changes the payroll period automatically. You must maintain the
DFINF feature to re-import the ABKRS feature when the Organizational
Assignment record is copied and the payroll area is not copied from the
previous record. The DFINF feature controls the determination of field values for certain infotypes. The ABKRS feature
determines the default value for the payroll area.
If an employee changes payroll area on July 15, but a change of payroll area is not permitted until August 1, you can save the
Organizational Assignment infotype containing the change in employee subgroup. The system then creates a new record
containing the change in payroll area that is valid from August 1.
If an employee leaves an organization, the Basic Pay infotype must not be delimited. The basic payroll data must remain in the
system. This is the only way of guaranteeing a correct retroactive accounting run, if one is needed. If a leaving personnel action
delimits the Basic Pay infotype, you can reset the end date of the Basic Pay infotype to 12.31.9999.

in the system for each month, by generating monthly work

schedules. Before you can run payroll for a period, you must
generate the monthly work schedule in the system. A previous
and subsequent period of a monthly work schedule must exist
for each period to be included in the payroll run. Payroll will not
be run for an employee for whom the work schedule does not
exist.
If you want to go live with the SAP payroll system in January 2014 (period 01.2014 for a monthly payroll area), the payroll control
record for the corresponding payroll area must be created in the system for 12.2013.
If the control record is incorrectly set to 01.2014, the system changes the payroll period to 02.2014 when the payroll is released.
In this case, you cannot run payroll for the period 01.2014.
If a control record is set incorrectly, delete the old control record and create a new one. Partial Period Factoring Factoring refers
to the proportional calculation of periodical remuneration. Periodical remuneration comprises the wage types that an employee
receives as basic pay, recurring payments, and additional payments, if required.
The following scenarios can result in factoring: Change in basic pay
An employee joins your enterprise, but not on the first day of a period.
An employee receives a pay raise in the middle of a period.
An employee leaves your enterprise, but not on the last day of a period.
An employee has unpaid leave.
Organizational assignment:
An employee moves to another department, and is therefore, assigned to another cost center. You want the cost centers
involved to be debited for the correct periods.
Reduction in recurring payments or additional payments:
An employee receives a transportation allowance and has a three-week vacation. The transportation allowance is only paid for
the period during which the employee travels to work.
During a payroll run, changes in the following infotypes are evaluated for factoring:
Actions (0000)
Organizational Assignment (0001)
Planned Working Time (0007)
Basic Pay (0008)
Recurring Payments/Deductions (0014)
Additional Payments (0015)
Absences (2001)
If a situation arises where factoring is necessary, the current partial period factor is calculated and multiplied by the assigned
wage type. Reductions are triggered, for example, by unpaid leave during a payroll period.
Unit 5 Payroll Reports
After a payroll run, you can view the payroll results in different views.
Views allowed by the payroll system:
Technical
In this view, you can generate an international report that displays payroll results.
Employee
In this view, the RPCEDTx0 program enables you to generate employee remuneration statements.
Department
In this view, various programs are available that provide different views of payroll data.
International Report
An international report enables you to display the payroll results for a specific country.
The country to which the international report belongs is indicated by the suffix at the end
of the report name.
An international report provides the following features:
It enables you to display the content of all the tables and field lists for any payroll
cluster.
It enables you to display and then temporarily save the selection of tables so that the
time required to call the tables is reduced.
It enables you to display archived payroll results.
A remuneration statement contains a list of payments and deductions effected during a payroll run for an employee.
The remuneration statement is usually created after the payroll run, but before payment is effected. If you perform more than
one payroll run in a specific period, you can create remuneration statements after each payroll run. If corrections are made, the
original documents are overwritten.

Customizing enables you to determine the format, structure, and

content of the forms you want to use. The SAP system also enables you
to create personal or general notifications for your employees that are
printed on the remuneration statement as additional information.
The notifications can be standard texts, such as general information
from management or birthday greetings.
You can enter any additional information in the Notifications infotype
(0128).
The wage type reporter is a tool that you can use to evaluate wage types. Using this tool, you can display various wage types for a
specific period with in-period or for-period views. The evaluation can be formatted using the list viewer and exported to an Excel
file. In the future, the wage type reporter will replace the wage type statement and the wage type distribution tools.

The Ad Hoc Query tool is an HR reporting tool that you can use to perform simple evaluations for selected payroll results. Using
this tool, you can choose selection and output fields and access data from all areas within Human Resources.
By configuring an infotype in Customizing, you can access payroll results for employees.
The Payroll Results infotype has four fixed fields: Payroll area , Country grouping , Currency , and For-period . You can use
Customizing to define all the other fields.
The Ad Hoc Query tool can be used for both master data and recruitment.
Unit 6 Post Payroll Results
You use posting runs to group FI-relevant payroll results into documents and post these documents to various FI components.
Payroll includes the calculation of wages and salaries paid to employees and deduction calculations.
You need to post payroll results to FI after a payroll run. Posting of payroll results needs to be done once for each payroll period.
When the payroll results have been posted to FI, all posting information is selected from the payroll results, summarized,
formatted, and posted to the integrated FI component.
The FI department is interested in the flow of payments including personnel expenses, payables, and resulting payments. The
payments are posted according to the type or identity of the payee and the due date of the payment. FI also provides an
overview of resource allocation within the enterprise.
The cost accounting department is interested in the classification of costs according to the type (cost center = general ledger
[G/L] account) and the assignment to cost centers or other account assignment objects (additional account assignment). These
costs include the allocation of personnel costs to cost objects or as overhead costs.
Posting information is stored in master data using a series of different infotypes. You can store a different cost center for a
different account assignment in the Recurring Payments and Deductions , Additional Payments , and Remuneration Statements
infotypes.
You can differentiate between posting wage types (for example, production wages, salaries, bank transfers, and so on) based on
their cost assignments and cost center assignment information.
After the payroll run, you can post the results to FI. You complete the process by posting to FI and reworking in Cost Center
Accounting (CCA).
A posting run can be performed in the following ways:
A test run without documents (T)
A simulation run with simulated documents (S)
A productive run (P)
In a test run, the system checks whether the balance of expenses and payables is zero. In a simulation run and a productive run,
the system checks all HR and FI tables. Posting information in master data is validated against the FI table entries.
The Create Posting Run step evaluates payroll results in a live run and helps you perform the following tasks:
Create a posting run.
Create posting documents.
Select the employees to be evaluated.
The sequence of evaluations for posting to FI should correspond to the sequence of payroll periods. It is usually sufficient to set
the current period as the payroll period. Alternatively, you can post individual personnel numbers. It is recommended that the
entries here correspond to those for the corresponding payroll runs. The selection of personnel numbers for the posting run
should be the same as the selection for the basic payroll run.
You can use the Type of document creation section to create a posting document for a live posting run. You can run a live posting
run only once for each personnel number and for each payroll period. If you want to repeat a live posting run, you must first
delete the existing run.
However, you can simulate a posting run for the same personnel number in the same period whenever required.
You can use Posting variant to create posting variants in Customizing for posting payroll results to FI.
When you choose Execute Run for a productive run, the system performs the following steps:
1. Creates a posting run.
2. Evaluates the payroll results.
3. Creates payroll documents.
4. Flags the payroll results of the evaluated employees.
5. Generates index information.
You can use the posting run log to review the processed personnel numbers and statistics. You can also expand the tree to view
further detailed information.
To access the document overview section, choose the Document Overview pushbutton or double-click the Doc. Creation line.

To obtain an overview of the documents, call the Posting Run Overview

screen by choosing Edit Posting Run . You can also double-click the
documents creation line to view the details.
You can carry out the following activities for each posting run:
Display the accompanying documents.
Display an overview of the run status (including history
Execute posting (when all documents are released).
Delete the posting run.
You can check the following characteristics in a posting run:
Status:
You can view the status of the posting run in the Status column on the Display Posting Run screen.
History:

Attributes:

Details:

The standard system displays only those posting runs that have been created and not yet posted. You can use a filter (choose Edit
ing runs
that have been deleted.
Document Overview
You can display a list of posting documents by double-clicking a posting run.
For each posting document, you can perform the following activities:
Display the document.
Release the document.
Display the posting documents only when the run has been posted and is in the same system.
 The Display Documents function generates a variable list for which company-specific and employee-specific variants can be
created and modified as required. You can display the line items of the posting document by double-clicking a posting
document.
You can display the underlying revision information for each document line item by double clicking the item or by selecting the
item and choosing Details . You can branch to auditing information for the posting document (that is, view the underlying
wage type).
You can double-click individual items in the Details list to display the underlying information from the payroll results.
You must release each document that is created. This action updates the document status.
When the last document is released, the posting run has the status All documents released.
To release documents, perform the following steps:
1. Display the posting documents for a posting run.
2. Flag the checked posting documents.

4. Confirm the release.

If the payroll run has the status All Documents Released, the documents
can be posted.
To confirm the posting of the documents, perform the following steps:
1. Call the list of posting runs.
2. Select the required posting runs.

4. Verify the posting of the posting documents.

If a posting run is successful, all the posting documents for the selected posting
run are transferred to FI or Cost Center Accounting (CCA). If required, the
documents are also transferred to Funds Management (FM) and then posted. The posting run has the status
Documents posted and the accompanying posting documents have the status Released .
If a posting run is unsuccessful, it has the status Document Transfer failed.
After you have successfully posted the payroll results to Financial Accounting (FI), perform the following activities in FI:
Compare transferred and posted payables.
Check withholdings for advance payments.
Check withholdings for claims.
Unit 7 Process Model
Whether employee remuneration is paid by bank transfer or check is specified in the Payment Method field of the Bank Details
infotype (0009).
If employees want to distribute their salary between two
different bank accounts, you need to enter the details of the
main bank in subtype 0 and the details of the second bank in
subtype:
1. You must also specify the percentage of the salary or the
fixed amount to be transferred to the second bank. The
remaining amount is then transferred to the main bank.
In some countries a zero net advice statement is available. For
those employees who receive no pay because of more
deductions than pay, a zero net advice can be offered to
demonstrate the payroll accounting.
Bank transfers and checks are generated based on the
preliminary program for data medium exchange (DME).
The preliminary program for DME generates a temporary
dataset that is used as input for the DME program. This report
creates a file that complies with the banking regulations for
DME and contains all payment information.
You can generate bank transfers in two steps.
Execute the preliminary program for DME to select data from the payroll results. The DME program creates a program run date
and an identification feature.
The entries in the DME program are then used to create the corresponding bank transfers and generate checks.
After you execute the preliminary program, note the number and the date of the file that is created.
The program used to generate bank transfers is country-specific and is not available for every country. This program is available
under the Bank Transfer area in your country-specific Payroll.
To start the DME program, you must enter the number and date of the file that was created after you executed the preliminary
program so that the data in the file can be copied.
Payroll as a Background Operation
You can run payroll as a background operation in the following ways:
Using a payroll calendar:
You can use the payroll calendar to schedule and execute payroll jobs sequentially. The payroll jobs are grouped into
various tasks according to payroll areas. The scope of functions contains a calendar in which you can mark one or
several dates, for example, and display the scheduled tasks.
Using report RPCSC000:
You can use report RPCSC000 to run payroll for a large number of personnel numbers in a payroll period by splitting
it into several background jobs. The system then processes the background jobs on several application servers in
parallel. To do this, you must specify the number of personnel numbers to be included in a background job, or the
number of background jobs to be created. Report RPCSC000 selects the personnel numbers for which the payroll is
run from the database and groups them into background jobs. You can release the background jobs either
individually or simultaneously.
Defining jobs:

jobs.
Using the process model:
You can define a process model to run various payroll-related process steps in the background.
A process model is used to control the payroll process
and the subsequent evaluation programs. The programs
are processed in a specific sequence. Process models are
used as a basis for carrying out processes. Every process
is created using a process model and is given a unique
process number.
A process is the concrete execution of the process steps
specified in the process model, or programs, after taking
into consideration the defined breakpoints.
If a process model is used regularly, you create a new
process every time. For example, you use the same
process model every month to develop the payroll run,
the bank transfer to the employee, and the form
printing. You create a new process for every month using
this process model. In December, you can use a different
process model that contains additional evaluation
reports for the end of the year.
Advantages of a process model:
You can monitor the execution of the programs.
You can check every personnel number during the process procedure.
You can repeat individual process steps.
You can reduce the process run time by running programs in parallel.
You can send a notification under certain circumstances.
A process model comprises the following key elements:
Process step:
A process step refers to the processing of a program in the process model.
Breakpoint:
A breakpoint refers to a point at which you can stop a process between two steps. A breakpoint is used to interrupt
and monitor the process sequence.
Wait point:
A wait point refers to a point at which you can stop a process until a specific event occurs. You can use a wait point if
you want to make the processing of the next point dependent on an external event. Alternatively, you can use a wait
point if you want a
process step to start only if another process step is being run in a different branch.
Every process step has the following attributes:
Program Category:
A program category specifies a step from a business point of view (for example, payroll posting) and establishes the
role of a program in a process model. You can assign as many programs as you want to a program category.
Program Name:
A program name specifies the program that is executed in a step.
Selection Variant:
A selection variant specifies the selection variant and criteria that are used to execute a step.
Size of Package:
The size of package specifies the size of personnel number packages. A program can process personnel number
packages of different sizes in parallel.
Communication:
Communication specifies when and how a particular person is contacted. For example, after a specific step is
executed, the person who started the process receives an e-mail.

.
The following types of breakpoints are available for the process model:
Unconditional breakpoint:
The process is always interrupted when it reaches this breakpoint.
Conditional breakpoint:
The process is only interrupted when it reaches a certain percentage of incorrect personnel numbers.
Variable breakpoint:
A self-defined function module is used to determine whether or not the process is interrupted.
You can specify the name of the person who is notified by e-mail if a breakpoint is reached.
You can also specify the standard text that is used in the e-mail.