Predefined Integration Mappings for Intra-Org Transfer Orders

For businesses that utilize their stockrooms and warehouses to fulfil internal requests on top of transfers to other facilities or shipments to customers, the system requires an ability to fulfil internal requests within the same facility and send shipment confirmation using Container Outbound Load Export file. 

With the new predefined integration for internal orders (intra-organization transfer orders)  between Oracle Cloud SCM and Oracle Cloud WMS, you can now fulfil the request within the same stockroom or warehouse. This solution ensures integration errors is reduced, improves traceability, and supports accurate, real-time inventory updates—enabling every department to seamlessly manage on their core priorities.

ENHANCED SHIPPING CONFIRMATION WITH ‘CONTAINER OUTBOUND LOAD EXPORT’ FILE

Previously, we introduced an action type “Ship OBLPN” to the OBLPN Putaway Type Action View (OblpnPATypeActionView) Mobile transaction,  where you can ship OBLPNs directly to a specified shipping location in the OBLPN putaway workflow, reducing the need for separate shipping transactions.

Now, the Ship OBLPN to Ship Location (rf.outbound.cwrfshipoblpn) mobile transaction includes a new parameter choice “Container Outbound Load Export” in the output-file-to-generate screen parameter.

When you select 'Container Outbound Load Export', an LLS file is generated through the ship OBLPN transaction. This simplifies sending shipment confirmations through the Ship Confirm Prebuilt Integration and supports the intra-org transfer process with Fusion Inventory.

NOTE: If your company parameter is set to generate LLS, the Container Outbound Load Export file is generated twice; once when the OBLPN is packed, and again when the OBLPN is shipped. This is applicable only when you enable both company param and the screen param.

GENERATE ‘CONTAINER OUTBOUND LOAD EXPORT’ FILES VIA API

You can now generate a 'Container Outbound Load Export' (LLS) file every time you ship an OBLPN using the Ship OBLPN API or Bulk Ship OBLPN API. Currently, the Ship OBLPN API creates ‘OBLPN Shipping Info’ and ‘LPN Inventory’ files. Now, you can also generate an LLS file as needed for your shipping confirmation workflows.

A new option 'container_outbound_load_export' is introduced in the 'output-file-to-generate' API parameter. 

  • Ship OBLPN via API: Bulk Ship OBLPN URL:

POST entity/oblpn/bulk_ship/

  • For shipping a single OBLPN: Ship OBLPN URL:

POST entity/oblpn/{id}/ship/

For more information, refer to WMS REST API Guide.

CONFIGURING FILTER CRITERIA AND TRACKING STATUS FOR ‘CONTAINER OUTBOUND LOAD EXPORT’ FILES

You can now control which 'Container Outbound Load Export' (LLS) files are generated after shipping OBLPNs using the Ship OBLPN mobile transaction. You can set filter criteria directly from the output interface configuration UI, ensuring only relevant LLS files are created for your intra-org transfer to Fusion Inventory.

  • In the Output interface target UI, the detail icon is now enabled for the 'Container Outbound Load Export Interface type. The Detail icon displays all available column names, as seen with OBLPN Shipping Info file filters.
  • You can Create and manage filter criteria records for the LLS file, customizing which OBLPNs trigger file generation after shipping.
  • A new flag “oblpn_status” is added to the 'Container Outbound Load Export' file (LLS) and the Outbound Manifest files. Impacted XSD files are, contaiter_shipped_load, order_shipped_load, shipped_load, shipped_load_ics, and parcel_manifest.
  • The oblpn_status flag tracks each OBLPN’s status:
    • If value is 'shipped', then the OBLPN is shipped using the Ship OBLPN mobile transaction.
    • If value is 'packed', then the LLS file is generated for packed OBLPNs (based on your company configuration).
  • Following columns are added to Output interface target column selection dropdown for LLS
    • carrier_type, carrier_code, tracking_nbr, ob_lpn_type, oblpn_status, ship_via_code, and invn_attr_a to o.

FULFIL INTERNAL ORDERS BY SENDING SHIPMENT CONFIRMATION USING LLS FILE

You can quickly fulfil internal orders within your own facility and easily send shipment confirmations to Oracle Cloud Inventory by mapping the Container Outbound Load Export' File in the Shipment Confirmation Prebuilt integration.

NOTE: Only LLS files generated via the Ship OBLPN mobile transaction will be sent to Oracle Integration Cloud (OIC) for shipment confirmation. The key field oblpn_status in the LLS file distinguishes the shipment type:

  • oblpn_status = 'shipped': Use for prebuilt integration and shipment confirmation (when OBLPN is shipped).
  • oblpn_status = 'packed': These files, generated when the OBLPN is only packed, will not be sent to OIC for confirmation.

NOTE: An existing ship confirmation prebuilt using outbound load export remains intact. Current change is limited to the ship oblpn transaction where the ship confirmation now considers LLS file in the prebuilt.

Steps to enable and configure

  1. Navigate to the Ship OBLPN to Ship Location (rf.outbound.cwrfshipoblpn) transaction screen.
  2. On the output-file-to-generate parameter, select 'Container Outbound Load Export'.
  3. After shipping an OBLPN, the system automatically generates an LLS file for each OBLPN shipped.
  4. Use the exported LLS file to send shipping (when OBLPN status is Shipped) confirmation to Fusion inventory.