Search Results cont_orig_system
Overview
The APPS.HZ_IMP_LOAD_CONTACT_ROLE_PKG package is a PL/SQL interface loader within the Oracle E-Business Suite Trading Community Architecture (TCA) and Receivables (AR) module family. Its primary business function is to move contact role assignment data from the open interface staging tables into the base TCA contact role tables. The package is the engine invoked by the Contact Roles Import process to validate staged rows in the interface table and to propagate valid records into HZ_ORG_CONTACT_ROLES, thereby creating or updating role relationships between organizational contacts and their associated roles within the customer or party model.
The package is part of the broader HZ_IMP_* family of import loaders that support bulk data migration, initial implementation seeding, and ongoing integration of external systems into EBS. The header comment (ARHLOCRS.pls, version 120.6) confirms a long-standing, patched implementation shipping as a Noship-owned TCA artifact.
Key Procedures and Functions
The ETRM metadata documents a single public procedure: LOAD_CONTACTROLES. This procedure is the entry point for the contact-role import batch.
LOAD_CONTACTROLES— Orchestrates the loading of contact role records from the interface table. It accepts a DML record parameter (the signature begins withP_DML_RECORD IN), which carries the batch context and commit/rollback semantics for the invocation. The procedure validates staged rows, resolves references to contacts and organizations, and performs the insert or update intoHZ_ORG_CONTACT_ROLESaccording to theINSERT_UPDATE_FLAGsupplied on each interface row. Invalid rows are flagged and routed to error recording rather than aborted, which is characteristic of TCA interface loaders.
While the public API surface is limited to this one procedure, the package declares an extensive set of PL/SQL collection types used internally to bulk-fetch, validate, and process interface rows. These include associative-array types mapped to interface columns such as BATCH_ID, CONT_ORIG_SYSTEM, CONTACT_ORIG_SYSTEM_REFERENCE, INSERT_UPDATE_FLAG, ROLE_TYPE, INTERFACE_STATUS, ACTION_FLAG, ERROR_ID, ORG_CONTACT_ID, and ORG_CONTACT_ROLE_ID, along with generic column wrappers (TYPE_COLUMN, IND_COLUMN, YEAR_COLUMN, NUMBER_COLUMN, FLAG_COLUMN, DATE_COLUMN). A RefCurType REF CURSOR is declared for result-set handling. Sentinel constants G_MISS_NUM (-9999), G_MISS_CHAR ('!'), and G_MISS_DATE (01/01/4000) provide the standard TCA "missing value" semantics used to distinguish null from unspecified. Error collection types (error_ids, LOOKUP_ERROR, FLAG_ERROR) and message metadata types (ERROR_MESSAGE_NAME, ERROR_MESSAGE_TOKEN) support structured error reporting.
Tables Accessed
Through APPS synonyms, the package reads and writes the following documented tables:
HZ_IMP_CONTACTROLES_INT— The contact roles open interface table. This is the primary source table; the loader reads staged rows, batch identifiers, action flags, and status here.HZ_IMP_CONTACTROLES_SG— The interface staging table used during pre-processing, from whichACTION_FLAGis sourced before records reach the loader.HZ_ORG_CONTACT_ROLES— The base TCA table holding the actual organization contact role assignments. This is the target of the insert/update operations performed byLOAD_CONTACTROLES.HZ_IMP_ERRORSandHZ_IMP_ERRORS_S— Interface error tables (and their sequence) where validation failures are logged withERROR_ID, message name, and token values.HZ_IMP_TMP_ERRORS— A temporary error collection table used during batch processing and later consolidated into the main error table.
Usage Notes
This package is not intended for direct ad hoc invocation. It is typically executed as part of the contact roles import cycle, driven either by a concurrent program (the Contact Roles Import process under the Trading Community Architecture responsibility) or by a loading API that passes a DML record describing the batch. One other package in the EBS documentation set references HZ_IMP_LOAD_CONTACT_ROLE_PKG, reflecting a layered call chain in which a controller or importer package invokes this loader.
Because the procedure participates in a larger transaction, callers control commit behavior through the DML record rather than relying on the loader to commit internally. Customizations that need to seed or migrate contact role data should populate HZ_IMP_CONTACTROLES_INT (and, where relevant, HZ_IMP_CONTACTROLES_SG) and then invoke the standard import path rather than calling LOAD_CONTACTROLES directly. This preserves validation, error logging to HZ_IMP_ERRORS, and correct integration with TCA contact role consolidation logic.
-
PACKAGE: APPS.HZ_IMP_LOAD_CONTACT_ROLE_PKG
12.2.2
-
PACKAGE: APPS.HZ_IMP_LOAD_CONTACT_ROLE_PKG
12.1.1
-
PACKAGE BODY: APPS.HZ_IMP_LOAD_CONTACT_ROLE_PKG
12.1.1
-
PACKAGE BODY: APPS.HZ_IMP_LOAD_CONTACT_ROLE_PKG
12.2.2
-
APPS.HZ_IMP_LOAD_CONTACT_ROLE_PKG dependencies on HZ_IMP_CONTACTROLES_INT
12.2.2
-
APPS.HZ_IMP_LOAD_CONTACT_ROLE_PKG dependencies on HZ_IMP_CONTACTROLES_INT
12.1.1
-
APPS.HZ_IMP_LOAD_SSM_MATCHING_PKG dependencies on HZ_ORG_CONTACTS_S
12.1.1
-
APPS.HZ_IMP_LOAD_SSM_MATCHING_PKG dependencies on HZ_ORG_CONTACTS_S
12.2.2
-
APPS.HZ_IMP_LOAD_SSM_MATCHING_PKG SQL Statements
12.1.1
-
APPS.HZ_IMP_LOAD_SSM_MATCHING_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.HZ_IMP_LOAD_SSM_MATCHING_PKG
12.1.1
-
PACKAGE BODY: APPS.HZ_IMP_LOAD_SSM_MATCHING_PKG
12.2.2