Customer Relationship Management Blogs by Members
Find insights on SAP CRM and other customer relationship management products and topics in blog posts from community members and share your own perspective.
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member
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.




!https://weblogs.sdn.sap.com/weblogs/images/251712330/blog3-3.JPG|height=308|alt=image|width=599|src=...!
        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



      !https://weblogs.sdn.sap.com/weblogs/images/251712330/blog3-6.JPG|height=273|alt=image|width=501|src=...!
        Distribute model view (this is done through menu entry Edit/ model view/ distribute (transaction BD64).



        !https://weblogs.sdn.sap.com/weblogs/images/251712330/blog3-8.JPG|height=83|alt=image|width=588|src=h...!

          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.





          !https://weblogs.sdn.sap.com/weblogs/images/251712330/blog3-14.JPG|height=245|alt=image|width=597|src...!

              1. In Order to get modified data replicated automatically, it is necessary to activate the change pointer mechanism. Also plan a job that invokes report RBDMIDOC, which generates IDoc’s by the information provided by the change pointers.
                  1. In source system :-IMG path:- ALE -> Master Data Distribution -> Replication of Modified Data -> Activate change pointers for Message Types>
                  1. IMG path:- ALE -> Master Data Distribution -> Replication of Modified Data -> Creating IDocs from change pointers -> Define Variants>
                  1. Creating IDocs from change pointers -> Schedule Job>
                !https://weblogs.sdn.sap.com/weblogs/images/251712330/blog3-15.JPG|height=307|alt=image|width=382|src...!


              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.
            9 Comments