Search Results post_upd

Overview

CSM_WF_PKG is the central entry-point package for Customer Service Manager (CSM) business logic within Oracle E-Business Suite, shell version 120.12 (last shipped 2008/05/21). As documented in the package header comment, it "acts as the entry point to CSM logic from user and vertical hooks as well as from concurrent programs." Rather than exposing business rules directly to forms or external callers, the package serves as a controlled integration layer: triggers, forms, and vertical (partner) customizations call into CSM_WF_PKG, which in turn orchestrates the underlying CSM and TeleService data structures.

A defining characteristic of the package is its "pre/post" API pattern, which is directly relevant to the search term post_upd. For each major entity, the package exposes a matched pair of pre-update and post-update procedures. The pre-update routines capture the row image before a DML operation, caching key column values into package-level global records so that later logic can compare old versus new state. The post-update routines then fire the downstream side effects — workflow notifications, status escalation, and accounting interface population. This pattern is instantiated through global record types declared at the top of the body, including g_task_ass_pre_upd_typ, g_task_pre_upd_typ, g_sr_pre_upd_typ, and g_debrief_line_pre_upd_typ, along with their corresponding null-record counterparts used for initialization and reset. A set of package globals (g_old_subinventory_code, g_old_organization_id, g_old_eff_date_start, g_old_eff_date_end, g_old_default_code) performs the same holding function for inventory location assignments.

Key Procedures and Functions

The package exposes 61 documented procedures and functions, grouped by the entity they govern. The naming convention is consistent: <entity>_PRE_UPD, <entity>_POST_UPD, <entity>_POST_INS, and <entity>_POST_DEL.

• Task Assignment APIs — TASK_ASSIGNMENT_POST_INS, TASK_ASSIGNMENT_PRE_UPD, TASK_ASSIGNMENT_POST_UPD, and TASK_ASSIGNMENT_POST_DEL cover the assignment of resources to service tasks. The pre-update member caches resource_id, assignment_status_id, and task_id so the post-update member can detect meaningful reassignment or status transitions.
• Task APIs — TASK_POST_INS, TASK_PRE_UPD, TASK_POST_UPD, and TASK_POST_DEL govern the task record itself. The pre-update captures task_status_id, task_type_id, scheduled_start_date, scheduled_end_date, and task_id, enabling the post-update member to drive workflow events and scheduling recalculation.
• Service Request APIs — SR_POST_INS, SR_PRE_UPD, and SR_POST_UPD handle the service request (incident) header. The g_sr_pre_upd_typ record is unusually rich, spanning incident_id, customer_id, install_site_id, customer_product_id, inventory_item_id, inv_organization_id, contract_service_id, party_id, location_id, incident_location_id, and owner_group_id — reflecting the breadth of attributes whose change influences downstream CSM processing.
• Debrief Header APIs — CSF_DEBRIEF_HEADER_POST_INS, CSF_DEBRIEF_HEADER_PRE_UPD, CSF_DEBRIEF_HEADER_POST_UPD, and CSF_DEBRIEF_HEADER_POST_DEL manage the field service debrief header lifecycle.
• Debrief Line APIs — CSF_DEBRIEF_LINE_POST_INS, CSF_DEBRIEF_LINE_PRE_UPD, CSF_DEBRIEF_LINE_POST_UPD, and CSF_DEBRIEF_LINE_POST_DEL do the same for debrief lines, caching debrief_line_id, inventory_item_id, and instance_id.
• Inventory Location Assignment APIs — CSP_INV_LOC_ASSIGNMNT_POST_INS and related members manage changes to inventory location assignments, using the g_old_* globals described above.

Tables Accessed

The package reads and writes both base and interface (denormalized) tables via APPS synonyms. The CSM_*_ACC tables — CSM_DEBRIEF_HEADERS_ACC, CSM_DEBRIEF_LINES_ACC, CSM_ITEM_INSTANCES_ACC, CSM_PO_LOC_ASS_ALL_ACC, CSM_REQ_HEADERS_ACC, and CSM_REQ_LINES_ACC — form the core write targets, as these are the interface tables consumed by downstream service and field service processes. The package also reads CSF_DEBRIEF_HEADERS and CSF_DEBRIEF_LINES, CSI_ITEM_INSTANCES for installed base context, and CSM_ACTIVITY_SEQ for sequence generation. Reference and security data are accessed through CS_COUNTER_PROPERTIES, CS_COUNTER_PROP_VALUES, JTF_NOTES_B, JTF_RS_GROUP_MEMBERS, and ASG_USER.

Usage Notes

CSM_WF_PKG is not intended to be called directly by end users. It is invoked from CSM forms, from database triggers on the CSM tables, and from concurrent programs and workflow background processes. Vertical (partner) extensions are expected to hook into these procedures rather than modifying base logic. A notable maintenance point recorded in the header is the 12/16/02 change by ANURAG restoring the workflow threshold value — evidence that the package participates in workflow threshold evaluation. The pre/post update pairing means the procedures must be called in the correct order; calling a post-update routine without its preceding pre-update will leave the global records holding stale or null values and can produce incorrect workflow or accounting results. The package is referenced by four other packages.