Results for “msc_get_bis_values”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_GET_BIS_VALUES is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Advanced Supply Chain Planning (ASCP) and Business Intelligence/Decision Support (BIS) functional area. Its principal business role is to supply the calculation, aggregation, and retrieval logic that drives the BIS (Business Intelligence System) performance-measure infrastructure used by Oracle's planning applications. The package acts as a shared utility layer: it evaluates business intelligence targets, computes period-based actuals, derives service-level and margin metrics, and constructs the dynamic SQL WHERE clauses used by the BIS materialized-view reporting stack. Because the package is recorded as VALID in the ETRM metadata for both 12.1.1 and 12.2.2, it remains an active, supported component of the supply chain planning schema in these releases.

The package is not a public API in the traditional sense; the API classification is OTHER, indicating it is primarily an internal implementation dependency invoked by other BIS packages and concurrent planning engines rather than by external integrations.

Key Procedures and Functions

The documented interface exposes 32 procedures and functions. The most significant are grouped below by purpose:

• Margin and trend analytics: GET_MARGIN, GET_ITEM_MARGIN, GET_ITEM_MARGIN_TREND, GET_MARGIN_TREND, and GET_MARGIN_BY_ORG compute gross-margin and item-level margin values, including historical trend series and organization-specific breakdowns.
• Targets and actuals: GET_ACTUALS, GET_TREND_ACTUALS, GET_TARGETS, and GET_TARGETS_TREND retrieve measured performance against defined targets, supporting period-over-period comparisons.
• Service-level analysis: GET_SERVICE_LEVEL, SERVICE_DATA_EXIST, SERVICE_TARGET, and SERVICE_TARGET_TREND evaluate service-level attainment and verify whether underlying data exists before reporting.
• Period and date handling: GET_PERIOD_NAME, CHECK_PERIODS, and POPULATE_PLAN_DATE resolve planning calendar periods and populate plan-date context needed by downstream BIS queries.
• Order and demand analysis: LATE_ORDERS identifies past-due demand, typically for exception reporting.
• Dynamic WHERE construction: CONSTRUCT_BIS_WHERE, CONSTRUCT_RES_WHERE, and CONSTRUCT_RES_INSTANCE_WHERE assemble the predicate clauses used by BIS materialized views and resource-summary queries, enabling flexible filtering by plan, organization, and period.

No parameter lists are documented in the metadata; these procedures should be treated as internal and inspected in the database before direct invocation.

Tables Accessed

The package reads and writes a defined set of BIS and planning tables through APPS synonyms, including:

• BIS configuration and results: MSC_BIS_BUSINESS_PLANS, MSC_BIS_PERFORMANCE_MEASURES, MSC_BIS_TARGETS, MSC_BIS_TARGET_LEVELS, and MSC_BIS_PERIODS — the core definitions of plans, measures, targets, and reporting periods.
• BIS aggregates and materialized views: MSC_BIS_INV_CAT_MV_TAB, MSC_BIS_INV_DATE_MV_TAB, MSC_BIS_RES_DATE_MV_TAB, MSC_BIS_RES_SUMMARY, MSC_BIS_INV_DETAIL, and MSC_DEMAND_MV_TAB — pre-aggregated inventory and resource summaries consumed for fast reporting.
• Planning and demand sources: MSC_DEMANDS and MSC_BOM_COMPONENTS — demand and bill-of-material data that feed margin, service-level, and late-order calculations.
• Foundation references: FND_ORACLE_USERID and FND_PRODUCT_INSTALLATIONS — used to resolve schema/user context and confirm installed products.

Usage Notes

MSC_GET_BIS_VALUES is referenced by three other packages, most notably MSC_ANALYSIS_BUDGET, MSC_ANALYSIS_SAFETY_STOCK, and MSC_BUDGET_DETAILS, which invoke it to populate budget, safety-stock, and detail-level analytics. It is therefore executed indirectly during BIS concurrent program runs and planning data collection, not through a dedicated form or user-facing screen. Custom code should avoid calling the package directly where possible, since its interface is undocumented and may change between patch levels; where direct invocation is unavoidable, the caller must supply the correct plan and period context and should validate results against the standard BIS reports. Because the package constructs dynamic SQL, DBAs should ensure that the APPS schema retains the necessary privileges on the referenced synonyms in both 12.1.1 and 12.2.2 environments.