Search Results ar_turnover

Overview

The view BIS_AR_TURNOVER_V belongs to the Oracle EBS Applications BIS (Business Intelligence System / Balanced Scorecard) product family. In Oracle EBS 12.1.1 and 12.2.2, BIS provides the underlying schema that supports Oracle Balanced Scorecard (OBSC) and related performance-management functionality. The view exposes the target and threshold configuration associated with the AR_TURNOVER (Accounts Receivable Turnover) performance measure, as defined within a business plan.

The object is explicitly flagged in the ETRM documentation as “Retrofitted” and “Not implemented in this database.” This is a significant qualification: the view is a legacy or compatibility construct that may exist only in certain patched environments and is not guaranteed to be present in a standard 12.1.1 or 12.2.2 installation. Where it does exist, it serves as a reporting and integration surface that joins plan metadata with target values and threshold ranges for a specific measure. Its practical role is to present a single, denormalized row of scorecard configuration that reporting queries, integrations, or scorecard tooling can consume without reconstructing the multi-table joins themselves.

Underlying Base Objects

The ETRM metadata lists no documented referenced base objects, but the view text itself reveals the source tables that constitute its definition. The view is a four-way join across the BIS and General Ledger schemas:

• BIS_TARGET_VALUES (aliased VAL) — the driving table, holding the target value, threshold ranges, and role assignments for a given target-level and plan combination.
• BIS_BUSINESS_PLANS (aliased PLAN) — supplies plan identity and descriptive attributes such as plan ID, short name, version, and current-plan flag.
• BIS_TARGET_LEVELS (aliased LVL) — provides the target-level definition and, critically, the WF_PROCESS attribute. The view is filtered by LVL.SHORT_NAME = 'AR_TURNOVER', which restricts output to the AR turnover measure.
• GL_PERIODS (aliased GL) — joined as a cross-referencing operand, consistent with period-based scorecard evaluation.

The join predicates link VAL.TARGET_LEVEL_ID = LVL.TARGET_LEVEL_ID and VAL.PLAN_ID = PLAN.PLAN_ID. Because GL_PERIODS is included without an explicit join predicate in the excerpted view text, it functions as a cross join, which effectively multiplies rows by the period set. Administrators evaluating this view should confirm the join as deployed, since the documented excerpt may be abridged.

Key Columns

The view returns twenty columns. The most operationally relevant are grouped below.

• WF_PROCESS — the workflow process identifier inherited from the target level; relevant for scorecard workflow integration.
• PLAN_ID, PLAN_SHORT_NAME, VERSION_NO, CURRENT_PLAN_FLAG — business plan identity and versioning metadata, used to select the active plan version.
• TARGET — the numeric target value configured for the AR turnover measure.
• RANGE1_LOW / RANGE1_HIGH, RANGE2_LOW / RANGE2_HIGH, RANGE3_LOW / RANGE3_HIGH — the three configurable threshold bands used to grade performance against the target.
• ROLE1_ID, ROLE2_ID, ROLE3_ID and ROLE1, ROLE2, ROLE3 — responsibility/role ownership assignments associated with each threshold band, enabling notification and escalation logic.

Note that the documented column list also includes TOTAL_TIME, which is not present in the excerpted SELECT clause. This discrepancy is consistent with the view’s “Retrofitted” status and indicates that column expectations should be validated against the deployed definition.

Common Use Cases and Queries

The primary use case is retrieving the current target and threshold configuration for the AR turnover measure for reporting or scorecard comparison. A representative query filtering on the current plan is:

• SELECT plan_short_name, version_no, target, range1_low, range1_high, role1
• FROM bis_ar_turnover_v
• WHERE current_plan_flag = 'Y';

Secondary use cases include auditing threshold bands across plan versions, extracting role ownership for escalation mapping, and feeding external performance dashboards that require a flattened measure definition. Before relying on the view, confirm its existence with ALL_VIEWS or DBA_VIEWS, since the ETRM metadata records it as not implemented in the reference database.