What Is The Difference Between HRP1000 And HRP1001 In SAP?

HRP1000 and HRP1001 are two of the most foundational database tables in SAP Human Capital Management (HCM) for Organizational Management (OM).

At a high level, the difference is that HRP1000 stores the organizational objects themselves, while HRP1001 stores the relationships between those objects. Together, they are essential for building and maintaining the entire organizational structure in SAP.

Detailed article: The two-table model of SAP Organizational Management

To understand the core difference between HRP1000 and HRP1001, it is best to view them as a "nodes and connections" model of a company's organizational structure.

• HRP1000: The Nodes. This table contains the individual components, or "nodes," of the organization. When you create a new organizational unit, a position, or a job in SAP, the system generates a new record in the HRP1000 table. This table stores the fundamental existence and descriptive details of these objects.
• HRP1001: The Connections. This table provides the "connections," or relationships, that link the nodes from HRP1000 together. For a position to be part of an organizational unit, or for an employee to be assigned to a position, there must be a corresponding entry in HRP1001 defining that connection.

This two-table structure is how SAP builds the complete picture of your organization, from the highest-level reporting lines down to which employees occupy which seats.

Anatomy of an HRP1000 record

An entry in HRP1000 is relatively straightforward. Its primary fields define the object itself:

• PLVARcap P cap L cap V cap A cap R

  𝑃𝐿𝑉𝐴𝑅

  (Plan Version): The plan to which the object belongs (e.g., '01' for the active plan).

• OTYPEcap O cap T cap Y cap P cap E

  𝑂𝑇𝑌𝑃𝐸

  (Object Type): The type of object being created. Common values include:

  • O: Organizational Unit
  • S: Position
  • C: Job
  • P: Person

• OBJIDcap O cap B cap J cap I cap D

  𝑂𝐵𝐽𝐼𝐷

  (Object ID): A unique, system-generated number that identifies the object.

• STEXTcap S cap T cap E cap X cap T

  𝑆𝑇𝐸𝑋𝑇

  (Object Name): The full, descriptive name of the object.

• SHORTcap S cap H cap O cap R cap T

  𝑆𝐻𝑂𝑅𝑇

  (Abbreviation): A short-text version of the object's name.

• BEGDA/ENDDAcap B cap E cap G cap D cap A / cap E cap N cap D cap D cap A

  𝐵𝐸𝐺𝐷𝐴/𝐸𝑁𝐷𝐷𝐴

  : The validity period for the object.

Anatomy of an HRP1001 record

The HRP1001 table defines a relationship between two objects, and therefore has a more complex key and set of fields:

• OTYPEcap O cap T cap Y cap P cap E

  𝑂𝑇𝑌𝑃𝐸

  and OBJIDcap O cap B cap J cap I cap D

  𝑂𝐵𝐽𝐼𝐷

  : The object initiating the relationship (the "from" object).

• RSIGNcap R cap S cap I cap G cap N

  𝑅𝑆𝐼𝐺𝑁

  (Relationship Direction): Defines the direction of the relationship, which is a key concept. It is either 'A' for a "top-down" relationship or 'B' for a "bottom-up" relationship.

• RELATcap R cap E cap L cap A cap T

  𝑅𝐸𝐿𝐴𝑇

  (Relationship Type): The specific type of relationship (e.g., '002' for "Reports to," '008' for "Holder").

• SCLAScap S cap C cap L cap A cap S

  𝑆𝐶𝐿𝐴𝑆

  (Related Object Type): The object type of the receiving object (the "to" object).

• SOBIDcap S cap O cap B cap I cap D

  𝑆𝑂𝐵𝐼𝐷

  (Related Object ID): The ID of the receiving object.

A crucial point about HRP1001 is that relationships are created bi-directionally to ensure consistency. For example, if you create a relationship stating that Position X reports to Position Y (RSIGNcap R cap S cap I cap G cap N

𝑅𝑆𝐼𝐺𝑁

='A'), the system automatically creates a corresponding inverse relationship stating that Position Y is reported to by Position X (RSIGNcap R cap S cap I cap G cap N

𝑅𝑆𝐼𝐺𝑁

='B'). This ensures the integrity of the organizational chart when traversing it in either direction.

A practical example: Mapping the organization

Consider a simple organizational structure:

• The 'Global Marketing' organizational unit.
• The 'Marketing Manager' position.
• The employee 'Jane Smith.'

Here is how HRP1000 and HRP1001 work together to represent this in SAP:

1. HRP1000 records are created for each object:
   • Record 1: $$(OTYPE='O', OBJID='00001000', STEXT='Global Marketing')
   • Record 2: $$(OTYPE='S', OBJID='00002000', STEXT='Marketing Manager')
   • Record 3: $$(OTYPE='P', OBJID='12345678', STEXT='Jane Smith')
2. HRP1001 records define the relationships:
   • Connection 1: Position belongs to Org Unit:
     • To connect the 'Marketing Manager' position to the 'Global Marketing' unit, two records are created in HRP1001:

       • **Top-down (RSIGNcap R cap S cap I cap G cap N

         𝑅𝑆𝐼𝐺𝑁

         ='A'):**(OTYPE=′O′,OBJID=′00001000′,RELAT=′003′,SCLAS=′S′,SOBID=′00002000′)open paren cap O cap T cap Y cap P cap E equals prime cap O prime comma cap O cap B cap J cap I cap D equals prime 00001000 prime comma cap R cap E cap L cap A cap T equals prime 003 prime comma cap S cap C cap L cap A cap S equals prime cap S prime comma cap S cap O cap B cap I cap D equals prime 00002000 prime close paren

         (𝑂𝑇𝑌𝑃𝐸=′𝑂′,𝑂𝐵𝐽𝐼𝐷=′00001000′,𝑅𝐸𝐿𝐴𝑇=′003′,𝑆𝐶𝐿𝐴𝑆=′𝑆′,𝑆𝑂𝐵𝐼𝐷=′00002000′)

         (Org Unit 00001000 includes Position 00002000)

       • **Bottom-up (RSIGNcap R cap S cap I cap G cap N

         𝑅𝑆𝐼𝐺𝑁

         ='B'):**(OTYPE=′S′,OBJID=′00002000′,RELAT=′003′,SCLAS=′O′,SOBID=′00001000′)open paren cap O cap T cap Y cap P cap E equals prime cap S prime comma cap O cap B cap J cap I cap D equals prime 00002000 prime comma cap R cap E cap L cap A cap T equals prime 003 prime comma cap S cap C cap L cap A cap S equals prime cap O prime comma cap S cap O cap B cap I cap D equals prime 00001000 prime close paren

         (𝑂𝑇𝑌𝑃𝐸=′𝑆′,𝑂𝐵𝐽𝐼𝐷=′00002000′,𝑅𝐸𝐿𝐴𝑇=′003′,𝑆𝐶𝐿𝐴𝑆=′𝑂′,𝑆𝑂𝐵𝐼𝐷=′00001000′)

         (Position 00002000 belongs to Org Unit 00001000)

   • Connection 2: Employee holds Position:
     • To staff 'Jane Smith' into the 'Marketing Manager' position, another pair of HRP1001 records is created:

       • **Top-down (RSIGNcap R cap S cap I cap G cap N

         𝑅𝑆𝐼𝐺𝑁

         ='A'):**(OTYPE=′S′,OBJID=′00002000′,RELAT=′008′,SCLAS=′P′,SOBID=′12345678′)open paren cap O cap T cap Y cap P cap E equals prime cap S prime comma cap O cap B cap J cap I cap D equals prime 00002000 prime comma cap R cap E cap L cap A cap T equals prime 008 prime comma cap S cap C cap L cap A cap S equals prime cap P prime comma cap S cap O cap B cap I cap D equals prime 12345678 prime close paren

         (𝑂𝑇𝑌𝑃𝐸=′𝑆′,𝑂𝐵𝐽𝐼𝐷=′00002000′,𝑅𝐸𝐿𝐴𝑇=′008′,𝑆𝐶𝐿𝐴𝑆=′𝑃′,𝑆𝑂𝐵𝐼𝐷=′12345678′)

         (Position 00002000 is held by Person 12345678)

       • **Bottom-up (RSIGNcap R cap S cap I cap G cap N

         𝑅𝑆𝐼𝐺𝑁

         ='B'):**(OTYPE=′P′,OBJID=′12345678′,RELAT=′008′,SCLAS=′S′,SOBID=′00002000′)open paren cap O cap T cap Y cap P cap E equals prime cap P prime comma cap O cap B cap J cap I cap D equals prime 12345678 prime comma cap R cap E cap L cap A cap T equals prime 008 prime comma cap S cap C cap L cap A cap S equals prime cap S prime comma cap S cap O cap B cap I cap D equals prime 00002000 prime close paren

         (𝑂𝑇𝑌𝑃𝐸=′𝑃′,𝑂𝐵𝐽𝐼𝐷=′12345678′,𝑅𝐸𝐿𝐴𝑇=′008′,𝑆𝐶𝐿𝐴𝑆=′𝑆′,𝑆𝑂𝐵𝐼𝐷=′00002000′)

         (Person 12345678 holds Position 00002000)

Key takeaway

Ultimately, the separation of HRP1000 and HRP1001 is a fundamental design principle in SAP HCM that enforces data integrity and flexibility. HRP1000 provides the content (the objects), while HRP1001 provides the context (the relationships). This structured approach enables the complex reporting and analysis of organizational data that is central to many SAP functions. Any developer or consultant working with Organizational Management must have a clear understanding of these two tables and their interplay to effectively navigate and manipulate the organizational model.