General assumptions and limitations
Following are the assumptions and limitations that apply to this integration.
Assumptions:
- This integration process assumes that both WebSphere Commerce and Sterling Order Management have already been installed.
- Some data base field lengths may differ between WebSphere Commerce and Sterling Order Management. When this occurs, the minimum data field lengths of Sterling Order Management are supported. For more information, refer to the Sterling Order Management Entity Relationship Diagrams (ERDs.)
- Customers are not mapped and are assumed to exist in WebSphere Commerce only.
- Items must be created in both systems.
- Integration is supported for only one distribution group or the default distribution group. Node Level Inventory monitoring is not supported.
- The following table shows how items are mapped between systems:
WebSphere Commerce Name Sterling Order Management Name Product Item Prebuilt kit Physical kit Static kit Bundle Bundle N/A
Limitations:
- getItemPrice API will return only pricing related information. Adjustments related to any promotions will not be returned.
- The following input parameters in getOrderPrice will not be honored:
- RunCatalogOnlyRules
- SuggestManualRuleAdjustments
- SuppressRuleExecution
- SuppressShipping
- EligibleForShippingDiscount
- ListPrice will not be available in the output.
- Integration for Shipping Charges and Tax calculation is not provided in this release.