PA20 versus PA30: Display and maintain personnel data with the right scope
A plant HR administrator needs to inspect an employee's record without confusing display access with permission to change it.
START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED
What it is. Why it matters.
PA20 displays personnel data and PA30 maintains it in relevant SAP HCM systems. Reading an employee record and changing it require different purposes and permissions.
Completely new to SAP?
Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.
SAP HR applications manage employee-related records and processes. A record’s subject, validity dates and access permissions all matter before it is read or changed.
A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Scope and source-review notes
Scope and evidence
Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.
Classic SAP HCM Personnel Administration PA20/PA30 concepts. Personnel-data access and effective-record operations require the relevant role and business process.
Reviewed relevant official SAP indexed documentation excerpts on 14 November 2026. Examples, identifiers, amounts and expected observations are illustrative; no customer SAP execution was performed. Transaction availability, labels and results depend on the installed release, deployment and local configuration.
A MANUFACTURING EXAMPLE
Separate factory personnel display from maintenance
Display or maintain?
Read the example values
- Business need
- Read a valid address
- Classic display
- PA20
- Classic maintenance
- PA30
- Relevant scope
- Employee and validity dates
Words you’ll meet in this guide
- Employee record
- Stored information about a person’s employment.
- Validity
- The dates during which a record applies.
- Payroll
- The process that calculates an employee’s pay.
- HANA
- SAP’s database platform.
- HCM
- Human Capital Management: SAP software for employee-related information and processes.
Preview the practical steps
SEE THE CONNECTION
See it in a simple example.
A small example to make the idea concrete.
Separate factory personnel display from maintenance
A plant HR administrator needs to inspect an employee's record without confusing display access with permission to change it.
PA20 displays personnel data; PA30 supports maintenance
Use PA20 to investigate classic HCM personnel records when the task is display.
Confirm the selected employee in the work area
SAP’s Object Manager provides search and selection areas, then a work area for the selected employee.
Choose infotype, subtype and validity before judging a field
PA20/PA30 can display different records according to the selected infotype, subtype and period.
Separate factory personnel display from maintenance
A plant HR administrator needs to inspect an employee's record without confusing display access with permission to change it.
Use the appropriate authorized task and validity context before interpreting what another user should be able to see or maintain.
| Reader | Business question | Evidence to carry forward |
|---|---|---|
| Plant HR, time and payroll application teams | Separate factory personnel display from maintenance | Use the appropriate authorized task and validity context before interpreting what another user should be able to see or maintain. |
01 PA20 displays personnel data; PA30 supports maintenance
Use PA20 to investigate classic HCM personnel records when the task is display. Use PA30’s supported maintenance operations only when an authorized data change is required. The difference is both purpose and access: finding an unexpected address does not automatically make changing it the correct next step. [1] [2]
This guide is for HR administrators, payroll/time analysts and support teams using classic Personnel Administration in SAP ERP or supported HCM for S/4HANA. Employee Central People Profile is a different application and data model. You need authorized personnel and infotype access; available screens, country fields, actions and operations vary. Fictional personnel P100 and address labels avoid using any real employee data.
02 Confirm the selected employee in the work area
SAP’s Object Manager provides search and selection areas, then a work area for the selected employee. A search result containing several similar names is not proof that the work area has switched to the intended personnel assignment. Confirm the personnel number/assignment and relevant identity context after selection. [1]
This matters when an administrator opens a favorite search or moves among employees. A remembered selection, copied screenshot or session default can point to someone else. Record a protected personnel reference in the ticket and use approved masking outside authorized HR systems. Do not diagnose an employee’s data from a name alone.
03 Choose infotype, subtype and validity before judging a field
PA20/PA30 can display different records according to the selected infotype, subtype and period. SAP documents a Period field that restricts records offered for display/maintenance and an overview showing records valid in the selected interval. The chosen time range is therefore part of the evidence. [2] [3]
For an address, distinguish its use or subtype as well as dates. A temporary residence and permanent residence can be different valid facts. An overview spanning two years is not a single current-state screen. Write the precise question, such as “Which permanent address applies to P100 on 14 November 2026?” and preserve that date with the observed value.
04 Worked case: today’s address and a planned December move
P100 has Address A valid through 30 November 2026 and Address B from 1 December 2026, under the declared supported subtype history. A user runs a14 November display and expects B because it was entered yesterday. Entry time does not make the future record current: A answers the 14 November question.
An authorized overview covering November–December can show both records. If B has a typo, first identify whether the approved task is correction of B’s existing future interval or a different new move. The display investigation should establish the exact record and business intention before any PA30 operation is chosen.
| Task | Relevant context | Expected result |
|---|---|---|
| Read current address | PA20;14 November | Address A |
| Read planned future address | PA20;1 December | Address B |
| Review transition history | Permitted November–December overview | Both intervals visible |
| Correct typo in B | Authorized maintenance of identified B record | Intended future interval corrected |
| Record another later move | Supported new effective record/action | Distinct dated event, not silent historical overwrite |
05 Understand the operation before saving
Display, change, create, copy and delimit operations express different intentions where the installed infotype supports them. A correction to existing data is different from a new event effective on a later date. A delimitation changes when an existing record ends; it should not be used merely to hide an unwanted value from a report.
For B, verify the selected interval and operation before accepting proposed changes. If the real move date changes from 1 December to 15 December, inspect neighboring records and the approved time-constraint behavior. A gap from 1–14 December may be unacceptable for a required continuous record, while an overlap may be incompatible with its subtype. Let the supported process validate the intended history.
06 Personnel actions can coordinate related records
A hire, transfer or termination can require a supported personnel action rather than an isolated field edit. SAP’s Object Manager documentation identifies PA40 alongside PA20/PA30; the action process and infotype sequence depend on configuration. Do not treat every organizational change as a direct change to one0001 field. [1] [4]
If a transfer affects personnel area, subarea, payroll area or other records, establish the approved action and effective date with the HR process owner. The practical investigation can still begin in PA20: read the existing dated history, then determine which supported maintenance process reflects the actual employment event. A field being editable is not proof that an isolated edit is the complete process.
07 Access can differ by data, organization and time
HCM authorization is more specific than the ability to start PA20 or PA30. SAP learning describes master-data checks involving infotype, subtype, activity and organizational fields, and time logic based on record validity and administrator responsibility. A user can therefore display some personnel information while correctly being restricted from another category or interval. [4] [5]
If two users see different records, first compare personnel identity, infotype/subtype, selected period and intended responsibilities. Then capture the actual authorization evidence through the organization’s supported security process. Do not copy a broad HR role simply because another administrator can see everything in a comparison screenshot. Verify the smallest legitimate task and negative access boundaries.
08 Investigate without changing data
Use display to establish the saved facts and the question the application is answering. Maintenance should follow a concrete approved correction, not serve as a diagnostic experiment.
Confirm the work-area identity
Select P100 and verify its personnel assignment in the active work area.
Expected observation: A similar search-result name has not selected another employee.
Set category and dates
Choose the relevant infotype/subtype and a period covering the disputed date.
Expected observation: The offered record population is explicit.
Review neighboring records
Open the permitted overview and note start/end boundaries around 30 November/1 December.
Expected observation: A and B form the declared transition.
Compare the report or consumer
Record its evaluation date and actual input/output reference.
Expected observation: A current/future mismatch is distinguished from wrong data.
Define any authorized maintenance
Specify operation, target record, effective interval and expected neighboring results before PA30 use.
Expected observation: The proposed correction is reviewable and narrowly scoped.
09 Troubleshoot missing and unexpected records
A blank screen, missing future record or disabled operation has several possible causes. Identify the layer before proposing a role or data change.
| Observation | Inspect | Interpretation to test |
|---|---|---|
| Wrong person’s value | Active work-area identity | Search selection may not be the intended assignment |
| Future B absent | Period and subtype | Current-date selection can exclude future data |
| Only one user sees B | Selection and authorized responsibility | Access or date scope can differ |
| New record rejected | Time constraint/neighbors | Overlap, gap or required history conflict |
| Maintenance unavailable | Activity access and supported operation | Display permission is not change permission |
| Downstream report unchanged | Consumer period/run/input | Saving master data is not recalculating every result |
10 Preserve history when correcting an effective date
Suppose the approved move is 15 December rather than 1 December. Reconstruct the desired timeline before editing: A through 14 December and B from 15 December under the declared continuous subtype design. Check whether the installed operation automatically delimits or adjusts neighbors, and inspect its messages before saving.
After authorized maintenance, reopen the overview and evaluate14 December and 15 December. A changed B start alone does not prove that A’s end was extended or that no gap remains. Conversely, changing A’s address content to B would wrongly describe the earlier interval. The correct acceptance criterion is the complete intended history, not one field matching a request.
11 Payroll and replication restrictions need their own evidence
A payroll-relevant past/current change can be restricted by payroll state or retroactive limits. An Employee Central replication flow can apply additional control-record rules that differ from direct PA30 maintenance. Capture the actual operation and source route before interpreting a rejection as a missing role.
If the data is mastered in another application, verify ownership and synchronization before making a local correction. A direct target change may be overwritten by the next replication or leave source and target inconsistent. The correct resolution can be an approved source correction and reprocessing, with target display used to verify the result. Do not assume one PA30 save completes the integrated employee-data process.
12 Verify display and change outcomes separately
A positive display check returns A on 14 November and B on 1 December. A positive authorized correction check modifies only the intended future record, then reopens the overview and neighboring key dates. Preserve the change reference or audit evidence available under the actual process.
A negative test uses a user with legitimate display-only access and confirms that the business read works without granting maintenance. Another chooses the wrong subtype and explains the different record rather than changing it. A boundary test evaluates the day before and on the corrected move date. These are proposed training checks; no employee data was accessed or maintained in a customer system for this article.
13 Compare two displays with an explicit selection worksheet
When two administrators disagree, record personnel assignment, infotype, subtype, period start/end and the actual record start/end from each display. Then compare the work-area identity and relevant access context. This small matrix often reveals that one person is showing a future interval and the other is showing today.
For P100, a14 November key-date result of A and a November–December overview containing A/B can both be valid. The resolution is to label those questions correctly, not to remove B or change A. Only after the selections and identities match should a remaining discrepancy be investigated as missing data, saved-state or authorization behavior.
14 Frequently asked questions
Can PA30 be used simply to read? It may expose display functions, but use the authorized display route for an investigation and avoid unnecessary maintenance. Does a record being visible mean it is current? Read its interval and the selected date. Why can I start PA20 but not see a particular infotype? Transaction access and data authorization are different layers.
Can I fix a report by changing history? Establish whether the record or the report’s date/selection is wrong. Use the infotype lesson for time constraints, personnel-area guidance for organizational dependencies and PA03 guidance when the restriction comes from payroll processing rather than the display transaction.
Related services and next steps
Primary sources
Found this useful?
Share this guide with your network, or leave a like.
Your like is saved in this browser.