Oracle Demantra Release Notes for 7.3.1.4

Oracle Demantra Release Notes for Release 7.3.1.4 [ID 1463260.1]Modified: Jan 3, 2013 Type: BULLETIN Status: PUBLISHED Priority: 3

Applies to:

Oracle Demantra Demand Management - Version 7.3.1 to 7.3.1 [Release 7.3.0]Information in this document applies to any platform.

Purpose

This document provides release information for Oracle Demantra Release 7.3.1. This document has been updated to provideadditional information for release 7.3.1.4.

Scope

The information included in this document assumes that you have already installed Oracle Demantra 7.3.1 according to theinstructions in the following document:

Oracle Demantra Installation Guide for Release 7.3.1.4 Document 1490558.1

Note: This document - especially Section 5, Known Issues - may be updated after initial release. Any changes are listed inSection 6, Change Record. If you print this document, periodically check to ensure you have the most recent version.

The latest version of this document is available on My Oracle Support, Document 443969.1, Oracle Demantra DocumentationLibrary.

Details

In this Document

What's New1.

Documentation2.

New and Changed Features3.

Diagnostics and Logging4.

Known Issues in Oracle Demantra Release 7.3.1.45.

Change Record6.

Documentation Accessibility7.

1. What's New

In Release 7.3.1, Oracle Demantra has added or changed the following features since its last release.

Feature Name Description

Service Parts Forecasting (SPF) In release 7.3.1, Demantra provides integration with Oracle Service PartPlanning (SPP) to generate a demand forecast and forecast accuracymetrics for service parts (also referred to as spare parts). The forecast canbe based on usage history or shipment history. In cases where there isinsufficient history for a reliable basis, Demantra bases the forecast on theitem's install base population and average failure rate.

The following changes support Service Parts Forecasting (SPF):

New workflows and integration interfaces to import service partsusage, shipment history, and install base under contract data intoDemantra.

Calculate failure rates and generate an analytical forecast for serviceparts. The average failure rate per week is calculated based oninstall base under contract data as well as historical service partsconsumption.

New SPF worksheets and related series to view the calculated

Document https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_a...

1 of 58 1/21/2013 8:06 PM


forecast, statistical forecast, and forecast metrics, and to runsimulations.

New method to incrementally export changes made in Demantraworksheets to Service Parts Planning.

Forecast demand for the latest item in a service parts supersessionchain by merging together the history of all items in the chain.

Define multiple forecasting engine configurations so that a singleDemand Management installation can be leveraged for multiplelines of business that forecast in different ways. For example, SupplyChain can use CTO forecasting while Service Parts Planning canconsider different data streams and analytical configurations whengenerating a forecast.

Include General Levels in the forecast tree (in addition to Item andLocation levels).

New engine profiles:

Forecast Install Base

Forecast Spares Demand

Simulation Install Base

Simulation Spares Demand

New workflows and integration interfaces to export the service partsdemand forecast, forecast accuracy metrics, and other data toOracle Service Parts Planning.

IMPORTANT: If you will be leveraging Service Parts Forecasting (SPF)functionality, refer to the Oracle Demantra Installation Guide, MyOracle Support Document 1226023.1 for important pre- andpost-installation tasks.

Database Performance Improvements Database performance can decline due to out-of-order tables or incorrectlydefined primary keys. In this release, standard mechanisms for performingdatabase "health checks" (both a quick and thorough version) andprocedures to rebuild key data tables, like SALES_DATA and MDP_MATRIX,are available. This procedure will be dynamically created in Demantra andcan be run either while the application server is live or when theapplication server is not running.

For details, refer to the Oracle Demantra Implementation GuideSupplement.

Forecasting for Multiple BusinessProcesses

In this release, all analytical engine settings can be configured for eachengine profile. These changes support various business processes, increaseconfiguration flexibility, and support forecasting for service parts (SPF) andmanufacturing options. When configuring the forecast tree and causalfactors, users can now choose which engine profile to which the settingsapply.

For details, refer to "Configuring the Forecast Tree" and "Configuring CausalFactors" in the Oracle Demantra Implementation Guide.

Proport Enhancements The Proport mechanism typically processes a large amount of data and canrequire substantial amount of time and resources. In this release, severalnew system parameters can improve Proport runtime performance byenabling parallel processing and by grouping the Proport process intoseveral iterations.

For details, see the "Fine Tuning and Scaling Demantra" chapter in theOracle Demantra Implementation Guide.


2 of 58 1/21/2013 8:06 PM


Parallel Hints on Worksheets Some worksheets access a large amount of data which can cause themrender slowly. A parallel hint can be implemented to improve theperformance for specific worksheets and users. A hint specifies the numberof threads used by the worksheet query and can be applied to two parts ofthe worksheet: generation of the combinations and retrieval of data to bedisplayed.

Note: Setting a hint requires manually adding a row to theWORKSHEET_HINTS table using SQL Developer or similar tool.Therefore; this task should be performed only by an experiencedsystem or database administrator.

For details, see the "Fine Tuning and Scaling Demantra" chapter in theOracle Demantra Implementation Guide.

Rolling Data Profile Groups In this release, Demantra users can create groups of rolling data profilesand assigned each an ID. All profiles within the group can then beexecuted by calling the profile group ID from a workflow.

For details, refer to the "Configuring Rolling Data" chapter in the OracleDemantra Implementation Guide.

Subset Forecasting Subset forecasting allows customers who have large data sets whichcannot be completed in a single processing cycle to generate a batchforecast for a filtered subset of combinations. This run will not advanceforecast versioning and will simply override the latest forecast for thespecified subset. This process is similar to executing and accepting asimulation but without the need to open a worksheet and with the benefitof processing parallelization. Subset forecasting does not entirely replacefull batch runs, as they are required to drive forecast versioning.

Engine Performance Improvements This release sets engine pass through as the default configuration for theanalytical engine. With this configuration, the Sales_Data_Engine will notbe created for every engine branch, but instead, the data will be retrieveddirectly from the Sales_Data table as needed.

This enhancement reduces configuration time needed to apply thisconfiguration, improves implementation delivery times, and maintains orimproves engine run times.

Data Preservation Setting for GeneralLevels

A new "Data Preservation" setting was added to the Population Attributessection of the Configure Levels screen in Business Modeler. This parameteris available only if the Population Type setting for the selected GL level is"Searchable" and the selected level has a Data table.

This setting controls whether the selected General Level (GL) member'sdates are preserved when either the member's "from" and "until" dateschange, or the member's population changes. It also controls whether theseries-level settings "Copy/Paste Preservation Type" and "MovePreservation Type" are respected when a member's dates or populationchanges.

Examples:

Member's date range shifts:Old date range = 10 weeks in 2011.New date range = 10 weeks in 2012.

Member's date duration changes:Old duration = Brand A, 10 weeks in 2011.New duration = Brand A, 15 weeks in 2011

Member's population changes:Old population = Brand A, 10 weeks in 2011.New population = Brand B, 10 weeks in 2011.

A member's date or population may change when:

Reloading a member via an integration interface


3 of 58 1/21/2013 8:06 PM


Editing a member in a Worksheet

Copy/pasting a member

Running the "Refresh Population" method

Values for the Data Preservation setting include:

Disable: The GL member's data will not be shifted and the"preservation type" settings will be ignored (equivalent tosetting Preservation Type to "Do Nothing").

This is the default setting for all General Levels except "Promotion".

Enable for Manual Edit Only: Preservation Type settingsare respected when the member's "from" and "until" date orpopulation is changed by a manual edit in the worksheet, byCopy/Paste, or by Refresh Population.

Enable for Manual Edit and Integration: PreservationType settings are respected when the member's "from" and"until" date or population is changed either by a manual editin the worksheet, by Copy/Paste, by Refresh Population, or bydata integration.

This is the default setting for the Promotion level.

For more information about configuring General Levels, see "Adding aPopulation Attribute to a General Level" in the Oracle DemantraImplementation Guide.

Demantra Web Service NamespaceChange

In the Demantra 7.3.1.2 release, a property in the Demantra Web serviceWSDL file has changed (this file exposes the Web service to clients). Thenamespace attribute was modified as were several other attributes derivedfrom it.

Previously the syntax used was:

http://workflow.webServices.common.demantra.com/

This has changed to:

http://com.demantra.common.webServices.workflow/

Therefore, if you used Web services in a prior Demantra release and areupgrading to 7.3.1.2 or above, you must change the client code thataccesses the Demantra Web service according to the new modified WSDLfile.

The following files must be modified:

MSC_WS_DEMANTRA_WORKFLOW.wsdl

MSC_WS_DEMANTRA_WORKFLOW.wsdl.WLS

Note that in release 7.3.1.2 Demantra supports only the WebLogicapplication server, so the only affected file isMSC_WS_DEMANTRA_WORKFLOW.wsdl.

For more information about Web services, see the Oracle DemantraImplementation Guide.

Launch URL from Worksheet In this release, Demantra provides the ability to embed a URL in a seriesand display it as a link in any Demantra worksheet. The URL can then beused to launch a webpage or external document.


Enhancements to PTP Engine Improvements have been made to the Analytical Engine's ability to reviewand analyze indirect cannibalization and halo effects caused by promotions.Enhancement filters information viewed by the engine and reduceschanges of overfitting.


4 of 58 1/21/2013 8:06 PM


For details, refer to "Influence Group Handling and Filtering" in the OracleDemantra Implementation Guide Supplement.

Integration with Asset IntensivePlanning

In this release, Demantra provides integration with Oracle ComplexMaintenance Repair and Overhaul (cMRO) as well as Enterprise AssetManagement (eAM). These integrations enable an organization to plan forcomplex maintenance activities and spare parts usage. Suchimplementations must be able to project material and resource usage andmanage the entire maintenance lifecycle for complex assets, such asaircraft engines and component assemblies.

Note: If you will be integrating Demantra with one of the supportedasset intensive planning applications, please review the recommendedimplementation steps that are provided in the patch Readme file.


Demantra Trade PromotionOptimization - Enhancements toOptimization

This release provides the following enhancements to the Trade PromotionOptimization (TPO) module:

Exclusion rules: Users will be able to define a set of conditions thatshould not occur together in a solution. For example, you should notrun a TPR simultaneously with an Ad, and discount should excludediscounts in a certain range.

Optimized buydown: Buydown is now optimized like other variablesin the optimizer. In previous releases, the buydown calculation wasdeterministic and calculated using the minimum retailer marginconstraint. In this version, buydown is now part of the optimizationproblem and the value is selected by the optimization process.

Vehicle cost overrides: The vehicle_cost expression has beenchanged to allow cost event overrides per causal and per transpose.

Control over impact of financial constraints: Provide the ability toturn off financial constraints such as minimum manufacturer or retailmargins.

Define baseline: If a manual override was done to the baselineforecast, customers might require that value be used as the baselinefor the promotion when calculating Revenue and Profit. In thisrelease, we provide control over the expression denoting baseline.

Embedded Demantra Worksheets inVCP Applications

In release 7.3.1.4, using Demantra Anywhere, Value Chain Planning (VCP)applications allow users to access Demantra applications and worksheetsfrom the VCP application. A separate log in is not required, and the userdoes not need to open a second browser instance.

This enhancement also provides additional support for the following mobiletechnology applications:

Apple iPad

For details, refer to "Embeddable Worksheets" in the Oracle DemantraImplementation Guide Supplement.

Demantra Predictive Trade Planning(PTP) Promotion Calendar

Promotion calendars graphically display promotions in an interactivecalendar. In a promotion calendar, levels, table and calendar are combinedinto a single graphical representation. The left side displays aggregativelevels and summary information. The right side displays promotions acrosstime as part of a promotional calendar.

Each promotion appears as a separate box in the calendar, and each maydisplay several series and their values (for example, Vehicle Type, Startand End Event dates, Event Spend).

The ability to define a Promotion Calendar is available in release 7.3.1.4.


5 of 58 1/21/2013 8:06 PM



Aggregate Work Orders As part of Asset Intensive Planning (AIP) projected use of material andresources coming from eAM and cMRO is loaded into Demantra striped bykey work order attributes.

Processing a large volume of work orders individually in ASCP for the entireprojection horizon may adversely affect performance.

In EBS release 12.1.3.8, work orders may be aggregated when loaded intoASCP. This aggregation level is higher than the aggregation used inDemantra. Demantra release 7.3.1.4 supports this aggregation. Detailedwork order information is loaded from ASCP to Demantra (as in previousreleases) while aggregate information is imported directly from ODS.


Demantra User Interface (UI)Enhancements

In release 7.3.1.4, the Demantra user interface has been enhanced toprovide a better user experience and enhanced security. The applicationinterface "look and feel" has been updated to match other Oracleapplications. The application has also been streamlined to reduce thenumber of steps or clicks to perform tasks.

User Interface Enhancements

In this release, Demantra provides the following user interfaceenhancements:

Enhanced visuals including gradients and 3D graphs.

Ability to access level methods from toolbar

Configurable colors and fonts

Hide frame - Each worksheet tab has a frame around it. This frameallows you to minimize, maximize, and re-size the worksheet tab. Tohide these frames, click Hide Frames in the Options menu.

Drag and drop levels and series in a table - Levels and series withina worksheet can be moved using drag and drop.

Graph display enhancements - New graph display styles areavailable by right-clicking a graph and selecting an option. Graphscan now display as 3-D and the angle of the 3-D appearance can bealtered by clicking and holding mouse over the graph. Moving thepointer over the graph changes the angle of the 3-D graph highlight.

New toolbar icons - More consistent appearance and improvedusability.

Display Methods in the Toolbar - New setting allows methods to bedisplayed as an icon on the toolbar.

For information about the toolbar and interface changes, refer to theDemantra Predictive Trade Planning User's Guide.

Return to What's New

Top

2. Documentation

This section provides information on the following topics:

2.1 Online Help and PDF Documentation

2.2 Technical Documentation

2.3 White Papers


6 of 58 1/21/2013 8:06 PM

Top

2.1 Online Help and PDF Documentation

The Oracle Demantra Online help is installed when you upgrade or install release 7.3.1. In addition to English, all Demantra userguide content is available in the following languages:

Chinese Simplified

Chinese Traditional

French (Canada)

Japanese

Korean

Portuguese (Latin America)

Russian

Spanish (Latin America)

In addition, the following Oracle Demantra documentation in U.S. English is available as part of the Installer process:

Oracle Demantra Installation Guide for Release 7.3.1.4,My Oracle Support, Document 1490558.1

Oracle Demantra System Requirements Guide for Release 7.3.1.4,My Oracle Support, Document 1490559.1

Oracle Demantra Implementation Guide,Part No. E05136-11, November 2010HTML | PDF

Oracle Demantra Implementation Guide Supplement,Part No. E26760-04, September 2012

Oracle Demantra User's Guide,Part No. E05072-06, November 2010HTML | PDF

Oracle Demantra Demand Management User's Guide Supplement,Part No. E26759-02, May 2012

Oracle Demantra Demand Management User Guide,Part No. E05179-08, November 2010HTML | PDF

Oracle Demantra Sales and Operations Planning User Guide,Part No. E10533-06, November 2010HTML | PDF

Oracle Demantra Predictive Trade Planning User's Guide,Part No. E05137-07, September 2012HTML | PDF

Oracle Demantra Deductions and Settlement Management User's Guide,Part No. E05138-04, November 2010HTML | PDF

Online documentation and Adobe Acrobat PDFs are cumulative; they include updated documentation for all Oracle Demantra 7.3.1changes.

Return to Documentation

Top

2.2 Technical Documentation

Technical reference material is planned for the release 7.3.1 time frame. Please check the Oracle Demantra Documentation Library,Document 443969.1, frequently for updates.



7 of 58 1/21/2013 8:06 PM

Top

2.3 White Papers

Please refer to the Demantra Documentation Library, Document 443969.1, on My Oracle Support or contact Oracle Support Services.


Top

3. New and Changed Features

In Release 7.3.1, the Oracle Demantra products have added or changed the following features since the last release.

Use this section to access the following information for each feature:

New, Changed, Obsolete Components

Implementation Considerations

Customizations and Extensions

Minimum Level Requirements

Technology Stack Incompatibilities

Technology Architecture Considerations

Troubleshooting Tips

This document contains information on the following new product features:

3.1 Service Parts Forecasting (SPF)

3.2 Forecasting for Multiple Business Processes

3.3 Proport Enhancements

3.4 Parallel Hints on Worksheets

3.5 Rolling Data Profile Groups

3.6 Subset Forecasting

3.7 Integration with Asset Intensive Planning

3.8 Enhancements to the PTP Engine

3.9 Launch URL from Worksheet

3.10 Database Performance Enhancements

3.11 Demantra Trade Promotion Optimization - Enhancements to Optimization

3.12 Embedded Demantra Worksheets in VCP Applications

3.13 Demantra Predictive Trade Planning (PTP) Promotion Calendar

3.14 Aggregate Work Orders

3.15 Demantra Predictive Trade Planning (PTP) Enhancements

Top

3.1 Service Parts Forecasting (SPF)

Description In release 7.3.1, Demantra provides integration with Oracle Service Part Planning (SPP) togenerate a demand forecast and forecast accuracy metrics for service parts (also referred to asspare parts). The forecast can be based on usage history or shipment history. In cases wherethere is insufficient history for a reliable basis, Demantra bases the forecast on the item's installbase population and average failure rate.

The following changes support Service Parts Forecasting (SPF):


8 of 58 1/21/2013 8:06 PM

New workflows and integration interfaces to import service parts usage, shipmenthistory, and install base under contract data into Demantra.

Calculate failure rates and generate an analytical forecast for service parts. The averagefailure rate per week is calculated based on install base under contract data as well ashistorical service parts consumption.

New SPF worksheets and related series to view the calculated forecast, statisticalforecast, and forecast metrics, and to run simulations.

New method to incrementally export changes made in Demantra worksheets to ServiceParts Planning.

Forecast demand for the latest item in a service parts supersession chain by mergingtogether the history of all items in the chain.

Define multiple forecasting engine configurations so that a single Demand Managementinstallation can be leveraged for multiple lines of business that forecast in different ways.For example, Supply Chain can use CTO forecasting while Service Parts Planning canconsider different data streams and analytical configurations when generating a forecast.

Include General Levels in the forecast tree (in addition to Item and Location levels).

New engine profiles:

Forecast Install Base

Forecast Spares Demand

Simulation Install Base

Simulation Spares Demand

New workflows and integration interfaces to export the service parts demand forecast,forecast accuracy metrics, and other data to Oracle Service Parts Planning.

IMPORTANT: If you will be leveraging Service Parts Forecasting (SPF) functionality, referto the Oracle Demantra Installation Guide, My Oracle Support Document 1226023.1 forimportant pre- and post-installation tasks.

New, Changed,ObsoleteComponents

This section lists the components that were added, changed, or made obsolete for this featurein Oracle Demantra in Release 7.3.1. These components may include the following: worksheets,series, levels, methods, workflows, system parameters, reports, alerts, APIs, programs, tables,views, profile options, and integration interfaces.

Technical reference material is planned for the release 7.3.1 time frame. Please check theOracle Demantra Documentation Library Document 443969.1 frequently for updates.

New Worksheets

The following new worksheets are associated with this feature:

SPF: Analyze Forecast Organization Latest Revision

SPF: Analyze Forecast Latest Revision

SPF: Analyze Organization Base Model Spare

Changed Worksheets

There are no changed worksheets that are associated with this feature.

Obsolete Worksheets

There are no obsolete worksheets that are associated with this feature.

New Series


9 of 58 1/21/2013 8:06 PM

The following new series are associated with this feature:

SPF Item Shipments

SPF Item Shipment Override

SPF Item Shipment Final

SPF Item Usage

SPF Item Usage Override

SPF Item Usage Final

SPF Consensus Forecast

SPF Engineering Estimated Failure Rate %

SPF Engineering Estimated Failure Rate % MAPE

SPF Failure Rate % Calculated

SPF Calculated Failure Rate % MAPE

SPF Failure Rate % Generation Method

SPF Failure Rate % Override

SPF Failure Rate % Final

SPF Forecast MAPE (In Sample)

SPF Final Forecast MAPE (Out of Sample)

SPF Analytics Forecast MAPE

SPF Analytical Forecast BIAS %

SPF Calculated Forecast MAPE

SPF Calculated Forecast BIAS %

SPF Analytical Forecast

SPF Simulation Analytical

SPF Calculated Forecast

SPF Analytical Forecast Archive1



SPF Calculated Forecast Archive1



SPF Forecast Method

SPF Forecast Override

SPF Final Forecast

SPF Final Forecast Archive1



SPF Analytical Forecast MAPE 1 Month lag

SPF Final Forecast MAPE 1 Month lag

SPF Calculated Forecast MAPE 1 Month lag


10 of 58 1/21/2013 8:06 PM

SPF Analytical Forecast Bias % 1 Month lag

SPF Final Forecast Bias % 1 Month lag

SPF Calculated Forecast Bias % 1 Month lag

SPF Forecast Volatility

SPF Average Demand

SPF Install Base Under Contract

SPF Install Base Override

SPF Install Base Forecast

SPF Install Base Simulation

SPF Install Base Final

SPF Analytical Models

SPF Item Price

Changed Series

There are no changed series that are associated with this feature.

Obsolete Series

There are no obsolete series that are associated with this feature.

New Levels

The following SFP Location and General levels are new.

SPF Location Levels:

Organization Type

Organization Tier

Country Virtual

Region Virtual

Time Zone Virtual

Global Virtual

SPF General Levels:

SPF

SPF Base Model

SPF Child

SPF Demand Type

SPF Latest Revision

SPF Parent

SPF Parent Item

Changed Levels

There are no changed levels that are associated with this feature.

Obsolete Levels


11 of 58 1/21/2013 8:06 PM

There are no obsolete levels that are associated with this feature.

New Methods

The following new methods are associated with this feature:

Publish SPF Changes

Changed Methods

There are no changed methods that are associated with this feature.

Obsolete Methods

There are no obsolete methods that are associated with this feature.

New Workflows

The following new workflows are associated with this feature:

SPF Upload Data

SPF Incremental Upload

Calculate Spares Forecast

Calculate Spares Forecast for LOB

Export Consensus Forecast for SPF

Import SPF Base Model

Import SPF Child

Import SPF Data

Import SPF Latest Revision

Import SPF Level

Run Forecast Install Base

Run Forecast Spares Demand

SPF Calc Forecast Accuracy

SPF Full Download

SPF Generate Forecast

SPF GL Data Download

SPF Archive Forecast

Changed Workflows

There are no changed workflows that are associated with this feature.

Obsolete Workflows

There are no obsolete workflows that are associated with this feature.

New System Parameters

The following new system parameters are associated with this feature:


12 of 58 1/21/2013 8:06 PM

GLPropSupersessionMethod

EngKeyDef_Supersession

Changed System Parameters

There are no changed system parameters that are associated with this feature.

Obsolete System Parameters

There are no obsolete system parameters that are associated with this feature.

New Windows or Pages

There are no new windows or pages that are associated with this feature.

Changed Windows or Pages

There are no changed windows or pages that are associated with this feature.

Obsolete Windows or Pages

There are no obsolete windows or pages that are associated with this feature.

New Reports

There are no new reports that are associated with this feature.

Changed Reports

There are no changed reports that are associated with this feature.

Obsolete Reports

There are no obsolete reports that are associated with this feature.

New Alerts

There are no new alerts that are associated with this feature.

Changed Alerts

There are no changed alerts that are associated with this feature.

Obsolete Alerts

There are no obsolete alerts that are associated with this feature.

New Public APIs

There are no new public APIs that are associated with this feature.

Changed Public APIs

There are no changed public APIs that are associated with this feature.


13 of 58 1/21/2013 8:06 PM

Obsolete Public APIs

There are no obsolete public APIs that are associated with this feature.

New Programs

There are no new programs that are associated with this feature.

Changed Programs

There are no changed programs that are associated with this feature.

Obsolete Programs

There are no obsolete programs that are associated with this feature.

New Tables

The following new tables are associated with this feature:

init_params_121

init_params_122

init_params_141

init_params_142

BIIO_SPF_BASE_MODEL

BIIO_SPF_BASE_MODEL_ERR

BIIO_SPF_CHILD

BIIO_SPF_CHILD_ERR

BIIO_SPF_DATA

BIIO_SPF_DATA_ERR

BIIO_SPF_LATEST_REVISION

BIIO_SPF_LATEST_REVISION_ERR

BIIO_SPF_LEVEL

BIIO_SPF_LEVEL_ERR

BIIO_SPF_POPULATION

BIIO_SPF_POPULATION_ERR

BIIO_SPF_SALES_FCST_DATA

BIIO_SPF_SALES_FCST_DATA_ERR

BIIO_SPF_SPARES_HIST_DATA

BIIO_SPF_SPARES_HIST_DATA_ERR

Changed Tables

There are no changed tables that are associated with this feature.

Obsolete Tables


14 of 58 1/21/2013 8:06 PM

There are no obsolete tables that are associated with this feature.

New Views

There are no new views that are associated with this feature.

Changed Views

There are no changed views that are associated with this feature.

Obsolete Views

There are no obsolete views that are associated with this feature.

New Profile Options

There are no new profile options that are associated with this feature.

Changed Profile Options

There are no changed profile options that are associated with this feature.

Obsolete Profile Options

There are no obsolete profile options that are associated with this feature.

New Integration Interfaces

The following new integration interfaces are associated with this feature:

SPF

Data/level profiles for SPF integration interface:

IMPORT_SPF_DATA

IMPORT_SPF_SALES_FORECAST_DATA

IMPORT_SPF_SHIPMENT_HISTORY

IMPORT_SPF_BASE_MODEL

IMPORT_SPF_CHILD

IMPORT_SPF_LATEST_REVISION

IMPORT_SPF_LEVEL

SPF Upload Forecast Data & Metrics

Data/level profiles for SPF Upload Forecast Data & Metrics integration interface:

SPF Upload Final Forecast

SPF Upload Metrics

Changed Integration Interfaces

There are no changed integration interfaces that are associated with this feature.

Obsolete Integration Interfaces

There are no obsolete integration interfaces that are associated with this feature.


15 of 58 1/21/2013 8:06 PM

Return to New and Changed Features

Top

3.2 Forecasting for Multiple Business Processes

Description In this release, all analytical engine settings can be configured for each engine profile. Thesechanges support various business processes, increase configuration flexibility, and supportforecasting for service parts (SPF) and manufacturing options. When configuring the forecasttree 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 DemantraImplementation Guide.




New Worksheets

There are no new worksheets that are associated with this feature.

Changed Worksheets


Obsolete Worksheets


New Series

There are no new series that are associated with this feature.

Changed Series


Obsolete Series


New Levels

There are no new levels that are associated with this feature.

Changed Levels


Obsolete Levels


New Methods


16 of 58 1/21/2013 8:06 PM

There are no new methods that are associated with this feature.

Changed Methods


Obsolete Methods


New Workflows

There are no new workflows that are associated with this feature.

Changed Workflows


Obsolete Workflows




EngTabDef_Parameters

EngTabDef_HistoryForecast

EngTabDef_Matrix

EngDimDef_ItemOrLoc

EngKeyDefPK

EngTabDef_Inputs












17 of 58 1/21/2013 8:06 PM

New Reports


Changed Reports


Obsolete Reports


New Alerts


Changed Alerts


Obsolete Alerts


New Public APIs


Changed Public APIs




New Programs


Changed Programs


Obsolete Programs


New Tables

There are no new tables that are associated with this feature.

Changed Tables


18 of 58 1/21/2013 8:06 PM

The following changed tables are associated with this feature:

CAUSAL_FACTORS

ENGINE_CACHES

FORECAST_TREE

FORECAST_TREE_STRATEGY

ITEMS_LEVELS

LOC_LEVELS

M3_CAUSAL_FACTORS

MODEL

MODEL_MATRIX

PARAM_MATRIX

PROPORT_JOB_LIST

PROPORT_LEVELS

Obsolete Tables


New Views


Changed Views


Obsolete Views


New Profile Options







There are no new integration interfaces that are associated with this feature.




19 of 58 1/21/2013 8:06 PM



ImplementationConsiderations

New and Changed Setup Steps

This section lists the setup steps that were added or changed for Oracle Demantra in Release7.3.1. For additional details about performing the setup steps listed below, refer to thedocumentation described in the 2.1 Online Help and PDF Documentation.

To enable this feature, the New Parameters listed in the previous section must be defined.

Upgrade Considerations

There are no upgrade considerations for this feature.

Sizing

Table Space Considerations

There are no table space considerations for this feature.

Performance Considerations

XMLDB Usage

There are no XMLDB usages for this feature.

Load Balancing

There is no load balancing information for this feature.

New Bulk Interfaces

There are no new bulk interfaces for this feature.

Customizationsand Extensions

Customizations and extensions are not possible for this feature.

Minimum LevelRequirements

There are no minimum level requirements for this feature.

TechnologyStackIncompatibilities

There are no technology stack incompatibilities for this feature.

TechnicalArchitectureConsiderations

There are no technology architecture considerations for this feature.

TroubleshootingTips

There are no troubleshooting tips for this feature.


Top

3.3 Proport Enhancements


20 of 58 1/21/2013 8:06 PM

Description The Proport mechanism typically processes a large amount of data and can require substantialamount of time and resources. In this release, several new system parameters can improveProport runtime performance by enabling parallel processing and by grouping the Proportprocess into several iterations.

For details, see the "Fine Tuning and Scaling Demantra" chapter in the Oracle DemantraImplementation Guide.




New Worksheets


Changed Worksheets


Obsolete Worksheets


New Series


Changed Series


Obsolete Series


New Levels


Changed Levels


Obsolete Levels


New Methods


Changed Methods



21 of 58 1/21/2013 8:06 PM

Obsolete Methods


New Workflows


Changed Workflows


Obsolete Workflows




ProportParallelJobs

ProportRunsInCycle

ProportTableLabel












New Reports


Changed Reports



22 of 58 1/21/2013 8:06 PM

Obsolete Reports


New Alerts


Changed Alerts


Obsolete Alerts


New Public APIs


Changed Public APIs




New Programs


Changed Programs


Obsolete Programs


New Tables

There are no new tables that are associated with this feature.

Changed Tables


Obsolete Tables


New Views


23 of 58 1/21/2013 8:06 PM


Changed Views


Obsolete Views


New Profile Options















To enable this feature, the new system parameters listed above must be defined.



Sizing





24 of 58 1/21/2013 8:06 PM

XMLDB Usage


Load Balancing


New Bulk Interfaces










TroubleshootingTips



Top

3.4 Parallel Hints on Worksheets

Description Some worksheets access a large amount of data which can cause them render slowly. A parallelhint can be implemented to improve the performance for specific worksheets and users. A hintspecifies the number of threads used by the worksheet query and can be applied to two parts ofthe worksheet: generation of the combinations and retrieval of data to be displayed.

Note: Setting a hint requires manually adding a row to the WORKSHEET_HINTS table usingSQL Developer or similar tool. Therefore, this task should be performed only by anexperienced system or database administrator.





New Worksheets


Changed Worksheets



25 of 58 1/21/2013 8:06 PM

Obsolete Worksheets


New Series


Changed Series


Obsolete Series


New Levels


Changed Levels


Obsolete Levels


New Methods


Changed Methods


Obsolete Methods


New Workflows


Changed Workflows


Obsolete Workflows




26 of 58 1/21/2013 8:06 PM

There are no new system parameters that are associated with this feature.











New Reports


Changed Reports


Obsolete Reports


New Alerts


Changed Alerts


Obsolete Alerts


New Public APIs


Changed Public APIs




27 of 58 1/21/2013 8:06 PM


New Programs


Changed Programs


Obsolete Programs


New Tables


WORKSHEET_HINTS

Changed Tables


Obsolete Tables


New Views


Changed Views


Obsolete Views


New Profile Options









28 of 58 1/21/2013 8:06 PM








Some manual setup is required to implement worksheet hints. For details, refer to the "FineTuning and Scaling Demantra" chapter in the Oracle Demantra Implementation Guide.



Sizing




XMLDB Usage


Load Balancing


New Bulk Interfaces










TroubleshootingTips




29 of 58 1/21/2013 8:06 PM

Top

3.5 Rolling Data Profile Groups

Description In this release, Demantra users can create groups of rolling data profiles and assigned each anID. All profiles within the group can then be executed by calling the profile group ID from aworkflow.

For details, refer to the "Configuring Rolling Data" chapter in the Oracle DemantraImplementation Guide.




New Worksheets


Changed Worksheets


Obsolete Worksheets


New Series


Changed Series


Obsolete Series


New Levels


Changed Levels


Obsolete Levels


New Methods



30 of 58 1/21/2013 8:06 PM

Changed Methods


Obsolete Methods


New Workflows


Changed Workflows


Obsolete Workflows



There are no new system parameters that are associated with this feature.











New Reports


Changed Reports


Obsolete Reports


31 of 58 1/21/2013 8:06 PM


New Alerts


Changed Alerts


Obsolete Alerts


New Public APIs


Changed Public APIs




New Programs


Changed Programs


Obsolete Programs


New Tables


ROLLING_GROUP_PROFILES

ROLLING_GROUPS

Changed Tables


Obsolete Tables


New Views


32 of 58 1/21/2013 8:06 PM


Changed Views


Obsolete Views


New Profile Options














This section lists the setup steps that were added or changed for Oracle Demantra in Release7.3.1. For additional details about performing the setup steps listed below, refer to thedocumentation described in the 2.1 Online Help and PDF Documentation..

Some manual setup is required to implement rolling profile groups. For details, refer to the"Configuring Rolling Data" chapter in the Oracle Demantra Implementation Guide.



Sizing





33 of 58 1/21/2013 8:06 PM

XMLDB Usage


Load Balancing


New Bulk Interfaces










TroubleshootingTips



Top

3.6 Subset Forecasting

Description Subset forecasting allows customers who have large data sets which cannot be completed in asingle processing cycle to generate a batch forecast for a filtered subset of combinations. Thisrun will not advance forecast versioning and will simply override the latest forecast for thespecified subset. This process is similar to executing and accepting a simulation but without theneed to open a worksheet and with the benefit of processing parallelization. Subset forecastingdoes not entirely replace full batch runs, as they are required to drive forecast versioning.


This section lists the components that were added, changed, or made obsolete for this featurein Oracle Demantra in this release. These components may include the following: worksheets,series, levels, methods, workflows, system parameters, reports, messages, APIs, programs,tables, views, profile options, and integration interfaces.


For details, refer to Oracle Demantra Demand Management User's Guide Supplement andOracle Demantra Implementation Guide Supplement.


This table lists the changed windows and pages.

Changed Window orPage Name

TechnicalName

Description

Modify Engine Profiles page - New Subset Forecasting option availableon page.




34 of 58 1/21/2013 8:06 PM

There are no new or changed setup steps for this feature.



Sizing

Tablespace Considerations

There are no tablespace considerations for this feature.


XMLDB Usage


Load Balancing


New Bulk Interfaces










TroubleshootingTips There are no troubleshooting tips for this feature.


Top

3.7 Integration with Asset Intensive Planning

Description In this release, Demantra provides integration with Oracle Complex Maintenance, Repair, andOverhaul (cMRO) as well as Enterprise Asset Management (eAM). These integrations enable anorganization to plan for complex maintenance activities and spare parts usage. Suchimplementations must be able to project material and resource usage and manage the entiremaintenance lifecycle for complex assets, such as aircraft engines and component assemblies.

For details, refer to the Oracle Demantra Implementation Guide Supplement.


This section lists the components that were added, changed, or made obsolete for this featurein Oracle Demantra in this release. These components may include the following: worksheets,series, levels, methods, workflows, system parameters, reports, alerts, APIs, programs, tables,views, profile options, and integration interfaces.

New Series


35 of 58 1/21/2013 8:06 PM

Available Resource Plan

Beginning On Hand Defectives

Constrained Forecast Archived

Demand Variability

Fleet Flight Hours

Fleet Size

Fleet Times Used

Intransit Defectives

Personnel in Organization

Plan Purchase Cost Per Unit

Plan Repair Cost Per Unit

Plan Resource Cost Per Hour

Production Cost Per Unit

Purchase Cost Per Unit

Repair Cost Per Unit

Repair Plan

Required Capacity Archived

Required Resource Plan

Resource Cost Per Hour

SPF Fleet Size

SPF Fleet Times Used

SPF Fleet Usage Hours

SPF Item Usage Final

SPF Total Independent Demand

SPF Weighted Failure Rates

SPF Work Order History

Total Demand

Work Order Demand

Work Order Demand Approved

Work Order Demand Archive

Work Order Demand MAPE

New Series Group

SPF-cMRO

New Profile Options

MSD_DEM: Include organization in CMRO Data Load

MSD_DEM: Simulation Set Name

MSD_DEM: Enable Supply Plan Download for work orders


36 of 58 1/21/2013 8:06 PM

New Tables

BIIO_SPF_VISIT_TYPEBIIO_SPF_VISIT_STAGE_TYPEBIIO_SPF_MAINTENANCE_TYPEBIIO_SPF_CMRO_DATAT_SRC_SALES_TMPLBIIO_SPF_CMRO_DATAT_SRC_SALES_TMPLBIIO_SPF_CMRO_DATABIIO_SPF_CMRO_FLEET_DATABIIO_SPF_CMRO_FLEET_DATABIIO_SPF_CMRO_FLEET_DATABIEO_SPF_PLNFCTBIEO_SPF_NUWO_FCSTBIEO_NM_FCST_VBIEO_TOTAL_DEMAND_VBIEO_WORK_ORDER_DEMAND_ORG

New Workflows

SPF - cMRO - Import cMRO Data

SPF - cMRO - Import cMRO Fleet Data

SPF - cMRO Export Failure Rates

SPF - cMRO - Generate non-Routine Maintenance Forecast

SPF - cMRO Export non-Routine Maintenance Forecast

SPF - cMRO - Import cMRO or EAM Costs

SPF - cMRO - Export Non- Maintenance Forecast

SPF - cMRO - Calculate Demand Variability

SPF - cMRO Export Total Demand and Demand Variability


Export Planning Factors

SPF Upload Forecast Data & Metrics

Unit Cost

New Index

Cost Adjustment Factor

New Engine Profiles

Forecast non-UMP Work Orders








37 of 58 1/21/2013 8:06 PM





Top

3.8 Enhancements to PTP Engine

Description Improvements have been made to the Analytical Engine's ability to review and analyze indirectcannibalization and halo effects caused by promotions. Enhancement filters information viewedby the engine and reduces changes of overfitting.




IGLIndirectLimit


UseEnvelope - This parameter now accepts a value of '3'.






Sizing



XMLDB Usage


Load Balancing


New Bulk Interfaces





38 of 58 1/21/2013 8:06 PM









Top

3.9 Launch URL from Worksheet

Description In this release, Demantra provides the ability to embed a URL in a series and display it as a linkin any Demantra worksheet. The URL can then be used to launch a webpage or externaldocument.




Series Display properties window - The Hyperlink option has been added to the DisplayFormat setting.






<h5 >Sizing



XMLDB Usage


Load Balancing


New Bulk Interfaces





39 of 58 1/21/2013 8:06 PM









Top

3.10 Database Performance Improvements

Description Database performance can decline due to out-of-order tables or incorrectly defined primarykeys. In this release, standard mechanisms for performing database "health checks" (both aquick and thorough version) and procedures to rebuild key data tables, like SALES_DATA andMDP_MATRIX, are available. This procedure will be dynamically created in Demantra and canbe run either while the application server is live or when the application server is not running.




New Procedures

run_table_reorg.sql


MIN_NUMROWS_FOR_REORG

QUICK_CHECK_TIMEOUT

THOROUGH_CHECK_INTERVAL

THOROUGH_CHECK_TIMEOUT






Sizing



XMLDB Usage


40 of 58 1/21/2013 8:06 PM


Load Balancing


New Bulk Interfaces


Customizationsand Extensions Customizations and extensions are not possible for this feature.









Top

3.11 Demantra Trade Promotion Optimization - Enhancements to Optimization

Description This release provides the following enhancements to the Trade Promotion Optimization(TPO) module:

Exclusion rules: Users will be able to define a set of conditions that should not occurtogether in a solution. For example, you should not run a TPR simultaneously with anAd, and discount should exclude discounts in a certain range.

Optimized buydown: Buydown is now optimized like other variables in the optimizer.In previous releases, the buydown calculation was deterministic and calculated usingthe minimum retailer margin constraint. In this version, buydown is now part of theoptimization problem and the value is selected by the optimization process.

Vehicle cost overrides: The vehicle_cost expression has been changed to allow costevent overrides per causal and per transpose.

Control over impact of financial constraints: Provide the ability to turn off financialconstraints such as minimum manufacturer or retail margins.

Define baseline: If a manual override was done to the baseline forecast, customersmight require that value be used as the baseline for the promotion when calculatingRevenue and Profit. In this release, we provide control over the expression denotingbaseline.


This section lists the components that were added, changed, or made obsolete for thisfeature in Oracle Demantra in this release. These components may include the following:worksheets, series, levels, methods, workflows, system parameters, reports, messages,APIs, programs, tables, views, profile options, and integration interfaces.

Refer to the "Oracle Demantra Release 12.1.3.7 (7.3.1.3) Transfer of Information" for moreinformation. Please check the Oracle Demantra Documentation Library Document 443969.1frequently for updates.

New Tables


41 of 58 1/21/2013 8:06 PM

This table lists the new tables.

Table Name Description

TPO_EXCLUSION_RULES Stores the definition of exclusion rules which areused by the promotion optimization engine.






Sizing




XMLDB Usage


Load Balancing


New Bulk Interfaces


Customizations andExtensions




Technology StackIncompatibilities






Top

3.12 Embedded Demantra Worksheets in VCP Applications

Description In release 7.3.1.4, using Demantra Anywhere, Value Chain Planning (VCP) applications allowusers to access Demantra applications and worksheets from the VCP application. A separate login is not required, and the user does not need to open a second browser instance.


42 of 58 1/21/2013 8:06 PM

This enhancement also provides additional support for the following mobile technologyapplications:

Apple iPad

For details, refer to "Embeddable Worksheets" in the Oracle Demantra Implementation GuideSupplement.



Please check the Oracle Demantra Documentation Library, Document 443969.1, frequently forupdates.



This section lists the setup steps that were added or changed in Oracle Demantra in thisrelease. For additional details about performing the setup steps listed below, refer to thedocumentation described in 2.1 Online Help and PDF Documentation.

To enable this feature, communication is established via a URL with specified parameters. Thelogin process requires Oracle Single Sign On, and both applications must be registered with thesame SSO server. The Demantra application must be configured to use Demantra Anywhere (goto Security > Create/Modify User, select a user, go to Modules, and enable DemantraAnywhere).

Refer to the following:

See "Access to Embedded Demantra Worksheets" in the Oracle Advanced PlanningCommand Center User's Guide Supplement.

See "Embeddable Worksheets" in the Oracle Demantra Implementation GuideSupplement.



Sizing




XMLDB Usage


Load Balancing


New Bulk Interfaces



43 of 58 1/21/2013 8:06 PM











Top

3.13 Demantra Predictive Trade Planning (PTP) Promotion Calendar

Description Promotion calendars graphically display promotions in an interactive calendar. In a promotioncalendar, levels, table and calendar are combined into a single graphical representation. Theleft side displays aggregative levels and summary information. The right side displayspromotions across time as part of a promotional calendar.

Each promotion appears as a separate box in the calendar, and each may display several seriesand their values (for example, Vehicle Type, Start and End Event dates, Event Spend).

The ability to define a Promotion Calendar is available in release 7.3.1.4. For details, refer tothe Oracle Demantra Implementation Guide Supplement.



Please check the Oracle Demantra Documentation Library Document 443969.1 frequently forupdates.


This table lists system parameters that are new.

New System ParameterName

TechnicalName

Description

AllowUpdatesfromCalendar - Control whether or not boxes can bemoved/resized on the calendar. If"AllowUpdatesfromCalendar"="No"(default setting) for a Calendar View,then users cannot move or resize boxeson the calendar. If"AllowUpdatesfromCalendar"="Yes" for aCalendar View, then users can updatedates by moving or resizing boxes on theCalendar in the same way the ActivityDetails/Gantt Chart works today.




TechnicalName

Description


44 of 58 1/21/2013 8:06 PM

Worksheet Designer -Calendar View option

- New right-click menu option, CalendarView, for Level in Layout page. SelectCalendar View to display promotions onplanning calendar in Promotion Calendarview.

New Tables

This table lists the new tables.

Table Name Description

CALENDAR_VIEW_DEFUsed to define general information about thePromotion Calendar.

Refer to "Defining a Promotion Calendar" in theOracle Demantra Implementation Guide Supplementfor more information.

CALANDER_SERIES_DEFUsed to define the series that will appear in thePromotion Calendar.

Refer to "Defining a Promotion Calendar" in theOracle Demantra Implementation Guide Supplementfor more information.

New Views

This table lists the new views.

View Name FeatureArea

Description

Promotion Calendar -The Promotion Calendar graphicallydisplays promotions in an interactivecalendar.

Refer to "PMO: Promotion Calendar" inthe Oracle Demantra Predictive TradePlanning User's Guide for moreinformation.



This section lists the setup steps that were added or changed in Oracle Demantra in thisrelease. For additional details about performing the setup steps listed below, refer to thedocumentation described in 2.1 Online Help and PDF Documentation.

Define your promotion calendars using the new tables and system parameters mentionedabove. Refer to "Defining Promotion Calendar" in the Oracle Demantra Implementation GuideSupplement for details.



Sizing



45 of 58 1/21/2013 8:06 PM



XMLDB Usage


Load Balancing


New Bulk Interfaces












Top

3.14 Aggregate Work Orders

Description As part of Asset Intensive Planning (AIP) projected use of material and resources coming fromeAM and cMRO is loaded into Demantra striped by key work order attributes.

Processing a large volume of work orders individually in ASCP for the entire projection horizonmay adversely affect performance.

In EBS release 12.1.3.8, work orders may be aggregated when loaded into ASCP. Thisaggregation level is higher than the aggregation used in Demantra. Demantra release 7.3.1.4supports this aggregation. Detailed work order information is loaded from ASCP to Demantra(as in previous releases) while aggregate information is imported directly from ODS.







This section lists the setup steps that were added or changed for Oracle Demantra in thisrelease. For additional details about performing the setup steps listed below, refer to the


46 of 58 1/21/2013 8:06 PM

documentation described in 2.1 Online Help and PDF Documentation.

Set the Maintenance Work Order options for the appropriate time periods in the Aggregation tabof the Plan Options page. Refer to "Understanding Aggregate Work Orders" in the OracleDemantra Implementation Guide Supplement for details.



Sizing




XMLDB Usage


Load Balancing


New Bulk Interfaces












Top

3.15 Demantra User Interface (UI) Enhancements

Description In release 7.3.1.4, the Demantra user interface has been enhanced to provide a better userexperience and enhanced security. The application interface "look and feel" has been updatedto match other Oracle applications. The application has also been streamlined to reduce thenumber of steps or clicks to perform tasks.

User Interface Enhancements

In this release, Demantra provides the following user interface enhancements:

Enhanced visuals including gradients and 3D graphs.

Ability to access level methods from toolbar


47 of 58 1/21/2013 8:06 PM

Configurable colors and fonts

Hide frame - Each worksheet tab has a frame around it. This frame allows you tominimize, maximize, and re-size the worksheet tab. To hide these frames, click HideFrames in the Options menu.

Drag and drop levels and series in a table - Levels and series within a worksheet can bemoved using drag and drop.

Graph display enhancements - New graph display styles are available by right-clicking agraph and selecting an option. Graphs can now display as 3-D and the angle of the 3-Dappearance can be altered by clicking and holding mouse over over the graph. Movingthe pointer over the graph changes the angle of the 3-D graph highlight.

New toolbar icons - More consistent appearance and improved usability.

Display Methods in the Toolbar - New setting allows methods to be displayed as an iconon the toolbar.

For information about the toolbar and interface changes, refer to the Demantra Predictive TradePlanning User's Guide.





This table lists system parameters that are new.

New System ParameterName

TechnicalName

Description

client.lookAndFeel.newIcons - Determines whether the application usesthe new icons that are used by default inrelease 7.3.1.4. Valid values are 1 (usenew icons) and 0 (use pre-7.3.1.4 icons).




TechnicalName

Description

Level Method EditPromotion (in BusinessModeler)

-This dialog has been modified to includethe following:

Enable Toolbar Display - Thischeck box is used to display LevelMethods for toolbar. The defaultfor this option is unchecked.

Toolbar Icon path - Used to thespecify toolbar icon.

These settings will be global and applyto all Users and Worksheets that accessthe Method.




48 of 58 1/21/2013 8:06 PM

This section lists the setup steps that were added or changed for Oracle Demantra in thisrelease. For additional details about performing the setup steps listed below, refer to thedocumentation described in 2.1 Online Help and PDF Documentation.

Set the Level Method Edit Promotion - General Properties Window - Configure Methods dialog inBusiness Modeler to display Level Method in the toolbar.



Sizing




XMLDB Usage


Load Balancing


New Bulk Interfaces












Top

4. Diagnostics and Logging

Application Server Messages

The Application Server writes logs that record activity of the server and clients.

Server Logs

The default server log location is the Demantra_root/Collaborator/virtual_directory/portal/logs directory.

Follow the comments in the Demantra_root/Collaborator/virtual_directory/portal/conf/logconf.lcf file to specify this log fileinformation:


49 of 58 1/21/2013 8:06 PM

Name and location

Maximum size of the log file

Number to keep

Log categories and log level

You can also set log levels at runtime with the following URL:

http://Demantra_root/Collaborator/virtual_directory /admin/loggerManager.jsp

Client Logs

Client logs are written by Java Plugin into the Java Plugin console and/or log files according to the Java Plugin configuration.

The default log location is the following directory: Demantra_root/Collaborator/virtual_directory/portal/logs.

Follow the comments in the Demantra_root/Collaborator/virtual_directory/portal/conf/ClientLogConf.lcf file to specify which logcategories are written during runtime.

Integration Failures

Integration (data upload) failures appear in these places:

Application Server log file.

For data validation failures, a database table whose name is the same as the data source table appended with_ERR.

Engine Failures

If the engine fails during execution, check the following logs:

manager.log

engine2k.log

To access file manager.log, perform the following:

In Windows, view the console of the Engine Administrator. To it change to a log file, use the Engine Administrator > Settings> Configure > tab Engine Manager log settings > dropdown Output Target > File.

In Linux, copy files /bin/Setting.xml and /bin/EngineAdministrator.exe to a Windows machine and follow the instructions forWindows. Copy file Settings.xml file back to Linux directory /bin.

To access file engine2k.log, perform the following:

In Windows, go to folder <drive from which you registered the Engine>/engine2k/<DB server name and schema that theengine uses>. There are time-stamped log files for each execution.

In Linux, go to folder $ENGINE_ROOT/engine2k/<DB server name and schema that the engine uses>. There aretime-stamped log files for each execution.

Contact Oracle Support for instructions on the following issues:

Setting appropriate log levels

Handling exceptions

Client Issue - Out of Memory

Verify memory settings: Windows Start menu > Settings > Control Panel > Java plug in the Plug-In Control Panel frame appears >tab Advanced > verify that the value of field Java Runtime Parameters is at least-Xmx256Mand is based on the client machinehardware/RAM capacity. Oracle recommends value-Xmx512Mfor heavy duty client side use.

Check the physical memory on the machine on which the user interface is running. If the machine has other processes that consumeoperating system memory, the user interface may run out of memory even before it reaches the memory limitation because theoperating system does not allocate more memory to the Java Virtual Machine process.

To view actual memory usage at runtime, use these Java console commands:

m: Displays total memory and free memory. Usage is total memory less free memory.

g: Requests the Java virtual machine to collect garbage then display the information from commandm.


50 of 58 1/21/2013 8:06 PM

s: Displays all Java runtime parameters

Oracle suggests executing commandgthree times in 30 seconds then executing commandmonce.

If the Plug-in Console window is not accessible from the System Tray, view the plug-in log file directly at $USER_HOME/ApplicationData/Sun/Java/Deployment/log directory/pluginXXX_XX.trace; XXX_XX is your Java version.

Client Issue - Java Threading

Use the-verboseoption; which is a Java VM option in the Java Control Panel > Java Runtime Parameters > tab Advanced. Oraclerecommends you use-verbose:gcto put as little spare text in the console as possible (explained below).

When you theverboseoption every time an applet executes, a DOS console window opens in which the specified verboseinformation is required. Ignore the information and press Ctrl+Break to get the client stack trace.

The verbose options are as follows:

-verbose:class: Displays information about each class loaded

-verbose:gc: Reports garbage collection events. It creates a smaller console log than the-verbose:classoption and helpsto debug memory usage and patterns

-verbose:jni: Reports information about the use of native methods and other Java Native Interface activity.

Installer Logging

For installation issues, turn on the debugging option.

Execute program setup.exe > a splash screen appears > select Configure Log > select custom settings >set the file name andlocation > select log level DEBUG.

Database Stored Procedure Logging

The DB_EXCEPTION_LOG and DB_WARNING_LOG tables contain diagnostics. The messages should be viewed with ORDER BYERR_DATE.

Some of the Demantra Stored Procedures for the Oracle Databases have a logging mechanism. This mechanism is controlled by theLOG_IT_PARAMS table.

LOG_IT_PARAMS.PNAME is the name of the functionality that is logged. For example; insert_units, chaining, and proport.

LOG_IT_PARAMS.LOG_TABLE is the name of the table where the log messages are written.

LOG_IT_PARAMS.LOGGING.LEVEL is the level of detail logged:

0 = no logging

6 = maximum logging

Notes:

Never modify the PNAME or LOG_TABLE values.

Do not modify the LOGGING_LEVEL while Demantra is actively processing.

Setting LOGGING_LEVEL to a value greater than 0 can negatively impact performance.

Messages written to LOG_TABLE should be ordered by LOG_ID.

Return to Diagnostics and Logging

Top

5. Known Issues in Oracle Demantra Release 7.3.1.4

This section provides information about known issues with Oracle Demantra in Release 7.3.1, and possible workarounds for thoseissues. This document has been updated to provide additional information for release 7.3.1.4.

The information provided below applies to all Oracle Demantra customers who are installing, or upgrading to, Oracle DemantraRelease 7.3.1.

This section may be updated from time to time. Always check My Oracle Support for the most current version of this documentbefore you begin to install or upgrade your system.

The table below displays the Known Issues.


51 of 58 1/21/2013 8:06 PM

Date Known Issue Resolution Fixed In

July 1, 2009 When using the MozillaFirefox browser, if aDemantra user closesthe browser using the Xicon, it is possible torestore the session byre-launching a newFirefox browser. In thisscenario, the login pageis not displayed and theuser is not required toenter a username andpassword.

Modify Mozilla Firefox configuration settingsas follows:

Select Tools > Options > Startup > tabMain.

1.

Verify that when Firefox starts, it is notset to Show my windows and tabsfrom last time. Change this setting asrequired.

2.

Navigate to tab Security and verifythat Remember password for sites isnot selected.

3.

Save your changes.4.

Fix not yet available.

July 1, 2009 Oracle Demantra maycreate database tablesin a single table spacerather than the tablespaces that youspecified when youinstalled OracleDemantra. This mayaffect systemperformance.

The database administrator can manuallycreate key tables and indexes with thedesired table spaces after running the OracleDemantra Installer.


June 1, 2010 A Demantra user wantsto review and/orsimulate only GeneralLevel data, such asCTO Base Modeldemand, in aworksheet. If youinclude only GeneralLevels in a worksheet,meaningful results forsales_data series suchas Adjusted History,Simulation, andConsensus Forecastcannot be viewed. Thevalues are displayed asthe total across theentire systempopulation, which is notexpected behavior andcan negatively affectsystem performance. Italso does not providesufficient context forsimulation.

Follow these steps to review data with only aCTO level, such as the Base Model:

If the data is exclusivelyGeneral Level data series,construct a worksheet usingonly General Levels, such asCTO or promotion levels.

1.

If the data includes a mix ofGeneral Level and sales dataseries, include an item level inthe hierarchy.

2.

For example, if you want to review, adjust,and simulate independent demand for yourbase model, construct a worksheet with theitem level, Parent Item level and filter onDemand Type = Base Model. If you want toreview, adjust and simulate promotions, youmust construct a worksheet with an itemlevel, such as Promotion Group, in addition topromotion levels.


November 2010 Failure Rate Calculation

As implemented inDemantra 7.3.1, thefollowing seriescurrently use straightaverage, not weightedaverage:

SPF CalculatedForecast

SPF Failure Rate% Calculated

Use two sets of series. One set will be usedfor client expression failure rates. These canuse weighted averages. The other set will beused for SPF Batch and hook calculations.These will not have weighting. Since batchand hook calculations always run onlowest-level data, there is no need for anyweighting.

The series that drive edit propagation can bechanged. For back-end, worksheet hook andbatch calculations, modifythespf_series_definitiontable. For frontend, client-expression calculations, modify



52 of 58 1/21/2013 8:06 PM


SPF Failure Rate% Final

SPF Failure Rate% Override

SPF FinalForecast

The user can see adiscrepancy betweenclient propagation(based on straightaverage) and updatehook calculation(performed at lowestlevel).

This issue can causethese series to giveincorrect values ataggregate levels, andcause clientexpressions to performincorrect propagations.The back-end hook willalways calculate andstore the correctvalues.

thetree_view_edit_propagationtable.

November 2010 When running theengine in PE mode,rows in thePROMOTION_DATAtable that containnon-null records foranother engine profilemay be deleted.

To ensure that the non-null rows are notdeleted when the engine runs with a differentengine profile, set the engine parameterDeleteIsSelfCondition to "0" for that profile.


November 2010 (Known issue withDemantradocumentation - Thisinformation was notincluded in the release7.3.1 Oracle DemantraImplementation Guide.)

The system parameter"SimNotification", whichis defined in theAPS_PARAMS table, isavailable in release7.3.1 but was notincluded in the release7.3.1 Oracle DemantraImplementation Guide.

This parameter controls whether Demantradisplays a message in the following scenario:

A simulation that has not yet beenaccepted or rejected already exists forthe current user and worksheet.

The Accept Simulation, RejectSimulation, or both options aredisabled for the current user.

The user chooses to create a newsimulation.

If this option is set to True (the default),Demantra displays a message indicating thata simulation already exists. The user canthen either accept or reject it based on theirprivileges.

If this option is set to False, Demantra doesnot display a message and automaticallyaccepts or rejects the simulation based onthe user's privileges.

Documentationupdated for version12.2.

November 2010 (Known issue withDemantradocumentation - Thisinformation was not

To enable a new User Group to accessWorkflow Manager:

Determine the application_id of thenew group from the APS_PARAMS

1.

Documentationupdated for version12.2.


53 of 58 1/21/2013 8:06 PM


included in the release7.3.1 Oracle DemantraImplementation Guide.)

Flagging a new UserGroup as a"Collaboration Group"does not provide accessto the WorkflowManager.

table.

In Business Modeler, navigate toParameters > System Parameters >Application Server > Workflow (tab).

2.

Add the application ID of the new UserGroup to the existing list of values forthe "workflow group" parameter(separate values with a comma).

3.

Save the changes, and then restart theapplication server.

4.

January 2011 Demantra cannot beused with SSL mutualauthentication (clientauthentication) whenusing Java version1.6.0_23.

To use SSL mutual authentication (clientauthentication), use Java 1.6.0_19 andperform the following:

In the Java control panel, go to the Java tab,and then click View. In the Java RuntimeEnvironment Settings window, enter thefollowing in the Runtime Parameters field andthen save the change:

-Dsun.security.ssl.allowUnsafeRenegotiation= True


August 2011 On the Windows Vistaplatform, if theDemantra user doesnot have administratorprivileges:

The ExportWorksheet toExcel featuresdoes not work

Worksheets willnot open whenMutual SSLauthentication isenabled

Disable the Windows Vista "User AccountControl" (UAC) feature.


August 2011 An issue with thehttpOnly cookieattribute and Java 5code base causeslogging issues inDemantra worksheets.

Set the 'httpOnly' parameter in theapplication server configuration file to False,or delete it. For example, if using Tomcat, theparameter 'useHttpOnly' is defined inserver.xml. If using Web Logic, 'cookie-http-only' is defined in weblogic.xml.


August 2011 The 'undo' action (Edit> Undo, or Ctrl + Z)does not work afterusing the 'Edit Cells'action to modify morethan 25 rows at thesame time.

Select Data > Reset Manual Changes, orrerun the worksheet without saving thechanges; either action will reset all changedvalues.

Also note that if the 'Same Value Update'setting for a modified series is set to Yes,then the user will see that the change hasnot been "undone."


August 2011 Oracle Deductions andSettlementManagement (DSM)worksheets fail to loadwhen using Oracle DBversion 11.1.0.6 or

Upgrade Oracle DB to 11.1.0.7 or later. Fix not yet available.


54 of 58 1/21/2013 8:06 PM


earlier.

January 2012 Restricted Characters inSeries Names

The Oracle Demantra documentation doesnot address the restrictions for using specialcharacters when entering or updating seriesnames.

You can use any combination of letters,numbers, and characters when namingseries, but the following characters shouldnot be used:

.

=

+

|

:

-

*

/

\

<>

These characters are all valid Operators thatcan be used when defining a client or serverexpression. Using any of these characters in aseries name can result in unexpectedworksheet behavior and is therefore notrecommended.

Documentationupdated forDemantra 12.2release.

January 2012 (Known issue withDemantradocumentation - Thisinformation was notincluded in the release7.3.1 Oracle DemantraImplementation Guideand Oracle DemantraUser's Guide. )

Description of the 'FullContext' Open Withoption.

The 'Open with Context' feature specifies howa worksheet should be filtered when a useropens it through the Open or Open Withmenu options on the right-click menu.

Selecting Full Context (for Sub-Tabworksheets) generates the full context for allLevels in the calling worksheet. For theOpen-With worksheets, this is the same aschoosing the Selected Context option.


January 2012 (Known issue withDemantradocumentation - Thisinformation was notincluded in the release7.3.1 Oracle DemantraImplementation Guide.)

Description of new logcategory in thelogconf.lcf file.

The parameter collaborator.login.user can beset in the logconf.lcf file. When this logcategory is enabled, the following informationwill print out to the collaborator.log file:

date/time : User "username" loggedin, "number" users online.

date/time : User "username" has beenbrutally logged out, "number" usersonline.

date/time : User "username" loggedout, "number" users online.

For additional information, refer to Logging



55 of 58 1/21/2013 8:06 PM


Messages of the Application Server in theOracle Demantra Implementation Guide.

May 2012 NON UMP Forecastreturns zero results.

Before loading CMRO data:

Log in to workflow manager as user'dm'.

1.

Open the the "SPF-cMRO - ImportcMRO Data" WF Schema.

2.

Go to the Proport Procedure Step (3rdstep from the end).

3.

Change 2nd Parameter value to 1.4.

Run the WF to load the CMRO data.5.

Run the NON UMP Forecast engine andreview engine results.

6.


June 2012 If you haveAuto-Update enabled,your JRE 1.6 versionwill be updated to JRE7. Although Demantramay work with JRE 7, ithas not been testedand is therefore notofficially supported.

Disable JRE Auto-Update (Java Control Panel> deselect Check for UpdatesAutomatically.)

Fix available in12.2.1.

Return to Known Issues

Top

6. Change Record

Date Description of Change

September 2012 Published document for 7.3.1.4 updates.

May 2012 Published document for 7.3.1.3 updates.

January 2012 Updated to address special character restrictions, Full Context Open Withoption, and new log category, collaborator.login.user.

January 2012 Published document for 7.3.1.2 updates.

September 2011 Published document for 7.3.1.1 updates.

August 2011 Published update.

January 2011 Published document.

Top

7. Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


56 of 58 1/21/2013 8:06 PM

Copyright Notice

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure andare protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may notuse, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in anyform, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors,please report them to us in writing.

Restricted Rights Notice

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable FederalAcquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, andadaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extentapplicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial ComputerSoftware License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed orintended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you usethis software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup,redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damagescaused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respectiveowners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license andare trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo aretrademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from thirdparties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect tothird-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, ordamages incurred due to your access to or use of third-party content, products, or services.

Revenue Recognition Notice

The information contained in this document is for informational sharing purposes only and should be considered in your capacity asa customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material,code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of anyfeatures or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Youraccess to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and ServiceAgreement, which has been executed and with which you agree to comply. This document and information contained herein maynot be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This documentis not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries oraffiliates.

References

NOTE:443969.1 - Oracle Demantra Documentation LibraryNOTE:1462296.1 - Oracle Value Chain Planning (VCP) Readme, Release 12.1.3.8


57 of 58 1/21/2013 8:06 PM

NOTE:1490558.1 - Oracle Demantra Installation Guide, Release 7.3.1.4NOTE:1490559.1 - Oracle Demantra System Requirements Guide, Release 7.3.1.4


58 of 58 1/21/2013 8:06 PM

Documents

Oracle Demantra Release Notes for 7.3.1.4