Oracle Supply Chain Planning and Business Intelligence Products - A blog dedicated to Oracle's Fusion/On Prem VCP and BI offering.
Wednesday, November 17, 2010
Demantra 7.3: Engine split based on series
Demantra 7.3 has come up with quite few features which customers have been wishing to see. One of these is ability to split statistical forecast which generated at aggregated level to split down to lowest level based on user defined/controlled proportions. Prior to 7.3 this split was always based on historical proportions and there was no workaround for it. These historical proportions were calculated based on every product and location combinations historical monthly sales averages using proport procedure. Split by series option allows user to pick a series which dictates weights for dis-aggregation of baseline forecast.
How we USE it?
1. Define a new series with server expression, the server expression gets used in weight calculation.
2. Using Business modeler setup parameter: ENGINE > PROPORT tab > parameter name "ProportionSeries" shall be populated with the internal name of the above series.
3. Select combinations/population to use SPLIT MECHANISM by using series "Engine Proportion Method" in a worksheet. The series has two dropdown values, Matrix Based Proportions which is the default and Series Based Proportions which is the value required for series based split.
Monday, August 9, 2010
Oracle Open World 2010: Sales and Operations Planning for the Food and Beverage Industry
http://www.eventreg.com/cc250/sessionDetail.jsp?SID=315911
Friday, June 18, 2010
Oracle E-Business Suite, Virtualization and Cloud Computing
New and Valuable Capabilities in this Oracle Release
February 3, 2010,
Volume 144, Issue 1
In a five-part series on virtualization and cloud topics, Ivo Dujmovic, an architect in Oracle's Applications Technology Integration group, offers a detailed view of the Oracle E-Business Suite 12.1.1 for prospective and current users.
Read the complete article by clicking on this link "Oracle E-Business Suite, Virtualization and Cloud Computing"
Friday, April 16, 2010
Cloud Computing
Definition:
It has essential characterstics of on demand self service, resource pooling, rapid elasticity to scale out and scale in, the ability to meter who is using what and broad network access.
Three service models for cloud computing are:
1. SaaS software as a service, is a prebuilt, vertically integrated application/solution delivered to customer as a service.
2. IaaS infrastructure as a service, is purely providing computing resources, storage and network, as service to the client.
3. PaaS platform as a service. is a flexible combination of above two service models and thus customer can develop and deploy their own application using best of both the worlds.
1. Public cloud, is shared across multiple customers or tenants and is hosted and managed by a service provider.
2. Private cloud on the other hand is exclusive for an organization and is controlled and governed by that organization.
3. Hybrid cloud is where an organization with a private cloud model uses public clouds for any excess cloud service requirements occassionally. Eg an overflow or for additional workload needs
4. Community cloud is a semi private cloud with access to only a set of defined tenants who share backgrounds or needs
What is driving clouds ?
AGILITY AGILITY AGILITY
The fact that users can provision resources on demand, acquire more resources when needed and release them when done with them, is the key driver for cloud computing.
Any drop off which may occur in the interaction happening between two clouds, might just mean a complete loss of valuable services. It is like two clouds up in the sky and informatiin flashin like lightening going from cloud to cloud and cloud to ground, the possibiltiess of loss of energy is inevitable and that is where the core problem of cloud computing lies.
Amazon web services are already in this niche market. For a public cloud to become a feasible solution for small businesses, the need to ensure the security of transaction and data.
Google OS is another such initiative where we will see a huge participation and usage of cloud computing capabilities.
Wednesday, March 3, 2010
Demantra SIG Webinar: "Infrastructure Rationalization for Demantra Environments"
"Demantra SIG Webinar - 03/10/2010 | ||||||||||||||||||||||||||||||||
|
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
Fueling supply chain with retailer's POS data - Oracle DSR
- Lost sales due to out of stock conditions
- High inventory carrying cost due of misplaced stocking
- Promotion expenses going in vain
- Loss of margins due of expedition costs
- Increasing IT Complexity

- Capture and manage large volumes of disparate external demand data
- Analyze, report and take action based on Day/SKU/Store level insights
- Integrate clean, harmonized demand data to external applications
- Greater visibility of data to better sense, shape and respond to demand
- Reduce manual effort and cost
- Simplify collaboration across teams and applications.
Wednesday, February 10, 2010
Exploring Demantra's BPM capabilities
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, January 20, 2010
News: Oracle Integrates Financial, Operational Planning
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
Tuesday, January 12, 2010
Engine enhancements in Demantra 7.3 release
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.