Search Results pa_rbs_headers_vl




Overview
Explore in AI Chat

Overview

PA_RBS_HEADERS_VL is a seeded, validity-language (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Projects (PA) application. In ETRM 12.2.2 the object is documented with a status of VALID. It presents Resource Breakdown Structure (RBS) header definitions, combining the single-language business data held in PA_RBS_HEADERS_B with the translatable name and description held in PA_RBS_HEADERS_TL. RBS headers are the top-level containers of an RBS, the hierarchical structure used in Oracle Projects to classify and group resources for planning, budgeting, costing, and allocation purposes.

Because the view resolves the translated columns through USERENV('LANG'), it returns descriptive text in the language of the current session. This makes it the appropriate source for reports, concurrent programs, and integrations that must display RBS header information to end users, while hiding the underlying _B and _TL partitioning from the calling code. It is the standard interface layer for RBS header data and should be preferred over direct queries against the base tables in custom development.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through APPS synonyms:

  • PA_RBS_HEADERS_B — the business table, holding the non-translatable attributes of each RBS header. Aliased as B in the view definition.
  • PA_RBS_HEADERS_TL — the translation table, holding the language-dependent NAME and DESCRIPTION columns. Aliased as T in the view definition.

The two tables are joined on RBS_HEADER_ID, with the translation row further restricted by T.LANGUAGE = USERENV('LANG'). The SELECT list returns B.ROWID as ROW_ID alongside all business columns and the two translated columns. The join is not outer, so only RBS headers for which a translation row exists in the session language are returned; in a correctly configured installation the translatable rows are maintained for the defined languages.

Key Columns

  • ROW_ID — the ROWID of the underlying PA_RBS_HEADERS_B row, useful for building updatable views or row-level operations.
  • RBS_HEADER_ID — the primary key and the foreign key used by child RBS structures and related Projects entities.
  • EFFECTIVE_FROM_DATE / EFFECTIVE_TO_DATE — date-range columns controlling the validity period of the RBS header.
  • BUSINESS_GROUP_ID — the business group to which the header belongs, a key partitioning and access-control column in Oracle EBS.
  • USE_FOR_ALLOC_FLAG — indicates whether the RBS is intended for use in allocations.
  • NAME — the translated user-visible name of the RBS header.
  • DESCRIPTION — the translated descriptive text for the RBS header.
  • RECORD_VERSION_NUMBER — optimistic locking/versioning column maintained by the application.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns.

Common Use Cases and Queries

Typical uses include validation lists on reports or DFF value sets, RBS header lookups in Projects-to-other-module integrations, and ad hoc reporting against RBS definitions for a given business group. A representative query returning the currently valid RBS headers for a business group follows:

SELECT rbh.rbs_header_id, rbh.name, rbh.description, rbh.effective_from_date, rbh.effective_to_date, rbh.use_for_alloc_flag FROM pa_rbs_headers_vl rbh WHERE rbh.business_group_id = :p_business_group_id AND sysdate BETWEEN rbh.effective_from_date AND NVL(rbh.effective_to_date, sysdate) ORDER BY rbh.name;

For a simple name-resolution lookup driven by the header ID:

SELECT rbh.name FROM pa_rbs_headers_vl rbh WHERE rbh.rbs_header_id = :p_rbs_header_id;

Because the view already applies the session-language predicate, no additional TL join is required, and the returned NAME and DESCRIPTION appear in the language of the running session. Custom queries should reference PA_RBS_HEADERS_VL rather than the base tables to preserve translation behaviour and insulate code from future changes to the underlying table structure.