SAP Library / SuccessFactors / Cheat sheet
SAP SuccessFactors cheat sheet
17 objects in 3 groups. Each links to its full reviewed page.
T-Codes8
- PA20PA20 is the read-only transaction for viewing infotype records against a personnel number. It shares the exact screen layout of PA30 (the maintenance transaction) but has no save, insert or delimit function. It is used to confirm what is actually stored in the infotype tables for a given date before touching the data, without risk of an accidental change.
- PA30PA30 is used to create, change, delimit and copy employee infotype records in classic SAP HCM Personnel Administration. It is most useful when HR administrators maintain an employee's organizational, personal, payroll or other infotype-based master data. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
- PA40PA40 is the Personnel Actions transaction. It runs a predefined sequence of infotype maintenance screens tied to a specific action type, such as hiring, transfer, or termination, so that all the infotypes that logically belong to one business event are updated together with the same action date and reason, instead of being maintained one at a time in PA30.
- PPOMEPPOME is the classic Organization and Staffing maintenance transaction for SAP Organizational Management. It provides a graphical structure for maintaining organizational units, positions, holders, and relationships with effective dates. Use it where the SAP HCM organizational plan is authoritative; in Employee Central-led landscapes, direct backend changes must follow the defined replication and ownership model.
- PT60PT60 runs the SAP Time Evaluation report RPTIME00. It evaluates employee time and labor data using the selected time-evaluation schema and period, producing time-evaluation results used for time accounts, wage types, quotas, and downstream payroll according to configuration. It is commonly scheduled as a recurring background job and also run manually for testing or recalculation.
- PA03PA03 maintains the payroll control record for a payroll area, not employee Infotype 0003. It controls the current payroll period and payroll-run status, such as release for payroll, release for correction, and exit payroll. The control record also governs whether payroll-relevant master data can be changed while a payroll run is in progress.
- PU03PU03 is the dedicated transaction for editing infotype 0003, Payroll Status. It exposes control fields that govern how far back payroll can retroactively recalculate for an employee, plus locks that block a payroll run. Most of infotype 0003 is normally updated automatically by the payroll driver, so PU03 is the tool used to override it by hand, typically to fix a stuck or runaway retroactive accounting situation.
- PO13PO13 is the single-object maintenance transaction for Position (object type S) in SAP Organizational Management. It lets a consultant create or change one position's infotypes directly, without going through the org-chart-style PPOME interface. In SuccessFactors Employee Central integration scenarios it is mainly used to inspect or patch position data on the ECC/S4 side, since EC is usually the system of record.
Key Tables8
- PA0000PA0000 is the Actions infotype table in SAP Personnel Administration. Each row records a single personnel action (hire, transfer, leave, termination, rehire) for one personnel number, with an action type, reason, and employment status, valid for a specific date range. It is the master gate that Payroll, Time Management and Benefits check to decide whether an employee is eligible for processing.
- PA0001PA0001 stores infotype 0001, Organizational Assignment: the time-dependent link between a personnel number and its organizational unit, position, job, cost center, company code, personnel area/subarea, employee group/subgroup and administrator groups. Every row is one validity-delimited assignment record for one PERNR. It is the table most reports join to for headcount, cost center allocation, and reporting-line questions.
- PA0002PA0002 stores infotype 0002, Personal Data: the employee's name components, date of birth, gender, marital status, nationality and birthplace, one time-sliced record per PERNR per validity period. It is the master source for legal name and biographical data used across payroll, benefits, and statutory reporting, and is read constantly by ESS/MSS and downstream interfaces.
- PA0008PA0008 stores the Basic Pay infotype (0008) for each personnel number: pay scale classification, annual salary, working time percentage, and up to twenty wage type and amount pairs valid for a date range. Each row is one time-sliced version of an employee's pay structure, delimited by BEGDA and ENDDA, and is the primary input to payroll valuation and remuneration statements.
- PA2001PA2001 holds absence records for infotype 2001 (Absences) - sick leave, vacation, unpaid leave and similar events, one row per absence period per employee per absence type. It is the transparent reporting copy of records whose master storage for time infotypes is the payroll time cluster, kept in sync automatically when the record is saved through the standard infotype maintenance transactions.
- PA2006PA2006 is the transparent table behind infotype 2006, Absence Quota. One row is a single quota entitlement record for one employee and one quota type, valid for a specific deduction period, carrying the entitled amount that absences recorded in infotype 2001 draw down during time evaluation. It does not store the running remaining balance directly; that is derived at read time.
- HRP1000HRP1000 stores Organizational Management object master records for Infotype 1000 (Object), including object type, object ID, plan version, validity, status, and short or long object text. It is the base identity record for OM objects such as organizational units, positions, jobs, and work centers; relationships between those objects are stored separately in HRP1001.
- HRP1001HRP1001 stores the relationships between Organizational Management objects in SAP HCM: reporting lines, position-to-org-unit assignments, position holders, job classifications and cost center assignments. Each row is one relationship instance between two objects, valid for a date range. It is the table behind org charts, staffing reports and authorization checks, and is either the source of truth or a replica depending on whether Employee Central owns organizational data.