Results for “dim7_level_value_id”
23 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BISBV_TARGETS is a read-only Oracle EBS view owned by the APPS schema and registered under the BIS (Applications BIS) product family. In the Oracle E-Business Suite 12.1.1 and 12.2.2 releases, BIS designates the Business Intelligence System / Balanced Scorecard subsystem, which underpins the Daily Business Intelligence and enterprise performance-management reporting stack. The view is a thin projection over the target values table and exists to expose balanced-scorecard target definitions — the quantitative objectives that a plan pursues across organizational, time, and dimensional hierarchies — to reporting and integration consumers in a controlled, read-only form.
Functionally, BISBV_TARGETS answers the question "what target has been set for a given combination of plan, organization level, time level, and dimension level values, and which responsible parties have been notified in relation to it?" This makes it relevant both to downstream BI reporting and to any custom code that must resolve target ownership or notification routing.
Underlying Base Objects
The view is defined with a single-table SELECT statement with a WITH READ ONLY clause, over the base table BIS_TARGET_VALUES:
SELECT ... FROM BIS_TARGET_VALUES BIS_TARGET_VALUES WITH READ ONLY
No joins, aggregations, or additional base objects are documented in the ETRM metadata. The read-only designation is significant: it prevents DML against the view and guarantees that any consumer reads the persisted target definition rather than a transient or recomputed value. Because the view is a direct, non-transformative projection, its rows correspond one-to-one with rows in BIS_TARGET_VALUES. The documented base object list in the ETRM metadata is empty, but the view text itself establishes BIS_TARGET_VALUES as the sole underlying object.
Key Columns
The columns fall into three logical groups. The first group identifies the target and its position within the planning hierarchy: TARGET_ID and TARGET_LEVEL_ID uniquely identify the target and its level, while PLAN_ID ties it to a planning scenario. ORG_LEVEL_VALUE_ID, TIME_LEVEL_VALUE_ID, and DIM1_LEVEL_VALUE_ID through DIM7_LEVEL_VALUE_ID place the target along the organizational, temporal, and up to seven analytical dimensions supported by the model.
The second group carries the measurement itself: TARGET holds the numeric objective, and RANGE1_LOW/RANGE1_HIGH through RANGE3_LOW/RANGE3_HIGH define up to three tolerance or threshold bands around it, which scorecard reporting uses to classify actual performance (for example, as on-target, warning, or critical).
The third group governs notification and accountability, and this is where the search term notify_resp2_id applies. The view exposes NOTIFY_RESP1_ID, NOTIFY_RESP2_ID, and NOTIFY_RESP3_ID together with their companion short-name columns NOTIFY_RESP1_SHORT_NAME, NOTIFY_RESP2_SHORT_NAME, and NOTIFY_RESP3_SHORT_NAME. Each NOTIFY_RESPn_ID is a responsibility identifier — a foreign key to the FND_RESPONSIBILITY table — and NOTIFY_RESPn_SHORT_NAME is the user-facing responsibility short name resolved for convenience. Up to three responsibilities may be associated with a target so that, when the target is missed or a threshold is breached, the correct operational or managerial groups are alerted. NOTIFY_RESP2_ID therefore designates the secondary notification responsibility for the target.
Common Use Cases and Queries
Typical uses include auditing which responsibilities are configured to receive target notifications, joining target definitions to dimension and plan reference data for scorecard reports, and troubleshooting missing alerts where the notification responsibility was left null.
List targets with their three notification responsibilities:
SELECT t.target_id,
t.plan_id,
t.target,
t.notify_resp1_short_name,
t.notify_resp2_short_name,
t.notify_resp3_short_name
FROM apps.bisbv_targets t
WHERE t.notify_resp2_id IS NOT NULL;
Resolve the secondary notification responsibility to its authoritative definition:
SELECT t.target_id, t.notify_resp2_id, r.responsibility_name
FROM apps.bisbv_targets t,
apps.fnd_responsibility_vl r
WHERE t.notify_resp2_id = r.responsibility_id
AND t.plan_id = :plan_id;
Identify targets with no notifications configured at all, which is a frequent cause of silent scorecard failures:
SELECT target_id, plan_id, target FROM apps.bisbv_targets WHERE notify_resp1_id IS NULL AND notify_resp2_id IS NULL AND notify_resp3_id IS NULL;
Because the view is read-only, it should be used strictly for retrieval; maintenance of target values and their notification assignments is performed against the underlying BIS_TARGET_VALUES table through the supported BIS application flows.
-
View: BISBV_TARGETS 12.1.1
-
View: BISFV_TARGETS 12.1.1
APPS.BISFV_TARGETS·↳ BIS_BUSINESS_PLANS·↳ BIS_BUSINESS_PLANS_TL·↳ BIS_TARGET_LEVELS·Explore BIS module →
-
View: BISBV_TARGETS 12.2.2
Not implemented in this database·Explore BIS module →
-
VIEW: APPS.BISBV_TARGETS 12.1.1
-
VIEW: APPS.BISFV_TARGETS 12.1.1
-
View: BISFV_TARGETS 12.2.2
Not implemented in this database·Explore BIS module →
-
PACKAGE: APPS.BIS_ACTUAL_PUB 12.1.1
-
PACKAGE: APPS.BIS_TARGET_PUB 12.1.1
-
PACKAGE: APPS.BIS_TARGET_PVT 12.1.1
-
eTRM - BIS Tables and Views 12.1.1