B2B monitoring and operations

A partner is only live when someone can see its traffic, explain a failure and fix it without a developer. Integration Suite gives B2B scenarios their own monitor on top of the normal message processing log, and it is the screen Contoso's support desk will live in after the move.

The B2B monitor

Go to Monitor > B2B Scenarios. Two tiles open, both showing the last 24 hours by default: Interchanges, for interchanges that were assigned to a partner or transaction, and Unassigned Interchanges, for interchanges where an error during metadata extraction meant no business document could be attached. Interchanges are kept for 90 days.

In the Interchanges list you filter by status, processing status, creation time, error category, sender, receiver, direction, relation type and custom search attributes. Selecting an interchange shows its header (status, processing status, and where they apply the sender technical acknowledgment status, sender functional acknowledgment status and receiver functional acknowledgment status), its general data including the agreement and Usage Indicator (Test or Production), the sender and receiver AS2 message IDs, an events section and the payloads.

Each event has a Monitoring Reference link that opens the message processing log of that integration flow run, so you can move from business view to technical detail in one click. Failed interchanges also show an Error Information section and a Check Agreements button.

Statuses and error categories

Interchange statuses are Failed, Retry, Processing, Completed, Waiting for Acknowledgment, Acknowledgment Overdue and Canceled. Failed and unassigned interchanges carry an error category: Initial Decryption Failed, Signature Validation Failed, Agreement Configuration Access Failed, Interchange Validation Failed, Interchange Mapping Failed, Interchange Transmission Failed, Acknowledgment Overdue, or Unspecified Error. The category is the first clue in any triage.

Restart, retry, duplicate and cancel

Select interchanges and open Actions. Restart works on Failed interchanges and resets the sender payload to Step 1b, so mapping runs again: use it after you correct a mapping or agreement. Retry also works on Failed interchanges but resets the receiver payload to Step 3, bypassing mapping: use it when the receiver was down. Duplicate and Retry works only on Completed interchanges and processes a copy as a new interchange while the original keeps its status. Each action asks for a reason, can't be reversed and keeps the original interchange ID with new events appended. These actions need generic flow version 2.3.7 or later and a BTP destination named B2BTPM_Reprocess_Endpoint. Cancel is permanent and is available for Failed, Retry, Processing, Waiting for Acknowledgment and Acknowledgment Overdue interchanges.

Alerts in SAP Cloud ALM and the operations hand-off

TPM can publish interchange data to SAP Cloud ALM for statistics and alerting by partner or message type. SAP notes that after enabling data collection it can take up to 12 hours before publishing starts, the first publication covers only the latest hour, and each new interchange takes about 5 minutes to sync. To show business document numbers in Cloud ALM, define a custom search attribute named Document ID in the Configuration Manager and assign it to the agreement activity; for the IDoc receiver adapter SAP suggests the source type Parameter with the value SAP_TPM_IDocNumber.

Contoso's hand-off from Theo's team to the support desk is a short runbook per partner: the agreement name, the partner contacts, the expected daily volume, the cut-off times, how to tell a test interchange from a production one, the error-category table above, and who may cancel. The support desk gets the business expert role in production; developers keep design rights only in the development tenant (CMC_DEV).