Results for “plc_sta”
40 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.PO_APPROVAL_ACTION package is a PL/SQL specification defined under the AUTHID CURRENT_USER privilege model, meaning its procedures execute with the privileges of the calling user rather than the package owner. In Oracle EBS Purchasing, this package belongs to the approval and workflow decision layer of the procurement cycle, providing the granular state-evaluation logic consumed by the Oracle Workflow approval process for both purchase requisitions and purchase orders. Its declared purpose is to answer binary approval questions — whether a document is eligible to be approved, and whether requisition completion criteria have been satisfied — returning a VARCHAR2 result that the workflow engine interprets as a routing outcome.
Key Procedures and Functions
Three documented functions constitute the package interface:
REQ_STATE_CHECK_APPROVE— Evaluates the approval state of a purchase requisition. Invoked with an item type and item key, it determines whether the requisition identified within the workflow context is in a condition that permits approval to proceed, returning a status string to the caller.PO_STATE_CHECK_APPROVE— The parallel check for purchase orders. It additionally accepts a document type parameter, allowing the same logic to serve the purchase order and purchase release document families distinguished bydoctype.REQ_COMPLETE_CHECK— Validates that a requisition has satisfied the conditions required for completion, returning a result that indicates whether the requisition may be treated as fully processed within the approval workflow.
These functions are designed to be called from workflow function activity nodes rather than directly by end users. The specification carries a legacy header reference (POXWPA9S.pls), reflecting the package's long-standing role in the Purchasing workflow architecture across EBS releases including 12.1.1 and 12.2.2.
Tables Accessed
The package reads the core purchasing and financials reference tables needed to arbitrate approval eligibility:
PO_REQUISITION_HEADERS,PO_REQUISITION_HEADERS_ALL,PO_REQUISITION_LINES_ALL, andPO_REQ_DISTRIBUTIONS— requisition document state, lines, and accounting distributions consulted byREQ_STATE_CHECK_APPROVEandREQ_COMPLETE_CHECK.PO_HEADERSandPO_RELEASES— purchase order and release headers used byPO_STATE_CHECK_APPROVE.FINANCIALS_SYSTEM_PARAMETERSandFINANCIALS_SYSTEM_PARAMS_ALL— system-level control settings that influence whether approval or completion is permissible.GL_PERIOD_STATUSES— open/closed period information, relevant where approval depends on accounting period availability.PO_ONLINE_REPORT_TEXTandPO_ONLINE_REPORT_TEXT_S— textual approval or rejection messaging associated with the online approval report.
Usage Notes
In practice, PO_APPROVAL_ACTION is invoked by the Purchasing approval workflow as a function activity, evaluating document state before an approver notification or an approval branch is selected. It is also available to custom workflow configurations and extensions that require the same approval-gating semantics without re-implementing requisition and purchase order state checks. The metadata records one dependent package referencing it, confirming a narrow, well-defined integration surface. Because the functions accept workflow item type and item key identifiers, custom code should replicate that calling convention exactly and rely on the returned VARCHAR2 status, since the package exposes no documented out-parameters and performs no side effects of its own.
-
VIEW: APPS.PJM_PROJECT_REQ_V 12.1.1
-
VIEW: APPS.PJM_PROJECT_REQ_V 12.2.2
-
View: PJM_PROJECT_REQ_V 12.2.2
Project related purchase requisition information for the Web Inquiry.
APPS.PJM_PROJECT_REQ_V·↳ FINANCIALS_SYSTEM_PARAMS_ALL·↳ FND_CURRENCY_CACHE·↳ FND_GLOBAL·Explore PJM module →
-
View: PJM_PROJECT_REQ_V 12.1.1
Project related purchase requisition information for the Web Inquiry.
APPS.PJM_PROJECT_REQ_V·↳ FINANCIALS_SYSTEM_PARAMS_ALL·↳ FND_CURRENCY_CACHE·↳ FND_GLOBAL·Explore PJM module →
-
10SC ONLY - Retrofitted
APPS.PO_REQUISITION_HEADERS_INQ_V·↳ FND_GLOBAL·↳ PO_DOCUMENT_TYPES_ALL_B·↳ PO_DOCUMENT_TYPES_ALL_TL·Explore PO module →
-
10SC ONLY - Retrofitted
APPS.PO_REQUISITION_HEADERS_INQ_V·↳ FND_GLOBAL·↳ PO_DOCUMENT_TYPES_ALL_B·↳ PO_DOCUMENT_TYPES_ALL_TL·Explore PO module →
-
View: ICX_EDM_PURCHASE_REQ_V 12.1.1
Project Related Purchase Requisitions View
APPS.ICX_EDM_PURCHASE_REQ_V·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·↳ FND_GLOBAL·Explore ICX module →
-
View: ICX_PO_REQ_HEADERS_V 12.2.2
Requistion Headers View
APPS.ICX_PO_REQ_HEADERS_V·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·↳ FND_GLOBAL·Explore ICX module →
-
View: ICX_EDM_PURCHASE_REQ_V 12.2.2
Project Related Purchase Requisitions View
APPS.ICX_EDM_PURCHASE_REQ_V·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·↳ FND_GLOBAL·Explore ICX module →
-
View: ICX_PO_REQ_HEADERS_V 12.1.1
Requistion Headers View
APPS.ICX_PO_REQ_HEADERS_V·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·↳ FND_GLOBAL·Explore ICX module →
-
Requisition Headers View
APPS.ICX_PO_REQUISITION_HEADERS_V·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·↳ FND_GLOBAL·Explore ICX module →
-
Requisition Headers View
APPS.ICX_PO_REQUISITION_HEADERS_V·↳ FINANCIALS_SYSTEM_PARAMETERS·↳ FND_CURRENCY·↳ FND_GLOBAL·Explore ICX module →
-
PACKAGE BODY: APPS.PO_CORE_S 12.1.1
-
PACKAGE BODY: APPS.PO_CORE_S 12.2.2