Results for “site_use_code”

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

Overview

The CZ_IMP_ADDRESS_USE table is an Oracle EBS Configurator (CZ) staging table that holds address-use data scheduled for import into, or rejected from, the permanent CZ_ADDRESS_USES table. It resides in the CZ schema and is classified as VALID in the ETRM 12.1.1 and 12.2.2 object inventories. Its documented purpose is to capture rows that are either pending validation before being promoted into CZ_ADDRESS_USES or retained as exceptions when the import process rejects them. This staging pattern is common in Configurator, where bulk loads from external or legacy sources must be validated against the model's referential integrity before commit.

From a Data Vault modeling perspective, the metadata's heuristic classification for this object is standalone. The table does not exhibit the multi-parent foreign-key structure typical of a link table, nor does it carry the descriptive, slowly-changing attributes of a pure satellite; it behaves more like a transient hub-aligned record whose primary purpose is identity resolution of an ADDRESS_USE_ID before the row is written to the target. Modeling suggestions of this nature should be treated as guidance only, since the object is a technical staging artifact rather than a subject-oriented entity.

Key Information Stored

The table contains ten documented columns. The surrogate primary key is ADDRESS_USE_ID, which also serves as a foreign key to the parent CZ_ADDRESS_USES table, making it the primary business-key candidate for reconciliation between staging and target rows. ADDRESS_ID identifies the address record associated with the use, and ORIG_SYS_REF preserves the original system reference for source traceability during migration.

• ADDRESS_USE_ID — surrogate identifier and FK to CZ_ADDRESS_USES; the join key for promotion or rejection tracking.
• ADDRESS_ID — the address to which the use applies.
• ORIG_SYS_REF — originating system reference, used for lineage and duplicate detection.
• SITE_USE_CODE — the site-use classification (for example, business or shipping) in the target model.
• WAREHOUSE_ID — warehouse associated with the address use, where applicable.
• DELETED_FLAG — soft-delete indicator carried through import.
• RUN_ID — identifies the import batch or concurrent program run that produced the row.
• REC_STATUS — processing status of the staging row (accepted, pending, rejected).
• DISPOSITION — outcome assigned after validation, distinguishing rows to be imported from those rejected.
• FSK_ADDRESS_1_1 — flexible/foreign surrogate key supporting the address relationship in the Configurator model.

Common Use Cases and Queries

Typical scenarios include auditing a specific import run, isolating rejected rows for correction, and reconciling staged counts against committed CZ_ADDRESS_USES records. A representative query filtering by run and disposition is:

SELECT address_use_id, address_id, site_use_code, rec_status, disposition
FROM cz.cz_imp_address_use
WHERE run_id = :run_id AND rec_status = 'REJECTED';

Reconciliation against the target uses the shared key: SELECT i.address_use_id FROM cz.cz_imp_address_use i WHERE NOT EXISTS (SELECT 1 FROM cz.cz_address_uses a WHERE a.address_use_id = i.address_use_id); This highlights staged rows that failed to promote. Reporting on source lineage leverages ORIG_SYS_REF, while batch monitoring aggregates on RUN_ID.

Related Objects

The dominant relationship is the foreign key from CZ_IMP_ADDRESS_USE.ADDRESS_USE_ID to CZ_ADDRESS_USES, which defines the promotion path and the primary reconciliation join. Related objects of significance include CZ_ADDRESS_USES (the target entity), the address master table referenced through ADDRESS_ID and FSK_ADDRESS_1_1, warehouse reference data joined via WAREHOUSE_ID, the site-use lookup supporting SITE_USE_CODE, and the Configurator concurrent program and import interface logic that populate RUN_ID, REC_STATUS, and DISPOSITION. Analysts should verify column-level mappings against the CZ_ADDRESS_USES definition before promoting staged rows, as the staging table's column set is a proper subset of the target's.