Oracle Supply Chain Planning and Business Intelligence Products - A blog dedicated to Oracle's Fusion/On Prem VCP and BI offering.
Wednesday, July 23, 2008
Demantra 7.2 New Features
1. Support for multiple forecast streams: With this release Oracle has overcomed the missing ability of support for generating and managing multiple forecast in Demantra product. This has been developed using Engine profile options and system of forecast versioning. You can now create more than one forecast based on different historical data, like Forecast based on Shipment history, Forecast based on Booking history, Forecast based on Customer POS, etc.
Setting up multiple forecast generation is pretty straight forward, one just needs to define separate engine profiles with "Quantity from" parameter pointing to different history data. One can view and analyse these multiple forecasts generated by the engine, in worksheet as usual and can utilise forecasted booking trends to compare with forecasted shipment trends. This feature has for sure added a missing card into the pack of capabilities offered by Demantra product.
2. Enhanced Engine Performance: Demantra's Analytical engine, often referred as heart of the Demantra Suite has been improved by cutting down the processing time. Unlike older version, for combinations which have been forecasted already in previous runs existing branch allocation will be used now on. This cuts down the engine run time, as there are only few new combinations and thus allocation of branch happens only for them. Besides this, with few other changes has been done on engine side, to enhance Engine performance.
3. Enahnced Worksheet usability: You can now create series with "No Summary" option, thus users don't see any irrelevant numbers as Summary for each of the series. This takes off the compulsion of having a summary function even for Series with data, which doesn't have any significance at Summary level, e.g. Date type series, Approval series etc.
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
Thursday, December 27, 2007
Demantra forecasting models -Part1
Oracle's Demantra Demand Management module only provides 9 basic mathematical models and 6 configurable Causal Factors, rest of the 6 advanced statistical models and flexibility of creating unlimited Casual Factors are given away with Advanced Forecasting & Demand Modeling (AFDM) module.
Demand Management module's forecast library has following set of models for usage:
1. Regression
2. Transformation Model(log)
3. Regression for Intermittent
4. Holt
5. Croston for Intermittent
6. Combined Transformation Model(elog)
7. Multiplicative Monte Carlo Regression(CMReg)
8. Integrated Causal Exponential Model(BWint)
9. Auto & Linear Regression
Let's try to get a feel of what are these models and how they work ?
1. Regression: These models are statistical models which are capable enough of describing the variation(trend/pattern) one or more variable(s), based on the variation of one or more other variable(s). Inferences based on this kind of methodology are known as Regression analysis.
e.g. Variation of Demand of a product in market based on time variation.
2. Transformation Model(log): Log transformation model utilizes the log function which squeezes the large values of data together and stretches the small values apart, thus leading to correction data issues like skewed data, outliers and unequal variation.
e.g. Normally demand data has various such problems, the log transformation model tries to minimize those.
3. Regression for Intermittent: This model uses regression analysis for intermittent kind of data. There are parameters related to defining intermittent part of data in the application.
4. Holt: An extension of exponential smoothing can be used when time-series data exhibits a linear trend.
5. Croston for Intermittent: Croston’s Intermittent Model is specifically designed to deal with sporadic demand (no seasonality) with a two-step process. Croston’s Intermittent model recognizes both : the demand size and the demand occurrence.
.. to be continued
Friday, November 30, 2007
Downloading Demantra - Too many choices
The latest release is 7.2 and is only 2 weeks old. Previous releases are 7.1.1 which now is 6 months old and quite a few implementation of this version are either completed or are towards completion phase. 7.1.0.1 version was the first release made by Oracle, which is more of an Oracle christened Demantra product.
Which one I need?
There are lot many factors which will drive this decision, but the differentiators here in terms of integration offered by Oracle will be a key to decision making.
- Demantra 7.2: For business which wants to do an integrated S&OP using Demantra spectrum.
- Demantra 7.1.1: For those who want to have just the basic Demand Planning environment to start with, but need the integration with EBS.
- Demantra 7.1.0.1: For stand alone Demantra installation.
As per standard practise, it is always recommended to go for the latest version of product when it comes to buying licence of a product. But again points like stability of a release, industry examples, need of business and budget etc. play a vital role in making a call.
Monday, November 19, 2007
What Demantra's 7.2 version has to offer ?
S&OP integration comes in line with the earlier release 7.1 where Oracle integrated Demand Management module of Demantra with Oracle's EBS & JDE E1. Oracle Demantra Demand Management offered an out of box configured web based collaborative demand planning environment for achieving best in class, unconstrained accurate forecast. This unconstrained consensus forecast was then available for being referred and used by down the line Supply chain components and ERP system for supply planning.
S&OP integration on top of it, empowers you to bring in all the capacity & material constraints with all the supply plan information into Demantra application. The inbound integration in 7.2 has grown to ASCP(Advanced Supply Chain Planing) & SNO(Strategic Network Optimization) modules, along with EBS. This seeded integration fetches in supply chain intelligence information & cost data too, for being utilized in S&OP process. Outbound seeded integration available in this release are to ASCP, SNO, IO(Inventory Optimization) & PS(Production Scheduling).
More information on JDE E1 integration with Demantra is available on : "http://www.peoplesoft.com/corp/en/iou/implement/integration/demantra.jsp"
Sunday, November 18, 2007
Oracle Demantra 7.2 released
Getting the Application
Once downloaded you can run the installer and can easily install a stand alone Demantra application demo.
Demanta 7.2 version integrates Demantra S&OP module with Oracle's EBS and provides an out of box configuration for S&OP business process. It also has seeded integration between Enterprise One & Demantra's PTP & DSM modules.
Note:Make sure you follow the Terms & Conditions prescribed by Oracle for usage of the application downloaded from their e-delivery sites.
Friday, November 16, 2007
Demantra 7.2 version Documentation
3. Demantra DSM integration with E1
With this release Oracle has delivered on it's promise to provide a tight integration between Demantra and it's other ERP modules. Looking forward in Demantra deliverables, we should be getting Demantra CTO(Configure to Order) module, Demantra PTP integration with Siebel & Demantra S&OP integrated with Enterprise One.
| Oracle Demantra Demand Management Documentation Library | ||||
| Doc ID: | Note:443969.1 | Type: | LIBRARY | |
| Last Revision Date: | 13-NOV-2007 | Status: | PUBLISHED | |
|