A personnel transfer can look correct today and still be wrong for a historical date. Classic SAP HR/HCM stores many employee records with validity periods. A reliable transfer changes the relevant assignment from the intended date while preserving the earlier history.
This exercise uses fictional employee data in classic SAP HCM Personnel Administration. It is not a SuccessFactors Employee Central workflow. Organisations may integrate the two products, but their screens, event handling and data models differ. Configuration, country-specific payroll and integration design determine the exact transfer steps in a real system.
Define the business change first
Employee TEST-240 works in organisational unit “Service Operations” with cost centre C100 through 15 October. The approved transfer moves the employee to “Project Services” and cost centre C200 from 16 October. The personnel number stays the same, and this example does not change company code, payroll area, salary or work schedule.
Those exclusions are deliberate assumptions for the exercise. A real transfer might change any of them, so obtain the approved values and effective dates rather than assuming that every field follows the organisational unit.
| Validity period | Organisational unit | Cost centre |
|---|---|---|
| Through 15 October | Service Operations | C100 |
| From 16 October | Project Services | C200 |
Before entering data, record the current assignment, intended position, effective date, approval reference and fields that must remain unchanged. Use synthetic names and identifiers in portfolio screenshots. Actual employee records can contain personal and salary information that is unnecessary for demonstrating this skill.
Understand which records carry the change
In classic Personnel Administration, infotype 0000 stores personnel-action information and infotype 0001 stores organisational assignment. Your configured transfer action and infogroup determine which records the user processes. Do not expect every organisation to use the same action code or screen sequence.
If Personnel Administration and Organizational Management are integrated, inspect the target position and its relationships for the transfer date. The position might exist today but not be valid on 16 October, or its cost-centre assignment might change later. Check the configured source of each assignment instead of manually overriding a derived value.
Check the date boundary, not only today’s display
- Display organisational assignment immediately before the transfer, on 15 October. Expect Service Operations and C100.
- Display the assignment on 16 October. Expect Project Services and C200.
- Display the assignment on a later date. Confirm that a pre-existing future record has not unexpectedly restored the old assignment.
- Review the record overview for gaps and overlaps according to the infotype’s configured time constraint.
- Check the action history and the configured reason for the transfer.
For the expected uninterrupted organisational assignment in this example, the old interval ends on 15 October and the new one starts on 16 October. Ending the old record on 14 October leaves a missing day. Keeping it valid through 16 October while a new record also starts that day creates a conflicting boundary unless the system’s time-constraint handling resolves it.
Separate transfer dates from payroll consequences
A transfer entered after payroll processing may affect retroactive accounting, payroll posting or reporting, depending on the changed fields and system settings. Ask the payroll owner which period is affected, whether the employee has already been processed and which payroll controls apply.
A mid-month cost-centre change does not mean that every payroll amount must be divided equally between two cost centres. Posting rules, payroll results, cost distribution and other configuration can determine the allocation. Validate the expected output with the payroll and finance teams rather than calculating a split from the calendar alone.
Build useful negative checks
In a training system, try a target position that is not valid on the transfer date, a future-dated assignment that conflicts with the intended change and an incorrectly entered effective date. Record the message or observed history and the controlled correction you would propose.
Also inspect authorisation scope. A user being unable to select a position may be a legitimate access restriction rather than missing master data. The correction should match the cause and the organisation’s maintenance process.
Prepare an evidence sheet for review
A concise deliverable contains the approved scenario, before-and-after validity intervals, unchanged-field checks, target-position validity and payroll-impact questions. Mark expected outcomes separately from observed outcomes; this example is a learning plan, not a claim that a system test has been completed.
The SAP HCM personnel-administration guide explains the broader employee-data model. The SAP support ticket lifecycle project can help you write a clear investigation record. For the course covering personnel administration, organisational management, time and payroll topics, review SAP HR training in Vizag at Softenant and confirm which HCM landscape is available for practice.
Worked example: find a future record that reverses the transfer
Extend the fictional case with a record already scheduled for 1 November. It contains Service Operations and C100 because it was created before the October transfer was approved. The employee looks correct when you inspect 16 October, but a report with a 1 November key date shows the old team again. This is a useful practice problem because the first transfer screen can be correct while the complete timeline still fails.
Write three expected results before editing anything: 15 October should show C100; 16 October should show C200; and 1 November should continue to show C200 unless a separate approved business change applies. Then compare those expectations with the record overview. In this example, the November record is evidence of a conflict to investigate, not automatic permission to delete it.
Ask what business event originally created the November record. It might contain another legitimate change that must be retained. The proposed correction should preserve that approved change while carrying forward the correct organisational assignment. After the authorised correction, repeat all three date checks and review the entire affected interval. Record who reviewed the outcome and which items remain open.
Use a small diagnosis table before proposing a correction
| Observed symptom | First check | Evidence to retain |
|---|---|---|
| Old team appears in a report | Report key date and employee selection | Selection screen and dated assignment |
| Correct team but unexpected cost centre | Target position relationships and assignment source | Effective dates of the relevant relationship |
| Change disappears next month | Existing future assignment records | Complete validity timeline |
| Action saved but result incomplete | Records actually processed in the configured sequence | Saved records and skipped or pending steps |
Treat each row as a hypothesis. A screenshot of an unexpected value identifies a symptom; it does not establish the cause. Avoid changing several fields together during diagnosis, because the resulting success would not reveal which correction mattered.
Frequently asked questions about personnel transfers
Which transaction codes can a beginner use?
In a classic SAP GUI training landscape, PA20 is used to display HR master data and PA40 provides personnel actions. Use the action configured by your instructor for organisational reassignment. Screen availability, authorisations and local procedures determine the exact path. A transaction code alone does not specify the approved business process.
Why should I check more than one infotype?
An action brings related records together, but a successful save does not prove that every required step was completed. Compare the approved change with the records actually saved. In this exercise, explicitly confirm the assignment and verify that salary, work schedule and payroll area still match the starting evidence.
Does a transfer always create a new personnel number?
No new number is required by this fictional internal-transfer scenario. Other employment or legal-entity changes can follow different processes. First establish the business event and the organisation’s personnel-number policy; do not generalise this exercise to every movement between companies.
What makes the exercise ready for review?
Another learner should be able to identify the employee, reproduce the date selections, explain the old and new assignments, and locate any unresolved payroll question. A final result of “saved successfully” is insufficient when the historical and future checks are still pending.
Official SAP references
For the underlying concepts, consult SAP Learning’s Executing Personnel Actions lesson and SAP Help’s Organizational Assignment, Infotype 0001. Check documentation for your installed product and release when applying the exercise.