Search Results validate_receiver

Overview

The OKS_CT_EVENTS_WFA package is a PL/SQL workflow activity package belonging to the Oracle E-Business Suite Service Contracts (OKS) and TeleService (CS) integration layer. Its name follows the Oracle convention used for Workflow Activity (WFA) callbacks: the _WFA suffix indicates that the procedures contained within are invoked directly by the Oracle Workflow engine as activity functions in a Service Request (SR) or Contract event workflow process. In Oracle EBS 12.1.1 and 12.2.2, this package mediates between contract-related business events and Service Request processing, enabling the automatic creation, validation, and updating of Service Requests when contract events (such as service coverage triggers, entitlement checks, or support agreements) occur. The package header bears a 2005 release stamp (OKSCTEVS.pls 120.0), confirming it is a stable, long-lived component of the ETRM/Service Contracts technical stack that has been carried forward through the 12.2.x releases with minimal structural change. It is classified as an OTHER API, meaning it is not a public, documented interface for customer extension but rather an internal workflow callback invoked by the Workflow runtime.

Key Procedures and Functions

• SELECTOR — A standard Workflow activity dispatcher procedure. Its purpose is to route the workflow's control flow to the appropriate internal activity handler based on the current item type and activity, acting as the entry point used by the Workflow engine when the process reaches a branching or selection node.
• GET_VALUES — Retrieves the attribute values required by the workflow to populate item attributes or to supply runtime data (for example, incident type, severity, or contract references) before subsequent activities execute.
• CREATE_SR — Performs the core business action: instantiating a Service Request record using the values gathered by the preceding activities. This is the principal write operation of the package and links contract events to TeleService incidents.
• VALIDATE_RECEIVER — Validates the intended receiver or recipient of the event/SR (typically resolving against FND_USER and HZ_PARTIES data) before the SR is created or dispatched.
• UPDATE_EVENT — Updates the underlying event or contract record to reflect the outcome of SR processing, closing the loop between the workflow instance and the source business object.

All five procedures follow the Workflow standard signature pattern of itemtype, itemkey, actid, funcmode, result, where result returns either COMPLETE or ERROR to the Workflow engine. No parameter lists are invented here; only the documented procedures are described.

Tables Accessed

The package reads and writes through APPS synonyms to the following documented tables:

• CS_INCIDENT_TYPES, CS_INCIDENT_SEVERITIES, CS_INCIDENT_STATUSES, CS_INCIDENT_URGENCIES — Reference/lookup tables supplying the classification, severity, status, and urgency values applied when constructing the Service Request, ensuring the SR conforms to configured TeleService setup.
• CS_SR_TYPE_MAPPING — Determines how the incoming contract event maps to an accessible Service Request type, driving the CREATE_SR logic.
• FND_USER — Resolves the acting or receiving application user during receiver validation.
• HZ_PARTIES, HZ_RELATIONSHIPS — Provide the party and party-relationship data needed to identify and validate the correct customer, contact, or billing party associated with the event.
• MTL_SYSTEM_ITEMS — Supplies item information where the contract event is item-specific (for example, covered products).
• OKC_K_ITEMS, OKC_K_PARTY_ROLES_B — The core Contracts tables holding contract line items and party roles, which bind the event to its originating contract and define who is entitled to service.

Usage Notes

OKS_CT_EVENTS_WFA is not invoked directly by end users and is not exposed through an application form. Instead, it is executed by the Oracle Workflow engine as part of a contract-event workflow process, with each procedure registered as a function activity in a Workflow definition. It is typically triggered indirectly when a contract event is raised — for example, upon creation or update of a contract in the Service Contracts module — and the configured workflow subsequently creates or updates the associated Service Request. Because it is referenced by zero other PL/SQL packages per the ETRM metadata, it stands as a self-contained leaf component in the dependency chain, consumed only by Workflow runtime invocations. Customization should be avoided; any extension should be implemented by copying the workflow process rather than modifying the seed package, since the package is delivered under the APPS schema and is subject to patching across 12.1.1 and 12.2.2. Database administrators and ETRM developers troubleshooting SR auto-creation from contracts should inspect Workflow item activity errors and check the OKS/CS setup (incident types, severities, and SR type mappings) referenced above, as most runtime failures in this package trace to missing or misconfigured reference data rather than code defects.