Results for “pa_exp_task_eff”

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

Overview

The APPS.PJM_TRANSFER_SPEC_CHARGES_PKG package is a PL/SQL program unit within the Oracle E-Business Suite Projects (Oracle Projects) module, classified as an "OTHER" API type in the ETRM documentation. Its principal business function is to transfer specific, identified charges from Oracle Purchasing and Oracle Payables source transactions into the Oracle Projects transaction interface so that they can subsequently be imported, costed, and accounted as project costs. In the context of Oracle EBS 12.1.1 and 12.2.2, this package supports the flow of externally incurred costs — most notably supplier invoice lines and receipt-originated distributions — into project accounting, preserving the linkage between the original procurement document and the eventual project expenditure item. This is a critical bridge activity that enables organizations to capture committed and actual costs against projects and tasks without manual re-entry of transaction data.

Key Procedures and Functions

The documented metadata identifies a single procedure within this package:

• TRANSFER_SPEC_CHARGES_TO_PA — The primary and only documented entry point. Its purpose is to take selected charges originating in Oracle Payables and Oracle Purchasing and move them into the Oracle Projects transaction interface (PA_TRANSACTION_INTERFACE and its "_ALL" variant), preparing them for the standard Project Transaction Import process. The procedure encapsulates the logic necessary to validate, transform, and stage these charges so that Oracle Projects can recognize them as project expenditure. No parameter lists are documented in the ETRM metadata, and therefore they are not reproduced here.

The package includes both the specification and the package body, and its dependency listing shows it references the SYS.STANDARD package, which is the standard PL/SQL foundation required by all compiled program units. The package is listed as VALID, indicating it is successfully compiled in the APPS schema.

Tables Accessed

The package's data access footprint spans the procurement, payables, and projects schemas, consistent with its charge-transfer purpose. Documented references via APPS synonyms include:

• AP_INVOICES, AP_INVOICE_DISTRIBUTIONS, AP_CHRG_ALLOCATIONS, AP_SYSTEM_PARAMETERS — The source of invoice-related charges and the ledger/currency configuration needed to interpret them.
• PO_DISTRIBUTIONS, PO_LINES, RCV_SHIPMENT_HEADERS, RCV_TRANSACTIONS — The receipt and purchase order side, providing the receiving context for charges associated with goods receipts.
• PA_PROJECTS_ALL, PA_TASKS — The project and task master data used to validate and attribute charges to the correct project structure.
• PA_TRANSACTION_INTERFACE, PA_TRANSACTION_INTERFACE_ALL — The target staging tables where transferred charges are written for subsequent import.
• PJM_ORG_PARAMETERS, PJM_PROJECT_PARAMETERS — Oracle Projects implementation and project-level parameters that govern transfer behavior and defaulting.
• GL_DAILY_CONVERSION_TYPES — Currency conversion definitions applied when charges require translation into project functional currency.

Usage Notes

This package is typically invoked as part of the Oracle Projects transaction import workflow, most often called from PL/SQL-based concurrent program logic or from extension code that automates the transfer of specific supplier charges to project expenditure. Because it is classified as an "OTHER" API rather than a formally published public API, it should be treated as a semi-internal routine: customizations may call TRANSFER_SPEC_CHARGES_TO_PA, but doing so risks inter-version differences between 12.1.1 and 12.2.2. The package is not referenced by any other documented package, indicating it sits at a leaf position in the dependency graph and is intended to be driven by external callers. Implementers should invoke it within the same processing window as the Project Transaction Import, ensure the relevant PJM organization and project parameters are configured, and validate that all staged rows reach PA_TRANSACTION_INTERFACE correctly before running import.