3752192 - Delivery organization in RM differs from S4HC after project demand replication

A delivery organization maintained for a project role in a professional services project in SAP S/4HANA Cloud Public Edition-S4HC appears as a different organization in Resource Management-RM.
For example, delivery organization ServiceOrg222 in S4HC and ServiceOrg111 in RM.

• SAP Product and Resource Management - Resource Management
• SAP S/4HANA Public Edition

1. In a professional services project in S4HC, create a demand/role and set the delivery organization as ServiceOrg111.
2. Let project data replicate to RM so that a resource request is created with service org ServiceOrg111.
3. In S4HC, update the delivery org to ServiceOrg222.
4. After replication, in RM, observe that the delivery organization differs from the value updated in S4HC.

By design, after the initial replication from S4HC, subsequent changes to the delivery organization are not replicated to RM.
That's because the delivery organization can be manually maintained by resource manager in RM and this should not be overwritten by later updates from S4HC.

1. Ensure the desired delivery organization is correct in S4HC before the initial replication of the demand/role, because later changes in S4HC do not update the delivery organization in RM.
2. If it's necessary to change the delivery organization in S4HC after the initial replication, and in "Manage Resource Requests" app, the request is 'Not Published', you can go to update the field 'Requested Resource Organization'. 
   If the request has already been 'Published', you can forward the resource organization by clicking 'Forward' button in "Staff Resource Requests" app.

delivery organization mismatch, resource management, sprm, rm, s/4hana cloud, professional services, resource request, staff resource requests, manage resource requests, demand replication, publishing status, forward service org, change documents, cloud alm, identify similar requests , KBA , PPM-CLD-RES , Resource Management , Bug Filed