Search Results pa_ind_rate_schedules_all_bg




Overview
Explore in AI Chat

Overview

The PA_IND_RATE_SCHEDULES_ALL_BG table is a core master data table within Oracle E-Business Suite Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the repository for implementation-defined burden schedules, which are also commonly referred to as indirect cost (IDC) or overhead rate schedules. These schedules are critical for project costing and billing, as they define the rules and rates for applying indirect costs—such as administrative overhead, fringe benefits, or general and administrative (G&A) expenses—to raw project costs like labor and materials. The table's structure supports multi-organization data through its "_ALL" suffix and is integral to the burden costing engine, enabling complex cost accumulation and revenue generation for projects, particularly in contract and government contracting environments.

Key Information Stored

The table stores the header-level definition of each indirect rate schedule. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal its critical attributes. The primary key, IND_RATE_SCH_ID, uniquely identifies each schedule. The IND_RATE_SCH_NAME provides a unique, user-defined identifier for the schedule. The table links to other master entities to define the schedule's scope and applicability, including PROJECT_ID, TASK_ID, COST_PLUS_STRUCTURE, ORGANIZATION_STRUCTURE_ID, and ORG_STRUCTURE_VERSION_ID. These foreign keys allow schedules to be defined at various levels of granularity, from enterprise-wide to specific projects or tasks, and within specific organizational hierarchies. The table also contains standard Oracle EBS columns (e.g., CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY) for auditing.

Common Use Cases and Queries

Primary use cases involve configuring burden cost structures, reporting on schedule assignments, and troubleshooting project cost calculations. Administrators query this table to audit which schedules are defined and their assignments. A common reporting requirement is to list all schedules along with their associated projects. A sample SQL pattern for this is:

  • SELECT sch.ind_rate_sch_name, sch.ind_rate_sch_id, proj.segment1 project_number FROM pa_ind_rate_schedules_all_bg sch, pa_projects_all proj WHERE sch.project_id = proj.project_id(+);

Another critical scenario is identifying the specific burden schedule applied to a project for a given cost type (cost, revenue, invoice). This involves joining PA_PROJECTS_ALL on one of its many foreign key columns to this table (e.g., COST_IND_RATE_SCH_ID). Technical consultants often query this table and its child revision table (PA_IND_RATE_SCH_REVISIONS) to validate the rates being used in transaction cost distribution.

Related Objects

PA_IND_RATE_SCHEDULES_ALL_BG is a central hub with extensive relationships. Its primary child table is PA_IND_RATE_SCH_REVISIONS, which stores the effective-dated rate lines (multipliers and bases) for each schedule. It is heavily referenced by PA_PROJECTS_ALL for default and override schedules for cost, revenue, invoice, and capital interest rate calculations. PA_PROJECT_TYPES_ALL similarly references it for default schedules at the project type level. For Grants Accounting (GMS), it is linked to GMS_AWARDS_ALL and GMS_OVERRIDE_SCHEDULES for award-specific IDC. Other key related objects include PA_CINT_RATE_MULTIPLIERS for capital interest, PA_COST_PLUS_STRUCTURES, PA_TASKS, and the HRMS organization structures tables (PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_VERSIONS).