Upsert (SAP IS Adapter)

This operation allows users to create new records or update records by batches.

1. Configure the exchange property in Content Modifier:

   • access-token – The token can be retrieved from the global variable set by a separate token store integration flow. See https://pricefx.atlassian.net/wiki/spaces/ACCDEV/pages/3621650736.
     
     

   Open

   

    

2. Configure the message body in Content Modifier. It is an array of all the records to be upserted.

   The maximum number of records to be upserted is 500. The full JSON schema can be found in the “Sample Artifacts for SAP S/4HANA Integration with Pricefx” integration package from SAP API Business Hub. See https://pricefx.atlassian.net/wiki/spaces/ACC/pages/5013871236.
   
   

   Open

   

   
   Sample upsert message:

   [ { "customerId": "CUSTOMERSAP1", "name": "CUSTOMERSAP1", "attribute1": 1, "attribute3": "xxx" }, { "customerId": "CUSTOMERSAP2", "name": "CUSTOMERSAP2", "attribute1": 2, "attribute3": "xxx" } ]

    

3. In the Adapter configuration, select operation and target type.

    

4. For Product Extensions and Customer Extensions, specify the name of the table as well.

5. For Price Parameters, specify the name of the table and Target Date as well.

6. You can set up following options as well. By default:

   1. Full records are returned unless “Return only number of processed records” is selected.

   2. System fields (such as typedId, version) which are not available in the standard schema are not returned unless “Show systems fields” is selected.

   3. Null is stored in the key field unless “Replace Null key with Empty String” is selected.

Response Message

The full records are returned if “Return only number of processed records” is not selected, otherwise the number of records updated is returned.

The full JSON schema can be found in the “Sample Artifacts for SAP S/4HANA Integration with Pricefx” integration package from SAP API Business Hub. See https://pricefx.atlassian.net/wiki/spaces/ACC/pages/5013871236.