Search Results create_chgorderworkitem

Overview

OE_CHG_ORDER_PVT is a private PL/SQL package body in the Oracle Order Management module of Oracle E-Business Suite, owned by the APPS schema. As indicated by the "PVT" (private) API classification, the package is not part of the supported public API surface and is intended for internal consumption by Oracle's own forms, workflows, and dependent packages. Its central business function is to support change order processing within the Order Management workflow: it creates and drives the change order workflow item type (OECHGORD) and manages the history and audit records that capture changes made to orders, order lines, sales credits, and price adjustments.

The package body header identifies the API name as OE_CHG_ORDER_PVT and classifies it as private, with a version of 1.0. The script carries a revision identifier ($Header: OEXVCHGB.pls 120.7) reflecting its maintenance lineage. In the 12.1.1 and 12.2.2 releases the package remains a supporting element of the change order and audit history infrastructure rather than a customer-facing interface.

Key Procedures and Functions

The package exposes twelve documented procedures and functions:

• START_CHANGEORDERFLOW — starts the change order workflow process by invoking the Workflow Engine for a given item type and item key. Debug messages are emitted conditionally when the OE debug level is greater than zero.
• CREATE_CHGORDERWORKITEM — the procedure matched by the user's search term. It is called from a Notification Window to create a change order workflow item type and to start a flow that sends an FYI notification to the resolving responsibility. It is declared with PRAGMA AUTONOMOUS_TRANSACTION so that its commit or rollback does not affect the calling session, such as the Error Message form.
• GENERATE_PLSQLDOC — a utility procedure for generating PL/SQL documentation comments associated with the package.
• UPDATE_USER_TEXT — updates the user-supplied text associated with a change order or notification item.
• UPDATE_ORDER_NUMBER — updates the order number reference on the workflow or change order records.
• RECORDLINEHIST, RECORDHEADERHIST, RECORDHSCREDITHIST, RECORDLSCREDITHIST, RECORDHPADJHIST, RECORDLPADJHIST — a family of history-recording procedures that write change history for header-level and line-level records, sales credits (header and line), and price adjustments (header and line).
• RESET_AUDIT_HISTORY_FLAGS — resets audit and history flags, typically after history capture has completed.

Tables Accessed

The package reads and writes several base tables through APPS synonyms. OE_ORDER_HEADER_HISTORY, OE_ORDER_LINES_HISTORY, OE_SALES_CREDIT_HISTORY, and OE_PRICE_ADJS_HISTORY store the historical snapshots generated by the RECORD*HIST procedures. OE_WF_KEY_S is used to obtain workflow item key sequences when creating change order workflow items. FND_USER supplies user identity information for history and notification records, while IBY_CREDITCARD_H provides credit card data relevant to credit history capture. DUAL is used for simple single-row evaluations, and HTF and PLITBLM support HTML formatting and PL/SQL table manipulation within the package's text-handling logic.

Usage Notes

OE_CHG_ORDER_PVT is referenced by nine other packages, confirming its role as shared internal infrastructure. It is typically invoked from Order Management forms and from workflow notification windows rather than directly by customers. The autonomous transaction in CREATE_CHGORDERWORKITEM is significant: callers can request FYI notifications without committing or rolling back their own transactional context. Customizations should avoid calling these private procedures directly, since Oracle does not guarantee signature stability across patches; supported change order extensions should instead use the public Order Management APIs. Administrators tracing change order history issues should enable OE debug output to capture the diagnostic messages emitted by START_CHANGEORDERFLOW.