Search Results spawn_csp_req_headers_ins

Overview

CSM_USER_EVENT_PKG is an Oracle E-Business Suite package owned by the APPS schema that supports user provisioning and life-cycle event handling for the Customer Service (CSM) and Field Service product families. Its header indicates an AUTHID CURRENT_USER declaration and a generation date of June 2002, with subsequent modifications extending its scope through Release 12.1. The package name reflects its role as a subscriber to user-event activities: when a user is created, updated, or deleted, or when a responsibility is assigned, the package orchestrates the creation of supporting "ACC" (access or account) staging records for a range of dependent CSM entities. The suffix "_ACC" on the referenced tables indicates that this package populates shadow or auto-synchronization tables used to propagate data from runtime tables into an offline client or synchronized access layer.

Key Procedures and Functions

The documented interface contains twenty-three procedures and functions. The central routine relevant to the user's search is INSERT_ACC, which performs the actual insertion of accumulated records into the CSM auto-sync access tables during a user event. The package groups its logic into several families:

• User and responsibility lifecycle: IS_OMFS_PALM_RESPONSIBILITY, IS_FIRST_OMFS_PALM_USER, USER_RESP_INS_INITIALIZER, USER_DEL_INIT, DISABLE_USER_PUB_SYNCH, and ENABLE_USER_PUB_SYNCH manage the enablement, disabling, and initialization of public synchronization for a user and their assigned responsibilities.
• Entity spawn routines: SPAWN_TASK_INS, SPAWN_INCIDENT_INS, SPAWN_TASK_ASSIGNMENT_INS, SPAWN_PERZ_INS, SPAWN_DASHBOARD_SRCH_COLS_INS, SPAWN_INV_LOC_ASSIGNMENT_INS, SPAWN_PO_LOC_ASS_ALL_INS, SPAWN_CSP_REQ_HEADERS_INS, SPAWN_CSP_REQ_LINES_INS, SPAWN_MAT_TXN, and SPAWN_MTL_SERIAL_NUMBERS create access-layer rows for tasks, incidents, assignments, personalizations, dashboard columns, inventory locations, purchasing locations, service request headers and lines, material transactions, and serial numbers.
• Accounting/maintenance: ITEMS_ACC_PROCESSOR and PURGE_ALL_ACC_TABLES process item-related access records and remove obsolete access data for a given user.

Parameters are intentionally omitted here; only the documented names and intents are asserted.

Tables Accessed

The package reads and writes ASG_USER and ASG_USER_PUB_RESPS to resolve the user and responsibility context, and folds results into the CSM auto-sync family: CSM_AUTO_SYNC_ACC, CSM_AUTO_SYNC_LOG_ACC, CSM_CLIENT_NFN_LOG_ACC, and CSM_CLIENT_UNDO_REQUEST_ACC. Business content tables include CSM_CONTR_BUSS_PROCESSES_ACC, CSM_CONTR_BUSS_TXN_TYPES_ACC, and CSM_CONTR_HEADERS_ACC for contract information, plus the counter tables CSM_COUNTERS_ACC, CSM_COUNTER_PROPERTIES_ACC, CSM_COUNTER_PROP_VALUES_ACC, and CSM_COUNTER_VALUES_ACC. Coverage data flows through CSM_COV_ACTION_TIMES_ACC and CSM_CSI_ITEM_ATTR_ACC. INSERT_ACC is the point at which rows from these sources are written into the access-layer targets.

Usage Notes

CSM_USER_EVENT_PKG is invoked indirectly rather than as a user-facing entry point. Typical callers are the user-management forms and Oracle CRM foundation workflows that raise user-event triggers, and it is referenced by two other packages within the CSM module. Because the AUTHID is CURRENT_USER, callers must ensure the invoking schema has privileges on the underlying CSM objects. Operations should be executed in a controlled maintenance window, since the spawn and purge routines manipulate large volumes of access-layer rows; ITEMS_ACC_PROCESSOR and PURGE_ALL_ACC_TABLES are best treated as batch or diagnostic operations. Customizations should avoid direct invocation where a concurrent program or standard form already provides the call path.