Scenario - Sales order entry (inbound)
In this scenario, the customer needs to create sales orders that are coming from external system(s), such as Salesforce, B2B web shop, or Amazon.
The sales orders are for the following items:
- Up to 20k sales lines each hour in high season from B2B web shops
- 500 sales lines each hour during peak hours from Salesforce
Patterns
Consider the following patterns (best practices):
Low volume - Use OData to create sales orders with lower volume. The benefit to this approach is simpler error handling and multisystem transactional (NOUN).
High volume – Use batched integration through Data Management API or through custom services.
Further information
For OData, timeouts and parallelism of processing is up to the sender.
Anti-patterns
Consider the following anti-patterns (pitfalls):
- Create a complex entity through an OData batch for high-volume, inbound sales orders.
- Provide expensive, subsequent logic on the entity (for example, intercompany or Available to Promise (ATP) / Capable to Promise (CTP) checks).