1. Online Help
  2. Expense Destination Items on Transfer Ordern / IB Shipment

Expense Destination Items on Transfer Ordern / IB Shipment

For orders destined for locations or requesters outside the warehouse, goods can be received at the warehouse dock and manually issued to their destination. Expensed destination purchase orders and transfer orders from Oracle Cloud Inventory Management are supported for receipt in Cloud WMS. Upon receipt, these items are immediately auto consumed, and the WMS sends the auto consumed information to Inventory Management.

An Expensed Destination flag has been added at the Purchase Order IB Shipment Detail level to identify expensed items and enable automatic consumption upon receipt.

When processing an expensed destination receipt (IB Shipment Detail), the system receives and consumes the LPN, generating an IHT-1 (LPN Received) record which is sent to Fusion for receiving receipt confirmation.

Fusion can identify whether the PO/ASN is received in WMS from the receiving receipt confirmation.

  • Requestor Details

Three new fields have been added to the PO and IB Shipment Detail Interfaces:

  • expensed_destination_flg
  • Requestor Name (250 characters)
  • Requestor Address (250 characters)

These are available in XML, XLS, and PSV formats, allowing CREATE/UPDATE operations and will also appear in the Inbound Shipment Stage table.

Note: If an expensed detail has a Lock Code, the corresponding LPN inherits the same code and is auto consumed.

Expensed Destination Receipt – Information Message

An informational message is displayed when receiving expensed destination inventory.

When receiving expensed inventory, the following message is shown:“Expensed inventory received in %LPN and to be delivered to %Requestor name, %Requestor address”

This provides clear visibility of who requested the inventory and where it should be delivered.

  • Expensed Destination Receiving Metrix:
Receiving Method Condition Displayed Message
ASN UI-Based Receiving Destination Type = Expensed; Requestor Name populated Expensed inventory received in %LPN and to be delivered to %Requestor name, %Requestor address
ASN UI-Based Receiving Requestor Name/Address not populated; multiple requestors in LPN Expensed inventory received and consumed in LPN: %LPN1, %LPN2
RF-Based Receiving (ASN, Load) Destination Type = Expensed; Requestor Name populated Expensed inventory received in %LPN and to be delivered to %Requestor name, %Requestor address
RF-Based Receiving (ASN, Load) Requestor Name/Address not populated; multiple requestors in LPN Received LPNs are consumed to expensed destination

Message Format Details:

Scenario Displayed Message
Single LPN Received Expensed inventory received in %LPN and to be delivered to %Requestor name, %Requestor address
Multiple LPNs Received Expensed inventory received in %LPN_count(s) LPNs and to be delivered to %Requestor name, %Requestor address
Note:
  • The message displays only for Expensed Destination receipts.
  • Requestor Name and Address must be populated.
  • If multiple requestors exist in a single LPN, the system displays the standard message instead.
  • Applies to PO, ASN, and RF-based receiving workflows.

IB Shipment Detail UI Configuration

Expensed Destination Flag:

  • Checkbox field: Expensed Destination (expensed_destination_flg)
  • Usage:
    • Checked - Expensed
    • Unchecked - non-expensed
  • Default value: Blank (unchecked)
  • Available for both Create and Edit actions.

Requestor Details:

Fields added to capture requestor information:
  • Requestor Name (250 characters)
  • Requestor Address (250 characters)
  • Fields visible in Create/Edit pane and can be added directly through the UI.
  • Columns for these fields are available on the IB Shipment screen:
    • Users can show/hide and save preferred views.
    • Exportable in CSV format.
  • Requestor Address also appears in the Purchase Order and IB Shipment UIs.

RF Receiving – Expensed Destination Handling

When receiving via ASN or PO where the Expensed Destination flag is enabled:

  • System automatically consumes ASN details upon receipt.
  • Applies to:
    • RF Receive by Shipment
    • RF Receive by Load
    • RF Receive Single SKU
    • RF Sort and Receive
  • Auto-consumption occurs immediately before the LPN is picked by Flowthrough or Xdock.
  • Location prompt for consumed LPN is suppressed.
  • System displays: “LPN %LPN% received and consumed to expensed destination.”
  • Inventory Mixing Validation
Scenario User Action System Behavior
ASN has expensed details Receive SKUs in single LPN Allowed – auto consumed
ASN has both expensed and non-expensed details Receive expensed details in one LPN Error: “Cannot mix both expensed and non-expensed inventories in a single LPN.”

If the ASN is linked to a PO, expensed destination validations remain identical.

Handling Tolerance During RF Receiving

Line-level tolerance applies to ASN and PO receiving.

  • If prompt-po-seq-line is disabled, receiving may fail when SKUs have different tolerances across PO lines. Auto-consumption will not occur.
  • If prompt-po-seq-line is enabled:
    • Line or header-level tolerance applies.
    • Excess quantity within tolerance is auto consumed.
  • Tolerance applies at both line and header levels for ASN, PO, and ASN+PO combinations.
  • RF Screen are suppressed for Auto Consumed LPNs
Screen/Action Description
Location Prompt Suppressed during expensed LPN receipt
Xdock Screen Skipped
Flowthrough Screen Skipped
Next Screen Directly proceeds to QC Flow

Important Notes:

  • Expensed destination receipts are auto consumed and unavailable for putaway or staging.
  • Ensure the Expensed Destination flag is correctly set on ASN/PO records before receiving.
  • Lock code behavior and IHT updates ensure accurate traceability and Fusion integration.

Auto Consumption in Detailed Receiving Flow

When a non-cartonized ASN line is marked as Expensed Destination = Yes:

  • Any LPN received for that line is automatically consumed once the LPN is ended.
  • If an LPN is used to receive quantities from both expensed and non-expensed details, the system records an error:

“Cannot mix both expensed and non-expensed inventories in a single LPN.”

IHT Events Generated:

  • IHT-1: LPN Received
  • IHT-2: Container Consumed

Auto-consumption executes only when the LPN is ended.

Applies to both Receive Entire Shipment and Receive LPN options in the IB Shipment process.

API-Based Receiving

  • Receive Entire Shipment API

Endpoint: /entity/ib_shipment/receive_entire_shipment

  • ASN lines with Expensed Destination = Yes are automatically consumed upon receipt.
  • LPNs for expensed lines are marked as consumed.
  • Error displayed if same LPN is used for both expensed and non-expensed details: “Cannot mix both expensed and non-expensed inventories in a single LPN%”
  • IHT Trigger Points:
    • IHT-1: LPN Received
    • IHT-2: Container Consumed

Receive IBLPN API

Endpoint: /entity/iblpn/receive

  • Auto consumption occurs for expensed ASN lines.
  • LPNs associated with expensed lines are marked as consumed.
  • Mixing validation enforced; error generated if violated:

“Cannot mix both expensed and non-expensed inventories in a single LPN%”

  • IHT Trigger Points:
    • IHT-1: LPN Received
    • IHT-2: Container Consumed
    • REF_FIELD_18
            (EXP)
      updated with Yes/No based on shipment configuration.

Dummy SKU Exclusion from Inventory Adjustment

To exclude Dummy SKU items from triggering Inventory Adjustment (IHT-4/17) integrations:

  • In Output Interface Configuration → Inventory History → Output Interface Target Filter Criteria, a new column is available:
    • ITEM.Dummy Sku
            flg
  • This column can filter out Dummy SKU items from Inventory Adjustment Integration.
  • The same field is added to the Inventory History Export Output Interface file for downstream visibility.

Error Handling in IB Shipment Interface and UI

Validation ensures no conflicting expensed configurations exist for the same SKU within a shipment.

Example Item Qty Expensed Destination Flag
SHPMNT-01 SKU-A 10 Yes
SHPMNT-01 SKU-A 15 No
  • System restricts interfacing when conflicting expensed flags exist for the same SKU.
  • Validation applies to both CREATE and UPDATE actions in the IB Shipment Interface.

Validation and Synchronization Between IB Shipment and PO Details

When linking IB Shipment Details to Purchase Order Details:

  • The following fields are automatically copied:
    • expensed_destination_flag
    • requestor_name
    • requestor_address
  • If IB Shipment Detail is marked Expensed = Yes while the PO Detail is No, the system restricts the operation and records an error: “Conflicting expensed records for the item: %ITEM_CODE”
  • Once linked, these fields cannot be modified. Any attempt generates the same error message.

Vendor QC UI Configuration

The Vendor QC UI supports configuration using the following Shipment Detail fields:

  • Shipment Detail Expensed Destination Flag
  • Shipment Detail Requestor Name
  • Shipment Detail Requestor Address

These can be configured under Sort & Receive Config UI – Criteria Fields to automatically mark items for QC during receiving.

  • Message on Approving Expensed LPN in QC

When approving an expensed LPN marked for QC, the system displays: “Expensed inventory received in %LPN and to be delivered to %Requestor name, %Requestor address.”

The LPN moves to Consumed status upon approval.

Label Configuration

Requestor information fields are available in Label Designer for label customization.

Available Fields:

  • Requestor_Name
  • Requestor_Address

Supported Label Type: IBLPN

Labels can be configured and printed using these fields in Label Designer.