Search Results update_counter_relationship

Overview

CSI_COUNTER_TEMPLATE_PVT is a private PL/SQL package in the APPS schema within Oracle E-Business Suite, associated with the Enterprise Asset Management (eAM) and Process Manufacturing (OPM) counter and meter functionality delivered by the Customer Service Intelligence (CSI) product family. The package encapsulates the business logic required to define, validate, create, and maintain counter templates and their associated configuration data. Counter templates provide a reusable framework that governs how counters (meters) are structured, how they relate to inventory items, how their readings are derived, and how they are categorized into counter groups.

The PVT designation indicates that this is a private implementation package. It is not intended to be called directly by external applications or custom code; instead it is consumed by the public packages that constitute the supported API surface. The metadata confirms that CSI_COUNTER_TEMPLATE_PVT references CSI_CTR_DATASTRUCTURES_PUB for its record and table type definitions, and is itself referenced by CSI_COUNTER_PUB, CSI_COUNTER_PVT, and CSI_COUNTER_TEMPLATE_PUB.

Key Procedures and Functions

The ETRM metadata documents a comprehensive set of procedures organized around two themes: validation and data manipulation. The validation routines establish data integrity before any persistent change is committed. VALIDATE_COUNTER_GROUP confirms that a counter group is properly defined, while VALIDATE_START_DATE ensures the effective start date of a counter template is valid. VALIDATE_INVENTORY_ITEM and VALIDATE_UOM verify that the associated item and unit of measure are legitimate, and VALIDATE_DATA_TYPE confirms that the declared counter data type is supported. VALIDATE_LOOKUPS checks configured lookup values, VALIDATE_CTR_RELATIONSHIP confirms the validity of counter-to-counter relationships, and VALIDATE_COUNTER performs the overall counter validation.

The creation and update procedures provide the transactional core of the package. CREATE_COUNTER_GROUP and UPDATE_COUNTER_GROUP manage counter group records. CREATE_ITEM_ASSOCIATION and UPDATE_ITEM_ASSOCIATION establish and maintain the links between counters and inventory items. CREATE_COUNTER_TEMPLATE and UPDATE_COUNTER_TEMPLATE handle the header definitions, while CREATE_CTR_PROPERTY_TEMPLATE and UPDATE_CTR_PROPERTY_TEMPLATE manage the property templates attached to a counter. CREATE_COUNTER_RELATIONSHIP and UPDATE_COUNTER_RELATIONSHIP govern the relationships formed between counters, and CREATE_DERIVED_FILTERS together with UPDATE_DERIVED_FILTERS handle the derived filters that drive conditional counter readings.

Tables Accessed

The package operates against the principal CSI counter tables through APPS synonyms. CSI_COUNTER_TEMPLATE_B stores the base counter template definitions, with CSI_COUNTER_TEMPLATE_TL holding the translated template descriptions. CSI_COUNTERS_B, CSI_COUNTER_PROPERTIES_B, and CSI_COUNTER_ASSOCIATIONS hold counter definitions, their properties, and item associations respectively. CSI_CTR_ITEM_ASSOCIATIONS links counters to specific items, corroborated by validation against MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_B. CSI_COUNTER_RELATIONSHIPS stores counter-to-counter relationships, and CSI_COUNTER_DERIVED_FILTERS stores the derived filter logic. CSI_COUNTER_READINGS holds the actual measurement data captured against counters. CS_CSI_COUNTER_GROUPS defines the grouping hierarchy, and CSI_ITEM_INSTANCES references the deployed item instances. MTL_UNITS_OF_MEASURE supports UOM validation, and PLITBLM provides the standard PL/SQL table structure used internally.

Usage Notes

Because CSI_COUNTER_TEMPLATE_PVT is a private package, it is not registered as a public API and should not be invoked directly from custom forms, concurrent programs, or user code. Access is provided through the public wrapper packages CSI_COUNTER_TEMPLATE_PUB and CSI_COUNTER_PUB, which expose supported entry points and handle error handling conventions. The package is invoked during counter template setup when administrators define and maintain counter configurations, during item-to-counter association maintenance, and when derived filters or counter relationships are established or changed. Customizations that need this behavior should call the corresponding public API procedures, allowing the private package to be upgraded independently during patching and maintaining a supported upgrade path across EBS 12.1.1 and 12.2.2.