Results for “pqh_info_type_security_rit_v”

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

Overview

The view PQH_INFO_TYPE_SECURITY_RIT_V is an Oracle E-Business Suite database object owned by the APPS schema and delivered as part of the PQH (Public Sector HR) product family. It is classified as a VIEW with a status of VALID, and its object name indicates that it exposes information-type security for role-based information types (the _RIT_ token referencing PQH_ROLE_INFO_TYPES). The view functions as a reporting and integration surface that joins information-type security assignments to the role information type definitions they govern. Because it is a view rather than a table, it carries no independent storage and is materialized at query time from its underlying base objects. For users searching on per_info_type_security, this view is the natural access point for retrieving security context that links a responsibility and application to the specific information types it is permitted to see, restricted to the PQH role information type taxonomy.

Underlying Base Objects

The view is defined over two documented synonyms: PER_INFO_TYPE_SECURITY and PQH_ROLE_INFO_TYPES. The view text joins these on two conditions: the security table is filtered where INFO_TYPE_TABLE_NAME = 'PQH_ROLE_INFO_TYPES', and the join matches INFORMATION_TYPE between the two sources. This construction restricts the result set to only those information type security records whose target table is the PQH role information types table, effectively scoping the view to the Public Sector HR role information type domain. The security side supplies the application and responsibility identifiers, while the role information type side supplies descriptive and legislative attributes. Both base objects are exposed as synonyms, meaning the view is intended to be consumed through the standard APPS synonym layer rather than by direct owner-qualified reference.

Key Columns

The view exposes seventeen columns. The first two, APPLICATION_ID and RESPONSIBILITY_ID, originate from PER_INFO_TYPE_SECURITY and identify the application and responsibility to which the security entry applies. INFORMATION_TYPE is the join key present in both sources. The remaining columns derive from PQH_ROLE_INFO_TYPES: ACTIVE_INACTIVE_FLAG and MULTIPLE_OCCURENCES_FLAG denote whether the type is active and whether multiple occurrences are permitted; DESCRIPTION provides the human-readable name; and LEGISLATION_CODE identifies the legislation context. The audit and concurrency columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE — support traceability and concurrent-program diagnostics.

Common Use Cases and Queries

Typical uses include auditing which responsibilities are granted access to which role information types, validating security configuration before or after upgrades, and driving integration extracts that synchronize security metadata. A representative query filters by responsibility:

• SELECT responsibility_id, information_type, active_inactive_flag, description FROM apps.pqh_info_type_security_rit_v WHERE responsibility_id = :resp_id;
• SELECT application_id, responsibility_id, information_type FROM apps.pqh_info_type_security_rit_v WHERE legislation_code = :leg_code AND active_inactive_flag = 'Y';
• SELECT INFORMATION_TYPE, DESCRIPTION, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM apps.pqh_info_type_security_rit_v ORDER BY INFORMATION_TYPE;

Because the view already applies the INFO_TYPE_TABLE_NAME restriction and the join, consumers do not need to replicate this logic. Queries should generally constrain on RESPONSIBILITY_ID or LEGISLATION_CODE to limit result volume, since the view spans all qualifying security rows across applications and responsibilities.