Search Results bsc_lookups




Overview
Explore in AI Chat

Overview

BSC_LOOKUPS is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the FND - Application Object Library product family. It presents a filtered, language-aware projection of Oracle's standard lookup values, restricted to lookup types that begin with the prefix "BSC". In EBS 12.1.1 and 12.2.2 alike, the view carries a status of VALID and is defined entirely in PL/SQL-free SQL over the FND_LOOKUP_VALUES table, which is the core repository for extensible lookup codes in the applications.

The view's principal role is to isolate the lookup set used by Balanced Scorecard (BSC) functionality so that reports, concurrent programs, and integration extracts can retrieve scorecard-related codes without scanning the full lookup table. Because it screens on the BSC prefix, it acts as a logical domain boundary around scorecard lookup values.

Underlying Base Objects

The documented base object for BSC_LOOKUPS is FND_LOOKUP_VALUES (aliased LV in the view definition). No additional base objects are documented in the ETRM metadata. The view definition is:

Three predicates govern the result set. The LANGUAGE filter uses USERENV('LANG') so that each session sees lookup meanings in its own language, drawing on the multilingual rows maintained in FND_LOOKUP_VALUES. The LIKE 'BSC%' predicate narrows the output to Balanced Scorecard lookup types. The SECURITY_GROUP_ID = 0 condition selects only the seed or shared data group, excluding rows belonging to other security groups.

Key Columns

  • APPLICATION_ID — Exposed through the alias VIEW_APPLICATION_ID. Identifies the application owning the lookup type, typically the Balanced Scorecard application context.
  • LOOKUP_TYPE — The lookup type name; always begins with "BSC" given the view's filter. Groups related codes together.
  • LOOKUP_CODE — The internal code value stored on transactional and setup records.
  • MEANING — The user-facing, translatable label corresponding to the code for the session language.
  • DESCRIPTION — Optional extended text explaining the code's purpose.
  • ENABLED_FLAG — Indicates whether the lookup code is active ("Y") or disabled ("N").
  • START_DATE_ACTIVE and END_DATE_ACTIVE — Effective date range bounding when the code may be used.

Common Use Cases and Queries

Typical scenarios include validating scorecard setup data, joining lookup meanings onto scorecard fact extracts, and building value sets or LOVs for concurrent program parameters. The view is frequently used to translate stored codes into display text for operational reports.

Retrieve all enabled BSC lookups:

  • SELECT lookup_type, lookup_code, meaning FROM apps.bsc_lookups WHERE enabled_flag = 'Y' ORDER BY lookup_type, lookup_code;

List codes for a specific lookup type:

  • SELECT lookup_code, meaning, description FROM apps.bsc_lookups WHERE lookup_type = 'BSC_INDICATOR_TYPE';

Join lookup meanings to transaction data:

  • SELECT t.scorecard_id, t.indicator_code, l.meaning FROM bsc_transactions t, apps.bsc_lookups l WHERE t.indicator_code = l.lookup_code AND l.lookup_type = 'BSC_INDICATOR_TYPE';

Because the view filters on the session language, results vary by login language and should not be used for code-value validation where language independence is required; query FND_LOOKUP_VALUES directly in such cases.