Search Results bis_target_values_u1

Overview

BIS.BIS_TARGET_VALUES is a transaction-data table in the Oracle E-Business Suite Business Intelligence System (BIS) schema. It stores the individual target values that a user has entered for a particular performance measure at a specific target level, providing the numeric benchmarks against which actual performance results are compared. As described in the ETRM documentation, the table captures values such as a projected turnover for a given office, period, and staff category; an entry that ties the organizational, time, and dimensional parameters into a single target value. The table also supports the definition of tolerance ranges around each target, allowing performance to be graded across multiple bands, and it permits several business plans to specify different values for the same underlying target.

The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. Its heuristic Data Vault classification, mined from the foreign key structure, is standalone. Under a Data Vault modeling approach this suggests the object functions as an independent reference of measurement values rather than participating in a hub-and-link relationship pattern; it is best treated as a satellite-like store of target quantities keyed by its own surrogate identifier.

Key Information Stored

The table contains 30 documented columns. The most significant are the following:

• TARGET_ID (NUMBER) — The surrogate primary key of the row and the single column of unique index BIS_TARGET_VALUES_U1. It is also the foreign key column that references AMS_DM_TARGETS_B, linking each stored value to its parent target definition.
• TARGET_LEVEL_ID (NUMBER) — Identifies the target level to which the value belongs, providing the link to the target-level hierarchy.
• PLAN_ID (NUMBER) — The business plan identifier. Because multiple plans may specify different values for the same target, this column is essential to disambiguate rows.
• ORG_LEVEL_VALUE and TIME_LEVEL_VALUE (VARCHAR2(80)) — Legacy organizational and time level identifiers; the ETRM comments explicitly mark both as no longer used.
• DIMENSION1_LEVEL_VALUE through DIMENSION7_LEVEL_VALUE (VARCHAR2(80)) — The dimensional level value identifiers that qualify the target, replacing the deprecated organization and time columns. Together with TARGET_LEVEL_ID, PLAN_ID, and the two legacy columns they form the composite business key of unique index BIS_TARGET_VALUES_U2.
• TARGET (NUMBER) — The numeric value of the performance target itself.
• RANGE1_LOW, RANGE1_HIGH, RANGE2_LOW, RANGE2_HIGH, RANGE3_LOW, RANGE3_HIGH (NUMBER) — Percentages defining up to three tolerance bands around the target, used to classify measured results as on-target, above, or below.
• ROLE1_ID, ROLE2_ID, ROLE3_ID and the corresponding ROLE1, ROLE2, ROLE3 — Role references associated with the target value.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns populated by the WHO columns convention.

Common Use Cases and Queries

Typical usage centers on retrieving target values and their tolerance ranges for a measure, plan, and dimensional slice, then comparing them to actual results. A basic retrieval pattern selects the target and its band definitions for a given plan and target level:

SELECT target_id, target, range1_low, range1_high,
       range2_low, range2_high, range3_low, range3_high
  FROM bis.bis_target_values
 WHERE target_level_id = :target_level_id
   AND plan_id = :plan_id;

Because multiple business plans can hold different values for the same target, reporting queries should always constrain on PLAN_ID where a specific plan perspective is required. Lookup by surrogate key is efficient due to the unique index BIS_TARGET_VALUES_U1, while lookups by the full dimensional combination rely on BIS_TARGET_VALUES_U2. Reporting use cases include performance scorecards comparing actual to target, banded RAG (red-amber-green) classification using the RANGE columns, and plan-versus-plan target comparison for the same measure and dimensional intersection.

Related Objects

The principal relationship is the foreign key from BIS_TARGET_VALUES.TARGET_ID to AMS_DM_TARGETS_B.TARGET_ID, which anchors each row to its target definition in the marketing/measurement target tables. Collectively, the most significant related objects are:

• AMS_DM_TARGETS_B — Parent target definition; joined on TARGET_ID.
• AMS_DM_TARGETS_TL — Translated target names and descriptions; joined to AMS_DM_TARGETS_B by TARGET_ID.
• BIS target-level definition objects referenced by TARGET_LEVEL_ID.
• BIS business-plan objects referenced by PLAN_ID.
• Dimensional level value objects referenced by DIMENSION1_LEVEL_VALUE through DIMENSION7_LEVEL_VALUE.

These joins support the standard reporting pattern of resolving a target value to its human-readable measure name, plan, and dimensional context for presentation in performance dashboards and analytical reports.