Purpose: Use this screen to indicate whether the order edit and accept runs in synchronous or asynchronous sequence for orders received through the Generic Order Interface (Order API).
Yes/No field: Select this field to run the order edit and accept in asynchronous sequence, or in parallel with the remaining order processing, for orders received through the Generic Order Interface (Order API).
Note: If the web site is expecting only an order acknowledgement from OROMS on the final submit of an order with payment, select this system control value in order to receive the response faster.
Why use asynchronous order edit? Use the asynchronous order edit to improve the performance of processing orders received through the Generic Order Interface (Order API). When the system reaches the step to perform the order edit, the system runs the order edit in a separate thread so that the remaining order processing can happen at the same time.
The same order processing occurs as when you run the order edit in synchronous, or interactive, sequence; however if the order is received with payment, the system continues with order processing and will generate the response message before the order edit completes. The order will remain in an error status and the order ship-to in a suspended status until the order finishes processing through the asynchronous order edit.
Leave this field unselected to run the order edit in synchronous, or interactive, sequence for orders received through the Generic Order Interface (Order API).
Note: If you are doing a lot of end of order promotions through OROMS and the web site integration is waiting for a response to provide final totals and other end of order updates, unselect this system control value.
For more information: See Order API Processing Overview for the steps the system performs when processing an order received through the Generic Order interface (Order API).
