Integration managers
Integration monitoring and recovery
Investigate blocked handovers without creating duplicate bookings.
What to do
- Open the integration workspace and locate the affected submission. Read its current state, separate document confirmations and assigned responsibility.
- Use the available assignment action to make ownership clear. Record the reason when the workflow requests one.
- Check whether the result is a confirmed failure or an uncertain external outcome. Those cases need different recovery decisions.
- Use only the recovery action permitted for the current state. A lost response requires reconciliation of the existing business reference before deciding whether another send is safe.
- Review the resulting history and status. Escalate missing mappings, source conflicts or unresolved external confirmations to the responsible integration operator.
Before you continue
Simulator results are labelled test behavior and do not represent SAP documents.
The selected ERP edition, API contract and mapping determine live capabilities. Do not assume an unsupported ERP endpoint exists.
Questions and troubleshooting
Why is an old import rejected?
An older source timestamp or conflicting accepted data can block overwrite. Review provenance and create a new accurate preview rather than altering timestamps to force acceptance.
Can an ordinary administrator retry ERP jobs?
Only an identity with the required integration permission can use the relevant action. Organization administration does not automatically grant operational permissions.