Results for “fnd_request_set_programs”

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

Overview

FND_REQUEST_SET_PROGRAMS is a core Application Object Library (FND) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the individual concurrent programs belonging to a request set. A request set is a collection of concurrent programs that Oracle EBS executes sequentially or in parallel as a single submitted unit, and this table stores the membership, ordering, stage assignment, and runtime characteristics of each program within that set. The table resides in the APPLSYS schema, is documented as VALID, and is described as "Reports within report sets." Every row represents one concurrent program placed into one stage of one request set.

Because the table is a child of FND_REQUEST_SET_STAGES and FND_CONCURRENT_PROGRAMS and is itself referenced by execution-history and argument tables, the ETRM relationship model classifies it as satellite-leaning. For Data Vault modeling purposes, this suggests treating it as a satellite attached to the request set and stage hubs, capturing the descriptive and operational attributes (sequence, printer, criticality) that describe the program-to-set linkage rather than as an independent hub.

Key Information Stored

The table carries the 20 documented columns, of which the following are most significant:

• SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID, REQUEST_SET_PROGRAM_ID — the identifying columns. The surrogate primary key is FND_REQUEST_SET_PROGRAMS_PK over (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_PROGRAM_ID).
• SEQUENCE — the execution order of the program within its stage.
• PROGRAM_APPLICATION_ID, CONCURRENT_PROGRAM_ID — the foreign key to FND_CONCURRENT_PROGRAMS identifying the actual program to run.
• CRITICAL — flag indicating whether failure of this program aborts the rest of the request set.
• NUMBER_OF_COPIES — how many times the program is submitted.
• PRINTER, PRINT_STYLE — output routing and print formatting, referencing FND_PRINTER and FND_PRINTER_STYLES.
• SAVE_OUTPUT_FLAG — controls retention of the report output.
• NLS_LANGUAGE, NLS_TERRITORY — session language and territory for the program run.
• CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, LAST_UPDATE_DATE — standard audit columns referencing FND_USER and FND_LOGINS.
• ZD_EDITION_NAME — the editioning column supporting online patching in 12.2.2.

Business-key candidates are given by the unique indexes: FND_REQUEST_SET_PROGRAMS_U1 (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID, SEQUENCE, ZD_EDITION_NAME) and FND_REQUEST_SET_PROGRAMS_U2 (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_PROGRAM_ID, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical scenarios include listing the programs inside a request set, verifying execution order, and joining to program definitions for reporting.

• List programs in a set, ordered by stage and sequence:

SELECT rsp.REQUEST_SET_ID, rsp.REQUEST_SET_STAGE_ID, rsp.SEQUENCE, cp.CONCURRENT_PROGRAM_NAME, rsp.CRITICAL, rsp.NUMBER_OF_COPIES FROM FND_REQUEST_SET_PROGRAMS rsp, FND_CONCURRENT_PROGRAMS cp WHERE rsp.PROGRAM_APPLICATION_ID = cp.APPLICATION_ID AND rsp.CONCURRENT_PROGRAM_ID = cp.CONCURRENT_PROGRAM_ID AND rsp.REQUEST_SET_ID = :set_id ORDER BY rsp.REQUEST_SET_STAGE_ID, rsp.SEQUENCE;

• Identify critical programs that can abort a set.
• Audit printer and print-style assignments across sets.
• Trace request-set membership against FND_RUN_REQUESTS to reconcile submitted executions.

Related Objects

• FND_REQUEST_SET_STAGES — parent stage definition; joined on SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID.
• FND_CONCURRENT_PROGRAMS — the program definition; joined on PROGRAM_APPLICATION_ID, CONCURRENT_PROGRAM_ID.
• FND_REQUEST_SET_PROGRAM_ARGS — arguments for each program; joined on APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_PROGRAM_ID.
• FND_RUN_REQUESTS — runtime execution records; joined on SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_PROGRAM_ID.
• FND_RUN_REQ_PP_ACTIONS — post-processing actions; joined on SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_PROGRAM_ID.
• FND_PRINTER and FND_PRINTER_STYLES — output routing references.
• FND_USER and FND_LOGINS — audit references.