Search Results hr_de_link_type_mappings

Overview

APPS.HR_DE_ORG_LINK_TYPES_MAPPING is a reporting view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that exposes the configuration of Organization Hierarchy link type mappings used by Oracle HRMS. In HRMS, the mapping between an organization link type (for example, a parent-child reporting relationship) and the organization classification it is permitted to connect is not held in a conventional developer extension table. Instead, it is stored within Oracle Payroll's flexible "user table" framework, which is a generic key-flexfield-style storage model built on the PAY_USER_* tables. This view de-normalizes those flexible rows into a simple, query-friendly two-column projection: the organization link type name and its associated organization classification. It is owned by the APPS schema and is intended for read-only consumption, making it suitable for reporting, data extraction, and validation of HR organization structure configuration.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms: PAY_USER_TABLES, PAY_USER_ROWS_F, PAY_USER_COLUMNS, and PAY_USER_COLUMN_INSTANCES_F. PAY_USER_TABLES identifies the specific user-defined table by name; the view filters this to USER_TABLE_NAME = 'HR_DE_LINK_TYPE_MAPPINGS'. PAY_USER_ROWS_F stores the individual mapping rows (records) belonging to that table. PAY_USER_COLUMNS defines the attributes (columns) available on the user table; the view selects two of these rows, the one named 'ORG_LINK_TYPE' and the one named 'ORG_CLASS'. PAY_USER_COLUMN_INSTANCES_F holds the actual value stored for each column on each row, and it is joined twice — once per column — to resolve the two values that appear in the final output. The joins are driven by USER_TABLE_ID, USER_ROW_ID, and USER_COLUMN_ID, which are the standard key columns of the user table framework. Because the view queries the "_F" (date-effective) variants of the row and column instance tables and performs no effective-date filtering itself, callers should be aware that historical rows may be returned.

Key Columns

The view exposes only two unnamed output columns, both taken from the VALUE columns of the two PAY_USER_COLUMN_INSTANCES_F aliases:

• First column (UCI1.VALUE): the organization link type, sourced from the user column named ORG_LINK_TYPE.
• Second column (UCI2.VALUE): the organization classification, sourced from the user column named ORG_CLASS.

Internally, the view relies on the identifiers USER_TABLE_ID, USER_ROW_ID, and USER_COLUMN_ID to correlate columns to their instances. The specific column of interest in a search for user_column_id is USER_COLUMN_ID, which links PAY_USER_COLUMNS to PAY_USER_COLUMN_INSTANCES_F and uniquely identifies which attribute (ORG_LINK_TYPE or ORG_CLASS) a stored value belongs to.

Common Use Cases and Queries

Typical uses include auditing which organization classifications may be linked under a given link type, and joining the view to organization hierarchy definitions to validate configurations. A basic query is:

SELECT link_type_value, org_class_value
FROM   apps.hr_de_org_link_types_mapping;

To resolve the underlying user column identifiers, join through the framework tables:

SELECT uc.user_column_name, uc.user_column_id, uci.value
FROM   apps.pay_user_columns uc,
       apps.pay_user_column_instances_f uci
WHERE  uc.user_column_id = uci.user_column_id
AND    uc.user_table_id  = (SELECT user_table_id
                            FROM   apps.pay_user_tables
                            WHERE  user_table_name = 'HR_DE_LINK_TYPE_MAPPINGS');

Because the view has no effective-date predicate, supply an explicit date or join to the base instances with an effective date when current, point-in-time results are required.