Results for “actual_value”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The BIS_LATEST_ACTUAL_VALUES_V view in the APPS schema of Oracle E-Business Suite (documented for both 12.1.1 and 12.2.2) is a reporting and integration construct within the BIS - Applications BIS product family. It presents the most recent actual performance value recorded for each combination of organization and target level, without requiring the calling application or report to filter historical rows manually. The view therefore acts as a convenience layer over the transactional actual-values data, collapsing a potentially large history into a single "as-of-latest-update" snapshot per key.

Its principal role is to support tracking of performance against targets. Because it returns one row per ORGANIZATION_ID and TARGET_LEVEL_ID, consumers such as Oracle Daily Business Intelligence dashboards, custom concurrent programs, and external integration extracts can obtain current attainment figures directly rather than re-implementing the MAX-of-date logic themselves.

Underlying Base Objects

According to the documented view text, the view is defined over a single base table: BIS_ACTUAL_VALUES. No other base objects are documented in the ETRM metadata for this view.

Internally the view aliases this table twice — once as A1 for the outer query and once as A2 for a correlated subquery. The outer query selects rows from BIS_ACTUAL_VALUES A1, while the subquery returns the maximum LAST_UPDATE_DATE from BIS_ACTUAL_VALUES A2 where A2.TARGET_LEVEL_ID matches A1.TARGET_LEVEL_ID and A2.ORGANIZATION_ID matches A1.ORGANIZATION_ID. A row qualifies only when its own LAST_UPDATE_DATE equals that per-key maximum.

This correlated subquery pattern gives the view its "latest" semantics. It is important to note the implication for ties: if two rows share the same organization, target level, and identical maximum last-update date, both will be returned. The view does not perform any deduplication beyond the date comparison, and it exposes no TRUNC or NVL logic, so timestamp precision in LAST_UPDATE_DATE directly governs which rows are selected.

Key Columns

• ORGANIZATION_ID — Identifies the operating unit or inventory organization context for the actual value. Combined with TARGET_LEVEL_ID, it forms the effective key of the view's result set.
• TARGET_LEVEL_ID — References the target-level definition against which actuals are measured. This is the column most often used as a query predicate, including by users searching for "target_level_id," since it links the view to the broader target and metric hierarchy.
• ACTUAL_VALUE — The measured actual amount for the given organization and target level. It is the principal numeric measure returned by the view and is typically compared against target or goal values by reporting consumers.
• LAST_UPDATE_DATE — The timestamp of the most recent update to the underlying row. Because the view's filtering logic is built entirely on this column, it serves both as an audit attribute and as the determinant of which record is considered "latest."

Common Use Cases and Queries

The most frequent use case is retrieving the current actual value for a specific target level within an organization, or a set of target levels across organizations for dashboard or reporting purposes. The view eliminates the need to write the MAX-date subquery against BIS_ACTUAL_VALUES repeatedly.

Retrieve the latest actuals for a single target level:

• SELECT organization_id, target_level_id, actual_value, last_update_date FROM apps.bis_latest_actual_values_v WHERE target_level_id = :p_target_level_id ORDER BY organization_id;

Retrieve latest actuals across all organizations for reporting:

• SELECT organization_id, target_level_id, actual_value FROM apps.bis_latest_actual_values_v WHERE organization_id = :p_org_id;

Join to target-level definitions to display descriptive names alongside the actual value:

• SELECT l.organization_id, l.target_level_id, l.actual_value FROM apps.bis_latest_actual_values_v l, apps.bis_target_levels_v t WHERE l.target_level_id = t.target_level_id AND l.organization_id = :p_org_id;

Because the view performs a correlated subquery on every execution, queries benefit from limiting rows via predicates on ORGANIZATION_ID and TARGET_LEVEL_ID. The presence of the documented index columns in BIS_ACTUAL_VALUES is not specified in ETRM metadata, but performance tuning should target those two key columns and LAST_UPDATE_DATE.