Breadcrumbs

Purchasing Conditions

Price management can be further extended to support purchasing conditions. This can be achieved by configuring the integration flows similarly to sales price conditions. A multicast process can be added if both purchasing and sales condition records are required.

Multicast updated Pricefx condition record table to create purchasing and sales price conditions in SAP S4HANA

This integration flow built different requests message to the JMS queue which triggers the get sales condition records and get purchasing condition records integration flows.

Screenshot 2025-08-21 at 1.52.13 pm.png

Below parameters can be configured but default values are provided:

  1. Sender – The process direct incoming path of this integration flow.

  2. Error receiver – The error handling integration flow.

  3. Get Conditions receiver - The integration flow which publishes the get condition requests to JMS queue

  4. Transaction handling

  5. Message header properties

  6. Condition record set, source ID xpaths.

Consume fetch condition record requests from JMS

The request message is sent to either get purchasing or sales condition record process.

Screenshot 2025-08-21 at 2.04.55 pm.png

Below parameters can be configured but default values are provided:

  1. The incoming JMS queue

  2. Error receiver – The error handling integration flow.

  3. Get purchasing and sales condition record receivers

  4. Transaction handling

  5. Message header properties

Get purchasing price condition records from Pricefx

This integration flow is triggered from a JMS queue. It fetches one batch of condition records from condition record set. It gets any metadata required for the integration from the value mapping. This value mapping is configured per condition record set table. Once the first batch of records are fetched, they will be set to integration status = 1 (or any numeric value you defined in the mapping) to indicate the records are being processed and would not be fetched again in next call. These records are then sent to the next process to create price conditions in SAP S/4HANA. The process would be repeated by putting the message into the JMS queue again until no more records can be fetched from the condition record set.

Screenshot 2025-08-21 at 10.18.41 am.png

Below parameters can be configured but default values are provided:

  1. Sender – The process direct incoming path of this integration flow.

  2. Create condition receiver - The integration flow which creates the price conditions in S/4HANA

  3. Republish receiver - The integration flow which publishes the message to a JMS queue again for next batch

  4. Fetch condition records receiver – The integration flow which fetches the records from Pricefx

  5. Update condition status receiver - The integration flow which updates the condition status.

  6. JSON array XML receivers - The integration flows which convert JSON array to/from XML

  7. Error receiver – The error handling integration flow.

  8. Transaction handling

  9. Fetch records request message

  10. Value mappings keys

  11. Page size

  12. Splitter properties

  13. Message header properties

Consume condition record create requests from JMS

The request message is sent to both create purchasing or sales condition record processes.

Screenshot 2025-08-21 at 2.04.13 pm.png

Below parameters can be configured but default values are provided:

  1. The incoming JMS queue

  2. Error receiver – The error handling integration flow.

  3. Create purchasing and sales condition record receivers

  4. Transaction handling

  5. Message header properties

Create purchasing price condition records in SAP S4HANA

This integration flow creates purchasing price conditions in SAP S/4HANA by OData API. The results are written back to Pricefx condition records.

Screenshot 2025-08-21 at 12.23.44 pm.png

Below parameters can be configured but default values are provided:

  1. Sender – The process direct incoming path of this integration flow.

  2. SAP Connection properties receiver - The integration flow which retrieves SAP connection properties from value mapping

  3. Error receiver – The error handling integration flow.

  4. PFX receiver - The integration flow which writes the records to Pricefx

  5. SAP result receiver - The integration flow which extracts SAP results from the response

  6. PFX result update receiver - The integration flow which writes the results back to Pricefx

  7. OData properties

  8. Transaction handling

  9. Message header properties

  10. Connection properties xpath

  11. Names of all available SAP tokens