- Site level integration with EBS enhanced: EBS-DM integration enhanced to allow clients collect historical sales into Demantra from EBS Order Management at account or customer level of Site hierarchy. This used to be a typical customization at client locations and with this option surely customers with EBS integration implementing Demantra or looking for upgrades will be able to leverage this OOTB feature now. Implementing this option will also take care of concerns in later upgrades/patches to EBS side as this becomes a supported option.
- Improved Security: Earlier releases used HTTP calls to communicate between modeler/engine/application server mainly, also allowed a user within firewall to launch engine or other calls if they had the right URL. Calling methodology now uses database layer & oracle wallet to improve security.
- Enhanced Workflow Tool: Few small but handy changes like SAVE AS option to copy a workflow definition & ability to view(no changes allowed if not an owner) workflow definition owned by other users. Additionally an importance enhancement to allow indicating in workflow step, from which step workflow should restart in case of failures. This surely adds to recovery ability of workflows.
- Global instance enhanced timezone support: User's timezone will be considered in worksheets or any other user actions like simulation launch. E.g. history and first forecast bucket will transition based of user's timezone and not based of instance system timezone.
- Intermittent flag to IO: Inventory Optimization module now gets an intermittency indicator along with Forecast and forecast accuracy which it leverages to improve Safety stock & Service level.
- Mobility Support enhanced: Demantra Anywhere now supports most regular worksheet functionality, additionally users can launch methods, run simulations, and introduce new products.
- GUI: Improved GUI for better user experience. New release also allows selecting a pre 7.3.1.4 UI or revised 7.3.1.4 UI or latest 12.2.5.1 interface.
Oracle Supply Chain Planning and Business Intelligence Products - A blog dedicated to Oracle's Fusion/On Prem VCP and BI offering.
Saturday, March 5, 2016
Demantra 12.2.5.1 New Features
Sunday, January 18, 2015
Tuesday, July 30, 2013
Oracle's Demantra 12.2.1 released !
Oracle last month released 12.2.1 version of Demantra. This version was long over due for release and it finally is available for all customers. One can download the new version from Oracle's E-Delivery.
Though be careful, as this version can either be installed as stand alone or it can be installed along with VCP 12.2.1 version only. For using the VCP/EBS - Demantra standard integration, one has to be a 12.2.1 version of VCP.
One of the key feature of this release is having the ability to utilize both weekly and Gregorian calendars in one data model itself.
Thursday, September 20, 2012
New "Guided Resolution" for Demantra
They have started with five topics:
- Data loading related issues (Note Id 1461899.1)
- Data loading issues not related to error codes (Note Id 1468884.1)
- Workflow related issues (Note Id 1353217.l)
- Worksheet related issues (Note Id 1486639.1)
- Engine related issues (Note Id 1486634.1)
How to Use the Demantra Guided Resolution, a Proactive Services Tutorial. Note 1473992.1
Sunday, July 8, 2012
Demantra: Engine Status Check
Checking status of Engine:
To determine if engine is running or not, one can use the work_status parameter in init_params_0 table. Value_float column indicates if the current or the last engine run was in batch mode or simulation mode.
- 99 => Simulation Run
- 1=> Batch Run
Value_date reflects the current state of engine. If the value_date changes every 22 sec then it would mean that Engine is running currently.
As Engine can only run in one mode at a time, it helps to be aware of the current state of engine prior to launching engine run.
Sunday, June 3, 2012
Demantra 7.3.1.3 version released
Following are few key new features:
- Integration with Asset Intensive Planning Applications.
- DM module is now integrated with cMRO(Complex Maintenance Repair & Overhaul) module of Oracle EBS application. Integration empowers using Demantra's capabilities to build non-unit maintenance plan forecast and to support deriving planning factors accurately for cMRO module.
- DM module is also integrated with eAM(Enterprise Asset Management) module of Oracle EBS application. The integration let's Demantra users to generate a non-maintenance forecast and then use it further with ASCP and cMRO to support planning for maintenance activities.
- Ability to run database health check using standard procedures. Flexibility to run a quick or a comprehensive test has been provided.
- Additional improvements on PTP/TPMO engine are also part of this release.
Refer to document ID 1453644.1 on Metalink for more details about this new release.
Monday, June 6, 2011
Integrated Causal Exponential Model (BWint)
Tuesday, March 2, 2010
Understanding Forecast Bias

- Forecast1 has a positive forecast bias
- Forecast2 has a negative forecast bias
- Forecast3 has mixed bias and the cumulative bias in such case could be insignificant
Decision on whether a forecast is biased or not can be made by reviewing the forecast error as well, study the example below.

Thursday, February 18, 2010
Thursday, January 21, 2010
Model codes used in MDP_MATRIX
H Holt
J Regression FOR Intermittent
K Multiplicative Monte Carlo Regression FOR Intermittent (ICMRegr)
L Transformation Model (log)
R Regression
E Combined Transformation Model (elog)
C Multiplicative Monte Carlo Regression (CMReg)*
B Integrated Causal Exponential Model (BWint)
F Croston For Intermittent
G Logistic*
A ARLogistic*
X Auto and Linear Regression (ARX)
V Integrated Auto and Linear Regression (ARIX)*
D DailyMultiplicativeRegression*
T Naive Holt
N Naive (if all models failed, a moving average forecast is generated)
NULL No forecast attempt made on this combination.
M Modified Ridge Regression*
NONE Combination remains non forecasted yet, not processed by engine.
E.g. MODEL column has value BFR for a combination, this means engine used models B, F and R to generate Bayesian combined model forecast.
Detailed information about models and parameters is available in Demantra implementation guide.
Refer to "My Oracle Support"
Oracle Demantra Documentation Library [ID 443969.1]
Wednesday, September 30, 2009
Demand Management Process & Demantra’s Solution
Sensing Demand
Demand data should be collected from various possible sources and which can be treated as “BIBLE” for basing your forecast on. Not only actual sales data but other attributes of sales data like promotional causals, holidays, events etc. should be brought in, which justify the variations in demand data. E.g. Sales data collected from various Retailers’ store varies with days on which store is open, promotions which were launched at the store and competition activities near store’s location. So while predicting sales at these stores we should consider all these factors as well.
Demantra implementation offer real-time Demand sensing capabilities, collect demand data and information from various sources like sales orders, shipments, POS data, distribution center data, customer data and marketing data. Demand can be collected inside Demantra on daily or weekly basis as per the requirements.
Shaping Demand
There are items & locations for which sometime sales data is not available, in that case Demand Planners based on their instincts & experience should be able to enter or edit the sales history. Not only history of sales but forecast numbers generated by engine is likely to be edited to consider inputs which have not been captured by the Analytical Engine.
Oracle Demantra Demand Management provides user ability to define override series for each of collected series and also for forecast series. Demantra provides flexibility to create unlimited number of Causal Factors to capture the information which can describe the demand variance and events which occurred. Causal Factors are created and used to ensure that impacts of these factors are taken into consideration by Engine to generate the Forecast numbers.
Collaboration
For any organization the problem of keeping all the stakeholders who represent various verticals like Manufacturing, Marketing, Sales, Retailers, etc. is very common. Today most of the firms are into global markets and have operations and sales happening in various corners of world. Also to become a demand driven supply chain network, the need of having collaboration with all the demand nodes (e.g., customer’s stores) and supply nodes (e.g., raw material supplier’s factory) becomes vital for most of the industries.
The Demantra application provides an easy to use tool for collaborating with all the stake holders using a web based platform. Users can easily collaborate with their internal stakeholders & customers to better predict their forecast. Also all the stakeholders can be informed and kept in loop to reach to final Consensus Forecast number.
Alerts, Exceptions & Notifications
In most of industrial scenarios it becomes difficult to analyze and to figure out the issues like Demand plan crossing the budget limits, import data failures etc. Thus the automated notifications can assist the planners and managers to take up remedy actions. Alerts can be created within Demantra for notifying stakeholders and concerned group of users on Real-time basis. Automated workflows keep all the users notified and updated if there are any exceptions meeting defined conditions.
Wednesday, June 3, 2009
Notes from Today's Webcast on "The Key to Optimizing Demantra Worksheet Performance"
Wednesday, May 27, 2009
Upcoming Demantra Webcast from Oracle
Advisor Webcasts offer a convenient way for you to interact with professional, technical, and application experts regarding topics such as troubleshooting tips, best practices, new release information and more.
Webcast: The Key to Optimizing Demantra Worksheet Performance
- Topics will include:
- Java Plugin Settings
- Creating Worksheets in the optimal manner
- Backend Database Checks
- Application Server Settings
- Other options when your worksheet performance doesn't meet your needs
A short, live demonstration and question and answer period will be included. "
You can register for this webcast from the link provided in the metalink note. (Id provided at the beginning of this post).
Thursday, May 14, 2009
Forecasting Basics: Qualitative Approach
Saturday, December 13, 2008
Demantra: Analyical Engine - A deeper look - Part2
Analytical Engine's Demand planning(DP) mode run comprises of Prepossessing stage, followed by model application & testing stage. In Promotion Effectiveness(PE) mode run of engine, various promotional CFs are prepared and used before Forecast phase starts.
Forecast Phase of Engine Run:
Pre-processing Stage:
1. Treatment of missing values.
2. Detection of intermittency.
3. Preliminary outlier and regime change detection.
4. Removal of obvious (gross) outliers.
5. Data transformation for use in specific models.
Model application & Testing Stage:
1. Checking that the number of data points exceeds at least by two the number of causal factors. This is done to ensure that, No over-fitting occurs and coefficients for all causal factors can be determined.
2. Estimation. Statistical algorithms, are implemented to data and their parameters are calculated.
3. Fit and Residuals calculation. Fit is calculated by applying an estimated model to the historical period. It reflects the ability of the model to reproduce the actual series. The deviation of fit from the actual forms the residual series. The variance of residual, along with complexity (number of estimated parameters) is utilized to compute the weights for model averaging.
4. To check the ability of a model to mimic the actual series, a Fit validation is performed, provided the nableFitValidation flag is on.In Fit validation the residuals undergo a battery of statistical tests.Forecast performs identical calculation to Fit, only for the future period, lead.
5. To perform Forecast validation, both the parameter EnableForecastValidation and the variable ValidFit have to be “True”. This is because if a model reached this stage with invalid fit, it must be running at the highest forecast level, and at this level forecast validation is disabled, allowing a somewhat more liberal treatment of models. In Forecast validation models undergo three tests:
• A test for an unusual zigzag-type jump
more details on Demantra's Engine can be found in Oracle Metalink's Documentation library for Demantra.
Tuesday, December 9, 2008
Demantra: Analytical Engine - A deeper look - Part1
What is Forecasting
Forecasting empowers one to predict the futuristic tendencies of supply chain, influenced by seasonal and other predictable factors. The result of forecast is a projected curve that has been smoothed to show tendencies and de-emphasize the exceptional variations.
Demantra engine is capable of multidimensional forecasting with mixed modeling techniques. It has been designed to be robust enough for handling large scale installations. It is capable of modeling hundreds of thousands of data sets with various data patterns.
Modeling is performed according to forecast tree, in which each node in the tree is defined by an item-location combination in the Enterprise Data model. Engine tries to generate forecast at lowest level of item-location combination, but in situations where due of data insufficiency's , it is unable to generate a good forecast, then it traverses the Forecast tree to higher level for generation of forecast at an aggregated level. Forecast generated at higher level is split down to lowest level, using a splitting mechanism called “proport”.
Batch verses Simulation
Engine can be executed in two modes, Batch or Simulation.
Batch Run:
Traverses a large forecast tress, described in database. Each node in tress represents a time based data series that is subjected to forecast.
Performs model calculation on a large subset of data series (each node of forecast tree)
Writes the processed data series to a new forecast table in database.
Executes a post-process procedure which updates new forecast table
Simulation Run:
Same steps as above are performed but on a selective subset of data, as chosen by user for “what-if” kind of simulation run.
Engine Components
Engine consists to two components, Engine manager and Engine server. There is one instance of Engine manager and one or more instances of engine server. The engine server scans a portion of the forecast tree according to the traversal rules, and sends the output to the split mechanism.
The engine server receives IDs of tasks from Engine manager, which divides the forecast tree into sub-trees (tasks). The engine manager is responsible for the engine run as a whole.Based on Engine settings done via Engine Administrator application, Engine managers tries to initiate an engine server on list of machines on network having engine registered and server component installed.
Reference “Details of Engine Manager & Server”. (source: Oracle Demantra Engine Guide v.5.2.6)
Causal Factors
Factors which cause the deviation from a trend, are known as Causal Factors. E.g. a sales promotion, due of it’s result you expect sales to rise. On the other hand, a sales promotion by your competitor can impact your sales negatively, which also becomes a causal factor.
Causal factors such as promotions, marketing campaigns and production stoppages are essential components when analyzing demand pattern.
Global Causal Factors effect all the nodes of forecast tree, seasonal CFs are normally global.
Local CFs can be different for each item-location combination.
Event is another word for CF, it can be loaded easily with Code, value and intensity information. Event information is not necessarily required to be loaded in future.
............to be continued.
Sunday, November 16, 2008
How is "Demantra different from ODP" ?
Wednesday, October 29, 2008
Demantra Forecasting Models- Part2
7. Multiplicative Monte Carlo Regression(CMReg): This model comes into picture for both DP &PE mode run as well, and utilizes long Causal Factors.
Thursday, July 17, 2008
Oracle Demantra: Seeded EBS-DM integration data flow
In EBS-DM integrated environment, one can start the process of demand planning, with responsibility "Demand Management System Administrator" .
The process starts with Collection of master/transactional data (item, location & sales) from EBS and ends with publishing back consensus forecast to Oracle supply chain planning application. Demand Administrator logs into the Demantra responsibility and starts the Collection program, downloads the master and historical data into Demantra application using seeded workflows, kicks off a workflow to execute the analytical engine in batch mode, makes manual adjustments/overrides on forecast with information like causal factors and promotions and finally runs another workflow to upload the forecast back into APS/MRP.
Demand planning using Demantra Demand Management application compromises of following high level process steps:
- Collection of Dimensional, historical, pricing, costing and other reference data
- Validate & Modify data
- Generate Baseline Forecast
- Consolidate Baseline, Simulation and manual forecasts
- Upload Final Forecast to ASCP/SNO/IO/MRP
- Archive Monthly Forecast
Thursday, May 1, 2008
Statistical Process Control : Using Demantra
Statistical Process Control: A tool to monitor forecasting process, identifying those SKUs whose forecast error is going out of set of limits and those whose error are under control.
Benefits: Reduces time required by Analysts for forecast analysis and lets him focus on area of concern instead of wandering through all the SKUs.
Set Performance indicators like health signals for forecast and define alerts/exception raising conditions, say:
Forecast Accuracy <>
95% <> 95% Medium Level AlertAutomated Alerts/
Exceptions: Create setup for invoking alerts/exceptions automatically as and when required during the demand planning cycle. Ex. Raising alerts just after forecasting engine completes batch run, raising alerts after final forecast is approved, and so on.
Notifications: Configure your tool to send automated notifications to concerned business users to keep them updated with what chunk of data they should be analyzing for resolving the raised alerts.
Here is an example of how the same can be achieved by using Oracle’s Demantra application:
Customization Required:
Option1:- Create Exception worksheets with all the SKUs data in it, with Forecast accuracy related series- Put exception condition & Save worksheet definition- Create a workflow with exception step which can be launched by analyst using a Level method from worksheet or directly from Workflow manager page. - Send alerts to Analyst for any exceptions found
Option2:- Create Exception worksheets with all the SKUs data in it, with Forecast accuracy related series- Put required exception conditions- Write custom code to call up run workflow at end of every forecasting cycle.- Send alerts to Analyst for any exceptions found by calling these custom codes


