Processing Records into SAP
What processing does in SAP, processing now or later, immediate and background runs, pausing and stopping, reading results, retrying, unknown outcomes and undoing.
Draft brief for authors. Section page.
Source in the product repository: .claude/rules/mass-processing.md, docs/mass-processing-architecture.md, .claude/rules/staging-app.md (processing menu), customer guide §5 and §8.
In this section
- Before You Process: What Happens in SAPWhose user posts the change, what SAP records, what costs quota, which records are skipped, and the rules MDM keeps whatever happens.
- Processing Selected or All Not Started RecordsStart a run from Staging Records or Monitor Mass Changes, read the confirmation, and understand the three outcomes: finished at once, started in the background, nothing to process.
- Immediate and Background RunsSmall runs finish while you wait; larger ones run in the background, appear under Background Jobs and can be paused, resumed and stopped.
- Scheduling a Run for LaterSchedule the processing of a Task for a later time when the table runs under the integration user or the background opt-in; stop it under Background Jobs before it starts.
- Following a Background RunWatch a run's progress under Background Jobs and on the Task page, and get notified when it finishes.
- Pausing, Resuming and Stopping a RunWho may pause, resume or stop, what happens to the records in progress, the pause reasons and their next steps, and which runs resume by themselves.
- Reading the ResultsWhere to read what happened to every record: statuses and messages in Staging Records, failed records by error on the Task page, and the entries in Application Logs.
- Retrying Failed RecordsCorrect the values SAP rejected with Mass Edit, then process again; Retry Failed Records sends only the records a machine may send again unchanged, Retry All sends them all.
- Records with an Unknown OutcomeSAP did not confirm a change in time, so it may or may not have been applied; MDM never sends such a record again by itself.
- Undoing a Processed ChangeA revert Task puts back the values a processed Task changed, built from the preview's stored values; today through an assistant or the API.
Last updated: