ERP synchronization after record approval
Publish a reviewed record without entering it again. Follow the result in the application rather than assuming the ERP update succeeded.
When is approved Business Partner data published?
Direct submissions send approved master data to the selected connection. Bulk jobs use background processing; configured synchronization routes run on their schedule.
Individual writes, batches and schedules
Direct submission
Use direct submission for individual reviewed records and the bulk workflow for larger selections.
Durable background jobs
Keep the source and target explicit. A write can trigger automation in the connected system.
Visible outcomes
Check the outcome and external record ID. Uncertain writes need source-side verification before retrying.
How it works
- 1
Review
Select the connection.
- 2
Approve
Review the record or batch.
- 3
Deliver
Approve the intended update.
- 4
Inspect
Follow the operation to its outcome.
Example: Real-Time Publishing
A user confirms a new customer draft and submits it to SAP. A larger cleansing job runs separately in the background, with its own progress and results.
“Real-time publishing” describes direct submission, not a guaranteed delivery time. Bulk and scheduled routes have different timing.
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.