Search Results get_bsc_fnd_owner

Overview

APPS.BSC_BSC_XTD_PKG is a PL/SQL package belonging to the Oracle Balanced Scorecard (BSC) application module within Oracle E-Business Suite. Its primary business function is to support the calculation, storage, and maintenance of extended (XTD) and rolling-period reporting data used by the Balanced Scorecard reporting engine. The package manages the runtime generation of report calendar keys, the population of period-based report keys, and the alignment of Scorecard KPIs against system calendars and periodicities. The header comment references BSCRPTCS.pls and a creation date of 2006, indicating the package has been part of the BSC reporting framework for many releases, and it remains present in both EBS 12.1.1 and 12.2.2.

The package exposes a set of PL/SQL collection types (varchar_tabletype, number_tabletype, boolean_tabletype, date_tabletype) and a record type (xtd_record) that captures session, KPI, report date, and periodicity information. Global variables such as g_roll_year_range, g_roll_qtr_range, g_roll_period_range, and g_roll_week_range define the window sizes used when generating rolling-period report keys (365, 90, 30, and 7 days respectively).

Key Procedures and Functions

The ETRM documentation lists 21 procedures and functions. The principal public routines include:

• OPEN_FILE — Opens the output file used to record processing activity or errors.
• POPULATE_RPT_KEYS — Overloaded procedure/function that populates report calendar keys for a given session, KPI, report date, period, and periodicity, supporting both ROLLING and XTD modes.
• POPULATE_ROLLING_RPT_KEYS — Specialized routine for generating rolling-period keys across the configured day, week, quarter, and year ranges.
• POPULATE_RPT_KEYS_DAILY — Variant that builds report keys for daily periodicity.
• PARSE_VALUES — Parses option or parameter strings into usable values.
• INSERT_RPT_CAL_KEYS and CORRECT_RPT_CAL_KEYS — Insert and correct entries in the report calendar key table.
• CORRECT_ROLLING_DATA and CORRECT_ROLLING_DATA_92_91 — Correct previously generated rolling data, including a version-specific routine for release 9.2/9.1 data.
• DELETE_RPT_KEYS and DELETE_TABLE — Remove report keys or tables as part of cleanup.
• CREATE_RPT_KEY_TABLE and DROP_RPT_KEY_TABLE — Create and drop the temporary report key staging table.
• GET_BSC_FND_OWNER — Returns the schema owner for BSC and FND objects.
• INIT — Initializes package globals and options prior to processing.
• GET_DAY_COUNT — Returns the count of days for a given period, central to rolling-period calculations such as the "get_day_count" query the user searched for.
• IS_DAILY_PERIODICITY — Determines whether a periodicity is daily.
• GET_TIME — Returns a time value used during key generation.

Tables Accessed

The package references several BSC and system tables through APPS synonyms:

• BSC_RPT_KEYS — The primary repository of generated report keys.
• BSC_KPI_PERIODICITIES — Defines which periodicities apply to each KPI.
• BSC_SYS_CALENDARS_B — Base table of system calendar definitions.
• BSC_SYS_PERIODICITIES — System-level periodicity definitions.
• ALL_TABLES — Used to check existence of report key or temporary tables.
• PLITBLM — Internal PL/SQL table used in parsing or bulk operations.

Usage Notes

BSC_BSC_XTD_PKG is typically invoked by the Balanced Scorecard report generation framework, including concurrent programs that refresh KPI report calendars and rolling-period data. It is referenced by two other packages and is intended for internal BSC use rather than direct end-user invocation. Custom code should treat it as an internal API; the GET_DAY_COUNT function in particular is used during rolling-period key derivation to establish day-count ranges.