Search Results update_pa_addition_flg




Overview
Explore in AI Chat

Overview

PA_PO_INTEGRATION_UTILS is an Oracle EBS Applications (APPS) schema PL/SQL package that supports the integration between Oracle Projects and Oracle Purchasing. Its primary purpose is to provide utility logic that governs how project and task information flows into purchasing documents, and to enforce user access and project-related validation rules during the procurement lifecycle. The package is classified as an OTHER API, indicating it is a supporting utility rather than a documented public interface API. It is a VALID object in both EBS 12.1.1 and 12.2.2, and it references the FND_API package along with PO_DISTRIBUTIONS_ALL, confirming its role at the boundary between project accounting and purchasing distribution processing. The package is referenced by three other packages, including RCV_SEEDEVENTS_PVT, which suggests it participates in receiving and event-seeding flows that must reconcile project and purchasing data.

Key Procedures and Functions

The documented package exposes six procedures and functions, each addressing a specific control or retrieval task:

  • PA_USER_PO_ACCESS_CHECK — Performs a user-level access check to determine whether the current user is permitted to perform purchasing-related actions against project data, supporting security enforcement.
  • PA_USER_PO_ACCESS_PROJ — Extends access checking to a project or project-specific scope, validating that a user may transact against a given project in the purchasing context.
  • ALLOW_PROJECT_INFO_CHANGE — Determines whether project information attached to a purchasing document may be changed, guarding against modifications that would violate project or purchasing constraints.
  • GETPOLINENUM — Retrieves purchase order line number information, used to align project-related references with the corresponding purchasing line identifiers.
  • UPDATE_PA_ADDITION_FLG — Updates the project accounting "addition" flag, which controls whether project-related cost or distribution information is added or recognized for the associated transaction.
  • VALIDATE_NOVATION_PROJECTS — Validates projects involved in novation scenarios, ensuring that project records satisfy the conditions required for novation processing before the change is allowed.

Tables Accessed

The package reads and writes against a broad set of APPS synonyms. Purchasing distribution data is handled through PO_DISTRIBUTIONS_ALL, which underpins the project-to-PO distribution linkage. User and organization context is drawn from FND_USER and HR_ALL_ORGANIZATION_UNITS. Party and supplier data comes from HZ_PARTIES and PA_CI_SUPPLIER_DETAILS. Item references use MTL_SYSTEM_ITEMS. Contract and deliverable information is accessed via OKC_DELIVERABLES and OKC_RESP_PARTIES_TL. Project budgeting and control logic relies on PA_BUDGETARY_CONTROLS, PA_BUDGETARY_CONTROL_OPTIONS, PA_BUDGET_ENTRY_METHODS, PA_BUDGET_LINES, PA_BUDGET_TYPES, PA_BUDGET_VERSIONS, and PA_CONTROL_ITEMS. This table mix confirms the package bridges procurement, project budgeting, supplier, and contract data.

Usage Notes

PA_PO_INTEGRATION_UTILS is typically invoked indirectly rather than called directly by end users. It is referenced by three other packages, most notably RCV_SEEDEVENTS_PVT, and is exercised during purchasing and receiving flows where project and task information must be validated. Access-check procedures are commonly triggered from Purchasing forms or from custom code that creates or modifies purchase orders and distributions tied to projects. The UPDATE_PA_ADDITION_FLG procedure is relevant whenever the project accounting addition indicator must be synchronized with a purchasing transaction. Because the package references FND_API, it follows standard Oracle EBS API error-handling conventions, and customizations should call the documented procedures within the same transaction context as the originating purchasing action to preserve data integrity.