Search Results bis_actual_values_s

Overview

BIS_POSTACTUAL is a PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite environment, classified under the general "OTHER" API category rather than as a formally versioned public interface. Its central purpose is to load or "post" actual performance results into the Oracle Balanced Scorecard (BIS) data model. The package takes raw actual values — typically collected from feeder systems, spreadsheets, or other EBS modules — and writes them into the actual values tables that drive Balanced Scorecard scorecards, key performance indicators, and strategy dashboards.

The object is reported as VALID in the ETRM metadata, and the dependency list confirms its role as a data-posting utility rather than a general-purpose library. The name itself ("POST ACTUAL") signals that the package performs an insert/update operation against stored actuals, as distinct from packages that merely retrieve or validate data.

Key Procedures and Functions

• POST_ACTUAL — The primary entry point. This routine accepts actual measurement values and posts them into the BIS actual values schema. It handles the persistence logic, including determining whether a value should be inserted as new or updated against an existing record, and interacts with FND_API and FND_GLOBAL for standard API error-handling conventions and session context (for example, the current user and login).
• GET_START_END_DATE — A helper routine that derives the effective start and end dates for a posting operation, typically by resolving the calendar or period boundaries relevant to the actual being recorded. It draws on GL_PERIODS to determine period start and end dates, ensuring that posted actuals are aligned to the correct accounting or scorecard period.

Both procedures are documented in the 12.1.1 metadata; no parameter lists are published, so callers should consult the package specification and reference the dependency list when constructing invocations.

Tables Accessed

• BIS_ACTUAL_VALUES — The principal target of the posting logic. Actual performance results are written here.
• BIS_ACTUAL_VALUES_S — The sequence or surrogate-key table associated with BIS_ACTUAL_VALUES. The user query "bis_actual_values_s" points directly at this object; it is used to generate unique identifiers for newly posted actual records.
• BIS_TARGET_LEVELS — Consulted to resolve the target level (organization, scorecard, KPI, or dimension level) to which an actual value applies.
• GL_PERIODS — Used by GET_START_END_DATE to determine accounting period boundaries for the actual.
• HR_ALL_ORGANIZATION_UNITS — Referenced to resolve organization context, allowing actuals to be posted against the appropriate business unit or organization.

Additional dependencies on BIS_UTIL, FND_API, FND_GLOBAL, and the STANDARD library indicate that the package follows Oracle's standard API conventions for error handling, message stacking, and session initialization.

Usage Notes

BIS_POSTACTUAL is not referenced by any other database object and is not a public API in the FND_API sense; it is invoked by the Balanced Scorecard application layer, typically through a concurrent program or an internal call from the BIS posting engine. Administrators and developers integrating external data into the Scorecard should call POST_ACTUAL to load actuals, passing values that already identify the correct target level and period. Because the package relies on GL_PERIODS and HR_ALL_ORGANIZATION_UNITS, callers should ensure the relevant period and organization are defined before posting. Custom code should avoid direct DML against BIS_ACTUAL_VALUES and use this package instead to preserve integrity and standard error handling.