Search Results csm_notes_type_mapping_acc_s

Overview

CSM_NOTES_TYPE_MAP_EVENT_PKG is an Oracle EBS Applications (APPS) package body that maintains the denormalized accelerator table CSM_NOTES_TYPE_MAPPING_ACC, which caches note-type mapping rows sourced from JTF_OBJECT_MAPPINGS. The package implements a single documented entry point, REFRESH_ACC, which synchronizes the accelerator table with the base mapping data by performing delete, update, and insert operations driven by three explicit cursors (c_delete, c_update, and c_insert). Its primary business purpose is to keep the note-type mapping accelerator current so that downstream Service/CRM functionality reads note-type mappings without repeatedly querying the full JTF_OBJECT_MAPPINGS base table.

Dating from the 11i/12.x code line (header revision 120.2, 2011), the package is designed to be invoked as a concurrent-program event. The REFRESH_ACC procedure is declared with PRAGMA AUTONOMOUS_TRANSACTION, allowing it to commit its own synchronization work independently of any enclosing transaction. It records and reads its last execution timestamp from JTM_CON_REQUEST_DATA, keyed by package name and procedure name, so each run processes only changed rows.

Key Procedures and Functions

The documented API surface consists of one procedure:

• REFRESH_ACC — Refreshes the CSM_NOTES_TYPE_MAPPING_ACC accelerator table. It returns status and message output parameters (p_status, p_message), runs autonomously, and determines its processing window by reading the prior run date from JTM_CON_REQUEST_DATA. Within the body it declares cursors c_delete, c_update, and c_insert to reconcile the accelerator against JTF_OBJECT_MAPPINGS. The cursor most relevant to the user search term "c_delete" identifies accelerator rows whose MAPPING_ID no longer exists in JTF_OBJECT_MAPPINGS (NOT EXISTS on the base table), marking them for removal so stale note-type mappings do not persist.

No additional public functions are documented for this package; the remaining logic is internal to REFRESH_ACC.

Tables Accessed

• CSM_NOTES_TYPE_MAPPING_ACC — The accelerator table maintained by the package; rows are deleted, updated, or inserted based on comparison with the base mapping table.
• CSM_NOTES_TYPE_MAPPING_ACC_S — The sequence associated with the accelerator table, referenced via g_notes_type_map_seq_name for key generation.
• JTF_OBJECT_MAPPINGS — The authoritative source of note-type mappings (OBJECT_CODE = 'JTF_NOTE_TYPE'); drives the delete (orphan), update (changed LAST_UPDATE_DATE), and insert (missing mapping) logic.
• JTM_CON_REQUEST_DATA — Stores the last run date per package/procedure, used to compute the incremental processing window.
• ASG_USER / ASG_USER_PUB_RESPS — Queried by cursor c_user_id to resolve users holding the 'SERVICEP' responsibility, supporting population of the access list (l_access_list, asg_download.user_list).
• PLITBLM — Standard EBS table type used for list/array handling within the package.

Usage Notes

REFRESH_ACC is typically scheduled as a concurrent program rather than called from interactive forms. Because it is an autonomous transaction, it commits independently and is safe to run on a recurring schedule to keep the note-type accelerator synchronized with JTF_OBJECT_MAPPINGS. The presence of the ASG_USER and ASG_USER_PUB_RESPS lookups indicates the refresh also rebuilds user access/security lists for the 'SERVICEP' responsibility, which is relevant when note-type visibility is restricted by responsibility.

When troubleshooting stale note-type mappings, the c_delete cursor is the focal point: it removes accelerator rows whose MAPPING_ID has no corresponding base record. Administrators reviewing the "c_delete" search should understand it handles orphan cleanup only; updates and inserts are handled by the separate c_update and c_insert cursors. The package is referenced by no other documented packages, so it is normally driven directly by its concurrent program definition or bespoke scheduling code.