Results for “por_util_pkg”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
POR_UTIL_PKG is a PL/SQL package owned by the APPS schema that serves as the principal utility library for the Oracle Purchasing requisition module in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The object metadata records the package as VALID, with an API classification of OTHER, indicating that it functions as an internal service layer rather than a published public API. Its core responsibility is to centralize the low-level operations that surround requisition creation, modification, validation, submission, and purge, so that the higher-level requisition forms and concurrent programs do not duplicate this logic. The package body references FND_API for the standard EBS API error and message conventions, and it declares PL/SQL types such as ICX_ENC_IN_TYPE, PO_FCOUT_TYPE, and PO_TBL_NUMBER, indicating that it participates in both single-record and bulk, table-driven processing flows.
Key Procedures and Functions
The ETRM documentation lists 63 documented procedures and functions. Representative members include the following:
- BOOL_TO_VARCHAR — converts a Boolean value into its character representation for use in contexts where Booleans cannot be passed directly.
- DELETE_REQUISITION and PURGE_REQUISITION — remove requisition data, with PURGE_REQUISITION orchestrated by the concurrent purge program POR_PURGE_SYS_SAVED_REQ.
- DELETE_WORKING_COPY_REQ and RESTORE_WORKING_COPY_REQ — manage the working-copy requisitions used in the AutoCreate flow, deleting or restoring them as the sourcing cycle proceeds.
- GET_CURRENT_APPROVER — returns the current approver for a requisition in the approval workflow.
- GETSITESENABLEDFLAGFORCONTRACT, GET_COST_CENTER, GET_DOCUMENT_NUMBER, and GET_GLOBAL_DOCUMENT_NUMBER — resolve reference and defaulting information, including contract site enablement and document numbering.
- GET_ITEM_COST — retrieves the cost associated with an item, supporting price and cost defaulting on requisition lines.
- INTERFACE_START_WORKFLOW — initiates the workflow that drives requisition approval and routing.
- JUMPINTOFUNCTION and SUBMITREQ — support navigation and requisition submission from the middle tier.
- VALIDATE_PJM_PROJECT_INFO, VALIDATE_CCID, VALIDATE_OPEN_PERIOD, VALIDATE_SEGS, and VAL_RCV_CONTROLS_FOR_DATE — implement the validation rules for project and task information, account code combinations, open accounting periods, key flexfield segments, and receiving controls on a given date.
- REQ_HEADER_ID_EXIST — verifies the existence of a requisition header, a common precondition check.
Tables Accessed
The package reads and writes a set of APPS synonyms that span requisition, financial, and reference data. FINANCIALS_SYSTEM_PARAMETERS and MTL_PARAMETERS supply system-level defaults and control flags. FND_CURRENCIES, FND_ID_FLEX_SEGMENTS, and FND_SEGMENT_ATTRIBUTE_VALUES provide currency and key flexfield metadata used by VALIDATE_CCID and VALIDATE_SEGS. FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS, and FND_LOBS support attachments associated with requisitions. FND_USER resolves approver identities, while HR_ALL_ORGANIZATION_UNITS and HR_ORGANIZATION_INFORMATION resolve organization and cost center context. MTL_MATERIAL_TRANSACTIONS and MTL_SUPPLY are used for item cost and supply lookup. FND_LOG_MESSAGES and FND_NEW_MESSAGES are used for logging and message retrieval.
Usage Notes
POR_UTIL_PKG is an internal utility rather than a documented public API, so it is normally invoked indirectly. It is referenced by nine other packages, including POR_VIEW_REQS_PKG, PO_AUTOCREATE_DOC, PO_RCO_VALIDATION_PVT, and POR_PURGE_SYS_SAVED_REQ, which call it during requisition display, autocreation, validation, and purge processing. The requisition entry form and the AutoCreate workflow therefore exercise the package through those callers. Custom code should generally not call POR_UTIL_PKG directly; supported extension points should be used instead, since the package signature and internal behavior are not guaranteed across patches or releases. Where custom validation or defaulting logic is required, the appropriate approach is to wrap the supported API that references this utility and to avoid depending on its internal procedures.
-
PACKAGE: APPS.POR_UTIL_PKG 12.1.1
-
PACKAGE: APPS.POR_UTIL_PKG 12.2.2
-
TYPE: APPS.PO_FCOUT_TYPE 12.1.1
-
TYPE: APPS.PO_FCOUT_TYPE 12.2.2
-
TYPE: APPS.ICX_ENC_IN_TYPE 12.1.1
-
TYPE: APPS.ICX_ENC_IN_TYPE 12.2.2
-
TYPE: APPS.ICX_TBL_VARCHAR40 12.1.1
-
TYPE: APPS.ICX_TBL_DATE 12.1.1
-
TYPE: APPS.ICX_TBL_DATE 12.2.2
-
TYPE: APPS.ICX_TBL_VARCHAR40 12.2.2