Search Results as_business_event_s

Overview

AS_GAR is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. Its name and dependency footprint indicate that it functions as a Generic Activity/Event Raiser utility, most closely associated with the Oracle Contracts (Service) product family where AS_ prefixed objects reside. The package provides a reusable mechanism for detecting Workflow Business Event subscriptions, assembling a Workflow parameter list, and programmatically raising a Business Event through the Workflow Event System. It also supplies centralized logging and tracing facilities used by the surrounding Service modules. Because the documented API classification is OTHER, the package is not a public, customer-callable business API; it is an internal infrastructure helper invoked by other Service packages and by concurrent processing. The documented status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and AS_GAR is not referenced by any database object, meaning it sits at the top of its dependency chain and exposes only implicitly callable entry points.

Key Procedures and Functions

• INIT — Performs package-level initialization, establishing session context and any cached values required before the remaining routines execute.
• EXIST_SUBSCRIPTION — Checks whether a Business Event subscription exists for a given event, allowing callers to avoid raising events that no subscriber will consume.
• RAISE_BE — Raises a Business Event, typically constructing the parameter list and invoking the Workflow event API. This is the principal functional entry point of the package.
• LOG_EXCEPTION — Records an exception condition to the logging framework, preserving diagnostic context for failures encountered during event processing.
• LOG — Writes a general diagnostic or informational message to the FND log, used broadly for troubleshooting.
• SETTRACE — Enables or disables trace-level logging, generally driven by a profile option value so that verbose output can be switched on without code changes.
• SET_AREA_SIZES — Establishes sizing for internal area or buffer allocations, supporting correct handling of parameter and message data.

Seven documented routines exist in total; no parameter lists are asserted here because they are not part of the documented metadata.

Tables Accessed

• AS_BUSINESS_EVENT_S — The Service module’s Business Event definition table, consulted to validate or resolve events handled by the package.
• WF_EVENTS and WF_EVENT_SUBSCRIPTIONS — Workflow Event System tables examined by EXIST_SUBSCRIPTION and used when raising events.
• WF_PARAMETER_LIST_T — The Workflow parameter list type used to pass event payload data to the event framework.
• FND_CONCURRENT_REQUESTS and FND_CONCURRENT_REQUESTS_S — Concurrent request data, read for request and session context associated with the running process.
• DUAL, PLITBLM, V$PARAMETER — Utility and system references supporting PL/SQL constructs, initialization, and environment inspection.

Usage Notes

AS_GAR is normally reached indirectly. Service-related concurrent programs and forms-based transactions call the parent AS_ packages, which in turn invoke AS_GAR to determine whether an event subscription exists and to raise the corresponding Business Event. Administrators rarely call these routines directly; instead, they influence behavior through profile options controlling trace and log output, and through Workflow Administrator responsibility when diagnosing failed subscriptions. Because the package is not referenced by any database object, it is safe to treat it as a leaf dependency — modifications to its logic affect only its callers. Developers extending Service event handling may model custom event-raising code on the RAISE_BE / EXIST_SUBSCRIPTION pattern, and should route diagnostics through LOG and LOG_EXCEPTION so that output remains consistent with standard EBS logging. Tracing should be enabled cautiously in production environments, as verbose logging from event-heavy transactions can affect performance.