Search Results csi_ctr_gen_utility_pvt




Overview
Explore in AI Chat

Overview

CSI_CTR_GEN_UTILITY_PVT is a private PL/SQL utility package in the Oracle EBS Customer Intelligence (CSI) product family, delivered under the APPS schema. It supports the Counter Template and Counter Group generation subsystem, which produces derived counter definitions used in asset tracking, metering, and quality data collection. The package encapsulates common validation, descriptive flexfield initialization, formula and grouping validation, and diagnostic logging routines shared across the counter generation application programming interfaces. Because it is classified as a PVT (private) API, it is not intended for direct invocation by external integrations; rather, it is called by the public counter generation APIs and their dependent packages. The package follows the standard EBS private API conventions, including the use of FND_API sentinel values and profile-driven debug logging consistent with Bug 7197402, which relocated profile reads into a dedicated procedure to avoid repeated queries. Referenced by twelve other packages, it functions as a reusable internal service layer rather than an end-user-facing module.

Key Procedures and Functions

The package exposes a set of diagnostic, validation, and flexfield utilities. The "G_MISS_*" functions (G_MISS_NUM, G_MISS_CHAR, G_MISS_DATE) return the standard FND_API missing-value sentinels, allowing callers to distinguish null from uninitialized values.

Tables Accessed

The package reads CSI_COUNTER_DERIVED_FILTERS and CSI_COUNTER_RELATIONSHIPS through APPS synonyms to resolve counter derivation and relationship definitions. DUAL is used for scalar lookups such as session identity, while V$SESSION supplies SID and OS user for log annotation. Dynamic SQL is executed via DBMS_SQL, and PLITBLM is used for PL/SQL index-by table operations. File output relies on the UTL_FILE built-in package.

Usage Notes

CSI_CTR_GEN_UTILITY_PVT is invoked internally by the counter generation APIs and their callers within the CSI schema. The csi_logfile_name profile option, read by READ_DEBUG_PROFILES and consumed by PUT_LINE, controls diagnostic output and is typically set only during troubleshooting. Administrators enable logging by setting CSI_DEBUG_LEVEL and CSI_LOGFILE_NAME at the site or user level, then reproduce the counter generation transaction through its normal form or concurrent program. No direct custom invocation is recommended; customization should use the public counter generation APIs.