Hello SAPiens,
With new Cloud Integration – Trading Partner Management V2 version 2.3.7 SAP has released a new B2B monitor feature of Restart/Retry Interchanges
Understanding a feature:-
The B2B Monitor has a manual restart/retry function exclusively designed for failed interchanges, allowing you to re-process failed messages. The Actions button is enabled when you select the interchanges and it consists of two options: Restart and Retry. These options appear only for interchanges with the status Failed.
Restart: This option resets the sender payload to integration flow Step 1b – Write Message to Message queue, thereby re-initiating the messaging process from the beginning. As a result, the message mapping is re-executed, making room for corrections or adjustments to be made. Restart is ideal for addressing errors related to message transformation or formatting.
Retry: Retry resets the receiver payload to Step 3 – Receiver Communication Flow V2, bypassing the message mapping step. This option is suited for resolving errors related to receiver-side processing or temporary connectivity issues, where the original message mapping remains valid.
Prerequisites
1. Deploy Iflow – Step 1 – Sender Communication Flow V2 – Internal
2. Copy deployed endpoint URL from Integrations Content
3. Create BTP – Destination
Name – B2BTPM_Reprocess_Endpoint
URL – <host:port>/http/tpm/internal/repost_endpoint
Ignore HTTP 500 error of test connection check.
Procedure
Login to CPI –> Navigate to B2B Monitor –> Select failed message –> Actions –> Restart / Retry
#HappyLearning
Regards,
RJ
Hello SAPiens,With new Cloud Integration – Trading Partner Management V2 version 2.3.7 SAP has released a new B2B monitor feature of Restart/Retry InterchangesUnderstanding a feature:- The B2B Monitor has a manual restart/retry function exclusively designed for failed interchanges, allowing you to re-process failed messages. The Actions button is enabled when you select the interchanges and it consists of two options: Restart and Retry. These options appear only for interchanges with the status Failed.Restart: This option resets the sender payload to integration flow Step 1b – Write Message to Message queue, thereby re-initiating the messaging process from the beginning. As a result, the message mapping is re-executed, making room for corrections or adjustments to be made. Restart is ideal for addressing errors related to message transformation or formatting.Retry: Retry resets the receiver payload to Step 3 – Receiver Communication Flow V2, bypassing the message mapping step. This option is suited for resolving errors related to receiver-side processing or temporary connectivity issues, where the original message mapping remains valid.Prerequisites1. Deploy Iflow – Step 1 – Sender Communication Flow V2 – Internal2. Copy deployed endpoint URL from Integrations Content 3. Create BTP – Destination Name – B2BTPM_Reprocess_EndpointURL – <host:port>/http/tpm/internal/repost_endpointIgnore HTTP 500 error of test connection check.ProcedureLogin to CPI –> Navigate to B2B Monitor –> Select failed message –> Actions –> Restart / Retry#HappyLearning Regards,RJ Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog