cancel
Showing results for 
Search instead for 
Did you mean: 

HR Replication - only part of org structure needed in SRM - excess IDOC's

lbraspenning
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear peers,

we are running HR-ALE to replicate HR master data from a separate HR system (ECC 6) into the ERP system (ECC 6, with SRM as add-on).

Only a part of the organizational structure is needed in SRM, this O-unit is specified in PFAL for initial replication. Delta replication is setup through change pointers - as recommended by SAP.

Unfortunately change pointers are generated for the complete org structure, not just for the org part we are replicating into SRM. This results in a lot of IDOC's that go into error because of missing and irrelevant data.

What can we do to avoid generating IDOC's that are not needed?

> continue with the change pointers, and filter out non-relevant data via user exit on outbound side

> switch off change pointers, and schedule PFAL in update mode instead

> perhaps the root org structure can be specified in the ALE distribution model filter as well so IDOC's generated from change pointers take this into account

Thanks for your point of view on this topic

Cheers, Linda

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Linda,

In our project SAP is the single point of truth. So we are not stopping any replication pertaining to postion and organization unit in SRM as well as CRM from SAP.

Having said that user is assgined to postion and user has role. As a results if any user doesn't have any role related to SRM and CRM , user will not be replicated. In that case those user deosn't have any authorization to access the SRM systems though their postion and organization unit may be avaialble in SRM.

otherwise : switch off change pointers, and schedule PFAL in update mode instead

This will be simplest methods

Regards

Dayal