Friday Dec 20, 2013

Demantra Platform or Application Upgrading - Program Manager Recommendations

Hello Demantra Customers!  Are you planning on an upgrade?  Should you follow a platform or application upgrade path?  MyOracleSupport (MOS) Note 1609763.1 delivers high impact information from the Demantra Program Management Office (PMO).  Take a look, it will help you make an informed decision for your upgrade path.    Regards!   Jeff

Monday Dec 16, 2013

Demantra 12.2.3 Is Now Available!

Greetings!   Demantra 12.2.3 is now available via ARU 17048199, Bug 17921238

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, 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."

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.

4. Customers who are on or later who are using In-Memory Consumption Driven Planning (CDP) cannot upgrade to 12.2.3, as 12.2.3 does not support those enhancements.

A future release of the 12.2.x branch will include the CDP enhancements, and upgrading from or later will be supported at that time. Please contact Oracle Support for additional information.

For known issues and work arounds, see MOS note Demantra 12.2.3 Upgrade / Install Known Issues and Workarounds (Doc ID 1608474.1)

Wednesday Dec 04, 2013

Do you want to Review Demantra Patches Released in Real Time?

Hello Demantra Customers!   If you want to view a list of Demantra patches released in real time, review MOS note 1400207.2.   In the upper left you will see 'Real Time List of Released Patches'.  Regards!   Jeff

Tuesday Dec 03, 2013

Demantra Integration Interface Modifications via the Database

How does one do modifications to the Integration Interface from the database?  Is there a java class that can be used for this?

Looking to avoid logging into the Business Modeller to perform these modifications?

1) The interface tables in the database are a set of tables starting with "Transfer_", while transfer_query is the main one. There are separate tables for series, levels, filter etc.

2) I do not believe there is a Java class for this.

3) A Java servelet is triggered when an Integration interface is modified through business modeler so that an application server bounce is not required. This servelet is specific to integration interfaces only.

4) Any update to the "transfer_xxx" table(s) would need application server bounce.

As per my knowledge, logging into Business modeler and modifying is the recommended option, mainly where multiple tables in the database get updated.

Upgrading to 12.2.2? Do you want extra speed? Use a logon trigger for parallelism

When upgrading your Demantra application from an older version directly to 12.2.2, you can minimize the upgrade time.  You can force parallelism using a Logon trigger on the server.

   Creation of new Indexes on sales data can take long time.

   As part of the upgrade there is a script building a new set of indexes, one per engine profile, on each profile quantity_form expression.

   The creation of the index can take a long time on big data tables.

    - Remember to disable or drop that trigger when the upgrade has completed.

   The following trigger was created as SYS database user and tested successfully by creating DEMANTRA database user and logging in with it:

 CREATE OR REPLACE TRIGGER force_parallel_ddl_trg






END force_parallel_ddl_trg;


 Make sure to:

  1. Modify DEMANTRA to be the database schema name.
  2. drop it after it is not needed anymore using the foillowing:

 DROP TRIGGER force_parallel_ddl_trg;


This blog delivers the latest information regarding performance and install/upgrade. Comments welcome


« December 2013 »