Mirror of Oracle documentation
Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.
4
Data Conversion
This chapter lists the setup and conversion of data to be done before any messages are sent between solutions. This includes conversion of master data, like stores, warehouses, and items, as well as conversion of any open transactional data and initialization of inventory levels.
Manual Conversion
For a few foundational data elements, it is recommended that you just manually set up the data in WMS Cloud to match what you have in your Merchandising implementation. This includes the configuration of order types and reason codes.
Order Types
The Order type field is used to define the set of transactions that will be mapped to Merchandising, SIOCS, and OROB. These need to be manually set up within WMS Cloud and cannot be pre-configured. One record needs to be created in WMS Cloud for each of the order types that is listed below. This is case sensitive and only these order types are supported in the integration.
Table 4-1 Order Types
| Oracle Retail Transaction | WMS Cloud | |
|---|---|---|
| Order Type | Description | |
| Customer Orders | B2C | Sales Orders |
| Stock Orders and Purchase | B2B | Stock Orders |
| Orders | ||
| RTV Request | RTV | Return to Vendor Request |
The flags for configuration of the order types can be set however works best for your business, with some exceptions described below.
For more information on how to create order types and how these flags are used in WMS Cloud, see the Oracle Warehouse Management Cloud documentation.
Stock Orders
The Partial allocation flag must not be checked when integrating the stock order status for stock allocation or deallocation with Merchandising.
Customer Orders
The Single Order on Multiple Loads must be set to Not Allowed when integrating with OROB, because it can only handle a single tracking number for each fulfillment order.
Customer Orders (Store Pickup)
For B2C orders that don’t need to be directly shipped to the customer but instead will be picked up from the store, USM will send only the destination store ID to WMS Cloud and not the address details of the customer. Also, the Consumer Direct field (set to Y in this case) that is required for SIOCS while processing the message will be present in the ASNOut message for this workflow.
Return to Vendor Request
To support multiple inventory status codes in the stock return request from Merchandising, as well as to send RTV shipment with the inventory from a locked status to Merchandising, the following configurations must be made for an RTV order type:
-
Eligible Lock Code for Allocation - must be set to a comma-delimited list of all lock codes that could have RTVs created against them. In Merchandising, these lock codes are mapped to the inventory status codes within an inventory status. For more details on the lock code and inventory status code mapping, see the “Lock Codes” section below.
-
Wave Flag - this flag must be unchecked. RTV orders will be allocated and picked using the “RF Direct Allocation” or “RF Pick and Allocate” modules in WMS.
-
Allocate during Pick - this flag must be checked to allow allocation when the order is picked for return.
Reason Codes
Reason codes in WMS Cloud are similar to the inventory adjustment reason codes used in Merchandising. If you already have inventory adjustments reasons configured in Merchandising, then these same codes should be setup in WMS Cloud, as appropriate. If you are adding new codes for your WMS Cloud implementation, then you will need to add them in both solutions.
Note
Merchandising requires inventory adjustment reason codes to be numeric and less than or equal to four digits in length.
Additionally, you will need to set up a reason code in WMS Cloud with the ID of RMA , which should be used for customer order returns processing in the warehouse.
Customer Order Returns
For customer order returns processed into the warehouse, WMS Cloud does not update Merchandising directly, as Merchandising is expecting an update through returns processing ( OMS > Sales Audit > Merchandising ). So, the return should be mapped only to OMS from WMS. To prevent the return from flowing through and updating Merchandising, a reason code RMA must be created in WMS. This is what is used in the integration to filter these transactions from updating Merchandising. This reason code must be used when processing inventory adjustments in WMS related to a customer order return. To better support this process, it is recommended that you create a distinct RF screen for customer orders using the Createlpn option and as part of that setup, set RMA as the default reason-code with the mode set to either prompt for reason code OR null .
Note
Customer order returns cannot use Receiving in WMS when integrated with Merchandising.
Receiver Unit Adjustments
If you want receipt adjustments made during pre-verification to be communicated to Merchandising as receipt adjustments, rather than just an inventory adjustment, then you should configure a reason code in WMS Cloud named RUA . This will be a signal to the integration of this adjustment to map it to the Merchandising as a receipt adjustment rather than an inventory adjustment. To better support this process, it is recommended that you create a distinct RF screen for receipt adjustment using the Modifylpn option and, as part of that setup, set RUA as the default reason code with the mode set to either prompt for reason code OR null.
Note
The RUA reason code should only be used for the purpose described above. Usage of that reason code for other adjustments will raise errors since Merchandising requires that reason codes for inventory adjustments be numeric.
Lock Codes
Lock codes in WMS Cloud are similar to inventory status codes in Merchandising. These need to be coordinated between the two solutions in order to properly map locked inventory in WMS to Merchandising. There are two components of this in WMS Cloud and two components of this in Merchandising that should be configured. First, in WMS Cloud, when creating the lock code, you will also configure an ERP bucket that this lock code should map to. This is because in some cases two lock codes can be assigned for an item in WMS Cloud, but in Merchandising it will always only have one unavailable status at a time. You can also define a priority for the lock code. If used, this will determine which is used to update Merchandising in the case that two are added or removed. Both the lock code and ERP bucket values must exist - in Merchandising. See “Appendix Activity Codes” for details on how they are translated in the integration.
Lock Code DM
Description Damaged
Allocatable
Unlock on locate to Reserve
Treat as Attribute
Allow Multiple Lock Codes Generate Adjustments Instead of Lock Code Records Allow Loading Allow Manifesting Prevent Putaway Copy to Transfer Shipment flag Prevent Direct Consume
|’
Inventory attribute transfer code
ERP Bucket TRBL
Lock Gode Priority = 1
eee ee ee ee ee ee ee e e eeeee eee ee eee eee eee ee eee
Note
Allocatable lock codes, which allows different classifications of available inventory, are not supported in the WMS Cloud and Merchandising integration.
Convert Master Data
This section describes how to initialize master data in WMS Cloud based from Merchandising data. Master data includes stores, warehouses, external finishers, supplier sites and items from Merchandising. Prior to running the integration to load data into Cloud WMS, the key master data from Merchandising must be loaded into WMS Cloud, to ensure all subscribers and publishers can execute successfully.
Other Notes
-
The WMS Managed flag for each of the below described entities in WMS Cloud should be set to N (false).
-
Where necessary, truncate Merchandising values to ensure that they meet any size limitations of WMS Cloud.
-
In addition to the data elements called out below, you will need to validate that the codes used for language, states and countries match between Merchandising/SIOCS and WMS Cloud as part of the initial configuration.
-
WMS Cloud is a multi-tenant application and requires a company code1 to be sent in all inbound integrations, including those recommended for data conversion below. The code to be used when loading data can be found in the Companies screen in WMS Cloud for your implementation.
Note
This code will be assigned to your company on provisioning of WMS Cloud. It is not the same ID created as the top level of the organizational and merchandise hierarchies in Merchandising.
-
Use the action code CREATE for all conversion data loading, when required on the WMS Cloud inbound file.
-
To extract data from your Merchandising database to support the conversion requirements outlined below, it is recommended that you use one of the following methods:
-
Replicated DAS schema
-
Application Express (APEX) Data Viewer
-
BI Publisher
-
Stores, Partners, and Warehouses
First, stores, partners, and warehouses must be loaded. For stores and partners, these can be setup manually in the WMS Cloud Facilities screen, or loaded from data extracted from
1 This code will be assigned to your company on provisioning of WMS Cloud. It is not the same ID created as the top level of the organizational and merchandise hierarchies in Merchandising.
Merchandising. It is recommended that data be loaded using the Store and Site interfaces to minimize data entry errors.
Stores
Extract the attributes for stores into a .csv file, based on the attributes in the Store API. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-4 Stores Mappings
| WMS Cloud | Merchandising |
|---|---|
| code | store.store |
| name | store.store_name |
| address_1 | addr.add_1 |
| address_2 | addr.add_2 |
| city | addr.city |
| locality | addr.county |
| state | addr.state |
| country | addr.country_id |
| zip | addr.post |
| contact | store.store_mgr_name |
| phone_nbr | store.phone_number |
| store.email | |
| lang | store.lang |
Other Notes
- Use the primary business address (type 01) as the address for this import.
External Finishers
Extract attributes for external finishers into a .csv file, based on the attributes in the Site API. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-5 External Finisher Mappings
| WMS Cloud | Merchandising |
|---|---|
| code | partner.partner_id |
| name | partner.partner_desc |
| address_1 | addr.add_1 |
| address_2 | addr.add_2 |
| city | addr.city |
| locality | addr.county |
| state | addr.state |
| country | addr.country_id |
| zip | addr.post |
| contact | addr.contact_name |
Table 4-5 (Cont.) External Finisher Mappings
| WMS Cloud | Merchandising |
|---|---|
| phone_nbr | addr.contact_phone |
| addr.contact_email | |
| lang | partner.lang |
Other Notes
-
Only partners of type ‘E’ (External Finisher) from Merchandising should be loaded into WMS Cloud.
-
Use the primary business address (type 01) as the address for this import.
Warehouses
WMS Cloud does not have an inbound integration for warehouses, so they must be created within the solution manually through the Facilities screens. These warehouse IDs in WMS Cloud should match the physical warehouse IDs in Merchandising. For more details on how to create facilities, refer to the Oracle Warehouse Management Cloud documentation.
Note
If you add any new physical warehouses in Merchandising post implementation of this integration, those facilities will also need to be created manually in WMS Cloud using similar rules to that described above.
Vendors
Extract attributes for supplier sites into a .csv file, based on the attributes in the Vendor API. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-6 Vendors Mappings
| WMS Cloud | Merchandising |
|---|---|
| vendor_code | sups.supplier |
| name | sups.sup_name |
| address_1 | addr.add_1 |
| address_2 | addr.add_2 |
| address_3 | addr.add_3 |
| city | addr.city |
| state | addr.state |
| country | addr.country_id |
| zip | addr.post |
| contact | addr.contact_name |
| phone_nbr | addr.contact_phone |
Table 4-6 (Cont.) Vendors Mappings
| WMS Cloud | Merchandising |
|---|---|
| addr.contact_email |
Other Notes
-
Only supplier sites should be loaded into WMS Cloud.
-
Use the primary business address (type 01) as the address for this import.
Items
To initialize items in WMS Cloud, it is recommended that they be loaded from data exported from Merchandising to create a .csv file with the attributes required. Then, use the APIs provided by WMS Cloud for loading. Only approved items should be loaded into WMS Cloud.
Item Header
Use the Item API to load transaction level items from Merchandising. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-7 Item Header Mappings
| WMS Cloud | Merchandising |
|---|---|
| part_a or item_alternate_code | item_master.item |
| part_a | item_master.item_parent |
| part_b | item_master.diff1 |
| part_c | item_master.diff2 |
| part_d | item_master.diff3 |
| part_e | item_master.diff4 |
| hierarchy1_code | item_master.dept |
| hierarchy1_description | deps.dept_name |
| hierarchy2_code | item_master.class |
| hierarchy2_description | class.class_name |
| hierarchy3_code | item_master.subclass |
| hierarchy3_description | subclass.sub_name |
| description | item_master.item_desc |
| short_descr | item_master.short_desc |
| shipping_temperature_instr | item_master.handling_temp |
| catch_weight_method | (see below) |
| retail_price | (see below) |
| brand_code | item_master.brand_name |
Table 4-7 (Cont.) Item Header Mappings
| WMS Cloud | Merchandising |
|---|---|
| invn_attr_a_tracking | item_master.inventory_ind |
| description2 | image: (see below) |
Other Notes
-
Only approved, transaction-level items should be loaded into WMS Cloud using this API.
-
For items without a parent or with a parent but not using diffs in Merchandising, part_a should be set equal to the item ID when loaded into WMS Cloud.
-
Merchandising will not send length, width, height, weight, and cube information to WMS Cloud. These fields will be protected in WMS Cloud. This is due to differences in UOM related fields between the two solutions.
-
Values not listed above are not available in Merchandising so should be left null in the import to WMS Cloud.
-
Item Facility records do not need to be loaded. They will be created automatically in WMS Cloud.
-
If an item has a defined catch_weight_type in Merchandising, then use Y for the catch_weight_method field. Otherwise, set to N.
-
For retail price, the integration will send the regular retail price for the item in the base zone converted to the primary currency and standard unit of measure. Similar logic can be used for the item conversion.
-
Hierarchy levels 4 and 5 should be left null in WMS Cloud.
-
The primary item image for an item in Merchandising will be mapped to the WMS Cloud description2 field for items in the integration, if defined. For conversion, it is recommended you do the same, concatenating the image_addr and the image_name for the primary image defined for your item.
Item Barcodes
Use the Item Barcode API to load reference items from Merchandising to WMS Cloud. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-8 Item Barcodes Mappings
| WMS Cloud | Merchandising |
|---|---|
| vendor_barcode | item_master.item |
| item_barcode | item_master.item_parent |
Other Notes
-
Only approved reference items (where tran_level+1 = item_level) from Merchandising for transaction items that meet the criteria of the item import above should be mapped in this API.
-
WMS Cloud requires a mandatory barcode for each item loaded into it, and in cases where Merchandising does not have this value, the item can be duplicated as the barcode.
Item Pre-packs
Use the Item Pre-packs API to load the components of a pack item from Merchandising to WMS Cloud. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-9 Item Pre-packs Mappings
| WMS Cloud | Merchandising |
|---|---|
| parent_item_code | packitem_breakout.pack_no |
| seq_no | packitem_breakout.seq_no |
| child_item_code | packitem_breakout.item |
| child_units | packitem_breakout.pack_item_qty |
Other Notes
-
Only component details for approved, complex pack items should be loaded into WMS Cloud using this API.
-
Simple packs are treated as regular items in terms of stocking and inventory movement within WMS Cloud, hence they will be sent in the integration as part of the item feed.
Item Supplier Pack Size
Use the Item Supplier Country API to load the pack size details for an item from Merchandising to WMS Cloud. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-10 Item Supplier Pack Size Mappings
| WMS Cloud | Merchandising |
|---|---|
| std_pack_qty | inner_pack_size |
| std_case_qty | supp_pack_size |
| lpns_per_tier | ti |
| tiers_per_pallet | hi |
Other Notes
-
This is an optional data point; the item supplier pack size details are not interfaced in the default setup of this integration.
-
Only pack sizes for the primary supplier and country are loaded into WMS Cloud using this API.
Item Dimensions
Use the Item Dimension API to load the dimension details for an item from Merchandising to WMS Cloud. The table below outlines how the Merchandising attributes map to the WMS Cloud attributes.
Table 4-11 Item Dimensions Mappings
| WMS Cloud | Merchandising |
|---|---|
| length | Based on item_supp_country_dim.dim_object, For dim object as each, item_supp_country_dim. unit_length |
| For dim object as inner, item_supp_country_dim. std_pack_length For dim object as case, item_supp_country_dim. std_case_length | |
| width | Based on item_supp_country_dim.dim_object, For dim object as each, item_supp_country_dim. unit_width |
| For dim object as inner, item_supp_country_dim. std_pack_width | |
| For dim object as case, item_supp_country_dim. std_case_width | |
| height | Based on item_supp_country_dim.dim_object, For dim object as each, item_supp_country_dim. unit_height |
| For dim object as inner, item_supp_country_dim. std_pack_height | |
| For dim object as case, item_supp_country_dim. std_case_height | |
| weight | Based on item_supp_country_dim.dim_object, For dim object as each, item_supp_country_dim. unit_weight |
| For dim object as inner, item_supp_country_dim. std_pack_weight | |
| For dim object as case, item_supp_country_dim. std_case_weight |
Other Notes
-
This is an optional data point; the item dimension details are not interfaced in the default setup of this integration.
-
Only dimensions for the primary supplier and country are loaded into WMS Cloud using this API.
Convert Transactional Data
It is highly recommended that you close all open shipments between the facilities that will be using WMS Cloud and your stores so that there are no open transfers or allocations for the facility, including any customer orders from the warehouse. This means that no stock orders would need to be converted into WMS Cloud from Merchandising. However, it is expected that some open purchase orders may exist that need to be converted. Additionally, there will be a need to initialize the inventory values in WMS Cloud and synch this with Merchandising. The sections below outline the recommended approach for this.