Search Results xtr_cashpool_attributes_s

Overview

XTR_CASHPOOL_UTLS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, part of the Treasury (ETRM / XTR) application family. Its business purpose is to centralize the utility logic that maintains cash pool definitions and their associated attribute records. In Treasury terminology, a "cash pool" describes an arrangement of participating portfolios whose balances are aggregated or netted for interest calculation, cash concentration, or notional pooling. The package provides the reusable insert, update, and delete primitives that internal Treasury routines — and, where relevant, external callers — use to create and maintain those cash pool header and attribute rows in a consistent manner. The object is documented with a VALID status and an API classification of OTHER, indicating it is a supporting utility package rather than a published end-user API.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions in this package. They fall into distinct groups corresponding to the different cash pool constructs supported by Treasury.

• INSERT_IAC_CASHPOOL — Creates a new cash pool record for the IAC (interest allocation / inter-account cash) cash pool type, establishing the header definition and its initial attribute set.
• INSERT_IG_CASHPOOL — Creates a new cash pool record for the IG (interest group) cash pool type.
• UPDATE_IAC_CASHPOOL — Modifies an existing IAC-type cash pool definition, including its associated attribute values.
• UPDATE_IG_CASHPOOL — Modifies an existing IG-type cash pool definition and its attributes.
• UPDATE_IG_ROW_CASHPOOL — Updates an individual IG cash pool row, providing row-level maintenance granularity within the interest group structure.
• DELETE_XTR_CASHPOOL — Removes a cash pool definition and its dependent attribute data from the Treasury tables.
• DEFAULT_IAC_IG_ATTRIBUTES — Populates default attribute values for IAC and IG cash pools, ensuring that pools created without explicit attribute input still carry the standard configuration required by downstream interest and pooling processes.

These routines encapsulate the DML logic so that cash pool maintenance is performed through a single controlled entry point rather than through ad hoc SQL against the underlying tables.

Tables Accessed

The package operates against three documented tables, all referenced through APPS synonyms:

• XTR_CASHPOOL_ATTRIBUTES — The core attribute table holding cash pool configuration values. It is the primary target of the insert, update, and delete operations and the record set populated by DEFAULT_IAC_IG_ATTRIBUTES.
• XTR_CASHPOOL_ATTRIBUTES_S — The companion DFF (descriptive flexfield) / translated segment table for cash pool attributes. Because it is listed as a dependency, the package reads or writes attribute segment values that are stored separately from the base attribute rows.
• XTR_PORTFOLIOS — The Treasury portfolio table. It is referenced to validate that the portfolios being associated with a cash pool are legitimate and available, supporting the pool-to-portfolio relationship.

The package also depends on FND_GLOBAL, which supplies the application and user context (such as user ID and responsibility) required for the standard WHO columns and any audit or validation logic embedded in the routines.

Usage Notes

XTR_CASHPOOL_UTLS is not referenced by any other database object according to the dependency metadata, which indicates that it is invoked directly rather than nested inside another PL/SQL package in the shipped code. It is typically called from Treasury setup and maintenance forms, from concurrent programs that mass-maintain cash pool configurations, and from custom extensions or migration scripts that need to create or alter cash pools programmatically. Because the package performs multi-table DML, callers should invoke its routines within a transaction they control and commit only after all related cash pool changes succeed. The presence of the companion _S table in the dependency list means that attribute flexfield values must be synchronized with their base rows; custom code should therefore prefer these packaged routines over direct INSERT, UPDATE, or DELETE statements against XTR_CASHPOOL_ATTRIBUTES to avoid orphaned or inconsistent attribute segment data.