Results for “hz_citizenship”

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

Overview

HZ_CITIZENSHIP is a table owned by the AR (Receivables) schema within the Oracle E-Business Suite Trading Community Model architecture. It stores a person's claimed nationality — that is, the citizenship or nationality declared for a specific party record. In the EBS Trading Community Model, this table sits beneath the party layer (HZ_PARTIES) and captures a specific attribute of a person's identity profile. The table holds 23 documented columns in release 12.2.2 and is classified as VALID in the ETRM registry.

In Data Vault modeling terms, the ETRM metadata offers a heuristic classification of link. This reflects the table's role as an associative structure connecting a party (via PARTY_ID) to a reference territory or country (via COUNTRY_CODE). Rather than functioning as a standalone hub or a pure descriptive satellite, HZ_CITIZENSHIP resolves the relationship between persons and nationalities, with its own attribute set layered on top.

Key Information Stored

The table's surrogate primary key is CITIZENSHIP_ID, enforced via the constraint HZ_CITIZENSHIP_PK and mirrored by the unique index HZ_CITIZENSHIP_U1. This is the business-key candidate documented in the metadata. Beyond the surrogate key, the most significant columns are:

• PARTY_ID — Foreign key to HZ_PARTIES, identifying the person whose nationality is recorded.
• COUNTRY_CODE — Foreign key to FND_TERRITORIES, holding the territory representing the claimed citizenship.
• BIRTH_OR_SELECTED — Indicates whether the citizenship is a birth nationality or a selected/acquired one.
• DATE_RECOGNIZED and DATE_DISOWNED — Mark when the citizenship was recognized and, where applicable, when it was renounced or ended.
• DOCUMENT_TYPE and DOCUMENT_REFERENCE — Capture supporting documentation such as passport or naturalization details.
• STATUS — Tracks the record's active/inactive state.
• START_DATE/END_DATE equivalents via END_DATE — effective-dating for the citizenship claim.
• Standard EBS audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.
• Concurrent program columns: REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, APPLICATION_ID, CREATED_BY_MODULE, and WH_UPDATE_DATE.

Common Use Cases and Queries

Typical reporting retrieves all citizenships for a given party, often joined to territory names for display. A representative query:

SELECT c.citizenship_id, c.country_code, t.territory_short_name, c.birth_or_selected, c.status FROM hz_citizenship c, fnd_territories_tl t WHERE c.party_id = :p_party_id AND c.country_code = t.territory_code AND t.language = USERENV('LANG');

Common scenarios include customer master data quality audits (identifying parties with missing or duplicate citizenship records), compliance and KYC reporting where nationality is a required attribute, and integration extracts feeding downstream systems. Because the table carries WH_UPDATE_DATE, it also participates in warehouse incremental extraction patterns.

Related Objects

• HZ_PARTIES — Parent party entity; joined on HZ_CITIZENSHIP.PARTY_ID = HZ_PARTIES.PARTY_ID.
• FND_TERRITORIES — Territory reference; joined on HZ_CITIZENSHIP.COUNTRY_CODE = FND_TERRITORIES.TERRITORY_CODE.
• The party-level TCA APIs, such as HZ_PARTY_V2PUB, which insert and maintain citizenship rows as part of person party creation and update.
• HZ_PERSON_PROFILES — Person-specific extension referencing the same party, useful for consolidated person reporting.
• HZ_ORG_CONTACTS and HZ_CONTACT_POINTS — Sister tables under the party model, frequently queried alongside citizenship for full party profiles.

These relationships make HZ_CITIZENSHIP a compact but important link table within the TCA party model, tying individuals to their declared nationalities.