Search Results valid_portfolio

Overview

XTR_IAC_TRANSFERS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (Treasury) module as an OTHER API. Its role is to encapsulate the validation, settlement, and creation logic for inter-account transfers (IAC deals) recorded in the XTR_INTERACCT_TRANSFERS table. Inter-account transfers represent movements of funds between internal bank accounts or treasury portfolios, and this package serves as the central control point through which such transfer records are verified, settled, and persisted. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the defining schema, which is significant when the package is invoked from custom code, forms, or concurrent programs running under different schema contexts.

Key Procedures and Functions

The package exposes a mix of boolean-returning validation functions and DML/validation procedures. The validators include VALID_CURRENCY, which checks whether a supplied currency code corresponds to an enabled currency (referencing XTR_MASTER_CURRENCIES); VALID_PARTY_ACCT, which verifies a party and party account combination for a given currency and returns a varchar2 result, presumably an error or status message; VALID_PRODUCT; VALID_PORTFOLIO; VALID_DEALER_CODE; VALID_TRANSFER_AMOUNT; and VALID_DEAL_DATE. Each of these performs a discrete domain check against its corresponding reference table. Utility routine LOG_IAC_Errors records validation failures with an error code and optional field name.

Procedural logic is handled by CHECK_MANDATORY_FIELDS, which inspects a full XTR_INTERACCT_TRANSFERS rowtype for required attributes and raises an error flag; VALIDATE_DEALS, which validates an inter-account transfer record and returns derived bank codes for the from and to sides along with an error flag; and VALIDATE_SETTLE_DDA, which evaluates settlement and dual-authorization state and returns numerous out parameters covering settlement status, reference numbers, authorization details, and audit indicators. The write-side procedures are INS_DEAL_DATE_AMTS, which inserts deal-date amount rows for the from and to banks associated with a transaction; CREATE_IAC_DEAL, which constructs the persistent transfer record; and TRANSFER_IAC_DEALS, which drives the overall transfer processing flow.

Tables Accessed

Through APPS synonyms the package touches XTR_INTERACCT_TRANSFERS (the primary transaction record), XTR_DEAL_DATE_AMOUNTS (dated amount rows inserted by INS_DEAL_DATE_AMTS), XTR_BANK_ACCOUNTS (bank account resolution and validation), XTR_MASTER_CURRENCIES (currency validation), XTR_PARTY_INFO (party and counterparty checks), XTR_DEALER_CODES (dealer validation), XTR_SETTLEMENT_NUMBER_S (settlement numbering sequence), XTR_EXPOSURE_TRANS_S (exposure transaction linkage), and DUAL for scalar checks. These tables support both the front-end validation logic and the back-end record creation and settlement updates.

Usage Notes

Custom code should call the public functions and procedures rather than manipulate XTR_INTERACCT_TRANSFERS directly, since the package enforces mandated validation and audit semantics. VALID_CURRENCY is typically invoked during entry or interface load to reject unsupported currency codes before a transfer is saved. Because the package is AUTHID CURRENT_USER and referenced by one other package, callers should ensure the invoking schema holds appropriate privileges on the XTR objects. Typical invocation points include the inter-account transfer maintenance forms, settlement concurrent programs, and inbound interface programs that load treasury transfers. Error handling should inspect the boolean error out parameters and query logged errors via LOG_IAC_ERRORS conventions.