Title
Initialization of Table HRMDORIGIN

Purpose
This report initializes table HRMDORIGIN, which is used to store theoriginal systems of objects in distributed Organizational Management,and in the 'Distributed HR Master Data' scenario. For more informationon the 'Distributed Organizational Management' and 'Distributed HRMaster Data' scenarios, access the SAP Library and chooseCross-Application Components -> Business Framework Architecture ->ALE Business Process Library -> Human Resources -> Master DataDistribution (Human Resources).

Integration

Prerequisites
If you want to use the original system mechanism, you must set the ALEREPLI or ALE REPPA switch in table T77S0.

Features
All of the objects selected on the selection screen that do not have anentry in table HRMDORIGIN are listed for an entry with the currentsystem as the original system. If required, you can enhance this listwith additional information by including the objects that were selectedbut for which an original system has already been registered inHRMDORIGIN. If you do not want to enter all of the objects, you can usethe list to make a selection. The selected objects are entered, andchange pointers are written so that the table entries are distributedto the other logical systems in the distribution model. If an objecthas outdated entries in table HRMDORIGIN, they are deleted when the newentry is made. The selection screen enables you to deactivate thedistribution of entries by change pointers. If you decide to use thisoption, you must make sure that the original entries of existingobjects remain the same in all systems.
In batch processing, the table is skipped with the option ofdeselection, and selected objects that have not been registered in theoriginal table are entered directly.

Activities
This report must gradually be started in all of the logical systemsentered in the distribution model.
Each time the program is started, you must ensure that change pointerswritten in other systems during previous initialization activities arewritten successfully in the current system. The original system mayotherwise be initialized twice, that is, incorrectly.

Examples

Distributed Organizational Management
In your distribution model, an HR System is connected to a LogisticsSystem. Some of the organizational units of type 'A' (workcenters) are in the HR System, and some are in the Logistics System. Tohandle this situation, you have provided the following number ranges:

• 00000000 - 09999999 HR work center


• 10000000 - 19999999 Logistics work center

To initialize table HRMDORIGIN for object type 'A', start thereport in the HR System with the following parameters:

• Object type = A


• Object ID = 00000000-09999999

Let the report enter all of the objects listed. Now start the report inthe Logistics System with the following parameters:

• Object type = A


• Object ID = 10000000-19999999

Once again, let the report enter all of the objects listed.

Distributed HR Master Data
System A is the 'Corporate System', in which planning data ismaintained. Systems B and C are local payroll systems; employees whobelong to company code 'DE01' are maintained in system B, and employeeswho belong to company code 'DE02' are maintained in system C.Initialize all objects of type 'O' and 'S' in system A,and use change pointers to distribute this information to systems B andC. To effect initialization in system B, you access the 'employeeselection screen' and enter company code 'DE01'. You then select all ofthe employees with company code 'DE02' in system C.