Moving an order through M, C, R, S and D states
Aleksander Kovač 270004M7HS Visits (6952)
This text gives an overview of moving an order through M, C, R, S and D states (or statuses) for WebSphere Commerce 7.
During the development or testing, knowing how the order transitions through various states can be very useful. The procedure is not that straight forward, so I am giving the reader an idea about what is required to move an order through the main steps in the order process flow. It will also enable him or her to look for related materials in the WebS
Picture 1: Order status transition flow diagram
Some states can be achieved only through a scheduled job, while others can also be achieved using the WebSphere Commerce Accelerator tool.
Transition from state B to M
Managed by the Proc
Transition from state M to C to R
Transition from state M to state C is conditioned by the payment status, which has to be authorized: EDPPAYHIST table must contain ApproveAndDeposit (or Approve) value in the OPERATIONNAME column, and PPCPAYMENT must have APPROVEDAMOUNT set. The command which transitions the order from state M to C is the Orde
To facilitate development and avoid the need to schedule the Orde
Change the paymentActionRule from “Early Approval” to “Early Deposit”:
Then restart the server. More about payment rules in the Information Center: Paym
The next step is to schedule the Rele
Transition from state R to S
This step requires a pick batch, a release package, and release shipment confirmation. I found it more convenient to use the Accelerator tool for testing:
Transition from state S to D
Managed by the OrderCloseCmd command, which must be scheduled on the store level (or on the site level with storeId=xyz parameter set). The order can be closed only if the payment for the order is deposited; the EDPPAYHIST table must contain ApproveAndDeposit (or Deposit) value in the OPERATIONNAME column, and PPCPAYMENT must have DEPOSITEDAMAOUNT set. This state can be easily achieved by using the Early Deposit payment rule.
I have complied a list of tables which may come handy when dealing with the order process flow:
ORDERS, BUSEVENT, EDPPAYHIST, SCHCONFIG, SCHSTATUS, PPCPAYMENT, ORDERITEMS, ORDRELEASE, FFMCENTER, PICKBATCH, CMDREG, STOREENT
The following resources are useful when debugging the scheduler:
SELECT SCCPATHINFO, SCSSTATE, SCSACTLSTART, SCSEND, SCCINTERVAL FROM SCHCONFIG, SCHSTATUS
Thanks to Mojca Spazzapan and Fredrik Isaksson for help and useful comments.