Search Results bis_scheduler




Overview
Explore in AI Chat

Overview

BIS_SCHEDULER is a repository table within the Oracle E-Business Suite Applications BIS product family. Its documented description is simply "BIS Scheduler table," reflecting its role as a persistence store for scheduled graph and KPI rendering definitions used by the BIS (Business Intelligence System) framework. In Oracle EBS 12.1.1 and 12.2.2, this table holds the configuration that drives scheduled generation of graphs, report regions, and associated concurrent requests. Each row represents a single scheduled item, tying together a user, a plug (the KPI source definition), a function or responsibility context, and the parameters required to render a cached graph.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone. Because the table has no incoming foreign keys other than the outbound reference to BSC_USER_KPILIST_PLUGS, it is best treated as a hub-like entity anchored by its own unique business key (SCHEDULE_ID), rather than as a link or dependent satellite. Modelers should note that the "Not implemented in this database" annotation indicates the table may be absent or unused in certain EBS installations, so existence checks against ALL_TABLES are advisable before querying.

Key Information Stored

The table is owned by BIS and contains 17 documented columns in the 12.1.1 ETRM schema. The most significant are:

  • SCHEDULE_ID — surrogate primary key and the sole unique business-key candidate (index BIS_SCHEDULER_U1). Uniquely identifies each scheduled item.
  • PLUG_ID — foreign key to BSC_USER_KPILIST_PLUGS, identifying the KPI plug or data source that the schedule renders.
  • USER_ID — the user who owns or receives the scheduled output.
  • RESPONSIBILITY_ID — the responsibility context under which the schedule executes, controlling access to functions and data.
  • FUNCTION_NAME — the application function invoked when the schedule runs.
  • TITLE — the display name of the scheduled graph or report.
  • GRAPH_TYPE — the rendering type (for example, bar, line, or pie) for the graph output.
  • FILE_ID — reference to the file or document that stores the rendered or cached output.
  • CACHED_GRAPH — stored representation of the last-rendered graph, enabling fast redisplay.
  • CONCURRENT_REQUEST_ID — links the schedule to its Oracle Concurrent Manager request, supporting submission and status tracking.
  • REPORT_REGION_CODE — identifies the report region where output is displayed.
  • PARAMETER_STRING — serialized parameters passed to the underlying function or graph generator.
  • Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — capture who created and last modified each row.

Common Use Cases and Queries

The predominant use case is auditing and troubleshooting scheduled BIS graphs. Administrators may query all schedules for a given user or responsibility, or trace a failed schedule back to its concurrent request.

  • Retrieve a user's active schedules: SELECT schedule_id, title, graph_type, function_name FROM bis_scheduler WHERE user_id = :user_id;
  • Join to the plug definition to understand the KPI source: SELECT s.schedule_id, s.title, p.* FROM bis_scheduler s JOIN bsc_user_kpilist_plugs p ON s.plug_id = p.plug_id;
  • Correlate scheduled output with Concurrent Manager: SELECT schedule_id, title, concurrent_request_id FROM bis_scheduler WHERE concurrent_request_id IS NOT NULL;
  • Find stale or missing cached graphs: SELECT schedule_id, title FROM bis_scheduler WHERE cached_graph IS NULL;

These patterns support migration validation, cleanup of orphaned schedules, and performance tuning of cached rendering.

Related Objects

Because the metadata classifies BIS_SCHEDULER as standalone, related objects above rely on logical (non-enforced) relationships except for the single documented FK to BSC_USER_KPILIST_PLUGS.