Search Results spawn_counters_ins
Overview
CSM_ITEM_INSTANCE_EVENT_PKG is a PL/SQL package owned by the APPS schema that forms part of the Oracle E-Business Suite Service (CSM) event infrastructure for item instance management. It supports the capture, tracking, and lifecycle handling of customer product instances registered in Oracle Installed Base (CSI). The package functions primarily as an event processing layer: it detects changes to item instances, records them in the CSM item-instance accountability structures, and responds to business events by maintaining relationships between instances and the incidents, tasks, and service requests that reference them. Its API classification is OTHER, meaning it is an internal supporting package rather than a public, documented integration API.
Sitting between the pure Installed Base data model (CSI) and the Service request/incident model (CSM), the package is central to maintaining data consistency whenever item instances are created, updated, transferred, or removed. Because it is a dependency of several higher-level event packages, it effectively acts as the transactional engine beneath the Service module's consumer-facing event processing.
Key Procedures and Functions
The documented API exposes eleven procedures and functions:
- ITEM_INSTANCE_MDIRTY_U_ECHUSER — Marks item instance records as modified (dirty) so downstream accountability processing re-evaluates them; associated with tracking the last-updating user.
- II_RELATIONSHIPS_ACC_I — Inserts accountability records for item-instance relationships when new relationships are created.
- ITEM_INSTANCES_ACC_PROCESSOR — The central processor that reconciles item instances against their accountability staging records.
- II_RELATIONSHIPS_ACC_D — Handles deletion of relationship accountability records when relationships are removed.
- ITEM_INSTANCES_ACC_D — Deletes item-instance accountability rows for instances no longer relevant.
- REFRESH_INSTANCES_ACC — Rebuilds or refreshes the accountability tables to reflect the current state of Installed Base.
- GET_IB_AT_LOCATION — Retrieves installed-base instances associated with a given location.
- SPAWN_COUNTERS_INS — Creates counter records (based on counter groups) for newly inserted instances so usage counters can be tracked.
- DELETE_IB_AT_LOCATION — Deletes installed-base instances tied to a specified location.
- SPAWN_COUNTERS_DEL — Removes the counters generated for deleted instances.
- DELETE_IB_NOTIN_INV — Deletes installed-base instances that no longer appear in inventory, aligning IB with inventory records.
Tables Accessed
The package reads and writes through APPS synonyms across three functional areas:
- Installed Base (CSI): CSI_ITEM_INSTANCES, CSI_II_RELATIONSHIPS, CSI_INSTANCE_STATUSES, CSI_I_VERSION_LABELS — the core instance, relationship, status, and version data being processed.
- Accountability/staging (CSM): CSM_ITEM_INSTANCES_ACC and its sequence CSM_ITEM_INSTANCES_ACC_S, CSM_II_RELATIONSHIPS_ACC and CSM_II_RELATIONSHIPS_ACC_S, CSM_INCIDENTS_ALL_ACC, CSM_MTL_ONHAND_QTY_ACC — intermediate tables that track pending instance/relationship changes and on-hand quantities.
- Counters and service context: CS_COUNTERS, CS_COUNTER_GROUPS, CS_INCIDENTS_ALL_B, ASG_USER, JTM_CON_REQUEST_DATA — supporting counter generation, incident linkage, user resolution, and service request data.
Usage Notes
CSM_ITEM_INSTANCE_EVENT_PKG is not intended for direct end-user invocation. It is invoked programmatically by higher-level Service event packages — CSM_DEBRIEF_EVENT_PKG, CSM_SR_EVENT_PKG, CSM_SYSTEM_ITEM_EVENT_PKG, CSM_TASK_ASSIGNMENT_EVENT_PKG, and CSM_WF_PKG — and is also referenced by itself. These callers trigger instance-event handling during service request creation, debrief processing, task assignment, and workflow transitions.
Typical invocation occurs indirectly through Service module business flows and concurrent accountability-processing programs rather than through Oracle Forms directly. In Oracle EBS 12.1.1 and 12.2.2, the package runs in the APPS schema and depends only on SYS.STANDARD, indicating a self-contained implementation with no external custom dependencies. Because it is an internal package, customizations should avoid calling its procedures directly; integrations should instead operate through supported Installed Base or Service APIs.
-
PACKAGE: APPS.CSM_ITEM_INSTANCE_EVENT_PKG
12.2.2
-
PACKAGE: APPS.CSM_ITEM_INSTANCE_EVENT_PKG
12.1.1
-
PACKAGE BODY: APPS.CSM_ITEM_INSTANCE_EVENT_PKG
12.1.1
-
PACKAGE BODY: APPS.CSM_ITEM_INSTANCE_EVENT_PKG
12.2.2
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on CSM_UTIL_PKG
12.2.2
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on CSM_UTIL_PKG
12.1.1
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on FND_LOG
12.1.1
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on CSM_COUNTER_EVENT_PKG
12.1.1
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on FND_LOG
12.2.2
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on CSM_COUNTER_EVENT_PKG
12.2.2
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on CSM_ITEM_INSTANCE_EVENT_PKG
12.1.1
-
APPS.CSM_ITEM_INSTANCE_EVENT_PKG dependencies on CSM_ITEM_INSTANCE_EVENT_PKG
12.2.2