Search Results error_message_token




Overview
Explore in AI Chat

Overview

HZ_IMP_LOAD_FINNUMBERS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Trading Community Architecture (TCA) and Oracle Receivables family of objects that support bulk import of customer financial data. Its specific business function is to load financial number records — such as bank ratings, financial reports, and financial indicator values — from the TCA interface and staging tables into the base TCA financial report and financial number tables.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user and resolves unqualified object references against that caller's schema. The package header carries a version string of 120.1 dated 2005/10/30, which is consistent with the long-lived, relatively stable nature of TCA import utilities. The package exposes a single public procedure and relies on a large set of PL/SQL collection types to support bulk (array) processing.

Key Procedures and Functions

The package documents one published procedure: LOAD_FINNUMBERS. Its purpose is to consume the records supplied through the HZ_IMP_LOAD_WRAPPER.DML_RECORD_TYPE structure and apply the appropriate insert, update, or delete actions against the financial number and financial report tables. The procedure reports its outcome through three standard concurrent-processing style OUT parameters: a return status indicator, a message count, and a message data value. These follow the conventional x_return_status / x_msg_count / x_msg_data pattern used across EBS PL/SQL APIs, allowing callers to determine success or failure and to retrieve error messages.

Supporting the procedure are numerous declared collection types used for bulk binding and in-memory processing, including ROWID, FN_ID, FR_ID, FINANCIAL_NUMBER, FINANCIAL_NUMBER_NAME, FINANCIAL_NUMBER_CURRENCY, PROJECTED_ACTUAL_FLAG, FINANCIAL_UNITS_APPLIED, CREATED_BY_MODULE, and ACTION_FLAG. Error handling is supported by collection types such as LOOKUP_ERROR, FLAG_ERROR, ERROR_ID, ERROR_MESSAGE_NAME, ERROR_MESSAGE_TOKEN, and ERROR_MESSAGE_TOKEN_NAME. The presence of ERROR_MESSAGE_TOKEN is directly relevant to users searching on that term: it is the PL/SQL associative array (table of HZ_IMP_ERRORS.TOKEN1_VALUE) used to pass substitution token values into error messages recorded in the HZ_IMP_ERRORS tables. No procedure parameter lists beyond LOAD_FINNUMBERS are documented, and none should be inferred beyond what ETRM records.

Tables Accessed

Through APPS synonyms, the package references several interface and base tables. HZ_IMP_FINNUMBERS_INT is the primary interface table holding incoming financial number rows before validation and load. HZ_IMP_FINNUMBERS_SG is the staging table that carries the action flag and financial number and report identifiers used to drive the load. HZ_IMP_ERRORS and its sequence HZ_IMP_ERRORS_S, together with HZ_IMP_TMP_ERRORS, are the error repository tables where validation and load failures are logged, including message names and token values. HZ_FINANCIAL_REPORTS and HZ_FINANCIAL_NUMBERS are the TCA base tables into which validated financial report and financial number data is ultimately written. DUAL is referenced for single-row operations, and PLITBLM is the standard EBS PL/SQL table utility package used for collection management.

Usage Notes

The package is typically invoked from the TCA customer import concurrent programs and from related import processing logic rather than directly by end users. In 12.1.1 and 12.2.2 it forms part of the import engine that consumes staging rows prepared by the interface loader, and callers invoke LOAD_FINNUMBERS with a DML_RECORD_TYPE payload, then inspect the return status and message outputs to decide whether further error extraction is required. Error token collection types such as ERROR_MESSAGE_TOKEN allow the load process to record parameterised error messages so that later reporting can reconstruct the relevant token substitutions. Custom code should treat the package as an internal TCA component: call it through the supported DML record wrapper, avoid direct DML against the interface and error tables, and reference the documented LOAD_FINNUMBERS signature only.