Search Results get_new_user_mtl_system_items




Overview
Explore in AI Chat

Overview

APPS.CSM_MTL_SYSTEM_ITEMS_EVENT_PKG is a PL/SQL package that belongs to the Oracle E-Business Suite Customer Service (CSM) module, part of the Service (CS) application family. Its principal business function is to support event-driven processing and concurrency control for inventory item records that are surfaced within the Customer Service user interface, particularly in the context of service requests, incidents, and debrief activities. The package maintains a denormalized or cached copy of Oracle Inventory master item data, represented by the CSM_MTL_SYSTEM_ITEMS_ACC table and its corresponding sequence, so that Customer Service forms and concurrent processes can query item information without repeatedly joining directly to the core MTL_SYSTEM_ITEMS tables.

The "_ACC" suffix on the package name and on the tables it manages refers to the Accelerator or Access Control caching pattern widely used across the CSM event packages. This package is classified with an API type of OTHER in the ETRM repository and holds a VALID status in the APPS schema under both Oracle EBS 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The ETRM metadata documents four callable entities within this package:

  • REFRESH_MTL_SYSTEM_ITEMS_ACC — Repopulates the item access table (CSM_MTL_SYSTEM_ITEMS_ACC) from the underlying Inventory sources. It is the primary maintenance routine that keeps the cached item set synchronized with master data.
  • GET_NEW_USER_MTL_SYSTEM_ITEMS — Retrieves the subset of inventory items that are newly available or newly relevant to a given user. It supports user-scoped item visibility, typically validating against the user's assigned inventory organizations.
  • MTL_SYSTEM_ITEMS_ACC_I — The insert (I) handler responsible for creating new rows in the item access table when items become visible to Customer Service users.
  • MTL_SYSTEM_ITEMS_ACC_D — The delete (D) handler responsible for removing rows from the item access table when item visibility is revoked or no longer applicable.

Exact parameter signatures are not enumerated in the ETRM excerpt; the naming convention indicates that I and D variants operate as row-level DML handlers, while the GET and REFRESH routines perform set-based query and maintenance operations respectively.

Tables Accessed

The package reads and writes a broad set of CSM and Inventory-related tables through APPS synonyms. The central objects are CSM_MTL_SYSTEM_ITEMS_ACC and CSM_MTL_SYSTEM_ITEMS_ACC_S (its supporting sequence), which together store the cached item access records. CSM_USER_INVENTORY_ORG links users to the inventory organizations whose items they may view. CSI_ITEM_INSTANCES and CSM_ITEM_INSTANCES_ACC support item instance tracking within customer service flows.

Incident and requirement context is drawn from CS_INCIDENTS_ALL_B, CSM_INCIDENTS_ALL_ACC, CSP_REQUIREMENT_HEADERS, CSP_REQUIREMENT_LINES, CSP_REQ_LINE_DETAILS, CSM_REQ_LINES_ACC, and CSM_REQ_LINE_DETAILS_ACC. ASG_USER provides the resource or user identifier used in user-scoped item retrieval. CSF_DEBRIEF_LINES and CS_TRANSACTION_TYPES_B supply debrief and transaction-type reference data. The package depends on the SYS.STANDARD schema object, which is the normal PL/SQL built-in package.

Usage Notes

CSM_MTL_SYSTEM_ITEMS_EVENT_PKG is an internal implementation package rather than a public integration API. It is referenced by five sibling event packages — CSM_ITEM_INSTANCE_EVENT_PKG, CSM_PARTY_DATA_EVENT_PKG, CSM_SR_EVENT_PKG, CSM_TASK_ASSIGNMENT_EVENT_PKG, and CSM_USER_EVENT_PKG — which invoke its routines as part of broader Customer Service event propagation. Because it carries an OTHER API classification, Oracle does not document it as a supported direct-call interface.

Typical invocation occurs indirectly when Customer Service forms raise item-related events, when users are assigned new inventory organizations, or when item visibility must be refreshed for debrief and service request workflows. Custom code should avoid calling it directly; instead the supported entry points and standard CSM business flows should be used, since the cached access tables must remain consistent with the CSM event framework's sequencing and locking conventions.