Search Results set_request_id

Overview

BIS_RS_RUN_CHILD_REQIDS_V is a reporting and integration view within the Oracle E-Business Suite BIS (Applications BIS) product family. Its purpose is to consolidate request identifiers for child concurrent requests that were spawned from a parent request within the BIS run-history framework. The view exposes a uniform three-column projection of request identifiers drawn from multiple BIS run-history tables, allowing a calling process or report to resolve the relationship between a parent request and the set of child requests it launched.

In the ETRM metadata for Oracle EBS 12.2.2, the object is documented as a view belonging to the BIS module. The metadata notes that it is "Not implemented in this database," which indicates that the view definition is catalogued in ETRM but the database instance from which the metadata was harvested did not contain a deployed copy. This is a documentation artifact rather than an indication that the view is universally absent; the view remains part of the BIS schema definition. The user search term "set_request_id" reflects the central role this column plays in the view, since it is the field that ties atomic request IDs back to the originating set-level request.

Underlying Base Objects

The view text documents a UNION of three source tables, each contributing the same three projected expressions: ID, VALUE, and SRID. The documented base objects are:

• BIS_RS_PROG_RUN_HISTORY — contributes REQUEST_ID as ID and VALUE, and SET_REQUEST_ID as SRID for program run-history rows.
• BIS_RS_STAGE_RUN_HISTORY — contributes REQUEST_ID as ID and VALUE, and SET_REQUEST_ID as SRID for stage run-history rows.
• BIS_RS_RUN_HISTORY — contributes REQUEST_ID as ID, VALUE, and SRID, meaning the request ID serves as its own set identifier for rows originating from this table.

The view is therefore a union over the program, stage, and general run-history tables. The ETRM metadata records no further documented base objects, and the owner is not specified. The UNION (distinct) semantics imply that duplicate (ID, VALUE, SRID) triples across the three sources are collapsed into a single row.

Key Columns

• ID — the request identifier of the child or individual run-history entry. In all three branches it maps to REQUEST_ID.
• VALUE — a second projection of the same REQUEST_ID, presented for compatibility with generic value-lookup consumers that expect an ID/VALUE pair.
• SRID — the set request identifier (SET_REQUEST_ID for the program and stage history branches, REQUEST_ID for the general history branch). This is the column that answers the "set_request_id" lookup and links each child row to its parent set request.

Common Use Cases and Queries

Typical usage is to enumerate all child request IDs associated with a given set request, or to confirm that a specific request participates in a set. A representative query resolves children for a known set request:

• SELECT ID, VALUE, SRID FROM BIS_RS_RUN_CHILD_REQIDS_V WHERE SRID = :set_request_id;
• SELECT ID, VALUE, SRID FROM BIS_RS_RUN_CHILD_REQIDS_V WHERE ID = :request_id; — to determine the set request to which an individual request belongs.
• SELECT SRID, COUNT(*) FROM BIS_RS_RUN_CHILD_REQIDS_V GROUP BY SRID; — to count children per set request.

Because the view normalizes three heterogeneous history tables into a single ID/VALUE/SRID surface, it is suited to integration code that must treat program, stage, and general run-history requests uniformly when walking a parent-child request tree.