Results for “owner_table_key_1”

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

Overview

HZ_CODE_ASSIGNMENTS is an intersection (link) table owned by the AR schema within the Oracle E-Business Suite Receivables product family, documented as VALID in both 12.1.1 and 12.2.2 environments. Its stated purpose is to link industrial classification codes — such as NAICS, SIC, or user-defined classification schemes — to parties or related entities. In TCA (Trading Community Architecture) terms, this table acts as the cross-reference carrier that associates a standardized classification code to a party record through the HZ_PARTIES hub.

Under the heuristic Data Vault classification derived from the foreign-key topology, HZ_CODE_ASSIGNMENTS is modeled as a link table. The metadata flags a 30-column physical structure with a surrogate primary key and two unique indexes, one of which is a composite business key spanning the owner table identity, category, class code, and start-date-activation combination.

Key Information Stored

The surrogate primary key is CODE_ASSIGNMENT_ID, enforced by the HZ_CODE_ASSIGNMENTS_PK constraint and the HZ_CODE_ASSIGNMENTS_U1 unique index. The principal business-key candidate is the composite unique index HZ_CODE_ASSIGNMENTS_U2, formed by OWNER_TABLE_ID, OWNER_TABLE_KEY_1 through OWNER_TABLE_KEY_5, OWNER_TABLE_NAME, ACTUAL_CONTENT_SOURCE, CLASS_CATEGORY, CLASS_CODE, and START_DATE_ACTIVE. The most operationally significant columns include:

• CODE_ASSIGNMENT_ID — surrogate primary key identifying each assignment row.
• OWNER_TABLE_ID — foreign key to HZ_PARTIES; identifies the party to which the code is assigned.
• OWNER_TABLE_NAME — the source entity type, typically HZ_PARTIES for party-linked rows.
• CLASS_CATEGORY — foreign key to HZ_CLASS_CATEGORIES, naming the classification scheme.
• CLASS_CODE — the actual classification value (e.g., a NAICS or SIC code) within the category.
• PRIMARY_FLAG — identifies the primary code assignment when multiple exist for one party.
• CONTENT_SOURCE_TYPE and ACTUAL_CONTENT_SOURCE — distinguish how the content was sourced or derived.
• IMPORTANCE_RANKING and RANK — ordering attributes where multiple classifications apply.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective-dating window controlling code validity.
• STATUS — record state flag supporting soft-delete semantics.
• OWNER_TABLE_KEY_1 through OWNER_TABLE_KEY_5 — generic key columns allowing the assignment to target non-party owner tables.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent-program lineage for the creating process.

Common Use Cases and Queries

Typical scenarios include customer classification reporting, segmentation analytics, and validation of primary industry codes during data conversion or cleansing exercises. The most frequent access pattern joins assignments back to parties and categories:

• Resolving a party's classification: SELECT a.class_category, a.class_code, a.primary_flag FROM hz_code_assignments a WHERE a.owner_table_id = :party_id;
• Current-and-effective filter: add AND SYSDATE BETWEEN a.start_date_active AND NVL(a.end_date_active, SYSDATE) to exclude expired assignments.
• Category drill-down joins: JOIN hz_class_categories c ON a.class_category = c.class_category to retrieve category names.
• Primary-code extraction: filter on PRIMARY_FLAG = 'Y' when only one code per party is required.
• Program lineage audits: group by REQUEST_ID and PROGRAM_ID to trace which concurrent program inserted classifications.

Because the table is effective-dated, historical reporting must respect START_DATE_ACTIVE and END_DATE_ACTIVE rather than assuming one row per party and category.

Related Objects

• HZ_PARTIES — parent hub for party-owner assignments; joined via OWNER_TABLE_ID.
• HZ_CLASS_CATEGORIES — defines the classification scheme referenced by CLASS_CATEGORY.
• HZ_IMP_CLASSIFICS_SG — staging table referencing CODE_ASSIGNMENT_ID for bulk imports of classifications.
• HZ_PARTY_SITES and related TCA party objects — commonly report alongside assignments for full party profiling.
• Public TCA APIs (e.g., HZ_PARTY_V2PUB) that write classification assignments during party creation and update.

The table participates in standard TCA data model integrity: deleting or merging parties requires appropriate handling of dependent assignment rows to avoid orphaned classifications.