Distributing the HR-ORG Model 

Use

You want to distribute the HR-ORG model that you have created in your HR system to one or more systems (see scenarios) to use it to perform indirect role assignment in these systems.

You should usually only distribute the required objects when distributing the HR-ORG model. In this description, only the objects required for user administration are distributed.

The distribution process is dependent on the following factors, which you must also consider later when making the filter settings for the HR-ORG model:

·        Maintaining the role assignments in the HR-ORG model: If you make the role assignments in the HR-ORG model in the source system and distribute them together with the model, use authorizations in the receiving system to ensure that no user can change the HR-ORG model. If you perform the distribution without links to roles, you should still use authorizations to ensure in the receiving system that no user can change the objects of the HR-ORG model. Only the role assignments may be changed.

·        Existence of the Employee organization object type: If at least one of the target systems does not know the employee object type (that is, it is not an HR system), the assignment of position to employee must be replaced by the assignment of position to user during the distribution process. To do this, create a Customer Exit that adds the position ‑ user relationships in addition to the existing position ‑ employee ‑ user relationships. The ALE exit filters then delete the relationships that cannot be used, depending on the target system.

Prerequisites

·        The 0105 infotype for the employee is maintained.

·        You have ensured that the same active plan version has the value 01 both in the HR system and in the target system. This parameter is in table T77S0, group PLOGI, and semantic abbreviation PLOGI.

·        The users used in the HR Org. structure of the source system must exist in all target systems (through CUA distribution or client copy), since only the relationships of the structure, but not those of the objects themselves are distributed.

Process Flow

If you are distributing the HR-ORG model with the user assignment from an HR system to an HR system and a non-HR system, the process flow is as follows:

...

       1.      Create the HR-ORG distribution model in the HR system. When doing this, ensure that you maintain infotype 0105 in particular.

       2.      Generate partner profiles in HR and in the CUA central system.

       3.      If one of the target systems does not know the Employee object type, create an outbound filter wih a customer exit in the HR system.

       4.      So that you can later distribute only the changed data of the HR-ORG model, activate the change pointers and, if necessary, write the change pointers for Infotype 0105 (for target systems that do not know the Employee object type).

       5.      Distriute the entire HR-ORG model

       6.      Distribute the changes to the HR-ORG model

 

See also:

·        SAP Note 200343: HR-CA-ALE: Composite SAP Note: Distribution of HR Master Data

·        SAP Note 363187: HR-CA-ALE: Initial Distribution with HRMD_A/HRMD_ABA (Tips)

·        SAP Note 200066: HR-CA-ALE: Q&A for Setting Up HR-ALE-Scenarios

This note contains links to the QuickStart documentation for ALE and the ALE HR business processes.

·        SAP Note 581019: Distribute PFCG HR-ORG model for indirect role