Search Results log_ig_errors

Overview

APPS.XTR_IG_TRANSFERS_PKG is a PL/SQL package body within Oracle E-Business Suite Financials, belonging to the Treasury and Risk Management (ETRM) module. Its primary business function is to manage the import, validation, and creation of intergroup (IG) transfer deals from the staging interface tables into the core treasury deal tables. Within a multi-organization or multi-entity corporate structure, intergroup transfers represent internal deals between distinct legal entities or business units, and this package enforces the data integrity rules, currency conversions, and reporting requirements those transactions demand.

The package is classified under the ETRM metadata as an "OTHER" API, meaning it is not a formally published public interface but rather an internal processing engine invoked by the IG transfer import workflow. It is referenced by two other packages and exposes roughly thirty-four documented procedures and functions organized around three concerns: field-level validation, calculation (including high-level currency and reporting currency amounts), and interface-to-base-table loading. The user search term log_ig_errors points directly at the package's central error-handling routine, LOG_IG_ERRORS, which is the mechanism through which all validation failures surface to end users.

Key Procedures and Functions

The documented procedures fall into validation, calculation, and loading groups:

• LOG_IG_ERRORS — Central error logging routine. It resolves dynamic prompt text from language tables and, depending on the error code, posts a formatted message via FND_MESSAGE, setting tokens such as FIELD, LIMIT_CODE, or DATE. Recognized codes include XTR_MANDATORY, XTR_INV_LIMIT_CODE, XTR_IMP_DEAL_REVAL_EXIST, XTR_IMP_DEAL_ACCRUAL_EXIST, XTR_LIMIT_EXCEEDED, and several description-flex API errors. Where source context is not ZBA or CL, it delegates to XTR_IMPORT_DEAL_DATA.LOG_INTERFACE_ERRORS.
• VALID_CPARTY_CODE, VALID_PARTY_ACCT, VALID_COMP_ACCT, VALID_IG_ACCT, VALID_BANK_ACCOUNTS-type checks — Validate counterparty, party account, company account, and IG account references against XTR_PARTY_INFO and XTR_BANK_ACCOUNTS.
• VALID_TRANSFER_DATE — Ensures the transfer date is within permissible bounds for the deal.
• VALID_CURRENCY, VALID_COMP_REPORTING_CCY — Validate transaction and company reporting currencies.
• VALID_ACTION, VALID_PRODUCT, VALID_PORTFOLIO, VALID_LIMIT_CODE, VALID_PRINCIPAL_ADJUST, VALID_DEAL_LINKING_CODE, VALID_DEALER_CODE — Validate action, product, portfolio, limit, principal adjustment, deal linking, and dealer code values against their respective setup tables.
• CHECK_MANDATORY_FIELDS — Enforces required-field completeness before any record proceeds to loading.
• CALC_DETAILS, CALC_HCE_AMTS, CALCULATE_VALUES — Compute deal detail amounts, high-level currency equivalent amounts, and derived values applying XTR_PRICE_MODELS and XTR_AMOUNT_ACTIONS logic.
• COPY_FROM_INTERFACE_TO_IG — Populates the XTR_INTERGROUP_TRANSFERS and XTR_DEALS_S base tables from XTR_DEALS_INTERFACE after validation succeeds.

Tables Accessed

The package reads and writes the intergroup interface and base tables at the core of its operation: XTR_DEALS_INTERFACE, XTR_INTERGROUP_TRANSFERS, XTR_DEALS_S, and XTR_DEAL_DATE_AMOUNTS. Validation logic draws on setup and reference tables including XTR_PARTY_INFO, XTR_BANK_ACCOUNTS, XTR_DEALER_CODES, XTR_AMOUNT_ACTIONS, XTR_PRICE_MODELS, XTR_ACCRLS_AMORT, and the XTR_IG_JOURNAL_STRUCTURES / _S tables that define journal generation for intergroup transfers. Error rows are persisted through XTR_INTERFACE_ERRORS, and processing is tracked via XTR_BATCHES and XTR_BATCH_EVENTS. Language prompt text is read from XTR_SYS_LANGUAGES_VL.

Usage Notes

XTR_IG_TRANSFERS_PKG is typically invoked by the intergroup transfer import concurrent program and related ETRM forms during deal entry and import cycles. It is not intended for direct invocation by external applications; customizations should call the documented wrapper interfaces rather than individual validation routines. Because LOG_IG_ERRORS branches on the G_Ig_Source and G_Ig_External_Source package globals, correct global initialization before calling the package is essential. Error codes passed to LOG_IG_ERRORS must belong to the recognized set to receive a properly tokenized message; unrecognized codes fall through to the generic interface error logging path. Standard EBS message dictionary setup for the XTR application must be intact for FND_MESSAGE token substitution to render correctly.