Results for “batch_name”

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

Overview

APPS.PJM_TRANSFER_IPV_PKG is a PL/SQL package in the Oracle E-Business Suite Projects (PJM) application schema. Its principal business function is to move Supplier Invoice cost transactions — specifically those associated with Inter-Project and Intra-Project transfers (IPV/ERV) — into the Oracle Projects transaction interface so that they can be processed, costed, and accounted for against the correct project, task, and expenditure type. In practice, the package bridges Oracle Payables and Oracle Projects: it evaluates invoice distribution lines, determines the appropriate expenditure type for IPV (Invoice Price Variance) and ERV (Exchange Rate Variance) amounts, and populates the PA_TRANSACTION_INTERFACE tables for downstream import into Oracle Projects. This supports organizations that must route supplier invoice variances and related costs to projects rather than absorbing them outside the project cost structure. The package is classified as OTHER in the ETRM API classification, indicating it is not a public, externally supported API but rather an internal component used by Oracle Projects' transfer logic.

Key Procedures and Functions

• BATCH_NAME — Generates or returns a batch identifier that groups the set of IPV/ERV transfer transactions created during a processing run. This value is used to correlate interface records with the batch in which they were inserted.
• GET_IPV_EXPENDITURE_TYPE — Determines the expenditure type to assign to invoice price variance amounts when transferring them to Oracle Projects. It resolves the correct expenditure type based on project/organization parameters and system configuration.
• GET_ERV_EXPENDITURE_TYPE — Determines the expenditure type to assign to exchange rate variance amounts. It mirrors GET_IPV_EXPENDITURE_TYPE but targets the ERV variance category.
• TRANSFER_IPV_TO_PA — The primary driver procedure. It reads the relevant supplier invoice distribution data, computes the IPV (and related) amounts, applies the resolved expenditure types, and inserts records into the PA transaction interface tables for subsequent import by Oracle Projects.

Tables Accessed

The package reads and writes the following documented tables (accessed through APPS synonyms):

• AP_INVOICES, AP_INVOICE_DISTRIBUTIONS — Source supplier invoice headers and distribution lines that carry the variance amounts to be transferred.
• AP_SYSTEM_PARAMETERS — Payables system-level settings that influence invoice and variance processing.
• GL_DAILY_CONVERSION_TYPES — Currency conversion type definitions used in exchange rate variance determination.
• PA_PROJECTS_ALL, PA_TASKS — Project and task validation and lookup for the target project charge.
• PA_TRANSACTION_INTERFACE, PA_TRANSACTION_INTERFACE_ALL — Interface tables into which transfer records are inserted for Oracle Projects import.
• PJM_ORG_PARAMETERS, PJM_PROJECT_PARAMETERS — Organization and project-level configuration controlling IPV/ERV processing behavior.
• PO_DISTRIBUTIONS, PO_LINES — Purchase order distribution and line data used to trace cost origins and validate transfers.
• RCV_SHIPMENT_HEADERS, RCV_TRANSACTIONS — Receiving data that may be referenced when reconciling invoice costs to receipt-based commitments.
• WIP_DISCRETE_JOBS — Work in Process job references for cost transactions tied to manufacturing.

Usage Notes

PJM_TRANSFER_IPV_PKG is an internal Oracle Projects component rather than a customer-invoked public API. It is referenced by the related package PJM_TRANSFER_SPEC_CHARGES_PKG, indicating that it participates in the broader special-charges transfer flow. Invocation typically occurs indirectly through Oracle Projects concurrent programs or forms that transfer supplier invoice variances to project cost. Because the package writes directly into PA_TRANSACTION_INTERFACE tables, any custom usage should respect interface record structure and run Oracle Projects interface import processes afterward. Customizations should avoid modifying the package itself; extending behavior is better achieved through configuration of expenditure types, project/organization parameters, and Payables system options.