Search Results delete_set_all

Overview

BIS_CREATE_REQUESTSET is an Oracle EBS Applications (APPS) PL/SQL package that belongs to the Oracle Business Intelligence System (BIS) product family. Its principal business function is the programmatic construction and maintenance of Oracle Concurrent Manager request sets from sets of Oracle E-Business Suite objects. A request set is a collection of concurrent programs that are submitted together and executed in a defined sequence with defined stage and dependency relationships. BIS_CREATE_REQUESTSET provides the internal engine that translates BIS object definitions, dependencies, and property metadata into the underlying FND_REQUEST_GROUPS / request-set structures so that collections of concurrent programs can be generated, staged, executed, and subsequently cleaned up without manual configuration in the Concurrent Programs form.

The package is registered in the APPS schema with status VALID and is classified as OTHER in the ETRM API classification (that is, it is not a published end-user API). Its dependencies show it relies on SYS.STANDARD and is referenced by a number of other BIS components, including BIS_BIA_RSG_LOG_MGMNT, BIS_COLL_RS_HISTORY, BIS_MV_REFRESH, and BIS_TRUNCATE_EMPTY_MV_LOG_PKG. This dependency profile indicates that the package is a core utility within the BIS collections and materialized-view refresh framework rather than a standalone user-facing utility.

Key Procedures and Functions

The package exposes 35 documented procedures and functions. The primary groupings are as follows.

• Set lifecycle: CREATE_SET_ALL builds a complete request set from BIS object definitions; DELETE_SET_ALL removes the generated request set and its associated objects; WRAPUP performs final consolidation of the request set after construction.
• Object membership: ADD_OBJECT_TO_SET adds an individual BIS object to a request set; REMOVE_EMPTY_STAGES prunes stages that contain no runnable objects; OBJECT_HAS_DATA and IS_STAGE_EMPTY test whether an object or stage contains data and therefore should be retained.
• Sequence and identification helpers: GET_STAGE_SEQUENCE, GET_MAX_PROG_SEQUENCE, and GET_STATS_STAGE_SEQUENCE return ordering information used to arrange stages and programs; GET_OBJECT_OWNER resolves the owning schema of a BIS object; SET_IN_GROUP marks an object as belonging to a given group.
• Dependency and staging support: DEPENDENCY_EXIST checks whether a dependency relationship exists between objects; ADD_FIRST_LAST_STAGES inserts the terminal stages that bracket execution.
• Option and object maintenance: CREATE_RS_OPTION and DELETE_RS_OPTION manage request-set options; CREATE_RS_OBJECTS and DELETE_RS_OBJECTS manage the underlying request-set objects.
• Concurrent entry points: PREPARATION_CONC and FINALIZATION_CONC are the concurrent-program entry points that perform the pre-execution preparation and post-execution finalization of the request set.

Tables Accessed

BIS_CREATE_REQUESTSET reads and writes a mix of BIS configuration tables and standard Oracle Application Object Library (FND) tables, accessed through APPS synonyms.

• BIS staging and definition tables: BIS_BIA_RSG_IMPL_FLAG_TEMP, BIS_BIA_RSG_STAGE_OBJECTS, BIS_OBJ_DEPENDENCY, BIS_OBJ_PROG_LINKAGES, and BIS_OBJ_PROPERTIES supply the object definitions, program linkages, dependencies, and implementation flags from which request sets are built.
• Request-set output tables: BIS_REQUEST_SET_OBJECTS and BIS_REQUEST_SET_OPTIONS store the generated request-set objects and options, while BIS_RS_PROG_RUN_HISTORY and BIS_RS_STAGE_RUN_HISTORY capture execution history at program and stage level.
• FND reference tables: FND_APPLICATION, FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS, FND_FORM_FUNCTIONS, FND_ORACLE_USERID, and FND_REQUEST_GROUPS provide application, concurrent program, request, function, user, and request-group metadata used to resolve and register the request set within the Concurrent Manager framework.

Usage Notes

BIS_CREATE_REQUESTSET is an internal BIS utility and is not intended for direct invocation from custom code. It is normally driven by the BIS Collections administration flows and by the concurrent programs whose entry points (PREPARATION_CONC and FINALIZATION_CONC) are defined inside the package. Administrators typically trigger request-set creation indirectly through the Collections or materialized-view refresh setup, and the package is also called from sibling packages such as BIS_MV_REFRESH, BIS_COLL_RS_HISTORY, BIS_BIA_RSG_LOG_MGMNT, and BIS_TRUNCATE_EMPTY_MV_LOG_PKG. Because the package manipulates Concurrent Manager metadata directly, direct calls should be confined to Oracle-supported BIS processes, and any modification or extension should be validated against the documented dependency and staging logic before use in a production environment.