Document History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Update Version Notes
04 JUN 2019 May Maintenance Pack for 18C Delivered new features in May Maintenance Pack for 18C.
04 JUN 2019 April Maintenance Pack for 18C Revised April Maintenance Pack for 18C.
08 MAY 2019 March Maintenance Pack for 18C Revised March Maintenance Pack for 18C.
29 MAR 2019 February Maintenance Pack for 18C Delivered new features in February Maintenance Pack for 18C.
29 MAR 2019 January Maintenance Pack for 18C Revised January Maintenance Pack for 18C.
22 FEB 2019 December Maintenance Pack for 18C Delivered new features in December Maintenance Pack for 18C.
22 FEB 2019 November Maintenance Pack for 18C Revised November Maintenance Pack for 18C.
27 NOV 2018 October Maintenance Pack for 18C Delivered new features in October Maintenance Pack for 18C.
29 MAR 2018 Update 18C Revised update 18C.

May Maintenance Pack for 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
04 JUN 2019 Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

Additional Timezone Support

Integration Enhancements

Designate Page Size for GET Request in REST Service APIs

XML Support for Custom Inventory Summary API

Functional Enhancements

Additional Timezone Support

As part of 18C updates, Oracle WMS Cloud now supports an additional 385 timezones. From the Facility screen, you can access 433 timezones in total.

See the following table for a list of the available time zones:

Africa/Abidjan

Africa/Accra

Africa/Addis_Ababa

Africa/Algiers

Africa/Asmara

Africa/Bamako

Africa/Bangui

Africa/Banjul

Africa/Bissau

Africa/Blantyre

Africa/Brazzaville

Africa/Bujumbura

Africa/Cairo

Africa/Casablanca

Africa/Ceuta

Africa/Conakry

Africa/Dakar

Africa/Dar_es_Salaam 

Africa/Djibouti

Africa/Douala

Africa/El_Aaiun

Africa/Freetown

Africa/Gaborone

Africa/Harare

Africa/Johannesburg

Africa/Juba

Africa/Kampala

Africa/Khartoum

Africa/Kigali

Africa/Kinshasa

Africa/Lagos

Africa/Libreville

Africa/Lome

Africa/Luanda

Africa/Lubumbashi

Africa/Lusaka

Africa/Malabo

Africa/Maputo  

Africa/Maseru  

Africa/Mbabane  

Africa/Mogadishu  

Africa/Monrovia  

Africa/Nairobi  

Africa/Ndjamena  

Africa/Niamey  

Africa/Nouakchott  

Africa/Ouagadougou  

Africa/Porto-Novo  

Africa/Sao_Tome  

Africa/Tripoli  

Africa/Tunis  

Africa/Windhoek  

America/Adak

America/Argentina/San_Luis  

America/Argentina/Tucuman  

America/Argentina/Ushuaia  

America/Aruba  

America/Asuncion  

America/Atikokan  

America/Bahia  

America/Anchorage  

America/Anguilla  

America/Antigua  

America/Araguaina  

America/Argentina/Buenos_Aires  

America/Argentina/Catamarca  

America/Argentina/Cordoba  

America/Argentina/Jujuy  

America/Argentina/La_Rioja  

America/Argentina/Mendoza  

America/Argentina/Rio_Gallegos  

America/Argentina/Salta  

America/Argentina/San_Juan

America/Bahia_Banderas  

America/Barbados  

America/Belem  

America/Belize  

America/Blanc-Sablon  

America/Boa_Vista

America/Bogota  

America/Boise  

America/Cambridge_Bay

America/Campo_Grande  

America/Cancun  

America/Caracas  

America/Cayenne  

America/Cayman  

America/Chicago  

America/Chihuahua  

America/Costa_Rica  

America/Creston  

America/Cuiaba  

America/Curacao  

America/Danmarkshavn  

America/Dawson  

America/Dawson_Creek  

America/Denver  

America/Detroit  

America/Dominica  

America/Edmonton

America/Eirunepe

America/El_Salvador  

America/Fort_Nelson

America/Fortaleza  

America/Glace_Bay  

America/Godthab  

America/Goose_Bay  

America/Grand_Turk  

America/Grenada  

America/Guadeloupe  

America/Guatemala  

America/Guayaquil  

America/Guyana

America/Halifax  

America/Havana  

America/Hermosillo  

America/Indiana/Indianapolis

America/Indiana/Knox  

America/Indiana/Marengo  

America/Indiana/Petersburg  

America/Indiana/Tell_City  

America/Indiana/Vevay  

America/Indiana/Vincennes  

America/Indiana/Winamac  

America/Inuvik  

America/Iqaluit  

America/Jamaica  

America/Juneau  

America/Kentucky/Louisville  

America/Kentucky/Monticello 

America/Kralendijk

America/La_Paz

America/Lima  

America/Los_Angeles  

America/Lower_Princes  

America/Maceio  

America/Managua

America/Manaus  

America/Marigot  

America/Martinique  

America/Matamoros

America/Mazatlan  

America/Menominee

America/Merida

America/Metlakatla

 America/Mexico_City  

America/Miquelon

America/Moncton  

America/Monterrey  

America/Montevideo  

America/Montserrat  

America/Nassau  

America/New_York  

America/Nipigon  

America/Nome

America/Paramaribo  

America/Phoenix  

America/Port-au-Prince  

America/Port_of_Spain  

America/Porto_Velho  

America/Puerto_Rico  

America/Punta_Arenas  

America/Rainy_River  

America/Rankin_Inlet  

America/Noronha

America/North_Dakota/Beulah

America/North_Dakota/Center   America/North_Dakota/New_Salem  

America/Ojinaga  

America/Panama  

America/Pangnirtung   

America/Recife  

America/Regina  

America/Resolute  

America/Rio_Branco  

America/Santarem

America/Santiago  

America/Santo_Domingo

America/Sao_Paulo  

America/Scoresbysund  

America/Sitka  

America/St_Barthelemy  

America/St_Johns  

America/St_Kitts  

America/St_Lucia  

America/St_Thomas  

America/St_Vincent  

America/Swift_Current  

America/Tegucigalpa  

America/Thule  

America/Thunder_Bay  

America/Tijuana  

America/Toronto  

America/Tortola  

America/Vancouver  

America/Whitehorse  

America/Winnipeg  

America/Yakutat  

America/Yellowknife  

Antarctica/Casey  

Antarctica/Davis  

Antarctica/DumontDUrville  

Antarctica/Macquarie  

Antarctica/Mawson  

Antarctica/McMurdo  

Antarctica/Palmer  

Antarctica/Rothera  

Antarctica/Syowa  

Antarctica/Troll  

Antarctica/Vostok  

Arctic/Longyearbyen  

Asia/Aden  

Asia/Almaty  

Asia/Amman  

Asia/Anadyr  

Asia/Aqtau  

Asia/Aqtobe  

Asia/Hong_Kong  

Asia/Hovd  

Asia/Irkutsk

Asia/Jerusalem  

Asia/Kabul  

Asia/Kamchatka

Asia/Karachi  

Asia/Kathmandu  

Asia/Khandyga

Asia/Kolkata  

Asia/Krasnoyarsk

Asia/Kuala_Lumpur  

Asia/Kuching  

Asia/Kuwait  

Asia/Macau  

Asia/Magadan  

Asia/Makassar  

Asia/Manila  

Asia/Muscat  

Asia/Nicosia  

Asia/Novokuznetsk  

Asia/Novosibirsk  

Asia/Omsk

Asia/Oral  

Asia/Phnom_Penh  

Asia/Pontianak  

Asia/Pyongyang  

Asia/Qatar  

Asia/Qyzylorda  

Asia/Riyadh  

Asia/Sakhalin

Asia/Samarkand  

Asia/Seoul

Asia/Shanghai

Asia/Singapore  

Asia/Srednekolymsk

Asia/Taipei

Asia/Tashkent

Asia/Tbilisi  

Asia/Tehran  

Asia/Thimphu

Asia/Tokyo  

Asia/Tomsk  

Asia/Ulaanbaatar  

Asia/Urumqi  

Asia/Ust-Nera  

Asia/Vientiane  

Asia/Vladivostok  

Asia/Yakutsk  

Asia/Yangon  

Asia/Yekaterinburg  

Asia/Yerevan  

Atlantic/Azores  

Atlantic/Bermuda  

Atlantic/Canary  

Atlantic/Cape_Verde 

Atlantic/Faroe

Atlantic/Madeira

Atlantic/Reykjavik

Atlantic/South_Georgia

Atlantic/St_Helena

Atlantic/Stanley

Australia/Adelaide

Australia/Brisbane  

Australia/Broken_Hill  

Australia/Currie  

Australia/Darwin  

Australia/Eucla  

Australia/Hobart  

Australia/Lindeman  

Australia/Lord_Howe

Australia/Melbourne

Australia/Perth

Australia/Sydney  

Canada/Atlantic  

Canada/Central  

Canada/Eastern  

Canada/Mountain  

Canada/Newfoundland  

Canada/Pacific  

Europe/Amsterdam  

Europe/Andorra  

Europe/Astrakhan  

Europe/Athens  

Europe/Belgrade

Europe/Berlin  

Europe/Bratislava  

Europe/Brussels  

Europe/Bucharest  

Europe/Budapest  

Europe/Busingen  

Europe/Chisinau  

Europe/Copenhagen  

Europe/Dublin  

Europe/Gibraltar  

Europe/Guernsey  

Europe/Helsinki  

Europe/Isle_of_Man  

Europe/Istanbul  

Europe/Jersey  

Europe/Kaliningrad  

Europe/Kiev  

Europe/Kirov

Europe/Lisbon  

Europe/Ljubljana

Europe/London  

Europe/Luxembourg

Europe/Madrid  

Europe/Malta  

Europe/Mariehamn  

Europe/Minsk  

Europe/Monaco  

Europe/Moscow  

Europe/Oslo

Europe/Paris  

Europe/Podgorica  

Europe/Prague  

Europe/Riga  

Europe/Rome  

Europe/Samara  

Europe/San_Marino  

Europe/Sarajevo  

Europe/Saratov  

Europe/Simferopol  

Europe/Skopje  

Europe/Sofia  

Europe/Stockholm  

Europe/Tallinn  

Europe/Tirane  

Europe/Ulyanovsk  

Europe/Uzhgorod  

Europe/Vaduz  

Europe/Vatican  

Europe/Vienna  

Europe/Vilnius  

Europe/Volgograd

Europe/Warsaw  

Europe/Zagreb  

Europe/Zaporozhye  

Europe/Zurich  

GMT  

Indian/Antananarivo

Indian/Chagos

Indian/Christmas  

Indian/Cocos  

Indian/Comoro  

Indian/Kerguelen  

Indian/Mahe  

Indian/Maldives

Indian/Mauritius

Indian/Mayotte  

Indian/Reunion  

Pacific/Apia

Pacific/Auckland   

Pacific/Bougainville  

Pacific/Chatham  

Pacific/Chuuk  

Pacific/Easter  

Pacific/Efate  

Pacific/Enderbury  

Pacific/Fakaofo  

Pacific/Fiji  

Pacific/Funafuti  

Pacific/Galapagos  

Pacific/Gambier  

Pacific/Guadalcanal

Pacific/Guam

Pacific/Honolulu  

Pacific/Kiritimati  

Pacific/Kosrae  

Pacific/Kwajalein  

Pacific/Majuro  

Pacific/Marquesas  

Pacific/Midway  

Pacific/Nauru  

Pacific/Niue  

Pacific/Norfolk

Pacific/Noumea

Pacific/Pago_Pago  

Pacific/Palau  

Pacific/Pitcairn  

Pacific/Pohnpei  

Pacific/Port_Moresby  

Pacific/Rarotonga  

Pacific/Saipan

Pacific/Tahiti  

Pacific/Tarawa  

Pacific/Tongatapu 

Pacific/Wake

Pacific/Wallis

US/Central

US/Alaska  

US/Arizona

US/Eastern  

US/Hawaii

US/Mountain

US/Pacific

UTC

Steps to Enable

No steps are required to enable this feature.

Integration Enhancements

Designate Page Size for GET Request in REST Service APIs

Previously, the UI rows per page setting for API users was used as the records per page for API responses as well. This had the limitation that it had a hard upper limit of 125 which might be too low for API responses. It was also more cumbersome to change. The number of records returned per GET API request can now be changed more easily, per request. A new API parameter page_size is now available optionally and if used, will override the UI rows per page setting.

There is still a hard upper limit, but it is much higher, at 1250. If a page_size above that value is requested, an error will be returned. If the page_size parameter is left out, the earlier behavior applies (i.e. the user’s UI rows per page setting is used). The "page_size" is a query parameter that is part of the request URL. The parameter value is not saved anywhere and applies only to that request.

The following are examples of GET requests to designate page size:

GET .../entity/inventory/?page_size=10

This also works with the "sequenced" pagination style:

GET .../entity/inventory/?page_mode=sequenced&page_size=10

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > REST API). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Refer to the REST API Guide for more details.

XML Support for Custom Inventory Summary API

Prior to this update, querying the Custom Inventory Summary API used to return the report in pipe-delimited format. Now, When you query the Custom Inventory Summary API, you can specify the output format as XML using the existing ‘format’ query string parameter to get the Custom Inventory Summary report in xml format. When blank, the existing logic is retained where the result set is pipe-delimited and is returned as a binary file attached to the response. "json" is not supported for this API.

The following is an example of a GET request for xml output format:

GET.../report/custom_inventory_summary?item_code=<item_code>&company_id=<company_id>&facility_id=<facility_id>&format=xml

Or

GET.../report/custom_inventory_summary.xml?item_code=<item_code>&company_id=<company_id>&facility_id=<facility_id>

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > REST API). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Refer to the REST API Guide for more details.

April Maintenance Pack for 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
04 JUN 2019 Honor Expiration Date Ranges in RF Pack NC Updated document. Revised feature information.
09 MAY 2019 Group Level Permissions in UI Screens Updated document. Revised feature information.
08 MAY 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

Group Level Permissions in UI Screens

Additional Language Support

Two New Scheduled Jobs (Alternative for Upcoming Deactivation of WMS Cloud Hosted SFTP Site)

Receive Additional Purchase Order Details with PO Receiving Mode

Print OBLPN Packing Slips from Web Reports

Honor Expiration Date Ranges in RF Pack NC

Print Labels in Arabic

Integration Enhancements

Track and Validate Items with MHE Pick Confirm API

Functional Enhancements

Group Level Permissions in UI Screens

A new set of permissions are now available, as these are some of the important actions frequently done in the Oracle WMS Cloud workflow. Only users with respective permissions should be able to access the action buttons. Prior to this enhancement, these action buttons were enabled for all the users.

NOTE: With this change, users with the role of employee, supervisor, guard will not have the corresponding action buttons enabled unless exclusive permissions have been provided at the group level.

Steps to Enable

To enable the action buttons, ensure that you get the respective permissions at the group level.

Additional Language Support

As an enhancement in 18C, Oracle WMS Cloud now supports four new languages for a better user experience.

The new languages are:

Steps to Enable

No steps are required to enable this feature.

Two New Scheduled Jobs (Alternative for Upcoming Deactivation of WMS Cloud Hosted SFTP Site)

Oracle Cloud WMS currently provides an SFTP hosting service for transferring interface files. This service is being decommissioned and information was provided last year to customers.

NOTE:

Two new scheduled job services have been created. “SFTP get files" to allow pulling files from an external SFTP site. In addition another scheduled job “SFTP put files" is also being provided to allow files to be transmitted to external SFTP sites (however the recommended way to send files out is to use the output interface configuration which already supported the SFTP protocol). For more details about the configuration of these jobs, please refer to Setting up Scheduled Jobs.

Steps to Enable

Set up SFTP get files and SFTP put files in the Scheduled Jobs UI.

Receive Additional Purchase Order Details with PO Receiving Mode

PO-Receiving mode is an existing mode that is now enhanced to allow you to add unreceived details and update the ASN/ PO to the correct status, so you can receive it. Previously, when an ASN was linked to a Purchase Order (PO), and the ASN was in a status of received (not yet verified), you could add new lines to the PO using the input interface. However, previously, using the PO receiving mode you could not receive the newly added PO lines. Now, when you set the Receive Shipment LPN module mode to "PO-Receiving", you will be able to receive additional details added to the PO.

Prior to this change, users could add more details to a purchase order, but they could not receive inventory using the the RF Rec {shipment} LPN with Mode: PO Receiving option as it was giving them an error that the Purchase Order had been received. Now, if new details are added to Purchase Orders in Received Status, then the status will be updated to In-Receiving. This allows you to receive more inventory against this PO.  Oracle WMS Cloud will find the current Purchase Order detail line and change the status to in receiving, so that you are able to receive it.

Steps to Enable

No steps are required to enable this feature.

Print OBLPN Packing Slips from Web Reports

Prior to this change, if you created an OBLPN packing slip using web reports, and you wanted to print the packing slip, you needed to go to the Web Reports UI or the corresponding action button in the UI screens and print each OBLPN packing slip from this UI. This process is time consuming, and sometimes users that needed to print this custom OBLPN packing slip did not have access to the UI.

You now have the option to print OBLPN Packing Slips and Order Packing Slips developed in web reports from the RF. You no longer have to go to the UI to print OBLPN or order Packing Slips developed in web reports.

Steps to Enable

Set up the OBLPN Packing report type in the Company Report Type UI.

Honor Expiration Date Ranges in RF Pack NC

Previously, Oracle WMS Cloud users could configure wave templates to only allocate inventory using a specific expiry date range window. The system would allocate based on that expiry range, but if the user doing the packing substituted the inventory with other inventory where the expiration range was not within this range, the system would allow it.

NOTE:  This change applies only to the Non-Cubed Active Picking Screen.

Now, if you want to substitute inventory using the RF Pack NC transaction, and the original inventory was part of an allocation that was based on the expiry range, the system will only allow you to substitute with inventory that is within that time frame. If allocation has happened without defining the expiration window range, then substituted inventory should match the expiration date with the allocated inventory. This check will happen during picking from reserve or active using the Non-Cubed Active Picking screen.

The following are descriptions for the req-lpn-sub-validations screen parameter settings (that apply when picking during substitution is from an Active location):

  1. Blank/All: When the parameter value is set to Blank or ALL, the default behavior is retained when the system performs an expiration date range check defined for items that have prod_life_days > 0 or for items that are tracking the batch and expiration dates (if the underlying batch number is not reserved for any order).
  1. Batch: If the item is tracking a batch number, then the system checks for the batch number for the substitution item. The system only allows substitution if the batch number matches. However, if the item is tracking expiration date only, then expiration window range checks are performed.
  1. Expiry: If the item is tracking an expiration date, then the system checks for the expiration date of the substituted item. However, if the item is only tracking a batch number, then the system allows substitution given that the batch number does not match with the order and the order is not reserved for the batch.
  1. None: Allows substituting inventory without checking for the batch number for the allocated order and doesn’t perform expiration window range check validations for items tracking an expiration date.

Steps to Enable

  1. Go to the Pack NC Active UI > Screen Parameter/
  2. Select req-lpn-sub-validations and click Edit.
  3. Select the module parameter choice from the drop-down menu. 
  4. Click Save.

Print Labels in Arabic

Previously, Oracle WMS Cloud users could not create labels in Arabic. Document and Label Designer has been enhanced to include the ability to create labels in Arabic.  This will allow printer drivers to easily identify relevant information on the label such as the store or destination enabling customers to read labels in Arabic.

Steps to Enable

To enable this feature, you need to install the Arabic Font. Please refer to Zebra Support for more details on how to do this.

Integration Enhancements

Track and Validate Items with MHE Pick Confirm API

When handling batch number tracked items, Oracle WMS Cloud could have allocated different number than what was picked physically by the MHE system. Prior to this change, WMS did not have an ability to send batch numbers in the MHE Pick Confirm API. WMS now accepts batch numbers via the MHE Pick Confirm API and performs updates based on what batch number is shared in the API.

This feature includes:

WAVE PICK INFO Output File

In 18C, three new fields are introduced in the Wave Pick Info Output file that provide an ability to send specific information about the items that are picked to the MHE system. These new fields allow you to track the items (allocated by the WMS system) and validate the same items through the MHE Pick Confirm API.

NOTE: The Wave Pick Info Output file generated supports XML or One-Line format.

This feature includes:

NOTE: The system has has ability to store inventory with packs/case qty that is different from item's standard case qty. Currently, while creating allocations for orders, the system honors the inventory case/pack quantity.

MHE PICK CONFIRM API 

This enhancement introduces MHE Pick Confirmation API that captures batch number, allocation UOM and UOM Quantity of an item that is picked by the MHE and sends this information back to the WMS system as a pick confirmation.

This feature includes:

NOTE: Once you perform an export of the MHE Pick Confirm UI, the system populates the Batch Number, Allocation UOM, and UOM quantity fields in the generated csv/excel file.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Tips And Considerations

NOTE: These fields are disabled/hidden by default. If you need to view additional inventory information, you can configure your UI grid accordingly.

Key Resources

Refer to the REST API Guide for more details.

March Maintenance Pack for 18C

Revision History

Date Feature Notes
08 MAY 2019 Locate Serial Number Discrepancy Using Cycle Count Trigger

Updated document. Delivered feature in March Maintenance Pack for 18C.

08 MAY 2019 Generate IBLPN Reports with Scheduled Jobs

Updated document. Delivered feature in March Maintenance Pack for 18C.

08 MAY 2019

Link OBLPN with Asset Number Using RF OBLPN Asset Seal Link API Parameter

Updated document. Delivered feature in March Maintenance Pack for 18C.

08 MAY 2019

Update Module and Screen Name in REST Service APIs

Updated document. Delivered feature in March Maintenance Pack for 18C.

16 APR 2019 Check Permissions for Cartonize and Ship Load Updated document. Revised feature information and steps to enable.
29 MAR 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

Complete Scanning Serial Numbers Before Pack OBLPN Tasking Updates

Locate Serial Number Discrepancy Using Cycle Count Trigger

Generate IBLPN Reports with Scheduled Jobs

Link OBLPN with Asset Number Using RF OBLPN Asset Seal Link API Parameter

User Experience and Usability Enhancements

Execute Task RF UI Improvements

Check Permissions for Cartonize and Ship Load

Integration Enhancements

Update Module and Screen Name in REST Service APIs

Functional Enhancements

Complete Scanning Serial Numbers Before Pack OBLPN Tasking Updates

During LPN packing, if there is a serial number mismatch (quantity in terms of the associated serial number count), the system prompts you to confirm the serial numbers. Previously, when confirming the serial numbers, if you exited out without scanning all serial numbers, the task was getting completed and OBLPN's that were created would have serial numbers less than the current quantity.

As part of this change, RF Pack OBLPN is enhanced so that in this scenario, the system prevents the task from moving to completed status. When you are in the serial number screen, and you press CTRL-E or CTRL-X or CTRL-W, a message displays alerting you that there is a serial number mismatch and the LPN is not packed.The user is taken back to the IBLPN confirmation screen.

The task will be in Ready status, the IBLPN will still be allocated and will still have the hyperlink with the current serial number in the transaction. You can go and update the serial numbers that are missing. The OBLPN will not be packed until the task is completed.

Steps to Enable

No steps are required to enable this feature.

Locate Serial Number Discrepancy Using Cycle Count Trigger

In instances where users send a POS interface file with a serial number that is not on a active location, the serial number gets delinked from the IBLPN. This scenario occurs when the transaction type is SALE. A serial number discrepancy can occur when a SALE transaction occurs from an active location but the serial number being sold is present in an Inbound LPN. The system delinks the serial number from Inbound LPN. To address this, Oracle WMS Cloud now has a new Cycle Count trigger that will create a cycle count task every time which will help users find the IBLPNs or locations that now have a mismatch of serial numbers.

After the POS interface has been run, if enabled, the Cycle Count trigger “Un-anticipated Serial Nbr Sold via POS Interface” in the system will double-check if there is a serial number discrepancy.

For example:

The POS file contains a computer with an Active Location ID of Active 1, and Serial Number: 123.

In the system, we have the following information about the serial number:

After the POS Interface file is sent, the system will delink the serial number from the IBLPN, and it will reduce the quantity of the active location (as Point of Sale only works for active inventory). When this situation occurs on the floor instead of the sale transaction being stopped, Oracle WMS Cloud delinks the serial number from the reserve location. Now, the Inbound LPN will have a higher quantity than the number of serial numbers linked. To correct this situation, the cycle count task will be created using the new trigger for the reserve 1 location and for active 1.

Steps to Enable

Enable Cycle count trigger: unanticipated Serial Nbr Sold via POS Interface.

Generate IBLPN Reports with Scheduled Jobs

Previously, the system did not send the IBLPN report to an external destination location. The default IBLPN status was only set to " Received" and "Located".

This enhancement includes the following supported status values:

A new job type "Run IBLPN Report" is now available in Scheduled Jobs for generating the IBLPN report.

Important features in this enhancement are:

  1. The generated IBLPN report contains the following column information:
  1. A new output interface type "IBLPN Report" is introduced in the Output Interface Configuration UI that allows you to define the external destination location to store the extracted IBLPN records.

NOTE: The Interface Format supported is "One Line".

Steps to Enable

Set up the Scheduled Job "Run IBLPN Report" and the Output Interface configuration type "IBLPN Report."

Link OBLPN with Asset Number Using RF OBLPN Asset Seal Link API Parameter

In every warehouse, inventories are picked, packed, and shipped on a daily basis. To satisfy the order need, warehouse operations use different types of containers (for example, physical totes) to move the goods from one place to another. In order to make the best use of available resources, warehouses may want to reuse the same totes for cubed picking after every transaction is complete. Previously, the system did not allow users to perform cubed picking through Re-Usable totes. In the warehouse, operations may need the MHE to perform cubed picking through reusable totes that have pre-printed labels.

To accomplish these scenarios, users may need an ability to pick through the asset number. You can now associate the Asset Number to the OBLPN Number (generated during a wave) so that picking can happen using pre-printed Labels:

This enhancement includes:

  1. An API parameter "OBLPN Link Asset" to link the OBLPN number (generated during cubed wave) to the Asset (Tote). This also includes:
  1. A new screen parameter is available in the RF Screen "RF - OBLPN Asset Seal Link" that replaces the original OBLPN generated during a wave with Asset Nbr when the Facility parameter "Reusable_Tote=Yes".

This RF screen introduces following new parameters:

Additional updates include:

NOTE: The reference container field is set only if it is empty. If the same container is linked to an asset multiple times, the ref container will be set only the very first time.

Steps to Enable

No steps are required to enable this feature.

User Experience and Usability Enhancements

Execute Task RF UI Improvements

Warehouse managers may need to associate group of users to specific specific tasks and task types. Certain groups of users might not be equipped to execute certain tasks on the floor. Previously, Oracle WMS Cloud did not have the functionality of assigning a user or group of users with a specific set of tasks. Any user could perform any tasks and the only way to filter for a specific set of tasks was by scanning the task type as part of EXECUTE TASK. If the tasks associated with that task type were exhausted, the system would open up the filter and the user would be eligible to execute other tasks.

You may want to configure separate Task Types so that you are only getting the tasks you need. For example, if you have the Task Type description pointing to REPLEN-LPN,CC-LOCATION-DTL, the system will filter tasks with Full LPN Replenishment type. If no tasks are determined for full LPN replenishment, then the message "no tasks found" displays. If multiple tasks are found, prioritization is performed using the current logic.

To address the need to separate tasks by user group, a new screen parameter task-type-desc-filter has been added to RF Execute Task. This parameter provides you an option to configure a valid task type description.

Note the following considerations when using the task-type-desc-filter parameter:

NOTE: There is a limit to the number of characters that can be added to the task types field. Tasks types need to be separated by a comma.

SHORTCUTS ON THE RF UI TO HONOR TASK TYPES

Some warehouse managers may need Ctrl-P (execute tasks in progress in RF Execute Task), so they can scan only the task associated with the task type(s) set in the screen parameter. Also, users may need Ctrl-T (Change Task Type) to display only the task type(s) set in the screen parameter.

The Ctrl-P and Ctrl-T RF keys have been enhanced so that they now honor the task types in task-type-desc-filter.

Steps to Enable

  1. In the Screens UI, configure the task-type-desc-filter screen parameter.

Check Permissions for Cartonize and Ship Load

Prior to this enhancement, any user (irrespective of user role) could perform cartonizing of an IB Shipment and use ship Load in the OB Load UI without any restrictions. To limit this operation, new parameters are now available where users can access these action buttons only if these parameters are enabled for the user for the respective screens.

The following are the two new parameters available:

  1. Cartonize in Shipment Detail of the IB Shipment UI: The parameter "IB Shipment / Can Cartonize" controls the access to perform the following operations in the IB Shipment Detail UI.
  1. Ship Load in OB Load UI: Ship Load in the OB Load UI now has a new Group permission "Load / Can Ship Load" that controls the access to perform Ship Load via the OB Load UI.

NOTE: The user assigned to a group needs to have the above two permission checks enabled for that group. Otherwise, the action buttons are disabled. By default, the new Group permission is disabled for user roles with SUPERVISOR, GUARD, EMPLOYEE, and MANAGEMENT.

Steps to Enable

  1. Provide the permission “IB Shipment / Can Cartonize” and “Load / Can Ship Load" permission from the corresponding Group UI. Users with employee, supervisor, and management roles who need to have these actions enabled should have the corresponding group.

Integration Enhancements

Update Module and Screen Name in REST Service APIs

Prior to this change, when calling REST Service APIs, for inventory history records that were created during the call, Oracle WMS Cloud did not record the module name or screen name. There was not a clear way to identify that transactions were done via an API call. After this change, the module name and the transaction will be recorded according to the API call. The Oracle WMS Cloud REST Service APIs can now set your module name and the transaction will be recorded according to the API being called. These values are recorded in inventory history and now have a consistent way of being set that distinguishes the invoked API.

The following are some examples of the module and screen names updated based on the called API:

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Tips And Considerations

Prior to this change, when calling REST Service APIs, for inventory history records that were created during the call, Oracle WMS Cloud did not record the module name or screen name. There was not a clear way to identify that transactions were done via an API call. After this change, the module name and the transaction will be recorded according to the API call. The Oracle WMS Cloud REST Service APIs can now set your module name and the transaction will be recorded according to the API being called. These values are recorded in inventory history and now have a consistent way of being set that distinguishes the invoked API.

The following are some examples of the module and screen names updated based on the called API:

February Maintenance Pack for 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
29 MAR 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

Honor Inventory Case/Pack Quantity During Cubing

User Experience and Usability Enhancements

Run Wave Groups

Display Configurable Facility fields in Dynamic Wave Search

Integration Enhancements

Adjust Inventory using Modify LPN API

Create OBLPN from IBLPN API

Execute Custom Inventory Summary Report API

Update Active Inventory to REST Service API

Functional Enhancements

Honor Inventory Case/Pack Quantity During Cubing

Oracle WMS Cloud has the ability to receive inventory with different case or pack qty than the item's standard case or pack qty. Prior to update 18C, Oracle WMS Cloud did not honor the inventory case/pack quantity while cubing but considered item's standard pack or case qty always when allocation was done with Cases or Packs UOM. If allocation UOM is in cases or packs then considering the right case or pack qty will result in finding the right OBLPN types.

In update 18C, cubing logic has been expanded to consider the case or pack quantity from the corresponding inventory rather than always falling back to item's standard case or standard pack qty. If case_qty or pack_qty considered during cubing is not the same as the item's standard case or pack quantity, OBLPN's weight and volume calculated will be from unit_weight/unit_volume.

NOTE: This change will reflect without any additional configurations.

Steps to Enable

No steps are required to enable this feature.

User Experience and Usability Enhancements

Run Wave Groups

Some warehouse customers may have a large and demanding supply and may have limited space for operations. In this case, warehouse may have to replenish inventory to active locations and keep these locations stocked up to fulfill picking demand. In scenarios like these where the replenishment takes place from Reserve to different active locations, the system creates picking tasks from individual wave templates and replenishment tasks are created across different waves within a wave group. This may require floor users to move from one place to another based on the tasks assigned to them. Thus, to ensure that the same reserve location is not being visited by multiple people or that floor users do not visit the location multiple times, a task creation template is now available at the wave group level. This task creation template allows allocations across different waves to be combined into one task when the system replenishes inventory from bulk/reserve locations.

This enhancement includes the following changes:

UNDO WAVE OPERATION

Steps to Enable

  1. From Modules, add a new screen to WaveGroupRunView.
  2. Navigate to the Wave Group Inquiry UI to access the View Wave Group Tasks action button.

Display Configurable Facility fields in Dynamic Wave Search

Some warehouse users may need to stop processing of orders based on the destination store status. For example,  the store you are shipping to is not ready to receive the inventory for the order because the store is undergoing audit or is currently shutdown. This enhancement adds facility-related custom fields 1 to 5 to the dynamic wave search selection criteria rules.

NOTE: the system will not automatically determine whether a store is closed or not. Appropriate values have to be passed in the available custom fields.

The system can filter orders from getting selected during wave based order values configured in the custom fields on destination, ship to facilities, or ship to companies associated with the order.

Refer to the Appendix for more details on the custom fields that have been added.

Steps to Enable

No steps are required to enable this feature.

Integration Enhancements

Adjust Inventory using Modify LPN API

Prior to this release, there were only two APIs that allowed you to adjust inventory. These APIs include Consume LPN API, which consumes a full LPN, and Adjust Active Location API, which allows you to adjust inventory in an active location. If you needed to do a partial picking using an API call, you would have to use a call to get the full LPNs information, consume the LPN, create a new one with the leftover quantity, and then locate it to the same position. This process is incredibly taxing from a processing standpoint, and it has been optimized and improved to substantially reduce the number of calls required to complete this process.

Now, Modify LPN API has been enhanced to allow adjusting of inventory. This API allows for the modification of a single item in a single IBLPN per request.  This new functionality is great for manufacturing customers that require partial consumption of inventory or 3PL customers that ship partial LPNs and have a need to perform inventory adjustments without consuming an entired LPN.

You can determine the IBLPN to be modified by using it's ID value in the URL, or by providing filter parameters in the request body. Once the API is successful, the Qty is updated (i.e the Qty is either incremented or decremented depending on the adjustment_qty provided in the API. If the item is serial nbr tracking and qty is adjusted to 0, then the system will delink the serial nbr associated with the inventory.

When an IBLPN is modified successfully, Inventory History Activity is recorded ('4 - Inventory Adjusted pre verification' or '17 - Inventory Adjusted post verification' ) depending on whether the IB Shipment from which the LPN was received is verified or not. If the LPN is not linked to any IB Shipment, it generates inventory history record '17 - Inventory Adjusted post verification.')

If the transaction_reference number is passed in Modify IBLPN API, the reference field_4  of inventory history (IHT-4 Inventory Adjusted pre verification or IHT-17 Inventory Adjusted post verification) can be used by external systems for reconciliation purposes.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Create OBLPN from IBLPN API

This new API is designed for customers that have inventory in facilities that are not currently managed by Oracle WMS Cloud. These customers would like to maintain inventory information in Oracle WMS Cloud. The Create OBLPN from IBLPN API allows you to create an OBLPN in a specific facility.The new OBLPN is created from reserve inventory and can be in a created or packed status. The caller of the API should provide information like order details to be packed and corresponding inventory (inbound LPN's) from where the inventory needs to be consumed. An optional flag is available which will update the OBLPN status to Packed.

The following are use cases the Create OBLPN from IBLPN API supports:

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .  

Key Resources

Refer to the REST API Guide for more details.

Execute Custom Inventory Summary Report API

A new API Execute Custom Inventory Summary Report API, has been added which allows you to get custom inventory summary data for a single item. The API response will include the file. This API has the same logic as Generating Standard Reports.

The following is an example of how you can use the Execute Custom Inventory Summary Report API:

.../lgf_100_qa/wms/lgfapi/v10/report/custom_inventory_summary/

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Update Active Inventory to REST Service API

Some warehouse users use the update active inventory API extensively for inventory consumption and adjustments for active locations. This enhancement converts the existing UpdateActiveInventory legacy API to a new REST Service API and adds an optional parameter to capture the transaction reference which is passed to an inventory history reference field. The legacy version of this API still remains but is not enhanced.

The following are additional changes added to the new API:

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

January Maintenance Pack for 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
29 MAR 2019 Improvements to Consume LPN API Updated document. Delivered feature in January Maintenance Pack for 18C.
22 FEB 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Integration Enhancements

GET Support for lgfapi Entities

Trailer Yard Movement API

Check in and Check out Option in Load Entity

Consume LPN API

Create Outbound Load in Input Interface

Custom Inventory Summary Report API

Enable/Disable Detail Receiving flag from IB Shipment Screen

Order Header Patch API

Improvements to Consume LPN API

Integration Enhancements

GET Support for lgfapi Entities

GET support has been added to the following entities:

GET Requests will automatically be filtered by eligible facilities and companies

Steps to Enable

No steps are required to enable this feature.

Trailer Yard Movement API

Some warehouse users may need enhanced visibility in the yard to facilitate a smoother workflow for their business process. You may have external systems or applications that manage the yard and determine when to check in the load/trailer to the dock door or yard location.

The new API Trailer Yard Movement, allows you to move trailers to and from yard locations.

API Trailer Yard Movement includes the following details:

The Trailer Yard Movement API allows you to complete the following tasks:

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Check in and Check out Option in Load Entity

Some warehouse users may need enhanced visibility in the yard to facilitate a smoother workflow for their business process. You may have external systems or applications that manage the yard and determine when to check in the load/trailer to dock door or yard location.

A new API (lgf_api) is available in the Load entity which allows you to check-in/checkout IB Loads or OB Loads to a Dock Door.

NOTE:

Using lgf_api, you can complete the following tasks:

You will need to send a Post Request for performing check in and check out.

For check in by passing load id:

For check out by passing load id

Steps to Enable

No steps are required to enable this feature.

Consume LPN API

This enhancement allows you to pass an additional field in Consume LPN API, so that it can be used for reconciliation purposes by external systems.

When WMS generates inventory history, the reference value is passed. When the reference number passed in consume LPN API is reverted back in the inventory history, external systems can use it for reconciliation purposes.

The optional parameter LPN API (lgfapi) has been added to Consume LPN API. Once Consume LPN is performed successfully, the system writes Inventory History Activity (IHT-2 Container Consumed). The transaction_reference number is passed in consume LPN API in the reference field_3 of the inventory history. This field can be used by external systems for reconciliation purposes.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Create Outbound Load in Input Interface

A new Input Interface for bringing in Outbound Load into the system is available from update 18C onwards. From 18C onwards, outbound load can be created through the Input Interface or through the Init Stage Interface API. 

Create Outbound Load includes the following details:

NOTE: for action code update, Oracle WMS Cloud only supports updating the load fields (no stop dates.)

Steps to Enable

No steps are required to enable this feature.

Key Resources

Refer to the following documents for more details:

Custom Inventory Summary Report API

The Execute Custom Inventory Summary Report API allows you to generate a custom inventory summary report and return the result set as a file attached to the response. This API has the same logic used for generating a standard report. This API has the capability to accept report parameters.

The following are some of the salient features of the Execute Custom Inventory Summary Report API:

GET .../report/custom_inventory_summary/?facility_id__code=FAC1&company_id__code=COM1&item_code=ITEM1

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Enable/Disable Detail Receiving flag from IB Shipment Screen

Previously, you could enable detailed receiving for LPNs for IB Shipments which are in “In transit” status. For example, the action buttons "Select for Dtl Recv" or "Deselect from Dtl Recv" in the IB Shipment Detail will get enabled in cases where the shipment status is in "In Transit". This new feature includes the following details:

Steps to Enable

No steps are required to enable this feature.

Order Header Patch API

The Order Header Patch API has been enhanced to support Route Number.

Allowed order statuses include:

NOTE: If there is a different status, then the API responds with an error message.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Improvements to Consume LPN API

Prior to this release, customers could use the Consume LPN API to consume an IBLPN and write an Inventory History Activity (IHT-2 Container Consumed). This API has been enhanced to send a transaction reference number field. The system writes IHT-2 once Consume LPN API is performed. If the transaction reference number is shared, it will be passed in ref_field_3 of the inventory history. This new functionality is great for manufacturing customers who use this API to consume an IBLPN, and need this information, so that this number can be used by external systems for reconciliation purposes.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

December Maintenance Pack for 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
22 FEB 2019   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

Configure Location Size Type for 3PLs

Create Single IB Shipment for Multiple Purchase Orders

View Order and Status in RF LPN Inquiry

Prompt LPN Type in RF Repack

Schedule WebReports in the Scheduled Job UI

Allow Multiple UOM in Same OBLPN

Scan LPNs Not Part of Shipment for Fully Cartonised Shipments

Consolidation and Distribution

Description Field in Ship Via / Carrier Screens

Language Column in Facility Screen

Functional Enhancements

Configure Location Size Type for 3PLs

Prior to 18C, for a 3PL set up, Directed Putaway did not pick up a empty reserve location not permanently dedicated to any item even though the location was empty, if the scanned LPN belonged to a company which was not same as company associated with the underlying location size type of the reserve location. Location was indirectly getting assigned to the child company of the associated location size type. This prevented Directed Putaway to pick up such locations for use if the incoming LPN's belonged to a different company. This could lead to not using empty spots in the warehouse.

Update 18C includes the following changes which address the above scenario:

Steps to Enable

  1. You must login with the parent company.
  2. Create reserve locations that have the location size type of the parent company. The location should not be dedicated to any company. This can be done using the location interface.
  3. You must configure distinct location size types across parent and child companies. This prevents the system from overriding the location to be dedicated to the child company.

Create Single IB Shipment for Multiple Purchase Orders

Some warehouse users may need to create a single shipment from multiple purchase orders in a single transaction. To support this scenario, this enhancement adds additional functionality to the creation of IB Shipment in the Purchase Order Screen, IB Shipment screen, and Inbound Shipment Interface file. "Create IB Shipment" button in the Purchase Order screen which allows you to create a single IB shipment for all selected and eligible Purchase Orders.

PURCHASE ORDER UI

In the Purchase Order UI, when you select multiple purchase orders and click on the "Create IB Shipment" button, Oracle WMS Cloud creates a single IB shipment for all eligible PO's. The created IB shipment has all of the eligible Purchase Order detailsOnly POs with status created whose Shipped quantity is less than the order quantity are eligible for IB Shipment creation, otherwise the system will show an error. If the IB shipment is created, you will receive a message letting you know that it was succesfull. You can select details, and this displays the purchase order details that are eligible for the Inbound Shipment Creation. You need to explicitly set the shipment type, for the IB shipment that was created from multiple PO's with a different PO type.'

PURCHASE ORDER DETAIL UI

The Create IB Shipment Option in the Purchase Order detail UI allows you to add a purchase order detail to an existing IB Shipment. Once you select the Purchase Order Detail and click on Create IB Shipment, a new window appears. This new window allows you to type a specific Inbound Shipment to Auto Generate a new Inbound shipment. You have to explicitly set the shipment type, for IB shipments created from multiple PO's with a different PO type.

INPUT INTERFACE UI

Oracle WMS Cloud allows you to process an Inbound Shipment with underlying details pointing to different Purchase Orders with the same SKU. This is available for both action codes create and update. This new feature is available for non-cartonized IB Shipments and cartonized IB Shipments. One shipment detail is created per Purchase Order.

INBOUND SHIPMENT UI USING PerformDetail RECEIVING BUTTON

Oracle WMS Cloud updates the shipment detail that points to the same SKU with multiple PO numbers. The received quantity is updated on the corresponding Purchase Order detail. An Inventory History 1 – LPN Received is split with the corresponding Purchase Orders.

Also when shipment has multiple details for same sku and pointing to same PO but different sequence number, system updates the appropriate shipment detail, and corresponding PO detail. The PO Sequence Number then displays in the Inbound Shipment detail UI.

INBOUND SHIPMENT DETAIL UI

You can now add new shipment detail having the same SKU as an existing SKU present in the shipment, but referring to a different Purchase Order. You can add a new shipment detail with the same LPN number if it is pointing to a different Purchase Order.

RECEIVING

Prior to 18C, if you received an LPN that was linked to multiple POs, the system would write inventory history record for each IB Shipment Detail and the PO Nbr field in the Inv History UI is populated with all the PO nbrs (comma separated) associated in the LPN. Now, the system will populate PO number corresponding to the shipment detail. These changes are applicable for IHT1- LPN Received and IHT72- Container Received Subject to QC[RG1] .

As we don't prompt for PO number during IBLPN receiving, system populates PO Nbr in the IHT based on the IB Shipment Detail that is been updated.

Even though one IBLPN may contain same SKU multiple POs, the system captures one PO number against the IBLPN record.

QUALITY CONTROL

Once an LPN that contains the same SKU from a different PO is accepted/rejected, the "Received Qty" for the corresponding IB Shipment Dtl pertaining to the LPN which is accepted/rejected should get updated with the quantity that is received:

IHT-73 QC Accept - is written for each Shipment Dtl in the LPN that is accepted. PO Nbr field will be populated with the corresponding PO Number

IHT-74 QC Reject - is written for each Shipment Dtl in the LPN that is rejected. PO Nbr field will be populated with the corresponding PO Number

MODIFY LPN

Oracle WMS Cloud allows the same SKU from a different Purchase Order to go into one IB Shipment and the IB shipment Detail is split based on the PO Nbr. We also support the same SKU from a different PO in one LPN. Once IBLPNs are received into the warehouse, when you modify an IBLPN before verification, the shipment details get updated and IHT - 4 - Inventory Adjusted pre-verification information is written in the Inventory History.

Once you modify an IBLPN quantity (with the same SKU pointing to different PO's), if multiple shipment details are updated, then IHT -4 "Inventory Adjusted pre verification" is written for each modified shipment detail and captures the respective PO number. This is helpful in keeping you aware of any shipment detail that is modified before an IB shipment verification.

SORT AND RECEIVE

While Sort and Receiving a shipment with an SKU with multiple POs, Oracle WMS Cloud will ignore any shipment detail that has been consumed (Received Qty>= Shipped Qty), and check for available shipment details (Received Qty<Shipped Qty)  to determine which Inbound Shipment Detail will Trigger the Sort and Receive Rules.

Steps to Enable

No steps are required to enable this feature.

View Order and Status in RF LPN Inquiry

In the warehouse, users need an option in the RF to display the order and order status associated to the OBLPN so that you do not start final processing without all of the order inventory staged. A new Ctrl Key is now available in the RF LPN Inquiry which allows you to display the Order Number and Order Status of the order(s) associated with scanned OBLPNs. You do not have to access the UI to make sure that the order has been picked. The Ctrl-O key is available in the RF LPN Inquiry. This key is available only for Outbound LPNs.

Steps to Enable

No steps are required to enable this feature.

Prompt LPN Type in RF Repack

There are  situations where warehouse packers are able to fit inventory into smaller boxes while using the RF Repack transaction. Now, you can update an LPN type and repack your inventory without having to use the control key. This functionality will make the LPN Type editable and user needs to type it. Overriding the LPN type will change the LPN Type of the TO LPN.

This enhancement adds the new parameter "prompt-lpn-type-on-packed" which has the following options:

NOTE: "prompt-lpn-type-on-packed" will NOT auto populate from the “FROM LPN”, it will not have the CTRL-U option to update the LPN Type available, and it will not show the “TO LPN” type on the first screen. You can scan all the inventory from the “FROM LPN”, and it will ask you at the end to scan the LPN Type.

Steps to Enable

Set prompt-lpn-type-on-packed to Yes

Schedule WebReports in the Scheduled Job UI

The WebReports Scheduler has been enhanced to include the option to schedule WebReports within the Scheduled Jobs screen. This enhancement allows all scheduled jobs with a “Run Web Reports” type to be linked to one WebReports configuration by specifying the report name in the Schedule Jobs screen. The formats supported are Xls., .pdf, and .csv. The documents generated are similar to the ones generated by choosing “Export PDF”, “Export CSV” or “Export xls” from within WebReports.

Steps to Enable

  1. Configure Interface Type: Web Reports on the Output Interface Configuration UI.
  2. Configure a type of schedule job for each report on the Schedule Jobs UI.

Allow Multiple UOM in Same OBLPN

Prior to 18C, during cubing, OBLPN's were created based on UOM (Units or Cases or Packs) during wave allocation. In 18C, Oracle WMS Cloud allows you to create an OBLPN with a different UOM during wave allocation. Combining multiple UOM's in one OBLPN allows you to optimize your shipping efficiencies by allowing more cubing opportunities

Steps to Enable

To create an OBLPN with different UOMs:

  1. Configure "Alloc UOM" and set the break by quantity to 0 in the Ordering criteria of the cubing rule.
  2. If you want existing functionality of an OBLPN to be created based on UOM, you should not configure "Alloc UOM" in the Ordering criteria of the cubing rule.

Scan LPNs Not Part of Shipment for Fully Cartonised Shipments

An enhancement has been added to RF Receiving that allows you to scan LPNs that are not part of a fully cartonised shipment. Earlier, if your vendor sent you a cartonized shipment, and you scanned an LPN not expected on the shipment, then Oracle WMS Cloud threw an error message.You can now scan an LPN, which is different from the anticipated LPN while receiving through RF Receiving by Shipment /Load. When you scan an unanticipated LPN, Oracle WMS Cloud displays a warning message Shipment detail doesnot have this LPN listed; you can then accept the message and proceed receiving with the unanticipated LPN. You have the flexibility to set the customized message as an error, warning, or disable the message.

NOTE: Earlier if the screen parameter “rcv-sku-not-on-shpmnt” is set to yes, system allowed to over receive the anticipated SKU and even though Over Receipt error is set as as 0% or blank.  As part of 18C, if the shipment type populated in the IB Shipment is set upwith Over Receipt erroras 0% or blank and screen parameter “rcv-sku-not-on-shpmnt”  is set to yes and the quantity entered while receiving (for the anticipated SKU in the shipment) is more than the {total shipped qty - total received qty} for the SKU, you will get an error message, and you will not be able to receive this LPN as part of this shipment. However, the system allows you to receive any quantity of the unanticipated SKU against the shipment (regardless of over receipt tolerance set in the shipment type), if the screen parameter “rcv-sku-not-on-shpmnt” is set to yes.

Steps to Enable

No steps are required to enable this feature.

Consolidation and Distribution

Enhancement made in Consolidation and Distribution to prevent merging of Inventory records in temporary LPNs after picking them from the From Location. This enhancement includes the following details:

Steps to Enable

No steps are required to enable this feature.

Description Field in Ship Via / Carrier Screens

Enhancements are added to the Ship Via and Carrier screens to so that the "Description" column is now a mandatory field. Oracle WMS Cloud does not allow you to create, edit, or save the record unless the description field is provided with a value.

Steps to Enable

No steps are required to enable this feature.

Language Column in Facility Screen

Prior to 18C, Oracle WMS Cloud the language column was available in the Facility screen. Now, in 18C, the language column is removed from the Facilities UI grid. However, this language field is still available in the database table.

Steps to Enable

No steps are required to enable this feature.

November Maintenance Pack for 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
22 FEB 2019 Order Lock/Unlock APIs Updated document. Delivered feature in November Maintenance Pack for 18C.
30 NOV 2018   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

Additional Fields in Allocation

Attribute Transfer Code

Case and Pack Quantity in OBLPN Type

Consolidate Replenishment

Divert Confirmation API

Multiple UOMs in Cubing

Receiving for Unexpected LPN's

RF Move LPN - Suppress Pallet Prompt

RF Receiving by Shipment/Load

Support for Additional UOMs for Standalone and Wave-Based Replenishment

Warning Message in Assign Load UI

Order Lock/Unlock APIs

User Experience and Usability Enhancements

Recalculate OBLPN Status in OB Container UI

Appendix

Treat as Attribute

Functional Enhancements

Additional Fields in Allocation

Update 18C includes the following new fields in the Allocation screen in the UI.

These fields are also available on the Allocation screen in the Wave Inquiry UI.

You can search the allocations based on Batch Number and Attributes (A to O) from the Allocation screen as well as from the Allocation screen in the Wave Inquiry UI.

Steps to Enable

No steps are required to enable this feature.

Attribute Transfer Code

Prior to 18C, when a Treat as Attribute was enabled on a lock code, the corresponding lock code value was updated on the inventory attribute field set up in the Treat as Attribute.

To provide flexibility, this new feature allows you to define and populate an alias value on the inventory attribute instead of displaying the lock code value.

Salient features in this enhancement include the following:

The following are additional characteristics of the “Attribute Transfer Code” field:

When Lock Code is Applied:

When Lock Code is Removed, the system nullifies the corresponding inventory attribute irrespective of the following scenarios:

Steps to Enable

  1. Navigate to Lock Code UI
  2. Populate a value in attribute transfer code column for the lock codes which has treat as attribute enabled. By default, attribute transfer code column is blank.

Case and Pack Quantity in OBLPN Type

Enhancements have been added in cubing logic so that when you are determining the OBLPN Type, Oracle WMS Cloud considers the Case/Pack quantity of the inventory (when the Allocation_UOM is Cases/Packs). Warehouses can receive inventories with different case/pack quantities. WMS has the ability to store inventories with different case/pack quantities. Case/pack quantities of the inventory will not always be same as the item's standard case/pack quantity. As such, during cubing, if inventory is allocated in cases/packs, Oracle WMS Cloud will always honor the case/pack quantity of the inventory while determining the OBLPN Type.

Steps to Enable

No steps are required to enable this feature.

Consolidate Replenishment

Prior to 18C, replenishment with consolidate and distribute flow enabled did not honor case and pack qty from the inventory. In update 18C, consolidate and distribute flows in replenishment have been modified to consider case qty or pack qty from the corresponding inventory record while allocating inventory for replenishment with the consolidate and distribute flag set to yes. As part of update 18C, Oracle WMS Cloud supports allocating inventory with the same item having different case and pack quantities.

The following enhancements are added:

NOTE: There are some cases with the "distribution-uom" parameter where allocations could be created in terms of units even though picked inventory is in cases. This depends upon the outstanding need in the destination locations being replenished.

Steps to Enable

  1. Configure the company parameter CONSIDER_ITEM_STD_UOM_QUANTITY_FLG to No if consolidate and distribute replenishment has to consider varying inventory case or pack qty.
  2. Navigate to the screen parameters for rf.inbound.cwrfpickiblpnreplen module. Set the screen parameter distribution-uom to Units if the distribution phase of replenishment is handled in units  even though the allocation was performed in cases or packs.

Divert Confirmation API

In 18C, the Divert Confirmation API has been enhanced to include Pallet Nbr. This helps MHE systems like ASRS to send pallet information to Oracle WMS Cloud after it has been diverted to a location.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Multiple UOMs in Cubing

Prior to 18C, during cubing, OBLPN's were created based on UOM (Units or Cases or Packs) during wave allocation. In 18C, Oracle WMS Cloud allows you to create an OBLPN with a different UOM during wave allocation. Combining multiple UOM's in one OBLPN allows you to optimize your shipping efficiencies by allowing more cubing opportunities.

Steps to Enable

To create an OBLPN with different UOMs:

  1. Configure "Alloc UOM" and set the break by quantity to 0 in the Ordering criteria of the cubing rule.
  2.  If you want existing functionality of an OBLPN to be created based on UOM, you should not configure "Alloc UOM" in the Ordering criteria of the cubing rule.

NOTE:

Receiving for Unexpected LPN's

There can be cases where you may need to enable detailed receiving for remaining LPNs in a shipment after you start receiving a shipment.

You can now receive unanticipated LPNs for fully cartonised shipments. The action buttons "Select for Dtl Recv" or "Deselect from Dtl Recv" will get enabled in cases where the shipment status is > In Transit.

For example, if the vendor has sent LPN01 with 50 units for SKU1 and in reality, the vendor has sent in two different boxes (LPN01- 30 units and LPN02- 20 units), with this functionality, the vendor can still receive the shipment. This new feature includes the following details:

Steps to Enable

  1. Click "Select for Dtl Recv" button to set Detail Receive Flag to True for all selected LPNs.
  2. Click "Deselect for Dtl Recv" button to set Detail Receive Flag to False for all selected LPNs.

RF Move LPN - Suppress Pallet Prompt

In 18C, the pallet prompt on the RF Move LPN screen has been made optional.  This enhancement is useful when a single LPN is being handled as a part of a Full LPN Replenishment task.  You can pick up the LPN, with a single scan of the LPN, versus scanning both the LPN and a pallet on which it is picked.  It also helps save a pallet label.

A new screen parameter to-plt-display-behavior is used to control the behavior of pallet prompt:

Steps to Enable

  1. Configure the to-plt-display-behaviour screen parameter by upgrading to the new release.
  2. Go to RF Move LPN screen -> to-plt-display-behaviour.
  3. Choose the module parm choice (Pallet prompt mandatory or Skip pallet prompt for single LPN task).

RF Receiving by Shipment/Load

Prior to 18C, if a shipment was fully cartonised and you scanned an LPN which was not on the shipment, then Oracle WMS Cloud threw an error message. In the warehouse, we might not have received the anticipated LPN, or the vendor might have sent same SKU's in a different LPN. In these scenarios, we are not able to receive such LPNs through the RF.

In 18C, you can scan an LPN, which is different from the anticipated LPN while receiving through RF Recv by Shipment /Load. When you scan an unanticipated LPN, Oracle WMS Cloud displays a warning message; you can accept the message if you want to proceed receiving with the unanticipated LPN. You have the flexibility to set the message as an error or warning or disable the message. By default, if you scan an unanticipated LPN, Oracle WMS Cloud displays a warning alert.

Steps to Enable

No steps are required to enable this feature.

Support for Additional UOMs for Standalone and Wave-Based Replenishment

The Replenishment for Standalone (Lean-Time) is accomplished by pushing inventories from one place to another without creating any picking allocation against an order creation. The standalone replenishment is run based on the configuration in the replenishment template. Whereas, in wave-based replenishment, the system first runs the picking allocation based on the anticipated inventories and then creates a replenishment task.

The following are the general enhancements for replenishment:

NOTE: Replenishment with UOM for Packs and Units is supported for Reserve to Active locations. However, if allocation location type is Active to Active or Active to Reserve, then the system sets the Replenishment with UOM to Units only.

Prior to 18C, the Capacity Check Method was supported only in wave-based replenishment. In the current enhancement, the standalone replenishment rule is expanded to support Capacity Check Method for Units and Volume, and fall back to Units.

Previously, we supported the Ignore Order Details Attribute List in the Wave template that helped you to provide instructions to the system on which attribute to ignore when the wave was run. We have introduced the same function in 18C by adding a new field Ignore Order Details Attribute List, in the Replenishment Rule.

NOTE: If the Replenishment Rule is configured to ignore an attribute and meanwhile, if a wave is strict about the attribute, then replenishment with picking waves does not occur.

The following are the features of the new field Ignore Order Details Attribute List:

Steps to Enable

To Consider or Ignore Inventory Attributes for standalone or wave-based replenishment

  1. Open Replenishment Template
  2. Navigate to Replenishment Rule from replenishment template
  3. Populate the ignore order attribute list with the relevant attributes which needs to be ignored.

To add support of replenishment in terms of units or pack

  1. Open Replenishment Template
  2. Navigate to Replenishment Rule from replenishment template
  3. Navigate to replenishment rule sequence.
  4. Create a rule sequence with UOM of units or packs.

Warning Message in Assign Load UI

Update 18C includes an enhancement made in the OB Load screen. When you try to assign an OBLPN to a load through the "Add LPN on Stop" screen; Oracle WMS Cloud displays a warning message and requests for a confirmation in the following cases:

The “Add LPNs to Stop” screen in the OB Load UI includes the following new fields in the data grid:

Steps to Enable

No steps are required to enable this feature.

Order Lock/Unlock APIs

There may be scenarios where you may need to hold an order line, for example, due to a credit check for the order or payment hold etc. Now, you have the ability to lock or unlock an Order via REST APIs. If you lock an Order, Oracle WMS Cloud prevents the order line from getting processed for downstream operations like allocation, pick, and pack.

You can apply locks to multiple Orders in the same request. After the locks are applied, you can see them in the Order UI. You will need to send a POST Request. The following is an example URL for this request:

.../entity/order_hdr/bulk_lock

If your lock code has the allocatable_flg set to NO, Oracle WMS Cloud prevents allocation from the following modules:

ORDER UNLOCK APIS

Some shipping managers may need the option to unlock or release a hold on the order. Sometimes Order Management can lock or put an order on hold. When this happens, Inventory Shipping will make an API call to update the lock on the Order. When the order lock is supposed to be removed, Inventory shipping makes an API call to remove the order lock or order hold.

After the orders are unlocked, if the lock contained an allocatable_flg set to No you will be able to allocate these Orders.

You will need to send a POST Request. The following is an example URL for this request:

POST .../entity/order_hdr/bulk_unlock

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

For more details regarding the API invocation and parameters please refer to our Rest API Guide.

User Experience and Usability Enhancements

Recalculate OBLPN Status in OB Container UI

In various material handling, warehouse managers may have a need to recalculate an OBLPN status.

A new action button, Recalculate OBLPN Status, is now available in the OB Container View UI. This button allows you to update an OBLPN’s status from an “In Packing” to “Packed” status.

There are some configurations which will automatically end an OBLPN and set it to pack when picks are completed. Some configurations don't automatically end the OBLPN and leave it to the user to complete manually.

Some examples of when you might use this button include the following:

NOTE: You should only use this button if you know for sure picking for the OBLPN is in fact complete and you know for sure you want the OBLPNs status to be Packed.

Steps to Enable

From the OB Container View UI, click Recalculate OBLPN Status and update the status from “In Packing” to “Packed.”

Appendix

Treat as Attribute

Certain business operations want to ship inventories with specific lock codes from the facility. To achieve this, clients interface Orders with the lock code value in the particular Inventory Attribute column. You should have lock code values applied in IBLPN or Active Inventory for Oracle WMS Cloud to allocate the inventory when running waves.Treat as Attribute functionality in the Lock Code UI helps to copy the Lock Code value to the Inventory Attribute field when locks are applied to IBLPN/Active Inventory.

October Maintenance Pack for 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
27 NOV 2018   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

Cubed Together Flag

LPN Substitution in RF Pack NC Active

Over-Replenishment for Active Locations

Wave Group

User Experience and Usability Enhancements

Custom Reference Text in Trailer UI

IB LPN Inquiry

Functional Enhancements

Cubed Together Flag

Cubing is the process of grouping inventory into outbound containers based on the maximum volume and maximum weight defined at the container type level. The computation of volume and weight is based on the items/weight/volume dimensions defined at the item's appropriate UOM level. The cubing rules feature allows customers to define how cubing should take place. It is based on various breaking criteria such as weight, volume, and other item attributes within the max volume and max weight limits. This feature now introduces an additional flag, Cubed together flag, in the ordering criteria for the cubing rules.

This flag allows you to group inventory within the container. In other words, if your ordering criteria is set to Order dtl cust field 1 and the flag cubed together is set to yes, all the order details for the unique order dtl cust field 1 will be in the same box without being limited by break by count. For example, your order is for a school and you are saving the class id in the Order dtl cust field 1, and you have the cubed together flag set to yes. If the complete class will fit in a box, all contents for that class will allocate to one box. If another class's contents can completely fit in the same box, then WMS will add the class contents to this box. However, if a complete class cannot fit into a box, it will get a full box and it's remaining items can still be combined with other classes that can fit completely in that box. This will reduce the occurrence of classes getting spread out and mixing with other classes.

Steps to Enable

To enable Cubing together order lines based on grouping criteria:

  1. Navigate to Ordering Criteria section of cubing rules.
  2. Enable the Cube together flag for the column which is part of the ordering criteria.
  3. Enable the Cube together flag for the column which is part of the ordering criteria.

LPN Substitution in RF Pack NC Active

In 18C, you are able to substitute an LPN even if the batch or expire date doesn't match. This new feature gives more flexibility to customers that want to allow users to substitute inventory while using the RF Pack NC Active. A new parameter “req-lpn-sub-validations” is available  that allows you to substitute an LPN based on the validation rule set in the screen parameter, even if the batch number or expiry date does not match with the allocated LPN.

The available validation rules include the following:

NOTE: The substitution of LPN for inventory applies only for Reserve pick. When the company parameter ORD_DTL_BLANK_BATCH_NBR_IS_WILDCARD is set to Yes or No, the LPN substitution screen parameter takes precedence and validates the substitution of an LPN in the following scenarios:

Steps to Enable

To enable the substitution functionality with the validation rule:

  1. Configure the req-lpn-sub-validations by upgrading to the new release.
  2. Go to Pack NC Active screen > req-lpn-sub-validations
  3. Choose the module parm choice (All, Batch, Expiry and None).

Over-Replenishment for Active Locations

Some clients may have picking locations (active locations) that cannot accommodate the orders need or the incoming inventory from one or more reserve locations. Quantity that can be replenished to the location is limited to the corresponding pick locations maximum units defined. Customers may want to push the inventory to the destination active locations in increments. Update 18C now allows customers to be able to replenish beyond configured location's max and provides an ability to replenish inventory going through multiple hops into corresponding destination locations using new RF Module.

REPLENISH BEYOND LOCATION'S MAX

NEW RF MODULE TO PICK INVENTORY FROM DROP LOCATIONS

The new RF Module "rf.inbound.cwrfmultistepreplen" does the following:

The following are the different screen parameters added to the new module:

NOTE: A wave might have created a full LPN replenishment task to be picked from an initial source location to the final destination location. In this case you need to drop the allocated LPN using wave generated task to move inventory to the initial drop location. From the drop location, you can use "rf.inbound.cwrfmultistepreplen"  for systematic movement of inventory to the final destination locations.

Steps to Enable

To enable wave-based replenishment to replenish beyond location’s max

  1. Navigate to Replenishment rule associated with the picking wave template
  2. Enable the Ignore Capacity for Last Permanent Location flag(if the destination location has candidate permanent location for the sku and if order need is more than candidate location max then perform replenishment up to need.

Wave Group

Prior to 18C, multiple wave templates could be chained together to be running one after the other using wave groups. Wave groups provide a mechanism to associate multiple wave templates. Each wave runs on its own and once the first wave is completed, Oracle WMS Cloud invokes the second wave as per the sequence configured on the wave group. Each wave creates tasks independently. As tasks are created independently, there could be chances of replenishment happening from similar source locations across different waves. If separate tasks are created, there could be chances of traffic in the pick areas. Update 18C addresses this issue and the following are some of the salient features added to enhance wave group functionality:

Steps to Enable

To enable configuration of Task creation at wave group level.

  1. Navigate to Wave group Inquiry Screen.
  2. Associate Task creation template in wave group screen.

User Experience and Usability Enhancements

Custom Reference Text in Trailer UI

A new Custom Reference Text field is introduced in the Trailer UI. This field gives you the flexibility to capture additional trailer information. This field is also made available in the Appointment UI.

Some of the characteristics of the custom field are:

A new read-only Custom Reference Text field is added to the data-grid of the ObViewLoad UI. This custom field displays the value entered in the Custom Reference Text field of Trailer UI.

Steps to Enable

No steps are required to enable this feature.

IB LPN Inquiry

In some cases you may want to prevent edit batch number in order to maintain data integrity. A new screen parameter is available in the IbContainerView screen that restricts all users from modifying the batch number for batch tracking inventory.

The UI parameter “allow_edit_batch_nbr” is configured in the IbContainerView with the following options:

NOTE: This enhancement is applicable for inventory tracking batch. For a non-batch tracking inventory, Oracle WMS Cloud displays an error “Item does not track batch or expiry” when you attempt to modify the batch number in the IBLPN.

Steps to Enable

In the IbContainerView, set the “allows_edit_batch_nbr” parameter to No.

Update 18C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes
29 MAR 2019 APPENDIX Updated document. Added Dynamic Wave Search Criteria.
31 AUG 2018   Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Action Required to Enable Feature

Feature

Automatically Available

End User Action Required

Administrator Action Required

Oracle Service Request Required

Functional Enhancements

RF Receiving

RF Print Item Label

Printer Selection

Return Facility on Inbound Shipment

Pack with Wave

Enable / Disable Company Flag

Priority Date Traceability

Additional Carrier Type Support

Inbound Shipment View

Lock Codes on Inbound Shipments

Reference LPN Number Display

Oracle Cloud Migration

Update Route Number for Multiple Orders

Oracle SCM Cloud Execution

Load Assignments for Orders Planned by OTM

Close Load

Reset External Planned Load Number from Order Header Browser UI

Integration Enhancements

Outbound LPN Shipping Info Triggered at Status Change

Generate Outbound LPN Info upon Manifest

Generate Order Export at Order Packed

XML Support for Additional Input Interfaces

Expanded Selection Criteria in Output Interface

FedEx International Shipment

Output File Target Selection

Item Master Protected Fields

Rearrangement of XLS File Format for Route Input Interface

Include Printer in Outbound LPN Shipping Info

Auto Process Inventory History Records

Oracle SCM Cloud Integration

Changes to Planned OB Load Interface

New logic for Loading API

REST API

Create LPN API

Update Custom Fields for Current lgfapi REST API

New API to Bulk Update Inventory Attributes

User Experience and Usability Enhancements

RF Screen Layout Realignment

Oracle WMS BI Cloud Reports

Improved Literal Localization

Improved Time Zone Localization

Yard Management Improvements

Oracle WMS BI Cloud Framework

Order Detail Level Permissions

Document Design and Printing

Price Label Support with Label Designer

Case and Pack Labels Using Label Designer

OBLPN Number Labeling and Printing

APPENDIX

Functional Enhancements

RF Receiving

The following screen parameters have been added to both “Receive by Load” and “Receive by Shipment” modules that provide additional flexibility during receiving:

  1. LPN Prompt: Using this new screen parameter, the LPN Prompt is now made optional and blind LPNs can be received without explicitly scanning the LPN numbers. This parameter can be configured with the following Parameter choices None, Mandatory, Not mandatory, or Auto Generate.  When the screen parameter is configured to None or Not mandatory, and you do not scan the LPN number, then Oracle WMS Cloud automatically generates LPN numbers during receiving. With this change, you do not need to print blind labels upfront. Your warehouse should ensure that all the users have operational controls on matching the labels printed with LPNs received, when multiple people are receiving and printing LPNs to the same printer.
  2. Prompt Location: This screen parameter can be configured to None, Do not prompt, Prompt if not known after receiving is complete. Support is added to locate inventory directly to an active location as long as the module is not configured for palletized receiving.
  3. Print Labels: This screen parameter provides an option to print None, Inbound LPN Label, UOM Case Label, UOM Pack Label, LPN Label and UOM Case Label after receiving is complete. When this parameter is configured, the RF option displays the Ctrl P key to capture printer information of the session. 

NOTE: Inbound LPN Labels/Case/Pack label print requests are routed to the printers using Ctrl P key. If not overridden, the request is routed to the default label printer attached to the user.

  1. Prompt Dock Door: This screen parameter can be configured to None, Prompt or Do Not Prompt
  2. Prompt Trailer: This screen parameter can be configured to None, Prompt, Do Not Prompt
  3. Confirm-uom-qty: This screen parameter can be configured to None, Do Not Prompt or Prompt per Sku per LPN. If this parameter is configured to Prompt per Sku per LPN and the receiving UOM is configure to “Packs or Cases”, users are prompted for Pack or Case quantity. You have an option to override the item’s standard pack or case quantity for each LPN Received. This mode is useful for items in which the vendor does not have a pattern to the case or pack quantity. If this parameter is configured as “Do Not Prompt”, you can use control Ctrl Q key to change the Case or Pack quantity.

Steps to Enable

Enable the following screen parameters:

RF Print Item Label

A new transaction “RF Print Item Label” allows you to print item labels through an RF device. You have an option to scan the printer, item, and number of labels to be printed. If you want to print through a default printer, you can tab through the printer prompts and the system will automatically accept your defined default printer for printing the labels.

Steps to Enable

No steps are required to enable this feature.

Printer Selection

In 18C, the following enhancements are added for label printing:

Steps to Enable

Set the "Default document printer" in the User screen or User Interface

Return Facility on Inbound Shipment

Oracle WMS Cloud provides an option to capture facility information for return shipments.  An advanced look-up option is introduced in the Create/Edit pane of the Inbound Shipment UI. You can now look-up Inbound Shipments by selecting the Return From Facility Code and/or Return From Facility Type. This allows you to find faster return shipments.

To facilitate this feature, a new flag called Capture Returns Information is now available on Shipment Type. This flag needs to be set to Yes for Shipment Type used for return shipments.

The Inbound Shipment interface is enhanced to accommodate return facility information in the input file/message. Oracle WMS Cloud validates to ensure that the shipment type used on such  shipments has the Capture Returns Information flag set to Yes.

Oracle WMS Cloud also includes return facility information on Transfer Shipments depending on the Shipment Type determined for a transfer shipment.

When a return shipment is verified, the return facility information is included in the Shipment Verification file.

Steps to Enable

  1. Set Capture Returns Information flag to Yes on the Shipment Type used to returned shipments.
  2. Add returned_from_facility_code on the IB_Shipment Interface File

Pack with Wave

Some warehouses need to pack large volumes of brochures and mail-out catalogs to be shipped out for customers without being too concerned about inventory accuracy or tracking inventory. In these cases, you could skip the picking process in Oracle WMS Cloud for such items and the picking is done outside of the WMS system.

In order to facilitate this requirement, "Pack with Wave" has been introduced for dummy sku items. The following enhancements have been added:

ITEM MASTER 

The following enhancements provide item level support for "Pack with Wave" functionality:

WAVE TEMPLATE 

’Pack with Wave' is added in the create/edit/copy pane of the Wave Template UI.

NOTE: Pack with Wave is not supported along with Replenishment with picking wave. Support for performing pack with wave will be done for items which are marked dummy and items which have 'pack_with_wave_flg' enabled at item level.

Pack with Wave is added if the wave template is set as the following:

After that, the system creates outbound LPN’s which are in Packed status and the order status is calculated accordingly. Oracle WMS Cloud will perform load assignment or manifesting for the Outbound LPN’s created. The application can cube multiple sku's in same OBLPN. If any of the items in the determined outbound LPN are not marked dummy or if items are marked dummy but not eligible for pack with wave, then the corresponding outbound LPN will not be subjected to Packing Steps (All items on the cubed outbound LPN should have dummy_sku_flg set to yes and have 'pack_with_wave_flg' set to yes).

WAVE INQUIRY

Sometimes, you might want to perform pick and pack updates outside of a wave as you might need to watch the allocations as part of a wave run. The “Undo Wave” option will not undo/cancel pick and pack updates.

If you want to perform Pick and Pack updates after the wave is run, a new button ‘Autopack Wave OBLPNs' is added to the Wave Inquiry UI where you can select the wave and perform Pick and Pack (applicable for dummy sku items only).

NOTE: The ‘Auto-Pack Wave OBLPNs’ button will be enabled only if the selected wave's run status is Completed, Not Fully Allocated or Completed.

Steps to Enable

  1. Set the Pack with wave flg to Yes for the “Dummy” Items. This could be done on the Item UI or Item Interface.
  2. Set the Pack with wave flg to Yes on the Wave Template.

Enable / Disable Company Flag

This new feature allows you to deactivate the company when it is no longer required or it is out of business.

In order to facilitate this requirement, the following enhancements are added:

NOTE: Parent company cannot be deactivated using the new button from the company UI.

Steps to Enable

  1. Select the “Activate/Deactivate” button on the Company Screen.
  2. Add the permission "Deactivate/Activate Company."

Priority Date Traceability

During Receiving or LPN creation, the priority date on the inventory is updated with either the expiry date for expiry tracked items and the manufacturing date or the create time stamp. The Allocation Method for FEFO uses the Priority date for the inventory. When the inventory is transferred to another facility, the priority date from the outbound LPN is not copied to Inbound LPN’s, which potentially creates discrepancies in pushing inventory in a FIFO manner. In order to address this scenario, the following enhancements have been added:

Upon performing RF Modify Cancel OBLPN, the Priority date is copied from an Outbound LPN to the Inbound LPN that was created. Prior to 18C, the Inbound LPN’s created from RF Modify LPN would have create_ts populated as the Priority date.

If an Inbound Shipment received has the Priority Date populated, this information is passed on to the corresponding priority date on the Inbound LPN Inventory. Even if items are tracking expiry date, priority_date from an Inbound Shipment detail is considered. Updates in 18C include the option to transfer the Priority Date from the shipped LPN to the received LPN. Customers can now adhere to FIFO without having to use Expiration Dates reducing spoilage and obsolescence in the Supply Chain. To adhere to FEFO, users should leave the Priority Date blank.

NOTE: Existing clients that track expiry dates should ensure that Inbound Shipment detail does not have Priority Date populated.

Steps to Enable

No steps are required to enable this feature.

Additional Carrier Type Support

In update 18C, additional carrier types "AIR, "OCEAN", and "RAIL" are available. 

If the carrier type is "AIR, "OCEAN", or "RAIL", Oracle WMS Cloud will accept the load assignment logic. When a load is assigned in Oracle WMS Cloud, the system considers the carrier types as "AIR, "OCEAN" and "RAIL" apart from LTL/TL.

Steps to Enable

No steps are required to enable this feature.

Inbound Shipment View

Oracle WMS Cloud users may often use the ref_nbr on IB Shipment to map their internal shipment reference numbers to the Inbound Shipments in Oracle WMS Cloud. In order to enable clients to view this field on Inbound Shipment, ref_nbr is exposed on Inbound Shipment View.

Steps to Enable

No steps are required to enable this feature.

Lock Codes on Inbound Shipments

Currently, Oracle WMS Cloud allows transfer of inventory between facilities as long as these facilities have the correct configuration. In18C, an option is provided to transfer Lock Codes from Outbound shipment to the destination facility. This enhancement allows customers using Lock Codes on inventory to share information across facilities. Sharing this Lock Code information allows traceability across facilities, which provides accuracy to the shipping process of the company. This functionality will only transfer lock codes that have the Copy to Transfer Shipment flag set to Yes on the Lock UI.

In 18C, a new button, “View IB Shipment Container Lock”, is added to the Inbound Shipment UI. A new UI  allows you to view the Lock Codes available for LPNs from cartonized Inbound Shipments. You can also add Lock Codes to LPNs from cartonized Inbound Shipments.

Steps to Enable

Set the Copy to Transfer Shipment flag to Yes on the Lock Code Screen.

Reference LPN Number Display

The container record has the reference LPN number used to store the parent LPN from which the inbound LPN is created. The reference LPN number also has a corresponding Inbound LPN number when you perform full LPN allocations. In 18C, a reference LPN number column is exposed in Inbound LPN Inquiry and Outbound LPN Inquiry.

Steps to Enable

Add the reference_lpn_number from the Add/Remove column option if it is required to display on the datagrid.

Oracle Cloud Migration

Update 18C introduces support for Oracle Cloud Infrastructure (OCI), the latest version of the Oracle Cloud. New customers are provisioned on OCI. Existing customer production environments will be migrated at a later point. In other words, the 18C update and OCI migration will be separate events. Some technical details such as URLs may change for existing customers. Details will be provided to customers once update dates are finalized.

Steps to Enable

No steps are required to enable this feature.

Update Route Number for Multiple Orders

Oracle WMS Cloud allows you to update the Route of multiple orders from the Order Header UI.

The following enhancements have been added:

Steps to Enable

Add the permission "Set Route."

Oracle SCM Cloud Execution

Load Assignments for Orders Planned by OTM

Oracle WMS Cloud can receive the planned load information for the order from OTM (or other transportation management systems) and receive it as an Outbound Load. In version 9.0.0, the externally planned load flag was exposed on the order input interface. This flag informs that the particular order is going to be planned by an external system. The external system can interface at a later stage, after the transportation management system has planned the external planned load number. In update 18C, the following functionality enhancements have been added:

NEW LOAD ASSIGNMENT LOGIC

Oracle WMS Cloud has a new load assignment logic. It will prevent assigning an OBLPN if it has Orders that have the external planned load flag set to Yes, and if the external load number is blank. This new logic affects the following modules:

NOTE: By default, the alert will be a warning message. This message can be set as an Error/Warning or they can be turned off.

Steps to Enable

The externally planned load flag should be set to yes.

Close Load

Prior to 18C, when users performed close load from the UI or the RF; Oracle WMS Cloud did not show any indication of remaining orders that were planned for the load which has an external planned load number populated. So, the user would close the load without knowing that there were pending orders for the OTM’s planned load.

In 18C, when you perform Close Load from the RF/UI, you will receive a warning if there are pending orders or OBLPNs planned for an external load associated with the load being closed or shipped.

Alerts in the RF are configurable as Error, Warning (default), or they can be turned off. However, an alert in the UI is always a warning.

NOTE: The message will be applicable only if the selected load has external planned load number populated and if there are any Orders/OBLPNs planned for the same external planned load and are not loaded yet.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

By default, alert messages are set as Warnings. Users can modify or change these alerts to an Error message.

Reset External Planned Load Number from Order Header Browser UI

Earlier, an option to clear an external planned load number on Order detail from the UI was not available. In 18C, a new button “Reset Externally Planned Load Nbr” is available from the Order Header UI > Order Detail View. This action button is permission controlled; only those with permissions can perform resetting of an externally Planned Load Nbr. This button will help to clear external planned load number from order detail.

To perform reset of externally planned load number, you can:

  1. Select the Order and go to Order Detail.
  2. Select the required order detail and click Reset Externally Planned Load Nbr. 
  3. The order details that are in the status "Created", "Partly Allocated", "Allocated", “In Picking”, “Picked”, “In Packing” and “Packed” are eligible for update.

The order details which are packed and assigned to the load, by nullifying the external planned load number will not unassign the OBLPN from the assigned load. Oracle WMS Cloud issues an error message when the selected order detail is fully loaded/shipped. Whenever a reset of the externally planned load nbr is performed using the Reset Externally Planned Load Nbr action button, a corresponding log is written in the Application Logs.

Steps to Enable

Add a new permission to Reset Externally Planned Load Nbr.

Integration Enhancements

Outbound LPN Shipping Info Triggered at Status Change

Prior to 18C, customers were only able to send the "container ship load file" (LLS) when an LPN went to Packed status. This was possible only if the company parameter "LLS_AT_LPN_PACKED" was set to Yes.

In 18C, the company parameter "LLS_AT_LPN_PACKED" is renamed to “FILES_TO_GENERATE_AT_LPN_PACKED”. This change gives customers the flexibility to generate the following files when an LPN goes to Packed status:

The format of the OBLPN shipping information file will be based on the set up of the file in the output interface configuration UI.

NOTE: For customers having configuration LLS_AT_LPN_PACKED as ‘Y’ or ‘y’, the FILES_TO_GENERATE_AT_LPN_PACKED parameter will be configured as ‘LLS’, when they are migrated to 18C.

Steps to Enable

Change the value on the Company Parameter FILES_TO_GENERATE_AT_LPN_PACKED.

Generate Outbound LPN Info upon Manifest

Prior to 18C, to successfully Manifest the OBLPN (Outbound LPN) in the UI, you needed to select the existing button "Send OBLPN Info". Update 18C allows both actions to be completed by clicking Manifest OBLPN. A new screen parameter has been added to the OBLPN Inquiry screen "gen_oblpn_shipping_info". A default set to No, and a parameter value of Yes will generate the OBLPN Info file after you click Manifest OBLPN. This enhancement improves the efficiency of this process, and it prevents mistakes.

Steps to Enable

Change the screen parameter value on OBLPN Inquiry Screen "gen_oblpn_shipping_info".

Generate Order Export at Order Packed

A new company parameter, FILES_TO_GENERATE_AT_ORDER_PACKED is now available for the PLS file when an Order goes to Packed Status. You can configure this parameter with the values PLS, PBL, PBS, and PLP. When any of these values are set, an Order Outbound Load Export file is generated when an Order goes to packed status.

The format of the Order Outbound Load Export file is based on the output interface configuration set up. For example, if the FILES_TO_GENERATE_AT_ORDER_PACKED value is PLP, and your output interface configuration is set up to generate in XML, then the file that is generated at order packed will be Order Outbound Load Export in XML format.

Steps to Enable

Configure Company Parameter FILES_TO_GENERATE_AT_ORDER_PACKED to generate the Order Verification file with one of the following values:

XML Support for Additional Input Interfaces

Update 18C enables Web Service support and XML support for the following input interfaces:

Steps to Enable

No steps are required to enable this feature.

Expanded Selection Criteria in Output Interface

External order management systems that send orders to Oracle WMS Cloud typically keep track of order status by subscribing to IHT-20 (Order Status Change). Additional IHT records like IHT-10 (Container Detail Packed) and IHT-11 (Container Packed) provide detailed information during pick and pack. To ensure that only data specific to the Orders sent by such systems is filtered and sent back, a new filter for Order Type has been added to the Output Interface Configuration for Inventory History. 

Other commonly used entities have also been added to the selection criteria (filter) for Inventory History in the Output Interface Configuration as listed below:

Steps to Enable

No steps are required to enable this feature.

FedEx International Shipment

In update 18C, the built-in integration to FedEx International Shipments now allows the support of Commercial Invoices. This new enhancement will send the required information to FedEx, so FedEx can generate the Commercial Invoice. Oracle WMS Cloud will make the direct web service call to FedEx if the destination country is other than the US, and if the standard carrier accessorial in the Ship Via detail is either FedEx Express or FedEx Freight. Paper Invoices are not supported in this enhancement. FedEx will be able to generate the electronic commercial invoice, and Oracle WMS Cloud will not hold any information about the generated Commercial Invoice.

Steps to Enable

Change the ship via accessorial to INTL_ELECTRONIC_COMMERICAL_INVOICE.

Output File Target Selection

CHANGE IN TIME ZONE CODE IN INTERFACE 

Update 18C includes the time zone code for the facility where the load is shipped out from WMS in the following interfaces:

DISTRIBUTION MHE INTERFACE BACKWARD COMPATIBILITY 

In update 18C, new facility and company parameters are added to the "TO_MHE_DISTRIBUTION_INFO" and "TO_MHE_IBLPN_INFO" output interfaces to support backward compatibility. These two interfaces expose additional inventory attributes.

If the value is configured as lgf or blank, then the latest version or current version is considered. Oracle WMS Cloud will look at the company parameter at the child company level first and then at the corresponding parent company level. If both parameters are not configured, then the facility parameter value determines the fields for the relevant version.

NOTE: This change is introduced in version 9.0.0 as well.

Steps to Enable

  1. Change Company or Facility parameter OUTPUT_LGF_FINFO_TO_MHE_DISTRIBUTION_INFO.
  2. Change Company or Facility parameter OUTPUT_LGF_FINFO_TO_MHE_IBLPN_INFO.

Item Master Protected Fields

Update 18C allows you to configure the following item fields in the Interface Protected Fields UI:

Steps to Enable

Select the desired fields to protect in the Interface Protected Fields UI

Tips And Considerations

If a field is configured as protected, Oracle WMS Cloud will prevent the item from being updated from the Host/External System.

Rearrangement of XLS File Format for Route Input Interface

The column positioning for the Route XLS file format is changed. Please refer to the latest Interface Specification documentation for the latest format.

Steps to Enable

Map the latest Route XLS from the Interface Specification documentation.

Include Printer in Outbound LPN Shipping Info

Update 18C introduces the new columns "printer_type" and "printer_name" in the OBLPN_Shipping_Info and Pallet_Shipping_Info interfaces. Some customers use information from these two interfaces to be shared with an external printing systems for printing shipping labels or packing slips. If external systems are using these interfaces to print labels or packing slips, it will be useful to send the actual printer name in the OBLPN_Shipping_Info and Pallet_Shipping_Info where the documents need to be printed. The actual printer where the document needs to be printed will be selected by the end user who is generating the file.

In update 18C, when you click the Generate Shipping Info action button from Wave Inquiry or Outbound LPN Inquiry, Oracle WMS Cloud displays a pop-up screen with a drop-down list containing entries for the associated printer type and printer name. The selected printer type and printer name is shared in the OBLPN_Shipping Info file. You will have an option to select the printer name. Customers updating to 18C will see that Oracle WMS Cloud prompts for a pop-up screen where you are presented with an option to select a label or document printer.

In update 18C, from Pallet Inquiry, when you click the Generate Pallet Shipping Info action button, Oracle WMS Cloud displays a pop-up screen where you can select either a label or document printer. The selected printer type and printer name is shared in the Pallet Shipping Info file. You have an option to select a printer name. Those updating to 18C will see that Oracle WMS Cloud prompts for a pop-up screen where you are presented an option to select a label or document printer while you are generating pallet shipping Info.

Steps to Enable

No steps are required to enable this feature.

Tips And Considerations

Refer to the Interface specifications for update 18C to see the fields added to the OBLPN_Shipping_Info and Pallet_Shipping_Info interfaces.

Auto Process Inventory History Records

Oracle WMS Cloud now provides the option to auto process inventory records for a particular activity type, which clients do not necessarily consume. This is so that they can become eligible for purges and can be cleaned up whenever the scheduled purge is executed.

In order to facilitate this requirement, the following enhancements have been added:

Steps to Enable

Add the permission "Change inventory history activity parm."

Oracle SCM Cloud Integration

Changes to Planned OB Load Interface

Update 18C includes new fields in the Planned OB Load interface and changes in logic for searching relevant order detail(s) based on the new fields in the Planned OB Load.

The following fields are available in the Planned OB Load interface: 

Prior to 18C, the following fields were mandatory in the Planned OB Load interface. As part of 18C, the following fields are now non-mandatory:

New logic has been added for searching relevant order detail(s) based on the new fields in the Planned OB Load:

In 18C, we have introduced the following changes to associate a planned OB Load:

Steps to Enable

No steps are required to enable this feature.

New logic for Loading API

For a better integration with OTM, a change to Load Assignment Logic using the Assign OBLPN to Load API has been added. This change prevents the assignment of loads for orders that are expected to be assigned by OTM. If the OBLPN contains an order that is marked for external load planning, Oracle WMS Cloud prevents updates on such OBLPNs. Oracle WMS Cloud also prevents updates, when you try to assign another load that it is different from the load expected by the external system.

Steps to Enable

The externally planned load flag should be set to Yes.

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

REST API

Create LPN API

Version 9.0.0 introduced a new set of APIs that follow REST standards to create entities. You can create an LPN using the new lgfapi REST API. With the Create LPN API, you can create an LPN by making a separate request for each entity as part of the LPNs such as iblpn, Inventory, batch, or attributes. In update 18C, a new lgfapi REST API, composite_create, is introduced to create an LPN. This new API optimizes the creation of an LPN by reducing the number of requests sent to the external system to just one request.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

Update Custom Fields for Current lgfapi REST API

Update 18C allows you to update the Custom fields on the existing lgfapi entities. This is possible using the verb “PATCH”. Custom fields are informational fields and pass-through data is provided by the customers without any associated business logic. You can update these fields with minimal restriction at your discretion using lgfapi. This update currently supports "cust" field(s) only on a single resource per request in "retrieve" mode.

Steps to Enable

Review the REST API guide to leverage (available from the Oracle Help Center > your apps service area of interest > REST API) .

Key Resources

Refer to the REST API Guide for more details.

New API to Bulk Update Inventory Attributes

In version 9.0.0, a new functionality is added to the IB Container screen to allow you to bulk update IBLPN inventory attributes. Update 18C has expanded this functionality by adding a new lgfapi REST API, bulk_update_inventory_attributes. This new API, which acts on the inventory entity, allows updating the inventory attributes for inventory in IBLPNs as well as active locations.

Steps to Enable

No steps are required to enable this feature.

User Experience and Usability Enhancements

RF Screen Layout Realignment

Currently, Oracle WMS Cloud supports decimal numbers in the application. You can enter decimals in the UI and in the RF. Update 18C includes enhanced RF screen layouts to display better information to the user. RF screens are realigned. This new display positioning will make it easier and faster for you to read and process the displayed information. This change allows you to scroll through the quantity entry field.

Steps to Enable

No steps are required to enable this feature.

Oracle WMS BI Cloud Reports

Oracle WMS Cloud now allows you to launch and print additional custom report types designed using WebReports, directly from the UI. On the “Company Report Type” UI, choose the “WebReport” subreport type and provide the corresponding web report name and path to print custom webreports from the UI.  This feature was already available for Order Packing List and Bill of Loading (BOL). As of 18C, this feature is enabled for the following additional reports:

NOTE:  Custom reports design through WebReports cannot be invoked from the RF (This note is only applicable for reports that can be printed via RF).

Steps to Enable

Improved Literal Localization

Earlier, you could personalize literals one by one through the browser UI. 18C introduces a new input interface entity: “Literals”. This interface helps you to change/modify the description for the literal in the required language in bulk. You can upload either through the Input Interface screen (UI) or through the Init Stage Interface (API).

The following formats are supported:

You can download all/multiple literals from the application in csv format, from the literals screen, modify the description of the required literal, save them in xls, and upload this file using the input interface UI. This feature allows you to update hundreds of records in bulk, through your uploaded files instead of doing so one by one through the browser. The Literals Screen Module data grid fields are now fixed relative to each other, and cannot be rearranged, so as to facilitate download and upload. You can download a literal as a CSV into excel, save as XLS format, and then upload it from the input interface screen.

UI/RF SCREEN MESSAGES 

The UI Inbound screens and RF Messages screens now have literals, so that you can rename these messages to their wording or language of preference.

Steps to Enable

No steps are required to enable this feature.

Improved Time Zone Localization

ADDITIONAL TIME ZONES 

Update 18C now supports the following time zones:

Steps to Enable

No steps are required to enable this feature.

Yard Management Improvements

In 18C, the following enhancements have been added in Oracle WMS Cloud for yard management:

NOTE:  Prior to 18C, to locate trailers to yard locations or move trailers from one yard location to another, we used location drop down in edit/create option in UI. The “Location” field in the create/edit pane will be removed. 

Steps to Enable

Add permission "trailer / Locate Trailer to Yard"

Oracle WMS BI Cloud Framework

The mapped framework between Oracle WMS BI Cloud and Oracle WMS Cloud now supports additional objects and mappings, particularly those objects and mappings added in more recent releases such as Trailers and new fields for Orders.

Steps to Enable

No steps are required to enable this feature.

Order Detail Level Permissions

Prior to 18C, if you had order level permissions order_hdr/add order, order_hdr/change orders, or order_hdr/delete orders, you got access to modify the order header and also to add/edit/delete the order details. You had the permissions to add/modify/delete order details (navigated from order header screen). Update 18C includes additional permissions to add/edit/delete order details so that permissions for order header and detail are separated out. If you have permissions for order_hdr/add order, order_hdr/change orders, and order_hdr/delete orders, do not give permissions to add/modify/delete order details.

Upon updating to 18C, users with an employee role who have permissions for order_hdr/add order, or order_hdr/change orders will not be able to add/modify/delete order details. New Order detail level permissions need to be provided exclusively.

Steps to Enable

Add the new Order detail permission.

Document Design and Printing

Price Label Support with Label Designer

Update 18C allows you to create a Price Label using Label Designer. This new feature enhances the flexibility to personalize labels. Now, you can select a Price Label template from the Standard Templates drop-down, and design the Price Label by choosing the width from a selection of fields available in the Column Name. You can configure the created Price Label in the Label Template View UI, copying the user-defined Template name to the Template Name in the Label Template View UI. Update 18C also includes the locations where you can print the designed Price Label. The IB Shipment Screen and IB Shipment Detail Screen now have a Print Price Label button which will print the design Price Label. Also, the RF transaction "RF Retail Price Label" will print the design price label.

Steps to Enable

Configure the Price Label template on Label Designer

Case and Pack Labels Using Label Designer

Label Designer is enhanced to support the creation of Case and Pack Labels. A new button “Print UOM Label” is added to IBLPN UI to print Case and Pack Labels.

Steps to Enable

Configure the Case and Packs Label template on Label Designer with the following settings:

OBLPN Number Labeling and Printing

Some customer operations have specific requirements for LPN number labeling. Currently Oracle WMS Clouds creates a random LPN number for non-cubed OBLPNs which prevents the desired labeling for LPN. A new function "RENAME_OUT_BOUND_CONTAINER_NUMBER_ONCE" has been added to Label Designer. You can add this function on the Container Label by clicking Print OBLPN label on the OBLPN Screen. This function first checks to see if the field ref_oblpn is empty in the OBLPN, and if it will look up the sequence counter for that OBLPN's destination facility. It populates the LPN number according to the configuration on the sequence counter, and the old LPN number is moved to the ref_oblpn field.

Steps to Enable

Add the function RENAME_OUT_BOUND_CONTAINER_NUMBER_ONCE to the oblpn_content_label template.

APPENDIX

SELECTION CRITERIA

Putaway Type Calculation

Container Asset Nbr

Container Current Location Aisle

Container Current Location Alloc Zone

Container Current Location Area

Container Current Location Barcode

Container Current Location Bay

Container Current Location Billing Location Type

Container Current Location Height

Container Current Location Length

Container Current Location Level

Container Current Location Lock Code

Container Current Location MHE System Code

Container Current Location Size Type

Container Current Location String

Container Current Location Task Zone

Container Current Location Type

Container Current Location Width

Container Height

Container Inbound Shipment Nbr

Container is LPN as Physical Pallet Flag

Container Length

Container Lock Code

Container LPN Type

Container Previous Location Aisle

Container Previous Location Alloc Zone

Container Previous Location Area

Container Previous Location Barcode

Container Previous Location Bay

Container Previous Location Billing Location Type

Container Previous Location Height

Container Previous Location Length

 

Container Previous Location Level

Container Previous Location Lock Code

Container Previous Location MHE System Code

Container Previous Location Size Type

Container Previous Location String

Container Previous Location Task Zone Code

Container Previous Location Type

Container Previous Location Width

Container Priority Date

Container Purchase Order Nbr

Container Putaway Type

Container QC Status

Container Received Time Stamp

Container Received Trailer Number

Container Received User

Container Status

Container Type (I or O)

Container VAS Status

Container Volume

Container Weight

Container Width

IB Shipment Dtl Cust Date1

IB Shipment Dtl Cust Date2

IB Shipment Dtl Cust Date3

IB Shipment Dtl Cust Date4

IB Shipment Dtl Cust Date5

IB Shipment Dtl Cust Decimal1

IB Shipment Dtl Cust Decimal2

IB Shipment Dtl Cust Decimal3

IB Shipment Dtl Cust Decimal4

IB Shipment Dtl Cust Decimal5

IB Shipment Dtl Cust Field1

IB Shipment Dtl Cust Field2

IB Shipment Dtl Cust Field3

IB Shipment Dtl Cust Field4

IB Shipment Dtl Cust Field5

IB Shipment Dtl Cust Long Text1

IB Shipment Dtl Cust Long Text2

IB Shipment Dtl Cust Long Text3

IB Shipment Dtl Cust Number1

IB Shipment Dtl Cust Number2

IB Shipment Dtl Cust Number3

IB Shipment Dtl Cust Number4

IB Shipment Dtl Cust Number5

IB Shipment Dtl Cust Short Text1

IB Shipment Dtl Cust Short Text10

IB Shipment Dtl Cust Short Text11

IB Shipment Dtl Cust Short Text12

IB Shipment Dtl Cust Short Text2

IB Shipment Dtl Cust Short Text3

IB Shipment Dtl Cust Short Text4

IB Shipment Dtl Cust Short Text5

IB Shipment Dtl Cust Short Text6

IB Shipment Dtl Cust Short Text7

IB Shipment Dtl Cust Short Text8

IB Shipment Dtl Cust Short Text9

IB Shipment Hdr Cust Date1

IB Shipment Hdr Cust Date2

IB Shipment Hdr Cust Date3

IB Shipment Hdr Cust Date4

IB Shipment Hdr Cust Date5

IB Shipment Hdr Cust Decimal1

IB Shipment Hdr Cust Decimal2

IB Shipment Hdr Cust Decimal3

IB Shipment Hdr Cust Decimal4

IB Shipment Hdr Cust Decimal5

IB Shipment Hdr Cust Field1

IB Shipment Hdr Cust Field2

IB Shipment Hdr Cust Field3

IB Shipment Hdr Cust Field4

IB Shipment Hdr Cust Field5

IB Shipment Hdr Cust Long Text1

IB Shipment Hdr Cust Long Text2

IB Shipment Hdr Cust Long Text3

IB Shipment Hdr Cust Number1

IB Shipment Hdr Cust Number2

IB Shipment Hdr Cust Number3

IB Shipment Hdr Cust Number4

IB Shipment Hdr Cust Number5

IB Shipment Hdr Cust Short Text1

IB Shipment Hdr Cust Short Text10

IB Shipment Hdr Cust Short Text11

IB Shipment Hdr Cust Short Text12

IB Shipment Hdr Cust Short Text2

IB Shipment Hdr Cust Short Text3

IB Shipment Hdr Cust Short Text4

IB Shipment Hdr Cust Short Text5

IB Shipment Hdr Cust Short Text6

IB Shipment Hdr Cust Short Text7

IB Shipment Hdr Cust Short Text8

IB Shipment Hdr Cust Short Text9

Inbound Shipment Detail Lock Code

Inventory Attribute A

Inventory Attribute B

Inventory Attribute C

Inventory Attribute D

Inventory Attribute E

Inventory Attribute F

Inventory Attribute G

Inventory Attribute H

Inventory Attribute I

Inventory Attribute J

Inventory Attribute K

Inventory Attribute L

Inventory Attribute M

Inventory Attribute N

Inventory Attribute O

Item Alternate Code

Item Barcode

Item Brand Code

Item Carrier Commodity Description

Item Case Oblpn Type

Item Catch Weight Method

Item Code

Item Conveyable

Item Currency Code

Item custom attribute 1

Item custom attribute 2

Item Description

Item Description 2

Item Description 3

Item Dimension 1

Item Dimension 2

Item Dimension 3

Item External Style

Item facility Conveyable

Item Facility Description

Item Facility Material Hazard Type

Item Facility Preferred aisle

Item Facility Preferred area

Item Facility Replenishment type

Item Full Dangerous Goods Flg

Item Hazardous

Item Hazmat Packaging Description

Item Hierarchy Code 1

Item Hierarchy Code 2

Item Hierarchy Code 3

Item Hierarchy Code 4

Item Hierarchy Code 5

Item Host Aware Item Flag

Item Invn Attribute A Tracking Value

Item Invn Attribute B Tracking Value

Item Invn Attribute C Tracking Value

Item Invn Attribute D Tracking Value

Item Invn Attribute E Tracking Value

Item Invn Attribute F Tracking Value

Item Invn Attribute F Tracking Value

Item Is Parent Flag

Item Limited Qty Flg

Item Line

Item Lpns Per Tier

Item Lpns Per Tier

Item Material Hazard Type

Item Max Case Qty

Item Net Cost

Item Nmfc Code

Item Oblpn Type

Item Oblpn Type

Item Order Consolidation Attribute

Item Pack Oblpn Type

Item Packing Group

Item Packing Tolerance Percent

Item Part A

Item Part B

Item Part C

Item Part D

Item Part E

Item Part F

Item Pre Pack Code

Item Product Life

Item Proper Shipping Name

Item Putaway Type

Item Recv Type

Item Regular Code

Item Required Batch Number Flag

Item Retail Price

Item Season Code

Item Serial Number Tracking Value

Item Shipping Temperature Instr

Item Short Description

Item Sortable

Item Stackability Code

Item Std Case Height

Item Std Case Length

Item Std Case Qty

Item Std Case Volume

Item Std Case Width

Item Std Pack Height

Item Std Pack Length

Item Std Pack Qty

Item Std Pack Volume

Item Std Pack Width

Item Tiers Per Pallet

Item UN Class

Item UN Description

Item UN Number

Item Unit Cost

Item Unit Cost

Item Unit Height

Item Unit Length

Item Unit Volume

Item Unit Weight

Item Unit Width

Item Vas Group Code

Item Velocity Code

 

Inbound Sorting Criteria

Container Carrier Code

Container Ship Via

Order Hdr Carrier Account Number

Order Hdr Cust Field 1

Order Hdr Cust Field 2

Order Hdr Cust Field 3

Order Hdr Cust Field 4

Order Hdr Cust Field 5

Order Hdr Cust Long Text 1

Order Hdr Cust Long Text 2

Order Hdr Cust Long Text 3

Order Hdr Cust Short Text 1

Order Hdr Cust Short Text 10

Order Hdr Cust Short Text 11

Order Hdr Cust Short Text 12

Order Hdr Cust Short Text 2

Order Hdr Cust Short Text 3

Order Hdr Cust Short Text 4

Order Hdr Cust Short Text 5

Order Hdr Cust Short Text 6

Order Hdr Cust Short Text 7

Order Hdr Cust Short Text 8

Order Hdr Cust Short Text 9

Order Hdr Customer City

Order Hdr Customer Country

Order Hdr Customer Name

Order Hdr Customer Number

Order Hdr Customer PO Number

Order Hdr Customer PO Type

Order Hdr Customer State

Order Hdr Customer Zip

Order Hdr Destination Company Code

Order Hdr Destination Dept Number

Order Hdr Destination Facility Code

Order Hdr External Route

Order Hdr Host Allocation Number

Order Hdr LPN Type Class

Order Hdr Order Nbr

Order Hdr Order Type

Order Hdr Priority

Order Hdr Reference Number

Order Hdr Route Number

Order Hdr Sales Channel

Order Hdr Sales Order Number

Order Hdr Scheduled Ship Date

 

Order Hdr Ship To City

Order Hdr Ship To Country

Order Hdr Ship To Name

Order Hdr Ship To State

Order Hdr Ship To Zip

Order Hdr Ship Via

Order Hdr Shipto Facility Code

Order Hdr Start Ship Date

Order Hdr Vas Group Code

Outbound Stop Load Number

Outbound Stop Route Number

 

Task Creation

Destination LPN Number

Destination LPN Type

Final OBLPN Number

From Active Location  Location Cust Field 1

From Active Location  Location Cust Field 2

From Active Location  Location Cust Field 3

From Active Location  Location Cust Field 4

From Active Location  Location Cust Field 5

From Active Location Item Dedication Type

From Active Location Location Aisle

From Active Location Location Alloc zone

From Active Location Location Area

From Active Location Location Barcode

From Active Location Location Bay

From Active Location Location Billing Location Type

From Active Location Location Bin

From Active Location Location Height

From Active Location Location Length

From Active Location Location Level

From Active Location Location Lock Code

From Active Location Location MHE System Code

From Active Location Location Pick Sequence

From Active Location Location Pick Zone

From Active Location Location Position

From Active Location Location Replenishment Zone

From Active Location Location Size Type

From Active Location Location Task Zone

From Active Location Location Width

From Inventory Batch Number

From Inventory Expiry Date

From Inventory Inventory Attr A

From Inventory Inventory Attr B

From Inventory Inventory Attr C

From Inventory Inventory Attr D

From Inventory Inventory Attr E

From Inventory Inventory Attr F

From Inventory Inventory Attr G

From Inventory Item Code

From LPN Asset Nbr

From LPN Current  Location Cust Field 1

From LPN Current  Location Cust Field 2

From LPN Current  Location Cust Field 3

From LPN Current  Location Cust Field 4

From LPN Current  Location Cust Field 5

From LPN Current Item Dedication Type

From LPN Current Location Aisle

From LPN Current Location Alloc zone

From LPN Current Location Area

From LPN Current Location Barcode

From LPN Current Location Bay

From LPN Current Location Billing Location Type

From LPN Current Location Bin

From LPN Current Location Height

From LPN Current Location Length

From LPN Current Location Level

From LPN Current Location Lock Code

From LPN Current Location MHE System Code

From LPN Current Location Pick Sequence

From LPN Current Location Pick Zone

From LPN Current Location Position

From LPN Current Location Replenishment Zone

From LPN Current Location Size Type

From LPN Current Location Task Zone

From LPN Current Location Type

From LPN Current Location Width

From LPN Height

From LPN Inbound Shipment Nbr

From LPN Is PALLET Flag

From LPN Length

From LPN Lock Code

From LPN LPN Type

From LPN Number

From LPN Pallet Number

From LPN Priority Date

From LPN Purchase Order Nbr

From LPN Putaway Type

From LPN QC Status

From LPN Received Trailer Number

From LPN Status

From LPN Type (I or O)

From LPN VAS Status

From LPN Volume

From LPN Weight

From LPN Width

Item Alternate Code

Item Barcode

Item Batch Tracking Flag

Item Brand code

Item carrier commodity description

Item Case OBLPN Type

Item Catch Weight Method

Item Company Code

Item Conveyable Flag

Item Currency Code

Item Custom Attribute 1

Item Custom Attribute 2

Item Description

Item Description 2

Item Description 3

Item Dimension 1

Item Dimension 2

Item Dimension 3

Item Dummy Sku Flag

Item Excepted Qty Instruction

Item External Style

Item Facility  Preferred aisle

Item Facility  Preferred area

Item Facility Active Location Type

Item Facility Conveyable Flag

Item Facility Item Description

Item Facility Putaway Type

Item Facility Replenishment type

Item Full Dangerous Goods Flag

Item Full OBLPN Type

Item group code

Item Harmonized Tariff

Item hazard statement

Item Hazmat Flag

Item hazmat packaging description

Item Hierarchy Code 1

Item Hierarchy Code 2

Item Hierarchy Code 3

Item Hierarchy Code 4

Item Hierarchy Code 5

Item Host Aware Item Flag

Item Invn Attribute A Tracking Value

Item Invn Attribute B Tracking Value

Item Invn Attribute C Tracking Value

Item Invn Attribute D Tracking Value

Item Invn Attribute E Tracking Value

Item Invn Attribute F Tracking Value

Item Invn Attribute G Tracking Value

Item Is Parent

Item Limited Qty Flag

Item lpns per tier

Item Max Case qty

Item Minimum Dispatch UOM

Item Net Cost

Item NMFC Code

Item OBLPN Type

Item Order Consolidation Attribute

Item Pack OBLPN Type

Item Packing Group

Item Packing Tolerance Percent

Item Part a

Item Part b

Item Part c

Item Part d

Item Part e

Item Part f

Item Pre Pack Code

Item product life

Item Proper Shipping Name

Item Putaway type

Item Recv Type

Item Regularity Code

Item Retail Price

Item Season Code

Item Serial Number Tracking value

Item Shipping Temperature Instruction

Item Short Description

Item Sku Line

Item Sortable Flag

Item Stackability Code

Item Std Case height

Item Std Case length

Item Std Case qty

Item Std Case volume

Item Std Case weight

Item Std Case width

Item Std Pack height

Item Std Pack length

Item Std Pack qty

Item Std Pack volume

Item Std Pack width

Item tiers per pallet

Item UN Class

Item UN Description

Item UN Number

Item Unit Cost

Item Unit Height

Item Unit Length

Item Unit Volume

Item Unit Weight

Item Unit Width

Item VAS Group Code

Item Velocity Code

MHE System Code

Order Dtl Cust Field 1

Order Dtl Cust Field 2

Order Dtl Cust Field 3

Order Dtl Cust Field 4

Order Dtl Cust Field 5

Order dtl Cust Long Text 1

Order dtl Cust Long Text 2

Order dtl Cust Long Text 3

Order dtl Cust Short Text 1

Order dtl Cust Short Text 10

Order dtl Cust Short Text 11

Order dtl Cust Short Text 12

Order dtl Cust Short Text 2

Order dtl Cust Short Text 3

Order dtl Cust Short Text 4

Order dtl Cust Short Text 5

Order dtl Cust Short Text 6

Order dtl Cust Short Text 7

Order dtl Cust Short Text 8

Order dtl Cust Short Text 9

Order dtl Host OB LPN Number

Order Dtl Inv Attribute A

Order Dtl Inv Attribute B

Order Dtl Inv Attribute C

Order Dtl Inv Attribute D

Order Dtl Inv Attribute E

Order Dtl Inv Attribute F

Order Dtl Inv Attribute G

Order Dtl Inv Attribute H

Order Dtl Inv Attribute I

Order Dtl Inv Attribute J

Order Dtl Inv Attribute K

Order Dtl Inv Attribute L

Order Dtl Inv Attribute M

Order Dtl Inv Attribute N

Order Dtl Inv Attribute O

Order Dtl Special Instruction

Order Dtl VAS Activity Code

Order Hdr Cust Field 1

Order Hdr Cust Field 2

Order Hdr Cust Field 3

Order Hdr Cust Field 4

Order Hdr Cust Field 5

Order Hdr Cust Long Text 1

Order Hdr Cust Long Text 2

Order Hdr Cust Long Text 3

Order Hdr Cust PO Number

Order Hdr Cust Short Text 1

Order Hdr Cust Short Text 10

Order Hdr Cust Short Text 11

Order Hdr Cust Short Text 12

Order Hdr Cust Short Text 2

Order Hdr Cust Short Text 3

Order Hdr Cust Short Text 4

Order Hdr Cust Short Text 5

Order Hdr Cust Short Text 6

Order Hdr Cust Short Text 7

Order Hdr Cust Short Text 8

Order Hdr Cust Short Text 9

Order Hdr Customer Address

Order Hdr Customer City

Order Hdr Customer Country

Order Hdr Customer Name

Order Hdr Customer Number

Order Hdr Customer PO Number

Order Hdr Customer PO Type

Order Hdr Customer State

Order Hdr Customer Zip

Order Hdr Destination Company Code

Order Hdr Destination Facility Code

Order Hdr External Route

Order Hdr Host Allocation Number

Order Hdr LPN Type Class

Order Hdr Order Nbr

Order Hdr Order Type

Order Hdr Priority

Order Hdr Reference Number

Order Hdr Route Number

Order Hdr Sales Channel

Order Hdr Sales Order Number

Order Hdr Ship To City

Order Hdr Ship To Country

Order Hdr Ship To Name

Order Hdr Ship To State

Order Hdr Ship To Zip

Order Hdr Ship Via

Order Hdr Shipto Facility Code

Order Hdr VAS Group Code

To Task Zone

 

Cycle Count Task Creation Rules

inventory-batch number

inventory-curr qty

inventory-expiry date

inventory-inv attribute a

inventory-inv attribute b

inventory-inv attribute c

inventory-inv attribute d

inventory-inv attribute e

inventory-inv attribute f

inventory-inv attribute g

Item- Hazmat Flag

Item- Hierarchy Code 1

Item- Hierarchy Code 2

Item- Hierarchy Code 3

Item- Hierarchy Code 4

Item- Hierarchy Code 5

item-alternate code

item-barcode

Item-Batch Tracking Flag

item-brand code

item-calculated code

Item-carrier commodity description

Item-Case OBLPN Type

Item-Catch Weight Method

item-conveyable flag

item-created time

Item-Currency code

Item-Custom Attribute 1

Item-Custom Attribute 2

item-description

Item-Description 2

Item-Description 3

Item-Dimension 1

Item-Dimension 2

Item-Dimension 3

Item-Dummy Sku Flag

Item-Excepted Qty Instruction

item-external style

Item-Full Dangerous Goods Flag

Item-Group code

Item-Harmonized Tariff

Item-Hazard statement

Item-hazmat packaging description

Item-Host Aware Item Flag

Item-Invn Attribute A Tracking Value

Item-Invn Attribute B Tracking Value

Item-Invn Attribute C Tracking Value

Item-Invn Attribute D Tracking Value

Item-Invn Attribute E Tracking Value

Item-Invn Attribute F Tracking Value

Item-Invn Attribute G Tracking Value

item-is parent flag

Item-Limited qty flag

Item-Lpns per tier

Item-Max Case qty

Item-Minimum Dispatch UOM

item-modified time

item-modified user

Item-Net cost

Item-NMFC Code

Item-OBLPN Type

Item-Order Consolidation Attribute

Item-Pack OBLPN Type

Item-Packing Group

Item-Packing Tolerance Percent

item-part a

item-part b

item-part c

item-part d

item-part e

item-part f

item-pre pack code

item-product life

Item-Proper Shipping Name

item-putaway type

Item-Recv Type

Item-Regularity Code

item-require batch flag

Item-Retail Price

item-season code

Item-Serial Number Tracking value

Item-Shipping Temperature Instruction

item-short description

Item-Sku Line

item-sortable flag

Item-Stackability Code

Item-Std Case height

Item-Std Case length

Item-Std Case qty

Item-Std Case volume

Item-Std Case width

Item-Std Pack height

Item-Std Pack length

Item-Std Pack qty

Item-Std Pack volume

Item-Std Pack weight

Item-Std Pack width

Item-Tiers per pallet

Item-UN Class

Item-UN Description

Item-UN Number

item-unit cost

Item-Unit Height

Item-Unit Length

Item-Unit Volume

Item-Unit Weight

Item-Unit Width

item-vas group code

item-velocity code

Item Facility-Active Location Type

Item Facility-Conveyable Flag

Item Facility-Description

Item Facility-Modify Interface Flag

Item Facility-Preferred aisle

Item Facility-Preferred area

Item Facility-Putaway Type

Item Facility-Replenishment type

location-aisle

location-alloc zone

Location-Allow Multi Sku Flag

location-allow reserve partial pick flag

location-area

Location-Assembly Flag

location-barcode

location-bay

Location-Billing Location Type

Location-Bin

location-created time

Location-Cust Field 1

Location-Cust Field 2

Location-Cust Field 3

Location-Cust Field 4

Location-Cust Field 5

Location-dedicated item code

location-dedicated company

Location-Divert Lane

Location-Height

Location-Item Dedication Type

location-last count time

location-last count user

Location-Length

location-level

Location-Location Size Type

location-lock code

Location-Lock For Putaway Flag

Location-Max LPNs

Location-Max Units

Location-Max Volume

Location-MHE System Code

Location-Min Volume

location-modified time

location-pick sequence

location-pick zone

location-position

location-putaway sequence

Location-Replenishment Zone

Location-Restrict Invn Attribute Flag

Location-Restrict Single Batch Number Flag

location-task zone

location-to be counted flag

location-type

Location-Width

Outbound Sorting Criteria

Container Carrier Code

Container Ship Via

Order Hdr Carrier Account Number

Order Hdr Cust Field 1

Order Hdr Cust Field 2

Order Hdr Cust Field 3

Order Hdr Cust Field 4

Order Hdr Cust Field 5

Order Hdr Cust Long Text 1

Order Hdr Cust Long Text 2

Order Hdr Cust Long Text 3

Order Hdr Cust Short Text 1

Order Hdr Cust Short Text 10

Order Hdr Cust Short Text 11

Order Hdr Cust Short Text 12

Order Hdr Cust Short Text 2

Order Hdr Cust Short Text 3

Order Hdr Cust Short Text 4

Order Hdr Cust Short Text 5

Order Hdr Cust Short Text 6

Order Hdr Cust Short Text 7

Order Hdr Cust Short Text 8

Order Hdr Cust Short Text 9

Order Hdr Customer City

Order Hdr Customer Country

Order Hdr Customer Name

Order Hdr Customer Number

Order Hdr Customer PO Number

Order Hdr Customer PO Type

Order Hdr Customer State

Order Hdr Customer Zip

Order Hdr Destination Company Code

Order Hdr Destination Dept Number

Order Hdr Destination Facility Code

Order Hdr External Route

Order Hdr Host Allocation Number

Order Hdr LPN Type Class

Order Hdr Order Nbr

Order Hdr Order Type

Order Hdr Priority

Order Hdr Reference Number

Order Hdr Route Number

Order Hdr Sales Channel

Order Hdr Sales Order Number

Order Hdr Scheduled Ship Date

Order Hdr Ship To City

Order Hdr Ship To Country

Order Hdr Ship To Name

Order Hdr Ship To State

Order Hdr Ship To Zip

Order Hdr Ship Via

Order Hdr Shipto Facility Code

Order Hdr Start Ship Date

Order Hdr Vas Group Code

Outbound Stop Load Number

Outbound Stop Route Number

Dynamic Staging Criteria

Order Hdr Order Nbr

Order Hdr Order Type

Order Hdr Cust PO Number

Order Hdr Shipto Facility Code

Order Hdr Destination Facility Code

Order Hdr Destination Company Code

Order Hdr Customer Name

Order Hdr Customer State

Order Hdr Customer City

Order Hdr Customer Country

Order Hdr Customer Zip

Order Hdr Reference Number

Order Hdr Customer Number

Order Hdr Priority

Order Hdr Host Allocation Number

Order Hdr Sales Order Number

Order Hdr Customer PO Number

Order Hdr Ship Via

Order Hdr Route Number

Order Hdr External Route

Order Hdr VAS Group Code

Order Hdr Ship To Name

Order Hdr Ship To State

Order Hdr Ship To City

Order Hdr Ship To Country

Order Hdr Ship To Zip

Order Hdr Sales Channel

Order Hdr Cust Field 1

Order Hdr Cust Field 2

Order Hdr Cust Field 3

Order Hdr Cust Field 4

Order Hdr Cust Field 5

Order Hdr Customer PO Type

Order Hdr LPN Type Class

Order Hdr Scheduled Ship Date

Order Hdr Carrier Account Number

Order Hdr Destination Dept Number

Order Hdr Start Ship Date

Order Hdr Ship Via

Order Hdr Cust Long Text 1

Order Hdr Cust Long Text 2

Order Hdr Cust Long Text 3

Order Hdr Cust Short Text 1

Order Hdr Cust Short Text 2

Order Hdr Cust Short Text 3

Order Hdr Cust Short Text 4

Order Hdr Cust Short Text 5

Order Hdr Cust Short Text 6

Order Hdr Cust Short Text 7

Order Hdr Cust Short Text 8

Order Hdr Cust Short Text 9

Order Hdr Cust Short Text 10

Order Hdr Cust Short Text 11

Order Hdr Cust Short Text 12

Sort and Receive Selection Criteria

Inbound Shipment-Cust_Field_1

Inbound Shipment-Cust_Field_2

Inbound Shipment-Cust_Field_3

Inbound Shipment-Cust_Field_4

Inbound Shipment-Cust_Field_5

Inbound Shipment Detail-Batch Number

Inbound Shipment Detail-Cust_Field_1

Inbound Shipment Detail-Cust_Field_2

Inbound Shipment Detail-Cust_Field_3

Inbound Shipment Detail-Cust_Field_4

Inbound Shipment Detail-Cust_Field_5

Inbound Shipment Detail-expiry date

Inbound Shipment Detail-Invn Attr a

Inbound Shipment Detail-Invn Attr b

Inbound Shipment Detail-Invn Attr c

Inbound Shipment Detail-Invn Attr d

Inbound Shipment Detail-Invn Attr e

Inbound Shipment Detail-Invn Attr f

Inbound Shipment Detail-Invn Attr g

Inbound Shipment Detail-Invn Attr h

Inbound Shipment Detail-Invn Attr i

Inbound Shipment Detail-Invn Attr j

Inbound Shipment Detail-Invn Attr k

Inbound Shipment Detail-Invn Attr l

Inbound Shipment Detail-Invn Attr m

Inbound Shipment Detail-Invn Attr n

Inbound Shipment Detail-Invn Attr o

Inbound Shipment Detail-Lock Code

Inbound Shipment Detail-PO Number

Inbound Shipment Detail-Putaway Type

Inbound Shipment Origin Code

Inbound Shipment Reference Number

Inbound Shipment Type

Item Alternate Code

Item Barcode

Item Batch Tracking Flag

Item Brand Code

Item Carrier Commodity Description

Item Case Oblpn Type

Item Catch Weight Method

Item Code

Item Conveyable Flag

Item Currency Code

Item Custom Attribute 1

Item Custom Attribute 2

Item Description 2

Item Description 3

Item Dimension 1

Item Dimension 2

Item Dimension 3

Item Dummy Sku Flag

Item External Style

Item Facility-Active Location Type

Item Facility-Conveyable

Item Facility-Description

Item Facility-Preferred Aisle

Item Facility-Preferred Area

Item Facility-Putaway Type

Item Facility-Replenishment Type

Item Fulldg Flag

Item Group Code

 

Item Harmonized Tariff Code

Item Hazard Statement

Item Hazmat Flag

Item Hazmat Packaging Description

Item Hierarchy Code 1

Item Hierarchy Code 2

Item Hierarchy Code 3

Item Hierarchy Code 4

Item Hierarchy Code 5

Item Host Aware Item Flag

Item Invn Attribute A Tracking Value

Item Invn Attribute B Tracking Value

Item Invn Attribute C Tracking Value

Item Invn Attribute D Tracking Value

Item Invn Attribute E Tracking Value

Item Invn Attribute F Tracking Value

Item Invn Attribute G Tracking Value

Item Is Parent

Item Limited Qty Flag

Item Lpns per Tier

Item Max Case Qty

Item Minimum Dispatch UOM

Item Net Cost

Item NMFC Code

Item Oblpn Type

Item Order Consolidation Attribute

Item Pack Oblpn Type

Item Packing Group

Item Part A

Item Part B

Item Part C

Item Part D

Item Part E

Item Part F

Item Pre Pack Code

Item Product Life

Item Proper Shipping Name

Item Putaway Type

Item Recv Type

Item Regularity Code

Item Retail Price

Item Season Code

Item Serial number Tracking Flag

Item Shipping Temperature Instr

Item Sortable Flag

Item Stackability Code

Item Std Case Height

Item Std Case Length

Item Std Case Qty

Item Std Case Volume

Item Std Case Width

Item Std Pack Height

Item Std Pack Length

Item Std Pack Qty

Item Std Pack Volume

Item Std Pack Width

Item Tiers per Pallet

Item UN Class

Item UN Description

Item UN Number

Item Unit Cost

 

Item Unit Height

Item Unit length

Item Unit Volume

Item Unit Weight

Item Unit Width

Item Vas Group Code

Item Velocity Code

 

Dynamic Wave Search Criteria

Batch Nbr

Cost

Item Alternate Code

Item Barcode

Item Brand Code

Item Carrier Commodity Description

Item Case OBLPN Type

Item Catch Weight Method

Item Conveyable Flag

Item Currency Code

ITEM Cust Attr 1

ITEM Cust Attr 2

Item Description

Item Description 2

Item Description 3

Item Dimension 1

Item Dimension 2

Item Dimension 3

Item Dummy Sku Flag

Item Excepted Qty Instruction

Item External Style

Item Facility Conveyable Flag

Item Facility Item Description

Item Facility Material Hazard Type

Item Facility Preferred Aisle

Item Facility Preferred Area

Item Facility Putaway type

Item Facility Replenishment Type

Item Full Dangerous Goods Flg

Item Group Code

Item Harmonized Tariff

Item Hazard Statement

Item HazMat Flag

Item Hazmat packaging Description

Item Hierarchy 1 Code

Item Hierarchy 2 Code

Item Hierarchy 3 Code

Item Hierarchy 4 Code

Item Hierarchy 5 Code

Item Host Aware Item Flag

Item Invn Attribute A Tracking Value

Item Invn Attribute B Tracking Value

Item Invn Attribute C Tracking Value

Item Invn Attribute D Tracking Value

Item Invn Attribute E Tracking Value

Item Invn Attribute F Tracking Value

Item Invn Attribute G Tracking Value

Item Is Parent

Item Limited Qty Flag

Item Line

Item Lpns Per Tier

Item Material Hazard Type

Item Max Case Qty

Item Net Cost

Item NMFC Code

Item OBLPN Type

Item Order Consolidation Attribute

Item Pack OBLPN Type

Item Packing Group

Item Packing Tolerance Percent

Item Part A

Item Part B

Item Part C

Item Part D

Item Part E

Item Part F

Item Pre Pack Code

Item Product Life

Item Proper Shipping Name

Item Putaway type

Item Recv Type

Item Regularity Code

Item Retail Price

Item Season Code

Item Serial Number Tracking Value

Item Shipping Temperature Instr

Item Short Description

Item Sortable Flag

Item Stackability Code

Item Std Case Height

Item Std Case Length

Item Std Case Qty

Item Std Case Volume

Item Std Case Weight

Item Std Case Width

Item Std Pack Height

Item Std Pack Length

Item Std Pack Qty

Item Std Pack Volume

Item Std Pack Weight

Item Std Pack Width

Item Tiers Per Pallet

Item UN Class

Item UN Description

Item UN Number

Item Unit Cost

Item Unit Height

Item Unit Length

Item Unit Volume

Item Unit Weight

Item Unit Width

Item VAS Group Code

Item Velocity Code

Order Customer City

Order Customer Country

Order Customer State

Order Customer Zip

Order Dtl Cust Date 1

Order Dtl Cust Date 2

Order Dtl Cust Date 3

Order Dtl Cust Date 4

Order Dtl Cust Date 5

Order Dtl Cust Decimal 1

Order Dtl Cust Decimal 2

Order Dtl Cust Decimal 3

Order Dtl Cust Decimal 4

Order Dtl Cust Decimal 5

Order Dtl Cust Field 1

Order Dtl Cust Field 2

Order Dtl Cust Field 3

Order Dtl Cust Field 4

Order Dtl Cust Field 5

Order Dtl Cust Number 1

Order Dtl Cust Number 2

Order Dtl Cust Number 3

Order Dtl Cust Number 4

Order Dtl Cust Number 5

Order Dtl Inv Attribute A

Order Dtl Inv Attribute B

Order Dtl Inv Attribute C

Order Dtl Inv Attribute D

Order Dtl Inv Attribute E

Order Dtl Inv Attribute F

Order Dtl Inv Attribute G

Order Dtl Inv Attribute H

Order Dtl Inv Attribute I

Order Dtl Inv Attribute J

Order Dtl Inv Attribute K

Order Dtl Inv Attribute L

Order Dtl Inv Attribute M

Order Dtl Inv Attribute N

Order Dtl Inv Attribute O

Order Dtl Original Item Code

Order Dtl Reqd LPN Nbr

Order Dtl Required Pallet Number

Order Dtl Ship Request Line

Order Dtl VAS Activity Code

Order External Route

Order Externally Planned Load

Order Hdr Carrier Account Number

Order Hdr Cust Date 1

Order Hdr Cust Date 2

Order Hdr Cust Date 3

Order Hdr Cust Date 4

Order Hdr Cust Date 5

Order Hdr Cust Decimal 1

Order Hdr Cust Decimal 2

Order Hdr Cust Decimal 3

Order Hdr Cust Decimal 4

Order Hdr Cust Decimal 5

Order Hdr Cust Long Text 1

Order Hdr Cust Long Text 2

Order Hdr Cust Long Text 3

Order Hdr Cust Number 1

Order Hdr Cust Number 2

Order Hdr Cust Number 3

Order Hdr Cust Number 4

Order Hdr Cust Number 5

Order Hdr Cust Short Text 1

Order Hdr Cust Short Text 10

Order Hdr Cust Short Text 11

Order Hdr Cust Short Text 12

Order Hdr Cust Short Text 2

Order Hdr Cust Short Text 3

Order Hdr Cust Short Text 4

Order Hdr Cust Short Text 5

Order Hdr Cust Short Text 6

Order Hdr Cust Short Text 7

Order Hdr Cust Short Text 8

Order Hdr Cust Short Text 9

Order Hdr Customer Email

Order Hdr Customer Number

Order Hdr Customer Phone

Order Hdr Customer PO Number

Order Hdr Customs Broker Contact

Order Hdr Destination Department

Order Hdr Duties Payment Method

Order Hdr Expiry Date

Order Hdr Host Allocation Number

Order Hdr LPN Type Class

Order Hdr OB LPN Type

Order Hdr Payment Method

Order Hdr Reference Number

Order Hdr Shipto Address

Order Hdr Shipto Address2

Order Hdr Shipto Address3

Order Hdr Shipto Contact

Order Hdr Shipto Email

Order Hdr Shipto Phone Nbr

Order Hdr Vendor Code

Order Qty

Order Required Ship Date

Order Sales Channel

Order Sales Order Nbr

Order Scheduled Ship Date

Order ShipTo City

Order ShipTo Country

Order Start Ship Date

Order Stop Ship Date

OrderDtl Cust Long Text 1

OrderDtl Cust Long Text 2

OrderDtl Cust Long Text 3

OrderDtl Cust Short Text 1

OrderDtl Cust Short Text 10

OrderDtl Cust Short Text 11

OrderDtl Cust Short Text 12

OrderDtl Cust Short Text 2

OrderDtl Cust Short Text 3

OrderDtl Cust Short Text 4

OrderDtl Cust Short Text 5

OrderDtl Cust Short Text 6

OrderDtl Cust Short Text 7

OrderDtl Cust Short Text 8

OrderDtl Cust Short Text 9

Sale Price

Vas Group Code

Order's Destination Facilities Custom field_1

Order's Destination Facilities Custom field_2

Order's Destination Facilities Custom field_3

Order's Destination Facilities Custom field_4

Order's Destination Facilities Custom field_5

Order's Destination Facilities facility type

Order's Destination Facilities priority

Order's Ship to Facility Custom field_1

Order's Ship to Facility Custom field_2

Order's Ship to Facility Custom field_3

Order's Ship to Facility Custom field_4

Order's Ship to Facility Custom field_5

Order's Ship to Facility facility type

Order's Ship to Facility Priority

Order's Destination Company Custom field_1

Order's Destination Company Custom field_2

Order's Destination Company Custom field_3

Order's Destination Company Custom field_4

Order's Destination Company Custom field_5

Order Hdr Destination Facility Custom field_1

Order Hdr Destination Facility Custom field_2

Order Hdr Destination Facility Custom field_3

Order Hdr Destination Facility Custom field_4

Order Hdr Destination Facility Custom field_5

Order Hdr Destination Facility Type

Order Hdr Destination Facility Priority

Order Hdr ShipTo Facility Custom field_1

Order Hdr ShipTo Facility Custom field_2

Order Hdr ShipTo Facility Custom field_3

Order Hdr ShipTo Facility Custom field_4

Order Hdr ShipTo Facility Custom field_5

Order Hdr ShipTo Facility Type

Order Hdr ShipTo Facility Priority

Order Hdr Destination Company Custom field_1

Order Hdr Destination Company Custom field_2

Order Hdr Destination Company Custom field_3

Order Hdr Destination Company Custom field_4

Order Hdr Destination Company Custom field_5

MHE Route Instruction Configuration

Destination Facility Code

Inventory Attribute A

Inventory Attribute B

Inventory Attribute C

Inventory Attribute D

Inventory Attribute E

Inventory Attribute F

Inventory Attribute G

Inventory Attribute H

Inventory Attribute I

Inventory Attribute J

Inventory Attribute K

Inventory Attribute L

Inventory Attribute M

Inventory Attribute N

Inventory Attribute O

Item Alternate Code

Item Barcode

Item Brand Code

Item Carrier Commodity Description

Item Case OBLPN Type

Item Catch Weight Method

Item Code

Item Cost

Item Currency Code

Item Cust Attribute 1

Item Cust Attribute 2

Item Description

Item Description 2

Item Description 3

Item Dimension 1

Item Dimension 2

Item Dimension 3

Item Excepted Quantity Instruction

Item External Style

Item Facility conveyable Flag

Item Facility Description

Item Facility Preferred Aisle

Item Facility Preferred Area

Item Facility putaway Type

Item Facility Replenishment Type

Item Full Dangerous Good Flag

Item Full OBLPN Type

Item Group Code

Item Harmonized Tariff

Item Hazard Statement

Item Hazmat Flag

Item Hazmat Packing Description

Item Height

Item Hierarchy 1 Code

Item Hierarchy 2 Code

Item Hierarchy 3 Code

Item Hierarchy 4 Code

Item Hierarchy 5 Code

Item Host Aware Item Flag

Item Invn Attribute A Tracking value

Item Invn Attribute B Tracking value

Item Invn Attribute C Tracking value

Item Invn Attribute D Tracking value

Item Invn Attribute E Tracking value

Item Invn Attribute F Tracking value

Item Invn Attribute G Tracking value

Item Is Parent Flag

Item Length

Item Limited Quantity Flag

Item LPNs Per Tier

Item max case Qty

Item Net Cost

Item NMFC Code

Item OBLPN Type

Item Order Consolidation Attribute

Item Pack OBLPN Type

Item Packing Group

Item Packing Tolerance Percent

Item Part A

Item Part B

Item Part C

Item Part D

Item Part E

Item Part F

Item Pre Pack Code

Item Product Life

Item Proper Shipping Name

Item Putaway Type

Item Recv Type

Item Regularity Code

Item Require Batch Number Flag

Item Retail Price

Item Season Code

Item Serial Number Tracking Value

Item Shipping Temperature Instruction

Item Short Description

Item SKU Line

Item Stackability Code

Item Std Case Height

Item Std Case Length

Item Std Case Qty

Item Std Case Volume

Item Std Case Weight

Item Std Case Width

Item Std Pack Height

Item Std pack Length

Item Std pack Qty

Item Std Pack Volume

Item Std Pack Weight

Item Std pack Width

Item Tiers Per Pallet

Item UN Class

Item UN Description

Item UN Number

Item VAS Group Code

Item Velocity Code

Item Volume

Item Weight

Item Width

LPN Height

LPN Length

LPN Type

LPN Putaway type

LPN Volume

LPN Weight

LPN Width

Order Hdr Carrier Account Number

Order Hdr Cust Contact

Order Hdr Cust Country

Order Hdr Cust Date 1

Order Hdr Cust Date 2

Order Hdr Cust Date 3

Order Hdr Cust Date 4

Order Hdr Cust Date 5

Order Hdr Cust Decimal 1

Order Hdr Cust Decimal 2

Order Hdr Cust Decimal 3

Order Hdr Cust Decimal 4

Order Hdr Cust Decimal 5

Order Hdr Cust Long Text 1

Order Hdr Cust Long Text 2

Order Hdr Cust Long Text 3

Order Hdr Cust Number 1

Order Hdr Cust Number 2

Order Hdr Cust Number 3

Order Hdr Cust Number 4

Order Hdr Cust Number 5

Order Hdr Cust Short Text 1

Order Hdr Cust Short Text 10

Order Hdr Cust Short Text 11

Order Hdr Cust Short Text 12

Order Hdr Cust Short Text 2

Order Hdr Cust Short Text 3

Order Hdr Cust Short Text 4

Order Hdr Cust Short Text 5

Order Hdr Cust Short Text 6

Order Hdr Cust Short Text 7

Order Hdr Cust Short Text 8

Order Hdr Cust Short Text 9

Order Hdr Customer Address

Order Hdr Customer Address2

Order Hdr Customer Address3

Order Hdr Customer City

Order Hdr Customer Email

Order Hdr Customer Name

Order Hdr Customer Number

Order Hdr Customer Phone

Order Hdr Customer PO Number

Order Hdr Customer State

Order Hdr Customer Zip

Order Hdr Customs Broker Contact

Order Hdr Destination Department

Order Hdr Duties Payment Method

Order Hdr Expiry Date

Order Hdr Host Allocation Number

Order Hdr LPN Type Class

Order Hdr OB LPN Type

Order Hdr Payment Method

Order Hdr Priority

Order Hdr Reference Number

Order Hdr Require Ship Date

Order Hdr Route number

Order Hdr Sales Order Number

Order Hdr Shipto Address

Order Hdr Shipto Address2

Order Hdr Shipto Address3

Order Hdr Shipto City

Order Hdr Shipto Contact

Order Hdr Shipto Country

Order Hdr Shipto Email

Order Hdr Shipto Name

Order Hdr Shipto Phone Nbr

Order Hdr Shipto State

Order Hdr Shipto Zip

Order Hdr Start Ship Date

Order Hdr Status

Order Hdr Stop Ship Date

Order Hdr Vendor Code

Order Number

Ship Via

Shipto Facility Code

 

Packing Restriction Rules Selection Criteria

Inventory Attribute A

Inventory Attribute B

Inventory Attribute C

Inventory Attribute D

Inventory Attribute E

Inventory Attribute F

Inventory Attribute G

Inventory Attribute H

Inventory Attribute I

Inventory Attribute J

Inventory Attribute K

Inventory Attribute L

Inventory Attribute M

Inventory Attribute N

Inventory Attribute O

Item Alternate Code

Item Barcode

Item Brand Code

Item Carrier Commodity Description

Item Case OBLPN Type

Item Catch Weight Method

Item Conveyable Flag

Item Currency Code

Item Custom Attribute 1

Item Custom Attribute 2

Item Description

Item Description 2

Item Description 3

Item Dimension 1

Item Dimension 2

Item Dimension 3

Item Dummy Sku Flag

Item Excepted Qty Instruction

Item Externan Style

Item Facility Conveyable Flag

Item Facility Item Description

Item Facility Preferred Aisle

Item Facility Preferred Area

Item Facility Putaway Type

Item Facility Replenishment Type

Item Full Dangerous Goods Flag

Item Full OBLPN Type

Item Group Code

Item Harmonized Tariff

Item Hazard Statement

Item Hazardous flag

Item Hazmat packaging Description

Item Hierarchy 1 Code

Item Hierarchy 2 Code

Item Hierarchy 3 Code

Item Hierarchy 4 Code

Item Hierarchy 5 Code

Item Host Aware Item Flag

Item Invn Attribute A Tracking Value

Item Invn Attribute B Tracking Value

Item Invn Attribute C Tracking Value

Item Invn Attribute D Tracking Value

Item Invn Attribute E Tracking Value

Item Invn Attribute F Tracking Value

Item Invn Attribute G Tracking Value

Item Is Parent

Item Limited Qty Flag

Item Lpns Per Tier

Item Max Case Qty

Item Net Cost

Item NMFC Code

Item OBLPN Type

Item Order Consolidation Attribute

Item Pack OBLPN Type

Item Packing Group

Item Packing Tolerance Percent

Item Part a

Item Part b

Item Part c

Item Part d

Item Part e

Item Part f

Item Pre Pack Code

Item Product Life

Item Proper Shipping Name

Item Putaway Type

Item Recv Type

Item Regularity Code

Item Require Batch Number Flag

Item Retail Price

Item Season Code

Item Serial Number Tracking Value

Item Shipping Temperature Instruction

Item Short Description

Item Sku Line

Item Sortable Flag

Item Stackability Code

Item Std Case Height

Item Std Case Length

Item Std Case Qty

Item Std Case Volume

Item Std Case Weight

Item Std Case Width

Item Std Pack Height

Item Std Pack Length

Item Std Pack Qty

Item Std Pack Volume

Item Std Pack Weight

Item Std Pack Width

Item Tiers Per Pallet

Item UN Class

Item UN Description

Item UN Number

Item Unit Cost

Item Unit Height

Item Unit Length

Item Unit Volume

Item Unit Weight

Item Unit Width

Item VAS Group Code

Item Velocity Code

Order Dtl Cust Field 1

Order Dtl Cust Field 2

Order Dtl Cust Field 3

Order Dtl Cust Field 4

Order Dtl Cust Field 5

Order Dtl Item Code

Order Hdr Carrier Account Number

Order Hdr Cust Contact

Order Hdr Cust Country

Order Hdr Cust Date 1

Order Hdr Cust Date 2

Order Hdr Cust Date 3

Order Hdr Cust Date 4

Order Hdr Cust Date 5

Order Hdr Cust Long Text 1

Order Hdr Cust Long Text 2

Order Hdr Cust Long Text 3

Order Hdr Cust Short Text 1

Order Hdr Cust Short Text 10

Order Hdr Cust Short Text 11

Order Hdr Cust Short Text 12

Order Hdr Cust Short Text 2

Order Hdr Cust Short Text 3

Order Hdr Cust Short Text 4

Order Hdr Cust Short Text 5

Order Hdr Cust Short Text 6

Order Hdr Cust Short Text 7

Order Hdr Cust Short Text 8

Order Hdr Cust Short Text 9

Order Hdr Customer Address

Order Hdr Customer Address2

Order Hdr Customer Address3

Order Hdr Customer City

Order Hdr Customer Email

Order Hdr Customer Name

Order Hdr Customer Number

Order Hdr Customer Phone

Order Hdr Customer PO Number

Order Hdr Customer State

Order Hdr Customer Zip

Order Hdr Customs Broker Contact

Order Hdr Destination Department

Order Hdr Duties Payment Method

Order Hdr Expiry Date

Order Hdr Host Allocation Number

Order Hdr LPN Type Class

Order Hdr OB LPN Type

Order Hdr Payment Method

Order Hdr Priority

Order Hdr Reference Number

Order Hdr Require Ship Date

Order Hdr Route number

Order Hdr Sales Order Number

Order Hdr Shipto Address

Order Hdr Shipto Address2

Order Hdr Shipto Address3

Order Hdr Shipto City

Order Hdr Shipto Contact

Order Hdr Shipto Country

Order Hdr Shipto Email

Order Hdr Shipto Facility

Order Hdr Shipto Name

Order Hdr Shipto Phone Nbr

Order Hdr Shipto State

Order Hdr Shipto Zip

Order Hdr Start Ship Date

Order Hdr Status

Order Hdr Stop Ship Date

Order Hdr Vendor Code

Order HdrCust Decimal 1

Order HdrCust Decimal 2

Order HdrCust Decimal 3

Order HdrCust Decimal 4

Order HdrCust Decimal 5

Order HdrCust Number 1

Order HdrCust Number 2

Order HdrCust Number 3

Order HdrCust Number 4

Order HdrCust Number 5

Order Number

Selection Criteria for Output Interface Configuration

Item Conveyable Flag in selection criteria for Output Interface type "Distribution Info".

Item Conveyable Flag for Output Interface type of "LPN Info".

Item Sortable Flag to Dynamic Wave Search

 

---