Results for “t_v4”

2 results




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

Overview

APPS.OE_WSH_BULK_GRP is a package specification classified as a Group (GRP) type object within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the APPS schema and sits at the intersection of Oracle Order Management (OE) and Oracle Shipping Execution (WSH). As its name implies, the package centralises the shared PL/SQL data structures and type definitions used by the bulk-processing programs that drive order and delivery workflows — in particular the bulk pick, bulk pack, bulk ship, and shipping group (delivery) consolidation logic exercised during the order-to-shipment lifecycle.

In R12, order lines flow into the shipping model through the WSH_DELIVERY_DETAILS and WSH_DELIVERY_ASSIGNMENTS tables, and the bulk shipping processes operate on large sets of lines simultaneously. OE_WSH_BULK_GRP provides the common record and collection types that allow these high-volume routines to pass arrays of records between PL/SQL layers without a database round trip per row. Because it is a header-only (specification) package, it does not itself execute business transactions; rather, it defines the canonical shapes that other OE and WSH programs depend upon. The ETRM metadata confirms this dependency-heavy role: the package is referenced by 37 other packages, indicating it is a foundational utility in the Order Management/Shipping code base.

Key Procedures and Functions

The ETRM documentation for this object lists zero callable procedures or functions. This is consistent with its GRP classification and the header source, which contains only type declarations. The package exposes the following data types rather than program units:

  • Scalar collection types — T_DATE (TABLE OF DATE), T_NUM (TABLE OF NUMBER), and T_B_INT (TABLE OF BINARY_INTEGER), used to pass date, numeric, and integer arrays between bulk routines.
  • Varchar collection types — A family of TABLE OF VARCHAR2 types sized for specific data domains: T_V1, T_V3, T_V4, T_V10, T_V15, T_V25, T_V30, T_V40, T_V50, T_V80, T_V150, T_V240, T_V250, T_V1000, and T_V2000. These correspond to standard EBS column widths (for example, T_V240 matches the attribute columns of the order line interface tables).
  • Line_Rec_Type — The central record type describing an order/shipping line. Its fields include accounting_rule_id, accounting_rule_duration, actual_arrival_date, agreement_id, arrival_set_id, ato_line_id, ato_line_index, and twenty attributes (attribute1 through attribute20), each typed as T_V240. The attributes are documented as DFF/context columns, with attribute16 annotated "For bug 2184255." This record allows bulk programs to carry the full line footprint — including Configure-to-Order (ATO) references and agreement context — in a single collection element.

Tables Accessed

The ETRM metadata documents no direct table references by this package. This is expected for a type-definition library: it neither queries nor mutates data. The types it defines are used by the 37 dependent packages that perform the actual DML, including the OE order import and WSH shipping interfaces. Indirectly, the Line_Rec_Type mirrors the structure of staging and interface entities such as the order line interface and delivery detail records, which is why the attribute1–20 fields and ATO/agreement identifiers are represented.

Usage Notes

Because OE_WSH_BULK_GRP contains only declarations, it is never executed as a standalone program. It is invoked implicitly through PL/SQL compilation whenever a dependent package references one of its types — for example, a bulk shipping or delivery consolidation routine that declares a parameter or local variable of Line_Rec_Type. Typical consumers include the WSH bulk ship confirmation, delivery assignment, and pick-release concurrent programs, as well as Order Management line processing utilities, whether invoked from the Shipping Transactions form, the Order Organizer, or a scheduled concurrent request.

Custom extensions should follow the same pattern: reference the collection types rather than redefining local equivalents, so that custom code remains aligned with Oracle's array sizing and avoids conversion overhead. When a custom program needs to bulk-process order or delivery lines, declaring a collection of Line_Rec_Type and its supporting T_* arrays is the supported, forward-compatible approach. Care should be taken to preserve the ordering of attribute columns, since dependent packages rely on positional consistency, and to confirm that the package is not invalidated after patching, as invalidation would cascade to all 37 dependent packages.