demand_ikb_integration.pdf

Integration Guide JDA

® Demand

JDA® Intactix Knowledge Base

Last updated: 15 February 2013

JDA Software Group, Inc.

Legal notice

Rights to the content of this document

Copyright © 2011-2013 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








http://jda.com/JDAPatents





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. 146038 Taiwan Patent No. 544599 Taiwan Patent No. M377652

Taiwan Patent No. 154327 Taiwan Patent No. 561424 Taiwan Patent No. NI-158220




Taiwan Patent No. 155708 Taiwan Patent No. I221578 Taiwan Patent No. NI-182787

Taiwan Patent No. 157467 Taiwan Patent No. I221978 Taiwan Patent No. NI-182974

Taiwan Patent No. 159609


Table of Contents

Chapter 1. Introduction ................................................................................................... 1

Who should use this guide .......................................................................................... 1 Terminology .............................................................................................................. 1 Integration overview .................................................................................................. 1 Related documents .................................................................................................... 2

Chapter 2. Requirements and conditions ......................................................................... 3

Hardware and software requirements ........................................................................... 3 Category Advisor requirements .................................................................................... 3

Chapter 3. Demand implementation ................................................................................ 4

Overview .................................................................................................................. 4 Database implementation ........................................................................................... 4 Forecast data file preparation ...................................................................................... 5

Chapter 4. IKB implementation ....................................................................................... 6

Configure fact database settings .................................................................................. 6 Import data into a Category Advisor database................................................................ 6 Synchronize lookup data ............................................................................................. 7 Clean up Demand history ............................................................................................ 8

Introduction

JDA Demand - JDA Intactix Knowledge Base Integration Guide 1 © 2011-2013 JDA Software Group, Inc.- Confidential

Chapter 1. Introduction

This guide provides a high-level overview of the integration between JDA Intactix Knowledge Base (IKB) and JDA Demand.

Who should use this guide

This guide is intended for the technical staff responsible for implementing the integration between IKB and Demand. Before using this guide, you should have a functional and technical understanding of IKB and Demand.

Terminology

Category Advisor: An IKB component that allows you to incorporate time-specific retailer data in planograms for in-depth planogram analysis. This component is licensed separately.

Fact database: A secondary Intactix Knowledge Base database that stages profit, unit sales, or

quantity information from an external retailer database. This information can then be summarized and used when analyzing and comparing planograms using Category Advisor.

IKB: Intactix Knowledge Base. This acronym may be used to refer to components of the

application.

Intactix Console: A component of IKB that allows you to configure the Intactix database.

Rollover period: The number of years of data to be stored in the database.

Integration overview

The integration between Demand and IKB allows you to leverage a synchronized forecast coming from Demand to help make intelligent space planning decisions. You can focus on past metrics (for example, dollar per linear foot) or review a future time-phased forecast to enhance your space planning

decisions. You can use forecast data instead of historical performance data so you can consider future events and trends.

The basic Demand – IKB integration process is:

1. Demand sends Forecast values to the DFUTOITXFCST table. The data in this table is then exported to a flat file.

Introduction


2. IKB imports the Demand Forecast values from the flat file into a CategoryAnalysis fact database so the data can be used in analysis.

Related documents

Intactix Knowledge Base Installation Guide

Intactix Knowledge Base Administrator Guide

Intactix Knowledge Base Release Notes

Platform Release Notes

Requirements and conditions


Chapter 2. Requirements and conditions

Hardware and software requirements

Demand and IKB must be installed and properly configured to transfer data between the systems.

Refer to the JDA Platform Release Notes for the hardware and software requirements for Demand.

Refer to the JDA Intactix Knowledge Base Installation Guide for the hardware and software requirements for IKB.

Category Advisor requirements

To import Demand data for analysis in IKB, you must activate and configure Category Advisor and

create a separate fact database to store the forecast analysis data.

Two levels of Category Advisor activation are available:

Level 1 activation provides access to the JDA Demand integration. If you use Level 1 activation,

you can import data into only one field (Value11).

Level 5 activation provides full Category Advisor functionality, including JDA Demand integration. If you use Level 5 activation, you can import data into all available fields.

See "Activate Category Advisor", "Configure Category Advisor calendar settings" and "Create a fact database" in the Intactix Knowledge Base OnLine Expert for more information.

Demand implementation


Chapter 3. Demand implementation

Overview

The Transfer Forecast process is used by Demand to implement the Demand – IKB integration. The process page search for this integration should be Item, Loc, or SKU based. The Space Management

option should be selected to populate the forecast data available in the FCST table to the DFUTOITXFCST table.

You should populate the DFUTOSKU table to define the mapping used to map data from DFUs to SKUs. A unique DFU can be mapped to a unique SKU, a unique DFU can be mapped to many SKUs, or many

DFUs can be mapped to the single SKU. This table is used by the Transfer Forecast process to map forecast from DFUs to SKUs.

The allocation factor defined in the DFUTOSKU table determines the portion of the DFU's quantity that

should be allocated to the SKU.

This process maps forecast records whose Start Date is equal to or greater than the process Start Date and that fall within the duration specified. It then transfers the data based on the selected calendar in

the process page. The DFUTOSKUFCST table acts as an intermediate staging table. The sum of the quantities for forecast types, selected in the DFUTOSKU table, is populated in the DFUTOITXFCST:Qty column from the DFUTOSKUFCST table.

If you do not want to define a mapping in the DFUTOSKU table, then you can use

DBParam:DefaultDFUMapSw to perform automatic mapping between SKUs and Summary DFUs. If this switch is On, the system automatically maps the total forecast and overrides for a Summary DFU to its associated SKU where:

DFU:DmdUnit matches SKU:Item

DFU:Loc matches SKU:Loc

DFU:DmdGroup matches DBParam:SummaryDmdGroup

DFU:Model matches DBParam:SummaryModel

Automatic mapping eliminates the need for setting up and maintaining rows in the DFUTOSKU table. If DefaultDFUMapSw is On, then the SummaryDmdGroup and SummaryModel must exist in the DMDGROUP and MODEL tables.

Using reference FiscYrStart, defined in the Webworks system properties, the respective Fiscal year and Fiscal period are calculated for each row of the DFUTOITXFCST table.

Database implementation

Demand uses the DFUTOITXFCST table to provide forecast values to IKB.

Field Type Description

FISCALYEAR INTEGER Fiscal Year: The fiscal year of the record.

FISCALPERIOD INTEGER Fiscal Period: The fiscal period of the record.

LOC VARCHAR2(50) (PK) Location: The location associated with the DFU from which forecast demand data is mapped.

ITEM VARCHAR2(50) (PK) Item: The item associated with the SKU to which forecast demand data is mapped.

STARTDATE DATE (PK) Start Date: The start date from which the forecast demand data is mapped. In cases where the record is a

weekly record, this is the first date of the week to which the value applies.

Demand implementation


Field Type Description

DUR INTEGER Duration: The amount of time the record covers, in minutes. Typically, the values are 1440 for a day or 10080

for a week.

QTY FLOAT Quantity: The Demand forecast value of the record.

Forecast data file preparation

Intactix Knowledge Base expects to import Forecast data from a flat file. Therefore, you must export the data from the DFUTOITXFCST to the appropriate file.

1. After the transfer forecast is run, navigate to the DFUTOITXFCST table.

2. Perform a search to retrieve the appropriate forecast data.

3. Click Actions, then select Export. The file is saved with the .csv file extension.

IKB implementation


Chapter 4. IKB implementation

Configure fact database settings

You specify fact database information to identify the fact database used for all fact (POS, Demand, and space) data import processes.

Note: To modify Category Advisor settings, you must be the database owner (SQL) or dba (Oracle) or have the Administrator role.

Path: Intactix Console > Tools > CA Settings > Fact Database (tab)

Window: Settings for Category Advisor

1. Select a Location option to specify whether the Category Advisor fact data resides within the

Intactix database schema or in an external database.

Notes:

If the Intactix database is also an internal fact database, the Location field contains only Not configured and Internal options.

Before you define a Fact database as Internal, make sure that the Intactix database that you are logged into contains both IKB and Fact schemas.

Before you define a Fact database as External, make sure that the Intactix and fact databases

consist of only Intactix Knowledge Base schema.

2. If the Category Advisor fact data exists in an external database, specify information to connect to the database, including the database server name, fact database name, Windows domain user

name (SQL Server and NT Authentication only), user name, and password.

Notes:

When specifying the server name, you must specify the actual machine name. You can specify "localhost", but you cannot specify "(local)".

You can click Test Connection to verify the connection to the external fact database.

When configuring to an external database, a database link is created. For this reason, you must have the privilege to create database links.

If the database server name for the external fact database changes, the system writes an entry into the event log that contains the From and To database information.

3. Click Apply.

Import data into a Category Advisor database

To incorporate Demand data in your planogram analysis, you must import the data from an external data source into the Category Advisor database. The data must be exported from the Demand database as a text file that is either stored with a .txt file extension or zipped with a .zip file extension.

The data is matched against a format or control file that maps the external data to fields in the Category Advisor database tables.

1. Configure fact database settings.

2. Select Tools > Fact Data.

3. Click Manage Demand Data. One of three pages is displayed:

If connecting to an external Oracle fact database, the SQL Loader Login page is displayed.

If account support is enabled in the database, the Account Selection page is displayed.

If the previous options are not applicable, the Process Options page is displayed.

IKB implementation


4. If connecting to an external Oracle fact database, specify the Login Name and Password to connect to SQL Loader, then click Next.

5. If account support is enabled in the database, select the account to associate with the imported

data, then click Next. The Process Options page is displayed.

6. Select Load ETL file, then click Next. The Process Parameters page is displayed.

7. Enter the location where the external Demand data is stored in the Location field. You can click the ellipsis button to select a location. On SQL Server, the location must be specified as a UNC

path, and should be a mapped drive on the external server. The format for a UNC path is \\server\volume\directory\file, and is not case-sensitive; for example,

\\Shared1_svr\Shared1\WGroups\Network\Orders.xls.)

8. Select a File Type option to specify whether to process the compressed (.zip), text (.txt, for SQL

Server), or data (.dat, for Oracle) files in the Location folder.

9. Specify the name of the format (SQL Server) or control (Oracle) file to use when matching fields in the external data to fields in the fact database in the Format file or Control file field. You can click the ellipsis button to select the file. The default format file is stored in the folder in which

Intactix Knowledge Base is installed.

10. If you are importing into an Oracle Category Advisor database, specify the name of the log file that will be generated after the import process is complete. The log file stores detailed information

about the import, such as the number of records loaded. You can click the ellipsis button to select the file.

Note: If multiple data files are selected for import into the database, a separate log file is

generated for each data file. A number is appended to the log file name to make each file name unique.

11. Enter the location where the external Demand files should be moved after the import in the Archive Folder field. You can click the ellipsis button to select a location. This location should be a

mapped drive on the external server.

12. Click Next. The Select Files to Process page is displayed.

13. Select the files to import, or select Select All to import all listed files. If you are processing

compressed (.zip) files, the first zip file in the Location folder is extracted and its text files are listed for import. If you are processing text files, all text files in the Location folder are listed for import.

14. Click Finish. Fact data is imported to the database. If you processed compressed (.zip) files, only the zip file is archived. If you processed text files, only the selected text files are archived.

Synchronize lookup data

If you are using object versioning for products and stores in your database, when object versions are

cycled, it is possible for a Historic product or store version to be associated with fact data in the Category Advisor database. You can synchronize lookup data to ensure that the fact data is associated with the current Live version.

Note: This process also may create products or stores, if fact data exists for products or stores that do not exist in the Intactix database.



3. Click Manage Demand Data. The Account Selection page is displayed if account support is enabled in the database. Otherwise, the Process Options page is displayed.

4. If account support is enabled in the database, select the account to associate with any created

stores, then click Next. The Process Options page is displayed.

IKB implementation


5. Select Synchronize lookup data, then click Finish. The fact data is associated with the current Live versions of products and stores.

Clean up Demand history

When new data is appended to the Category Advisor database, it is possible that the history data will exceed the number of years specified by the Rollover Period for the database. You can clean up the fact database by removing all data for years that precede the specified rollover period.



3. Click Manage POS Data or Manage Demand Data. The Process Options page is displayed.

4. Select Cleanup Demand history, then click Finish. Historical data that precedes the specified

rollover period is removed from the database.

demand_ikb_integration.pdf

Documents

Transcript of demand_ikb_integration.pdf