Results for “non_labor”

24 results




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

Overview

PA_PLAN_REVENUE is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite (validated across 12.1.1 and 12.2.2). It belongs to the Oracle Projects (PA) module and supports revenue planning within the project financial planning (FP) framework. The package is responsible for resolving, deriving, and returning the billing and revenue rates that drive planned versus actual revenue calculations for project resources, resource classes, and planning scenarios.

In the project financial planning flow, planned revenue must be computed by applying the appropriate bill rate or revenue rate to planned quantities and amounts. Those rates can originate from several sources: standard bill rate schedules, employee or job rate overrides, resource-specific rates, or default rates. PA_PLAN_REVENUE centralizes the logic used to determine which rate applies for a given planning context, abstracting the underlying complexity from higher-level planning, budgeting, and forecasting programs. It is classified as an "OTHER" API rather than a public published interface, meaning it is intended primarily for internal use by other Oracle Projects packages and is not formally documented as a customer-callable API.

Key Procedures and Functions

The package exposes seven documented procedures and functions, each returning rate information for a distinct planning context:

The structure of these routines reflects a matrix of planning basis (plan or actual) against rate dimension (general, revenue, resource class), with defaults applied as a last resort.

Tables Accessed

The package reads from a defined set of APPS synonyms:

Usage Notes

PA_PLAN_REVENUE is not typically invoked directly through a form or concurrent program; instead it is consumed programmatically. Documented callers include PA_FIN_PLAN_UTILS2, PA_FP_CALC_PLAN_PKG, PA_FP_GEN_BUDGET_AMT_PUB, PA_FP_GEN_FCST_AMT_PVT, and PA_PROGRESS_UTILS. These packages drive financial plan calculation, budget amount generation, and forecast amount generation. Custom extensions that need consistent rate resolution within the FP framework should call the same routines rather than reimplementing rate logic, since the package encapsulates override precedence, schedule selection, and default fallback behavior. Because it is classified as a non-public API, its signatures may change between patch levels, and customers should validate behavior against their specific release before relying on it in bespoke code.