Search Results g_sis_hdr_inserted

Overview

OKL_PRCTIMEOUT_PVT is a private (PVT) PL/SQL package in the Oracle Lease and Finance Management (OLFM/ETRM) module of Oracle E-Business Suite. It belongs to the APPS schema and is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the calling user rather than the definer. The package header identifies it as part of the stream interface processing infrastructure, indicated by the prefix "PRCTIMEOUT" (process timeout) and by the request-status constants declared within it.

The overriding business function of this package is to detect and handle timeouts or stalled processing associated with stream interface requests. Stream interfaces in OLFM support integrations where contract and lease data are loaded into the application through staging tables. The package defines a set of canonical request statuses used to track the lifecycle of such a request:

• G_SIS_HDR_INSERTED ('HDR_INSERTED') — the header row has been inserted into the interface.
• G_SIS_DATA_ENTERED ('DATA_ENTERED') — data was entered but processing has not yet begun.
• G_SIS_PROCESS_COMPLETE ('PROCESS_COMPLETE') — the request finished successfully.
• G_SIS_PROCESSING_FAILED ('PROCESSING_FAILED') — the request terminated with errors.
• G_SIS_PROCESSING_REQUEST ('PROCESSING_REQUEST') — the request is currently in progress.
• G_SIS_RET_DATA_RECEIVED ('RET_DATA_RE...') — return data has been received from the external or downstream process.

The constant G_SIS_PROCESS_COMPLETE corresponds to the "process_complete" condition that users commonly search for, and the package's logic centers on evaluating whether a request has reached that state within an expected timeframe.

Key Procedures and Functions

The package exposes a single documented program unit:

• REQUEST_TIME_OUT — This procedure is the functional core of the package. Its purpose is to evaluate whether a stream interface request has exceeded its allotted processing window and to act on that determination. It is the entry point that callers invoke to trigger the timeout check logic. The metadata does not document its parameter list, so signature details should be confirmed against the deployed source in the specific EBS release (12.1.1 or 12.2.2).

Supporting declarations include the exception G_EXCEPTION_HALT_VALIDATION, along with standard OLFM error-handling exceptions G_EXCEPTION_ERROR and G_EXCEPTION_UNEXPECTED_ERROR, and the token constants G_SQLERRM_TOKEN and G_SQLCODE_TOKEN used for formatted error messages. These indicate that REQUEST_TIME_OUT is expected to raise structured, translated errors through the standard OKL_API message framework.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

• OKL_STREAM_INTERFACES — This is the primary transactional table. It stores stream interface records together with their current request status. REQUEST_TIME_OUT reads this table to identify requests still in a processing state and to determine whether their elapsed time exceeds the threshold, then updates the status to reflect a timeout or failure condition.
• PLITBLM — This is an Oracle-supplied standard table (part of the FND/PLITBLM utility infrastructure) frequently used for PL/SQL message lookups and token substitution. Its presence confirms that the package retrieves and formats error or notification messages for the timeout condition.

Usage Notes

As a PVT (private) package, OKL_PRCTIMEOUT_PVT is not part of the public API surface and is not intended for direct customer invocation. It is referenced by no other documented packages, indicating that it is called internally, most likely from a concurrent program or a wrapper package that performs periodic monitoring of stream interface requests. The procedure REQUEST_TIME_OUT would typically be scheduled as part of a background process that periodically scans OKL_STREAM_INTERFACES for requests stalled in the PROCESSING_REQUEST state and marks or reports them as timed out.

Customizations should not call this package directly. Any extension of timeout behavior should instead be implemented through supported OLFM APIs or by adding a custom concurrent program that operates on the stream interface tables. When diagnosing issues in releases 12.1.1 or 12.2.2, confirm the exact compiled signature in the target instance, since the source header ($Header: OKLRPTOS.pls 115.2) reflects an early ETRM lineage and later patches may have altered the procedure's parameters.