Search Results bim_dimv_prod_lov




Overview
Explore in AI Chat

Overview

BIM_DIMV_PROD_LOV is a read-only Oracle EBS view owned by the APPS schema, defined within the BIM – Marketing Intelligence product family. In ETRM metadata it carries a VALID status for the 12.1.1 and 12.2.2 releases, though the BIM Marketing Intelligence module itself is classified as Obsolete. The view functions as a list-of-values (LOV) source, presenting the hierarchical relationship between interest types, primary interest codes, and secondary interest codes. Its purpose is to flatten the three-level categorization structure used by Marketing Intelligence into a single denormalized result set suitable for LOV pickers, concurrent program parameters, and reporting joins against sales category hierarchies.

Because the module is obsolete, the view is retained primarily for backward compatibility with any customizations, reports, or interfaces that still reference BIM structures. It is documented as a dependent object rather than an actively maintained feature.

Underlying Base Objects

The view is defined over four documented base objects:

  • BIM_SALES_CATEGORY_HIER (SYNONYM) — the driving table supplying the interest type and primary/secondary interest code identifiers that define the hierarchy.
  • AS_INTEREST_TYPES_TL (SYNONYM) — the translated interest type name, restricted to the session language.
  • AS_INTEREST_CODES_TL (SYNONYM) — joined twice (aliased PCODE and SCODE) to resolve both primary and secondary code descriptions in the session language.
  • FND_LOOKUPS (VIEW) and FND_GLOBAL (PACKAGE) — used for the lookup-based placeholder row and language resolution via USERENV('LANG').

Both interest code joins use the outer-join (+) operator, so hierarchy rows lacking a matching translated code still appear. The language predicate on each TL table ensures only the current session language's name is returned. A UNION ALL appends a synthetic row with all identifier columns set to -999 and description columns set to the meaning of lookup type BIM_VALUE_TYPE for the -999 code, providing a generic "all values" LOV entry.

Key Columns

Note the ETRM column listing shows the ID columns alongside display-oriented columns (PRIMARY_INTEREST_CODE, SECONDARY_INTEREST_CODE) that map to the PCODE.CODE and SCODE.CODE selections in the view text.

Common Use Cases and Queries

Typical uses include populating LOV pickers for marketing interest classification, driving report parameters, and validating that a secondary code is associated with a given primary code and interest type. A representative query:

  • SELECT INTEREST_TYPE, PRIMARY_INTEREST_CODE, SECONDARY_INTEREST_CODE FROM APPS.BIM_DIMV_PROD_LOV WHERE INTEREST_TYPE_ID <> -999 ORDER BY 1,2,3;
  • SELECT PRIMARY_INTEREST_CODE, SECONDARY_INTEREST_CODE FROM APPS.BIM_DIMV_PROD_LOV WHERE INTEREST_TYPE_ID = :type_id AND PRIMARY_INTEREST_CODE_ID = :primary_id;

The -999 exclusion in the first query filters the synthetic BIM_VALUE_TYPE row when a concrete listing is required. Because the view is WITH READ ONLY, no DML is possible; consumers should treat it strictly as a query source. Given the obsolete module status, any new development should verify the view's continued presence in the target instance.