Questions regarding cancellation of an order through the Sterling Call Center and Store (COM) application.

Answer

Q. Is there a way to know, from the input to YFSOrderRepricingUE, if an order is being cancelled?

A. Yes. If the input to YFSOrderRepricingUE has this element <ModificationType ImpactsPricing="Y" Level="ORDER" Name="CANCEL"/> , then the order is being cancelled. However, this input is populated only when the order is being cancelled through the Foundation Console. If the order is cancelled through the Call Center and Store application, then the modification type is populated at the line level.

Q. Why is the modificationType element populated at line level, though an entire order is being cancelled through the Call Center and Store application?

A. The Call Center and Store application's implementation of cancelOrder API is at a line level unlike Foundation's implementation where it is at both line level and order level. So when an entire order is being cancelled through the Call Center application, the modification type is populated at the line level for all the lines that are being cancelled.

Q. Apart from the solution mentioned above, with reference to the Call Center and Store application, is there any other way to identify if an order is being cancelled?

A. Following solutions can be made use to determine from a UE, if the order is being cancelled:

1. The Cancel Order Task has two flags - 'Select all available quantity' and 'Select specific quantity for cancellation'. A transaction object can be set at the Environment variable when the entire order is being cancelled. The value of this transaction object can be retrieved within the UE to find out if the entire order is cancelled. (For more information on setting a transaction object, please refer to the JavaDocs for the YFSEnvironment class.)

2. Create a custom task to call changeOrder API with Action="CANCEL" at the Order level. This will ensure that the modificationType element is populated at header level, in the UE's input. In case the order has shipments, then the custom task should call changeShipment API and changeOrder API in succession. Call to changeShipment should be done to remove the lines from the shipment and the call to changeOrder to cancel the lines on the order.