Search Results asp_service_content_provider




Overview
Explore in AI Chat

Overview

ASP_SERVICE_CONTENT_PROVIDER is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the ETRM "OTHER" API category, indicating that it is an internal utility package rather than a formally published public API. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, a design choice typical of helper packages whose callers already hold the necessary object privileges.

The package header comment, dated 15-Aug-2005 and revised 19-Aug-2005 by the developer axavier, states its single purpose: it "provides content for the Service Alert." The Service Alert is the Oracle EBS framework that surfaces contextual notifications to users — for example, prompting a service agent with relevant information about an open incident or customer. This package supplies the dynamic content that the alert displays, bridging workflow-driven alert logic with operational service data. In the broader EBS architecture it acts as a content provider plug-in for the Service Alert workflow activity, not as a general-purpose business API.

Key Procedures and Functions

ETRM documents exactly one public routine for this package: CREATE_CONTENT. It is a procedure whose stated role is to "provide content for the Service Alert." The procedure is designed to be invoked as a workflow function activity; its parameter names follow the standard Oracle Workflow function activity contract rather than a bespoke API signature. The documented arguments are:

  • itemtype — a valid item type from the WF_ITEM_TYPES table, identifying the workflow process to which the activity belongs.
  • itemkey — a string generated from the application object's primary key, uniquely identifying the workflow item instance.
  • actid — the function activity instance id, locating the specific executing activity within the item.
  • funcmode — the function execution mode, set by the workflow engine as RUN, CANCEL, or TIMEOUT.
  • resultout — an output parameter returning the activity result, either COMPLETE:SUCCESS or NULL, indicating successful completion of the alert content generation.

No overloads, additional procedures, or private helper routines are documented in the ETRM metadata. Developers should treat CREATE_CONTENT as the only supported entry point.

Tables Accessed

The package references two base tables through APPS synonyms:

  • CS_INCIDENTS_ALL_B — the base table for Oracle Service (TeleService) incidents. This is the primary source from which alert content is assembled, supplying incident number, status, severity, and related identifiers for the workflow item being processed.
  • HZ_PARTIES — the Trading Community Architecture party registry. It supplies customer or contact identification data so the alert can present the affected party's name and context alongside the incident details.

These two references confirm the package's scope: it reads, rather than writes, service-request and party data in order to render alert text. No insert, update, or delete activity against these tables is indicated.

Usage Notes

ASP_SERVICE_CONTENT_PROVIDER is invoked indirectly through Oracle Workflow. When a Service Alert process reaches a function activity whose function name resolves to this package's CREATE_CONTENT routine, the Workflow Engine calls the procedure, passing the standard itemtype, itemkey, actid, and funcmode arguments and capturing resultout. Customers and partners do not call this package directly from forms, concurrent programs, or custom PL/SQL; ETRM records zero dependent packages, underscoring that it sits at the edge of the call graph.

Because the package is not a published API and is marked noship in its version header, its signature and behavior may change without the compatibility guarantees that apply to formal APIs. Customizations should avoid direct invocation and instead rely on the supported Service Alert configuration. When troubleshooting missing or malformed alert content in either 12.1.1 or 12.2.2, DBAs and developers should inspect Workflow activity error logs and verify the presence and status of the referenced incident and party records rather than modifying this package.