Order Status Transition flow diagram in IBM WCS

Order Status Transition flow diagram

The Order status transition flow diagrams section provides order process flow diagrams for different store configurations and shopping flows. The Order status transition flow diagram page provides and overall view of the Commerce order states; it also lists the commands which govern the transitions between those states:

Transition from state B to M

Managed by the ProcessBackordersCmd command, which should be scheduled on the store level.

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 OrderPaymentSynchronizeCmd command, which must be scheduled on store level - see Scheduling the processing of pending payments page for more information: Scheduling the processing of pending payments

To facilitate development and avoid the need to schedule the OrderPaymentSynchronizeCmd command, the payment rule can be changed to Early Deposit; together with using the BillMeLater or PayLater payment methods we can configure the development environment for straightforward testing. To change the payment rule, modify the PaymentMappings XML file:

Location: WC_eardir/xml/config/payments/edp/groups/default

Change the paymentActionRule from “Early Approval” to “Early Deposit”:

<Mapping paymentActionRule="Early Deposit"

paymentConfiguration="BillMeLaterOffline" paymentMethod="BillMeLater"/>

<Mapping paymentActionRule="Early Deposit"

paymentConfiguration="BillMeLaterOffline" paymentMethod="PayLater"/>

Then restart the server. More about payment rules in the Information Center: Payment rules provided in WebSphere Commerce

The next step is to schedule the ReleaseToFullfilmentCmd command on the store level to transition the order from state C to R or, with the Early Deposit payment rule, from state M to R.

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:

Pick batch: Select a store and fulfillment center, then open Operations->Pick batches. All R state orders will be added to this pick batch.

Using the same store and fulfillment center, create a package for an order via Operations->Find releases ready to ship

Once a package was created, confirm the release as shipped using the “Find releases ready to ship” screen

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.

Tables which may come handy when dealing with the order process flow:

ORDERS, BUSEVENT, EDPPAYHIST, SCHCONFIG, SCHSTATUS, PPCPAYMENT, ORDERITEMS, ORDRELEASE, FFMCENTER, PICKBATCH, CMDREG, STOREENT



Refrence : an overview of moving an order through states