Master Data Distribution (Human Resources) 

Use

You can distribute Human Resource master data (organizational data, HR master data) between different systems.

Features

An infotype is distributed completely with all fields.

Entries in table T77TR set an import lock for objects in the target system.

In insert mode (complete distribution), the objects are transported completely.

In update mode (change pointers), transported data is replaced completely in the target system.

Object types and infotypes can be further restricted by filters. A filter should be defined for the object types that are actually required.

Distributable HR Master Data

If you want to distribute HR master data, various filter types must be maintained in the distribution model for message type HRMD_A.

Message type HRMD_A must be assigned a filter object of the 'object type' type, and the value P.

For infotypes to be distributed, message type HRMD_A must be assigned a filter object of the 'infotype' type for each infotype, and the infotype number as the value.

You can distribute all standard scenario infotypes that are required in the non-HR system.

Infotypes for important applications in the target system:

-         If you want to validate personnel numbers using the HR master record (existence check), object type P and infotypes 0000, 0001, 0002, and 0003 must be distributed.

-         If you want to generate vendors in FI, object type P and infotypes 0000, 0001, 0002, 0003, 0006, 0009, and 0017 must be distributed.

-         If you want to identify the sales employee, object type P and infotypes 0000, 0001, 0002, 0003, 0006, and 0900 must be distributed.

Distributable Organizational Data

All Organizational Management object types are distributed (except X*; for information on TS, T, WF, WS, and RY, see below).

All Organizational Management infotypes can be distributed (with the exception of roles and workflow).

Constraints

Human Resource data has just one centralized SAP HR system in which all Human Resource components are integrated. HR master data and organizational data must not be changed in the receiving system. Profiles with read authorization, for example, can be used to ensure this.

Data in the receiving system is created using the same plan version as in the sending system.

If more HR master data needs to be maintained in the receiving system, you must ensure that the number range intervals are different from those in the sending system.

Tasks and responsibilities are not distributed, the relationship (1001) for these object types can be distributed.

If you are in update mode, local Organizational Management relationships are retained in the target system.

If you delete an object without activated change pointers, you must also delete it manually in the target system.

Data is saved in the target system without a dialog check.

Texts on HR master data infotypes are not distributed.

If you want to distribute HR master data infotypes, you must ensure that infotypes 0000, 0001, 0002, and 0003 are distributed. Infotype 0003 is only distributed by change pointers if it has been changed in combination with one of the other HR master data infotypes that are supported.