This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date |
What’s Changed |
Notes |
|---|---|---|
| 18 APR 2018 |
Updated document. Revised documentation link. |
|
| 18 APR 2018 |
Updated document. Revised table. |
|
| 13 APR 2018 |
Created initial document. |
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.
We would like to remind you if your system has modified security structures you may need to advise your security administrator of new features.
We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.
For information about upgrading from earlier versions, refer to the Release Announcement in Oracle Warehouse Management Cloud - Documentation for Release 9.0.0 (Doc ID 2381586.1).
The table below offers a quick view of the actions required to enable each of the 9.0.0 Update features.
| Action Required to Enable Feature |
||||
|---|---|---|---|---|
| Feature |
Automatically Available |
End User Action Required |
Administrator Action Required |
Oracle Service Request Required |
| Oracle Warehouse Management Cloud |
||||
| Functional Enhancements |
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
| Integration Enhancements |
||||
|
|
||||
|
|
||||
| Sending Allocatable or Unallocatable Flag in Inventory History |
|
|||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
| Outbound License Plate Number (OB LPN) to Delivered Status API |
|
|||
| User Experience and Usability |
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
| Option to Reprocess Failed Messages Coming from MHE Distribution Pack Complete |
|
|||
|
|
||||
|
|
||||
|
|
||||
| Matched Look and Feel of Oracle WMS Cloud with Oracle SCM Cloud Products |
|
|||
|
|
||||
Oracle Warehouse Management Cloud
The 9.0.0 Update of Oracle Warehouse Management Cloud (Oracle WMS Cloud) includes substantive improvements and changes to the following areas of the product:
- User Experience and Usability Enhancements
- Functional Enhancements
- Integration Enhancements
What follows is a brief summary. The enhancements apply to Oracle WMS Cloud Enterprise Edition unless otherwise noted. For more details about each feature and improvement, please review the What’s New 9.0.0 Update document and the official Oracle Warehouse Management Cloud documentation in the Oracle Cloud Help Center.
Oracle WMS Cloud has had REST API's for many years. However, the focus has been very functional. It has focused on:
- Data interfaces - getting transactional data in and out
- Operational APIs - specific operations to support integrating with automation systems
Version 9.0.0 includes a new set of API's that focus on exposing broader and deeper access to the system. It follows REST standards more closely to create entities (resources) and allows access to these resources via the HTTP verbs GET, POST etc. This is a multi-release feature with a focus in 9.0.0 on exposing the most commonly used entities for read access via GET and a few specific entities for creation and modification via POST. In later versions, PATCH and DELETE verbs will also be supported and POST support extended. The eventual goal is to be able to expose enough access so that it is possible for customers to create rich applications or user interfaces on top of these API's.
- Entities are queried with a SQL-like query language including support for joins between different entities
- Results are retrieved either in whole, or paginated and fetched in chunks
- URI representation of individual objects
- Support for releasing of the API. Every year a new version number will be included in the URL so that the API can be released. The previous year's API will be supported for one year and can be removed a year later.
The previous set of APIs will continue to be supported as is and may be slightly enhanced but the main focus going forward will be the new API's.
In version 9.0.0, the application has been extended to accept quantity in decimals in all areas of the application. You can enter quantity in decimals in handheld devices (RF) or Web based UI screens and also Input Interfaces/APIs. Until version 9.0.0, only some RF Modules captured quantity in terms of decimals for items with a conversion factor greater than one. Decimal entry for quantity fields was not supported from the UI. The following are major highlights of the decimal support changes:
- The new field handle_decimal_qty_flg is added to item entity. Customers that want to track inventory for items in decimals will have to set the flag value to Yes. The field is exposed in the item interface and also on the Item User interface. The default value is false.
- The Item decimal handling flag cannot be enabled if items are also serial number tracked. You cannot configure items tracking serial numbers or inventory with decimals.
- Changing the item decimal handling flag from true to false does not impact existing data. Inventory is present in decimals even though the item is not tracking decimals.
- The Prepack interface item is expanded to support the definition of child sku's and the corresponding quantity in terms of decimals. Parent items can also be configured to track decimals. The ratio definition for the underlying child items in item prepack is for one unit of the parent item.
- Two new fields are added to the company table which control the number of decimals supported for quantity related fields (inventory quantity) and Weight/Volume/Dimension related fields. Customers configure same or different decimal scale for quantity related fields and Weight/Volume/Dimension columns. New action button has been introduced to company table for configuring the values. The action button is security controlled. Default value for quantity related decimal scale field will be 0 and default value for the Weight/Volume/Dimension setting will be 5.
- The max number of decimal digits that can be configured for quantity, Weight/Volume/Dimension fields is 25. Customers need to change the field value for quantity depending upon whether they have sku's which needs to have inventory in decimals. Decreasing/Increasing the decimal scale will not modify any existing data. It is recommended to have this value configured properly from the beginning and not change this.
- From version 9.0.0 onwards, Oracle WMS Cloud stores quantity in decimals. As customers upgrade from previous versions, sku's marked with a conversion factor greater than 1 will be marked to track decimals and the conversion factor value will be set to 1. During the upgrade process, the corresponding inventory quantity is divided by the conversion factor value. The item conversion factor will not be available for customers to be changed from version 9.0.0 onwards. Future versions will deprecate the item conversion factor field.
- Input Interfaces are expanded to allow values in decimals for items which are tracking decimals. All input interfaces with quantity fields support values to be interfaced with decimal values. Interfaced quantity values interfaced are rounded if the number of nonzero decimal digits is more than the corresponding company setting for the quantity. The number of decimals is rounded as per the corresponding company setting for quantity fields. The input interface will fail if the item is not tracking decimals and you interface value with decimals. Weight/Volume/Dimension-related fields interfaced through input interfaces are rounded if the number of non-zero decimal digits is more than the corresponding company setting for Weight/Volume/Dimension. Refer to the interface specification for details on which fields on the input interface allow decimals and which fields are rounded.
- Scheduled data extracts (job types beginning with ‘Extract’) may not honor the company level decimal accuracy settings. You may get more precision than that is set. These extracts are not meant for standard integration with ERP systems, but for use with your own reporting systems.
- Existing API's modifying inventory accept quantity in decimals and the value is rounded as per the company setting.
- From version 9.0.0 onwards you can enter quantity in decimals across all RF Screens where quantity entry is supported.
- The quantity entry field restricts the number of decimals based on the corresponding company setting. You can enter quantity in decimals only if the corresponding setting on the company has a value greater than one and the item is configured to track inventory in decimals.
- Certain RF Screens do support Sku Scan as well. If items tracking decimals is scanned, each scan of sku is assumed to be one unit. Picking units in SKU Scan mode for fractional units is not supported in RF. You should use RF screens with the quantity entry mode enabled for items tracking decimals.
- RF Screens configured to enter quantity with UOM of Packs or Cases will not allow decimal entry. Decimal entry will be supported for UOM of Units only. Even though the application allows up to 25 digits after decimals, due to space constraints in the RF Screens quantity values displayed in the RF can be truncated.
- Some of the RF Screens support weight capture entry. The number of decimals supported in weight entry is limited based on the corresponding company setting for Weight/Volume/Dimension. Weight entry should be supported in decimals irrespective of whether the underlying item is tracking decimals or not.
- Weight/Volume Related fields computed in RF Screens as part of LPN creation, LPN Modification, or Capacity determination for location are subjected to rounding based on the corresponding company setting for Weight/Volume/Dimension.
- RF screens which support adjustments like RF Modify LPN, RF Cycle Counting can handle entry of quantity in decimals and even post inventory adjustments in decimal quantity. For items not tracking decimals if the inventory quantity is in decimals, RF Cycle Counting has to be used to correct the inventory quantity. This situation can arise if the decimal handling flag is flipped from tracking to not tracking and also if the company scale for quantity is reduced. You should not change the value.
- Until version 9.0.0, the web UI did not allow Quantity Entry fields like Ordered Qty, Shipped Qty, or Quantity fields related to inventory or allocation to accept the values in decimals. From version 9.0.0 onwards, Oracle WMS Cloud is enhanced to accept decimals for quantity-related fields.
- Quantity-related fields for inventory support decimal entry. Corresponding quantity fields restrict the number of decimal digits based on the company setting for quantity.
- If an item is not tracking decimals and you enter a value in decimals, Oracle WMS Cloud will prevent the record from saving.
- Weight/Volume/Dimension-related fields support entry in decimals and the number of decimal digits is restricted based on the corresponding company setting for Weight/Volume/Dimension.
- Price-related columns restrict the number of decimal digits to two.
- The application displays quantity/weight/volume/dimension-related columns without any trailing zeros and the UI display does not round the values.
- Weight/Volume-related fields computed as part of UI operations like LPN creation, LPN Quantity Adjustment, or outstanding capacity determination for location are subjected to rounding based on the corresponding company setting.
- Prior to version 9.0.0, only limited output interfaces supported quantity values in decimals based on the item’s conversion factor value. From version 9.0.0 onwards support for sending quantity in decimals is extended to all base output interfaces published in the interface specifications.
- All output Interfaces are expanded to support send quantity values in decimals. Quantity values are subjected to rounding if the determined value has a higher number of nonzero decimal digits than the corresponding company setting for quantity.
- Even if the item is not tracking decimals and corresponding inventory quantity has decimal values, decimal digits are not truncated.
- All output Interfaces are expanded to support send weight/volume/dimension-related values in decimals. Generated values are subjected to rounding if the determined value has a higher number of non-zero decimal digits than the corresponding company setting for quantity.
Oracle WMS Cloud will send quantity in decimals for the base interfaces we support with Material Handling Equipment (MHE). Implementation teams should judge whether MHE is handling decimal qty or not. Your implementation team should consider whether external systems can handle decimal quantities before configuring items in decimals.
- With version 9.0.0, the inventory quantity present can be in decimals. Orders can also be interfaced with decimal quantity. You can now interface order with decimal quantity. You can also allocate inventory in decimals
- All different wave allocation strategies will support allocation of orders if the order has the order quantity in decimals and also with inventory having decimals. Decimal allocation is supported only when allocation UOM is Units.
- Cubing and Tasking logic is enhanced to handle allocations in decimals. For decimal tracked items, the number of units cubed into an LPN is in decimals based on Capacity settings of the determined outbound LPN type.
- For decimal tracked items, Cubing logic will infer the minimum quantity to split an allocation based on the decimal scale value configured for the company when the cartonized UOM is configured as Cubed. If the item is not tracking decimals, the minimum quantity to split an allocation will be one unit.
- If the item is not tracking decimals and if the underlying inventory is in decimals, then Oracle WMS Cloud allocates the inventory in decimals. Note that picking does not happen for fractional units and you will have to short the fractional units which cannot be picked. You should not switch the decimal handling flag for the item when inventory is present in decimals. Cycle Counting should be used to post the discrepancy. You will be able to post adjustments
- All picking flavors are enhanced to handle picks and packs in decimals for items tracking decimal quantity if the allocation UOM is units. Non Cubed Active Picking and RF Distribute LPN supports auto pack one UOM functionality. Auto Pack one UOM will cube one unit into the outbound LPN for items tracking decimals. Fractional items remaining due to allocation in terms of decimals will go into its own quantity.
- Work Order Wave logic is enhanced to handle work order qty in decimals if the parent is tracking decimal quantities. Also, support for handling child items ratios in decimals is included. While computing the required component item, the value can be rounded as per the decimal setting at the company level.
NEW INVENTORY ATTRIBUTES
Version 9.0.0 provides better flexibility for customers in industries that are required to store multiple attributes. Fifteen attributes are available in the system, so customers whose business requirements need multiple fields to store this information can now use the extra field Inventory Attributes. Please note that the new inventory attributes H to O can only be interfaced in the application. You are not prompted for these attributes in the RF. New attributes added do not have item level tracking flags and support for capturing inventory attributes is only available for inventory attributes A to attribute G.
The following features are completed to support this change:
- Eight new attributes (H, I, J, K, L, M, N, and O) are added to support a total of fifteen attributes. All Inventory Attributes support a length of 75 characters.
- Support for sending all fifteen attributes through the following Input Interfaces: Purchase Order (PO), Inbound Shipment, Order, Point of Sale, and Work Order.
- Support for sending all fifteen attribute through the following Output Interfaces: Shipment Verification file, Inventory History file, Outbound License Plate Number (OBLPN) Shipping Info, Pallet Shipping Info, SLS File, PLS, File, LLS File, License Plate Number (LPN) Inventory, Order Out Interface, TO MHE Distribution Info, To MHE Inbound License Plate Number (IBLPN) Info, and Order Verification.
- You can see the new attributes in UI Screens related to Inventory such as Purchase Order User Interface (UI), IBLPN UI, Reserve Inventory UI, etc.
- Additional Inventory Attributes (H-O) have been exposed only for PO Extract, Inbound Shipment Extract, Inbound LPN Detail Extract, and Outbound LPN Detail Extract.
- Create Shipment from PO now copies the new inventory attributes to IB shipment.
- Create Return Advanced Shipping Notice (ASN) from Order UI or OBLPN UI copies new inventory attributes to ASN.
- New inventory attributes in Shipment detail are copied to LPN’s created as part of receiving.
- New inventory attributes are transferred to IBLPN when using RF Split IBLPN.
- When you use Radio Frequency (RF) Pack LPN, new inventory attributes are transferred from IBLPN to OBLPN.
- When you use RF Split OBLPN, new inventory attributes are transferred to OBLPN. When you use RF Modify OBLPN, new inventory attributes are transferred.
- RF Create LPN from Active now transfers the new inventory attributes to the created IBLPN.
- Ignore Order Detail Inventory Attributes H to O are now available in allocation mode sequence.
- RF NC Active Picking shows new inventory attributes when you invoke control key CTRL-V
- The following APIs have been expanded to expose new inventory attributes: Create LPN API, Inventory Adjustment API, From MHE Distribution OBLPN Pack API, and From MHE distribution Short API.
- New Inventory attributes have been added in the Sorts, Filters, and Layouts of the following Web Report Categories: AllocationFromInventory, AllocationToInventory, CCAdjustmentHeaderDetail, ContainerLocks, Inventory, InventoryItemLocation, SimpleInventory, and InventoryHistory.
- New inventory attributes are available in the search criteria on the following Output Interface Configuration: LPN Inventory and OBLPN Shipping Info
- Label Designer now considers the new inventory attributes.
- The Restrict Inventory Attribute flag in location is honored during Wave Based Replenishment allocations or Order based replenishment.
Mass Update of Inventory Attributes
A new button “Mass Update Attributes”, is available from the IBLPN UI. The action button is permission controlled, only those with permissions can perform mass update. In order to perform Mass Update, you can use the search criteria to narrow down the number of records that need to be updated. Oracle WMS Cloud issues an error message when no filter criteria is applied before performing "Mass Update Attributes". Once you click "Mass Update Attributes", Oracle WMS Cloud lets you know the number of records that are updated so you can have an idea of how many records will be affected or that you can cancel/continue.
After confirming the number of records, you are able to update the inventory attributes A-O and putaway type only. The records that are filtered and in the status Received and Located are eligible for update. The process of updating can take time depending on the number of records handled. Any modification in the inventory attribute (a to o) is updated back to the IB Shipment detail, if the corresponding IB Shipment is not verified.
Upon successful update, the inventory records for the same item within the LPN that are identical are merged together into a single inventory record. Mass update of attributes is performed on LPN, which are in a specific status i.e. Received, or Located.
Display Standard Pack and Case Quantity Equivalents
From version 9.0.0 onwards items and item prepack standard pack quantity, case quantity, max quantity fields only support integer values with no decimals. Even if an item is tracking inventory in decimals corresponding to the item’s standard pack quantity, case quantity, and max quantity fields do not support values in decimals.
Receive Entire Shipment in Browser Enhancement
Prior to version 9.0.0, if you were receiving an Inbound Shipment using “Receive Entire Shipment”, the information related to the pallet was not passed after receiving even if the Inbound Shipment contained this information. In version 9.0.0, customers that track pallet numbers can now use “Receive Entire Shipment”, and the pallet number associated with the LPNs is updated in the container. The “Pallet Number” field is now available in the edit pane of the IB Shipment detail. You can add or edit the Pallet Number in the IB Shipment detail UI. You can use Receive Entire Shipment to keep the association between the LPN and the Pallet number in the IB Container UI, Pallet UI, and Pallet History UI after receiving a cartonized IB Shipment.
Auto Create Transfer Shipment Facility Parameter
When a new facility is added in Oracle WMS Cloud, the facility parameter CREATE_FACILITY_TRANSFER_SHIPMENT_FOR_ALL defaults to YES. Version 9.0.0 changes the behavior of this parameter so that if the value is blank or NULL, it is treated as NO, and a transfer shipment is not created. In order for a transfer shipment to be created in the target DC, the value has to be explicitly set as YES, Y, or TRUE. Blank, NULL, or any other value is treated as NO.
Configurable Lock Codes for RF Create LPN
In version 9.0.0, a new parameter default-lock code is available in RF CREATE LPN, and you can set up the default lock code to be applied when you create an LPN using RF CREATE LPN. The same parameter is available in CREATE LPN API. If customers do not want a lock code to be applied to the LPN, the value in the parameter should be blank. This feature provides customers the flexibility to assign specific lock codes to the new LPN.
3PL Task Management Improvements
Version 9.0.0 enhances the Task Management Module to include Company ID on the task. This new functionality is a great feature for 3PL Customers, as they may want to restrict users from running tasks for companies that they are not eligible. Version 9.0.0 populates the Company ID of the task. You can see the Company ID and the Facility fields on the Task UI. In the RF, the Execute Task Transaction only displays tasks that are eligible according to the eligible company setting. Tasks created prior to this change with a null Company ID will still be available to all the users in the RF.
Selection Criteria Enhancements
Version 9.0.0 includes selection criteria rules enhancements for the following: Putaway Type Selection Criteria Rules, Inbound Sorting Criteria, Task Creation Criteria Rules, Cycle Count Task Creation Rules, Outbound Sorting Selection Criteria, Dynamic Staging Selection Criteria, Sort and Receive Selection Criteria, Dynamic Wave Search Selection Criteria, MHE Route Instruction Configuration, Packing Restriction Rules Selection Criteria, Outbound Audit Rules and Selection Criteria for Output Interface Configuration. Refer to the Appendix for detailed selection criteria information.
SUPPORT FOR IN, NOT IN OPERATOR IN SELECTION CRITERIA RULES
- The operators IN, NOT IN. and <> are treated as basic operators.
- The IN operator allows you to select a record if a column value matches any value in a list of values defined in the selection criteria for that expression.
- The NOT IN operator allows you to exclude a record if the column value matches any value in a list of values in the selection criteria for that expression.
- The <> operator represents Not Equal To which allows you to exclude a record if the column value matches the value specified in the selection criteria.
- These enhancements are applicable in Putaway Type Selection Criteria Rules, Task Creation Criteria Rules, Cycle Count Task Creation Rules, Dynamic Wave Search Selection Criteria, Cubing Rules, and Outbound Audit Rules.
SUPPORT FOR SPECIFIC FORMAT FOR DATE AND DATETIME RELATED FIELDS IN SELECTION CRITERIA RULES
- You need to specify date columns in the selection criteria rules with the prescribed format of YYYY-MM-DD.
- The format for datetime-related columns in the selection criteria rules is YYYY-MMDDTHH:MM:SS.
- These enhancement are applicable in Putaway Type Selection Criteria Rules, Task Creation Criteria Rules, Cycle Count Task Creation Rules, Dynamic Wave Search Selection Criteria, Cubing Rules, and Outbound Audit Rules.
Allocation Methods on Allocation Modes
Version 9.0.0 introduces an allocation method on the allocation mode. You now have the ability to set different allocation methods on each allocation mode defined on a wave template. If the allocation mode is not set on a specific allocation mode, then the allocation method for that particular sequence defaults to the allocation method set on the wave template.
The new transaction “RF Consume LPN” allows you to consume an LPN on the RF device, and it asks you for a reason code if a default is not provided on the screen parameter. This transaction is helpful for customers that need to transfer inventory to other systems such as manufacturing to remove the inventory from the LPN. Only LPNs with a Located status are available to be consumed and the user is required to enter a reason code. This transaction records an Inventory History Transaction IHT-2 container consumed. It will have the LPN, Item, lock codes, reason code, and inventory attributes.
A new flag is added to the Lock Code UI, “Prevent direct consume”. If the LPN has a lock code with this flag on, the system does not allow you to consume this LPN.
Version 9.0.0 introduces multi-field barcode scanning. These are single barcodes (either 1D or 2D) that contain multiple values within them, such as the LPN number, the item barcode, and manufacture date. Multi-field barcode scanning saves time and increases operational efficiency. You can configure multiple classes of multi-field barcode scanning and define different sets of supported fields within each class. Each multi field barcode class defines all possible fields, and not the contents of any one specific barcode. A class is identified by different prefixes. The barcode scanner must be configured appropriately. Multiple classes can be defined and enabled or disabled. The application has a default multi field barcode class that is a subset of the GS1 spec, including fields (AI's or application identifiers in GS1 terminology) that are frequently used in warehouse management. Each field is associated with a standard barcode type.
All RF screens can now recognize multi-field barcode scanning based on the prefix. Once a certain class is detected, it extracts all the component fields and they are used within the current RF operation. For example, if a receiving option expects an LPN number, manufacturing date, SKU, and count via entry fields (that may be on multiple screens), and a barcode containing the LPN number, manufacturing date and SKU is scanned, all three values will be extracted and used automatically.
The application validates all three fields automatically and moves to the quantity field. In certain modules like Cycle Count modules, it is possible to configure it to restrict multi-field barcode scanning to just apply to the current field and not to extract all fields. A new RF parameter, Multi field barcode restricts to current field has been added for this purpose.
New functionality has been added to Label Design to print GS1 barcodes. Refer to Enhancements to Label Designer for more details.
In version 9.0.0, the following Barcode Types Entries have been added:
- Count
- Expire Date
- Weight
- Manufacture Date
Version 9.0.0 has added Basic Yard Management functionality to Oracle WMS Cloud. This allows the tracking of trailers in the yard and dock locations.
A new location type called Yard is available in Oracle WMS Cloud. You can now create, copy, edit, and filter yard locations in the Locations UI screen similar to other location types. Oracle WMS Cloud also supports interfacing Yard locations into the system.
The trailer UI is enhanced to include location information. This helps to show if a trailer is in the dock location, yard location, or not located. You can also use this view to locate trailers to yard locations or move trailers from one yard location to another. Oracle WMS Cloud supports validation to ensure that this view is only used to locate trailers to the yard location and not to dock locations. Locating the trailer to yard location creates a new inventory history record Yard Movement that has information about the Trailer, the location to which it has been moved, along with other key fields related to the trailer.
Checking in an appointment now updates the dock location on the trailer. Since this is typically done when trailers are moved from yard to dock doors, this action also generates the Yard Movement Inventory History Record. Checking out an appointment clears out the location information on the trailer. You can move the trailer back to the Yard location in the Trailer UI. In general, any movement of Trailer from or to Yard locations triggers the creation of the Yard Movement Inventory History Record.
Similar to appointment check in/out, checking in inbound loads using the Inbound Load screen also results in an update of the dock location on trailer. Checking out the load clears the location and you have the option to update to the yard location via the Trailer UI. Again, any movement of Trailers from and to yard locations will trigger the creation of IHT-81 Yard Movement Inventory History Record.
Version 9.0 supports updating the trailer number from the Inbound Load Inquiry Screen. Updating the trailer number from the Appointment screen is no longer supported.
For an Inbound Shipment Inquiry, if the trailer number is changed for an inbound load that is checked in, the trailer number on the underlying appointment is updated with the new trailer number. This results in an update of the corresponding locations on the old and new trailers. The Yard Movement Inventory History Record is written for both old and new trailers. The record for the old trailer indicates movement from dock location to an undefined (blank) location. The record for the new trailer indicates movement from an undefined (blank) location to the dock location.
Similarly, on OB Load Inquiry, if the trailer number is changed for an outbound load that has been checked in, the trailer number on the underlying appointment is updated with new trailer number. This results in update of corresponding locations on the old and new trailers. Yard Movement Inventory History Record is written for both old and new trailers. The record for the old trailer indicates movement from the dock location to an undefined (blank) location. The record for the new trailer indicates movement from the undefined (blank) location to the dock location.
Finally a validation has been added in the system to ensure that the same trailer number associated with different inbound/outbound Loads cannot be checked into different dock doors at the same time.
Enhancements to Label Designer
You can now generate/print valid Multi-field barcode scanning using Label Design. This new functionality allows you to specify the barcode construction by editing the expression field of the barcode on Label Design. This gives you the ability to have a function’s text inside the expression field, so that the system can generate a multi field barcode with the different parts of the GS1 code. You can use either Data Matrix type or UCC_128 to create this barcode, and you should map the Article ID to an existing column, and use the following format when creating a label expression:
[Start C Character] + [FNC1 Character] + Barcode Prefix + [Code A Character] + Merchant ID + [Code C Character] + Article ID (without Merchant ID + [Symbol Check Character] + [Sop Character]
The label designer data grid can now be setup to use metric measurements instead of imperial measurements, which will be helpful in countries using metric.
Inventory History File Updates
The Inventory History interface is now updated to include to_location for warehouse movements and a creation time stamp.
Detailed Serial Number Inventory History Integration
ENHANCEMENTS TO INVENTORY HISTORY
Prior to Version 8.0.2/9.0.0, if the item in question was serial number tracked, some of the Inventory History Activity Records are split by serial number. For each distinct serial number a separate inventory history record is written. From Version 8.0.2 onwards support is added for some more additional Inventory History Records to perform split by serial number if the item being handled is tracking serial numbers.
The following additional activity types are enabled to split by serial number:
- 14-Container Cancelled
- 23-Lock Container - After ASN Verification
- 24-Unlock Container - Before ASN Verification
- 25-Unlock Container - After ASN Verification
- 36-Split Container Lock Acquired
- 39-Cycle Count - Lost IBLPN counted
- 40-Cycle Count - IBLPN Lost
- 49-Lock Active
- 50-Un Lock Active
- 63-Lock Update pre-verification LPN
- 64-Lock Update post-verification LPN
- 65-Lock OBLPN
- 66-Unlock OBLPN
- 80-Container Delivered
- From versions 8.0.2 onwards, you can configure inventory history records split by serial number. This provides flexibility where customers can turn off serial number information to be written for supported Inventory History records.
- A new UI Module (Inventory History Activity Parameters) allows you to configure splitting by serial number or not against each inventory history activity code. Splitting the inventory history by serial number can only be carried out for activity codes which have support_split_by_srl_nbr_flg set to Yes. If the support_split_by_srl_nbr_flg is set to No (example Order Detail Shorted, Appointment Change etc.) then you will not be able to configure that particular inventory history to be split by serial number. Inventory History Activity which has Enable split by serial nbr flg set to yes is split by serial number if the item is tracking serial numbers and the company is configured to track serial numbers.
- By default when clients upgrade to 8.0.2, the inventory history records referenced above have Enable split by serial nbr flg set to No and are not split by serial number. To exclusively turn on the configuration to split Inventory History by serial number, you should go to the Inventory History Activity Parameters UI.
- Inventory History activity codes which were supported to split by serial number prior to version 8.0.2 have the Enable split by serial nbr flg set to yes by default so that the current behavior is not modified. Clients should change the configuration from Inventory History Activity Parameters UI if there is any need to change the behavior.
- By enabling split by serial Number of Inventory History there will be a significant increase in volume of IH transaction.
Sending Allocatable or Unallocatable Flag in Inventory History
- Oracle WMS Cloud can apply lock codes on the Inbound LPN. The applied lock codes make inventory allocatable or not for downstream operations like allocating for a sales order. This is controlled through the allocatable flag on the lock code. When the lock code is applied or removed from the corresponding inventory, the Inventory History record which contains the lock code information is written. Other systems consuming inventory history record when the lock code is applied might not know which lock code has the allocatable flag set to yes or no. From version 9.0.0 onwards, the Inventory History Transaction will inform if inventory is allocatable or not as a REF VALUE field using REF CODE Previous Allocatable State (PAS) or Current Allocatable State (CAS).
- When the lock code is applied or removed on an Inbound LPN, Oracle WMS Cloud determines whether the lock codes currently present on the inventory are allocatable or not. Even if one of the lock codes on the inbound LPN is unallocatable, the current allocatable state (CAS) reference field value will have a value of "No". If all the lock codes present for the inbound LPN have an allocatable flag set to yes or if none of the lock codes are present on the inbound LPN, the CAS reference field value is “Yes”. If the active location or inbound LPN has a lock code which is unallocatable and after removing the lock code none of the outstanding lock codes have an allocatable flag set to yes, then the previous allocatable state PAS field value is “No” and the current allocatable state CAS reference field value is yes.
- When we do inventory adjustments, the Previous Allocatable Status (PAS) and Current Allocatable Status (CAS) of the corresponding Inventory record are populated. If the adjusted inventory is an existing one, the previous allocatable status is set to Yes or No based on whether the corresponding lock code is allocable or not. If the inventory is adjusted to zero, then the previous allocatable status is set to Yes or No based on whether the adjusted inventory has an unallocatable lock code or not. Even if one of the lock codes on the adjusted inventory is unallocatable, the previous allocatable state (CAS) reference field value will is "No". The current allocatable status of the inventory is blank. For inventory adjustments marked for Quality Control (QC), both the previous allocatable state (CAS) reference field value and the current allocatable status reference field is set to “No”.
- In addition to Locking/Unlocking and Inventory adjustments, version 9.0.0 populates the allocatable status of inventory in the corresponding Inventory History records when inventory creation is initiated. This process is part of Receiving/Creating an LPN or Accepting or Rejecting after performing QC Operations. For some of the Inventory History records, Reference Fields 11 and 12 have the value of Previous Allocatable status and current allocatable status. For some of the Inventory History Records reference fields 12 and reference fields 13 get populated with previous allocatable status and current allocatable status. Refer to the interface specifications for more details on which reference fields carry the values and the corresponding Inventory History records.
NOTE: Two reference fields are reserved; one to hold the previous allocatable status of the inventory and another reference field to hold the current allocatable status of the inventory.
Inventory Summary – Alphabetized Lock Codes
Default Custom Inventory Summary (CINS) currently exposes columns which hold the lock code values and the corresponding quantity associated with it. Oracle WMS Cloud exposes 10 column pairs which hold the lock code values and the corresponding quantity associated. From version 9.0.0 onwards, when the Custom Inventory Summary is generated for each item/batch combination where inventory is present, underlying lock codes are ordered in alphabetical sequence. The number of Lock Codes displayed for each item/batch combination is limited to ten.
RF Distribute LPN Enhancements
In automated facilities, after inducting LPN to the Material Handling Equipment (MHE) LPNs went to a Reserved status awaiting MHE completion messages. Now you can complete the Distribute LPN tasks in the RF UI that were in-flight instead of awaiting MHE completion messages.
ADD CREATE TIMESTAMP AND TO LOCATION IN THE INVENTORY HISTORY OUTPUT FILE
Currently we have Create_Date format (yyyymmdd) in the Inventory History Output file, but we do not send the time. However, some external systems also need the time. Instead of changing the existing field to include the time, the Create_Ts format (yyyymmddhhmn) field has been added to the output file which has the same date information as create date and time.
From Version 9.0.0 onwards, the to_location field is exposed in the Inventory History Output File. Now you can see the to_location value populated when you perform the IHT-51 inventory movement.
Currently, Oracle WMS Cloud allows you to configure items at the company level, so weight and dimension values cannot be stored using different system for each facilities. For companies that have facilities that handle imperial and metric systems such as US and UK and ship using FedEx to those two countries, shipping could fail. FedEx only takes Imperial values when shipping to or within the US. In order to prevent shipping from failing, two new company parameters have been added. PARCELDIMENSIONS-UOM and PARCEL-WEIGHT-UOM. The values accepted are IN/CM or LB/KG respectively. This identifies how dimensions and weight are stored for the company, and if you are shipping using FedEx to the US, Oracle WMS Cloud will check the parameters and it will make the necessary changes so the request is in the Imperial System.
Wave Pick Information Integration Enhancements
The Wave Pick Info file contains information about items and locations where these items have to be picked. In warehouses that have MHE, this file is typically sent to WCS (Warehouse Control Systems) that eventually control PTL (Pick To Light) systems based on this information. In certain warehouses, information in this file is also used by external systems to print relevant labels that need to go on each picked unit.
Apart from the order header and detail information that is already present on this file, version 9.0.0 also includes all of the custom fields from Order Header and all of the custom fields from Order Detail in this file. Custom fields are sometimes used by host systems to send additional information about the order and items ordered. Custom fields on the wave pick info file also help external systems use this information for labels or WCS systems as required.
Order Interface Enhancements for Oracle SCM Cloud
The Order interface now supports fields intended to enhance the ability to build outbound fulfillment integrations with Oracle Order Management Cloud, Oracle Transportation Management Cloud, and Oracle Inventory Management Cloud. The additional fields include reference numbers from the Oracle Order Management Cloud sales order, Oracle Inventory Management Cloud customer shipment, and Oracle Transportation Management Cloud order releases (representing transportation shipments).
Send Output File After Ship OB LPN
You can ship a packed OBLPN (Outbound LPN) out from a facility independent of a load either by using the RF Ship OBLPN option OR if external systems invoke the ship request via the Ship OBLPN API. Currently when an OBLPN is shipped using either option, no file is generated. Version 9.0.0 allows you to generate either the OBLPN Shipping Info file or the LPN Inventory file after an OBLPN is shipped using either the RF option OR the API option.
A new parameter has been added to both RF Ship OB LPN and Ship OBLPN API. You can use this parameter to define which file needs to be generated after shipping an OBLPN using one of these options. You can also leave the parameter blank if no file is required to be generated.
The current OBLPN Shipping Info file that is generated for OBLPNs during a wave run OR generated from LPN Inquiry is modified to include additional fields required for external systems. Apart from existing information, the file now includes the status of the OBLPN, the Load Nbr, Manifest Nbr, Carrier Code, Carrier Type, Inventory Attributes, and Order-related dates.
The LPN Inventory file remains the same as the one which is currently generated through MHE route instruction.
Allocatable and Unallocatable Status Change In Integration
Many inventory history transactions now include if the transaction has changed the materials status to allocatable or un-allocatable. This additional information streamlines integration with external systems such as ERP’s.
Point Of Sale (POS) Interface Serial Number Enhancements
The Point of Sale (POS) Interface supports the transaction types "Sale" and "Return". Version 9.0.0 includes several changes to Point of Sale interface.
- The Point of Sale interface now accepts serial number information while processing the transaction type of "Sale" or "Returns".
- If Serial Number information is passed, the returned quantity should be one. A serial number which is subjected for a sale transaction is marked Shipped in the Serial number history.
- If the serial number passed on the Sale Transaction type is subjected to validations, serial numbers associated with outbound LPN's in Loaded or Shipped status are not allowed to be subjected to Sale transaction.
- The Returns transaction type also supports passing of serial number information. The returned quantity cannot be greater than one when serial number information is passed.
- A Returned Serial number is also subjected to validations before accepting the returned serial number. The serial number returned should not already be linked to any inbound LPN (Received, Located, Partly Allocated, Allocated status) or active location or outbound LPN (In Picking, Picked, Packed, Loaded) where returns are processed. A returned serial number does not need to match the serial number corresponding to the sale transaction performed. This behavior is controlled using a new company parameter.
- The new company parameter POS_RETURNS_INVN_VALIDATION performs transactions of type Return. This parameter accepts three values and the behavior is outlined for all three options.
- ALLOW_ANY_SKU: In this mode, Returns will validate for the Sale transaction Number and Sequence Number. You can return any item even though the item is not part of the corresponding sale. If the item shared is tracking batch numbers, expiry dates, inventory attributes or serial numbers and if the corresponding value is not populated, Oracle WMS Cloud inherits those missing values from a relevant Sale transaction as long as the sku matches.
- SKU_MATCH_ONLY: In this mode, Returns will validate for Sale transaction Number and Sequence Number and returned sku should match the sku sold on the corresponding sale transaction. Returned Batch/Expiry date/Inventory Attributes/Serial number need not match what is on Sale transaction. If the item shared is tracking batch numbers, expiry dates, inventory attributes or serial numbers and if the corresponding value is not populated, Oracle WMS Cloud inherits those missing values from the relevant Sale transaction as long as the sku matches.
- MATCH_SKU_AND_ATTRIBUTES: This enforces strict restriction. The returned sku/Batch/Expiry date/Inventory Attributes/Serial number combination has to match against the corresponding sale transaction.
- You can configure any of the below options based on the desired work flow.
Serial Number Length Increased
From Version 9.0.0 onwards, the field length of serial_nbr column is increased to 40 characters in the following input interfaces:
- IB_SHIPMENT_SERIAL_NBR
- POS
- ORDER
- ORDER_HDR_DTL
- ORDER_DTL
Unsupported Input Interfaces Removed
In the past, Oracle WMS Cloud provided an option to interface order data via two formats called picktickets and storedistro, through the Input Interfaces UI. However, these are long deprecated interfaces and are no longer used and have been removed. Clients need to use the Order interface instead.
XML Support for Additional Input Interfaces
For most input interfaces Oracle WMS Cloud, Web Services is enabled. In other words, apart from file based integration (using PSV/CSV format), currently Oracle WMS Cloud provides Web Service support using XML format for most of the input interfaces. Version 9.0.0 has enabled Web Service support for the following input interfaces listed below:
- CUBISCAN
- POINT_OF_SALE
- LOCATE_LPN_LOCK
- PRICE_LABEL
- DEST_FACILITY_ATTRIBUTES
- ASSET
- USER
OAuth2.0 Token Based Authentication
Version 9.0.0 includes support for OAuth2-based authentication for Oracle WMS Cloud REST APIs. This supports integration of Oracle WMS Cloud.
Version 9.0.0 introduces the following changes to the legacy APIs. The first one is the permission "common.lgfapi_update_access" which replaces "wms.can_run_ws_stage_interface". This permission allows you to run the legacy APIs. The new company level decimal settings are to be stored and displayed in the system. The following changes are done to the legacy API's, so either the incoming or outgoing data complies with the configuration set up for decimal support:
Update OBLPN Dims legacy API:
- Company parameter max_allowed_wt_vol_dim_decimal_scale now controls the decimal precision of the following fields: length, width, height, weight, and volume.
Update Tracking Number legacy API:
- Company parameter max_allowed_wt_vol_dim_decimal_scale now controls the decimal precision of the weight fields: weight and dry_ice_weight
- The precision of rate fields is set at 2
Create LPN legacy API:
- Company parameter max_allowed_qty_decimal_scale now controls the decimal precision of the quantity fields :qty
- Company parameter max_allowed_wt_vol_dim_decimal_scale now controls the decimal precision of the weight fields: lpn_weight
Load OBLPN legacy API:
- Company parameter max_allowed_wt_vol_dim_decimal_scale now controls the decimal precision fields: oblpn_weight
Update Active Inventory legacy API:
- Company parameter max_allowed_qty_decimal_scale now controls the decimal precision fields: actual_qty and adjusted_qty
MHE pick_confirm legacy API:
- Company parameter max_allowed_qty_decimal_scale now controls the decimal precision fields: qty
- Applies to the PICK and SHORT scenarios
From MHE Distribution Pack legacy API:
- Company parameter max_allowed_qty_decimal_scale now controls the decimal precision fields: uom_qty and packed_qty
From MHE Distribution Short legacy API:
- Company parameter max_allowed_qty_decimal_scale now controls the decimal precision fields: short_qty
As warehouse systems become more interconnected, this new API allows external systems, such as manufacturing lines, to create a LPN in the Oracle WMS Cloud.
This new API allows you to consume an LPN. This API is useful for clients that need to transfer inventory to other systems such as manufacturing, and this API allows you to record this information. The API allows LPNs in a Located status to be consumed, but the system must send a valid reason code. This information is recorded in an Inventory history transaction IHT-2 consumed container. IH2 is written with the Consume LPN API.
Outbound License Plate Number (OB LPN) to Delivered Status API
When an LPN that is a part of a facility transfer shipment is received at a destination facility, the status of the outbound LPN (OBLPN) is marked as delivered in the origin facility. Currently this feature of updating OBLPNs to a delivered status is applicable only to OBLPNs that are part of a transfer shipment.
Version 9.0 extends this feature to all OBLPNs that are shipped out from a facility. A web based API is available that can be used by external systems to notify Oracle WMS Cloud when OBLPNs are delivered. This message triggers an update of the OBLPN to a DELIVERED status and also the creation of an Inventory History Activity (IHT - 80-Container Delivered) in the system.
The major new features released in the Oracle WMS Cloud 9.0.0 update include:
Updated User Interface Look And Feel
Update 9.0.0 aligns the Oracle WMS Cloud look and feel with Oracle SCM Cloud. This includes the login page, home screen, application colors and icons.
Version 9.0.0 provides the flexibility to automatically trigger cycle count tasks creation on predetermined days at regular frequencies via scheduled jobs. This feature helps optimize the cycle count tasks creation process since users do not have to navigate to the Task Creation UI anymore to trigger task creation.
A new job type called Run Cycle Count Tasks is available in the scheduled jobs UI. After the cycle count template is created via the Task Creation UI, all that is required is to specify the name of the template on the scheduled job along with the user name. Tasks are automatically created on scheduled days at the scheduled time.
In version 9.0.0, the RF Menu can be set up to have up to three levels. This new feature is beneficial for customers whose users work on multiple areas of the warehouse. It allows you to find transactions faster, and to organize transactions by having them on different levels. You can configure this on the Menu UI.
Version 9.0.0 provides extra room on RF screens by adding three more rows of space before the text that displays the environment. This enables you to see additional information for the transactions. The recommended number of columns to configure for RF display is a max of 28 characters.
Also apart from using the regular control keys provided on RF, you can now use customized keys for your convenience. For example, you could choose to use F5 instead of Ctrl+W. A new UI module RFKeyMapView allows you to map frequently used control keys to a key of your choice. After mapping the control keys, Oracle WMS Cloud also allows you to transfer the configurations across their eligible facilities. This is especially useful since hand-held devices among different clients vary and the ease with which certain keys are used on one hand-held may not be the same on a different hand-held device.
In RF, a function key F1 has been introduced, that displays the list of ctrl keys available. If you map default ctrl keys to customized keys, the system displays them accordingly. A new facility parameter HIDE_RF_KEY_INDEX is available that controls if you want to use this feature or not. The Facility Parameter must be set to Yes in order for this functionality to work.
NOTE: Control key mapping is applicable to all RF screens except the main RF login screen. On the main RF login screen, the control keys default to system defined control keys.
Option to Reprocess Failed Messages Coming from MHE Distribution Pack Complete
In warehouses that have a MHE system, after the OBLPNs are packed, WCS (Warehouse Control Systems) use the Distribution Pack Confirmation MHE API to send the OBLPNs packed messages to Oracle WMS Cloud. Sometimes due to the number of API requests coming from WCS, the messages could fail and get marked as an error in Oracle WMS Cloud.
Version 9.0.0 has introduced a new button “Reprocess Failed Record” on the main screen of the From MHE OBLPN HDR UI. On this screen, you can select failed records (only one record can be selected at a time) and hit the Reprocess Failed Record button. This selects all the associated detail records that have failed and submits them for reprocessing.
Enhancements to Display Quantity in Cases
If you deal with inventory in cases and you are required to capture and see the information in cases, the following features are completed to support this need:
- A new button “Cartonize LPN by Cases” is available in the IB Shipment-Detail UI which helps you to cartonize the LPN by entering the number of standard cases that need to present in the LPN. In order to cartonize LPN by cases, select the IB Shipment Detail, click the action button, and specify the number of cases that need to go in each LPN and can specify how many such LPNs are required. Also you can specify whether the LPN is a Physical Pallet or not. You can cartonize one Shipment Detail at a time.
- You can see the quantity in cases in the RF Location Inquiry, RF LPN Inquiry, and RF Pack OBLPN. A new screen parameter display_qty_uom has been introduced in the RF Location Inquiry and the RF LPN Inquiry. Also, default_qty_uom in RF Pack OBLPN will help you to set the preferred unit of measure (UOM).
- You can see Current quantity and Allocated quantity in cases/packs in the Reserve Inventory UI.
- You can see Current quantity, Packed quantity, and Allocated quantity in cases/packs in OBLPN Inquiry.
- Support for displaying quantity in preferred units of measure (UOM) (units, cases and packs) or in the allocation UOM (depending on your preference) in the RF Mod/Cancel OB Container. The new screen parameter qty_uom has been introduced in RF Mod/Cancel OB Container that helps you to set the preferred UOM.
Support for Additional Time Zones
In addition to the time zones that Oracle WMS Cloud already supports, version 9.0.0 supports the following time zones:
- Arabia Standard Time (Asia/Riyadh)
- Spain Time (Europe/Madrid)
- Portugal Time (Europe/Lisbon)
- Germany Time (Europe/Berlin)
With regards to the Australian region, version 9.0.0 includes support for additional zones and redefined existing time zones for better clarity as described below:
- Prior to Version 9.0.0
- Australian New South Wales Time
- Australian Western Standard Time
- Australian Eastern Standard Time
- Version 9.0.0
- Australia/Brisbane (AEST)
- Australia/Adelaide (ACST)
- Australia/Melbourne (AEST)
- Australia/Perth (WST)
- Australia/Sydney (AEST)
Expansion of Language Translations
In version 9.0.0, several new languages have been added. The following is a complete list of all the languages supported in the application, both in the browser-based UI and the mobile RF:
- Chinese - Simplified
- Chinese - Traditional
- French - Canada
- French - France
- German
- Italian
- Japanese
- Korean
- Polish
- Portuguese - Brazil
- Russian
- Spanish - Worldwide
- Thai
- Turkish
Matched Look and Feel of Oracle WMS Cloud with Oracle SCM Cloud Products
Version 9.0.0 changes the look and feel of the browser-based Oracle WMS Cloud UI to match with that of other Oracle Cloud Supply Chain Management (SCM) products. At a very high level, the following changes are apparent in the new version:
- Login screen
- Icons used on UI screens
- The top bar of the application
- Buttons and Tabs
- A user-configurable home screen called springboard, that can be configured with screens the user need to use frequently. The recently used tabs continue to be available as before.
Transaction Monitoring and Reprocessing Enhancements
Prior to version 9.0.0, the support team was in charge of scheduling jobs, enabling and disabling existing jobs, and other functions. After version 9.0.0, most of the functionality has been moved to the application, and you can do the following:
- “Reset Load Status” – you can reset load status on the OB Load UI. This new button is available for ADMINISTRATORS and MANAGEMENT roles. You can assign it to other users via the new permission “Reset Load Status". The button is enabled if a load is in a Close Load in Progress or Ship Load in Progress status. After you click this button, the Load with status Close Load in Progress is changed to Loading Started and Ship Load In Progress will have the status set to Loaded.
- “Reset Current Value” you can reset the current_value of the staging location in the Stage Location Configuration UI. This new button is available for ADMINISTRATORS and MANAGEMENT roles. You can assign it to other users via the new permission 'Reset Current Value'. The reset of current value is only available if the location is empty.
- MHE failed Task - New Module MHEfailedtask of screen type UI-HTML. The new UI screen “MHE failed task” displays the failed celery task with details like company, facility, task name, celery task id, or user etc. You can search on this screen based on the MHE Job id, user, or failed timestamp. The screen has three action buttons- Resubmit, Delete, and Delete all. The new buttons are available for ADMINISTRATORS and MANAGEMENT roles. You can assign it to other users via the new permission MHE Job Admin.
- Input Interface changes - The following entities - Purchase Order, Inbound Shipment, Order, Route, and Work Order now have a detail button on the stage tab. You can see detailed records that have errored out or have not been processed yet during interface.
- Clear Stage Records – You can now clear stage records. The new permission clear_stage_records, allows you to click on the Clear Stage Records button on the Input Interface UI. You are warned, and asked to provide the password one more time.
- Recalculate Order Status- You can now recalculate the order status. The new permission recalc_order_status, allows you to recalculate the order status on the Order Header UI. You are asked to provide the password one more time.
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
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
---
Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
9.0.0 Rev 1