Results for “version_end_date”

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

Overview

The PA_RBS_VERSIONS_AMG_V view is a reporting object in the Oracle E-Business Suite Projects (PA) module, defined in the APPS schema. It presents version-level information for a Resource Breakdown Structure (RBS), combining the RBS header details, the individual version records, and the associated job group into a single denormalized result set. In Oracle Projects, a Resource Breakdown Structure defines the hierarchical classification of resources used for planning, budgeting, and costing. Each header may have multiple versions, and the version carries the effective dates and status that govern when the structure may be used. This view exposes that version metadata without requiring the caller to join the three base objects manually.

The view is read-only and is intended for reporting, inquiry, and integration scenarios where the version_start_date, version_end_date, and current reporting indicator of a resource breakdown structure version must be retrieved. Its primary value is convenience: it resolves the header name, version name and number, and job group display name in one access path.

Underlying Base Objects

The view is defined over three referenced base objects, all owned by APPS:

• PA_RBS_HEADERS_VL (view) — the RBS header, providing RBS_HEADER_ID and NAME. This is the parent record to which every version belongs.
• PA_RBS_VERSIONS_VL (view) — the RBS version records, providing RBS_VERSION_ID, version name and number, current reporting flag, status code, and the start and end dates.
• PER_JOB_GROUPS (synonym) — the HR job group definition, providing JOB_GROUP_ID and DISPLAYED_NAME.

The view joins PA_RBS_VERSIONS_VL to PA_RBS_HEADERS_VL on the common RBS_HEADER_ID, and outer joins to PER_JOB_GROUPS on JOB_GROUP_ID (the (+) operator). The outer join means a version row is still returned even when no job group is assigned, in which case the job group name is null.

Key Columns

• RBS_HEADER_ID / RBS_HEADER_NAME — identifier and name of the parent resource breakdown structure.
• RBS_VERSION_ID / RBS_VERSION_NAME / RBS_VERSION_NUMBER — identifier, descriptive name, and sequence number of the specific version.
• VERSION_START_DATE — the effective start date of the version; this is the column most commonly searched, as it determines from when a version is valid for use.
• VERSION_END_DATE — the effective end date, after which the version is no longer active.
• CURRENT_REPORTING_FLAG — indicates whether the version is the current one used for reporting.
• STATUS_CODE — the lifecycle status of the version.
• JOB_GROUP_ID / JOB_GROUP_NAME — the associated HR job group and its displayed name, null when unassigned.

Common Use Cases and Queries

Typical uses include identifying the active version of a resource breakdown structure as of a given date, validating that planning data was captured against a valid version, and listing versions that are current for reporting.

SELECT rbs_header_name,
       rbs_version_name,
       rbs_version_number,
       version_start_date,
       version_end_date,
       status_code,
       job_group_name
FROM   apps.pa_rbs_versions_amg_v
WHERE  TRUNC(SYSDATE) BETWEEN version_start_date
                          AND NVL(version_end_date, TRUNC(SYSDATE))
AND    current_reporting_flag = 'Y';

The view is also useful for auditing version history by header and for feeding external systems that require version validity dates and job group associations. Because it contains no bind-variable logic, standard Project security and access responsibilities should be applied by the caller.