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.
5 Integration Configuration
This chapter covers configuration that needs to be done in order to extract WMS transaction records and set up the outbound interfaces.
Schedule Jobs
Create a schedule job for Inventory History that will extract the relevant information during scheduled intervals from WMS Cloud. This needs to be set up for Receipts, RTVs, Stock Orders, Inventory Adjustments, and Outbound ASNs. You can create one schedule for all of these entities, or separate schedules by functional area. Segregating has the advantage of setting different frequency on each scheduled job which is set using the Every and Period fields. The example below shows how the Generate Inventory History extract in WMS Cloud could be setup in three different schedules based on the activity code that correlates to a Merchandising entity.
Table 5-1 Inventory History Extract in WMS Cloud
| Job Type | Activity Code | Schedule Name | Schedule Type | Every Period |
|---|---|---|---|---|
| Generate Inventory History Extract Generate Inventory History Extract | 1 10 | Receipts SOStatus | Interval Interval | Set these fields to values between 1 and 5 minutes, depending on the volume of transactions that are being processed in your warehouse. The more transactions being processed, the shorter the interval should be. |
| Generate Inventory History Extract | 19 | InvAdj | Interval |
Enabled Auto Send
The main way to extract WMS transaction records is through scheduled jobs at pre-determined intervals. You can also automatically send inventory history records in a real-time manner as and when they are created. They are sent through the Output Interface setup just like other outgoing messages configured through scheduled jobs. To enable Auto-Send of Inventory History for an activity code, choose enable_auto_send from the Inventory History Activity Parameter screen. If you are using this option for integration, ensure all activity codes generated in the same group in WMS are integrated using the enable_auto_send option. This ensures that these integration messages are interfaced in the required order, making consistent updates to Merchandising.
Configure Outbound Interfaces
Outbound interface configurations must be created in WMS Cloud for each facility, one for each of the following exports:
-
Inventory History
-
Outbound Loads
-
Outbound Manifest
Inventory History Export
The Inventory History export is used to communicate updates to receipts, for purchase orders, transfers and allocations, stock order status updates, and inventory adjustments. To configure this for export, set the interface format to XML on the Output Interface Configuration for Inventory History Export.
Note
Although these exports require configuration in WMS, these are not customizable integrations. Only the activity codes described in this section are supported in the base integration.
Next, create three targets for Inventory History Export, using the appropriate host and port for your implementation in the URL definition. The target creation can be done in the WMS Cloud application under the Output Interface Configuration tab.
- Column value = ‘1|4’
Target 2: SOStatus
URL: http://
Output Interface Target Criteria:
-
Column name = Activity Code
-
SQL operator = IN
-
Column value = ‘10|11|12|27|31|32|54|85’
Target 3: InvAdj
URL: http://
Output Interface Target Criteria:
-
Column name = Activity Code
-
SQL operator = IN
-
Column value = ‘2|4|17|19|22|23|24|25|29|30|49|50|53|65’
- See “Appendix - Activity Codes” for more details on these activity codes.
Outbound Loads Export
The Outbound Loads export is used to map shipments that are shipped via TL/LTL from the warehouse to Merchandising (RTVs and stock order shipments), SIOCS (stock order shipments to stores), and OROB (stock order shipments for customer orders), as opposed to via a parcel service such as UPS or FedEx1. To configure this for export, set the interface format to XML on the Output Interface Configuration for Outbound Loads Export.
Note
This determination is made based on the presence or absence of a parcel service in the Ship Via field for an order.
Next, create two targets for Outbound Loads Export, using the appropriate host and port for your implementation in the URL definition. The target creation can be done in the WMS Cloud application under the Output Interface Configuration tab.
1 This determination is made based on the presence or absence of a parcel service in the Ship Via field for an order.
- Column value = RTV
Target 2: ASNOut
URL: http://
Output Interface Target Criteria:
-
Column name = Order Type
-
SQL operator = IN
-
Column value = B2B | B2C
Target 3: ASNOut
URL: http://
Output Interface Target Criteria:
-
Column name = Order Type
-
SQL operator = IN
-
Column value = B2B
Outbound Manifest
The Outbound Manifest export is also used to map shipments to Merchandising (RTVs and stock order shipments), SIOCS (stock order shipments to stores), and OROB (stock order shipments for customer orders). But unlike the Outbound Load Export, it is done via a parcel 2 service . To configure this for export, set the interface format to XML on the Output Interface Configuration for Outbound Manifest.
Note
This determination is made based on the presence or absence of a parcel service in the Ship Via field for an order.
2 This determination is made based on the presence or absence of a parcel service in the Ship Via field for an order.
Output Interface Target Criteria:
-
Column name = Order type
-
SQL operator = IN
-
Column value = RTV
Target 2: ASNOut
URL: http://
Output Interface Target Criteria:
-
Column name = Order type
-
SQL operator = IN
-
Column value = B2B | B2C
For ALL of the targets listed above, include the following:
-
Interface Protocol = REST Web Service
-
Username =
-
Password =
Note
If the account password expires or is changed, it needs to be changed here as well.
Other Configurations
A few other configurations need to be considered in WMS Cloud that are used in the integrations with Merchandising, SIOCS, and OROB.
Sequence Counters
You will need to configure the sequence length for specific counters in the Sequence Counters tab in WMS Cloud to ensure the generated sequence numbers do not exceed the length supported by the integration to Merchandising. The following are the counter codes that need to be configured:
BOL Number
The sequence count used for generating BOL numbers is used in the integration of stock order shipments from the warehouse and mapped to the BOL number in Merchandising. It must be configured such that the combined prefix and sequence number does not exceed 17 characters in length that are allowed by the integration.
Inbound Shipment Number
The sequence counter used for generating shipment numbers is used in the integration of DC to DC shipments. It must be configured such that the combined prefix and sequence number do not exceed 30 characters.
Configure Integration Layer
Configure USM
In USM, URLs will need to be configured for your environment to allow the RIB to communicate with WMS Cloud. This configuration will be done by the Oracle Cloud Operations team, but you may be asked to help provide the URLs for this configuration. These are the two URLs that need to be configured:
-
LogFire_Host_Url_Key – this is your link to the WMS Cloud application; configure this appropriately to allow USM to connect to the WMS Cloud application.
-
RibLgf_host_UrlKey – this is the link to the RIB application for this integration; set this field in USM to enable it to connect with the RIB
Configure Static DVMs
Once the links to the end applications are configured, the static DVMs have to be configured with values from your specific implementation for company code and facility codes. These are mandatory values. The DVMs that are to be edited are:
-
CompanyCode_dvm.LogFireIntegration – this is where the company code is to be set. The company code to use here can be found in the WMS Cloud Companies screen. The entry to be made in the DVM is “CompanyName” in the name column and your company code in the value column. Company code is case sensitive.
-
FacilityCode_dvm.LogFireIntegration – this is where the facility codes are to be set - one record for each physical warehouse that you configured in WMS Cloud in the Warehouse conversion section. The entry to be made in the DVM is the warehouse ID in the FacilityId column, facility type in the FacilityType column and facility time zone in the FacilityTimeZone column. This should match exactly how you have configured your facilities in WMS Cloud.
Note
There is also a static DVM for country code, however this is not required for the integration so does not need a configuration.
More details about the configuration of the USM application can be found in the Oracle Retail Integration Cloud Service Universal Service Mapper User Guide , a link for which is provided in “Appendix - Activity Codes”.
Configure RIB
When being sent from Merchandising to WMS Cloud, data passes through an application called RIB-TAFR (Transformation Addressing Filtering Routing). As part of the standard RIB configuration, the warehouse facility IDs need to be configured in the RIB in order for the TAFR logic to filter and route messages. This is done by the Oracle Cloud Operations team. Once you have your warehouse facilities set up in WMS Cloud, you will need to provide these IDs to the Oracle Cloud Operations team for them to do this configuration. More details can be found in the Oracle Retail Integration Bus Operations Guide .
Be
In this guide
- Guide: Oracle Retail and WMS Cloud Implementation Guide
- Previous: 4 Data Conversion
- Next: A Appendix - Solution Overviews