Search Results fnd_run_req_pp_actions




Overview
Explore in AI Chat

Overview

The FND_RUN_REQ_PP_ACTIONS table is a core technical table within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a persistent queue for managing post-processing actions associated with concurrent request sets. When a request set completes, the system may need to perform specific follow-up tasks, such as sending notifications or triggering subsequent processes. This table stores the definitions of those pending actions, ensuring they are tracked and executed by the appropriate post-processing engine. Its role is critical for the automated workflow and chaining of business processes initiated through the concurrent manager.

Key Information Stored

The table's structure is defined by its composite primary key, which precisely identifies a specific action within the context of a completed request set. The key columns are PARENT_REQUEST_ID, REQUEST_SET_PROGRAM_ID, SET_APPLICATION_ID, REQUEST_SET_ID, and SEQUENCE. These fields collectively link the action to the original parent concurrent request (PARENT_REQUEST_ID) and the specific program (REQUEST_SET_PROGRAM_ID) within a defined request set (REQUEST_SET_ID from a specific SET_APPLICATION_ID). The SEQUENCE column orders multiple actions. While the provided metadata does not list non-key columns, typical data would include the action type (e.g., 'SEND_MAIL'), action parameters, status flags, and timestamps to manage the execution lifecycle of the post-processing task.

Common Use Cases and Queries

This table is primarily used for administrative monitoring and troubleshooting of the post-request processing subsystem. Common scenarios include diagnosing why a post-completion email notification was not sent or investigating hung workflow steps after a request set finishes. A typical diagnostic query would join to the main concurrent requests table to examine pending actions for a specific request.

  • Sample Query to Find Pending Actions:
    SELECT rrpa.* FROM apps.FND_RUN_REQ_PP_ACTIONS rrpa, apps.FND_CONCURRENT_REQUESTS fcr WHERE rrpa.parent_request_id = fcr.request_id AND fcr.request_id = &REQUEST_ID;
  • Reporting Use Case: Generating a report of all incomplete post-processing actions across the system to identify potential stalls in business process automation.

Related Objects

The table maintains strict referential integrity through documented foreign key relationships with core concurrent processing tables. These relationships are essential for understanding its data lineage and for constructing accurate joins in queries.

  • FND_CONCURRENT_REQUESTS: Links via FND_RUN_REQ_PP_ACTIONS.PARENT_REQUEST_ID = FND_CONCURRENT_REQUESTS.REQUEST_ID. This ties each action to the master concurrent request record.
  • FND_REQUEST_SET_PROGRAMS: Links via a composite foreign key: FND_RUN_REQ_PP_ACTIONS.SET_APPLICATION_ID = FND_REQUEST_SET_PROGRAMS.APPLICATION_ID, FND_RUN_REQ_PP_ACTIONS.REQUEST_SET_ID = FND_REQUEST_SET_PROGRAMS.REQUEST_SET_ID, and FND_RUN_REQ_PP_ACTIONS.REQUEST_SET_PROGRAM_ID = FND_REQUEST_SET_PROGRAMS.REQUEST_SET_PROGRAM_ID. This relationship connects the action to the specific program definition within the request set's structure.