Search Results bis_schedule_preferences

Overview

BIS_SCHEDULE_PREFERENCES is a table in the BIS schema (Applications BIS product) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores user-level scheduling preferences that drive how scheduled reporting or delivery jobs are configured, rendered, and dispatched through the BIS scheduling infrastructure. The table acts as a personalization layer: each row ties a specific user to a scheduling request, a plug (a registered KPI or report definition), a request type, and presentation attributes such as the graph type and title associated with the delivered output.

From a Data Vault modeling perspective, the mined FK structure classifies this object heuristically as standalone. This suggests it functions as a self-contained satellite-like record keyed to a user and a plug, rather than acting as a pure hub or a junction between two business entities. Its grain is essentially "one preference configuration per schedule, user, and plug combination," which is consistent with a satellite attached to a user/plug business key. The single documented foreign key (PLUG_ID to BSC_USER_KPILIST_PLUGS) reinforces this interpretation.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• SCHEDULE_ID — Identifies the schedule preference record; the primary surrogate key candidate for the row.
• USER_ID — The owning user; a strong business-key candidate that scopes all preferences to a specific individual.
• PLUG_ID — Foreign key to BSC_USER_KPILIST_PLUGS; identifies the registered plug (KPI/report) the preference applies to.
• REQUEST_TYPE — Classifies the type of scheduling or concurrent request being configured.
• TITLE — The display title applied to the scheduled output or graph.
• GRAPH_TYPE — Specifies the chart/graph rendering style for the delivered content.
• FILE_ID — References an associated file artifact used by the schedule.
• EXTERNAL_SOURCE_ID — Carries the identifier of an external source system supplying the scheduled data.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the preference was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent change and session context.

The surrogate key is SCHEDULE_ID; the natural business key is best understood as the combination of USER_ID and PLUG_ID. No unique index is documented in the supplied metadata, so cardinality should be verified against the live instance.

Common Use Cases and Queries

Typical usage centers on diagnosing why a scheduled report or KPI delivery renders differently for one user than another. Administrators query this table to enumerate a user's active schedule preferences:

• SELECT schedule_id, user_id, plug_id, request_type, title, graph_type FROM bis.bis_schedule_preferences WHERE user_id = :p_user_id;
• Joining to the plug list to resolve human-readable plug names: ... FROM bis.bis_schedule_preferences p JOIN bsc.bsc_user_kpilist_plugs k ON p.plug_id = k.plug_id;
• Auditing recent changes: filter on last_update_date and last_updated_by to trace who altered a rendering preference.
• Reporting on distribution of graph_type or request_type across the user base to standardize output formats.

Because the table is standalone and user-scoped, it is commonly extracted into reporting marts for dashboard personalization analytics and troubleshooting delivery failures.

Related Objects

• BSC_USER_KPILIST_PLUGS — the documented parent of BIS_SCHEDULE_PREFERENCES.PLUG_ID; supplies plug definitions and KPI list membership. This is the primary join path.
• FND_USER — resolves USER_ID to user names and responsibilities for reporting.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — link scheduling behavior to concurrent program executions.
• BIS scheduling and delivery engine tables that consume SCHEDULE_ID, REQUEST_TYPE, and FILE_ID at dispatch time.

These relationships make the table a focal point for personalization, scheduling, and delivery troubleshooting within the BIS module.