Search Results hz_dss_groups

Overview

APPS.HZ_DSS_GRANTS_V is a supplementary database view owned by the APPS schema and registered under FND Design Data as AR.HZ_DSS_GRANTS_V. It is classified in the Oracle E-Business Suite data dictionary as a "supplementary view used to simplify forms coding." Within Oracle EBS 12.1.1 and 12.2.2, this view exposes the grant records that govern the Data Security System (DSS) applied to the Trading Community Architecture (TCA) and Receivables party model, particularly through the HZ_DSS_GRANTS_PUB public package.

The view presents one row per security grant, describing which grantee (a user, role, group, or menu-defined entity) holds which privileges over a given DSS group. Oracle explicitly warns that the view is not intended as a public query or update interface: "Oracle does not recommend you query or alter data using this view. It may change dramatically in subsequent minor or major releases." The view's status is VALID, and it exists primarily as a convenience layer for Oracle Forms-based setup screens and for internal DSS resolution logic.

The user search term dss_grantee_key corresponds directly to a column exposed by this view (DSS_GRANTEE_KEY, VARCHAR2(240)), making it the principal identifier returned when diagnosing why a particular user or group can or cannot see secured TCA data.

Underlying Base Objects

HZ_DSS_GRANTS_V is defined over three base objects, all accessed through APPS synonyms:

• FND_GRANTS — the core grant table storing grantee identity, grant type, and the object/group granted.
• FND_MENUS — the menu definition table, used to resolve menu-based DSS grants.
• FND_OBJECTS — the object registry that maps grant targets to their underlying application entities.

The view joins these objects to produce a single, forms-friendly row set for DSS grant administration. Because the view is a naming abstraction rather than a stored structure, it inherits the commit and caching behavior of FND_GRANTS; changes to grants are persisted in the base table and reflected immediately on subsequent queries. The companion API APPS.HZ_DSS_GRANTS_PUB references this view and is the supported programmatic entry point for manipulating DSS grants.

Key Columns

• DSS_GROUP_CODE (VARCHAR2(30)) — identifies the DSS security group to which the grant applies. This is the grouping dimension against which secured TCA records are filtered.
• DSS_GRANTEE_TYPE — the category of the party receiving the grant (for example, user, group, or menu).
• DSS_GRANTEE_KEY (VARCHAR2(240)) — the unique identifier of the grantee. This is the column matching the user's search term and is the principal value used when diagnosing grantee-level access.
• VIEW_FLAG, INSERT_FLAG, UPDATE_FLAG, DELETE_FLAG (CHAR) — four privilege indicators that specify which operations the grantee may perform on records within the granted DSS group.

Common Use Cases and Queries

Typical uses include auditing which grantees hold grants in a DSS group, confirming that a given user has the required privileges, and troubleshooting access failures reported by TCA/R receivables users. A basic query listing all grants is:

• SELECT DSS_GROUP_CODE, DSS_GRANTEE_TYPE, DSS_GRANTEE_KEY, VIEW_FLAG, INSERT_FLAG, UPDATE_FLAG, DELETE_FLAG FROM APPS.HZ_DSS_GRANTS_V;
• To trace a specific grantee: SELECT * FROM APPS.HZ_DSS_GRANTS_V WHERE DSS_GRANTEE_KEY = :grantee;
• To list all grantees with update privilege in a group: SELECT DSS_GRANTEE_KEY FROM APPS.HZ_DSS_GRANTS_V WHERE DSS_GROUP_CODE = :group AND UPDATE_FLAG = 'Y';

Because Oracle discourages direct DML and warns of possible structural change across releases, production integrations should use HZ_DSS_GRANTS_PUB or FND_GRANTS-based APIs rather than issuing modifications against this view. For read-only diagnostics and reporting, it remains a convenient and stable-at-runtime access path in both 12.1.1 and 12.2.2.