Search Results cz_imp_end_user




Overview
Explore in AI Chat

Overview

CZ_IMP_END_USER is a staging table within the Oracle E-Business Suite Configurator (CZ) module. Its documented purpose is to hold data destined for import into, or rejected from, the CZ_END_USERS table. It therefore functions as an intermediate landing area between an external source system and the canonical end-user master within Configurator. The table is owned by the CZ schema and carries a VALID status across EBS 12.1.1 and 12.2.2. The documented physical schema for 12.2.2 comprises 50 columns.

The heuristic Data Vault classification derived from the foreign-key structure is standalone. In modeling terms, this suggests CZ_IMP_END_USER should be treated as an independent staging entity rather than a true hub, link, or satellite. Its single documented foreign key points outward to CZ_END_USERS, indicating that records are validated or reconciled against the target master before acceptance. Rows may persist here with a rejection status when import validation fails, making the table a useful audit surface for import troubleshooting.

Key Information Stored

The surrogate primary key is END_USER_ID, which also serves as the foreign key to CZ_END_USERS, tying each staging row to its intended target record. The business context of an end user is captured through identity and contact attributes: NAME, FIRSTNAME, LASTNAME, MI, TITLE, LOGIN_NAME, END_USER_ORG_ID, and ORIG_SYS_REF, the latter identifying the originating source system. Contact details include ADDR_LINE1, ADDR_LINE2, CITY, STATE, PROVINCE, COUNTY, ZIP, COUNTRY, PHONE, FAX, PAGER, CELLULAR, and EMAIL_ADDR. Commercial and descriptive attributes are held in ALLOWABLE_DISCOUNT and DESC_TEXT.

Import control is governed by REC_NBR, RUN_ID, REC_STATUS, DISPOSITION, and DELETED_FLAG, which together allow a specific import batch and the outcome of each record to be identified. Effective-dating columns EFF_FROM, EFF_TO, and EFF_MASK support temporal validity, while CHECKOUT_USER, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY provide standard audit and concurrency tracking. Extensibility is provided by USER_STR01 through USER_STR04 and USER_NUM01 through USER_NUM04. The FSK_ENDUSER_1_1, FSK_ENDUSER_1_EXT, FSK_USERGROUP_2_1, and FSK_USERGROUP_2_EXT columns represent foreign surrogate keys linking to end-user and user-group definitions, and SECURITY_MASK supports access restriction.

Common Use Cases and Queries

The primary operational scenario is monitoring an import run and identifying rejected records. A typical query filters by batch and status:

  • SELECT rec_nbr, end_user_id, name, login_name, rec_status, disposition FROM cz.cz_imp_end_user WHERE run_id = :run_id AND rec_status = 'REJECTED';
  • Comparing staged data against the target master: SELECT i.end_user_id, i.name, e.name FROM cz.cz_imp_end_user i, cz.cz_end_users e WHERE i.end_user_id = e.end_user_id AND i.name <> e.name;
  • Audit reporting on who imported or changed a staging row, using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.
  • Reviewing batch volumes and dispositions grouped by RUN_ID to assess import throughput and error rates.
  • Extracting custom attributes from USER_STR01–04 and USER_NUM01–04 for downstream reporting where standard fields are insufficient.

Related Objects

The most significant related object is CZ_END_USERS, the documented FK target joined on END_USER_ID, which is the authoritative end-user master. The FSK_ENDUSER_1_1 and FSK_ENDUSER_1_EXT columns imply relationships to end-user definition entities, while FSK_USERGROUP_2_1 and FSK_USERGROUP_2_EXT imply relationships to user-group entities within Configurator. Import processing is generally driven through the Configurator import concurrent programs and accompanying validation logic rather than direct DML against this table. Reporting and reconciliation typically join CZ_IMP_END_USER to CZ_END_USERS and to the associated user-group and organization definitions referenced by END_USER_ORG_ID.