Search Results get_ind_rate_sch_rev




Overview
Explore in AI Chat

Overview

PA_COST_PLUS1 is a PL/SQL package in the Oracle EBS Projects (PA) application that supports cost-plus burdening and indirect cost calculation for project expenditures. Its primary purpose is to derive indirect cost amounts — cost, revenue, and invoice burden — from the compiled indirect cost multipliers and rate schedules maintained in the Projects costing engine. The package is classified as an "OTHER" API within ETRM, indicating that it is not a formally published public API but rather an internal engine component used by Oracle's own processing logic and, in practice, sometimes called from custom extensions.

The package name reflects its role in cost-plus processing: given a task, effective date, expenditure type, organization, and schedule type, it evaluates the applicable indirect cost rules and returns the burdened amounts alongside the denominators and account/project adjustments required for distribution and accounting. It also exposes helper routines for viewing and compiling indirect cost information.

Key Procedures and Functions

  • GET_INDIRECT_COST_IMPORT — The central procedure, and the object most commonly searched for. It accepts a task, an optional transaction interface identifier, effective date, expenditure type, organization, schedule type, and direct cost inputs, and returns the aggregated indirect cost, indirect cost denominator, indirect cost account, and indirect cost project amounts for the three currency contexts (project functional, project, and accounting) involved in a transaction. It also maintains a compiled set identifier and status/stage indicators, which signal whether the calculation succeeded or requires further processing. It is typically invoked during transaction import to stamp indirect cost amounts onto interface rows.
  • VIEW_INDIRECT_COST — A read-oriented counterpart that evaluates indirect cost for a given task, effective date, expenditure type, organization, schedule type, and direct cost, returning the indirect cost amount together with status and stage. It is used where the caller needs the computed burden without the full import-side bookkeeping.
  • GET_INDIRECT_COST_AMOUNTS — Returns the three distinct indirect cost components — costing, revenue, and invoice — for a given task, GL date, expenditure type, organization, and direct cost, along with a return status and stage. This separation mirrors the way Projects burdens the same base expenditure differently for cost, revenue, and invoicing purposes.
  • GET_IND_RATE_SCH_REV — Retrieves attributes of an indirect rate schedule revision, including the schedule name, revision identifier, revision type, and the active start and end dates. It provides the rate-schedule context that underpins the multiplier lookups performed by the other procedures.
  • GET_COMPILE_SET_INFO — Returns information about a compiled set, the structure that ties indirect cost rules to the multipliers actually applied at run time.

Tables Accessed

The package reads the compiled indirect cost structures maintained by the Projects costing engine, accessed through APPS synonyms:

  • PA_COMPILED_MULTIPLIERS — Stores the multipliers actually applied to a direct cost base once indirect rules have been compiled; this is the primary source of the burden rates returned by the cost calculation procedures.
  • PA_IND_COMPILED_SETS — Holds the compiled set definitions and their identifiers; the compiled set identifier returned by GET_INDIRECT_COST_IMPORT is resolved against this table.
  • PA_IND_RATE_SCH_REVISIONS — Maintains indirect rate schedule revisions, providing the schedule name, revision, revision type, and active date range returned by GET_IND_RATE_SCH_REV.

Together these tables form the compiled burdening model: a compiled set references a rate schedule revision, and the compiled multipliers supply the rates applied to the expenditure base.

Usage Notes

PA_COST_PLUS1 is an internal engine package rather than a supported public API. It is referenced by two other packages within the EBS codebase, and is most commonly encountered when transaction import or cost distribution processing needs to assign indirect costs to project expenditures. The most frequent touchpoint for developers is GET_INDIRECT_COST_IMPORT, invoked while populating and validating expenditure interface rows, which is why it appears in search queries related to indirect cost import.

Because the procedure declares numerous IN OUT NOCOPY parameters and relies on compiled set and rate schedule state, it must be called with the correct task, organization, effective date, and expenditure type so that the compiled multipliers are current. Custom code should treat the status, stage, and compiled set identifier outputs as authoritative indicators of whether the calculation completed successfully. Given its internal classification, direct calls from custom code carry upgrade risk, and any extension should be tested carefully against each release of the 12.1.1 and 12.2.2 code lines. The companion procedures VIEW_INDIRECT_COST and GET_INDIRECT_COST_AMOUNTS are preferable where only a display or single-component burden amount is required.