Output Interface
A new qty_uom_code field is added to export the value based on Primary UOM from respective item facility. If primary UOM on the item facility is not defined, then Primary UOM from respective item is populated.
UOM Support in Output Interface
New fields are added to the output interface files for Quantity/ Weight/ volume/ Dimensions values:
- weight_uom_code
- volume_uom_code
- dimension_uom_code
UOM in Output Interface
Fields Behaviour Conversion for Reference Fields weight_uom_code When facility param "OUTPUT_INTF_FACILITY_WT_VOL_DIM_UOM" is set as blank/no, respective company weight UOM is exported. When facility param "OUTPUT_INTF_FACILITY_WT_VOL_DIM_UOM" is set as 'Yes', respective facility weight UOM is exported.
When facility param "OUTPUT_INTF_FACILITY_WT_VOL_DIM_UOM" is set as blank/no, weight fields can be exported without conversion when facility param.
When facility param "OUTPUT_INTF_FACILITY_WT_VOL_DIM_UOM" is set as 'Yes', weight fields should be converted from company weight UOM to facility weight UOM and exported.volume_uom_code dimension_uom_code
These new UOM fields are applicable for following output interface files:
- Wave Pick Information (WOA) Interface
- Order Outbound Load Export File (PLS)
- Shipped Load File (SLS) Interface
- Pallet Shipping Info File (PLI)
- OBLPN Shipping Info File (OLO)
- Inventory History (IHT) Interface
- TO_MHE_DISTRIBUTION_INFO
- Standard Inventory Summary
- Customer Inventory Summary
- Shipment Verification (SVS) Interface
- Outbound Manifest File (SLS)
- Container Outbound Load Export File (LLS)
- TO_MHE_IBLPN_INFO"
Order Outbound Load Export File (PLS) and Shipped Load File (SLS) Interface
When an Order is packed, you can generate the Order outbound load export file along with UOM in PLS file with underlying details similar to Shipped Load output interface file.
The fields exported with supporting UOM are qty, weight, volume, and dimension fields for Shipped Load and Order outbound load export.
Fields | Level in Interface | Reference |
---|---|---|
weight_uom_code | Load/Stop | total_weight, total_volume, ob_lpn_weight, total_pallet_weight |
volume_uom_code | Load/Stop | total_volume, ob_lpn_volume, total_pallet_volume |
dimension_uom_code | Stop | ob_lpn_length, ob_lpn_width, ob_lpn_height, pallet_length, pallet_width, pallet_height |
Pallet Shipping Info File (PLI)
Fields | Level in Interface | Reference |
---|---|---|
weight_uom_code | Pallet/OBLPN Header | total_pallet_weight, carton_weight, total_pallet_weight |
volume_uom_code | Pallet/OBLPN Header | total_pallet_volume, carton_volume, total_pallet_volume |
dimension_uom_code | Pallet/OBLPN Header | pallet_length, pallet_width, pallet_height, carton_length, carton_width, carton_height, pallet_length, pallet_width, pallet_height |
Fields | Level in Interface | Reference |
---|---|---|
weight_uom_code | OBLPN header | carton_weight, total_pallet_weight |
volume_uom_code | OBLPN header | carton_volume, total_pallet_volume |
dimension_uom_code | OBLPN header | carton_length, carton_width, carton_height, pallet_length, pallet_width, pallet_height |
Inventory History (IHT) Interface
The field qty_uom_code is added to track following related fields:
- orig_qty,
- adj_qty,
- units_shipped,
- units_received,
- qty_shipped and
- qty_received
TO_MHE_DISTRIBUTION_INFO & TO_MHE_IBLPN_INFO
Following are the new fields that UOM:
- New field "uom_code" in distro header and "alloc_qty_in_uom_code" in distro_dtl.
- When the alloc_uom is Cases/Packs, this field provides the actual Case/Packs UOM of
the inventory which is being dealt with:
UOM Fields
Fields Reference Behavior alloc_qty_in_uom _code alloc_qty_in_uom alloc_qty_in_uom_code: Provides the context to the alloc_qty_in_uom when the allocations are in Packs/Cases by associating the Case/Pack UOM to alloc_qty_in_uom
- If allocation UOM is UNITS : Primary UOM code associated with the Item Facility/Item
- If allocation UOM is CASES : UOM code associated with the Item Case UOM
- If allocation UOM is PACKS : UOM code associated with the Item Pack UOM
- Weight and Volume Conversion
Weight and Volume Conversion
Field Without UOM Field With UOM item_unit_weight Case1: When Company and Facility Weight UOM are the same, process the unit_weight same as in Item Master. Case2: When Company and Facility Weight UOM are different, then we need to convert the unit_weight specific to Facility and then process Example: Company Weight UOM = KG ; Facility Weight UOM = POUNDS ; Item Units Weight = 10 Now when processing weight information, we need to convert KG to Pounds 10 KG = 10 x 2.20462 = 22.0462 lbs
weight_uom_code Case1: When Company and Facility Weight UOM are same, Process the uom code from either company or facility Case2: When Company and Facility Weight UOM are different, then process the uom code from Facility
item_unit_volume Case1: When Company and Facility Volume UOM are the same, process the unit_volume same as in Item Master. Case2: When Company and Facility Weight UOM are different, then we need to convert the unit_volume specific to Facility and then process Example: Company Volume UOM = CC ; Facility Weight UOM = Cubic Inch; Item Units Volume= 100 Now when processing volume information, we need to convert CC to Cubic Inch 100 CC = 100 x 0.061 = 6.10 cubic inch
volume_uom_code Case1: When Company and Facility Volume UOM are same, Process the uom code from either company or facility Case2: When Company and Facility Volume UOM are different, then process the uom code from Facility
Standard Inventory Summary & Customer Inventory Summary
The qty_uom_code provides quantity support to following columns:
- oblpn_total,
- active_total,
- active_allocated,
- active_available,
- iblpn_allocated,
- iblpn_total,
- iblpn_available,
- iblpn_notverified,
- total_allocated,
- total_available,
- total_inventory,
- four_wall_inventory,
- open_order_qty
New company parameter OUTPUT_LGF_FINFO_INVENTORY_SUMMARY is added in case you want to generate the output file in the old format configure the field as lgf22a. For generating the file as per new format, populate the value of "lgf" or leave it blank. By default, the parameter will be blank.
New facility parameter: Program Key: OUTPUT_LGF_FINFO and Parameter Key INVENTORY_SUMMARY is added in case you want to generate the file as per the old format configure the field as lgf22a. For generating the file as per new format, populate the value of "lgf" or leave it blank. By default, the parameter will be blank.
Customer Inventory Summary
- oblpn_total,
- active_total,
- active_allocated,
- active_available,
- active_lockcode,
- active_allocated_lockcode,
- iblpn_allocated,
- iblpn_allocated_lockcode,
- iblpn_total,
- iblpn_available,
- iblpn_notverified,
- iblpn_lockcode,
- iblpn_lost,
- total_allocated,
- total_available,
- total_inventory,
- four_wall_inventory,
- open_order_qty
New Company Parameter OUTPUT_LGF_FINFO_CUSTTOMER_INVENTORY_SUMMARY is added in case you want to generate the file as per the old format configure the field as lgf22a. For generating the file as per new format, populate the value of "lgf" or leave it blank. By default, the parameter will be blank.
New Facility Paramater: Program Key: OUTPUT_LGF_FINFO and Parameter Key will be CUSTOMER_INVENTORY_SUMMARY is added in case you want to generate the file as per the old format configure the field as lgf22a. For generating the file as per new format populate the value of "lgf" or leave it blank. By default, the parameter will be blank.
Outbound Manifest File (SLS)
Fields | Level in Interface | Reference |
---|---|---|
weight_uom_code | Load/Stop | total_weight, ob_lpn_weight, total_pallet_weight |
volume_uom_code | Load/Stop | total_volume, ob_lpn_volume, total_pallet_volume |
dimension_uom_code | Stop | ob_lpn_length, ob_lpn_width, ob_lpn_height, pallet_length, pallet_width, pallet_height |