Search Results get_implementation_type

Overview

APPS.BIS_COMMON_PARAMETERS is a shared PL/SQL utility package within the Oracle EBS Business Intelligence System (BIS) product family. Its central purpose is to centralize the retrieval of implementation-level and site-level configuration parameters that many other BIS components require at runtime. Rather than embedding profile option lookups, system date references, and currency or period controls directly within each dependent module, the package exposes a stable set of accessor functions that return the currently effective value for the calling session or responsibility. This design ensures consistent parameter resolution across the BIS schema and simplifies maintenance when underlying storage locations or profile option names change. The package header carries a header revision string dating to 2007, indicating a long-lived and stable interface that has persisted across the 12.1.1 and 12.2.2 releases without structural change. Because it is owned by APPS and classified as OTHER, it is treated as an internal supporting API rather than a public, documented integration interface.

Key Procedures and Functions

The package exposes a broad set of getter functions and a small group of procedural utilities. The documented routines include the following:

• HIGH, MEDIUM, LOW — Return numeric thresholds associated with transaction complexity profiling. Historically these were sourced from profile options BIS_TXN_COMPLEXITY_HIGH, BIS_TXN_COMPLEXITY_MEDIUM, and BIS_TXN_COMPLEXITY_LOW.
• GET_RATE_TYPE / GET_SECONDARY_RATE_TYPE — Return the configured currency rate type and its secondary counterpart used for conversion logic.
• GET_CURRENCY_CODE / GET_SECONDARY_CURRENCY_CODE — Return the primary and secondary functional currency codes.
• GET_PERIOD_SET_NAME, GET_PERIOD_TYPE, GET_START_DAY_OF_WEEK_ID — Return calendar and period configuration used for time-based aggregation.
• GET_WORKFORCE_MES_TYPE_ID, GET_AUTO_FACTOR_MODE, GET_ITM_HRCHY3_VBH_TOP_NODE — Return workforce measurement type, factor automation behavior, and the top node of the item hierarchy value set.
• GET_GLOBAL_START_DATE — Returns a date representing the global starting boundary for BIS processing.
• GET_IMPLEMENTATION_TYPE — Returns a VARCHAR2 describing the customer's implementation classification, used by dependent logic to branch behavior between standard and specialized deployments.
• GET_GLOBAL_PARAMETERS / CHECK_GLOBAL_PARAMETERS — Accept a list of parameter names and return or validate their resolved values, enabling bulk retrieval.
• GET_ITEM_CATEGORY_SET_1/2/3, GET_ITEM_ORG_CATSET_1, GET_ITEM_HIERARCHY3_TYPE — Return configured item category set and hierarchy identifiers.
• GET_MASTER_INSTANCE — Returns the master instance identifier for multi-instance deployments.

Tables Accessed

The package references several underlying objects through APPS synonyms. FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES supply the definition and effective values of the profile options that back most getter functions. BIS_SYSTEM_DATE provides system date context. DBMS_SQL is used for dynamic SQL construction in the bulk parameter routines, while DBMS_SQL.VARCHAR2_TABLE supplies the PL/SQL collection type for parameter lists. PLITBLM and V$PARAMETER are referenced for session and database parameter interrogation. The package does not appear to perform DML; its role is read-only parameter resolution.

Usage Notes

BIS_COMMON_PARAMETERS is typically invoked from BIS forms, concurrent programs, and custom BI extensions rather than directly by end users. Developers should call the discrete getter functions instead of re-querying profile options directly, ensuring consistent behavior. Because the package is referenced by at least seven other packages, modifications to its public signatures carry broad downstream impact. The GET_IMPLEMENTATION_TYPE function in particular is queried when dependent code must determine which implementation variant is active before selecting processing paths.