Oracle Demantra Release 7.3.

1 - Last Updated 01/05/2011

=====================================================
For full installation instructions, please carefully review the Oracle Demantra
Installation guide (dmt_inst.htm) found in the root folder of the installation p
ackage, in particular 'Instructions for Installing this Release'. Also note the
latest patches for any release (including installation guide changes) can be fou
nd on My Oracle Support (formerly known as Metalink) at https://support.oracle.c
om. The latest documentation can be found in the Demantra Documentation Library,
which is My Oracle Support document 443969.1.

Service Parts Forecasting (SPF)

--------------------------------------------------In release 7.3.1, Demantra provides integration with Oracle Service Part Plannin
g (SPP) to generate a demand forecast and forecast accuracy metrics for service
parts (also referred to as spare parts). The forecast can be based on usage hist
ory or shipment history. In cases where there is insufficient history for a reli
able basis, Demantra bases the forecast on the item's install base population an
d average failure rate.
The following changes support Service Parts Forecasting (SPF):
* New workflows and integration interfaces to import service parts usage, sh
ipment history, and install base under contract data into Demantra.
* Calculate failure rates and generate an analytical forecast for service pa
rts. The average failure rate per week is calculated based on install base under
contract data as well as historical service parts consumption.
* New SPF worksheets and related series to view the calculated forecast, sta
tistical forecast, and forecast metrics, and to run simulations.
* New method to incrementally export changes made in Demantra worksheets to
Service Parts Planning.
* Forecast demand for the latest item in a service parts supersession chain
by merging together the history of all items in the chain.
* Define multiple forecasting engine configurations so that a single Demand
Management installation can be leveraged for multiple lines of business that for
ecast in different ways. For example, Supply Chain can use CTO forecasting while
Service Parts Planning can consider different data streams and analytical confi
gurations when generating a forecast.
* Include General Levels in the forecast tree (in addition to Item and Locat
ion levels).
* New engine profiles:
o Forecast Install Base
o Forecast Spares Demand
o Simulation Install Base
o Simulation Spares Demand
* New workflows and integration interfaces to export the service parts deman
d forecast, forecast accuracy metrics, and other data to Oracle Service Parts Pl
anning.
IMPORTANT: If you will be leveraging Service Parts Forecasting (SPF) functionali
ty, refer to the Oracle Demantra Installation Guide, My Oracle Support Document
1226023.1 for important pre and post-installation tasks.

Forecasting for Multiple Business Processes

------------------------------------------------------------In this release, all analytical engine settings can be configured for each engin
e profile. These changes support various business processes, increase configurat

ion flexibility, and support forecasting for service parts (SPF) and manufacturi
ng options. When configuring the forecast tree and causal factors, users can now
choose which engine profile to which the settings apply.
For details, refer to the Configuring Rolling Data chapter in the Oracle Demantr
a Implementation Guide.

Proport Enhancements
--------------------------------------------------The Proport mechanism typically processes a large amount of data and can require
substantial amount of time and resources. In this release, several new system p
arameters can improve Proport runtime performance by enabling parallel processin
g and by grouping the Proport process into several iterations.
For details, see the Fine Tuning and Scaling Demantra chapter in the Oracle Dema
ntra Implementation Guide.

Parallel Hints on Worksheets

--------------------------------------------------Some worksheets access a large amount of data which can cause them render slowly
. A parallel hint can be implemented to improve the performance for specific wor
ksheets and users. A hint specifies the number of threads used by the worksheet
query and can be applied to two parts of the worksheet: generation of the combin
ations and retrieval of data to be displayed.
Note: Setting a hint requires manually adding a row to the WORKSHEET_HINTS table
using SQL Developer or similar tool. Therefore; this task should be performed o
nly by an experienced system or database administrator.
For details, see the Fine Tuning and Scaling Demantra chapter in the Oracle Dema
ntra Implementation Guide.

Rolling Data Profile Groups

--------------------------------------------------In this release, Demantra users can create groups of rolling data profiles and a
ssigned each an ID. All profiles within the group can then be executed by callin
g the profile group ID from a workflow.
For details, refer to the Configuring Rolling Data chapter in the Oracle Demantr
a Implementation Guide.

Deploying Demantra Application Server:

-------------------------------------------------------To deploy Oracle Demantra, create a new WAR file in a Windows environment:
1. After successful completion of the installation, run 'create_war.bat', found
in <Demantra installation root folder>\Collaborator\<virtual directory>. For exa
mple, C:\Demantra\7.3.1\Collaborator\demantra.
2. Once this is complete, deploy the WAR file.

For detailed instructions on deploying on Oracle Application Server 10g, please

see the section entitled 'Deploying the Oracle Demantra Web Application on Oracl
e Application Server 10.3' in the Oracle Demantra installation guide.
Important upgrade notes:
-------------------------------------1. If you want to use new Service Parts Forecasting (SPF) functionality, you MUS
T select the "Platform and Application Upgrade" option when running the Demantra
Installer. SPF functionality will not work on 7.3.1 after a PLATFORM-only upgra
de.
2. This release includes both a platform and application upgrade option. Please
note the application upgrade installer option is available only to customers who
have implemented the *standard* pre-configured applications (available from Dem
antra 7.1.1 onwards). You should choose the 'Platform Upgrade Only' option only
if your implementation is highly customized. A platform-only upgrade will preser
ve custom configurations and enable new platform functionality. It will not intr
oduce new application objects. Also note Demantra 7.2.1 customers should contact
support prior to running an application upgrade, to get latest patch details fo
r that release.
Please note the upgrade process may identify certain objects which have changed
between your existing Demantra version (Demantra 7.1.1 or 7.2.0.2, for example)
and the current release. This may be due to Oracle extensions in the latest rele
ase and/or due to customer extensions in their implementation. In a default upgr
ade mode, the current versions of these objects will be preserved during the upg
rade process and, where there are conflicting definitions with the new Oracle ve
rsion, we will create duplicate objects with a version suffix.
For example, if you extended the configuration of the workflow 'EBS Price List D
ownload', the upgrade process will maintain this and introduce the Oracle standa
rd workflow as 'EBS Price List Download_730'. In some cases, the original object
may be suffixed with its version (for example, 'EBS Full Download_711'and the l
atest configuration will be 'EBS Full Download'). You will identify the latest v
ersion by either a suffix of the latest version, or by a sibling item with an ea
rlier version stamp. You may then review the two and merge as appropriate. In th
e case of duplicate objects, it is recommended to use the latest version, prefer
ably after removing the ? _730? suffix and merging any of your customizations into th
e latest version.
For Predictive Trade Planning customers, you will note that Promotion Type is no
longer a level but instead a series, after application upgrade. This enables pr
omotions to have multiple tactics per promotion, typically for different items o
r locations being promoted. While promotion type can now vary across different i
tems, locations, it should not vary below the Lowest Promotional Level defined i
n the forecast tree.
If you are uncertain as to which upgrade option to choose, please contact suppor
t for guidance.

Known Issues:
==========================
Issue: When using the Mozilla Firefox browser, if a Demantra user closes the bro
wser using the X icon, it is possible to restore the session by re-launching a n
ew Firefox browser. In this scenario, the login page is not displayed and the us

er is not required to enter a username and password.

Workaround: Modify Mozilla Firefox configuration settings as follows:
1. Select Tools > Options > Startup > tab Main.
2. Verify that when Firefox starts, it is not set to Show my windows and tabs fr
om last time. Change this setting as required.
3. Navigate to tab Security and verify that Remember password for sites is not s
elected.
4. Save your changes.
Issue:
Oracle Demantra may create database tables in a single table space rather than t
he table spaces that you specified when you installed Oracle Demantra. This may
affect system performance.
Workaround:
The database administrator can manually create key tables and indexes with the d
esired table spaces after running the Oracle Demantra Installer.
Issue:
A Demantra user wants to review and/or simulate only General Level data, like CT
O Base Model demand, in a worksheet. If you include only General Levels in a wor
ksheet, it is not possible to view meaningful results for sales_data series such
as Adjusted History, Simulation, Consensus Forecast, and so on. The values all
show up as the total across the entire system population; this is not expected b
ehavior and can negatively affect system performance. It also doesn't provide su
fficient context for simulation.
Workaround:
If you want to review data in the context of only a General Level, such as CTO B
ase Model or Promotion, perform the following:
1. If the data to be reviewed is exclusively General Level data series, construc
t a worksheet using only General Levels (for example, CTO or promotion levels).
2. If the data to be reviewed includes a mix of General Level and sales data ser
ies, include an item level in the hierarchy. For example, if you wish to review,
adjust, and simulate independent demand for your base model, you must construct
a worksheet with the item level, Parent Item level and filter on Demand Type =
Base Model. If you wish to review, adjust and simulate promotions, you must cons
truct a worksheet with an item level, such as Promotion Group, in addition to pr
omotion levels.
Issue:
Failure Rate Calculation
As implemented in Demantra 7.3.1, the following series currently use straight av
erage, not weighted average:

*
*
*
*
*

SPF
SPF
SPF
SPF
SPF

Calculated Forecast
Failure Rate % Calculated
Failure Rate % Final
Failure Rate % Override
Final Forecast

The user can see a discrepancy between client propagation (based on straight ave
rage) and update hook calculation (performed at lowest level).
This issue can cause these series to give incorrect values at aggregate levels,
and cause client expressions to perform incorrect propagations. The back-end hoo
k will always calculate and store the correct values.
Workaround:
Use two sets of series. One set will be used for client expression failure rates
. These can use weighted averages. The other set will be used for SPF Batch and
hook calculations. These will not have weighting. Since batch and hook calculati
ons always run on lowest-level data, there is no need for any weighting.
The series that drive edit propagation can be changed. For back-end, worksheet h
ook and batch calculations, modify the spf_series_definition table. For front en
d, client-expression calculations, modify the tree_view_edit_propagation table.
Issue (bug 10198908):
When running the engine in PE mode, rows in the PROMOTION_DATA table that contai
n non-null records for another engine profile may be deleted.
Workaround:
To ensure that the non-null rows are not deleted when the engine runs with a dif
ferent engine profile, set the engine parameter DeleteIsSelfCondition to "0" for
that profile.
Issue:
Impossible to use Demantra with SSL mutual authentication (client authentication
) on latest Java 6 build. (6.23).
Workaround:
To use SSL mutual authentication (client authentication), use Java 6.19 and add
the Java security flag (in Java control panel, set sun.security.ssl.allowUnsafeR
enegotiation = True).
Bugs fixed in 7.3.1:
======================
Num
Subject
10148459
IN 7.3 VIEW FILTERS BRING ALL MEMBERS INTO WORKSHEET TREE
10167605
SYSTEM INVOKES PROPORT_J PROC UPON UPDATE ON ANY MDP_MATRIX SERI
ES
10058137
ERRORS IN CALL TO ENCRYPTION.GET_UAK WITH VERY LONG NAME AND PAS
SWD
10151779
APPPROC REBUILD CONTEXT CACHES PROCEDURE FAILS DURING APP SERVER

NOTIF
10187995
10128757
10111504
TRATION
10187986
A
10061249
BM
9856307
ING UP
9855063
9855064
CREATIO
10078360
T
10187978
.1
10105982
9880235
10058724
10033987
10105886
9864818
9794389
9860779
10049320
10187928
10187952
ES
9939635

RECEIVING WORKSHEET CANNOT BE SHOWN ERROR WHEN LOADING PROMOTION

DEMANTRA PATCH 9255161 FAILED - INSTALLER ISSUES
UNABLE TO ACCESS THE EDIT ADD DELETE BUTTONS IN DEMANTRA ADMINIS
WORKSHEET LAYOUT DEFINITIONS ARE LOST AFTER UPGRADE FROM DEMANTR
COLOR OF SERIES ON GRAPH IS NOT CONSISTENT WITH SERIES COLOR IN
DEMANTRA SERIES WITH VALUE X.5 IS ROUNDING DOWN INSTEAD OF ROUND
IMPORT AND EXPORT WORKFLOW NOT FUNCTIONING AS EXPECTED
ENABLE TO EDIT A WORKFLOW WITH CONDITION STEP AFTER SUCCESSFULL
CONFIGURATION INCONSISTENCIES ERROR WHEN SAVING DATA IN WORKSHEE
MEMBER CODE CHANGES AFTER UPGRADING FROM DEMANTRA 7.1.0 TO 7.3.0
SUMMARYWAVG FUNCTION DOES NOT WORK PROPERLY
DEMANTRA WORKSHEET RUNNING SLOW
DEMANTRA DATES DO NOT SAVE YEAR CORRECTLY IF ENTERED MANUALLY
WORKSHEETS NOT LOADING IN P
WORKSHEET PERFORMNACE
ACCESS TO RUN THE SIMULATION BUT NOT TO ACCEPT THE RESULT
UPDATE OF PROGRAM_GROUP OBJECTS FAILED
CYCLICAL PROPORT FEATURE
PROMOTIONAL OUTPUT DATA IS LIMMITED BY 10,000,000
CUSTOM METHODS THAT START WITH NEW DELETED DURING UPGRADE
CUSTOM METHODS SHOULD NOT AUTOMATICALLY BE ASSIGNED NEW ATTRIBUT
CAN'T ACCESS THE COLLABORATOR.LOG THROUGH THE URL IN V731