Search Results apply_update
Overview
CSM_USER_PKG is a PL/SQL package in the APPS schema that participates in the Oracle E-Business Suite publication and subscription synchronization framework. Its name and structure indicate that it acts as a subscriber-side handler for the CSF_M_USER publication item, exposing the standard apply routine (APPLY_CLIENT_CHANGES) that the publication framework calls to reconcile inbound records against the local user data model. The package header comment references the source file csmuusrb.pls and the globals g_object_name (CSM_USER_PKG) and g_pub_name (CSF_M_USER), confirming that the package is bound to the user publication item and relies on CSM_UTIL_PKG.LOG for debug tracing at FND_LOG levels.
Functionally the package bridges the CSF message queue tables and the local ASG_USER record, propagating migration-status attributes and, in specific version scenarios, removing responsibility assignments from FND_USER. It is classified as a non-API ("OTHER") package in the ETRM 12.2.2 repository, meaning it is intended for framework consumption rather than direct customer invocation.
Key Procedures and Functions
The ETRM 12.2.2 metadata documents a single entry point:
- APPLY_CLIENT_CHANGES — The subscriber-side apply routine for the
CSF_M_USERpublication item. It is the procedure the publication framework invokes to process inbound user records on the client (receiving) instance. Based on the package body, the routine dispatches to internal apply handlers such as APPLY_INSERT and APPLY_UPDATE (which the source excerpt shows are declared but not exposed as documented API entries), and it is responsible for setting the return status back to the framework.
No parameter signatures are published in the ETRM record, so the exact interface should be confirmed against the deployed package specification on the target instance.
Tables Accessed
- CSF_M_USER_INQ — The inbound inquiry view/queue over the
CSF_M_USERpublication item. The documented cursorc_USER_inqselects from this object filtered bytranid$$andclid$$cs, which is how the framework delivers a single record to the apply routine. - ASG_USER — The local user table into which the package applies migration attributes. The source shows an UPDATE driven by
USER_ID, writingMIGRATION_COMPLETED,MIGRATION_COMPLETED_DATE, andMIGRATION_COMPLETION_VERSION. - FND_APPLICATION — Read to resolve the
CSLapplication short name (APPLICATION_ID 868), used when the migration completion version equals 12 to determine the responsibility to remove.
The package also calls FND_USER_PKG.DELRESP, FND_API, FND_LOG, and CSM_UTIL_PKG.
Usage Notes
CSM_USER_PKG is invoked indirectly by the CSF publication framework whenever the CSF_M_USER publication item delivers records to the subscriber. It is not designed for direct call from forms or concurrent programs; the ETRM record lists one dependent package referencing it, confirming framework-driven execution. Custom code should not invoke APPLY_CLIENT_CHANGES directly, as the routine assumes the framework has already staged inbound rows in CSF_M_USER_INQ and controls transaction and error semantics. When troubleshooting synchronization of user migration attributes or unexpected responsibility removal on the CSL_IMOBILE responsibility, enable FND_LOG at procedure level to capture the package's internal trace messages.
-
APPS.CSM_USER_PKG SQL Statements
12.2.2
-
APPS.CSM_USER_PKG SQL Statements
12.1.1
-
APPS.CSL_TASK_ASSIGNMENTS_PKG SQL Statements
12.2.2
-
APPS.CSL_NOTES_PKG SQL Statements
12.1.1
-
APPS.CSL_COUNTER_PROP_VALUES_PKG SQL Statements
12.1.1
-
APPS.CSM_NOTES_PKG SQL Statements
12.2.2
-
APPS.CSL_COUNTER_VALUES_PKG SQL Statements
12.2.2
-
APPS.CSL_TASK_ASSIGNMENTS_PKG SQL Statements
12.1.1
-
APPS.CSL_NOTIFICATION_ATTR_PKG SQL Statements
12.2.2
-
APPS.CSL_NOTES_PKG SQL Statements
12.2.2
-
APPS.CSM_TASK_ASSIGNMENTS_PKG SQL Statements
12.1.1
-
APPS.CSL_NOTIFICATION_ATTR_PKG SQL Statements
12.1.1
-
APPS.CSM_DEBRIEF_HEADERS_PKG SQL Statements
12.2.2
-
APPS.CSL_COUNTER_VALUES_PKG SQL Statements
12.1.1
-
APPS.CSM_NOTES_PKG SQL Statements
12.1.1
-
APPS.CSL_MATERIAL_TRANSACTION_PKG SQL Statements
12.2.2
-
APPS.CSL_NOTIFICATIONS_PKG SQL Statements
12.1.1
-
APPS.CSM_DEBRIEF_HEADERS_PKG SQL Statements
12.1.1
-
APPS.CSL_MATERIAL_TRANSACTION_PKG SQL Statements
12.1.1
-
APPS.CSL_SERVICE_REQUESTS_PKG SQL Statements
12.2.2
-
APPS.CSL_COUNTER_PROP_VALUES_PKG SQL Statements
12.2.2
-
APPS.CSL_NOTIFICATIONS_PKG SQL Statements
12.2.2
-
APPS.CSM_TASKS_PKG SQL Statements
12.1.1
-
APPS.CSM_MATERIAL_TRANSACTION_PKG SQL Statements
12.2.2
-
APPS.CSM_DEBRIEF_EXPENSES_PKG SQL Statements
12.2.2
-
APPS.CSM_AUTO_SYNC_PKG SQL Statements
12.2.2
-
APPS.CSM_DEBRIEF_EXPENSES_PKG SQL Statements
12.1.1
-
APPS.CSL_TASKS_PKG SQL Statements
12.2.2
-
APPS.CSM_MAIL_RECIPIENTS_PKG SQL Statements
12.1.1
-
APPS.CSM_DEBRIEF_LABOR_PKG SQL Statements
12.1.1
-
APPS.CSL_SERVICE_REQUESTS_PKG SQL Statements
12.1.1
-
APPS.CSM_AUTO_SYNC_NFN_PKG SQL Statements
12.2.2
-
APPS.CSM_TASKS_PKG SQL Statements
12.2.2
-
APPS.CSM_DEBRIEF_LABOR_PKG SQL Statements
12.2.2
-
APPS.CSM_MATERIAL_TRANSACTION_PKG SQL Statements
12.1.1
-
APPS.CSM_COUNTER_VALUES_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.CSM_USER_PKG
12.1.1
-
APPS.CSM_TASK_ASSIGNMENTS_PKG SQL Statements
12.2.2
-
APPS.CSM_COUNTER_VALUES_PKG SQL Statements
12.1.1
-
APPS.CSM_DEBRIEF_PARTS_PKG SQL Statements
12.2.2
-
APPS.CSM_CLIENT_NFN_LOG_PKG SQL Statements
12.2.2
-
APPS.CSL_TASKS_PKG SQL Statements
12.1.1
-
APPS.CSM_MAIL_RECIPIENTS_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.CSM_USER_PKG
12.2.2
-
APPS.CSM_ORDERS_PKG SQL Statements
12.2.2
-
APPS.CSM_AUTO_SYNC_LOG_PKG SQL Statements
12.2.2
-
APPS.CSL_REQUIREMENTS_PKG SQL Statements
12.1.1
-
APPS.CSL_REQUIREMENTS_PKG SQL Statements
12.2.2
-
APPS.CSL_DEBRIEF_PKG SQL Statements
12.2.2
-
APPS.CSM_SERVICE_REQUESTS_PKG SQL Statements
12.1.1