Search Results hz_imp_load_relationships_pkg




Overview
Explore in AI Chat

Overview

APPS.HZ_IMP_LOAD_RELATIONSHIPS_PKG is a PL/SQL package that belongs to the Oracle E-Business Suite Trading Community Architecture (TCA) import framework. Its primary business function is to load party relationship records from the interface table HZ_IMP_RELSHIPS_INT into the base TCA tables, principally HZ_RELATIONSHIPS and HZ_PARTIES. In the context of Oracle EBS 12.1.1 and 12.2.2, this package forms part of the set of "HZ_IMP_LOAD_*" packages used by the Customer Interface / Party Import concurrent programs, allowing bulk creation and update of relationships between parties (such as contact-to-customer or organization-to-person links) from external or staged data.

The package declares a set of collection types used internally during load processing, including BATCH_ID, PARTY_ID, RELATIONSHIP_TYPE, COMMENTS, ATTRIBUTE_CATEGORY, ATTRIBUTE, RELATIONSHIP_ID, ROWID, NUMBER_COLUMN, FLAG_COLUMN, and FLAG_ERROR. The FLAG_COLUMN type, defined as a table of VARCHAR2(1), is characteristic of the flag-based control columns (for example insert/update indicators and validation status) used throughout the TCA import stack. The FLAG_ERROR type is documented explicitly as holding validation error columns. These collections support bulk-bind processing of interface rows.

Key Procedures and Functions

The ETRM metadata documents two callable units:

  • LOAD_RELATIONSHIPS — The primary procedure responsible for processing staged relationship records. It accepts a DML_RECORD_TYPE parameter from HZ_IMP_LOAD_WRAPPER and returns the standard TCA return status triple (x_return_status, x_msg_count, x_msg_data). It performs the insert or update of HZ_RELATIONSHIPS rows, resolving party identifiers and applying validation outcomes recorded in the interface and error tables.
  • VALIDATE_DESC_FLEXFIELD_F — A validation function that checks a descriptive flexfield context (attribute category) and its associated attribute segments against a supplied validation date. It returns a VARCHAR2 result indicating validation success or failure, and is invoked during relationship load processing to ensure that any DFF values attached to a relationship are valid before commit.

No other procedures or functions are exposed by the package specification.

Tables Accessed

The package references the following objects, documented through APPS synonyms:

  • HZ_IMP_RELSHIPS_INT — The relationship interface table, the main source of inbound rows to be loaded.
  • HZ_PARTIES — Used to resolve and validate party identifiers referenced by the relationship records.
  • HZ_RELATIONSHIPS — The base table into which valid relationship records are inserted or updated.
  • HZ_IMP_ERRORS_S — The sequence used to generate error identifiers for records that fail validation.
  • HZ_IMP_RELSHIPS_SG — The sequence used to generate relationship identifiers during load.
  • HZ_IMP_TMP_ERRORS — A temporary staging table for accumulating validation error messages.
  • HZ_IMP_TMP_REL_END_DATE — A temporary table used to manage relationship end-date processing during the load.
  • DUAL and PLITBLM — Standard utility objects used for single-row selects and PL/SQL table (index-by table) operations.

Usage Notes

HZ_IMP_LOAD_RELATIONSHIPS_PKG is not intended for direct end-user invocation. It is called by the TCA party import concurrent programs and, per the documented metadata, is referenced by one other package in the import stack. The typical invocation path is through the Customer Interface or Party Import concurrent program, which populates HZ_IMP_RELSHIPS_INT and then delegates row processing to LOAD_RELATIONSHIPS, passing a DML_RECORD_TYPE that describes the batch and DML mode.

Customizations should call the package through the same wrapper used by the standard import process, and callers must always inspect x_return_status and the message count/data outputs. The FLAG_COLUMN and FLAG_ERROR collection types indicate that processing is flag-driven; any custom staging of interface records must therefore populate the appropriate flag columns correctly to ensure records are selected, validated, and loaded. Because the package writes to core TCA tables, it should only be invoked in a controlled import context rather than ad hoc from Forms or SQL*Plus.