Many applications outside the SAP Human capital management- system need HR data. A lot of questions occur in the forums how to set up such distribution scenarios. As I have had the privilege to cooperate with the developers of the HR ALE technology very closely I have summarized the most important information. There are tons of information available I have chosen the ones which have been helpful for me in the past. This should make HR master data distribution easy for you if you are a beginner in this area.
The document ALE quick start for distributed HR enables you to set up a complete HR distribution scenario. Please go through all the steps not only to get the hands-on experience but also to understand the concept behind and especially the difference between a manual distribution of data and a change pointer triggered distribution.
The most important Transactions and reports for ALE in HR are:
SALE Central Access to ALE configuration
BD64 Maintain ALE Model View
WE20 Partner Profiles
WE21 Port definition
SM36 Define batch jobs
Monitoring / Administration
WE02/WE05 IDoc Lists
WE09 IDoc Search
BD87 Status monitor for ALE messages, reprocess IDocs
BDM 5 Technical consistency check
PFAL = RHALEINI Manual distribution of HR Master Data.
BD21 = RBDMIDOC Evaluate Change Pointer Tables and create IDocs
RE_RHALECPS Display HR ALE Change Pointers
RE_RHALESMD Evaluate HR ALE Change Pointers. Re-evaluation of CPs
already processed is also possible.
A huge task could be distributed customizing. The overall guideline is that the HR-customizing in the different system which exchange data must be the same. This guideline is sometimes hard to follow. Therefore it is very recommendable to use a spreadsheet link the one below in order to work out the affected customizing settings. (Please note that this is just an example and not complete).
Distribution to a CRM-system
The example in the quick start mentioned above describes a distribution between two ERP-systems. If you want to distribute data from an ERP to a CRM/ SRM system refer to:
This note provides the information for integration scenarios as of SRM release 3.0 and CRM release 4.0.
Please note that these scenarios include another IDoc-type: HRMD_ABA.
Adding more infotypes
The IDoc-type HRMD_A and HRMD_ABA in their different versions contains the infotypes necessary to support the different integration scenarios mentioned in the IMG. Nevertheless it is possible to support all the different infotypes even if they are custom developed. The only exception is the infotype 2011.
This note provides a guideline on how to distribute custom infotypes or even extended standard infotypes.
165699 HR-CA-ALE: Segment Z1Pnnnn prevents distribution
The use of this note is required if filtering is done and 105148 was applied.
Limitations and restrictions
The possible distribution scenarios and the most important restrictions are mentioned in:
Moreover this note provides several hints in case you run into an error with your distribution scenario.
More information and links for error handling can be found in:
A more detailed description of the limitations are enumerated in:
Initial distribution in detail
363187 HR-CA-ALE: Initial distribution w. HRMD_A/HRMD_ABA
This note provides a step-by-step instructions on how to initially distribute HR Master Data. Especially important with respect to EBP/CRM, since data distribution using e.g. an OM root object following an evaluation path may not lead to the expected result.
Up from release R/3 Enterprise the filtering mechanism have been enhanced. In addition to the standard filters (most important: object type, infotype, subtype) you can now filter the distributed data based on organizational data (e.g. only distribute data for a specific subsidiary).
As of release 4.7 transactions OOALE_FILTER1 and OOALE_FILTER2 can be used to set up such a filtering. Two filter criteria can be implemented based on your choice. You have to implement the necessary customer specific coding in the BAdI HRALE00OUTBOUND_
IDOC, Interface FILTER_VALUES_SET. You can find more information in the documentation provided in the transaction SE 18.
Hopefully this blog makes your task a bit more easy.