Special Handling of Relationships

Use

An inconsistency exists for personnel planning if in table HRP1001 relationships exist that do not have a corresponding inverse relationship in the database.If infotype 1001 were to be handled in the same way as all other infotypes, such an inconsistency would arise. Therefore, the following procedure has been implemented:

  • Table HRP1001_ARCH exists for the inverse relationship records of relationships that have been archived or deleted. This is not taken into consideration by the normal HR functions. The structure of this table is identical to that of table HRP1001 .

  • When the archive is written, the relationships from HRP1001 and HRP1001_ARCH are read. In the archive, the table is always called HRP1001 .

  • Archived relationships are deleted as follows:

    • If the relationship still exists in table HRP1001 : the relationship is deleted from HRP1001 . The corresponding inverse relationship is copied to HRP1001_ARCH and deleted from HRP1001 .

    • If the relationship no longer exists in table HRP1001 : the relationship is deleted from HRP1001_ARCH .

This ensures that table HRP1001 contains either both records for a relationship or neither. Furthermore, all the data that belongs to a data object is always written. This is regardless of the order in which objects are archived and deleted.

You can use the object key to access the object. The relevant relationships are always included in the data objects for an object.