Results for “is_global_scenario”

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

Overview

MSD_DEM_UPLOAD_FORECAST is an Oracle EBS PL/SQL package owned by APPS that supports the Demand Planning and Advanced Supply Chain Planning (ASCP) integration flows within the ETRM (Enterprise Territory and Resource Management) / MSD schema family. Its primary business function is to upload forecast data, planning percentages, total demand, and related demand-scenario metrics from a staging or denormalized form into the structures consumed by the planning engine. The package also installs forecast data into an ASCP instance, manages global versus profile-scoped scenarios, and controls the timing of upload execution.

The constants declared in the specification reveal the design intent. Uploads are categorized by data profile type (import, export, or combined), bucket granularity (day, week, month), time level, export mode (full or incremental), and forecast series prefixes such as FCST_, ACRY_, PRTY_, and DKEY_. The user's query term, is_global_scenario, corresponds directly to the documented function IS_GLOBAL_SCENARIO, which classifies whether a given demand scenario is global in nature and therefore eligible for global forecast upload processing.

Key Procedures and Functions

• GET_SR_INSTANCE_ID_FOR_GLOBAL — Returns the SR instance identifier used for a global forecast, distinguishing global-scope uploads from profile-scoped ones.
• GET_SR_INSTANCE_ID_FOR_PROFILE — Returns the SR instance identifier appropriate for a specific data profile.
• IS_GLOBAL_SCENARIO — Evaluates and reports whether the scenario under consideration is a global scenario. This governs which upload path the package follows.
• IS_VALID_SCENARIO — Validates that a scenario qualifies for upload; the excerpt notes that a forecast series with an internal name beginning FCST_ is part of this eligibility check.
• GET_ERROR_TYPE — Returns the error classification produced by validation or upload processing.
• GET_CUSTOMER_FROM_TPZONE and GET_ZONE_FROM_TPZONE — Derive customer or zone identifiers from a trading-partner-zone mapping.
• CHECK_UPLOAD_LAST_RUN and WAIT_UNTIL_UPLOAD — Provide concurrency and sequencing control, ensuring an upload does not overlap or begin before a prior run completes.
• UPLOAD_FORECAST, UPLOAD_FORECAST_WITH_APP_ID, UPLOAD_CTO_FCST_WITH_APP_ID, and UPLOAD_SPF_INC_FORECAST — Perform the core forecast uploads, including CTO-specific and SPF incremental variants.
• UPLOAD_PLANNING_PERCENTAGES, UPLOAD_PLNG_PCTG_WITH_APP_ID, and UPLOAD_CTO_PLNG_PCT_DIRECT — Push planning percentage data into the planning repositories.
• UPLOAD_TOTAL_DEMAND, UPLOAD_TO_CP, UPLOAD_SPF_METRICS, and GET_TIME_STRINGS — Handle total demand, connection-processor transfer, SPF metric loading, and time-bucket string generation.

Tables Accessed

• MSC_APPS_INSTANCES — Resolves the source and destination ASCP application instances for cross-instance uploads.
• MSC_DMD_SCN_METRICS — Stores demand scenario metrics that are loaded or refreshed during SPF and metric uploads.
• MSD_DP_SCN_ENTRIES_DENORM and MSD_DP_PLANNING_PCT_DENORM — Denormalized source structures for scenario entries and planning percentages.
• MSD_DP_PLANNING_PCT_TMP — Temporary working table used during planning-percentage upload processing.
• MSC_SYSTEM_ITEMS, MSC_REGIONS, MSC_TP_ID_LID — Provide item, region, and trading-partner identifier mappings needed to resolve keys.
• DBMS_LOCK, DBMS_RANDOM, DUAL, and PLITBLM — Support locking for concurrency control, randomization, scalar queries, and bulk PL/SQL table handling.

Usage Notes

This package is typically invoked from concurrent programs, planning engine integration jobs, or custom PL/SQL that orchestrates forecast publication into ASCP. The presence of CHECK_UPLOAD_LAST_RUN and WAIT_UNTIL_UPLOAD indicates that callers should expect coordinated, serialized execution rather than parallel invocation. When integrating custom code, callers should first evaluate IS_GLOBAL_SCENARIO and IS_VALID_SCENARIO to select the correct upload path, and should use the appropriate C_* constants to supply profile, bucket, and export-mode values consistently. The package is referenced by seven other packages, so modifications to its public signatures can impact dependent planning objects across Oracle EBS 12.1.1 and 12.2.2 deployments.