Approval workflows for master data changes
Give company administrators control over their connections. Keep setup, record review and automatic-update approval as separate decisions.
Who controls Business Partner master-data updates?
Data governance here means defined company access, self-service activation and explicit approvals for source changes. A company administrator can configure the company without a separate SaaS-admin enablement.
Separate setup from update approval
Company self-service
The company workspace limits access to its configuration and process results.
Separate decisions
Manual review confirms individual proposals. Critical automatic modes use the required administrator verification.
Bounded automation
Record outcomes and error references give the team a way to follow up incomplete work.
How it works
- 1
Configure
Set up the company.
- 2
Activate
Configure and test a connection.
- 3
Review
Approve the chosen process and records.
- 4
Confirm
Check results and resolve outstanding cases.
Example: Governance Workflows
A company administrator activates source updates. Users still review the proposed merge, and an automatic bulk mode has its own approval.
Stopping remaining work does not undo writes already completed. Source automation can run after an update.
Frequently asked questions
What does this process do?
Which systems and data are covered?
What access or approval is needed?
What should I check before using it?
Have a record or connection in mind?
Set up your company workspace, or describe the ERP and master data problem through Contact.