Search Results value_n




Overview
Explore in AI Chat

Overview

BSC.BSC_TMP_BIG_IN_COND is a temporary interface table residing in the BSC (Balanced Scorecard / Enterprise Planning and Budgeting) schema. Its documented purpose is to "Store Big Condition," indicating that it serves as a staging container for large conditional expressions or filter values generated during the execution of analytical or planning processes. The object is classified as VALID, holds FND Design Data under the identifier BSC.BSC_TMP_BIG_IN_COND, and is stored in the APPS_TS_INTERFACE tablespace — a placement that confirms its role as a transient, session-scoped working table rather than a persistent transactional entity.

The table carries no foreign keys that it references except a logical dependency from VARIABLE_ID to RG_DSS_VARIABLES; the provided metadata also notes that it "does not reference any database object" at the database-constraint level. Based on the documented FK structure, the heuristic Data Vault classification is standalone. This suggests a modeling approach in which the table is treated as an independent staging or work structure rather than a hub, link, or satellite in a conventional Data Vault design.

Key Information Stored

The table contains four documented columns. The most operationally significant are:

  • SESSION_ID (NUMBER) — Identifies the user or process session that owns a given set of condition values. This is the primary grouping key for all rows produced during a single run.
  • VARIABLE_ID (NUMBER) — Identifies the variable or parameter to which a condition applies. The metadata records a dependency from this column to RG_DSS_VARIABLES, making it the principal business-key candidate and the join path back to the variable definition.
  • VALUE_N (NUMBER) — Holds the numeric form of the condition value.
  • VALUE_V (VARCHAR2, length 2000) — Holds the character form of the condition value; this is the column most often targeted by searches for "value_v," since it stores string-based filter criteria that may exceed typical column widths.

The non-unique index BSC_TMP_BIG_IN_COND_N1 spans SESSION_ID and VARIABLE_ID in the APPS_TS_INTERFACE tablespace, confirming the composite (SESSION_ID, VARIABLE_ID) pairing as the effective lookup key. No surrogate primary key is documented, which is consistent with a temporary staging table where uniqueness is enforced by application logic rather than a constraint.

Common Use Cases and Queries

Typical scenarios include inspecting the condition values generated for a specific session, resolving conditions against their variable definitions, and diagnosing why a large filter was not applied as expected.

  • Retrieve all conditions for a session:
    SELECT SESSION_ID, VARIABLE_ID, VALUE_N, VALUE_V FROM BSC.BSC_TMP_BIG_IN_COND WHERE SESSION_ID = :session_id;
  • Join to variable definitions to obtain descriptive context:
    SELECT c.SESSION_ID, c.VARIABLE_ID, v.VARIABLE_NAME, c.VALUE_N, c.VALUE_V FROM BSC.BSC_TMP_BIG_IN_COND c, BSC.RG_DSS_VARIABLES v WHERE c.VARIABLE_ID = v.VARIABLE_ID AND c.SESSION_ID = :session_id;
  • Search by character value when troubleshooting filter behavior:
    SELECT * FROM BSC.BSC_TMP_BIG_IN_COND WHERE UPPER(VALUE_V) LIKE '%&value_v%';
  • Reporting on condition volume and distribution per session or variable, useful for monitoring the size of generated expressions.

Because rows are session-scoped, any reporting or cleanup logic should filter on SESSION_ID to avoid cross-session contamination.

Related Objects

The documented relationships identify the following objects of significance:

  • BSC.RG_DSS_VARIABLES — Referenced by BSC_TMP_BIG_IN_COND.VARIABLE_ID; supplies the variable definitions that give meaning to each stored condition.
  • APPS.BSC_TMP_BIG_IN_COND — The APPS-layer synonym or view through which the table is exposed to application code, listed as the referencing object in the dependency metadata.
  • BSC_TMP_BIG_IN_COND_N1 — The non-unique index on (SESSION_ID, VARIABLE_ID) that supports session-scoped lookups and joins to the variable table.

No additional referencing objects are enumerated in the supplied metadata; further dependencies should be confirmed against the ETRM dependency report for the 12.1.1 and 12.2.2 releases.