Search Results add_to_fulfillment_set

Overview

OE_SPLIT_UTIL is an internal utility package in the APPS schema that supports line-splitting operations within the Oracle Order Management module of Oracle E-Business Suite. Order lines frequently must be divided into multiple lines to satisfy distinct shipping, scheduling, warehouse, or fulfillment requirements — for example when a single ordered quantity ships from more than one inventory organization, when a drop-ship portion must be separated from a stocked portion, or when backordered quantities must be released independently. OE_SPLIT_UTIL centralizes the low-level logic that performs these divisions, invokes the public order-capture APIs, preserves attribute values, and writes the resulting split relationships to the order line split detail tables.

The package is classified as a UTIL (utility) API rather than a public interface. It is invoked internally by other Order Management packages rather than by external integrators, and its status is VALID in the ETRM registry for both 12.1.1 and 12.2.2. It depends on FND_API for the standard EBS API return-status conventions and on OE_ORDER_PUB, the public order-capture PL/SQL interface, for line creation and maintenance operations.

Key Procedures and Functions

Eight procedures and functions are documented for this package:

• DEFAULT_ATTRIBUTES — populates default values for the attributes of a line being created during a split, ensuring the new line inherits required column values such as order, line type, item, and shipping attributes.
• SPLIT_LINE — the core routine that divides an existing order line into two or more lines according to the requested split quantities or criteria.
• CHECK_SPLIT_COURSE — evaluates whether a proposed split is permitted, applying Order Management split-course validation rules before the split is executed.
• CASCADE_NON_PROPORTIONAL_SPLIT — handles cascading effects when a split is non-proportional, propagating the split to dependent or child line structures.
• RECORD_LINE_HISTORY — writes order line history records that document the split action for audit and traceability purposes.
• ADD_TO_FULFILLMENT_SET — associates the split line with the appropriate fulfillment set so downstream fulfillment and shipping processes treat the lines correctly.
• DEFER_SPLIT — marks a split to be performed at a later processing point rather than immediately, supporting deferred-processing scenarios.
• BULK_INSERT — performs high-volume insertion of multiple split lines or split detail rows in a single operation for performance.

Tables Accessed

The package references the following tables through APPS synonyms:

• OE_ORDER_LINES / OE_ORDER_LINES_ALL — the base order line tables; the split utility reads source lines and writes the newly created split lines. OE_ORDER_LINES_ALL is the multi-organization master table.
• OE_LINE_SPLIT_DETAILS — stores the split detail relationships, recording which source line produced which split lines and in what quantities.
• OE_LINE_SETS — used by the ADD_TO_FULFILLMENT_SET logic to associate split lines with fulfillment sets.
• OE_DROP_SHIP_SOURCES — reference data for drop-ship sourcing, consulted when a split separates a drop-ship portion of a line.

Usage Notes

Because OE_SPLIT_UTIL is an internal utility, it should not be called directly from ordinary custom code. It is invoked by OE_LINE_UTIL, OE_ORDER_PVT, OE_SCHEDULE_UTIL, OE_SHIPPING_INTEGRATION_PVT, OE_SHIP_CONFIRMATION_PUB, and recursively by itself, according to the documented dependency tree. These callers drive splits triggered from Order Management forms, the schedule and shipping integration flows, and shipping confirmation processing. Developers extending Order Management should use the public OE_ORDER_PUB APIs, which ultimately delegate to this utility, rather than invoking OE_SPLIT_UTIL procedures directly. Any custom call should observe FND_API error-handling conventions and must respect the same validation and history-recording steps the standard callers perform.