HRP1000 table — Organizational Management Object Master (Infotype 1000)
HRP1000 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.
Verified practitioner reference for HRP1000 — Organizational Management Object Master (Infotype 1000), covering its real SAP role, keys and joins, diagnostic proof, S/4HANA context, common pitfalls, ownership, and related objects.
Published 20 Sept 2026· 550 words
Purpose
HRP1000 is the foundational object table of classic SAP Organizational Management. Each effective-dated row describes an OM object in a plan version: for example an organizational unit, position, job, work center, or another configured object type. The table tells you that an object exists, what it is called, its status, and when that version is valid. It does not describe how the object is connected to other objects; relationships belong in HRP1001.
Key fields
OM records are effective-dated, so object ID without plan version, type, and validity is incomplete.
- PLVAR — plan version.
- OTYPE — OM object type, such as O for organizational unit, S for position, C for job.
- OBJID — internal object ID.
- ISTAT — planning status.
- BEGDA/ENDDA — validity interval.
- SHORT/STEXT — short and long object descriptions where stored.
- LANGU — language context for text records where relevant.
How it joins the data model
HRP1001 uses the same PLVAR/OTYPE/OBJID object identity to store effective-dated relationships such as organizational-unit hierarchy, position assignment, job assignment, or holder assignment. PA0001 can reference OM objects for employee organizational assignment. PP01/PPOME provide standard maintenance views over the OM object and relationship model.
How to read it safely
Always select the intended plan version, object type, status, and key date. The same OBJID value can mean a different object when object type or plan version differs, and multiple time slices can exist over history. Use HRP1001 for the structure rather than assuming a parent or holder from HRP1000 alone.
How to prove it in the data
For an organizational object that appears missing or has the wrong name, identify its object type and ID in PPOME or PP01, then select HRP1000 for the active plan version and business date. Confirm an active validity slice and text. If the object exists but is placed incorrectly in the hierarchy, move the proof to HRP1001 and inspect the relevant relationship record rather than changing HRP1000.
ECC vs S/4HANA
HRP1000 remains part of SAP HCM Organizational Management in S/4HANA HCM and hybrid scenarios. In SuccessFactors Employee Central-led architectures, organizational objects may be replicated from the cloud and the backend table can become a consuming representation rather than the system of record. Direct backend maintenance must therefore follow the defined source-of-truth model.
Common pitfalls
- Selecting OBJID without OTYPE and plan version.
- Ignoring validity dates and reading a historical or future object slice.
- Expecting hierarchy or holder relationships in HRP1000 instead of HRP1001.
- Changing replicated OM data locally when Employee Central is authoritative.
- Treating an object text problem as a relationship problem or vice versa.
Whose problem this is
Primary ownership is HCM Organizational Management. SuccessFactors/integration teams join where objects are replicated from Employee Central, workflow teams consume the hierarchy, and Security may be involved where structural authorizations depend on the same OM model.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/hrp1000ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.