Search Results oe_copy_util_ext

Overview

OE_COPY_UTIL_EXT is an APPS-owned PL/SQL package that belongs to the Oracle Order Management (OE) module family and supports the order and line copy functionality within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Oracle Order Management provides an extensive copy capability that allows users to duplicate existing sales orders, order lines, and related descriptive flexfield (DFF) information into new or existing orders. The OE_COPY_UTIL_EXT package is a supporting utility that extends the core copy logic implemented in OE_ORDER_COPY_UTIL, providing specialized handling for copy operations that fall outside the primary routing paths of the standard copy engine.

Within the ETRM 12.2.2 metadata, OE_COPY_UTIL_EXT is classified as API classification OTHER, indicating that it is not a formally published public API but an internal utility package. Its status is VALID in the APPS schema, confirming it is a compiled, operational database object. It functions as a dependent helper rather than an entry point, which shapes both its invocation pattern and the way custom code should treat it.

Key Procedures and Functions

The documented package includes one procedure: COPY_LINE_DFF.

• COPY_LINE_DFF — This procedure handles the copying of order line descriptive flexfield (DFF) data as part of a broader order or line copy operation. Descriptive flexfields store user-defined attribute values attached to order lines, and these values must be transferred correctly when a source line is duplicated to a target line. The procedure exists to ensure that DFF segment values are propagated alongside the standard copy attributes, preserving the business context configured by the user. Its exact parameter list is not published in the ETRM extract and is therefore not reproduced here.

The single-procedure footprint reflects the narrow, focused role of the package: it supplements the copy engine rather than implementing a general-purpose API surface.

Tables Accessed

The ETRM documentation excerpt lists no direct table references via APPS synonyms for this package. Instead, the package obtains its data access indirectly through its dependencies. The package references OE_ORDER_COPY_UTIL, the principal copy engine for Oracle Order Management, which in turn performs the physical reads and writes against the order and line tables (including the header and line DFF storage). OE_COPY_UTIL_EXT also references OE_ORDER_PUB, the public Order Management API package, through which order and line data manipulation is normally routed. This layered dependency means the package reads and writes order line DFF values in practice, but it does so through the shared copy utility and public API rather than through its own direct table DML.

Usage Notes

• Not a standalone entry point. Because OE_COPY_UTIL_EXT is referenced by OE_ORDER_COPY_UTIL, OE_DELAYED_REQUESTS_UTIL, and by itself, it is best understood as an internal extension point invoked from within the copy workflow rather than a package that end users or integrators call directly.
• Invocation through standard copy flows. In Oracle EBS 12.1.1 and 12.2.2, the standard order copy feature is triggered from the Sales Orders window (via the Copy action) or from concurrent programs such as the delayed order copy request. When a copy request includes line-level DFF propagation, the copy engine calls COPY_LINE_DFF to carry those values forward.
• Custom code considerations. Custom extensions that need to replicate the same DFF-copying behavior for lines can reference COPY_LINE_DFF, but the preferred integration surface remains the published OE_ORDER_PUB API. Direct invocation should be limited to scenarios that mirror the internal copy flow, since the procedure is designed to be called in a specific context where the source and target line identifiers are already established by the caller.
• Release consistency. The package exists with VALID status in both 12.1.1 and 12.2.2, and its dependency on OE_ORDER_COPY_UTIL and OE_ORDER_PUB is consistent across those releases, so behavior is expected to remain stable during upgrades within the 12.x line.