reference manual - umsl

man

ugis

tics

Reference Manual

NetWORKS Strategy

6.2version

Manugistics is a registered trademark and the phrase “Leveraged Intelligence,” the Manugistics logo, NetWORKS, NetWORKS Strategy, WebConnect, VIEWpoint, and ONEview are trademarks of Manugistics, Inc.

THIS DOCUMENT WAS PREPARED TO HELP USERS OF SOFTWARE OF MANUGISTICS, INC. THE CONTENTS OF THIS DOCUMENT SHALL NOT BE USED FOR ANY OTHER PURPOSE WITHOUT THE EXPRESS WRITTEN PERMISSION OF MANUGISTICS, INC. MANUGISTICS, INC. SUPPLIES THE MATERIAL IN THIS DOCUMENT AS IS, WITHOUT REPRESENTATION OR WARRANTY, EXPRESSED OR IMPLIED, OF ANY KIND. SPECIFICALLY, MANUGISTICS, INC. DISCLAIMS AND EXCLUDES ANY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY AND DISCLAIMS AND EXCLUDES ANY WARRANTY, INCLUDING ANY IMPLIED WARRANTY, OF FITNESS. THERE ARE NO WARRANTIES WHICH EXTEND BEYOND THE DESCRIPTION ON THE FACE HEREOF.

Copyright © 1997-2001 Manugistics, Inc.

Printed in the United States of America

All rights reserved. Reproduction of this document or any portion of it, in any form, without the express written consent of Manugistics, Inc. is prohibited.

ORACLE is a trademark of Oracle Corporation. Intel is a trademark of Intel Corporation. Windows 95 and Windows NT are registered trademarks of Microsoft Corporation. Internet Information Server, SQL Server, and ODBC are copyright of Microsoft Corporation. ObjectStore is a trademark of Object Design Inc. Orbix and Orbix Web are registered trademarks of IONA Technologies Ltd. Java Developer Kit is a registered trademark of SUN Microsystems. CORBA is a trademark of the Object Management Group, Inc. CPLEX is a trademark of ILOG. Crystal Reports and Crystal Reports for Windows are trademarks of Crystal Computer Services, Inc., a Seagate Software Co. Adobe Acrobat is a registered trademark and Reader is a trademark of Adobe Systems Inc. Cold Fusion is a trademark of Allaire. MapInfo MapX™ (OR MapMarker® OCX, as appropriate) is a proprietary trademark of MapInfo Corporation, Troy, NY, and is licensed to Manugistics by MapInfo. RoboHelp is a copyright of eHelp Corporation. dBASE is a copyright of Borland International.

Throughout this document, certain designations may be used that are trademarks that identify the goods of third parties. Although this document attempts to identify the particular trademark owner of each mark used, the absence of a trademark symbol or other notations should not be taken as an indication that any such mark is not registered or proprietary to a third party. Use of such third-party trademarks is solely for the purpose of accurately identifying the goods of such third party.

Contents

Part 1: General Information

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Conventions used in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Specifying user input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Specifying optional values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Specifying variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Specifying repeating values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Using the NetWORKS documentation set . . . . . . . . . . . . . . . . . . . . . . . . . 5

Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Basics and Beyond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Readme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Getting additional help from Manugistics . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2: Importing, exporting, and deleting data . . . . . . . . . . . . . . . 9

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Creating an input file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Specifying multiple objects (using wildcards) . . . . . . . . . . . . . . . . . . 12

Specifying dates and numbers in different locales . . . . . . . . . . . . . . 13

Importing and exporting complex objects . . . . . . . . . . . . . . . . . . . . . . . . 14

Special formatting for complex objects . . . . . . . . . . . . . . . . . . . . . . . 14

Importing and exporting complex attributes . . . . . . . . . . . . . . . . . . . 15

Importing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Creating versus updating objects using Data Import . . . . . . . . . . . . . 21

Using wildcards to update multiple objects . . . . . . . . . . . . . . . . . . . . 23

Using data selections to update objects . . . . . . . . . . . . . . . . . . . . . . 23

iv NetWORKS Strategy Reference Manual

Using attributes other than name to update objects . . . . . . . . . . . . . 24

Running the Data Import process . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Deleting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Using wildcards to delete multiple objects . . . . . . . . . . . . . . . . . . . . 29

Using data selections to delete objects . . . . . . . . . . . . . . . . . . . . . . 29

Using attributes other than name to delete objects . . . . . . . . . . . . . 30

Running the Delete Data process . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Exporting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Exporting selected attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Exporting all attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Using wildcards to export objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Using data selections to export data . . . . . . . . . . . . . . . . . . . . . . . . . 35

Using attributes other than name to export objects . . . . . . . . . . . . . 35

Running the Data Export process . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Tips on creating input files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Using SQL to export data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Importing a file into a spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Adding attributes and values in a spreadsheet . . . . . . . . . . . . . . . . . 40

Chapter 3: Using the Data Loader to import data . . . . . . . . . . . . . . . 43

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Sample Data Loader files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

MakeProcess template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Generic templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Rate templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Customizing data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Header rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Contents v

Data Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Reserved keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Customizing keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Label keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Mapping user-defined keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Running the Data Loader tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Syntax of the command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 4: Importing carrier cost data from NetWORKS Transport . 59

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Exporting transportation resources from Strategy . . . . . . . . . . . . . . . . . . 59

Generating cost data from Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter 5: Maintaining calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Overview of the calendar utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Filtering attributes with the -f parameter . . . . . . . . . . . . . . . . . . . . . . . . . 64

Purging intervals with the P operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Copying intervals with the CI operation . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Trimming intervals with the TR operation . . . . . . . . . . . . . . . . . . . . . . . . . 66

Compressing intervals with the CO operation . . . . . . . . . . . . . . . . . . . . . 67

Rolling interval dates with the R operation . . . . . . . . . . . . . . . . . . . . . . . . 68

Rolling interval dates and values with the RV operation . . . . . . . . . . . . . . 69

Normal-slotted calendar example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Level-slotted calendar example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Setting the transaction size with the -b parameter . . . . . . . . . . . . . . . . . . 74

Part 2: Strategy database objects

Chapter 6: Overview of NetWORKS Strategy objects . . . . . . . . . . . . 77

vi NetWORKS Strategy Reference Manual

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Using objects and attributes to import and export data . . . . . . . . . . 78

Item (spItem) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Item (spItem) attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Import/export notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Lane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Lane attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85


Location (spLocation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Location attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93


MakeProcess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

MakeProcess attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Import/export notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

MoveProcess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

MoveProcess attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . 102


NamedCalendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Understanding Named Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106


PlanMetrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

PlanMetricsDetails attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . 108


PurchaseProcess (Buy or Sell) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

PurchaseProcess attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . 111


ResourceRequirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Contents vii

ResourceRequirement attribute descriptions . . . . . . . . . . . . . . . . . . . . . 117


ReusableResource (spReusableResource) . . . . . . . . . . . . . . . . . . . . . 120

ReusableResource attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . 122


Service Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Service Level attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Service Level Set attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 132


Importing Service Level objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Exporting Service Level objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

SKU (spSKU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

SKU attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143


SKURequirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

SKURequirement attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 158

Import/export notes: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

SourcingGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Sourcing Group (SourcingGroup) attribute descriptions . . . . . . . . . . . . . 162

Tiered Cost/Price . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Tiered Cost/Price attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 165

Tiered Price Pair attribute descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 168


Importing Tiered Cost/Price objects . . . . . . . . . . . . . . . . . . . . . . . . . 168

Exporting Tiered Cost/Price objects . . . . . . . . . . . . . . . . . . . . . . . . . 169

Part 3: Appendices

Appendix A: Data types for database attributes . . . . . . . . . . . . . . . . 173

viii NetWORKS Strategy Reference Manual

Notes on data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Separator character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Quotes in your data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Specifying time intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Specifying and customizing units of measure . . . . . . . . . . . . . . . . . 177

Updating lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Appendix B: Changes to NetWORKS Strategy objects since 6.1 . . 179

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

New Strategy objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Changes to Strategy objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Tables

1: Strategy object types ........................................................................ 12

2: Required keywords in the MakeProcess template ........................... 44

3: Keywords in the Lane template ........................................................ 46

4: Keywords in the Move and PurchaseProcess templates.................. 47

5: Keywords in the Inventory SKURequirement template .................... 48

6: Keywords in the SKU Independent Demand template ..................... 49

7: Keywords in the On Hand template.................................................. 50

8: Keywords in the Safety Stock template............................................ 51

9: Keywords in the Resource Maximum Capacity template ................. 51

10: Keywords in the Resource Cost template ........................................ 52

11: Keywords in the SKU Rate template................................................. 52

12: spDataLoader command syntax........................................................ 57

13: Parameters for manucalendarutils .................................................... 63

14: Item (spItem) attributes .................................................................... 81

15: Lane attributes .................................................................................. 84

16: Location (spLocation) attributes ........................................................ 92

17: MakeProcess attributes .................................................................... 97

18: MoveProcess attributes .................................................................. 101

19: PlanMetrics attributes ..................................................................... 108

20: PurchaseProcess attributes ............................................................ 110

21: ResourceRequirement attributes .................................................... 117

22: ReusableResource (spReusableResource) attributes ..................... 120

23: Service Levels attributes................................................................. 131

24: SKU (spSKU) attributes ................................................................... 138

25: SKURequirement attributes ............................................................ 158

26: Sourcing Group (SourcingGroup) attributes .................................... 162

27: Tiered Cost/Price attributes............................................................. 164

x NetWORKS Strategy Reference Manual

28: Data types for database attributes.................................................. 173

29: New Strategy objects in version 6.2 ............................................... 179

30: Changes to Strategy objects in version 6.2 .................................... 179

Part 1

Part OneGeneral Information

2 NetWORKS Strategy Reference Manual

Chapter 1

Introduction

This chapter contains an overview of the information contained in this manual and how it is organized. It also introduces you to the type of information available for NetWORKS and the document conventions used to present this information.

Overview

NetWORKS is supply chain management software that facilitates supply and demand planning, manufacturing scheduling, and strategic and tactical planning across the supply chain. This manual provides reference information for NetWORKS Strategy.

This manual is organized as follows:

• Part One: General Information

> The introduction (this chapter) describes the contents of and conventions used in this book.

> The chapter “Importing, exporting, and deleting data” on page 9 explains the basics of setting up an input file and running the Data Import, Data Export, and Delete Data processes.

> The chapter “Maintaining calendars” on page 63 provides information on managing calendar attributes in Strategy.

> The chapter “Using the Data Loader to import data” on page 43 provides information on using the Data Loader tool to create input files for Data Import in Strategy.

> The chapter “Importing carrier cost data from NetWORKS Transport” on page 59 provides information on using the Data Import and Data Export processes to import carrier cost rates from NetWORKS Transport.

> The chapter “Maintaining calendars” on page 63 provides information about managing and administering calendar attributes.

• Part Two: Strategy database objects

The chapter “Overview of NetWORKS Strategy objects” on page 77 provides detailed information on the objects and attributes in Strategy. This information


helps you understand how attributes affect your supply chain model and how to set up input files for the Data Import, Data Export, or Delete Data processes.

• Part Three: Appendices

This manual contains the following appendices:

“Data types for database attributes” on page 173

“Changes to NetWORKS Strategy objects since 6.1” on page 179

Conventions used in this manual

This section describes the typographic conventions used.

Specifying user input

When showing commands that a user should type as input or examples of user input, this manual shows the commands in a monospaced font that looks like a typewriter font. An example of the content of an input file for Data Import would be given as:

(NamedCalendar),descriptionMfg1,sample ManufacturingAvailability Calendar

In this example, you are shown the exact (literal) information that should make up your input file. See the following sections for information on specifying variables and optional values.

Specifying optional values

When showing the syntax and format for entering commands at the command prompt or in input files, this manual shows optional values enclosed in [brackets]. For example, the following is the syntax for an input file:

(spSKU)[,<attribute>, <attribute>]<name>,<attribute_name>, <numeratorUOM>, <denominatorUOM>[,,<interval_start_date>, <interval_end_date>,<rate>][,,<interval_start_date>, <interval_end_date>,<rate>]

In this example, the (spSKU), <name>, and <attribute_name> parameters are required, but the intervals (interval_start_date, interval_end_date, and rate) are not required. You would not type the brackets around the options.

Introduction 5

Specifying variables

When specifying a variable that the user would enter, this manual shows the variable in bracketed <italic>. For example, the following syntax is given for an input file:

(spSKU)<name>

In this example, you would type (spSKU) as shown, but substitute the name of the SKU for <name>. You would not type the brackets (<>) around the name.

Specifying repeating values

In many instances, you can repeat values multiple times within the same command. This manual shows such values followed by a … to denote that a value may be repeated. For example, the following is a sample entry in an input file for Data Import:

(purchaseprocess),<attribute-name>,…<process-name>, <attribute-value>,…

In this example, you can repeat the <attribute-name> and <attribute-value> variables multiple times.

Using the NetWORKS documentation set

Included with NetWORKS are four different types of documentation to help you learn how to use this sophisticated software—manuals, online help, online articles called Basics and Beyond, and a Readme file.

Manuals

Each of the following manuals is available as a traditional printed book or as an Adobe Acrobat PDF (Portable Document Format) file. When you install any of the Manugistics products, you can choose to install any or all of the manuals appropriate for that product. Then at any time, you can review these manuals online or print copies of them. To open the PDF manuals, on the Help menu, select the name of the book. The books can also be accessed from the NetWORKS 6.2 program group on your Start menu. The following manuals are available:

• NetWORKS Strategy Reference Manual (this manual)


• NetWORKS Scheduling and Strategy Installation/Administration Manual

Online help

NetWORKS components contain a context-sensitive online help system that guides you through the user interface. Each menu command and window has its own help topic that describes the purpose of each command and window, explains how to use the options on each window, and offers guidance and tips about the program functions. You can access online help in the following ways:

• On the Help menu, click Online Help. In the dialog box that appears, select the Contents tab for a table of contents to the online help information. Select the Index tab if you prefer to find information using an alphabetical index of the help topics. Select the Find tab if you want to search the help system using one or more key words.

• For help about a command choice on a menu, highlight the command and press F1.

• For help information about the window currently displayed, click Help or press

F1.

The help system also contains additional information that you can access through hypertext links in the help text. By default these links are displayed as highlighted text. To “jump” to related help information, click a link or press Tab to move to the link and then press Enter.

Searching for help

To find help information about a specific topic or window, on the Help menu, click Online Help and then select the Find tab. Follow the directions in this dialog box for narrowing your search by using key words.

Using the online glossary

The Manugistics6 applications and help systems use many terms that might be unfamiliar to you. The help system includes an online glossary that defines these terms. To open the glossary for your application, on the Help menu, click Online Help

Note: You need Adobe Acrobat Reader (version 3.01 or higher) to view these electronic manuals. If you do not already have Acrobat Reader installed, you can find an installation copy in the windows\acrobat directory on the Manugistics CD.

Introduction 7

and select the Contents tab. Then double-click the Glossary “book” in the table of contents.

Basics and Beyond

Basics and Beyond is an evolving online publication, which contains a set of articles that expands with each new release. These articles provide targeted information, designed to help you use the different parts of NetWORKS to solve specific business problems.

In the Basics and Beyond, you will find an introductory article for your NetWORKS component. Additional articles cover the best way to use NetWORKS for completing specific business tasks.

Readme

The Readme file contains sections with the following information:

• Hardware and software requirements: the required operating system and third-party software components necessary to install Strategy. Minimum hardware requirements are also listed.

• Installation information: An overview of installing the product.

• Enhancement summary: a list of changes made to Strategy since the last major release.

• Known Issues: known issues in the software and, if necessary, ways to work around them.

The Readme is provided in HTML format (readme.html), which requires an HTML browser such as Netscape Navigator or Internet Explorer, or in text format (readme.txt). The Readme is installed by the setup program and available from the Windows Start menu, in the NetWORKS 6.2 program group, under the Strategy application group. You can also access the Readme from the installation CD.

Documentation Feedback

Manugistics welcomes your comments on our documentation. To give feedback, please do one of the following:

• E-mail [email protected] with your comments

• Fill out our online survey at http://www.manugistics.com/docsurvey

• Click Documentation Feedback from the NetWORKS Help menu

http://www.manugistics.com/docsurvey


Getting additional help from Manugistics

If you have questions or problems with your Manugistics application, you can obtain help in one of the following ways:

• Manugistics Global Client Support provides support for all Manugistics applications. While you are under contract for Solution Support, you can contact Global Client Support with questions and issues about the Manugistics products. Global Client Support can be reached via the following methods:

> phone: 301-984-5160

> fax: 301-984-5290

> e-mail: [email protected]

• NetLINK, a web-based Manugistics support site where you can obtain information about the newest releases, access a Solution Bank of useful tips and techniques, report issues, request product enhancements, and order software upgrades. To access NetLINK, point your browser to:

http://www.manugistics.com/netlink

You will be prompted for a username and password. If you do not have a username and password, contact Global Client Support about receiving one.

http://www.manugistics.com/netlink

Chapter 2

Importing, exporting, and deleting data

This section describes how to use the Data Import, Data Export, and Delete Data processes with NetWORKS Strategy.

Overview

This chapter gives information on setting up input files for and using the Data Import, Data Export, and Delete Data processes.

• The Data Import process allows you to import data for new or existing objects in NetWORKS Strategy.

• The Data Export process can export all or selected data from Strategy.

• You can use the Delete Data process to easily delete data from Strategy.

Whether you are importing, exporting, or deleting data, you need to specify your data in an input file. You can use a text editor or spreadsheet to create your input file, or you can generate the file automatically from another database or computer system. After you have created your input file, use the appropriate process to read the file and perform the requested action.

See the following sections for information on how to:

• Create an input file (page 9)

• Import or update data (page 20)

• Delete data (page 28)

• Export data (page 32)

Creating an input file

The first step in using the Data Import, Data Export, or Delete Data processes is to create a plain text file that defines the objects, attributes, and values you want to work with. This plain text file will serve as the input file for the process. For more specific information about setting up input files for importing, exporting, and deleting, refer to the sections that follow concerning import, export, or deletion. For


information on the actual objects and their attributes, see the chapter “Overview of NetWORKS Strategy objects” on page 77.

An input file consists of one or more rows of text. You can have three types of rows in your input file:

• comment rows: Any line that starts with a # and at least one space (#) is considered a comment and will be ignored when the file is imported.

• header rows: A header row defines the object, such as spitem or amsitem, followed by the attributes that will be created, updated, or deleted when the file is read by the process. The object-type name must be surrounded by parentheses, for example (spitem). Both the object-type name and attribute names are case insensitive.

See Table 1 on page 12 for a list of Strategy objects.

To determine the appropriate attributes for a particular object, see the section of this manual that describes that object. Each section contains a table that lists the import/export names for each object and attribute.

• data rows: A data row contains the actual data you will import. Each value in a data row must correspond to the object-type or attribute in the header row that precedes it.

In your header rows and data rows, each item must be separated with a unique separator character (for example: , ‘ ! “ # % & ; ^). This character must not be found in your data. For example, if you use a comma as the separator character, you cannot have commas in your data. You can have no spaces before or after your separator character, or you can leave spaces between the separator character and your data—it does not make any difference.

Note: When specifying the object in your input file, do not put any spaces or characters within the parentheses other than the object-type name. In addition, do not use double quotes as part of an object name (for example, 3/4” threads). Doing so can cause problems in many areas of the product.

Note: For the examples in this manual and the sample input files shipped with Strategy, a comma (,) is shown as the separator character. You can not use the following characters as separator characters: @ / : . and *.

Importing, exporting, and deleting data 11

A simple example of an input file for Data Import is:

All attributes have a data type, which determines how your values should be formatted in the input file. For example, a data type may require a number, a date, or a specific value from a list of values. To determine the appropriate format for an attribute, see the section of this manual that describes that object. Each section contains a table that lists the data type for each attribute. For information on what the data type designations mean, see the section “Data types for database attributes” on page 173.

Guidelines for input files:

• Each line of data must be followed by a carriage return. You cannot have two contiguous header rows, or the process will generate an error. If you want to place a header row in your input file as a placeholder, but have no data after it, put a comment line (#) between your header rows.

• Many objects depend on other objects. For example, a SKU consists of an item at a location. To delete an item, no SKUs can reference the item. To create a SKU, the item referenced in the SKU must already exist. Each object described in this manual contains information on dependencies between objects.

• If you use file transfer protocol (FTP) to transfer input files from one computer to another (for example, from a Windows computer to a UNIX server), be sure to transfer the files in ASCII mode. Otherwise, control characters will be introduced during the FTP process and Data Import/Export will fail to read the file correctly. Alternatively, you can remove the control characters on the UNIX server using vi or another text editing tool.

• You can use double quotes around any of your data values as long as the entire value string has both a “beginning and ending quote.” Quotes will not appear in

# create items(spitem), defaultuofm10100, case10200, case# create locations(splocation),description, isdcFLA, Florida, trueDET, Detroit, true

header row

data rows

Comment row

separator character


Strategy after the data has been imported, even if there are multiple sets of quotes.

Specifying multiple objects (using wildcards)

You can use a wildcard character (*) to specify the names of multiple objects. For example, you could use:

• 10* to specify the name of all objects that begin with 10

• *transportation* to specify the name of all objects that contain the word ‘transportation’

Note: Do not use double quotes as part of an object name (for example, 3/4” threads). Doing so can cause problems in many areas of the product.

Table 1: Strategy object types

Object type

Item (spItem)

Lane

Location (spLocation)

MakeProcess

MoveProcess

NamedCalendar (also used by Scheduling)

PlanMetrics (export only)

PurchaseProcess (Buy or Sell)

ResourceRequirement

ReusableResource (spReusableResource)

Service Level Sets

SKU (spSKU)

SKURequirement

SourcingGroup

TieredCost/Price

Tip: Importing many objects and attributes can be simplified using the Data Loader. See the chapter “Using the Data Loader to import data” on page 43 for more information.


• *dent to specify the name of all objects that end in “dent”

• * to specify all objects of a certain type in the database

An example of an input file that uses wildcards to specify multiple objects for updating via Data Import is:

Specifying dates and numbers in different locales

When you specify dates and numbers in your input file, use the date and number format that is configured on the computer that runs the Strategy server application. Even if your Windows client computer is configured with different date and number formats, your input file must match the date and number formats recognized by the Strategy server.

For example, if you set your server locale to the Korean locale, your date format might look like:

2000-01-01 0:00:00

as opposed to a U.S. format of:

1/1/2000 0:00:00

In an input file configured for the Korean locale, importing a NamedCalendar might look like:

(NamedCalendar),descriptionquarterly,quarterly Display Calendar,cal,reporting,,2000-01-01,2000-04-01,,2000-04-01,2000-07-01,,2000-07-01,2000-10-01,,2000-10-01,2001-01-01

Note: You can only use wildcards to designate the names of multiple objects, not to designate multiple names for attributes.

# update items(spitem), defaultuofm10*, case# update SKUs(spSKU), costpricetype*, local

specifies all SKUs in the database

specifies all items beginning with 10


In addition, if your number formatting includes commas in place of decimals, you must adjust the separator character in your input file so that it uses a character not found in your data. For example, in many European number formats, a comma is used instead of a period in decimal numbers. In this instance, you could use a semicolon to separate your data in your input file, as the following example demonstrates:

(spSKU)00101;price;Gallon;Kilogram;;2000-01-01 0:00:00;2000-04-01 0:00:00;0,580000;;2000-04-01 0:00:00;2000-07-01 0:00:00;0,590000;;2000-07-01 0:00:00;2000-10-01 0:00:00;0,580000;;2000-10-01 0:00:00;2001-01-01 0:00:00;0,600000

When you export data, dates and numbers will appear in your output file in the format that is configured on the Strategy server when the Data Export process was run.

The valid date range for all Manugistics products is January 1, 1970 to January 18, 2038. Use of any dates outside this range will result in inconsistent results. When specifying a starting interval or ending interval to span this entire time range, use min_time and max_time. See the section “Using min_time and max_time” on page 176 for more information.

Importing and exporting complex objects

Special formatting for complex objects

Selected objects are complex and require special formatting in your input file if you wish to import or export them. These objects include:

• NamedCalendar. See the section “NamedCalendar” on page 106 for information on formatting this object.

• PlanMetrics. See the section “PlanMetrics” on page 108 for information on formatting this object.

Note: In the remainder of this manual, all date and number examples are shown in U.S. format with a comma as a separator character. If you are creating input files, you must configure your input files according to the date locale on your server system.

If you change locale, make sure that the iTLZero setting is still set to your preferred setting. The iTLZero setting is controlled by the time setting in Regional Settings, and determines whether there is a leading 0 in time settings.


• Service Levels. See the section “Service Levels” on page 131 for more information on formatting this object.

• TieredCostPrice. See the section “Tiered Cost/Price” on page 164 for information on formatting this object.

See the sections that follow for information specific to importing, exporting, or deleting data.

Importing and exporting complex attributes

Many attributes contain more than one value and are thus more complex than those shown in the previous examples. Examples of these type of attributes are:

• Double Calendars (DblCalendar): See the section “Working with DblCalendar attributes” on page 15.

• Quantity Calendars (QtyCalendar): See the section “Working with QtyCalendar attributes” on page 16.

• Rate Calendars (RateCalendar): See the section “Working with RateCalendar attributes” on page 17.

Working with DblCalendar attributes

Double calendars are time-phased attributes that specify a value for one or more intervals. A double calendar specifies one or more intervals, each of which specifies:

• start date

• end date

• value during the interval

When importing attributes with a data type of DblCalendar, you must use the following format in your input file:

(<object>)<name>,<attribute_name>,, <interval_start_date>, <interval_end_date>,<decimal>[,,<interval_start_date>, <interval_end_date>, <decimal>]

If you have more than one interval, the <interval_start_date> in the second and subsequent intervals must be the same as the <interval_end_date> of the previous interval. If you do not specify a time, the system will set the time to 0:00:00.


For example, the % Constraint attribute in Strategy is a double calendar. To specify this attribute in a file for Data Import, enter:

(SKURequirement)flour@CHI->Make--Bread@CHI,percentageconstraint,,1/1/2000,4/1/2000,.30,,4/1/2000, 7/1/2000,.10

To define one value for all time intervals (time independent values), use min_time and max_time in place of the <interval_start_date> and <interval_end_date>. For example, to define a time independent supply percentage constraint, you would enter:

(SKURequirement)flour@CHI->Make--Bread@CHI,percentageconstraint,,min_time,max_time,.10

Working with QtyCalendar attributes

Quantity calendars are time-phased attributes that specify a quantity for zero or more intervals. A quantity calendar specifies each of the following:

• default unit of measure

• zero or more intervals, each of which specifies:

> start date

> end date

> quantity during the interval

When importing attributes with a data type of QtyCalendar, you must use the following format in your input file:

(<object>)<name>,<attribute_name>, <default-UOM>,

Note: Only some attributes with a Data Type of DblCalendar support time independent values. If the size of the interval has no effect on the value, then time independence is supported; otherwise, it is not.

You can also use the Strategy Calendar utility to manage many of your calendar values. See the section “Maintaining calendars” on page 63 for more information.


[,,<interval_start_date>, <interval_end_date>, <qty>][,,<interval_start_date>, <interval_end_date>, <qty>]


For example, the SKU attribute for safety stock quantity is a quantity calendar. To specify this attribute in a file for Data Import, enter:

(spSKU)flour@CHI,safetystock,pound,,1/1/2000,4/1/2000,100,,4/1/2000,7/1/2000,150

To define one minimum inflow amount for all time intervals (time independent values), use min_time and max_time in place of the <interval_start_date> and <interval_end_date>. For example, to define a time independent minimum inflow amount, you would enter:

(spSKU)flour@CHI,mininflow,pound,,min_time,max_time,150

When QtyCalendar attributes are exported, they also follow the preceding format.

Working with RateCalendar attributes

Rate calendars are time-phased attributes that specify a rate for zero or more intervals. A rate calendar specifies each of the following:

• numerator unit of measure

Note: Only some attributes with a Data Type of QtyCalendar support time independent values. If the size of the interval has no effect on the value, then time independence is supported; otherwise, it is not. For example, SafetyStock supports time independence, but MinInflow does not.

Tip: Importing many QtyCalendar attributes can be simplified using the Strategy Data Loader. See the section “Using the Data Loader to import data” on page 43 for more information. You can also use the Strategy Calendar utility to manage many of your calendar values. See the section “Maintaining calendars” on page 63 for more information.


• denominator unit of measure

• zero or more intervals, each of which specifies:

> start date

> end date

> rate during the interval

When importing attributes with a data type of RateCalendar, you must use the following format in your input file:

(<object>)<name>,<attribute_name>, <numeratorUOM>, <denominatorUOM>[,,<interval_start_date>, <interval_end_date>,<rate>][,,<interval_start_date>, <interval_end_date>,<rate>]


For example, the spSKU attributes for price and maximum onhand penalty are Rate Calendars. To specify these attributes in a file for Data Import, you would enter:

(spSKU), description, scninitialohflour@CHI, white flour,200 pounds,price,USD,pound,,1/1/2000,4/1/2000,.30,,4/1/2000,7/1/2000,.32,maxohpenalty,USD,pound,,1/1/2000, 4/1/2000, 5,,4/1/2000, 7/1/2000, 6

To define one price for all time intervals (time-independent values), use min_time and max_time in place of the <interval_start_date> and <interval_end_date>. For example, to define a time-independent price, you would enter:

(spSKU), description, scninitialohflour@CHI, white flour,200 pounds,price,USD,pound,,min_time,max_time,.30


When RateCalendar attributes are exported, they also follow the preceding format.

Updating complex attributes

If you are updating complex attributes, you must include all data that comprises that attribute in your input file. If you specify only a portion of the attribute, the values you did not specify will be erased.

For example, if you were updating a calendar attribute, you would need to specify all the intervals within your calendar even if you wanted to update only one of the intervals. If an attribute has four intervals, but you specified only a single time interval during an update process, the process would set the values for the remaining time intervals within your calendar to zero. For the calendar with four intervals:

(spSKU)10100,USD, unit,,1/1/2000,4/1/2000,12,,4/1/2000,7/1/2000,12.5,,7/1/2000,10/1/2000,12.25,,10/1/2000,1/1/2001,13

to set the last interval to 15, you would need to specify the following in your input file:

(spSKU)10100,USD, unit,,1/1/2000,4/1/2000,12,,4/1/2000,7/1/2000,12.5,,7/1/2000,10/1/2000,12.25,,10/1/2000,1/1/2001,15

Tip: Importing many QtyCalendar attributes can be simplified using the Data Loader. See the section “Using the Data Loader to import data” on page 43 for more information. You can also use the Strategy Calendar utility to manage many of your calendar values. See the section “Maintaining calendars” on page 63 for more information.


Importing data

This section describes the process for importing data to create or update objects in Strategy. To create an object or update an attribute associated with an object, your entries in the input file must be formatted as:

(<object>),<attribute_name>, <attribute_name>. . .<name>,< attribute_value>, <attribute_value>. . .[<name>, <attribute_value>, <attribute_value>. . .]

The <object> names are shown in Table 1 on page 12 and described in more detail in the chapter “Overview of NetWORKS Strategy objects” on page 77. The tables within this chapter lists the <attribute_names> for each object, as well as information on the format needed for the <attribute_values>.

For example, to create a SKU called flour@CHI and set the attributes for description and initial onhand, enter the following:

(spSKU), item, location, description, scninitialohflour@CHI, flour, CHI, white flour, 200 pounds

You can create more than one SKU by entering additional lines. Each new object name must be enclosed in parentheses ( ) in the file to signal that a new type of object is to be created. For example, to create items, locations, and SKUs in the same file, you would format it as:

(spITEM), description, isstorable, defaultuofmflour, white flour, true, poundsugar, brown sugar, true, pound20000,1 gallon bags, true, unit(spLOCATION), description, isplantCHI, chicago, true(spSKU), item, location, descriptionflour@CHI, flour, CHI, white floursugar@CHI, sugar, CHI, brown sugar

Tip: Adding to existing data can be streamlined by exporting the object with its existing attribute, adding or updating the new data, and then reimporting the object and attribute.

You can also use the Strategy Calendar utility to manage many of your calendar values. See the section “Maintaining calendars” on page 63 for more information.


Special formatting rules apply for creating and updating many objects (see “Special formatting for complex objects” on page 14 for a listing). Attributes with certain data types require a special format. See “Importing and exporting complex attributes” on page 15 for additional information.

Creating versus updating objects using Data Import

The Data Import process can be used to create new objects or to update existing objects. The process creates or updates based on whether the <name> you specify for the object exists or not.

Creating objects

If an object with the specified <name> does not exist, a new object will be created with the name and the attribute value(s) specified. You must list all the required attributes and values for an object in order to create it. For example, in order to create a SKU, you must specify the item and location attributes for the SKU:

(spSKU), item, locationpunch@plant1, punch, plant1

Required attributes are noted for each object in the section that describes that object later in this manual.

In addition, when you are creating multiple objects, you must specify a value for each attribute listed in the header row for that object. For example, if you created three locations and specified the following attributes in the header row:

(splocation), issupplier, isplant, isdc, iscustomer

Note: Because the item and location objects are referenced by the SKU objects, you must order the file so that the items and locations are created first, then the SKUs are created.

Tip: The sample input file stratimport.txt is located in the Strategy impexp directory on the client or the server (..\manuv62\scnams\impexp for Windows or ../manuv62/scnams/impexp for UNIX).

Tip: Importing many objects and attributes can be simplified using the Data Loader. See the chapter “Using the Data Loader to import data” on page 43 for more information.


you must include a value for each attribute for each object, even if it is the default value for that attribute. For example:

(splocation), issupplier, isplant, isdc, iscustomerATL, true, false, false, falseLOS, false, true, false, falseDUT, false, false, true, false

If you do not specify an attribute in the header row of your input file and the attribute is not required to create the object, a null or default value will be inserted for that attribute. Default values may differ when you create an object using the Data Import process compared with when you create an object in the Strategy userviews. Default values are listed for each object in the section that describes that object later in this manual.

Updating objects

If an object with the specified <name> already exists, the Data Import process will update only the attribute values that you specify in the header row. For example, if you had the following input file:

(spsku), costpricetypecookies@CHI, off

you would replace whatever value previously existed for the costpricetype attribute with the value off.

If you specify an attribute in a header row and don’t provide a value beneath it, you will overwrite the value for that attribute with a null value. For example, if you specify:

(spsku), description, usemaxsourcingcookies@CHI, ,true

you would clear the existing value for the description attribute. If the attribute you are clearing is at the end of a line, you must include the second separator character to signal the blank field. For example:

(spsku), description

cookies@CHI, ,

Note: To clear complex attributes with a data type of QtyCalendar, RateCalendar, or CapacityCalendar, you must specify the UOM, even if you enter blanks. To enter a blank UOM, enter four underscores (____). For example:


(spSKU),flour@CHI,,mininflow,____

Once an object has been created, some attributes (for example, name) cannot be updated. Refer to the section of this manual specific to an object for information on read-only attributes; such attributes are shaded in the tables that describe the object’s attributes.

Using wildcards to update multiple objects

You can use a wildcard character (*) for the <name> in order to update all or a group of object records with a single attribute value. For example, to update all SKUs to assign a Cost/Price type of Off, you could enter the following in your input file:

(spSKU), CostPriceType*,Off

You can also use the wildcard character to take advantage of the naming conventions of objects. For example, you could use the wildcard character to update the Requirement attribute on selected SKURequirements. For example:

(SKURequirement)12ozSoda@PlantA*,requirement, gallon,,7/1/2000, 10/1/2000, 2500,,10/1/2000, 1/1/2001, 3000

The above example would assign the requirement to all input SKURequirements for 12ozSoda@PlantA.

Using data selections to update objects

If you have defined a data selection in a Strategy userview, you can use that data selection in your input file to specify those objects you want to update. The format for using data selections is:

(<object>), <attribute_name>=data_selection<data_selection_name>, <attribute_value>

For example, if you defined a data selection for Labor resources at Chicago, you could use that data selection in your input file to update the FixedCost attribute on those resources, as follows:

(spreusableresource)=data_selection


Labor resources at Chicago,fixedcost, USD, year,,min_time, 7/1/1999, 10000,,7/1/1999, max_time, 12500

Guidelines for using Data Selections

• Any user can use a data selection with a Scope of Public in an input file.

• Only the user who defined the data selection can use data selections with a Scope of User in an input file. If another user attempts to use a data selection with a Scope of User, the process will return a message that the data selection is not found.

• You cannot use data selections that prompt you for a value.

• If you are using Scheduling and Strategy in the same database, you cannot have data selections with the same name in both the Scheduling and Strategy folders. If you do have two data selections with the same name and you specify the name of a data selection in your input file, the process will use the data selection that was created first, regardless of which folder the process is run from.

See the online help for additional information on creating data selections.

Using attributes other than name to update objects

You can also select objects for updating by specifying certain attributes other than name. The format for selecting by another attribute is:

(<object>),<attribute_name>=<selection_attribute><selection_attribute_value>, <update_attribute_value>

For example, to update the IndependentDemand attribute for all SKUs where UseEntireTimeHorizon equals False, you could format your input file as follows:

(spReusableResource)=ResTypeLabor,Cost, USD, Hour,,min_time, 7/1/1999, 250000,,7/1/1999, max_time, 300000

If there are no objects that meet the criteria you specified, you will receive an error message that "Object "<value> of type "<object_type>" not found: caused update to fail. For example, in the preceding example, if there were no Reusable Resource with


a ResType of Labor, you would receive the message: Object ’labor’ of type "spresuableresource" not found: caused update to fail.

• Lane: SourceLocation, MaxCapacityStatus, MinCapacityStatus

• PurchaseProcess: OverriddenUnitPrice, CostPriceType, TieredCostPrice

• ResourceRequirement: ReusableResource, Demander

• spReusableResource: ResLoc, MinCapacityStatus, MaxCapacityStatus, CostPriceType, TieredCostPrice

• spSKU: MinInflowStatus, MaxInflowStatus, MinOutflowStatus, MaxOutflowStatus, SafetyStockStatus, MaxOHStatus, IndependentDemandStatus, and MaxDemandStatus, TargetOHStatus, CostPriceType, TieredCostPrice

• SKURequirement: Supplier, Demander, PercentageConstraintEnabled

Some duration attributes are also supported. See “Data types for database attributes” on page 173 for more information.

Running the Data Import process

After you have set up your input file to import or update data, use the Data Import process to read the file and import your data.

To run the Data Import process:

Important: The above option is supported for all attributes with a data type of string, list of values, boolean, decimal, duration, integer, and list. However you cannot use the following attributes to select objects when setting up input files:

Important: Before you import data, back up the database (see the NetWORKS Scheduling and Strategy Installation/Administration Manual) so that you can recover your data if the Data Import process does not work correctly.


1. Transfer your input file to the ..\manuv62\scnams\impexp directory (Windows) or ../manuv62/scnams/impexp directory (UNIX).

2. In the Processes pane of the Strategy application, double-click Data Import.

3. In the Action box, select Import.

4. In the Data files section:

a. For Location, select Client or Server/Stand-alone to designate whether your input file is on your computer or on the server computer. If your client and server are on the same computer, select Server/Stand-alone.

b. In the File to be imported box, enter the name of your input file or click Browse to select the file from a location on your computer.

5. Select the separator character you used to separate the values in your input file.

6. In the Commit section:

a. Change Commit after every ‘n’ updates to the desired setting. If your system is memory-constrained and you have a large input file, you may want to commit more often to decrease memory usage. Otherwise, committing less often usually leads to better processing performance.

b. If desired, select or deselect the Always commit on new object type check box. If this check box is selected, the process will commit to the database each time it encounters a new header row that defines an object in your input file, regardless of the commit interval. If you have many different types of objects interspersed within your file, the process will run faster if you do not select this option.

7. Enter a value for the Max. number of exceptions to process. This setting determines how many warnings or errors the process will allow before it stops processing your input file.

Note: By default, the process looks for the file in this location. Alternatively, you can specify the full path to the file and skip this step. If specifying a path, you must use the path on the client if Client is selected as the Location and the path on the server if Server/Stand-alone is selected.

Tip: Browse is enabled only if the Location is set to Client. If your client and server are on the same computer (standalone), you can select Client to enable the Browse button, select your file, then reselect Server/Stand-alone.


8. To save your settings, click Apply. If you click Apply, you will save all your settings so that they appear the next time you run this process.

9. Click OK to start the process.

A Process Status window appears. If there are errors in your input file, the process may generate warnings and continue, or it may stop. The following errors in your input file will cause a warning exception to be generated and the process to continue (up to the number of errors you specified for Max. number of exceptions to process), but the object will not be created:

• An object you specified cannot be created because it depends on other objects that do not exist.

• An object you specified cannot be created because you did not specify required values.

• You specified the name of an object incorrectly such that if the object were created as specified, it would duplicate another object.

The following errors in your input file will cause the process to stop and not continue:

• An attribute value is not formatted properly or contains invalid values (for example, a string instead of a number; T instead of True).

• An object-type or attribute name is spelled incorrectly.

• A value is not specified for an attribute that appears in your header row.

Comment lines and header rows are included in the calculation of line number. In some instances where an error would cause database corruption, the process may roll back to the last commit point. In this case, you will see a message that gives the line number where the error occurred and the line number to which the updates were rolled back.

Note: If the process stops due to one of the above errors, all lines up until the error occurred will be committed. If the process fails, you will see a message noting the line number where the error occurred. You can then correct your error and continue your import with a file that contains the data from the erroneous line forward.

Tip: If you see the error "Data cannot be specified without a header preceding it; Check input file" and you do have a header row in your input file, check to see that you selected the correct separator character for your input file.


When a Data Import process has completed successfully, click on Exception

Manager in the Process Status window to review any business exceptions that were generated during the process. You can also use the Process Status userview to make sure that the process completed successfully. Refer to the online help for information on using these userviews.

Deleting data

You can delete any object that exists in Strategy. You must delete the entire object. To delete objects, your entries in the input file can be formatted as:

(<object>)<name>[<name>]

For example, if you wanted to delete the SKUs flour@CHI and wwflour@CHI, you would enter the following in your input file:

(spsku)flour@CHIwwflour@CHI

The <object> names are shown in Table 1 on page 12 and described in more detail in the chapter “Overview of NetWORKS Strategy objects” on page 77.

You can delete more than one object by entering additional lines. Each new object name must be enclosed in parentheses ( ) in the file to signal that a new type of object is to be deleted. For example, to delete SKUS, items, and locations in the same file, you would format it as:

(spSKU)bread@ATL(spitem)bread(splocation)ATL

Note: Because the SKU references the item and location objects, you must order the file so that the SKU is deleted first and the items and locations are deleted last.


If you try to delete an object that another object depends on, you will see a warning exception in the Exception Manager. See the chapter “Overview of NetWORKS Strategy objects” on page 77 for information on dependencies between objects.

Using wildcards to delete multiple objects

You can use a wildcard character (*) for the <name> in order to delete all or a group of object records. For example, to delete all SKUs, you could format your input file as follows:

(spSKU)*

You can also use the wildcard character to take advantage of the naming conventions of objects. You can use a leading or trailing wildcard (for example, item*, *311, or *tex*) to delete multiple objects that begin or end with the same characters. For example, to delete all purchase processes for item1, you would format your input file as follows:

(purchaseprocess)Buy--item1*

The above format would delete all purchase processes in the database that begin with item1, as all processes start with Buy--<item_name>

Using data selections to delete objects

If you have defined a data selection in a Strategy userview or the Manugistics Explorer, you can use that data selection in your input file to specify those objects you want to delete. The format for using data selections is:

(<object>)=data_selection<data_selection_name>

For example, if you defined a data selection for all SKUs that contain itemA and named it itemA, you could use that data selection in your input file to delete all SKUs in that data selection:

(spSKU)

Tip: The sample input file stratdelete.txt is located in the Strategy impexp directory on the client or the server (..\manuv62\scnams\impexp for Windows or ../manuv62/scnams/impexp for UNIX). Note that both Strategy and Scheduling use the NamedCalendar object, so care should be taken in deleting this object if both components are using the same database.


=data_selectionitemA

See the section “Guidelines for using Data Selections” on page 24 for restrictions on using data selections. See the online help for additional information on creating data selections.

Using attributes other than name to delete objects

In some instances, you can also select objects to delete based on the value of one of the object’s attributes. To do this, you would format your input file as follows:

(<object>)=<selection_attribute><selection_attribute_value>

For example, to delete all SKUs with an item of itemA, enter the following in your input file:

(spSKU)=itemitemA

Running the Delete Data process

After you have set up your input file to delete data, use the Delete Data process to read the file and delete your data.

Note: The previous option is supported only for attributes with a data type of string, list of values, boolean, decimal, integer, and list. Some duration attributes are not supported. See the sections “Using attributes other than name to update objects” on page 24 and “Data types for database attributes” on page 173 for other exceptions.

Important: Before you delete data, back up the database (see the NetWORKS Scheduling and Strategy Installation/Administration Manual) so that you can recover your data if the Delete Data process does not work correctly.

Tip: Before running the Delete Data process, you can test your input file by using the Data Export process to export the data. You can then confirm that the data exported is what is meant to be deleted. See the section “Running the Data Export process” on page 36 for information on exporting data.


To run the Delete Data process:


2. In the Processes pane of the Strategy application, double-click Delete Data.



b. In the File to be imported box, enter the name of your input file or click Browse to select the file from a location on your computer.


5. In the Commit section, change Commit after every ‘n’ updates to the desired setting. If your system is memory-constrained and you have a large input file, you may want to commit more often to decrease memory usage. Otherwise, committing less often usually leads to better processing performance.


7. To save your settings, click Apply.


Note: By default, the process looks for the file in this location. Alternatively, you can specify the full path to the file and skip this step. If specifying a path, you must use the path on the client if Client is selected as the Location and use the path on the server if Server/Stand-alone is selected.



A Process Status window appears. If there are errors in your input file, the process will generate a warning exception and continue (up to the value of Max. number of

exceptions to process). You will receive warnings if:

• Object to be deleted is not found

• Object cannot be deleted because it is referenced by other objects

In addition, the Delete Data process may fail and not continue if you spell the name of an object-type incorrectly. If the process stops, all deletions will be made up to the point where the process fails. If the process fails, you will see a message noting the line number where the error occurred. You can then correct your error and continue your process with a file that contains the data from the point forward from where the error was.

When a Delete Data process has completed successfully, click on Exception Manager in the Process Status window to review any business exceptions that were generated during the process. You can also use the Process Status userview to make sure that the process completed successfully. Refer to the online help for information on using these userviews.

Exporting data

This section describes the process for exporting data from Strategy to a text file. You can export all information about an object or you can export only selected attribute values for an object. The <object> names are shown in Table 1 on page 12 and described in more detail in the chapter “Overview of NetWORKS Strategy objects” on page 77.

Special formatting rules apply for exporting many objects (see “Importing and exporting complex attributes” on page 15 for a listing).

If you export more than one type of object with the intention of reimporting the data into another database, be sure you format your export file such that dependent


Tip: The sample input file stratexport.txt is located in the Strategy impexp directory on the client or the server (..\manuv62\scnams\impexp for Windows or ../manuv62/scnams/impexp for UNIX).


objects are exported after the objects they depend upon. For example, you would want to export items and locations first, then SKUs and reusable resources. In addition, make sure you export any required attributes for your objects. See “Overview of NetWORKS Strategy objects” on page 77 for specific information on dependencies between objects and required attributes for each object. See the sample input file (stratexport.txt) for an example of a file that will allow you to reimport your data to another database.

Exporting selected attributes

To export an object and certain attributes of an object, your entries in the input file must be formatted as:

(<object>),<attribute_name>, <attribute_name>. . .<name>[<name>]

For example, to export the description and Strategy initial onhand attributes of the SKU called flour@CHI, enter the following in the input file:

(spSKU), description, SCNinitialohflour@CHI

To export the same data for more than one object, enter the additional objects on additional lines. For example, to export the same attributes for item1@FLA and item2@FLA, you would enter:

(spSKU), description, SCNinitialohitem1@FLAitem2@FLA

If you export multiple types of objects, each new object must be enclosed in parentheses ( ) in the file. For example:

(spITEM), description, isstorable, defaultuofmfloursugar(spLOCATION), description, isplant,issupplier,isdc,iscustomerCHI(spSKU), description, SCNinitialohflour@CHIsugar@CHI20000@CHI


Exporting all attributes

You can use a wildcard character (*) for the <attribute_name> in order to export all attributes for an object. To do this, format your input file as follows:

(<object>), *<name>[<name>]

For example, to export all attributes for the SKUs flour@SFO and sugar@SFO, you would format your input file as follows:

(spSKU),*flour@SFOsugar@SFO

Using wildcards to export objects

You can use a wildcard character (*) for the <name> in order to export all or a group of object records. For example, to export the name of all SKUs, you could format your input file as follows:

(spSKU)*

You can also use the wildcard character to take advantage of the naming conventions of objects. You can use a leading or trailing wildcard (for example, item*, *311, or *tex*) to export multiple objects that begin or end with the same characters.

For example, to export all buy purchase processes for item1 in Strategy, you could format your input file as follows:

(purchaseprocess)Buy--item1*

The above format would export only the names of all purchase processes in the database for item1, as all processes start with Buy--<item_name>.


To export all attributes for all purchase processes, you could format your file as:

(purchaseprocess),**

Using data selections to export data

If you have defined a data selection in a Strategy userview, you can use that data selection in your input file to specify those objects you want to export. The format for using data selections is:

(<object>), <attribute_name>, <attribute_name>,. . .=data_selection<data_selection_name>

For example, if you defined a data selection for all SKUs that contain itemA and named it itemA, you could use that data selection in your input file to export all SKUs in that data selection:

(spSKU)=data_selectionitemA

See the section “Guidelines for using Data Selections” on page 24 for restrictions on using data selections. See the online help for additional information on creating data selections.

Using attributes other than name to export objects

You can also export objects by specifying attribute values. You would use the following format:

(<object>),* =<selection-attribute><selection-attribute-value>

For example, to export all attributes for location objects where the isSupplier attribute is set to “true,” you would enter the following in your input file:

Note: If you use a wildcard to export all objects of a particular type and there are no objects of that type found in the database, Data Export will generate a warning exception and comment out the header line for that object in your exported file. This allows you to reimport the file without receiving an error.


(spLocation),*=issuppliertrue

Running the Data Export process

After you have set up your input file to import or update data, use the Data Export process to read the file and export your data.

To run the Data Export process:


2. In the Processes pane of the Strategy application, double-click Data Export.

3. In the Action box, select Export.



b. In the Input file for export box, enter the name of your input file or click Browse to select the file from a location on your computer.

c. In the Export filename box, enter the name of the file that you want to contain your exported data.

Note: The above option is supported only for attributes with a data type of string, list of values, boolean, decimal, integer, and list. However, there are some exceptions to this. See the sections “Using attributes other than name to update objects” on page 24 and “Data types for database attributes” on page 173 for exceptions.

Note: By default, the process looks for the file in this location. Alternatively, you can specify the full path to the file and skip this step. If specifying a path, you must use the path on the client if Client is selected as the Location and the path on the server if Server/Stand-alone is selected.





7. To save your settings, click Apply.


A Process Status window appears. If there are errors in your input file (for example, a specified object does not exist), the process will generate a warning and continue. If you misspelled an object-type or attribute name in your input file or if you have invalid values in your database, the Data Export process may fail with a partially written data file and not continue. In this case, you must correct your input file or your database and start the process again.

When a Data Export process has completed successfully, click on Exception

Manager in the Process Status window to review any business exceptions that were generated during the process. You can also use the Process Status userview to make sure that the process completed successfully. Refer to the online help for information on using these userviews.

Tips on creating input files

This section gives tips on creating input files. If you want to create an input file using data from a relational database, you can use standard Structured Query Language (SQL) queries in conjunction with a spreadsheet program to assist you. You can also use a spreadsheet program alone to create your input file. The sections that follow provide tips on how to use SQL and a spreadsheet program to create an input file using data exported from a relational database.

To create an input file, you can do the following:

• Use SQL to export the relevant data from your relational database to a file.

• Import the file into a spreadsheet program.

• Add columns into the spreadsheet to define additional attributes for the objects.

• Save and export the data to a comma-delimited file.



Each of the previous steps is described in the sections that follow.

Using SQL to export data

If portions of your data are stored in a relational database, you can use SQL queries to create a file to which you can add additional data. For example, if you had used the Data Transfer process to import SKUs from NetWORKS Fulfillment, you may want to update the attributes that were not available in Fulfillment. To create a file that contains the names of the SKUs in your relational database, issue the following query:

spool <filename>select distinct '(spsku),item,location' from skuselect item,'@',loc, ',', item, ',', loc from [<owner>].skuspool off

This query results in a file that looks something like the following:

(spsku), item, location10300 @OAKLD, 10300, OAKLD10300 @PHIL, 10300, PHIL10300 @SCMTO, 10300, SCMTO200-00-000@CHI, 200-00-000, CHI200-08-000@CHI, 200-08-000, CHI200-08-199@CHI, 200-08-199, CHI200-10-000@CHI, 200-10-000, CHI

Tip: Turn off certain query options so that the file conforms to a "flat file" format. For example, in Oracle's SQL*Plus, enter the following prior to executing the query:

Set newpage 0Set space 0Set linesize <max-line-width>Set pagesize 0Set echo offSet feedback offSet heading offColumn <column> format A<max-column-width>

where <column> is the name, <max-line-width> is the maximum line size, and <max-column-width> is the maximum width of the column you are exporting. Setting these options keeps SQL*Plus from inserting page breaks, extra spaces, or messages into your output.


You can invoke multiple SQL queries to generate objects for the same input file. If you do this, make sure you order your SQL statement so that objects are created in an order that honors Strategy dependencies.

For example, you could query for data on items, locations, and SKUs for a single input file, as follows:

spool <filename>select distinct '(spitem),','defaultuofm' from item;select item, ',', uom from [<owner>].item;select distinct '(splocation)' from loc;select loc from [<owner>].loc;select distinct '(spsku)' from sku;select item, '@', loc, ',', item, ',', loc from[<owner>].sku;spool off

See the following section for information on importing the file into a spreadsheet program, such as Microsoft Excel or Lotus 123.

Importing a file into a spreadsheet

Once you have created a file using SQL queries, you can import the file into a spreadsheet program and add information about the attributes that you want to update. To import a text file, follow the instructions that accompany your spreadsheet


program. After importing a file into Microsoft Excel, your screen might look something like Figure 1.

Adding attributes and values in a spreadsheet

After importing the file into a spreadsheet program, you can add the attributes and values necessary to complete your input file. For example, if you wanted to update

Figure 1: Microsoft Excel spreadsheet containing imported text file


the values for the location types and SKU description, your spreadsheet might look something like Figure 2.

Once you have entered the appropriate data into the spreadsheet, you can save the file as a delimited text file (or export the data to a file, depending on your application).

Tip: You can add bold and underline formatting to your spreadsheet to enhance readability.

Figure 2: Microsoft Excel spreadsheet with edited location and SKU description values


A comma-delimited file from the previous spreadsheet looks like Figure 3 when exported from Microsoft Excel.

Figure 3: Sample file exported from spreadsheet

Note: The extra commas do not affect the import program, as long as they are consistent throughout the file in both the header and body rows. If the last attribute value(s) for an object are null, you may lose the commas for these attributes when you export the spreadsheet to a comma-delimited file. To avoid this, put a blank character in any columns that have null values at the end of a row. You can also have extra sets of quotation marks, as long as they are balanced, meaning the same number appear on either side of a word or phrase and they are not on a comment line.

Chapter 3

Using the Data Loader to import data

The chapter explains how to use the Data Loader tool to import different kinds of data into NetWORKS Strategy. The Data Loader is a set of utilities that helps you create easy-to-use templates for loading data using the Data Import process.

Overview

The Data Loader utility allows users of Data Import/Export the ability to rapidly populate an import file template with object data from a spreadsheet application, such as Microsoft Excel. The utility runs on a NetWORKS Strategy client computer.

To use the tool, you must:

1. Create a template containing keywords that specify the Data Import/Export format of a specific Strategy object.

2. Create a data file containing data to be loaded into the template structure. Columns in the data file are headed by the keywords used in the template. Each row of data in the data file maps to one populated instance of the template.

3. Run the Data Loader utility to map the data from the data file into the template, creating a mapped output file. A parameter of the utility determines the format of the output file, for example, the format for a MakeProcess, a Rate, or a Generic template.

4. Import the mapped output files into Strategy using the Data Import process. See the chapter “Importing, exporting, and deleting data” on page 9 for more information on using the Data Import process.

This chapter describes, with examples, how to build templates and data files for use with the Data Loader, as well as how to run the Data Loader tool to create the import files.

Sample Data Loader files

Sample template and data files are located in the Manugistics manuv62\scnams\bin\help directory on a client workstation. The files are of type .csv,


which can be opened with a spreadsheet application such as Microsoft Excel. A sample template and a sample data file are included for each Strategy object.

Each of the following sections describes a template for an object, defines the keywords in the template, and refers you to the corresponding sample template and data file.

Templates

This section details how to generate a template, what the different parts of the template mean, and how to add keywords to the template so it can be used to load data quickly and efficiently.

Strategy uses three different template formats:

• Make Process template

• Rate template

• Generic template

MakeProcess template

The MakeProcess template can be used to define the Data Import files for the MakeProcess and its corresponding SKU and ResourceRequirement objects. The template allows you to define production requirements in a spreadsheet format.

For a sample MakeProcess template and data file, see maketemplate.csv and stratmakedata.csv in the Manugistics manuv62\scnams\bin\help directory.

The MakeProcess input file is generated using the -m option when the Data Loader is run. For more information, see “Running the Data Loader tool” on page 56.

The required keywords in the template are listed in Table 2.

Table 2: Required keywords in the MakeProcess template

Keyword Definition

RESLOC The location of the process.

MITEM The primary item to be made by this process.

MPLABEL A description of the process (required if multiple routings are possible for a SKU).

Using the Data Loader to import data 45

Guidelines for importing MakeProcesses

• The input SKU lines and additional output SKU lines for SKURequirements and the lines for the ResourceRequirements have been hard-coded in the Data Loader and therefore cannot be modified using the template.

• Zero or more RESTYPE, RESLABEL, RESUOFM, RESRATE columns can be specified in the data file. Each quadruplet of columns will create a ResourceRequirement on the MakeProcess when the data line has a value for RESTYPE that is not blank. You must use all four columns to create a ResourceRequirement.

• In the data file, zero or more INPUT_ITEM, ISRATE, and ISUOFM columns can be specified. Each triplet of columns will create an input SKURequirement on the

PROD_RATE The numerator of the production rate (SKURequirement for the MITEM).

PROD_RATE_UOFM The default unit of measure for MITEM.

Important: When the following keywords exist in the data file, SKU and Resource Requirements are generated by the Data Loader. These keywords are not found in the template file.

OUTPUT_ITEM Used for additional output SKUs in the case of by-products (optional).

OSRATE The SKURequirement for the secondary output SKU (required if OUTPUT_ITEM is used).

OSUOFM The default unit of measure for OUTPUT_SKU (required if OUTPUT_ITEM is used).

INPUT_ITEM Item required to make MITEM (optional).

ISRATE Quantity of item to make the MITEM (required if INPUT_ITEM is used).

ISUOFM The default unit of measure for INPUT_ITEM (required if INPUT_ITEM is used).

RESTYPE Type of reusable resource used to make this item (optional).

RESLABEL User-defined description of the reusable resource (required if RESTYPE is used).

RESUOFM The default unit of measure for the reusable resource (required if RESTYPE is used).

RESRATE The quantity of resource required for this process and the denominator of the production rate (required if RESTYPE is used).

Table 2: Required keywords in the MakeProcess template (continued)

Keyword Definition


MakeProcess when the data line has a value for INPUT_ITEM that is not blank. You must use all three columns to create a SKURequirement.

• Zero or more OUTPUT_ITEM, OSRATE, and OSUOFM columns can be specified in the data file. Each triplet of columns will create an output SKURequirement on the MakeProcess when the data line has a value for OUTPUT_ITEM that is not blank. You must use all three columns to create a SKURequirement.

Generic templates

Using the generic template you can define Data Import files for objects and attributes that are related. They enable you to define data in a familiar spreadsheet format.

Lane template

The Lane template is used to create Lanes and Lane resources. If you import costs in a different file, remove the FREIGHTRATE column.

For a sample Lane template and data file, see stratlanetemplate.csv and stratlanedata.csv in the Manugistics manuv62\scnams\bin\help directory.

A Lane input file is generated using the –gns flag option when the Data Loader is run. For more information, see “Running the Data Loader tool” on page 56.

Lane template keywords are described in Table 3.

Table 3: Keywords in the Lane template

Keyword Definition

SOURCELOC A location identified as a source of SKUs.

DESTLOC A location identified as destination of SKUs.

LANELABEL A unique identifier to define a lane.

RESTYPE Transportation or ExtraTransportation.

RESLABEL User-defined description of the reusable resource.

RESUOFM The default unit of measure for the reusable resource.

FREIGHTRATE The cost of freight for this lane per default unit of measure.


Strategy MoveProcess and PurchaseProcess templates

The MoveProcess and PurchaseProcess templates can be used to define the Data Import files for either MoveProcesses or PurchaseProcesses and their corresponding SKURequirement and ResourceRequirement objects. (The PurchaseProcess templates consist of templates for Buy processes and Sell processes.) These templates enable you to define sourcing requirements in a spreadsheet format.

For sample MoveProcess and PurchaseProcess templates and data files, see the following files in the Manugistics manuv62\scnams\bin\help directory:

• MoveProcessTemplate.csv

• BuyProcessTemplate.csv

• SellProcessTemplate.csv

• MovePurchProcessData.csv

Input files for Move and Purchase processes are generated using the –gns option when the Data Loader is run. For more information, see “Running the Data Loader tool” on page 56.

Keywords for these templates are described in Table 4.

Inventory SKURequirement template

This template can be used to create the SKURequirements for an inventory resource.

Table 4: Keywords in the Move and PurchaseProcess templates

Keyword Definition

MOITEM Item to be moved through the process.

MPLABEL The name of the Move or PurchaseProcess.

MO_RATE The number of units to be moved per resource unit of measure.

TRANSRES_UOFM The unit of measure for transportation costs or capacity.

SOURCELOC A location identified as a source of SKUs.

DESTLOC A location identified as destination of SKUs.

LANELABEL A unique identifier to define a lane.

RESLABEL User-defined description of the reusable resource.


For sample template and data files for a SKURequirement object, see InvResReqTemplate.csv and InvResReqData.csv in the Manugistics manuv62\scnams\bin\help directory.

Keywords in the template are explained in Table 5.

Rate templates

The Rate templates are used when importing object attributes that require either a QtyCalendar or a RateCalendar format, for example, independent demand, capacities, costs, and so on. For more information about these formats, see “Working with QtyCalendar attributes” on page 16 and “Working with RateCalendar attributes” on page 17. The Rate templates already contain the required keywords and are ready for use as input files for Rate data.

Input files for Rate data are generated using the –r flag option when the Data Loader is run. For more information, see “Running the Data Loader tool” on page 56.

Rate template structure

The Rate template has a distinct structure based on a quantity or rate calendar for the SKU or Reusable Resource objects. When using rate templates, do the following:

1. Create data files by first adding all of the keywords as column headings.

2. In increasing order (from left to right), create column headings that are dates.

Table 5: Keywords in the Inventory SKURequirement template

Keyword Definition

SKU Item at location to be associated with the inventory resource.

RESLABEL User-defined label for the inventory resource.

LOC Location of the inventory resource.

RES_UOFM Unit of measure used by the inventory resource.

Note: All Data Import date formats are accepted, such as two year, four year, without time, with time, MIN_TIME, MAX_TIME, and so on. Each pair of date column headings represents an interval, where the left column of the pair is the start time and the right column of the pair is the end time.


3. Specify the rate value itself at the end time of each pair. The date value for the first date column heading is always left blank.

SKUIndependentDemand template

This template file can be used to convert your data into the quantity calendar format necessary to import independent demand data into Strategy for SKU objects. The status flag for the Independent Demand attribute has a default value of Soft. If the constraint is set to Hard, change the template file.

For a sample Independent Demand template and data file, see StratSkuIndDeptemplate.csv and StratSkuIndDepdata.csv in the Manugistics manuv62\scnams\bin\help directory.

Keywords in the template are described in Table 6.

Customizing the SKU Independent Demand template to import other SKU attributes

You can customize the Independent Demand template to update the following other SKU attributes:

• Maximum Demand

• Maximum On Hand

• Maximum Inflow Amount

• Maximum Outflow Amount

• Minimum Inflow Amount

Note: The second date column is the end time of the interval beginning at the first date column and the start time of the interval which ends at the third date column. You may specify as few or as many date column headings in the data file as is necessary to specify rates.

Table 6: Keywords in the SKU Independent Demand template

Keyword Definition

ITEM Name of an existing item.

LOCATION Name of an existing location.

UOFM The default unit of measure for the item.


• Maximum Inflow Amount

To customize the template, open the template file in a spreadsheet application, such as Microsoft Excel. Use the Find and Replace features of the application to locate the string “independentdemand” and replace all occurrences of it with the SKU attribute to be defined (see the section “SKU (spSKU)” on page 138 for the import/export names for these attributes). Save the template as a new file.

Strategy InitialOnHand template

This template file can be used to import On Hand inventory quantities for NetWORKS Fulfillment SKUs into Strategy.

For a sample On Hand template and data file, see StratOnHandsTemplate.csv and StratOnHandsData.csv in the Manugistics manuv62\scnams\bin\help directory.

The keywords are described in Table 7.

Strategy SafetyStock template

You can use this template file to convert your Safety Stock data into the quantity calendar format required to import it into Strategy.

For a sample Safety Stock template and data file, see StratSafetyStockTemplate.csv and StratSafetyStockData.csv in the Manugistics manuv62\scnams\bin\help directory.

Table 7: Keywords in the On Hand template

Keyword Definition

ITEM Item that requires an update to On Hand quantities.

LOCATION Location of the item.

UOFM Unit of measure for the On Hand quantity.

ONHANDS Beginning On Hand quantity for this item and location.



Strategy ResMaxCap template

This template file enables you to provide resource capacity data that can be converted into the quantity calendar format required to import the information into Strategy. The status flag for the Maximum Capacity Enabled attribute of a ReusableResource has a default value of Soft. If you change the value to Hard or Off, you must also change the template file.

For a sample template and data file, see StratResMaxCapTemplate.csv and StratResMaxCapData.csv in the Manugistics manuv62\scnams\bin\help directory.

The keywords in the template are described in Table 9.

You can also customize this template to provide data for the Minimum Capacity attribute. To customize the template, open the template file in a spreadsheet application, such as Microsoft Excel. Use the Find and Replace features of the application to locate the string “MaxCapacity” and replace all occurrences of it with "MinCapacity." Save the template as a new file.

Table 8: Keywords in the Safety Stock template

Keyword Definition

ITEM Item that requires an update to safety stock levels.

LOCATION Location of the item.

UOFM Unit of measure for the safety stock quantity.

SS Safety stock quantity for this item and location.

Table 9: Keywords in the Resource Maximum Capacity template

Keyword Definition

RESLOC The location of the reusable resource.

RESLABEL The name of the reusable resource.

RESTYPE A system-defined resource name, for example, Machinery.

UOFM The default unit of measure for this reusable resource.


Strategy ResCost template

This template file allows you to provide resource costs in a format that can be converted to the rate format required to import these costs into Strategy.

For a sample template and data file, see StratResCostTemplate.csv and StratResCostData.csv in the Manugistics manuv62\scnams\bin\help directory.

Input files for Cost data are generated using the –r flag option when the Data Loader is run.


SpSKURate template

Use this template file to provide Unit Price data for a SKU in a format that can be converted into the rate format required for importing into Strategy.

For a sample template and data file, see SpSKURateTemplate.csv and SpSKURateData.csv in the Manugistics manuv62\scnams\bin\help directory.

Input files for unit price data are generated using the –r flag option when the Data Loader is run.

The keywords for this template are described in Table 11.

Table 10: Keywords in the Resource Cost template

Keyword Definition

RESLOC The location of the reusable resource.

RESLABEL The name of the reusable resource.

RESTYPE A system-defined resource name, for example, Machinery.

UOFM_NUM The unit of measure used to define the cost, for example, dollars.

UOFM_DEM The default unit of measure for the resource.

Table 11: Keywords in the SKU Rate template

Keyword Definition

ITEM Name of an existing item.

LOCATION Name of an existing location.


Customizing the SKU Rate template to import other SKU attributes

You can customize the Rate template to update the following other SKU attributes:

• Cost

• Independent Demand Penalty

• Maximum Demand Penalty

• Maximum Inflow Penalty

• Maximum Outflow Penalty

• Maximum OnHand Penalty

• Safety Stock Penalty

• Minimum Inflow Penalty

• Minimum Outflow Penalty

To customize the template, open the template file in a spreadsheet application, such as Microsoft Excel. Use the Find and Replace features of the application to locate the string “price” and replace all occurrences of it with the SKU attribute to be defined (see the section “SKU (spSKU)” on page 138 for the import/export names for these attributes). Save the template as a new file.

Customizing data files

This section explains the structure of the data file and how to add keywords as column headings to the data file so that it can be used with the template to load data.

Header rows

The first row in a data file is the header row. This row contains the reserved and user-defined keywords that are mapped to the template. There is no limit to the number of user-defined keyword columns.

UOFM_NUM The unit of measure used to define the cost, for example, dollars.

UOFM_DEM The default unit of measure for the item.

Table 11: Keywords in the SKU Rate template (continued)

Keyword Definition


To create a header row in the data file, refer to the template mapped with keywords, and add your keyword to each column heading in the desired order.

Data Rows

The second and subsequent rows are the data rows. Each row of data is mapped to one instance of a template. Each data value in a column is mapped to that column’s keyword in the template. There is no limit to the number of data rows in the spreadsheet.

Fill in your data as appropriate to match your column keywords.

Reserved keywords

The following keywords have special meaning, therefore they cannot be changed in the data files or the templates:

Reserved for the –m flag optionRESLOCRESTYPERESRATERESUOFMINPUT_ITEMISRATEISUOFMOUTPUT_ITEMOSUOFMOSRATE

Reserved for all flag optionsRESLABELLANELABELMPLABEL

Any keyword that is not reserved may be modified inside the template and data files. For example, you can rename MITEM in the StratMakeTemplate.csv and StratMakeData.csv files.

Important: If you change a keyword, you must change it in both the template and the data file.


Customizing keywords

When using the –m option, you can append letters or numbers to the following keywords:

RESTYPERESRATERESUOFMRESLABELINPUT_ITEMISRATEISUOFMOUTPUT_ITEMOSUOFMOSRATE

For example, you can have:

Label keywords

The following keywords are used as labels for certain types of objects:

RESLABELLANELABELMPLABEL

When working with a template for an object having a label, you must use one of the above keywords because the Data Loader behaves a specific way when it encounters one of them in the file. When the data value corresponding to one of these keywords is blank, any leading underscore found before the label keyword in the template is removed.

For example, when LANELABEL is blank, you might see:

Chicago->Atlanta

But when it is not blank, you would see:

Chicago->Atlanta_truck

INPUT_ITEM1 ISRATE1 ISUOFM1 OUTPUT_ITEM2 ISRATE2 ISUOFM2

A 5 unit B 6 gram


Mapping user-defined keywords

This section describes how to add user-defined keywords to a template. User-defined keywords enable you to map your data from the keyword-mapped data file to the template.

You might not need to provide a keyword for every data field in the template. Some of the data fields will have the same value for all instances. You should provide template keywords only for columns that might change across instances, which will reduce the size of the data file you must create. For example, a ReusableResource Cost is either enabled or not, that is, the attribute is set to either True or False. The setting does not change, therefore you do not need to map that attribute and provide data for it.

Adding user-defined keywords to a template

Certain fields in the template require only user-defined keywords. Do the following:

1. Identify those data fields that require user-defined keywords.

2. Replace the data field values with meaningful keywords. For example, ORDERQTY, AMOUNT, or SSRULE.

Guidelines• You cannot use a keyword that is also used as an actual piece of data. For

example, you could not use a keyword called Packline and data such as Packline1, Packline2, and Packline3. Instead, set the keyword to something different, such as Packoutres.

• Avoid including superfluous data in the data file. It will cause errors when

you run the Data Loader tool.

Running the Data Loader tool

This section describes how to use the utility and its parameters and their meaning. Before using the tool, note the following:

Important: You can choose any keyword you want for a data field, however, you cannot repeat keywords and you must not use keywords that include substrings of other keywords. For example, OUTPUT_ITEM exists as a reserved keyword; therefore, you cannot have a user-defined keyword of OUTPUT or ITEM.


• All of the required files (template and data file) must exist in one directory (for example, the manuv62\scnams\impexp directory).

• The commands and parameters for using the Data Loader are run from an MS-DOS command line, within the same directory in which the required files are stored.

• You run the Data Loader tool using a single command with options that specify the format of the generated file.

Syntax of the command

To run the Data Loader tool:

1. Open a command prompt (MS-DOS) window.

2. Change to the directory where your template and data files are located.

3. Type the following syntax:

spDataLoader -<Flag> <TemplateFile> <DataFile> <MappedFile>

Each part of the syntax is explained in Table 12.

Table 12: spDataLoader command syntax

Name Description

SpDataLoader The executable program that loads the template. This file is located in the manuv62\scnams\bin directory on a client computer.

TemplateFile The filename of the template. It contains keywords that are mapped from the data file.

DataFile The filename of the file containing the keyword-mapped data.

MappedFile The filename of the file that holds the mapped template data. This file is the output file created by the Data Loader and can be imported into the database using the Data Import process.

Flag The flag defines the format of the file to be generated. Options:• m = creates a Make process import file.• r = creates a Rate import file, for example, Independent Demand.• gs = uses a generic template where the first line will be skipped, leaving one

header in the resulting mapped output file.• gns = uses a generic template where the header will not be skipped in the

resulting mapped output file.


Usage

Below are several examples of the Data Loader command using the example template names:

SpDataLoader -m stratmaketemplate.csv stratmakedata.csv

stratmakeimport.csv

SpDataLoader -gns stratlanetemplate.csv stratlanedata.csv

stratlaneimport.txt

SpDataLoader -r spSKUratetemplate.csv spSKUratedata.txt

The mapped file can have any name and extension you want, for example, .csv, .txt, .imp, and so on.

A generic template is any template that does not require data-specific processing by the Data Loader. All templates other than those using the -r and --m option are generic, as well as any templates you create for your use.

You can use the -gns flag instead of the -gs flag for generic templates, but you cannot specify -gs instead of -gns. When possible, you should use the -gs option rather than the -gns option because it will result in better Data Import performance.

Important: The -gns option must be used when you have a generic template with more than one Import object-type in it, that is, more than one line with parentheses enclosing an object-type.

Warning: When you are using the -gns and -m options, you should not select the "Always commit on new object type" setting from the Data Import Process Options dialog box. Disabling this option will improve the Data Import performance of files generated using the -gns and -m flags. The other generated import files do not need this option because they contain only one header row.

Chapter 4

Importing carrier cost data from NetWORKS Transport

This chapter describes the process for using the Data Import and Data Export processes to import carrier cost rates from NetWORKS Transport into NetWORKS Strategy.

Overview

You can use the Data Import and Data Export processes to import carrier rates from the NetWORKS Transport (Transportation Management) component into NetWORKS Strategy. The general process for importing carrier cost data is:

• In Transport, configure aliases for Strategy locations and the transportation types for which you will be requesting rates. See the Transport online help for information on configuring Transport.

• In Strategy, use the Export Resources for Transport process to export your transportation resources to a file on the Strategy client or server.

• Move the file to the Transport client computer (if different) and place it in the tm\bin directory.

• Use Transport to generate the rates, offset, and duration for your transportation resources.

• Transfer the file generated from Transport to the Strategy client or server (if different).

• In Strategy, use the Data Import process to import the data.

Exporting transportation resources from Strategy

This section describes the process for exporting your transportation resources from Strategy to a file that can be read by Transport. A copy of the Data Export process called Export Resources for Transport is available in Strategy. This process contains default options for exporting only transportation resources from Strategy. The default input file for this process is called strat_export_to_mtm.txt, which is formatted to export all of your transportation resources from Strategy. You can use this default file


or create your own file to export only selected transportation resources. To export resources, do the following:

1. If you are using a file other than the default input file, transfer your input file to the ..\manuv62\scnams\impexp directory (Windows) or ../manuv62/scnams/impexp directory (UNIX).

2. From the Strategy Explorer, double-click the Export Resources for Transport process.



b. In the Input file for export box, enter the name of your input file or click Browse to select the file from a location on your computer.

c. In the Export filename box, enter the name of the file that you want to contain your exported data.

4. Select the separator character used in your input file.

5. If you want to save your settings, click Apply.

6. Click OK to export your resources.

Your data will be exported to a file on your Strategy client or server computer, depending on the option you specified when you ran the process. If Transport is running on a different computer, you must transfer this file to a Transport client computer and import the file into Transport.

Generating cost data from Transport

You must transfer the file generated from Strategy to the Transport client computer (if different) and use it to generate cost data from Transport. Prior to generating the cost data, you must tag your Strategy locations with aliases to uniquely identify the location in Transport. You must also configure the Rate Provider. See the Transport online help for information on tagging locations and configuring the Rate Provider.

To generate cost data from Transport, you must do the following:


Importing carrier cost data from NetWORKS Transport 61

1. Copy the file you exported from Strategy to the tm\bin directory on a Transport client computer. Rename the file mtm.out.

2. At the command prompt, type the following:

scnrateprovider

3. Log onto the Rate Provider, giving a scenario ID that corresponds to a scenario configured for your Strategy data.

4. The Rate Provider will generate a file called scn.out. Errors will be logged to a file called srp.out. Review the srp.out file to ensure there are no problems with the data that was generated.

5. Copy or transfer the scn.out file to the Strategy client or server computer, in the directory ..\manuv62\scnams\impexp (Windows) or ../manuv62/scnams/impexp (UNIX).

6. Use the Data Import process to import the cost data into Strategy.

See “Running the Data Import process” on page 25 for information on running the Data Import process.

Note: By default, the process looks for the file in this location. Alternatively, you can specify the full path to the file and skip this step.

Chapter 5

Maintaining calendars

This chapter provides information about managing and administering calendar attributes in NetWORKS Strategy.

Introduction

Because time-phased attributes are an integral part of NetWORKS Strategy, the ability to administer calendars is important. The calendar maintenance utility provides a means of managing your Strategy calendar attributes.

Overview of the calendar utility

The calendar utility is a server-side-only utility; there is no user interface component. The utility operates only on the database or scenario specified. Changes are not propagated from one scenario to the live database, from the live database to the scenarios, or from scenario to scenario. The calendars to be manipulated are specified by object/attribute pairs in an input file.

The utility is invoked from the command line by typing:

manucalendarutils -o <operation> -d <database_name> -f<attribute_file> [parameters]

The options are shown in Table 13. Depending on the operation specified, additional parameters may be required.

Table 13: Parameters for manucalendarutils

Parameter Required? Description

-o <operation> X Specifies the operation to be performed. Choose from the following:P – Purge intervalsCI – Copy intervalsTR – Trim intervalsCO – Compress intervalsR – Roll interval datesRV – Roll interval dates and adjust the values


Filtering attributes with the -f parameter

You can specify the calendars to be examined by the utility. The attributes are specified in an input file containing object/attribute pairs. For example, you can select the calendars to be purged by specifying the object and attributes in a text file. See the chapter “Overview of NetWORKS Strategy objects” on page 77.

The calendar utility attribute file contains object names and attribute names. One attribute per line is expected. Comment lines can be added and are denoted with the

-d <database_name> X Name of the database to be updated.

-f <attribute_file> X Attribute file specifying the objects and attributes to be updated.

-c <model_calendar> Required when using the RV (roll interval dates and values) operation.

-e <effective_date> Required when using the P (purge interval) and CI (copy interval) operations.

-n <number_of_days>

Required when using the R (roll interval dates) operation.

-b <batch size> Transaction batch size is used to enhance performance of the update. This parameter should only be used when performance of the utility is of concern. The default is 3,000.

-force The program normally prompts you to confirm that it should be run. The -force parameter allows you to bypass the prompt in the event that the utility is run as a batch job.

-h <holiday file> Optional when using the RV (roll interval dates and values) operation.

-s <scenario> Name of the scenario to be used. Use to update calendars in a scenario other than the live scenario. If this parameter is not specified, the program updates data in the live scenario.

-Saturday Optional when using the RV (roll interval dates and values) operation.

-Sunday Optional when using the RV (roll interval dates and values) operation.

Table 13: Parameters for manucalendarutils (continued)

Parameter Required? Description

Maintaining calendars 65

“#” sign at the beginning of the line. A calendar utility attribute file is automatically installed in c:\manu\manuv62\scnams\resource\attribs.txt when you install Strategy. In order to use the file, you must edit the file and uncomment the appropriate lines. An example is provided below:

#File: attribs.txt#Each line is object name and attribute name separated by #aspace#Comment lines begin with #

# Make ProcessMakeProcess FixedCost

# Purchase ProcessPurchaseProcess FixedCostPurchaseProcess OverriddenUnitPrice

Purging intervals with the P operation

You can delete all of the time buckets that end before the effective purge date. The –e parameter specifies the effective date.

When purging the intervals from the database, the utility releases the persistent storage used by the intervals. The total size of the database will not decrease; however, the newly released space can be reused during future operations. To make the most effective use of this space, the ObjectStore utility, oscompact, should be run on the resultant database to remove fragmentation from the free space.

Consider the following calendar stored in the 1999 PlanningDB database:

The result of the following command:

manucalendarutils -d PlanningDB -o P -fc:\manu\manuv62\scnams\resource\attribs.txt -e 7/10/1999

Note: The time buckets in a calendar are non-inclusive with respect to the end date.

7/5-7/6 7/6-7/7 7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/1

11 12 13 14 14 0 0 77 140


would be as follows:

Copying intervals with the CI operation

You can duplicate the last interval in a calendar up to the effective end date. The -e parameter specifies the effective date. The utility removes the burden of manually creating additional intervals.

The duration of the newly created intervals will be based on the interval length of the last interval in the original calendar. The utility will attempt to determine what type of interval it is, such as a day, week, month, quarter, or year interval. The new interval lengths will reflect that type. For example, if the last interval in the original calendar is the month of February, incremental months will be added to the calendar up to the effective end date that you specify on the -e parameter. If the interval is not one of these types, the new intervals will have the exact duration as the last interval.



manucalendarutils -d PlanningDB -o CI -fc:\manu\manuv62\scnams\resource\attribs.txt -e 8/16/1999


Trimming intervals with the TR operation

You can eliminate leading or trailing time buckets that have a value of zero. The utility modifies the manner in which the calendar is stored in the database in order to save space. No change will be made to the calendar display in the Strategy userviews.

7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/1

0 0 77 140

7/5-7/6 7/6-7/7 7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/1

11 12 13 14 14 0 0 77 140

7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/1 8/1-8/14

0 0 77 140 140




manucalendarutils -d PlanningDB -o TR -fc:\manu\manuv62\scnams\resource\attribs.txt


Compressing intervals with the CO operation

You can compress consecutive time buckets in calendars that have empty values. The time buckets are replaced with one time bucket that represents the entire duration of the consecutive time buckets. The utility modifies the manner in which the calendar is stored in the database. However, no change will be made to the calendar display in the Strategy userviews.

Normal-slotted versus level-slotted calendars

A calendar can have one of two slotting types: normal or level. A normal-slotted calendar is a calendar in which the time bucket values are time-sensitive; the value of the time bucket is related to the length of the time bucket. The Independent Demand constraint is an example of a normal-slotted calendar, because the demand for an item is a function of the length of the time bucket.

A level-slotted calendar is a calendar in which the time bucket values are not time-sensitive; the value of the time bucket is independent of the length of the time bucket. The Unit Price of a SKU is slotted level, because the cost of a SKU is a per unit cost and does not increase if the size of the time bucket increases. All rate calendars in Strategy are level-slotted.

7/5-7/6 7/6-7/7 7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/1

0 0 13 14 14 0 0 0 0

7/7-7/8 7/8-7/9 7/9-7/10

13 14 14

Note: No change will be apparent in the Strategy userviews.


For calendars that use level slotting, the CO (compress intervals) operation will also combine adjacent time buckets that contain the same value. This is valid because the value of a time bucket for a level-slotted calendar does not change relative to the duration. For calendars that use normal slotting, adjacent intervals whose value is zero will be combined. The TR (trim intervals) operation can then be used to remove leading and trailing zeros.



manucalendarutils -d PlanningDB -o CO -fc:\manu\manuv62\scnams\resource\attribs.txt


For a calendar that uses normal slotting:

For a calendar that uses level slotting:

Rolling interval dates with the R operation

You can modify the dates of the calendar by shifting them based on an offset that you specify with the –n parameter. This offset determines the number of days to roll the calendar dates. The calendars can be shifted forward or backward; a positive offset moves the calendar forward, and a negative offset rolls the calendar backward.

7/5-7/6 7/6-7/7 7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/1

0 0 13 14 14 0 0 0 99

7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/19 7/19-8/1

13 14 14 0 99

Note: No change will be apparent in the Strategy userviews.

7/7-7/8 7/8-7/10 7/10-7/19 7/19-8/1

13 14 0 99


The values contained in the time buckets are not modified. The calendar maintains the same size and duration.

Consider a calendar containing seven daily buckets, a one-week bucket, and a two-week bucket in the 1999 PlanningDB database:


manucalendarutils -d PlanningDB -o R -fc:\manu\manuv62\scnams\resource\attribs.txt -n 10


Rolling interval dates and values with the RV operation

You can modify the dates of the calendar, shifting them to the future as determined by an input model calendar. The values contained in the time buckets are modified proportionally to the existing calendar. The new calendar will contain the same intervals as the model calendar, and the data from the existing calendar will be proportionally added to the new calendar.

The model calendar is specified using the –c parameter. The calendar must already exist in the database as a Named Calendar. The calendars can be created through the Strategy Calendars userview or through the Import/Export process.

You can specify that Saturday and/or Sunday is a weekend day (non-working day). Weekends are respected in the sense that time-bucket data will not allocate data for weekend days. The –Saturday and –Sunday parameters specify what weekend days are to be considered non-working days.

In addition, you can specify a list of holidays that will be respected. Holidays can be specified in an input file. The holiday file format is one numeric date (MM/DD/YYYY) per line. Comments are denoted with an initial # delimiter for each comment line.

7/5-7/6 7/6-7/7 7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/2

11 12 13 14 14 0 0 77 140

7/15-7/16 7/16-7/17 7/17-7/18 7/18-7/19 7/19-7/20 7/20-7/21 7/21-7/22 7/22-7/29 7/29-8/12

11 12 13 14 14 0 0 77 140


For example:

#These are the holidays#Christmas12/25/1999#Yom Kippur9/19/19999/20/1999

Dates not included in the model calendar, but in the existing calendar, will be removed, and dates in the model calendar, but not in the existing calendar, will be added. The data for any intervals added to the new calendar will be extrapolated from the existing calendar. The values to be used from the existing calendar will be determined by calculating the additional length of the model calendar and using the same duration from the end of the existing calendar.

The extrapolation of existing interval values is determined by the following rules:

• The values will be apportioned based on the average per working day of the existing calendar onto the working days of the model calendar.

• If the extrapolation of values requires a calendar that is larger than the existing calendar, the existing calendar will be extrapolated as far into the future as possible and the remaining values will be left blank.

Normal-slotted calendar example

Consider the normal-slotted calendar containing seven daily buckets, a one-week bucket, and a two-week bucket in the 1999 PlanningDB database:

Assume that the non-working days are:

And consider the model calendar, NewCal, containing seven daily buckets, a one-week bucket, and a two-week bucket:

7/5-7/6 7/6-7/7 7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/2

11 12 13 14 14 0 0 77 140

7/10/99 7/11/99 7/17/99 7/18/99 7/24/99

7/25/99 7/31/99 8/1/99 8/7/99 8/8/99

7/12-7/13 7/13-7/14 7/14-7/15 7/15-7/16 7/16-7/17 7/17-7/18 7/18-7/19 7/19-7/26 7/26-8/9



manucalendarutils -d PlanningDB -o RV -fc:\manu\manuv62\scnams\resource\attribs.txt -c NewCal-Saturday -Sunday -hc:\manu\manuv62\scnams\resource\holidays.txt


Details on Calculations

The formula for calculating the interval values for a normal-slotted calendar is:

(Value of the existing interval) / (Number of working days in the existing interval) * (Number of working days in the new interval)

Therefore, the calculation of the interval 7/12 – 7/13 is calculated by:

(Value of the interval 7/12 – 7/19) / (Number of working days in the interval 7/12 – 7/19) * (Number of working days in the interval 7/12 – 7/13)

= (77 / 5) * 1 = 15.4

The calculations for the intervals 7/13 – 7/14, 7/14 – 7/15, 7/15 – 7/16, and 7/16 – 7/17 are identical.

The intervals 7/17 – 7/18 and 7/18 – 7/19 both result in a value of zero because they are non-working days.

The interval 7/19 – 7/26 is calculated by:

(Value of the interval 7/19 – 8/2) / (Number of working days in the interval 7/19 – 8/2) * (Number of working days in the interval 7/19 – 7/26)

= (140 / 10) * 5 = 70

The interval 7/26 – 8/9 is calculated in two parts: 7/26 – 8/2 and 8/2 – 8/9. Data for the interval 7/26 – 8/2 is determined from the existing calendar, and data for the interval 8/2 – 8/9 is extrapolated from the existing data.

7/12-7/13 7/13-7/14 7/14-7/15 7/15-7/16 7/16-7/17 7/17-7/18 7/18-7/19 7/19-7/26 7/26-8/2

15.4 15.4 15.4 15.4 15.4 0 0 70 140



(Value of interval 7/19 – 8/2) / (Number of working days in the interval 7/19 – 8/2) * (Number of working days in the interval 7/26 – 8/2)

= (140 / 10) * 5 = 70

The dates covered by the interval 8/2 – 8/9 are extrapolated by counting the total number of days in the interval. The starting point in the existing calendar is determined by counting the number of days of data to be extrapolated from the end of the calendar. In this case, the starting date is 7/26.

The value is calculated by:

(Value of interval 7/19 – 8/2) / (Number of working days in the interval 7/19 – 8/2) * (Number of working days in the interval 8/2 – 8/9

= (140 / 10) * 5 = 70

The sum of the two values is 140.

Level-slotted calendar example

Consider the level-slotted calendar in the 1999 PlanningDB database:

Assume that the non-working days are:

Consider a model calendar, NewCal, containing seven daily buckets, a one-week bucket, and a two-week bucket:


manucalendarutils -d PlanningDB -o R -fc:\manu\manuv62\scnams\resource\attribs.txt -c NewCal

7/5-7/6 7/6-7/7 7/7-7/8 7/8-7/9 7/9-7/10 7/10-7/11 7/11-7/12 7/12-7/19 7/19-8/2

11 12 13 14 14 0 0 15 17

7/10/99 7/11/99 7/17/99 7/18/99 7/24/99

7/25/99 7/31/99 8/1/99 8/7/99 8/8/99

7/12-7/13 7/13-7/14 7/14-7/15 7/15-7/16 7/16-7/17 7/17-7/18 7/18-7/19 7/19-7/26 7/26-8/9


-Saturday -Sunday -hc:\manu\manuv62\scnams\resource\holidays.txt


Details on calculations

The formula for calculating the interval values for a level-slotted calendar is:

Sum of ((Value of the existing interval) *(Number of working days in the intersection of the existing interval and the new interval—for each interval in the existing calendar that overlaps with the new interval))

/ (Number of working days in the new interval)

For example, calculation of the interval 7/12 – 7/13 is calculated by:

(Value of the interval 7/12 – 7/19 * Number of working days contained in the overlap of the intervals 7/12 – 7/13 and 7/12 – 7/19) / (Number of working days in the interval 7/12 – 7/13)

= (15 * 1) / 1 = 15

The calculations for the intervals 7/13 – 7/14, 7/14 – 7/15, 7/15 – 7/16, and 7/16 – 7/17 are identical.

The intervals 7/17 – 7/18 and 7/18 – 7/19 result in a value of zero because they are non-working days.


(Value of the interval 7/26 – 8/2 * Number of working days contained in the overlap of the intervals 7/26 – 8/2 and 7/19 – 8/2) / (Number of working days in the interval 7/19 – 7/26)

= (17 * 5) / 5 = 17

The interval 7/26 – 8/9 is calculated in two parts: 7/26 - 8/2 and 8/2 – 8/9.

7/12-7/13 7/13-7/14 7/14-7/15 7/15-7/16 7/16-7/17 7/17-7/18 7/18-7/19 7/19-7/26 7/26-8/9

15 15 15 15 15 0 0 17 17



(Value of interval 7/19 – 8/2 * Number of working days contained in the overlap of the intervals 7/26 – 8/2 and 7/19 – 8/2) / (Number of working days in the interval 7/19 – 7/26)

= (17 * 5) / 5 = 17

The dates covered by the interval 8/2 – 8/9 are extrapolated by counting the total number of days in the interval. The starting point in the existing calendar is determined by counting number of days of data to be extrapolated from the end of the calendar. In this case, the starting date is 7/26. The interval 8/2 – 8/9 is calculated by:

(Value of interval 7/19 – 8/2 * Number of working days contained in the overlap of the intervals 7/26 – 8/2 and 7/19 – 8/2) / (Number of working days in the interval 7/19 – 7/26)

= (17 * 5) / 5 = 17

The weighted average of these two values is:

(17 * 5 + 17 * 5) / 10 = 17

Setting the transaction size with the -b parameter

Adjusting the transaction size can improve the performance of the calendar utility for large databases where the number of transactions can grow to be quite large. This hinders performance due to the overhead of committing a transaction. Therefore, increasing the size of each transaction with the -b parameter can improve the performance of the utility for large databases.

The batch size you specify with the -b parameter refers to the number of objects that have been examined by the utility. The batch size itself is not related to the actual number of database updates to be performed. The batch size is configurable, as the optimal transaction size will vary depending on the platform and the database size.

Part Two

Strategy database

objects

Chapter 6

Overview of NetWORKS Strategy objects

This chapter provides detailed information on the objects and attributes in NetWORKS Strategy. This information helps you understand how different attributes affect your supply chain model and how to set up input files for the Data Import, Data Export, or Delete Data processes.

Introduction

This chapter lists all object-types that apply to NetWORKS Strategy.

Each object is listed in a separate section. The sections are ordered alphabetically by object-type.

The beginning of each section contains the following information:

• The Strategy userview that can be used to view or manage the object and attributes

• Other objects that reference the object

• The dependencies the object has on other objects

For each type of object, all the attributes you can set in a Strategy userview, or using the Data Import process, are listed in a table. Each table contains the following information:

• Display name: The name of the attribute as it appears in the relevant userview.

• Import/export name: The name of the attribute as it appears when imported or exported. You must use this name in any input files for the Data Import, Data Export, or Delete Data processes. This name is not case-sensitive, but is presented in mixed-case for better readability.

• DS/MU name: The name of the attribute as it appears when you create a data selection or when you use the mass update feature.

• Data type: How the information is stored in the database. A list of relevant data types is given in the section “Data types for database attributes” on page 173.


• Valid values: Constraints on the values you can enter or import for this attribute, if any.

• Default: Any default values that will be used if you do not set a value for the attribute.

• Req?: Whether the attribute is required or not. If required, you must specify a value for the attribute when you create the object.

Attributes whose values are read-only are shaded in the attribute table. These attributes may often be assigned when the object is created, but the value may not be updated later. Some of these attribute values are generated by Manugistics processes (such as the Supply Chain Optimizer) and can never be updated in the userview or using the data import process.

Using objects and attributes to import and export data

This section gives some basic tips for using the object and attribute information in this chapter to import and export data. You should be aware of the following:

• All object and attribute names consist of a single word and should be entered as such in your input file. In some instances, attribute names may appear to be more than one word in the attribute table due to space limitations.

• See “Importing, exporting, and deleting data” on page 9 for information on setting up input files for import or export. Some objects and attributes require special formatting. In this case, information on special formatting requirements is given at the end of each object section under the heading Import/Export Notes.

• Many objects depend on other objects. For example, you cannot create a SKU at a location that does not yet exist—you must create the location first and then create the SKU. See the sections that follow for information on these specific dependencies.

Importing objects to respect dependencies

You should import Strategy objects in the following order:

• NamedCalendar

• TieredCostPrice

Note: Some objects and attributes are not visible in the applications. Information about these attributes is provided to allow you to delete or export them if necessary.

Overview of NetWORKS Strategy objects 79

• ServiceLevelSet

• spItem

• SourcingGroup

• spLocation

• Lane

• spSKU

• spReusableResource

• MakeProcess

• MoveProcess

• PurchaseProcess

• ResourceRequirement

• SKURequirement

Deleting objects to respect dependencies

If you delete multiple objects in an Strategy database, you would delete the objects in the following order to ensure dependencies do not prohibit an object from being deleted:


• MoveProcess

• PurchaseProcess

• MakeProcess

• SKURequirement (Deleted by MakeProcess, MoveProcess, or PurchaseProcess)


• spSKU

• Lane

• spLocation

• SourcingGroup

• spItem


• ServiceLevelSet

• TieredCostPrice

• NamedCalendar

Exporting objects to respect dependencies

If you want to export information from a database and intend to reimport it to another database, you should export objects in the following order so that the input file for the subsequent Data Import process honors dependencies in Strategy:

• NamedCalendar

• TieredCostPrice

• ServiceLevelSet

• spItem

• SourcingGroup

• spLocation

• Lane

• spSKU


• MakeProcess

• PurchaseProcess

• MoveProcess


• SKURequirement

Item (spItem) 81

Item (spItem) Strategy userview: Item or Strategy (User-defined Conversions are only visible in the Item userview)

Referenced in Strategy by: SKU

Item (spItem) attribute descriptions

An item is an individual product—a manufactured or purchased finished good, component, raw material, or work in process (WIP).

Name

Text name of this item. Once an item has been created, you cannot update the name.

Default Unit of Measure

This UOM will be automatically propagated to any SKUs created for this item.

Table 14: Item (spItem) attributes

Display name Import/export name

DS/MU name Data type Valid values Default Req?

Name (spItem) Name String X

Default Unit of Measure DefaultUofM Default UOM

UOM See “Data types for database attributes” on page 173.

X

Description Description Description String

Item Name (see Name)

Max Prebuild Periods PrebuildPeriods Maximum Prebuild Periods

Integer -1 (unlimited/off)

Storable IsStorable Is Storable Flag

Boolean True, False True

User-defined Conversions QtyConversion N/A QtyConversion


Description

Free-form text description of this item.

Item Name

See Name

Max Prebuild Periods

The number of periods in advance of the current period during which prebuild is allowed. Using a monthly calendar, a prebuild value of 2 will limit manufacture of an item to the month in which the demand for it occurs or up to 2 months prior. Setting a value of 0 limits manufacturing to the same period in which demand occurs. The default value is -1, which indicates that prebuild is unlimited/off.

Storable

Determines whether this item can be kept in inventory. If set to False, inventories for this item at all locations will be kept at 0.

User-defined Conversions

User-defined conversions between units of measure (UOMs) in different categories. While the System Administration application in Strategy allows you to manage item-independent conversions within categories, this attribute defines item-dependent conversions between UOMs from different categories (for example, Solid Measure and Liquid Measure). Only one conversion between categories is recognized. For example, the conversion Gallons 8 Pounds implies that 1 Quart equals 2 Pounds and 1 Ton is 250 Gallons.

Conversions are not transitive between categories. Even though the conversions Gallons 8 Pounds and Dozen 2 Gallons are defined, the conversion Dozen 16 Pounds must still be made explicitly to be recognized as valid.

Import/export notes• Because the Item object exists in both NetWORKS Scheduling and Strategy, the

object name spItem is used in all Data Import and Data Export input and output

Note: When specifying the QtyConversion attribute in your input file for Data Import, all UOMs must be singular (for example, Gallon instead of Gallons. In addition, you must use double quotes around the UOM if it is more than one word. See Notes on data types on page 82.

Item (spItem) 83

files to denote the Strategy Item object. You cannot use the Item to denote the item object in any input files used in the Data Import, Data Export, or Delete Data processes.

• If you use Data Import to update the user-defined conversions (QtyConversion) for an item, you will overwrite all the existing user-defined conversions for that item. If you want to keep existing user-defined conversions, you must respecify them in your input file when you update the QtyConversion attribute.

• To define more than one user-defined conversion for an item, specify the conversions in tuples without a separator character. To specify a unit of measure that is more than one word, use quotes around the unit of measure. For example:

(spitem), defaultuofm, qtyconversion101001, pound, gallon 4 pound "square centimeter" 5 pound

You cannot specify more than one conversion between the same unit of measure categories (for example, you can specify only one conversion between a volume and weight UOM).

• If you want to clear all user-defined conversion values for an item, you would use the format:

(spitem),qtyconversion101001,,


Lane Strategy userview: Strategy

Referenced by: Reusable Resources (spReusableResource)

Table 15: Lane attributes

Display name Import/export name DS/MU name Data type Valid values Default Req?

Name (Lane) Name String X

Default Currency Unit of Measure

DefaultCurrencyUofM Default Currency UOM

UOM Any UOM enabled in the Currency category

USD

Default Lane DefaultLane Default Lane Boolean True, False False


Destination Location

DestLocation Destination Location

String Name of an existing location

X

ImplicitlyConnectNow Boolean True, False

Implicitly Connect SKUs

Implicitly ConnectSkus


Boolean True, False False

Lane Label Label String X

Maximum Capacity MaxCapacity Thruflow Constraints, Maximum, Amount

QtyCalendar

Maximum Capacity Enabled

MaxCapacity Status Thruflow Constraints, Maximum, Status

List of values Soft, Hard, Off Off

Minimum Capacity MinCapacity Thruflow Constraints, Minimum, Amount

QtyCalendar

Lane 85

Lane attribute descriptions

A lane is a connection between two locations. You create a move or purchase process between two SKUs after a lane between the two locations has been created.

Name

Name of lane. The format of a lane name is:

<Sourcelocation> --> <Destlocation>_<label>

For example:

CHI->NY_Truck

Once a lane has been created, you cannot update the name.

Minimum Capacity Enabled

MinCapacity Status Thruflow Constraints, Minimum, Status

List of values Soft, Hard, Off Off

Overutilization Amount

MaxCapacity Unmet N/A QtyCalendar

Overutilization Penalty

Overutilization Penalty Thruflow Constraints, Maximum, Penalty

RateCalendar

Source Location SourceLocation Source Location

String Name of an existing location

X

Underutilization Amount

MinCapacity Unmet N/A QtyCalendar

Underutilization Penalty


Thruflow Constraints, Minimum, Penalty

RateCalendar

Table 15: Lane attributes (continued)



Default Currency Unit of Measure

Indicates the default currency to be used for this location. Costs of reusable resources created on this lane will default to this currency.

Default Lane

• True: This lane acts as the default lane. Any move or purchase processes created between the two locations connected by this lane will be associated with this lane by default. If multiple lanes between the same two locations exist, this attribute may be True for only one of them.

It is possible to create a move or purchase process that does not use a transportation resource (that is, a reusable resource on a lane). Such a process is associated with the default lane. The quantity of the item moved will count against the capacities of the lane.

• False: This lane is not the default.

Description

Free-form text description of this lane.

Destination Location

The location to which items are shipped on this lane. Once a lane has been created, this attribute cannot be updated.

ImplicitlyConnectNow

When specified in your input file during Data Import, this attribute functions like a command to achieve the effect of default connectivity by automatically creating move or purchase processes between the locations connected by this lane. See the definition for Implicitly Connect SKUs for more information about default connectivity.

Import/Export notes:

• Sourcing or purchase processes are only created automatically via Data Import if you set the ImplicitlyConnectNow attribute to True in addition to setting both the DefaultLane and ImplicitlyConnectSKUs attributes to True. Otherwise the ImplicitlyConnectNow attribute has no effect.

• You can set this attribute to True when you create the lane, or you can set it at a later time. Each time the attribute is set to True in your input file, the Data Import process determines whether or not objects need to be created given the current state of the data.

Lane 87


This attribute controls default connectivity—the automatic creation of move or purchase processes between the locations connected by this lane. The existence of a move or purchase process allows the Optimizer to consider moving SKUs referenced by the move or purchase processes from one location to the other.

Values for this attribute are:

• True

When a lane has the Default Lane and Implicitly Connect SKUs attributes set to True, Strategy will look for common SKUs (SKUs with the same item) at the two locations and connect them to each other via move or purchase processes.

If the Default Lane attribute is also True, Strategy automatically creates move or purchase processes across this lane in the following situations:

> When the lane is created. In this setting, Strategy creates a move or purchase process for each pair of SKUs with the same item existing at both the source and destination location. An input and output SKU Requirement is also created. The draw and yield quantity for the SKU Requirements on the process is set to be time-independent and to be one of the default UOMs of the SKU.

> When a new SKU is created at either location referenced by the lane. In this situation, if a SKU with the same item exists at the connected location, Strategy creates a move or purchase process that allows the SKU to move across the lane. An input and output SKU Requirement is created as in the preceding bullet. In addition, Resource Requirements for any reusable resources on the lane are connected to the move or purchase process, as described in the bullet that follows.

> When a reusable resource is created on the lane. In this situation, Strategy will add a Resource Requirement for the Reusable Resource to all move and purchase processes that move across this lane. The draw quantity will be set to be time-independent and to be the same as the draw quantity of the input SKU requirement.

Strategy creates a purchase process if the source location is a supplier or the destination location is a customer. Otherwise, it creates a move process.

Note: SKUs and lanes are not associated with one another. Move and Purchase processes move SKUs across a lane.


• False

Default connectivity is off. This is the default setting.

Import/Export note: If you set the ImplicitlyConnectSKUs attribute to True using the Data Import process, the Default Lane attribute and the ImplicitlyConnectNow attributes must both be set to True in order for the default connections to be made.

Lane Label

If there are multiple lanes from this source to this destination, assign labels to the lanes to identify them uniquely.

Once a lane has been created, this attribute cannot be updated.

Maximum Capacity

Maximum quantity that can be transported over this lane in any time period by all move and purchase processes on this lane. The quantity should be expressed in terms of measurement of the lane capacity. Strategy uses this constraint if the value in Maximum Capacity Enabled is Soft or Hard. This constraint is independent of any transportation resource on the lane.


Determines whether the Maximum Capacity constraint is enabled when you run the Supply Chain Optimizer.

• Off: The Optimizer does not constrain on Maximum Capacity.

• Soft: The constraint has a penalty cost. The Optimizer may violate the Maximum Capacity constraint and incur the penalty cost in order to achieve a feasible optimal plan.

• Hard: The Optimizer constrains on Maximum Capacity and will not violate the constraint.

Minimum Capacity

Places a minimum constraint on the total capacity in each period for all move and/or purchase processes using this lane. This constraint is independent of any transportation resource on the lane. The quantity should be expressed in terms of measurement of the lane capacity.

Lane 89


Determines whether this constraint is enabled when you run the Supply Chain Optimizer.

• Off: The Optimizer does not constrain on Minimum Capacity.

• Soft: The constraint has a penalty cost. The SC Optimizer may violate the Minimum Capacity constraint and incur the penalty cost in order to achieve a feasible optimal plan.

• Hard: The Optimizer constrains on Minimum Capacity and will not violate the constraint.


The amount by which the actual capacity used on the lane exceeds the amount specified in the Maximum Capacity constraint. The Supply Chain Optimizer outputs this value and you cannot change it.


The penalty cost that will be assessed for violating the Maximum Capacity constraint. Numerator units must be in a currency UOM.

Source Location

The location from which items are shipped on this lane. Once a lane has been created, this attribute cannot be updated.

Underutilization Amount

The amount by which the actual capacity used on the lane is under the amount specified in the Minimum Capacity constraint. The Supply Chain Optimizer outputs this value and you cannot change it.


The penalty cost that will be assessed for violating the Minimum Capacity constraint. Numerator units must be in or convertible to a currency UOM.

Import/export notes• Importing Lanes and their associated Resources can be simplified using the Data

Loader. See the section “Using the Data Loader to import data” on page 43 for more information.


• Sourcing or purchase processes are only created automatically via Data Import if you set the ImplicitlyConnectNow attribute to True after setting both the DefaultLane and ImplicitlyConnectSKUs attributes to True. Otherwise the ImplicitlyConnectNow attribute has no effect.

• You can set the ImplicitlyConnectNow attribute to True when you create the lane, or you can set it at a later time. Each time the attribute is set to True in your input file, the Data Import process determines whether or not objects need to be created given the current state of the data. For example, if your input file contained the following:

# create SKUs(spsku), item, locationcookies@ATL, cookies, ATLcookies@ESS, cookies, ESSbrownies@ATL, brownies, ATLbrownies@ESS, brownies, ESS# create lane between ATL and ESS(lane),sourcelocation,destlocation,label,defaultlane,implicitlyconnectSKUsATL->ESS_boat, ATL, ESS, boat, true, true

no default move or purchase processes would be created to move the cookies or brownies across the lane. However, if you formatted your file as follows:

# create SKUs(spsku), item, locationcookies@ATL, cookies, ATLcookies@ESS, cookies, ESSbrownies@ATL, brownies, ATLbrownies@ESS, brownies, ESS# create lane between ATL and ESS(lane),sourcelocation,destlocation,label,defaultlane,implicitlyconnectSKUs, implicitlyconnectnowATL->ESS_boat, ATL, ESS, boat, true, true, true

Strategy would create move processes (if ATL and ESS were both DCs or plants) or purchase processes (If ATL were a supplier or ESS were a customer).

Another example of an input file is:

# create SKUs(spsku), item, locationcookies@ATL, cookies, ATLcookies@ESS, cookies, ESSbrownies@ATL, brownies, ATLbrownies@ESS, brownies, ESS# create lane between ATL and ESS

Lane 91

(lane),sourcelocation,destlocation,label,defaultlane,implicitlyconnectSKUsATL->ESS_boat, ATL, ESS, boat, true, true# create reusable resource on the lane(spreusableresource), resloc, resourcetypetransportation_@ATL->ESS_boat, ATL->ESS_boat, transportation(lane), implicitlyconnectnowATL->ESS_boat, true

The preceding input file would create the SKUs, lane, and resources, then create move or purchase processes to move the SKUs across the lane. It would also create a resource requirement for the transportation resource and attach it to the move or purchase processes.


Location (spLocation) Strategy userview: Location or Strategy

Referenced in Strategy by: Lane, Reusable Resource (spReusableResource), SKU (spSKU).

Table 16: Location (spLocation) attributes


Name (spLocation) Name String X

Cost of Capital costofcapital costofcapital Rate Calendar

Percent/Year 0

Default Currency UOM

DefaultCurrency UofM Default Currency UOM

UOM Any UOM enabled in the Currency category

USD


Entire Time Horizon

UseEntireTime Horizon

Use Entire Time Horizon


Fixed Costs FixedCost Fixed Cost Rate Calendar

0 Default Curr UOM/Years

Fixed Costs Enabled

FixedCostEnabled Fixed Cost Enabled

Boolean True (on), False (off)

False (off)

Include Destination

IncludeDestAsSource Include Dest as Source


Latitude Latitude Latitude Decimal 0

Location Code Code Code String

Location Type IsCustomerIsDCIsPlantIsSupplier

Is <Type> Location Flag

Boolean True, False X

Longitude Longitude Longitude Decimal 0

Location (spLocation) 93

Location attribute descriptions

A location defines a site that houses a collection of resources and/or SKUs. A location can also be the site for a make process.

Name

Text name of this location. You cannot change this value after the location has been created.

Cost of Capital

A rate that represents the cost of money, expressed in terms of a percent per year.

Default Currency UOM

Indicates the default currency to be used for this location.

Description

Free-form text description of this location.

Entire Time Horizon

When Max Sourcing is enabled, whether the same maximum sourcing restriction is used for the entire planning calendar.

Maximum Sources

MaxSources Max Sources Integer 1

Service Levels Achieved

ServiceLevels AchievedCal

N/A QtyCalendar

Service Levels Enabled

ServiceLevelsEnabled Service Levels Enabled

Boolean True, False

Service Levels Name

ServiceLevelSet Service Level Set

ServiceLevelSet

Sourcing Type sourcingtype sourcingtype Enumeration Off, Group, Local Off

Sourcing Group sourcinggroup sourcinggroup String

Table 16: Location (spLocation) attributes (continued)



• True: The same maximum number of sources is used for the entire planning calendar.

• False: The maximum number of sources can change during the planning calendar or be restricted to a period within it.

Fixed Costs

Indicates the fixed cost for this location, which (if enabled) will be used by the Cost Metrics calculation. A fixed cost is always assessed and is not based on utilization. This value must be expressed in units of currency per unit of time. This value is not used by the SC Optimizer process.

Fixed Costs Enabled

Determines whether the Strategy uses the Fixed Cost in its Cost Metrics calculation.

• Off (False): The Cost Metrics calculation ignores any Fixed Cost value. False is the value used in the Data Import and Data Export processes.

• On (True): The Cost Metrics calculation will use Fixed Costs when calculating the cost of your network. True is the value used in the Data Import and Data Export processes.

Include Destination

When Sourcing Type is Local or Group, if there is a make process for the SKU at this location (destination), determines if the location is considered as a possible source.

• True: Strategy considers this destination as a possible sourcing location, so it will consider make processes when calculating the number of sources for this destination.

• False: Strategy does not consider this location as a possible source, so it will not consider make processes when calculating the number of sources for this destination.

Latitude

Indicates the location’s latitude on the geographic map.

Location Code

Abbreviated text that you want to appear on the AccuMap to mark the location. When you have several plants and distribution centers, short Location Code abbreviations are easier to read than the full Location Name text.

Location (spLocation) 95

Location Type

The Location Type identifies the purpose of the location. Some types of locations have certain constraints, explained below.

• Supplier: Location of a vendor from which you purchase raw materials or components. A supplier can be the source location of a purchase process to a plant or DC. Supplier locations cannot also be another type of location. Once the type has been set to Supplier, it cannot be changed.

• Plant: Location at which SKUs are manufactured. SKUs that are input to, or output from, make processes must be at plant locations. A location may be both a plant and a DC, but plant locations cannot also be suppliers or customers. A plant can be the destination location of a purchase process from a supplier. It can also be the source or destination of a move process to/from a DC or another plant. Finally, it can be the source location of a purchase process to a customer.

• DC: A distribution center, to which SKUs may be transported from plants or other DCs, and from which SKUs may be transported to other DCs or customers. A location may be both a plant and a DC. A location may be both a DC and a plant, but DC locations cannot also be suppliers or customers.

• Customer: A location where a customer receives products from a location in your supply chain. Customer locations cannot also be another type of location. Once the type has been set to Customer, it cannot be changed. A customer can be the destination location of a purchase process from a plant or DC.

Longitude

Indicates the location’s longitude on the geographic map.

Maximum Sources

When Sourcing Type is set to Group or Local, the maximum number of locations from which the Optimizer can source a SKU.


Calculation of the actual percentage that is being delivered for all the SKUs at the location (considered as an aggregate). If both SKU-level and location-level service levels apply, the location service level takes precedence.

Note: All locations must have a location type. If you are migrating a database from an earlier version of Strategy, any locations that did not have a location type in the earlier version will be assigned a location type of Plant.



Determines whether service levels are enabled at the location level. If set to FALSE, service levels are disabled for this location.

Service Level Set

If service levels are enabled, this attribute indicates the name of the service level set that will be applied.

Sourcing Group

If Sourcing Type is set to Group, indicates the sourcing group for this location.

Sourcing Type

Defines the type of max sourcing to be used at this location. If set to Off, max sourcing is disabled for this location; if set to Local, max sourcing applies only to the location itself; if set to Group, max sourcing applies to all locations in the group. When you set a sourcing type to Group, you must also select the group for this location.

Import/export notes

Because the Location object exists in both NetWORKS Scheduling and Strategy, the object-type name spLocation is used in all Data Import and Data Export input and output files to denote the Strategy Location object. You cannot use the object-type Location for any input files used in the Data Import, Data Export, or Delete Data processes.

Note: Supplier locations cannot be assigned to sourcing groups because they do not have source.

MakeProcess 97

MakeProcessStrategy userview: Processes

Referenced in Strategy by: ResourceRequirement, SKURequirement

Table 17: MakeProcess attributes



Name (MakeProcess) Name String See explanation for Name below

X

Calculated Lead Time Display only 0

Executions Completed Outflow PlannedExecs

Outflow Planned Executions

Double Calendar

Executions Started - see Number of Executions

Fixed Costs FixedCost Fixed Cost Rate Calendar 0 USD/Year

Fixed Costs Enabled FixedCost Enabled Fixed Cost Enabled

Boolean True (On), False (Off)

False (Off)

Has Executions

Boolean True, False

Lead Time MinLeadTime Lead Time Duration 0 Days

Lead Time Enable LeadTime Enabled Lead Time Enabled

Boolean False (Off), True (On)

False (Off)

Number of Executions (Executions Started)

Planned Executions Planned Executions

DoubleCalendar

Output SKU SKU Output SKU String Name of an existing SKU

X

Process Label Label Label String X


MakeProcess attribute descriptions

Within the supply chain, a process represents a step that replenishes the inventory of a particular SKU (while usually consuming inventory of one or more other SKUs). Make Processes replenish a SKU by manufacturing it.

A Make Process combines zero or more input SKUs to produce one or more output SKUs. A make process must be at a plant.

Name

The system creates the process name, using the following format:

Make_<Label>--<Item>@<Location>

For example:

Make_1--Widget@NewYork

Calculated Lead Time

The duration of the process, determined by taking the maximum of the following:

• The lead time of the process

• The maximum of the sum of the lead time duration and offset of each resource requirement associated with the process.

You cannot edit or update this field.

Executions Completed

If lead time is enabled, a process may start in one period and end in another. This value represents the completed executions.

Executions Started

See Number of Executions. If a process has lead times enabled and one execution of the process lasts for more than half of a calendar time period, the number of executions at the beginning of the process will display as the Executions Started. In this case, the process will also have a value for Executions Completed.

Import/export note: This attribute is imported and exported as PlannedExecutions, whether it displays as Number of Executions or Executions Started.

MakeProcess 99

Fixed Costs

Indicates the fixed cost for this process, which (if enabled) will be used by the Cost Metrics calculation. A fixed cost is always assessed and is not based on utilization. This value must be expressed in units of currency per unit of time. This value is not used by the SC Optimizer.

Fixed Costs Enabled

Determines whether Strategy uses the Fixed Cost in its Cost Metrics calculation.


• On (True): The Cost Metrics calculation will use Fixed Costs when determining the cost of your network. True is the value used in the Data Import and Data Export processes.

Has Executions

This is a special attribute that allows you to create data selections to select processes that have executions. To select all make processes where the Number of Executions or Executions Completed has a value in any period, create your data selection such that Has Executions is True.

Lead Time

Indicates the duration of the lead time for this process, independent of the lead time duration and offsets of any resource requirements associated with the process.

Lead Time Enable

Determines whether Lead Times will be considered by the SC Optimizer. Values are:

• Off (False): The Optimizer ignores any Lead Time value. False is the value used in the Data Import and Data Export processes.

• On (True): The Optimizer will take lead times into consideration when optimizing your network. True is the value used in the Data Import and Data Export processes.

Number of executions (Executions Started)

The number of executions of this process. Each execution consumes capacity from resources, depletes onhand of input SKUs, and replenishes onhand of output SKUs in accordance with the specified draw/yield quantities. If you have run the Optimizer,


you will see amounts that reflect optimal recommendations for how many times the process should run.

If a process has lead times enabled and one execution of the process lasts for more than half of a calendar time period, the number of executions at the beginning of the process will display as the Executions Started and you will not see the Number of Executions displayed. In this case, the process will also have a value for Executions Completed.


Output SKU

Name of the SKU produced by this make process. The SKU must exist in the database before the process is created. You cannot change this value after the process has been created.

Process Label

If there is more than one make process for this output SKU, you must specify a label to identify this process uniquely. You cannot change this value after the process has been created.

Import/export notes• When you create a MakeProcess using the Data Import process, the program

automatically creates an output SKU requirement for the specified SKU. The program does not update the requirement attribute (quantity) of the SKURequirement. You can set the requirement attribute for the output SKURequirement and add additional input and output SKURequirements to the process by creating SKURequirement objects in your input file.

• Importing MakeProcesses and their associated SKURequirements and ResourceRequirements can be simplified using the Data Loader. See the section “Using the Data Loader to import data” on page 43 for more information.

• If you delete a MakeProcess, any SKURequirement and Resource Requirement objects associated with the process will also be deleted.

MoveProcess 101

MoveProcessStrategy userview: Processes or Strategy

Referenced in Strategy by: ResourceRequirement, SKURequirement

Table 18: MoveProcess attributes


Name (MoveProcess) Name String X


Display only N/A 0

Destination SKU DestSKU N/A String Name of an existing SKU

X


OutflowPlannedExecs


Double Calendar


Fixed Costs FixedCost Fixed Cost Rate Calendar 0 USD/Years

Fixed Costs Enabled



False (Off)

Has Executions Boolean True, False


Lead Time Enable LeadTimeEnabled Lead Time Enabled


False (Off)


Planned Executions

Planned Executions

QtyCalendar

Process Label Label Label String X


MoveProcess attribute descriptions

Within the supply chain, a process represents a step that replenishes the inventory of a particular SKU (while usually consuming inventory of one or more other SKUs). Move processes replenish a SKU by transporting it from one location to another. Resource costs are used to calculate the total cost of the process.

A move process moves one item to a different location. Thus it has one supplying SKU at the source location and one demanding SKU at the destination location.

Move processes and purchase processes may be referred to collectively as sourcing processes.

Name

The system generates the process name, using this format:

Move_<Label>--<Item>--<Location>-><Location>

For example:

Move_1--Widget--NewYork->Chicago


The duration of the process, determined by taking the maximum of the following:

• The lead time of the process

• The maximum of the sum of the lead time duration and offset of each resource requirement associated with the process.

You cannot edit or update this field.

Source SKU SourceSKU N/A String Name of an existing SKU

Tax/Tariff TaxTariffCost Tax/Tariff Cost Rate Calendar

Tax/Tariff Enabled

TaxTariffEnabled Tax/Tariff Enabled


False (Off)

Table 18: MoveProcess attributes (continued)


MoveProcess 103

Destination SKU

Name of the demanding SKU, at the destination location.

• The item associated with the Demanding SKU must be the same as the item associated with the Source SKU.

• The location associated with the Demanding SKU must be a DC or plant.


If lead time is enabled, a process may start in one period and end in another. This value represents the completed executions.

Executions Started

See Number of executions. If a process has lead times enabled and one execution of the process lasts for more than half of a calendar time period, the number of executions at the beginning of the process will display as the Executions Started. In this case, the process will also have a value for Executions Completed.


Fixed Costs

Indicates the fixed cost for this process, which (if enabled) will be used by the Cost Metrics calculation. A fixed cost is always assessed and is not based on utilization. This value must be expressed in units of currency per unit of time.

Fixed Costs Enabled




Has Executions

This is a special attribute that allows you to create data selections to select processes that have executions. To select all move processes where the Number of Executions or Executions Completed has a value in any period, create your data selection such that Has Executions is True.


Lead Time


Lead Time Enable

Determines whether the lead time will be considered by the SC Optimizer. Values are:



Number of executions (Executions Started)

The number of executions of this process. Each execution consumes capacity from resources, depletes onhand of input SKUs, and replenishes onhand of output SKUs in accordance with the specified draw/yield quantities. If you have not run the Supply Chain Optimizer on the model, this value will be 0. If you have run the Optimizer, you will see amounts that reflect optimal recommendations for how many times the process should run.



Process Label

If there is more than one move process for this source/destination combination, you must specify a label to identify this process uniquely.

Source SKU

Name of the supplying SKU, at the source location.

• The item associated with the Source SKU must be the same as the item associated with the Destination SKU.

• The location associated with the Source SKU must be a DC or plant.

MoveProcess 105

Tax/Tariff

Indicates the tax or tariff cost for each execution of this process. This value should be represented as units of currency per quantity UOM.

Tax/Tariff Enabled

Determines whether Strategy uses the Tax/Tariff Cost.

• Off (False): The Optimizer ignores any Tax/Tariff Cost value. False is the value used in the Data Import and Data Export processes.

• On (True): The Optimizer will use Tax/Tariff Costs when optimizing your network. True is the value used in the Data Import and Data Export processes.

Import/export notes• Importing MoveProcesses and their associated SKURequirements and

ResourceRequirements can be simplified using the Data Loader. See the section “Using the Data Loader to import data” on page 43 for more information.

• Once a move process has been created, you cannot update the source SKU, destination SKU, or label attributes of that process.

• When you create a move process using Data Import, the process automatically creates an input and output SKU requirement for the specified SKUs. The process does not create the requirement attribute for the SKU requirement; you must include the SKU requirement attribute in your input file or through the Process userview.

• If you delete a move process, any SKU requirements and resource requirements associated with the process will also be deleted.


NamedCalendar Strategy userview: Calendars (Reporting)

Referenced in Strategy by: None

Understanding Named Calendars

Calendars define time intervals (time buckets) used by the system to display time-phased data and to perform calculations on time-phased data. For example, you might want to display some data grouped by months and other data by weeks or days. Strategy uses Reporting Calendars, which determine the time buckets used for displaying data.

Reporting calendars define the time buckets in which time-phased data is displayed in spreadsheet format. For example, you might have daily, weekly, and monthly Reporting calendars. You might also have Reporting calendars with time buckets of unequal length.

When you open a userview that displays time-phased data in spreadsheet format, the system asks which display calendar to use. You select from a list of Reporting calendars.

When you run the Supply Chain Optimizer or the Cost Metrics Process, you must specify a reporting calendar to control the horizon and time buckets to consider.

Import/export notes

Reporting calendars can be created in the Calendars userview or by using the Data Import process. A reporting calendar consists of one or more intervals.

To create a Reporting calendar using the Data Import process, use the following format in your input file:

(NamedCalendar)[, description]<Calendar-name>, <description-text>,Cal,reporting,,<interval-start-date>, <interval-end-date>[,,<interval-start-date>, <interval-end-date>]

For example, to create a quarterly calendar called Quarterly, format your file as follows:

(NamedCalendar),description

NamedCalendar 107

Quarterly,quarterly display calendar for 1998,cal,reporting,,1/1/1999,4/1/1999,,4/1/1999,7/1/1999,,7/1/1999,10/01/1999,,10/1/1999,1/1/2000

• Once you create a calendar, you cannot change the name or type of the calendar.

• If you create a calendar using the Data Import process, your calendar start date will be assumed to be the start of your first interval and the calendar end date will be assumed to be the end of your last interval. You cannot create a calendar with no time intervals using Data Import, then create your time intervals in the Calendars userview. You must create the time intervals for the calendar when you create the calendar using the Data Import process. If your first interval does not start with a start date/time of MM/DD/YY 00:00:00, you will see a time zone shift message when you select the calendar in the Calendars userview.

• When specifying time intervals, the end date of one interval must be the same as the start date of the next period. All dates are assumed to be at 00:00 of that date, and the system assumes the date includes all time up to, but not including,

the end date. Thus, if you wanted to specify January 1st through March 31st and

April 1st through June 30th 1999, you would enter the start date of 01/01/1999 and an end date of 04/01/1999 for the first interval and a start date of 04/01/1999 and an end date of 07/01/1999 for the second interval.

• If you want to update only one existing interval for a calendar, you must respecify all existing intervals for the calendar. Otherwise, the existing intervals will be completely overwritten when you specify the update.

• You can use min_time and max_time to create calendars with starting and ending intervals that span the entire allowable time frame. See “Data types for database attributes” on page 173 for additional information.


PlanMetrics Strategy userview: Strategy

Referenced in Strategy by: None

PlanMetricsDetails attribute descriptions

Plan metrics is an alternative method to view the raw data used to display the Cost data in the Strategy userview. You can export this data using the Data Export process.

Category

Type of cost—Fixed Costs, Item Costs, Penalty Costs, and so forth.

Cost

The cost displayed in currency per unit of measure for the item.

GroupStringsVec

A group of strings that displays information about the item for which cost data is shown. You would specify a * to export all strings that make up this attribute (see Import/export notes that follow).

Import/export notes

PlanMetrics can only be exported; they cannot be imported or deleted. You must use a special, leveled format in your input file to export the PlanMetrics object, as follows:

Table 19: PlanMetrics attributes

Display name Import/Export name Data type

PlanMetrics

(PlanMetrics) string

PlanMetricsDetail (planmetricsdetail-detailvec)

Description Category string

<Scenario_Name> Cost QtyCalendar

GroupStringsVec List

PlanMetrics 109

(level), planmetrics,*1,*

Using the above format, your exported data would look similar to:

(level),PlanMetrics1, ,(level),planmetricsdetail-detailvec,category2,,Item Costs,cost,USD,,01/ 1/1998 0:00:00,01/ 1/1999 0:00:00,478.277554,groupstringsvec,To Chicago,ItemA,From Boston(level),planmetricsdetail-detailvec,category2,,Transportation Costs,cost,USD,,01/ 1/1998 0:00:00,01/ 1/1999 0:00:00,615.105735,groupstringsvec,Regular,LA->Chicago,Transportation,ItemA

110 NetWORKS Stategy Reference Manual

PurchaseProcess (Buy or Sell)Strategy userview: Processes or Strategy

Referenced in Strategy by: ResourceRequirement, SKURequirement.

Table 20: PurchaseProcess attributes



Name (PurchaseProcess) Name String X


Display only 0

Cost/Price Type CostPriceType Cost/Price Type

List of values Off, Local, Multitier (Tiered Cost/Price)

Local

Destination SKU DestSKU Destination SKU

String X


OutflowPlannedExecs


Double Calendar


Fixed Costs FixedCost Fixed Cost Rate Calendar

0 USD/Years

Fixed Costs Enabled



False (Off)

Has Executions

Boolean True, False


Lead Time Enable LeadTimeEnabled Lead Time Enabled

Boolean Off (False), On (True)

False (Off)

PurchaseProcess (Buy or Sell) 111

PurchaseProcess attribute descriptions

Within the supply chain, a process represents a step that replenishes the inventory of a particular SKU (while usually consuming inventory of one or more other SKUs). Purchase processes have an associated price, and they are used for two different purposes:

• Buying raw materials or components from suppliers

• Selling finished goods to customers

A purchase process moves one item to a different location. Thus it has one supplying SKU at the source location and one demanding SKU at the destination location.

Purchasing processes and move processes may be referred to collectively as sourcing processes.


PlannedExecutions Planned Executions

Double Calendar

Overridden Price (to sell) or Overridden Cost (to buy)

OverriddenUnitPrice

Overridden UnitPrice

Rate Calendar

Process Label Label Label String

Source SKU SourceSKU Source SKU String X

Tax/Tariff TaxTariffCost Tax Tariff Cost

Rate Calendar

Tax/Tariff Enable TaxTariffEnabled Tax Tariff Enabled


False (Off)

Tiered Cost/Price TieredCostPrice Tiered Cost/Price

String Name of an existing tiered cost/price

Table 20: PurchaseProcess attributes (continued)




Name

The system creates the process name, using one of the following formats.

If the source location is a supplier:

Buy_<label>--<Item>--<Location>-><Location>

For example:

Buy_1--Widget--NewYork->Chicago

If the destination location is a customer:

Sell_<label>--<Item>--<Location>-><Location>

For example:

Sell_1--Widget--Chicago->Dallas


The length of time the product should be delayed through the process. When lead time is enabled with a lead time duration of zero, Strategy will calculate the lead time based on the maximum of the process lead time duration and the derived lead time duration from the supplying resources. When lead time is disabled, the Strategy calculated lead time will be zero. You cannot edit or update this field.

Cost/Price Type

The cost/price type Strategy will use. The value here determines how the cost to buy or price to sell the SKU is calculated. How this setting is used depends on whether the purchase process is a Buy or Sell process.

For a Buy process:

Cost/Price Type Cost calculated using

Local Value of Overridden Cost (to buy) attribute

Multitier (Tiered Price/Cost)

Tiered Cost/Price associated with the process

Off • If the source SKU’s Cost/Price Type is Local, uses the source SKU’s Cost (to buy).

• If the source SKU’s Cost/Price Type is Multitier, uses the Tiered Cost/Price associated with the source SKU.

• If the source SKU’s Cost/Price Type is Off, there is no cost


For a Sell process:

Destination SKU

The demanding SKU at the destination location. You cannot change this value after a process has been created.

The item associated with the Destination SKU must be the same as the item associated with the Source SKU.


If Lead Time Enabled is True, a process may start in one period and end in another. This value represents the completed executions.

Executions Started

See Number of Executions. If a process has lead times enabled and one execution of the process lasts for more than half of a calendar time period, the number of

Cost/Price Type Price calculated using

Local Value of Overridden Price (to sell) attribute

Multitier (Tiered Price/Cost)

Tiered Cost/Price associated with the process

Off • If the destination SKU’s Cost/Price Type is Local, uses the destination SKU’s Price (to sell).

• If the destination SKU’s Cost/Price Type is Multitier, uses the Tiered Cost/Price associated with the destination SKU.

• If the destination SKU’s Cost/Price Type is Off, use the Cost/Price Type attribute of the Source SKU, as follows: > If the source SKU’s Cost/Price Type is Local, uses the source SKU’s Cost

(to buy).> If the source SKU’s Cost/Price Type is Multitier, uses the Tiered

Cost/Price associated with the source SKU.> If the source SKU’s Cost/Price Type is Off, there is no price

If the Source SKU location is: The Destination SKU location must be:

Supplier DC or Plant

DC or Plant Customer


executions at the beginning of the process will display as the Executions Started. In this case, the process will also have a value for Executions Completed.


Fixed Costs


Fixed Costs Enabled




Has Executions

This is a special attribute that allows you to create data selections to select processes that have executions. To select all purchase processes where the Number of Executions or Executions Completed has a value in any period, create your data selection such that Has Executions is True.

Lead Time


Lead Time Enable

Determines whether Lead Times will be considered by the SC Optimizer. Values are:





The number of executions of this process. Each execution consumes capacity from resources, depletes onhand of input SKUs, and replenishes onhand of output SKUs in accordance with the specified draw/yield quantities. If you have not run the Supply Chain Optimizer on the model, this value will be 0. If you have run the Optimizer, you will see amounts that reflect optimal recommendations for how many times the process should run.



Overridden Price (to sell) or Overridden Cost (to buy)

For a Sell process, the Overridden Price (to sell) is the price used when items are sold via execution of this process. For a Buy process, the Overridden Cost (to buy) is the cost used when items are purchased via execution of this process. This value overrides the cost or price set on the SKU.

Process Label

If there is more than one purchase process for this source/destination/item combination, you must specify a label to identify this process uniquely. You cannot change this value after a process has been created.

Source SKU

The supplying SKU at the source location. You cannot change this value after a process has been created.

The item associated with the Source SKU must be the same as the item associated with the Destination SKU.

If the Source SKU location is: The Destination SKU location must be:

Supplier DC or Plant

DC or Plant Customer


Tax/Tariff

Indicates the tax or tariff cost for each execution of this process. This value should be represented as units of currency per quantity UOM.

Tax/Tariff Enable

Determines whether Strategy uses the Tax/Tariff Cost.

• Off (False): The Optimizer ignores any Tax/Tariff Cost value. False is the value used in the Data Import and Data Export processes.

• On (True): The Optimizer will use Tax/Tariff Costs when optimizing your network. True is the value used in the Data Import and Data Export processes.

Tiered Cost/Price

Name of the Tiered Cost/Price object associated with this process. You can have several tiered costs/prices defined, but only one can be associated with the process at one time. See the section “Tiered Cost/Price” on page 164 for more information on the Tiered Cost/Price object.

Import/export notes• Importing Purchase Processes and their associated SKURequirements and

ResourceRequirements can be simplified using the Data Loader. See the section “Using the Data Loader to import data” on page 43 for more information.

• When you create a purchase process using Data Import, the process automatically creates an input and output SKU requirement for the process, using the specified SKUs. The process does not create the Requirement attribute for the SKU requirement; you must include the SKU requirement as a separate object in your input file or through the Process userview.

• If you delete a purchase process, any SKU requirements and resource requirements associated with the process will be deleted at the same time.

ResourceRequirement 117

ResourceRequirementStrategy userview: Process

Referenced in Strategy by: MakeProcess, PurchaseProcess, MoveProcess, SKU.

ResourceRequirement attribute descriptions

Resource Requirements define:

• How much of a reusable resource is needed for one execution of a make, move, or purchase process

“Execution” is a conceptual term, not an attribute that is defined and stored in the database. Before defining resource requirements for a process, you must decide how much of the associated SKU is to be made or transported by one execution of the process—a single unit of the SKU, for example, or a whole batch or lot.

• When the use of the resource begins, in relation to the start of the process

• The duration of time for which the resource is required by the process

• A resource requirement is also used to associate a SKU with the storage resource that stores it.

Table 21: ResourceRequirement attributes


Name (ResourceRequirement) Name String See Name below

ReusableResource Reusable Resource

String The name of an existing reusable resource

X

Demander Demanding Supply Node

String Name of an existing process or SKU

X

Duration LeadTimeDuration Lead Time Duration

Duration 0 Days

Offset LeadtimeOffset Lead Time Offset

Duration 0 Days

Requirement Requirement Requirement Qty Calendar


Name

Name of resource requirement in the format reusableresource->demander. For example:

Production@Phil_SoupLine->Make--Soup@PhilStorage@Sacramento_Bulk->Make--Ingredients@Sacramento

Demander

Name of the process or SKU that draws on the resource.

For most reusable resources, the Demander is the process that places a requirement on this reusable resource. For example, a resource requirement might be set up as:

Reusable Resource: Oven1

Demander: Make Cookies

For storage resources, Demander is a SKU that is physically stored in the resource. For example:

Reusable Resource: Refrigerated Storage

Demander: Milk

If this storage resource and the item associated with this SKU have different units of measure, a conversion between those units of measure must be defined in Item:User-defined Quantity Conversion.

Reusable Resource

The resource associated with this requirement. This reusable resource must already exist in Strategy.

Duration

Specifies how long the process uses the resource for one execution of the process. This attribute is ignored for storage resources demanded by SKUs.

Offset

The amount of time by which resource utilization is offset from the start of an execution of the process. This attribute is ignored for storage resources demanded by SKUs.

Requirement

Time-phased quantity of this resource required for one execution of the process.

ResourceRequirement 119

For storage resources demanded by SKUs instead of by processes, the system ignores this value. Instead, utilization of the resource is determined by the onhand amounts of the associated SKU.

Import/export notes• Once a resource requirement has been created, you cannot update the name, the

reusable resource, or the demander of the requirement.

• If you delete a process, reusable resource, or SKU, all of its associated resource requirements are automatically deleted at the same time.


ReusableResource (spReusableResource)Strategy userview: Reusable Resources or Strategy

Referenced in Strategy by: ResourceRequirement

Table 22: ReusableResource (spReusableResource) attributes

Display name Import/export name DS/MU name Data type Valid

values Default Req?

Name (spReusable Resource)

Name String X

Actual utilization or Average Actual utilization

Utilization N/A QtyCalendar

Cost per UOM Cost Cost RateCalendar 0 USD/<Default UOM>

Costing/Pricing CostPriceType Cost/Price Type List of values Off, Local, Multitier (Tiered Cost/Price)

Local

Default Duration DefaultLT Duration Default Lead Time Duration

Duration 0 Days

Default Offset DefaultLTOffset Default Lead Time Offset

Duration 0 Days


DefaultUofM Default UOM UofM Valid UOM enabled in your system

X


Exceeds Any Max Constraint

Boolean True, False

Fixed Costs FixedCost Fixed Cost Rate Calendar 0 USD/Years

ReusableResource (spReusableResource) 121

Fixed Costs Enabled FixedCostEnabled Fixed Cost Enabled


False (Off)

Has Utilization Boolean True, False

Location/Lane ResLoc Location String Existing location or lane

X

Label Label Label String

Maximum Capacity MaxCapacity Thruflow Constraints, Maximum, Amount

QtyCalendar 0 <Default UOM>


MaxCapacity Status Thruflow Constraints, Maximum, Status

List of values Off, Soft, or Hard

Off

Minimum Capacity MinCapacity Thruflow Constraints, Minimum, Amount

QtyCalendar 0 <Default UOM>


MinCapacity Status Thruflow Constraints, Minimum, Status

List of values Off, Soft, or Hard

Off


MaxCapacity Unmet N/A QtyCalendar


OverUtilization Penalty

Thruflow Constraints, Maximum, Penalty

RateCalendar 0 USD/<Default UOM>

Resource Type ResType Resource Type List of values See description below

X

Table 22: ReusableResource (spReusableResource) attributes (continued)


values Default Req?


ReusableResource attribute descriptions

A resource such as a machine, labor, transportation that is drawn upon but not consumed when it is used. Reusable Resources can be grouped into the following categories, depending on their type.


String Name of an existing tiered price

Typesee Resource Type

Under Any Min Constraint

Boolean True, False

Underutilization amount

MinCapacity Unmet N/A QtyCalendar 0 USD/<Default UOM>


UnderUtilization Penalty

Thruflow Constraints, Minimum, Penalty

RateCalendar 0 <Default UOM>

Table 22: ReusableResource (spReusableResource) attributes (continued)


values Default Req?

Resource Type Exists atDemander (via Resource Requirement)

Definition

InhandlingLaborMachineryMaterial ConversionProductionOuthandling

Location • Make Process

• Move Process

• Purchase Process

Represents the cost and capacity of entities such as equipment or people used in the manufacturing or shipping of SKUs.


Name

The system creates a resource name in this format:

<Resource Type>@<Location>_<Label>

Examples:

Machinery@Suffolk_Oven1Transportation@Phil->Birm_Truck

You cannot change the name after a resource has been created.

TransportationExtraTransportation

Lane • Move Process

• Purchase Process

Represents the cost and capacity of the entity used for transporting SKUs from one location to another over a specific lane. The entity is usually a transportation alternative such as a parcel delivery service, trucking company, private fleet, air freight, barge, or ship. As such, the costs and capacities can be internal to the company or those of a third party.

Storage Location SKU (or Make Process when used has a holding tank)

Normally, represents the cost and capacity of the storage space needed to store associated SKUs based on their onhand levels. The key difference between this type of resource and the others is that its consumption must be expressed over some period of time. For example, 50 pallet positions for 1 week or 1,000 square feet of space for 1 month. When associated with a Make Process, this represents the cost and capacity of a storage entity such as a holding tank to store work in progress during the execution of the process.

Note: You cannot create reusable resources at supplier or customer locations.

Resource Type Exists atDemander (via Resource Requirement)

Definition


Actual Utilization

The actual utilization in each period of this resource. This value is output from the Supply Chain Optimizer.

Cost

Cost in each period per amount of resource used, in the following format:

Cost/Price Type (Costing/Pricing)

The costing/pricing type used by Strategy:

• Off: The Optimizer considers the resource to have no cost.

• Local: The Optimizer uses the local costing/pricing attribute for this object (Cost).

• Tiered Cost/Price: The Optimizer uses the selected tiered cost/price.

Default Duration

Value is used as a starting Lead Time Duration for all Resource Requirements for this Resource. When a Resource Requirement is created for this Resource, this value is copied to the ResourceRequirement:Duration attribute.

Default Offset

Value is used as a starting Lead Time Offset for all Resource Requirements for this Resource. When a Resource Requirement is created for this Resource, this value is copied to the ResourceRequirement:Offset attribute.


The unit of measure for this resource. Typically, transportation and storage resources are measured in terms of weight or volume; labor and machinery resources are typically measured in terms of time.

Description

Description of this resource.


This is a special attribute that allows you to create data selections to select reusable resources that exceed capacity. To select all reusable resources where the

Currency amountQuantity in or convertible to the default unit of measure for this resource----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


Overutilization Amount has a value in any period, create your data selection such that Exceeds Any Max Constraint is True.

Fixed Costs


Fixed Costs Enabled




Has Utilization

This is a special attribute that allows you to create data selections to select reusable resources that have utilization. To select all reusable resources where the Actual Utilization (or Average Actual Utilization) has a value in any period, create your data selection such that Has Utilization is True.

Label

If there is more than one resource of this type at this location or on this lane, you must specify a label to identify this resource uniquely. You cannot change this value after a resource has been created.

If you intend to transfer transportation rates into Strategy from NetWORKS Transport, you must use a label that corresponds to the Strategy resource name specified in the TM scenario configuration. See “Importing carrier cost data from NetWORKS Transport” on page 59 for additional information.

Location/Lane

The location associated with this resource. If this is a Transportation or Extra Transportation resource, specify a lane instead of a location. The location must already exist in the database before the resource is created. You cannot change this value after a resource has been created.


Maximum Capacity

Maximum capacity of this resource. The setting of Maximum Capacity Enabled determines the effect of this value when the Optimizer is run.


This attribute determines whether the Maximum Capacity constraint is enabled when you run the Supply Chain Optimizer. Values are:

• Off: The Optimizer does not constrain on Maximum Capacity.

• Soft: The constraint has a penalty cost. The Supply Chain Optimizer may violate the Maximum Capacity constraint and incur the penalty cost in order to achieve a feasible optimal plan.

• Hard: The Optimizer constrains on Maximum Capacity and will not violate the constraint.

Minimum Capacity

Minimum capacity of this resource that must be utilized without incurring a penalty cost.


Determines whether this constraint is enabled when you run the Supply Chain Optimizer. Values are:

• Off: The Optimizer does not constrain on Minimum Capacity.

• Soft: The constraint has a penalty cost. The Supply Chain Optimizer may violate the Minimum Capacity constraint and incur the penalty cost in order to achieve a feasible optimal plan.

• Hard: The Optimizer constrains on Minimum Capacity and will not violate the constraint.

Overutilization amount

The amount by which the actual utilization of this resource was over the Maximum Capacity constraint specified. This value is output by the Supply Chain Optimizer.

Overutilization penalty

The penalty cost incurred if the actual utilization is more than the amount specified in the Maximum Capacity constraint. Units must be in or convertible to currency/default UOM.


Resource label

See Label

Resource type

This value helps identify how this resource is used. You cannot change this value after a resource has been created.

Following is a list of the predefined resource types. Types given in parentheses are the types used for the Data Import and Data Export processes.

Tiered Cost/Price

Name of the tiered cost or price object associated with this resource. You can have several tiered costs/prices defined, but only one can be associated with the resource at one time. See the section “Tiered Cost/Price” on page 164 for more information on the Tiered Cost/Price object.

Type

See Resource Type


This is a special attribute that allows you to create data selections to select reusable resources that are under capacity. To select all reusable resources where the

Resource type Purpose Exists at

Machine Production (cost and capacity) Location

Production Production (cost and capacity) Location

Labor Labor (cost and capacity) Location

Material conversion (MaterialConversion) Material conversion (cost and capacity) Location

InHandling Capacity to handle incoming goods Location

OutHandling Capacity to handle outgoing goods Location

Transportation Ability to move goods Lane

Extra transportation (ExtraTransportation) Ability to move goods Lane

Storage Storage (cost and capacity) Location


Underutilization Amount has a value in any period, create your data selection such that Under Any Min Constraint is True.

Underutilization amount

The amount by which the actual utilization of this resource was under the Minimum Capacity constraint specified. This value is output by the Supply Chain Optimizer.

Underutilization penalty

The penalty cost incurred if the actual utilization is less than the amount specified in the Minimum Capacity constraint. Units must be in or convertible to Currency/Default UOM.

Import/export notes• Because the ReusableResource object exists in both NetWORKS Scheduling and

Strategy, the object-type name spReusableResource is used in all Data Import and Data Export input and output files to denote the Strategy ReusableResource object. You cannot use the object-type ReusableResource for any input files used in the Data Import, Data Export, or Delete Data processes.

• Importing many time-phased attributes, such as Maximum Capacity, Minimum Capacity, and so forth, can be simplified using the Data Loader. See the section “Using the Data Loader to import data” on page 43 for more information.

• You must specify a label if you have more than one resource of a particular type at a location or across a lane. If you intend to transfer transportation rates into Strategy from NetWORKS Transport, you must use a label that has been configured to correspond to a transportation mode in Transport. See “Importing carrier cost data from NetWORKS Transport” on page 59 for additional information.

• Valid resource types are:

Transportation types

ExtraTransportationa

Inhandling

Labor

Machinery

Material Conversion


• If you delete a reusable resource, you will also delete all of the resource requirements that draw on the resource.

• Because the under, over, and actual utilization amounts are output by the Supply Chain Optimizer, you cannot update those attributes.

OutHandling

Production

Transportation

Storage

a.Note that there is no space in ExtraTransportation.

Transportation types

Service Levels 131

Service LevelsStrategy userview: Service Level

Referenced in Strategy by: Location, SKU

Service Level attribute descriptions

Service levels describe how quickly products must be shipped to customers. The Service Level object defines these constraints as a certain percentage of product that must be shipped within the specified amount of time. When service levels are enabled, Strategy determines if the defined constraints are feasible, and if they are, develops a plan that minimizes cost or maximizes profit while respecting the service level constraint.

Service levels can be defined as either the percentage of revenue or the percentage of product volume that must be shipped within a specified time period. Service levels can be applied to individual SKUs or to locations (effectively, all customer SKUs for the specified location).

A service level set consists of multiple service levels that apply to the same SKU or location. Each service level set contains multiple pairs of lead times and service

Table 23: Service Levels attributes



Service Level Set

Name (ServiceLevelSet) Name string X

Service Levels ServiceLevels Service Levels ServiceLevel

Service Level

Lead Time Requirement (min.)

LeadTimeReq Lead Time Requirement (min.)

Duration greater than or equal to 0

0

Service Percentage (%)

ServicePercentage Service Percentage (%)

Decimal 0.000 - 100


percentages. For example, the following table shows two levels of service--50% must be shipped within the one day and 90% must be shipped within three days.

The same Service Level object can be referenced by multiple objects. For example, a SKU and a location could both reference the same Service Level.

Lead Time Requirement (min.)

Number of minutes in which the specified service percentage must be met. For example, a value of 1440 indicates that the service percentage must be achieved in one day.

Service Percentage (%)

The percentage of product, calculated in terms of the specified measure (revenue or volume), that must be shipped within the specified lead time. This value cannot exceed 100 percent.

Service Level Set attribute descriptions

Service level sets are collections of service levels. Each service level set can have multiple pairs of lead time requirements and service percentages defined.

Name

Text name of the service level set.

Service Levels

Service levels contained in the set.

Import/export notes

Special formatting is required to import or export this object. See the sections that follow for specific instructions.

Lead Time Requirement (min.) Service Percentage (%)

4320 90

1440 50

Service Levels 133

Importing Service Level objects

To import a service level object, you must use a special, leveled format, as follows:

(level),ServiceLevelSet, <attribute_name>, . . .1,<ServiceLevelSet_name>

The following input creates a service level set, SLPreferred, containing three service levels (the header row breaks in this example due to its length):

(level),ServiceLevelSet

1,SLPreferred

(level),servicelevel-servicelevels,leadtimereq,servicepercentage

2,Service Level,1440,65





Exporting Service Level objects

To export service level objects, you must use the following format:

(level),ServiceLevelSet, <attribute_name>, . . .1,<ServiceLevelSet_name>

To export all service level objects and their associated attributes, use the following format:

(level),ServiceLevelSet,*

1,*

Information related to service levels appears in more than one part of your export output file. For example, the following output would occur when exporting a service level set named SL1 containing two service levels. The first level defines a lead-time requirement of one day and a service percentage of 50%. The second level defines a a lead-time requirement of two days and a service percentage of 70%. The export output file would contain information about the service level set itself as shown below (some rows break in this example due to their length):

(level),ServiceLevelSet


1,SL1





In addition, the export output file would also contain service level data associated with the SKUs or locations to which the service levels apply. This data indicates the name of the service level set and the service level achieved. The following example shows SKU-level output (some rows break in this example due to their length):

(level),spSKU,costpricetype,description,includedestassource,independentdemandstatus,item,location,maxdemandstatus,maxinflowstatus,maxohstatus,maxoutflowstatus,maxsources,mininflowstatus,minoutflowstatus,needsdemandforecast,safetystockstatus,servicelevelsenabled,servicelevelset,sourcegroup,sourcingtype,targetohstatus,tieredcostprice,useentiretimehorizon

1,ItemA@Cust1,Local,,false,Soft,ItemA,Cust1,Hard,Off,Off,Off,1,Off,Off,false,Off,true,SL1,,OFF,Off,,true

,demandmet,Kilogram

,,01/ 1/2001 0:00:00,01/ 8/2001 0:00:00,200.000000

,,01/ 8/2001 0:00:00,01/15/2001 0:00:00,200.000000

,,01/15/2001 0:00:00,01/22/2001 0:00:00,200.000000

,,01/22/2001 0:00:00,01/29/2001 0:00:00,200.000000

,,01/29/2001 0:00:00,02/ 5/2001 0:00:00,200.000000

,,02/ 5/2001 0:00:00,02/12/2001 0:00:00,200.000000

,,02/12/2001 0:00:00,02/19/2001 0:00:00,200.000000

,,02/19/2001 0:00:00,02/26/2001 0:00:00,200.000000

,independentdemand,Kilogram

,,01/ 1/2001 0:00:00,01/ 8/2001 0:00:00,200.000000

,,01/ 8/2001 0:00:00,01/15/2001 0:00:00,200.000000

,,01/15/2001 0:00:00,01/22/2001 0:00:00,200.000000

,,01/22/2001 0:00:00,01/29/2001 0:00:00,200.000000

,,01/29/2001 0:00:00,02/ 5/2001 0:00:00,200.000000

,,02/ 5/2001 0:00:00,02/12/2001 0:00:00,200.000000

Service Levels 135

,,02/12/2001 0:00:00,02/19/2001 0:00:00,200.000000

,,02/19/2001 0:00:00,02/26/2001 0:00:00,200.000000

,independentdemandpenalty,USD,Kilogram

,,MIN_TIME,MAX_TIME,10.000000

,independentdemandunmet,Kilogram

,maxdemand,Kilogram

,,01/ 1/2001 0:00:00,01/ 8/2001 0:00:00,500.000000

,,01/ 8/2001 0:00:00,01/15/2001 0:00:00,500.000000

,,01/15/2001 0:00:00,01/22/2001 0:00:00,500.000000

,,01/22/2001 0:00:00,01/29/2001 0:00:00,500.000000

,,01/29/2001 0:00:00,02/ 5/2001 0:00:00,500.000000

,,02/ 5/2001 0:00:00,02/12/2001 0:00:00,500.000000

,,02/12/2001 0:00:00,02/19/2001 0:00:00,500.000000

,,02/19/2001 0:00:00,02/26/2001 0:00:00,500.000000

,maxdemandpenalty,USD,Kilogram

,maxdemandunmet,Kilogram

,maxinflow,Kilogram

,maxinflowpenalty,USD,Kilogram

,maxinflowunmet,Kilogram

,maxoh,Kilogram

,maxohpenalty,USD,Kilogram

,maxohunmet,Kilogram

,maxoutflow,Kilogram

,maxoutflowpenalty,USD,Kilogram

,maxoutflowunmet,Kilogram

,mininflow,Kilogram

,mininflowpenalty,USD,Kilogram

,mininflowunmet,Kilogram

,minoutflow,Kilogram

,minoutflowpenalty,USD,Kilogram

,minoutflowunmet,Kilogram

,optimaloh,Kilogram


,optimaloh,Kilogram

,price,USD,Kilogram


,safetystock,Kilogram

,safetystockpenalty,USD,Kilogram

,safetystockunmet,Kilogram

,scninitialoh,Kilogram

,standardcost,USD,Kilogram

,targetoh,Kilogram

,targetohpenalty,USD,Kilogram

,targetohunmet,Kilogram

(level),qtycalendar-servicelevelsachievedcals,defaultuom,end,start

2,Quantity Calendar,Percent,02/26/2001 0:00:00,01/ 1/20010:00:00

(level),qtyinterval-list,duration,end,quantity,start

3,Quantity Interval,10080,01/ 8/2001 0:00:00,50.000000Percent,01/ 1/2001 0:00:00


3,Quantity Interval,10080,01/15/2001 0:00:00,50.000000Percent,01/ 8/2001 0:00:00


3,Quantity Interval,10080,01/22/2001 0:00:00,50.000000Percent,01/15/2001 0:00:00




3,Quantity Interval,10080,02/ 5/2001 0:00:00,50.000000Percent,01/29/2001 0:00:00




Service Levels 137




(level),qtycalendar-servicelevelsachievedcals,defaultuom,end,start

2,Quantity Calendar,Percent,02/26/2001 0:00:00,01/ 1/20010:00:00


3,Quantity Interval,10080,01/ 8/2001 0:00:00,100.000000Percent,01/ 1/2001 0:00:00








3,Quantity Interval,10080,02/ 5/2001 0:00:00,75.000000Percent,01/29/2001 0:00:00








SKU (spSKU) Strategy userview: SKU

Referenced in Strategy by: MakeProcess, PurchaseProcess, ResourceRequirement, SKURequirement, MoveProcess.

Table 24: SKU (spSKU) attributes

Display name Internal name DS/MU name Data type Valid values Default Req?

Name (spSKU) Name String X

Cost (to buy) or Price (to sell)

Price Unit Price Rate Calendar

0 USD/<default UOM>

Cost/Price Type (Costing/Pricing)

CostPriceType Cost/Price Type List of values

Off, Local, Multitier (Tiered Cost/Price)

Local


Display only N/A


Entire Time Horizon UseEntireTime Horizon



Exceeds any Max Constraint

Boolean True, False

Has Met Demand

Boolean True, False

Has Unmet Demand

Boolean True, False

Include Destination IncludeDestAs Source

Include Dest as Source


Independent Demand

Independent Demand

Independent Demand Constraint, Minimum, Amount

QtyCalendar 0 <default UOM>

SKU (spSKU) 139

Independent Demand Enabled

Independent DemandStatus

Independent Demand Constraint, Minimum, Status

List of values

Off, Soft, Hard Off

Independent Demand Penalty

Independent DemandPenalty

Independent Demand Constraint, Minimum, Penalty

Rate Calendar

0 USD/<default UOM>

Independent Demand Unmet Amount

Independent DemandUnmet

N/A QtyCalendar

Storage Resource Display only

Item Item Item String Name of an existing Item

X

Location Location Location String Name of an existing location

X

Location Restricted Read only N/A Boolean True, False

Manufactured Display only Boolean False

Maximum Demand MaxDemand Independent Demand Constraint, Maximum, Amount


Maximum Demand Enabled

MaxDemand Status

Independent Demand Constraint, Maximum, Status

List of values

Off, Soft, Hard Off

Maximum Demand Penalty

MaxDemand Penalty

Independent Demand Constraint, Maximum, Penalty

Rate Calendar

0 USD/<default UOM>

Table 24: SKU (spSKU) attributes (continued)



Maximum Demand Unmet Amount

MaxDemand Unmet

N/A QtyCalendar

Maximum Inflow Amount

MaxInflow Inflow Constraints, Maximum, Amount


Maximum Inflow Penalty

MaxInflow Penalty

Inflow Constraints, Maximum, Penalty

Rate Calendar

0 USD/<default UOM>

Maximum Inflow Enabled

MaxInflow Status

Inflow Constraints, Maximum, Status

List of values

Off, Soft, Hard Off

Maximum Inflow Unmet Amount

MaxInflowUnmet

N/A QtyCalendar

Maximum Onhand MaxOH Thruflow Constraints, Maximum, Amount


Maximum Onhand Enabled

MaxOHStatus Thruflow Constraints, Maximum, Status

List of values

Off, Soft, Hard Off

Maximum Onhand Penalty (per day)

MaxOHPenalty Thruflow Constraints, Maximum, Penalty

Rate Calendar

0 USD/<default UOM>

Maximum Onhand Unmet Amount

MaxOHUnmet N/A QtyCalendar

Maximum Outflow Amount

MaxOutflow Outflow Constraints, Maximum, Amount




SKU (spSKU) 141

Maximum Outflow Enabled

MaxOutflow Status

Outflow Constraints, Maximum, Status

List of values

Off, Soft, Hard Off

Maximum Outflow Penalty

MaxOutflow Penalty

Outflow Constraints, Maximum, Penalty

Rate Calendar

0 USD/<default UOM>

Maximum Outflow Unmet Amount

MaxOutflowUnmet

N/A QtyCalendar

Met Demand Amount

DemandMet N/A QtyCalendar

Maximum Sources MaxSources Max Sources Integer 1

Minimum Inflow Amount

MinInflow Inflow Constraints, Minimum, Amount


Minimum Inflow Enabled

MinInflowStatus Inflow Constraints, Minimum, Status

List of values

Off, Soft, Hard Off

Minimum Inflow Penalty

MinInflow Penalty

Inflow Constraints, Minimum, Penalty

Rate Calendar

0 USD/<default UOM>

Minimum Inflow Unmet Amount

MinInflow Unmet

N/A QtyCalendar

Minimum Outflow Amount

MinOutflow Outflow Constraints, Minimum, Amount


Minimum Outflow Enabled

MinOutflowStatus

Outflow Constraints, Minimum, Status

List of values

Off, Soft, Hard Off




Minimum Outflow Penalty

MinOutflow Penalty

Outflow Constraints, Minimum, Penalty

Rate Calendar

0 USD/<default UOM>

Minimum Outflow Unmet Amount

MinOutflow Unmet

N/A QtyCalendar

Needs Demand Forecast

NeedsDemand Forecast



Optimal Onhand OptimalOH N/A QtyCalendar

Price (to sell) or Cost (to buy)

Price Unit Price Rate Calendar

0 USD/<default UOM>

Raw Material (Display only) Boolean False

Safety Stock SafetyStock Thruflow constraints, Minimum, Amount


Safety Stock Enabled

SafetyStock Status

Thruflow constraints, Minimum, Status

List of values

Off, Soft, Hard Off

Safety Stock Penalty (per day)

SafetyStock Penalty

Thruflow constraints, Minimum, Penalty

Rate Calendar

0 USD/<default UOM>



N/A QtyCalendar


ServiceLevels Enabled


Boolean True, False

Service Levels Name

ServiceLevelSet Service Level Set

ServiceLevel Set

Safety Stock Unmet Amount

SafetyStock Unmet

N/A QtyCalendar



SKU (spSKU) 143

SKU attribute descriptions

Stockkeeping unit. A SKU defines an item at a location.

Name

The system creates a unique name for each SKU using this format:

Sourcing Type SourcingType sourcingtype List of values

Off, Group, Local Off

Sourcing Group SourcingGroup sourcinggroup String

Standard Cost StandardCost standardcost Rate Calendar

US dollars/year 0

Strategy Initial On-hand

SCNInitialOH Strategy Initial On-hand


Target On-hand TargetOH Target On-hand Constraint, Amount

Qty Calendar 0 <default UOM>

Target On-hand Enabled

TargetOHStatus Target On-hand Constraint, Status


False (Off)

Target On-hand Penalty (per day)

TargetOHPenalty Target On-hand Constraint, Penalty

Rate Calendar

0 USD/<default UOM>

Target On-hand Variance Amount

TargetOHUnmet N/A QtyCalendar


String Name of an existing tiered cost/price


Boolean True, False

Violates Supplying % Constraint

Boolean True, False




<Item>@<Location>

For example:

24-783@Toronto

You cannot change this value after the SKU is created.

Cost (to buy)

The default cost for any purchases of this SKU from a supplier, expressed as a currency unit of measure per unit of measure for the item.

Cost of Capital

The rate that represents the cost of money invested in inventory rather than in an investment that provides a return. Expressed in terms of a percentage.

Cost/Price type (Costing/Pricing)

The costing/pricing type used by Strategy:

• Off: The Optimizer considers the SKU to have no cost or price.

• Local: The Optimizer uses the Local costing/pricing attribute for this object (Cost or Price).

• Tiered Cost/Price: The Optimizer uses the selected tiered cost/price.

Default UOM

The default unit of measure, taken from the item associated with the SKU.

Import/export note: This value cannot be imported or exported.

Description

Free-form text description of this SKU.

Entire Time Horizon

If Max Sourcing is enabled, whether the same maximum sourcing restriction is used for the entire planning calendar.

• True: The same maximum number of sources is used for the entire planning calendar.

• False: The maximum number of sources can change during the planning calendar or be restricted to a period within it.

SKU (spSKU) 145


This is a special attribute that allows you to create data selections to select SKUs that have exceeded any of the following maximum constraints:

• Maximum onhand unmet amount

• Maximum inflow unmet amount

• Maximum outflow unmet amount

• Target onhand variance amount

To select all SKUs where the maximum attributes have a value in any period (or where Target on-hand variance amount has a positive value in any period), create your data selection such that Exceeds Any Max Constraint is True.

Has Met Demand

This is a special attribute that allows you to create data selections to select SKUs that have met demand. To select all SKUs where the Met Demand Amount has a value in any period, create your data selection such that Has Met Demand is True.

Has Unmet Demand

This is a special attribute that allows you to create data selections to select SKUs that have unmet demand. To select all SKUs where the Maximum Demand Unmet Amount has a value in any period, create your data selection such that Has Unmet Demand is True.

Include Destination as Source

If Max Sourcing is enabled and there is a make process for the SKU at this location (destination), whether it will be considered as a possible source.

• True: Strategy sees this destination as a possible sourcing location.

• False: Strategy does not consider this location as a possible source.

Independent Demand

The Independent Demand and Maximum Demand constraints are the mechanisms that “pull” product through the Supply Chain Network. Independent Demand represents the minimum forecasted demand for a particular product, and Maximum Demand represents the maximum forecasted demand. You may wish to set both Independent and Maximum Demand to ensure that a certain amount of product is


produced, but that additional product may be produced if it is profitable. See the section “Maximum Demand” on page 147 for more information on that attribute.

When only Independent Demand is enabled (Soft or Hard), it acts as both a minimum and a maximum constraint. Like a minimum constraint, the Independent Demand constraint has a penalty associated with it for not meeting independent demand. Like a maximum constraint, the Independent Demand constraint prevents the Optimizer from producing more than the independent demand amount. Note that Independent Demand is not a true maximum constraint because maximum constraints have a penalty associated with amounts that exceed the constraint. Independent Demand does not have such a penalty. The constraint is used in this manner to safeguard against the production of additional product. If the constraint were not treated in this manner, the Optimizer may chose to “push” a SKU in excess of demand. For example, if a SKU has storage costs associated with it, the Optimizer may choose to "push" more of the product through the Supply Chain as opposed to incurring the additional storage costs.

Independent Demand Enabled


• Off: The Optimizer does not constrain on Independent Demand.

• Soft: The constraint has a penalty cost. The Supply Chain Optimizer may violate this constraint and incur the penalty cost in order to achieve a feasible optimal plan.

• Hard: The Optimizer constrains on Independent Demand and will not violate the constraint.

Independent Demand Penalty

The penalty cost incurred if the actual demand met is less than the amount specified in the Independent Demand constraint. Units must be in or convertible to Currency/SKUs default unit of measure.

Independent Demand Unmet Amount

The amount by which the actual demand met was under the Independent Demand constraint specified. This value is output by the Supply Chain Optimizer.

Item

The item associated with this SKU. This item must exist in the database before the SKU is created. You cannot change this value after the SKU is created.

SKU (spSKU) 147

Location

The location associated with this SKU. This location must exist in the database before the SKU is created. You cannot change this value after the SKU is created.

Location Restricted

Designates whether Max Sourcing is enabled on the Location associated with the SKU. If Max Sourcing is enabled on the Location, the Max Sources on the Location will override any Max Sources setting on the SKU. You cannot change this setting.

Manufactured

Designates whether this item is manufactured. Strategy sets this attribute based on whether a make process exists with this SKU as an output.

Maximum Demand

The Independent Demand and Maximum Demand constraints are the mechanisms that "pull" product through the Supply Chain Network. Independent Demand represents the minimum forecasted demand for a particular product, and Maximum Demand represents the maximum forecasted demand. If more than this amount is met, a penalty cost will be incurred. You may wish to set both Independent and Maximum Demand to ensure that a certain amount of product is produced, but that additional product may be produced if it is profitable. See the definition of “Independent Demand” on page 145 for more information on how the Independent Demand attribute affects the Optimizer.

If the Optimization Objective is to Maximize Profit and the Maximum Demand constraint is enabled (whether Soft or Hard), the Optimizer treats the Maximum Demand constraint as a hard constraint. By enabling the Maximum Demand constraint, the Optimizer will not produce an unlimited amount of product. Otherwise, if the cost of producing and storing a product is less than the revenue generated, the Optimizer would choose to produce an unlimited amount of the product.

Maximum Demand Enabled


• Off: The Optimizer does not constrain on Maximum Demand.



• Hard: The Optimizer constrains on Maximum Demand and will not violate the constraint.

Maximum Demand Penalty

The penalty cost incurred if the actual demand met is more than the amount specified in the Maximum Demand constraint. Units must be in or convertible to Currency/SKU’s default unit of measure.

Maximum Demand Unmet Amount

The amount by which the actual demand met was over the Maximum Demand constraint specified. This value is output by the Supply Chain Optimizer.

Maximum Inflow Amount

The Maximum Inflow constraint for this SKU. Total supply of this SKU as the result of incoming move/purchase/make processes must be no greater than the value specified in this attribute for each time period or a penalty cost will be incurred.

Maximum Inflow Penalty

The penalty cost incurred if the actual inflow is more than the amount specified in the Maximum Inflow constraint. Units must be in or convertible to a currency unit of measure per the SKU’s default unit of measure.

Maximum Inflow Enabled


• Off: The Optimizer does not constrain on Maximum Inflow.


• Hard: The Optimizer constrains on Maximum Inflow and will not violate the constraint.

Maximum Inflow Unmet Amount

The amount by which the actual inflow amount was over the Maximum Inflow constraint specified. This value is output by the Supply Chain Optimizer.

SKU (spSKU) 149

Maximum Onhand

The maximum amount of material onhand or maximum length of forward coverage for this SKU. You can specify this attribute in terms of quantity or in terms of time.

• Specifying as a quantity: If specified as a quantity, the Optimizer treats the value as the minimum amount of material that must be kept on hand. No more than this amount can be kept on hand at the end of each period or a penalty cost will be incurred.

• Specifying as a time (forward inventory coverage): If specified as time, the Optimizer will calculate the required inventory based on demand (forward inventory coverage). Forward inventory coverage allows the Optimizer to look ahead and make sure there is enough, but not too much, on hand in order to meet future demand. In this case, the Optimizer calculates the inventory level as the total of the outflow (the independent and dependent demand) during the forward coverage period.

This attribute can be set in conjunction with the Safety Stock attribute to control your inventory levels, or you can use the Target Onhand attribute instead. Alternatively, you can enable Safety Stock and Maximum Onhand as Hard constraints, and enable Target Onhand as a Soft constraint. See “Safety Stock” on page 152 and “Target On-hand” on page 155 for information on those attributes.

The setting of Maximum Onhand Enabled determines the effect of this value on Strategy.

Maximum Onhand Enabled


• Off: The Optimizer does not constrain on Maximum Onhand.


• Hard: The Optimizer constrains on Maximum Onhand and will not violate the constraint.

Maximum Onhand Penalty

The penalty cost incurred (per day) if the actual on hand is more than the amount specified in the Maximum Onhand constraint. Units must be in or convertible to a currency unit of measure per the Item’s default unit of measure.


Maximum Onhand Unmet Amount

The amount by which the actual on-hand amount was over the Maximum Onhand constraint specified. This value is output by the Supply Chain Optimizer.

Maximum Outflow Amount

The Maximum Outflow constraint for this SKU. Total demand from this SKU as the result of outgoing move/purchase/make processes must be no greater than the value specified in this attribute for each time period or a penalty cost will be incurred.

Maximum Outflow Enabled


• Off: The Optimizer does not constrain on Maximum Outflow.


• Hard: The Optimizer constrains on Maximum Outflow and will not violate the constraint.

Maximum Outflow Penalty

The penalty cost incurred if the actual outflow is more than the amount specified in the Maximum Outflow constraint. Units must be in or convertible to Currency/Item’s default unit of measure.

Maximum Outflow Unmet Amount

The amount by which the actual outflow amount was over the Maximum Outflow constraint specified. This value is output by the Supply Chain Optimizer.

Max OH

See Maximum Onhand

Maximum Sources

The maximum number of locations from which the Optimizer can source a SKU.

Met Demand Amount

The actual demand that was met. This value is output by the Supply Chain Optimizer.

SKU (spSKU) 151

Minimum Inflow Amount

The minimum inflow constraint for this SKU. Total supply of this SKU as the result of incoming move/purchase/make processes must be no less than the value specified in this attribute for each time period.

Minimum Inflow Enabled


• Off: The Optimizer does not constrain on Minimum Inflow.


• Hard: The Optimizer constrains on Minimum Inflow and will not violate the constraint.

Minimum Inflow Penalty

The penalty cost incurred if the actual inflow is less than the amount specified in the Minimum Inflow constraint. Units must be in or convertible to Currency/unit of measure.

Minimum Inflow Unmet Amount

The amount by which the actual inflow amount was under the Minimum Inflow constraint specified. This value is output by the Supply Chain Optimizer.

Minimum Outflow Amount

The Minimum Outflow constraint for this SKU. Total demand from this SKU as the result of outgoing move/purchase/make processes must be no less than the value specified in this attribute for each time period or a penalty cost will be incurred.

Minimum Outflow Enabled


• Off: The Optimizer does not constrain on Minimum Outflow.



• Hard: The Optimizer constrains on Minimum Outflow and will not violate the constraint.

Minimum Outflow Penalty

The penalty cost incurred if the actual outflow is less than the amount specified in the Minimum Outflow constraint. Units must be in or convertible to Currency/unit of measure.

Minimum Outflow Unmet Amount

The amount by which the actual outflow amount was under the Minimum Outflow constraint specified. This value is output by the Supply Chain Optimizer.


• True: Some of the demand for this SKU is forecasted.

• False: None of the demand for this SKU is forecasted.

This attribute is not used by the Supply Chain Optimizer, but it can be used in data selections and for reporting purposes.

Optimal Onhand

The time-phased, end-of-period on-hand inventory values that are generated by execution of the Supply Chain Optimizer.

Price (to sell)

The default price to sell this SKU to a customer, expressed as a currency unit of measure per unit of measure for the item.

Raw Material

Designates whether this item is a raw material. Strategy sets this attribute based on whether this SKU is an input SKU to a MakeProcess.

Safety Stock

The minimum amount of material onhand or minimum length of forward coverage for this SKU. You can specify this attribute in terms of quantity or in terms of time.

• Specifying as a quantity: If specified as a quantity, the Optimizer treats the value as the minimum amount of material that must be kept on hand. If inventory drops below this level, a penalty will be incurred.

SKU (spSKU) 153

• Specifying as a time (forward inventory coverage): If specified as time, the Optimizer will calculate the required inventory based on demand (forward inventory coverage). Forward inventory coverage allows the Optimizer to look ahead and make sure there is enough, but not too much, on hand in order to meet future demand. In this case, the Optimizer calculates the inventory level as the total of the outflow (the independent and dependent demand) during the forward coverage period.

Safety Stock can be set in conjunction with the Maximum Onhand attribute to control your inventory levels, or you can use the Target Onhand attribute instead. Alternatively, you can enable Safety Stock and Maximum Onhand as Hard constraints, and enable Target Onhand as a Soft constraint. See “Maximum Onhand” on page 149 and “Target On-hand” on page 155 for information on those attributes.

The setting of Safety Stock Enabled determines the effect of this value on Strategy.

Safety Stock Enabled


• Off: The Optimizer does not constrain on Safety Stock.


• Hard: The Optimizer constrains on Safety Stock and will not violate the constraint.

Safety Stock Penalty

The penalty cost incurred per day if the actual on hand is less than the amount specified in the Safety Stock constraint. Units must be in or convertible to a Currency UOM per the SKU’s default UOM.

Safety Stock Unmet Amount

The amount by which the actual on-hand amount was under the Safety Stock constraint specified. This value is output by the Supply Chain Optimizer.


Calculation of the actual percentage that is being delivered for the SKU. If both SKU-level and location-level service levels apply, the location service level takes precedence.



Determines whether service levels are enabled for this SKU. If set to FALSE, service levels are disabled for this SKU.

Service Level Set

If service levels are enabled, this attribute indicates the name of the service level set that will be applied.

Sourcing Group

If Sourcing Type is set to Group, indicates the sourcing group to which this location belongs.

Sourcing Type

Defines the type of max sourcing to be used at this location. If set to Off, max sourcing is disabled for this location; if set to Local, max sourcing applies only to the location itself; if set to Group, max sourcing applies to all locations in the group. When you set a sourcing type to Group, you must also select the group for this location.

Standard Cost

The monetary value of the investment in inventory, including the total cost of material, labor, and overhead assigned to an item.

Storage Resource

The reusable resource, whose Type is Storage, where this SKU is stored. A resource requirement is used to associate the SKU with the storage resource.

Strategy Initial On-hand

The time-phased amount used as the initial on-hand inventory of this item at this location. The Optimizer uses the value of this attribute at one minute prior to the planning calendar as the initial on hand of the SKU. The rest of the values of this attribute are ignored for that run of the Optimizer.

Note: Supplier locations cannot be assigned to sourcing groups because they do not have source.

SKU (spSKU) 155

Target On-hand

The desired inventory level or desired length of forward coverage. You can specify this attribute in terms of quantity or in terms of time.

• Specifying as a quantity: If specified as a quantity, the Optimizer treats the value as the desired amount of material that should be kept onhand, and a penalty will be incurred if the inventory deviates from that value. This value should be greater than Safety Stock and less than Maximum Onhand, if those constraints are used.

• Specifying as a time (forward inventory coverage): If specified as time, then the Optimizer will calculate the required inventory based on demand (forward inventory coverage). Forward inventory coverage allows the Optimizer to look ahead and make sure there is enough, but not too much, on hand in order to meet future demand. In this case, the Optimizer calculates the inventory level as the total of the outflow (the independent and dependent demand) during the forward coverage period.

This attribute can be set in conjunction with or in addition to the Safety Stock and Maximum Onhand attributes to control your inventory levels. If enabling Safety Stock and Maximum Onhand, set them as Hard constraints and enable Target Onhand as a Soft constraint. See “Maximum Onhand” on page 149 and “Safety Stock” on page 152 for information on those attributes.

The setting of Target On-hand Enabled determines the effect of this value on Strategy.

Target On-hand Status

Determines whether this constraint is enabled when you run the Supply Chain Optimizer.

• On: The Optimizer considers future demand for the SKU along with the desired (target) inventory level when determining on-hand levels.

• Off: The Optimizer ignores any Target On-hand values.

Target On-hand Penalty

This cost, specified in terms of a currency per SKU’s default UOM, is incurred if the inventory level varies in either direction from the specified target. Unit of measure cannot be in terms of forward coverage.


Target On-hand UnMet

The variance (over or under) between the target on hand and the actual on hand recommended by the Supply Chain Optimizer. This value is output by the Optimizer.

Tiered Cost/Price

Name of the tiered cost or price object associated with this SKU. You can have several tiered costs/prices defined, but only one can be associated with the SKU at one time. See the section “Tiered Cost/Price” on page 164 for more information on the Tiered Cost/Price object.


This is a special attribute that allows you to create data selections to select SKUs that have gone below any of the following minimum constraints:

• Safety stock unmet amount

• Minimum inflow unmet amount

• Minimum outflow unmet amount

• Target on hand variance amount

To select all SKUs where the minimum attributes have a value in any period (or where Target on hand variance amount has a negative value in any period), create your data selection such that Under Any Min Constraint is True.

Violates Supplying % Constraint

This is a special attribute that allows you to create data selections to select SKUs that are referenced by a supplying SKU Requirement where the supply percentage constraint has been violated. To select all SKUs referenced by a SKU Requirement where the Constraint % unmet amount has a value in any period, set Violates Supplying % Constraint to True.

Import/export notes• Because the SKU object exists in both NetWORKS Scheduling and Strategy, the

object-type name spSKU is used in all Data Import and Data Export input and output files to denote the Strategy SKU object. You cannot use the object-type SKU for any input files used in the Data Import, Data Export, or Delete Data processes.

SKU (spSKU) 157

• Importing many time-phased attributes, such as Independent Demand, Maximum On Hand, and so forth, can be simplified using the Data Loader. See the section “Using the Data Loader to import data” on page 43 for more information.

• The following attributes are generated by the Supply Chain Optimizer and cannot be updated, except in a baseline scenario:

> Optimal onhand

> Minimum and maximum inflow unmet amount

> Minimum and maximum outflow unmet amount

> Safety stock unmet amount

> Maximum onhand unmet amount

> Target onhand unmet amount

> Independent demand unmet amount

> Maximum demand unmet amount

> Met demand amount.


SKURequirementStrategy userview: Processes (for process name and requirement), SKU (for constraints)

Referenced in Strategy by: MakeProcess, MoveProcess, PurchaseProcess, SKU (spSKU)

SKURequirement attribute descriptions

SKU Requirements define the quantity of a SKU that is input to or output from one execution of a make, move, or purchase process.

For a make process, you specify SKU requirements for one or more output SKUs (the SKU being made) and zero or more input SKUs (raw materials or components).

For a move or purchase process, you specify SKU requirements for one source SKU and one destination SKU.

Table 25: SKURequirement attributes


Name (SKURequirement) Name String

Supplier Supplier String Name of an existing SKU or process

X

Demander Demander String Name of an existing SKU or process

X

Constraint penalty

PercentageConstraintPenalty N/A Rate Calendar 0 USD/<default UOM>

Constraint% unmet amount

OverPercentage AmountUnderPercentage Amount

N/A QtyCalendar

%Constraint PercentageConstraint N/A Double Calendar

%Constraint enabled

PercentageConstraintEnabled N/A List of values Off, Soft, or Hard Off

Requirement Requirement Requirement QtyCalendar

SKURequirement 159

Before defining SKU Requirements for a process, you must decide how much of the associated SKU is to be made or transported by one execution of the process—a single unit of the SKU, for example, or a whole batch or lot. “Execution” is a conceptual term, not an attribute that is defined and stored in the database.

For example, if one execution of a make process produces one unit of a SKU (one carton of 12-ounce cans of soup), the SKU requirements might be:

Or if one execution of the make process produces one batch of the SKU (500 cartons of 12-ounce cans of soup), the SKU requirements might be:

Name

Name of process associated with this SKURequirement. The system created this name, using the following format:

supplier−>demander

For example:

ItemA@LA->Buy--ItemA--LA->ChicagoSell--ItemB--NewYork->Miami->ItemB@Miami

Demander

If this is a requirement for an input SKU, Demander is the name of the process associated with the requirement.

SKU Input or Output Requirement

Carton of 12-ounce cans of soup Output 1 unit

Soup Input 2.25 gallons

Cans Input 24 units

Cartons Input 1 unit

SKU Input or Output Requirement

Carton of 12-ounce cans of soup Output 500 units

Soup Input 1125 gallons

Cans Input 12,000 units

Cartons Input 500 units


If this is a requirement for an output SKU, Demander is the name of the output SKU.

Supplier

If this is a requirement for an input SKU, Supplier is the name of that SKU.

If this is a requirement for an output SKU, supplier is the name of the process associated with the requirement.

Constraint penalty

The penalty cost incurred if the percent of total supply contributed by this requirement is different than the percentage specified in the supply percentage constraint. Units must be in or convertible to a currency/UOM per the SKU’s UOM.

Constraint% unmet amount

The amount, in terms of the SKU’s default UOM, by which the percent of total supply contributed by this requirement was over or under the supply percentage constraint specified. This value is output by the Supply Chain Optimizer and cannot be changed. A positive value means the supply percentage was over and a negative number means the supply percentage was under.

Import/export note: Although this value is shown as one attribute in Strategy, it actually exists as two separate attributes in the database:

• OverPercentage Amount: The amount by which the supply percentage is over the % constraint.

• UnderPercentage Amount: The amount by which the supply percentage is under the % constraint.

%Constraint

The percentage constraint. If more than one process supplies a SKU, then the amount supplied by the process connected to this requirement must be exactly the percentage specified by this constraint or a penalty cost will be incurred.

%Constraint enabled

Determines whether these constraints are enabled when you run the Supply Chain Optimizer. Values are:

• Off: The Optimizer does not constrain on this constraint.

SKURequirement 161


• Hard: The Optimizer constrains on the percentage constraint and will not violate the constraint.

Requirement

The draw or yield quantity—that is, the quantity of SKU required as input or output. This quantity is time-phased.

Import/export notes:• Once a SKU requirement has been created, you cannot update the name of the

requirement, the supplier, or the demander.

• If you delete a process, the program will delete all of its associated SKU requirements at the same time.

• You cannot delete the last output SKU requirement for a manufacturing (make) process. The last output SKU requirement must be deleted with the process itself.


SourcingGroupStrategy userview: Sourcing Group

Referenced in Strategy by: SKU or Location

Sourcing Group (SourcingGroup) attribute descriptions

A sourcing group is a collection of SKUs or locations that obey a common max sourcing constraint. By using sourcing groups, you can set a maximum number of total sources for a group of SKUs or locations.

Name

Text name of this sourcing group.

Description

Free-form text description of this sourcing group.

Group Type

Defines the type of the sourcing group: SKU or Location. The group must consist of either SKUs or locations; it cannot contain both.

Table 26: Sourcing Group (SourcingGroup) attributes


Name (SourcingGroup) Name String Yes


Group Type GroupType N/A String SKU/Location Yes


includedestassource includedestassource Boolean True, False False

Is group enabled isgroupenabled isgroupenabled Boolean True, False False

Include location in group

isgrouplocincluded isgrouplocincluded Boolean True, False False

Max Sources maxsources maxsources Integer 0


useentiretimehorizon useentiretimehorizon Boolean True, False False

163


When Sourcing Type is Local or Group, if there is a make process for the SKU at this location (destination), determine if a location will be considered as a possible source.

• True: Strategy considers this destination as a possible sourcing location, so it will consider make processes when calculating the number of sources for this destination.

• False (default): Strategy does not consider this location as a possible source, so it will not consider make processes when calculating the number of sources for this destination.

Is Group Enabled

If set to True, max sourcing is enabled on this group; if set to False (the default), max sourcing is disabled on this group.

Include Location in Group

If set to True, Strategy considers locations within the group as sources to the group; if set to False (the default), Strategy does not consider locations within the group as sources to the group.

Max Sources

Specifies the maximum number of sources that can be selected for the group in each time period.


If set to True, forces the sources selected to be the same ones in every time period across the entire planning horizon; if set to False (the default), enables the sources to change in each time period.


Tiered Cost/PriceStrategy userview: Tiered Costs/Prices or Strategy

Referenced in Strategy by: PurchaseProcess, ReusableResource, SKU

Table 27: Tiered Cost/Price attributes



Tiered Cost/Price

Name (TieredCostPrice) Name String X

Accumulation Period

Accumulation PeriodType

Accumulation Period Type

List of values Day(s), Week(s), Month(s), Quarter(s), Year(s)

Year

NumAccumulationPeriods

Num Accumulation Periods

Integer 1

Batch ZeroUtilBatchCost Zero Util Batch Cost

QtyCalendar

Calculation Method

IsCumulative Is Cumulative Flag

Boolean True (Cumulative), False (Direct)

False (Direct)

Currency unit of measure

CurrencyUofM Currency UOM

UOM Valid currency UOM enabled for your system

X


Grouping IsGrouped Is Grouped Flag

Boolean True (Yes), False (No)

False (No)

Quantity unit of measure

QuantityUofM Quantity UOM UOM Valid UOM enabled for your system

X

Tiers N/A List Tiers associated with this cost/price object

Tiered Price Pair

Tiered Cost/Price 165

Tiered Cost/Price attribute descriptions

The Tiered Cost/Price object models volume cost and price breaks that are typically presented in a multi-tiered format, in which each tier specifies a range of quantities that share the same price or cost. You can apply the tiered structure to SKU prices or the costs of SKUs or reusable resources.

Multi-tier pricing enables Strategy to develop a more robust solution when you have the option of buying products or consuming resources according to a multi-tier pricing or costing scheme. It also helps you analyze alternative prices and quantities against inventory carrying costs, and it enables you to use more accurate resource costs.

The same Tiered Cost/Price object can be referenced by multiple objects. For example, a SKU and a Purchase Process could reference the same Tiered Cost/Price.

Note that enabling Multitiered Costing/Pricing requires the use of Mixed Integer Programming (MIP) and can slow performance when running the SC Optimizer.

Name

Text name of this tiered cost/price. Once a tiered cost/price has been created, you cannot update the name.

Accumulation Period

Whether the accumulation period represents years, quarters, months, weeks, or days.

Import/export note: If you are using the Data Import process, you must specify the period as Day(s), Year(s), Quarter(s), Month(s), or Week(s).

Tiered Price Structure

Tier-Tiers String Tier

Break Quantity Break Quantity Break Quantity

Qty

Type, Batch BatchCost Batch Cost QtyCalendar

Type, Per UOM PerUOMCostPrice Per UOM Cost/Price

RateCalendar

Table 27: Tiered Cost/Price attributes




Num Accumulation Periods

The number of accumulation periods, using the type specified above. For example, if you specify 6 for the number and monthly for the period type, Strategy will track the quantity purchased or utilized over 6 months, selecting the appropriate cost/price tier (volume discount) to use for each month.

Batch

If the utilization is exactly zero, then this cost (which must have a currency unit of measure) is incurred.

Calculation Method

Determines the method Strategy uses to calculate the total cost, using tiered prices or costs.

• Direct (False): Strategy calculates the total price by directly multiplying the corresponding quantity break’s UOM cost/price with the quantity purchased or utilized, and then adds the result with the corresponding Batch cost. For example:

Quantity purchased: 25 units

False is the value used by the Data Import and Data Export processes.

• Cumulative (True): Strategy calculates the total price by aggregating the quantity and price from each quantity break until the total quantity is attained. (The batch cost for 0 quantity is not included in the cumulative calculation.) For example:

Quantity purchased: 25 units

Break Quantity Cost/price per UOM ($) Batch Cost ($)

=0 0 1

>0 10 2

>10 9 3

>20 8 4

Total cost = (25 units x $8) + $4 = $204

Break Quantity Cost per UOM ($) Batch Cost ($) Contribution to cumulative cost

=0 0 1 0


True is the value used by the Data Import and Data Export processes.

Currency unit of measure

Indicates the currency unit of measure that Strategy uses for the costs/prices in this tier.

Description

Free-form text description of this tiered cost/price.

Grouping

Determines how Strategy determines quantity breaks for price/cost tiers.

• Yes (True): Quantity break based on the total volume of SKUs, resources, or purchase processes that share the same tier name. True is the value used by the Data Import and Data Export processes.

• No (False): Quantity break based on the volume of each SKU, resource, or purchase process independently, even if they share the same tier name. False is the value used by the Data Import and Data Export processes.

Quantity unit of measure

Indicates the quantity unit of measure that Strategy uses when determining break quantities and unit costs.

Tiers

A collection of tiered cost/price pairs. See definition below. You can have several tiered costs/price pair objects defined.

>0 10 2 (10 units x $10) + $2 = $102

>10 9 3 (10 units x $9) + $3 = $93

>20 8 4 (5 units x $8) + $4 = $44

Total cost = $102 + $93 +$44 = $239

Break Quantity Cost per UOM ($) Batch Cost ($) Contribution to cumulative cost


Tiered Price Pair attribute descriptions

Break Quantity

The quantity at which point this price or cost break is applied.

Type, Batch

The incremental cost that is added when the break quantity is reached.

Type, Per UOM

The base cost/price that is associated with one quantity of the currency unit of measure. The units of measure are implicitly based on the currency unit of measure and quantity unit of measure in the tiered cost/price.

Import/export notes

Special formatting is required to import or export this object. See the sections that follow for specific instructions.

Importing Tiered Cost/Price objects

To import a tiered cost/price object, you must use a special, leveled format, as follows:

(level), tieredcostprice, <attribute>, . . .1, <tieredcostprice_name>, <value>, . . .(level), tier-tiers, <attribute>, . . .2,Tier, <value>, . .

For example:

(level), tieredcostprice, currencyuofm, quantityuofm1,Cost/Price 1,USD,Gram(level),tier-tiers,breakquantity2,Tier,25.000000 Grams,batchcost,USD,,MIN_TIME,MAX_TIME,56.000000,peruomcostprice,USD,Gram,,MIN_TIME,MAX_TIME,2.000000(level),tier-tiers,breakquantity2,Tier,100.000000 Grams,batchcost,USD,,MIN_TIME,MAX_TIME,45.000000,peruomcostprice,USD,Gram



Or (the header row breaks in this example due to its length):

(level),TieredCostPrice,accumulationperiodtype,currencyuofm,description,iscumulative,isgrouped,numaccumulationperiods,quantityuofm1,ACMETransRates,Quarters(s),USD,,false,false,1, Kilogram,zeroutilbatchcost,USD,,MIN_TIME,MAX_TIME,100.000000(level),tier-tiers,breakquantity2,Tier,0.000000 Kilograms,batchcost,USD,,MIN_TIME,MAX_TIME,200.000000,peruomcostprice,USD,Kilogram,,MIN_TIME,MAX_TIME,10.000000(level),tier-tiers,breakquantity2,Tier,1000.000000 Kilograms,batchcost,USD,,MIN_TIME,MAX_TIME,100.000000,peruomcostprice,USD,Kilogram,,MIN_TIME,MAX_TIME,8.000000(level),tier-tiers,breakquantity2,Tier,5000.000000 Kilograms,batchcost,USD,,MIN_TIME,MAX_TIME,0.000000,peruomcostprice,USD,Kilogram,,MIN_TIME,MAX_TIME,6.000000

Exporting Tiered Cost/Price objects

To export tiered cost/price objects, you must use the following format:

(level),tieredcostprice, <attribute_name>, . . .1,<tieredcostprice_name>

To export all tiered cost/price objects and their associated attributes, use the following format:

(level),tieredcostprice,*1,*

To export only the tiered price pairs for all tiered cost/price objects, set up your input file in the following format:

(level),tieredcostprice, tiers1,*

Part Three

Appendices

Appendix A

Data types for database attributes

This section contains information on the data types used in this Reference Manual. You must use these data types to format your attribute values when you are setting up your input files for the Data Import, Data Export, and Delete Data processes.

The table below lists the data types that are used in this Reference Manual. The data type name is listed in the first column. Next to the data type is its format, followed by a column that gives examples of that type. The column to the far right indicates whether you can use attributes with that data type to select objects for updating, exporting, or deleting objects.

Note: All attribute values are case insensitive.

Table 28: Data types for database attributes

Data type Format Examples Can be used to select objects?

Boolean True or FalseYes or No

True YesFalse No

X

Conversion factor

Decimal 1.52 4

Capacity Calendar

,UOM,,start_date, end_date, starting_capacity, ending_capacity

,gallon,,2/ 1/1998 0:00:00, 2/1/1997 0:00:00, 40.000000, 40.000000

Date/time Formatted according to the date/time format configured on the Scheduling server computer. For example, MM/DD/YYYY HH:MM:SS See the section “Specifying dates and numbers in different locales” on page 13 for more information. Note: See the note below on valid date ranges. This is 24 hour format. If no time is specified, the time is assumed to be 0:00:00.

12/31/19993/1/1999 7:302000-01-01 0:00:00


DblCalendar ,,start_date, end_date, Decimal 01/01/1998, 04/01/1998, 1.5, 04/01/1998, 07/01/1998, 4

Decimal whole or fractional number 1.553.634-3.52

X

Duration Integer value. The value is always assumed to be in terms of minutes.

20401

X

Integer whole number 0256-4

X

Interval start_date, end_dateTo define one interval for all time (time independent values), use min_time and/or max_time in place of the start or end date. This is 24 hour format. If no time is specified, the time is assumed to be 0:00:00.

4/1/1998 11:00, 4/2/1998 7:00min_time, 5/1/1998 13:0010/1/1998, max_timemin_time, max_time

List One or more strings, each listed as a separate data value. Often lists require you to specify the name(s) of other object(s); in this case, the object you are referencing must already exist.During updates, anything specified for a list attribute will replace rather than append to any existing values for that attribute.

ProdFam1, ProdFam2item1@loc1, item2@loc1

X

List of values A specific value is required. SoftPink

XNote: Certain attributes of this type cannot be used to select objects. See “Using attributes other than name to update objects” on page 24 for more information.

Qty Decimal UOM 5 liters25.5 fluid ounces

Table 28: Data types for database attributes (continued)


Data types for database attributes 175

Notes on data types

Separator character

In the examples given in this manual, a comma (,) is shown as the separator character. When you create an input file, the separator character between values can be a comma or any unique character you specify (for example, ' ! " # % & * . / : ; @ ^). The separator character you use must not be used in your data values. For example, if you use a comma as the separator character, you cannot have commas in your data. Choose a character that is unique and will not cause conflicts with your data. You do not have to have spaces before or after your separator character.

Quotes in your data

You should not use double quotes around your data values.

QtyCalendar UOM [, interval_start_date, interval_end_date, Qty…] Important: the UOM must be specified in the singular (for example, kilogram, not kilograms)

Gallon, 1/1/1998, 4/1/1998, 5 [UOM]

QtyConversion source_UOM conversion_factor target_UOM [source_UOM conversion_factor target_UOM. . .]Important: the UOMs must be specified in the singular (for example, kilogram, not kilograms)

kilogram 1 unitPound 5 “fluid ounce”Liter 4 pound ounce 3 unit

Rate Qty [per UOM] 5 3 dollars per fluid ounce1462

RateCalendar numerator_UOM, denominator_UOM, [interval_start_date, interval_end_date, Rate. . .]Important: The UOMs must be specified in the singular (for example, kilogram, not kilograms)

USD, gram, 01/01/1999, 04/01/1999, 5 [numerator_UOM per denominator_UOM]

String Text syrup - 8 oz bottlecough medicine - 12 oz

X

UOM (unit of measure)

Text string; if using in a QtyConversion and is more than one word, enclose in quotes (“”); otherwise, no quotes are needed around multiple words.Important: The UOM must be singular when used to specify a default UOM (for example, kilogram, not kilograms), but can be plural when used to specify a quantity (5 pounds).

unitlitersfluid ounces (if in Qty or Rate)“fluid ounces” (if in QtyConversion)

Table 28: Data types for database attributes (continued)



Specifying time intervals

Several of the data types require you to specify time intervals. When specifying time intervals using Data Import, the end date of one interval must be the same as the start date of the next period. All dates that are not specified with a time are assumed to be at 00:00 of that date, and the system assumes the date includes all time up to, but not

including, the end date. Thus, if you wanted to specify January 1st through March 31st

and April 1st through June 30th 1999, you would enter your data as follows in your Data Import file:

01/01/1999, 04/01/199904/01/1999, 07/01/1999

Using min_time and max_time

When specifying time intervals, you can use the keywords min_time and/or max_time to define the beginning or ending date of an interval. Using min_time denotes that you want the interval to start at the earliest possible time (1/1/1970). Using max_time denotes that you want the interval to end at the latest possible time (12/31/2037). If you use both min_time and max_time in your interval, you will define one interval for all time.

The valid date range for all Manugistics products is January 1, 1970 to January 18, 2038. Use of any dates outside this range will result in inconsistent results in Manugistics products.

Updating intervals

If you are updating intervals in a calendar, you must update all relevant intervals within your calendar at the same time. If you specify only a single time interval during an update process, the process will set the values for the remaining time intervals within your calendar to zero. For example, if you had a calendar with four quarters, you can update all four intervals at once, for example:

(spSKU), price10100,price,dollar, unit,,1/1/1999,4/1/1999,12,,4/1/1999,7/1/1999,12.5,,7/1/1999,10/1/1999,12.25,,10/1/1999,1/1/2000,13

If you subsequently want to update only one of the intervals (for example, 10/1/1999, 1/1/2000, 12 dollars), you must respecify all four of the intervals or you will delete the

Data types for database attributes 177

existing values for the other three intervals. If you want to clear a calendar entirely, you can specify the attribute for an object with no time intervals, for example:

(spsku), price10100,dollar,unit

All intervals in the existing calendar would be erased in the above example.

Specifying and customizing units of measure

Strategy by default uses a list of predefined units of measure. You can customize your unit of measure categories and the entries within those categories using the System Administration utility. Only those categories and entries that have been enabled in the System Administration utility appear in the list of values you see in Strategy .

If you are using the Data Import process to create or update objects, you must use units of measure that are valid for your system. You must keep the unit of measure entries and categories synchronized across all Strategy computers that comprise your system. If you do not, data corruption may occur.

For information on setting up customized units of measure, see the System Administration online help and the NetWORKS Scheduling and Strategy Installation/Administration Manual.

Specifying default units of measure

If you are using the Data Import process and you specify a default unit of measure in your input file, you must specify it in the singular (for example, liter, not liters).

However, when specifying an actual value with a unit of measure, you can use the plural. Take the following example:

(spSKU), description, scninitialohflour@CHI, white flour,200 pounds,price,USD,pound,,1/1/2000,4/1/2000,.30,,4/1/2000,7/1/2000,.32,maxohpenalty,USD,pound,,1/1/2000, 4/1/2000, 5,,4/1/2000, 7/1/2000, 6

plural

singular


Specifying units of measure in a QtyConversion attribute

If you are specifying a UOM following a number in a value with a data type of QtyConversion, you must use double quotes around the UOM if it is more than one word. For example, see the following QtyConversion for item:

(spITEM), qtyconversion10100, pound 4.5 "fluid ounce"

Updating lists

If you specify a data value for an attribute with a data type of List, you will replace any existing data that exists for that attribute.

Note: This is the only time you need to use double quotes around a UOM that is more than one word.

Appendix B

Changes to NetWORKS Strategy objects since 6.1

This section describes the changes made to the NetWORKS Strategy objects since version 6.1. You need this information in order to adjust any input files you were using in the previous version to run the Data Import and Data Export processes.

Overview

As a result of the new features added to NetWORKS Strategy in version 6.2, new attributes and objects were added to the database. In addition, changes were made to add attributes to existing objects. If you have standard input files that you were using with the Data Import, Data Export, or Delete Data processes, you must review those files to ensure that they will function properly in the new version.

New Strategy objects

The objects in Table 29 were added to Strategy in version 6.2.

Changes to Strategy objects

Table 30 shows the changes to existing objects in version 6.2.

Table 29: New Strategy objects in version 6.2

Object name Referenced by For more information, see. . .

Service Levels Location, SKU “Service Levels” on page 131

Table 30: Changes to Strategy objects in version 6.2

Display name Import/export nameAdded/ Deleted/ Changed

Data type For more information, see. . .

Location



Added QtyCalendar “Location (spLocation)” on page 92



ServiceLevelsEnabled Added Boolean

Service Levels Name

ServiceLevelSet Added string

SKU



Added QtyCalendar “SKU (spSKU)” on page 138


ServiceLevelsEnabled Added Boolean

Service Levels Name

ServiceLevelSet Added string

Table 30: Changes to Strategy objects in version 6.2 (continued)

Display name Import/export nameAdded/ Deleted/ Changed

Data type For more information, see. . .

Index

Symbols

%Constraint(SKUReqirement) 160(SKURequirement) 158

%Constraint enabled(SKURequirement) 158, 160

A

Accumulation Period(Tiered Cost/Price) 164

Accumulation Period Type(Tiered Cost/Price) 165

Acrobat, Adobe Reader 6Actual Utilization

(ReusableResource) 120, 124Always commit on new object type 26attribs.txt 65Average Actual utilization

(ReusableResource) 120

B

-b parameter 64Basics and Beyond 7Batch

(Tiered Cost/Price) 164, 166Batch Cost

(Tiered Cost/Price) 168Boolean 173Break Quantity

(Tiered Cost/Price) 165, 168Buy Process 110

C

-c parameter 64Calculated Lead Time

(MakeProcess) 97, 98(MoveProcess) 101, 102(PurchaseProcess (Buy or Sell Process))

110, 112Calculation Method

(Tiered Cost/Price) 164, 166

calendar 67calendar utility 63, 64calendars 63Capacity calendar

data type 173Category

(PlanMetrics) 108Code

(Location) 92comment row 10complex attributes

importing and exporting 15updating 19

complex objects, importing and exporting 14Constraint penalty

(SKURequirement) 160Constraint% unmet amount

(SKURequirement) 158, 160conventions in this manual 4Conversion factor 173Cost

(PlanMetrics) 108(ReusableResource) 120, 124

Cost (to buy)(SKU) 138, 142, 144

Cost per UOM(ReusableResource) 120

Cost/Price Type(PurchaseProcess (Buy or Sell Process))

110, 112(ReusableResource) 124(SKU) 138, 144

Costing/Pricing(ReusableResource) 120, 124(SKU) 138, 144

CostPriceType(ReusableResource) 120

creating objects, using Data Import 21Currency unit of measure

(Tiered Cost/Price) 164, 167CurrencyUofM

(Tiered Cost/Price) 164Customer

(Location) 95


D

-d parameter 64Data export

about 9overview 32running process 36Using SQL to export data 38

Data importabout 9creating versus updating objects 21importing a file into a spreadsheet 39overview 20running the data import process 25tips on creating input file 11, 37

data row 10data selections

using to delete objects 29using to export data 35using to update objects 23

Data transferusing implicitly Connect SKUs 105

Data type 77boolean 173capacity calendar 173conversion factor 173date/time 173decimal 174duration 174integer 174interval 174list 174, 177list of values 174overview 173Qty 174rate 175string 175

Date/timeformat for 173specifying 176specifying in different locales 13

DblCalendardata type 174

DblCalendar attributesformatting 15

updating 19DC

(Location) 95Decimal 174Default Currency Unit of Measure

(Lane) 84Default Currency UofM

(Lane) 86Default Currency UOM

(Location) 92, 93Default Duration

(ReusableResource) 120, 124Default Lane

(Lane) 84, 86Default Lead Time Duration

(ReusableResource) 120Default Lead Time Offset

(ReusableResource) 120Default Offset

(ReusableResource) 120, 124Default Unit of Measure

(Item) 81(ReusableResource) 120, 124(SKU) 138

Default UOM(ReusableResource) 120(SKU) 144

DefaultCurrencyUofM(Lane) 84

DefaultLT Duration(ReusableResource) 120

DefaultLTOffset(ReusableResource) 120

Deleting dataabout 9, 28running the process 30

Deleting objects for SCNrespecting dependencies 79

Demander(ResourceRequirement) 117, 118(SKURequirement) 158, 159

Demanding Supply Node(ResourceRequirement) 117

DemandMet(SKU) 141

Index 183

Description(Item) 81, 82(Lane) 84, 86(Location) 92, 93(PlanMetrics) 108(ReusableResource) 120, 124(SKU) 138, 144(SourcingGroup) 162(Tiered Cost/Price) 164, 167

Destination Location(Lane) 84, 86

Destination SKU(MoveProcess) 101, 103(PurchaseProcess (Buy or Sell Process))

110, 113DestLocation

(Lane) 84DestSKU

(MoveProcess) 101(PurchaseProcess (Buy or Sell Process) )

110Display name 77documentation

Basics and Beyond 7manuals 5online help 6Readme 7

Double Calendarformatting 15updating 19

DS/MU name 77Duration

(ResourceRequirement) 117, 118data type 174

E

-e parameter 64Entire Time Horizon

(Location) 92, 93(SKU) 138, 144

errorsduring Data Import 24, 27header row not specified 27, 32, 37when deleting data 32

Exceeds Any Max Constraint(ReusableResource) 124(SKU) 138, 145

Executions Completed(MakeProcess) 97, 98, 99(MoveProcess) 101, 103(PurchaseProcess (Buy or Sell Process))

110, 113Executions Started


110, 113exporting

all attributes 34data 32data, overview 9selected attributes 33

Exporting transportation resources for TM 59

F

-f parameter 64Fixed Costs

(Location) 92, 94(MakeProcess) 97, 99(MoveProcess) 101, 103(PurchaseProcess (Buy or Sell Process))

110, 114(ReusableResource) 120, 125

Fixed Costs Enabled(Location) 92, 94(MakeProcess) 97, 99(MoveProcess) 101, 103(PurchaseProcess (Buy or Sell Process))

110, 114(ReusableResource) 121, 125

-force parameter 64

G

Group Type(SourcingGroup) 162

Grouping(Tiered Cost/Price) 164, 167


GroupStringsVec(PlanMetrics) 108

H

-h parameter 64Has Executions

(MakeProcess) 97, 99(MoveProcess) 103(PurchaseProcess (Buy or Sell Process))

110, 114Has Met Demand

(SKU) 138, 145Has Unmet Demand

(SKU) 138, 145Has Utilization

(ReusableResource) 125header row 10help

online, glossary 6online, searching for 6online, using 6Product Support 8

I

Implicitly Connect SKUs(Lane) 84, 87

ImplicitlyConnectNow(Lane) 84, 86, 90

Import/export name 77importing

data, overview 9data, running the process 25

importing objects for NetWORKS Strategyrespecting dependencies 78

Include Dest as Source(SKU) 138

Include Destination(Location) 92(SKU) 138

Include Destination as Source(Location) 94(SKU) 145(SourcingGroup) 162, 163

Include Location in Group(SourcingGroup) 162, 163

IncludeDestAs Source(Location) 92

Independent Demand(SKU) 138, 145

Independent Demand Constraint(SKU) 138, 139

Independent Demand Enabled(SKU) 139, 146

Independent Demand Penalty(SKU) 139, 146

Independent Demand Unmet Amount(SKU) 139, 146

Independent DemandStatusSKU) 139

Independent DemandUnmet(SKU) 139

Inflow Constraints(SKU) 140, 141

Input filescreating for Data import/export/delete 9tips on creating 37tips on creating for Data import/export/delete

11using SQL 38

input, specifying 4Integer 174interval

formatting 174specifying 176

Is Group Enabled(SourcingGroup) 162, 163

IsCumulative(Tiered Cost/Price) 164

IsCustomer(Location) 92

IsDC(Location) 92

IsGrouped(Tiered Cost/Price) 164

IsPlant(Location) 92

IsStorable(Item) 81

Index 185

IsSupplier(Location) 92

Item(SKU) 139, 146attributes 81importing and exporting 82overview 81

L

Label(Lane) 84, 88(MakeProcess) 97(MoveProcess) 101(PurchaseProcess (Buy or Sell Process))

111(ReusableResource) 121, 125

Laneattributes 84importing and exporting 89overview 84

Latitude(Location) 92, 94

Lead Time(MakeProcess) 97, 99(MoveProcess) 101, 104(PurchaseProcess (Buy or Sell Process))

110, 114Lead Time Enable

(MakeProcess) 97(MoveProcess) 101, 104(PurchaseProcess (Buy or Sell Process))

110, 114Lead Time Requirement

(Service Levels) 131, 132LeadTime Duration

(ResourceRequirement) 117LeadtimeOffset

(ResourceRequirement) 117level-slotted 67List attributes

formatting 174updating 19, 178

List of values 174locales, specifying dates and numbers for 13Location

(SKU) 139, 147attributes 92importing and exporting 96overview 92

Location Code(Location) 92, 94

Location Type(Location) 92, 95

Location/Lane(ReusableResource) 121, 125

Longitude(Location) 92, 95

M

MakeProcess 97manucalendarutils 63, 64Manufactured

(SKU) 139, 147Max OH

(SKU) 150Max Prebuild Periods

(Item) 81, 82Max Sources

(SourcingGroup) 162, 163Max Sourcing Enable

(Location) 95Max. number of exceptions to process 31max_time 176MaxCapacity Status

(Lane) 84(ReusableResource) 121

MaxCapacity Unmet(Lane) 85(ReusableResource) 121

MaxDemand(SKU) 139

MaxDemand Penalty(SKU) 139

MaxDemand Status(SKU) 139


MaxDemand Unmet(SKU) 140

Maximum Capacity(Lane) 84, 88(ReusableResource) 121, 126

Maximum Capacity Enabled(Lane) 84, 88(ReusableResource) 121, 126

Maximum Demand(SKU) 139, 147

Maximum Demand Enabled(SKU) 139, 147

Maximum Demand Penalty(SKU) 139, 148

Maximum Demand Unmet Amount(SKU) 140, 148

Maximum Inflow Amount(SKU) 140, 148

Maximum Inflow Enabled(SKU) 140, 148

Maximum Inflow Penalty(SKU) 140, 148

Maximum Inflow Unmet Amount(SKU) 140, 148

Maximum Onhand(SKU) 140, 149

Maximum Onhand Enabled(SKU) 140, 149

Maximum Onhand Penalty(SKU) 140, 149

Maximum Onhand Unmet Amount(SKU) 140, 150

Maximum Outflow Amount(SKU) 140, 150

Maximum Outflow Enabled(SKU) 141, 150

Maximum Outflow Penalty(SKU) 141, 150

Maximum Outflow Unmet Amount(SKU) 141, 150

Maximum Sources(Location) 93, 95(SKU) 141, 150

MaxInflow(SKU) 140

MaxInflowPenalty(SKU) 140

MaxInflowStatus(SKU) 140

MaxInflowUnmet(SKU) 140

MaxOH(SKU) 140

MaxOHPenalty(SKU) 140

MaxOHStatus(SKU) 140

MaxOHUnmet(SKU) 140

MaxOutflow(SKU) 140

MaxOutflow Penalty(SKU) 141

MaxOutflow Status(SKU) 141

MaxOutflow Unmet(SKU) 141

MaxSources(Location) 93(SKU) 141

Met Demand Amount(SKU) 141, 150

min_time 176MinCapacity

(Lane) 84MinCapacity Status

(Lane) 85MinCapacity Unmet

(Lane) 85(ReusableResource) 122

Minimum Capacity(Lane) 88(ReusableResource) 121, 126

Minimum Capacity Enabled(Lane) 85, 89(ReusableResource) 121, 126

Minimum Inflow Amount(SKU) 141, 151

Minimum Inflow Enabled(SKU) 141, 151

Index 187

Minimum Inflow Penalty(SKU) 141, 151

Minimum Inflow Unmet Amount(SKU) 141, 151

Minimum Outflow Amount(SKU) 141, 151

Minimum Outflow Enabled(SKU) 141, 151

Minimum Outflow Penalty(SKU) 142, 152

Minimum Outflow Unmet Amount(SKU) 142, 152

MinInflow(SKU) 141

MinInflowPenalty(SKU) 141

MinInflowStatus(SKU) 141

MinInflowUnmet(SKU) 141

MinLeadTime(MakeProcess) 97(MoveProcess) 101(PurchaseProcess (Buy or Sell Process))

110MinOutflow

(SKU) 141MinOutflow Penalty

(SKU) 142MinOutflow Unmet

(SKU) 142MinOutflowStatus

(SKU) 141multiple objects

specifying using wildcards 12updating 23

N

-n parameter 64Name

(Item) 81(Lane) 84, 85

(Location) 92, 93(MakeProcess) 97, 98(MoveProcess) 101, 102(PurchaseProcess (Buy or Sell Process))

110, 112(ResourceRequirement) 117, 118(ReusableResource) 120, 123(Service Level Set) 131, 132(SKU) 138, 143(SKURequirement) 158, 159(SourcingGroup) 162(Tiered Cost/Price) 164, 165

NamedCalendarimporting and exporting 106overview 106

Needs Demand Forecast(SKU) 142, 152

NetLINK 8NetWORKS 3NetWORKS Strategy

maintaining calendar attributes 63NetWORKS Strategy Initial On-hand

(SKU) 154NetWORKS Transport

exporting transportation resources from NetWORKS Strategy 59

generating cost data from Transport 60importing carrier cost data from 59importing carrier cost data from Transport to

Strategy 59normal-slotted 67NumAccumulationPeriods

(Tiered Cost/Price) 164Number of Accumulation Periods

(Tiered Cost/Price) 166Number of Executions


111, 115Numbers

specifying in different locales 13


O

-o parameter 63Object

SourcingGroup 162Objects

changes since 6.1 179Item 81Lane 84list of 12Location (spLocation) 92MakeProcess 97MoveProcess 101NamedCalendar 106overview 77PlanMetrics 108PurchaseProcess 110ResourceRequirement 117ReusableResource (spReusableResource)

120Service Levels 131SKU (spSKU) 138SKURequirement 158Tiered Cost/Price 164

Object-typeslist of 12

Offset(ResourceRequirement) 117, 118

Optimal Onhand(SKU) 142, 152

OptimalOH(SKU) 142

Outflow Constraints(SKU) 140, 141, 142

Outflow Planned Executions(MakeProcess) 97(PurchaseProcess (Buy or Sell Process))

110OutflowPlanned Execs

(MoveProcess) 101Output SKU

(MakeProcess) 97, 100OverPercentage Amount

(SKURequirement) 158

Overridden Cost (to buy)(PurchaseProcess (Buy or Sell Process))

111(PurchaseProcess (Buy Process)) 115

Overridden Price (to sell)(PurchaseProcess (Buy or Sell Process))

111(PurchaseProcess (Sell Process)) 115

Overutilization Amount(Lane) 85, 89(ReusableResource) 121, 126

Overutilization Penalty(Lane) 85, 89(ReusableResource) 121, 126

P

Per UOM Cost/Price(Tiered Cost/Price) 168

Percent Constraint(SKURequirement) 158

Percent Constraint enabled(SKURequirement) 158, 160

PercentageConstraint(SKURequirement) 158

PercentageConstraintEnabled(SKURequirement) 158

PercentageConstraintPenalty(SKURequirement) 158

PerUOMCostPrice(Tiered Cost/Price) 165

PlanMetricsattributes 108importing and exporting 108

Planned Executions(MakeProcess) 97(MoveProcess) 101(PurchaseProcess (Buy or Sell Process))

111Plant

(Location) 95Price

(SKU) 138, 142Price (to sell)

(SKU) 142, 152

Index 189

ProcessMake 97Move 101Purchase 110

Process Label(MakeProcess) 97, 100(MoveProcess) 101, 104(PurchaseProcess (Buy or Sell Process))

111, 115Product Support, contacting 8PurchaseProcess (Buy or Sell Process)

attributes 110importing and exporting 116

Q

Qtydata type 174

QtyCalendardata type 175

QtyCalendar attributesformatting 16updating 19

QtyConversion(Item) 81data type 175

Quantity Calendarformatting 16updating 19

Quantity unit of measure(Tiered Cost/Price) 164, 167

QuantityUofM(Tiered Cost/Price) 164

Quotes 175

R

Ratedata type 175

RateCalendardata type 175

RateCalendar attributesformatting 17updating 19

Raw Material(SKU) 142, 152

Readme 7Reporting calendar

importing and exporting 106Requirement

(ResourceRequirement) 117, 118(SKURequirement) 158, 161

ResLoc(ReusableResource) 121

Resource label(ReusableResource) 127

Resource Type(ReusableResource) 121, 127

ResourceRequirementattributes 117definition 117

ResType(ReusableResource) 121

Reusable Resource 120(ResourceRequirement) 117, 118importing and exporting 128

S

-s parameter 64Safety Stock

(SKU) 142, 152Safety Stock Enabled

(SKU) 142, 153Safety Stock Penalty

(SKU) 142, 153Safety Stock Unmet Amount

(SKU) 142, 153SafetyStockStatus

(SKU) 142SafetyStockUnmet

(SKU) 142-Saturday parameter 64scndelete.txt 29scnexport.txt 32, 33scnimport.txt 21selecting objects

using attributes other than name 24, 30, 35


Sell Process 110Separator character 10, 175server

manager processes 63Service Level Set

(Location) 96(SKU) 154

Service Levels 131(Service Level Set) 132exporting 133importing 133

Service Levels Achieved(Location) 93, 95(SKU) 142, 153

Service Levels Enabled(Location) 93, 96(SKU) 142, 154

Service Levels Name(Location) 93(SKU) 142

Service Percentage(Service Levels) 131, 132

ServiceLevels AchievedCal(Location) 93(SKU) 142

ServiceLevelsEnabled(Location) 93(SKU) 142

ServiceLevelSet(Location) 93(SKU) 142

SKUoutput for Make Process 97source SKU for Move Process 102

SKU (spSKU) 138SKURequirement

attributes 158definition 158importing and exporting 161

Source Location(Lane) 85, 89

Source SKU(MoveProcess) 102, 104(PurchaseProcess (Buy or Sell Process))

111, 115

Sourcing Groupattributes 162overview 162

spLocation 92spReusableResource 120spSKU 138Storable

(Item) 81, 82Storage Resource

(SKU) 139, 154Strategy Initial On-hand

(SKU) 143String 175-Sunday parameter 64Supplier

(Location) 95(SKURequirement) 158, 160

T

Target On-hand(SKU) 143, 155

Target On-hand Constraint(SKU) 143SKU object 143

Target On-hand Enabled(SKU) 143

Target On-hand Penalty(SKU) 143, 155

Target On-hand Status(SKU) 155

Target On-hand UnMet(SKU) 156

Target On-hand Variance Amount(SKU) 143

TargetOH(SKU) 143

TargetOHStatus(SKU) 143

TargetOHUnmet(SKU) 143

Tax/Tariff(MoveProcess) 102, 105(PurchaseProcess (Buy or Sell Process))

111, 116

Index 191

Tax/Tariff Enable(PurchaseProcess (Buy or Sell Process))

111, 116Tax/Tariff Enabled

(MoveProcess) 102, 105Thruflow Constraints

(Lane) 84, 85(ReusableResource) 121(SKU) 140, 142ReusableResource object 121, 122

Tiered Cost/Price 164(PurchaseProcess (Buy or Sell Process))

111, 116(ReusableResource) 122, 127(SKU) 143, 156exporting 169importing 168

Tiered Price Structure(Tiered Cost/Price) 165

TieredCostPrice(ReusableResource) 122

Tiers(Tiered Cost/Price) 164, 167

Tier-Tiers 165Type

(ReusableResource) 127Type, Batch

(Tiered Cost/Price) 168Type, per UOM

(Tiered Cost/Price) 168

U

Under Any Min Constraint(ReusableResource) 122, 127(SKU) 143, 156

UnderPercentage Amount(SKURequirement) 158

Underutilization Amount(Lane) 85, 89(ReusableResource) 122, 128

Underutilization Penalty(Lane) 85, 89

(Reusable esource) 122(ReusableResource) 122, 128

Unit of Measurecustomizing 177default values 175

Unit Price(SKU) 138, 142

UOMdata type 175

updating objectsusing Data Import 22using data selections 23

Use Entire Time Horizon(SourcingGroup) 162, 163

UseEntireTime Horizon(Location) 92(SKU) 138

User-defined Conversions(Item) 81, 82

Utilization(ReusableResource) 120

V

valuesoptional 4repeating 5

variables, specifying 5Violates Supplying % Constraint

(SKU) 143, 156

W

wildcardsusing to delete multiple objects 29using to export multiple attributes 34using to export multiple objects 34using to specify multiple objects 12using to update objects 23

Z

ZeroUtilBatchCost(Tiered Cost/Price) 164

reference manual - umsl

Documents