Search Results search_requests

Overview

APPS.FND_RT_REQUEST is an Oracle E-Business Suite utility package that belongs to the concurrent processing and regression-testing infrastructure of the FND (Foundation) product. Its name reflects its role in the runtime ("RT") domain: it manages records that associate a regression test identifier with the concurrent requests spawned by that test, providing the plumbing used to track, enumerate, and retrieve child requests generated during an automated test execution. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the calling schema rather than the definer, a convention typical of internal EBS utilities that are invoked from within the APPS environment. The header comment (originally tracked as AFRTREQS.pls) dates the package to 1999, indicating that it is a long-standing, stable component of the EBS foundation layer that has been carried forward into release 12.1.1 and 12.2.2 without functional change. Its principal purpose is to populate and drain a staging table (FND_RT_REQUESTS) that acts as a work queue of request IDs tied to a given test run.

Key Procedures and Functions

• GET_TEST_ID — Obtains a unique test identifier suitable for distinguishing one regression test from another. It relies on the FND_RT_REQUESTS_S sequence to generate the unique value, returning it through an IN OUT parameter.
• LOG_REQUEST — Inserts a new record into the FND_RT_REQUESTS table for a supplied test identifier and request identifier, recording that a particular concurrent request is associated with a given test.
• SEARCH_REQUESTS — The central procedure and the object of the "search_requests" query. Given a test identifier and a timeout, it scans the FND_CONCURRENT_REQUESTS table for all child requests belonging to the parents registered under that test, and inserts the discovered child requests into FND_RT_REQUESTS. In effect, it expands a test run into the complete set of concurrent requests it produced.
• GET_REQUEST — Retrieves the next request identifier for a given test identifier and then removes that record from FND_RT_REQUESTS, implementing a destructive-read (queue-drain) pattern that lets a caller iterate through the collected requests exactly once.

Tables Accessed

• FND_RT_REQUESTS — The working table into which LOG_REQUEST and SEARCH_REQUESTS insert records and from which GET_REQUEST reads and deletes. It holds the test-to-request associations.
• FND_RT_REQUESTS_S — The sequence supplying unique test identifiers to GET_TEST_ID.
• FND_CONCURRENT_REQUESTS — The core concurrent request repository, read by SEARCH_REQUESTS to identify child requests for the parents associated with a test run.
• DBMS_LOCK — Referenced to provide serialization or synchronization around the shared staging table, ensuring concurrent test processes do not corrupt the queue.
• DUAL — Used for single-row sequence and utility operations.

Usage Notes

FND_RT_REQUEST is an internal infrastructure package rather than a public business API. It is typically invoked indirectly by regression-test harnesses and internal EBS test utilities, and the ETRM metadata notes that it is referenced by one other package. Because SEARCH_REQUESTS depends on the FND_CONCURRENT_REQUESTS hierarchy and an explicit timeout, callers are expected to invoke it after the parent requests of a test run have had time to spawn children. GET_REQUEST's delete-on-read behavior means a test identifier's queue is consumed as it is processed; callers should therefore avoid invoking it from multiple concurrent sessions unless coordinated. For release 12.1.1 and 12.2.2, the package remains an APPS-owned, CURRENT_USER-authenticated utility with no documented public customization surface, and it should not be modified or called directly from production forms or concurrent programs.