Search Results external_source_id

Overview

BIS.BIS_SCHEDULE_PREFERENCES is a transactional configuration table in the Oracle E-Business Suite Business Intelligence System (BIS) schema. It persists the per-user and per-plug preferences that govern how scheduled Reports and KPI-based dashboards are defined, displayed, and re-executed within the SSWA (Self-Service Web Applications) framework. Each row captures a saved schedule definition — the report title, the request type, the graph type, the retained output file, and the owning user or plug — so that a previously configured schedule can be reproduced without the end user re-entering the same parameters.

The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, which is consistent with a moderate-update transactional object. Its dependency footprint is narrow: it references no other database object by foreign key except a documented link whereby PLUG_ID points to BSC_USER_KPILIST_PLUGS, and it is exposed to the runtime through the APPS synonym BIS_SCHEDULE_PREFERENCES. Under the heuristic Data Vault classification mined from the FK structure, the table is best modeled as a standalone object — that is, a satellite-like record keyed by its own surrogate identifier rather than a hub or link, since it neither resolves multiple business entities nor serves purely as a relationship table.

Key Information Stored

The documented schema contains 13 columns. The most operationally significant are:

• SCHEDULE_ID (NUMBER) — Report Schedule Id; the principal surrogate identifier for a saved schedule instance and the leading column of the non-unique index BIS_SCHEDULE_PREFERENCES_N3 and of BIS_SCHEDULE_PREFERENCES_N4.
• USER_ID (VARCHAR2, 80) — SSWA Userid. Note the datatype is character, not numeric, reflecting the SSWA login identity rather than FND_USER.USER_ID; this column appears in both the _N2 and _N3 indexes.
• PLUG_ID (NUMBER) — SSWA Plug Id, identifying the KPI plug or dashboard component to which the schedule belongs. It is the FK column to BSC_USER_KPILIST_PLUGS and participates in the _N2 and _N3 indexes.
• TITLE (VARCHAR2, 80) — Schedule Report Title, the user-visible name of the saved schedule.
• REQUEST_TYPE (VARCHAR2) — Report Request Type, distinguishing the class of concurrent request or report execution being scheduled.
• GRAPH_TYPE (VARCHAR2) — Schedule Report Graph Type, controlling the visualization applied when the report output is rendered.
• FILE_ID (NUMBER) — File Id referencing the retained output artifact; the leading column, with SCHEDULE_ID, of index BIS_SCHEDULE_PREFERENCES_N4.
• EXTERNAL_SOURCE_ID (NUMBER) — External Source, a nullable reference linking the schedule preference to an external source system or integration identifier. Because the user searched for this term, it is worth noting that the column is not indexed and not part of any documented unique constraint.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns. CREATED_BY and LAST_UPDATED_BY are foreign keys to FND_USER.USER_ID; LAST_UPDATE_LOGIN maps to FND_LOGINS.LOGIN_ID.

No unique index is documented, so the business key is effectively the composite of SCHEDULE_ID with the SSWA identity pair (USER_ID, PLUG_ID) and, where relevant, FILE_ID. These three combinations are served by the _N3, _N2, and _N4 non-unique indexes respectively.

Common Use Cases and Queries

Typical use cases include auditing which users have saved schedules against a given plug, diagnosing why a scheduled report fails to re-execute, and reconciling external source mappings. A representative query lists all saved schedules for a plug:

SELECT sp.SCHEDULE_ID, sp.USER_ID, sp.TITLE, sp.REQUEST_TYPE, sp.GRAPH_TYPE, sp.EXTERNAL_SOURCE_ID FROM BIS.BIS_SCHEDULE_PREFERENCES sp WHERE sp.PLUG_ID = :plug_id ORDER BY sp.TITLE;

To trace schedules to their plug definition, join on the documented FK:

SELECT sp.SCHEDULE_ID, sp.TITLE, p.PLUG_ID FROM BIS.BIS_SCHEDULE_PREFERENCES sp, BSC.BSC_USER_KPILIST_PLUGS p WHERE sp.PLUG_ID = p.PLUG_ID;

To identify rows that are not yet associated with an external source, filter on the column the user searched for:

SELECT SCHEDULE_ID, USER_ID, TITLE FROM BIS.BIS_SCHEDULE_PREFERENCES WHERE EXTERNAL_SOURCE_ID IS NULL;

For WHO audit reporting, join CREATED_BY and LAST_UPDATED_BY to FND_USER to resolve the responsible individuals and LAST_UPDATE_LOGIN to FND_LOGINS for session traceability.

Related Objects

• BSC.BSC_USER_KPILIST_PLUGS — the only documented foreign-key target, joined on PLUG_ID; defines the KPI dictionary plug to which the schedule belongs.
• APPS.BIS_SCHEDULE_PREFERENCES — the APPS-layer synonym through which the table is normally queried.
• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for WHO audit resolution.
• FND_LOGINS — joined on LAST_UPDATE_LOGIN to trace the operating-system session that last modified a row.
• BIS_SCHEDULE_PREFERENCES_N2 / _N3 / _N4 — supporting non-unique indexes on (USER_ID, PLUG_ID), (SCHEDULE_ID, USER_ID, PLUG_ID), and (SCHEDULE_ID, FILE_ID) respectively, which constrain the practical join paths used in reporting.
• BIS.BIS_SCHEDULE_REPORTS and related BIS schedule/report objects — commonly queried alongside this table when reconstructing the full definition of a scheduled dashboard output, though no FK is documented.

Collectively these objects place BIS_SCHEDULE_PREFERENCES at the preference layer of the BIS scheduling stack, bridging the SSWA security identity, the KPI plug catalogue, and the retained report output artifacts.