Search Results bisfv_targets




Overview
Explore in AI Chat

Overview

The BISFV_TARGETS view is a reporting and integration object within the Oracle E-Business Suite BIS (Applications BIS / Business Intelligence System) product family. It consolidates target values defined in the BIS target-management subsystem and resolves them against their owning target levels, business plans, and assigned roles, producing a single denormalized row per target record suitable for downstream reporting, ad-hoc querying, and integration into analytical applications.

The view is one of the standard "BISFV" (BIS Foundation View) family, whose members typically join a transactional base table to one or more descriptive lookup tables and translation (_TL) tables so that consumers receive both surrogate identifiers and human-readable names without having to write the joins themselves. In ETRM documentation for 12.2.2, the object is classified as not implemented in this database, meaning the view text is shipped as reference metadata even though the object is not deployed in the queried environment. Its presence in the ETRM catalog nonetheless documents the shipped definition used wherever the BIS target planning schema is present (for example, 12.1.1 through 12.2.2 installations with the BIS target/planning components licensed and installed).

Underlying Base Objects

The view is defined over five documented base tables joined in a single SELECT. ETRM lists no explicitly documented "referenced base objects" beyond what appears in the view text itself, and the visible SQL confirms the following:

  • BIS_TARGET_VALUES — the driving detail table holding the numeric targets, ranges, dimension level values, time values, and role assignments. Aliased twice in the column list as BIS_TARGET_VALUES.
  • BIS_TARGET_LEVELS — header table providing the target level identifier and its short name.
  • BIS_TARGET_LEVELS_TL — translation table supplying the language-specific long name for the target level.
  • BIS_BUSINESS_PLANS — plan header providing the plan identifier and plan short name.
  • BIS_BUSINESS_PLANS_TL — translation table supplying the language-specific plan name.

The joins are driven by foreign-key relationships: BIS_TARGET_VALUES.TARGET_LEVEL_ID = BIS_TARGET_LEVELS.TARGET_LEVEL_ID, with the _TL tables keyed on the same identifiers, and the plan columns linked through PLAN_ID. The view also invokes the PL/SQL function BIS_UTILITIES_PUB.RESOLVE_ROLE_NAME three times to translate numeric role identifiers into display names.

Key Columns

The projection is organized into several logical groups:

Because the projection repeats several column expressions (a documented quirk of the shipped view text), consumers should select named columns explicitly rather than relying on SELECT * in production code.

Common Use Cases and Queries

Typical applications include target-versus-actual reporting, dashboard threshold evaluation using the RANGE columns, and role-based routing of target notifications. A representative query retrieving resolved target details for a given plan is:

SELECT t.TARGET_ID,
       t.NAME            AS target_level_name,
       p.NAME            AS plan_name,
       t.TARGET,
       t.RANGE1_LOW,
       t.RANGE1_HIGH,
       t.ROLE1_ID,
       BIS_UTILITIES_PUB.RESOLVE_ROLE_NAME(t.ROLE1) AS role1_name
FROM   BISFV_TARGETS t,
       BIS_BUSINESS_PLANS_TL p
WHERE  t.PLAN_ID = p.PLAN_ID
AND    t.TARGET_LEVEL_ID = :target_level_id;

For dimensional analysis, filter on the relevant DIMENSIONn_LEVEL_VALUE columns; for threshold monitoring, compare TARGET against the RANGE bounds. Since the view is documented as not implemented in the ETRM reference database, deployers should verify object existence in their own environment before relying on it in concurrent programs, BI Publisher data templates, or custom forms.