Search Results bis_primary_currency_code

Overview

The APPS.BIS_COMMON_PARAMETERS package body is a central utility component of the Oracle EBS Business Intelligence System (BIS) schema, now commonly associated with the Daily Business Intelligence (DBI) and Embedded Analytics framework introduced in Release 12. Its primary purpose is to act as a single, authoritative access layer for the BIS system's configuration parameters. Rather than each BIS program, view, or collection routine reading profile options and system settings independently, BIS_COMMON_PARAMETERS encapsulates that logic and exposes it through a set of strongly typed getter functions. This provides consistent interpretation of global implementation choices across the BIS product family. The object holds a status of VALID and resides in the APPS schema; it is not referenced by any other database object, meaning it functions as a top-level entry point rather than a dependency of other packages. It is documented under API classification OTHER, indicating it is not a public, supported extension API but an internal supporting package.

Key Procedures and Functions

The ETRM documentation records thirty-eight procedures and functions, of which twenty are explicitly named; the remaining eighteen follow the same naming and caching pattern. The named accessors include:

• GET_GLOBAL_PARAMETERS and CHECK_GLOBAL_PARAMETERS — retrieve and validate the complete set of BIS global parameters, forming the base routine that other getters rely upon.
• GET_IMPLEMENTATION_TYPE and GET_GLOBAL_START_DATE — return the configured implementation mode and the effective start date for BIS data collection.
• GET_CURRENCY_CODE and GET_SECONDARY_CURRENCY_CODE, together with GET_RATE_TYPE and GET_SECONDARY_RATE_TYPE — supply the primary and secondary currency and exchange-rate type used in BIS reporting and conversions.
• GET_PERIOD_SET_NAME, GET_PERIOD_TYPE, and GET_START_DAY_OF_WEEK_ID — return calendar and accounting period configuration used for time-bucketed analysis.
• GET_WORKFORCE_MES_TYPE_ID — identifies the workforce measurement type applied to HR analytics.
• GET_AUTO_FACTOR_MODE — reports the automatic factor mode setting used when generating BIS factors.
• GET_ITM_HRCHY3_VBH_TOP_NODE — returns the designated top node of the third item hierarchy used for value-based hierarchy analysis.
• GET_ITEM_CATEGORY_SET_1, GET_ITEM_CATEGORY_SET_2, and GET_ITEM_CATEGORY_SET_3 — return the three item category sets configured for BIS item classification and reporting.
• HIGH, MEDIUM, and LOW — constants or helper routines defining severity or logging thresholds internal to the package.

Each getter typically resolves a value from profile options and, where applicable, caches it for the duration of the session to avoid repeated queries.

Tables Accessed

The package reads from a narrow set of system and profile tables. FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES are the primary sources of configuration data, since most BIS parameters are stored as profile option values. BIS_SYSTEM_DATE provides the system date reference used for date-sensitive parameters. V$PARAMETER is queried through DBMS_SQL to inspect database initialization parameters, which is why DBMS_SQL and PLITBLM appear as dependencies. FND_PROFILE supplies the runtime profile retrieval interface. The use of V$PARAMETER indicates the package checks settings such as cursor or optimizer parameters that affect BIS collection behaviour.

Usage Notes

BIS_COMMON_PARAMETERS is invoked indirectly by BIS forms, concurrent programs, and collection routines rather than by end users. Any BIS program that needs a currency, calendar, or category-set value calls these getters instead of reading profile options directly, ensuring uniform behaviour. Because it is not referenced by other database objects and is classified OTHER, customers should not bind custom code to it; the supported path is to modify values through the standard BIS setup forms and profile options. The package is dependency-safe for upgrades because it isolates configuration reads in one location, allowing Oracle to revise parameter resolution without impacting dependent BIS programs.