scpo_configuration_guide.pdf

Configuration Guide JDA® Supply Chain Planning and Optimization Release 8.1.0.0

JDA Software Group, Inc.

Legal notice Rights to the content of this document

Copyright © 1997-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. Overview ........................................................................................................ 1

Chapter 2. Configure the SCPO application ...................................................................... 2 Use pre-configured templates to set up the solution ........................................................ 2 Control user access .................................................................................................... 2 Modify system properties ............................................................................................ 2

Modify server and browser properties................................................................... 2 Edit the DBParam table ...................................................................................... 5

Set up calendars ........................................................................................................ 5 Set up Scenarios ....................................................................................................... 6

Identify the discrepancies which will cause the scenarios to fail ................................ 7

Chapter 3. Implement security ........................................................................................ 8 Use the Security module ............................................................................................. 8

Users .............................................................................................................. 8 Roles .............................................................................................................. 8 Resources ........................................................................................................ 8 Filters ........................................................................................................... 34

SCPO security features ............................................................................................. 34 Encrypt the SCPO schema owner's password ............................................................... 39

Chapter 4. Customize and maintain the database .......................................................... 40 Common database tables .......................................................................................... 40 Manage tables and columns ...................................................................................... 40 Administer user-defined tables and user-defined columns .............................................. 40 Maintain existing databases ...................................................................................... 41

Copy databases .............................................................................................. 41 Edit tables and columns ................................................................................... 41 Delete tablespaces .......................................................................................... 41 Back up and restoring databases ....................................................................... 41

Chapter 5. Configure JDA Demand ................................................................................. 42 Set up hierarchies .................................................................................................... 42 Decision Support Workbench ..................................................................................... 42

Customize the Demand DSW ............................................................................ 42 Supported Network Environments for the Demand DSW ....................................... 42 Memory considerations for Demand DSW ........................................................... 43

Enable user-defined data streams .............................................................................. 45 Create user-defined data streams ...................................................................... 45 Update user-defined data streams ..................................................................... 46 Delete user-defined data streams ...................................................................... 46

Demand Worksheet RMI service ................................................................................. 46 Set up dashboard for Demand Planner ........................................................................ 47 Use the Demand reports in CDS environment .............................................................. 47

Chapter 6. Configure JDA Fulfillment ............................................................................. 49 .Net UI Common Properties ....................................................................................... 49 Deploy Load Manager Workbench ............................................................................... 49

Migration of Load Manager instances to the Load Manager Workbench .................... 49 Order Optimization User Interface .............................................................................. 50

Order Optimization Online Services .................................................................... 50 Constrained Supply Online Actions ..................................................................... 51


Order Optimization purge obsolete orders ................................................................... 52 JDA Fulfillment Replenishment Dashboard Online Services ............................................. 52 JDA Fulfillment Dynamic Allocation ............................................................................. 52

Setup information for Dynamic Allocation ........................................................... 52 JDA Fulfillment Dynamic Allocation online services ............................................... 54

Set up dashboard for Replenishment Planner ............................................................... 54

Chapter 7. Set up data for JDA Markdown Optimization and JDA Promotions Management56

Chapter 8. Configure JDA Promotions Management ....................................................... 61 Set up data ............................................................................................................. 61

Configure hierarchies for JDA Promotions Management ......................................... 61 Define price points for Price Optimization ............................................................ 62 Configure marketing instruments and user defined attributes ................................ 63 Configure activity types ................................................................................... 71 Configure promotional activity tasks .................................................................. 72 Configure DFU cost elements ............................................................................ 73 Configure product categories ............................................................................ 75 Configure integration between JDA Promotions Management and JDA Advertising..... 76 Define the price zones and ad zones used in JDA Advertising ................................. 76 Set up the Treatment data domain .................................................................... 76 JDA Advertising: Deploy Image browser ............................................................. 78

Configure Modeling Workbench .................................................................................. 78 Set up Import Offer process ...................................................................................... 80 Configure Candidate ID ............................................................................................ 81 Set SRE node configuration properties ........................................................................ 83 Configure Pricing parameters ..................................................................................... 83 Configure the loyalty pricing feature ........................................................................... 87 Limit the number of offers or products displayed .......................................................... 88 Set up offer-level security ......................................................................................... 89

Example 1: UDC values stored in metadata tables ............................................... 89 Example 2: UDC values specified in a reference table ........................................... 95

Set up the event calendar ....................................................................................... 100

Chapter 9. Configure JDA Strategic Pricing .................................................................. 101 Set up data ........................................................................................................... 101

Configure hierarchies for JDA Strategic Pricing .................................................. 101

Chapter 10. Configure JDA Demand Decomposition ..................................................... 103 Set up data ........................................................................................................... 103

Configure hierarchies for JDA Demand Decomposition ........................................ 103 Configure Modeling Workbench ................................................................................ 104

Chapter 11. Configure JDA Markdown Optimization .................................................... 107 Set up data ........................................................................................................... 107

Configure hierarchies for JDA Markdown Optimization ........................................ 107 Configure Modeling Workbench ................................................................................ 108

Chapter 12. Configure JDA Production and Sourcing Optimization .............................. 111 Enable users to commit scenarios ............................................................................ 111 Customize units of measure .................................................................................... 111

Chapter 13. Configure JDA Enterprise Supply Planning ............................................... 112 Set SRE node configuration properties ...................................................................... 112


Chapter 14. Compressed Data Storage ........................................................................ 113 What is Compressed Data Storage? .......................................................................... 113

Structure of regular tables .............................................................................. 113 Structure of CDS tables ................................................................................. 114 Details and flow chart .................................................................................... 115 Advantages .................................................................................................. 117 Business Implications .................................................................................... 117

Limitations when using CDS tables ........................................................................... 117 Platform limitations ....................................................................................... 118 Demand limitations ....................................................................................... 118 Fulfillment limitations .................................................................................... 120 Reporting limitations ..................................................................................... 120 Monitor limitations ........................................................................................ 120

Index ........................................................................................................................... 121

Overview

Chapter 1. Overview This guide describes the various tasks and processes to configure the various products in SCPO.

JDA Supply Chain Planning and Optimization Configuration Guide 1 © 1997-2014 JDA Software Group, Inc.- Confidential

Configure the SCPO application

Chapter 2. Configure the SCPO application This chapter provides detailed instructions for configuring Supply Chain Planning and Optimization (SCPO) on UNIX or Windows.

Use pre-configured templates to set up the solution JDA provides pre-configured templates that assume you have installed the following JDA applications:

• JDA Platform

• Supply Chain Planning and Optimization (SCPO), which includes JDA Demand, JDA Fulfillment, and JDA Master Planning

• JDA Reporting

After you install the above applications, you can use the installed templates to configure the solution. Note that even if you are implementing only a subset of the above solutions, you can still use the standard templates for that portion of the solution.

Two sets of templates are installed:

• XML files that can be imported using the JDA Enterprise Change Management feature to configure the security, user-defined columns, user interfaces, processes, and tasks.

• Command/shell scripts, xml files, and SQL files to support the batch processes

Control user access After you install SCPO and create the SCPO database schema, use the Security application to establish users and roles, and to control access to resources. Features, entities, and tables are types of SCPO resources. Also create user accounts in the Security module. Without user accounts, users cannot access SCPO. User accounts established in version 6.x of SCPO Client/Server will not function in SCPO. You can also store encrypted passwords.

For more information on implementing security for SCPO, see "Implement security (on page 8)".

Modify system properties SCPO provides configuration files that let you modify certain settings for your environment. The primary configuration file is scpo_config.xml. However, some JDA applications use additional configuration files. In addition, many system-wide settings are stored in the DBPARAM database table. See the table in "Modifying server and browser properties (on page 2)".

Modify server and browser properties The SCPO installation program automatically configures several property files and resource bundles. Some files allow the server administrator to change the default menu text and messages displayed on the browser interface and on the server. On the browser, this includes informational and error messages as well as portions of the user interface. On the server side, this includes informational and error messages.

Resource bundles enable SCPO to display web pages in the user's preferred language. One file is provided for each supported language. For example, in a translated version, SCPOWebResourceBundle.properties has a Spanish equivalent file called SCPOWebResourceBundle_es.properties. If using a version that supports translation, a user can select the preferred language from a list of supported languages. When you edit a resource file, you should edit all resource files in that bundle. Otherwise, the edit is not available in all languages.



Changing the properties and resource bundles affects the text displayed, but does not change how Web pages and messages are processed. Most files contain name-value pairs. If you modify the properties files, be careful to edit the value, not the name. You should back up the properties files before editing them.

The following table describes the properties files and resource bundles that are installed with SCPO.

SCPO properties files

Property File Name Location Description

Common

DAO.properties \config\properties

Maps Data Access Objects to class names. You should not modify this file.

scpo_config.xml \config\properties

Properties that govern the user interface and performance of user interface processes. Note that algorithm tuning hints should be specified in the sre_node_config_props for the relevant process, not in scpo_config.xml.

SCPOBusinessObjectResourceBundle.properties

\config\resources

Informational and error messages, text, labels, and display names used in the Decision Support Workbenches (Demand Workbench, Promotions Management Workbench, and Event Management Workbench).

SCPOConfigResourceBundle.properties

\config\resources

Used in the system properties to define how to display properties in scpo_config.xml.

SCPOWebDirectoryResourceBundle.properties

\config\resources

Display names used in the Directory.

SCPOWebResourceBundle. properties

\config\resources

Informational and error messages, text, labels, and menu items for SCPO.

SPClientResourceBundle.properties \config\resources

Errors messages, menu text, and labels for client pages.

Flowcasting

SCSCResourceBundle.properties \config\resources

Informational and error messages, text, labels, and menu items for Flowcasting.

Demand

DPEEMigration.properties \config\properties

Properties used by the process that migrates a Demand Planning Extended Edition (DPEE) database to SCPO.

Enterprise Supply Planning

ESPResourceBundle.properties \config\resources

Informational and error messages, text, labels, and menu items for Enterprise Supply Planning.

PlanningExceptionsResourceBundle.properties

\config\resources

Informational and error messages for the Enterprise Supply Planning process.

Fulfillment

FulfillmentResourceBundle. properties

\config\resources

Informational and error messages, text, labels, and menu items for Fulfillment.





\config\resources

Informational and error messages for the Fulfillment Planning process.

SupplyExceptionsResourceBundle. properties

\config\resources

Informational and error messages generated by the Fulfillment algorithm.

IPO

IPOResourceBundle.properties \config\resources

Informational and error messages, text, labels, and menu items for Inventory Policy Optimizations.


\config\resources

Provides process related model exceptions which are reported in SKUException table.

SCPOSREResourceBundle.properties

\config\resources

Contains the process name.

SCPOWebDirectoryResourceBundle.properties

\config\resources

Contains the process name.

Markdown Optimization

DRMResourceBundle.properties \config\resources

Informational and error messages, text, labels, and menu items for DRM.

Master Planning

MasterPlanningResourceBundle.properties

\config\resources

Informational and error messages, text, labels, and menu items for Master Planning.


\config\resources

Informational and error messages for the Fulfillment Planning process.

PlanningDisabledExceptionTypes.properties

\config\resources

Information that can be used to disable certain Master Planning exceptions.

Promotions Management

APMBusinessObjectResourceBundle.properties

\config\resources

Informational and error messages used in the Promotions Management Workbench, Event Management Workbench, and Promotions Management processes.

APMResourceBundle.properties \config\resources

Informational and error messages, text, labels, and display names used in the Promotions Management Workbench, Event Management Workbench, and Promotions Management processes.

PromotionResourceBundle.properties

\config\resources

Exceptions, status messages, and log messages for Promotions.

Strategic Price Optimization

P2ResourceBundle.properties \config\resources

Informational and error messages, text labels and display names used in the Price Actions Workbench, Price Review Workbench, Rule Manager, Rule et Manager, Scenario Manager and Shelf Price Optimization processes.

DRMResouceBundle.properties \config\resources

Informational and error messages, text labels and menu items for DRM.

Production and Sourcing Optimization




StrategyResourceBundle.properties \config\resources

Informational and error messages, text, labels, and display names used in the Directory.

strategy_interactive_ui.properties \config\resources

Unit of measure names, Production and Sourcing Optimization-specific symbols and names, userview entries, and other text labels.

Supply

supply.properties \config\properties

Performance tuning parameters for JDA Supply algorithms.

Modify a resource bundle To change external text and labels displayed to users, open the appropriate resource bundle, such as SCPOWebResourceBundle.properties.

1. Shut down the JDA Platform Server.

2. Using a text editor, open SCPOWebResourceBundle.properties in the <install_dir>\config\resources directory

3. Find the specific property to modify. For example, to change the title for the DFU Maintenance page, find the External Text section:

#External Text

DFUMaint.Title=DFU Maintenance

4. Enter the new value for the property. For example, to change the title to Maintain DFU, enter the new value to the right of the equal sign:

DFUMaint.Title=Maintain DFU

5. Save and exit the properties file.

6. Repeat steps 2-5 for each SCPOWebResourceBundle_<language>.properties file, including English. Note that when editing non-English files, they must be converted from Unicode escape, which respresents special and double-byte characaters by their ASCII encoding sequence. To do this, use the nativetoascii utility provided by java.

7. Restart the JDA Platform Server.

Edit the DBParam table The initial database setup is performed after the SCPO installation process. A key part of this setup is the definition of global parameters that apply to multiple JDA applications. When you create the database, these parameters are set to a default value in the DBParam (Database Parameters) table. You should evaluate these defaults and adjust the parameters as necessary before you begin using the database.

To set these column values, open a Flexible Editor page for the DBParam table, select and edit the row. See the online help for your application for detailed instructions on editing the DBParam table.

Set up calendars In the SCPO applications, calendars define the time buckets used to display and report data. They also define a variety of time periods associated with specific applications.



The system uses several different types of calendars to display data and derive calculations. All calendars define time buckets. Some calendars also specify whether something is open or closed. Most of the calendar types are specific to a particular JDA application, including:

• Demand calendars: Time periods that define forecast periods used in fitting statistical models and calculating forecasts.

• Enterprise Supply Planning calendars: Time periods that define availability of production and transportation resources, and time periods when a product can be shipped from or received at a location.

• Fulfillment/Distribution calendars: Periods when destinations can ship or receive product, periods when production can occur, or allocation profiles for forecasted demand.

• Fulfillment/Deployment calendars: Intervals into which recommended shipments are grouped.

• Fulfillment/Production calendars: Time periods that define when CPP resources are open for production and the amount of capacity they have in each period.

• Markdown calendars: Time periods that define forecast periods used in fitting statistical models and calculating forecasts.

• Master Planning calendars: Time periods that define availability of production and transportation resources, and time periods when product can be shipped from or received at a location.

• Promotions calendars: Time periods that define forecast periods used in fitting statistical models and calculating forecasts.

• Supply calendars: Time periods that define forecast periods used in fitting statistical models and calculating forecasts, time periods that define when resources are open for production, and time periods that define the amount of capacity the resources have in each period.

In addition, the system uses reporting calendars to report time-dependent data. Reporting calendars are the only calendar types that are used in all components.

The system stores calendar data in the Cal (Calendars) and CalData (Calendar Data) tables. The Cal table defines the calendar names and types for all calendars in the database. The CalData table specifies the details of each calendar defined in the Cal table.

When a new database is created, the system automatically creates the following standard reporting calendars:

• Hours: Hourly, on the hour

• Days: Daily, midnight to midnight

• Weeks: Weekly, ending Saturday

• Months: Calendar months

Note: All time is assumed to be entered in Greenwich Mean Time (GMT).

See the online help for a more detailed explanation of the various types of calendars, and for instructions for creating a calendar.

Set up Scenarios If you want to load Fulfillment/Enterprise Supply Planning/Master Planning/IPO/PSO scenarios and/or if you do not want to commit PSO scenarios:

1. Set the value of ‘ScenarioCommit’ property in scpo_config.xml in System Properties to false (default value).

Note: You must not run the add_sim_constraints script.



2. Load PSO/Fulfillment/Enterprise Supply PlanningMaster Planning/IPO scenarios in the same database instance.

Note: As the constraints are not applied on tables, the PSO scenarios cannot be committed.

If you want to commit PSO scenarios:

1. Set the value of ‘ScenarioCommit’ property in scpo_config.xml in System Properties to true.

2. For loading PSO scenarios, you must have already run the add_sim_constraints.sql script, which adds referential integrity constraints on the scenario (SIM_) tables. Otherwise, the PSO scenarios will fail to load.

3. After running the add_sim_constraints.sql script, PSO and (Fulfillment/Enterprise Supply Planning/Master Planning/IPO) scenarios can never be run in the same database instance. The Fulfillment/Enterprise Supply Planning/Master Planning/IPO scenarios must be run in a separate instance. If you try to load the Fulfillment/Enterprise Supply Planning/Master Planning/IPO scenarios, the scenarios may fail with constraint errors.

Note: If there are any Fulfillment/Enterprise Supply Planning/Master Planning/IPO scenarios which are already available, then you should delete those scenarios.

Identify the discrepancies which will cause the scenarios to fail A scenario may fail while loading due to discrepancies between the Live and the respective SIM table definitions.

To load a scenario successfully, the Live table and the respective SIM table definitions (Number of columns except FF_TRIGGER_CONTROL column, each column data type, Null constraint of each column) should match. Otherwise, a scenario loading process may fail.

Perform the following procedure to find the mismatches between the Live table and the respective SIM tables:

1. Open a command prompt or a shell prompt and navigate to the <install_dir>\config\bin\scpoweb directory.

2. Run the CompareLiveAndSimTables.cmd (Windows) or CompareLiveAndSimTables.sh (UNIX) file using the following syntax:

CompareLiveAndSimTables <scpouser> <scpopassword> <tns_name>

For example:

CompareLiveAndSimTables SCPOMGR SCPOMGR SAMPLE78

After the CompareLiveAndSimTables file is run, the CompareLiveAndSimTables.log file is created in the <install_dir>\config\database\scpoweb directory. This log file contains the mismatches between the Live and the respective Simulation tables.

For Example:

ITEM.PRODUCTLINE datatype length(50) is not matching with SIM_ITEM.PRODUCTLINE datatype length(200).

No matching SIM table column found for NETWORK.PROJORDERDUR

No matching SIM table column found for SKUDEMANDPARAM.WEEKLYAVGHIST

No matching SIM table column found for SKU.ITEMSTOREGRADE


Implement security

Chapter 3. Implement security This chapter provides a high-level description of security within SCPO. For information on how to define security for the JDA Interface Generation Program (IGP) see the JDA Platform Interface Generation Program Reference Guide and for Import data see the JDA Platform Common Concepts Reference Guide.

Use the Security module The Security module provides access control and security for SCPO. Security is installed as part of JDA Platform. See additional information on setting up security in the JDA Platform Installation/Administration Guide and the JDA Foundation Administration OnLine Expert.

SCPO uses the following types of security features:

• Users

• Roles

• Resources

• Filters

Note: JDA Platform supports partnership security, but this feature is not used by SCPO. In addition, SCPO supports enterprise security, but only for the default host enterprise.

SCPO also provides predefined security objects, which are loaded into the JDA Foundation schema when the database is configured. Manage these objects using the Security module.

You must log on using an account with the appropriate security permissions in order to create or maintain objects in the Security module. See the Security online help to learn how to create users, roles, resources, and filters.

In addition to the security provided by JDA Platform, Oracle includes security features that control how a database is accessed and used. For information on Oracle security features, see Oracle documentation.

Users A user is an individual with the authorization to log on to the JDA applications. Users are assigned roles that determine the resources they can access as well as the levels of permission, or privileges, they have for each resource. Available privileges include create, read, update, delete, and execute.

Roles Roles enable users to have varying levels of permissions for a given resource. A single user can have multiple roles and a single role can be assigned to multiple users. JDA Platform includes two default roles, HostAdmin and EnterpriseHierarchyAdmin. In addition, SCPO ships with two sample roles, SCPOAdmin and SCPOViewOnly, which you can copy and modify to start implementing your security quickly. The SCPOViewOnly role provides Read access to all tables in the SCPO application.

Caution: In addition to the resource for the JDA application (for example, Demand, Production and Sourcing Optimization), all users must be assigned a role that has the execute permission to the SCPO Application resource, SCPO Suite. Otherwise, the authentication failure message "You do not have access to the application" is displayed when the user tries to open any application userview.

Resources Resources are named objects in your system to which you can control access. The major resource types include: feature and entity.


Implement security

• Feature: Feature-level security controls access to specific functionality within the applications, such as the Demand Workbench or Plan Analysis. Feature-level security is controlled by assigning resources to specific roles.

• Entity: Entity-level security controls access to a table or group of tables that together perform a business operation. In SCPO, each table is mapped to a corresponding entity, which is the first level of permission for the table.

• Table: A table-based resource overrides the permissions granted by the entity resource. For example, if CRUDE permission is granted to the entity-based resource ITEM, but a table-based resource ITEM is created with only Read permission, then any roles assigned with the table-based permission will only have Read permission.

• Column: A column-based resource overrides the permissions granted on the entity or table resource.

The permissions associated with a resource are set in the Access Control List (ACL). Each ACL defines the permissions for a resource. Resources are assigned to a specific role using an ACL. A role can contain zero or more ACLs.

The following tables list all SCPO feature and entity resources. The naming conventions used for Product names are as follows:

• Demand - Dmd

• Demand Decomposition - Dmd Decomp

• Demand Unconstrained - Dmd Unconstr

• Dynamic Demand Response - DDR

• Enterprise Supply Planning - ESP

• Flowcasting

• Fulfillment - FF

• Inventory Policy Optimization - IPO

• Markdown Optimization - MDO

• Master Planning - MP

• Promotions Management - PM

• Supply Chain Planning and Optimization - SCPO

• Strategic Pricing - SP

• Production and Sourcing Optimization - PSO

• Travel Price Optimization - TPO

Note: For resources that are added in 8.1.0.0, you must add the relevant resources to any relevant roles that will require that functionality.


Implement security

Feature Resources UI/Process/

Function Type Resource Display

name Resource

database value New

in 7.5.2

.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Add/Update Models Process Add/Update Models Process

Add/Update Models Process

Dmd

Adjust Forecast for Pricing and Promotions

Process Adjust Forecast for Pricing and Promotions Process

Fpa Process PM, Dmd Decomp, MDO

Generate Cross product relationships

Process Generate Cross product relationships Process

Generate Cross product relationships Process

PM, Dmd Decomp

Adjust History for Pricing and Promotions

Process Adjust History for Pricing and Promotions Process

Normalization Process

PM, Dmd Decomp, MDO

Aggregate Demand and Availability Status

Process Aggregate Demand & Availability Status Process

Aggregate Demand & Availability Status Process

Dmd Unconstr

Aggregate History Process Aggregate History Process

Aggregation Process

Dmd Decomp, MDO

Allocate Materials Process Allocate Materials Process

Fulfillment_MaterialAllocation

FF

Assign Short Lifecycle Curve

Process Assign Short Lifecycle Curve Process

Demand.AssignShortLifecycleCurve

X Dmd

Automated Weight Estimation

Process Generate Competitor Weights

AutomatedWeightEstimation

X TPO

Build Seasonal Profile Collection

Process Build Seasonal Profile Collection Process

Build Seasonal Profile Collection

Dmd,


Implement security

UI/Process/ Function

Type Resource Display name

Resource database value

New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Build Short Lifecycle Curve

Process Build Short Lifecycle Curve

Demand.BuildShortLifecycleCurve

X Dmd

Build Transportation Loads

Process Build Transportation Loads

Fulfillment_LoadBuilder

FF

Build WFM Data Process Load Work Force Management DFUs

Demand.BuildWFMData

X Dmd

Calculate Actuals Process Calculate Actuals Actualization Process

SP

Calculate Cross Product Weights

Process Calculate Cross Product Weights process

DRM.CalculateCrossProductWeights

X Dmd Decomp, MDO, PM

Calculate Dependent Demand

Process Calculate Dependent Demand

Demand.DependentDemand

X Dmd

Calculate Dynamic Demand Response

Process Calculate Dynamic Demand Response

DynamicDemandResponse_Process

DDR

Calculate E3 Error Process Calculate E3 Error Demand.CalculateE3Error

Dmd

Calculate Historical Attach Rate

Process Calculate Historical Attach Rate

Demand.AttachRate

X Dmd

Calculate Lead Time Variance

Process Calculate Lead Time Variance

IPO.CalcSupplyVar X IPO

Calculate Master Plan

Process Calculate Master Plan Process

Calculate Master Plan

MP, ESP

Calculate Mean Daily Demand

Process Calculate Mean Daily Demand Process

Calculate Mean Daily Demand Process

IPO, FF

Calculate Model Process Calculate Model Process

Calculate Model Process

Dmd, DMF


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Calculate Net Forecast Error

Process Calculate Net Forecast Error

Calculate Net Forecast Error Process

FF, MP

Calculate Plan Process Calculate Plan Plan Algorithm Process

FF

Calculate Rules Based Priority

Process Calculate Rules Based Priority Process

MP RBO Service FF, MP

Calculate Seasonality Error

Process Calculate Seasonality Error

Calculate Seasonality Error Process

FF, MP

Calculate Sigmoid Priority

Process Calculate Sigmoid Priority Process

Calculate Sigmoid Priority

MP, ESP

Calculate SKU MSE Process Calculate SKU Mean Squared Error Process

Calculate SKU MSE

IPO, FF

Calculate Statistical Safety Stock

Process Calculate Statistical Safety Stock

Calculate Statistical Safety Stock

FF, MP

Calendar Manager UI Calendar Manager Calendar Management

SCPO

Classification Manager

UI Classification Manager

Classification Manager

Dmd

Classify DFUs and Tune Parameters

Process Classify DFUs and Tune Parameters Process

Classify DFUs and Tune Parameters Process

Dmd

Cleanse History Process Cleanse History Demand.CleanseHistory

X Dmd

Compress Causal Factors

Process Compress Causal Factor Process

Compress Causal Factor Process

Dmd

Compute Markdown Metrics

Process Compute Markdown Metrics Process

Markdown Metrics Computation

MDO


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Compute Price Elasticity

Process Compute Price Elasticity Process

PriceElasticityComputation Process

Dmd Decomp, MDO, PM

Compute Price Ratios

Process Compute Price Ratio Process

Price Ratio Computation Process

PM, Dmd Decomp, MDO

Compute Price Sensitivity

Process Compute Price Sensitivity Process

Price Sensitivity Process

Dmd Decomp, MDO

Compute Reference Prices

Process Compute Reference Prices Process

Reference Price Computation Process

Dmd Decomp, MDO

Copy Measure Data Process Copy Measure Data

Copy Measure Data

X Dmd

Copy SKU UI Copy SKU Copy SKU SCPO CPP Workbench UI CPP Workbench CPP Toolkit FF Create Recommended Shipment Prioritization Strategies

Process Create Recommended Shipment Prioritization Strategies

Fulfillment_RBO FF

Decision Support Workbench

UI Decision Support Workbench


Dmd

DDE Mass Update Process DDE Mass Update DDE Mass Update Dmd Delete Attach Rate Process Delete Attach Rate Demand.DeleteAtt

achRate X Dmd

Delete DFUs Process Delete DFUs Demand.DeleteDFU

Dmd


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Delete Forecast Process Delete Forecast Process

Delete Forecast Process

Dmd, DMF, MDO, PM

Delete History Process Delete History Process

Delete History Process

Dmd

Delete Order UI Fulfillment_Delete Order

OrderOpt.prop.DeleteOrder

X FF

Demand Product Demand SCPOWeb.Demand

Dmd

Demand Classification

Function Demand Classification

Demand Classification

Dmd

Demand Compound Workspace

UI Demand Compound Workspace

DEMAND COMPOUND WORKSPACE

Dmd

Demand Decomposition

Product Demand Decomposition

SCPOWeb.DemandDecomposition

X Dmd Decomp

Demand Flexible Editor

UI Demand Flexible Editor

DEMAND FLEXIBLE EDITOR

Dmd

Demand Decision Support Workbench

UI Demand Decision Support Workbench

SCPOWeb.DemandRichUI

Dmd

Demand Pegging UI Demand Pegging DemandPegging X Dmd Detect Out of Stock Process Detect Out of

Stock Fulfillment.OutOfStock

X FF

Causal Factor Function DSW Causal Factor

Demand Thick UI Causal Factor

Dmd

Data Driven Event Function DSW Data Driven Event

Demand Thick UI DDE

Dmd

Linear External Factor

Function DSW Linear External Factor

Demand Thick UI Linear External Factor

Dmd


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Lock Function DSW Lock Demand Thick UI Lock

Dmd

Mask Function DSW Mask Demand Thick UI Mask

Dmd

Mean Value Adjustment

Function DSW Mean Value Adjustment

Demand Thick UI Mean Value

Dmd

Override Function DSW Override Demand Thick UI Override

Dmd

Seasonality Function DSW Seasonality Demand Thick UI Seasonality

Dmd

Target Function DSW Target Demand Thick UI Target

Dmd

Demand Unconstraining

Product Demand Unconstraining

SCPOWeb.DU Dmd Unconstr

Demand Workbench UI Demand Workbench

Demand Workbench

Dmd

Dmd Workbench - Algorithm Properties

Function Demand Workbench - Algorithm Properties Tab

Demand Workbench - Algorithm Properties Tab

Dmd

Dmd Workbench - Causal Factors

Function Demand Workbench - Causal Factors Tab

Demand Workbench - Causal Factors Tab

Dmd

Dmd Workbench - DDE

Function Demand Workbench - Data Driven Events Tab

Demand Workbench - Data Driven Events Tab

Dmd

Dmd Workbench - Forecast Locks

Function Demand Workbench - History and Forecast Tab - Forecast Locks

Demand Workbench - History and Forecast Tab - Forecast Locks

Dmd


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Dmd Workbench -Hist & Fcst - Override

Function Demand Workbench - History and Forecast Tab - Override

Demand Workbench - History and Forecast Tab - Override

Dmd

Dmd Workbench - Lifecycle/Extranal Factors

Function Demand Workbench - Life Cycle/External Factors Tab

Demand Workbench - Life Cycle/External Factors Tab

Dmd

Dmd Workbench - Mask History

Function Demand Workbench - Mask History Tab

Demand Workbench - Mask History Tab

Dmd

Dmd Workbench - Mean Values

Function Demand Workbench - Mean Values Tab

Demand Workbench - Mean Values Tab

Dmd

Dmd Workbench - Seasonality

Function Demand Workbench - Seasonality Tab

Demand Workbench - Seasonality Tab

Dmd

Dmd Workbench - Targets

Function Demand Workbench - Targets Tab

Demand Workbench - Targets Tab

Dmd

Dmd Workbench - YOY

Function Demand Workbench - Year Over Year Tab

Demand Workbench - Year Over Year Tab

Dmd

Define Optimization Goals

UI Define Optimization Goals


X ESP

Deseasonalize Estimation Inputs

Process Deseasonalize Estimation Inputs Process

Decomposition Process

PM, Dmd Decomp, MDO

DFU Maintenance UI DFU Maintenance DFU Maintenance Dmd, DMF


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Disaggregate Unconstrained Demand

Process Disaggregate Unconstrained Demand Process

Disaggregate Unconstrained Demand Process

Dmd Unconstr

Distance Calculation Process Calculate Distance Between Locations

Distance Calculation

X PSO

DMF Compound Workspace

UI Demand Management Foundation Compound Workspace

DMF COMPOUND WORKSPACE

DMF

DMF Flexible Editor UI Demand Management Foundation Flexible Editor

DMF FLEXIBLE EDITOR

DMF

Dynamic Demand Response

Product Dynamic Demand Response

SCPOWeb.DynamicDemandResponse

DDR

Dynamic Demand Response Compound Workspace

UI Dynamic Demand Response Compound Workspace

DYNAMIC DEMAND RESPONSE COMPOUND WORKSPACE

DDR

Dynamic Demand Response Flexible Editor

UI Dynamic Demand Response Flexible Editor

DYNAMIC DEMAND RESPONSE FLEXIBLE EDITOR

DDR

Estimate Fractional Survival Curve

Process Estimate Fractional Survival Curve Process

Estimate Fractional Survival Curve Process

Dmd Unconstr

Estimate Market Response Model

Process Estimate Market Response Model

Calibration Process

PM, Dmd Decomp, MDO


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Evaluate Model Performance

Process Evaluate Model Performance

DRM.HoldoutEvaluation

X MDO, PM,Dmd Decomp

Requirement Plan Process Calculate Requirement Plan

Calculate Requirement Plan

X MP, ESP

Evaluate Pricing Scenario

Process Evaluate Pricing Scenario

Strategic Pricing Evaluation Process

SP

Event Management Workbench

UI Event Management Workbench

PromotionsManagement.EventManagementWorkbench

PM

Exception Navigator UI Exception Navigator

Exception Navigator

X MP, ESP

Promo Candidate Process Promotions Management Promo Candidate Process

PromotionsManagement.PromoCandidateProcess

X PM

Candidate Recommendation Tab

UI Promotions Management Candidate Recommendation

PromotionsManagement.CandidateRecommendation

X PM

Enterprise Supply Planning

Product SCPOWeb. EnterpriseSupplyPlanning

SCPOWeb. EnterpriseSupplyPlanning

X ESP

Enterprise Supply Planning Compound Workspace

UI Enterprise Supply Planning Compound Workspace

ENTERPRISESUPPLYPLANNING COMPOUND WORKSPACE

X ESP

Enterprise Supply Planning Flexible Editor

UI Enterprise Supply Planning Flexible Editor

ENTERPRISESUPPLYPLANNING FLEXIBLE EDITOR

X ESP

Exception Graphs UI Exception Graphs Exception Graphs Dmd


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Export Offers Process Export Offers Process

Export Offers Process

PM

Export Price Rules Process Export Price Rules Process

Export Price Rules Process

X PM

External Factor Manager

UI External Factor Manager

External Factor Manager

Dmd

Flexible Allocation UI Flexible Allocation Flexible Allocation Dmd Fulfillment Product Fulfillment SCPOWeb.Fulfillm

ent FF

Fulfillment Compound Workspace

UI Fulfillment Compound Workspace

FULFILLMENT COMPOUND WORKSPACE

FF

Fulfillment Flexible Editor

UI Fulfillment Flexible Editor

FULFILLMENT FLEXIBLE EDITOR

FF

Fulfillment Order Builder Projection

Process Fulfillment Order Builder Projection

FulfillmentProjOrderBuilder

X FF

Generate Allocation Calendar for DFUs

Process Generate Allocation Calendar

DynamicDemandResponse_AllocCal

DDR

Generate Allocation Calendar for SKUs

Process Generate Allocation Calendar

DynamicDemandResponse_AllocCal

DDR

Generate Constraints

Process Generate Constraints Process

Constraint Generation Process

SP

Generate Cross Product Relationship

Process Generate Cross Product Relationship

DRM.CrossRelationGeneration

X Dmd Decomp, PM

Generate Forecast Orders

Process Generate Forecast Orders Process

Forecast Order Generation

FF, MP, IPO

Generate Master Plan (MAP)

Process Generate Master Plan (MAP)

ESP.GenerateMasterPlan.Map

X ESP


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Generate Master Plan (LpOpt)

Process Generate Master Plan (LpOpt)

ESP.GenerateMasterPlan.LpOpt

X ESP

Generate Price Point Forecast

Process Generate Price Point Forecast Process

Price Point Demand Generation Process

Dmd Decomp, MDO, SPO

Generate Promotional Forecast

Process Generate Promotional Forecast Process

Promotions Management Evaluation Process

PM

Generate SKU Exceptions

Process Generate SKU Exceptions

SKU Exception Builder Process

FF, MP

Generate Safety Stock Orders

Process Generate Safety Stock Orders

Generate Safety Stock Orders

FF, MP

Generate Stocking Plan

Process Generate Stocking Plan Process

Generate Stocking Plan Process

IPO

Generate Supply & Demand Links

Process Generate Supply & Demand Links

Generate Supply & Demand Links

MP, ESP

Generate Supply & Demand Links Based on Priority

Process Generate Supply & Demand Links Based on Priority

Generate Supply & Demand Links Based on Priority

FF, MP

Grade SKUs Process Grade SKUs GradeSKUs X Flowcasting

Heuristic Elasticity Process Estimate Price Elasticity

HeuristicElasticity X TPO

Identify Markdown Candidates

Process Identify Markdown Candidates Process

Markdown Candidate Identification Process

MDO

Import Forecast Process Import Forecast Process

Import Forecast Process

Dmd, DMF, PM, MDO


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Inventory Policy Optimization

Product Inventory Policy Optimization

SCPOWeb.IPO IPO

IPO Compound Workspace

UI IPO Compound Workspace

IPO COMPOUND WORKSPACE

IPO

IPO Flexible Editor UI IPO Flexible Editor IPO FLEXIBLE EDITOR

IPO

IPO Workbench UI IPO Workbench IPOWorkbench IPO Launch Manager UI Launch Manager LaunchManager Dmd Level Production Loads

Process Level Production Loads

Load Leveler Process

FF

Level SKUs With Search

Process Level SKUs With Search

Level SKUs With Search

X FF, MP, IPO

Lifecycle Manager UI Lifecycle Manager Lifecycle Manager Dmd Load Manager UI Load Manager Load Manager FF Map DFUs Process Map DFUs Process Map DFUs Process Dmd,

DMF Markdown Compound Workspace

UI Markdown Compound Workspace

MARKDOWN COMPOUND WORKSPACE

MDO

Markdown Flexible Editor

UI Markdown Flexible Editor

MARKDOWN FLEXIBLE EDITOR

MDO


Product Markdown Optimization

SCPOWeb.Markdown

MDO

Markdown Rule Set Assignment

UI Markdown Rule Set Assignment

Markdown Rule Set Assignment

X MDO

Markdown Workbench

UI Markdown Workbench

Markdown Summary Workbench

X MDO

Markdown Approval Function Markdown Approval

Markdown Approval

MDO


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Markdown Recommendation Properties

Function Markdown Recommendation Properties

Markdown Recommendation Properties

MDO

Markdown Submit for Approval

Function Markdown Submit for Approval

Markdown Submit for Approval

MDO

Market Reference Price Computation

Process Calculate Market Reference Price

Market Reference Price Computation

X TPO

Master Planning Product SCPOWeb.Master Planning

SCPOWeb.MasterPlanning

MP, ESP

Master Planning Compound Workspace

UI Master Planning Compound Workspace

MASTERPLANNING COMPOUND WORKSPACE

MP, ESP

Master Planning Flexible Editor

UI Master Planning Flexible Editor

MASTERPLANNING FLEXIBLE EDITOR

MP, ESP

Master Planning Workbench

UI Master Planning Workbench

MP Workbench MP, ESP

Measure Maintenance

UI Measure Maintenance

Measure Maintenance

X Dmd

Stored Measures UI Stored Measure Stored Measure X Dmd Computed Measures UI Computation Computation X Dmd Pre-Defined Measures

UI PreDefined Measures

PreDefined Measures

X Dmd

Modeling Workbench UI Modeling Workbench

DRM.ModelingWorkbench

X MDO,PM, Dmd Decomp

Modeling Workbench Model Maintenance

UI Modeling Workbench Model Maintenance

DRM.MRMEditor X MDO, PM, Dmd Decomp

MP Replenishment Dashboard

UI MP Replenishment Dashboard

MPReplenishmentDashboard

X MP, ESP


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

MP Replenishment Workbench Dashboard

UI MP Replenishment Workbench Dashboard

MPReplenishment WorkbenchDashboard

X MP, ESP

Promotions Management Build Promotional History

Process Promotions Management Build Promotional History

PromotionsManagement.BuildPromotionalHistoryProcess

X PM

Publish Data For Reports

Process Publish Data For Reports

PublishDataForReports

X Flowcasting

Publish Forecast UI Publish Forecast PromotionsManagement.PublishForecast

X PM

TPO Competitor Management

UI Competitor Management

NPO.CompetitorManagement

X TPO

TPO Export UI Export NPO.Export X TPO TPO FlexibleEditor UI Flexible Editor NPO.FLEXIBLEEDI

TOR X TPO

TPO Graph Preferences

UI Preferences NPO.GraphPreferences

X TPO

TPO Optimization Process Optimize Price Recommendations

NPO.Optimization X TPO

TPO Override UI Rate to Send NPO.Override X TPO TPO Property Rules UI Property Rules NPO.PropertyRule

s X TPO

TPO RECMD Export UI Export NPO.RECMD.Export

X TPO

Calculate Aggregation

Process Aggregation X FF

Calculate Allocation Process Allocation X FF TPO RECMD Properties

UI Recommendation Review Column Preferences

NPO.RECMD.Properties

X TPO


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

TPO Season Management

UI Season Management

NPO.SeasonManagement

X TPO

TPO Workbench UI TPO Workbench NPOWorkbench X TPO Optimize Inventory Policy

Process Optimize Inventory Policy Process

Inventory Policy Optimizer

IPO

Optimize Markdowns Process Optimize Markdowns Process

Markdown Optimization Process

MDO

Optimize Orders Process Optimize Orders Optimize Orders FF Optimize Pricing Scenario

Process Optimize Pricing Scenario Process

Strategic Pricing Optimization Process

SP

Optimize Production Changeovers

Process Optimize Production Changeovers Process

Campaign Plan MP, ESP

Optimize Supply Chain

Process Optimize Supply Chain

Production and Sourcing Optimization Algorithm

PSO

Order Search/Details UI Order Search/Details

Order Search/ Details

FF

Order To Do/Task List

UI Order To Do/Task List

Order To Do/ Task List

FF

OrderSKU Search/Details

UI OrderSKU Search/Details

Order SKU Search / Details

FF

Allocation Workbench:Manual Configuration

UI AllocationManualWorkbench

X FF

Allocation Workbench:Review

UI AllocationReviewWorkbench

X FF


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Need Variable Manger

UI NeedVariableManager

X FF

Override Manager UI Override Manager Override Manager Dmd Plan Analysis UI Plan Analysis Plan Analysis FF, MP Plan Order Edit Process

Function Plan Order Edit Process

Plan Order Edit Process

FF, MP

Price Actions Workbench

UI Price Actions Workbench

Strategic Pricing Optimization Approval Workbench

SP

Price Review Workbench

UI Price Review Workbench

Strategic Pricing Optimization Analysis Workbench

SP

Pricing Product Pricing SCPOWeb.DRM DMF, PM, Dmd Decomp, Dmd Unconstr, MDO


Product Promotions Management

SCPOWeb.PromotionsManagement

PM

Promotions Management Compound Workspace

UI Promotions Management Compound Workspace

PROMOTIONS MANAGEMENT COMPOUND WORKSPACE

X PM

Promotions Management Flexible Editor

UI Promotions Management Flexible Editor

PROMOTIONS MANAGEMENT FLEXIBLE EDITOR

PM

Promotions Management Workbench

UI Promotions Management Workbench

PromotionsManagement.PromotionsManagementWorkbench

PM


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Approve Offer Function Approve Offer PromotionsManagement.Approve

PM

Publish Offer Function Publish Offer PromotionsManagement.PublishOffer

PM

Publish Prices Function Publish Prices PromotionsManagement.PublishPrices

PM

Replenishment Dashboard

UI Replenishment Dashboard

ReplenishmentDashboard

X FF

Replenishment Workbench Dashboard

UI Replenishment Workbench Dashboard

Replenishment WorkbenchDashboard

X FF

Save Offer Function Save Offer PromotionsManagement.Save

PM

Submit Offer Function Submit Offer PromotionsManagement.Submit

PM

Unrestricted Save Function Unrestricted Save PromotionsManagement.UnrestrictedSave

PM

Publish Forecast Process Publish Forecast Process

Publish Forecast Process

Dmd, DMF, MDO

Publish IPO Output Process Publish IPO Output Process

Publish IPO Output

IPO

Publish Optimal Production Changeovers

Process Publish Optimal Production Changeovers Process

Publish Campaign MP, ESP

Publish Price Coefficients

Process Publish Price Coefficients Process

PriceCoefficientPublisher Process

PM, Dmd Decomp, MDO


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Recommend Scheduled Receipts

Process Recommend Scheduled Receipts

Scheduled Receipts Process

FF, MP

Reconcile Forecast Process Reconcile Forecast Process

Reconcile Forecast Process

Dmd, DMF

Reconcile Forecast Subset

Process Reconcile Forecast Subset Process

Reconcile Forecast Subset Process

Dmd, DMF

Refresh Offers Process Refresh Offers Process

Refresh Offers Process

PM

Replenishment Workbench (Fulfillment)

UI Replenishment Workbench (Fulfillment)

Replenishment Workbench

X FF

Replenishment Workbench (Master Planning)

UI Replenishment Workbench (Master Planning)

MP Replenishment Workbench

X MP, ESP

Rule Manager UI Rule Manager Strategic Pricing Rule Manager

SP

Rule Set Manager UI Rule Set Manager Strategic Pricing Rule Set Manager

SP

Scenario Manager UI Scenario Manager (Pricing)

Strategic Pricing Scenario Manager

SP

Scenario Manager UI Scenario Manager (Planning)

Planning Scenarios SCPO

Scenario Commit Function Scenario Commit Scenario Commit PSO Scorecard View UI Scorecard View SCORECARD MP,

ESP SCPO Suite Product SCPO Suite SCPOWeb SCPO Seasonality Manager UI Seasonality

Manager Seasonality Dmd

Shelf Price Optimization

Product Shelf Price Optimization

SCPOWeb.Precision Pricing

SP


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Shelf Price Optimization Compound Workspace

UI Shelf Price Optimization Compound Workspace

Strategic Pricing Compound Workspace

SP

Shelf Price Optimization Flexible Editor

UI Shelf Price Optimization Flexible Editor

Strategic Pricing Flexible Editor

SP

Short Lifecycle Attribute

UI Short Lifecycle Attribute Maintenance

ShortLifecycleAttribute

X Dmd

SKU Classification Workbench

UI SKU Classification Workbench

SKUClassificationWorkbench

IPO, FF

SKU Classification Process SKU Classification Process

SKU Classification IPO, FF

Stocking Plan View UI Stocking Plan View

IPO Stocking Plan IPO

Store Derived Tables Process Store Derived Tables Process

Store Derived Tables Process

Dmd, DMF, MDO

Store Forecast Process Store Forecast Process

Store Forecast Dmd, DMF, MDO

Store Projections and Statistics

Process Store Projections and Statistics Process

Store Projections or Statistics

PSO

Store Resource Projections

Process Store Resource Projections

Store Resource Projections

FF, MP

Store SKU Projections (Fulfillment & Master Planning)

Process Store SKU Projections (Fulfillment & Master Planning)

Store SKU Projections

FF, MP, ESP


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Production and Sourcing Optimization

Product Production and Sourcing Optimization

SCPOWEb.Production and Sourcing Optimization

PSO

Production and Sourcing Optimization Client

UI Production and Sourcing Optimization Client

Stategy Client PSO

Production and Sourcing Optimization Compound Workspace

UI Production and Sourcing Optimization Compound Workspace

PRODUCTION AND SOURCING OPTIMIZATION COMPOUND WORKSPACE

PSO

Production and Sourcing Optimization Cost Metrics

UI Production and Sourcing Optimization Cost Metrics

Stategy Cost Metrics

PSO

Production and Sourcing Optimization Flexible Editor

UI Production and Sourcing Optimization Flexible Editor

PRODUCTION AND SOURCING OPTIMIZATION FLEXIBLE EDITOR

PSO

Production and Sourcing Optimization Geo Map

UI Production and Sourcing Optimization Geo Map

Production and Sourcing Optimization Geo Map

PSO

Production and Sourcing Optimization Model Management

UI Production and Sourcing Optimization Model Management

Production and Sourcing Optimization Model Management

PSO

Production and Sourcing Optimization Plan Analysis

UI Production and Sourcing Optimization Plan Analysis

Production and Sourcing Optimization Plan Analysis

PSO


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Supply Chain Network (Fulfillment)

UI Supply Chain Network (Fulfillment)

FF Bill of Materials FF

Supply Chain Network (IPO)

Supply Chain Network (IPO)

IPO Bill of Materials

IPO

Supply Chain Network (Master Planning)

UI Supply Chain Network (Master Planning)

MP Bill of Materials Workbench

MP, ESP

Target Manager UI Target Manager Target Manager Dmd Transfer Forecast Process Transfer Forecast Forecast Transfer

Process Dmd,

FF, MP, IPO

Transfer History Process Transfer History History Transfer FF, MP, IPO

Transfer Planned Order to Sequencing

Process Transfer Planned Order to Sequencing

SEQINT EXPORT TO SEQUENCING

MP, ESP

Transfer Scheduled Receipts from Sequencing

Process Transfer Scheduled Receipts from Sequencing

SEQINT IMPORT FROM SEQUENCING

MP, ESP

Transfer Seasonality Profiles

Process Transfer Seasonality Profile Process

Transfer Profile Process

Dmd

Unconstrain Demand Process Unconstrain Demand Process

Unconstrain Demand Process

Dmd Unconstr

Verify DFU Maps Process Verify DFU Maps Process

Verify DFU Maps Process

Dmd, DMF

Price Analysis Workbench

UI Precision Pricing Analysis Workbench

PrecisionPricing.PriceAnalysisWorkbench

X SP


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Run MRM Experiments

Process Run MRM Experiments

DRM.ExecuteMRMExperiments

X MDO, PM, Dmd Decomp

Compress Events Process Compress Events Process

Demand.CompressEvents

X Dmd

Demand Decomposition Flexible Editor

UI Demand Decomposition Flexible Editor

DEMAND DECOMPOSITION FLEXIBLE EDITOR

X Dmd

Expand Calendar Process Expand Calendar Process

Demand.ExpandCalendarProcess

X Dmd

Merge Forecast Process Merge Forecast Process

Demand.MergeForecast

X Dmd

Move History Process Move History Process

Demand.MoveHistory

X Dmd

NPI By Sequence UI NPI By Sequence Demand.NPIBySequence

X Dmd

Import Offers Process Promotions Management Import Offer Process

PromotionsManagement.PromoOfferImportProcess

X PM

Input Data Integration

UI Input Data Integration

INPUTDATAINTEGRATION

X PSO

Output Data Integration

UI Output Data Integration

OUTPUTDATAINTEGRATION

X PSO

LoadManager Workbench

UI Fulfillment LoadManager Workbench

LoadManagerWorkbench

X FF

Identify and Analyze Root Causes

Process Identify and Analyze Root Causes

SCPOWeb.IdentifyandAnalyzeRootCauses

X Flowcasting


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Prescriptive Scenario Analyzer

UI Prescriptive Scenario Analyzer

Flowcasting.PrescriptiveScenarioAnalyzer

X Flowcasting

Copy Measure Data Process Copy Measure Data

Copy Measure Data

X Dmd

MeasureMaintenance UI Measure Maintenance

Measure Maintenance

X Dmd

DemandWorksheet UI Demand Worksheet

Demand Worksheet

X Dmd

Demand Worksheet Commit

Process Demand Worksheet Commit

Demand.WorksheetCommit

X Dmd

Demand Planning Report Demand Planning Report Template

X ESP

Compute Connected Network

Process Compute Connected Network

Compute Connected Network

X MP, ESP

SUPERSESSION support in Calculate Master Plan process

Function X MP, ESP


Process X ESP

Generate Master Plan (MAP)

Process X ESP

Generate Master Plan (LpOpt)

Process X ESP

Map DFUs Subset Process Map DFUs Subset Process

Map DFUs Subset X Dmd

NPI by Priority Process NPI by Priority Process

NPI By Priority X Dmd


Implement security




New in

7.5.2.0

New in

7.6.0.0

New in

7.7.0.0

New in

7.8.0.0

New in

8.0.0.0

New in 8.1.0.0

Product Name

Configure Demand SalesConnect

UI Configure Demand SalesConnect

Demand Mobile Workbench Properties

X Dmd

Dashboard UI Dashboard Dashboard X Dmd, FF

Dashboard Manager UI Dashboard Manager

Dashboard Manager

X SCPO

Collaboration Workbench

UI Collaboration Workbench

Collaboration Workbench

X Flowcasting

New Product Intelligence

UI New Product Intelligence

New Product Intelligence

X Flowcasting


Implement security

Entity Resources Following are the entity resources added that are necessary to add ACLs for new features.

UI/Process/Function Type Product Name NPIToDFUExpression Entity Dmd NPIToDFU Entity Dmd NPIFromDFUPriority Entity Dmd NPIDFUError Entity Dmd HistTransPlan Entity FF HistTransActual Entity FF SKUClass Entity FF SKUClassDefinition Entity FF SKUClassDefinitionDetail Entity FF SKUClassOptions Entity FF AllocLikeLocParam Entity FF AllocAggFcst Entity FF SkuEffInventoryParam Entity ESP AltBom Entity ESP AltProductionStep Entity ESP IPlayer Entity ESP Lpdmdbands Entity ESP SchedRcptsDetail Entity ESP CalPattern Entity ESP CalAttribute Entity ESP SsBand Entity ESP PromoCoupon Entity PM

Filters Filters allows you to restrict access to data based on the content of the columns in the databases. They allow you to enforce data-level or row-level security. Filters are assigned to a specific role using an ACL.

Filters restrict the information included in any list of data, including the data accessed by searches and Flexible Editor (FE) pages. If you have a field into which you can type data, such as a prompted search, the filters do not restrict you from entering that data. However, if the entered data meets the filter's restriction criteria, you cannot see the data you entered. In other words, filters do not restrict insertions into the database, but they restrict viewing of that data.

SCPO security features You can control the ability to perform activities within SCPO by setting the create, read, update, delete, and execute properties of the resources needed to perform the activity. For example, to add a new DFU to JDA Demand, use the DFU Maintenance page. To complete this activity, you must have update and read privileges for the DFU Maintenance resource.

The following table lists the primary features in SCPO, their related resources, and the security privileges required to perform certain activities.


Implement security

Note: For all resources, if a user has create, update, delete, or execute privileges, it is implied that the user also has read access to that resource.

Primary SCPO security resources

Feature Resource Description

SCPO SCPOWeb Assigned to any role given access to the application.

Application access

Application resource, for example SCPOWeb.Demand or SCPOWeb.Strategy

Assigned to any role given access to the application.

Import data Flexible Editor Import and appropriate table resources

Must have execute access on the Flexible Editor Import resource and create access on the resource for the table into which you want to import data.

Export data Flexible Editor Export and appropriate table resources

Must have execute access on the Flexible Editor Export resource and read access on the resource for the table from which you want to export data.

Private custom instances of application pages

Directory Manager and appropriate feature resources

• Must have create access on feature resource to create a page or edit the page's properties. If you have create access on a feature, you automatically have update and delete access.

• Must have read access to the applicable feature resource to view the page from the directory.

• Must have execute access on the Directory Manager resource to create or delete custom instances.

Private custom instances of FE pages, compound workspaces, and searches

Directory Manager and appropriate table

• Must have create access on the appropriate table to create a page based on this table or to edit the page's properties. If you have create access on a table, you automatically have update and delete access for the FE pages, compound workspaces, and searches based on the table.

• Must have read access to the applicable table resource to view the page from the directory.

• Must have execute access on the Directory Manager resource to create or delete custom instances.


Implement security


Public instances of application pages, FE pages, and compound workspaces

Directory Publishing plus resources listed above

These pages work the same as the private custom instances of application pages, FE pages, compound workspaces, and searches described earlier in the table, with the following exception: In addition to having access to the Directory Manager resource, users must also have execute access on the Directory Publishing resource to make the page available to other users.

Database tables Appropriate table resource

• New tables cannot be created or deleted in the SCPO database.

• Create access is required for users to add data to a table, including to copy existing rows. It is also required to allow users to add custom instances of pages based on that table.

• Read access is required for users to access pages from the directory. Read access to a table also allows users to reset the page, add comments, view graphs, view statistics, apply column filters, peg into lower level data, and export information.

• Update table access is required to edit data, including global edits and to save data in any Flexible Editor page. Update access to the tables is also required to edit data in any application page.

• Delete access is required to remove data from a table.

• Create and update access are required to import data into a table and to perform Many to Many copies in a Flexible Editor page.

Processes Appropriate process resource

• Execute access is required to run any process, either through the UI or in batch. For more information on batch, see Run batch processes.

• Create access allows a user to create new option sets.

• Read access is required to view the process from the directory.

• Update access allows a user to edit the process option sets, as long as the user is the original owner of the option set.

• Delete access allows a user to delete a process option set, as long as the user is the original owner.

Note: Only the user who created the original option set can edit or delete the option set.


Implement security


Process Chains Process Chaining • Create access is not required to add a process chain. However, when a user adds a process chain, the Process Chains page displays only processes, option sets, searches, and scenarios that the user has permission to access.

• Delete access is required to delete a process chain.

• Execute access is required to run a process chain.

Scenarios Planning Scenarios

• Create access is required to create new scenarios.

• Read access only allows a user to view the scenario settings.

• Update access allows a user to edit the scenario definition, as long as the user is the original owner.

• Delete access allows a user to delete a scenario, as long as the user is the original owner.

• Execute access is required to load data into the simulation tables.

Note: Only the user who created the scenario can edit and delete it.

In addition, a Scenario_Commit resource is available for Production and Sourcing Optimization users. A user must have Execute access on this resource to commit scenarios to the database.


Implement security


Application features, such as Buyer Planner Workbench, Plan Analysis, Master Planner Scorecard, Model Manager, Demand Workbench, Markdown Workbench, or Promotions Management Workbench

Appropriate feature resource

• JDA Production and Sourcing Optimization users must have create, read, update, and delete permissions on all tables related to a specific tab in order to access that tab. If the user does not have all four permissions set for every required table, the user has only read access to that tab.

• Users must have create access on the tables associated with the feature in order to insert new data into the table. In addition, create access for a feature resource is required to create a custom instance of any page associated with the feature or to edit a page's properties. For JDA Demand, only update access to the feature is required to create data through the application pages. Similarly, for JDA Promotions Management and JDA Markdown Optimization, update access to the Promotion Management Workbench or Markdown Workbench feature automatically provides create access. However, unlike in Demand, create access to the appropriate tables must explicitly be assigned to the user.

• Read access is required to access the page from the directory.

• Users must have update access for the table associated with the feature to edit data on the page. In JDA Demand, update access to feature-related tables is granted automatically when a user is granted update access to a feature. In other applications, a user must be granted update access for both the feature resource and the related table resources. In addition, in Demand, Promotions, and Markdown, having update access automatically gives a user create, delete, and execute access to the feature.

• For most applications, users must have delete access for both the application page and the appropriate table resource to delete information in an application page. For JDA Demand, only update access to the feature is required to delete data through the application pages. For JDA Promotions Management and JDA Markdown Optimization, update access to the Promotions Management Workbench or Markdown Workbench feature automatically provides delete access. However, unlike in Demand, delete access to the appropriate tables must explicitly be assigned to the user.

• Users must have execute access for application features if they are to run any processes and calculations associated with the page.


Implement security


Promotions and Markdown Workflow features, such as approval, optimization, evaluate, publish, and override

Appropriate resource feature

These feature resources determine the menu options and other fields available on various JDA Promotions Management and JDA Markdown Optimization pages. They allow you to control the type of activities a user can perform within a specific page. To view the options associated with each resource or to perform the associated activity, such as publishing a promotion, the user must have execute access to the feature. Create, read, update, and delete permissions are ignored for these resources.

Encrypt the SCPO schema owner's password If the option to force_password_encryption is true in System Properties, you must encrypt the SCPO schema owner's password, which is stored in dbconnections.properties. The password is stored in plain text by default, but you can use the command line utility genEncryptedPassword to generate an encrypted password. You can find the utility at <install_dir>\config\properties.

1. Shut down any node pools started from the JDA Platform Server or SRE instance.

2. Using genEncryptedPassword, generate an encrypted version of the password used to access the schema. For example, if the password is scpomgr, then this is the password you enter to encrypt, as follows:

genEncryptedPassword scpomgr

3. Open dbconnections.properties in a text editor. The file contains a password property similar to the following:

Password:scpomgr

4. Replace the plain text password with the encrypted password. For example:

Password:{E:DESede}325c93c0da5dd5b93ahc12b7780175e

Note: The prefix {E:DESede} is necessary when property force_password_encryption is false in System Properties.

5. Save dbconnections.properties and exit the text editor.


Customize and maintain the database

Chapter 4. Customize and maintain the database This chapter is intended for administrators responsible for customizing the Supply Chain Planning and Optimization (SCPO) database based on the installations specific needs. The chapter also describes tasks associated with maintaining the database.

The chapter assumes that you have a working knowledge of the operating system and Oracle database management software. For more information see "Hardware and Software Requirements' in the JDA Platform Release Notes.

You should also be familiar with the basics of using the SCPO product, including Flexible Editor (FE) pages, processes, and searches. For information on these features, see the online help.

Common database tables Most tables in the database are specific to a particular component (such as JDA Demand or Fulfillment), but certain tables are common to all installations that are part of the SCPO schema, regardless of the installation's specific subcomponent configuration. These tables comprise the core database. The core database includes the following tables:

• DBParam

The DBParam table contains configuration settings for the SCPO application. To modify the settings, see Edit the DBParam table (on page 5).

• Cal

• CalData

• Loc

For more information on the remaining tables in the database, see the Supply Chain Planning and Optimization Reference Help for the applications for which you are licensed.

Manage tables and columns You can manage JDA application tables and columns using the Data Model Manager. This lets you perform the following database management tasks:

• View table and column attributes

• Modify table attributes, such as the Header (Display Name) and table description

• Modify selected column attributes

• Create user-defined columns

Note: You cannot view data stored in the schemas using Data Model Manager.

You must configure the application schemas before using the Data Model Manager. In addition, you must have resources assigned in the Security module to use the Data Model Manager. See the Data Model Manager online help for more information.

Administer user-defined tables and user-defined columns Users can customize the database by adding user-defined tables (UDTs) and user-defined columns (UDCs) to a table in the schema. You can add UDTs using Oracle utilities, and UDCs using the Data Model Manager. UDTs and UDCs are useful for storing custom data.

JDA application software cannot use a UDT. However, you can enroll the UDT with JDA Platform. Enrolling means that you create metadata for the UDT. This metadata enables Flexible Editor, Data Model Manager, and Searches to use the table. JDA Supply Chain Planning and Optimization Configuration Guide 40 © 1997-2014 JDA Software Group, Inc.- Confidential

Customize and maintain the database

See the Data Model Manager online help for procedures on creating a UDC. See "Configuring the JDA Platform Server" in the JDA Platform Installation/Administration Guide for information on creating and enrolling UDTs.

Each time you update the schema using the Data Model Manager, you must rerun the IGPXMLGenerator utility and the Interface Generation Program (IGP) before you can import data. See Import data in the JDA Platform Common Concepts Reference Guide and the IGP chapter in the JDA Platform Interface Generation Program Reference Guide.

Maintain existing databases The specific tasks involved in maintaining SCPO may vary among installations, but every installation must carry out certain general tasks on a regular basis.

Copy databases You can copy a database by using Oracle's export capability. You export the database, then reimport it to another database. See your Oracle documentation for information on performing this task.

When you copy a database, be sure that the level of the database you are copying matches the system you are using. In addition, be sure to import the data into the new database using the SCPO schema owner. Always ensure that the JDA Foundation schema and SCPO schema stay in sync with each other.

Edit tables and columns You can edit database tables and columns using the JDA Platform Data Model Manager. See the OnLine Expert for more information.

Delete tablespaces You can delete a tablespace/database using Oracle's server manager utility or DBA Studio. See your Oracle documentation for information on performing this task.

Before deleting a tablespace, make sure no users are using the database, and shut down the JDA Platform Server.

Back up and restoring databases The database administrator at your installation typically implements procedures for backing up data on a regular basis and recovering a database from a backup in the event that the database is damaged.

For information on restoring a database in a UNIX or Windows environment, see your Oracle documentation.


Configure JDA Demand

Chapter 5. Configure JDA Demand Perform specific configuration tasks before you can use the system:

Set up hierarchies You can use a hierarchy within the database to impose a structure on the data that can be used to group and aggregate forecast and planning data. This feature allows you to impose hierarchical relationships among data contained in one column without changing the underlying data.

You can use hierarchy levels in the search criteria to view specific sets of data easily. In JDA Demand, you can use the hierarchy data as part of the data aggregation and forecast reconciliation processes. To use hierarchies, you must first create the overall hierarchical structure, including all hierarchy levels. Next, you must populate the hierarchy by assigning entries to the various hierarchy levels.

You can create a hierarchy for any column of text data (including user-defined columns) in the following tables:

• DFU

• DmdGroup

• DmdUnit

• Item

• Loc

• SKU

After you have created a hierarchy, you can perform various maintenance activities, including deleting hierarchies, adding and deleting hierarchy levels, and adding and deleting entries.

See the JDA Demand online help for more information.


Customize the Demand DSW Several parts of the JDA Demand Decision Support Workbench (DSW) can be customized by modifying configuration files. These modifications require detailed knowledge of the Demand Decision Support Workbench Architecture, and should be changed only with the support of JDA Implementation Services. Contact JDA Customer Support Solutions office for more information. They can help coordinate the consulting resources required onsite at your location.

Supported Network Environments for the Demand DSW The Demand Decision Support Workbench provides a highly interactive user interface environment to evaluate and tune forecasts. The technology used to provide this environment is a Java applet. The Java applet provides a high degree of interactivity for the user. While it is deployed in a browser, the applet uses a different protocol to communicate with the application server than the standard HTTP protocol typically used in a Web-based application. The protocol used is Java RMI, which provides an efficient means for a Java client application such that the DSW applet to communicate with the application server.

The DSW environment is intended to be used within a corporate network environment. Because of the nature of the interaction between the DSW applet client and the application server, the network environment must meet several criteria for the application to function properly:

• The network must provide a high bandwidth link.



Low bandwidth links result in slow performance/responsiveness

• The network must not have high latency.

High latency links result in slow performance/responsiveness.

• There should not be a firewall or proxy server between the DSW client and the application server.

Firewalls and/or proxy servers in many instances do not correctly forward the RMI protocol between the client and the server. Firewalls and proxy servers are typically configured to only allow HTTP protocol traffic.

Memory considerations for Demand DSW The Demand DSW complements the existing HTML-based Demand Workbench with a highly interactive applet based interface. The interface requires that you download or install several components depending on the application server that is used on the server. The download of the JDA client JAR automatically occurs the first time the Demand DSW is accessed. If accessing a WebLogic server and you already have a version of the Java Plug-in that is different from the requirement for Demand DSW, see "Updating the Java Plug-in version" in the Java Plug-in Guide (http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guide/contents.html).

The Demand DSW is a client-side applet, so the memory settings on the client PC are important. The Java Plug-in has default settings for minimum and maximum memory.

In general, minimum settings need not be modified. However, the following section needs to be considered when tuning for memory consumption of the Demand DSW applet.

Tune memory consumption settings for Demand DSW There are three areas to consider when tuning for memory consumption of the Demand DSW applet. The first consideration is the Java™ Plug-in maximum memory setting. The second consideration is the number of DFUs retrieved and managed in each data selection. The third consideration is the management and display parameters selected on the Demand DSW page.

Tune the Java Plug-in maximum memory setting The default maximum memory setting for the Java Plug-in is 64 MB. This parameter is sufficient for a basic implementation with few DFUs selected. However, JDA strongly recommends that the maximum memory setting be raised to at least 1024 MB. This parameter may need to be raised even higher based on the configuration of the workbench. Local administrators should monitor client usage to determine the optimum setting. Administrator might want to raise the maximum memory setting if users encounter "Out of Memory" errors or the client hangs on large operations.

The DSW brings data from the server to the local Java Virtual Machine (JVM) to avoid network delays in interacting with data associated with a DFU, thus providing a very responsive environment to evaluate and adjust forecast models. The amount of memory on the client is limited, so by default the maximum number of DFUs returned by the search mechanism in the DSW is 1000. This is found as a reasonable number for most environments and data configurations. However to return more than 1000 DFUs in the search, maximum memory should be set to the one fourth of the Client PC memory.

The amount of memory consumed by the DFUs brought back to the client varies, according to the amount of memory available within the JVM in the Java Plug-in. The amount of memory available for the JVM can be configured (see Steps for setting the maximum memory setting). The amount of memory used by the DFUs varies based on forecast periodicity (that is, a weekly calendar consumes more memory than a monthly calendar), length of history stored, and forecast horizon used.


http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guide/contents.html



The JVM size which may be configured for the Java Plug-in for Internet Explorer varies, and is dependent on the amount of contiguous memory available when the JVM is initialized. Because of this limitation in JVM size, care must be taken when increasing the limit beyond on the number of DFUs returned by the search in DSW. Available memory can be exhausted in the JVM, which leads to an “out of memory” condition in Java, which further can cause freezing of the browser UI.

In order to raise the memory settings on the Java™ Plug-in the -Xmx parameter is set in the Java Runtime Settings of the Java Applet Runtime Settings. See section "Setting the maximum memory setting (-Xmx) for the Java Applet Runtime Settings" for more information.

You may also find that the following settings on the Java are helpful in diagnosing issues in a Weblogic configuration:

1. -verbosegc -XX:+PrintGCDetails : Displays a separate console window when the Java™ Plug-in starts listing information about the Java memory usage and garbage collection occurring.

2. -Dcom.sun.management.jmxremote: Allows connection to the process via the java console.

For further information see the Java Plug-in Guide (http://java.sun.com/javase/6/docs/technotes/guides/plugin/developer_guide/contents.html).

Setting the maximum memory setting (-Xmx) for the Java Runtime Environment Settings in a WebLogic configuration:

1. Open the Control Panel from the Start menu.

2. Double-click Java to view the Java Control Panel.

3. Select the Java tab on the Java Control Panel.

4. Select View under Java Runtime Environment Settings.

5. Double-click the Runtime Parameters field to edit it.

6. Add the parameter -Xmx512m -Xmx1024m. This increases the maximum memory to 1024 MB.

Note: If you have existing parameters in this field, add this parameter to the list. If you already have the -Xmx parameter in the list, ensure it is set to at least 1024 MB.

7. Click OK on each dialog box until you return to the Control Panel.

8. Close all open browser windows, then restart your browser and access the Decision Support Workbench.

Setting the maximum memory setting (-Xmx) for the Java Applet Runtime Settings in a WebSphere configuration:

1. Open the Control Panel from the Start menu.

2. Double-click Java to view the Java Control Panel.

3. Select the Java tab on the Java Control Panel.

4. Select View under Java Applet Runtime Settings.

5. Double-click the Java Runtime Parameters field to edit it.

6. Add the parameter -Xmx512m -Xmx1024m. This increases the maximum memory to 1024 MB.

Note: If you have existing parameters in this field, add this parameter to the list. If you already have the -Xmx parameter in the list, ensure it is set to at least 1024 MB.

7. Click OK on each dialog box until you return to the Control Panel.

8. Close all open browser windows, then restart your browser and access the Decision Support Workbench.





Manage the number of DFUs retrieved and managed in each data selection The Demand DSW uses a lazy load data approach that attempts to maximize moving between DFUs at the expense of additional overhead on the first load of a data selection. This means that the basic information needed to display a DFU is loaded for each DFU when the data selection is run. As each DFU is accessed, additional information is loaded specific to that DFU. In addition, the Demand DSW allows users to make multiple changes before saving, and the changes are cached in the Demand DSW memory until a save is performed.

In order to help manage the size of data returned by data selections, JDA provides a system-wide parameter to limit the number of DFUs returned to the Demand DSW interface, regardless of the size of the data selection. The appropriate setting will vary based on end user needs, but also in relation to the amount of data being displayed for each DFU. In general, the more data configured to display and the longer the time horizons, the fewer DFUs that can be selected for a specified Java™ Plug-in maximum memory setting.

Note: To configure the data settings, contact the JDA Consulting Services Group.

In addition, users should be encouraged to save their work after logical units are completed. This task helps ensure that they do not consume more than the available memory. If users must make many changes between saves and find they have out of memory issues, the maximum memory should be adjusted accordingly.

Memory impact of management and display parameters selected on the Demand DSW page The Demand DSW interface was designed to be highly configurable at both the system and individual user levels. Therefore, the more data elements and longer time horizons that are chosen for display, the more client memory is required.

JDA recommends that commonly used data should not be limited in display, unless a specific problem occurs. If the problem occurs, restrict your search and use the data which is necessary. However, rarely used data should be closely examined before configuring for display. Likewise, if memory issues occurs, rarely used data that is easily available in another page should be removed from the default configuration.

These recommendations apply not only due to client memory considerations, but also due to the network traffic and consequent response time delays that occur to retrieve rarely used data.

Enable user-defined data streams The standard installation of JDA Demand does not include the ability to use the User Defined Data Streams feature. The feature must be enabled before you can start using it.

1. Shut down the server.

2. Open a command line prompt.

3. Change to directory <install_dir>\config\database\scpoweb\demand.

4. Run PKG_Dmd_UserDefinedDataStream.sql as the Foundation schema owner, using the following syntax:

sqlplus wwfmgr/wwfmgr @PKG_Dmd_UserDefinedDataStream.sql

5. Restart the server.

Create user-defined data streams 1. Shut down the server.

2. Open a SQL Editor instance, then connect to the Foundation schema as the schema owner.

3. Run Add_UserDefinedDataStream command using the following syntax:

EXEC PKG_Dmd_UserDefinedDataStream.Add_UserDefinedDataStream('name', 'desc', 1); JDA Supply Chain Planning and Optimization Configuration Guide 45 © 1997-2014 JDA Software Group, Inc.- Confidential


• 'name' is the name of the Data Stream, it si stored in upper-case by the system, regardless of the case in which it is entered.'desc' is the description of the Data Stream

• 0 / 1 indicates the editable status of the Data Stream row in the Demand Decision Support Workbench. 1 indicates that the row values can be edited; 0 indicates that the row is read-only


Update user-defined data streams Note: You can modify only the description and editable status of an existing User Defined Data Stream. To change the name of an existing User Defined Data Stream, you must delete the Data Stream and then create a new one using the new name.


2. Open a SQL Editor instance, then connect to Foundation schema as the schema owner.

3. Run Update_UserDefinedDataStream command using the following syntax:

EXEC PKG_Dmd_UserDefinedDataStream.Update_UserDefinedDataStream('name', 'desc', 1);

• 'name' is the name of the Data Stream to be updated

• 'desc' is the updated description of the Data Stream

• 0 / 1 indicates the editable status of the Data Stream row in the Demand Decision Support Workbench. 1 indicates that the row values can be edited; 0 indicates that the row is read-only.


Delete user-defined data streams 1. Shut down the server.

2. Open a SQL Editor instance, then connect to Foundation schema as the schema owner.

3. Run the Delete_UserDefinedDataStream command using the following syntax:

EXEC PKG_Dmd_UserDefinedDataStream.Delete_UserDefinedDataStream('name');

where 'name' is the name of the Data Stream to be deleted


Note: Deleting a User Defined Data Stream does not automatically delete the corresponding data from the DFUExternalFcst table. You must delete the records manually using Flexible Editor.

Demand Worksheet RMI service JDA Demand Worksheet allows you to run the Multi-Dimensional Analysis and Planning (MDAP) architecture. These business functions are handled by the Demand Worksheet RMI SRE service. This service runs constantly using the continuous Lockable RMI SRE service, awaiting requests for various business functions on a user by user basis. For more information on Lockable RMI SRE services, see the JDA Foundation Administration OnLine Expert.

You must ensure that the Demand Worksheet RMI service, which is running in the SRE_NODE_POOL server and configured for the role associated with the Demand Worksheet users. For more information, see the JDA Foundation Administration OnLine Expert.

For more information on how to configure the user’s role to this service, see the Common user interface controls section in the JDA Foundation Administration OnLine Expert.

Note: One SRE Node is dedicated to only one user for Demand Worksheet Lockable RMI Service. For multiple users to use the service, configure multiple SRE nodes for this service and dedicate appropriate memory in the box where nodes are running. JDA Supply Chain Planning and Optimization Configuration Guide 46 © 1997-2014 JDA Software Group, Inc.- Confidential


A parameter is added to the Multiple_jobs_demandWorksheet_RMI.bat utility that allows multiple users to run the continuous job the number of times specified.

Usage:

Multiple_jobs_demandWorksheet_RMI.bat wwfuser wwfpswd no.of.jobs

This is used to create multiple continuous jobs for the Demand.WorksheetRMI service so that each node is assigned the number of jobs specified.

For example:

Multiple_jobs_demandWorksheet_RMI.bat wwfmgr wwfmgr 10

Set up dashboard for Demand Planner After you install JDA Demand, perform the following steps to set up the dashboard for Demand Planner:

1. Create a hierarchy using Hierarchy Manager if you do not have required hierarchies defined.

2. Assign a default hierarchy ID to a persona using the following steps:

a. Select a value from MD_Hierarchy:Hierarchy_ID in the Foundation schema for the required dimension name and hierarchy name.

b. Update Persona:DefaultHierarchyID in the SCPO schema with the same value you selected in MD_Hierarchy:Hierarchy_ID, for the persona.

3. After the default hierarchy ID is defined, perform the following steps in Dashboard Manager:

a. On the Manage Users tab, assign a user to a persona and default search.

Note: You must create a search in Search Manager.

b. On the Manage Goals tab, assign values to the goal metrics for a level in the selected hierarchy.

c. On the Manage Widgets tab, create group-by options to group and display data in the widgets.

d. On the Manage Workflows tab, create navigation links, if required, to which the planner can navigate from the analysis page.

Note: For more information on Dashboard Manager, see the SCPO General Systems OnLine Expert.

Use the Demand reports in CDS environment To use the Demand reports (Waterfall and Performance) in CDS environment:



3. Change to the directory <install_dir>\config\database\scpoweb\demand.

4. Run PKG_convert_CDS_to_classic.sql as the SCPO schema owner, using the following syntax: sqlplus scpomgr/scpomgr @PKG_convert_CDS_to_classic.sql


For more information on CDS, see Compressed Data Storage (on page 113).

If you are using CDS for your FCST and HIST data, follow these steps before running the post installation steps for Reporting:



1. Open the <install_dir>\config\reports\models directory.

2. Delete the demand folder.

3. Copy the demand_wide folder from the <install_dir>\install\reporting\reports\models directory to the <install_dir>\config\reports\models directory.

4. Rename the demand_wide folder to demand.

5. Open the <install_dir>\config\reports\deploymentPackages directory.

6. Delete the Demand.zip file.

7. Copy the Demand_wide.zip file from <install_dir>\install\reporting\reports\deploymentPackages directory to the <install_dir>\config\reports\deploymentPackages directory.

8. Rename the Demand_wide.zip file to Demand.zip.


Configure JDA Fulfillment

Chapter 6. Configure JDA Fulfillment Specific configuration tasks must be performed before the system can be used.

.Net UI Common Properties A setting in SCPO properties determines the behavior of dynamic navigation for the two .Net based workbenches (Replenishment Workbench and Load Manager Workbench). This setting ‘Use Existing Tab’ tells the system how to navigate within the Rich UI Shell into either of the two workbenches which may already be open within the shell.

If ‘Use Existing Tab’ is selected, and the workbench you are doing a dynamic navigation to is already open in an existing tab in the Shell, the system will not open another tab for that workbench. The system will update the existing tab with the new data.

If ‘Use Existing Tab’ is deselected and the workbench you are doing a dynamic navigation to is already open in an existing tab in the Shell, the system will open a new tab for the workbench.

Only .Net UIs would be displayed in the tabs within RichUI Shell. Any dynamic navigation from .Net UIs to Web UI pages, they would be opened up in a tab in Web UI only.

Deploy Load Manager Workbench The Load Manager Workbench instances appear on the directory listing. For information on deploying the Load Manager Workbench, see ".NET UI Framework Installation and Deployment" chapter in the JDA Platform Installation/Administration Guide. If you have not deployed Load Manager Workbench, and if you try to open the instance from the directory listing, an error will occur.

Notes:

• You need to install .NET on your system to use Load Manager Workbench. See JDA Platform Release Notes for the supported .NET version.

• Thin load manager instances are also created for the Load Manager workbench when you run the SCPO Migration scripts.

Migration of Load Manager instances to the Load Manager Workbench To create new Load Manager Workbench instances based on existing Load Manager Instances, run the migrate_LM_to_LMWB.bat script:

1. Specify the Oracle_SID.

2. Set the Oracle bin path.

3. In the <install_dir>\config\database\scpoweb directory, using SQL*Plus, run migrate_LM_to_LMWB.ksh (UNIX) or migrate_LM_to_LMWB. bat (Windows) script as the JDA Foundation schema owner using the following syntax:

UNIX:

migrate_LM_to_LMWB.ksh <wwfuser> <wwfpassword> <scpouser> <scpopassword>

Windows:

migrate_LM_to_LMWB.bat <wwfuser> <wwfpassword> <scpouser> <scpopassword>

This script creates new Load Manger Workbench instances with the name of the Load Manager instance with the suffix "--Migr_LMWB". You can either migrate properties, if possible, or use the default values in Load Manager Workbench instances. In Load Manager, the general tab, Recship tab, Vehicle Load tab properties are migrated to Load Manager Workbench instance properties.



Note: Make sure you run this script only after you have completed migrating the database to 8.1.0.0.

Order Optimization User Interface The Order Optimization User Interface enables you to approve, recalculate, or delete an Order, create a provisional Order, and change or clear an SKU’s SOQ.

All these actions are handled by the OrderBuilderRMI SRE service option. By default, this service runs as a single continuous job on the Basic node pool.

The configuration of OrderBuilderRMI may need to be adjusted based on the number of users and the actions they perform.

Order Optimization Online Services JDA Fulfillment Order Optimization allows you to run different business functions while viewing Order or SKU data from the Order Search, Order Details, Order SKU Search, and Order SKU Details pages. These business functions are handled by the OrderBuilderRMI SRE service. This service runs constantly, awaiting requests for various business functions. All the business functions that you request are handled by this service. For more information on the OrderBuilderRMI service, refer to the General SCPO manual.

Business functions Business functions for Order Optimization are summarized below:

Approve Order The business function of this service is to mark an Order and its vehicle loads as approved, so that, they can be exported to an external system. If an Order does not have vehicle loads, this service creates them.

This service always runs synchronously, that is, you must wait until the service completes the request before you can perform anything in the User Interface.

Recalculate Order The business function of this service is to recalculate an Order.

If an Order has fewer SKUs than the number of SKUs specified in the Max Order SKUs to recalculate through the Recalculate Interactively property on the Order Details page, this service runs synchronously. That is, you must wait until the process is complete before you can perform any task in the User Interface. Otherwise, a request is submitted to the batch SRE Order Optimization process for all SKUs that belong to a network or Order Group/Order Group Member. A message is displayed when the process is complete, but you may continue with other activities simultaneously.

Create Provisional Order The business function of this service is to calculate a new unapproved Order for the same network or an Order Group or an Order Group Member that possess an approved Order. The logic is the same as the batch Order Calculation process.

If an Order has fewer SKUs than the number of SKUs specified in the Max Order SKUs to recalculate through the Recalculate Interactively property on the Order Details page, then this service runs synchronously. That is, you must wait until the process is complete before you can perform any task in the User Interface. Otherwise, a request is submitted to the batch SRE Order Optimization process for all SKUs that belong to a network or an Order Group or an Order Group Member. A message is displayed when the process is complete, but you may continue with other activities simultaneously.



Change SOQ/Clear SOQ The business function of this service is to edit an SOQ for an individual SKU. This process updates certain fields on the Order SKU record to indicate that the value has been edited. It also makes adjustments to the Order Totals and Vehicle Loads to account for the change in the SOQ.

This service always runs synchronously. That is, you must wait until all the process is complete before you can perform any task in the User Interface. If multiple requests are issued from the Order SKU Search page, then you must wait until all SKUs have completed processing.

Delete Order The business function of this process is to delete an Order from the database.

This service always runs synchronously. That is, you must wait until the process is complete before you can perform anything in the User Interface.

Constrained Supply Online Actions This section explains how constrained supply has been incorporated into the use of the online actions such as Recalculate Order, Change SOQ, and Approve order.

Recalculate Order The recalculate order action is used to reprocess an order after changes are made to the order that have affected the SOQs or made it necessary to rebuild the loads associated with the order. The recalculation occurs for a single network or order group. This can conflict with constrained supply because a vendor SKU can supply dozens of DCs or hundreds of stores. This is easily handled in the Optimize Orders process but it is not handled by the recalculate order action.

When the user recalculates an order that has been impacted by constrained supply, the SKUs that are constrained at the source are locked and the SOQ is not changed by the recalculation. This ensures that the SOQ across all locations does not exceed the supply at the vendor. You can identify the locked SKUs by using the Source Inventory Status (OrderSKU: SourceInvStatus). The three values for this column are Unconstrained (1), Constrained – no source supply available (2), and Constrained – limited source supple available (3). When the SourceInvStatus is 2 or 3 then the SKU is locked during recalculation.

If you have made a change that requires reallocating the source supply or overall calculating a new SOQ for those SKUs then you need to run the Optimize Orders process for all the locations supplied by the constrained source. This may be necessary if the user has called the vendor and negotiated more supply.

Change SOQ In some cases, when you disagree with the allocation recommended by the system, you can override the allocation using the change SOQ action. The constrained SOQ (ConstrSOQ) continues to hold the system allocated quantity so you can refer to the original system SOQ. However, if you want to lock the changed SOQ and reallocate the remaining vendor supply to other locations then you must run the Optimize Order process. In this case, the process runs with the Keep User Adjustments option set to Yes. This locks the user overrides and reallocates the remaining vendor supply to other locations.

Approve Order The approve order process is used to mark orders, vehicle loads and supplemental orders as approved when you approve an order. When a supplemental order is impacted by constrained supply it can be necessary to not change the SuppOrderSKU: Status to Fulfilled.



Forced and ForcedUnrounded supplemental orders are not marked as Fulfilled unless the SOQ can meet those needs. All other supplemental orders within the SuppOrderOUTLDate are marked as Fulfilled even if the SOQ does not cover those needs. The needs will be met by the holdout logic applied on the SuppOrderSKU record. This will ensure that the system continues to adjust the ProjOH and purchase the supplemental order when the vendor has supply to meet the SOQ.

Order Optimization purge obsolete orders When all SKUs are removed from a traditional network or an Order Group, Orders associated with those networks or Order Groups may persist. This situation is more likely to occur during implementation of the new Order Groups feature, as SKUs are moved from traditional networks into Order Groups. The Order Optimization Purge Obsolete Orders feature automatically removes these obsolete orders during the batch process blocking finish.

There is a performance cost associated with this feature. Because of this and since it may not be required (for example, if the order optimization output tables are purged regularly), the feature is turned off by default.

The purging of obsolete orders can be turned-on by setting the SCPO Node configuration property "PurgeObsoleteOrders" to ON.

JDA Fulfillment Replenishment Dashboard Online Services JDA Fulfillment Replenishment Dashboard allows you to run the Multi Dimensional Analysis and Planning (MDAP) architecture. These business functions are handled by the Fulfillment Dashboard RMI SRE service. This service runs constantly using the continuous Lockable RMI SRE service, awaiting requests for various business functions on a user by user basis. For more information on Lockable RMI SRE services, see the JDA Foundation Administration OnLine Expert.

When the MDAP property is enabled, the Global temp table is used to insert data. This table inserts data into Temp tablespace to ensure that in a multi-user environment, there is an adequate table space provided for this feature to work properly.

When MDAP is enabled in the Process Manager page, you must ensure that the Fulfillment Dashboard RMI service is running in the SRE_NODE_POOL server and configured for this user who is running the Fulfillment Dashboard instance. For more information , see the JDA Foundation Administration OnLine Expert.

For more information on how to configure the user’s role to this service, see the Common user interface controls section in the JDA Foundation Administration OnLine Expert.

Note: One SRE Node is dedicated to one user only for Fulfillment dashboard Lockable RMI Service. For multiple users to use the service, configure multiple SRE nodes for this service and dedicate appropriate memory in the box where nodes are running.

JDA Fulfillment Dynamic Allocation

Setup information for Dynamic Allocation You must define Product Hierarchy, Location Hierarchy to use JDA Dynamic Allocation. The product hierarchy is to be defined under the Allocation.Product dimension and the location hierarchy is to be defined under the Allocation.Location dimension.

Define product hierarchy The product hierarchies can be defined based on the attributes defined in the Item table or any other attribute based any other UDTs (User-defined tables) that have 1 to 1 mapping with the Item table. You can define only one product hierarchies for a given database. However, all these hierarchies are defined under the Allocation.Product dimension. JDA Supply Chain Planning and Optimization Configuration Guide 52 © 1997-2014 JDA Software Group, Inc.- Confidential


Define location hierarchy The location hierarchy can be defined based on attributes defined in the Loc table or any other attribute based any other UDTs (User-defined tables) that have 1 to 1 mapping with the Loc table. You can define only one location hierarchies for a given database. However, all these hierarchies are defined under the Allocation.Location dimension. The location hierarchy that needs to be used for viewing the Dynamic Allocation results can be selected in the Pivot properties of the Allocation Workbench – Review page.

Configure AllocMaster table This table is the master table for the Dynamic Allocation feature. This table has a single entry that must be configured before you use this feature. The key columns are:

• AllocationHierarchyName: The product hierarchy to be used by the Dynamic Allocation is configured this column. The hierarchy that is to be configured has to be from Allocation.Product dimension. The column is one time setup. To change the product hierarchy to be used, see Change the Allocation level or hierarchy (on page 53).

• AllocationLevel: The level at which Allocation works. The level refers to the level number from the product hierarchy configured through the AllocationHierarchyName column.

• NumAggHistPeriods: Represents the number of periods in the AllocAggHist table. The default period of this column is 78 periods. Use the following procedure to add or reduce periods:



3. Change to directory <install_dir>\config\database\scpoweb.

4. Run AddorTrim_allocagghist.bat or AddorTrim_allocagghist.ksh as follows:

To add

AddorTrim_allocagghist.bat SCPOMGR SCPOMGR WWFMGR WWFMGR ADD 10

To remove

AddorTrim_allocagghist.bat SCPOMGR SCPOMGR WWFMGR WWFMGR TRIM 10

Note: If you remove a period, the corresponding data will be deleted.


• NumAggFcstPeriods: Represents the number of periods in the AllocAggFcst table. The default period of this column is 26 periods. Use the following procedure to add or reduce periods:



3. Change to directory <install_dir>\config\database\scpoweb\dbpatch.

4. Run addortrim_allocaggfcst.bat or addortrim_allocaggfcst.ksh as follows:

To add

addortrim_allocaggfcst.bat SCPOMGR SCPOMGR WWFMGR WWFMGR ADD 10

To remove

addortrim_allocaggfcst.bat SCPOMGR SCPOMGR WWFMGR WWFMGR TRIM 10

Note: If you remove a period, the corresponding data will be deleted.


Change the Allocation level or hierarchy The following tasks have to be performed when you want to change the allocation hierarchy: JDA Supply Chain Planning and Optimization Configuration Guide 53 © 1997-2014 JDA Software Group, Inc.- Confidential


1. Delete the Allocation sets.

2. Delete the Allocation profiles.

3. Data in the following tables purged:

• AllocAggHist, AllocDataCollections, AllocException, AllocItemAttrSel, AllocItemGrpSel, AllocItemHierSel, AllocNeed, AllocProfile, AllocResultDetails, AllocResultSourceDetails, AllocResultSummary, AllocSet, AllocSupplies and, associated RecShips.

4. Make changes to allocation hierarchy in the AllocMaster table. Log out and login a new session.

5. Re-create Allocation profiles and Allocation sets using the Allocation Workbench – Manual configuration.

6. Run the Calculate Aggregations and Allocations processes.

The following tasks have to be performed when allocation level is to be modified:

1. Delete the Allocation sets.

2. Data in the following tables purged:

• AllocAggHist, AllocDataCollections, AllocException, AllocItemAttrSel, AllocItemGrpSel, AllocItemHierSel, AllocNeed, AllocResultDetails, AllocResultSourceDetails, AllocResultSummary, AllocSet, AllocSupplies and associated RecShips.

3. Make changes to Allocation level in the AllocMaster table. Log out and login a new session.

4. Re-create allocation sets using the Allocation Workbench – Manual Configuration.

5. Run the Calculate Aggregations and Allocations processes.

JDA Fulfillment Dynamic Allocation online services JDA Dynamic Allocation feature allows you to run different business functions while working with Dynamic Allocations in the Allocation Workbench - Review page. These business functions are handled by the Fulfillment.AllocationCalcRMI SRE service. This service runs constantly, awaiting requests for various business functions. All the business functions that you request are handled by this service.

Business functions The business functions for the Dynamic Allocation feature are:

Calculate Allocations This business function of this service allows you to calculate allocations for the selected allocation sets. To run calculate allocation, you must select at least one allocation set in the Allocations panel and click this button. You can also select multiple allocation sets. This service always runs synchronously, that is, you must wait until the service completes the request before you can perform anything in the User Interface.

Commit Allocation This business function enables you to save the updated values to the database. The changes you make in the pivot page of the Allocation Workbench – Review page are not saved to the database automatically. Once you use this function, it evaluates and creates RecShips based on user updates and constraints. The business function does not re-calculate Need, but purges and re-generates the exceptions, if any.

Set up dashboard for Replenishment Planner After you install JDA Fulfillment, perform the following steps to set up the dashboard for Replenishment Planner:



1. Create a hierarchy using Hierarchy Manager if you do not have required hierarchies defined.

2. Assign a default hierarchy ID to a persona using the following steps:

a. Select a value from MD_Hierarchy:Hierarchy_ID in the Foundation schema for the required dimension name and hierarchy name.

b. Update Persona:DefaultHierarchyID in the SCPO schema with the same value you selected in MD_Hierarchy:Hierarchy_ID, for the persona.

3. After the default hierarchy ID is defined, perform the following steps in Dashboard Manager:

a. On the Manage Users tab, assign a user to a persona and default search.

Note: You must create a search in Search Manager.

b. On the Manage Goals tab, assign values to the goal metrics for a level in the selected hierarchy.

c. On the Manage Widgets tab, create group-by options to group and display data in the widgets.

d. On the Manage Workflows tab, create navigation links, if required, to which the planner can navigate from the analysis page.

Note: For more information on Dashboard Manager, see the SCPO General Systems OnLine Expert.


Set up data for JDA Markdown Optimization and JDA Promotions Management

Chapter 7. Set up data for JDA Markdown Optimization and JDA Promotions Management Before using JDA Promotions Management and JDA Markdown Optimization, you must set up the necessary business objects in the database. The following table describes the objects used by these applications. For additional information, see the Markdown Optimization and Promotions Management OnLine Experts.

JDA Promotions Management and JDA Markdown Optimization objects

Object Set up in ... Notes Demand Forecast Unit (DFU)

JDA Demand

Promotions JDA Promotions Management > Promotions Management Workbench

When creating a promotion, you must assign DFUs to it.

Markdowns JDA Markdown Optimization > Markdown Workbench

When creating a markdown, you must assign DFUs to it.

Marketing Instruments

JDA Promotions Management > Promotions Management Workbench

Marketing instruments are non-price information used to increase visibility and attract buyers. Assign marketing instruments to a promotion.

In addition, before running Estimate Market Response Model and other processes, you must populate the database tables identified in the following table. The data source, frequency of change, and size are estimates. Your business requirements may differ.

For information on loading data to the SCPO database using the JDA Platform Interface Generation Program (IGP), see 'Import data'.

JDA Markdown and JDA Promotions Management tables

Table Contains Description RAWVARIABLE Default variables, user-

defined variables, causal factors

Data source: business users, IMPLEMENTATION SERVICESimplementation services Frequency of change: low Size: small Modify using Oracle utilities.

Calendar data CAL Available calendars Data source: business users, back-end

systems Frequency of change: high Size: small Use Oracle utilities or IGP to load data.

CALDATA Data for each calendar Data source: business users, back-end systems Frequency of change: high (weekly, daily) Size: large Use Oracle utilities or IGP to load data.



Table Contains Description Marketing instruments MKTGINSTRUMENT

Available marketing instruments

Data source: business users, back-end systems Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

MKTGINSTRUMENTATTRIB

Attributes for each marketing instrument


DFU definitions DMDUNIT Available items Data source: business users, back-end

systems Frequency of change: high (weekly, daily) Size: large Use Oracle utilities or IGP to load data.

LOC Available locations Data source: business users, back-end systems Frequency of change: low (monthly) Size: large Use Oracle utilities or IGP to load data.

DMDGROUP Channel Data source: business users, back-end systems Frequency of change: low (monthly) Size: low Use Oracle utilities or IGP to load data.

DFUVIEW Valid DmdUnit, DmdGroup, Loc combinations for which a product is sold.

Data source: business users, back-end systems Frequency of change: low (monthly) Size: large Use Oracle utilities or IGP to load data.

DFU Forecast data for items. DmdUnit, DmdGroup, Loc, and Model combinations for which a product may be planned.

Data source: business users, back-end systems Frequency of change: high (weekly, daily) Size: large Use Oracle utilities or IGP to load data.

DFU data DFUPRICERELATION

Cross-product relationships Data source: business users, back-end systems Frequency of change: low (monthly) Size: low Use Oracle utilities or IGP to load data.



Table Contains Description DFUBASECOST Per unit cost for each DFU

during a time period Data source: business users, back-end systems Frequency of change: low (monthly) Size: large Import method: IGP Use Oracle utilities or IGP to load data.

DFUBASEPRICE Per unit base price for each DFU during a time period

Data source: business users, back-end systems Frequency of change: low (monthly) Size: large Use Oracle utilities or IGP to load data.

DFUPRICEPARAM For each DFU, the Market response model group, decomposition group, and so forth


MRM definition and data MRMGROUP Models for each MRM group Data source: business users,

IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

MRMODEL GLINT files for each model Data source: business users, IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

VARIANTMRMCAUSALFACTORVAL

Associates causal factor to a DFU

Data source: business users, IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

MRMCAUSALFACTOR

Available causal factors Data source: business users, IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

MRMPROXY Associates MRM group with proxy attributes

Data source: business users, IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

Decomposition definition and data



Table Contains Description DECOMPGROUP Model used for each

Decomposition group Data source: IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

DECOMPSUBGROUP

Decomposition subgroups Data source: IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

DECOMPSUBGROUPMKTINGINSTRUMENT

Associates marketing instruments with decomposition subgroups

Data source: IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

DECOMPSUBGROUPNORMFACTOR

Decomposition group and normalization factors

Data source: IMPLEMENTATION SERVICES Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.

History

HIST Historical information on DFUs

Data source: back-end system Frequency of change: high (weekly) Size: large Use Oracle utilities or IGP to load data.

HISTPROMO Historical promotions start date and duration

Data source: back-end system Frequency of change: low (monthly) Size: large Use Oracle utilities or IGP to load data.

HISTPROMOMKTGINSTRUMENTAVAL

Historical promotions with marketing instruments

Data source: back-end system Frequency of change: low (monthly) Size: large Use Oracle utilities or IGP to load data.

DFUEFFPRICE Historical effective prices Data source: back-end system Frequency of change: low (monthly) Size: large Use Oracle utilities or IGP to load data.

DFUEFFCOST Per unit effective cost for each DFU during a specific time period.

Data source: business users, back-end systems Frequency of change: low (monthly) Size: large Import method: IGP Use Oracle utilities or IGP to load data

Other configuration tables



Table Contains Description PRICEGLOBALPARAM

Calendar and optimization parameters

Data source: IMPLEMENTATION SERVICESimplementation services Frequency of change: low (monthly) Size: small Use Oracle utilities or IGP to load data.


Configure JDA Promotions Management

Chapter 8. Configure JDA Promotions Management Perform specific configuration tasks before you can use the system:

Set up data Before using JDA Promotions Management, you must set up the necessary business objects in the database. This section provides instruction to change the initial configuration of JDA Promotions Management version 8.1.0.0. You must install JDA SCPO 8.1.0.0 before performing the procedures in this section. For information on using this application, select Help in JDA Promotions Management.

Configure hierarchies for JDA Promotions Management The JDA Foundation schema provides a table to define hierarchies for any of the SCPO applications. For JDA Promotions Management, part of the configuration required is to define the hierarchies for your company.

Note: The hierarchies used in JDA Promotions Management are built using the SCPO schema. Typically, you will use user-defined columns as the different levels of your hierarchy. Use the JDA Foundation Data Model Manager to define the columns to use in your hierarchies before setting up the hierarchy metadata.

Set up the required hierarchy dimensions You must first create the dimensions you want to use in Promotions Management.

Note: The two dimensions - products and locations, already exist in the application. But you need to setup translations for these two dimensions.

You should set up the translations for the dimension names in the MD_DIMENSION_TRANS table. For example, you could set the English translation for the Product dimension as "Product dimension" as follows:

INSERT INTO MDD_DIMENSION_TRANS (DIMENSION_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('PromotionsManagement.Product', 'en', NULL, 'Product', 'Product dimension');

Define hierarchies After you have set-up the required dimensions, you must set up the hierarchies based on your business needs. You must create at least one hierarchy for the product dimension and one hierarchy for the location dimension. Often, companies only have one product and one location hierarchy. However, some companies might want to plan their promotions using different hierarchies. For example, a company might plan some promotions for radio and some for newspapers. The organization of these media zones might be different and require different hierarchies. If you establish different hierarchies, you must be certain that external systems that are expecting price or advertising exports can handle the different hierarchies that you define and use for your promotions.

To set-up a hierarchy to be used by Promotions Management, you must first insert one row into the MD_HIERARCHY table and one row for each language you will be using into the translation table, MD_HIERARCHY_TRANS. The value you use for the column MD_HIERARCHY.DIMENSION_NAME must match the DIMENSION_NAME defined in the MD_DIMENSION table. The HIERARCHY_NAME and HIERARCHY_ID can be set to be based on your business requirements. For example, if your business only requires one hierarchy for products, you might run the following statement to create a hierarchy:

INSERT INTO MD_HIERARCHY (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_ID) VALUES ('PromotionsManagement.Product', 'Product', 101);

Similar to how you set the translations for the MD_DIMENSION table, you should set up translations for each of the hierarchies you create. For example:



INSERT INTO MD_HIERARCHY_TRANS (DIMENSION_NAME, HIERARCHY_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('PromotionsManagement.Product', 'Product', 'en', NULL, 'Product Hierarchy', 'Groups Products by Department, Subdepartment, Class, Style.');

Set up hierarchy levels After you define the hierarchies to plan your promotions, you must define the levels of each hierarchy. For example, you might have Department, SubDepartment, Class, Style, and SKU levels for a product hierarchy and Region, Ad Zone, Price Zone, and Store levels for a location hierarchy. For each level in each hierarchy, you must insert a record into the MD_HIERARCHY_LEVEL table. For example, you may enter a level for the product hierarchy defined in the previous examples as follows:

INSERT INTO MD_HIERARCHY_LEVEL (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_LEVEL_NAME, HIERARCHY_LEVEL_ID, LEVEL_NUM, SCHEMA_NAME, TABLE_NAME, COLUMN_NAME) VALUES ('PromotionsManagement.Product', 'Product', 'Department', 10000000515, 1, 'SCPOMGR_NEW', 'DMDUNIT', 'U_DEPT');

The LEVEL_NUM column must be set so that the topmost level of your hierarchy ('Department') has the lowest value, the next lowest level has the next highest value, and so on. Typically, the SCHEMA_NAME, TABLE_NAME and COLUMN_NAME point to a user-defined column on the SCPO schema's DMDUNIT table (Product hierarchies) or LOC table (Location hierarchies) that conforms to your business practices. An exception to this is the lowest level in the hierarchies, which often maps to DMDUNIT.DMDUNIT and LOC.LOC respectively.

As you set up translations for the dimensions and hierarchies, you must also set translations for the hierarchy levels in the MD_HIERARCHY_LEVEL_TRANS table.

In the LocHierarchyName column of the PromoReportingLvl table, specify the name of each hierarchy. If Promotions Management is integrated with JDA Advertising, you must also specify values in the PriceZoneCol, AdZoneCol, and AdZoneAbbrCol columns in PromoReportingLvl table. Specify the names of the Loc table's UDA columns for price zone, ad zone, and ad zone abbreviation. That information enables the system to identify the columns that hold price zone and ad zone data for a vehicle to which a specific marketing instrument is assigned.

Define price points for Price Optimization JDA Promotions Management Price Optimization requires a set of discount values that must be considered during the optimization. This set of discount values prevents Price Optimization from suggesting discounts that would not be appealing to customers, such as "13% Off". If you intend to use Price Optimization, you must establish these valid values by entering them into the SCPO schema's table PROMOOPTPROFILEVAL. The following values are used for the PROFILETYPE column:

1 = "% Off" discount

2 = "Amount Off" discount

The VALUE column indicates the amount of the discount.

Note: For "% Off" discounts, the VALUE should be specified as a fraction. For example, to set a discount of 10%, the VALUE column should be 0.1.

Example: To set up discount values of 5%, 10%, and 25% off, insert three records into the PROMOOPTPROFILEVAL table:

SQLPLUS <SCPOSchemaOwner>/<SCPOSchemaOwner>

INSERT INTO PROMOOPTPROFILEVALUE (VALUE, PROFILETYPE) VALUES (0.05, 1);



COMMIT;



Note: This configuration step must be performed using Oracle utilities. It cannot be performed through the JDA Foundation Flexible Editor.

Configure marketing instruments and user defined attributes In Promotions Management, your company may want to change the initial configuration by adding its own user defined attributes, marketing instruments, incentive types, and causal factors. After adding new rows to the database tables for those entities, you must perform additional configuration.

Configure user-defined attributes User-defined attributes specify application-level data that is independent of any promotional offer and can be used in the Generalized LINear modeling Toolkit (GLINT) model.

You can add a user-defined column (UDC) to define this data. It is usually defined at the product level (DMDUNIT table) or location level (LOC table). For information on adding user-defined rows and columns, see the "Data Model Manager" chapter in the JDA Platform Installation/Administration Guide.

Define Business Object (BO) metadata for the attributes Metadata must be defined in the following tables:

• MD_ATTRIBUTE

A record is inserted in this table to associate the primitive attribute to the PromoDFU business object. The attribute must be associated only to the PromoDFU used in the GLINT model.

• MD_PRIMITIVE_ATTRIBUTE

A record is inserted for each attribute that defines the primitive attribute information.

• MD_PRIMITIVE_ATTRIBUTE_TRANS

This is the translation table for MD_PRIMITIVE_ATTRIBUTE. Insert a record in this table to translate the primitive attribute information.

• MD_ATTRIBUTE_GROUP_MEMBER

A record is inserted in this table to add the attribute to the business object’s group. The attribute will appear below that group name when displayed in the Tactics tab’s Properties dialog box.

Example: For locations, create a user-defined attribute called Loc_Size.

In the MD_ATTRIBUTE table, associate the attributes to the PromoDFU business object.

INSERT INTO MD_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, TYPE, AGGREGATOR_CLASS)VALUES ('PromoDFU', 'Loc_Size', 'PRIMITIVE', 'com.manu.scpoweb.drm.apm.ds.common.aggregation.MktgInstrumentBaseAggregator');

In the MD_PRIMITIVE_ATTRIBUTE table, add the primitive attribute information for all attributes.

INSERT INTO MD_PRIMITIVE_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, SEQ, SCHEMA_NAME, TABLE_NAME, COLUMN_NAME) VALUES ( 'PromoDFU', 'Loc_Size', 0, 'SCPOMGR', 'LOC', 'LOC_SIZE');

In the MD_PRIMITIVE_ATTRIBUTE_TRANS table, insert the translation for the primitive attribute.

INSERT INTO MD_PRIMITIVE_ATTRIBUTE_TRANS (BO_NAME, ATTRIBUTE_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('PromoDFU', 'Loc_Size', 'en', NULL, 'Location Size', 'Location Size');

In the MD_ATTRIBUTE_GROUP_MEMBER table, add the attribute to the business object’s group.

INSERT INTO MD_ATTRIBUTE_GROUP_MEMBER (GROUP_NAME, BO_NAME, ATTRIBUTE_NAME, ORDER_NO) VALUES ('PromoDFU', 'PromoDFU', 'Loc_Size', (SELECT NVL(MAX(ORDER_NO)+1, 1) FROM MD_ATTRIBUTE_GROUP_MEMBER WHERE GROUP_NAME='PromoDFU'));



Configure marketing instruments Add marketing instruments to the database Add a marketing instrument to the MktgInstrument table with an appropriate marketing instrument name.

The attributes of a marketing instrument can be defined at both promotional offer and promo DFU levels. The value set at the promotional offer level is a common value for all promo DFUs in the promotional offer.

Add each attribute of the marketing instrument to the MktgInstrumentAttrib table with the appropriate marketing instrument attribute names. Specify other column values as explained in the information for that table. If an attribute is defined at the promo DFU level, use "PromoDFU" as the BO_NAME value; for attributes defined at the promotional offer level, use "PromoOffer" as the BO_NAME value.

If a marketing instrument attribute is used in GLINT definition, the data type can only be CATEGORICAL, NUMERIC, or BOOLEAN. If the data type is CATEGORICAL, you cannot use spaces in the MI attribute.

For attributes not used in GLINT definition, you can use other data types.

Note: If you are adding a categorical attribute, you must first define its valid values in a metadata domain in the JDA Foundation schema. See "Working with Data Domain in the JDA Platform Common Installation/Administration Guide. The naming convention for the categorical marketing instrument attribute domain is SCPO_MI_ATTR_<marketing instrument attribute name>.

Create UDCs for attributes at the promotional offer level

For marketing instrument attributes defined at the promotional offer level, you must add a user defined column to the PROMOTION table. For information, see the "Data Model Manager" chapter in the JDA Platform Installation/Administration Guide. For attributes defined at the promo DFU level, you do not need to create a user defined column.

Define BO metadata for the attributes

Metadata must be defined in the following tables:

• MD_ATTRIBUTE

A record is inserted in this table to associate the primitive attribute to a business object. Normally if the marketing instrument attribute is defined at the promotional offer level, then the attribute is associated to the PromoOffer business object. If an attribute is defined at the promo DFU level, then the attribute is associated to the PromoDFU business object. In addition, for all attributes defined at the promo DFU level, an Aggregator_Class_Name column should contain a value defining the aggregator class name to be used for aggregating the data on the UI.

"Use "com.manu.scpoweb.drm.apm.ds.common.aggregation.MtgInstrumentBaseAggregator" for the Aggregator Class column value.

• MD_PRIMITIVE_INFO

A record is inserted in this table for each attribute that is at promo DFU level.

• MD_PRIMITIVE_ATTRIBUTE

A record is inserted in this table for each marketing instrument attribute. This table defines the primitive attribute for the marketing instrument attribute. For compound primitive attributes such as Currency, two records are inserted in this table.



• MD_PRIMITIVE_ATTRIBUTE_TRANS

This is the translation table for MD_PRIMITIVE_ATTRIBUTE. Insert a record in this table to translate the primitive attribute information. For compound primitive attributes, insert multiple records.

Modify RawVariable and market response model tables Use the following steps to configure the new marketing instrument in the RawVariable and MRModel tables.

Add entries to the RawVariable table

The RawVariable, system table contains sample record entries for marketing instrument attribute-related raw variables. For new marketing instruments, add appropriate raw variables to the RawVariable table.

• For a numeric or boolean marketing instrument attribute:

Naming convention: <Marketing Instrument Name>_<Marketing Instrument Attribute Name>

1. In the RawVariable table, duplicate the row for raw variable MKTGINSTRUMENT_NONCATEGORICALATTRIBUTENAME.

2. Replace the raw variable name MKTGINSTRUMENT_NONCATEGORICALATTRIBUTENAME with the new name and modify the description.

• For each category of categorical marketing instrument attribute:

Naming convention: <Marketing Instrument Name>_<Marketing Instrument Attribute Name>_<Category Display Name>

1. In the RawVariable table, duplicate the row for raw variable MKTGINSTRUMENTNAME_CATEGORICALATTRIBUTENAME_ CATEGORYVALUE.

2. Replace the raw variable name MKTGINSTRUMENTNAME_ CATEGORICALATTRIBUTENAME_CATEGORYVALUE with the new name and modify the description.

Modify Calibration GLINT

The Calibration GLINT defines independent predictors with proper transformation. Regression generates coefficients for each of the predictors. Introduce the new raw variables used in defining this new marketing instrument, so regression will generate appropriate coefficient values.

Modify Statistical Forecast Generation GLINT

The Statistical Forecast Calculation GLINT defines all independent predictors with their coefficient names necessary for adjusting the baseline demand forecast. Coefficient names and raw variable transformations, along with the predictor orders, must be synchronized with CalibrationSpec. Introduce the raw variables used in defining this new marketing instrument with the appropriate transformation, so it is used in demand forecast computation when this new marketing instrument is used in a promotion.

Example: Add a new marketing instrument, CIRCULAR, with categorical attribute FEATURE and non-categorical attribute PHOTO at promo DFU level, and non-categorical attribute PAGE at promotional offer level. Categorical domain SCPO_MI_ATTR_FEATURE has four categories: NONE, BACK, FRONT, and MID.

A. Add marketing instruments to the database

You may use the Flexible Editor, or any other SQL tool, to insert the following values.

In the MktgInstrument table, add a new row for the CIRCULAR marketing instrument using the following INSERT statement:



• MKTGINSTRUMENT: CIRCULAR

• OPTIMIZABLESW: 0

In the MktgInstrumentAttrib table, add the a new row for the CIRCULAR marketing instrument using the following INSERT statement:

INSERT INTO MKTGINSTRUMENT ( MKTGINSTRUMENT, OPTIMIZABLESW ) VALUES ('CIRCULAR', 0);

Data 1

• MktgInstrument: CIRCULAR

• MktgInstrumentAttrib: FEATURE

• Datatype: CATEGORICAL

• MinVal: 1

• MaxVal: 4

• DefaultVal: 1

• Domain_Name: SCPO_MI_ATTR_FEATURE

• TimeSlottingFunction: TIMEWEIGHTEDAVG

• AggregationFunction: SIMPLEAVG

• Bo_Name: PromoDFU

• Attribute_name: CircularFeature

Data 2


• MktgInstrumentAttrib: PHOTO

• Datatype: BOOLEAN

• MinVal: 0

• MaxVal: 1

• DefaultVal: 0

• Domain_Name: SCPO_MI_ATTR_NONCAT



• Bo_Name: PromoDFU

• Attribute_name: CircularPhoto

Data 3


• MktgInstrumentAttrib: PAGE

• Datatype: NUMERIC

• MinVal: 0

• MaxVal: 32

• DefaultVal: 0



• Domain_Name: SCPO_MI_ATTR_NONCAT



• Bo_Name: PromoOffer

• Attribute_name: CircularPage

Insert the listed data using the following INSERT statements:

INSERT INTO MKTGINSTRUMENTATTRIB ( MKTGINSTRUMENT, MKTGINSTRUMENTATTRIB, DATATYPE, MINVAL, MAXVAL, DOMAIN_NAME, DEFAULTVAL, TIMESLOTTINGFUNCTION, AGGREGATIONFUNCTION, BO_NAME, ATTRIBUTE_NAME ) VALUES ('CIRCULAR', 'PHOTO', 'BOOLEAN', 0, 1, 'SCPO_MI_ATTR_NONCAT', 0, 'TIMEWEIGHTEDAVG', 'SIMPLEAVG', 'PromoDFU', 'CircularPhoto');

INSERT INTO MKTGINSTRUMENTATTRIB ( MKTGINSTRUMENT, MKTGINSTRUMENTATTRIB, DATATYPE, MINVAL, MAXVAL, DOMAIN_NAME, DEFAULTVAL, TIMESLOTTINGFUNCTION, AGGREGATIONFUNCTION, BO_NAME, ATTRIBUTE_NAME ) VALUES ( 'CIRCULAR', 'FEATURE', 'CATEGORICAL', 1, 4, 'SCPO_MI_ATTR_FEATURE', 1, 'TIMEWEIGHTEDAVG', 'SIMPLEAVG', 'PromoDFU', 'CircularFeature');

INSERT INTO MKTGINSTRUMENTATTRIB ( MKTGINSTRUMENT, MKTGINSTRUMENTATTRIB, DATATYPE, MINVAL, MAXVAL, DOMAIN_NAME, DEFAULTVAL, TIMESLOTTINGFUNCTION, AGGREGATIONFUNCTION, BO_NAME, ATTRIBUTE_NAME ) VALUES ('CIRCULAR', 'PAGE', 'NUMERIC', 0, 32, 'SCPO_MI_ATTR_NONCAT', 0,'TIMEWEIGHTEDAVG', 'SIMPLEAVG', 'PromoOffer', 'CircularPage');

B. Create UDCs for attributes at the promotional offer level

Add the integer column CIRCULARPAGE to the PROMOTION table using Data Model Manager.

Add metadata for the marketing instruments to the database

Using appropriate SQL tool, insert the following values to the JDA Foundation schema.

1. In the MD_ATTRIBUTE table, associate the attributes to the appropriate business object.

INSERT INTO MD_ATTRIBUTE ( BO_NAME, ATTRIBUTE_NAME, TYPE, AGGREGATOR_CLASS ) VALUES ('PromoDFU', 'CircularFeature', 'PRIMITIVE', 'com.manu.scpoweb.drm.apm.ds.common.aggregation.MktgInstrumentBaseAggregator');

INSERT INTO MD_ATTRIBUTE ( BO_NAME, ATTRIBUTE_NAME, TYPE, AGGREGATOR_CLASS ) VALUES ( 'PromoDFU', 'CircularPhoto', 'PRIMITIVE', 'com.manu.scpoweb.drm.apm.ds.common.aggregation.MktgInstrumentBaseAggregator');

INSERT INTO MD_ATTRIBUTE ( BO_NAME, ATTRIBUTE_NAME, TYPE ) VALUES ( 'PromoOffer', 'CircularPage', 'PRIMITIVE');

2. In the MD_PRIMITIVE_INFO table, add the primitive information for the attributes at the promo DFU level.

INSERT INTO MD_PRIMITIVE_INFO ( PRIMITIVE_ID, LOGICAL_DATA_TYPE_NAME, DOMAIN_NAME,IS_USER_UPDATEABLE, IS_USER_DEFINED, IS_USER_REQUIRED, IS_USER_INSERTABLE, IS_NULLABLE,DATA_DEFAULT, MIN_VALUE, MAX_VALUE, STEP_SIZE ) VALUES ( 'PromoDFU.CircularFeature', 'OPTION_NUMBER', 'SCPO_MI_ATTR_FEATURE', 1, 1, 1, 1, 0, '1', '1', '4', '1');

INSERT INTO MD_PRIMITIVE_INFO ( PRIMITIVE_ID, LOGICAL_DATA_TYPE_NAME, DOMAIN_NAME,IS_USER_UPDATEABLE, IS_USER_DEFINED, IS_USER_REQUIRED, IS_USER_INSERTABLE, IS_NULLABLE,DATA_DEFAULT, MIN_VALUE, MAX_VALUE, STEP_SIZE ) VALUES (PromoDFU.CircularPhoto', 'BOOLEAN', NULL, 1, 1, 1, 1, 0, '0', '0', '1', '1');

3. In the MD_PRIMITIVE_ATTRIBUTE table, add the primitive attribute information for the attributes.



INSERT INTO MD_PRIMITIVE_ATTRIBUTE ( BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID, SCHEMA_NAME,TABLE_NAME, COLUMN_NAME ) VALUES ( 'PromoDFU', 'CircularFeature', 0, 'PromoDFU.CircularFeature', NULL, NULL, NULL);

INSERT INTO MD_PRIMITIVE_ATTRIBUTE ( BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID, SCHEMA_NAME,TABLE_NAME, COLUMN_NAME ) VALUES ( 'PromoDFU', 'CircularPhoto', 0, 'PromoDFU.CircularPhoto', NULL, NULL, NULL);

INSERT INTO MD_PRIMITIVE_ATTRIBUTE ( BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID, SCHEMA_NAME, TABLE_NAME, COLUMN_NAME ) VALUES ( 'PromoOffer', 'CircularPage', 0, 'Common.Integer', 'SCPOMGR', 'PROMOTION', 'CIRCULARPAGE');

4. In the MD_PRIMITIVE_ATTRIBUTE_TRANS table, insert the translation for the primitive attribute.

INSERT INTO MD_PRIMITIVE_ATTRIBUTE_TRANS ( BO_NAME, ATTRIBUTE_NAME, SEQ, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION ) VALUES ( 'PromoDFU', 'CircularFeature', 0, NULL, NULL, 'Circular Feature Placement', 'Feature placement in a Circular Marketing Instrument');

INSERT INTO MD_PRIMITIVE_ATTRIBUTE_TRANS ( BO_NAME, ATTRIBUTE_NAME, SEQ, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION ) VALUES ( 'PromoDFU', 'CircularPhoto', 0, NULL, NULL, 'Circular Photo', 'Whether a photo will be included in a Circular Marketing Instrument');

INSERT INTO MD_PRIMITIVE_ATTRIBUTE_TRANS ( BO_NAME, ATTRIBUTE_NAME, SEQ, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION ) VALUES ( 'PromoOffer', 'CircularPage', 0, NULL, NULL, 'Circular Page', 'Page number on a Circular Marketing Instrument');

C. Modify market response model tables

The following parts of the example describe how to configure the new marketing instrument attributes in the RawVariable and MRModel tables. The examples are for two of the marketing instrument attributes, FEATURE and PHOTO, of marketing instrument CIRCULAR.

Add entries to the RawVariable table

1. For numeric or boolean marketing instrument attributes:

a. Using the naming convention, the new raw variable name for this marketing instrument attribute will be CIRCULAR_PHOTO.

b. In the RawVariable table, duplicate the row for raw variable MKTGINSTRUMENT_NONCATEGORICALATTRIBUTENAME. Replace the raw variable name MKTGINSTRUMENT_ NONCATEGORICALATTRIBUTENAME with CIRCULAR_PHOTO and modify the description. For example:

INSERT INTO rawvariable(rawvariable, descr, calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval)

SELECT 'CIRCULAR_PHOTO', 'PHOTO non-categorical marketing instrument', calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval FROM rawvariable WHERE rawvariable = 'MKTGINSTRUMENT_NONCATEGORICALATTRIBUTENAME';

2. For each category of CATEGORICAL Marketing instrument attribute:

a. Using the naming convention, the raw variable names for the categories of the FEATURE attribute will be CIRCULAR_FEATURE_NONE, CIRCULAR_ FEATURE_FRONT, CIRCULAR_FEATURE_BACK and CIRCULAR_FEATURE_ MID.



b. For each of the new raw variables, duplicate the row in the RawVariable table for raw variable MKTGINSTRUMENTNAME_CATEGORICALATTRIBUTENAME_ CATEGORYVALUE and replace the raw variable name MKTGINSTRUMENTNAME_CATEGORICALATTRIBUTENAME_CATEGORYVALUE with the new name, then modify the description. For example:

INSERT INTO rawvariable(rawvariable, descr, calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval) SELECT 'CIRCULAR_FEATURE_NONE', 'None category of Feature marketing instrument', calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval FROM rawvariable WHERE rawvariable ='MKTGINSTRUMENTNAME_CATEGORICALATTRIBUTENAME_CATEGORYVALUE';

INSERT INTO rawvariable(rawvariable, descr, calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval) SELECT 'CIRCULAR_FEATURE_FRONT', 'Front category of Feature marketing instrument', calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval FROM rawvariable WHERE rawvariable = 'MKTGINSTRUMENTNAME_CATEGORICALATTRIBUTENAME_CATEGORYVALUE';

INSERT INTO rawvariable(rawvariable, descr, calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval) SELECT 'CIRCULAR_FEATURE_BACK', 'Back category of Feature marketing instrument', calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval FROM rawvariable WHERE rawvariable = 'MKTGINSTRUMENTNAME_CATEGORICALATTRIBUTENAME_CATEGORYVALUE';

INSERT INTO rawvariable(rawvariable, descr, calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval) SELECT 'CIRCULAR_FEATURE_MID', 'Mid category of Feature marketing instrument', calibrationproviderclass, evaluationproviderclass, sourcetable, sourcecol, TYPE, aggfunction, slotfunction, defaultval FROM rawvariable WHERE rawvariable = 'MKTGINSTRUMENTNAME_CATEGORICALATTRIBUTENAME_CATEGORYVALUE';

D. Modify Calibration GLINT

The following example shows an existing GLINT for Calibration, after declaring the appropriate raw variables and introducing the necessary derived variables. The changes are highlighted in bold.

Calibration_Model_Section:

Intercept: Yes

Declarations:

<cs DmdUnit>;

<cs Loc>;

<cs Loc_Loc_Size>;

<cs DmdGroup>;

<ns Sales>;

<ns Base_Price_Ratio>;

%New raw variables for Circular MI JDA Supply Chain Planning and Optimization Configuration Guide 69 © 1997-2014 JDA Software Group, Inc.- Confidential


<ns Circular_Photo>;

<ns Circular_FEATURE_FRONT>;

<ns Circular_FEATURE_BACK>;

Variables:

OwnPrice TimesV(AllCSToNV(Loc_Loc_Size), log(Base_Price_ Ratio))

%Define new independent predictors. Regression would generate %coefficients for each of the predictors.

MI_Photo Circular_Photo

MI_Feature_Front Circular_FEATURE_FRONT

MI_Feature_Back Circular_FEATURE_BACK

Response:

Log(Sales)

Smearing Factor Group Index:

%CATPROD(DMDUNIT, Loc_Loc_SIZE)

E. Modify Statistical Forecast Calculation GLINT

The following example shows an existing GLINT for Statistical Forecast Calculation, after declaring the appropriate raw variables and introducing the necessary derived variables. The changes are highlighted in bold.

Forecast_Model_Section:

Intercept: No

Declarations:

<cs Loc_LOC_SIZE>;

<ns Eff_Price>;

<ns Base_Price>;


<ns Base_Demand>;

%New raw variables for Circular MI


<ns Circular_FEATURE_FRONT>;

<ns Circular_FEATURE_BACK>;

Variables:

OwnPrice TimesV(AllCStoNV(LOC_LOC_SIZE),log(Divide(Eff_Price, Base_Price)))



%Define all independent predictors for new raw variables with their %coefficient names necessary for adjusting baseline demand forecast. %Coefficient names and raw variable transformations along with the %predictor orders must be in sync with those defined in the Calibration Spec.

MI_Photo Circular_Photo

MI_Feature_FrontCircular_FEATURE_FRONT

MI_Feature_Back Circular_FEATURE_BACK

Forecast Variables:

ForecastVar Base_Demand * exp (Response)

Configure activity types If JDA Promotions Management and JDA Advertising are integrated in your system, the PromoActivityType and PromoActivityType_Trans tables must define four activity types, numbered 5, 6, 7, and 8, as shown in the following tables.

PromoActivityType

ActivityType HierarchyLevel 5 Specify a value of 1 or greater 6 Previous level + 1 7 Previous level + 1 8 Previous level + 1

PromoActivityType_Trans

ActivityType Label 5 <display name of this

ActivityType> 6 <display name of this



ActivityType>

If JDA Promotions Management is not integrated with JDA Advertising, these tables could have as few as two ActivityTypes.

Below are examples of SQL that could be used to set up the environment.

INSERT INTO PROMOACTIVITYTYPE (ACTIVITYTYPE, IS_DEFAULT, HIERARCHY_LEVEL) VALUES (6, 1, 1);

INSERT INTO PROMOACTIVITYTYPE_TRANS (ACTIVITYTYPE, COUNTRY_CODE, LANGUAGE_CODE, LABEL) VALUES (6, NULL, 'en', 'Campaign');



You can also create user-defined attributes (UDAs) that are specific to an ActivityType. For example, for an ActivityType called Campaign, you might want a UDA called CampaignBudget. JDA Promotions Management ships with three tables (PromoVehicle, PromoEvent, and PromoCampaign) in which you can store UDA data for activities called Vehicle, Event, or Campaign. UDA data for other activities should be stored in the PromoActivity table.

To create a CampaignBudget UDA and associate it with ActivityType 6 (Campaign):

• In the PromoCampaign table, use the Data Model Manager to create a user-defined column (UDC) called CampaignBudget.

• Use metadata tables to define an attribute called PromoActivity.CampaignBudget. In MD_PRIMITIVE_ATTRIBUTE, point the attribute to the PromoCampaign.CampaignBudget column, as shown in the following SQL (where the SCPO schema name is SCPOMGR).

INSERT INTO MD_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, TYPE)

VALUES ('PromoActivity', 'Budget', 'PRIMITIVE');

INSERT INTO MD_PRIMITIVE_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID, SCHEMA_NAME, TABLE_NAME, COLUMN_NAME)

VALUES ('PromoActivity', 'Budget', 0, 'Common.Currency', 'SCPOMGR', 'PROMOCAMPAIGN', 'BUDGET');

INSERT INTO MD_PRIMITIVE_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID)

VALUES ('PromoActivity', 'Budget', 1, 'Common.Currency');

INSERT INTO MD_PRIMITIVE_ATTRIBUTE_TRANS (BO_NAME, ATTRIBUTE_NAME, SEQ, LANGUAGE_CODE, DISPLAY_NAME)

VALUES ('PromoActivity', 'Budget', 0, 'en', 'Budget');

INSERT INTO MD_PRIMITIVE_ATTRIBUTE_TRANS (BO_NAME, ATTRIBUTE_NAME, SEQ, DISPLAY_NAME)

VALUES ('PromoActivity', 'Budget', 0, 'Budget');

COMMIT;

• In the PromoActivityAttribDef table, configure the PromoActivity.CampaignBudget UDA as a UDA for ActivityType 6. Following is the SQL statement for doing that:

INSERT INTO PROMOACTIVITYATTRIBDEF (ACTIVITYTYPE, ATTRIBNAME) VALUES (6, 'PromoActivity.CampaignBudget');

Configure promotional activity tasks Promotional activities have routine tasks that must be completed in order to successfully execute and analyze the performance of the activity. These tasks will vary by activity type and will be assigned to a particular user or user group. Tasks will also vary based on the marketing instrument that is assigned to the promotional activity. The deadline for completing a task can be specified as a number of days before or after an activity. Tasks are displayed in the Tasks tab on the Event Management Workbench. You can configure these tasks in the PromoActivityTaskDef table.

When configuring tasks, the following items must be considered:

• Determine the activity type for which the task is applicable. For example, if the task is only applicable to vehicles, then its activity type designation should be for activity type representing vehicles. If an activity type is not designated, the task will be displayed in the Event Management Workbench for all promotional activities. Designate this value in the ActivityType column.



• Determine the marketing instrument for which the task is applicable. If the task is only applicable to vehicles representing print advertisements, then the task definition should include the appropriate marketing instrument that represents print media. Note that, if there is more than one marketing instrument representing a print advertisement (free standing insert, ROP), separate but similar tasks must be created, one for each marketing instrument. Designate this value in the MktgInstrument column.

• Determines who is responsible for completing the task. If there is a specific user or user group they can be assigned as the owner of the task. The list of available users and/or user groups is defined in the PromoCategory table. Designate the owner in the Owner column.

• Determine when the task due, which can be defined as a specific due date or a range of dates. For example, promotional product selection may have a specific due date while an ad proofing cycle may last a week. Setting a value in the Duration field indicates the task occurs over a range of dates. If a task is related to activity execution, indicate this by setting the FromStartSW field to 1, which indicates the DueDateOffset is based on the start date of the activity. If the task is related to post activity analysis, indicate this by setting the FromStartSW field to 0, which indicates the DueDateOffset is based on the end date of the activity. The DueDateOffset indicates the number of days before the start or end of an activity the task is due or is due to start.

The default status of the task is Not Yet Started. The numeric value associated with this status is 1. Designate the default status in the Status filed.

Configuration of this table is not required for the application to work.

A specific promotional activity might have common tasks that always start a specified number of days before or after an activity. You can configure these tasks in the PromoActivityTaskDef table.


Configure DFU cost elements The DFUCostElement table stores elements of DFU cost, such as additional charges, allowances, and other elements that are added to or subtracted from DFU cost to calculate a final cost. In Promotions Management, the list cost plus these additions and subtractions represents the net landed cost of a DFU, which affects the gross margin of a promotion. The values held in this table are intended to represent current deals that have been made with a supplier.

In order to use the DFU cost element to calculate net landed cost, you must first define the type of cost elements to use in the equation. Subtotal rows defined in the DFUCostElementType table display the net landed cost at the selected positions in the sequence.You can configure the cost element types in the DFUCostElementType table. The SCPO sample data includes three cost element types by default:

Type Name Operator 0 Charges Amount added to cost to calculate NLC 1 Allowances Amount subtracted from cost to calculate NLC 2 Billbacks Amount subtracted from cost to calculate NLC

In the Operator column, use a 1 to represent an element that adds to the cost of the DFU and a 2 to represent an element that reduces the cost of the DFU.

Once cost element types are defined, you can identify cost elements by DFU. Each cost element includes a DFU, start date, duration, element type, and value. Below is an example of SQL that could be used to set up the environment.

Insert into DFUCOSTELEMENT (DMDUNIT, DMDGROUP, LOC, STARTDATE, DUR, TYPE, VALUE)

Values ('436128', 'ALL', '261', TO_DATE('12/07/2013 00:00:00', 'MM/DD/YYYY HH24:MI:SS'), 1051200, 1, 0.1);



If there are overlapping cost elements of the same cost element type for a DFU for a period of time, the values are summed to determine the overall impact of the cost element type on the cost of a DFU. For example, if there is a 0.10 allowance for a DFU and a 0.15 allowance for the same DFU, these will be summed to reflect a 0.25 allowance for the DFU in the Promotions Management Workbench. If the business requires a more detailed breakdown of the allowances, this indicates that additional cost element types may need to be created.


Add values to cost elements A cost component is a specific amount or percent of gross or net cost that can be configured in the DFUCostElementType table to:

• Increase the cost of a product (charge), or

• Decrease the cost of a product (allowance or billback).

You can configure a cost element to make it editable or non-editable in the Promotions Management Workbench. The editability of a cost element depends on the MD_PRIMITIVE_INFO:Is_User_Defined column value.A non-editable cost element, in the Promotions Management Workbench, displays the values stored in the DFUCostElement table.

To configure a new cost element:

• Add entries, for the cost element to be created, in the following foundation database tables:

• MD_ATTRIBUTE: Use the Aggregator_Class_Name column value to define the aggregator class name to be used for aggregating the data in the Promotions Management Workbench. Add the Aggregator_Class column value as com.manu.scpoweb.drm.apm.ds.common.aggregation.CurrencyAggregatorRange for an amount type cost element and com.manu.scpoweb.drm.apm.ds.common.aggregation.PercentAggregatorRange for a percent type cost element.

• MD_ATTRIBUTE_GROUP_MEMBER: Ensure that the Group_Name column value is VendorTradePromotion. Add the cost element name in the Attribute_Name column.

MD_ PRIMITIVE_ATTRIBUTE: To configure a percent type cost element, in the primitive_Id column add PromoDFU.CostComponent.Percent for a percent type cost element, add PromoDFU.CostComponent.Currency for an amount type cost element. To make a cost element non-editable, set the IS_USER_DEFINED column value to 0 for the corresponding PRIMITIVE_ID in the MD_PRIMITIVE_INFO table.

• MD_PRIMITIVE_ATTRIBUTE_TRANS: For every cost element added, add values to the language_code column to translate its primitive information.

• Add entries, for the cost element to be created, in the DFUCostElementType table. See the JDA Pricing reference guide for more information.

Note: Add the Bo_Name column values as PromoDFU for the above mentioned foundation database tables.

The following script is an example of adding values, for an editable cost element, ScanBasedBillback:

Insert into DFUCOSTELEMENTTYPE (TYPE, ATTRIBUTE_NAME, OPERATOR, DFUCOSTELEMENTTYPESEQ, NETTYPE, PLANNEDSW, SUBTOTALSW, GROUPNAME) Values (1, 'PromoDFU.ScanBasedBillback', 2, 1, 'GROSS', '0', '0', ' ');

Insert into MD_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, TYPE, AGGREGATOR_CLASS) Values ('PromoDFU', 'ScanBasedBillback', 'PRIMITIVE', 'com.manu.scpoweb.drm.apm.ds.common.aggregation.CurrencyAggregatorRange');

Insert into MD_ATTRIBUTE_GROUP_MEMBER (GROUP_NAME, BO_NAME, ATTRIBUTE_NAME, ORDER_NO, SEQ) Values ('VendorTradePromotion', 'PromoDFU', 'ScanBasedBillback', 4, 0);



Insert into MD_PRIMITIVE_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID) Values ('PromoDFU', 'ScanBasedBillback', 0, 'PromoDFU.CostComponent.Currency');

Insert into MD_PRIMITIVE_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID) Values ('PromoDFU', 'ScanBasedBillback', 1, 'PromoDFU.CostComponent.Currency');

Insert into MD_PRIMITIVE_ATTRIBUTE_TRANS (BO_NAME, ATTRIBUTE_NAME, SEQ, LANGUAGE_CODE, DISPLAY_NAME) Values ('PromoDFU', 'ScanBasedBillback', 0, 'en', 'Scan based billback');

Insert into MD_PRIMITIVE_ATTRIBUTE_TRANS (BO_NAME, ATTRIBUTE_NAME, SEQ, DISPLAY_NAME) Values ('PromoDFU', 'ScanBasedBillback', 0, 'Scan based billback');

The following script is an example of adding values, for a non-editable cost element, OffInvoice:

Insert into DFUCOSTELEMENTTYPE (TYPE, ATTRIBUTE_NAME, OPERATOR, DFUCOSTELEMENTTYPESEQ, NETTYPE, PLANNEDSW, SUBTOTALSW, GROUPNAME) Values (2, 'PromoDFU.OffInvoice', 2, 2, 'GROSS', '0', '0', ' ');

Insert into MD_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, TYPE, AGGREGATOR_CLASS) Values ('PromoDFU', 'OffInvoice', 'PRIMITIVE', 'com.manu.scpoweb.drm.apm.ds.common.aggregation.CurrencyAggregatorRange');

Insert into MD_ATTRIBUTE_GROUP_MEMBER (GROUP_NAME, BO_NAME, ATTRIBUTE_NAME, ORDER_NO, SEQ) Values ('VendorTradePromotion', 'PromoDFU', 'OffInvoice', 11, 0);

Insert into MD_PRIMITIVE_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID) Values ('PromoDFU', 'OffInvoice', 0, 'Common.Currency');

Insert into MD_PRIMITIVE_ATTRIBUTE (BO_NAME, ATTRIBUTE_NAME, SEQ, PRIMITIVE_ID) Values ('PromoDFU', 'OffInvoice', 1, 'Common.Currency');

Insert into MD_PRIMITIVE_ATTRIBUTE_TRANS (BO_NAME, ATTRIBUTE_NAME, SEQ, LANGUAGE_CODE, DISPLAY_NAME) Values ('PromoDFU', 'OffInvoice', 0, 'en', 'Off Invoice');

Insert into MD_PRIMITIVE_ATTRIBUTE_TRANS (BO_NAME, ATTRIBUTE_NAME, SEQ, DISPLAY_NAME) Values ('PromoDFU', 'OffInvoice', 0, 'Off Invoice');

Save cost elements To save the value of a cost element to the database:

1. From the Tables and Columns tab in the Data Model Manager page, create a new User defined column (UDC) for the PromoDFU table. This automatically creates a records in the MD_COLUMN_INFO and MD_PRIMITIVE_ATTRIBUTE tables.

2. As a part of cost element setup, two records for the new UDC are automatically created in the MD_PRIMITIVE_ATTRIBUTE table. For the record with sequence number 0, enter values for the Schema name, Column name and Table name columns as used in creating the UDC for the PromoDFU table.

The values entered for the cost element are saved to the new UDC created in the PromoDFU table.

Note: Editable cost elements are saved to the PromoDFU table and the PromoDFUAttribValue tables. Non-editable cost elements are saved only to the PromoDFU table.

Configure product categories On the Space Allocation tab of the Event Manager, users can assign product categories to a specific page in an advertisement. For example, the meat category could be assigned to page 1 in a grocery circular and the dairy and bakery categories could be assigned to page 2. The system administrator must configure those product categories in the Category column of the system table PromoCategory.



A column in the DmdUnit table specifies the category for each demand unit. That column must be set up as a foreign key, referencing the PromoCategory.Category column, to ensure that it contains only values that exist in the PromoCategory table. For example, specify a user-defined column called Class as the foreign key:

ALTER TABLE DMDUNIT ADD CONSTRAINT FK_CATEGORY FOREIGN KEY (CLASS) REFERENCES PROMOCATEGORY(CATEGORY);

In the PriceGlobalParam table, set the value for the parameter DRM.APM.CATEGORY.UDA to the name of the DmdUnit table and column referenced in the foreign key – for example, DmdUnit.Class.

Configure integration between JDA Promotions Management and JDA Advertising If you have JDA Promotions Management and JDA Advertising installed and if you want to integrate them, you must follow some configuration steps.

Define the price zones and ad zones used in JDA Advertising JDA Advertising users generate advertising copy, such as "Save 10-20%," for different price zones for a promotional offer exported from Promotions Management.

As part of the integration between the two systems, Promotions Management reports the values required for the advertising copy for each promotional offer. These "save story" values are reported for all products in the reported price zone for the specific promotional offer. In the preceding example, Promotions Management would report 10% for the save story value Save From Percent and 20% for the save story value Save To Percent. JDA Advertising might generate different advertising copy for each price zone, so Promotions Management must report the save story values specific to each price zone.

The PromoReportingLvl table (part of the SCPO schema) must specify which column in the Loc table holds price zone data. If your system includes JDA Advertising, this data must correspond to price zone data in Advertising. If an offer is assigned to an activity, the DFUs added to the offer must have a corresponding Loc record whose price zone column data matches the price zone data of the activity. For example, if Loc:PriceZone is the column that holds price zone data and if the offer is assigned to the Spring Circular activity with price zones A, B, and C, Loc:PriceZone must contain A, B, or C for the related DFU to be added to the offer.

JDA Advertising also uses ad zones to version an advertisement from market to market. If your system includes JDA Advertising, the ad zone data that you specify must be coordinated with the data in Advertising. In the PromoReportingLvl table, use the AdZone and AdZoneAbbrCol columns to specify which columns on the Loc table contain ad zone names and abbreviations.

When you create an event in Promotions Management, you typically assign ad zones to the event. When you assign a promotional offer to the event, the offer inherits the ad zones from the event. The ad zone data must be coordinated with the data in Advertising.

When the event, offer, and ad zone data are exported to JDA Advertising, Advertising users can version their advertisements by each ad zone in the event, using the offers available for that ad zone.

Set up the Treatment data domain On the Fact Sheet tab of the Promotions Management Workbench, the Featured Products panel includes a Treatment column. If Promotions Management is integrated with JDA Advertising, the values in Treatment should correspond to the Advertising treatment types that are in use.

To accomplish that, the system administrator must specify the appropriate values in the data domain SCPO_APM_FACTSHEET_TREATMENT, which is included with Promotions Management. The following sample scripts illustrate how to specify a set of values for that data domain.

INSERT INTO MD_LIST_DOMAIN_VALUE ( VALUE_NAME, DOMAIN_NAME, IS_DEFAULT ) VALUES ( JDA Supply Chain Planning and Optimization Configuration Guide 76 © 1997-2014 JDA Software Group, Inc.- Confidential


'PROMO', 'SCPO_APM_FACTSHEET_TREATMENT', 0);

INSERT INTO MD_LIST_DOMAIN_VALUE ( VALUE_NAME, DOMAIN_NAME, IS_DEFAULT ) VALUES (

'FEATURE', 'SCPO_APM_FACTSHEET_TREATMENT', 1);


'SUB FEATURE', 'SCPO_APM_FACTSHEET_TREATMENT', 0);


'LINER', 'SCPO_APM_FACTSHEET_TREATMENT', 0);


'TABLE', 'SCPO_APM_FACTSHEET_TREATMENT', 0);


'STORY', 'SCPO_APM_FACTSHEET_TREATMENT', 0);

INSERT INTO MD_LIST_DOMAIN_VALUE_TRANS ( VALUE_NAME, COUNTRY_CODE, LANGUAGE_CODE, DISPLAY_NAME, DESCRIPTION, DOMAIN_NAME ) VALUES (

'PROMO', NULL, NULL, 'PROMO', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'LINER', NULL, NULL, 'LINER', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'FEATURE', NULL, NULL, 'FEATURE', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'SUB FEATURE', NULL, NULL, 'SUB FEATURE', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'TABLE', NULL, NULL, 'TABLE', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'STORY', NULL, NULL, 'STORY', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'STORY', NULL, 'en', 'STORY', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'TABLE', NULL, 'en', 'TABLE', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'SUB FEATURE', NULL, 'en', 'SUB FEATURE', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'FEATURE', NULL, 'en', 'FEATURE', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');


'LINER', NULL, 'en', 'LINER', NULL, 'SCPO_APM_FACTSHEET_TREATMENT'); JDA Supply Chain Planning and Optimization Configuration Guide 77 © 1997-2014 JDA Software Group, Inc.- Confidential



'PROMO', NULL, 'en', 'PROMO', NULL, 'SCPO_APM_FACTSHEET_TREATMENT');

JDA Advertising: Deploy Image browser Use the following steps to deploy JDA Advertising Image Browser for assigning images to the featured products in Fact Sheet tab:

Get pre-packaged ImageBrowser.war from JDA Advertising system administrator and place it in <install_dir>/config/scpoweb/bin directory. Please refer to JDA Advertising document for ImageBrowser.war. Follow the below steps for WebLogic and WebSphere environments:

For WebLogic

1. Start JDA server.

2. Run deployImageBrowserUI script located at <install_dir>/config/scpoweb/bin to deploy the ImageBrowser.war file to the application server. For example:

Usage for this command is:

deployImageBrowserUI <weblogic_admin_user> <weblogic_admin_password> <admin_url> <target>

In the above usage, 'target' is the name of the Administrative Server (in a non-clustered configuration), or the name of the Cluster (in a clustered configuration).

For example, in a default standalone configuration, enter the following:

deployImageBrowserUI weblogic weblogic1 t3://myhost:7001 AdminServer

In a default clustered configuration, enter the following:

deployImageBrowserUI weblogic weblogic1 t3://myhost:7001 JDACluster

For WebSphere

1. Run deployImageBrowserUI script located at <install_dir>/config/scpoweb/bin to deploy the ImageBrowser.war file to the application server.

Usage for this command in a standalone configuration is:

deployImageBrowserUI <admin_user> <admin_password> (in Windows)

deployImageBrowserUI <WAS_admin_user> <password> <profile_bootstrap_port> (in AIX)

For example, deployImageBrowserUI appAdmin password 6854

Usage for this command in a clustered configuration is:

deployImageBrowserUIToCluster <dmmgrHost> <dmMgrSOAPPort> <admin_user> <admin_password> (in Windows)

deployImageBrowserUIToCluster <dmmgrHost> <dmMgrbootstrap_port> <admin_user> <admin_password> (in AIX)

2. Start the JDA server.

Configure Modeling Workbench To configure the Modeling Workbench:

• Ensure that correct permissions are granted to the MRM processes and features, for the following roles.



For the MRMADMIN role, add the following resource with create, read, update, delete, and execute permissions.

• Modeling Workbench

For the SCPOADMIN role, add the following resources with create, read, update, delete, and execute permissions.

• MRMCAUSALFACTOR

• MRMCAUSALFACTORVALUE

• MRMCOEF

• MRMCOEFDRAFT

• MRMDFUCAUSALFACTOR

• MRMEXPERIMENT

• MRMGROUP

• MRMGROUPLRSTAT

• MRMGROUPLRSTATDRAFT

• MRMODEL

• MRMPROXY

• Create at least one product hierarchy and one location hierarchy using the hierarchy manager. The dimension names beneath which hierarchies are defined depend on the application being used. Valid dimensions and the respective application are shown below:

JDA Application Product Dimension Location Dimension


DemandDecomp.Product DemandDecomp.Location


PromotionsManagement.Product

PromotionsManagement.Location


Markdown.Product Markdown.Location

• Configure the dimension names for the parameters DRM.AUTOMRM.DIMENSION.LOCATION and DRM.AUTOMRM.DIMENSION.PRODUCT in the PriceGlobalParam table.

• MRM Experiments require several predefined prompted searches which need to be published to the MRMAdmin Role. The following parameters in the PriceGlobalParam table needs to be updated with the relevant search names :

Parameter

DRM.AUTOMRM.LOWERMAP.DFU.SEARCH

DRM.AUTOMRM.SEARCH.FCSTCALIBSW

DRM.AUTOMRM.SEARCH.FCSTEVALSW DRM.AUTOMRM.SEARCH.HOLDOUTEVAL DRM.AUTOMRM.SEARCH.LOWERMAP DRM.AUTOMRM.SEARCH.UPPERMAP

DRM.AUTOMRM.UPPERMAP.DFU.SEARCH

• On the modeling workbench, 'Model' and 'Hold-out' sections require some predefined searches. These searches have to be published to MRMAdmin role and must not contain any prompted fields. Ensure that the Calibration search or Model search is a super set of the products.



• For each process in the MRM experiment batch process, an option set has to be defined with private scope to the MRMAdmin user.

• Optionally, configure the batchstep in MRMExperimentDefBatchStep to change the default batch steps. You should only include the licensed processes.

• Before you run the MRM Experiment, run this script:

execute SRE_CONFIGURATION.INSTALLCONTINUOUSJOB ( 'DRM.MRMExperimentController', 'DEFAULT' );

• Add the credentials.properties file to this directory: \config\webworks\bin

• The Modeling Workbench batch process flows also allow you to customize the process flows by adding additional JDA processes or custom processes. Use the following steps to add additional JDA processes or custom processes:

1. Open the Batch Process tab

2. Click Add . The Add Processes dialog box is displayed with the JDA processes and custom processes details.

3. Click check box against all the processes you wish to select, click Done to save the selected processes.

Note: Selected processes are displayed in the Batch tab.

Set up Import Offer process To set up the import offer process, you must retrieve information from the following tables:

• Promotion_Import

• PromoDFUFcst_Import

The Promotion_Import table contains information related to the offer, while the PromoDFUFcst_Import table contains information related to the lift.

There are three types of offers supported, based on the level of lift provided.

Note: Offers with a date range of more than 52 periods are not valid.

Offer with search, but no calendar specified In this scenario, the lift is applicable to the entire date range of the offer. In this scenario, it obtains the default calendar value from the DRM.CALIBRATION.CALENDAR parameter in the PriceGlobalParam table, and distributes the lift accordingly. Such offers do not have to be entered in the PromoDFUFcst_Import table. You must define a proper search and the corresponding criteria values in the corresponding columns. Upto 10 criteria are supported.

Offer with a defined search and calendar In this scenario, the calendar must be defined in the Promotion_Import table. Also, there must be a defined lift value for each period in the PromoDFUFcst_Import table.

Offers with details of the DFU level lift In this scenario, no search is defined for these offers. Hence, a calendar is provided in the Promotion_Import table. Also, the DFU and its corresponding lift must be provided for each period in PromoDFUFcst_Import table. Ensure that the Search field is empty for such offers, as this is the factor that identifies the type of offer.



Parameters are set up for batch size, for reading base demand values from the Fcst/ FcstNarrow table. The DRM.APMHIST.BATCHUPDATESIZE parameter is configured in the PriceGlobalParam table for proper batch configuration.

Configure Candidate ID To configure the Candidate ID:

• You must configure the PriceGlobalParameters for Pricing and Promotions Management products. Currently, the percent off price strategy and the PGP parameter are being used to configure the same, that is, DRM.APM.CANDIDATEPROCESS.PERCENTOFF and default value is 0.2.

• Similarly, set the GLINT specification for Own Price, Cross Price and MI Elasticities respectively. You can use single GLINT for own and cross elasticity, which have been entered in the PriceElasticitySpec column of MRModel. Similarly, for MI Elasticity, you should use MIElasticitySpec. Ensure that you set the variable correctly, as causal factor and base demand are not supported. The following example illustrates the definition where own price elasticity is estimated using the location size attribute of a location:

Sample GLINT for own price and cross price

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%% This sample model is to compute elasticity for multiplicative model.

%% Consult Manugistics consultant for other types of Marketing Response Model.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Own_Price_Elasticity_Model_Section:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%'

Intercept:

No

Declarations:

<cs LOC_Loc_Size>;

Variables:

OwnPrice 1

Evaluation Variables:

OwnPriceElasticity Response

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

CROSS_Price_ELASTICITY_Model_SECTION:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Intercept:



No

Declarations:

<csv PoolName>;

<sv XPrice_Weight_Fac>;

Variables:

Cross_Price MASKNV(Sumsv(XPrice_Weight_Fac), CSVToBV(PoolName))


CrossPriceElasticity Response

Sample glint for MI

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Own_Price_Elasticity_Model_Section:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Intercept:

No

Declarations:

<ns CIRCULAR_FEATURE_FRONT>;

<ns CIRCULAR_FEATURE_BACK>;

<ns CIRCULAR_FEATURE_MIDDLE>;

<ns CIRCULAR_PHOTO>;

<ns DISPLAY_DISPLAYTYPE_BUSCAP>;

<ns DISPLAY_DISPLAYTYPE_ENDCAP>;

<ns BROADCAST_BROADCAST_TV>;

<ns BROADCAST_BROADCAST_RADIO>;

Variables:

MI_CIRCULAR_FEATURE_FRONT CIRCULAR_FEATURE_FRONT

MI_CIRCULAR_FEATURE_BACK CIRCULAR_FEATURE_BACK

MI_CIRCULAR_FEATURE_MIDDLE CIRCULAR_FEATURE_MIDDLE

MI_CIRCULAR_PHOTO CIRCULAR_PHOTO

MI_DISPLAY_DISPLAYTYPE_BUSCAP DISPLAY_DISPLAYTYPE_BUSCAP



MI_DISPLAY_DISPLAYTYPE_ENDCAP DISPLAY_DISPLAYTYPE_ENDCAP

MI_BROADCAST_BROADCAST_TV BROADCAST_BROADCAST_TV

MI_BROADCAST_BROADCAST_RADIO BROADCAST_BROADCAST_RADIO


MIElasticity Response

Set SRE node configuration properties A node pool with PromotionsManagement.CollectorServiceRMI service must be running for the user interface to work properly. When you open a promotional offer to which products are assigned, a “collector” is created in a PromotionsManagement.CollectorServiceRMI job. To help prevent an SRE node that is running a CollectorServiceRMI job from running out of memory, the MaximumNumberOfCollectorsPerNode should be set to a number greater than 0. Typically, JDA Consulting Services sets this value after considering the number of DFUs typically assigned to offers, the number of user-defined columns (UDCs), and the memory allocated to each node.

Configure the following JDA Platform service runtime environment (SRE) properties for Promotions Management. (For information about configuring SRE, see the Service Runtime Environment chapter in the JDA Platform Installation/Administration Guide. For additional information, see Modify the default configuration for processes.)

Set this value for the SRE node:

• Column name: MAX_NODES

Default: 1

Specify the maximum number of nodes allowed per node pool. Adjust this value to reflect the maximum number of concurrent users in your production environment.

Configure these properties of the Collector SRE:

• PROP_NAME: MaximumNumberOfCollectorsPerNode

Unit: none

Default: 0

Specify the maximum number of collectors that one node can contain.

Caution: Setting this value to 0 or a negative number disables this limit check. If the result is that too many collectors are created for a node, you will get an out-of-memory exception.

Configure Pricing parameters You can set values for price parameters in table PRICEGLOBALPARAM. Default values are supplied for some, but not all, records. You can set or modify default values using Oracle utilities. When setting a default, be sure to update the correct column using the appropriate data type. For example, if a record has a Type of Number, update the NumberValue column. JDA Supply Chain Planning and Optimization Configuration Guide 83 © 1997-2014 JDA Software Group, Inc.- Confidential


The following records can be configured with default values:

• DRM.APM.AD.PRODUCTION.WEBSERVICE.PASSWORD: Password for the webservices call to the JDA Advertising server.

• DRM.APM.AD.PRODUCTION.WEBSERVICE.URL: URL for the webservices call to the JDA Advertising server.

• DRM.APM.AD.PRODUCTION.WEBSERVICE.USER: Username for the webservices call to the JDA Advertising server.

• DRM.APM.AD.PRODUCTION.CLOSE.ON.IMAGE.SELECT: Determines whether the image browser automatically closes upon making an image selection or remains open, requiring you to manually close the page.

• DRM.APM.ALLOCATIONCALENDAR: Name of an allocation calendar, used as an allocation profile to adjust the base demand forecast displayed on the Performance tab in the Promotions Management workbench.

• DRM.APM.BASEDMDFCSTTYPES: A comma-separated list of FCST types to use in the calculation of the base demand forecast displayed in the Performance and Time Phased Lift tabs in the Promotions Management workbench. This parameter allows you to customize the base demand that is used for promotional lift forecasting. For more information on FCST types, see the Type column for the FCST table in the JDA Demand Reference Guide.

• DRM.APM.CANDIDATEPROCESS.PERCENTOFF: The default percent off used by the promotions candidate process when recommending product for promotion. Enter this as a decimal value. For example, a default price of 20% off is entered as 2.

• DRM.APM.CATEGORY.UDA: Name of the column in the DmdUnit table that references PromoCategory.Category.

• DRM.APM.DRAFTMODE: Indicates whether to use the FCST or FCSTDRAFT table for calculation of the base demand forecast displayed in the Performance and Time Phased Lift tabs in the Promotions Management workbench. TRUE for FCSTDRAFT table, FALSE for FCST table. This parameter also indicates the table on which Adjust Forecast for Pricing and Promotions is forecasted.

• DRM.APM.ENABLED.ADVANCEDOFFERS: Indicates whether or not the advanced offer functionality in Promotions will be used. By setting the value to false, the radio buttons on the New Offer dialog-box related to promotion type are not displayed, which prevents the creation of advanced offers.

• DRM.APM.ENABLED.COST.PRICE: Indicates that promotions planning will include the setting of promotional prices. By setting the value to True, Cost Price, Revenue, Profit and Margin attributes are displayed in the Promotions Management workbench and setting of Price Strategies is enabled. Setting the value to false indicates that Promotions Management is being used only for promotional forecasting.

• DRM.APM.ENABLED.INVENTORY: Indicates whether or not inventory metrics will be used. Setting the value to True enables the display of On Hand, Planned Receipts, and Beginning and Ending Inventory fields in the Promotions Management workbench

• DRM.APM.ENABLED.PAGES: Determines which major tabs are displayed in the Promotions Management Workbench. If both Promotions Management and Promotions Optimization are licensed, the list includes:

• PromoPlanningPage

• PromoAnalysisPage

• PromoCandidatesPage

• EventCalendarPage



To enable pages, add them to the parameter in a comma separated list. For example, PromoPlanningPage, PromoAnalysisPage, PromoCandidatesPage, EventCalendarPage. If a page is removed from the list, it is no longer displayed to users.

• DRM.APM.ENABLED.PLANNING.TABS: Determines which tabs are displayed in the Promo Planning page of the Promotions Management Workbench. By default, the list of tabs includes:

• Tactics

• Performance

• TimePhasedLift

• FactSheet

• SpaceAllocation

• PromoDetails

• PriceRules

To enable tabs, add them to the parameter in a comma separated list. For example, Tactics,Performance,TimePhasedLift,FactSheet. If a tab is removed from the list, it is no longer displayed to users.

• DRM.APM.ENABLED.PROMOACTIVITIES: Indicates whether or not promotional offers will be assigned to promotional activities managed in Event Management. By setting the value to false, the fields and searches related to selecting a promotional activity are not displayed, preventing the assignment of promotional offers to promotional activities.

• DRM.APM.ENABLED.PUBLISHFORECAST: By setting the value to true, the forecast status is set to Released when an offer is approved without additional user actions.

• DRM.APM.ENABLED.TOTALUNITS: By setting the value to True, the user is able to manually manage promotional lift on the Time Phased tab using the Total Forecast field. If the value is False, the promotional lift is managed on a period by period basis.

• DRM.APM.ENABLED.VAT: Determines if value added taxes will be utilized when planning promotions

• DRM.APM.IMPORT.HIERARCHY.LOCATION: Determines the location hierarchy to use for imported promotional offers. When a promotional offer is imported, this hierarchy will be used for the location display in the Promotions Management Workbench. If a single location hierarchy is used, this parameter is not necessary.

• DRM.APM.IMPORT.HIERARCHY.PRODUCT: Determines the product hierarchy to use for imported promotional offers. When a promotional offer is imported, this hierarchy will be used for the product display in the Promotions Management Workbench. If a single location hierarchy is used, this parameter is not necessary

• DRM.APM.MARKDOWNALLOCATION.HIERARCHYLEVEL: Enables the default configuration of the Markdown Allocation options for promotional offers using advanced pricing. If multiple product hierarchies will be used in Promotions Management, default values can be set by product hierarchy.The entry includes:

• Hierarchy name (followed by a colon)

• Number of levels to include (followed by a colon)

• Default level selection (followed by a semi-colon)

For example: Product.Hierarchy:3:3;

This parameter is not required. If the parameter is not set, all hierarchy levels except for the lowest level are displayed in drop down list, and the default selection is the top hierarchy level.



• DRM.APM.PROCESSDATE: Enables an override of the system date used in Promotions Management. This parameter is primarily used for testing efforts when it is not efficient or necessary to continually refresh data.

• DRM.APM.PROMOOFFER.PRICERULE.VIEWLOCS.THRESHOLD: Determines the number of locations to display in the Price Rules tab before switching the view to a hyperlink

• DRM.APM.VENDORFINANCIALSENABLED: Setting the value to True indicates that promotions will be planned by a supplier and activates the additional metrics necessary for determining supplier revenue and profit.

• DRM.APM.FCST.MODEL: If DRM.APM.DRAFTMODE mode is set to TRUE, specifies the MODEL to use in the FCSTDRAFT table for the base forecast data. For more information on the use of forecasting models, see FCSTDRAFT.MODEL in the JDA Demand Reference Guide or the online help for JDA Demand.

• DRM.APM.FETCHSIZE: Oracle fetch size, when reading base cost, base price, forecast, and history data.

• DRM.APM.INTEGRATEDWITHADVERTISING: Indicates if Promotions Management is integrated with the JDA Advertising server.

• DRM.APM.PRICERULEOUTPUTDIR: Name of the directory where the price rule XML files are saved when the price rule export is run.

• DRM.APM.PROMOOFFEROUTPUTDIR: Name of the directory where the promotional offer export XML files are saved when the promotional offer export is run. This parameter is used only when Promotions Management is not integrated with JDA Advertising.

• DRM.APM.PROMOTIONWITHLOYALTY: Controls whether the loyalty pricing (pricebook) feature is available for promotional offers.

• DRM.APM.READDFUBATCHSIZE: Batching size for DFUs when reading base cost, base price, forecast, and history data.

• DRM.APM.RETAILCALENDAR: Specifies which retail calendar (configured in the Cal and CalData tables) is to define the time periods on the Event Management Workbench.

• DRM.APM.TRADEPROMOTIONSENABLED: Determines whether the Vendor Trade Promotions feature is enabled.

• DRM.APM.USEPENDINGSTATE: A value of 1 indicates that the business process requires two step approval of promotions. Separate permissions are required to submit and approve a promotional offer.

• DRM.APMHIST.BATCHUPDATESIZE: Batch update size for Oracle when saving data.

• DRM.FPA.RETAILCALENDAR.PERIODS.YEAR: The number of periods to use per year in the retail calendar specified in DRM.APM.RETAILCALENDAR.

• DRM.APM.ACTIVITY.PROMOOFFER.LOADLIMIT: Indicates the number of offers that can be loaded in the Event Management Offers tab for a selected activity. Any non-negative value is valid, while the default value is 100.

For more information on pricing parameters, see the PRICEGLOBALPARAM table in the JDA Reference Guide: Markdown Optimization, Promotions Management, and Strategic Pricing.

• DRM.APM.SUPPORTED.FILTERED.TABLES: This parameter for filtered tables consists of a comma delimited list of criteria table names, which are used in the security filter to add products to a promotional offer in the Promotions Management Workbench.

For example: if the security filter criterion is related to the UDT_DMDUNIT and UDT_LOC tables, then the parameter value should be set to UDT_DMDUNIT, UDT_LOC

Note: You can set the parameter values only when there is a security filter assigned to your role.

• DRM.APM.PROMOOFFER.OPTNODELIMIT: Specifies the limit on the number of rows selected for optimization in the Tactics and Performance tab of Promotions Management Workbench.



Any non-negative value is valid, while the default value is 100.

When the limit on the number of rows selected for optimization in the Tactics and Performance tab is exceeded, a warning message is generated stating –The limit is crossed.

• DRM.APM.COLLECTOR.ALLOCATE.BY.MEMORY: Use this parameter to allocate promotional offers based on available memory on SRE nodes running the PromotionsManagement.CollectorServiceRMI job. Valid values are TRUE and FALSE. The default value is TRUE. If set to FALSE, offers are allocated based on the SRE property MaximumNumberOfCollectorsPerNode.

Configure the loyalty pricing feature With the loyalty pricing feature in Promotions Management, users can create promotional offers for specific groups of customers, such as a store's card-carrying members or high-volume customers. The forecasted lift for such an offer can be different from that for a regular offer, based on the GLINT file configuration.

To enable loyalty pricing, you must configure the system to use the pricebook feature so that users can select the appropriate pricebook on the New Offer dialog box. For example, an offer for the general public might use a pricebook called All, and an offer for membership card holders might use a pricebook called Loyalty.

Do the following to make loyalty pricing available in your system:

• In the MD_LIST_DOMAIN_VALUE and MD_LIST_DOMAIN_VALUE_TRANS tables, create a data domain to specify the valid PriceBook values. The following example creates PriceBook values of All, Loyalty, and Contractor:

INSERT INTO MD_LIST_DOMAIN_VALUE ( VALUE_NAME, DOMAIN_NAME, IS_DEFAULT )VALUES ( '1', 'SCPO_PROMOTION_PRICE_BOOK', 1);



INSERT INTO MD_LIST_DOMAIN_VALUE_TRANS ( VALUE_NAME, LANGUAGE_CODE, DISPLAY_NAME, DOMAIN_NAME )VALUES ( '1', 'en', 'All', 'SCPO_PROMOTION_PRICE_BOOK');

INSERT INTO MD_LIST_DOMAIN_VALUE_TRANS ( VALUE_NAME, LANGUAGE_CODE, DISPLAY_NAME, DOMAIN_NAME )VALUES ( '2', 'en', 'Loyalty', 'SCPO_PROMOTION_PRICE_BOOK');

INSERT INTO MD_LIST_DOMAIN_VALUE_TRANS ( VALUE_NAME, LANGUAGE_CODE, DISPLAY_NAME, DOMAIN_NAME )VALUES ( '3', 'en', 'Contractor', 'SCPO_PROMOTION_PRICE_BOOK');

INSERT INTO MD_LIST_DOMAIN_VALUE_TRANS ( VALUE_NAME, LANGUAGE_CODE, DISPLAY_NAME, DOMAIN_NAME )VALUES ( '1', NULL, 'All', 'SCPO_PROMOTION_PRICE_BOOK');

INSERT INTO MD_LIST_DOMAIN_VALUE_TRANS ( VALUE_NAME, LANGUAGE_CODE, DISPLAY_NAME, DOMAIN_NAME )VALUES ( '2', NULL, 'Loyalty', 'SCPO_PROMOTION_PRICE_BOOK');



INSERT INTO MD_LIST_DOMAIN_VALUE_TRANS ( VALUE_NAME, LANGUAGE_CODE, DISPLAY_NAME, DOMAIN_NAME )VALUES ( '3', NULL, 'Contractor', 'SCPO_PROMOTION_PRICE_BOOK');

• Configure GLINT files. As a result of GLINT file settings, the forecast lift for offers limited to loyalty card holders can differ from the forecast for offers available to all customers. The following configuration example produces a 50 percent reduction in the generated forecast for offers using PriceBook 2 and a 75 percent reduction in the generated forecast for offers using PriceBook 3 as compared to normal offers.

<ns PROMOMGMTPRICEBOOK >

CalculatedPriceRatio Divide(Eff_Price, IF(TYPICAL_PRICE > 0, TYPICAL_PRICE, List_Price))

PriceBookWt IF(PROMOMGMTPRICEBOOK == 2, 0.5, IF(PROMOMGMTPRICEBOOK == 3, 0.25, 1))

Variables:

OWNPRICE log(CalculatedPriceRatio)

……

Forecast Variables:

ForecastVar PriceBookWt * Basefcst * exp (Response) * LIFECYCLE

• Add entries to the RawVariable table:

INSERT INTO RAWVARIABLE ( RAWVARIABLE, DESCR, CALIBRATIONPROVIDERCLASS, EVALUATIONPROVIDERCLASS,

SOURCETABLE, SOURCECOL, TYPE, AGGFUNCTION, SLOTFUNCTION, DEFAULTVAL ) VALUES (

'PROMOMGMTPRICEBOOK', 'forecast lift for loyaty offers', NULL, 'com.manu.scpoweb.drm.common.evaluationcore.dataprovider.CoreEvalGrpVarDataProvider'

, ' ' , ' ' , ' ' , ' ', ' ', '0');

COMMIT;

• In the PriceGlobalParam table, set the value of the Parameter DRM.APM.PROMOTIONWITHLOYALTY to True. As a result, the New Offer dialog box and the Details tab on the Promotions Management Workbench include a PriceBook field, which enables users to select from the list of available PriceBooks.

Limit the number of offers or products displayed To help avoid Out of Memory issues, you can set search limits. For example, if you have a lot of offers with very few products, you might set a high limit for the number of open offers, but a low limit for the number of products in an offer. If your offers have a lot of products, you should set a lower limit on the number of offers and a higher limit on the number of products per offer.

The system administrator can set the following price parameters in table PRICEGLOBALPARAM:

• DRM.APM.PROMOOFFER.SEARCHLIMIT: Limits the number of promotional offers returned in a search and displayed in the Promotions Management workbench.

• DRM.APM.PROMOOFFER.PRODUCT.SEARCHLIMIT: Limits the number of products that can be included in a single promotional offer.

• DRM.APM.EVENT.SEARCHLIMIT: Limits the number of promotional activities returned in a search and displayed in the Event Management workbench.



The user is notified with a message in the Promotions Management workbench and the Event Management workbench if their search exceeds the number of offers, products or activities.

Set up offer-level security Offer-level security enables you to control who can view, change, and delete a promotional offer that meets the criteria you specify. If you do not use offer-level security, all users have full access to all offers.

To set up offer-level security, use Security Manager to create filters, assign the filters to roles, and assign the roles to users. Each filter consists of one or more equations based on column values in the Promotion table.

You can filter on a user-defined column (UDC) in the Promotion table. If you do that, you also create a user-defined attribute (UDA) that enables users to select the appropriate value for an offer on the Promotions Management workbench. For detailed information about creating UDCs and UDAs, see:

• JDA Foundation Administration Online Help: "Create a user-defined column"

• JDA Platform Installation/Administration Guide: "Metadata and data domains" and "Work with data domains"

• SCPO Installation/Administration Guide: Configure marketing instruments and user defined attributes (on page 63)

There are several ways to set up offer-level security. In each of the following examples, the system filters on a user-defined column (UDC) in the Promotion table.

Example 1: UDC values stored in metadata tables In this example, the administrator creates filters to grant access to promotional offers based on the category manager associated with the promotional offer. The filters that select promotional offers are based on the CategoryManagerUDA user-defined column (UDC) instead of on an existing column in the Promotion table.

Values for the CategoryManagerUDA UDC are stored in metadata tables (MD_LIST_DOMAIN_VALUE and MD_ LIST_DOMAIN_VALUE_TRANS). Each time a new user is added, the system administrator must add multiple rows to those tables in addition to adding the user name to the CSM_USER table.

To identify the category manager associated with each promotional offer, the creator of the offer selects a value for the Category Manager UDA, which appears on the Details tab of the Promotions Management Workbench, under Other Attributes.

The administrator wants to allow buyers for mens shirts to:

• View, update, and delete offers whose category manager is John

• View, but not change or delete, offers whose category manager is Jane or is not specified

• Be prevented from viewing offers for all other category managers

The administrator performs the following tasks.

Create a data domain for the CATEGORYMGR UDC The following tables list the values specified in the metadata tables for this example.



MD_DATA_DOMAIN

Column Value Explanation

DOMAIN_NAME SCPO_APM_UDA_CATEGORY_MGR

FUNDAMENTAL_DATA_TYPE

0 Text

MD_LIST_DOMAIN



HAS_REF_TABLE 0 The valid values for this data domain are not stored in a stand-alone reference table, but in the MD_LIST_DOMAIN_VALUE table.

In the MD_LIST_DOMAIN_VALUE table, specify the valid values for the data domain. The following table illustrates the valid values for one user (Jane) and for the default user (Unspecified). In this example, each user's name is a valid value. Create a record for each user and one record for Unspecified.

The data domain values are stored in the MD_LIST_DOMAIN_VALUE table instead of an external reference table, so the administrator must add each new user to the MD_LIST_DOMAIN_VALUE and MD_LIST_DOMAIN_VALUE_TRANS tables.

MD_LIST_DOMAIN_VALUE



VALUE_NAME Unspecified

IS_DEFAULT 1 "Unspecified" is the default value for this column.

DOMAIN_NAME SCPO_APM_UDA_CATEGORY_MGR VALUE_NAME Jane IS_DEFAULT 0 DOMAIN_NAME SCPO_APM_UDA_CATEGORY_MGR VALUE_NAME John IS_DEFAULT 0

For each Value_Name in MD_LIST_DOMAIN_VALUE, including the default value, add records to the MD_LIST_DOMAIN_VALUE_TRANS table. Add one record for each language supported by your installation. For example, if your installation supports English and French, create a record for Jane with a Language_Code of en and another record for Jane with a Language_Code of fr.



The following table illustrates the English records for Jane and the default value, Unspecified. Additional records would be created for each category manager and supported language.

MD_LIST_DOMAIN_VALUE_TRANS



VALUE_NAME Unspecified See the paragraph preceding this table. LANGUAGE_CODE en

DISPLAY_NAME Unspecified DOMAIN_NAME SCPO_APM_UDA_CATEGORY_MGR VALUE_NAME Jane LANGUAGE_CODE en DISPLAY_NAME Jane

Create a user-defined column 1. In Data Model Manager, select Tables and Columns tab.

2. Select the Promotion table from the Database Schema Hierarchy in the left pane. In the right pane, Promotion is then displayed in the Header and Description fields under Table.

3. Under Column Information, click Add.

4. Specify the following information for the new column:

• Column name: CATEGORYMGRUDA

• Header (display name): CATEGORYMGRUDA

• Description: CATEGORYMGRUDA

• Data type: Option text (Selecting this value displays the Data Domain Name list box.)

• Options: Allow updates

• Data domain name: From the list, select SCPO_APM_UDA_CATEGORY_MGR, click Go. The name is entered in the second field under Data domain name.

5. Click Go. The Data Domain Values dialog box is displayed.

6. From the Choose default value list, select Unspecified, then click Done. As a result, when a user creates a new promotional offer, the Category Manager field on the Details tab is initially set to Unspecified.

7. Click Save to save the new column to the database. A row containing the new data is added to the MD_COLUMN_INFO table. You should not need to modify this table.

Define business-object metadata for the UDA The Following table list the values specified in the business object metadata table:



MD_ATTRIBUTE


BO_NAME PromoOffer Business Object name

ATTRIBUTE_NAME CATEGORYMGRUDA

AGGREGATOR_CLASS NULL

MD_PRIMITIVE_ATTRIBUTE


BO_NAME PromoOffer Name of the Business Object


SEQ 0 SCHEMA_NAME Name of your SCPO schema TABLE_NAME PROMOTION COLUMN_NAME CATEGORYMGRUDA

The MD_PRIMITIVE_ATTRIBUTE_TRANS table stores translated versions of some data in MD_PRIMITIVE_ATTRIBUTE. As in the MD_LIST_DOMAIN_VALUE_TRANS table, you add records for each language supported by your installation, and a record for the default value (Null for Language_Code)

MD_PRIMITIVE_ATTRIBUTE_TRANS




LANGUAGE_CODE NULL Default value DISPLAY_NAME Category Mgr BO_NAME PromoOffer ATTRIBUTE_NAME CATEGORYMGRUDA LANGUAGE_CODE en DISPLAY_NAME Category Mgr

Create filters Create a filter to select promotional offers to which the shirt buyer has View access (ShirtBuyerRead) and another to select offers to which the shirt buyer has Update and Delete access (ShirtBuyerWrite).



Create the ShirtBuyerRead filter 1. Open Security Manager and select Filter tab.

2. Click Add. The Add Filter: Filter Profile page is displayed.

3. Enter the following values:

• Name: ShirtBuyerRead

• Enterprise: Manugistics

• Application: Promotions Management

• Table: SCPOMGR PROMOTION

• Description: Select the promotional offers to which shirt buyers have View access.

4. Click Next. The Add Filter: Criteria and Joins page is displayed.

5. Under Criteria, click Add. The Add Criteria page is displayed.

6. Select the following values:


• Column: CATEGORYMGRUDA

• Operator: =

• Compare with: Value

• Value: Jane

7. Click Done. The new criterion is displayed under Criteria section.

8. Repeat steps 5-7 with John as the Value.

9. Repeat steps 5-7 with Unspecified as the Value.

10. In the Filter Equation section, an equation has been created, using the Reference letters that precede each of the criteria. A, C, and D represent the three criteria you added. B is automatically added by the system; it should not be changed.

Modify the equation to look like the following:

(A | C | D) & B

Use the vertical bar to represent OR. After modifying the equation, click Preview and read the result. The preview should say:

Promotion.CategoryMgrUDA = ‘Jane’ OR Promotion.CategoryMgrUDA = ‘John’ OR Promotion.CategoryMgrUDA = ‘Unspecified’ AND Promotion.Promotion = Promotion.Promotion

11. Click Done. The filter is saved, the Add Filter page closes, and you return to the main page of Security Manager.

Create the ShirtBuyerWrite filter To create this filter, perform the same steps used to create ShirtBuyerRead, with these exceptions:

• Step 1:

Name: ShirtBuyerWrite

Description: Select the promotional offers to which shirt buyers have Update and Delete access.

• Steps 3-5: Create only two criteria. In one, enter a Value of John; in the other, enter a Value of Unspecified.

• Step 8: Modify the equation to look like the folllowing:

(A | C ) & B



Create roles and assign filters Create a ShirtBuyerRead role that gives shirt buyers Read access to selected resources. Create another role, ShirtBuyerWrite, that give shirt buyers Update and Delete access to selected resources.

1. In Security Manager, select the Role tab, then click Add. The Add Role page is displayed.


• Name: ShirtBuyerRead


• Inheritable: Do not select

• Description: Role that provides View access to selected offers.

3. Click Next, then click Next again. The Add Role page displays the Filter List section.

4. Click Add. The Assign Filter to Role dialog box is displayed.

5. Under Filter, select ShirtBuyerRead.

6. Select the For select check box. (This selection provides View access to the offers selected by the filter.)

7. Click Done. The Add Role page is displayed, showing your selections.

8. Click Done. The role is saved and the Security Manager main page is displayed.

9. Repeat steps 1-8 to create the ShirtBuyerWrite role.

a. In step 2, enter ShirtBuyerWrite as the Name.

b. In step 5, select ShirtBuyerWrite.

Assign roles to users 1. In Security Manager, select the User tab.

2. Enter PMShirtBuyer (the name of the user to whom you want to assign roles) in the User Name field, then click Go. The users name and information are displayed.

3. Click Edit in the PMShirtBuyer row. The Edit User page is displayed.

4. Select the Assign Roles tab.

5. From Available Roles list, select the roles to assign to this user:

• ShirtBuyerRead

• ShirtBuyerWrite

6. Click the right arrow to move the roles to the Roles list.

7. Click Done.

Users apply offer-level security to a promotional offer On the Promotions Management Workbench, the CategoryMgr UDA appears on the Details tab, under Other Attributes. When a user creates a promotional offer, the initial CategoryMgr value is Unspecified. To apply offer-level security to that promotion, the user selects the appropriate name from the displayed list of Category Managers.

When a user performs a search for promotional offers, the Category Manager value is used to filter out offers to which the user does not have access.



Example 2: UDC values specified in a reference table This example achieves the same goal as Example 1, in that the administrator grants access to promotional offers based on the product category manager that is associated with the offer. However this example, uses Security Manager filters to restrict the viewing of promotional offers based on the CategoryMgr user-defined column (UDC). The valid values for this UDC are determined by the data domain that the administrator must create. This data domain is based on a reference table (CSM_ROLE).

When a new user is added, the system administrator needs only to add the user name to the CSM_ USER table and assign the correct roles. The administrator does not need to modify data domains, as required in Example 1.

To identify the product category associated with each promotional offer, the creator of the offer selects a value for the CategoryMgr UDA, which appears on the Details tab of the Promotions Management Workbench, under Other Attributes.

In this example, the administrator wants to allow buyers and category managers to view, update, and delete promotional offers only for the products for which they are responsible.

To set up offer-level security using this method, the administrator performs the task in the following sections:

Create a data domain for the CATEGORY UDA The following tables list the values specified in the metadata tables for this example.

MD_DATA_DOMAIN



FUNDAMENTAL_DATA_TYPE

0 Text

MD_LIST_DOMAIN



HAS_REF_TABLE 1 The valid values for this data domain are stored in a stand-alone reference table.

REF_TABLE_SCHEMA_NAME

WWFMGR “Unspecified” is the default value for this column.

REF_TABLE CSM_USER_ROLE REF_TABLE_SQL_CONDITION

'ROLE_ID IN (SELECT ROLE_ID FROM CSM_ROLE WHERE ROLE_NAME = "PromotionsManagementCategoryManager")'

REF_VALUE_COLUMN USER_NAME REF_IS_DEFAULT_COLUMN

NULL



MD_LIST_DOMAIN


REF_TRANS_TABLE_SCHEMA_NAME

NULL

REF_TRANS_TABLE NULL REF_TRANS_LANGUAGE_CODE_COLUMN

NULL

REF_TRANS_COUNTRY_CODE_COLUMN

NULL

REF_TRANS_VALUE_COLUMN

NULL

REF_TRANS_DISPLAY_COLUMN

NULL

REF_TRANS_DESCRIPTION_COLUMN

NULL

Create a user-defined column 1. In Data Model Manager,

2. Select the Tables and Columns tab,

3. Select the Promotion table from the Database Schema Hierarchy in the left pane. In the right pane, Promotion is then displayed in the Header and Description fields under the Table Information.

4. Under Column Information, click Add.

5. Specify the following information for the new column:

• Column name: CATEGORYMGR

• Header (display name): CATEGORYMGR

• Description: CATEGORYMGR

• Data type: Option text (Selecting this value displays the Data Domain Name list box.)

• Options: Allow updates

• Data domain name: From the list, select SCPO_APM_UDA_CATEGORY, then click Go. The name is entered in the second field under Data domain name.

6. Click Go. The Data Domain Values dialog box is displayed.

7. From the Choose default value list, select Unspecified, then click Done. As a result, when a user creates a new promotional offer, the Category field on the Details tab will initially have a value of Unspecified.

8. Click Save to save the new column to the database. A row containing the new data is added to the MD_COLUMN_INFO table. You should not need to modify this table.

Define business-object metadata for the UDA The following tables list the values specified in the metadata tables for this example.



MD_ATTRIBUTE



ATTRIBUTE_NAME CategoryManager AGGREGATOR_CLASS NULL

TYPE PRIMITIVE

MD_PRIMITIVE_INFO


PRIMITIVE_ID PromoOffer.CategoryMgr

LOGICAL_DATA_TYPE_NAME

OPTION_TEXT


IS_USER_UPDATEABLE 1 IS_USER_DEFINED 1 IS_USER_REQUIRED 1 IS_USER_INSERTABLE 1 IS_NULLABLE 0




ATTRIBUTE_NAME CategoryManager By convention, attribute names are usually spelled out completely, but the administrator may choose to give them the same name as the UDC.

SEQ 0 Used only for compound primitives, such as currency attributes, which might have a column for the currency amount and a separate column for the currency code.

PRIMITIVE_ID PromoOffer.CategoryMgr Refers to the MD_PRIMITIVE_INFO table, where you define the relationship to the data domain that you have created for Category Managers.

SCHEMA_NAME Name of your SCPO schema

TABLE_NAME PROMOTION





COLUMN_NAME CATEGORYMGR

The MD_PRIMITIVE_ATTRIBUTE_TRANS table stores translated versions of some data in MD_PRIMITIVE_ATTRIBUTE. Add records for each language supported by your installation, and a record for the default value (using Null for Language_Code)

MD_PRIMITIVE_ATTRIBUTE_TRANS



ATTRIBUTE_NAME CategoryManager LANGUAGE_CODE NULL Default value

DISPLAY_NAME Category Manager LANGUAGE_CODE en DISPLAY_NAME Category Manager

Create filters for product categories Create a filter for each product category to enable category managers and category assistants to view, edit, and delete promotional offers for their products.

Create the Cosmetics filter 1. In Security Manager, select the Filter tab.

2. Click Add. The Add Filter: Filter Profile page is displayed.


• Name: CosmeticsFilter


• Application: Promotions Management


• Description: Restrict access to Cosmetics promotions

4. Click Next. The Add Filter: Criteria and Joins page is displayed.

5. Under Criteria, click Add. The Add Criteria page is displayed.

6. Select the following values:


• Column: CATEGORYMGR

• Operator: =

• Compare with: Value JDA Supply Chain Planning and Optimization Configuration Guide 98 © 1997-2014 JDA Software Group, Inc.- Confidential


• Value: The USER_NAME from the CSM_USER table for the manager of the Cosmetics department

7. Click Done. The new criterion is displayed under Criteria.

8. In the Filter Equation section, an equation has been created, using the reference letters that precede each of the criteria. A represents the new criterion you added. B is automatically added by the system; it should not be changed. Modify the equation to look like the following:

A & B

The preview should say:

Promotion.Category = '<the name of the category manage>' AND Promotion.Promotion = Promotion.Promotion

9. Click Done. The filter is saved, the Add Filter page closes, and the main page of Security Manager is displayed.

10. Create two additional filters. Use the Grocery and OTC Manager names as the value in step 6.

Create roles and assign filters Create one role for each product category on which you want to filter (Cosmetics, Grocery, and OTC) and assign the corresponding filters to the roles. Create another role called Unspecified, but do not assign it a filter.

In addition, create roles called PromotionsManagementCategoryManager and PromotionsManagementBuyer. Do not assign filters to them.

1. On the Role tab in Security Manager, click Add. The Add Role page is displayed.


• Name: CosmeticsBuyer


• Inheritable: Do not select

• Description: Cosmetics buyers and category managers

3. Click Next, then click Next again. The Add Role page displays the Filter List section.

4. Click Add. The Assign Filter to Role dialog box is displayed.

5. Under Filter, select CosmeticsFilter.

6. Select all check boxes (For select, For update, For delete). These selections provide view, edit, and delete access to the offers selected by the filter.

7. Click Done. The Add Role page is displayed, showing your selections.

8. Click Done. The role is saved and the Security Manager main page is displayed.

9. Repeat steps 1 through 8 to create the Grocery and OTC roles.

10. To create the Unspecified, PromotionsManagementCategoryManagement, and PromotionsManagementBuyer roles, which do not use filters, repeat steps 1 through 3, then click Done.

Assign Category Manager and Buyer roles to users You must assign the PromotionsManagementCategoryManager role to all category managers, and assign the PromotionsManagementBuyer role to all buyers and category managers.

You must also assign specific product category roles to each category manager and buyer.

1. In Security Manager, select the User tab.



2. Enter the name of the user to whom you want to assign roles in the User Name field, then click Go. The users name and information are displayed.

3. Click Edit in the row for this user. The Edit User page is displayed.

4. Select the Assign Roles tab.

5. From the Available Roles list, select the roles to assign to this user.

6. Click the right arrow to move selected roles to the Roles list.

7. Click Done.

Users apply offer-level security to a promotional offer On the Promotions Management Workbench, the Category UDA appears on the Details tab, under Other Attributes. When a user creates a promotional offer, the initial Category value is Unspecified. To apply offer-level security to that promotion, the user selects the appropriate name from the displayed list of Category Buyer roles.

When a user performs a search for promotional offers, the Category filters are used to filter out offers to which the user does not have access.

Set up the event calendar To specify the retail periods on the Event Management Workbench, you must create a Reporting calendar (Type 3) in the Cal table and define its time periods in the CalData table. In CalData, enter a row for each period in the calendar pattern and specify its Opt value as 6 (Reporting). For example, for a 4-5-4 calendar, you can define a row for each of the three periods (for 4, 5, and 4 weeks) followed by a row with the Repeat option (Opt 5) to repeat that 13-week pattern:

Cal Eff Opt Repeat

454 1/31/2010 6

454 2/28/2010 6

454 4/04/2010 6

454 5/02/2010 6 13W

Specify the name of the calendar in the PriceGlobalParam table (DPM.APM.RETAILCALENDAR) parameter), as explained in the online Help for that table and in the JDA Reference Guide: Markdown Optimization, Promotions Management, Shelf Price Optimization.


Configure JDA Strategic Pricing

Chapter 9. Configure JDA Strategic Pricing Set up data Before using JDA Strategic Pricing, you must set up the necessary business objects in the database. This section provides instruction to change the initial configuration of JDA Strategic Pricing version 8.1.0.0. You must install JDA SCPO 8.1.0.0 before performing the procedures in this section. For information on using this application, select Help in JDA Strategic Pricing.

Configure hierarchies for JDA Strategic Pricing The JDA Foundation schema provides a table to define hierarchies for any of the SCPO applications. For JDA Strategic Pricing, part of the configuration required is to define the hierarchies for your company.

Note: The hierarchies used in JDA Strategic Pricing are built using the SCPO schema. Typically, you will use user-defined columns as the different levels of your hierarchy. Use the JDA Foundation Data Model Manager to define the columns to use in your hierarchies before setting up the hierarchy metadata.

Set up the required hierarchy dimensions You must first create the dimensions you want to use in Strategic Pricing.



INSERT INTO MDD_DIMENSION_TRANS (DIMENSION_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('SPO.Product', 'en', NULL, 'Product', 'Product dimension');


To set-up a hierarchy to be used by Strategic Pricing, you must first insert one row into the MD_HIERARCHY table and one row for each language you will be using into the translation table, MD_HIERARCHY_TRANS. The value you use for the column MD_HIERARCHY.DIMENSION_NAME must match the DIMENSION_NAME defined in the MD_DIMENSION table. The HIERARCHY_NAME and HIERARCHY_ID can be set to be based on your business requirements. For example, if your business only requires one hierarchy for products, you might run the following statement to create a hierarchy:

INSERT INTO MD_HIERARCHY (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_ID) VALUES ('SPO.Product', 'Product', 101);



Configure JDA Strategic Pricing

INSERT INTO MD_HIERARCHY_TRANS (DIMENSION_NAME, HIERARCHY_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('SPO.Product', 'Product', 'en', NULL, 'Product Hierarchy', 'Groups Products by Department, Subdepartment, Class, Style.');


INSERT INTO MD_HIERARCHY_LEVEL (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_LEVEL_NAME, HIERARCHY_LEVEL_ID, LEVEL_NUM, SCHEMA_NAME, TABLE_NAME, COLUMN_NAME) VALUES ('SPO.Product', 'Product', 'Department', 10000000515, 1, 'SCPOMGR_NEW', 'DMDUNIT', 'U_DEPT');



In the LocHierarchyName column of the PromoReportingLvl table, specify the name of each hierarchy. If Strategic Pricing is integrated with JDA Advertising, you must also specify values in the PriceZoneCol, AdZoneCol, and AdZoneAbbrCol columns in PromoReportingLvl table. Specify the names of the Loc table's UDA columns for price zone, ad zone, and ad zone abbreviation. That information enables the system to identify the columns that hold price zone and ad zone data for a vehicle to which a specific marketing instrument is assigned.


Configure JDA Demand Decomposition

Chapter 10. Configure JDA Demand Decomposition Set up data Before using JDA Demand Decomposition, you must set up the necessary business objects in the database. This section provides instruction to change the initial configuration of JDA Demand Decomposition version 8.1.0.0. You must install JDA SCPO 8.1.0.0 before performing the procedures in this section. For information on using this application, select Help in JDA Demand Decomposition.

Configure hierarchies for JDA Demand Decomposition The JDA Foundation schema provides a table to define hierarchies for any of the SCPO applications. For JDA Demand Decomposition, part of the configuration required is to define the hierarchies for your company.

Note: The hierarchies used in JDA Demand Decomposition are built using the SCPO schema. Typically, you will use user-defined columns as the different levels of your hierarchy. Use the JDA Foundation Data Model Manager to define the columns to use in your hierarchies before setting up the hierarchy metadata.

Set up the required hierarchy dimensions You must first create the dimensions you want to use in Demand Decomposition.



INSERT INTO MDD_DIMENSION_TRANS (DIMENSION_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('DemandDecomp.Product', 'en', NULL, 'Product', 'Product dimension');


To set-up a hierarchy to be used by Demand Decomposition, you must first insert one row into the MD_HIERARCHY table and one row for each language you will be using into the translation table, MD_HIERARCHY_TRANS. The value you use for the column MD_HIERARCHY.DIMENSION_NAME must match the DIMENSION_NAME defined in the MD_DIMENSION table. The HIERARCHY_NAME and HIERARCHY_ID can be set to be based on your business requirements. For example, if your business only requires one hierarchy for products, you might run the following statement to create a hierarchy:

INSERT INTO MD_HIERARCHY (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_ID) VALUES (‘DemandDecomp.Product', 'Product', 101);




INSERT INTO MD_HIERARCHY_TRANS (DIMENSION_NAME, HIERARCHY_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES (‘DemandDecomp.Product', 'Product', 'en', NULL, 'Product Hierarchy', 'Groups Products by Department, Subdepartment, Class, Style.');


INSERT INTO MD_HIERARCHY_LEVEL (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_LEVEL_NAME, HIERARCHY_LEVEL_ID, LEVEL_NUM, SCHEMA_NAME, TABLE_NAME, COLUMN_NAME) VALUES (‘DemandDecomp.Product', 'Product', 'Department', 10000000515, 1, 'SCPOMGR_NEW', 'DMDUNIT', 'U_DEPT');



In the LocHierarchyName column of the PromoReportingLvl table, specify the name of each hierarchy. If Demand Decomposition is integrated with JDA Advertising, you must also specify values in the PriceZoneCol, AdZoneCol, and AdZoneAbbrCol columns in PromoReportingLvl table. Specify the names of the Loc table's UDA columns for price zone, ad zone, and ad zone abbreviation. That information enables the system to identify the columns that hold price zone and ad zone data for a vehicle to which a specific marketing instrument is assigned.






• MRMCAUSALFACTOR


• MRMCOEF

• MRMCOEFDRAFT


• MRMEXPERIMENT

• MRMGROUP



• MRMGROUPLRSTAT


• MRMODEL

• MRMPROXY












Parameter















Configure JDA Markdown Optimization

Chapter 11. Configure JDA Markdown Optimization Set up data Before using JDA Markdown Optimization , you must set up the necessary business objects in the database. This section provides instruction to change the initial configuration of JDA Markdown Optimization version 8.1.0.0. You must install JDA SCPO 8.1.0.0 before performing the procedures in this section. For information on using this application, select Help in JDA Markdown Optimization.

Configure hierarchies for JDA Markdown Optimization The JDA Foundation schema provides a table to define hierarchies for any of the SCPO applications. For JDA Markdown Optimization, part of the configuration required is to define the hierarchies for your company.

Note: The hierarchies used in JDA Markdown Optimization are built using the SCPO schema. Typically, you will use user-defined columns as the different levels of your hierarchy. Use the JDA Foundation Data Model Manager to define the columns to use in your hierarchies before setting up the hierarchy metadata.

Set up the required hierarchy dimensions You must first create the dimensions you want to use in Markdown Optimization.



INSERT INTO MDD_DIMENSION_TRANS (DIMENSION_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('Markdown.Product', 'en', NULL, 'Product', 'Product dimension');


To set-up a hierarchy to be used by JDA Markdown Optimization, you must first insert one row into the MD_HIERARCHY table and one row for each language you will be using into the translation table, MD_HIERARCHY_TRANS. The value you use for the column MD_HIERARCHY.DIMENSION_NAME must match the DIMENSION_NAME defined in the MD_DIMENSION table. The HIERARCHY_NAME and HIERARCHY_ID can be set to be based on your business requirements. For example, if your business only requires one hierarchy for products, you might run the following statement to create a hierarchy:

INSERT INTO MD_HIERARCHY (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_ID) VALUES ('Markdown.Product', 'Product', 101);




INSERT INTO MD_HIERARCHY_TRANS (DIMENSION_NAME, HIERARCHY_NAME, LANGUAGE_CODE, COUNTRY_CODE, DISPLAY_NAME, DESCRIPTION) VALUES ('Markdown.Product', 'Product', 'en', NULL, 'Product Hierarchy', 'Groups Products by Department, Subdepartment, Class, Style.');


INSERT INTO MD_HIERARCHY_LEVEL (DIMENSION_NAME, HIERARCHY_NAME, HIERARCHY_LEVEL_NAME, HIERARCHY_LEVEL_ID, LEVEL_NUM, SCHEMA_NAME, TABLE_NAME, COLUMN_NAME) VALUES ('Markdown.Product', 'Product', 'Department', 10000000515, 1, 'SCPOMGR_NEW', 'DMDUNIT', 'U_DEPT');



In the LocHierarchyName column of the PromoReportingLvl table, specify the name of each hierarchy. If Markdown Optimization is integrated with JDA Advertising, you must also specify values in the PriceZoneCol, AdZoneCol, and AdZoneAbbrCol columns in PromoReportingLvl table. Specify the names of the Loc table's UDA columns for price zone, ad zone, and ad zone abbreviation. That information enables the system to identify the columns that hold price zone and ad zone data for a vehicle to which a specific marketing instrument is assigned.






• MRMCAUSALFACTOR


• MRMCOEF

• MRMCOEFDRAFT


• MRMEXPERIMENT

• MRMGROUP



• MRMGROUPLRSTAT


• MRMODEL

• MRMPROXY












Parameter















Configure JDA Production and Sourcing Optimization

Chapter 12. Configure JDA Production and Sourcing Optimization Perform specific configuration tasks before you can use the system:

Enable users to commit scenarios If you plan to allow JDA Production and Sourcing Optimization users to use scenarios and commit them to the database, you must add referential integrity constraints on the scenario (SIM_) tables.

Caution: Committing a scenario replaces data in the live database with the scenario data. Ensure that your database has been backed up before proceeding. Also, after you enable this feature, users no longer can specify tables to load in scenarios. Instead, all tables are loaded.


2. Change to directory <install_dir>\config\scpoweb\database.

3. To enable Production and Sourcing Optimization users to commit scenarios, change the default value for the ScenarioCommit property in scpo_config.properties in System Properties to On. See Modify a SCPO properties file.

4. Using SQL*Plus, run add_sim_constraints.sql as the SCPO schema owner. For example:

sqlplus scpomgr/scpomgr @add_sim_constraints.sql

The script queries the constraints on the live tables and enables foreign key constraints on the scenario tables. It also creates a log file add_sim_cons.log.

Notes:

• Perform this task initially after database creation or migration. Subsequently, rerun this script each time a live table changes, so the changes are reflected in the scenario.

• Only the original scenario owner can commit the scenario to the database. In addition, the user must have the necessary security privileges. See "Implement security (on page 8)".

• See the online help for Scenario Manager for more information on committing scenarios.

Customize units of measure The Unit of Measure (UOM) identifies how to measure the resources being used, consumed, and produced within your supply chain model. For example, the capacity of a truck can be specified in weight or volume. JDA Production and Sourcing Optimization provides several UOMs by default. You can define additional categories or units of measure using Flexible Editor. You can also define UOM conversions within a category. For more information on using the Flexible Editor, see the JDA Foundation User OnLine Expert. For information on defining the default UOM settings, see the Production and Sourcing Optimization Preferences page in the application.


Configure JDA Enterprise Supply Planning

Chapter 13. Configure JDA Enterprise Supply Planning This section provides instruction to change the initial configuration of JDA Enterprise Supply Planning version 8.1.0.0. You must install JDA SCPO 8.1.0.0 before performing the procedures in this section. For information on using this application, select Help in JDA Enterprise Supply Planning.

Set SRE node configuration properties Configure the following JDA Platform service runtime environment (SRE) properties for Enterprise Supply Planning. (For information about configuring SRE, see the "Service Runtime Environment" chapter in the JDA Platform Installation/Administration Guide. For additional information, see Modify the default configuration for processes.)

The path for Oracle SQL loader file must be specified for the following services:

• ESP.GenerateMasterPlan.LpOpt

• ESP.GenerateMasterPlan.Map

Enter the following SRE properties in SRE_NODE_CONFIG_PROPS (this table can be found in the platform schema):

• PROP_NAME: OracleSqlldrDirPath

• SERVICE_NAME: As specified above

• PROP_VALUE: Specify the location of the Oracle SQL loader executable. For example:

• In windows: If you have installed oracle client in d:/oracle/product/11.2.0.3, specify the path as follows: d:/oracle/product/11.2.0.3/dbhome_1/bin. Verify that the file sqlldr.exe is present in this directory.

• In Unix: If you have installed oracle client in /tools/oracle/product/11.2.0.3, specify the path as follows: /tools/oracle/product/11.2.0.3/dbhome_1/bin. Verify that the file sqlldr is present in this directory.

Note: This has to be done for all the node configurations used for ESP.


Compressed Data Storage

Chapter 14. Compressed Data Storage With the increase in the number of JDA’s large retail customer deals, the scalability of batch processes has assumed great importance. With databases to the tune of hundreds of millions of DFUs, the traditional approach to processes was not sufficient to achieve satisfactory performance.

Storing time-phased data for a large number of DFUs consumes a large amount of space. Also, the number of rows in these tables increases to much larger numbers. There are multiple tables in SCPO that store time-phased data. The largest of these are the Hist, Fcst, FcstDraft, and DFUToSKUFcst tables. Due to the large size of the tables, the performance of the batch processes was adversely affected. So, an alternate method of storing data, the Compressed Data Storage (CDS) method, is introduced to overcome these issues.

What is Compressed Data Storage? The Hist, Fcst, FcstDraft, and DFUToSKUFcst time-phased tables consist of one record for each period, including a Start Date and Duration value for the period. So, a forecast with two years of weekly data for each DFU contains 104 records for each DFU. When you use the Compressed Data Storage (CDS) functionality, the time-phased data is stored in just one record instead of separate records being stored for each time period.

The CDS tables contain one record for each DFU, with 104 quantity columns for the 2 years of values. The Demand Calendar field and the start date are specified with each record. The start date of the ‘nth’ period can be calculated by referring to the ‘nth’ period of the specified calendar after the start date.

Along with the wide tables, the CDS structure also allows data to be stored with start date and duration. These tables are called narrow tables.

Currently, the following are stored in the Compressed Data Storage format:

• Regular tables: Hist, Fcst, FcstDraft, DFUToSKUFcst

• CDS Enabled:

• Wide tables: HistWide, FcstWide, FcstDraftWide, LewMeanQtyWide, DFUToSKUFcst

• Narrow tables: HistNarrow, FcstNarrow, FcstDraftNarrow, DFUToSKUFcst

The wide and narrow tables are meant to be the alternate storage mechanisms for regular Hist, Fcst/FcstDraft, and DFUToSKUFcst tables.

Structure of regular tables Hist Table:

DmdUnit DmdGroup Loc HistStream

StartDate

Type Event

Dur Qty

Fcst/FcstDraft Table:

DmdUnit

DmdGroup

Loc Model

StartDate

Type

FcstID

MarketMgrVersionI

D

LewMeanQty

Dur Qty



DFUToSKUFcst Table:

DmdUn

it DFULo

c

DmdGrou

p Item SKULoc TYPE

StartDate Dur

SupersedeSw

TotFcst

FF_TRIGGER_CONTROL

Structure of CDS tables HistWide Table:

DmdUnit

DmdGroup

Loc

HistStream

StartDate

Type

Event

DmdCa

l

Period 1

Period 2

Period .....

Period N

HistNarrow Table:

DmdUnit DmdGroup

Loc HistStream StartDate

Type Event Dur Qty

FcstWide/FcstDraftWide Table:

DmdUnit

DmdGroup

Loc Model

StartDate

Type

FcstID DmdCal

Period 1

Period 2

Period

.......

Period N

FcstNarrow/FcstDraftNarrow Table:

DmdUnit

DmdGroup

Loc Model StartDate

Type FcstID MarketMgrVersionID

Dur Qty

FcstLewMeanQtyWide Table:

DmdUnit

DmdGroup

Loc Model

StartDate

Publish

DmdCal Period 1

Period 2

Period .......

Period N

Note: In the CDS enabled mode, if you use flexible editor instances based on the Hist, Fcst or FcstDraft tables, they are actually reading and writing the corresponding wide and narrow tables. The Hist, Fcst or FcstDraft tables themselves are never accessed by flexible editor.

DfuToSkuFcstWide Table:



DmdUn

it

DmdGroup

DFULoc

Item SKULoc

Type

SupersedeSW

FF_Trigger_Contr

ol

DmdCa

l

StartDate

Period1

Period ……

Period N

DFUToSKUFcst Narrow Table:

DmdUn

it DFULo

c

DmdGrou

p Item SKULoc TYPE

StartDate Dur

SupersedeSw

TotFcst

FF_TRIGGER_CONTROL

Note: In the CDS enabled mode, if you use flexible editor instances based on the DFUToSKUFcst table, those instances are reading the corresponding wide and narrow tables. The DFUToSKUFcst table is never accessed by flexible editor.

Details and flow chart To facilitate migration of existing customers to the CDS enabled system, two new processes, Move History and Merge Forecast are available. These processes move data from the existing Hist table to CDS History tables, and move the forecast from the CDS Forecast/Draft Tables to the Fcst/FcstDraft table. These processes are required if systems interface with the Hist and Fcst tables.

Figure 1: Process Flow without Compressed Data Storage



Figure 2: Process Flow with Compressed Data Storage

You can also simplify the process flow by changing your data interfaces to directly interact with the CDS tables as below:



Figure 3: Process Flow with Compressed Data Storage (Simplified Data Interfaces)

Note: Other SCPO products work directly with the CDS tables. There is no need to run the Merge Forecast process.

Advantages The CDS Implementation is primarily intended to improve performance.

• Reduces the runtime of critical processes that are based on CDS tables, in some cases by more than 50%.

• Significantly reduces the storage space requirements of the database.

Business Implications Short Term and Long Term forecasting:

For a CDS enabled system, the maximum forecast horizon is fixed for a given calendar (for example, with a Weekly Calendar and with 104 forecast periods, a forecast for a maximum of two years can be calculated). Therefore, it is not possible to perform a one-off long term forecast (5 yrs in the example above). In order to forecast long term, you will need to increase the number of periods using the CDS Configuration script and reduce the size after validating the forecast.

Multi-Model in published mode:

A CDS enabled application supports only one published model for each DFU. Hence, you cannot publish different models at different periods. (for example, Lew Model for Jan to Feb and Fourier Model for March to December)

Limitations when using CDS tables Some functionality that is available with non-CDS tables is disabled when the Compressed Data Storage feature is enabled. The limitations that are imposed on applications due to CDS implementation are summarized below: JDA Supply Chain Planning and Optimization Configuration Guide 117 © 1997-2014 JDA Software Group, Inc.- Confidential


Platform limitations Search

• You cannot create or use a search with Fcst, FcstDraft, Hist or DFUToSKUFcst as a primary table.

• You cannot add criteria based on the Fcst, FcstDraft, Hist or DFUToSKUFcst tables, even if the primary table is some other table.

Security

You cannot create or use role filters on the StartDate, Dur or Qty columns for the Fcst, FcstDraft, Hist or DFUToSKUFcst tables.

User-defined Tables and User-defined Columns

• User-defined tables based on Fcst, FcstDraft, Hist, and DFUToSKUFcst tables are not supported.

• User-defined columns are not supported on CDS tables.

Lookup

The Lookup icon is not displayed for StartDate, Dur, and Qty columns of Fcst, FcstDraft Hist or DFUToSKUFcst tables.

Flexible Editor

The following limitations are imposed on the flexible editor functionality:

• Expressions, Filters, and Paging are not supported for Startdate, Dur, and Qty columns from CDS enabled tables.

• Outer Joins ('Show All from Primary Table' in the Data Options tab) are not supported.

• Columns based on one-to-one or one-to-many relations from CDS instances are not supported.

• Start Date and Dur columns are not editable.

• Import is supported on CDS Narrow tables but not on CDS Wide tables.

• Delete All is not supported for CDS tables.

• Adding flexible editor records for DFUs which are not already in the CDS tables is not supported.

• Adding new values before the beginning or after the end of the CDS record is not supported.

• Some flexible editor actions such as paging, filtering, sorting, and copying are not supported on LewMeanQty and MarketMgrVersionID columns of Fcst/FcstDraft.

• SRE implementation is not supported for CDS flexible editor instances.

• While setting up a CDS Flexible Editor instance for Time Allocation, the Duration field on the Data Options tab must be populated.

• While navigating from a CDS instance to another CDS instance, the target instance displays all of the date records for a given DFU, not just the date records selected in the source instance.

• In some cases, exceptions such as 'Unknown System exception: com.manu.Gensys.SCPOWebException' are generated due to certain actions or data situations. For more information about occurance of these errors, please contact JDA with the appropriate information logged by the server.

Demand limitations History and Forecast type

• History-Type1 and Forecast-Type1 records are stored only in the HISTWIDE, FCSTWIDE, and FCSTDRAFTWIDE tables. Type 1 values cannot be populated in the corresponding narrow tables.



• History-Type2, Type3 and Forecast-Type3, Type8, Type9 are stored only in the HISTNARROW, FCSTNARROW, and FCSTDRAFTNARROW tables. These types cannot be populated in the corresponding wide tables. The remaining forecast types are populated either in wide or narrow tables according to the process or application workbench from where the forecast is generated.

History and Forecast IDs

The IDs for various history and forecast types differ according to the process or application workbench from where the forecast is generated. The following are a few examples:

• Override Manager:

• OVERRIDE-TIMESTAMP-USERNAME (OVERRIDE-2010/05/18 04:26:57:974-SUPERUSER)

• Flexible Allocation:

• FLEX ALLOC-TIMESTAMP (FLEX ALLOC-2010/03/29 10:12:14:704) OR

• USER PROVIDED FCST ID-TIMESTAMP (ABC-2010/03/29 10:12:14:704)

• Compress Events process:

• COMPRESS_TIMESTAMP_RUNNINGCOUNTER

• Demand Workbench (No time stamps):

• FOR LOCK - FCSTLOCK

• FOR FORECAST OVERRIDE – OVERRIDE

• FOR HISTORY OVERRIDE – OVERRIDE

• Decision Support Workbench (No time stamps):

• FOR LOCK - FCSTLOCK

• FOR FORECAST OVERRIDE – OVERRIDE

• FOR HISTORY OVERRIDE – OVERRIDE

Note: Timestamps in FcstIDs are used only for forecasts generated from the Override Manager, Flexible Allocation, and Compress Events.

History and Forecast Duration

The number of periods for history and forecast tables can be controlled using the configure compressed data storage script.

Calculate Model

If the Calculate Model process is run with the PurgeAll switch ON, the performance may be degraded as all CDS table records are updated for Discontinue Date.

To increase throughput of Calculate Model process, dynamic mean in Lewandowski model is not stored in database anymore. This behavior can be controlled by the switch in the SRE_NODE_CONFIG_PROPS. Corresponding data is stored in the LewMeanQtyWide system table.

The MarketManagerVersionID value is stored in the FcstNarrow and FcstDraftNarrow tables.

In the publish mode (FcstWide and FcstNarrow), only single model data is supported. To support multi-model in the publish mode, the Publish Forecast process needs to clean up the CDS records for overlapping periods.

Import Forecast

The DisableChecks property is added in the SRE_NODE_CONFIG_PROPS table to skip the validation for effective and discontinue dates, and the history startdate and postdate while running the Import Forecast process.



Fulfillment limitations Plan Analysis:

Pegging on the DFUToSKUFcst table is not implemented and the results can be inaccurate. The data is still read from the DFUToSKUFcst table.

Flexible Editor:

The DFUToSKUFcst table is non-editable. All platform limitations apply to the DFUTOoSKUFcst table except a few of the limitations related to its editing.

Transfer Forecast process:

When the Transfer Forecast process is run, data is transferred from the FcstWide or FcstNarrow tables to the DFUToSKUFcstWide or DFUToSKUFcstNarrow tables.

Behavior of the Transfer forecast process for below scenarios:

If the Delete Prior Forecast checkbox is set to False, the existing forecast is retained. If you run the new forecast beyond the selected horizon (MD_TABLE_EXT - Number of periods), the new forecast is not transferred and a SKU Exception is displayed. For example: Assume, FcstWide is run with records starting from 06/01/2000 for the next 52 periods. The existing forecast is retained from 01/01/2000 to 05/31/2000. The existing forecast from 06/01/2000 to 12/31/2000 is updated with the latest forecast. The remaining forecast is not transferred. A SKU exception: "DFUToSKUFcstWide period length is insufficient" is displayed.

If you want to update forecast for a particular period, select the Delete Prior Forecast checkbox is set to False. The forecast lying before and after the chosen period are not changed. For example: Assume, FcstWide is run with records starting from 06/01/2000 for the next four periods only. The existing forecast is retained before and after the chosen four periods. The forecast is updated only for the chosen four periods.

Reporting limitations The Expand calendar process should be run before obtaining a report based on history or forecast tables. This populates the expanded calendar table with the startdate, and duration for the periods in the given date range.

• New PL/SQL Package is added to dynamically merge CDS based tables

• Reports will need to be modified to be pulled from this new package rather than from history or forecast tables

Monitor limitations • Data Comparison Business rules cannot be created based on Qty, StartDate, or Dur columns.



Index . .Net UI Common Properties • 49

A Add marketing instruments to the database • 64 Add values to cost elements • 74 Administer user-defined tables and user-defined columns •

40 Advantages • 117 Approve Order • 50, 51 Assign Category Manager and Buyer roles to users • 99 Assign roles to users • 94

B Back up and restoring databases • 41 Business functions • 50, 54 Business Implications • 117

C Calculate Allocations • 54 Change SOQ • 51 Change SOQ/Clear SOQ • 51 Change the Allocation level or hierarchy • 53 Commit Allocation • 54 Common database tables • 40 Compressed Data Storage • 113 Configure activity types • 71 Configure AllocMaster table • 53 Configure Candidate ID • 81 Configure DFU cost elements • 73 Configure hierarchies for JDA Demand Decomposition •

103 Configure hierarchies for JDA Markdown Optimization •

107 Configure hierarchies for JDA Promotions Management •

61 Configure hierarchies for JDA Strategic Pricing • 101 Configure integration between JDA Promotions

Management and JDA Advertising • 76 Configure JDA Demand • 42 Configure JDA Demand Decomposition • 103 Configure JDA Enterprise Supply Planning • 112 Configure JDA Fulfillment • 49 Configure JDA Markdown Optimization • 107 Configure JDA Production and Sourcing Optimization •

111

Configure JDA Promotions Management • 61 Configure JDA Strategic Pricing • 101 Configure marketing instruments • 64 Configure marketing instruments and user defined attributes

• 63 Configure Modeling Workbench • 78, 104, 108 Configure Pricing parameters • 83 Configure product categories • 75 Configure promotional activity tasks • 72 Configure the loyalty pricing feature • 87 Configure the SCPO application • 2 Configure user-defined attributes • 63 Constrained Supply Online Actions • 51 Control user access • 2 Copy databases • 41 Create a data domain for the CATEGORY UDA • 95 Create a data domain for the CATEGORYMGR UDC • 89 Create a user-defined column • 91, 96 Create filters • 92 Create filters for product categories • 98 Create Provisional Order • 50 Create roles and assign filters • 94, 99 Create the Cosmetics filter • 98 Create the ShirtBuyerRead filter • 93 Create the ShirtBuyerWrite filter • 93 Create user-defined data streams • 45 Customize and maintain the database • 40 Customize the Demand DSW • 42 Customize units of measure • 111

D Decision Support Workbench • 42 Define Business Object (BO) metadata for the attributes •

63 Define business-object metadata for the UDA • 91, 96 Define hierarchies • 61, 101, 103, 107 Define location hierarchy • 53 Define price points for Price Optimization • 62 Define product hierarchy • 52 Define the price zones and ad zones used in JDA

Advertising • 76 Delete Order • 51 Delete tablespaces • 41 Delete user-defined data streams • 46 Demand limitations • 118 Demand Worksheet RMI service • 46 Deploy Load Manager Workbench • 49 Details and flow chart • 115



E Edit tables and columns • 41 Edit the DBParam table • 5 Enable user-defined data streams • 45 Enable users to commit scenarios • 111 Encrypt the SCPO schema owner's password • 39 Entity Resources • 34 Example 1

UDC values stored in metadata tables • 89 Example 2

UDC values specified in a reference table • 95

F Feature Resources • 10 Filters • 34 Fulfillment limitations • 120

I Identify the discrepancies which will cause the scenarios to

fail • 7 Implement security • 8

J JDA Advertising

Deploy Image browser • 78 JDA Fulfillment Dynamic Allocation • 52 JDA Fulfillment Dynamic Allocation online services • 54 JDA Fulfillment Replenishment Dashboard Online Services

• 52

L Legal notice • i Limit the number of offers or products displayed • 88 Limitations when using CDS tables • 117

M Maintain existing databases • 41 Manage tables and columns • 40 Manage the number of DFUs retrieved and managed in

each data selection • 45 Memory considerations for Demand DSW • 43 Memory impact of management and display parameters

selected on the Demand DSW page • 45 Migration of Load Manager instances to the Load Manager

Workbench • 49 Modify a resource bundle • 5 Modify RawVariable and market response model tables •

65 Modify server and browser properties • 2

Modify system properties • 2 Monitor limitations • 120

O Offer with a defined search and calendar • 80 Offer with search, but no calendar specified • 80 Offers with details of the DFU level lift • 80 Order Optimization Online Services • 50 Order Optimization purge obsolete orders • 52 Order Optimization User Interface • 50 Overview • 1

P Platform limitations • 118 Provide feedback on this document • i

R Recalculate Order • 50, 51 Reporting limitations • 120 Resources • 8 Roles • 8

S Save cost elements • 75 SCPO security features • 34 Set SRE node configuration properties • 83, 112 Set up calendars • 5 Set up dashboard for Demand Planner • 47 Set up dashboard for Replenishment Planner • 54 Set up data • 61, 101, 103, 107 Set up data for JDA Markdown Optimization and JDA

Promotions Management • 56 Set up hierarchies • 42 Set up hierarchy levels • 62, 102, 104, 108 Set up Import Offer process • 80 Set up offer-level security • 89 Set up Scenarios • 6 Set up the event calendar • 100 Set up the required hierarchy dimensions • 61, 101, 103,

107 Set up the Treatment data domain • 76 Setup information for Dynamic Allocation • 52 Structure of CDS tables • 114 Structure of regular tables • 113 Supported Network Environments for the Demand DSW •

42

T Tune memory consumption settings for Demand DSW • 43



Tune the Java Plug-in maximum memory setting • 43

U Update user-defined data streams • 46 Use pre-configured templates to set up the solution • 2 Use the Demand reports in CDS environment • 47 Use the Security module • 8 Users • 8 Users apply offer-level security to a promotional offer • 94,

100

W What is Compressed Data Storage? • 113


scpo_configuration_guide.pdf

Documents

Transcript of scpo_configuration_guide.pdf