Results for “bsc_db_loader_control”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BSC_DB_LOADER_CONTROL is a control table within the Oracle E-Business Suite Balanced Scorecard (BSC) module, documented as obsolete in Release 12.1.1 and 12.2.2. Its stated purpose is to hold loader control information — the orchestration metadata that governs how the Balanced Scorecard database loader stage processes inbound data. The table belongs to the BSC schema and consists of six documented columns. It is important to note that the ETRM metadata explicitly records this object as "Not implemented in this database," meaning it should not be expected to exist in a standard, unmodified EBS instance. It is typically encountered only in environments where the legacy Balanced Scorecard loader was previously configured, or in historical reference documentation.

From a dimensional modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table's identity is not a single generated surrogate key but a composite natural key composed of the input table name and the process identifier. As a satellite-style structure, it would store descriptive, changeable attributes — status, error information, and staging position — that describe the progress of a loader run rather than defining a new business entity. Teams modernizing or reverse-engineering this schema should treat that classification as a heuristic suggestion, not a documented architectural fact.

Key Information Stored

The table carries a declared composite primary key, BSC_DB_LOADER_CONTROL_PK, defined over INPUT_TABLE_NAME and PROCESS_ID. A second unique index, BSC_DB_LOADER_CONTROL_U1, is defined over the same two columns in the opposite order (PROCESS_ID, INPUT_TABLE_NAME), reinforcing their joint role as the business-key candidate that uniquely identifies a loader control row. No separate surrogate key column is documented.

• PROCESS_ID — identifier for a specific loader process or run; part of both the primary key and the unique business key.
• INPUT_TABLE_NAME — the name of the source or staging table being loaded; the other half of the composite key and the column participating in the foreign key to BSC_DB_TABLES.
• STATUS — the current processing state of the loader entry, enabling restarts and progress tracking.
• ERROR_CODE — captures the failure code when a load step does not complete successfully.
• STAGE — indicates which loading stage the process has reached.
• LAST_STAGE_FLAG — flags whether the current stage is the final stage for the process.

Collectively these six columns form a compact control record: what is being loaded, under which process, how far it has progressed, and whether it succeeded.

Common Use Cases and Queries

The principal use case is monitoring and troubleshooting loader activity. Administrators query STATUS and ERROR_CODE to identify failed loads, and inspect STAGE and LAST_STAGE_FLAG to determine completion. A representative query joins the control table to its parent table definition:

• SELECT c.PROCESS_ID, c.INPUT_TABLE_NAME, c.STATUS, c.ERROR_CODE, c.STAGE, c.LAST_STAGE_FLAG FROM BSC_DB_LOADER_CONTROL c WHERE c.STATUS <> 'SUCCESS' ORDER BY c.PROCESS_ID;
• SELECT c.PROCESS_ID, t.* FROM BSC_DB_LOADER_CONTROL c JOIN BSC_DB_TABLES t ON t.TABLE_NAME = c.INPUT_TABLE_NAME WHERE c.LAST_STAGE_FLAG = 'Y';

Reporting teams may also aggregate control rows by STATUS to produce load-success dashboards or use PROCESS_ID to correlate runs across audit tables. Because the object is obsolete, any such queries are relevant only to legacy or migration reconciliation work.

Related Objects

The most significant dependency is the parent table referenced through the foreign key on INPUT_TABLE_NAME:

• BSC_DB_TABLES — the registry of loader-eligible source tables; joined via BSC_DB_LOADER_CONTROL.INPUT_TABLE_NAME → BSC_DB_TABLES.

Beyond this documented relationship, related BSC loader components typically include the staging and target tables registered in BSC_DB_TABLES, the loader execution programs that read and update control rows, and the Balanced Scorecard database loader APIs and concurrent programs that drive PROCESS_ID values. Direct dependencies on this table are narrow by design, reflecting its role as a control satellite rather than a central transaction entity.