cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BTP Integration Suite_Service Contract screen IF error message

ISoma
Participant
0 Likes
451

Hi Expert!

Service Contract information is linked to other peripheral systems using BTP Integration Suite.
When a Service Contract is created, BTP will be launched and data will be converted and integrated.

Requirements
When you press the "Save" button on the S/4HANA Cloud Service Contract, it is expected that IF integration will begin.
If an error occurs during IF integration, is it possible to display something like an error message on the Service Contract screen?

ISoma_0-1744283442408.png

Soma

Accepted Solutions (0)

Answers (2)

Answers (2)

Chuma
Active Contributor
0 Likes

Hello @ISoma 

Thank you for your question regarding displaying integration errors on the Service Contract screen when using SAP BTP Integration Suite.

In SAP S/4HANA Public Cloud Edition, the Service Contract Save action and the BTP integration are technically decoupled. This means you cannot block the Save or display a synchronous error message in the UI if the integration fails; the integration flow runs asynchronously after the document is saved.

In fact, there are supported ways to provide clear and immediate feedback to users:

Recommended Possible Solution

Integration Status on the Contract (preferred solution)

    • Add two custom header fields: 'Service Contract Integration Status' and 'Integration Error Text
    • Your iFlow updates these fields via the Service Contract OData API:
      • On success → set status to Success.
      • On error → set status to Error and write a short error message.
    • Users can see the result directly on the Service Contract they just saved.

In-app Notification (optional solution)

    • Use Situation Handling – Extended to raise a banner or notification when the Integration Status = Error.
    • This gives the user a proactive alert in the contract screen.

Output-based Feedback (if applicable)

    • If your iFlow is activated through Output Management, the Service Contract header displays the Output Log and Status directly.

Monitoring & Support

    •  Ensure your support users have access to Message Monitoring in both S/4HANA Cloud and BTP Integration Suite.
    • ◦ Using the Service Contract number as a correlation key will assist in tracing failed messages more efficiently.

Why is this approach necessary?

In an S4 HANA Public Cloud environment, integration calls are inherently asynchronous. This design ensures system resilience and avoids blocking the process of saving business documents. The preferred method is to communicate the integration results back through the Service Contract or in-app notifications, rather than attempting to halt the save process error.

Next Steps to follow
It is recommended adding the Integration Status fields to the Service Contract and enhancing your iFlow to update these fields automatically on success or error. This allows your end-users to quickly see whether the integration was successful or failed, right on the Service Contract screen. Let us know if you need example field definitions, an API PATCH sample, or a setup guide for the Situation Handling alert.

Let me know if you need further support

With regards

Chuma

DequanXu
Product and Topic Expert
Product and Topic Expert
0 Likes

Hello,

To implement a scenario where pressing the ‘Save’ button Use SAP BTP Integration Suite to Integrate S4/HANA… on an S/4HANA Cloud Service Contract initiates integration with SAP BTP Integration Suite, the following steps can be taken:

  1. Trigger Integration Flow: You can configure the SAP S/4HANA Cloud system to trigger an integration flow upon saving the Service Contract. This is typically done using communication arrangements that link specific actions in S/4HANA with integration flows on the SAP BTP Integration Suite.

  2. Handling Errors: To display error messages on the Service Contract screen when an error occurs during integration, the integration flow can be designed to send back response messages. Changes can be made in the integration flow to capture errors and relay them back to the S/4HANA Cloud system.

  3. Display Error Messages: SAP S/4HANA can be configured to listen for these error responses. Custom logic can be implemented in the UI—possibly extending the Service Contract application—to check for these responses and display appropriate error messages.

  4. Implement BTP Error Handling: On the BTP Integration Suite side, ensure that the integration flow has proper error handling in place. Use features such as error end events, throw alerts or messages, or write error logs that can be sent back to the originating system.

Best regards,

Dequan Xu