Search Results g_transfer_timeout




Overview
Explore in AI Chat

Overview

QP_JAVA_ENGINE_UTIL_PUB is a public PL/SQL utility package in the Oracle E-Business Suite Order Management / Advanced Pricing (QP) module. Its purpose is to provide a bridge between the PL/SQL tier of EBS and the Java-based pricing engine servlet used for Oracle Advanced Pricing calculations. When the pricing engine is deployed as a Java servlet rather than executed entirely in the database, application code needs a controlled way to discover the engine, verify its availability, and dispatch requests to it over HTTP. QP_JAVA_ENGINE_UTIL_PUB encapsulates that integration logic, including the construction of the parameter string that carries session context (database connect string, user ID, responsibility ID, login ID, org ID, application short name, ICX session ID, and call type) to the servlet, and the interpretation of the returned status code and status text.

The package is compiled with AUTHID CURRENT_USER and exposes a small, focused API. It also centralizes operational safeguards such as the transfer timeout (G_TRANSFER_TIMEOUT, default 60), an HTTP newline character sourced from FND_GLOBAL, and profile-driven polling controls (QP_JPE_MAX_STAT_REQUESTS and QP_JPE_STAT_REQUEST_INTERVAL) that govern how long and how frequently the caller waits for asynchronous engine responses. The package header identifies its version lineage through the $Header comment (QPXJUTLS.pls) and is classified as a PUB interface in ETRM, meaning it is intended for supported external invocation rather than internal-only use.

Key Procedures and Functions

ETRM documents six callable units in this package. Their responsibilities are as follows.

  • JAVA_ENGINE_INSTALLED — Returns an indicator ('Y' or 'N') stating whether the Java pricing engine component is installed in the environment. Callers use this as a precondition check before attempting any request dispatch.
  • JAVA_ENGINE_RUNNING — Returns an indicator ('Y' or 'N') stating whether the Java engine is currently running and reachable. This distinguishes a deployment that exists from one that is actually available at request time.
  • GET_ENGINE_URL — Returns the URL of the servlet where the Java Engine is deployed and running. This value is used to build the HTTP endpoint for request dispatch.
  • SEND_JAVA_ENGINE_REQUEST — Submits a request to the Java engine. It accepts an input parameter string (p_url_param_string) and returns a return status and a return status text. This is the primary entry point searched for by users looking up "send_java_engine_request".
  • SEND_JAVA_REQUEST — A companion dispatcher for issuing a Java request through the same HTTP infrastructure, used where the caller requires the lower-level send behavior without the higher-level engine request assembly.

Note that the excerpt truncates the parameter list of SEND_JAVA_ENGINE_REQUEST after the OUT NOCOPY status text; only the documented first three parameters are stated above, and no additional parameters are asserted here.

Tables Accessed

The package does not read or write application business tables. Its documented dependencies are on infrastructure objects exposed through APPS synonyms: UTL_HTTP for outbound HTTP calls to the servlet, UTL_TCP for the underlying TCP transport, DBMS_LOCK for serialization (consistent with the G_QP_INT_TABLES_LOCK constant used to guard concurrent access to pricing interface tables), DBMS_UTILITY for utility services, and PLITBLM for PL/SQL table (associative array) manipulation. Because no QP_% interface or pricing tables are directly referenced by this package, data persistence is handled by the packages that consume it; QP_JAVA_ENGINE_UTIL_PUB remains a transport and control utility.

Usage Notes

QP_JAVA_ENGINE_UTIL_PUB is referenced by 26 other packages, indicating it sits beneath higher-level pricing APIs rather than being called directly in most business flows. Typical invocation patterns include: Oracle Forms or OAF pages within Advanced Pricing that trigger engine-based price calculation; concurrent programs and concurrent-program wrappers that batch pricing requests; and custom PL/SQL extensions to EBS that need to reach the Java pricing engine. When invoking SEND_JAVA_ENGINE_REQUEST, callers must supply the assembled parameter string containing the session context values enumerated in the package constants (dbc, UserId, RespId, RespApplId, LoginId, OrgId, AppShortName, CallType, Action, IcxSessionId) and must check x_return_status and x_return_status_text before using any downstream result. Because the engine call is asynchronous, callers should honor the profile-controlled polling limits (QP_JPE_MAX_STAT_REQUESTS and QP_JPE_STAT_REQUEST_INTERVAL) and the 60-second transfer timeout to avoid runaway waits. Environments where the engine is not installed or not running should be filtered out using JAVA_ENGINE_INSTALLED and JAVA_ENGINE_RUNNING before dispatch to prevent avoidable HTTP failures.