Predefined Integration Mappings for Expensed Destination Transfer Orders and Purchase Orders

With this release, we are enhancing the IB Shipment process to support inbound orders destined for stocking locations or specific requestors outside of a warehouse, enabling WMS to receive and directly consume expensed inventories upon receipt.

To distinguish such shipments, a new flag called Expensed destination has been introduced at the Inbound Shipment detail level. If this flag is selected, it implies that the corresponding shipment detail is meant for an expensed destination and will be auto-consumed upon receipt.

Along with the flag, two new fields are introduced to capture requester details:

Field Name Length Description

Requestor Name

250

Name of the requester

Requestor Address

250

Address of the requester

These fields are available on:

  • Inbound Shipment Detail UI (create/edit pane, grid columns, CSV export)
  • Purchase Order UI (Requestor Address added)
  • Inbound Shipment Interfaces (XML, XLS, PSV)
  • Vendor QC UI (can configure expensed fields as QC criteria)
  • Label Designer (available for IBLPN label type)

When an IB Shipment Detail links to a Purchase Order Detail:

  • WMS copies the expensed flag, Requestor Name, and Address from the PO.

  • A warning message informs you about the copy.

    • If IB Shipment = Yes and PO Detail = No, WMS displays an error:
      “Conflicting expensed records for the item: %ITEM_CODE.”

  • You cannot edit expense-related fields once linked.

  • WMS restricts shipments from containing the same SKU on lines where one is expensed and another is not.

AUTO CONSUMPTION FOR RECEIVING

Receive Entire Shipment API
URL

PATCH.../entity/ib_shipment/receive_entire_shipment

When you receive an ASN with the Expensed flag, the system auto-consumes the LPNs immediately. Each LPN is marked as consumed as soon as it is received.The system does not allow you to mix expensed and non-expensed details in the same LPN. If attempted, it throws an error. Every consumed LPN generates the history triggers IHT-1 (LPN Received) and IHT-2 (Container Consumed).

Receive IBLPN API
URL

PATCH.../entity/iblpn/receive

When you receive an IBLPN with the Expensed flag, the system auto-consumes the LPN right after receipt. The LPN is immediately marked as consumed. As with shipment receiving, you cannot mix expensed and non-expensed details in the same LPN. The system blocks the action with an error. Each consumed IBLPN generates IHT-1 (LPN Received) and IHT-2 (Container Consumed).

Additionally, the system updates Ref Field 18 (EXP) to 'Yes' or 'No', depending on the shipment configuration.

The following PATCH APIs now support the Expensed Destination Flag, Requestor Name, and Requestor Address fields in alignment with UI behavior. You can use them to update shipment and purchase order details during integration.

  • PATCH .../wms/lgfapi/v10/entity/ib_shipment_dtl
    Use this API to update inbound shipment detail records. You can set or update the expensed flag, requestor name, and requestor address when the shipment header is in CREATED, IN_RECEIVING, or RECEIVED status (field restrictions apply).
     

  • PATCH .../wms/lgfapi/v10/entity/purchase_order_dtl

Use this API to update purchase order detail records. You can set or update the expensed flag, requestor name, and requestor address when the PO header is in CREATED status for the flag, and in CREATED, IN_RECEIVING, or RECEIVED status for requestor fields.

You can now update the Expensed destination flag, Requestor Name, and Requestor Address through APIs in the same way you can through the UI.

Field Name

Type

Length

Update Allowed When

expensed_destination_flg

Boolean

1

Only when Shipment/PO Header = CREATED

requestor_name

String

250

When Header = CREATED, IN_RECEIVING, or RECEIVED

requestor_address

String

250

Same as above

INVENTORY INVENTORY HISTORY OUTPUT

The Inventory History Output Interface now includes additional item-level filter columns, such as:

  • ITEM.Dummy SKU flag

  • Item Putaway Type, Velocity Code, External Style, Brand Code, VAS Group Code

  • Item Parent Flag, Host Aware Item, Hazardous, Conveyable, Season Code, and more

With these filters, you can exclude dummy SKUs and prevent unnecessary inventory adjustment transactions (IHT-4 and IHT-17) from being sent through the Inventory History Output Interface.

NOTE:

  • When the system generates an IHT-1: LPN Received, it now records expensed destination details (REF_CODE_19=EXD; REF_VALUE_19=YES if the receipt is from an expensed destination, otherwise NO), ensuring every expensed receipt is correctly flagged for tracking and reporting.
  • When you receive expensed inventory, a confirmation message displays the requester's details across Purchase Order UI, ASN UI, and RF Receiving:
    • If the requester's name/address is available, the message shows LPN(s) and the requester's details.
  • When an ASN line is marked as Expensed, any LPN received against it will be auto-consumed once you end the LPN. Expensed and non-expensed inventory cannot be mixed in the same LPN. Each expensed LPN generates the usual inventory history records (IHT-1 LPN Received and IHT-2 Container Consumed). 

Steps to Enable

You don't need to do anything to enable this feature.