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.

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.

WebSphere Commerce -Member Subsystem

WebSphere Commerce Member Subsystem:
Business logic in the Member subsystem provides member registration and profile management services
Member Subsytem: A top view

User Registration Flow:

User type :

• S(Site administrator )
• A(Administrator)
• G(Guest user)
• R(Registered User)

Table:

• USERS,USERREG,USERREPROF,USERDEMO,
• BUSPROF
• MEMBER,MBRATTR,MBRATTRVAL
• MBRREL
• MBRROLE
• MBRGRP,MBRGRPTYPE,MBRGRPMBR,MBRGRPUSG
• ORGENTITY
• ADDRESS

Commands:
UserRegistrationAddCmd

• PreUserRegistrationAddCmd
• Update USERS.REGISTERTYPE='R' from 'G'
• Create new record in USERREG
• Create new records in USERPROF,BUSPROF,USERDEMO
• Create new record in ADDRESS with unique nickname
• AuthenticationPolicyCmd
• ProcessPaymentMemberCmd
• ProcessPolicyTypeCmd
• AuditUserRegistrationCmd
• UserRegistrationRoleAssignCmd
• PostUserRegistrationAddCmd

AddressAdd

• Address type-S, B, SB(i.e.Shipping=S, Business=B, Shipping & Business=SB)
• isPrimary -0,1
• Address Status : P(permanent),T(Temporary)
• Unique nickname
• AddressBook

AddressDelete: status = T (from P)
AddressCheck:Check user has atleast one P address
AddressUpdate : Nick name cannot be updated

Important Commands & DataBeans present in Catalog Subsystem

Commands--
StoreCatalogDisplayCmdImpl-
This command sets the view task that will display the Catalogs available to browse in the current Store.

TopCategoriesDisplayImpl-
This command sets the view task that will display the root Categories in a specified Catalog.

CategoryDisplayCmdImpl-
retrieves the configured display page for the specified category in the specified catalog.

ErrorMissingAttributeCmd-
This error task command is set when a Product to Item resolution fails due to missing product attributes.

ErrorProductAttributeCmd-
This error task command is set when a Product to Item resolution fails due to incorrect product attributes

ProductDisplayCmdImpl-
This command retrieves the configured Display Page for the specified CatalogEntry which will in turn be launched in order to
display information about the CatalogEntry.This command first ensures that the CatalogEntry specified by the
ProductId can be displayed in the current store, if published, and is not marked for delete.

ResolveSkuCmd-Certain catalog entries may need further processing before being added to an order.
An example is resolving a product into an item through SKU resolution, performed by the ResolveSkuCmd task command.


DataBeans--
StoreDataBean--extends StoreAccessBean ->salesCatalogs()
CatalogDataBean-extends CachedCatalogAccessBean ->getTopCategories()
CategoryDataBean-extends CachedCatalogAccessBean ->getSubCategories()
CatalogEntryDataBean-extends CachedCatalogEntryAccessBean
ProductDataBean-extends CachedProductAccessBean

Important Tables & URLS present in Catalog Subsystem

Tables
STORECAT -store to catalog
CATTOGRP -catalog to group
CATGRPREL -group to group
CATGPENREL -group to parent
CATENTREL -group to praent
CATENTREL -parent to item

URLS---
StoreCatalogDisplay
TopCategoriesDisplay
CategoryDisplay
ProductDisplay

Detailed Description of Catalog Subsystem

CatalogSubsystem

The catalog subsystem is a component of theWebSphere Commerce Server that provides online catalog navigation,partitioning, categorization, and associations. The catalog subsystem containsall logic and data relevant to an online catalog, including catalog groups (orcategories), catalog entries, and any associations or relationships among them.

Catalogentries classification:

· Products.

· Items.

· Packages.

· Bundles.

· Dynamic or static kit.

PRODUCT and ITEM:
An item is a tangible unit of merchandise that has a specific name, partnumber, and price. For example, a 15 inch hammer with a wooden handle (partnumber 15) is an item.
A product, however, is a group of items that exhibit the same attributes.For example, a hammer is a product, while the 15 inch hammer with a woodenhandle is an item. The attributes of this product are "handle type"and "size," which are defined by the corresponding attribute values, wooden and 15 inch.
To distinguish products and items, keep in mind that a product cannot bepurchased, while an item can potentially be purchased.

PACKAGEand BUNDLE:

Packages and bundlesare groupings of catalog entries used for promotional purposes.

A bundle is acollection of catalog entries that allow customers to buy multiple items withone click. A bundle can be agrouping of items, or a combination of products, items, and fully resolvedpackages. The bundle is decomposed into separate orderableSKUs that are added individually to the shopping cart.

Unlike bundles, apackage is an atomic collection of catalog entries. Viewed in similar ways as aproduct, you cannot decompose ormodify a package during navigation or after the package has been placed in theshopping cart. For example, a computer package might contain a specific centralprocessing unit, monitor, and hard drive that cannot be sold separately.

Dynamic kit and Static kit

A dynamic kit is a typeof catalog entry which can be dynamically configured by the customer.
This configuration (or grouping) of products is based on the customer'srequirements and is sold as a single unit.

A static kit is a groupof products that are ordered as a unit. The information about the productscontained in a static kit is predefined and controlled within WebSphereCommerce.

Types of SUBSYSTEMS IN WCS.

Types of SUBSYSTEMS IN WCS.

• Catalog Subsystem.

• Order Subsystem.

• Trading Subsystem.

• Merchandising Subsystem.

• Marketing Subsystem.

• Member Subsystem.

• Payment Subsystem.