Documentos de Académico
Documentos de Profesional
Documentos de Cultura
In your enterprise, payroll is run monthly. You want the payment date for pensioners to be
the first day of the month, for industrial workers the 15th, and for salaried employees the
25th. You specify the following date modifiers:
You use a few logic condition such as personnel area, personnel sub area, company code,
employee group, etc., to determine down to the employee level what payroll area he/she
belongs to.
That then get transported to the payroll area field on IT0001. The payroll area field on
IT0001 is what payroll extract runs of when handling your payroll process.
TCODE – PE03
NOTE : - YOU MIGHT GET ERROR – FIELD VALUE NODES MUST HAVE
DEPENDENT NODES THEN GO TO INFO IN OTHERWISE – SELECT THE INFO – GO
TO DELETE – DELETE IT – SAVE.
CONTROL RECORD : -
In this step, you set up the system controls for the payroll control record. This control record
has the following functions in payroll:
It locks the master data and the time data to prevent changes from being made
during the payroll run.
This lock is valid for the payroll past and the payroll present. Changes which affect
the future can still be made.
Payday rule: This field specifies how the payment date should be calculated for each payroll
period.
Example: In your system, you use monthly payroll periods and want to define the 25th of the month
as the payment day. Then you need to make the following entries:
That means that the payment day in every payroll period is not based on the length of the month.
In your system, you use weekly payroll periods and want the payment day to come four days after
the end of the payroll period. You make the following entries:
- SAVE.
-
ESG GROUPING FOR PCR(Personnel Calculation Rule):
In this step, you can define the groupings for the personnel calculation rules and
collective agreement provisions for all your employee groups and subgroups.
The employee subgroup grouping for the personnel calculation rule is required in
Payroll Accounting. The collective agreement provisions grouping is required for
indirect valuation of wage types in the Basic Pay infotype (0008).
Collective Agreement Provisions are for Employee Union...The Employee Unions will
come up with a set of requirements for different employee groups and we need to
segregate an employee based on the provisions his particular association with a
union requires.
So you create a seperate grouping for different employees whose requirements vary
based on the agreement and then assign employees to these groupings.
1 = hourly wage
3 = salary/pension
3 = salaried employee
4 = AT
PAYSCALE TYPE
PAYSCALE AREA
In this step, you create your own wage types for the infotype
Basic Pay (0008) by copying the model wage types in the
standard system.
These copies are the wage types you will use in further
processing. You can also modify the copies to suit your
requirements.
Wage types
Wage types, as the primary data element for employee paychecks, are
also mapped to FI/CO accounts to record the debits and credits resulting
from the paycheck and reported on the W-2 and other tax forms. Wage
types can also be used to store statistical data – such as the number of
hours worked in a pay period, the average weekly wages for the past six
months, or the amount of wages eligible for a profit sharing calculation.
Wage type attributes are stored in several tables, but the central table is
T512W. Much more time will be spent on various aspects of T512W.
There are three categories of wage types – model, technical, and user.
Model wage types are delivered by SAP for customers to use as
guidelines for creating their own wage types. They always start with a
letter and SAP may add, delete or update them in system upgrades.
Technical wage types always start with the ‘/’ symbol, and are delivered
by SAP. They are intended for very specific standard processing in
payroll, and while you can modify them, SAP may also update them
during upgrades. So if you ever (I mean EVER) change a technical wage
type, check it after each upgrade to make sure it still has the attributes
you want. And never delete a technical wage type.
NOTE – THE ABOVE PROCEDURE STORES THE WAGE TYPE WHICH YOU
CREATED IN THE INFOTYE WHICH YOU SELECTED AT THE TIME OF
CREATING WAGE TYPE.
In this section, you can define which wage types may be entered for your groupings.
Example
You want to allow the "bonus" wage type only for employee subgroup grouping "9".
These employee groups and subgroups were defined in the previous but one step.
Set this indicator in column "9" of the "Admissibility for employee subgroup grouping"
block for your groupings.
You want to allow the "share of turnover" wage type only for personnel subarea
grouping "9". These personnel subareas were defined in the previous step. Set this
indicator in column "9" of the "Admissibility for personnel subarea grouping" block for
your groupings.
Amount - Minimum and maximum values – you can specify minimum and maximum
values for a wage type. This is useful to stop input errors at source. Having
meaningful values set here can prevent errors at the input stage rather than having
to find them in your payroll exception reports or even at a later stage. The difficulty
most customers find that it is very hard to decide on what values to use for each
instance. It is recommended to configure meaningful values for most of the wage
types that are input manually. You might only prevent a few incorrect inputs of data,
but it may well save your organisation a lot of money. Add to total - Tick this indicator
if you would like the value for this wage type to be included in the basic pay total for
the employee. Input combination - This controls what values are allowed at data
entry – i.e. whether you have to enter an amount or you can enter either an amount
or a number with units etc. There are 5 options for both amount and number and
these are controlled separately for both. The help is very useful in these fields and
won't be repeated here. Time Levelling and Time Sheet Basic hours - Defines
whether the wage type is a wage type for basic hours or a bonus wage type. The
indicator is used for time levelling. Number / Unit Time Unit / Measurement - This
allows you to stipulate the hours, months, years, shares etc If you have stipulated
that the user is to enter units on the input combination, then you should choose one
of the entries from the drop down. Minumum and Maximum Number - This is the
threshold value for minimum and maximum amount which can be entered for a
wage type in the Basic pay infotype (0008). If you create or change a wage type in the
Basic pay infotype (0008), the system checks the minimum value of a wage type
against the created or changed value. If the value entered in the infotype exceeds the
defined minimum value for the wage type, the system issues the relevant
information message. Indirect Valuation Indirect Evaluation Module -You can use the
indirect evaluation module to output various default values for wage types on
different infotypes. The most commonly used ones are as follows: TARIF - this
method valuates according to the "collective agreement group and level"
specifications you enter in the IMG. Wage types with TARIF will use the settings on
the wage type and the values held in table T510 to populate the relevant value into
the relevant infotype. There are 4 different module variants for TARIF – A, B, C and D.
See the SAP help for more assistance. PRZNT - this is used where you have a wage
type being a constant percentage of another wage type and wish this to be shown on
the infotype. The wage type in question and the wage type that the percentage is
based upon (base WT), are all held in table T539J. ANSAL - this is used in table T539J
for the wage types which you would like to be accumulated and shown as Annual
Salary on screen 2010 on infotype 0008 – Basic Pay. SUMME - very similar to the
'PRZNT' module except that the value of the wage type to be valuated indirectly is
always the entire basic pay. There are different module variants, which can be viewed
in more detail in the SAP help. CONST - Module for constant valuation of wage types
according to table T510K (V_T510K view).
TARIF -
Valuation according to the "collective agreement group and level" specifications you enter in
the IMG step:
Module variants: A, B
Module variants: A, B, C, H, I, J
The difference is derived from the valuation with module VERGL and the valuation with module TARIF.
PRZNT -
Country grouping assigned to the employee master (derived from the personnel area)
MODUL = 'PRZNT'
Valuated wage type = indirectly valuated wage type
The basic pay is determined from the total of all basic wage type amounts entered in infotype 0008
according to the specifications in the "basic wage type valuation" step irrespective of which infotype is
being valuated. Wage types in the Wage Maintenance infotype (0052) are then valuated using the wage
types in the Basic Pay infotype (0008).
The value of the wage type to be valuated indirectly is calculated by multiplying the basic pay by the
percentage specified for the wage type to be valuated.
The basic pay is determined from the total of all basic wage type amounts specified in the infotype
currently being valuated according to the specifications in the "basic wage type valuation" step. The
wage types in the Wage Maintenance infotype (0052) are then valuated using the wage types in the
Basic Pay infotype (0008).
The value of the wage type to be valuated indirectly is calculated by multiplying the basic pay by the
percentage specified for the wage type to be valuated.
The basic pay is determined from the total of all basic wage type amounts weighted with GWCHT
according to the specifications in the "basic wage type valuation" step. All these basic wage types are
valuated indirectly even if these wage types are valuated directly in the infotype.
The value of the wage type to be valuated indirectly is calculated by multiplying the basic pay by the
percentage specified for the wage type to be valuated.
SUMME
Module variants 'B', 'D', 'I','J'
The 'SUMME' module corresponds to the 'PRZNT' module except that the value of the wage type to be
valuated indirectly is always the entire basic pay.
Corresponds to the module variant 'D'. The basis wage types are valuated as unreduced.
Corresponds to the module variant 'I'. The basic wage types are not weighted in payroll.
UNITS
The 'UNITS' module corresponds to the 'PRZNT' module with the exception that the value of the wage
type to be valuated indirectly is calculated by multiplying the basic pay by the number entered for the
wage type to be valuated.
CONST
Module for constant valuation of wage types according to table T510K (V_T510K view).
In this module variant, the entry from table T510K is assigned to the wage type.
M In this module variant, the entry from table T510K is multiplied with the Number field (Number) of the infotype.
The wage type must be set up in the wage type table (T511) accordingly. In other words, a unit must be allowed,
and the minimum number should, if possible, be 1. If no value is entered, the system uses 0 as the default.
P In this module type, the entry from table T510K is valuated as a percentage using the infotype's Number field
(Number). The wage type must be set up in the wage type table (T511) accordingly. In other words, a unit must
be allowed, and the minimum number should, if possible, be 1. If no value is entered, the system uses 0 as the
default.
ARBPL -
Valuation according to the specifications which you must make in the "Determine indirect valuation for
positions/work centers" section of the IMG.
The module variants of the ORTSZ indirect valuation module determine the components included in the
valuation. The Family Bonuses infotype (0595) contains information on whether a claim exists for each
component. For more information on the meaning of the individual components, refer to the documentation on
indirect valuation of family-related, cost-of-living, and social bonuses.
1. Module variant 1 (component for single persons): Only the component for single persons: LD.
2. Module variant 2 (component for spouse): If a claim exists for the whole of the spousal component,
the amount VH is read. If a claim exists for half of the spousal component, the amount VH is read and
divided by 2.
3. Module variant 3 (component for children): For each child or counted child, the total number of
children increases by 1. There is a child componentKI and an increase amount K1 for each child. The
increase amount is K1 for the first child, and KE for each subsequent child. An exception to this is used
for a count child (non-marital). No increase amount is paid in such a case. If the first child is also a
count child (non-marital), and the second child simply a count child, then increase amount K1 is used
for the second child.
4. Module variant 4 (component for spouse): If a claim exists for the whole or half of the spousal
component, either amount VH or amount V1 is read.
5. Module variant 5 (component for children): This rule is the same as module variant 3, except that
componentK3 is used instead of component KI from the birth of the third child inclusively.
6. Module variant 6 (component for children): Determination of the social bonus according to BMTG
including allowable bonuses.
7. Module variant 7 (TVöD: vested payment for children): Determination of the component for
children for cost-of-living bonus based on pay scale information before the data was transferred to the
TVöD (Collective Agreement for Public Sector). This information, if it exists, is taken from the Basic Pay
(0008) infotype history. If sufficient history does not exist, the old pay scale information is taken from the
backup table PDPBSTVOED_UEB that was written when the data was transferred. If no entry exists in
this table either, then the valuation is made as for module variant 3.
8. Module variant 8 (TVöD: component for spouse without discount): This module variant
calculates the spousal component without discount if the checkbox "No part-time reduction" is set for the
spouse in the infotype 0595. If the checkbox is not set, the amount is set to 0. The pay scale information
is determined analog to module variant 7. This is necessary to avoid the part-time reduction of the
spousal component when using an individual interim level.
1
No reduction
2
Reduction according to the capacity utilization level specified in the Basic Pay infotype (0008)
3
Reduction according to
The regular weekly working time specified in table T508A
4
Reduction according to
Weekly working hours specified in the Planned Working Time infotype (0007)
5
Reduction according to
Regular weekly working hours in T508A - PS working hours in T510I
6
Reduction according to
Weekly working hours in the Planned Working Time infotype (0007) - PS wkly work. hours in T510I
Y
Use this option only if the view for the German public sector is active. Reduction is carried out according
to the numerator/denominator combination of basic pay. The Additional Information on Basic Pay
infotype (IT0304) is NOT taken into account in indirect valuation of wage types.
Z
Use this option only if the view for German public sector is active. The reduction is carried out according
to the numerator/denominator combination of basic pay. The Additional Information on Basic Pay
infotype (0304) is taken into account in indirect valuation of wage types.
Rounding type
The following values are permitted:
Rounding divisor
Accepted values for the rounding divisor are 0 - 999999.
Examples
Rounding to 20 PENCE : divisor = 20 pence
If you set the indicator, the fields are in input mode and can be overwritten.
If you do not set the indicator, the fields are not in input mode.
In this step, you can set up default wage types based on your internal company
structure for the Basic Pay infotype (0008) using the feature Planned remuneration
specification (LGMST) defined in the previous step.
Example
You want the system to propose the wage type "standard pay" for salaried
employees and industrial workers in all personnel areas. So you assigned the key
"----1DU" to these two employee subgroups in the previous step. In this step, you
determine the default wage type "standard pay" for this key.
FEATURE LGMST :
LGMST is a feature used to default values for planned payment specification from
T539A.It is used for payroll wage types.Eg: IT0008, we can default the no of wage
types depending on comp code, pers area etc etc...
In short we can default how many wagetypes & which wage types needed in the
particular IT.
Bank Details
Create Bank Connection Types
Use
In the SAP Best Practices the standard delivered bank connection types have not been modified.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management Personnel Administration Personal Data
Bank Details Create bank connection types
Transaction SPRO
Code
2. On the Change View “Subtype Characteristics”: Overview screen, choose the New entries button
and enter the following values:
SubType Bank Connection Type Text Time Constraint
0 Main Bank 1
1 Other Bank 3
2 Travel Expenses 2
3. Choose Save.
Define Payment Methods
Use
In the SAP Best Practices the standard delivered entries for Payment Methods are used. It is
recommended that no modifications be made in this area in order to avoid unnecessary configuration
in further steps.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management Personnel Administration Personal Data
Bank Details Define payment method
Transaction Spro
Code
2. On the Customizing: Maintain Payment Program screen choose the Pmnt methods in company
codes button.
3. On the Change View “Maintainence of Company Code Data for a Payment Method”: Overview
screen, choose the New entries button and enter the following values:
Pay Method Payment Method Text
C Check
4. Choose Save.
Off-Cycle Payroll covers the various payroll functions that are not covered by the regular
Payroll Process. Off-Cycle Payroll includes the processing of special payments, entering
information for manually created checks, reversing payroll results and reprinting checks, all
of which may take place outside the regular payroll cycle.
1. You can run offcycle by using tcode ---> PUOC_10 – (10 is nothing but u.s.a country code
so you should enter the country code of your sap hr project) (Offcycle workbench)
2. can i make payments for future dates? ---> YES you can make future payments
For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.
For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.
For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.
For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.
With use of a dynamic actions, infotype 0057 will be created in the background for Union
employees. A personnel calculation rule ZUSO has been created to take a deduction
based on a constant in T511K and the personnel calculation rule. A flat rate of $50.00 has
been configured for employees in Local 112 and a multiplier of 2 hours times the rate for
employees in Local 83.
For detailed information regarding all wage types that correspond to the payroll-related
configuration in Personnel Administration, please refer to the Wage Type Documentation
spreadsheet.
Procedure
2. Access the activity using one of the following navigation options:
IMG Path Personnel Management Personnel Administration Payroll Data
Basic Pay Revise Pay Scale Groups and Levels
Transaction SPRO
Code
3. On the Determine Work Area: Entry , enter the following values and press enter.
Country Grouping Pay Scale Type Pay Scale Area
10 01 01
Many examples of Pay Scale Groups and Levels are provided in the SAP Best Practices for HCM
USA to provide the customer with an understanding of how to represent different types of employees
with different pay scales.
These are only example pay structures and must be updated to meet customer needs.
Type Area Grp PS Group Level WT Amount Currency
3000
03 01 1 H001 00 8.00 USD
3000
03 01 1 H001 01 8.50 USD
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management Personnel Administration Payroll Data
Basic Pay Check Total Salary Against Salary Range Check
Number of Periods
Transaction SPRO
Code
2. On the “Process feature PFREQ: decision tree” screen, you will see the following:
PFREQ Payment frequency for annual salary
07 Canada
Weekly 52
Two-weekly 26
Half-monthly 24
Four-weekly 13
Monthly 12
Quarterly 04
Half-yearly 01
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management Personnel Administration Payroll Data
Basic Pay Define agreed salary
Transaction SPRO
Code
2. On the ‘Display View “Wage Type Characteristics”: Overview’ screen, you will see the
following value:
Wage Type Wage Type Long Text Start Date End DateEnd Date
/102 401(k) Wages 01/01/1900 12/31/9999
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management Personnel Administration Payroll Data
Basic Pay Maintain payroll simulation feature
Transaction SPRO
Code
2. On the ‘Process feature PM004; decision tree’ screen, you will see the following value:
PM004 Determining the Simulation Variant for the Payroll Program
GV Taxation of Pensions
GMVS
Procedure
1. Access the activity using one of the following navigation options:
IMG Path Personnel Management Personnel Administration Payroll Data
Basic Pay Define pay scale salary ranges
Transaction SPRO
Code
Payroll
PC00_M10_CALC_SIMU - Simulation
PC00_M99_PA03_RELEA - Release payroll
PC00_M10_CALC - Start payroll
PC00_M99_PA03_CHECK - Check result
PC00_M99_PA03_CORR - Corrections
PC00_M99_PA03_END - Exit payroll
PC00_M10_CEDT - Remuneration statement
PC00_M10_HRF - Remuneration statement with HR-Forms
Bank transfer
PC00_M10_CDTE - Test transfer
PC00_M10_CDTC - Pre-program DME
PC00_M10_FFOT - Create DME
PC00_M99_FPAYM - Create DME - Payment Medium Workbench
FDTA - DME management
PC00_M10_FFOC - Print check
PC00_M10_RFFOAVIS - Print zero net advices
Off-cycle
PUOC_10 - Off-Cycle Workbench (10 refers to the country code for u.s.a so you should use
the country code of your client project)
PUOCBA - OC Batch: Follow-up for payroll
PUOCBLTI - OC Batch: Mass LTI-processing
PUOCLG - List batch table
PUOCLL - List replacements, reversals
Subsequent activities
Per payroll period
Evaluation
PC00_M10_CDTB - Advance payment
Posting to accounting
PC00_M99_CIPE - Execute posting run
PC00_M99_PPM - Execute posting run for payments
PCP0 - Process posting run
PC00_M99_CIPC - Check completeness
Third-party remittance
PC00_M99_URME - Evaluate remittance (New)
PC00_M10_U500 - Evaluation run
PC00_M99_URMU - Store evaluation run
PC00_M99_URMP - Create posting run
PCP0 - Process posting run
PC00_M99_URMR - Reconcile postings
PC00_M99_URMW - Check processing classes
PC00_M99_URMA - Acknowledge postings
PC00_M99_URMD - Undo processing steps
PC00_M99_URMC - Run remittance completeness check
Garnishment status
PC00_M10_IPIT0 - Active -> inactive
PC00_M10_IPIT1 - Pending -> active
PC00_M10_IPIT2 - Delimit
Lists/statistics
PC00_MNA_CC_ADM - Cost Center Report - Administrator
PC00_M10_CLJN - Payroll journal
PC00_M99_CWTR - Wage type reporter
PC00_M10_REC - Payroll reconcilation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
Period-independent
Evaluation
Posting to accounting
PC00_M99_CIPE - Execute posting run
PCP0 - Process posting run
PC00_M99_CIPC - Check completeness
Third-party remittance
PC00_M99_URME - Evaluate remittance (New)
PC00_M10_U500 - Evaluation run
PC00_M99_URMU - Store evaluation run
PC00_M99_URMP - Create posting run
PCP0 - Process posting run
PC00_M99_URMR - Reconcile postings
PC00_M99_URMW - Check processing classes
PC00_M99_URMA - Acknowledge postings
PC00_M99_URMD - Undo processing steps
PC00_M99_URMC - Run remittance completeness check
Payroll supplement
Garnishments
PC00_M10_CPL3U0 - Garnishment statements
S_AHR_61016146 - Garnishment details report
PC00_M10_CPL5U0 - Print notice letter
PC00_M10_CPL7U0 - Print answer letter
PAUY - Adjustment Workbench (special retro processing)
PAUX - Adjustment Workbench
PU19 - Tax Reporter
PC00_M10_REC - Payroll reconciliation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
PC00_M07_STDR - STD/LTD report
PC00_M10_CLAIMS - Claims processing
Tax utilities
PC00_M10_UBSIU7 - Compare delivered tax authorities
PC00_M10_UTMDU0 - Taxability models / tax types by tax authority
PC00_M10_UAUTU1 - Display tax authorities
PC00_M10_UAUTU2 - Tax authorities not in residence or work tax area
PC00_M10_UBTXU0 - Update clients
PC00_M10_UTAX - Delete entries
Outsourcing
Export
PC00_M10_OTEX - Gross Payroll Export
PC00_M10_OTEM - Master Data Export
S_PH0_48000542 - Mini Master Export
S_PH0_48000543 - Combined Payroll Export
PC00_OTTM - Time Wage Type Export
WE05 - Display IDocs
WE14 - Process Outbound
Import
PC00_OTIN - Process Inbound
WE05 - Display IDocs
PC00_OTRL - Release IDocs
PC00_M10_OTCL - Payroll Import
PC00_M10_OTLJ - Payroll Journal
PC00_OFPM - Special pay model
Tax Services
PC00_M10_OTUT - Periodic/Quarterly Reporting
PC00_M10_OTUY - Yearly Reporting
WE05 - Display Idocs
WE14 - Release Idocs
PC00_M10_OTUR - Reconciliation Utilities
Utilities
PC00_M10_OTUT_SETUP - Conversion
PC00_M10_OTUT_DISP - Pay Period Tax Field Display
PC00_M10_OTL1 - Cross Year Adjustment Display
PC00_M10_OTU1 - IF cluster delete by pay period
Info system
Payroll results
PC00_MNA_CC_MAN - Cost Center Report - Manager's Overview
S_AHR_61018754 - Display payroll results
S_ALR_87014259 - Payroll journal
S_PH9_46000172 - Wage type reporter
PC00_M10_REC - Payroll reconciliation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
S_PH9_46000232 - Tip income and allocated tips report
S_PH9_46000233 - Pensionable earnings and hours report
S_AHR_61016146 - Garnishment details
S_AHR_61016148 - Workers' compensation report
Pay date
S_ALR_87014136 - Paydays on holidays or weekends
S_ALR_87014137 - Payday calendar
Tax
S_PH9_46000360 - Exemption expiration report
S_PH9_46000361 - W-4 withholding allowance report
S_AHR_61016142 - Tax infotype summary
S_AHR_61018777 - Taxability models/tax types by tax authority
S_AHR_61018778 - Display tax authorities
S_AHR_61018779 - Tax authorites not included in a residence or work tax area
PC00_M10_REC - Payroll reconcilation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
Tax Reporter reconciliation
S_AHR_61018782 - Tax amounts in tax interface tables
PC00_M10_REC - Payroll reconcilation report
PC00_M10_CPRS - Payroll reconciliation report (scheduler)
Public Sector
Certification and Licensing
P0000_M10_CL0_PBS - Generate Qualification Groups or Qualifications
P0000_M10_CL1_PBS - Convert Certificate or License to Qualification
P0000_M10_CL2_PBS - Out-of-Field Report
P0000_M10_CL3_PBS - Perform Certificates/Licenses Selection
P0000_M10_CL4_PBS - Check Qualification and Certificate Consistency
Equal Employment Opportunity
P0000_M10_EEO_PBS - EEO-4 and EEO-5 Reporting
Savings Bond Purchase Plans
P0000_M10_SBT_PBS - Savings Bonds Purchase
P0000_M10_SVB_PBS - Display Savings Bonds Purchases
Non-Resident Alien Processing
P0000_M10_ORM_PBS - Form 1042-S Printing
P0000_M10_SPT_PBS - Substantial Presence Test
Effort Reporting
PRP_US_EFFR_BUND_ACT - Actual Effort Certification by Employee
PRP_US_EFFR_BUND_DUN - Dunning Report
Tools
PC_PAYRESULT - Display Results
SLG1 - Analyze Application Log
PUST - HR Process Workbench
PA03 - Control Record
PC00_M99_UTSV - List TemSe Objects
PC00_M99_CPRC - Payroll Calendar
Outsourcing - Interface Toolbox
Data Export
PU12_EXPORT - Export
PU12_CONVERT - Conversion
PU12_DOWNLOAD - Download
Export History
PU12_SHOW_CLUSTER - Display Interface Results
PU12_SHOW_FILE - Display TemSe File
Data Import
PU12_IDOC_CREATE - Create Idocs
PU12_IDOC_PROCESS - Process Idocs
PU12 - Interface Toolbox
Customizing Tools
PEST - Maintain Process Model
PE01 - Schema
PE02 - Calculation Rule
PE04 - Function/Operation
PU30 - Wage Type Maintenance
PC00_M99_DLGA20 - Wage Type Utilization
PC00_M99_DKON - Wage Type Assignment - Display G/L Accounts
PU22 - Archiving
Problem Solving
PU03 - Maintain Payroll Status
PU01 - Delete Payroll Result
PC00_M99_UDIR - Restructure Payroll Directory
PC00_M99_UCRT - Restructure Cumulation Tables
Settings
PC00_M99_CURSET - Current settings
PC00_M99_ABKRS - Set payroll area