Results for “upd_idv_qty_amt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_DOCUMENT_ACTION_UTIL is a utility package body in the APPS schema whose classification is UTIL. It provides shared, low-level supporting logic for the Oracle Purchasing document action framework, most visibly the Document Control (accept, reject, return, cancel, close, and related authority-state transitions) that governs how purchasing documents move through their approval lifecycle. Rather than exposing a public API surface of its own, the package consolidates reusable helper routines that the primary documents action package family — notably PO_DOCUMENT_ACTION_PVT — calls to resolve preparer and employee identities, validate document state, mutate authorization status, and preserve the Purchasing action history.

The package is oriented toward maintaining data integrity around document state changes and quantity/price corrections. Because it manipulates PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and related draft and merge structures, it is a sensitive object that should never be modified without full regression across the purchasing document lifecycle.

A search for the related object PO_WORKFORCE_CURRENT_X is significant here: PO_DOCUMENT_ACTION_UTIL references PO_WORKFORCE_CURRENT_X, a current-version workforce view. This view resolves active employee and assignment information, and is the mechanism by which the package maps document preparers and approvers to current HR workforce records rather than to legacy PER tables. It is the preferred lineage for fields originally surfaced through the older PO_WORKFORCE_CURRENT_X / PER_WORKFORCE_CURRENT_X family, and it is why PO_WORKFORCE_CURRENT_X appears directly in the package's dependency list.

Key Procedures and Functions

Twelve documented procedures and functions are recorded for this package in the 12.2.2 metadata, including:

• CHECK_DOC_STATE — validates the current state of a purchasing document, confirming that the conditions required for a requested action are satisfied before the action proceeds.
• GET_DOC_PREPARER_ID — resolves the party who prepared the document, typically by mapping the stored person reference to a current workforce/employee identifier.
• GET_EMPLOYEE_ID — returns the employee identifier associated with a given user or person, normalizing identity across FND_USER and the HR workforce views.
• GET_EMPLOYEE_INFO — retrieves descriptive employee attributes (name, assignment, and related details) for display or audit purposes.
• CHANGE_DOC_AUTH_STATE — performs the actual authorization-state transition on the document, applying the new authority status to the header.
• HANDLE_CTL_ACTION_HISTORY — records or manages the Document Control action history entry so that each accept/reject/return decision is auditable.
• UPD_IDV_QTY_AMT and UPD_IDV_QTY_AMT_HDR — update quantity and amount values on lines and on the document header, respectively, supporting individual document quantity/amount corrections.
• UPDATE_DOC_AUTH_STATUS — persists the authorization status onto the document, complementing CHANGE_DOC_AUTH_STATE.

All routines operate as internal helpers; parameter lists are intended for framework callers, not external consumers.

Tables Accessed

The package reads and writes the core Purchasing transactional tables: PO_HEADERS and PO_HEADERS_ALL (document header state and authorization status), PO_LINES and PO_LINES_ALL, PO_LINE_LOCATIONS and PO_LINE_LOCATIONS_ALL, and PO_DISTRIBUTIONS_ALL for quantity and amount maintenance. Draft structures (PO_DRAFTS, PO_LINES_DRAFT_ALL) and merge views (PO_HEADERS_MERGE_V, PO_LINES_MERGE_V, PO_LINE_LOCATIONS_MERGE_V) are used during action evaluation. It also maintains PO_ACTION_HISTORY and PO_NOTIFICATIONS, references PO_AGENTS, PO_DOC_STYLE_HEADERS, and PO_LINE_UCAS, and looks up FND_USER, HR_LOCATIONS, and organization definitions. FINANCIALS_SYSTEM_PARAMETERS supplies system-level control settings, while PO_WORKFORCE_CURRENT_X appears explicitly in the dependency list for employee resolution.

Usage Notes

PO_DOCUMENT_ACTION_UTIL is invoked indirectly through the Purchasing Document Control UI and the document action framework, typically as a child of PO_DOCUMENT_ACTION_PVT and PO_DOCUMENT_TOTALS_PVT. It is not intended for direct invocation from custom code. Developers performing extensions or diagnostics should trace the calling action package rather than calling these utilities directly, and must regression-test accept, reject, return, and quantity/amount updates whenever the package is affected.