Search Results cz_customers_s

Overview

APPS.CZ_IMP_AC_KRS is a standalone PL/SQL package body in the Oracle E-Business Suite APPS schema. It belongs to the Oracle E-Business Suite (EBS) Customer Relationship Management (CRM) module, specifically to the Customer Data Management (CDM) / Trading Community Architecture (TCA) profile customization layer. The naming convention (CZ_) maps the package to the CRM "Trading Community" profile. CZ_ is the schema prefix used by the EBS application for CDM-related tables and program units, and IMP_AC in the package name indicates an import program for "Addresses and Contacts" (AC). The KRS suffix denotes the specific customer for which this import functionality was customized; KRS is an implementation-specific extension point.

The package exists to import (upload) address, contact, customer, end-user, user-group, and address-use data from external, temporary staging tables into the base EBS CDM tables. It is therefore an implementation-specific loader, not a standard Oracle public API or UTL utility. Its purpose is to read rows from the CZ_IMP_* interface/staging tables and write them into the permanent CZ_* base tables, validating and deriving surrogate keys as needed. The package body is VALID, which confirms the compiled code exists and is executable in the APPS schema.

Key Procedures and Functions

The documented package exposes eight program units, each handling a distinct entity in the import pipeline:

• KRS_ADDRESS — Imports address records into the address base table. It is the primary loader for the address entity.
• KRS_ADDRESS_USES — Imports address-use rows into the address-use base table, associating addresses with their contextual uses. This is the unit relevant to the CZ_ADDRESS_USES_S table referenced by the user's search term.
• KRS_CONTACT — Imports contact records into the contact base table, linking contacts to their owning party or customer.
• KRS_CUSTOMER — Imports customer (organization/person account) records into the customer base table.
• KRS_CUSTOMER_END_USER — Imports the associations between customers and end users.
• KRS_END_USER — Imports end-user (individual consumer) records into the end-user base table.
• KRS_END_USER_GROUP — Imports end-user group records, defining group membership of end users.
• KRS_USER_GROUP — Imports user-group records into the user-group base table.

The metadata does not document the exact parameter lists, so those are intentionally omitted here. Functionally, each unit corresponds to one import entity, and each writes its staging table (CZ_IMP_*) into its corresponding base table (CZ_*).

Tables Accessed

The package reads and writes the following documented tables, accessed through APPS synonyms:

• Interface/staging tables: CZ_IMP_ADDRESS, CZ_IMP_ADDRESS_USE, plus other CZ_IMP_* siblings such as CZ_IMP_ALL, CZ_IMP_CONTACT, CZ_IMP_CUSTOMER, CZ_IMP_CUSTOMER_END_USER, CZ_IMP_END_USER, CZ_IMP_END_USER_GROUP, and CZ_IMP_USER_GROUP. These hold the raw, pre-validated uploaded data.
• Base tables: CZ_ADDRESSES and CZ_ADDRESSES_S (interface and translation for addresses); CZ_ADDRESS_USES and CZ_ADDRESS_USES_S (address-use records and their language/translation rows — the object the user searched for); CZ_CONTACTS and CZ_CONTACTS_S; CZ_CUSTOMERS and CZ_CUSTOMERS_S; CZ_CUSTOMER_END_USERS; CZ_END_USERS and CZ_END_USERS_S; CZ_END_USER_GROUPS; CZ_USER_GROUPS and CZ_USER_GROUPS_S.
• Supporting table: CZ_DB_SETTINGS, used to read installation/site configuration parameters that drive import behavior.
• Utility package: CZ_UTILS, providing shared helper routines for key generation and validation.

Note that the _S suffixed tables (e.g., CZ_ADDRESSES_S, CZ_ADDRESS_USES_S) are the translation/detail tables paired with the base tables; the import program must populate both to keep the model consistent.

Usage Notes

This package is not part of the Oracle standard public API surface; it is an Oracle-internal or partner/implementation-specific loader. It is not referenced by any database object according to the dependency metadata, meaning it is invoked directly rather than called from another stored program. Typical invocation paths are:

• A concurrent program registered in the CDM application, executing the load from staging to base tables.
• A custom form or OAF page that calls the procedures as part of an address/contact upload flow.
• Ad-hoc or scheduled SQL*Plus / custom code execution for data migration batches.

Because it is "not referenced by any database object," DBAs and developers should treat it as an entry-point program. It depends on CZ_IMP_ALL, which likely serves as the top-level orchestrator that calls the eight KRS_* procedures in the correct sequence (customer, address, address-use, contact, end users, groups). When the metadata documents only the package body title and dependency list, exact parameter passing cannot be confirmed without reading the compiled source; the source can be examined via USER_SOURCE, ALL_SOURCE, or the EBS "Show Dependent Code" facility referenced in the metadata. As with all CZ_ packages, changes must be regression-tested in a clone before production deployment, since the package writes directly to base CDM tables.