Search Results get_rate_sch_rev_id

Overview

PA_COST_PLUS is a core Oracle Projects (PA) PL/SQL package in the APPS schema that implements burdening logic for cost-plus and indirect cost calculations within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal responsibility is to compile and maintain indirect cost multipliers, burden schedules, and cost-plus structures that determine how raw expenditure items are transformed into burdened costs. The package resolves the applicable rate schedule, rate schedule revision, and compiled multiplier set for a given organization or organization hierarchy, then applies the resulting burden to expenditure items and expenditure item adjustments.

In practice, PA_COST_PLUS serves as the computational engine behind indirect cost distribution and burdening across Oracle Projects and Grants Management. It evaluates cost bases, indirect cost codes, and expenditure type mappings to produce burden amounts that feed billing, revenue accrual, capitalized interest, funds control, and cross-charge transfer pricing. The package is classified as an "OTHER" API and is intended primarily for internal use by other Oracle Projects packages and concurrent processes rather than as a public extension surface.

Key Procedures and Functions

The package exposes 39 documented procedures and functions. The compilation group — COMPILE_ORG_RATES, COMPILE_ORG_HIERARCHY_RATES, COMPILE_SCHEDULE, and COMPILE_ALL — builds and refreshes compiled multiplier data for organizations, hierarchies, and rate schedules. NEW_ORGANIZATION supports initialization or setup of organization-level burdening context.

The retrieval group provides the read-side interface. GET_INDIRECT_COST_SUM, GET_DETAIL_INDIRECT_COSTS, and VIEW_INDIRECT_COST return aggregated or itemized indirect cost results. GET_BURDEN_AMOUNT and GET_BURDEN_AMOUNT1 compute burden for an expenditure item or adjustment. GET_EXP_ITEM_INDIRECT_COST and GET_EXP_ITEM_BURDEN_AMOUNT return burden figures tied to a specific expenditure item, while POPULATE_INDIRECT_COST drives population of indirect cost rows.

Supporting configuration lookups include GET_COST_BASE and GET_COST_PLUS_STRUCTURE, which resolve the applicable cost base and cost-plus structure, and GET_ORGANIZATION_ID and GET_COMPILED_SET_ID, which resolve organizational and compiled set identifiers. Rate schedule resolution is handled by FIND_RATE_SCH_REV_ID, GET_RATE_SCH_REV_ID, and GET_HIERARCHY_FROM_REVISION.

Tables Accessed

PA_COST_PLUS reads and writes the tables that define burdening configuration and store calculated results. PA_COMPILED_MULTIPLIERS and PA_IND_COMPILED_SETS hold compiled multiplier data generated by the COMPILE_* routines. PA_IND_COST_MULTIPLIERS, PA_IND_RATE_SCHEDULES, and PA_IND_RATE_SCH_REVISIONS define indirect rate schedules and their revisions. PA_COST_BASES, PA_COST_BASE_COST_CODES, PA_COST_BASE_COST_CODES_S, PA_COST_BASE_EXP_TYPES, and PA_COST_PLUS_STRUCTURES define cost bases, eligible cost codes, expenditure type mappings, and cost-plus structure definitions.

Expenditure-side access includes PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS, PA_EXPENDITURE_ITEMS_ALL, and PA_EXPEND_ITEM_ADJ_ACTIVITIES for source transactions and adjustments. PA_COST_DISTRIBUTION_LINES and PA_COST_DISTRIBUTION_LINES_ALL receive distributed cost and burden results. PA_PLSQL_DATATYPES supplies shared PL/SQL types.

Usage Notes

PA_COST_PLUS is referenced by 16 packages, reflecting its central role in Projects costing. Upstream callers include PA_COST, PA_COST1, PA_COST_PLUS, PA_COST_PLUS1, PA_COST_BASE_EXP_TYPES_PKG, and PA_BURDEN_CMTS, which drive burdening during cost distribution. Downstream consumers include PA_BILLING, PA_REVENUE_AMT, PA_CAPITALIZED_INTEREST, PA_FUNDS_CONTROL_PKG1, PA_FUNDS_CONTROL_UTILS, PA_INVOICE_DETAIL_PROCESS, PA_CC_TRANSFER_PRICE, and PA_FORECAST_COST. Grants Management packages GMS_COST_PLUS_EXTN and GMS_PA_API3 also depend on it.

The COMPILE_* routines are typically invoked from concurrent programs that pre-compute multipliers on schedule or after rate schedule maintenance, while the GET_* functions are called online during expenditure processing, billing, and revenue generation. Custom extensions should avoid direct calls to internal procedures and instead rely on documented interfaces and standard concurrent programs, since compile and retrieval semantics depend on consistent compiled set state.