Search Results retrieve_tl_selections

Overview

BIS_ACTUAL_PVT is the private implementation package supporting Oracle E-Business Suite's Business Intelligence System (BIS) actuals framework. It provides the underlying PL/SQL logic for capturing, validating, and retrieving actual performance values that are compared against targets within Oracle Balanced Scorecard, Daily Business Intelligence, and related KPI monitoring components. The package operates with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema, and it is not intended to be invoked directly by end users. Instead, it acts as the engine behind the public BIS_ACTUAL_PUB package, exposing internal procedures that enforce validation rules, handle dimension conversion, and persist actual values to the BIS repository. The "PVT" classification confirms that this is an internal, non-public API whose signature may change across releases. The package is essential for organizations that load external actual data—such as sales figures, headcount, or financial metrics—into the EBS analytical schema so that performance can be measured against defined targets. All procedures follow the standard EBS API conventions, using p_api_version, p_commit, x_return_status, and x_error_Tbl parameters to report outcome and error detail.

Key Procedures and Functions

The package exposes eleven documented procedures and functions that together form a complete actuals-management lifecycle.

• POST_ACTUAL — Posts an actual value into the BIS tables. This is the core write operation and is the subject of the user's search. It accepts an actual record from BIS_ACTUAL_PUB and a validation level, and writes the value through the BIS_ACTUAL_VALUES tables while collecting errors into an error table.
• RETRIEVE_ACTUAL — Returns the actual value for a specified combination of dimension values, such as organization and time period. When dimension detail is not required, the all_info flag can be set to FALSE for a lighter query.
• RETRIEVE_ACTUALS — Bulk variant that returns multiple actual records for a set of dimension criteria.
• RETRIEVE_LATEST_ACTUAL — Retrieves the most recent actual value matching the supplied context.
• RETRIEVE_LATEST_ACTUALS — Bulk variant returning the latest actual for multiple indicator or dimension combinations.
• RETRIEVE_USER_SELECTIONS — Fetches the KPIs a user has chosen to monitor on the personal homepage or summary report; this must be called before Post_Actual in the standard flow.
• RETRIEVE_TL_SELECTIONS — Returns all rows from BIS_USER_IND_SELECTIONS for a given target level.
• VALIDATE_ACTUAL — Performs full validation on an actual record prior to posting.
• VALIDATE_REQUIRED_FIELDS — Checks that mandatory attributes are populated.
• VALIDATE_DIMENSION_VALUES — Confirms that supplied dimension members exist and are valid.
• VALUE_ID_CONVERSION — Converts values between internal identifiers and external representations used by callers.

Tables Accessed

Three APPS-synonymed tables are referenced. BIS_ACTUAL_VALUES stores the primary actual values keyed by indicator and dimension combination; POST_ACTUAL inserts or updates here, while the retrieve procedures read from it. BIS_ACTUAL_VALUES_S is the corresponding seed or staging table used during load and validation. BIS_USER_IND_SELECTIONS records which indicators each user has elected to monitor, supporting Retrieve_User_Selections and Retrieve_tl_selections. These tables reside in the BIS schema and are accessed through APPS synonyms.

Usage Notes

BIS_ACTUAL_PVT is typically invoked indirectly through BIS_ACTUAL_PUB, which wraps and calls its private counterparts. Custom integrations that load actuals—such as external flat-file or interface-table loads—should call the public package rather than this private one, although direct calls are technically possible when the caller passes a valid API version and handles return status and error tables correctly. Within EBS, the package is exercised by the Balanced Scorecard personal homepage, summary reports, and any concurrent program that imports actual performance data. Because it is a private package, Oracle may alter its interface between patches, so custom code should be validated after each upgrade within 12.1.1 and 12.2.2 environments. Developers should always check x_return_status before committing and should pass p_commit explicitly where transactional control is required.