Showing posts with label Order subsystem. Show all posts
Showing posts with label Order subsystem. Show all posts

Sunday, 2 September 2012

Commands Present in Order Subsystem.

Some of the commands related to Order Sub-system are:
· com.ibm.commerce.order.commands.OrderDeleteCmd
· com.ibm.commerce.order.commands.OrderCancelCmd
· com.ibm.commerce.order.commands.OrderProfileUpdateCmd
· com.ibm.commerce.order.commands.OrderUnlockCmd
· com.ibm.commerce.order.commands.OrderScheduleCmd
· com.ibm.commerce.order.commands.ScheduledOrderCancelCmd
· com.ibm.commerce.order.commands.ScheduledOrderProcessCmd
· com.ibm.commerce.order.commands.OrderItemAddCmd
· com.ibm.commerce.order.commands.OrderItemDeleteCmd
· com.ibm.commerce.order.commands.OrderItemUpdateCmd
· com.ibm.commerce.order.commands.PayResetPMCmd
The tables in Order Sub-system are:
1. Orders
2. OrderMGP: Relation between Order & Member.
3. OrderItem
4. ORDITEMCONF: Relation between order items & order item shipment confirmation.
5. Ffmcenter
6. ORDUSERS: Contains information about users that worked with an order.
7. OrdTax: Represents the total tax for all order items in an order.
a. ORDSTAT: Contains information about the status of an Order Status Update inbound message.
b. ORDISTAT: This table contains information about the items within a single order for an Order Status Update inbound message.
8. SCHORDERS: Contains the entries for scheduled orders.
a. SUBORDERS: Contains subtotals of amounts for all the OrderItems of an Order with the same shipping address.
b. ORDPAYINFO: Holds a name-value pair representing payment information for a particular Order.
c. ORDPAYMTHD: The Order Payment Method table contains order payment or refund methods selected for an order.

Friday, 31 August 2012

Details About Order SubSystem.

ORDER SUBSYSTEM
  • Order Sub-system is a component of WCS that provides shopping carts, order capture, order fulfillment, inventory & payment function support.
  • An order includes one or more products, billing & shipping addresses, payment details & the total cost including shipping charges & taxes.
  • From a customer persective an order is a list of selected products.
  • Each product in a list is called an order item.
  • From a store perspective an order is a list of order items.
  • Orders are associated with a single store.
  • An order profile is a special type of order that can be associated with either a store or a store group.
  • The order profile holds default information about a customer such as payment information, shipping address, shipping mode & billing address.
Ø There are 4 inventory systems, they are:
1. ATP inventory.
2. Non-ATP inventory.
3. No inventory.
4. External inventory.
ATP Inventory: The ATP inventory model enables you to allocate stock from existing inventory or backorder from expected inventory. You can also obtain an estimated availability time for each order item once it has been added into the shopping cart. The ATP also supports allocating stocks for future order processing.
Non-ATP Inventory: The non-ATP inventory model supports inventory operations that are only based on existing on-hand inventory.
No Inventory: The no inventory model assumes that all products have infinite quantities. When the products in a store are virtual products, digital downloadable products, or electronic assets, such as downloadable images or music.
External Inventory: External inventory is used for Websphere Commerce and some external inventory systems integration. For integration with other inventory systems, you might select ATP, non-ATP, or No-inventory inventory system based on the specific inventory system and integration scenario.
The shipping codes for an order sub-system are:
  • A - Payment Authorization requires review.
  • B - Backordered.
  • C - Payment Authorization complete.
  • D - Deposited.
  • E - CSR Edit.
  • F - Ready for remote fulfillment.
  • G - Pending remote fulfillment.
  • H - Error in remote fulfillment.
  • I - Submitted.
  • J - Trashcan.
  • L - No inventory.
  • M - Either a part or total amount is approved.
  • N - Approval denied.
  • P - Pending Order.
  • Q - Quick order profile.
  • R - Released.
  • S - Shipped.
  • T - Temparory.
  • W - Pending approval.
  • X - Cancelled.
  • Y - Private requisition list.
  • Z – Sharable requisition list.

Order Flow Process For Consumer Direct Store

Consumer Direct Order flow Process:


Place an order. A customer or an administrator who has the authority to act on behalf of the customer places an order with the store. Placing an order involves browsing the online catalog, selecting one or more products for the order, and providing billing, shipping, and offline payment information. Once the customer or administrator completes the order checkout, the order moves from P state (pending with products in the shopping cart) to M state (pending payment approval).
Approve payment for the order. Once the order has been placed, the next step is to approve payment for the order, using WebSphere Commerce Payments. Offline payments are automatically approved and the order moves from M state (pending payment approval) to C state (approved and ready to be released to fulfillment).
Release the order to fulfillment.
Create a pick batch for all orders released to the specified fulfillment center. Pick batches must be created for all fulfillment centers, including the channel store. Once you receive the products from the channel store, you can then pick and pack them for delivery to customers. All releases for the selected fulfillment center are placed in one batch; pick slips are created for each pick batch and packing slips are generated for the releases.
View and print pick ticket.
View and print packaging slip.
Pick and pack products specified in the pick ticket and packaging slip. Products specified in the pick ticket are then manually picked from the fulfillment center, and products are packed according to the instructions in the packing slips.
Create package.
Ship goods. Ship the order to the customer.
Confirm shipment has been sent.
Confirm Shipment. Once you have verified the shipment on the system, the status of the order changes to Shipped.
Note:
1. Pick Ticket: A printed document containing a list of all the products required to fulfill the releases in a given pick batch.
2. Pick Batch: A group of releases that are managed as a unit in a fulfillment center.
3. Fulfillment Center: Serves as a storage warehouse where products are packed & shipped to customers.

Solr settings and full indexing (Attribute task update)

SOLR is mainly used for : Indexing Querying    SOLR is a product of apache and having the inbuilt server named jeety. Mainly the ...