Oracle Demantra Release 12.2.5.

1 - Last Updated 10/06/2015

===========================================================

For full installation instructions, please carefully review the Oracle Demantra
Installation guide (dmt_ins_122.pdf) found in the root folder of the installation
package, in particular 'Instructions for Installing this Release'. Also note the
latest patches for any release (including installation guide changes) can be found
on My Oracle Support (formerly known as Metalink). The latest documentation can be
found in the Demantra Documentation Library:

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=443969.1

Note: Please check My Oracle Support (MOS) Note 2123528.1 for information about
mandatory 12.2.5.1 patches.

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 example,
C:\Demantra\7.3.1\Collaborator\demantra.

2. Once this is complete, deploy the WAR file.

Important upgrade notes:

========================

1. 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
Demantra 7.1.1 onwards). You should choose the 'Platform Upgrade Only' option only
if your implementation is highly customized. A platform-only upgrade will preserve
custom configurations and enable new platform functionality. It will not introduce
new application objects. Also note Demantra 7.2.1 customers should contact support
prior to running an application upgrade, to get latest patch details for 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 release
and/or due to customer extensions in their implementation. In a default upgrade
mode, the current versions of these objects will be preserved during the upgrade
process and, where there are conflicting definitions with the new Oracle version,
we will create duplicate objects with a version suffix.

For example, if you extended the configuration of the workflow 'EBS Price List
Download', the upgrade process will maintain this and introduce the Oracle standard
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 latest
configuration will be 'EBS Full Download'). You will identify the latest version by
either a suffix of the latest version, or by a sibling item with an earlier version
stamp. You may then review the two and merge as appropriate. In the case of
duplicate objects, it is recommended to use the latest version, preferably after
removing the '_730' suffix and merging any of your customizations into the 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
promotions to have multiple tactics per promotion, typically for different items or
locations being promoted. While promotion type can now vary across different items,
locations, it should not vary below the Lowest Promotional Level defined in the
forecast tree.

If you are uncertain as to which upgrade option to choose, please contact support
for guidance.

2. If you already installed 12.2.1 or 12.2.2 (using the application upgrade or new
installation), please do not choose the "platform and application upgrade" option.
Instead, choose to perform only a "platform upgrade."
2. If you are upgrading from a release that did not support In-Memory Consumption
Driven Planning (IM-CDP) functionality and you want to use IMCDP, you MUST select
the "Platform and Application Upgrade" option when running the Demantra Installer.
IM-CDP functionality will not work when upgrading from 7.3.1.4 or earlier ot 12.2.3
or earlier after a PLATFORM-only upgrade.

3. If you are upgrading from a release that did not support Service Parts
Forecasting (SPF) functionality and you want to use SPF, you MUST select the
"Platform and Application Upgrade" option when running the Demantra Installer. SPF
functionality will not work when upgrading from a pre-SPF supported release to
7.3.1 or later after a PLATFORM-only upgrade.

Important Notes:
===========================
1) In this release, the Oracle Demantra Installer supports both a 32-bit and a 64-
bit JVM for new installations and when upgrading with the 'Platform Upgrade Only'
option. However, a 64-bit JVM is required if upgrading with the 'Application and
Platform Upgrade' option. If you are using a 32-bit JVM and you select the
'Application and Platform Upgrade' option, the Installer will prompt you to specify
the JVM Path for a 64-bit JVM.

2) In this release, a new 'SysAdmin' component and "super user" are available.
Details about this component and user are provided in the Oracle Demantra
Implementation Guide.
When upgrading from a previousn earlier release, if additional Demantra components
are added, the user will be prompted to modify the system-generated password for
the SysAdmin user, and this password can be changed later (only by the SysAdmin
user) using Business Modeler. However, if no new components are added when running
the Demantra installer, then the system will automatically generate a password for
this user. In this case, the password can be modified by a database administrator
only by connecting to the Demantra schema and then executing the following
procedure:

EXEC ENCRYPTION.UPDATE_SUPERUSER( 'newpassword' );

Where 'newpassword' is the password for the SysAdmin user.

After it has been re-set using this method, a user can log in to Business Modeler
as the SysAdmin user and modify the password by choosing Security > Create/Modify
User, selecting the 'Administration' component, and then modifying the SysAdmin
user.

3) For Exadata and SPARC SuperCluster deployments it is recommended

MaxDBConnections be increased to 300 as a starting point configuration which can be
adjusted further based on customer sizing.

4) In this release, Oracle Demantra no longer supports the following database

procedures for performing worksheet updates and integration imports:

* MANUALS_INS
* MANUALS_INS_INTEGRATION
* MANUALS_INS_RECOVERY
* MANUALS_POPULATE_INS
* EXEC_MANUALS_INS_INTEGRATION

Also note that the ImportDataMode SYS_PARAM parameter is no longer supported.

Please note that the procedures and system parameter listed above are still
included in the 12.2.5 Oracle Demantra Implementation Guide. However, they are NOT
supported in 12.2.5 and all references to these procedures and the parameter will
be removed from the documentation in a futurethe next release.

NEW FEATURES AND ENHANCEMENTS IN RELEASE 12.2.5.1

=================================================

Site Level Integration with EBS

--------------------------------

The 12.2.5.1 release of Demantra allows users to collect historical data from EBS
at an aggregated account or aggregated customer level. This enhances previous
capabilities which could either collect data at a very granular site level or at a
very aggregate level ignoring this hierarchy altogether. This functionality
respects the current customer filters and key account settings.

This enhancement reduces the need to customize data integration between EBS and
Demantra.

Security Enhancements (Better SSL Support)

-------------------------------------------

Changes were made to the notification methodology between different parts of the
Demantra deployment stack including the Business Modeler (configuration module),
Application Server and Analytical Engine. Prior to 12.2.5.1, communication was
primarily via HTTP calls which could be disrupted if single sign on protocol was
put in place requiring application server restarts to facilitate changes in the
other modules. In addition, users inside the firewall could call processes if they
possessed the appropriate URL. This release also modifies the calling methodology
to use DB layer and Oracle Wallet for improved security as well as seamless
integration with any supported single sign on option.

Workflow Recoverability and Enhancements

----------------------------------------
In the 12.2.5.1 release changes were made to improve how Demantra handles workflows
that fail and require recovery. As part of each workflow steps definition user will
have a new recovery option where they specify the step from which a workflow will
restart, regardless of whether restart occurs automatically or is user initiated.

Users can now view workflows that they do not own, although only the workflow owner
can edit and save a workflow.

This release introduces a "Save As" function for copying existing workflows.

Time Zone Support

-----------------

As businesses grow and planning processes grow and encompass a larger and larger
global footprint. The complexities of supporting a truly global process with users
in different countries and time zones become apparent. The 12.2.5.1 release of
Demantra allows both worksheets and user initiated actions to respect the user's
location and time zone.

User's time zone difference from general system time will be used to adjust the end
of history and beginning of future for the user. In addition when a user calls a
method and simulation, the time zone they are in is available and can be used to
modify the process being called.

Publish Intermittency Flag to Inventory Optimization

----------------------------------------------------

The 12.2.5.1 release adds an Intermittency Flag to the integration from Demantra
Demand Management to the Value Chain Planning Inventory Optimization module.

The Demantra forecast sent to Value Chain Planning Inventory Optimization module is
used to generate safety stock. An important part of this calculation is an
indication as to whether or not the history and resulting forecast are
intermittent. An indication of intermittency will be used as part of the IO safety
stock calculation and may cause different methodology to be used resulting in more
accurate and appropriate safety stock values and improved service level.
3.6 Demantra Anywhere Enhancements (Improved Mobility Support)

In the 12.2.5.1 release, enhancements were made to the Demantra Anywhere (DA)
product to better support mobility. Functionality which was previously only
available in a full worksheet will now be available in Demantra Anywhere worksheets
as well. The user will be able to execute seeded and custom methods, enabling a
much more robust support of a variety of business process including promotion
management and new item introduction. In addition the user will be able to call the
Demantra engine to execute simulations for ad-hoc what if analys

User Interface Enhancements

---------------------------

The 12.2.5.1 release refreshes parts of the Demantra user interface to better align
with more modern standards and other oracle products. The information displayed on
screen will continue to have high informational density but the borders and other
objects displayed will be modified and cleaned to reduce clutter and create a
cleaner more efficient work environment. Graphs will also be simplified to provide
a cleaner view. The modified settings will be part of preset configurations. Users
can choose between the pre-7.3.1.4 user interface, the revised 7.3.1.4 user
interface, or the new 12.2.5.1 interface.

If you are upgrading from a 7.3.x.x Oracle Demantra version to release 12.2.5,
please refer to 12.2.5 Oracle Demantra Release Notes. This document is cumulative
and describe all changes and new features in release 12.2.0, 12.2.1, 12.2.3, 12.2.4
and 12.2.5.

Known upgrade issues:

=====================

Issue:
If you are upgrading both the platform and the application, then new versions of
existing worksheets may be duplicatedcreated as duplicates of existing worksheets.
When worksheets are duplicated, the new worksheets are not automatically selected
in the 'My Worksheets' list in Collaborator Workbench. Any old worksheets which
were selected prior to the upgrade will still be selected.

Workaround:
After the upgrade, users should manually select the new duplicated worksheets in
the 'My Worksheets' list and use those new worksheets going forward (since they are
the latest version of the worksheets).

Issue:
12.2.1 Color Scheme: In that release, a new color theme (grey with a light blue
background) has been added to the Demantra worksheets. As part of the installation
or upgrade, the new theme will be applied system-wide.
Upgrading customers should be aware that a few seeded Demantra series have color
expressions that evaluate to the blue color, which was available in the pre-12.2.1
color scheme (this is referred to as the "classic" Demantra theme).

The list of series are:

- Abs % diff: Constrained Forecast Value and Budget
- Adjusted History
- Budget Value
- Cumulative Budget
- Demand Fill %
- Final Forecast
- Production Plan Accuracy
- Projected On-Hand Accuracy
- Utilization %

Workaround:
To display the new color code in the above series, replace each occurrence of
'15786191' with '11119017' in the series' color expression. The change can be made
within the Business Modeler after the upgrade is complete.
Note: You can also switch to the "classic" color scheme that was provided in
previous Demantra releases by modifying the 'UI_Definitions.properties' file (see
instructions below). The series listed above will not require any changes if you
switch to the "classic" theme.

To revert to the look and feel of previous Demantra versions:

1. Create a backup of the file 'Classic_UI_Definitions.properties'
2. Rename 'Classic_UI_Definitions.properties' to 'UI_Definitions.properties'
3. Restart the application server.

Issue:
Performing an application upgrade when data model time definitions are daily or
weekly monthly can result in unintended changes to data model.

Workaround:
For monthly customers execute the following from SQLPlus after upgrade before
interaction to data model
Update DM_WIZ_DM_DEF set time_bucket='month' where lower(time_bucket)='week';
Commit;
For daily customers execute the following from SQLPlus after upgrade before
interaction to data model
Update DM_WIZ_DM_DEF set time_bucket='day' where lower(time_bucket)='week';
Commit;

Review seeded worksheets and integration profiles and ensure time definitions and
from and until dates are set correctly.

Known Issues:
=============

Issue:

When activating component for the 1st time in 12.2.5.1, default workflows which
include engine steps will not be set up correctly to call the engine.
For example, when activating the CDP component, the engine will not get executed
when running the CDP related workflows. This will not impact any components which
are active during the upgrade to 12.2.5.1

Workaround:

After component is activated, update the web_upgrade_level parameter in SYS_PARAMS

table to 0 and start the application server.
This action will update the relevant workflows to use the new engine call
methodology on the APS startup.

Issue:

When using the Mozilla Firefox browser, if a Demantra user closes the browser using
the X icon, it is possible to restore the session by re-launching a new Firefox
browser. In this scenario, the login page is not displayed and the user 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 from
last time. Change this setting as required.
3. Navigate to tab Security and verify that Remember password for sites is not
selected.
4. Save your changes.

Issue:

Oracle Demantra may create database tables in a single table space rather than the
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
desired table spaces after running the Oracle Demantra Installer.

Issue:

A Demantra user wants to review and/or simulate only General Level data, like CTO
Base Model demand, in a worksheet. If you include only General Levels in a
worksheet, 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 behavior
and can negatively affect system performance. It also doesn't provide sufficient
context for simulation.

Workaround:
If you want to review data in the context of only a General Level, such as CTO Base
Model or Promotion, perform the following:
1. If the data to be reviewed is exclusively General Level data series, construct 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
series, 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 construct a
worksheet with an item level, such as Promotion Group, in addition to promotion
levels.

Issue:

Failure Rate Calculation

As implemented in Demantra 7.3.1 and later releases, the following series currently
use straight simple average, not weighted average:
 * SPF Calculated Forecast
* SPF Failure Rate % Calculated
* SPF Failure Rate % Final
* SPF Failure Rate % Override
* SPF Final Forecast

The user can see a discrepancy between client propagation (based on straight
average) 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 hook 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 calculations
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 hook
and batch calculations, modify the spf_series_definition table. For front end,
client-expression calculations, modify the tree_view_edit_propagation table.

Issue:

When running the engine in PE mode, rows in the PROMOTION_DATA table that contain
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
different engine profile, set the engine parameter DeleteIsSelfCondition to "0" for
that profile.

Issue:

On the Windows Vista platform, if the Demantra user does not have administrator
privileges:

- The Export Worksheet to Excel features does not work

- Worksheets will not open when Mutual SSL authentication is enabled

Woraround:
Disable the Windows Vista "User Account Control" (UAC) feature.

Issue:

The 'undo' action (Edit > Undo, or Ctrl + Z) does not work after using the 'Edit
Cells' action to modify more than 25 rows at the same time.
Workaround:
Select Data > Reset Manual Changes, or rerun the worksheet without saving the
changes; either action will reset all changed values.

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 has not been "undone."

Issue:

E-mail workflow step does not work when using SSL or non-default port number (25).

It is also possible that the user's e-mail server requires authentication, uses a
non-default SMTP port (the default is 25) or requires a secured connection (SSL).

Demantra supports only plain SMTP connection using default port 25 without user
authentication to the e-mail server.

Workaround:
Do not use SSL or disable user authentication.

Issue:

Tomcat Version 7 and HTTPOnly Setting.

The Tomcat 7 HTTPOnly setting is defined as On by default. Currently, Demantra does

not support HTTPOnly.

Workaround:
To run on Tomcat 7, you need to set HTTPOnly to Off.

Issue:

Oracle Deductions and Settlement Management (DSM) worksheets fail to load when
using Oracle DB version 11.1.0.6 or earlier.

Workaround:
Upgrade Oracle DB to 11.1.0.7 or later.

Issue:

Protocol ICMPV4 Is Blocked By Default on Windows 7.

ICMPv4 protocol is blocked by default causing timeout when the database is trying
to communicate with the remote application server showing ORA-12535 and ORA-29273.

Workaround:
Refer to the following document for information on resolving this issue:

http://technet.microsoft.com/en-us/library/cc972926%28WS.10%29.aspx

Issue:

In Firefox, the Close this window link does not close browser.

Workaround:
Firefox does not allow windows that are manually opened to be closed through code.
This is not a Demantra bug. It is the way Firefox is designed to function.

Issue:

Firefox blocks plug-in when using Java version 1.6_30 and earlier. For details, see
https://addons.mozilla.org/en-US/firefox/blocked/p80.

Workaround:
Upgrade to Java version 1.6_31, or the latest version of Java 1.7.

Issue:

The 'Duplicate Promotion' method does not adjust the start date correctly when used
in a weekly environments using Calendar Month environmentfunctionality.

Workaround:
The Duplicate Promotion method should not be used in Calendar Month
implementations. Copy promotion is the only supported method to copy promotions in
this case.

Issue:

Create Similar Product failing.

Performing an application upgrade will add new series entries into the
NPI_SERIES_DATA table to support new Launch Management functionality. Some of these
series are incompatible with the existing Create Similar Product functionality and
will cause failure during the collections driven data copy. The incompatibility
will also occur if it is a new Demantra implementation.

Workaround:
Use Launch Management capabilities instead of Create Similar Product, or system
administrator should remove the following rows from the NPI_SERIES_DATA table.

SOURCE_SERIES TARGET_SERIES APPLICATION_ID

prop_changes prop_changes NPI_SERIES_DATA:9
lead_time lead_time NPI_SERIES_DATA:10
cdp_target_wos cdp_target_wos NPI_SERIES_DATA:11
up_time up_time NPI_SERIES_DATA:12
cdp_sell_thru_hist_ovr cdp_sell_thru_hist_ovr NPI_SERIES_DATA:13
ship_date ship_date NPI_SERIES_DATA:14
end_date end_date NPI_SERIES_DATA:15
cons_promo cons_promo NPI_SERIES_DATA:16
promo_price promo_price NPI_SERIES_DATA:17
ed_price ed_price NPI_SERIES_DATA:18
event_type event_type NPI_SERIES_DATA:19

Note: removing the series will impact Launch Management ability to support PTP use
cases.

Bugs fixed in 12.2.5.1:

======================

20594826 LINKING AND UNLINKING PROCESS NOT WORKING AFTER APPLYING PATCHES
20493849 EXPORT TO EXCEL FOR ROWS GREATER THAN 65000
21923736 EBS 12.2 SV6: INTEGRATION WITH RAPID PLAN NOT BRINGING IN CONSTRAINED
FORECAST
20643140 FORWARD PORT OF 12.2.4.1 BUG 20520872 TO 12.2.5.1 HEAD
9259750 ABILITY TO INCREASE THE MAXSQLINEXPRESSIONTOKENS PARAMETER TO
GREATER THAN 1000
21883652 GSE EBS 12.2 SV6: LOGOUT LINK FOR DEMANTRA CWB & WORKFLOW NOT WORKING
20272206 WORKSHEET PERSONALIZATION DOES NOT SHOW FULL NAME
20005254 SSO CAN'T REDIRECT TO ENGLISH INTERFACE, ALWAYS TO CHINESE INTERFACE.
21182313 PROCEDURE NAMED EP_LOAD_SALES CREATES HUNDREDS OF SESSIONS
21090394 DEMANTRA 12.2.3 CANNOT CHANGE WORKSHEET OWNERSHIP FROM BUSINESS MODELER
20601373 FD INSERT_UNITS GET_FORECAST_LEVEL SHOULD USED THE PARENT_ID FOR SUBSET

20442872 FD 12.2.5.1 - CANNOT DUPLICATE PROMOTIONS IN VERSION 12.2.4.1

21220646 FD 12.2.5.1 - THE VALUES OF REGION AND BRANCH BECOME NONE
21039766 FD 12.2.5.1 HIDDEN COLUMNS IN T_SRC_SALES_TMPL
21320395 FD 12.2.5.1 RETURN ENGINE LOG SHOWS ERRORS
21256417 FD 12.2.5.1: EXCEL IMPORT RESULTS IN AN ERROR WHEN SITE OF THE SAME
NAME EXISTS
21311740 FD 12.2.5.1 PRELOGON PROCEDURE ERROR OUT
20910554 FD - 12.2.5.1 - ADDING A LARGE ATTACHMENT TO A NOTE DOESN'T GIVE ERROR
WHEN MEMO
19976571 FD 12.2.5.1 - BUG 19880404 - (ENGLISH)PERFORMANCE ISSUE OF EXCEL IMPORT
FUNCTION
19974717 FD 12.2.5.1 - LEVEL METHOD ANIMATION NOT WORKING IN 12.2.4
20074471 FD 12.2.5.1 - BUG 19942207 - DEMANTRA WORKSHEET NOT SHOWING GRAPH WHEN
SERIES AD
20085877 FD 12.2.5.1 - (ENGLISH)WHEN SETTING TIME BUCKET TO DAY,WE CAN'T EDIT
SERIES ON W
20221585 FD 12.2.5.1 DATA_CLEANUP PACKAGE IS DROPPING SIMULATION_SETTING TABLE
20542921 FD - 12.2.5.1 - BUSINESS MODELER NOT RUNNING FROM THE COLLABORATOR
WORKBENCH MEN
20759530 FD 12.2.5.1 - CURSOR LOCATION IN A DEMANTRA WORKSHEET JUMPS TO THE
START AFTER M
20642569 FD 12.2.5.1 - BUG 20613106 - WEBSERVER DOES NOT START IF LANGUAGE IS
CHINESE
20783151 FD 12.2.5.1 - WORKSHEET TAB LOCKS OR FREEZES FOR SWITCHED BETWEEN TABS,
EDITED A
20689948 FD 12.2.5.1 - BUG 20642553 - ERROR OF REGISTING TRANSLATION DATA BY
TRANSLATION
18083198 FD 12.2.4 - 'METHOD' OPTIONS ARE GRAYED OUT IN DEMANTRA WORKSHEET
21107762 FD 12.2.5.1 DB PROC FIX FOR BASE BUG 20971011
21048325 FD 12.2.5.1 SUPERUSER IS NOT ADDED AS EXPECTED
21337177 FD 12.2.5.1 COMPUTE_STD_ERR PROCEDURE: ORA-20002: -904 ORA-00904:
ERRORS
21251591 FD 12.2.5.1: DYNAMIC PROCEDURE CREATED IN PROPORT EXECUTION HAS SYNTAX
ERROR
19937186 FD:12.2.4 BATCH ENGINE ON LINUX FAILS AT LAST BRANCH
19763275 FD 12.2.5 REFRESH DIMENSION PARENT LEVEL ID VALUES
20025703 FD 12.2.5.1 SPF : APPPROC_CALC_ACCURACY FAILS WITH ORA-06502
20191787 FD 12.2.5.1 INSERT VALUES (SALES) NOT WORKING IN MEMBER MANAGEMENT
20039740 FD 12.2.5.1 CHAINING MANAGEMENT DO NOT RESPECT CALENDAR MONTH
FUNCTIONALITY
20091221 FD12.2.5.1: AFDM ANALYTICS WORKSHEET ONLY SHOWS BASE SETTINGS AS
DEFAULT NOT BAT
20142279 FD 12.2.5.1: USER UPDATE THROUGH API IS FAILING
20157985 FD 12.2.5.1 - BUG 18747344 - WORKSHEET FAILS TO EXPORT TO EXCEL
20043748 FD 12.2.5.1 UNIQUE CONSTRAINT ERROR WHILE RUNNING EP_LOAD_ITEMS AND
EP_LOAD_LOCA
20000917 FD 12.2.5.1 EP_LOAD_LOCATIONS ITEMS MAY FAIL DUE TO LONG DESCRIPTIVE
DATA
20401418 FD 12.2.5 CDP - SET BASED EP_LOAD_LOCATIONS ORA-12838
20260614 FD 12.2.5.1 - ESC-WS ERR -- ODPM-10334: FAILED TO EXECUTE REQUEST:
HTTP/1.1 500
20442824 FD - 12.2.5.1 - CANNOT RUN BATCH ENGINE USING SEEDED 'RUNENGINE'
WORKFLOW.
20122008 FD 12.2.5.1 GLOB_PROP , P1 TO P12 IS NOT RESET TO 0 WHEN BELOW
HIST_GLOB_PROP
19928520 FD 12.2.5.1 - CONSENSUS FORECAS NOT RETAINING WEIGHTED FORECAST
OVERRIDE SERIES
19893113 FD 12.2.5.1 - ORA-02291: INTEGRITY CONSTRAINT
(TPM.LIST_OF_NOTE_ATTACH_1_FK) VIO
21156001 FD: ISSUE WITH GL SYNCH
21362777 FD BUG 12.2.5.1 : DSM LINKING ISSUE IN 12.2.4.1
20442852 FD 12.2.5.1 - CREATE PROMOTION CREATES RECORDS PRIOR TO START SHIP IN
PROMOTION_
20189553 FD 12.2.5.1 TABLE_REORG - PROBLEMS IN THE CHECK TABLE SPACE
21284545 FD - 12.2.5.1 - ORA-00904: "LOCATION"."T_EP_XX_MARKET_EP_ID": INVALID
IDENTIFIER
20389762 FD 12.2.5.1 - RIGHT CLICK MENU SHRINKS AND BECOMES UNREADABLE
20391005 FD 12.2.5.1 - 12.2.4.1. USER ACCESS CONTROL NOT LOCKING USERS FROM
LOGIN /
19900448 FD 12.2.5.1 - UNSUPPORTED JAVA VERSION ERROR FOR JDK 1.8 FOR ENGINE
CONFIGURATIO
21227813 FD - 12.2.5.1 - ADDING ATTACHMENT ENCOUNTER 'CLOSED LOB' EXCEPTION