demand_mm_integration.pdf

Integration Guide JDA® Market Manager JDA® Demand Last updated: 8 April 2014

JDA Software Group, Inc.

Legal notice Rights to the content of this document

Copyright © 2009-2014 JDA Software Group, Inc. All rights reserved.

Printed in the United States of America.

Reproduction of this document or any portion of it, in any form, without the express written consent of JDA Software Group, Inc. ("JDA") is prohibited.

These materials are protected by the Copyright Act of 1976, as amended, as an unpublished work and the foregoing notice and legend shall not be deemed to constitute publication or an intent to publish thereunder. These materials are proprietary and confidential information of JDA and may be disclosed and used only as authorized in a signed, written agreement controlling such disclosure or use.

The fact that a particular name or logo does not appear on this notice does not constitute a waiver of any intellectual property rights that JDA has established in any of its products, feature or service names, or logos.

Modifications to the contents of this document

JDA reserves the right, at any time and without notice, to change these materials or any of the functions, features, and specifications of any of the software described herein. JDA shall have no warranty obligation with respect to these materials of the software described herein, except as provided in the JDA software license agreement with an authorized licensee.

Rights to the functionality of this document

Described functionality may not be available as part of a customer's maintenance agreement or the JDA Investment Protection Program. New features and products are subject to license fees. JDA warranty and support obligations apply only to the documentation as delivered by JDA, and are void if the documentation is modified or supplemented by anyone other than JDA. This document embodies JDA valuable trade secrets, is confidential to JDA, and must be kept in confidence and returned upon the expiration or termination of your JDA license agreement. You are not permitted to copy, extract, distribute, transfer, or share the contents of this document with anyone except authorized individuals within your organization.

Technical documentation

NOTICE: This design or technical documentation is supplied as a courtesy only and does not form part of the "Documentation" as defined in your JDA license agreement. This design or technical documentation is supplied in the English language only and is supplied "as is" and without warranties. JDA, at its discretion, may choose to offer this document in additional languages, but is under no obligation to do so. JDA undertakes no obligation to update this design or technical documentation.

Patents

This product may be protected by one or more US patents. Please see the JDA Patents website (http://jda.com/JDAPatents).

This product may be protected by one or more of the following non-US patents:

Europe Patent No. 0861474 (E) Taiwan Patent No. 161120 Taiwan Patent No. I222584 Europe Patent No. 0861474 (UK) Taiwan Patent No. 161181 Taiwan Patent No. I222585 German Patent No. 10195871 Taiwan Patent No. 161494 Taiwan Patent No. I222586 German Patent No. 69507020.7 Taiwan Patent No. 163816 Taiwan Patent No. I225208 German Patent No. 69507021 Taiwan Patent No. 164194 Taiwan Patent No. I225209 German Patent No. 69508931.5 Taiwan Patent No. 170630 Taiwan Patent No. I225605 German Patent No. 69508932 Taiwan Patent No. 172458 Taiwan Patent No. I227425 German Patent No. 69601151 Taiwan Patent No. 191262 Taiwan Patent No. I227427 German Patent No. 69601151.4 Taiwan Patent No. 196235 Taiwan Patent No. I231432 German Patent No. 69601152 Taiwan Patent No. 199069 Taiwan Patent No. I234724 German Patent No. 69601152.2 Taiwan Patent No. 200370 Taiwan Patent No. I235318 German Patent No. 69601207 Taiwan Patent No. 205817 Taiwan Patent No. I238957 German Patent No. 69601207.3 Taiwan Patent No. 283220 Taiwan Patent No. I239461

http://jda.com/JDAPatents


German Patent No. 69601208.1 Taiwan Patent No. 371338 Taiwan Patent No. I241800 German Patent No. DE10195968 Taiwan Patent No. 384430 Taiwan Patent No. I242952 Taiwan Patent No. 100569 Taiwan Patent No. 425517 Taiwan Patent No. I251760 Taiwan Patent No. 108409 Taiwan Patent No. 435034 Taiwan Patent No. I251996 Taiwan Patent No. 110827 Taiwan Patent No. 440780 Taiwan Patent No. I258090 Taiwan Patent No. 113331 Taiwan Patent No. 451145 Taiwan Patent No. I266251 Taiwan Patent No. 122508 Taiwan Patent No. 469405 Taiwan Patent No. I271617 Taiwan Patent No. 127358 Taiwan Patent No. 490625 Taiwan Patent No. I284847 Taiwan Patent No. 129860 Taiwan Patent No. 493122 Taiwan Patent No. I285339 Taiwan Patent No. 133048 Taiwan Patent No. 498236 Taiwan Patent No. I285342 Taiwan Patent No. 134299 Taiwan Patent No. 498247 Taiwan Patent No. I286709 Taiwan Patent No. 136847 Taiwan Patent No. 502183 Taiwan Patent No. I290290 Taiwan Patent No. 137376 Taiwan Patent No. 504640 Taiwan Patent No. I299837 Taiwan Patent No. 139353 Taiwan Patent No. 504915 Taiwan Patent No. I314297 Taiwan Patent No. 139680 Taiwan Patent No. 509869 Taiwan Patent No. I314298 Taiwan Patent No. 140308 Taiwan Patent No. 517193 Taiwan Patent No. I317103 Taiwan Patent No. 146038 Taiwan Patent No. 544598 Taiwan Patent No. M377652 Taiwan Patent No. 154327 Taiwan Patent No. 544599 Taiwan Patent No. NI-158220 Taiwan Patent No. 154338 Taiwan Patent No. 561424 Taiwan Patent No. NI-162685 Taiwan Patent No. 154339 Taiwan Patent No. 594530 Taiwan Patent No. NI-166322 Taiwan Patent No. 155489 Taiwan Patent No. 80326 Taiwan Patent No. NI-167148 Taiwan Patent No. 155708 Taiwan Patent No. 93090 Taiwan Patent No. NI-182787 Taiwan Patent No. 157467 Taiwan Patent No. I221578 Taiwan Patent No. NI-182974 Taiwan Patent No. 159609 Taiwan Patent No. I221978


Provide feedback on this document JDA values your opinion and strives to ensure that the documentation you receive is clear, concise, and provides the appropriate information required for you to use each JDA application efficiently.

If you would like to provide feedback on this document, you can submit your questions or suggestions to the JDA Documentation Management team (mailto:[email protected]) and they will be forwarded to the appropriate development teams for review and consideration in a future release.

mailto:[email protected]


Table of Contents Chapter 1. Introduction ................................................................................................... 1

Integrate Demand and Market Manager .......................................................................... 1 Integration overview ........................................................................................... 1

Chapter 2. Pre-integration steps ..................................................................................... 3

Chapter 3. Post-integration steps .................................................................................... 4

Chapter 4. Integrate Demand and Market Manager - new installation ............................. 5

Chapter 5. Market Manager limitation ............................................................................. 9

Chapter 6. Disable CDS support in Market Manager ....................................................... 10

Chapter 7. Integrate Demand and Market Manager - with data ..................................... 11

Chapter 8. Demand Market Manager Integration Migration ........................................... 15 Pre-migration steps ................................................................................................... 15 Migrate from 7.1 to 7.2 .............................................................................................. 16 Migrate from 7.2 to 7.2.1 ........................................................................................... 16 Migrate from 7.2.1/7.2.2 to 7.3/7.3.0.1 ....................................................................... 16 Migrate from 7.3.0.1 to 7.4.0.0 ................................................................................... 17 Migrate from 7.4.2.0 or later to 8.1.0.0 ........................................................................ 17

Chapter 9. Configure a complex setup ........................................................................... 19

Chapter 10. Remove old data from the SCPO schema .................................................... 20

Chapter 11. Change data sources for Demand-Market Manager integration .................. 21 Change from FCST to FCSTDRAFT ................................................................................ 21 Change from FCSTDRAFT to FCST ................................................................................ 23

Chapter 12. Synchronizing Market Manager Calendar with Demand .............................. 26

Chapter 13. Use Impact of Lock adjustment and market activity synchronization ......... 27 About Impact of Lock ................................................................................................. 27 Synchronize approved market activities with Demand .................................................... 27 Refresh Market Activity process ................................................................................... 27 Roll Forecast process ................................................................................................. 27 Use an additional SRE processes .................................................................................. 28 Market Manager and Demand integration system properties ........................................... 28

Valid Values for DEMAND_PERIODICITY and DEMAND_BOP .................................... 29 Rules on Impact of Lock adjustment and synchronizing market activities ................. 30 Display Impact of Lock in the worksheet .............................................................. 31 Impact of Lock and Market Activity Administration ................................................ 31 Usage of Refresh Market Activity SRE process ...................................................... 31 Usage of Roll Forecast SRE Process ..................................................................... 32


Additional rules for the Market Manager batch process ................................................... 34 JDA Market Manager data reference ............................................................................. 34

Introduction

Chapter 1. Introduction This document contains instructions to integrate JDA Market Manager version 8.1.0.0 with JDA Demand version 8.1.0.0 on the server. Market Manager provides Promotion Management support for the Demand Forecast process. You must install both applications before integrating them. For assistance in using the applications, select Help in Demand or Market Manager.

Integrate Demand and Market Manager Before trying to integrate Demand and Market Manager, you must have working knowledge of Oracle, SQL*Plus, database links, and synonyms. You should also be familiar with the SCPO schema and the Collaborative Services database schemas. Demand uses the SCPO schema and Market Manager the Collaborative Services schema.

Note: The schemas must be in the same Oracle SID and owned by different Oracle users.

Integration overview The integration configures the SCPO schema used by Demand and the Collaborative Services database used by Market Manager. Part of the integration includes data synchronization. Once synchronized, use Market Manager to manage promotion activities for Demand. Subsequent data synchronization between Demand and Market Manager occurs through direct database access.

For more information on this integration, See Demand - Market Manager Appendix in JDA Market Manager Installation/ Administration guide.

Summary of data and terms Market Manager relies on Demand data. The SCPO schema is the origin for Demand Forecast Units (DFUs). A DFU is a forecast for an item. If a DFU has an event associated with it, the initial data synchronization loads the DFU data into the Collaborative Services database. The following list contains the DFU attributes, followed by their equivalent Market Manager attribute. For a more detailed description of the data mappings, see Market Manager data mappings (on page 34).

• DFU.DMDUNIT

PRODUCT.NAME

• DFU.DMDGROUP

PLANNING_ITEM.DMDGROUP

• DFU.LOC

LOCATION.NAME

• DFU.MODEL

PLANNING_ITEM.DMDMODEL

JDA Market Manager - JDA Demand Integration Guide 1 © 2009-2014 JDA Software Group, Inc.- Confidential

Introduction

Each DFU has a Forecast Type associated with it. During the initial data synchronization, several DFU Types are loaded into the Collaborative Services database. In Market Manager, the DFUs are displayed as planning items. Using Market Manager, users create market activities, and market activity data is stored as Type 7 in the SCPO schema and Collaborative Services databases.


Pre-integration steps

Chapter 2. Pre-integration steps Before integrating Demand and Market Manager, you must install both applications and configure the databases.

1. Install WebLogic or WebSphere and JDA Platform version 8.1.0.0, and configure the Platform schema.

2. Install Demand version 8.1.0.0, and create or migrate the SCPO database to version 8.1.0.0.

Note: The SCPO schema and Collaborative Services database schemas must be in the same Oracle SID and owned by different Oracle users. Both Demand and Market Manager must use the same Platform database schema.

3. Install Market Manager version 8.1.0.0.

4. Create or migrate the Collaborative Services database to version 8.1.0.0. The scripts to create or migrate the database are available in the installed directory structure; for example, <install_dir>\config\database\collabsvcs\.

In the Collaborative Services database schema, verify that the PLANNING_ITEM table does not have the following user-defined columns:

• DMDGROUP

• DMDMODEL

The synchronization process creates the DMDGROUP and DMDMODEL columns in the PLANNING_ITEM table. For detailed instructions, see "Create the Collaborative Services Database Schema" and "Migrate the Collaborative Services Database".

Note: If you are upgrading and you previously integrated Demand and Market Manager, it is normal for the columns to be present on PLANNING_ITEM.

5. Enable java stored procedures on Oracle and load java classes. Use Oracle utilities. For detailed instructions, see "Implementing in-database JVM" in the JDA Market Manager Installation/ Administration guide.

6. Back up the SCPO and Collaborative Services databases before continuing.

7. Integrate Demand and Market Manager using scripts provided and instructions in this appendix. Begin based on one of the following configurations:

• If Demand 8.1.0.0 and Market Manager 8.1.0.0 are new installations with no forecast data. See Integrate Demand and Market Manager - new installation" (on page 5)

• If Demand was migrated to 8.1.0.0 and has forecast data but Market Manager 8.1.0.0 is new and does not have data. See Integrate Demand and Market Manager - with data (on page 11)

• If Demand and Market Manager were integrated successfully and forecast data was synchronized in a previous version, run Pre-migration steps (on page 15) and proceed to the migration from an existing version.


Post-integration steps

Chapter 3. Post-integration steps After integration is done and once you restart the the JDA Platform server, Navigate to JDA Demand and configure the system properties with one of the following data sources that the JDA Market Manager is integrated with.

NONE: Market Manager is not integrated with demand (Default value)

FCST: Market Manager is integrated with Demand and FCST table will be used to store type 7 records generated by Market Manager. Market Activity links will be enabled in Published mode of Demand Workbench in order to navigate from Demand Workbench to Market Manager Worksheet to view/edit that particular Market Activity.

FCSTDRAFT: Market Manager is integrated with Demand and FCSTDRAFT table will be used to store type 7 records generated by Market Manager. Market Activity links will be enabled in Draft mode of Demand Workbench in order to navigate from Demand Workbench to Market Manager Worksheet to view/edit that particular Market Activity.


Integrate Demand and Market Manager - new installation

Chapter 4. Integrate Demand and Market Manager - new installation Use these instructions if Demand and Market Manager are new installations and you have no data to synchronize. The examples use default schema names. Substitute them with your actual schema names, as needed. Note that the scripts contain database user names entered during installation.

1. Back up your database.

2. Run the following scripts, in the specified order, using SQL*Plus.

Step Script Run as schema owner

Description

1 demand_common_integration.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to integrate Market Manager with Demand. Run this script as CollabSvcs schema. For Example:

sqlplus nwmgr/nwmgr @demand_common_integration.sql FCST/FCSTDRAFT

Where nwmgr schema owns the CollabSvcs schema and FCST/FCSTDRAFT is the table that you want to integrate with SCPO schema.

This script alters planning_item table with DMDGROUP and DMDMODEL columns and resources related to CollabSvcs schema.

Note: This script must be run only once if you are integrating Collaborate and MarketManager with Demand.

2 wwf_demand_common_integration.sql Platform (wwfmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this the script as Platform schema owner. For example:

sqlplus <wwfmgr>/<wwfmgr> @ wwf_demand_common_integration.sql nwmgr scpomgr

Where nwmgr owns the CollabSvcs schema and scpomgr owns the SCPO schema.

This script creates resources and metadata in the Platform schema.





Description

3 enable_demand_integration_cds_support.sql Platform (wwfmgr)

In directory

<install_dir>\config\database\collabsvcs\scripts, run this script to enable CDS for Market Manager, when integrated with CDS enabled Demand.For example:

sqlplus <wwfuser>/<wwfpassword> @enable_demand_integration_cds_support.sql <Collabsvcs schema name>


4 demand_database_synonyms.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to create database synonyms to the SCPO schema. Run this script as the CollabSvcs schema owner. For example:

sqlplus nwmgr/nwmgr @demand_database_synonyms.sql <scpomgr>

Where scpomgr owns the SCPO schema.

This script creates synonyms to the following SCPO tables: EVENT, EVENTTYPE, SUBEVENT, PROFILE, PROFILEDATA, and FCST or FCSTDRAFT.

Note: If CDS enabled, This script creates synonyms to the following SCPO tables: EVENT, EVENTTYPE, SUBEVENT, PROFILE, PROFILEDATA, FCSTNARROW, FCSTDRAFTNARROW, and CALDATAEXPANDED.


5 grant_demand_table_privileges.sql SCPO (scpomgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script as the SCPO schema owner to grant privileges to the CollabSvcs schema owner. Run this script as the SCPO schema owner. For example:

sqlplus <scpouser>/<scpo/password> @grant_demand_table_privileges.sql <Collabsvcs schema name>





Description

6 create_triggers_common.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to create triggers to the CELL and its corresponding tables in the CollabSvcs schema. Run this script as the CollabSvcs schema owner. For example:

sqlplus nwmgr/nwmgr @create_triggers_common.sql

7 demand_mkm_integration.sql CollavSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to add system properties related to MarketManager Demand integration. Run this script as CollabSvcs schema owner. For Example:

sqlplus nwmgr/nwmgr @demand_mkm_integration.sql

8 wwf_demand_mkm_integration.sql Platform (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script as Platform schema owner. For Example:

sqlplus wwfmgr/wwfmgr @ wwf_demand_mkm_integration.sql

Where wwfmgr owns the JDA Platform schema.

This script enables SRE processes configuration in Platform schema.

9 create_triggers_mm.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to create triggers to the CELL , PROMOTION and its corresponding tables in the CollabSvcs schema. Run this script script as CollabSvcs schema owner. For Example:

sqlplus nwmgr/nwmgr @create_triggers_mm.sql




Description

10 load_translated_metadata Platform(wwfmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this batch (Windows) or shell (UNIX) script as the Platform database userand with option common. For example:

Windows:

load_translated_metadata wwfmgr wwfmgr tnsname demand_mm

UNIX:

load_translated_metadata.ksh wwfmgr wwfmgr tnsname demand_mm

This script loads translated metadata for Collaborate translated table and column names in the Platform schema. You must have SQL*Loader available in order to run this script.

3. Start the JDA Platform server.

To configure a system property in JDA Demand, see Post-Integration steps (on page 4).

For information on limitations when CDS is enabled, refer to Market Manager Limitation (on page 9).


Market Manager limitation

Chapter 5. Market Manager limitation When CDS is enabled in JDA Market Manager, the Expand calendar process in JDA Demand must be run before viewing forecast data on worksheet. This process populates the expanded calendar table with the start date, and duration for the periods in the given date range. This is required for JDA Market Manager to understand the specific start dates associated with the calendar buckets.


Disable CDS support in Market Manager

Chapter 6. Disable CDS support in Market Manager if CDS is disabled in JDA Demand, run the following scripts to also disable CDS integration in JDA Market Manager:




Description

1 disable_demand_integration_cds_support.sql Platform (wwfmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to disable CDS for Market Manager, when integrated with CDS enabled Demand.

For example:

sqlplus <wwfuser>/<wwfpassword> @disable_demand_integration_cds_support.sql <Collabsvcs schema name>



sqlplus nwmgr/nwmgr @demand_database_synonyms.sql <1> <2>

where the value for 1 is the Oracle schema owner for the SCPO schema, the value for 2 is the password of the SCPO schema owner.





3. Start the JDA Platform server.


Integrate Demand and Market Manager - with data

Chapter 7. Integrate Demand and Market Manager - with data Use these instructions if Market Manager is a new installation and Demand has forecast data to synchronize. The examples use default schema names. Substitute the names with your actual schema names, as needed.



Step Script Run as schema owner Description

1 demand_common_integration.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to integrate Market Manager with Demand. Run this script as CollabSvcs schema. For Example:

sqlplus nwmgr/nwmgr @demand_common_integration.sql FCST/FCSTDRAFT

where nwmgr schema owns the CollabSvcs schema and FCST/FCSTDRAFT is the table that you want to integrate with SCPO schema.

This script alters planning_item table with DMDGROUP and DMDMODEL columns and resources related to CollabSvcs schema.

Note: This script must be run only once if you are integrating Collaborate and Market Manager with Demand.

2 wwf_demand_common_integration.sql Platform (wwfmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this the script as Platform schema owner. For example:

sqlplus <wwfmgr>/<wwfmgr> @ wwf_demand_common_integration.sql nwmgr scpomgr

where nwmgr owns the CollabSvcs schema and scpomgr owns the SCPO schema.

This script creates resources and meta data in the Platform schema.

Note: This script must be run only once if you are integrating Collaborate and Market Manager with Demand.




3 enable_demand_integration_cds_support.sql Platform (wwfmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to enable CDS for Market Manager, when integrated with CDS enabled Demand.For example:

sqlplus <wwfuser>/<wwfpassword> @enable_demand_integration_cds_support.sql <Collabsvcs schema name>





where scpomgr owns the SCPO schema.














7 demand_mkm_integration.sql CollavSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to add system properties related to MarketManager Demand integration. Run this script as CollabSvcs schema owner. For Example:

sqlplus nwmgr/nwmgr @demand_mkm_integration.sql

8 wwf_demand_mkm_integration.sql Platform (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script as Platform schema owner. For Example:

sqlplus wwfmgr/wwfmgr @ wwf_demand_mkm_integration.sql

where wwfmgr owns the JDA Platform schema.

This script enables SRE processes configuration in Platform schema.


In directory <install_dir>\config\database\collabsvcs\scripts, run this script to create triggers to the CELL , promotion and its corresponding tables in the CollabSvcs schema. Run this script as the CollabSvcs schema owner. For example:


10 load_translated_metadata Platform(wwfmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this batch (Windows) or shell (UNIX) script as the Platform database userand with option common. For example:

Windows:

load_translated_metadata wwfmgr wwfmgr tnsname demand_mm

UNIX:

load_translated_metadata.ksh wwfmgr wwfmgr tnsname demand_mm

This script loads translated metadata for Collaborate translated table and column names in the Platform schema. You must have SQL*Loader available in order to run this script.




11 migrate_demand_to_marketmanager.sql

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to migrate forecast data to marketmanager. Run this script as CollabSvcs schema owner. For Example:

sqlplus nwmgr/nmmger @ migrate_demand_to_marketmanager.sql

3. Start the JDA Platform Server.

For information on limitations when CDS is enabled, refer to Market Manager Limitation (on page 9).


Demand Market Manager Integration Migration

Chapter 8. Demand Market Manager Integration Migration Follow the instructions in this chapter for Demand Market Manager Integration Migration. These instructions are for Demand and Market Manager integration in versions 7.1 to 7.2, 7.2 to 7.2.1, 7.2.1/7.2.2 to 7.3/7.3.0.1, 7.3.0.1 to 7.4.0.0, and 7.4.x to 7.5.1.0, 7.5.1.0 to 7.5.2.0, 7.5.2.0 to 7.6.0.0, 7.6.0.0 to 7.7.0.0, 7.7.0.0 to 7.7.1.0.,7.7.1.0 to 7.8.0.0 and 7.8.0.0 to 8.1.0.0.

Pre-migration steps Before you migrate the integrated database of Demand and Market Manager to the latest version, run the following scripts:


Description




Where scpomgr owns the SCPO schema.










Migrate from 7.1 to 7.2 Use these instructions if Demand and Market Manager were integrated and forecast data was synchronized. The examples use default schema names. Substitute them with your actual schema names, as needed.


2. Run the following script using SQL*Plus.


Description

1 Migration_Integration71_to_72.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\migration\v71to72, run this script to migrate data in the CollabSvcs schema. Run this script as the CollabSvcs user. For example:

sqlplus nwmgr/nwmgr @Migration_Integration71_to_72.sql

Migrate from 7.2 to 7.2.1 Use these instructions if Demand and Market Manager were integrated and forecast data was synchronized. The examples use default schema names. Substitute them with your actual schema names, as needed.


2. Run the following scripts using SQL*Plus.


Description

1 WWF_Migration_Integration72_to_721.sql Foundation (wwfmgr)

In directory <install_dir>\config\database\collabsvcs\migration\v72to721, run this script to migrate data in the Foundation schema. Run this script as the Foundation user. For example:

sqlplus wwfmgr/wwfmgr @WWF_Migration_Integration72_to_721.sql


In directory <install_dir>\config\database\collabsvcsmigration\v72to721, run this script to migrate data in the CollabSvcs schema. Run this script as the CollabSvcs user. For example:


Migrate from 7.2.1/7.2.2 to 7.3/7.3.0.1 There are no migration steps for the following migration levels:



• 7.2.1 to 7.2.2

• 7.2.2/7.2.3 to 7.3

• 7.3 to 7.3.0.1

Migrate from 7.3.0.1 to 7.4.0.0 Use these instructions if Demand and Market Manager were integrated and forecast data was synchronized. The examples use default schema names. Substitute your actual schema names, as needed.


2. Run the following script using SQL*Plus.


Description


In directory <install_dir>\config\database\collabsvcs\migration\v7301to74, run this script to migrate data in the CollabSvcs schema. Run this script as the CollabSvcs user. For example:


Migrate from 7.4.2.0 or later to 8.1.0.0 Migrate from 7.4.2.0 or later to 8.1.0.0. If your Collaborative Services database is at version 7.4.2 or higher, you can migrate the Platform schema and Monitor Schema (if using) to 8.1 with a single set of scripts.

To migrate a version 7.4.2.0 or higher database:


2. Open a command-line prompt.

3. Change to directory <install_dir>\config\database\collabsvcs\migration and run the pre-migration script as shown below.

Windows:

premigrate_collab.cmd collabtarget_user collabtarget_pwd wwftarget_user wwftarget_pwd [monitortarget_user/NA] [monitortarget_pwd/NA] system_user system_pwd db_hostname db_service db_listner_port [IsRerun_flag]

Unix:

premigrate_collab.sh collabtarget_user collabtarget_pwd wwftarget_user wwftarget_pwd [monitortarget_user/NA] [monitortarget_pwd/NA] system_user system_pwd db_hostname db_service db_listner_port [IsRerun_flag]

If not specified, the db_listener port is assumed to be 1521.

For example:

premigrate_collab nwmgr nwmgr wwfmgr wwfmgr emamgr(NA) emamgr(NA) system manager jdadbserver db_service 1521 JDA Market Manager - JDA Demand Integration Guide 17 © 2009-2014 JDA Software Group, Inc.- Confidential


If not using the default listener port:

premigrate_collab nwmgr nwmgr wwfmgr wwfmgr emamgr(NA) emamgr(NA) system manager jdadbserver db_service 1526

Review the log file premigrate.log. If any errors are reported in the log file, you must fix them before migration and run the premigrate step until it states that the schema can be safely migrated.

After you migrated to 8.1.0.0 and run the IGP steps, start integrating the database to the version 8.1 as follows:

Run integration_migration.cmd to migrate the database to the version 8.1. Verify the log files that are saved in migrate_collab.log, for ORA-errors once it is run.

Windows:

integration_migration.cmd collabtarget_user collabtarget_pwd wwftarget_user wwftarget_pwd

Unix:

integration_migration.sh collabtarget_user collabtarget_pwd wwftarget_user wwftarget_pwd

For example:

integration_migration wwfmgr wwfmgr system manager jdadbserver NWSAMPLE

integration_migration nwmgr nwmgr wwfmgr wwfmgr emamgr(NA) emamgr(NA) system manager jdadbserver db_service 1521

Note: If you do not have the monitor application, run the scripts by replacing emamgr with NA.

Parameters:

<db_hostname>: Name of the machine hosting the oracle service.

<db_service>: Name of the oracle service. In most cases, this is same as the SID name.

<db_listner_port>: The port configured for the oracle listner.


Configure a complex setup

Chapter 9. Configure a complex setup Follow the instructions in this section if you are running Market Manager and Demand on different application servers. This usually means that Market Manager and Demand are installed to different <install_dir> on the same machine or on different machines. In this configuration, you must update the Foundation schema and copy a properties file.


2. For both Demand and Market Manager, update the table CSM_APPLICATION with the following:

• Fully-qualified URL

• Name of the server

• Listen port

• Protocol

Note: Demand and Market Manager must use the same Foundation schema.

3. Use Oracle utilities or SQL*Plus to update the table. To use SQL*Plus, log in to the Foundation schema; for example:

sqlplus wwfmgr/wwfmgr@<NetServiceName>

4. Update Market Manager using the following example. Replace the values in single quotation marks with the values for your environment. Values are case sensitive.

update CSM_APPLICATION set URL=’http://manusrv1:7001’,

SERVER=’manusrv1.company.com’, PORT=’7001’, PROTOCOL=’t3’

where APPLICATION_NAME=’MarketManager’;

5. To update Demand, use the following example. Replace the values in single quotation marks with the values for your environment. Values are case sensitive.

update CSM_APPLICATION set URL=’http://manusrv2:7001’,

SERVER=’manusrv2.company.com’, PORT=’7001’, PROTOCOL=’t3’

where APPLICATION_NAME=’SCPOWeb.Demand’;

6. Commit the database changes.

7. To support Single Sign-On across the servers, set the property sso_cookie_domain in JDA Foundation System Properties. You must restart the server after making the change. For details on the sso_cookie_domain property, select Help in System Properties.

8. Generate a Single Sign-On encryption key. Use the generated key as the value for property encryption.service.key in Foundation System Properties. For details on the encryption.service.key property, select Help in System Properties.

9. On the machine hosting Market Manager, change to directory <install_dir>\config\properties.

10. Copy collabsvcs_config.xml to the machine hosting JDA Demand. Place the copy of the file in directory <install_dir>\config\properties.

11. Restart the JDA Foundation Server instances.


Remove old data from the SCPO schema

Chapter 10. Remove old data from the SCPO schema Follow these instructions after successfully synchronizing Demand and Market Manager data. When migrating the SCPO schema from version 7.0 to 7.1, Type 2 and 5 records are migrated to Type 99. The SQL scripts used in the data synchronization copy Type 99 Forecast records from the 7.2.1 SCPO schema to the Collaborative Services database used by Market Manager. The scripts do not automatically remove Type 99 records from the SCPO schema. If these records remain in the SCPO schema, some JDA Demand processes may complete with errors. Therefore, it is recommended that you remove Type 99 records from the SCPO schema following synchronization.

1. Back up the database.

2. Use Oracle utilities or SQL*Plus to remove the Type 99 Forecast records. Using SQL*Plus, log in to the SCPO schema. For example,

sqlplus scpomgr/<password>@<NetServiceName>

where <password> is the password for the scpomgr user.

3. Remove the records from the table FCST.

delete from FCST where type=’99’;

4. Remove the records from the table FCSTDRAFT.

delete from FCSTDRAFT where type=’99’;

5. Commit the deletions.


Change data sources for Demand-Market Manager integration

Chapter 11. Change data sources for Demand-Market Manager integration This section contains reference information and rules for changing the source of DFUs. The source can be either the FCST or FCSTDRAFT table. During the Market Manager installation, you must select the FCST or FCSTDRAFT table when integrating with Demand. Next, you must synchronize the SCPO schema and Collaborative Services databases based on the initial selection. If you want to change from FCST to FCSTDRAFT, or from FCSTDRAFT to FCST, you must take special steps to resynchronize data.

For example, you successfully integrated JDA Demand and Market Manager using the FCST table, but you want to use FCSTDRAFT table instead. These steps ensure a successful Demand–Market Manager integration.

This section assumes the Demand–Market Manager integration was completed initially with the SCPO and Collaborative Services databases synchronized.

Change from FCST to FCSTDRAFT 1. Stop the JDA Platform Server.

2. Back up the SCPO and Collaborative Services databases.

3. Drop the synonym to the FCST table. Re-create the synonym using the FCSTDRAFT table.


Description

1 change_demand_data_source.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to change the data source , when Market Manager integrated with Demand.Run this script as CollabSvcs owner.For example:

sqlplus nwmgr/nwmgr @change_demand_data_source.sql FCSTDRAFT

To change the property from FCST to FCSTDRAFT in SYSTEM_PROPERTIES table.

2 demand_database_synonyms.sql SCPO (scpomgr)



Where the value for 1 is the Oracle schema owner for the SCPO schema, the value for 2 is the password of the SCPO schema owner.

This script creates synonyms to the following SCPO tables: EVENT, EVENTTYPE, SUBEVENT, PROFILE, PROFILEDATA and FCSTDRAFT.

Note: If CDS enabled, This script creates synonyms to the following SCPO tables: EVENT, EVENTTYPE, SUBEVENT, PROFILE, PROFILEDATA, FCSTDRAFTNARROW, and CALDATAEXPANDED.




Description



sqlplus <scpouser>/<scpopassword> @grant_demand_table_privileges.sql <CollabSvcs schema name>







Note: If CDS enabled, the FCST or FCSTDRAFT source name remains the same but the underlying tables are referred to FCSTNARROW or FCSTDRAFTNARROW.

4. Remove Type 7 Forecast records from the FCSTDRAFT table. If you have not resynchronized data, the table may not contain Type 7 records.

Note: If CDS enabled, remove Type 7 Forecast records from the FCSTDRAFTNARROW table.

5. Synchronize the CELL table in the Collaborative Services schema with the FCSTDRAFT table in the SCPO schema. To accomplish this, use Oracle utilities to copy the Type 7 records from FCST to FCSTDRAFT. The following figure shows both tables and their columns.

Note: If CDS enabled, Synchronize the CELL table in the Collaborative Services schema with the FCSTDRAFTNARROW table in the SCPO schema. To accomplish this, use Oracle utilities to copy the Type 7 records from FCSTNARROW to FCSTDRAFTNARROW.

Demand Classic Model



Demand CDS Model

Change from FCSTDRAFT to FCST 1. Stop the JDA Platform Server.

2. Back up the SCPO and Collaborative Services databases.

3. Drop the synonym to the FCSTDRAFT table. Re-create the synonym using the FCST table.


Description

1 change_demand_data_source.sql CollabSvcs (nwmgr)

In directory <install_dir>\config\database\collabsvcs\scripts, run this script to change the data source , when Market Manager integrated with Demand.Run this script as CollabSvcs owner.For example:

sqlplus nwmgr/nwmgr @change_demand_data_source.sql FCST

To change the property from FCSTDRAFT to FCST in SYSTEM_PROPERTIES table.

2 demand_database_synonyms.sql SCPO (scpomgr)



Where the value for 1 is the Oracle schema owner for the SCPO schema, the value for 2 is the password of the SCPO schema owner.

This script creates synonyms to the following SCPO tables: EVENT, EVENTTYPE, SUBEVENT, PROFILE, PROFILEDATA and FCST.

Note: If CDS enabled, This script creates synonyms to the following SCPO tables: EVENT, EVENTTYPE, SUBEVENT, PROFILE, PROFILEDATA, FCSTNARROW, and CALDATAEXPANDED.




Description



sqlplus <scpouser>/<scpopassword> @grant_demand_table_privileges.sql <Collabsvcs schema name>







Note: If CDS enabled, the FCSTDRAFT or FCST source name remains the same but the underlying tables are referred as FCSTDRAFTNARROW or FCSTNARROW.

4. Remove Type 7 Forecast records from the FCST table. If you have not already resynchronized data, then the FCST table may not contain Type 7 records.

Note: If CDS enabled, remove Type 7 Forecast records from the FCSTNARROW table.

5. Synchronize the CELL table in the Collaborative Services schema with the FCST table in the SCPO schema. To accomplish this, use Oracle utilities to copy Type 7 records from the FCSTDRAFT table to the FCST table. For DFUs that have multiple models in the FCSTDRAFT table, select only one model per DFU. The FCST table permits only one model per DFU. Otherwise, the inserted data violates the constraints in the FCST table. The following figure shows both tables and their columns. Note that column MODEL is a primary key in FCSTDRAFT table but not in the FCST table.

Note: If CDS enabled, Synchronize the CELL table in the Collaborative Services schema with the FCSTNARROW table in the SCPO schema. To accomplish this, use Oracle utilities to copy Type 7 records from the FCSTDRAFTNARROW table to the FCSTNARROW table. For DFUs that have multiple models in the FCSTDRAFTNARROW table, select only one model per DFU. The FCSTNARROW table permits only one model per DFU. Otherwise, the inserted data violates the constraints in the FCSTNARROW table. The following figure shows both tables and their columns. Note that column MODEL is a primary key in FCSTDRAFTNARROW table but not in the FCSTNARROW table.



Demand Classic Model

Figure 1: FCSTDRAFT and FCST Tables

Demand CDS Model

Figure 2: FCSTDRAFTNARROW and FCSTNARROW Tables


Synchronizing Market Manager Calendar with Demand

Chapter 12. Synchronizing Market Manager Calendar with Demand By design any updates that happen to Type-7 and Type-3 components from Market Manager are always treated as 'daily' forecast though the actual forecast in Demand is in Weekly, Monthly, or Quarterly, etc..

To avoid this situation, a setting can be applied to define the calendar to use when synchronizing Market Manager data with Demand. With this setting applied, any updates made to Market Manager will be applied to Demand using that specified calendar rather than the default calendar of "daily".

To enable this calendar synchronization, two properties are available in Market Manager. These properties can be found in the "SYSTEM_PROPERTIES" table:

• DEMAND_PERIODICITY

• DEMAND_BOP

Follow the steps below to synchronize the market activity (Type 7) data in Demand using a specified calendar:

1. Set the appropriate values for DEMAND_PERIODICITY and DEMAND_BOP.

Note: The property values must be in sync with Demand and Market Manager Calendar.

For example: DEMAND_PERIODICITY = 2 DEMAND_BOP = 1

DEMAND_PERIODICITY = 2 represents that the related Demand and Market Manager calendars are in 'WEEKLY'

DEMAND_BOP=1 means that the Beginning Of the Period is 'SUNDAY'.

See "JDA Market Manager and JDA Demand integration system properties" (on page 28)

Caution: Once the above settings are completed and Worksheet cells modified and saved in any calendar other than 'WEEKLY' and the beginning of the period is not 'SUNDAY', it will result in improper Type-7 and Type-3 entries inserted into the FCST/FCSTDRAFT table which can result in ‘database inconsistent’ state.

2. When you start the server and navigate, make sure that 'ignoreDurationCellDurationOnWorksheetSave' property is checked in 'Collabsvcs System Properties.' Navigate to Directory > Administration > System Properties > JDA MarketManager > Worksheet settings. Check the 'ignoreDurationCellDurationOnWorksheetSave' property, for setting the property.

Caution: If the above property is not checked it assumes the calendar as a Daily calendar and it will result in improper Type-7 entries inserted into the FCST/FCSTDRAFT table which can result in ‘database inconsistent’ state.


Use Impact of Lock adjustment and market activity synchronization

Chapter 13. Use Impact of Lock adjustment and market activity synchronization This section provides information on configuring the Impact of Lock adjustment functionality. Before you can use Impact of Lock, you must enable the database server for Java Stored Procedures, configure the service runtime environment, and integrate Demand and Market Manager.

About Impact of Lock Market Manager recognizes Impact of Lock. In Demand, Impact of Lock represents buckets of time that cannot be updated. Any time period that includes a locked bucket is read-only in the Market Manager worksheet. If any part of a calendar bucket is locked, the whole bucket is locked. You cannot make a change to any of the market activities or net forecast, unless property MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK is true. This property and others are discussed later in this section.

When Demand components are shared, Impact of Lock is enforced for both the host and the partners. If a partner does not have access to Demand components and there are shareable market activities, the partner can change the net forecast. To prevent this, you can make the planning component secured. For more information about Impact of Lock, see the Online Help for JDA Demand.

It is possible to add promotional forecast data at the market activity level or net forecast level in Market Manager and change the value of Impact of Lock in Demand. A system-wide property in the system property table, MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK, indicates whether changes to market activity component data affect the value of Impact of Lock in Demand. See "JDA Market Manager system properties" (on page 28).

Synchronize approved market activities with Demand The system can be configured so that only approved market activities are synchronized with Demand. The value for ONLY_SYNC_APPROVED_MARKET_ACTIVITIES in the system property table must be set to true. When true, this functionality supports users who want only approved promotion forecasts in their Demand and Replenishment plans. To set the property, see "JDA Market Manager system properties" (on page 28).

Refresh Market Activity process In this process, the market activity allocated values are refreshed. This process recalculates the forecast allocation of a market activity when the base forecast of a planning item changes. For a given market activity and given calendar period, the base forecast and lift percent of a planning item are considered as input for the calculation. The calculated quantity is allocated to that calendar period.

Roll Forecast process The Roll Forecast process moves Forecast to the future calendar periods when the actuals vary from the forecast. This involves the calculation of forecast error from forecasted quantity, actual sale, and customer orders for a given duration. The calculated forecast error is now rolled to the future calendar periods. Based on your selection, the rolled quantity moves to the following:

• Next calendar period

• Last calendar period

• All the future calendar periods proportionally



Use an additional SRE processes Integrating Market Manager with Demand provides an additional service runtime environment (SRE) process. Before this process can be used, you must prepare the service runtime environment. For details, see Configure SRE Processes.

The MarketManager.SyncMAWithDmd process (Synchronize market activities with Demand) cannot be invoked directly through the user interface or batch. It runs as a background process when needed. By default, it uses the Basic node pool, but you can associate additional pools with the process. The process cannot run unless a node pool is available. Users must have resource Sync_MA_With_Demand assigned to a role to synchronize Market Activities with Demand.

Market Manager and Demand integration system properties Integrating Market Manager with Demand creates additional records in table SYSTEM_PROPERTIES. Each record is a name/value pair described in the following list. You can view and edit the values using Oracle utilities. You should back up the table before making changes. Restart the JDA Platform Server if you change the values.

• MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK: Controls whether market activities affect Impact of Lock values. Set to true or false. When false, the market activity data has no effect on impact of lock values. When true, the system adjusts Impact of Lock values based on market activity data. To support these changes, the system uses an SRE process called MarketManager.IOLAdjustment.

When total market activity is zero, it deletes Impact of Lock data from Demand.

This property was new in 7.2.1 and is valid in later versions. Default value is false.

OVERRIDE_DEMAND_LOCKS: This property is by default false and is available in SYSTEM_PROPERTIES table,only when Collaborate is integrated with Demand.

Controls Collaborate Type 5 and TYPE 6 mapped components affecting Impact Of Lock values.

If Type 5 and Type 6 creates Impact Of Lock values, this will be displayed as Collab IOL component in worksheet.

This property provides similar behavior as MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK. When both Collaborate and Market Manager is integrated with Demand, both of these properties are set as false by default. Both properties cannot be set to true at once.

If MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK is true, Sum of all Market activities in worksheet is NetForecast.

If OVERRIDE_DEMAND_LOCKS is true, Sum of all Collaborate Type 5 and Type 6 components in worksheet is Netforecast.

If MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK and OVERRIDE_DEMAND_LOCKS are set as false, both Market Activities and Collaborate Type 5 and Type 6 mapped components values are incremental to the Netforecast.

When the total of Type 5 and Type 6 mapped component values are zero, it deletes Collab IOL data from demand.

• ONLY_SYNC_APPROVED_MARKET_ACTIVITIES: Set to true or false. When true, this value enables market activity cell data to update the FCST or FCSTDRAFT table, depending on the table selected for the integration. To support these changes, the system uses an SRE process called MarketManager.SyncMAWithDmd.

Note: All market activities that are not approved must be removed from the FCST or FCSTDRAFT table in JDA Demand before setting this property to true.

This property is new in 7.2.1 and is valid in later versions. Default value is false.



• IOLADJUSTMENT_SERVICE_NAME: Default value is MarketManager.IOLAdjustment. This is the service name loaded into SRE_SERVICE_INFO during database creation or migration. You should not change this value, unless you rename the service. Generally, it is not necessary to change service names.

Note that this service cannot run unless ONLY_SYNC_APPROVED_MARKET_ACTIVITIES is true.

• IOLADJUSTMENT_NODE_CONFIG_NAME: The node configuration record that the IOLAdjustment process uses when running. Default value is IOLAdjustment Node Config. You can create additional node configuration records in table SRE_NODE_CONFIG.

• SYNC_MA_WITH_DMD_SERVICE_NAME: Default value is MarketManager.SyncMAWithDmd. This is the default service name loaded into SRE_SERVICE_INFO during database creation or migration. You should not change this value, unless you rename the service.

Note that this process cannot run unless MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK is true.

• SYNC_MA_WITH_DMD_NODE_CONFIG_NAME: The node configuration record that the SyncMAWithDmd process uses when running. Default value is SyncMAWithDmd Node Config. You can create additional node configuration records in table SRE_NODE_CONFIG.

• HOST_ENTERPRISE_USER: The user name required to run IOLAdjustment and SyncMAWithDmd. Generally, you should not change this unless you want to use a different user. The user must belong to the host enterprise and have access to all data. For example, planning item or market activity filters should not restrict this user's access to data.

• DEMAND_PERIODICITY: Represents the time period. Default value for this property is -1. See "Valid values for System_properties (on page 29)" to set the appropriate value to this property. For example, DEMAND_PERIODICITY=2 represents that the related Demand and Market Manager calendars are in 'WEEKLY'.

• DEMAND_BOP: Represents the beginning of a time period. Default value for this property is -1. See "Valid values for System_properties (on page 29)" to set the appropriate value to this property. For example,DEMAND_BOP=1 means that the Beginning Of the Period is 'SUNDAY'

Valid Values for DEMAND_PERIODICITY and DEMAND_BOP Below is the list of valid values corresponding to different calendars that need to be set in SYSTEM_PROPERTIES table:

Calendar DEMAND_PERIODICITY

DEMAND_BOP

DAILY 1 -1 (not applicable) WEEKLY 2 (Enter 1 if week starts with Sunday, 2 for Monday and so

on) 1 - Sunday 2 - Monday 3 - Tuesday 4 - Wednesday 5 - Thursday 6 - Friday 7 - Saturday

MONTHLY 3 -1 (not applicable)



Calendar DEMAND_PERIODICITY

DEMAND_BOP

QUARTERLY 4 Enter 1 if quarter starts with January, 2 if February and so on) 1 - January 2 - February 3 - March 4 - April 5 - May 6 - June 7 - July 8 - August 9 - September 10 - October 11 - November 12 - December

YEARLY 5 (Enter 1 if year starts with January, 2 if February and so on) 1 - January 2 - February 3 - March 4 - April 5 - May 6 - June 7 - July 8 - August 9 - September 10 - October 11 - November 12 - December

4-4-5 Not Supported

Rules on Impact of Lock adjustment and synchronizing market activities Observe the following rules when you use Impact of Lock.

• When ONLY_SYNC_APPROVED_MARKET_ACTIVITIES is true, market activities are not pushed to Demand until they are approved.

• When MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK is true, the following events can cause adjustments to Impact of Lock values:

• Market Manager worksheet (changing market activity data)

• IGP (importing market activity data)

• NWImport (market activity data)

• Component Data Synchronization



• Market Activity Administration (dissociate planning items from market activities or deleting market activities). For example, a user deletes or unassigns planning items from one or more activities, a product or location is deleted, or a market activity is deleted.

• If MARKET_ACTIVITY_CREATE_IMPACT_OF_LOCK is true and ONLY_SYNC_APPROVED_MARKET_ACTIVITIES is false, then all market activities of the host enterprise may cause adjustments to Impact of Lock values in Demand.

• If MARKET_ACTIVITY_CREATE_IMPACT_OF_LOCK is true and ONLY_SYNC_APPROVED_MARKET_ACTIVITIES is true, then only approved market activities of the host enterprise may cause adjustments to Impact of Lock values in Demand.

• When ONLY_SYNC_APPROVED_MARKET_ACTIVITIES is true, the following activities can cause synchronization to occur:

• Market Activity Approval process

• Activity Manager (approving market activities)

• IGP (changing market activity to approved)

• NWImport (approving market activities)

Display Impact of Lock in the worksheet When MARKET_ACTIVITY_CREATE_IMPACT_OF_LOCK and ONLY_SYNC_APPROVED_MARKET_ACTIVITIES are true, observe the following:

• Users should not change Impact of Lock values in Demand, because this affects the display in Market Manager worksheet. The worksheet displays what appears to be an illogical calculation.

• The worksheet always displays the Impact of Lock value from Demand.

• Impact of Lock values should only be removed from Demand. Use Demand to remove the values.

• The Net Forecast equals the sum of base forecast, other forecast, Impact of Lock, and approved market activities.

Impact of Lock and Market Activity Administration Deleting market activities or dissociates planning items from a market activity can cause Impact of Lock adjustments. The adjustments depend on values for MARKET_ACTIVITY_CREATES_IMPACT_OF_LOCK and ONLY_SYNC_APPROVED_MARKET_ACTIVITIES. The system determines the periods for which Impact of Lock adjustments must be performed.

Usage of Refresh Market Activity SRE process This SRE process recalculates the market activity forecast allocation when the base forecast of any planning item changes. The Refresh Market Activity process recalculates the allocated forecast value of a market activity for any given calendar period based on the base forecast and lift percent values of a planning item.

New Allocation = (Base Forecast)*(Lift Percent/100)

The Refresh Market Activity process can be invoked in following two ways:

1. Refresh Market Activity process page.

For more information, see the JDA Market Manager OnLine Expert.

2. Batch Process.

Option sets are not required for the process.

Note: Provide the prompted or non-prompted Market Activity search you want to execute.


Example: In the sample request XML file, notice the processName is MarketManager.RefreshMarketActivity and the nodeConfigurationName is the default, Refresh Market Activity Node Config. The sample includes element processOptionOverrides. Because the optionSet element is not declared, the overrides apply to the default option set.

<?xml version="1.0" encoding="UTF-8"?>

<batchJob xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="process_request.xsd">

<processRequest processName="MarketManager.RefreshMarketActivity " nodeConfigurationName="Refresh Market Activity Node Config" >



<searches>



<search searchName="ALL_MA" enterpriseName="JDA" isPublic="false"/>

</searches>





<!-- <searches>

<search enterpriseName="JDA" searchName="ALL_MA_Prompted" isPublic="false">

<prompt schemaName="NWMGR" tableName="Planning_Item" columnName="Planning_Item_Id">

<promptedValue>2300</promptedValue>

</prompt>

</search>

</processRequest>

</batchJob>

Usage of Roll Forecast SRE Process The Roll Forecast process moves the forecast to the future periods when the actuals vary from the forecasts. When this process is invoked for any given duration, the forecast quantity to be rolled is calculated based on the following:

• Net Forecast of the Planning Item

• Actual Sale

• Customer Orders

Given a specific duration, the formula used for calculating the rolled quantity is as follows:

Quantity to be rolled = Net Forecast–(Actual Sale+ Customer Orders)

Note: The Customer Orders value is assumed to be zero for buckets with End Dates before the Process Run Date.

For example, consider that the time periods are 01/01/14, 02/01/14, and 03/01/14, Roll Forecast Start Date is 01/01/04 and Process Run Date is 03/15/14. Since the first two time periods end before the Process Run Date, their Customer Orders value is assumed to be zero.

The periods to which the values are rolled are determined with the Roll Forecast option in the Promotion table.

The available values for the property are as follows:

None: Does not move the Forecast

Next: Moves the difference between forecast and Actual to the next open period.

Last: Moves the difference between forecast and Actual to the Last open period.

Proportionally: Moves the difference between forecast and Actual to the remaining open periods proportionally.

The Roll Forecast process can be invoked in following two ways:

1. Roll Forecast process page

For more information, see the JDA Market Manager OnLine Expert.

2. Batch Process

MarketManager.RollForecast.StartDate: The Date from which the values are to be rolled.

Example 1: In the sample request XML file, notice the processName is MarketManager.RollForecast and the nodeConfigurationName is the default, MarketManager.Roll Fcst Node Config. The sample includes element processOptionOverrides. Because the optionSet element is not declared, the overrides apply to the default option set.

<?xml version="1.0" encoding="UTF-8"?>

<batchJob xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="process_request.xsd">

<processRequest processName="MarketManager.RollForecast " nodeConfigurationName="MarketManager.Roll Fcst Node Config" >

<processOptionOverrides>

<!—Start Date in MM/DD/YYYY format-->

<option name="MarketManager.RollForecast.StartDate"

value="01/01/2014"/>



<searches>



<search searchName="AsynchTestSearch" enterpriseName="JDA" isPublic="false"/>

</searches>



<!-- to use multiple prompt values repeat <promptedValue> tag multiple times and to give multiple criteria repeat <prompt>

tag multiple times -->



</processRequest>

</batchJob>

Additional rules for the Market Manager batch process When Demand and Market Manager are integrated, the SCPO and CollabSvcs databases automatically exchange data. As a consequence, Market Manager batch processing has additional rules.

• Do not import Demand components directly into Market Manager (CollabSvcs database). The SCPO schema is the source for Demand components.

• When importing Type 7 Market Activities for the host enterprise into Market Manager (CollabSvcs database), the established database triggers also write this data to the SCPO schema, specifically the FCST or FCSTDRAFT table. Consider this additional write process when planning Market Activity import, since it could affect performance.

• NWImport and IGP support Impact of Lock adjustments for aggregate and planning item import. Impact of Lock adjustments are made in table FCST or FCSTDRAFT, and can affect performance.

• NWImport and IGP can be used to dissociate planning items from a market activity. This can cause Impact of Lock adjustments where cell data is associated with the unassigned planning items.

JDA Market Manager data reference When you install and integrate Demand and Market Manager, the Market Manager database tables are mapped to data sources. The following table lists the Market Manager tables and columns, and their associated data mappings. For some data, the Market Manager table and column is associated with a Demand table and column. In other cases, Market Manager does not associate with any Demand data. Instead, Market Manager obtains data from another source. This may include a predefined value or automated sequence number. After Demand and Market Manager are integrated, Market Manager writes only Type 7 forecast records to the FCST or FCSTDRAFT table.

Market Manager data mappings

Market Manager table.column associated Demand table.column

other data source

CELL.QUANTITY FCST.QTY or FCSTDRAFT.QTY

n/a

CELL.START_DATE FCST.STARTDATE or FCSTDRAFT.STARTDATE

n/a

CELL.VERSION_ID EVENT n/a

COMPONENT.DEMAND_TYPE n/a null



other data source

COMPONENT.DIV_BY_ZERO_CONST

n/a null

COMPONENT.IS_AVG_OVER_ PLANNING_ITEMS

n/a ’0’

COMPONENT.IS_AVG_OVER_TIME n/a ’0’

COMPONENT.IS_CONVERTED n/a ’1’ COMPONENT.IS_PREDERIVED n/a ’0’ COMPONENT.IS_REVENUE_TYPE n/a ’0’ COMPONENT.IS_WEIGHTED_AVG n/a ’0’ COMPONENT.NUMBER_OF_ VERSIONS

n/a ’1’

COMPONENT.SHAREABLE n/a ’0’

COMPONENT.URL n/a null LOCATION.ENTERPRISE_ID n/a sequence number LOCATION.LOCATION_ID n/a sequence number LOCATION.NAME DFU.LOC n/a PLANNING_ITEM.DMDGROUP (Column created during integration with Demand)

DFU.DMDGROUP n/a

PLANNING_ITEM.DMDMODEL (Column created during integration with Demand)

DFU.MODEL n/a

PLANNING_ITEM.EXTERNAL_ SYSTEM_ID

n/a null

PLANNING_ITEM.FREEZE_PROFILE_ID

n/a null

PLANNING_ITEM.LOCATION_ID DFU.LOC n/a

PLANNING_ITEM.PLANNING_ITEM_ENTERPRISE_ID

n/a host enterprise ID

PLANNING_ITEM.PLANNING_ITEM_ID

n/a sequence number

PLANNING_ITEM.PRODUCT_ID DFU.DMDUNIT n/a

PLANNING_ITEM_PROMOTION.IS_AUTHOR

n/a ’0’ or ’1’

PLANNING_ITEM_PROMOTION. MAPPED_PLANNING_ITEM_ID

n/a PROMOTION.AUTHOR_ENTERPRISE_ID

PLANNING_ITEM_PROMOTION. PLANNING_ITEM_ID

SUBEVENT.DMDUNIT or DMDGROUP or LOC or MODEL

n/a

PLANNING_ITEM_PROMOTION. PLANNING_ITEM_PROMOTION_ID

n/a sequence number




other data source

PLANNING_ITEM_PROMOTION. PROMOTION_ID

SUBEVENT.EVENT n/a

PRODUCT.ENTERPRISE_ID n/a host enterprise ID

PRODUCT.NAME DFU.DMDUNIT n/a PRODUCT.PRODUCT_ID n/a sequence number PROMOTION.APPROVED n/a ’0’ PROMOTION.AUTHOR_ENTERPRISE_ID


PROMOTION.CAMPAIGN n/a null

PROMOTION.DESCRIPTION EVENT.DESCR n/a PROMOTION.DURATION EVENT.DUR n/a PROMOTION.FREEZE_DURATION n/a ’0’ PROMOTION.NAME EVENT.EVENT n/a PROMOTION.PROMOTION_ID n/a sequence number PROMOTION.PROMOTION_TYPE_ID n/a PROMOTION_TYPE.P

ROMOTION_TYPE_ID

PROMOTION.RECIPIENT_ ENTERPRISE_ID


PROMOTION.SHAREABLE n/a ’1’

PROMOTION.START_DATE EVENT.STARTDATE n/a PROMOTION.STATUS_ID n/a PROMOTION_STATUS

.STATUS_ID where STATUS_NAME is ’temporarily assigned’

PROMOTION_PROFILE.DESCRIPTION

PROFILE.DESCR n/a

PROMOTION_PROFILE.ENTERPRISE_ID


PROMOTION_PROFILE.NAME PROFILE.PROFILE n/a

PROMOTION_PROFILE.PROFILE_ID n/a sequence number PROMOTION_PROFILE_PERIOD. PERCENTAGE

PROFILEDATA.FACTOR n/a

PROMOTION_PROFILE_PERIOD. PERIOD

PROFILEDATA.INTNUM n/a

PROMOTION_PROFILE_PERIOD. PROFILE_ID

n/a PROMOTION_PROFILE.PROFILE_ID

PROMOTION_STATUS.AUTHOR_EDIT

n/a ’1’

PROMOTION_STATUS.AUTHOR_ READ

n/a ’1’

PROMOTION_STATUS.RECIPIENT_EDIT

n/a null




other data source

PROMOTION_STATUS.RECIPIENT_READ

n/a null

PROMOTION_STATUS.STATUS_ DESCRIPTION

n/a ’created during Demand to Market Manager migration’

PROMOTION_STATUS.STATUS_ID sequence number

PROMOTION_STATUS.STATUS_ NAME

’temporarily assigned’

PROMOTION_TYPE.COLOR_NAME n/a assigns color for each item because this column has index

PROMOTION_TYPE.DESCRIPTION EVENTTYPE.DESCR n/a PROMOTION_TYPE.NAME EVENTTYPE.EVENTTYPE n/a PROMOTION_TYPE.PROMOTION_ TYPE_ID

n/a sequence number


demand_mm_integration.pdf

Documents

Transcript of demand_mm_integration.pdf