Search Results csf_debrief_line_post_ins

Overview

APPS.CSM_WF_PKG is a PL/SQL package in the Oracle E-Business Suite Applications schema that supports the Oracle Service (Customer Support) module's integration with the Workflow and business-event infrastructure. Its primary business function is to implement the table-level API trigger logic that fires when service-related records are inserted, updated, or deleted, allowing downstream workflow, notifications, and derived-entity processing to remain synchronized with the base service transaction data. The package is classified as an "OTHER" API, indicating it is an internal support package rather than a formally published public interface.

The package is documented as VALID under ETRM 12.2.2, and it is referenced by other service-layer packages including CSM_SERVICEP_WRAPPER_PKG as well as by itself, confirming that it participates in a network of interdependent service processing components. It depends on the FND_API utility package, which is the standard Oracle EBS foundation for error handling and API conventions, and on SYS.STANDARD, the default PL/SQL package.

Key Procedures and Functions

ETRM documents 61 procedures and functions, reflecting the package's role as a collection of granular event handlers rather than a single entry point. The documented procedures fall into several families:

• Task assignment handlers — TASK_ASSIGNMENT_POST_INS, TASK_ASSIGNMENT_PRE_UPD, TASK_ASSIGNMENT_POST_UPD, and TASK_ASSIGNMENT_POST_DEL. These fire before or after insert, update, and delete operations on task assignment records to maintain dependent workflow state.
• Task handlers — TASK_PRE_UPD, TASK_POST_UPD, TASK_POST_INS, and TASK_POST_DEL. These mirror the assignment logic at the task level.
• Service request handlers — SR_POST_INS, SR_PRE_UPD, and SR_POST_UPD, which propagate service request changes into workflow and related tables.
• Debrief header handlers — CSF_DEBRIEF_HEADER_POST_INS, CSF_DEBRIEF_HEADER_PRE_UPD, CSF_DEBRIEF_HEADER_POST_UPD, and CSF_DEBRIEF_HEADER_POST_DEL.
• Debrief line handlers — CSF_DEBRIEF_LINE_POST_INS, CSF_DEBRIEF_LINE_PRE_UPD, CSF_DEBRIEF_LINE_POST_UPD, and CSF_DEBRIEF_LINE_POST_DEL.
• Counter and resource handlers — including CSP_INV_LOC_ASSIGNMNT_POST_INS, plus additional documented entries dealing with counters and resource group membership.

The naming convention confirms the trigger pattern: PRE_UPD procedures execute before the DML statement, while POST_INS, POST_UPD, and POST_DEL execute afterward. The metadata does not document parameter lists, so signatures are omitted here.

Tables Accessed

The package reads and writes through APPS synonyms, including:

• CS_COUNTER_PROPERTIES and CS_COUNTER_PROP_VALUES — counter configuration and value storage used to drive numbering and workflow state.
• JTF_NOTES_B — the base notes table, supporting note attachment to service entities.
• JTF_RS_GROUP_MEMBERS — resource group membership, used to resolve assignment and routing.
• CSF_DEBRIEF_HEADERS and CSF_DEBRIEF_LINES — debrief header and line records for field service debrief processing.
• CSI_ITEM_INSTANCES — installed base item instance records.
• CSM_ACTIVITY_SEQ — activity sequence tracking for service activities.
• Various _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, which hold the audit/change capture rows generated from base table DML.
• ASG_USER — user reference data used for assignment resolution.

Usage Notes

CSM_WF_PKG is not intended for direct invocation by end users or custom applications. Its procedures are typically called from database triggers on the underlying Customer Support tables (task, task assignment, service request, debrief header, and debrief line), from the service processing wrapper package CSM_SERVICEP_WRAPPER_PKG, and from workflow-related processing initiated by Oracle Service forms and concurrent programs. The "_ACC" tables it populates are consumed by downstream audit and change-capture logic.

Because the package is classified as OTHER and is internally referenced, customizations should avoid modifying it. Developers extending Oracle Service workflow behavior should instead build on supported public APIs and let this package's trigger-driven logic run unmodified. When troubleshooting workflow propagation, assignment, or debrief audit issues in an EBS 12.1.1 or 12.2.2 environment, this is a primary candidate for review, since the trigger-based procedures are executed implicitly whenever the associated service records are changed.