The latest release of IBM® App Connect supports update and delete actions for SAP (via OData).
Unlike the “update or create” action, the update action updates a record without the option to create one. This is helpful in cases where you need to update records without creating them. This action results in a “record not found” exception when it tries to update a record with an ID that doesn’t exist.
Connecting to your SAP OData service
Before you use App Connect with SAP (via OData), make sure that you can connect to the SAP OData service from App Connect. You can connect App Connect to your SAP OData account by providing a set of connection details on the Catalog page:
To connect to SAP(via OData), you need to create a private network because the OData server is behind a firewall. When you click Create a new network, you’ll see a set of instructions to create a private network. When you’ve followed the instructions, and you’ve connected to your SAP OData service, you can discover the supported objects and actions by clicking Show more.
There are multiple use cases for integrating the SAP OData service with other applications and utilities in the App Connect catalog. In this article, we’re going to show how when a Salesforce contact is created, we retrieve travel agencies from SAP (via OData), then check whether a matching travel agency record exists. If it exists, we’ll update the record by using the new update action. If the record doesn’t exist, we’ll use a separate action to create a travel agency.
Note: We’re using a “TravelAgencies” object in this use case but objects might vary based on the SAP service that we connect to. The objects and operations supported are as defined in the OData service that we provide while creating the SAP OData account.
We’d love to hear from you. Why not share some of your use cases with us or send us any other comments?