Search Results pa_rate_pvt_pkg




Overview
Explore in AI Chat

Overview

PA_RATE_PVT_PKG is an internal (private) PL/SQL package in the APPS schema that centralizes the rate lookup and revenue calculation logic used throughout Oracle Projects. Its name reflects its dual role: "RATE" for the retrieval and derivation of bill rates and burden rates, and "PVT" for private, indicating that the package is intended for internal consumption by other Oracle Projects packages rather than as a public API for customer extensions. The package is classified as VALID and carries the API classification OTHER, distinguishing it from the formally supported public APIs documented for external integration.

In business terms, PA_RATE_PVT_PKG answers the recurring question of how much revenue should be recognized or how much cost should be charged for a given expenditure item or project event, based on the rate structures, revenue generation methods, and period definitions configured in Oracle Projects. It is a foundational utility layer: revenue generation, cost distribution, forecasting, and transfer pricing all depend on it to arrive at consistent amounts.

Key Procedures and Functions

  • GET_ITEM_AMOUNT — Derives the monetary amount associated with a specific expenditure item, applying the applicable rate or price logic for that item. It is typically the entry point used by callers that need a single item's computed value.
  • CALC_EVENT_BASED_REVENUE — Calculates revenue for projects configured with event-based revenue recognition, where revenue is recognized upon the occurrence of defined project events rather than as a function of cost or a fixed schedule.
  • CALC_COST_BASED_REVENUE — Calculates revenue for projects using the cost-based revenue generation method, applying the appropriate burden or rate to accumulated costs for the period.
  • GET_REVENUE_GENERATION_METHOD — Returns the revenue generation method configured for a project, allowing callers to branch their processing according to whether revenue is event-based, cost-based, or otherwise defined.
  • GET_INITIAL_BILL_RATE — Retrieves the initial bill rate applicable to a given item or assignment, serving as the starting point for rate derivation and any subsequent rate escalation logic.
  • CALC_RATE_AMOUNT — Computes an amount by applying a rate to a quantity, encapsulating the arithmetic and rounding conventions used consistently across Projects modules.
  • GET_REP_PERIOD_DATES — Returns the reporting period start and end dates, enabling date-driven calculations to align with the Projects reporting calendar rather than the GL calendar.

Tables Accessed

The package reads from a broad set of configuration and transaction tables through APPS synonyms. Rate and revenue configuration data come from PA_BILL_RATES_ALL, PA_FORECASTING_OPTIONS, PA_FORECASTING_OPTIONS_ALL, PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, PA_PROJECT_ASSIGNMENTS, and PA_IMPLEMENTATIONS (with its _ALL counterpart). Transaction-level data is drawn from PA_EXPENDITURE_ITEMS_ALL and PA_FORECAST_ITEMS. Period information is resolved through GL_PERIODS, GL_PERIOD_STATUSES, GL_DATE_PERIOD_MAP, and PA_PERIODS, while PA_REP_PERIOD_DATES_V supplies reporting period boundaries. GL_PERIODS and PA_PERIODS appear in the documented dependency list directly, confirming the package's reliance on both the General Ledger and Projects calendars.

Usage Notes

PA_RATE_PVT_PKG is referenced by nine other packages, including PA_COST, PA_REVENUE, PA_FI_AMT_CALC_PKG, PA_CC_TRANSFER_PRICE, PA_GENERATE_FORECAST_PUB, PA_FP_GEN_BUDGET_AMT_PUB, PA_FP_GEN_FCST_PG_PKG, PA_FORECAST_REVENUE, and PA_FCST_GLOBAL, as well as itself. Because these callers span cost distribution, revenue generation, forecasting, and cross-charge transfer pricing, the package is invoked during standard concurrent processes such as revenue generation and cost distribution, and during forecasting runs. It is not intended to be called directly from Oracle Forms or from customer-written code; the "PVT" designation signals that its signatures may change without notice. Customizations requiring equivalent rate or revenue logic should use the supported public APIs or create their own calculation routines rather than depending on this package. In Oracle EBS 12.1.1 and 12.2.2 the implementation resides in the APPS schema and is compiled as a valid database object, with its behavior governed by the Projects implementation options and period configuration of the operating unit in which it executes.