Search Results bis_scheduler_u1

Overview

BIS.BIS_SCHEDULER is a transactional table in the Business Intelligence System (BIS) schema of Oracle E-Business Suite, holding the definition and runtime state of scheduled reports and graphs executed through the Self-Service Web Applications (SSWA) framework. Each row represents one scheduled report request — the plug (report definition) that is being run, the user and responsibility under which it executes, the parameters supplied, and the resulting concurrent request or file output. The table is the persistence layer that allows the BIS Scheduler component to re-execute a report definition without user intervention and to cache generated graph images.

The object is owned by BIS and is classified under FND design data as BIS.BIS_SCHEDULER. It is stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and all of its indexes reside in APPS_TS_TX_IDX. From a heuristic Data Vault modeling perspective, the table is classified as standalone, meaning it was not mined as a hub, link, or satellite; it functions as an independent master-ish record set whose only documented foreign-key relationship is a reference to the KPI list plug definitions. Its primary key, SCHEDULE_ID, is the natural hub candidate if the table were ever normalized further.

Key Information Stored

The table contains 17 documented columns. The most operationally significant are:

• SCHEDULE_ID (NUMBER) — surrogate primary key, uniquely identifying each scheduled report instance. It is enforced by the unique index BIS_SCHEDULER_U1 in APPS_TS_TX_IDX.
• PLUG_ID (NUMBER) — identifies the SSWA plug, and is the documented foreign key to BSC_USER_KPILIST_PLUGS, tying a schedule to a KPI list plug.
• USER_ID (VARCHAR2(80)) — the SSWA userid that owns the schedule.
• RESPONSIBILITY_ID (VARCHAR2(80)) — the responsibility context under which the report runs, important for security and row filtering.
• FUNCTION_NAME (VARCHAR2(480)) — the report function invoked, effectively the report definition reference.
• TITLE (VARCHAR2(80)) — user-facing name of the scheduled report.
• REPORT_REGION_CODE (VARCHAR2(80)) — the AK region code identifying the report region rendered.
• PARAMETER_STRING (VARCHAR2(4000)) — the parameter set with which the report was last executed, encoding the run-time filter values.
• CONCURRENT_REQUEST_ID (NUMBER) — the concurrent request that produced the output, linking the schedule to the concurrent manager.
• GRAPH_TYPE (NUMBER) and FILE_ID (NUMBER) — the graph rendering type and the file identifier for generated output.
• CACHED_GRAPH (LONG) — cached graph image content.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns tracking audit actors.

Common Use Cases and Queries

Typical usage centres on auditing and troubleshooting scheduled BIS reports. A DBA or support analyst may list all schedules for a user, resolve a schedule to its concurrent request, or inspect the parameters used in the most recent run. Representative query patterns:

• List schedules for a user: SELECT SCHEDULE_ID, TITLE, FUNCTION_NAME, RESPONSIBILITY_ID FROM BIS.BIS_SCHEDULER WHERE USER_ID = :user;
• Resolve a schedule to its plug and report: join PLUG_ID to BSC_USER_KPILIST_PLUGS, filtering by SCHEDULE_ID or by USER_ID/FUNCTION_NAME (which is served by the non-unique index BIS_SCHEDULER_N3).
• Inspect execution history: query CONCURRENT_REQUEST_ID and REPORT_REGION_CODE to confirm which concurrent request ran a given schedule and which report region was rendered.
• Reproduce output: read PARAMETER_STRING to replay the exact filters that produced a cached graph (CACHED_GRAPH / FILE_ID).

Related Objects

The following objects are most significant to this table:

• BSC_USER_KPILIST_PLUGS — referenced on PLUG_ID, defining the KPI list plug a schedule is based on. This is the only documented foreign-key relationship.
• FND_CONCURRENT_REQUESTS — joins on CONCURRENT_REQUEST_ID to obtain request status, phase, and output.
• FND_USER — joins on CREATED_BY / LAST_UPDATED_BY for the audit actor, and provides the SSWA user dimension.
• FND_RESPONSIBILITY — the responsibility context corresponding to RESPONSIBILITY_ID.
• BIS_SCHEDULER_U1, BIS_SCHEDULER_N2, BIS_SCHEDULER_N3 — supporting indexes on SCHEDULE_ID, (USER_ID, PLUG_ID), and (USER_ID, FUNCTION_NAME) respectively.

The table itself is queried through the SELECT listed in the ETRM documentation, which exposes all 17 columns for reporting and diagnostic use.