Symptom
When transporting a Flexible Workflow (e.g., Sales Order Approval Workflow) from Development (DEV) to Production (PROD), the workflow is only partially imported.
The following behaviors are observed:
- Workflow is missing one or more approval steps (e.g., Level 2 approver).
- Import completes with warnings.
-
In Import Collection → Execution Messages, the following message appears:
No target user found for user ‘CBXXXXXXXXXX’ [businessPartId USERID … type Conditional Workflow]
-
Additional messages may include:
Pre-Import of Business User Mappings was not successful
Missing user(s) [scenario WS02000006]
In the Manage Sales Document Workflows app:
- Only some steps (e.g., Level 1) are visible.
- Missing steps cannot be edited or added in Production.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- In DEV tenant:
- Open Manage Sales Document Workflows.
- Create or maintain a workflow with multiple approval steps.
- Assign a specific user (e.g., A.B) as approver in one step.
- Activate the workflow.
- Export the workflow via:
- Export Software Collection
- In PROD tenant:
- Import the same collection using Import Collection.
- Check:
- Import Collection → Execution Messages
- Manage Sales Document Workflows
Observed Result
- Import completes with warnings.
- Workflow is missing one or more steps (e.g., Level 2).
-
Execution Messages show:
No target user found for user ‘CBXXXXXXXXXX’
Expected Result
- Workflow should be fully imported with all approval steps and assigned users.
Cause
Business Users (CB Users) in SAP S/4HANA Cloud are:
- System-generated
- Tenant-specific
- Not consistent across DEV, QA, and PROD
Flexible Workflows store internal CB User IDs, not just the User ID (e.g., A.B).
During transport:
- The system attempts to map the CB User from DEV to PROD.
- If the same CB User ID does not exist in PROD, mapping fails.
- As a result, workflow steps referencing that user are skipped during import.
Additionally:
- Production system does not allow editing of transported workflows.
- Manual user mapping functionality is not exposed in Public Cloud.
Resolution
Option 1 (Recommended) – Recreate User and Workflow in DEV
- Ensure the user (e.g., A.B) exists and is active in both DEV and PROD.
- If needed, recreate the user in DEV to generate a new Business Partner and CB User ID.
- Recreate or copy the workflow in DEV.
- Assign the correct user.
- Activate the workflow.
- Re-export the software collection.
- Re-import into PROD.
Option 2 – Align User Setup Across Tenants
- Ensure users are created consistently in all tenants before workflow configuration.
- Avoid using stale or previously deleted user references.
Additional Information
- Workflows transported via Key User Extensibility are read-only in Production.
- CB User IDs cannot be manually aligned or edited across tenants.
- Missing users during import will result in partial workflow deployment.
See Also
Keywords
Flexible Workflow, Sales Order Workflow, Workflow Transport, Import Collection, Export Software Collection, Execution Messages, No Target User Found, CB User, Business User, Business User Mapping, Business Partner Mapping, Missing Workflow Step, Approver Assignment, Conditional Workflow, Manage Sales Document Workflows, Tenant Mismatch, S/4HANA Cloud Public Edition, Key User Extensibility, WS02000006 , KBA , SD-SLS-SO-2CL , Sales Orders (Public Cloud) , Problem
SAP Knowledge Base Article - Public