Search Results cs_servicerequest_iuhk

Overview

CS_SERVICEREQUEST_IUHK is an internal Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the OTHER API category. Its name follows the Oracle Applications convention for "Internal User Hook" (IUHK) packages: modules that expose pre-processing and post-processing extension points around a base business API without themselves being the primary, publicly supported entry point.

In the Service (CS) module, this package functions as the hook layer that surrounds the core Service Request create and update logic. When a service request is created or modified through the standard Service Request APIs, the surrounding business logic invokes these internal hooks at defined points in the transaction lifecycle. Each hook returns a status value, allowing it to signal success or failure back to the calling process. This design gives Oracle — and, where reached through supported surroundings, the customer — a controlled location to inject logic that must run before or after the main create and update operation, without altering the base API code. In 12.1.1 and 12.2.2 the package is compiled with AUTHID CURRENT_USER, so it executes under the privileges of the invoking session rather than as definer-rights code owned by APPS.

Key Procedures and Functions

The ETRM metadata documents four procedures, all of which return an OUT status parameter; no other parameters are documented.

• CREATE_SERVICEREQUEST_PRE — Pre-processing hook executed before a service request is created. It runs ahead of the main creation logic and reports status through its OUT parameter. This is the procedure most commonly sought when searching for create_servicerequest_pre.
• CREATE_SERVICEREQUEST_POST — Post-processing hook executed after a service request has been created, allowing follow-on activities to run once the record exists.
• UPDATE_SERVICEREQUEST_PRE — Pre-processing hook for the update path, invoked before modifications to an existing service request are applied.
• UPDATE_SERVICEREQUEST_POST — Post-processing hook that runs after an existing service request has been updated.

All four are declared as internal procedures and are driven by the parent Service Request processing routine rather than called directly by end users.

Tables Accessed

The ETRM extract for this package lists no tables referenced via APPS synonyms. This is consistent with its role as a hook layer: the pre and post procedures primarily coordinate timing, validation, and status signalling around the base Service Request operations rather than performing direct SQL against service request tables. Any persistent data manipulation against the underlying CS service request entities is the responsibility of the base API that invokes these hooks. Consumers integrating with this package should therefore not assume that its routines commit or roll back service request rows.

Usage Notes

Because CS_SERVICEREQUEST_IUHK is an internal user hook package, it is not intended as a standalone, directly callable API. It is invoked implicitly by the Service Request create and update flows — typically from the Service Request forms and from concurrent or programmatic processes that call the standard CS service request APIs. The ETRM metadata records that the package is referenced by one other package, confirming it is a downstream dependency of a parent processing module rather than an entry point in its own right.

For customizations and extensions, the supported pattern is to extend behavior through the documented hook mechanisms and Oracle-supported personalization or dependent objects, not to modify this package directly, which would invalidate the APPS schema and place the system in an unsupported state. Note also the package header vintage (120.1, dated 2006), indicating the interface has been stable across the 12.1.1 and 12.2.2 code lines. Developers who locate CREATE_SERVICEREQUEST_PRE while tracing a create operation should treat it as a lifecycle callback whose OUT status must be honoured, and should route any new business requirements through officially supported extension points.