Search Results msc_bis_targets




Overview
Explore in AI Chat

Overview

MSC_BIS_TARGETS is a table within the MSC schema (Advanced Supply Chain Planning) in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the target values that drive the Business Intelligence System (BIS) reports used for supply chain performance measurement and exception management. Each row represents a defined target, together with its associated threshold ranges and notification assignments, so that actual planning results can be compared against expected performance levels and escalated when variance thresholds are breached.

Under the heuristic Data Vault classification derived from its foreign key structure, MSC_BIS_TARGETS is a link entity. This is a modeling suggestion rather than a physical implementation detail: the table connects target levels, business plans, organization hierarchies, and time dimensions into a single configured target, and the combination of these references forms the natural business key. The primary key, MSC_BIS_TARGETS_PK, is defined on the composite of TARGET_ID and SR_INSTANCE_ID, and the table carries 34 columns in the documented 12.2.2 physical schema.

Key Information Stored

The most operationally significant columns fall into three groups.

Standard audit and concurrent program columns are also present: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, along with REFRESH_NUMBER for tracking data refresh cycles.

Common Use Cases and Queries

Typical usage centers on retrieving targets for a given business plan or organization and comparing them with planned or actual results. A common pattern joins the target to its level definition:

  • Filter by SR_INSTANCE_ID and BUSINESS_PLAN_ID to list all targets configured for a plan.
  • Join to MSC_BIS_TARGET_LEVELS on TARGET_LEVEL_ID to obtain the level description and reporting context.
  • Evaluate actuals against the RANGE columns to classify performance into low, mid, and high bands and to determine whether notifications are required.
  • Use NOTIFY_RESP* columns to drive workflow or alert distribution for exception reporting.

A representative query selects TARGET, TARGET_LEVEL_ID, RANGE1_LOW, and RANGE1_HIGH for a specific instance and plan, ordered by TIME_LEVEL_VALUE_ID, to produce a trend view of planned versus targeted performance.

Related Objects

  • MSC_BIS_TARGET_LEVELS — referenced via MSC_BIS_TARGETS.TARGET_LEVEL_ID, defining the level at which targets are applied.
  • MSC_BIS_BUSINESS_PLANS — referenced via SR_INSTANCE_ID and BUSINESS_PLAN_ID, supplying the business plan context.
  • MSC_BIS_TARGETS_PK — the composite primary key index on TARGET_ID and SR_INSTANCE_ID.
  • MSC_BIS_TARGETS_U1 and MSC_BIS_TARGETS_U2 — unique indexes enforcing target uniqueness across instance, level, plan, organization, time, and dimension values.