Results for “status_f_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_RUN_REQ_PP_ACTIONS is a transactional table in the APPLSYS schema of Oracle E-Business Suite, owned by the FND - Application Object Library product. Its documented purpose is to store post request processing actions — that is, the deferred actions that the Concurrent Manager executes against a parent concurrent request after the request itself has completed or reached a defined state. These actions typically include operations such as copying or re-running a request, setting a request set program's status flags, and applying stored arguments to a follow-on program invocation.

The table is tightly coupled to the concurrent processing infrastructure. Every row is anchored to a parent concurrent request through PARENT_REQUEST_ID, and to a request set program definition through the composite of SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_PROGRAM_ID. In a heuristic Data Vault classification, FND_RUN_REQ_PP_ACTIONS is best modeled as a link, because it resolves a many-to-many association between concurrent requests and request set programs while carrying descriptive attributes of its own. This classification is a modeling suggestion only; the physical object is a standard third-normal-form Oracle EBS table.

Key Information Stored

The primary key FND_RUN_REQ_PP_ACTIONS_PK is a composite of five columns: PARENT_REQUEST_ID, REQUEST_SET_PROGRAM_ID, SET_APPLICATION_ID, REQUEST_SET_ID, and SEQUENCE. The first column, PARENT_REQUEST_ID, is the foreign key to FND_CONCURRENT_REQUESTS and identifies the request whose post-processing is being governed. REQUEST_SET_PROGRAM_ID, SET_APPLICATION_ID, and REQUEST_SET_ID together form the foreign key to FND_REQUEST_SET_PROGRAMS, identifying which member program of a request set is affected. SEQUENCE orders the actions within the parent request.

ACTION_TYPE determines the nature of the post request processing action to be performed. The status flags STATUS_S_FLAG, STATUS_W_FLAG, and STATUS_F_FLAG record the status conditions (success, warning, failure) under which the action applies. PROGRAM_APPLICATION_ID and PROGRAM_ID identify the concurrent program to be executed, while ARGUMENTS and the ten positional columns ARGUMENT1 through ARGUMENT10 supply the runtime parameters passed to that program. NUMBER_OF_COPIES governs how many instances are spawned. ORIG_SYSTEM and ORIG_SYSTEM_ID capture the originating system reference, with ORIG_SYSTEM_ID joining to HZ_ORIG_SYSTEMS_B. NLS_LANGUAGE and OPS_INSTANCE support multilingual and multi-node semantics respectively.

Common Use Cases and Queries

Functionally, this table is queried when diagnosing why a concurrent request set spawned follow-on programs, when auditing the sequence and arguments of post-processing actions, or when reconstructing the execution chain after a request completes. A typical diagnostic query joins the actions to their parent request to view the ordering and target program:

• Listing actions for a parent request: SELECT action_type, sequence, program_id, program_application_id FROM fnd_run_req_pp_actions WHERE parent_request_id = :req_id ORDER BY sequence;
• Resolving the target concurrent program name by joining PROGRAM_APPLICATION_ID and PROGRAM_ID to FND_CONCURRENT_PROGRAMS.
• Joining to FND_REQUEST_SET_PROGRAMS to identify the request set member that triggered the action.
• Auditing argument usage across a batch of requests by selecting ARGUMENT1 through ARGUMENT10 alongside PARENT_REQUEST_ID.
• Reporting on status-flag behavior to determine which outcomes propagate follow-on work.

These queries are most valuable to concurrent processing administrators and to developers troubleshooting request set behavior in both 12.1.1 and 12.2.2 environments, since the object's documented structure is stable across those releases.

Related Objects

The most significant related objects derive from the documented foreign key relationships:

• FND_CONCURRENT_REQUESTS — referenced via PARENT_REQUEST_ID; the parent request record for each action.
• FND_REQUEST_SET_PROGRAMS — referenced via SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_PROGRAM_ID; defines the request set member the action applies to.
• HZ_ORIG_SYSTEMS_B — referenced via ORIG_SYSTEM_ID; the origin system register in Oracle Trading Community Architecture.
• FND_CONCURRENT_PROGRAMS — implied by PROGRAM_APPLICATION_ID and PROGRAM_ID; identifies the executable program.
• FND_REQUEST_SETS — the parent request set definition that groups member programs.
• FND_CONCURRENT_PROGRAM_SERIAL and FND_CONCURRENT_WORKER_REQUESTS — commonly joined when tracing dispatched post-processing work.