Search Results get_txn_type_id

Overview

CSI_ML_UTIL_PVT is an Oracle E-Business Suite private PL/SQL package owned by the APPS schema, classified as a PVT API. It resides within the CSI (Installed Base / Customer Support Intelligence) product family and specifically supports the Counters and Meter Reading subsystem, known internally as "ML" (Meter Log / Meter Reading). The suffix "_PVT" indicates that this is an internal, private package intended for consumption by other CSI packages and concurrent programs rather than a public, directly callable API. Its primary business function is to supply common utility routines for resolving identifier values, managing interface records, validating hierarchical relationships between item instances, and processing status transitions during Counters and meter-reading data loads.

The package occupies a foundational position in the Counters architecture, sitting beneath the public creation and interface packages and providing the low-level resolution and validation logic they depend upon.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions. These fall into several functional groupings:

• Identifier resolution: RESOLVE_IDS, RESOLVE_PW_IDS, RESOLVE_UPDATE_IDS, and RESOLVE_REL_IDS resolve business keys and surrogate identifiers during interface processing, translating between external references and internal primary keys.
• Type and hierarchy derivation: GET_TXN_TYPE_ID retrieves a transaction type identifier; GET_CHILDREN, GET_NEXT_LEVEL, and GET_TOP_MOST_PARENT navigate the item-instance hierarchy to determine ancestry and descendants.
• Validation: VALIDATE_RELATIONSHIP, CHECK_CYCLIC, ELIMINATE_DUP_RECORDS, and ELIMINATE_DUP_SUBJECT enforce data integrity by detecting cyclic relationships and removing duplicate interface records or subjects before processing.
• Error and status handling: LOG_CREATE_ERRORS and LOG_CREATE_PW_ERRORS record errors arising during creation or power (PW) processing; SET_PTY_PROCESS_STATUS and SET_EXT_PROCESS_STATUS update the process status of party and extended records as interface batches progress.

No parameter signatures are documented in the metadata.

Tables Accessed

The package reads and writes a broad set of CSI tables via APPS synonyms. Interface tables such as CSI_II_RELATION_INTERFACE, CSI_INSTANCE_INTERFACE, CSI_I_ASSET_INTERFACE, and CSI_IEA_VALUE_INTERFACE hold staged data awaiting validation and resolution. The base and history tables CSI_II_RELATIONSHIPS, CSI_II_RELATIONSHIPS_S, and CSI_II_RELATIONSHIPS_H store confirmed instance relationships, while CSI_II_RELATION_TYPES provides relationship type definitions. CSI_ITEM_INSTANCES and CSI_INSTANCE_STATUSES hold the core instance and status records. Supporting tables include CSI_IEA_VALUES, CSI_IP_ACCOUNTS, CSI_I_EXTENDED_ATTRIBS, and CSI_I_ORG_ASSIGNMENTS, which supply extended attribute and organizational context.

Usage Notes

CSI_ML_UTIL_PVT is invoked by four other packages in the Counters module: CSI_ML_CREATE_PUB, CSI_ML_CREATE_PVT, CSI_ML_INTERFACE_TXN_PVT, and CSI_ML_PROGRAM_PUB. It is not intended for direct customer invocation. It is typically reached indirectly through concurrent programs that load meter and counter data (the CSI_ML_PROGRAM_PUB interface) or through public creation routines that ultimately delegate identifier resolution, hierarchy validation, and error logging to this utility layer. Custom development should prefer the public packages; referencing the _PVT package directly risks breakage across patches. The package depends on FND_API, confirming its use of the standard EBS API error-handling and message conventions.