Search Results get_line_rate_info

Overview

PO_PA_INTEGRATION_GRP is an APPS-owned PL/SQL package in Oracle E-Business Suite that supports the integration between Oracle Purchasing (PO) and Oracle Projects (PA). Its primary business function is to supply Purchasing-side validation and rate-derivation logic consumed by Projects subledger processing, so that project-related commitments and expenditures sourced from purchase order documentation are evaluated against consistent, centrally maintained rules. The package is classified as a GRP (group) unit, indicating that it consolidates a small set of related utility routines rather than exposing a single transactional API. This grouping allows callers in the Projects schema—particularly project transaction import and project utility packages—to invoke a stable, cohesive set of functions without duplicating PO table access logic.

Key Procedures and Functions

The package exposes four documented program units:

• VALIDATE_TEMP_LABOR_PO — Performs validation of temporary labor purchase order data, confirming that PO records presented for project processing meet the expected structural and referential conditions before they are accepted by the Projects application.
• IS_RATE_BASED_LINE — Determines whether a given purchase order line operates on a rate basis. This distinction governs how associated costs are derived and whether rate information must be resolved for downstream project accounting.
• GET_LINE_RATE_INFO — Retrieves the rate information associated with a purchase order line, supplying the rate attributes required by Projects when creating or reconciling project transactions.
• IS_PO_ACTIVE — Evaluates the status of a purchase order to establish whether it remains active for project integration purposes, allowing callers to exclude cancelled, closed, or otherwise inactive documents from processing.

Parameter signatures are not documented in the available metadata and are therefore not reproduced here; consumers should inspect the package specification in the target instance before invoking these units directly.

Tables Accessed

Access is performed through APPS synonyms. The package reads PO_HEADERS_ALL and PO_LINES_ALL to resolve purchase order header and line context, PO_LINE_LOCATIONS_ALL to evaluate shipment and schedule-level attributes, and PO_DISTRIBUTIONS_ALL to obtain distribution-level accounting detail. PER_ALL_PEOPLE_F is referenced for person-level information, typically to resolve the buyer or other responsible party associated with the document, while DUAL is used for standalone expression evaluation. Read activity dominates; the package exists to interrogate PO state rather than to maintain it, leaving the transactional write path to the calling Projects processes.

Usage Notes

PO_PA_INTEGRATION_GRP is not a user-facing API and is not invoked from an Oracle Forms interface. It is called programmatically by Projects packages, with the ETRM dependency listing identifying PA_TRX_IMPORT, PA_UTILS, and PA_PJC_CWK_UTILS as referencing packages; the package also references itself. These callers include transaction import routines that bring PO-sourced costs into Projects and utility routines that require PO status and rate checks. Typical invocation therefore occurs during concurrent program execution—for example, during project transaction import or cost distribution processing—rather than through direct user action. Because the package is a dependency of shipped Projects code, customizations should avoid modifying it in place; the recommended approach is to wrap or replicate required logic in a custom package. All four program units are documented as valid in both EBS 12.1.1 and 12.2.2, and the package remains a component of the standard Purchasing–Projects integration stack.