Search Results bsc_db_process_control

Overview

BSC_DB_PROCESS_CONTROL is a table in the BSC (Balanced Scorecard) product schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. The table stores process control information used by the Balanced Scorecard application to track the execution state of internal database processes, batch jobs, and scheduled routines. It provides a registry of processes along with their current status, timing information, and associated log file locations, allowing administrators and application logic to monitor, audit, and troubleshoot process execution within the BSC module.

The ETRM metadata classifies this object, using a heuristic Data Vault assessment mined from its foreign key structure, as standalone. From a dimensional or Data Vault modeling perspective, this classification suggests the table behaves as an independent entity without enforced foreign key dependencies to other BSC tables in the documented schema. It is best modeled as a standalone hub or reference structure keyed on its process identifier, rather than as a link or satellite dependent on a parent business entity.

Key Information Stored

The documented physical schema contains 12 columns. The most significant are described below.

• PROCESS_ID — The surrogate primary key, enforced by the BSC_DB_PROCESS_CONTROL_PK constraint. A unique index, BSC_DB_PROCESS_CONTROL_U1, also exists on PROCESS_ID, making it both the technical primary key and the documented business-key candidate.
• PROCESS_NAME — The descriptive name identifying the process. This is the primary human-readable attribute for identifying a given process control record in reports and queries.
• STATUS — The current execution state of the process, used to determine whether a process is running, completed, failed, or pending.
• START_TIME — The timestamp at which the process began execution.
• END_TIME — The timestamp at which the process completed, supporting duration calculations when compared with START_TIME.
• LOG_FILE_LOCATION — The file system or directory path where the process log output is written, enabling administrators to locate diagnostic output.
• DESCRIPTION — Free-form text describing the purpose or scope of the process.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified the record, when, and through which login session.

The surrogate key (PROCESS_ID) is distinct from the audit and descriptive attributes; no separate composite business key is documented beyond the unique index on PROCESS_ID itself.

Common Use Cases and Queries

Typical scenarios include monitoring process execution status, calculating runtime durations, and auditing process control activity. A representative query retrieves currently active or recently completed processes:

• Listing all processes with their status: SELECT PROCESS_ID, PROCESS_NAME, STATUS, START_TIME, END_TIME FROM BSC.BSC_DB_PROCESS_CONTROL ORDER BY START_TIME DESC;
• Identifying long-running processes: SELECT PROCESS_NAME, (END_TIME - START_TIME) AS DURATION FROM BSC.BSC_DB_PROCESS_CONTROL WHERE END_TIME IS NOT NULL;
• Locating logs for failed processes: SELECT PROCESS_NAME, LOG_FILE_LOCATION FROM BSC.BSC_DB_PROCESS_CONTROL WHERE STATUS = 'FAILED';
• Auditing recent changes: SELECT PROCESS_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM BSC.BSC_DB_PROCESS_CONTROL WHERE LAST_UPDATE_DATE > SYSDATE - 7;

These patterns support operational dashboards, DBA monitoring, and support diagnostics within the Balanced Scorecard module.

Related Objects

The documented metadata describes BSC_DB_PROCESS_CONTROL as standalone, meaning no foreign key relationships to other tables are recorded in the ETRM extract. Consequently, the most significant related objects are internal to the BSC schema and are referenced through the PROCESS_ID primary key rather than through enforced constraints.

• BSC_DB_PROCESS_CONTROL_PK — The primary key constraint on PROCESS_ID, defining row uniqueness.
• BSC_DB_PROCESS_CONTROL_U1 — The unique index on PROCESS_ID, reinforcing the business-key candidate.
• Other BSC.BSC_DB_* process and metadata tables — Companion tables in the BSC schema that collectively support Balanced Scorecard process execution and configuration, joined logically on PROCESS_ID where relationships exist.
• BSC application concurrent programs and scheduled routines — The processes registered and tracked by this table are executed by BSC module logic and Oracle concurrent processing, which read and update STATUS, START_TIME, and END_TIME.

Because no foreign keys are documented, DBAs should verify logical joins against BSC schema objects directly when building custom reports.