Search Results krs_customer_end_user

Overview

APPS.CZ_IMP_AC_KRS is an Oracle E-Business Suite PL/SQL import package belonging to the Customer Relationship Management (CRM) family of CZ modules, used broadly by the Oracle CRM foundation and Trade Management style schemas that leverage the CZ_ table prefix. Its declared purpose is to process inbound interface records and load them into the customer, contact, address, and end-user base tables maintained by the CZ data model. The package name incorporates the "KRS" suffix, which in these deployments identifies the specific source system or transfer group whose data is being imported; the inXFR_GROUP parameter carried by every procedure indicates that the package is transfer-group aware and can be invoked repeatedly for different inbound batches within the same run.

The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema rather than the definer. In Oracle EBS 12.1.1 and 12.2.2 this is a deliberate design choice that allows the package to be called from concurrent program definitions, from the CZ import forms, and from custom API code without requiring the APPS schema to hold elevated definer rights. The header revision string shows the source was last shipped at version 115.13, dated 2002/12/03, which places the package in the long-lived CZ import framework that predates the R12 online-patching model but is still present in the 12.2.2 file system.

Key Procedures and Functions

The package exposes eight documented procedures, all sharing a common interface signature of a run identifier, a commit size, a maximum error threshold, four OUT counters (inserts, updates, failed, duplicates), and a transfer group. The procedures are:

• KRS_CONTACT — imports contact records, loading them into the contact interface and base tables.
• KRS_CUSTOMER — imports customer header records.
• KRS_ADDRESS — imports party or customer address records.
• KRS_ADDRESS_USES — imports address-use assignments that bind addresses to locations or purposes.
• KRS_CUSTOMER_END_USER — imports the association between a customer and an end user.
• KRS_END_USER — imports end-user records.
• KRS_END_USER_GROUP — imports end-user group definitions.
• KRS_USER_GROUP — imports the mapping of users into end-user groups.

Each procedure follows the standard CZ import pattern: read staged rows from the CZ_IMP_* interface tables, validate them against the base tables, insert or update the corresponding CZ_S records, and return row-level counts. The MAX_ERR parameter permits the import to abort once a defined error threshold is reached, while COMMIT_SIZE controls the size of intermediate commits to balance throughput against rollback segment usage. The OUT counters allow the calling concurrent program to log run statistics without re-querying the interface tables.

Tables Accessed

The procedures read from the CZ_IMP_ADDRESS and CZ_IMP_ADDRESS_USE staging tables and write to the base and translation tables CZ_ADDRESSES, CZ_ADDRESSES_S, CZ_ADDRESS_USES, CZ_ADDRESS_USES_S, CZ_CONTACTS, CZ_CONTACTS_S, CZ_CUSTOMERS, CZ_CUSTOMERS_S, CZ_CUSTOMER_END_USERS, CZ_END_USERS, CZ_END_USERS_S, and CZ_END_USER_GROUPS. CZ_DB_SETTINGS is consulted for control and configuration parameters such as the active transfer group and validation switches. All references are made through APPS synonyms, so the package is installed in and resolved against the APPS schema in a standard EBS environment.

Usage Notes

CZ_IMP_AC_KRS is typically invoked by a concurrent program (or a custom wrapper program) that first loads the inbound flat file or feeder table into the CZ_IMP_* staging tables, then calls the appropriate KRS_* procedure once per entity type. It is not called interactively from a form, though a form can submit the concurrent request. Because the package is referenced by one other package in the CZ import chain, the usual orchestration is a parent import driver that sequences KRS_CUSTOMER, KRS_ADDRESS, KRS_ADDRESS_USES, KRS_CONTACT, KRS_END_USER, KRS_END_USER_GROUP, KRS_USER_GROUP, and KRS_CUSTOMER_END_USER in dependency order so that foreign-key relationships are satisfied as rows are loaded. When troubleshooting, the user-supplied search value "396361 krs" most commonly corresponds to a concurrent request ID or run identifier passed into inRUN_ID; the OUT failure and duplicate counters, together with the CZ_IMP_* rows left unprocessed, are the first diagnostic points to inspect.