Results for “input_table_name”

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

Overview

BSC_DB_VALIDATION is a table owned by the BSC schema within the Oracle E-Business Suite Balanced Scorecard module. Its documented purpose is to serve as a log of input table validation errors. When users define or load data into Balanced Scorecard input tables—the user-configurable structures that feed scorecard indicators and KPI calculations—the application validates incoming rows against the expected table and column definitions. Rows that fail this validation are recorded in BSC_DB_VALIDATION, producing a persistent audit trail of rejected input.

In Oracle EBS 12.1.1 and 12.2.2, the object carries the status VALID and is implemented with three documented columns. Its foreign key to BSC_DB_TABLES_COLS ties every error record back to the exact table-and-column definition that was violated, giving administrators a precise diagnostic pointer rather than a generic failure message.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. It holds descriptive, context-dependent attributes (the invalid code and error detail) keyed to a parent definition rather than representing an independent business entity or an association between two hubs. It should therefore be understood as an error-detail satellite attached to the Balanced Scorecard input table metadata, not as a hub or link.

Key Information Stored

The documented physical schema for 12.1.1 lists three columns, all of which are significant because the table is narrow and purpose-built:

• INPUT_TABLE_NAME — Identifies the Balanced Scorecard input table that failed validation. This is a business-key candidate and, critically, participates in the foreign key to BSC_DB_TABLES_COLS. It allows administrators to isolate errors by target table.
• COLUMN_NAME — Identifies the specific column within the input table that produced the validation failure. Together with INPUT_TABLE_NAME it forms the second component of the foreign key to BSC_DB_TABLES_COLS, pinpointing the exact column definition implicated.
• INVALID_CODE — Holds the code classifying the nature of the validation error. This is the primary diagnostic payload: it tells the consumer why the row was rejected (for example, a type, format, or reference mismatch).

No separate surrogate primary key column is documented in the metadata; the table is effectively keyed by the combination of INPUT_TABLE_NAME and COLUMN_NAME inherited through the foreign key relationship. Because only these three columns are documented, consumers should treat the table as a compact error ledger rather than a general-purpose staging table.

Common Use Cases and Queries

The principal use case is troubleshooting failed Balanced Scorecard data loads. When an input table upload or refresh reports errors, administrators query this table to enumerate the offending table/column pairs and the associated invalid codes.

• Listing all validation errors for a specific input table:
  SELECT input_table_name, column_name, invalid_code FROM bsc.bsc_db_validation WHERE input_table_name = :p_table;
• Aggregating error frequency by column to identify a systematically malformed source extract:
  SELECT column_name, COUNT(*) FROM bsc.bsc_db_validation GROUP BY column_name ORDER BY 2 DESC;
• Joining to the definition table to retrieve fuller context for each failure, using the documented foreign key columns INPUT_TABLE_NAME and COLUMN_NAME.

Reporting use cases include data-quality dashboards that trend validation failures over time and pre-load reconciliation checks that confirm an input table is clean before scorecard calculations are refreshed.

Related Objects

The documented foreign key relationship anchors this table to the Balanced Scorecard metadata layer. The most significant related objects are:

• BSC_DB_TABLES_COLS — The parent definition table. BSC_DB_VALIDATION.INPUT_TABLE_NAME and BSC_DB_VALIDATION.COLUMN_NAME reference BSC_DB_TABLES_COLS, supplying the authoritative definition of each input table and column against which validation was performed.
• Balanced Scorecard input table definitions — The broader family of BSC_DB_* metadata objects that describe input table structures; these are reached transitively through BSC_DB_TABLES_COLS.
• Scorecard indicator and KPI definitions — Downstream consumers of the validated input data; when validation errors accumulate, indicator calculations that depend on the affected input table may be incomplete or stale.

Because the object is a satellite-style error log, it is referenced by few, if any, other tables. Its value lies in what it references—the input table and column definitions—rather than in being referenced itself. Any interface that loads Balanced Scorecard input data should be considered a functional dependency, as it is the process that populates this log.