General mapping rules
Each installation of WebSphere Commerce and Sterling Order Management is different. Some assumptions are made about the mapping between the two systems, and these assumptions are reflected in the ValueMaps.xml file, which we can change to suit your particular environment.
Table 1. Mapping assumptions between WebSphere Commerce and Sterling Order Management WebSphere Commerce Sterling Order Management Where item is mapped, if applicable Example Buyable=N Item validation rule on. Effective dates in need to be defined for these items. If Buyable=N, then item does not appear in the WebSphere Commerce storefront and customers are not able to add it to cart. To control whether an item is buyable or not, the item must be created in Sterling Order Management and the effective dates must be supplied.
Carrier SCAC ValueMaps.xml file USPS Currency Currency Not mapped. Currency needs to be defined as same code in both systems. USD Customer Not mapped. Assumed to exist in WebSphere Commerce only. DeliveryMethod ValueMaps.xml file Pick, Ship Fulfillment center identifier ShipNode Fulfillment Center name Shipnode identifier Item Part Number Item Id Items Items Must be created in both systems. Level of service Not mapped. Available in Sterling Order Management only. Expedite Online store ID Enterprise Organization Code Online and Physical Store Names Shipnode Identifier Order Id SSFS Order No = WC_+ WC Order IdOrder Item ID Order Line No Payment Method PaymentType ValueMaps.xml file check –> CHECK Visa, MasterCard, etc. --> CREDIT_CARD Line of credit --> CUSTOMER ACCOUNT For others, directly map payment method name to payment type. It should be CUSTOMER_ACCOUNT and all others should be OTHERS. Physical store identifier ShipNode Reservation Id Inventory Reservation Id = WC_+ WC Order NoShipping Mode Code (ShipModeCode) CarrierServiceCode ValueMaps.xml file 2nd day air StoreId > Node ShipNode ValueMaps.xml file Line in valuemap.xml file: <mm:Map name="wcPhysicalShipNodeToscShipNode"> StoreId > Storefront Enterprise ValueMaps.xml file Line in valuemap.xml file: <mm:Entry key="Madisons">scMadisons</mm:Entry> User Not mapped. Assumed to exist in WebSphere Commerce only. User for API call Must configure a common authentication user in both systems. ShipModeStoreId+ShipModeCode+Carrier SCAC+CarrierServiceCode UPS Next day UOM – C62 UnitOfMeasure – EACH ValueMaps.xml file Mapping is based on the Common Attributes Mapping definition in ValueMaps.xml. If not defined, the mapping is:
- C62 in request
- EACH in response.