Search Results mtl_serial_numbers_u1




Overview

The APPS.CSL_MTL_SERIAL_NUMBERS_ACC_PKG package body is a supporting component of the Oracle E-Business Suite Field Service / TeleService (CSL) module, specifically the "access" or "accounting/assignment" layer that manages which serialized inventory items are visible to a given field service resource. Its core business function is to synchronize records between the master serial number repository (MTL_SERIAL_NUMBERS) and a resource-specific access table (JTM_MTL_SERIAL_NUMBERS_ACC). By doing so, the package controls the set of serial numbers that a field service technician or resource is permitted to view, transact, or service within a mobile or field application context. The header comment ($Header: cslsnacb.pls 115.6 2004/09/30) indicates this is a mature, tightly scoped utility that has been stable across the 12.1.1 and 12.2.2 releases. The package is classified as an "OTHER" API, meaning it is not an officially published open interface but rather an internal dependency invoked by the Field Service application flow.

Key Procedures and Functions

The package exposes four documented procedures, representing the standard CRUD lifecycle plus a specialized query routine:

  • INSERT_SERIAL_NUMBERS — Populates the resource access table with serial numbers that satisfy the current assignment rules. As shown in the source excerpt, it performs a BULK COLLECT from MTL_SERIAL_NUMBERS, filtering by current status (values 1 and 3) and by matching the current subinventory/organization of each serial against the resource's assignments in CSP_INV_LOC_ASSIGNMENTS. The sequence JTM_ACC_TABLE_S.NEXTVAL supplies surrogate keys.
  • DELETE_SERIAL_NUMBERS — Removes entries from the resource access table, typically when an assignment expires or a resource's inventory location coverage changes.
  • UPDATE_SERIAL_NUMBERS — Refreshes existing access rows to reflect changes in serial status, location, or assignment, keeping the resource's view consistent with the master data.
  • CON_REQUEST_SERIAL_NUMBERS — Handles serial number access in the context of a connection request (hence the CON_REQUEST prefix), querying data via JTM_CON_REQUEST_DATA to resolve which serialized items are relevant to an active service or connection workflow.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. The central master table is MTL_SERIAL_NUMBERS, the source of all serialized inventory records. The target access table JTM_MTL_SERIAL_NUMBERS_ACC stores the resource-specific projection, keyed by the JTM_ACC_TABLE_S sequence. Assignment and eligibility are resolved using CSP_INV_LOC_ASSIGNMENTS, which maps resources to subinventory/organization combinations. Resource identity and context are drawn from JTF_RS_RESOURCE_EXTNS, FND_USER, ASG_USER, ASG_PUB, and ASG_PUB_RESPONSIBILITY. Connection request context is sourced from JTM_CON_REQUEST_DATA. The PLITBLM table appears in the dependency list, reflecting the package's use of PL/SQL table-based bulk processing. Debug and audit output is routed through the JTM hook utility and message log infrastructure referenced in the body.

Usage Notes

This package is not intended for direct invocation by end users or external integrations. It is invoked internally by the Field Service application as part of the resource access synchronization process — for example when a resource's inventory assignments are established or changed, when serialized items are moved between subinventories, or when serial number status transitions at the tracked statuses of 1 and 3. The presence of the g_debug_level global and calls to JTM_HOOK_UTIL_PKG.Get_Debug_Level and jtm_message_log_pkg.Log_Msg indicates that diagnostic tracing can be enabled through the standard JTM debug mechanism. The user search term mtl_serial_numbers_u1 corresponds to the unique index on the underlying MTL_SERIAL_NUMBERS table, which is relevant because the bulk SELECT performed by INSERT_SERIAL_NUMBERS relies on efficient access paths through that index. In 12.1.1 and 12.2.2 the package retains its original $Revision 115.6 behavior, and it is referenced by one other dependent package within the Field Service stack; developers extending or troubleshooting serial number resource visibility should inspect this package's interaction with CSP_INV_LOC_ASSIGNMENTS rather than modifying the body directly.