Search Results log_iac_errors

Overview

APPS.XTR_IAC_TRANSFERS_PKG is a PL/SQL package body in the Oracle E-Business Suite Treasury (ETRM) module. Its name derives from "Inter-Account Transfers," and it encapsulates the business logic required to validate, create, and process inter-account transfer deals between internal treasury entities, bank accounts, and counterparties. The package serves as the programmatic backbone for recording movements of funds between company-owned accounts and for the settlement of those movements. It forms part of the Treasury deal lifecycle, sitting between user-driven data entry (typically through Treasury forms) and the underlying transactional tables that store deal, settlement, and exposure data.

The object is owned by APPS and reports a VALID status. It is documented in the ETRM 12.2.2 metadata as an "OTHER" API classification, meaning it is an internal, non-public API rather than a formally published interface. It is referenced by one other database object and references a defined set of ETRM views, tables, and utility packages.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions, organized around validation, deal assembly, and transfer execution:

• VALID_CURRENCY — Confirms that a supplied currency code is valid and active for the transfer.
• VALID_PARTY_ACCT — Validates the counterparty and bank account relationship used in the transfer.
• VALID_PRODUCT — Verifies the treasury product against authorized product types.
• VALID_PORTFOLIO — Checks that the portfolio referenced by the deal is valid.
• VALID_DEALER_CODE — Ensures the dealer code associated with the transaction is active and permissible.
• VALID_TRANSFER_AMOUNT — Validates the transfer amount, typically checking for positive values and acceptable ranges.
• VALID_DEAL_DATE — Confirms the deal date is within permitted accounting and deal-date windows.
• CHECK_MANDATORY_FIELDS — Confirms that all required attributes for an inter-account transfer have been populated.
• VALIDATE_DEALS — Orchestrates the individual validation routines across a set of deals before processing.
• VALIDATE_SETTLE_DDA — Validates settlement and demand deposit account (DDA) information for the transfer.
• INS_DEAL_DATE_AMTS — Inserts deal date amount records, feeding the deal/date amount table.
• CREATE_IAC_DEAL — Assembles and creates the inter-account transfer deal record.
• TRANSFER_IAC_DEALS — Executes the transfer of validated inter-account deals.
• LOG_IAC_ERRORS — Captures and logs errors raised during validation or processing, using the FND message framework.

Tables Accessed

The package reads and writes a defined group of ETRM tables accessed through APPS synonyms:

• XTR_INTERACCT_TRANSFERS — The primary transaction table holding inter-account transfer deals.
• XTR_DEAL_DATE_AMOUNTS — Stores per-date amounts for deals; populated by INS_DEAL_DATE_AMTS.
• XTR_BANK_ACCOUNTS — Source of internal and counterparty bank account data.
• XTR_DEALER_CODES — Dealer code validation.
• XTR_MASTER_CURRENCIES — Currency validation.
• XTR_PARTY_INFO — Party and counterparty information used in account validation.
• XTR_EXPOSURE_TRANS_S — Exposure transaction data related to transfers.
• XTR_SETTLEMENT_NUMBER_S — Sequence used to generate settlement numbers, directly relevant to the user's search term "xtr_settlement_number_s."
• DUAL — Used for single-row queries and sequence retrieval.

In addition to tables, the package depends on ETRM views (XTR_BANK_ACCOUNTS_V, XTR_AUTH_PRODUCT_TYPES_V, XTR_DEALER_CODES_V, XTR_PARTIES_V, XTR_PORTFOLIOS_V, XTR_DEAL_DATE_AMOUNTS_V) and utility packages including XTR_MISC_P, XTR_SETTLEMENT_SUMMARY_P, XTR_WRAPPER_API_P, and the FND_GLOBAL, FND_MESSAGE, and FND_MSG_PUB framework packages.

Usage Notes

XTR_IAC_TRANSFERS_PKG is invoked through Treasury inter-account transfer forms and related concurrent processing during deal entry, validation, and settlement. The XTR_SETTLEMENT_NUMBER_S sequence dependency indicates that settlement numbers for transfers are generated programmatically at deal creation or transfer time, so callers should not attempt to supply settlement numbers manually. Because the package uses FND message and logging utilities, validation failures are surfaced to the user through the standard Oracle EBS message stack. As an internal "OTHER" API, it is not intended for unrestricted external calls; custom code should treat it as a supported-but-internal interface and validate behavior against the specific release (12.1.1 or 12.2.2).