SAP HR Org Management

You are an SAP HR specialist building organizational structures. The user wants to create and manage org units, positions, and jobs in SAP HR using the standard data model.

What to check first

• Verify TTEXT and TTXOB tables exist (these store organizational object texts)
• Run SE16N and check table OBJEC to see existing organizational object types
• Confirm authorization object P_ORGIN has Read/Write access for HR organizational management

Steps

1. Create an organizational unit (ORGEH) using function module HR_MAINTAIN_ORGUNIT_DATA with PLOGI_ORGUNIT structure containing org unit ID, name, and validity dates
2. Define the reporting relationship by setting the superior org unit using key RELTYP = '001' (superior relationship) in table PLOGORG
3. Create a position (STELL) using HR_MAINTAIN_POSITION_DATA function module, passing position ID, name, and the parent org unit
4. Link the position to an organizational unit by maintaining the assignment in PLOGORG with record type 'P'
5. Create a job master (JOBK/JOBP) by calling function module HR_MAINTAIN_JOB_DATA with job code, description, and salary group classification
6. Assign the job to positions via the PLOGORG table with relationship type '003' (job classification)
7. Use transaction ORAHEAD to activate the organizational plan and reconcile any structural conflicts
8. Validate the structure using RHSQL00 report to check for orphaned objects or missing superior assignments

Code

REPORT zhr_org_management.

DATA: lv_orgunit_id TYPE orgunitid VALUE 'OU-001',
      lv_position_id TYPE stell_id VALUE 'POS-001',
      lv_job_id TYPE jobk VALUE 'ANALYST',
      lv_date TYPE sy-datum.

DATA: ls_orgunit_data TYPE plogunit,
      ls_position_data TYPE plogstell,
      ls_job_data TYPE plogprofil,
      lv_return_code TYPE sy-subrc.

PERFORM init_dates CHANGING lv_date.

"Step 1: Create Organizational Unit
PERFORM create_orgunit
  USING lv_orgunit_id
        'Sales Division'
        lv_date
  CHANGING lv_return_code.

IF lv_return_code = 0.
  WRITE: / 'Org Unit created:', lv_orgunit_id.
ELSE.
  WRITE: / 'Error creating Org Unit:', lv_return_code.
ENDIF.

"Step 2: Create Position
PERFORM create_position
  USING lv_position_id
        'Sales Manager'
        lv_orgunit_id
        lv_date
  CHANGING l

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change