Search Results oe_versioning_util




Overview
Explore in AI Chat

Overview

OE_VERSIONING_UTIL is a utility package in the Oracle E-Business Suite Order Management (OE) module, owned by the APPS schema. Its principal business function is to manage version history and audit trail capture for order, blanket, and quote entities. When users or concurrent processes modify transactional documents, this package records the prior state of those records so that a complete, queryable version history is preserved. The package supports the versioning and audit mechanisms that underpin Order Management's "Version" and "Audit" tabs, and it interacts closely with change order processing through OE_CHG_ORDER_PVT.

Classified as an API utility package (UTIL), OE_VERSIONING_UTIL is not intended as an end-user facing interface but as a shared service invoked by other Order Management packages. It is referenced by 22 other packages, which confirms its role as a common infrastructure component within the OE dependency chain.

Key Procedures and Functions

  • EXECUTE_VERSIONING_REQUEST — Drives a versioning request against the supplied entity, coordinating the versioning workflow.
  • PERFORM_VERSIONING — Performs the actual versioning operation, populating the appropriate history tables.
  • RECORD_CHANGED_RECORDS — Identifies and records records that have changed relative to the previously stored version.
  • RESET_GLOBALS — Reinitializes package-level global variables between calls, preventing state leakage across invocations.
  • CHECK_SECURITY — Validates that the calling context has authority to perform the versioning or audit action.
  • IS_REASON_RQD — Determines whether a reason code is mandatory for the change being recorded.
  • IS_AUDIT_REASON_CAPTURED — Checks whether an audit reason has already been captured for the current operation.
  • CAPTURED_REASON — Records or returns the reason captured for a change.
  • CAPTURE_AUDIT_INFO — Collects and stores audit metadata associated with a change, such as user and timestamp context.
  • GET_REASON_INFO — Retrieves reason information for display, validation, or downstream processing.

Tables Accessed

The package reads and writes the core Order Management tables through APPS synonyms. It accesses OE_ORDER_HEADERS_ALL and OE_ORDER_HEADER_HISTORY, together with OE_ORDER_LINES_HISTORY, to build order-level and line-level version snapshots. Blanket agreements are supported through OE_BLANKET_HEADERS_ALL, OE_BLANKET_HEADERS_EXT, and OE_BLANKET_HEADERS_HIST. Additional history tables—OE_PRICE_ADJS_HISTORY and OE_SALES_CREDIT_HISTORY—capture pricing adjustment and sales credit changes. PLITBLM is used as a PL/SQL index-by table type for in-memory list processing during record comparison and change detection.

Usage Notes

OE_VERSIONING_UTIL is normally invoked indirectly. Order Management forms trigger versioning through the OE_ORDER_PUB and OE_BLANKET_PUB APIs, and change order processing routes through OE_CHG_ORDER_PVT, which in turn calls this package. Concurrent programs that perform bulk audit or versioning runs may also invoke it. Because the package depends on FND_API, FND_MESSAGE, OE_MSG_PUB, and OE_DEBUG_PUB, it follows standard EBS API conventions for error handling and messaging, and it honors the OE_GLOBALS and OE_ORDER_CACHE session context. Developers extending Order Management should not call its procedures directly unless replicating the standard versioning flow, since it manipulates history tables that are expected to remain consistent with the base transactional APIs. The status of the object in both 12.1.1 and 12.2.2 is VALID, and no database object references it directly, confirming its position as a leaf utility consumed exclusively by other PL/SQL units.