Search Results bsc_db_process_control_u1

Overview

BSC.BSC_DB_PROCESS_CONTROL is a transactional table in the BSC (Balanced Scorecard / Enterprise Planning and Budgeting) schema of Oracle E-Business Suite. It stores control and status information about database processes executed within the BSC application stack, functioning as a lightweight process registry that records when a process started, when it completed, its current status, and where its log output resides. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10, reflecting its role as an operational transaction table rather than a high-watermark reference table. The object is documented as VALID with the FND Design Data registration BSC.BSC_DB_PROCESS_CONTROL.

Under the heuristic Data Vault classification supplied in the metadata, the table is modelled as a standalone construct. It contains no foreign key references to other database objects, meaning it does not participate as a link or satellite in a dependent hierarchy. A standalone classification suggests treating it as an independent hub-like record set keyed on its own identifier, with its descriptive attributes (status, timestamps, log location) forming satellite-style context around that key.

Key Information Stored

The table documents twelve columns, of which the following are the most operationally significant:

• PROCESS_ID (NUMBER, mandatory) — the surrogate primary key, enforced by BSC_DB_PROCESS_CONTROL_PK and mirrored by the unique index BSC_DB_PROCESS_CONTROL_U1. This is the single business-key candidate documented for the table.
• PROCESS_NAME (VARCHAR2) — the human-readable name of the process being tracked.
• STATUS (VARCHAR2) — the current lifecycle state of the process (for example, running, completed, or failed).
• LOG_FILE_LOCATION (VARCHAR2, length 500) — the filesystem or directory path where the process log is written; the generous length accommodates deep path structures.
• START_TIME and END_TIME (DATE) — the execution window, enabling duration and overlap analysis.
• DESCRIPTION (VARCHAR2, length 250) — documented as holding input table names, indicating the table also serves as a rudimentary provenance record for the source data consumed by the process.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing audit traceability.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting long-running or failed BSC processes. A typical operational query retrieves recent runs ordered by start time:

• SELECT process_id, process_name, status, start_time, end_time FROM bsc.bsc_db_process_control ORDER BY start_time DESC;
• Identifying stalled processes: filter on status where end_time IS NULL and start_time is older than an expected threshold.
• Locating log artifacts for a failed run by selecting log_file_location for a given process_name.
• Computing average elapsed time per process using end_time - start_time grouped by process_name.

The documented SELECT statement joins all twelve columns and is safe to use as a retrieval template. Purge or housekeeping logic may also target this table to remove stale process records by end_time.

Related Objects

The metadata states that BSC.BSC_DB_PROCESS_CONTROL does not reference any database object, confirming its standalone classification. It is referenced only within the APPS synonym layer:

• APPS.BSC_DB_PROCESS_CONTROL — the synonym exposing the table to the APPS schema, which is the standard access path for concurrent programs, PL/SQL packages, and BI Publisher reports.

Because no FK relationships are documented, joins to other BSC tables (such as staging or result tables named in the DESCRIPTION column) are implicit and driven by runtime convention rather than enforced constraints. Analysts should therefore validate join keys manually when correlating process records with downstream output tables.