Search Results hz_dss_assignments




Overview
Explore in AI Chat

Overview

The HZ_DSS_ASSIGNMENTS table is a core data object within the Oracle E-Business Suite Receivables (AR) module, specifically in versions 12.1.1 and 12.2.2. It serves as the repository for Data Sharing Group (DSS) assignments. In the context of Oracle EBS, Data Sharing Groups are a critical security and data partitioning mechanism used to control user access to trading community data, such as customers and related entities. This table functions as the junction table that maps specific entities (like parties or customer accounts) to defined Data Sharing Groups, thereby enforcing data visibility and operational security rules across the application.

Key Information Stored

The table's primary purpose is to store assignment records linking an entity to a Data Sharing Group. While the full column list is not detailed in the provided metadata, the documented relationships and keys reveal its essential structure. The primary key column, ASSIGNMENT_ID, uniquely identifies each assignment record. The foreign key column, DSS_GROUP_CODE, is pivotal, storing the code that references a specific group defined in the HZ_DSS_GROUPS_B table. Other typical columns, inferred from standard TCA (Trading Community Architecture) and DSS patterns, would likely include identifiers for the assigned object (such as PARTY_ID or CUST_ACCOUNT_ID), the object type, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) for auditing.

Common Use Cases and Queries

The primary use case revolves around security administration and data access reporting. Administrators use this data to audit which entities are visible to which groups of users. A common query involves listing all assignments for a specific Data Sharing Group to understand its data scope. For instance, to find all assignments for a group code 'US_OPERATIONS', one might use:

  • SELECT assignment_id, object_id, object_type FROM ar.hz_dss_assignments WHERE dss_group_code = 'US_OPERATIONS';

Conversely, to identify which groups have access to a specific customer account (e.g., CUST_ACCOUNT_ID=1000), a join is necessary:

  • SELECT a.dss_group_code, g.name FROM ar.hz_dss_assignments a, hz_dss_groups_b g WHERE a.dss_group_code = g.dss_group_code AND a.object_id = 1000 AND a.object_type = 'CUST_ACCOUNT';

These queries are foundational for troubleshooting data visibility issues and ensuring compliance with data access policies.

Related Objects

The HZ_DSS_ASSIGNMENTS table has a direct and critical dependency on the HZ_DSS_GROUPS_B table, which holds the definition of the Data Sharing Groups themselves. The documented foreign key relationship is:

  • HZ_DSS_GROUPS_B: This table is referenced via the column HZ_DSS_ASSIGNMENTS.DSS_GROUP_CODE. The DSS_GROUP_CODE in HZ_DSS_ASSIGNMENTS must exist as a valid group code in HZ_DSS_GROUPS_B. This relationship ensures referential integrity, meaning an assignment cannot be made to a non-existent group.

While not explicitly listed in the provided metadata, this table is also central to the Data Sharing Group security model and is inherently related to the core TCA entity tables (HZ_PARTIES, HZ_CUST_ACCOUNTS) through the object_id and object_type columns, forming the complete security assignment framework.