Skip to Content
This weblog is about distributing HR master data from HR system to CRM system. The Employee data exchange is not supported by the standard middleware so we need to setup the ALE distribution.

Some simple steps needs to be perform in both (source and target) the system to Use transaction BD64 and create a distribution model. Add a message type HRMD_A if HR system is smaller than 4.6C else HRMD_ABA. Add the filter setting to the distribution model as per note 312090. Save the distribution model. Generate the partner profile.




        1. Generate partner profile again (Transaction BD64).

      In transaction WE21 check for the version of IDocs record types. Change it to 3.0/3.1 only if HR system is smaller than 4.6C



        Distribute model view (this is done through menu entry Edit/ model view/ distribute (transaction BD64).


          Follow the steps mentioned below in the target(CRM) system:

          Maintain inbound parameter: Call the transaction WE20, expand the tree “Partner Type LS” and select the logical system of the target system. Insert into the table “inbound parameter” the message type HRMD_ABA.


              1. All objects of object type P are distributed with program RHALEINI. As a transfer mode, the INSERT mode should be used. This way we make sure that all objects of object type P are created in the target system for existence check. Then, also all distributed infotypes are created, especially the relationships to the organizational structure.

            Now the basic steps are taken and it should be possible to replicate employees. When IDocs arrives at the target system it will immediately be posted. This is ok for the test system but it could cause performance issue in production system. This can be change by calling transaction WE20 in the target system, expand the tree “Partner Type LS” and select the logical system of the target system. Double click at the line “HRMD_ABA” in table “inbound parameter”. In the group input mode select the radio button “collect IDocs”. We may now process incoming IDocs manually in transaction BD87 or schedule a job.

            In order to get replication work properly some customization needs to be done in the target system. I will be covering it in my next weblog.

            To report this post you need to login first.


            You must be Logged on to comment or reply to a post.

            1. Former Member
              Hi Vikash,

              Thanks for this useful blog. It’s nice to have screenshots for every step.
              I did the same for SRM systems, and it seems almost the same.
              It also worth to mention OSS Note 312090 – Integration HR – EBP/CRM, which is a good reference for this topic.
              Best regards,

              1. Former Member Post author
                Hi Peter,

                Thanks for your valuable comment. I will be adding those refrences in my blog part – 2.

                Once again thanks for the comment. It really help us to improve the quality of the document.

                Best regards,

            2. Former Member
              We replicate our HR org/position data to CRM so that it can be used for a custom approval process that we use within CRM’s TPM.  In addition to the replicated HR Data, then we have also created a “custom” org directly in CRM and are manually assigning positions and people to this custom org.  This way we can support both employees that have been setup in HR, as well as non-employees which our HR group will not maintain.  Just thought I’d mention this since it might give you some ideas for future scenarios.  I really liked your level of detail in this blog, I wish you’d created before I wrote all my documentation.  I could have just cut and pasted your hard work into my document.
              1. Former Member
                Nice Blog.

                Suppose on CRM system Business Partner (Role – Employee) is created manually. Then user creates the same employee at R/3 side & he is interested to replicate into CRM.
                In this case, it is not getting replaced.

                Suggestions please.

                Bapu Aher

            3. Former Member
              Hi Vikash,

              Thanks for such a detailed document. I have one more query though.
              Can we replicate the Organization Structure from HE system to CRM? If yes, can you please guide us?

              Many Thanks once again.

              Warm Regards,

            4. Former Member
              Firstly, Thanks for writing this very informative and helpful blog on replicating master data!!

              I have followed the steps as you said and have now managed to replicate all org units, positions and jobs successfully. However I currently have a problem when transferring the person details in respect of infotype 105.

              I keep getting the error that ‘infotype 105 could not be created because person <> does not exist.

              When I view the person in pa20, the data appears to be there but I still get this message. I also get a similar error when running transaction PZ03 for the person.

              You mentioned in your weblog that there were some pre-requisites for transferring master data…

              Could you help shed any light on something I may have missed?

              Also, I am not replicating into a CRM system but into a standalone instance of mySAP ERP 2005…


            Leave a Reply