Search Results bis_target_values

Overview

BIS_TARGET_VALUES is a table in the BIS (Applications BIS / Business Intelligence System) product schema of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores the numeric target definitions and threshold ranges used by Oracle's demand planning and performance management functionality, associating a target with the business levels at which it applies. Each row defines a target value together with the organizational, time, plan, and dimensional coordinates that identify the scope of that target.

The table holds 30 documented columns and is classified under a heuristic Data Vault model as standalone. From a modeling perspective, this suggests the table behaves more like a reference or satellite-style structure than a shared hub or link, since it carries a single foreign-key relationship and no dependent children of its own. Its primary linkage is to AMS_DM_TARGETS_B, the base table defining the target master.

Key Information Stored

The most important columns in BIS_TARGET_VALUES fall into three groups: identifiers, level coordinates, and target/range definitions.

• TARGET_ID — surrogate-style foreign key to AMS_DM_TARGETS_B; also the leading column of the unique index BIS_TARGET_VALUES_U1.
• TARGET_LEVEL_ID — identifier of the target level (e.g., the specific planning or performance level) at which the target is measured.
• PLAN_ID — the plan context in which the target applies.
• ORG_LEVEL_VALUE — the organization-level business key participating in the target scope.
• TIME_LEVEL_VALUE — the time-level business key (e.g., period or bucket) for the target.
• DIMENSION1_LEVEL_VALUE through DIMENSION7_LEVEL_VALUE — up to seven additional dimensional coordinates, allowing targets to be sliced across product, customer, channel, or other planning dimensions.
• TARGET — the actual target value being managed for that scope.
• RANGE1_LOW / RANGE1_HIGH, RANGE2_LOW / RANGE2_HIGH, RANGE3_LOW / RANGE3_HIGH — three pairs of low/high boundaries defining tolerance or performance bands around the target.
• ROLE1_ID, ROLE2_ID, ROLE3_ID — role identifiers (likely responsibility or approval roles) associated with each range.
• ROLE1, ROLE2, ROLE3 — descriptive role names corresponding to the role IDs.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

The business key is expressed through unique index BIS_TARGET_VALUES_U2, which combines TARGET_LEVEL_ID, ORG_LEVEL_VALUE, TIME_LEVEL_VALUE, PLAN_ID, and all seven DIMENSIONn_LEVEL_VALUE columns — confirming that a target is uniquely defined by its full level and dimensional context.

Common Use Cases and Queries

Typical uses include reporting actual-versus-target performance, extracting tolerance bands for alerting, and reconciling target definitions across plans and organizations. A representative query joins to the target master:

• SELECT t.target, t.range1_low, t.range1_high, b.target_name FROM bis.bis_target_values t JOIN ams.ams_dm_targets_b b ON b.target_id = t.target_id WHERE t.plan_id = :plan AND t.org_level_value = :org;
• Dimensional filtering by org, time, and any active DIMENSIONn_LEVEL_VALUE column to isolate a slice of targets.
• Auditing scope coverage using TARGET_LEVEL_ID combined with the dimension columns to detect gaps or duplicates against U2.

Related Objects

• AMS_DM_TARGETS_B — master/target base table; joined on TARGET_ID (the sole documented foreign key).
• AMS_DM_TARGETS_TL — translated target names and descriptions, joined via TARGET_ID for multilingual reporting.
• BIS_TARGET_VALUES_U1 / BIS_TARGET_VALUES_U2 — unique indexes defining the surrogate and composite business key, relevant for load and deduplication logic.
• BIS planning and BI reporting views — dependent views or extracts that consume target and range values for dashboards.

Because the metadata lists no child tables referencing BIS_TARGET_VALUES, it functions as a downstream detail table whose integrity is maintained through its foreign key and unique indexes rather than through dependent constraints.