Search Results cs_sr
Overview
CS_SR_WF_DUP_CHK_PVT is a private PL/SQL package body in the Oracle E-Business Suite Service (CS) module that supports duplicate service request detection and automatic task creation within the Service Request workflow. It is classified as a PVT (private) API within the APPS schema, meaning it is intended for internal invocation by Oracle's Service Request workflow rather than direct use by external integrations or customizations. The package operates as a workflow callback handler, accepting standard Workflow Engine parameters such as itemtype, itemkey, actid, funmode, and an OUT result indicator, which allows the Service Request workflow to branch conditionally based on duplicate-check outcomes.
The package header comment references a 2009 revision (120.1.12010000.2), reflecting its long-standing role in the CS Service Request lifecycle across both 12.1.1 and 12.2.2 releases. It forms part of the logic that determines whether an inbound service request (particularly one originating from Web or Email channels) should be subjected to duplicate validation, and it drives subsequent automated task assignment when duplicate criteria are satisfied.
Key Procedures and Functions
The package exposes seven documented procedures that together implement the duplicate-check decision flow and its downstream actions:
- CHECK_SR_CHANNEL — Evaluates the service request's creation channel (for example, WEB or EMAIL) via the sr_creation_channel column of CS_INCIDENTS_ALL_B and returns a result flag indicating whether the request qualifies for further duplicate checking.
- CHECK_SR_UPDATED — Determines whether the service request has been modified since creation, comparing creation_date, last_update_date, and object_version_number to decide if a re-check of duplication is warranted.
- CHECK_DUPLICATE_PROFILE — Inspects the duplicate-check system profile and related setup to confirm that duplicate detection is enabled and configured for the given service request type.
- CHECK_AND_PERF_DUP_CHECK — Performs the actual duplicate validation, orchestrating the preceding checks and driving the result that the workflow uses to route the request.
- AUTO_TASK_CREATE — Creates automated tasks (JTF_TASKS_B) associated with the service request when duplicate or configured criteria are met.
- SETUP_NOTIFY_NAME — Resolves the notification recipient name used for workflow notifications triggered by the duplicate check.
- CHECK_SR_OWNER_TO_NOTIFY — Determines the service request owner who should receive notification, leveraging resource information to route the workflow message correctly.
Tables Accessed
The package reads CS_INCIDENTS_ALL_B, the base table storing service request header data including incident_id, sr_creation_channel, creation_date, last_update_date, and object_version_number. Setup and configuration are sourced from CUG_SR_TYPE_DUP_CHK_INFO, which stores duplicate-check criteria per service request type. Notes are read from JTF_NOTES_B. Resource identification for ownership and notification relies on JTF_RS_RESOURCE_EXTNS, while automated tasks are created in JTF_TASKS_B. All tables are referenced through APPS synonyms, consistent with standard EBS schema conventions.
Usage Notes
CS_SR_WF_DUP_CHK_PVT is invoked exclusively from the Service Request workflow through Workflow Engine function activities, using the standard (itemtype, itemkey, actid, funmode, result) contract. When funmode is 'RUN', the procedures execute their logic; otherwise they return without action. Because the package is private and referenced by no other database packages (0 dependents), it should be treated as an internal Oracle component. Customizations should extend the workflow or use public CS APIs rather than calling these procedures directly. Exception handling delegates to WF_CORE.Context and re-raises, ensuring workflow diagnostics capture the failure context.