Results for “rev_ind_rate_sch_id”

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

Overview

PA_REVENUE_SCHEDULES_LOV_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the PA (Projects) product family and, as its name implies, functions as a list-of-values (LOV) source rather than a transactional or analytical data set. The view exposes the set of revenue rate schedules that are currently valid and eligible for selection in Projects application fields and forms. Its documented purpose is concise: it displays all defined valid revenue schedules.

Because it is a view and not a table, it carries no independent storage, holds no data of its own, and cannot be written to. Instead, it derives its result set at runtime from the Projects rate schedule infrastructure, presenting a filtered and user-friendly projection of scheduling data. In an EBS reporting and integration context, the view serves as the canonical reference for the revenue rate schedules that a user or concurrent program may legitimately choose. Reporting tools, form LOVs, and interface programs can query it to keep user selections consistent with the schedules that Oracle Projects considers active.

Underlying Base Objects

The documented dependencies for this view are FND_PROFILE (PACKAGE), PA_IND_RATE_SCHEDULES (VIEW), and PA_UTILS (PACKAGE). The central dependency is PA_IND_RATE_SCHEDULES, the view that maintains industry rate schedule definitions. PA_REVENUE_SCHEDULES_LOV_V reads from it directly, aggregating the schedule identifiers and names that satisfy the schedule type and validity criteria required for revenue recognition.

The ETRM excerpt lists the following implementation body:

• IND_RATE_SCH_ID and IND_RATE_SCH_NAME are selected from PA_IND_RATE_SCHEDULES IRS.
• The predicate IRS.PROJECT_ID IS NULL restricts the result set to shared, organization-level schedules that are not tied to a specific project.
• The date predicate TRUNC(SYSDATE) BETWEEN TRUNC(IRS.START_DATE_ACTIVE) AND NVL(IRS.END_DATE_ACTIVE, TRUNC(SYSDATE)) enforces active-date validity, so only schedules whose active window includes the current date are returned; a null end date is treated as open-ended.

The FND_PROFILE and PA_UTILS package references indicate that the view, as deployed in the EBS data model, also draws on profile option values and Projects utility logic to evaluate schedule eligibility. Because all these references share the APPS schema, the view can be queried without qualification by APPS-connected sessions.

Key Columns

The documented output columns map to the schedule attributes surfaced for selection:

• REV_IND_RATE_SCH_ID — the unique identifier of the revenue industry rate schedule. This is the internal key used in foreign-key relationships on revenue and billing transactions.
• REVENUE_RATE_SCHEDULE — the descriptive name of the revenue rate schedule presented to the user in LOV windows and reports.

The underlying implementation aliases the source columns as IND_RATE_SCH_ID and IND_RATE_SCH_NAME. In practice, the ID column supplies the value passed into foreign-key columns of downstream tables, while the name column supplies the displayed label. Both columns are populated for every active, non-project-specific schedule returned.

Common Use Cases and Queries

The primary use case is validating or populating a revenue rate schedule selection during project setup, revenue generation, or interface processing. A typical LOV query returns the identifier and name for a picker field:

• SELECT rev_ind_rate_sch_id, revenue_rate_schedule FROM pa_revenue_schedules_lov_v ORDER BY revenue_rate_schedule;

Reports that resolve a stored schedule ID to a display name, or that cross-check which valid schedules exist at a given run date, use the same view with a filter:

• SELECT revenue_rate_schedule FROM pa_revenue_schedules_lov_v WHERE rev_ind_rate_sch_id = :schedule_id;

Integration programs importing project or revenue data can query the view to confirm that an inbound schedule identifier is currently valid before inserting it into Projects tables. Because validity is evaluated against SYSDATE at query time, no additional date filtering is required by the caller. Compared with querying PA_IND_RATE_SCHEDULES directly, this view encapsulates the project-null and active-date rules, ensuring consistent behavior across forms, reports, and interfaces.