Results for “owner_table_id1”

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

Overview

HZ_DSS_ASSIGNMENTS is an Oracle E-Business Suite table owned by the AR (Receivables) schema. It is documented as valid in ETRM for releases 12.1.1 and 12.2.2 and is described as the storage for Data Sharing Group assignments. In practical terms, the table records which business entities are assigned to a particular Data Sharing Group, thereby governing how records are shared across operating units, legal entities, or other organizational boundaries configured within the Trading Community Architecture (TCA) and Receivables security model.

Under the heuristic Data Vault classification derived from its foreign key structure, HZ_DSS_ASSIGNMENTS is modeled as satellite-leaning. This indicates that it primarily functions as a descriptive, subsidiary structure that captures attributes and state around a business key rather than acting as a pure hub or link. It carries a foreign key reference to the group definition table, reinforcing its role as the assignment detail attached to a parent group entity.

Key Information Stored

The table contains fifteen documented columns and is uniquely identified by the primary key constraint HZ_DSS_ASSIGNMENTS_PK, defined on the ASSIGNMENT_ID column. The unique index HZ_DSS_ASSIGNMENTS_U1 also covers ASSIGNMENT_ID, marking it as the sole documented business-key candidate and confirming it as the surrogate identifier for each assignment record.

• ASSIGNMENT_ID — surrogate primary key and unique business-key candidate; uniquely identifies each assignment row.
• DSS_GROUP_CODE — foreign key referencing HZ_DSS_GROUPS_B; identifies the Data Sharing Group to which the assignment belongs.
• STATUS — indicates the active or inactive state of the assignment.
• OWNER_TABLE_NAME — the name of the source/owner entity table whose records are being assigned.
• OWNER_TABLE_ID1 through OWNER_TABLE_ID5 — identifier columns holding the key values of the assigned owner entity, spread across up to five positions to accommodate composite keys from heterogeneous source tables.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns capturing who created and last modified the row and when.

Common Use Cases and Queries

Typical scenarios include auditing which owner entities are assigned to a given Data Sharing Group, validating the integrity of sharing configurations after cloning or migration, and reporting on active versus inactive assignments. A representative query joins the assignment to its parent group:

• SELECT a.assignment_id, a.dss_group_code, a.status, a.owner_table_name, a.owner_table_id1
  FROM hz_dss_assignments a
  WHERE a.dss_group_code = :group_code AND a.status = 'A';
• SELECT g.group_code, g.group_name, a.owner_table_name, a.owner_table_id1
  FROM hz_dss_assignments a, hz_dss_groups_b g
  WHERE a.dss_group_code = g.dss_group_code;

Reporting use cases commonly filter by OWNER_TABLE_NAME to isolate assignments for a specific entity type, and by STATUS to identify stale or orphaned assignments. Because the table references owner identifiers in up to five columns, reconciliation queries should resolve the correct ID column according to the source entity being examined.

Related Objects

• HZ_DSS_GROUPS_B — the parent Data Sharing Group definition table, joined via DSS_GROUP_CODE. This is the documented foreign key relationship.
• HZ_DSS_GROUPS_TL — translation table supplying the group name and description for reporting joins on the group code.
• HZ_DSS_ASSIGNMENTS_PK — primary key constraint; HZ_DSS_ASSIGNMENTS_U1 — unique index on ASSIGNMENT_ID.
• HZ_PARTIES and related TCA tables — typical owner entities whose records may be assigned to a sharing group and referenced via the OWNER_TABLE_* columns.
• AR / TCA security and Data Sharing Group setup components — configuration and API layers that consume these assignments when enforcing record visibility across organizational boundaries.