Results for “hz_dss_secured_rel_types_v”

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

Overview

The view APPS.HZ_DSS_SECURED_REL_TYPES_V is a secured reporting view within the Oracle E-Business Suite Receivables (AR) product family. It presents relationship type definitions that have been registered as secured items within the Data Security Subsystem (DSS) framework, combining row-level security metadata from the DSS criteria infrastructure with the underlying relationship type and lookup definitions. The view derives its name from its role as a "secured relationship types" enumeration, filtering the broader relationship type population to those configured as DSS-controlled objects.

In practice, this view is used to expose the set of relationship types that participate in data security policies, along with the human-readable role meaning associated with each. The ROLE_MEANING column, sourced from the AR_LOOKUPS lookup type HZ_RELATIONSHIP_ROLE, translates the internal role code into a user-facing description, which makes the view particularly useful for reporting and for resolving the "role_meaning" of a secured relationship type during integration or diagnostic work.

Underlying Base Objects

The view is defined over three documented base objects, joined in a single SELECT statement:

• HZ_DSS_CRITERIA (SYNONYM) — the DSS criteria table (aliased HDC). It supplies the secured item identifier, status, DSS group code, owner table name and owner table ID, plus standard WHO audit columns. The join restricts rows to those whose OWNER_TABLE_NAME equals 'HZ_RELATIONSHIP_TYPES' and matches the numeric relationship type identifier.
• HZ_RELATIONSHIP_TYPES (SYNONYM) — the seeded relationship type definitions (aliased HRT). It contributes the relationship type name, forward and backward relationship codes, and the role code.
• AR_LOOKUPS (VIEW) — the Receivables lookup view (aliased ARL). It is outer-joined on LOOKUP_TYPE = 'HZ_RELATIONSHIP_ROLE' and LOOKUP_CODE = HRT.ROLE to resolve the role meaning.

Because AR_LOOKUPS is outer-joined (note the (+) operator), a secured relationship type is still returned even when no matching role lookup exists, in which case ROLE_MEANING is null.

Key Columns

• SECURED_ITEM_ID, STATUS, DSS_GROUP_CODE — the DSS identity, activation status, and security group for the secured item.
• RELATIONSHIP_TYPE_ID — the numeric relationship type identifier, converted from OWNER_TABLE_ID1 via TO_NUMBER.
• RELATIONSHIP_TYPE, FORWARD_REL_CODE, BACKWARD_REL_CODE — the relationship type name and its directional codes.
• ROLE — the internal role code from the relationship type definition.
• ROLE_MEANING — the user-facing meaning of the role, resolved from the HZ_RELATIONSHIP_ROLE lookup; this is the column most commonly searched for as "role_meaning".
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit and concurrency columns.

Common Use Cases and Queries

Typical uses include reporting the roles attached to secured relationship types, validating that role lookups are populated, and troubleshooting DSS configuration. A simple lookup by role meaning might read:

• SELECT relationship_type, role, role_meaning FROM hz_dss_secured_rel_types_v WHERE role_meaning = :meaning;
• SELECT secured_item_id, status, dss_group_code, relationship_type, role_meaning FROM hz_dss_secured_rel_types_v WHERE status = 'A' ORDER BY relationship_type;
• SELECT relationship_type, role_meaning FROM hz_dss_secured_rel_types_v WHERE role_meaning IS NULL; — to identify roles lacking a lookup translation.

Because the view filters on OWNER_TABLE_NAME = 'HZ_RELATIONSHIP_TYPES', results are limited to relationship types registered as DSS-secured items, which keeps the output focused on security-relevant role definitions.