Search Results g_set_tbl

Overview

OE_SET_UTIL is a PL/SQL utility package in the APPS schema that supports the Order Management "sets" and fulfillment feature set in Oracle E-Business Suite 12.1.1 and 12.2.2. A set in Order Management represents a grouping of order lines that must be processed, shipped, and fulfilled together, such as a kit, a configuration, or a grouped shipment. OE_SET_UTIL provides the core programmatic infrastructure for creating, validating, updating, and deleting these set definitions and their associated fulfillment relationships, and for resolving set identifiers and set records during order entry, order import, and shipping integration.

The package is classified as a UTIL package in the ETRM repository, is documented as VALID, and exposes 21 documented procedures and functions. It is referenced by 20 other packages and does not itself appear in the dependency list of any database object below it in the call hierarchy, which confirms its role as a low-level service consumed broadly across Order Management. Functionally, OE_SET_UTIL mediates between order-line processing utilities such as OE_LINE_UTIL and OE_HEADER_UTIL, scheduling and ATP utilities, and the shipping tables in the WSH schema that carry fulfillment and delivery detail data.

Key Procedures and Functions

The documented API surface groups naturally into set existence and identity, set lifecycle maintenance, attribute validation, and fulfillment processing.

• SET_EXIST / STAND_ALONE_SET_EXISTS — assess whether a set is defined for a given context and whether a stand-alone set exists, used before attempting set creation or linkage.
• GET_SET_ID / GET_SET_REC / QUERY_SET_ROWS — resolve set identifiers and retrieve set records and set rows for downstream logic.
• CREATE_SET / CREATE_LINE_SET / CREATE_FULFILLMENT_SET — instantiate set headers of the appropriate type: line-based sets and fulfillment-based sets.
• INSERT_INTO_SET / UPDATE_SET / DELETE_SET / SPLIT_SET / UPDATE_OPTIONS — maintain set membership, modify set attributes and options, split a set into multiple sets, and remove set definitions.
• VALIDATE_SET_ATTRIBUTES / VALIDATE_MULTI_ARR_SET — enforce business rules on set attributes and on multi-arrangement set configurations.
• GET_FULFILLMENT_LIST / REMOVE_FROM_FULFILLMENT / DEFAULT_LINE_SET / PROCESS_SETS — retrieve fulfillment membership, remove lines from fulfillment, apply default set logic to lines, and orchestrate overall set processing.

Parameter definitions are not published in the ETRM extract; callers should obtain exact signatures from the deployed package specification rather than assuming argument order or optionality.

Tables Accessed

The package reads and writes the core set tables OE_SETS, OE_SETS_S, and OE_LINE_SETS through their APPS synonyms, which store set headers, set translations or secure views, and the mapping of lines to sets respectively. Order line data is accessed through OE_ORDER_LINES and OE_ORDER_LINES_ALL, while MTL_SYSTEM_ITEMS_B supplies item master attributes used during set validation and defaulting.

Fulfillment behavior is grounded in the WSH shipping tables: WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS, WSH_NEW_DELIVERIES, and WSH_SHIPPING_PARAMETERS. These are required when sets are created or queried in a fulfillment context, such as grouping lines that must ship together. DUAL and PLITBLM appear as utility references.

Usage Notes

OE_SET_UTIL is an internal utility rather than a user-facing published API. It is most commonly invoked indirectly through Order Management forms during sales order entry, through order import and order publishing routines, and through shipping and fulfillment integration when delivery detail is assigned. The ETRM dependency record shows broad coupling to OE_ORDER_PUB, OE_ORDER_PVT, OE_DELAYED_REQUESTS_PVT, and OE_ORDER_CACHE, indicating that both the public order API path and the internal order cache path rely on this package.

Custom code should not call OE_SET_UTIL directly unless no supported public API exists, because its interfaces are not guaranteed across patch levels. Where set manipulation is required, prefer the supported Order Management public APIs, which in turn invoke this utility. The package records debug output through OE_DEBUG_PUB and raises messages through OE_MSG_PUB and FND_MESSAGE, so diagnostics follow standard EBS conventions. Profile options are read via FND_PROFILE, and exceptions are propagated using FND_API.