Organization structure (internal) is crucial master data of SRM; as all of attributes, approval hierarchy, and lot, more is maintained here.
If SAP HR is in place for the organization units for which SRM is under implementation, then as best practice SAP HR can be used to leverage the SAP SRM organization structure.
SAP HR Infotype 1001 (along with 1000, 1002) provides the major of the user data.
Synchronization report (RHALEINI) is used to integrate the both systems, please note SAP HR will be the leading system.
Updates are carried out using the IDoc (HRMD_ABA), for the specified change pointers (report RBDMIDOC).
Transaction BBP_BP_OM_INTEGRATE can be used to fix if something missing.
Obvious but to remember - purchasing specific data (P. Org, P Grp..) needs to be maintained in the SRM.
The changes done in the SRM Organisation structure can be tracked with the maintenance of customisation in table T77CDOC_CUST. The changes can be with report RHCDOC_DISPLAY.
As change logging can deteriorates system performance only important and audit critical infotypes should be used. For exaple- approval limit, spend limit.
Note- SAP tells to limit the number of users in organisation unit maximum two hundred to avoid performance problem. As the attributes search, partner search is performed it takes longer time.
If SAP HR is in place for the organization units for which SRM is under implementation, then as best practice SAP HR can be used to leverage the SAP SRM organization structure.
SAP HR Infotype 1001 (along with 1000, 1002) provides the major of the user data.
Synchronization report (RHALEINI) is used to integrate the both systems, please note SAP HR will be the leading system.
Updates are carried out using the IDoc (HRMD_ABA), for the specified change pointers (report RBDMIDOC).
Transaction BBP_BP_OM_INTEGRATE can be used to fix if something missing.
Obvious but to remember - purchasing specific data (P. Org, P Grp..) needs to be maintained in the SRM.
The changes done in the SRM Organisation structure can be tracked with the maintenance of customisation in table T77CDOC_CUST. The changes can be with report RHCDOC_DISPLAY.
As change logging can deteriorates system performance only important and audit critical infotypes should be used. For exaple- approval limit, spend limit.
Note- SAP tells to limit the number of users in organisation unit maximum two hundred to avoid performance problem. As the attributes search, partner search is performed it takes longer time.