Results for “orig_system_id”

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

Overview

The view FND_RESP_SEC_ROLES_VL is owned by the APPS schema and resides in the FND (Application Object Library) product module. In Oracle EBS 12.1.1 and 12.2.2, the _VL suffix conventionally denotes a "validated" or language-enabled view that presents translated display columns alongside base attributes, typically composed from an underlying _B and _TL table pair. FND_RESP_SEC_ROLES_VL is intended to expose responsibility-to-role security mappings associated with the Role-Based Access Control (RBAC) and Oracle User Management (UMX) infrastructure introduced with the 12.x security model, where roles replace or augment traditional responsibilities in the access decision path.

Its documented role in EBS reporting and integration is to serve as the queryable interface through which administrators, diagnostics, and custom extensions can inspect the relationship between responsibilities and the roles assigned to them. Because the ETRM catalog records the object as VALID and READ-ONLY in behavior, it is intended strictly for query access rather than direct DML.

Underlying Base Objects

The ETRM documentation for this object in 12.2.2 records a single referenced base object: DUAL, exposed through its SYNONYM in the APPS schema. The view text is documented as:

• A SELECT list of all required columns cast as TO_CHAR(NULL), TO_NUMBER(NULL), and TO_DATE(NULL) with explicit datatypes.
• A FROM clause of DUAL WHERE 1 = 2.

The WHERE 1 = 2 predicate is a standard EBS technique used to force an empty result set while preserving column metadata. This construct typically indicates that the view acts as a placeholder or a seed definition whose effective query is supplied or overridden at runtime, or that the object is deprecated in this release. Consequently, no direct physical dependency on a base table such as FND_RESP_SEC_ROLES_B or FND_RESP_SEC_ROLES_TL is documented in the provided metadata, and consumers should not assume persistent row-level storage behind this view.

Key Columns

The column list mirrors the standard EBS audit and language pattern. Although each expression returns a typed NULL in the documented definition, the column semantics in the EBS data model are as follows:

• NAME — the internal or developer-facing identifier of the responsibility-security role record.
• DISPLAY_NAME — the user-facing label rendered in the corresponding session language.
• DESCRIPTION — free-text explanation of the role's purpose within the responsibility mapping.
• LANGUAGE and SOURCE_LANG — the language code of the translated row and the source language of the base record, respectively.
• ORIG_SYSTEM and ORIG_SYSTEM_ID — the originating system identifier and its numeric key, supporting foreign-record integration.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row provenance.

Common Use Cases and Queries

Given the placeholder nature of the documented definition, the primary practical use of this view is metadata discovery — enumerating its columns from the data dictionary rather than extracting data.

• Verify the object's existence and column shape prior to developing dependent code.
• Confirm the presence of WHO audit columns and language columns when building extract or reconciliation logic.
• Detect whether the object has been customized in a specific instance.

Representative queries include:

• SELECT * FROM APPS.FND_RESP_SEC_ROLES_VL; — returns zero rows under the documented definition.
• SELECT COLUMN_NAME, DATA_TYPE, DATA_LENGTH, NULLABLE FROM DBA_TAB_COLUMNS WHERE OWNER = 'APPS' AND TABLE_NAME = 'FND_RESP_SEC_ROLES_VL' ORDER BY COLUMN_ID;
• SELECT TEXT FROM DBA_VIEWS WHERE OWNER = 'APPS' AND VIEW_NAME = 'FND_RESP_SEC_ROLES_VL';

Because the documented source is DUAL with a false predicate, any application logic requiring actual responsibility-role assignments should be redirected to the underlying FND security tables rather than relying on this view to return data in 12.1.1 or 12.2.2.