Results for “auto_pack_lines”

18 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_DLVB_COMMON_ACTIONS is a PL/SQL package in the APPS schema that provides the shared delivery-builder logic used by Oracle Shipping Execution (WSH). It centralizes the common actions that operate on delivery details and containers during the outbound shipping cycle: assigning and unassigning details to deliveries, auto-packing lines into containers, separating details, and computing container and item capacity totals. The package is classified as OTHER in the ETRM API registry, indicating it is an internal implementation package rather than a public, callable API. In Oracle EBS 12.1.1 and 12.2.2 the object holds VALID status and is composed of a package specification plus a package body, with its SQL statements and dependency tree recorded in the standard ETRM documentation pages.

The dependency metadata confirms that the package is generated on and reuses the group of WSH globals and utilities: it references WSH_GLBL_VAR_STRCT_GRP (the global variable structure group) and WSH_UTIL_CORE (general shipping utilities), and it is referenced in turn by WSH_CONTAINER_GRP, WSH_DELIVERY_DETAILS_GRP, and by itself through recursive/dependent code. This places the package at the centre of the shipping module's internal call graph rather than at its boundary.

Key Procedures and Functions

The documented metadata lists eight procedures and functions. Their purposes are as follows.

  • ASSIGN_DETAILS — Assigns delivery details (order lines, lots, and move-order transactions) to a specific delivery, establishing the delivery-detail association used by downstream picking and packing.
  • UNASSIGN_DETAILS — Performs the reverse operation, removing the association between details and a delivery so they can be reassigned elsewhere.
  • AUTO_PACK_LINES — Automatically packs eligible lines into containers according to shipping container rules, supporting automated packing during delivery building.
  • SEPARATE_DETAILS — Splits or separates detail records so that a portion of a line can be handled as a distinct shipping unit.
  • CALC_CONT_AVAIL — Calculates the available capacity of a container, used to determine whether remaining lines or items can be packed into it.
  • CALC_ITEM_TOTAL — Calculates the aggregate total for an item, supporting volume, weight, or quantity roll-ups across the items in a delivery or container.
  • CALCULATE_TOTAL_CAPACITIES — Computes total capacities across containers or a delivery, providing the denominator for capacity checks performed by the other procedures.

As this is an internal package, the procedures are not exposed as a documented public API and no parameter lists are published in the ETRM record.

Tables Accessed

The package reads and writes through APPS synonyms on the following core tables:

  • WSH_DELIVERY_DETAILS — The primary shipping detail table; holds the delivery-detail associations that ASSIGN_DETAILS and UNASSIGN_DETAILS create and remove, and the records inspected by the calculation routines.
  • WSH_NEW_DELIVERIES — The delivery header table; supplies delivery context and capacity attributes used when details are assigned and totals computed.
  • MTL_PARAMETERS — The inventory organization parameters table, providing organization-level defaults and unit-of-measure settings that govern capacity and packing calculations.
  • PLITBLM — An Oracle-supplied PL/SQL table type (index-by table of numbers used as a generic table/collection structure), employed here for passing and processing collections of IDs within the package's internal algorithms.

Usage Notes

WSH_DLVB_COMMON_ACTIONS is invoked internally by the Shipping Execution UI and by other WSH packages rather than directly by end users or custom forms. Documented references from WSH_CONTAINER_GRP and WSH_DELIVERY_DETAILS_GRP demonstrate that container and delivery-detail operations delegate their common actions to this package; the self-reference in the dependency list indicates the package body also calls its own procedures.

Typical invocation paths therefore include the Delivery Builder and container/packing windows in the Shipping Execution responsibility, where user actions such as assigning lines, auto-packing, and separating details trigger these procedures, and any concurrent or batch process that builds or modifies deliveries. Because the package is not a published API, Oracle does not guarantee its signature across releases; customizations should prefer the public WSH APIs and the delivery-detail and container group packages, treating WSH_DLVB_COMMON_ACTIONS as a subject of analysis, debugging, and tracing rather than of direct custom calls.