Integration managers

Integration monitoring and recovery

Investigate blocked handovers without creating duplicate bookings.

What to do

1. Open the integration workspace and locate the affected submission. Read its current state, separate document confirmations and assigned responsibility.
2. Use the available assignment action to make ownership clear. Record the reason when the workflow requests one.
3. Check whether the result is a confirmed failure or an uncertain external outcome. Those cases need different recovery decisions.
4. 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.
5. Review the resulting history and status. Escalate missing mappings, source conflicts or unresolved external confirmations to the responsible integration operator.
6. In Integration Center, prepare a company-specific SAP profile for S/4HANA Public, Private/on-premise, Business One or ECC. Select the family explicitly and record non-secret release, process, API contract and test-system references; confirm proposed field mappings, tax responsibility, reference lookup and separate material/invoice results with the customer. Save a revision and run the synthetic local check. Prepared or locally tested never means customer validated or enabled. No connection, credentials, transmission or invoice is created. Changing the profile requires a fresh local check; existing transfer history and pending-confirmation protection remain separate.
7. Open SAP read connection in the Integration Center. Enter the HTTPS origin and a reference issued by your secure credential store; never enter credentials here. Check the connection, compare the observed metadata fingerprint with your SAP API contract, save the confirmed fingerprint and check again. Only fresh customer read evidence can enable this read operation. Synthetic evidence cannot enable it; billing and material writes stay disabled. Credential rotation, profile or mapping changes require saving and checking again. Disable the read operation when access should stop.
8. Open Secure SAP credentials after your administrator has provisioned the encrypted store and approved HTTPS portal. Enter OAuth client credentials and token origin/path, or the Business One company database and service user/password for the selected profile. Saving returns only a reference. Select an existing reference to replace credentials, or revoke it to stop access. Fields are cleared after saving; secrets cannot be read back. Refresh references after an uncertain response before changing the action. Save the current reference in the read connection and repeat its check. Missing store or keys keep access closed; this does not activate billing or material writes.

Before you continue

Questions and troubleshooting