Model codes used in MDP_MATRIX

Here is a list of the coding convention used by Demantra, when populating MDP_MATRIX with information about which models were used(column MODEL) and which weren't.(column DELMODEL)

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]

News: Oracle Integrates Financial, Operational Planning

Oracle Corp. today introduced a packaged integration between its enterprise performance management application and its sales and operations planning software, making it easier for manufacturers to quickly analyze the financial implications of changing customer demand.

Oracle said the new integration between its Oracle Hyperion Planning EPM product and its Oracle Demantra Real-Time Sales and Operations Planning platform is available now. Based on Oracle’s Application Integration Architecture (AIA), the new EPM-S&OP integration provides manufacturers with a way to more easily tie together operational and financial planning processes

.............................................................read the complete article @

http://www.manufacturing-executive.com/news/read/Oracle_Integrates_Financial_Operational_Planning_33238

Engine enhancements in Demantra 7.3 release

Demantra's 7.3 version has come up with quite a few new enhancements on Analytical engine side. The focus has been on improving the forecast performance, making the AE more robust and faster.

The list of few interesting available features are:
1. Forecast split based on series: Earlier the forecast generated at aggregated level used to get allocated down based on monthly proportions calculated during the proport process. This functionality let's you select a series based from where the proportions shall be picked up for splitting the future forecast.

2. Engine deployment on Linux: Analytical engine is no more restricted to be installed on a windows box, you can install Engine on a Linux box. Engine can be even started and stopped remotely from a browser after doing the required configurations.

3. Forecast output threshold: This functionality provides you more control on engine output, by stating whether or not to write engine output to database, if the forecast numbers are not a lot different from the previous forecast numbers. E.g. if new forecast is 10010, while previous forecast was 10000, then you can mention a threshold so that engine would not try to write the new 10010 output to database.

For complete list of enhancements, refer to metalink's Demantra documentation library.

Bajaj Electrical success story - Oracle ERP, JDE, Demantra & Siebel

A video presentation on Oracle's yet another success story on a big bang implementation of Oracle ERP, JDE, Demantra and Siebel.

Updates: Oracle Rapid planning 1.0

Oracle's latest release in VCP suite, Oracle Rapid Planning(RP)'s version 1.0 can be installed only with VCP version 12.1.1