Search Results ind_rate_sch_usage

Overview

The PA_IND_RATE_SCHEDULES view is a business-group–scoped reporting object in the Oracle EBS Projects (PA) module, owned by the APPS schema. It exposes burden schedules — referred to internally as indirect rate schedules — that are owned by the current business group. In Oracle Projects terminology, an indirect rate schedule defines the multipliers or rates applied to raw costs and, in some configurations, to revenue and invoicing, to arrive at burdened amounts used for costing, revenue accrual, and invoicing.

The view's primary role is to filter the multi-organization base entity PA_IND_RATE_SCHEDULES_ALL_BG down to records accessible to the user's operating business group, unless the cross–business-group profile option permits broader visibility. It is therefore a common integration and reporting point for costing and burdening data, and it exposes the identifier IND_RATE_SCH_ID (the "ind_rate_sch_id") as the unique schedule key. Because it is a view, it presents a denormalized, ready-to-query row per indirect rate schedule without requiring the caller to replicate the business-group security predicate.

Underlying Base Objects

The view is defined over a single base object plus supporting packages. The documented referenced objects are:

• PA_IND_RATE_SCHEDULES_ALL_BG (SYNONYM) — the source of all columns; the alias A in the view text refers to this object.
• FND_PROFILE (PACKAGE) — invoked as FND_PROFILE.VALUE('PER_BUSINESS_GROUP_ID') to retrieve the session's current business group for the row-level filter.
• PA_UTILS (PACKAGE) — supplies PA_UTILS.ISCROSSBGPROFILE_WNPS, which determines whether cross–business-group access is enabled.

The WHERE clause implements the security rule: a row is returned when its BUSINESS_GROUP_ID equals the profile business group and the cross-BG flag is 'N', or unconditionally when the cross-BG flag is 'Y'. In 12.1.1 and 12.2.2 the view remains VALID and unchanged in structure.

Key Columns

• IND_RATE_SCH_ID — the unique surrogate key of the indirect rate schedule; joins to the schedule's rate lines.
• IND_RATE_SCH_NAME, DESCRIPTION — identification and free-text description.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating range of the schedule.
• IND_RATE_SCHEDULE_TYPE, IND_RATE_SCH_USAGE — the schedule's type and its usage context.
• COST_PLUS_STRUCTURE — the cost-plus burden structure applied.
• PROJECT_ID, TASK_ID — project/task association where the schedule is project-specific.
• COST_OVR_SCH_FLAG, REV_OVR_SCH_FLAG, INV_OVR_SCH_FLAG — flags indicating override behavior for cost, revenue, and invoice processing.
• BUSINESS_GROUP_ID — the owning business group, central to the view's filter.
• ORGANIZATION_STRUCTURE_ID, ORG_STRUCTURE_VERSION_ID, START_ORGANIZATION_ID — organizational scope of the schedule.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view supports validation of burden schedules, integration extracts, and troubleshooting of costing/revenue configuration. A typical lookup by the searched identifier:

• SELECT ind_rate_sch_id, ind_rate_sch_name, ind_rate_schedule_type, start_date_active, end_date_active, cost_plus_structure
• FROM pa_ind_rate_schedules
• WHERE ind_rate_sch_id = :p_sch_id;

To list currently active schedules in the operating business group:

• SELECT ind_rate_sch_id, ind_rate_sch_name
• FROM pa_ind_rate_schedules
• WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

Because the view enforces the business-group predicate automatically, it is preferred over querying PA_IND_RATE_SCHEDULES_ALL_BG directly for reporting, ensuring results align with the user's PER_BUSINESS_GROUP_ID context.