HR Master Data Distribution using ALE-IDOCS
This Document demonstrates a practical approach to distribute HR / HCM Master data for standard Infotypes and HRP master tables.
The data distribution is from one SAP system to another SAP system.
I have implemented and tested this Approach on ECC 6 SAP systems.
System Versions :
Sending System is on ECC 6 ( SP level 47 )
Receiving system is on ECC 6 ( SP level 97 )
Please note : It is not mandatory to have both systems on ECC6 with specified SP levels in order to distribute data.
You need to have a sound background on working of ALE-IDOCS and IDOC extension and IDOC enhancements.
You need to have good understanding of HR processes and master data concepts.
In addition to implement this strategy, consulting team needs to have a HCM Functional consultant.
Requirement in Brief :
- Create records for listed Infotypes in Partner system.
Infotypes like PA0000, PA0001, PA0002, PA0006, PA0022, PA0027, PA0041, PA0105 and several tables like HRP1001, HRP1002 etc.
This is for Cutover requirement.
- Post Cutover, delta records / updates in records to be transported to Partner system.
The following configuration needs to be done in SENDING system :
- Configure Logical system for your Partner system ( TCODE : SALE ) .
This configuration is usually done by Basis Consultants
- Create Partner Profile for your Partner system ( TCODE : WE20 ).
Maintain Message types HRMD_A and SYNCH.
SYNCH message type is not explicity required but in case you will be distributing Distribution Model,
system will ask you to maintain SYNCH message type.
- Create PORT ( TCODE : WE21 ) of type tRFC.
You need to specify PORT while adding Message type in Partner Profile.
- Get RFC created from BASIS consultant connecting to the receiving system.
- Create Distribution Model ( TCODE : BD64 ) and add Message type HRMD_A here
- This is the most IMPORTANT part. Creating Filter Group in Distribution Model.
I have created filter for Infotype 0001 which means only Infotype 0001 data will be distributed to receiving system.
we can add required Infotypes in this Filter Group to extend scope of data distribution.
If we do NOT create any filter group, then all Infotypes and HRP tables data ( specified in IDOC : HRMD_A07 ) will be distributed
The following configuration needs to be done in RECEIVING system :
- Logical system settings ( TCODE : SALE ).
- Partner Profile configuration for Incoming Message type HRMD_A ( TCODE : WE20 ).
Master Data Distribution Program :
- Execute Program RHALEINI ( TCODE : PFAL ) in Sending system . Specify required Object Type, ID etc. before executing.
Choose INSERT Radiobutton for ‘Transfer Mode’ as the data is sent for first time to Receiving system.
- As we see Outbound IDOCS have been generated from Sending system ( TCODE : WE02 / 05 ).
- Check for Inbound IDOCS in Receiving system.
- Some Inbound IDOCS may have errors . Reason will be some HR specific Data and config issues in Receiving system.
Take help of HR Functional consultant for this configuration and data issues and send data again.
Initial approach suggested for this requirement was download data from Sending system in excel file and upload it in Receiving system
using programs and BAPI call.
Advantages of this approach :
Development time is significantly reduced as ALE standard settings are required to transfer data
- After Cutover activity, updates / changes to Master data can be handled automatically using Change pointers .
- This does not require any manual intervention apart from scheduling RBDMIDOC program.
I will be covering Delta updates to Master Data using Change pointers and UPDATE Mode of program RHALEINI in next document.