dmf_ref_guide.pdf

Reference Guide JDA® Demand Management Foundation Release 8.1.0.0

JDA Software Group, Inc.

Legal notice Rights to the content of this document

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

Printed in the United States of America.

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

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

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

Modifications to the contents of this document

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

Rights to the functionality of this document

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

Patents

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

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

Europe Patent No. 0861474 (E) Taiwan Patent No. 161120 Taiwan Patent No. I222584 Europe Patent No. 0861474 (UK) Taiwan Patent No. 161181 Taiwan Patent No. I222585 German Patent No. 10195871 Taiwan Patent No. 161494 Taiwan Patent No. I222586 German Patent No. 69507020.7 Taiwan Patent No. 163816 Taiwan Patent No. I225208 German Patent No. 69507021 Taiwan Patent No. 164194 Taiwan Patent No. I225209 German Patent No. 69508931.5 Taiwan Patent No. 170630 Taiwan Patent No. I225605 German Patent No. 69508932 Taiwan Patent No. 172458 Taiwan Patent No. I227425 German Patent No. 69601151 Taiwan Patent No. 191262 Taiwan Patent No. I227427 German Patent No. 69601151.4 Taiwan Patent No. 196235 Taiwan Patent No. I231432 German Patent No. 69601152 Taiwan Patent No. 199069 Taiwan Patent No. I234724 German Patent No. 69601152.2 Taiwan Patent No. 200370 Taiwan Patent No. I235318 German Patent No. 69601207 Taiwan Patent No. 205817 Taiwan Patent No. I238957 German Patent No. 69601207.3 Taiwan Patent No. 283220 Taiwan Patent No. I239461 German Patent No. 69601208.1 Taiwan Patent No. 371338 Taiwan Patent No. I241800 German Patent No. DE10195968 Taiwan Patent No. 384430 Taiwan Patent No. I242952 Taiwan Patent No. 100569 Taiwan Patent No. 425517 Taiwan Patent No. I251760 Taiwan Patent No. 108409 Taiwan Patent No. 435034 Taiwan Patent No. I251996 Taiwan Patent No. 110827 Taiwan Patent No. 440780 Taiwan Patent No. I258090

http://jda.com/JDAPatents


Taiwan Patent No. 113331 Taiwan Patent No. 451145 Taiwan Patent No. I266251 Taiwan Patent No. 122508 Taiwan Patent No. 469405 Taiwan Patent No. I271617 Taiwan Patent No. 127358 Taiwan Patent No. 490625 Taiwan Patent No. I284847 Taiwan Patent No. 129860 Taiwan Patent No. 493122 Taiwan Patent No. I285339 Taiwan Patent No. 133048 Taiwan Patent No. 498236 Taiwan Patent No. I285342 Taiwan Patent No. 134299 Taiwan Patent No. 498247 Taiwan Patent No. I286709 Taiwan Patent No. 136847 Taiwan Patent No. 502183 Taiwan Patent No. I290290 Taiwan Patent No. 137376 Taiwan Patent No. 504640 Taiwan Patent No. I299837 Taiwan Patent No. 139353 Taiwan Patent No. 504915 Taiwan Patent No. I314297 Taiwan Patent No. 139680 Taiwan Patent No. 509869 Taiwan Patent No. I314298 Taiwan Patent No. 140308 Taiwan Patent No. 517193 Taiwan Patent No. I317103 Taiwan Patent No. 146038 Taiwan Patent No. 544598 Taiwan Patent No. M377652 Taiwan Patent No. 154327 Taiwan Patent No. 544599 Taiwan Patent No. NI-158220 Taiwan Patent No. 154338 Taiwan Patent No. 561424 Taiwan Patent No. NI-162685 Taiwan Patent No. 154339 Taiwan Patent No. 594530 Taiwan Patent No. NI-166322 Taiwan Patent No. 155489 Taiwan Patent No. 80326 Taiwan Patent No. NI-167148 Taiwan Patent No. 155708 Taiwan Patent No. 93090 Taiwan Patent No. NI-182787 Taiwan Patent No. 157467 Taiwan Patent No. I221578 Taiwan Patent No. NI-182974 Taiwan Patent No. 159609 Taiwan Patent No. I221978


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

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

mailto:[email protected]


Table of Contents Chapter 1. Documentation information ............................................................................ 1

Help information .......................................................................................................... 1 Installation/administration information ........................................................................... 1 Database information ................................................................................................... 1 Release Notes ............................................................................................................. 1 Get additional help from JDA ......................................................................................... 2

Chapter 2. The SCPO database (technical documentation) .............................................. 4 Predefined pages ......................................................................................................... 4 Database conventions .................................................................................................. 4 Information about tables .............................................................................................. 4

Applications that include the table ......................................................................... 4 Primary key columns in the table .......................................................................... 4 Parent/Child tables and columns (foreign keys) ...................................................... 5

Information about columns ........................................................................................... 5 Primary key columns ........................................................................................... 5 Applications that use the columns ......................................................................... 5 Datatype ........................................................................................................... 6 Valid values ....................................................................................................... 8 Default values .................................................................................................... 8

Paths between tables ................................................................................................... 9

Chapter 3. Tables in the database (technical documentation) ....................................... 10 AllocProfile ....................................................................................................... 11 AllocProfileCategory .......................................................................................... 12 AllocProfileLib ................................................................................................... 13 AllocProfileValues .............................................................................................. 14 AVSGravesParam .............................................................................................. 15 AVSGravesStats ............................................................................................... 18 Cal .................................................................................................................. 21 CalData ........................................................................................................... 26 CalDataExpanded.............................................................................................. 34 CausalFactor .................................................................................................... 35 CausalFactorType ............................................................................................. 36 CausalFactorValue ............................................................................................ 37 Collection_Info ................................................................................................. 39 CrostonParam .................................................................................................. 40 CrostonStats .................................................................................................... 43 Currency .......................................................................................................... 46 CurrencyProfile ................................................................................................. 47 CurrencyProfileVal ............................................................................................. 48 DBParam ......................................................................................................... 50 DDEProfile ....................................................................................................... 56 DFU ................................................................................................................ 58 DFUAllocProfileMap ........................................................................................... 72 DFUAttachRateNorm ......................................................................................... 74 DFUAttachRateRelation ...................................................................................... 75 DFUAttrib ......................................................................................................... 76 DFUCausalFactor .............................................................................................. 77 DFUCoef .......................................................................................................... 79 DFUDDEMap ..................................................................................................... 81 DFUDepDmdFcst ............................................................................................... 83 DFUDepDmdHist ............................................................................................... 84 DFUException ................................................................................................... 85


DFUExternalFcst ............................................................................................. 110 DFUMaintCopyDFU .......................................................................................... 112 DFUMap ......................................................................................................... 116 DFUMapFcstProfile .......................................................................................... 122 DFUMovingEventMap ....................................................................................... 124 DFUNPIRelation .............................................................................................. 125 DFUProjDraftStatic .......................................................................................... 127 DFUProjStatic ................................................................................................. 130 DFUTOE3FCST ................................................................................................ 133 DFUToEPFcst .................................................................................................. 135 DFUToItxFcst ................................................................................................. 136 DFUToSKU ..................................................................................................... 137 DFUToSKUFcst................................................................................................ 140 DFUTotalVol ................................................................................................... 142 DFUToWFMFcst ............................................................................................... 143 DFUView ........................................................................................................ 144 DmdGroup ..................................................................................................... 148 DmdUnit ........................................................................................................ 149 Event ............................................................................................................ 152 EventType ..................................................................................................... 154 Fcst ............................................................................................................... 155 FcstDraft ....................................................................................................... 159 FcstPerfStatic ................................................................................................. 162 FittedHist ....................................................................................................... 168 ForecastRecordImport ..................................................................................... 171 Hist ............................................................................................................... 173 HistFcst ......................................................................................................... 175 HistFcstEvents ................................................................................................ 178 HistStream ..................................................................................................... 180 HoltWintersParam ........................................................................................... 181 HoltWintersStats ............................................................................................. 184 Item.............................................................................................................. 187 LewandowskiParam ......................................................................................... 194 LewandowskiStats .......................................................................................... 199 LewFactor ...................................................................................................... 203 LewFactorCategory ......................................................................................... 204 LewFactorLibMap ............................................................................................ 205 LewFactorLibrary ............................................................................................ 206 LewFactorValue .............................................................................................. 207 LibraryCategoryMap ........................................................................................ 208 LinRegParam .................................................................................................. 209 LinRegStats .................................................................................................... 216 Loc ............................................................................................................... 221 LocType ......................................................................................................... 226 Map .............................................................................................................. 227 Mask ............................................................................................................. 228 MaskData ...................................................................................................... 229 MeanValueAdj ................................................................................................ 230 Model ............................................................................................................ 232 MovingAvgParam ............................................................................................ 234 MovingAvgStats .............................................................................................. 236 MovingAvgWgts .............................................................................................. 238 MovingEvent .................................................................................................. 240 MovingEventData ............................................................................................ 241 NPISequence .................................................................................................. 242 NPISequenceDetail .......................................................................................... 243 NPIValidDFU ................................................................................................... 245 PriceProfile ..................................................................................................... 246 PriceProfileVal ................................................................................................ 247


Profile ........................................................................................................... 248 ProfileData ..................................................................................................... 249 SeasonError ................................................................................................... 250 SeasonLib ...................................................................................................... 252 SeasonProfile ................................................................................................. 253 SeasonProfileValues ........................................................................................ 255 SKU .............................................................................................................. 257 SLCCurve ....................................................................................................... 268 SLCCurveAttrib ............................................................................................... 269 SKUFactsData ................................................................................................ 270 SLCParam ...................................................................................................... 271 SLCStats ........................................................................................................ 273 SmoothSeason ............................................................................................... 275 SubEvent ....................................................................................................... 277 Target ........................................................................................................... 279 TargetDFUMap ................................................................................................ 280 WDDArea ....................................................................................................... 281 WDDCategory................................................................................................. 282 WDDCategoryAreaMap .................................................................................... 283 WDDData ....................................................................................................... 284 WFMFcstStruct ............................................................................................... 285 Table Relationships ......................................................................................... 286

Chapter 4. Processes part 1: input and output tables .................................................. 366

Chapter 5. Processes part 2: input and output tables .................................................. 371

Index ........................................................................................................................... 376

Documentation information

Chapter 1. Documentation information The following documentation is included with this application.

Help information Supply Chain Planning and Optimization (SCPO) applications contain online HTML help that guides you through the user interface. Each page has its own context-sensitive help topic that describes the purpose of each component of the page. In addition, user information is included to describe high-level processes and procedures. You can access the OnLine Expert for a specific page by clicking Help at the top of the page.

The SCPO suite of applications includes some components and utilities that are used by multiple applications as well as components that are specific to a single application. When using SCPO applications, you must be aware of your location in the system as it determines the help text to which you have access. For example, if you are working in a Flexible Editor page, which is part of the basic SCPO architecture, and you click Help, you can access general help information for common SCPO components. In this help, you can find information about common features, such as Flexible Editor, calendar management, and import/export. This help also contains definitions for each database table. However, it does not provide information about specific JDA Demand or JDA Fulfillment features, such as forecasting, planning, distribution, or allocation.

To access information about application-specific features, you must access the help for that application. To do so, open the appropriate page in the application. If you are unsure of the page to use, open any application-specific page, such as Plan Analysis for JDA Fulfillment or Demand Workbench for JDA Demand, and click Help on that page. The context-sensitive help topic for the page you are on is displayed in the right frame and the table of contents for the entire application help system is displayed in the left frame. You can then use the table of contents, search, or index to find the application-specific information.

Installation/administration information The Supply Chain Planning and Optimization Installation/Administration Guide provides information about the architecture of Supply Chain Planning and Optimization, step-by-step instructions to install and configure the server and applications, instructions to create or migrate your database, and information to customize and administer the applications after they are installed.

SCPO guides are available online in Portable Document Format (PDF) format. When you install SCPO, you can access the guides from the <install_dir>\config\doc\guides\en directory, the JDA program group on the Windows Start menu, or from the installed directory structure.

Database information The application Reference Guide contains detailed information about tables and columns in the SCPO schema. These documents are in PDF format and are located in the <install_dir>\config\doc\guides\en directory. In addition, the definitions for the tables used by each JDA application are included in the application OnLine Expert.

Release Notes The Supply Chain Planning and Optimization (SCPO) Release Notes contains information that pertains to all JDA applications included in SCPO. In addition, individual product Release Notes are available for each JDA application for which you are licensed.

The Release Notes provide the following information:

JDA Demand Management Foundation Reference Guide 1 © 1997 - 2014 JDA Software Group, Inc.- Confidential


• Version-specific installation notes, hardware and software requirements, open-source software, and third-party software components necessary to install the application.

• Summary of the new features and enhancements in the application.

• Resolved issues in the software.

• Known issues in the software and, if available, workarounds for the issues.

The General SCPO Release Notes is named release_notes_generalSCPO.pdf. File names for individual product Release Notes are in the format release_notes_<appname>.pdf. For example: release_notes_esp.pdf. You can access Release Notes by opening the appropriate file in the doc\ directory. Readme files are also available from the JDA program group on the Windows Start menu and from the installed directory structure.

Get additional help from JDA In addition to the provided documentation, many additional resources are available to help you understand and work with your JDA applications.

• JDA Support Services

JDA Support Services enhances your experience with JDA solutions throughout the lifetime of your relationship with JDA Software. Support Services provides many key values, including:

• Worldwide support provided locally for issue resolution, including functional and technical assistance

• Defined service levels and proactive escalation paths

• Special Interest Group (SIG) membership

• Access to new software releases

• Access to the JDAUser website (http://www.jdauser.com), which provides:

• Self-service user administration

• Online knowledge base

• Online case management and user communities

• Product documentation and release announcements

• JDA Education Services

To enhance the return on your JDA solution investment, JDA Education Services provides options to optimize your experience and knowledge. JDA Education Services offers high-quality training with e-learning and instructor-led training opportunities. JDA Education Services also offers the JDA Certification Program, which defines a curriculum that maximizes your knowledge and qualifications for a specific job. Certification programs employ a blend of learning methods that end with an industry-recognized exam. See the JDALearn website (http://www.jdalearn.com) for more information.

• JDA Consulting Services

JDA Consulting Services provides a broad range of services, including:

• Process definition and improvement

• Change management

• Program and project management

• Functional and technical consulting

• Performance engineering

• Solution delivery


http://www.jdauser.com/

http://www.jdalearn.com/


Every solution deployment begins with the JDA Enterprise Methodology, which encompasses both technology and implementation expertise. JDA Consulting Services works collaboratively with you to help your business realize the results you need, on time and on budget.

• JDA Cloud Services

JDA Cloud Services enables you to achieve faster deployment, rapid time to value, investment protection, and improved cost structure with JDA supply chain solutions. This allows you to focus on your core business while JDA manages the JDA applications. Areas of specialty include:

• Solution availability management

• Performance management

• Issue resolution

• Change management

• Security management

• Optimization and analytics management

For more information on any of the JDA Services, see the JDA Services website (http://www.jda.com/services/services/).


http://www.jda.com/services/services/

The SCPO database (technical documentation)

Chapter 2. The SCPO database (technical documentation) The Reference Guide contains detailed information about the tables and columns in the SCPO schema used by this application, as well as other information about displaying and working with your data.

Predefined pages Your system includes a predefined Flexible Editor page for most tables in the SCPO schema. These pages enable you to work with and review data in your database. You can use these pages just as they are or tailor them to meet your needs.

To access these pages, open the Directory from the Welcome page of the JDA applications. The ability to access these pages is controlled by your Common Security Administration privileges.

Database conventions This section provides detailed information about the SCPO schema, the database used with your Supply Chain Planning and Optimization (SCPO) applications. It includes the following topics:

• Information about tables (on page 4) explains the categories of information provided for eachtable.

• Information about columns (on page 5) explains the kinds of information presented for eachcolumn within the tables.

• Paths between tables (on page 9) explains the paths from each table to other tables. When thesystem allows you to use data from multiple tables, or to navigate between two tables, there issaid to be a path between those tables.

Information about tables At the beginning of each table listing is information that applies to the whole table, as explained in the following sections.

Applications that include the table The label "Table included with" at the beginning of each table specifies the JDA applications that include that table.

For example, the JDA Fulfillment/Deployment application is available as an add-on to the JDA Fulfillment/Distribution component. Any table that is included with Fulfillment/Distribution is also included with Fulfillment/Deployment. However, tables that are included with Fulfillment/Deployment are not also included with Fulfillment/Distribution unless the listing specifically says so.

Each column also has an "Included with" label. A column is used by a particular application only if that application is listed as "included with" both the table and the column.

Note: The configuration code controls which JDA applications are installed, and therefore determines what database tables can be used. In Flexible Editor, you can view database tables common to multiple applications, such as JDA Demand and Fulfillment.

Primary key columns in the table Most tables in the database have a primary key—a column or group of columns whose values uniquely identify one row in the table. For each table, the primary keys are identified in the tabular presentation of column information, in the PK column. See Primary key columns (on page 5).



Parent/Child tables and columns (foreign keys) The SCPO schema uses referential integrity, which creates foreign key constraints in the schema and therefore constrains the data you can enter or import. The constraints exist between parent and child tables. Data must exist in the parent table before you can enter it in the child table. For a description of the parent/child relationships within the SCPO schema, see Table Relationships (on page 286).

Information about columns Each table in the database may contain a maximum of 1,000 columns, including system columns and user-defined columns.

Near the beginning of each table description in this guide is a tabular presentation of information about the columns in the table. For each column, the following information is included where it is applicable.

Primary key columns Most tables in the database have a primary key—a column or group of columns whose values uniquely identify one row in the table. For each table, the primary keys are identified in the tabular presentation of column information, in the PK column.

No two rows in a table can have the same combination of values in the primary key columns. For example, the primary key columns in the SKUProjStatic table are Item, Loc, StartDate, and OptionSet. The two rows in the following example have the same value for Item, Location, and OptionSet, but different values for StartDate:

Item Location StartDate OptionSet

16001 LA 4/30/05 3

16001 LA 5/31/05 3

You cannot change the value in a primary key column after it has been set. To change a value in a primary key column, you must delete the row containing that value and add a new row. You can do this manually within the application, or by importing new data.

Caution: Primary key text values are always saved as uppercase. For example, if you run a search with a criterion of loc.loc=New York, New York will not be returned. However, if you change the search criterion to loc.loc=NEW YORK, then NEW YORK will be returned.

Note: Primary key columns with the type SEQUENCE cannot be viewed or edited in Flexible Editor. These columns only appear in import/export files as the last column. When importing, for new rows, use the value negative one (-1) to indicate this row is to be added. If modifying an existing table row, you must use the actual ID value of that row in the import file.

Applications that use the columns In the tabular presentation of column information, the Included with column lists the JDA applications with which that column is included. The following application abbreviations are used:

• DDR: JDA Dynamic Demand Response

• Dmd: JDA Demand

• ESP: Enterprise Supply Planning

• Flowcasting: JDA Flowcasting

• Dmd Decomp: JDA Demand Decomposition



• FF: JDA Fulfillment

• IPO: JDA Inventory Policy Optimization

• MDO: JDA Markdown Optimization

• MP: JDA Master Planning

• PM: JDA Promotions Management

• SP: JDA Strategic Pricing

• PSO: JDA Production and Sourcing Optimization

• Supp: JDA Supply

• TPO: JDA Travel Price Optimization

Each table also has a Table included with label. A column is used by a particular application only if that application is listed in the Included with label for both the table and the column.

Datatype In the tabular presentation of column information, the Datatype column lists the column datatype, which identifies the basic kinds of data stored in that column, such as Text or Integer. The datatype imposes limits on:

• Which characters are valid in columns of that datatype

• The range of valid values (for numeric columns)

For each individual column, the column description may state further restrictions on valid values. For example, a column value may be required to be the name of an existing location, or may have a minimum value of 0.

The following paragraphs explain the purpose of each datatype and specify the characters that are valid for each.

Note: When working in the Flexible Editor in a JDA application, you may be able to change the display format for one column or all columns of a particular datatype. For example, in a Duration column, the format may be changed to display the data in days instead of hours, or in a Decimal column you may limit the number of digits displayed. For detailed information, See OnLine Expert.

Text and Upper_Text Text and Upper_Text columns are character columns of a maximum fixed length, generally used for freeform textual data. The maximum length for a text column is 50 characters.

When you enter a value into an entry field for a text column, the system removes any leading blanks, left-justifies the data, and checks it against the list of invalid characters. The following characters are invalid in some or all applications:

Character Character name Invalid in

" Double quote All applications

\ Backslash SCPO < Less Than symbol SCPO ~ Tilde SCPO

Values in text columns may be in both upper and lower case. Letters in upper_text columns must be upper case.



Boolean A Boolean column represents concepts that typically have only two possible values, such as True and False, or On and Off. A Boolean works like a switch, and the names of many Boolean columns end in the word "Switch."

The valid values for a Boolean column are typically 1 (meaning True or On) and 0 (meaning False or Off). To determine the valid values for a specific column, see the column description in Tables in the database (technical documentation) (on page 10).

Option_Number and Option_Text An option column has a small, fixed set of valid values.

For option_number columns, the valid values in the database are integers. For example, the Type column in the Calendar (on page 21) table is an option_number column whose valid values represent each of the types of calendars you can use. Each option_number column has a specific set of valid values, which are always integers in the database.

Each integer value for an option_number column represents a specific value, which is stated in the column description in Tables in the database (technical documentation) (on page 10). The user interface may display the text of these values, to make it easy to specify the value you want. However, when you import or export option_number data, the integer values are used.

For option_text columns, the valid values are strings of text characters.

Integer An integer column holds numeric values that do not require digits to the right of the decimal point. The range of valid values for integer columns is -2,147,483,647 to +2,147,483,647.

Valid characters for an integer column are 09, commas, and a plus (+) or minus () sign in the first position.

Decimal A decimal column is a numeric column that requires significant digits to the right of the decimal point.

Valid characters for a decimal number column are 0-9, one decimal point (.), commas (,) to the left of the decimal point, and a plus (+) or minus (-) sign in the first position.

The value in a decimal number column can have a maximum of 15 significant digits. The only insignificant digits are zeros that precede the leftmost non-zero digit to the left of the decimal point. On the right side of the decimal point, all zeros are significant unless the value of the entire number is exactly zero.

Date and DateTime A date column holds a calendar date – a combination of month, day, and year. A datetime column holds both a calendar date and clock time (hours and minutes). Times always refer to a 24-hour clock (00:00 to 23:59). For a date or datetime column, valid input characters are 0-9, slash (/), hyphen (-), period (.), and colon (:). If the column format includes any of the options in addition to the date and time, the system automatically calculates their value. Examples of valid date and datetime formats include: YYYY-MM-DD-hh.mm.dd; YYYY-MM-DD hh:mm:dd; MM/DD/YYYY; and MM-DD-YYYY.



The valid date range is January 1, 1971, to January 18, 2038. When you enter a year in the 71-99 range, the system considers it to be in the 1900s. It considers years in the 00-38 range to be in the 2000s. You can enter years in the 39-69 range, but that may produce inconsistent results. A date with a year of 70 is invalid and will result in an "Invalid date" error message. If a blank date is entered, it is stored as 1970-01-01-00:00 in the database.

UNIX counts time in seconds from UTC 00:00:00, January 1, 1970.

Duration A duration column holds a duration of time, expressed as days, hours, and minutes. A duration can be zero, positive, or negative. The valid input characters for durations are 0-9, W, D, H, and M, where:

• W: Weeks

• D: Days

• H: Hours

• M: Minutes

Some properties pages in JDA Demand accept only days. In that case, the text "days" is displayed after the entry field.

URL A URL column contains a Uniform Resource Locator, the World Wide Web address of a site on the Internet.

Sequence Sequence columns are typically identifiers, whose numbers are sequential beginning at 1. The value in a Sequence column is supplied by a database sequence generator.

Valid values The datatype limits which characters are valid for each column. For integer, decimal, and duration columns, the datatype also limits the range of values for the column.

In some integer, decimal, and duration columns, the system does not allow the full range of values associated with the datatype. For example, the FcstDur column in the SKU table is a duration column, but its range of valid values is 1 to 365 days. Column descriptions list any limitations on valid values beyond the limitations imposed by the datatype.

Option_number and option_text columns always have a finite set of valid values, which this chapter lists for each column.

Default values When you add a row to a table, you must provide values for all primary key columns.

For other columns, the system provides an initial value, which this chapter lists. The initial value for text and identifier columns is always blank. After you add a row, you can change the value for most columns that are not required columns.

No initial value is displayed for values that the system always generates.



Paths between tables When the system allows you to use data from multiple tables or navigate between two tables, a path exists between those tables.

For example, in a Flexible Editor page, you can include any column from the primary table. You may also be able to include columns from other tables as listed in the Flexible Editor Properties page. The primary table determines which columns from other tables you can include in a Flexible Editor page. You can include columns from most tables for which both of these conditions are true:

• The primary key columns of the primary table are found in the secondary table.

• The primary key columns of the second table are included in the page.

If the primary table contains the primary key columns for another table, a path exists from the primary table to the other table. For more information on creating Flexible Editor pages, see OnLine Expert.


Tables in the database (technical documentation)

Chapter 3. Tables in the database (technical documentation) This section presents detailed information about the tables and columns in the database that are used by this application.


AllocProfile

AllocProfile Table included with: Demand, Flowcasting

Column name PK Included with Datatype Valid values Default value

ProfileName 1 Dmd, Flowcasting

TEXT

Descr Dmd, Flowcasting

UPPER_TEXT

NumPeriods Dmd, Flowcasting

INTEGER

Category Dmd, Flowcasting

TEXT

Table description The AllocProfile table stores the identifiers which make up the allocation profile. A profile name, number of periods and category make up a complete allocation profile.

Column descriptions ProfileName Name of the allocation profile.

Descr Description for the allocation profile.

NumPeriods The number of periods you want to display for a calender year.

Category Name of the category you want this allocation profile to be stored in.


AllocProfileCategory

AllocProfileCategory Table included with: Demand, Flowcasting


Category 1 Dmd, Flowcasting

TEXT


UPPER_TEXT

Table description The AllocProfileCategory table stores the category and description for the category. Allocation profiles are stored in categories and categories are then stored in libraries.

Column descriptions Category Name of the category.

Descr Description for the category.


AllocProfileLib

AllocProfileLib Table included with: Demand, Flowcasting


LibName 1 Dmd, Flowcasting

TEXT


UPPER_TEXT

Table description The AllocProfileLib table stores the library and description for this library. Allocation profiles are stored in categories and categories are then stored in libraries.

Column descriptions LibName Name of the library.

Descr Description for the library.


AllocProfileValues

AllocProfileValues Table included with: Demand, Flowcasting



TEXT

Period 2 Dmd, Flowcasting

INTEGER

InputVal Dmd, Flowcasting

DECIMAL 0

NormVal Dmd, Flowcasting

DECIMAL 0

Table description The AllocProfileValues table stores the starting values in the InputVal column. To normalize the values so that the sum of the input values equals the period number, the system spreads the input values to equal the correct period total and stores the results in the NormVal column.

Column descriptions ProfileName Name of the allocation profile.

Period The period number against which the input value is applied.

Valid values for Period are 1 or greater.

InputVal Value you specify for the period’s initial allocation profile.

NormVal Normalized value. Calculate Model process distributes the input values proportionally so that the sum of the normalized values equals the period.


AVSGravesParam

AVSGravesParam Table included with: Demand, Flowcasting


DmdUnit 1 Dmd, Flowcasting

TEXT

DmdGroup 2 Dmd, Flowcasting

TEXT

Loc 3 Dmd, Flowcasting

TEXT

Model 4 Dmd, Flowcasting

TEXT

SmoothConstant Dmd, Flowcasting

DECIMAL 0.10

OutlierFactor Dmd, Flowcasting

DECIMAL 4

TrendMethod Dmd, Flowcasting

INTEGER 0

MinSeasonVal Dmd, Flowcasting

DECIMAL 0.0001

UpdateFreqFactor Dmd, Flowcasting

DECIMAL 2

SeasonalitySW Dmd, Flowcasting

BOOLEAN 0

NPITMax Dmd, Flowcasting

DECIMAL 0.0

InitialMeanValue Dmd, Flowcasting

DECIMAL 0

InitMeanOverrideSw

Dmd, Flowcasting

BOOLEAN 0

Table description The AVSGravesParam table contains the parameters for setting the AVS-Graves method.

Column descriptions DmdUnit The demand unit associated with this DFU.

DmdGroup The demand group associated with this DFU.

Loc The location associated with this DFU.

Model The combination of history stream and forecast algorithm to create the forecast.

SmoothConstant JDA Demand Management Foundation Reference Guide 15 © 1997 - 2014 JDA Software Group, Inc.- Confidential

AVSGravesParam

Smoothing constant for updating the absolute smoothed error, signed smoothed error, and smoothed demand size in the AVS-Graves algorithm.

Valid values for Smoothing Constant are 0 to 1. Default value is 0.1.

OutlierFactor The system uses this value to detect periods in which actual demand differs significantly from the statistical model.

The system multiplies Outlier Factor by the initial MADP of the model and then mutliplies by the average history. This number then adds to and subtracts from the average history to create the outlier bands. Outliers are history period values that fall outside of the outlier bands.

Outlier Bands = Average History +/- (Initial MADP * Average History * Outlier Factor)

If you decrease the value of OutlierFactor, the number of outliers increases. If you increase Outlier Factor, the number of outliers decreases.

Valid values for OutlierFactor are greater than or equal to 2. Default value is 4.

TrendMethod Whether or not to include trend data into the forecast.

Valid values for Trend method are 0=No trend and 1=With trend.

Note: AVS-Graves only considers constant trend.

MinSeasonVal This value controls the update of the forecast. When the profile value is below this value, system does not update the forecast. When profile values are low and a spike in sales occurs, it protects the forecast from increasing. Valid values for Minimum Seasonality are 0 to 1.

UpdateFreqFactor Determines the impact to the frequency of the forced updates. It is a multiplier impact value that can be applied to the system generated average number of periods between selling periods which are used to determine the forced updates.

SeasonalitySW Determines whether the model includes adjustments for seasonal influences.

Valid values for Seasonality Switch are 0 (No) and 1 (Yes).

• 0: without seasonality

• 1: with seasonality

NPITMax NPITMax is used by Calculate Model on the New DFU created by the New Product Introduction functionality. It is used to force a forecast update when there is a sequence of zero demand in the New DFU. This value is copied from old DFU’s AVSGravesStats:LastTMax (on page 20)during the process of introducing new DFU through the New DFU Introduction functionality.

Note: For NPI AVS-Graves, T resets to 1 after each force update.

For example:

NPITmax = 2

History for six periods are 0,0,10,0,0,0

Calculation for fitted Hist is as follows:


AVSGravesParam

Period T NpiTmax Comments

1 1 2

2 2 2 Update the fitted hist as T reaches NpiTmax and reset T=1

3 1 2 Valid history point smooth with history and T=1 4 1 2 Copy the old fitted hist as old fitted hist 5 2 2 Update the fitted hist as T reaches NpiTmax and

reset T=1 6 1 2 Copy the old fitted hist as new fitted hist

InitialMeanValue If there is no history or short history and InitialMeanOverrideSw = 1 (Manual), then the Initial Mean Value must be specified.

During the process of introducing NewDFUs through the New DFU Introduction functionality, the old DFU’s AVSGravesStats:LastDeseasonFittedHist (on page 20) is copied to the AVSGravesParam:InitialMeanValue of the new DFU.

InitMeanOverrideSw This switch determines whether the initial mean values are overridden.

Valid values for Initial Mean Override Switch are 0 (Automatic) and 1 (Manual):

• 0: Let the system automatically calculate the initial mean value for the model.

• 1: Manually set the initial mean value.


AVSGravesStats

AVSGravesStats Table included with: Demand, Flowcasting



UPPER_TEXT


UPPER_TEXT


UPPER_TEXT


UPPER_TEXT

MSE Dmd, Flowcasting

DECIMAL 0.0

SE Dmd, Flowcasting

DECIMAL 0.0

Mean Dmd, Flowcasting

DECIMAL 0.0

MADP Dmd, Flowcasting

DECIMAL 0.0

Trend Dmd, Flowcasting

DECIMAL 0.0

TrackingSignal Dmd, Flowcasting

DECIMAL 0.0

SignedError Dmd, Flowcasting

DECIMAL 0.0

NumSysAdjOutlier Dmd, Flowcasting

INTEGER 0

SmoothDmdSize Dmd, Flowcasting

DECIMAL 0.0

MaxDmd Dmd, Flowcasting

DECIMAL 0.0

Mindmd Dmd, Flowcasting

DECIMAL 0.0

LastDeseasonalFittedHist

Dmd, Flowcasting

DECIMAL 0.0

LastTMax Dmd, Flowcasting

DECIMAL 0.0

SymmetricMAPE Dmd, Flowcasting

DECIMAL 0.0

Table description The output table that holds resulting statistics when a AVS Graves forecast is run.

Note: If a DFU has an attached moving event, only Mean, MSE, SE, and SymmetricMAPE will be published.


AVSGravesStats




Model The model used by a Calculate Model process to identify the history stream and algorithm that is associated with the selected DFU.

MSE Mean squared error based on the historical fitting periods. The formula used is:

where N is the number of history points.

Valid values for Mean squared error are any real numbers greater than 0.

SE The standard error of the model is the square root of MSE.

Mean The average of the history points (on the second pass if there are outliers). This is used for exception graph display.

Valid values for Mean is any real number.

Note: All the DFUs associated with calendar and has weights, the stats should be calculated based on the weights.

MADP Mean Absolute Deviation expressed as a Percentage. It indicates the amount of variability present in the demand, which contributes to the amount of safety stock that is included in the ordering routines.

It is assigned to the item for expressing the forecast error of the forecast imported from Demand.

Trend Trend indicates a positive or negative direction to the data. Trend reflects the development of mean over consecutive history periods. Trends becomes positive if the mean is increasing and negative if the mean is decreasing. The trend is zero for a stable mean.

TrackingSignal The tracking signal is an indication of a DFU's trend. Generally, the farther the tracking signal is from 0, the more unstable the DFU.

SignedError Indicates the way error is propagating, if it is an over forecast or under forecast.

NumSysAdjOutlier The number of history points that were automatically adjusted by the Calculate Model process when doing outlier testing. This includes the first and second pass in the AVS-Graves algorithm.

SmoothDmdSize SmoothDmdSize indicates the final smoothed demand size as determined by the Calculate Model. JDA Demand Management Foundation Reference Guide 19 © 1997 - 2014 JDA Software Group, Inc.- Confidential

AVSGravesStats

MaxDmd Maximum Demand which is calculated by Calculate Model for the given history and algorithm parameters. All the de-seasonalized history periods will be less than or equal to MaxDmd. This is the upper outlier band for the de-seasonalized history.

MinDmd Minimum Demand which is calculated by Calculate Model for the given history and algorithm parameters. All the de-seasonalized history periods will be greater than or equal to MinDmd. This is the lower outlier band for the de-seasonalized history.

LastDeseasonFittedHist It is the Last Fitted History. This value is copied to new DFU’s AVSGravesParam:InitialMeanValue (on page 17) during the process of introducing new DFU through the New DFU Introduction functionality.

LastTMax Calculated by Calculate Model for the last history period. It is maximum number of periods of zero demand before updating the forecast. This value is copied to new DFU’s AVSGravesParam:NPITMax (on page 16) during the process of introducing new DFU through the New DFU Introduction functionality.

SymmetricMAPE Symmetric Mean Absolute Percent Error (Symmetric MAPE) compares the fitted history values (statistically generated forecast in the past) with the actual history for the entire duration of history. It is calculated only for periods with actual (nonzero) demand. Only base history (total history minus history overrides) is used if the Calculate Model process is run with Base History. Total history is used if the Calculate Model process is run with Total History.

Note: If Symmetric MAPE is zero and DFU:NPISw (on page 67) is enabled, it can be concluded that the DFU is new and does not yet have enough history for the model fit statistics to be meaningful. The statistical value will not be meaningful until the DFU reaches the Independence Date.


Cal

Cal Table included with: Fulfillment, Master Planning, Supply, Production and Sourcing Optimization, Demand, Markdown Optimization, Strategic Pricing, Inventory Policy Optimization, Dynamic Demand Response, Promotions Management, Travel Price Optimization, Flowcasting, Enterprise Supply Planning

Column name

PK Included with Datatype Valid values Default value

Cal 1 FF, MP, Supp, PSO, Dmd, MDO, SP, IPO, DDR, PM, Flowcasting, ESP

TEXT

Descr FF, MP, Supp, PSO, Dmd, MDO, SP, IPO, DDR, PM, Flowcasting, ESP

TEXT ' '

Master FF, MP, Supp, Dmd, MDO, SP, DDR, PM, Flowcasting, ESP

TEXT ' '

NumFcstPer FF, MP, Supp, Dmd, MDO, SP, IPO, DDR, PM, Flowcasting, ESP (Deep Tree)

OPTION_NUMBER

0,4,9,12,13,18,19,20,24,26,36,48,52,364,365,366

0

PatternSw ESP BOOLEAN 0,1 0

RollingSw Supp, PSO, Dmd, MDO, SP, DDR, PM, Flowcasting

BOOLEAN 0

Type FF, MP, Supp, PSO, Dmd, MDO, SP, IPO, DDR, PM, Flowcasting, ESP

OPTION_NUMBER

3,4,5,6,7,8,9,10,11,12,13

0

Table description Together, the Cal and CalData tables (and CalInterval if required) define the time periods (such as weeks beginning on Monday) into which the system can allocate time or aggregate data for reviews or reports. For a list of the types of calendars used by each application, see the Type column.

Each row in the Cal table defines the name and type of a calendar. The CalData table specifies the details of each of the calendars defined in the Cal table. If you are using rolling calendars, the CalInterval table defines intervals of a specified duration, but without specifying explicit dates.

Column descriptions Cal A unique identifier for a calendar. This identifier is used throughout the database.

Descr A description of this calendar.

Master


Cal

The optional identifier of the master calendar associated with an Arrival or Shipping, Production, or Production Capacity Calendar. You may use a master calendar to close those calendars for a specific time period, such as a holiday, without having to close each calendar individually.

When a master calendar is closed (when CalData:Opt for the master calendar is set to Closed), all the Arrival or Shipping, Production, and Production Capacity Calendars that the master calendar applies to are also closed. The Open option in a master calendar has no effect on other calendars. The calendar you specify in this column must already exist in the Cal table and must be Calendar Type 4. It must also have a name that is defined entirely in upper case.

You can specify a value in this column only for calendars whose Type is 6, 9, 10, or 11 (Arrival or Shipping, Production, Production Capacity, or Working/Transportation Calendars).

NumFcstPer NumFcstPer is used to determine whether the length of periods in the calendar (defined by rows in the CalData table) is reasonable. The length of a period in the calendar should be between .5 and 1.5 times the length of the period implied by NumFcstPer. For example, if NumFcstPer has a value of 12, forecasting is done monthly. The length of the period should be no less than 15.2 days ((365/12) ×.5) and no greater than 45.6 days ((365/12) × 1.5).

The valid values include:

• For demand calendars — 4, 9, 12, 13, 18, 19, 20, 24, 26, 36, 48, 52, 364, 365

• For all other calendars — 0

Demand calendars (calendars whose Type is 5) must have a fixed number of periods per year. NumFcstPer defines this number. For all other calendars, NumfcstPer must be 0.

PatternSw If the pattern switch is 1 data related to this calendar is in the CalPattern and CalAttribute table. This field is used by the Calendar Manager to determine from where to obtain the data related to this calendar.

RollingSw This switch indicates if the calendar is a rolling calendar or a static calendar. Static calendars (traditional SCPO calendars) are defined with respect to static dates/times in the CalData table. Rolling calendars are defined as a set of relative intervals in the CalInterval table.

Rolling calendars define a pattern and do not have any absolute dates in them. An example of a rolling calendar would be, weekly for the first 4 weeks, and monthly for the next 2 months, and quarterly for the next 3 quarters. This calendar simply defines a pattern. Once this calendar is associated with the start date, the actual time buckets are dynamically calculated.

By changing the start date of the calendar, the time periods get shifted based on the relative intervals defined in the CalInterval table.

Note: Rolling calendars are only supported by Production and Sourcing Optimization and JDA Supply in this release. Supply uses rolling calendars for period definitions used during Calculate Supply Plan and the Perform Resource Optimization processes.

Type A value that defines the function of the calendar. The valid values are 3 - 13. You set a value for Type when you add a calendar. You can change the value later, but you probably should create a new calendar instead of changing an existing one to a new Type.

Note: The default value for Type is 0. Any calendar with Type 0 is invalid.

• 3: Reporting calendar (all components)

Defines reporting periods such as weeks or months. You specify reporting calendars in the page properties to define the time intervals that the system uses for time-dependent data.


Cal

When you create a database, the system automatically generates the following reporting calendars in the new database. In the CalData or CalInterval tables, you can change values for these calendars so that the time periods meet your company's needs.

• Hours—hourly, on the hour

• Days—daily, midnight-to-midnight

• Weeks—weekly, ending Saturdays

• Months—calendar months

Production and Sourcing Optimization Production and Sourcing Optimization Model Manager uses only one type of calendar called the reporting calendar (Cal:Type = 3) for both optimization and reporting data. For example, you might use daily, monthly, and quarterly reporting calendars.

• 4: Master calendar (all components)

Overrides another calendar by defining closed periods. You use a master calendar to close multiple calendars as a group without having to close them individually. When you define a date in a master calendar as Closed, that Closed date can apply to multiple calendars of corresponding types. This applies to calendars of Cal:Type 6, 9 and 10.

• 5: Demand calendar (Demand/Promotions Management)

Defines forecast periods used in fitting statistical models and calculating forecasts. Each DFU in the DFU table can have its own demand calendar (DFU:DmdCal), or you can assign the same calendar to many DFUs. You can use DBParam:DmdCal to define a default demand calendar, which the system uses for any DFU for which DFU:DmdCal is blank. A demand calendar can also function as a reporting calendar. Dynamic Demand Response uses this as the aggregation calendar.

• 6: Arrival/Shipping Calendar (Master Planning, Fulfillment/Deployment, Fulfillment/Distribution/Promotions Management)

Determines when a location is open for receiving as well as when a location is open for shipping.

For Fulfillment/Distribution and Fulfillment/Deployment, to specify periods when product can arrive at a destination, specify an arrival calendar in Sourcing:ArrivCal.

For Master Planning, Fulfillment/Distribution and Fulfillment/Deployment, to specify periods when product can be shipped from a source, specify a shipping calendar in Sourcing:ShipCal.

For Dynamic Deployment, specify an arrival calendar in DynDepSrc:ArrivCal and a shipping calendar in DynDepSrc:ShipCal.

• 7: Allocation Calendar (Fulfillment/Distribution, Master Planning, IPO)

For a SKU, this calendar defines an allocation profile for forecasted demand, which the system uses to spread the forecast to periods of a different duration. For example, you might have a forecast in weekly periods and an allocation calendar in daily periods. Allocation calendars are specified in the SKUDemandParam table.

Master Planning For every allocation calendar specified, create a separate row with CalData:Opt = 5 in the CalData table to repeat the calendar pattern. Note that CalData:Eff cannot be a null value when the allocation calendar (Type 7) is specified.

• 8: Recommended Shipments Calendar (Fulfillment/Deployment)


Cal

Defines the specific points in time on which RecShip:SchedShipDate times can occur. If SKUDeploymentParam:ConstrRecShipSw is set to yes, then a RecShipCal is required in order for Recommended Shipments to be generated from a source SKU. If the RecShipCal is defined, then the SchedShipDate of every recommended shipment will be one of the points in time that is specified in this calendar. A RecShipCal does not have open and closed periods; rather, it defines a set of specific time points when RecShips can occur. The RecShipCal is also used to consolidate continuous forecasted demands at the source and the destination SKUs when allocating source supply to priority demands. Recommended shipments calendars are specified in the SKUDeploymentParam table.

• 9: Production Calendar (Master Planning, Fulfillment/Production, Fulfillment/Distribution, Supply)

Defines the periods when production can and cannot be completed. The system uses this calendar when generating planned orders.

Master Planning Production calendars are specified in ProductionMethod:FinishCal.

Fulfillment For Fulfillment/Production and Fulfillment/Distribution, production calendars are specified in SKUPlanningParam:ProdCal. In Fulfillment/Production, the production calendar must be open for at least one minute during a period in order to create a new planned order in that period.

Supply The production calendar for a SKU is specified in the SKUSupplyParam:Cal column.

Note: Ship calendars should be defined for all time periods when demand need dates or supply due dates are scheduled. So if a demand exists on 1/1990 then ensure that you define a ship calendar for that period.

• 10: Production Capacity Calendar (Master Planning, Fulfillment/Production, Supply)

The production capacity calendar is specified in the Res:Cal column. The resource capacity for each period is specified in CalData:Avail.

Master Planning Master Planning uses production capacity calendars to determine the available capacity on resources when calculating a constrained plan.

Fulfillment Fulfillment/Production uses these calendars to define the periods when CPP resources are open for production, and how much capacity they have in each period. The CPP Level Loads process uses this calendar when calculating a constrained production plan and when you edit the plan.

• 11: Working Calendar / Transportation Calendar (Fulfillment/Distribution and Fulfillment/Deployment)

Working Calendar

Calculate Plan uses these calendars to define the periods when the location is open for loading and unloading an order for the item. To assign a Working Calendar to a SKU, first define the calendar in Cal and CalData tables, then enter the identifier of that calendar into SKUPlanningParam:WorkingCal. The Sourcing:LoadDur of the source SKU and the Sourcing:UnloadDur of the destination SKU are calculated based on open instances of the Working Calendar. The Working Calendar has valid values that are the same as Cal:Type 6.

Transportation Calendar


Cal

Calculate Plan uses these calendars to specify when the actual truck movement can occur. Consider an example where the lead time between the source and the destination is X days, but the truck is not allowed to travel on weekends. In this case, the calendar specifies that the truck can be dropped at an intermediate depot on Friday evening and picked up on Monday morning to resume the trip. To assign a Transportation Calendar to a SKU, first define the calendar in Cal and CalData tables, then enter the identifier of that calendar into Network:TransCal. The Transportation Calendar has valid values that are the same as Cal:Type 6.

• 12: Review Calendar (Fulfillment/Distribution and Fulfillment/Deployment)

Calculate Plan uses these calendars to specify when orders can be placed. It identifies open instances on the source SKU’s order review cycle. For example, the Review Calendar is used to specify review periods in the retail environment. Loads representing purchase orders are considered only during open instances of the Review Calendar. To assign a Review Calendar to a SKU, first define the calendar in Cal and CalData tables, then enter the identifier of that calendar into Sourcing:ReviewCal. The Review Calendar has valid values that are the same as Cal:Type 6.

• 13: Order Review Calendar

The Optimize Orders process uses this calendar to understand the vendor specific dates. This calendar provides information on the vendor such as:

• The days when the order can be placed with the vendor

• Closed - The days when the vendor is closed for ordering

• Forced - The days when you must place an order with the vendor

• AsNeeded - The days when you can place an order with the vendor. That is, order if needed.

• The normal ordering cycle with the vendor. You specify the ordering cycle as the coverage duration (CalData: CovDur) for the order.

The Order Review Calendar is associated with Network and thus you must attach this calendar to the Network.

• 14: Storage Calendar

Specifies time phased storage related attributes. The following attributes can be defined in this calendar:

• StorageUnits

• SurplusStorageUnits

• StorageCost

• SurplusStorageCost

• 16: Yield Calendar

Specifies time phased yields for a parent SKU, subordinate SKU, and co-products. The Yield Adjustment Factor attribute can be defined in this calendar.

• 17: Production Rate Efficiency Calendar

Specifies time phased production rate for resources. The ProdRate Adjustment Factor attribute can be defined in this calendar.

• 22: Price Calendar

Specifies the time phased price for a SKU. The Selling Price attribute can be defined in this calendar.


CalData

CalData Table included with: Fulfillment, Master Planning, Supply, Production and Sourcing Optimization, Demand, Strategic Pricing, Markdown Optimization, Inventory Policy Optimization, Dynamic Demand Response, Promotions Management, Flowcasting, Enterprise Supply Planning

Column name PK Included with Datatype Valid values

Default value

AllocWgt FF, MP, Supp, PSO,Dmd, SP, MDO, IPO, DDR, PM, Flowcasting, ESP

DECIMAL 0

AltCal MP, Supp, PSO, Dmd, SP, MDO, DDR, PM, Flowcasting

TEXT ' '

Avail FF, MP, Supp, PSO, Dmd, SP, MDO, DDR, PM, Flowcasting

DECIMAL 0

Cal 1 FF, MP, Supp, PSO, Dmd, SP, MDO, IPO, DDR, PM, Flowcasting

TEXT

CovDur FF, DDR, PM, Flowcasting

DURATION 0

Descr FF, MP, Supp, PSO, Dmd, SP, MDO, IPO, DDR, PM, Flowcasting

TEXT ' '

Eff 2 FF, MP, Supp, PSO, Dmd, SP, MDO, IPO, DDR, PM, Flowcasting

DATETIME

Opt FF, MP, Supp, PSO, Dmd, SP, MDO, IPO, DDR, PM, Flowcasting

OPTION_NUMBER

1,2,5,6,7 5

PerWgt FF, Supp, PSO, Dmd, SP, MDO, DDR, PM, Flowcasting

DECIMAL 0

Repeat FF, MP, Supp, PSO, Dmd, SP, MDO, IPO, DDR, PM, Flowcasting

DURATION 0

Table description Together, the Cal, CalData, and CalInterval (if required) tables define the time periods (such as weeks beginning on Monday) into which the system can allocate time or aggregate data for reviews or reports. For a list of the types of calendars used by each application, see the Cal:Type column.


CalData

Each row in the Cal table defines the name and type of a calendar. The CalData table specifies the details of each of the calendars defined in the Cal table. If you are using rolling calendars, the CalInterval table defines intervals of a specified duration, but without specifying explicit dates.

Each row in the CalData table defines a calendar period. The period of time prior to the first effective date defined in the calendar is assumed to be closed (Option 1). So, if you define a calendar and leave it empty, and if Avail, PerWgt, and AllocWgt are 0, it is closed.

When a new database is created, it automatically includes several standard reporting calendars, which are listed in the following table. Each calendar includes one or more rows, as shown in this table:

Cal Eff Opt Repeat Description

HOURS 1/1/05 00:00 5 1H Every hour on the hour

DAYS 1/1/05 00:00 5 1D Repeat every day at midnight

WEEKS 1/1/05 00:00 5 7D Weeks ending Saturday night

MONTHS 1/1/05 00:00 6 January (leap year) MONTHS 2/1/05 00:00 6 February MONTHS 3/1/05 00:00 6 March . . .

(The MONTHS calendar includes a row for each month in the leap year)

6

MONTHS 1/1/05 00:00 6 January (non-leap year)

.

.

.

(The MONTHS calendar includes a row for each month in the non-leap year)

6

MONTHS 1/1/06 00:00 5 365d repeat the non-leap year cycle

MONTHS 1/1/08 00:00 5 1461 repeat the 4 year cycle The MONTHS calendar includes a row for each month and uses repeat rows to account for leap years and non-leap years in a 4 year cycle.

Column descriptions AllocWgt For an allocation calendar associated with a SKU, this is the weight the system uses to spread the forecasted demand to periods of a different duration. For example, you might have a forecast in weekly periods and an allocation calendar in daily periods, with a different AllocWgt for each day.

Fulfillment If Sourcing:ShipCal is blank, then the calendar specified in SKUDemandParam:AllocCal is used in its place. In that case, when AllocWgt is 0, the location associated with the SKU is not open for shipping.

The following example illustrates how the system uses AllocWgt to spread the forecast. For each forecast period, the system totals the AllocWgt values for all the rows whose time periods are within the forecast period. Then it calculates the forecast for each period in the calendar as:


CalData

For example, you could create a weekly profile calendar that spreads the forecast into daily periods using these Allocation Weights starting with Day 1: 0, 10, 30, 40, 10, 10, 0.

Suppose you have three forecasts (for example, a statistical forecast and two events) that you want to spread to a daily number. Those forecasts might have the following quantities and durations:

Forecast Quantity StartDate Duration

Forecast 1 1000 Day 1 00:00 7D

Forecast 2 500 Day 4 00:00 2D Forecast 3 300 Day 5 00:00 1D Because Forecast 1 has exactly the same duration as that defined in the calendar, the system uses all the Allocation Weights to spread it from a single weekly forecast to a forecast for each day. For example, the system calculates the value of Forecast 1 for Day 2 as:

For Forecast 2, which covers Days 4 and 5, the system calculates the forecast for Day 4 as:

The resulting spreads of all three forecasts, and the daily total forecasts, are:

Period Alloc Weight Spread 1 Spread 2 Spread 3 Total Spread

Day 1 0 0

Day 2 10 100 100 Day 3 30 300 300 Day 4 40 400 400 800 Day 5 10 100 100 300 500 Day 6 10 100 100 Day 7 0 0 The forecast is spread in the same way even for a forecast period that is not to be allocated in its entirety—if OHPost falls within the forecast period, for example, or if a DFU to SKU mapping is interrupted in the middle of a forecast period by DFUtoSKU:Eff or DFUtoSKU:Disc. In effect, the system allocates the forecast for the entire forecast period but uses the allocated forecast only for the allocation periods on or after OHPost or within an effective DFUtoSKU map.

AltCal The identifier of an alternate calendar, whose pattern is incorporated into the pattern of another calendar. Valid values include:

• If CalData:Opt (on page 30) is 7, the identifier of a calendar whose Cal:Type is the same as this calendar's

• If CalData:Opt (on page 30) has any other value, blank

Alternate calendars make it easy to define a calendar pattern that you use frequently, then incorporate that pattern into many calendars without having to define the pattern for each one.

For example, you might define a calendar pattern of two shifts a day for five days and two days closed, with the pattern repeating each week. The CalData table for that pattern would include this data:


CalData

Cal Eff Opt Repeat

80HR 1/04/05 00:00 1

80HR 1/04/05 07:00 2 80HR 1/04/05 23:00 1 80HR 1/05/05 00:00 5 1D 80HR 1/09/05 00:00 1 80HR 1/11/05 00:00 5 7D You could insert that pattern into any other calendar of the same calendar type with just one CalData row. For example, to insert the 80HR pattern into the OVEN1 calendar beginning on 5/6/05, add this row to CalData:

Cal Eff Opt AltCal

OVEN1 5/06/05 00:00 7 80HR

AltCal can be the name of any existing calendar whose type is the same as the type of the calendar in CalData:Cal (on page 30).

If you specify a value for AltCal, CalData:Opt (on page 30) must be 7 (Use Alternate Calendar).

For example, calendar PACK1 might define a 40-hour work week and calendar 80HR might define an 80-hour work week. To change the PACK1 calendar pattern to an 80-hour week, you could either type an entirely new calendar pattern or specify 80HR as an alternate calendar, as follows:

Cal Eff Opt AltCal

PACK1 12/01/05 00:00 7 80HR

In the example, the PACK1 calendar begins using the 80HR pattern on 12/01/05. PACK1 uses whatever 80HR option is in effect on that date. For example, if 80HR is closed on that date, PACK1 is also closed.

A calendar specified in AltCal can itself have an alternate calendar, which can have an alternate calendar. However, eventually the alternate calendar you specify must define a calendar pattern. In the following example, the PACK4 calendar uses PACKCAL as an alternate calendar. PACKCAL uses the 40HR and 80HR calendars as alternate calendars. Both 40HR and 80HR are defined as calendar patterns.

Cal Eff Opt AltCal

PACK4 09/04/05 00:00 7 PACKCAL

PACKCAL 07/29/05 00:00 7 80HR PACKCAL 12/31/05 00:00 7 40HR PACKCAL 04/29/05 00:00 7 80HR If there is a conflict in calendar patterns between the alternate and master calendars, the system uses the master calendar pattern.

Do not specify an alternate calendar that results in a circular calendar, as in the following example:

Cal AltCal

Oven1 Weeks1


CalData

Cal AltCal

Weeks1 Weeks2 Weeks2 Oven1 Alternate calendars are used in JDA Master Planning.

Alternate Calendars are not used or respected in Fulfillment.

Avail Avail is the daily production capacity for a resource during the time period defined in this row. You can specify capacity in terms of standard cases, tons, or any other unit of measure that makes sense in your production environment.

You can specify a value for Avail only for the production capacity calendar (Cal:Type = 10). The value in CalData:Opt (on page 30) must be 6.

Cal The calendar (from the Cal table) whose time periods and other data are defined in this row.

CovDur The Coverage Duration represents the standard ordering cycle with a vendor. That is, it indicates the frequency in which an order is placed with a vendor.

This CovDur can only be set for Order Review Calendars (Cal:Type 13).

Descr A description of the event defined for this calendar period. For example, if CalData:Opt (on page 30) is 5 (Repeat), the description might explain that this period might begin or resume a repeat pattern.

Eff The date and time when the Calendar Period Option (Opt (on page 30)) for this row takes effect. The Calendar Period Option specified in any row is in effect from the effective date of that row until the next effective date/time of a row for the same calendar.

Note: Ensure that you populate CalData:Eff with a valid value. If CalData:Eff is zero then the system may ignore the calendar or produce incorrect results.

Opt The option associated with this calendar beginning at the date/time in Eff (on page 30). Valid values include 1, 2, 5, 6, and 7.

Note: Options 3, 4, 8, 9, 10 and 11 are not used.

• 1: Closed

• Master calendars (Fulfillment/Production)—Not available for production.

• Arrival calendars (Master Planning, Fulfillment/Distribution)—Not available for arrivals.

• Production calendars (Master Planning, Fulfillment/Production, Fulfillment/Distribution, Supply)—Not available for completion of production.

• Order Review calendars (Fulfillment/OrderOptimization) - Not available for ordering.

• 2: Open

• Master calendars (Fulfillment/Production)—Available for production.

• Arrival calendars (Master Planning, Fulfillment/Distribution)—Available for arrivals.

• Production calendars (Master Planning, Fulfillment/Production, Fulfillment/Distribution, Supply)—Available for completion of production.

• 5: Repeat JDA Demand Management Foundation Reference Guide 30 © 1997 - 2014 JDA Software Group, Inc.- Confidential

CalData

All calendars—Begin or resume repeat pattern.

If you specify a Length of Repeat Period (Repeat) for this row, the system begins repeating the pattern that was in effect immediately preceding the Effective Date/Time. For example, the OVEN1 calendar could define a repeating pattern of five days open followed by two days closed like this:

Cal Eff Opt Repeat

OVEN1 10/01/05 00:00 2

OVEN1 10/06/05 00:00 1 OVEN1 10/08/05 00:00 5 7D If you do not specify a value for Repeat, the system resumes the most recent repeat pattern (that is, the last time that Calendar Period Option 5 was specified for that calendar) at the same point where it would have been if it had continued repeating without interruption. For example, if OVEN1 had to be shut down for 36 hours, specifying Option 5 with no Repeat would cause the pattern to resume:

Cal Eff Opt Repeat

OVEN1 10/01/05 00:00 2

OVEN1 10/06/05 00:00 1 OVEN1 10/08/05 00:00 5 7D OVEN1 11/27/05 12:00 1 OVEN1 11/29/05 00:00 5 If no value is specified for Repeat and this is the first Option 5 for the calendar, the calendar is closed until the next Effective Date/Time. The first row in the calendar should not be defined as a repeat row.

• 6: Reporting, Demand, Allocation, and RecShip Period; or Availability

Reporting, Demand (Demand), Allocation (Fulfillment/Distribution, Master Planning, IPO), and RecShip (Fulfillment/Distribution) calendars—the duration from the effective date of one row to the effective date of the next constitutes one period in the calendar.

Production capacity calendars (Fulfillment/Production, Master Planning, Supply)—the daily resource capacity during the time period is specified in CalData:Avail (on page 30).

• 7: Use Alternate Calendar

Master Planning uses Alternate Calendars.

To set up alternate calendars, edit the Cal and the CalData tables using the Flexible Editor or import the relevant data into these tables. For more information on using the Flexible Editor and importing data, see JDA Help.

Note: You cannot set up alternate calendars through the Calendar Manager.

• 12: As Needed

Order Review Calendar (Fulfillment/OrderOptimization) - The order can be placed on this day if needed.

• 13: Forced

Order Review Calendar (Fulfillment/OrderOptimization) - The order must be placed on this day.

PerWgt For demand calendars, this is the weight for the period. Valid values include:

• If Cal:Type is 5, greater than or equal to 0


CalData

• If Cal:Type is not 5, 0

PerWgt enables you to weight the FittedHist and the Forecast—for example, if you have a monthly forecast and the months contain different numbers of selling days.

Note: All statistics in the LewandowskiStats table are period weighted.

Repeat The length of time for which the calendar repeats a defined pattern of Calendar Period Options (Opt (on page 30)). For example, a Repeat duration of one week might be used for a pattern of five days Open and two days Closed. A value in this column applies only to rows whose Calendar Period Option is Repeat; for all other rows, it is not allowed.

The Repeat duration ends with the Effective Date of the row, as in the example. The Repeat specified is for the pattern that begins on 9/7/05 00:00 and ends on 9/14/05 00:00. The pattern begins to repeat at 9/14/05 00:00.

Cal Eff Opt Repeat

PLANT1 9/14/05 00:00 5 1W

When you specify a Repeat, the pattern continues to repeat until the Effective Date of a new option.

You can specify any pattern of Calendar Period Options, then repeat them by specifying a Repeat duration that is exactly the length of the pattern.

Suppose you want to set up a calendar for a plant that is open from 7 a.m. to 11 p.m. Monday through Friday, closed from 11 p.m. to 7 a.m., and closed all weekend. You could begin the calendar on a Monday, specifying a pattern for one normal workday. Effective with Tuesday, you could repeat that one-day pattern. Then you could specify that the plant is closed, effective on Saturday. On Monday, you could specify a repeat of one week. The calendar would look like this:

Cal Eff Opt Repeat

PLANT1 5/07/05 00:00 1

PLANT1 5/07/05 07:00 2 PLANT1 5/07/05 23:00 1 PLANT1 5/08/05 00:00 5 1D PLANT1 5/12/05 00:00 1 PLANT1 5/14/05 00:00 5 7D You can interrupt a repeating pattern (to insert a one-day plant closing, for example) then resume the pattern as if it had not been interrupted. To do that, you specify a Calendar Period Option of 5 but do not specify a Length of Repeat Period. For example, using the calendar above, you might want to close the plant on Wednesday, May 20, then resume the normal pattern for Thursday on May 21. The calendar would look like this:

Cal Eff Opt Repeat

PLANT1 5/07/05 00:00 1

PLANT1 5/07/05 07:00 2 PLANT1 5/07/05 23:00 1 PLANT1 5/08/05 00:00 5 1D PLANT1 5/12/05 00:00 1 PLANT1 5/14/05 00:00 5 7D


CalData

Cal Eff Opt Repeat

PLANT1 5/20/05 00:00 1 PLANT1 5/21/05 00:00 5 You can specify holidays in the same way. However, it may be more convenient to use a single master calendar for holidays and to apply it to multiple primary and secondary calendars.


CalDataExpanded

CalDataExpanded Table included with: Demand, Flowcasting


Cal 1 Dmd, Flowcasting

UPPER_TEXT

Dur Dmd, Flowcasting

INTEGER 0

StartDate Dmd, Flowcasting

DATE TO_DATE('01/01/1970 00:00','MM/DD/YYYY HH24:MI')

Table description Each row in the Cal table defines the name and type of a calendar. The CalData table specifies the details of each of the calendars defined in the Cal table. When the Expand Calendar process is run, the CalDataExpanded table is populated with the expanded calendars (CalData:Cal (on page 30)) with start date and duration for the periods for the given date range.

Column descriptions Cal The name of a calendar. This column entry refers to the calendar stored in the CalData:Cal (on page 30) column.

Dur The duration of the period for this row. The duration specified on the Expand Calendar process page is divided into periods according to the calendar selected in the search. The duration of the period is then converted to minutes. The default value for this column is 0.

StartDate The beginning of the period covered by the duration defined in this row.


CausalFactor

CausalFactor Table included with: Demand, Flowcasting


CausalFactor 1 Dmd, Flowcasting

TEXT


TEXT ' '

Type Dmd, Flowcasting

TEXT ' '

Table description Each row in this table defines a causal factor. Causal factors are variables that represent an impact on the forecast, such as the day of the week, a holiday, or the price of a product in a sales region. They are used in the calculation of Multiple Linear Regression models.

CausalFactor is one of four tables in the database that store causal factor information. The other three tables are:

• CausalFactorType—defines the categories for grouping causal factors.

• CausalFactorValue—defines a time series of causal factor values for the causal factors defined in this table.

• DFUCausalFactor—defines the coefficient for a specified causal factor that is associated with a specific DFU.

Each causal factor defined in the CausalFactor table is identified by a name and a type. This table can contain multiple causal factors for the same causal factor type.

Column descriptions CausalFactor The name or identifier of the causal factor defined in this row.

Descr The description of the causal factor.

Type The type identifier for a causal factor. Causal factor types are defined in the CausalFactorType table.


CausalFactorType

CausalFactorType Table included with: Demand, Flowcasting



TEXT ' '

Type 1 Dmd, Flowcasting

TEXT

Table description Each row in this table identifies a specific causal factor type, such as holiday or price. Causal factor types are the categories into which you can group causal factors.

CausalFactorType is one of four tables in the database that store causal factor information. The other three tables are:

• CausalFactor—defines the causal factors for the causal factor types defined in this table.

• CausalFactorValue—defines a time series of causal factor values for the causal factors defined in the CausalFactor table.


Column descriptions Descr A description of the causal factor type.

Type The type identifier for a causal factor.


CausalFactorValue

CausalFactorValue Table included with: Demand, Flowcasting



TEXT

CausalFactorValue Dmd, Flowcasting

DECIMAL 1.0

StartDate 2 Dmd, Flowcasting

DATE

Table description Defines a time series of causal factor values for the causal factors defined in the CausalFactor table. Each row in this table defines a value for the associated causal factor for a specified period of time. A value is in effect from the start date for the value until the next start date is specified. To activate a causal factor, a row must be entered in this table assigning the causal factor value and indicating the date the impact begins. To turn off the causal factor, another row must be added indicating the date the impact ends. Dates in between these rows do not need to be added.

Note: If you have imported causal factor data into this table and it contains rows for every time period over which the causal factor was in effect, you can remove unnecessary date rows by running the Compress Causal Factors function available via the JDA initialization file.

If a causal factor value changes over time, the CausalFactorValue table has multiple rows for the same causal factor, each defining a different value for a particular time period. For example, suppose you have a causal factor called SummerPrice that represents an item whose price increases during the summer months. SummerPrice starts out at 2.39 until 4/15/01, when the price increases to 2.69. On September 1, the price drops to 2.59. Rows in the CausalFactorValue table for SummerPrice might look something like this:

Table 1: Rows in the CausalFactorValue table for causal factor SummerPrice

CausalFactor StartDate Value

SummerPrice 1/15/01 2.39

SummerPrice 4/15/01 2.69 SummerPrice 9/01/01 2.59 A causal factor may have only one value defined and therefore only one row in the CausalFactorValue table. For example, suppose your company is adding snack bar facilities to all the stores in a particular region; the completion date is June 1. To model this, you could define a causal factor called SnackBar in the CausalFactor table. The CausalFactorValue table would have a single row for SnackBar with a start date of 6/1/01 and a value of 1, as shown in the example below.

Table 2: Rows in the CausalFactorValue table for causal factor SnackBar

CausalFactor StartDate Value

Snack Bar 1/1/01 0

SnackBar 6/1/01 1 CausalFactorValue is one of four tables in the database that store causal factor information. The other three tables are:


CausalFactorValue

• CausalFactorType—defines the categories for grouping causal factors.

• CausalFactor—defines causal factors for the causal factor types defined in the CausalFactorType table.


Column descriptions CausalFactor The name or identifier of the causal factor defined in this row.

CausalFactorValue The value of the causal factor for the defined period. The causal factor values defined in this table do not have to be in the same calendar as the DFUs that use the data. When Demand calculates a forecast, it buckets the causal factors into the calendar specified for the DFU.

StartDate The beginning of the period covered by the causal factor defined in this row.


Collection_Info

Collection_Info Table included with: Demand


DmdUnit 3 Dmd UPPER_TEXT

DmdGroup 4 Dmd UPPER_TEXT

“

Loc 5 Dmd UPPER_TEXT

“

Model 6 Dmd UPPER_TEXT

“

Aggregate_Key 2 Dmd UPPER_TEXT

“

Collection_Name 1 Dmd UPPER_TEXT

“

Table description The Collection_Info table stores the collection information and the mode of sending the data to SPI.





Aggregate_Key Specifies the key using which the data is grouped before sending in a group by mode.

Collection_Name The name of the collection. Collection is the collection of DFU and profiles to be sent to SPI.


CrostonParam

CrostonParam Table included with: Demand, Flowcasting

Column name PK Included with

Datatype Valid values Default value


TEXT


TEXT

InitialInterval Dmd, Flowcasting

DECIMAL 1.0

InitialSize Dmd, Flowcasting

DECIMAL 0.0

InitialValSw Dmd, Flowcasting

BOOLEAN 0

IntervalSmooth Dmd, Flowcasting

DECIMAL 0.15

IntervalSmoothSw Dmd, Flowcasting

BOOLEAN 0


TEXT


TEXT

MSESmooth Dmd, Flowcasting

DECIMAL 0.15

MSESmoothSw Dmd, Flowcasting

BOOLEAN 0

NegHistSw Dmd, Flowcasting

BOOLEAN 0

NPIMeanDmdRate Dmd, Flowcasting

DECIMAL

NumPerForInitialVal

Dmd, Flowcasting

DECIMAL

SizeSmooth Dmd, Flowcasting

DECIMAL 0.15

Table description Contains the parameters for setting the Croston method.

Column descriptions DmdGroup The demand group associated with this DFU.

DmdUnit The demand unit associated with this DFU.

InitialInterval User-entered estimate of the demand interval series.


CrostonParam

InitialSize User-entered estimate of the demand size series.

InitialValSw Enable to enter initial values for demand size and demand interval.

IntervalSmooth IntervalSmooth is the smoothing coefficient for the demand interval. This is only used when the IntervalSmoothSw = Y. If IntervalSmoothSw = N, SizeSmooth is used to smooth both size and interval. The default value for the smoothing coefficient is 0.15.

The smoothing coefficient is calculated as:

where n ranges between 0 and 1

IntervalSmoothSw Enable to change demand interval smoothing independently of SizeSmooth value.


Model The model used by a Calculate Model process to identify the history stream and algorithm associated with the selected DFU. The valid value for this column is the identifier of a model.

MSESmoothSw Enable user to change demand MSE smoothing (MSESmooth) parameter independently of SizeSmooth value.

MSESmooth Factor used to smooth the mean squared error. The default value is the same value as the SizeSmooth parameter.The formula used is the following:

where SMSEt represents smoothed MSE in period t and ε(t) is the error.

NegHistSw Allow negative history. If you do not allow it, negative demand is treated as zero. Therefore, the valid values for this column are 0=Do not allow negative history and 1=Allow negative history.

NPIMeanDmdRate NPIMeanDmdRate is used by Calculate Model to smooth the mean demand rate calculated from the actual history. This value is copied from the old DFU’s CrostonStats:MeanDmdRate (on page 44) during the process of introducing New DFUs through the New DFU Introduction functionality.

NumPerForInitialVal The initial window size or the number of periods to be used to calculate Initial Demand Size and Initial Demand Interval.

SizeSmooth SizeSmooth is the smoothing coefficient for the demand size. The default value for the smoothing coefficient is 0.15.

The smoothing coefficient is calculated as:


CrostonParam

where n ranges between 0 and 1.


CrostonStats

CrostonStats Table included with: Demand, Flowcasting



AvgInterval Dmd, Flowcasting

DECIMAL 0.0

CumActualDmd Dmd, Flowcasting

DECIMAL 0.0

CumPredDmd Dmd, Flowcasting

DECIMAL 0.0


TEXT

DmdRateSE Dmd, Flowcasting

DECIMAL 0.0


TEXT

LastPeriod Dmd, Flowcasting

DATE TO_DATE('01/01/1970','MM/DD/YYYY')


TEXT


DECIMAL 0.0


TEXT


DECIMAL 0.0

MeanDmdRate Dmd, Flowcasting

DECIMAL 0.0

SmoothMSE Dmd, Flowcasting

DECIMAL 0.0

StdDevDemand Dmd, Flowcasting

DECIMAL 0.0

StdDevInterval Dmd, Flowcasting

DECIMAL 0.0


DECIMAL 0.0

Table description The output table that holds resulting statistics when a Croston forecast is run.

Note: If period weighting is applied, all statistics are calculated based on weighted history.

Column descriptions AvgInterval Average interval between instances of demand.


CrostonStats

CumActualDmd Cumulative actual demand

CumPredDmd Cumulative predicted demand

DmdGroup The demand group associated with this DFU

DmdRateSE Demand rate standard error.


LastPeriod The start date of the last period of history.





Model The model used by a Calculate Model process to identify the history stream and algorithm associated with the selected DFU.

MSE Demand mean squared error. The statistics of fit are based on the demand size series. Zero intervals are excluded. For MSE, this formula is used

with the following modifications:

• In calculation of the forecast residuals, the predicted demand corresponding to the first actual demand period after an interval of size n is

n X mean demand rate = accumulated demand during demand interval of size n

• N corresponds to the number of history periods with nonzero demand.


MeanDmdRate MeanDmdRate indicates the final smoothed mean demand rate as determined by the Calculate Model. The mean demand rate is defined as the ratio of the smoothed demand size estimate to the smoothed demand interval. The ratio is obtained by treating occurrences of actual nonzero demand and the intervals between them as two independent time series. During the process of introducing New DFUs through the New DFU Introduction functionality, CrostonStats:MeanDmdRate of the old DFU is copied to CrostonParam:NPIMeanDmdRate (on page 41) of the new DFU.


CrostonStats

SmoothMSE The smoothed forecast error for this DFU. The statistics of fit are based on the demand size series. Zero intervals are excluded. For SmoothMSE, the calculation is standard but smoothing is suspended during zero periods.

where ω is a smoothing constant 0.1.

StdDevDemand Demand size standard deviation.

StdDevInterval Interval standard deviation.

SymmetricMAPE Symmetric Mean Absolute Percent Error (Symmetric MAPE) compares the fitted history values (statistically generated forecast in the past) with the actual history for the entire duration of history. It is calculated only for periods with actual (nonzero) demand. Only base history (total history minus history overrides) is used if the Calculate Model process is run with Base History. Total history is used if the Calculate Model process is run with Total History.



Currency

Currency Table included with: Demand, Flowcasting, Markdown Optimization, Promotions, and Strategic Pricing.


Currency 1 Dmd, Flowcasting, PM, MDO, SP

TEXT

Descr Dmd, Flowcasting, PM, MDO, SP

TEXT ' '

Table description This table is used to store all defined currencies. This table is used with the CurrencyProfile and CurrencyProfileVal tables to define currencies and their conversion rates if you are using Time Phase Conversion factors.

This table might include data such as the following:

Currency Description

USD U.S. Dollars

Euros European currency

Column descriptions Currency Type of currency.

Descr The description for this type of currency.


CurrencyProfile

CurrencyProfile Table included with: Demand, Flowcasting, Markdown Optimization, Promotions, and Strategic Pricing.


FromCurrency 1 Dmd, Flowcasting, PM, MDO, SP

TEXT

ToCurrency 2 Dmd, Flowcasting, PM, MDO, SP

TEXT

Table description Use this table to map one type of currency to another if you want to apply currency conversion rates. To convert your price information to a different currency, this table must at least contain entries mapping your PriceProfile:BaseCurrency values to Currency:Currency values. If you are not using different currencies, this table must still contain an entry mapping your base currency to itself (for example, from USD to USD).


FromCurrency ToCurrency

USD USD

USD Euros

USD Pesos

Column descriptions FromCurrency The identifier for the originating currency.

ToCurrency The identifier for the target currency.


CurrencyProfileVal

CurrencyProfileVal Table included with: Demand, Flowcasting, Markdown Optimization, Promotions, and Strategic Pricing.


Datatype Valid values

Default value

ConversionValue

Dmd, Flowcasting, PM, MDO, SP

DECIMAL 1.0

EndDate Dmd, Flowcasting, PM, MDO, SP


FromCurrency 1 Dmd, Flowcasting, PM, MDO, SP

TEXT

StartDate 3 Dmd, Flowcasting, PM, MDO, SP

DATE

ToCurrency 2 Dmd, Flowcasting, PM, MDO, SP

TEXT

Table description Use this table to store currency conversion values. This table contains rows of data showing the conversion rate and the time period over which it was in effect for each CurrencyProfile map. If you are not using currency conversion rates, in other words the CurrencyProfile table contains only one record mapping the base currency to itself, the table automatically populates this table with a single row that uses a value of 1.


From Currency ToCurrency StartDate EndDate ConversionValue

USD USD 1/1/1970 1/1/1970 1

USD Euros 1/1/03 2/1/03 1.1 USD Euros 2/1/03 3/1/03 1.2 USD Euros 3/1/03 4/1/04 1.15 Note: The system automatically extends the starting and ending dates of the first and last period to 1/1/1970 to ensure all historic and future time periods have a currency rate applied to them.

Column descriptions ConversionValue Conversion rate based on the FromCurrency. The currency conversion rate cannot be zero or a negative number.

EndDate End date up to which this currency information is effective.

FromCurrency


CurrencyProfileVal

The identifier for the originating currency.

StartDate Start date from which this currency information is effective.

ToCurrency The identifier for the target currency.


DBParam

DBParam Table included with: Fulfillment, Demand, Master Planning, Supply, Production and Sourcing Optimization, Inventory Policy Optimization, Flowcasting


Default value

CalcModel_KeepReconImpacts

FF, MP, Dmd, Flowcasting

BOOLEAN 1

CalcModel_PurgeOpt Dmd NUMBER 0 CalcModel_UseWeightedStats

Dmd, Flowcasting BOOLEAN 1,0 0

CalcStoreFittedHistSw


BOOLEAN 1

DBName FF, MP, Dmd TEXT DefaultDFUMapSw FF, MP, Dmd BOOLEAN DmdCal FF, Dmd TEXT EnableDraftPDMs Dmd NUMBER (1) 0 IgnoreEffDiscDateSw

MP, Dmd, Flowcasting

NUMBER (1) 1

KeepReconImpacts FF, MP, Dmd, Flowcasting

BOOLEAN 0

LoadID FF, MP, Dmd, Flowcasting

INTEGER

MinHist FF, MP, Dmd, Flowcasting

DURATION

MinModelDur FF, MP, Dmd, Flowcasting

DURATION

MLRAutoSvd FF, MP, Dmd, Flowcasting

BOOLEAN 0

OutlierOpt FF, MP, Dmd, Flowcasting

OPTION_NUMBER

1,2,3

Publish_ZeroForecast

Dmd, Flowcasting BOOLEAN 1,0 1

PublishSSSw FF BOOLEAN ReconAllowNetNegative

Dmd BOOLEAN 1.0

ReconFcstSigAdj MP, Dmd DECIMAL 0.1 ReconNullValues Dmd BOOLEAN 1,0 0

ReconUseNegQtySw MP, Dmd BOOLEAN 1 Recon_CircMapCheck


BOOLEAN 1

Recon_SkipRelevel FF, MP, Dmd, Flowcasting

BOOLEAN 0

SPI_Periodicity Dmd, Flowcasting INTEGER -1

STRAT_USE_SCPO_PRODRATE

PSO INTEGER 0,1 1


DBParam


Default value

SummaryDmdGroup FF, Dmd, Flowcasting

TEXT

SummaryModel FF, MP, Dmd, Flowcasting

TEXT

UseLeadingBlanks Dmd, Flowcasting BOOLEAN WDDSw Dmd, Flowcasting BOOLEAN

Table description The columns in this table contain information that pertains to the entire database; therefore, this table and all of the columns in it are configured for all applications, even if the application does not necessarily use a specific column. The table consists of a single row. You cannot add or delete a row.

Column descriptions CalcModel_KeepReconImpacts Whether Calculate Model should delete Reconcile Forecast and Flexible Allocation reconcile impacts (Type 2, Type 4, Type 5, Type 6, and Type 7) records from FCST/FCSTDRAFT tables or not. If this switch is ON, Calculate Model will not delete reconcile impacts (Type 2, Type 4, Type 5, Type 6, and Type 7) records. If it is OFF, it will delete reconcile impact records.

CalcModel_PurgeOpt The Calculate Model uses this option to determine if all forecast records outside the range of effective and discontinue dates should be deleted. The default value is 0. Valid values include 0, 1, 2, and 3.

• 0: No records outside the effective date range are deleted.

• 1: All forecast records (Type 1, Type 2, Type 3, Type 4, Type 5, Type 6, Type 7, Type 8, Type 9) that fall outside the effective and discontinue date range are deleted. Also, all records of types 2,4,5,6 and 7 that fall before the Demand Post Date are deleted.

• 2: All forecast records of types 2,4,5,6 and 7 that fall before the Demand Post Date are deleted.

• 3: All forecast records (Type 1, Type 2, Type 3, Type 4, Type 5, Type 6, Type 7, Type 8, Type 9) that fall after the Demand Post Date and are outside the effective and discontinue date range are deleted.

Notes:

• CalcModel_PurgeOpt takes precedence over CalcModel_KeepReconImpacts. When CalcModel_PurgeOpt value is either 1, 2, or 3, Calculate Model deletes reconcile impacts (Type 2, Type 4, Type 5, Type 6, and Type 7) even if CalcModel_KeepReconImpacts is ON. Similarly, if CalcModel_PurgeOpt value is 0 and CalcModel_KeepReconImpacts is ON, reconcile impacts (Type 2, Type 4, Type 5, Type 6, and Type 7) are retained while Type 1, Type 3, Type 8, and Type 9 forecast records are deleted.

• Selecting CalcModel_PurgeOpt option to either 1, 2, or 3 can affect system performance.

CalcModel_UseWeightedStats The Calculate Model process uses the weighted history to calculate model statistics, test for seasonality, and perform outlier and serial correlation test when set to Y (1). When set to N (0), the true history is used for statistics, seasonality, outlier, and seasonality tests. This is applicable only to DFUs using the MLR or Fourier algorithms with time weighting applied. The coefficient and forecast are based on the weighted history irrespective of the value of the switch, whereas mean is always based on the actual history.


DBParam

CalcStoreFittedHistSw Whether to store data in the FittedHist table, which is used for the Demand Workbench. The value of this switch can be overridden by DFU:StoreFittedHistOpt.

Note: With this switch turned off, performance is faster, but the data will not be stored and will not be displayed in Demand Workbench.

DBName The current database.

DefaultDFUMapSw Determines whether you want the system to perform automatic mapping between SKUs and Summary DFUs. If this switch is set to Yes, the system automatically maps the total forecast and overrides for a Summary DFU to its associated SKU where DFU:DmdUnit matches SKU:Item, DFU:Loc matches SKU:Loc, DFU:DmdGroup matches DBParam:SummaryDmdGroup (on page 54), and DFU:Model matches DBParam:SummaryModel (on page 55). Automatic mapping eliminates the need for setting up and maintaining rows in the DFUtoSKU table. If DefaultDFUMapSw is Yes, then the SummaryDmdGroup and SummaryModel must exist in the DmdGroup and Model tables.

DmdCal The demand calendar the system uses if DFU:DmdCal is blank.

EnableDraftPDMs Specifies if the pre-defined draft measures are enabled in the Demand Worksheet and Measure Maintenance page.

• 1: You can view pre-defined draft measures.

• 0: You cannot view pre-defined draft measures.

IgnoreEffDiscDateSw Allows you to run the the Publish Forecast, Map DFUs, Map DFUs Subset, Reconcile Forecast, and Reconcile Forecast Subset processes on DFUs without considering their EffDiscDate. When this field is set to 0, only the forecast of DFUs that are effective is published.

Note: The Publish Forecast process considers the Effective and Discontinue dates from the DFU table. The Map DFUs, Reconcile Forecast, and Reconcile Forecast Subset processes consider these dates from the DFUMap table.

KeepReconImpacts Used with the Reconcile Forecast and Reconcile Forecast Subset processes. Retains existing reconcile impacts (records whose Fcst:Type is 4, Reconcile) when Reconcile Forecast is run. If KeepReconImpacts is True, Reconcile Forecast retains the results of previous reconciliations and includes those results in the calculation of the new reconciliation. If KeepReconImpacts is False, Reconcile Forecast discards all results of previous reconciliations before calculating the new reconciliation.

Reconciliation differentiates between reconciliation records that come from a different DFU map, for example, as a result of Flexible Allocation. If the fcstid in the forecast table is other than the current map, then this switch does not apply and the reconciliation records are kept and used to calculate the new reconciliation.

LoadID If you create a VehicleLoad without specifying a load ID, the system uses this value as the load ID. Valid values are 1000 or greater. The system increments LoadID by 1 each time it is used for a new load. When the LoadID 9999999999 has been used, the system begins at 1000 again.

MinHist Determines whether a DFU has short history. If the earliest period for which history exists is later than the current system date minus MinHist, the DFU has short history. Applies to both the Fourier and MLR models.


DBParam

MinModelDur If a DFU has history for less than the duration specified in MinModelDur, the Calculate Model for the DFU will have a maximum of two terms.

To prevent the system from fitting a seasonal model with insufficient history, set MinModelDur to be greater than or equal to MinHist.

The Fourier series algorithm in the Calculate Model function can be expected to generate valid models if two years of history is available. With less than two years of history, one- and two-term models will still be valid, but models with four or more terms (seasonal models) may or may not be valid. For this reason, it is recommended that this column be set to 2 years.

Note: This option applies to Fourier and MLR models.

MLRAutoSvd If the QR regression method is set, but the data does not run properly (has a less than full rank exception or any of the regression statistics are non-finite), then Svd runs if this switch is set to yes.

OutlierOpt Option that determines what Calculate Model does when it finds outliers.

• 1: Mask outlier values and refit the model.

If the DFU is forecasted using Holt-Winters and the database Outlier Opt parameter is set to Option 1, then the setting defaults to Option 2.

Note: Since the outlier setting applies to the entire database, no exception will be generated when this setting defaults to option 2.

The number of history periods to be used is calculated as follows:

Number of history periods observed - Periods Masked - Number of System Adjusted Outliers.

• 2: Replace outlier values with the outlier limit based on LinRegParam:OutlierFactor (Fourier/MLR) and HoltWintersParam:OutlierFactor (Holt-Winters)and refit the model.


Number of history periods observed - Number of System Adjusted Outliers

• 3: Replace outlier values with the mean of the historical demand, excluding outliers, and refit the model. Applies to all models except Lewandowski


Number of history periods observed - Number of System Adjusted Outliers

Publish_ZeroForecast Controls if zero forecast can be published by the Publish Forecast process. If the switch is set to 0, zero forecast is not published. The default setting (1) allows zero forecast to be published.

PublishSSSw Controls the publishing of safety stock quantity using the Calculate Plan process. The default value is 0.

ReconAllowNetNegative When this switch is set to ON the negative Type 4 for a DFU will be created even if Total forecast for that DFU goes negative. For example, when the bottom level contribution is more than the upper level and all except one bottom level DFUs is locked, no exception (4023) is written to the DFUException table. When the Net forecast at the Top is negative, then a net negative forecast will be created at the bottom irrespective of the value of this switch.

ReconFcstSigAdj


DBParam

Controls when a DFU’s quantity is treated as zero during reconciliation. If the Type4 quantity to be created for a time period is less than this setting, it will be treated as zero and no forecast quantity will be reconciled for that time period.

ReconNullValues This switch is used in the Reconcile Forecast and Reconcile Forecast Subset process. If the switch is set to 1, the null values at the upper level and lower level are treated as zeros during the reconcile process - From highest to lowest and From lowest to highest respectively.

ReconUseNegQtySw Controls whether negative values are treated as zeros during reconciliation. If there are negative values for the total forecast and this value is set to 1, then negative Type 4 values may be added. If there are negative values for the total forecast and this value is zero, then the negative value is treated as zero during the calculations.

Recon_CircMapCheck Used with the Reconcile Forecast and Reconcile Forecast Subset processes. If ReconCircMapCheck is set to True, then the Reconcile Forecast or Reconcile Forecast Subset process will check for circular mapping prior to running the process. If ReconCircMapCheck is set to False, then the process will skip the check.

Recon_SkipRelevel When running the Reconcile Forecast process, you specify a Relevel option that indicates whether you want the system to recalculate the level for every row in the DFU Map table or whether you only want the system to recalculate the level for new and related rows. Depending on the size of your DFU Map table, either option can be very time consuming.

In order to accelerate processing, use this variable to skip releveling as part of the Reconciliation process. To skip releveling, set the SkipRelevel variable to Yes. This option should only be used if you know that you do not have any LevelNum = -1 in the DFU Map table. If this option is set, the Relevel option entry in the Reconciliation Process Properties dialog is ignored.

If you set the SkipRelevel variable to Yes and you have multiple levels in your DFU mappings, you can set up multiple maps per level and have the Reconciliation process run them concurrently.

SPI_Periodicity Determines the periodicity specified by the JDA Seasonal Profiling in the Build Seasonal Profile Collection process. This column is used only when Demand is integrated with Seasonal Profiling. It is not used by any seasonality calculation which is a direct result from within JDA Demand.

STRAT_USE_SCPO_PRODRATE With this release the Production rate has two definitions. In the earlier releases of JDA Production and Sourcing Optimization, Production Rate was defined as The number of units of resource utilized by each execution of the production process. With this release an additional interpretation has been added, and you can choose which interpretation to use:

• Set STRAT_USE_SCPO_PRODRATE = TRUE to use the following interpretation: The quantity of the primary output SKU that is produced by a unit resource. This new interpretation is compliant with the SCPO interpretation.

• Set DBPARAM.STRAT_USE_SCPO_PRODRATE = FALSE to use the following interpretation: The number of units of resource utilized by each execution of the production process. This is the JDA Production and Sourcing Optimization interpretation.

These two interpretations of Production Rate provide enhanced inter-application functionality. By default, Production and Sourcing Optimization uses the SCPO Production Rate interpretation; by default STRAT_USE_SCPO_PRODRATE = TRUE.

SummaryDmdGroup


DBParam

Demand group used for Summary DFUs. Valid values are a DmdGroup in the DMDGroup table. The system identifies a DFU as a Summary DFU when the value in DFU:DmdGroup matches the value in this column.

SummaryDmdGroup and SummaryModel can be used if you have a one-to-one relationship between DFUs and SKUs, and you do not want to use the DFU-to-SKU map. To use this feature, you must have a one-to-one relationship where DmdUnit=Item and DFULoc=SKULoc. In addition, you can only have one demand group, such as All. If these conditions are met, you can populate the SummaryDemandGroup column with your standard group name (in the example, "All") and populate the SummaryModel column with the Model Name. Then, you can run a plan without using DFU-to-SKU mapping.

A Summary DFU is an aggregate DFU that stores the total forecast mapped to it from its subordinates, plus any forecast overrides. When you adjust the statistical forecast for a Summary DFU using the Forecast Override function, the system automatically maps the total forecast and overrides for the Summary DFU to an associated SKU, provided that DBParam:DefaultDFUMapSw (on page 52) is set to Yes.

You cannot define both summary DFUs and DFU to SKU mappings. If you use this column, the DFUtoSKU table must be empty. If DefaultDFUMapSw is Yes, then the SummaryDmdGroup must exist in the DmdGroup table.

SummaryModel The model used for a Summary DFU. The CalcSKUMSE process uses this value to determine which DFU row to use for a summary DFU. You cannot define both summary DFUs and DFU to SKU mappings. If you use this column, the DFUtoSKU table must be empty. If DefaultDFUMapSw is Yes, then the SummaryModel must exist in the Model table. Valid values are a model already defined in the Model table.

UseLeadingBlanks Determines whether the system should use the leading blanks starting from the defined history start date (DFU:HistStart) as zeroes to generate the forecast or use the first non-zero bucket to generate the forecast. When set to ON (1), the system treats leading blanks as zeroes and generates the forecast. Treating the leading blanks as zeros lowers the mean value. When set to OFF (0), the system uses first non-zero history bucket and generates the forecast. The default value is 0. This switch is used by the Calculate Model process, Calculate E3 Error process, and Demand Classification.

WDDSw Determines whether you want to display the Weather Driven Demand Panel in Demand Workbench properties and the Weather Driven Demand Exception Graph in Exception Graphs.


DDEProfile

DDEProfile Table included with: Demand, Flowcasting


DDEProfileID 1 Dmd, Flowcasting

UPPER_TEXT


TEXT ' '

DmdCal Dmd, Flowcasting

UPPER_TEXT ' '


UPPER_TEXT ' '


UPPER_TEXT ' '


UPPER_TEXT ' '


UPPER_TEXT ' '



StartPct1 Dmd, Flowcasting

DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20

Table description The Data Driven Events Profile table stores the data driven event definitions so they can be reused with other DFU Models. The DDE Mass Update feature has been added to the interface to allow you to automatically generate DDEs based on a search. However, if you import DDEs using the Import tool, instead of using the DDE Mass Update feature, you must manually set the DDEProfileID to a value that is less than the starting value for DDE (10000000000) and the DFU:RunCalcModelSw to Y, which will cause the DFU forecast to automatically be calculated when the DFU is displayed in the workbench.

Column descriptions DDEProfileID Unique, system-defined number (OID) assigned to the profile.

Descr


DDEProfile

Optional description of the DDE profile defined in this row.

DmdCal The demand calendar assigned to the DFU in the DFU table when a DDE is assigned. This is the calendar used to generate Model and Forecast. Valid values are an identified of a calendar whose Cal:Type is 5.

DmdGroup The demand group of the parent DFU.

DmdUnit The demand unit of the parent DFU.

Loc The location of the parent DFU.

Model The model of the parent DFU.

StartDate The starting date and time of the period defined in this row.

StartPct Percentage indicating how the total value of the data driven event should be distributed for the first period during the duration of the event.

StartPct2 Percentage indicating how the total value of the data driven event should be distributed for the second period during the duration of the event.

StartPct3 Percentage indicating how the total value of the data driven event should be distributed for the third period during the duration of the event.

StartPct4 Percentage indicating how the total value of the data driven event should be distributed for the fourth period during the duration of the event.

StartPct5 Percentage indicating how the total value of the data driven event should be distributed for the fifth period during the duration of the event.

StartPct6 Percentage indicating how the total value of the data driven event should be distributed for the sixth period during the duration of the event.


DFU

DFU Table included with: Fulfillment, Demand, Travel Price Optimization, Demand Decomposition, Markdown Optimization, Promotions Management, Flowcasting, Enterprise Supply Planning


Default value

AdjDmdPostDate

Dmd, Flowcasting


CopyDate Dmd, Dmd Decomp, MDO, Flowcasting


CopyFromDmdGroup

Dmd, Dmd Decomp, MDO, Flowcasting

TEXT ' '

CopyFromDmdUnit


TEXT ' '

CopyFromLoc Dmd, Dmd Decomp, MDO, Flowcasting

TEXT ' '

CopyFromModel Dmd, Dmd Decomp, MDO, Flowcasting

TEXT ' '

DCRank Dmd, Flowcasting

INTEGER 0

Disc Dmd, Dmd Decomp, MDO, Flowcasting


DmdCal Dmd, Dmd Decomp, MDO, Flowcasting, ESP (Deep Tree)

TEXT ' '

DmdGroup 2 FF, Dmd, Dmd Decomp, MDO, Flowcasting

TEXT


DFU


Default value

DmdPostDate Dmd, Dmd Decomp, MDO, Flowcasting, ESP (Deep Tree)


DmdUnit 1 FF, Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

E3Error Dmd, Flowcasting

DECIMAL

E3ErrorDate Dmd, Flowcasting

DATE

Eff Dmd, Dmd Decomp, MDO, Flowcasting


FcstHor Dmd, Dmd Decomp, MDO, Flowcasting

DURATION 525600

HistStart Dmd, Dmd Decomp, MDO, Flowcasting

DATE TO_DATE('01.01.1970.00:00', 'MM.DD.YYYY.HH24:MI')

HwModelSw Dmd BOOLEAN 0 Include_In_SLCCurve

Dmd, Flowcasting

INTEGER 1

InitE3Error Dmd, Flowcasting

DECIMAL 0

InitE3ErrorDate Dmd, Flowcasting

DATE

Loc 3 FF, Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

LockDur Dmd, Dmd Decomp, MDO, Flowcasting

DURATION 1440

MapUsed Dmd, Dmd Decomp, MDO, Flowcasting

TEXT ' '

Mask Dmd, Dmd Decomp, MDO, Flowcasting

TEXT ' '


DFU


Default value

MaxHist Dmd, Dmd Decomp, MDO, Flowcasting

DURATION 1576800

Model 4 FF, Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

ModelDate Dmd, Dmd Decomp, MDO, Flowcasting


MSEHistDur Dmd, Dmd Decomp, MDO, Flowcasting

DURATION 0

NPIFromDmdPostDate

Dmd, Flowcasting


NPIFromMSE Dmd, Flowcasting

DECIMAL 0

NPIIndDate Dmd, Flowcasting


NPIMeanSmooth

Dmd, Flowcasting

DECIMAL 0.5

NPITrendSmooth

Dmd DECIMAL 0

NPIScalingFactor

Dmd, Flowcasting

DECIMAL 1.0

NPISw Dmd, Flowcasting

OPTION_NUMBER

0

NegFcstSw Dmd, Dmd Decomp, MDO

BOOLEAN 0

NetFcstError Dmd, Dmd Decomp, MDO, ESP (Deep Tree)

DECIMAL 0.0

NetFcstMSE Dmd, Dmd Decomp, MDO, ESP (Deep Tree)

DECIMAL -1

NetFcstMSESmConst

Dmd, Dmd Decomp, MDO, ESP (Deep Tree)

DECIMAL 0


DFU


Default value

NewDFUSw Dmd, Dmd Decomp, MDO

BOOLEAN 0

NumYears FF, Dmd, Dmd Decomp, MDO, Flowcasting, ESP (Deep Tree)

INTEGER 1

ObsoleteFlag Dmd, Flowcasting

INTEGER 0

OutlierOpt Dmd, Dmd Decomp, MDO, Flowcasting

OPTION_NUMBER

0,1,2,3 0

PickBestDate Dmd, Dmd Decomp, MDO, Flowcasting


PickBestSw Dmd, Dmd Decomp, MDO, Flowcasting

BOOLEAN 0

PublishDate Dmd, Dmd Decomp, MDO, Flowcasting


RefitDate Dmd, Dmd Decomp, MDO, Flowcasting


RunCalcModelSw


BOOLEAN 0

SeasonErrorLag FF, Dmd, Dmd Decomp, MDO, Flowcasting, ESP (Deep Tree)

INTEGER 0

SeasonProfile Dmd, Flowcasting

TEXT

SEOutlierFactor FF, Dmd, Dmd Decomp, MDO, Flowcasting, ESP (Deep Tree)

DECIMAL 4


DFU


Default value

SEOutlierOpt FF, Dmd, Dmd Decomp, MDO, Flowcasting, ESP (Deep Tree)

OPTION_NUMBER

1,2 1

StaticCFDescr Dmd, Dmd Decomp, MDO, Flowcasting

TEXT ' '

StaticCFValue Dmd, Dmd Decomp, MDO, Flowcasting

DECIMAL 1.0

StatMSE Dmd, Dmd Decomp, MDO, Flowcasting, ESP (Deep Tree)

DECIMAL 0.0

StoreFittedHistOpt

Dmd, Flowcasting

OPTION_NUMBER

0, 1, 2 2

SymmetricMAPE


DECIMAL 0.0

TotFcstLock Dmd, Dmd Decomp, MDO, Flowcasting

BOOLEAN 0

Table description Columns in the DFU table represent inputs that are common to all model algorithms in Demand. Each row represents a demand forecasting unit (DFU)—the entity for which Demand calculates forecasts. A DFU may have multiple models associated with it.

For information about columns specific to Fourier and MLR models, see the LinRegParam table. For information about columns unique to Lewandowski models, see the LewandowskiParam table. For information about columns specific to Holt Winters and Croston see the HoltWintersParam and CrostonParam tables, respectively.

Column descriptions AdjDmdPostDate Adjusted demand post date is the actual date used by the Calculate Model in processing DFUs that are in relationship while introducing New DFUs through the New DFU Introduction functionality. If the DmdPostDate falls within a calendar bucket, the first date of the calendar bucket is set as the Adjusted DemandPostDate. If the DmdPostDate is not set, the start date of the calendar period following the last history period is treated as the AdjustedDemandPostDate.

CopyDate


DFU

The date on which the copy action took place through DFU Maintenance.

CopyFromDmdGroup The DmdGroup associated with the DFU from which you are copying.

CopyFromDmdUnit The DmdUnit associated with the DFU from which you are copying.

CopyFromLoc The location associated with the DFU from which you are copying.

CopyFromModel The Model associated with the DFU from which you are copying.

DCRank Indicates the algorithm recommendation of Demand Classification. Values include First, Second, Third, or Not Recommended.

Disc The date after which the system will no longer calculate the statistical forecast for the DFU. Disc affects only the statistical model.

Disc and Eff work together to determine the period for calculating the statistical forecast. The following chart summarizes the results of all possible combinations of values for Eff and Disc.

Eff value Disc value Result

Blank Blank Effective

Date Blank Not effective until Eff; effective as of Eff Blank Date Effective until Disc, then discontinued Date earlier than Disc

Date Not effective until Eff; effective as of Eff; discontinued as of Disc

Date later than Disc

Date Effective until Disc; discontinued as of Disc; effective as of Eff

The figure below shows how Effective and Discontinue dates affect the calculation of the forecast.


DFU

Figure 1: Effective and Discontinue Dates - impact on forecast calculation

DmdCal The demand calendar used by the Calculate Model process in JDA Demand. If this column is blank, the system uses the default calendar specified for the database in DBParam:DmdCal. Valid values for this column are identifiers of calendars whose Cal:Type is 5. The initial value for this column is “DMDMONTH.”


DmdPostDate The date up to which demand for the DFU has been posted. You change this date each time you post demand for the DFU.

The Calculate Model process calculates a forecast for the period beginning with DmdPostDate.

This value is set by the system and the initial value for this column the date when this row was created.


E3Error E3Error is the final calculated error value that is transferred to the DFUTOE3FCST (on page 133) table using the Transfer Forecast process.

E3ErrorDate The date when the E3Error value is updated after the Transfer Forecast process is run.


DFU

Eff The date before which the system will not calculate the statistical forecast for the DFU. All forecast periods before Eff are set to 0.

Eff affects only the statistical forecast. It has no effect on adjustments to the forecast.

Eff and Disc work together to determine the period for calculating the forecast. The chart under Disc summarizes the results of all possible combinations of Eff and Disc.

FcstHor The length of time for which the system will calculate forecasts for this DFU.

HistStart The Calculate Model process uses the history from this date to fit the model. The HistStart will be set to the date of the first history period in the Hist table if the HistStart is blank. Once the HistStart is set, the Calculate Model process will not overwrite it. The HistStart will need to be updated accordingly if history is added in the Hist table before the HistStart date in order for it to be taken into account in the calculation.

HwModelSw This switch indicates whether the Holt-Winters DFU model has shifted from multiplicative seasonality to additive seasonality. The value of this switch is updated when running the Calculate Model process or clicking Save and Calculate in the Demand Workbench. If HwModelSw is 0, DFU has a multiplicative seasonality else additive seasonality.

• 0: Multiplicative seasonality

• 1: Additive seasonality

Note: This switch is applicable only for the Holt-Winters model.

Include_In_SLCCurve The switch that determines whether to include the DFU in the Build Short Lifecycle curve process.

• 1: DFU is included in the process.

• 0: DFU is excluded from the process.

The default value is 1.

InitE3Error Initial E3 Error is the value calculated when the Calculate E3 Error process is run. This value is further smoothed during the running of the Transfer Forecast process and is then stored as DFU:E3Error (on page 64).

InitE3ErrorDate The date when the InitE3Error value is updated after the Calculate E3 Error process is run.


LockDur The length of the time period used for TotFcstLock.

MapUsed The name of the map that Map DFUs used when it updated forecast or history data for this DFU. When you run Map DFUs, it maps forecast or history from the FromModels to the ToModels based on the map defined in the Map and DFUMap tables. The new forecast or history quantity replaces the old quantity in the Hist or Fcst tables for the ToModel. Map DFUs then updates this field for the To Model in the map.

Mask JDA Demand Management Foundation Reference Guide 65 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFU

Identifier of the mask assigned to this DFU. When Calculate Model fits a model for this DFU, it ignores history for all periods in the mask. This column only displays the current mask name. Valid values for this column are either a blank or the identifier of a mask in the Mask table.

MaxHist MaxHist is the maximum amount of history that will be retained when Delete History process is run. The duration starts backwards from the DmdPostDate.

Model The model used by JDA Demand’s Calculate Model process to identify the history stream and algorithm associated with the selected DFU.

ModelDate The date when the system fit the statistical model for the DFU. This date is updated by the system each time a Calculate Model process is run (see DFU:RefitDate, below). This value cannot be edited.

MSEHistDur Determines how much history to include for MSE. If 0, all history from HistStart date is used. Otherwise, uses duration that is entered (counted backward from the DmdPostDate).

NegFcstSw The switch that determines whether Calculate Model will produce negative statistical forecasts for a DFU. If NegFcstSw is 0 and the system calculates a negative statistical forecast quantity, the system sets that quantity to 0.

• 0: No negative statistical forecasts allowed.

• 1: Statistical forecasts may be less than 0.

Note: NegFcstSw is not applicable for Lewandowski and AVS-Graves DFUs as these algorithms do not support negative forecasts.

NetFcstError The residual forecast error for the forecast period preceding DFU:DmdPostDate, which is captured by a CalcNetFcstError process. The residual forecast error is calculated as:

Fcst:Qty - Hist:Qty

NetFcstError is blank the first time you run the CalcNetFcstError process.

NetFcstMSE When the value in DFU:NetFcstMSE is -1 (the initial value), CalcNetFcstError replaces it with the Statistical Model Mean Squared Error (DFU:StatMSE). If it is any other value, CalcNetFcstError uses the new residual forecast error (DFU:NetFcstError) to smooth it:

((1 - NetFcstMSESmConst) × Old NetFcstMSE) + (NetFcstMSESmConst × DFU:NetFcstError2)

JDA calculates this value but does not use it in inventory management. If your system includes Demand but not Fulfillment/Distribution, you may want to export DFU:NetFcstMSE to another planning system.

NetFcstMSESmConst The Net Forecast Mean Squared Error Smoothing Constant is the constant value used to smooth the DFU-level Net Forecast Mean Squared Error (DFU:NetFcstMSE) as explained under DFU:NetFcstMSE.

Higher values give more weight to the new NetFcstMSE. Reasonable values for this column are between 0 and 0.3.

NewDFUSw Indicates whether or not a new DFU model has been created during the Add/Update Model process.

NPIFromDmdPostDate


DFU

NPIFromDmdPostDate is the old DFU’s AdjDmdPostDate, copied to the new DFU during the process of introducing New DFUs through the New DFU Introduction functionality.

NPIFromMSE This column is used to capture the Mean Squared Error (MSE) value of the Old DFU. The Old DFU’s MSE is used for calculating the MSE of the New DFU, which is in a New DFU Introduction relationship. The value so calculated is written to the Stats (LinRegStats / HoltWinterStats / LewandowskiStats) table during the time it is in relationship with the old DFU. After the Independence Date, the new DFU’s MSE is calculated based on the fitted history, posted history and DFU:MSEHistDur and written to the Stats table. NPIFromMSE also respects MSEHistDur of the Old DFU.

NPIIndDate The date from which the new DFU, created using the New DFU Introduction functionality, will become independent and have forecast based on its own history.

NPIMeanSmooth The mean smoothing parameter used during the process of introducing New DFUs through the New DFU Introduction functionality. The default value is 0.5. The value ranges between 0.0 and 1.0.

NPITrendSmooth The trend smoothing parameter used during the process of introducing New DFUs through the New DFU Introduction functionality. The default value is 0. The value ranges between 0.0 and 1.0.

NPIScalingFactor The scaling factor used during the process of introducing New DFUs through the New DFU Introduction functionality. The default value is 1. Scaling factor can take any positive number.

Note: The lowest valid value is zero.

NPISw Indicates that the DFU has been created using the New DFU Introduction functionality. Default value is 0. The value changes to 0 once the Independence Date is reached.

NumYears Indicates the number of years of indices that are to be used in calculating the seasonality factor (see SKUProjStatic:SeasonFactor for a description). When the value of NumYears is 3 or more, an outlier test is performed.

ObsoleteFlag Indicates if the DFU Model is obsolete. The flag is set by the Add/Update model process.

OutlierOpt Option that determines what Calculate Model does when it finds outliers:

• 0: Use DBParam:OutlierOpt

• 1: Mask outlier values and refit the model

If the DFU is forecasted using Holt-Winters or Croston method, and the database Outlier Opt parameter is set to Option 1, then the setting defaults to Option 2.

Note: Since the outlier setting applies to the entire database, no exception will be generated when this setting defaults to option 2.

• 2: Replace outlier values with the outlier limit (based on LinRegParam:OutlierFactor (Fourier/MLR), HoltWintersParam:OutlierFactor (Holt-Winters), and CrostonParam:OutlierFactor (Croston) and refit the model.

• 3: Replace outlier values with the mean of the historical demand, excluding outliers, and refit the model. Applies to all models except Lewandowski

PickBestDate


DFU

Indicates the date when the Calculate Model process was run with the Pick Best option selected.

PickBestSw If set to 1, indicates this DFU Model was selected as the best fit when running the Calculate Model process with the Pick Best option selected. The best fit is determined by comparing the Symmetric MAPE for each model. The model with the lowest value is considered the best fit. This column is cleared each time the Calculate Model process is run for this specific DFU with the Pick Best option selected.

PublishDate Date when the DFUModel is published from the FcstDraft table to the Fcst table. You can publish only one model per time period for a DFU. This value is set by the system and cannot be edited.

RefitDate Date when Calculate Model updated the model that was previously created. This date is updated each time a Calculate Model process is run (see DFU:ModelDate, above), and cannot be edited.

RunCalcModelSw If the value is set to 1, indicates changes have been made to this DFU Model; therefore, the forecast needs to be recalculated. DFUs changed through import also have the switch set to 1.

The RunCalcModelSw switch is set for the DFUs listed in the Output column in the following scenarios:

Scenarios Output RunCalcMode

lSw Copy a DFU model using the DFU Maintenance page A new DFU Set to 1 NPI (Run NPI with all options) A new DFU Set to 1 Add a new DFU using the Add/Update Model process A new DFU Set to 1 Update the existing DFU using the Add/Update Model process

Existing DFU parameters are updated Set to 1

Run the Calculate Historical Attach Rate process A new attach rate DFU Set to 1 Copy a DDE from one DFU to other using the Demand Workbench DDE is attached to ToDFU Set to 1 Copy mean value from one DFU to other using the Demand Workbench Mean Value is attached to ToDFU Set to 1 Copy parameters from one DFU to other using the Demand Workbench Parameters are copied to ToDFU Set to 1

Attach or detach a lifecycle from a DFU using the Lifecycle Manager page

Lifecycle is attached or detached from ToDFU Set to 1

Attach or detach a seasonal profile from a DFU using the Seasonality Manager page

Seasonal profile is attached or detached from ToDFU Set to 1

Attach or detach an external factor from a DFU using the External Factor Manager page

External factor is attached or detached from ToDFU Set to 1

Run the Calculate Model process All DFUs in the search

If set to 1, turned back to 0

Run the Calculate Model process from the Demand Workbench DFU currently displayed



DFU

Scenarios Output RunCalcMode

lSw

Run the Calculate Model process from the Decision Support Workbench DFU currently displayed


You can set the value of this switch to 0 from the Flexible Editor page of the DFU table.

SeasonErrorLag The number of lag periods used in retrieving historical forecast data from the HistFcst table.

SeasonProfile The seasonality profile attached to this DFU.

SEOutlierFactor Determines the upper and lower-bound limitations of outlier values (anomalous data) to be used by the Calculate Seasonality Error process to adjust time-phased statistical safety stock. The set of limitations is reciprocal. For example, if the value of SEOutlierFactor is 3, then the upper-bound limitation is 3 and the lower-bound limitation is 1/3.

Whether an outlier test is performed during the Calculate Seasonality Error process depends on the value in DFU:NumYears. If that value is more than 3, a test is performed.

SEOutlierOpt Determines how the system will handle the outlier values (anomalous data) detected by the Calculate Seasonality Error process. The options are:

• 1: Ignore outlier values.

• 2: Use a substitute value.

StaticCFDescr Description of the static conversion factor.

StaticCFValue Static conversion factor value.

StatMSE The Statistical Model Mean Squared Error is the value that measures the accuracy of the statistical model by comparing it to actual demand. StatMSE is written to the DFU table for use by DFUtoSKU (for example, when a supply planner is performing statistical safety stock); it is written to the LinRegStats table for reporting.

To calculate StatMSE, Calculate Model finds the residual differences, posted history minus fitted history, for each history period.

Calculate Model initially calculates StatMSE as:

If the model is set for smoothing, the Calculate Model function uses the forecast error to smooth the new StatMSE for each period:

(1-SmoothConstant x oldStatMSE) + (SmoothConstant x forecast error2)

The total forecast for this DFU is locked out to the Lock Duration.

StoreFittedHistOpt


DFU

The StoreFittedHistOpt value indicates the storage behavior of the fitted history for a DFU. The valid values for StoreFittedHistOpt are:

• 0: Do not store Fitted Hist.

• 1: Store FittedHist.

• 2: Refer to DBPARAM.CALCSTOREFITTEDHISTSW to make the decision.

Note: The default value for StoreFittedHistOpt is 2.

SymmetricMAPE Symmetric Mean Absolute Percent Error compares the fitted history values (statistically generated forecast in the past) with the actual history for the entire duration of history. For Lewandowski models, total history, including overrides and data driven events, is used. For Fourier, MLR, Holt-Winters, and Croston models, base history (total history minus history overrides) is used. It is calculated as the average of the absolute error divided by the average of history and fitted history, expressed as a percentage. Symmetric MAPE is always calculated when you run the Calculate Model process.


The formula for measuring Symmetric MAPE is:

where:

• y = actual history

• = fitted history

• n = number of history observations

• t = time period

The following table illustrates the Symmetric MAPE for a DFU with one year of history using a monthly calendar:

Month Time History Fitted History

Absolute Error

Average of history and

fitted history

Calculations required for

SMAPE

H FH AE=|H-FH|

AVG=(H+FH)/2 100*AE/AVG

January -11 50 52 2 51 3.9 February -10 55 47 8 51 15.7 March -9 38 41 3 39.5 7.6 April -8 32 37 5 34.5 14.5 May -7 42 38 4 40 10.0 June -6 37 40 3 38.5 7.8 July -5 45 42 3 43.5 6.9 August -4 41 44 3 42.5 7.1 September

-3 51 46 5 48.5 10.3

October -2 50 48 2 49 4.1 November -1 36 40 4 38 10.5 JDA Demand Management Foundation Reference Guide 70 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFU


Absolute Error


fitted history


SMAPE

December 0 53 51 2 52 3.8 Total

Average=SMAPE 102.2 8.5

Note: SymmetricMAPE may yield unreasonable value when History and Fitted History values are close to zero. For example, if History = 0 and Fitted History = 0.0000001, SymmetricMAPE will become 200. This is applicable to all algorithms.

TotFcstLock Prevents functions that change the statistical forecast (such as Calculate Model) from changing the total forecast. When TotFcstLock is Yes, if a function changes the statistical forecast, it offsets that change. It adds a Static Forecast Lock Adjustment to the Fcst table (that is, a row whose Record Type is 3 and whose Quantity plus the amount by which the statistical forecast changed totals 0).


DFUAllocProfileMap

DFUAllocProfileMap Table included with: Demand, Flowcasting



TEXT


TEXT


TEXT


TEXT

LaunchStartDate

Dmd, Flowcasting

Date

TotalSalesQty Dmd, Flowcasting

DECIMAL 0.0

ProfileName Dmd, Flowcasting

TEXT

LaunchEndDate Dmd, Flowcasting

Date

Table description The DfuAllocProfileMap table stores the association between allocation profiles and individual DFU Models.





LaunchStartDate The date on which the product is launched (Release Date) and from this date the forecast is generated using the allocation profile.

TotalSalesQty The total sales quantity of the DFU.

ProfileName The name of the profile.

LaunchEndDate


DFUAllocProfileMap

Indicates when the launching ends for the allocation profile in this row. It determines when the allocation profile is actually launched.


DFUAttachRateNorm

DFUAttachRateNorm Table included with: Demand, Collaborative Shelf Planning and Analytics

Column name PK Included with Datatype Valid

values Default value

NormGroup 1 Dmd TEXT

Value Dmd INTEGER

Table description The DFUAttachRateNorm table defines the group of relations for which the attach rates value has to be normalized. Each row in this table represents a group and a normalization value associated with that group.

Column descriptions NormGroup The normalization group defined in this row. This group is generally defined for the relations of related target DFUs, mostly the DFUS that belong to the same source.

Value The value to be used for the normalization. The Calculate Dependent Demand process performs the normalization in such a way that the forecasted attach rates values of relations in the same normalization group sums to the input normalization value.


DFUAttachRateRelation

DFUAttachRateRelation Table included with: Demand, Flowcasting


Default value

Relation 1 Dmd, Flowcasting TEXT

SourceDmdUnit Dmd, Flowcasting TEXT TargetDmdUnit Dmd, Flowcasting TEXT StaticRelationVal Dmd, Flowcasting INTEGER LevelID Dmd, Flowcasting INTEGER NormGroup Dmd TEXT

Table description The DFUAttachRateRelation table defines the relationship between the source and target DFUs involved in the process of calculating the dependent demand. Each row in this table represents a mapping and a static relationship value between the source and target DFUs as well as the level ID and normalization group for that mapping.

Column descriptions Relation The user defined name given to the relation. This is the identifier which is used to define the relationship between the source and the target DFUs that are sold as a package. This relationship is used to determine the attach rate value for the target DFU in association with the source DFU.

SourceDmdUnit The demand unit for the source product of the relationship.

TargetDmdUnit The demand unit for the target product of the relationship.

StaticRelationVal The value of the relationship, typically when the relationship is static and not time variant. When this value is provided, it is considered as an attach rate and the dependent demand is calculated as:

Target Dependent Demand = Source Forecast * Static Relation Value

LevelID The level identifier, which represents the relative position of the relation defined in this row in the product assembly. When you define a new relation, the system assigns a default level ID as -1 to that relation. When you run the Calculate Historical Attach Rates process, the level IDs are reassigned for each relation according to their occurrences in the product assembly. The topmost relation in the assembly tree is leveled as 0 and the subsequent related relations are leveled 1, 2, and so on.

NormGroup The normalization group defined for this relation. This column is mapped to the DFUAttachRateNorm:NormGroup column.


DFUAttrib

DFUAttrib Table included with: Demand, Flowcasting


AttribName 1 Dmd, Flowcasting

TEXT

ColName Dmd, Flowcasting

TEXT

PrimaryAttribSW

Dmd, Flowcasting

BOOLEAN 1

TableName Dmd, Flowcasting

TEXT

Priority Dmd, Flowcasting

INTEGER

DFUAttribGroup Dmd UPPER_TEXT

Table description The DFUAttrib table stores identifiers which make an attribute for a DFU. This attribute can be a column from any of the following tables: DmdUnit (on page 149), DmdGroup (on page 148), Loc (on page 221), DFUView (on page 144) and DFU (on page 58).

Column descriptions AttribName The user-defined name given to the attribute. The attribute is consists of table and column pair. For example, select the UDC_Size column from the DFU table. You may give the name to this attribute as ‘Size’ where the table and column pair is ‘DFU.UDC_Size’.

ColName The name of the column associated with the attribute. This column can be a column from any of the following tables: DmdUnit (on page 149), DmdGroup (on page 148), Loc (on page 221), DFUView (on page 144) and DFU (on page 58).

PrimaryAttribSW The identifier that indicates whether the attribute is a primary attribute or a secondary attribute. It displays a value of ‘1’ for the primary attribute and ‘0’ for the secondary attribute. A DFU can have only one primary attribute. The default value is 1.

TableName The name of the table associated with the attribute. This column contains entries for tables such as DmdUnit, DmdGroup, Loc, DFUView, and DFU tables.

Priority The priority assigned to the attribute. This priority is used while assigning the best suited curve to the DFU in the Assign Short Lifecycle Curve process. The attribute that have priority ‘1’ is a primary attribute. The attribute with lower priority number will have higher priority. Priorities cannot overlap.

DFUAttribGroup The name of the DFU attribute group to which this attribute belongs. This field is mapped to DFUAttribGroup:DFUAttribGroup.


DFUCausalFactor

DFUCausalFactor Table included with: Demand, Flowcasting



TEXT

Coef Dmd, Flowcasting

DECIMAL 0


TEXT


TEXT

Force Dmd, Flowcasting

BOOLEAN 0

Included Dmd, Flowcasting

BOOLEAN 0


TEXT


TEXT

PValue Dmd, Flowcasting

DECIMAL 0.0

TStatistic Dmd, Flowcasting

DECIMAL 0.0

Table description Each row in this table defines the coefficient for an MLR causal factor associated with a particular DFU. Each DFU may have multiple coefficients associated with it. This table also includes the T-statistics and P-value which identify whether a causal factor has a significant impact.

The Calculate Model process uses coefficients to calculate the forecast for a DFU. Calculate Model uses the following steps to generate a forecast:

• Extract the appropriate model data from the database.

• Extract the corresponding causal factors from the database.

• Bucket the causal factors into the calendar specified for the DFU.

• Calculate the forecast for the DFU forecast duration using this calculation:

where:

• Ft = the forecast for period t

• n = number of causal factors

• c1 = the coefficient for the ith causal factor

• CFit = the value of the ith causal factor in period t

• Seasonal (Fourier) portion of the forecast = Level, trend, and seasonality


DFUCausalFactor

Several other tables also store causal factor information:

• CausalFactorType defines the categories for grouping causal factors.

• CausalFactor defines causal factors for the causal factor types defined in the CausalFactorType table.

• CausalFactorValue defines a time series of causal factor values for the causal factors defined in CausalFactor table.

Column descriptions CausalFactor The name or identifier of the causal factor whose coefficient is defined in this row.

Coef The coefficient of the causal factor for the DFU. The coefficient represents an estimate of the volume impact of a specific causal factor.

DmdGroup The demand group associated with the DFU whose coefficient is defined in this row.

DmdUnit The demand unit associated with the DFU whose coefficient is defined in this row.

Force If you are using a subset selection method other than 1 (No subset), you can set this switch to Yes to force the system to use a causal factor even if it is not statistically significant to the model. This is helpful if you want to always include the same causal factors for a group of DFUs to maintain consistency among the DFUs.

Before using the Force feature, however, make sure you have a good understanding of the causal factor data. Perform some analysis with automatic subset selection methods to verify that the causal factor you want to force properly explains historical sales.

Included The Calculate Model process updates this column for a particular causal factor if it was selected for this DFUModel.

Loc The location associated with the DFU whose coefficient is defined in this row.


PValue A number that represents the probability that the coefficient is not zero. This value is populated by the both Calculate Model process and Estimate Market Response Model process.

TStatistic A measure of the coefficient’s significance for the DFU. This value is populated by both Calculate Model process and Estimate Market Response Model process.


DFUCoef

DFUCoef Table included with: Demand, Flowcasting


Attrib 5 Dmd, Flowcasting

TEXT

Coef Dmd, Flowcasting

DECIMAL 0


TEXT


TEXT

EventType 6 Dmd, Flowcasting

TEXT

Included Dmd, Flowcasting

BOOLEAN 0


TEXT


TEXT

PValue Dmd, Flowcasting

DECIMAL 0.0

TStatistic Dmd, Flowcasting

DECIMAL 0.0

Table description The DFUCoef table stores the coefficients for both Fourier and Multiple Linear Regression (when calculated in JDA) models.

Column descriptions Attrib For Fourier models, the number that identifies the coefficient: 0 = Level, 1 = Trend, and 2 and up = additional coefficients for each sine/cosine combination (that is, each seasonal wave).

For MLR models, the number that identifies the level, trend, and seasonality coefficients. The Calculate Model process also identifies additional MLR coefficients in the DFUCausalFactor table.

Coef The value of this coefficient.

DmdGroup The demand group associated with the DFU whose coefficient is defined in this row.

DmdUnit The demand unit associated with the DFU whose coefficient is defined in this row.

EventType Identifier of this event type. If this column is blank, then the coefficient is part of the base model. This value is set by the Calculate Model process and cannot be edited.


DFUCoef

Included Indicates whether a seasonal coefficient is included for MLR or Fourier (unlike Fourier, MLR may not include every seasonal coefficient).

• 1: Included

• 0: Not included

This value is set by the user.

Loc The location associated with the DFU whose coefficient is defined in this row.


PValue A percentage that represents the probability that the coefficient is not zero. This value is populated by both Calculate Model process and Estimate Market Response Model process, and cannot be edited.

TStatistic A measure of the coefficient’s significance for the DFU. This value is populated by Calculate Model process and Estimate Market Response Model process, and cannot be edited.


DFUDDEMap

DFUDDEMap Table included with: Demand, Flowcasting


DDEProfileID 5 Dmd, Flowcasting

TEXT


TEXT


TEXT


TEXT


TEXT

OptimPct1 Dmd, Flowcasting

DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20


DECIMAL 1.0e+20

Table description The DFU Data Driven Events Map table stores the association between DDE profiles (in the DDEProfile table) and individual DFU Models. This table also stores the optimized percent values. The actual forecast quantities associated with a DDE are stored in either the Fcst or FcstDraft table, depending on the Calculate Model settings. Since DDEs are stored separately from the forecast and history data, future DDEs will automatically move to the historic time periods as the demand post date is updated.

Column descriptions DDEProfileID Unique, system-defined number (OID) assigned to the profile.




Model


DFUDDEMap

The model used by a Calculate Model process to identify the history stream and algorithm associated with the selected DFU.

OptimPct1 Percentage generated by the system indicating how much of the total forecast has been allocated to this data driven event for the first period.

OptimPct2 Percentage generated by the system indicating how much of the total forecast has been allocated to this data driven event for the second period.

OptimPct3 Percentage generated by the system indicating how much of the total forecast has been allocated to this data driven event for the third period.

OptimPct4 Percentage generated by the system indicating how much of the total forecast has been allocated to this data driven event for the fourth period.

OptimPct5 Percentage generated by the system indicating how much of the total forecast has been allocated to this data driven event for the fifth period.

OptimPct6 Percentage generated by the system indicating how much of the total forecast has been allocated to this data driven event for the sixth period.


DFUDepDmdFcst

DFUDepDmdFcst Table included with: Demand, Flowcasting



DmdGroup 2 Dmd, Flowcasting TEXT

Dur Dmd, Flowcasting DURATION HistStream Dmd, Flowcasting TEXT Loc 3 Dmd, Flowcasting TEXT Qty Dmd, Flowcasting DECIMAL Relation 1 Dmd, Flowcasting TEXT StartDate 4 Dmd, Flowcasting DATE

Table description The DFUDepDmdFcst table stores the forecasted dependent demand for the target DFU in relation to the source DFU. The Calculate Dependent Demand process calculates the dependent demand and stores the values in this table.

Column descriptions DmdGroup The demand group associated with the target DFU whose forecasted dependent demand is defined in this row.

Dur The length of time in minutes covered by the forecasted dependent demand defined in this row.

HistStream The history stream identifier associated with this row.

Loc The location associated with the target DFU whose forecasted dependent demand is defined in this row.

Qty The forecasted dependent demand quantity for the defined period.

Relation The relationship between different products that are sold as a package. This column is mapped to the DFUAttachRateRelation:Relation column.

StartDate The beginning of the period covered by the forecast defined in this row.


DFUDepDmdHist

DFUDepDmdHist Table included with: Demand, Flowcasting



DmdGroup 2 Dmd, Flowcasting TEXT Dur Dmd, Flowcasting DURATION HistStream Dmd, Flowcasting TEXT Loc 3 Dmd, Flowcasting TEXT Qty Dmd, Flowcasting DECIMAL Relation 1 Dmd, Flowcasting TEXT StartDate 4 Dmd, Flowcasting DATE

Table description The DFUDepDmdHist table stores the historical dependent demand for the relationship between the source and target DFUs defined in the DFUAttachRateRelation table. The Calculate Historical Attach Rate process uses these dependent demand values to calculate the attach rate ratio between the source and target DFUs.

Column descriptions DmdGroup The demand group associated with the target DFU whose forecasted dependent demand is defined in this row.

Dur The length of time in minutes covered by the forecasted dependent demand defined in this row.

HistStream The history stream identifier associated with this row.

Loc The location associated with the target DFU whose forecasted dependent demand is defined in this row.

Qty The forecasted dependent demand quantity for the defined period.

Relation The relationship between different products that are sold as a package. This column is mapped to the DFUAttachRateRelation:Relation column.

StartDate The beginning of the period covered by the forecast defined in this row.


DFUException

DFUException Table included with: Demand, Flowcasting



TEXT ' '


TEXT


TEXT

Exception 6 Dmd, Flowcasting

INTEGER

FunctionName 5 Dmd, Flowcasting

TEXT ' '

FunctionNum 7 Dmd, Flowcasting

INTEGER


TEXT


TEXT

UserID Dmd, Flowcasting

TEXT ' '

When Dmd, Flowcasting


Table description Each row in this table identifies an exception found while processing a DFU (by any process that works with DFUs). The process that detects the exception inserts rows into the table; it clears the existing rows the next time it processes the DFU.

Though you cannot edit the table, you can delete the rows through Flexible Editor, provided you have the appropriate privileges on the table.

Note: You can control the logging of exceptions using the SkipExceptions parameter in the SRE_NODE_CONFIG_PROPS:PROP_NAME. Enter the exception number to be skipped in the SRE_NODE_CONFIG_PROPS:PROP_VALUE. Similarly, enter the service name of the process for which the exception will be skipped in the SRE_NODE_CONFIG_PROPS:SERVICE_NAME.

• If PROP_VALUE is set to All, no exceptions are logged for the service specified in SERVICE_NAME.

• If PROP_VALUE is set to Blank, all exceptions are logged for the service specified in SERVICE_NAME.

• If PROP_VALUE is set to Exception number(s) (comma separated), only these exceptions are not logged for the service specified in SERVICE_NAME.

Consider the following example:


DFUException

SERVICE_NAME PROP_NAME PROP_VALUE Results

Demand.CalcModel SkipExceptions 1001 Exception 1001 is not logged for the Calculate Model process.

Demand.Reconcile SkipExceptions 4025, 4026 Exceptions 4025 and 4026 are not logged for the Reconcile Forecast process.

Demand.AssignShortLifeccyle

SkipExceptions All No exceptions are logged for the Assign Short Lifecycle process.

Demand.SpiCollectionBuilder

SkipExceptions blank All exceptions are logged for the Build Seasonal Collection Profile process.

Column descriptions Descr Description of this exception.

DmdGroup The demand group associated with the DFU whose exception is defined in this row.

DmdUnit The demand unit associated with the DFU whose exception is defined in this row.

Exception Exception code number. These are the possible exceptions:

Exception Number

Exception Description Type Processes that generate this

exception

0223 No Match The data for the selected DFU in Hist and Fcst tables does not match.

Error Calculate NetForecastError

0223 No Forecast The data for the selected DFU in Fcst table does not exist.


0224 No History The data for the selected DFU in Hist table does not exist.


0243 Missing Data in Hist or HistFcst

The Calculate Seasonal Error process skips this SKU because the history or forecast data specified for the SKU is insufficient.

Error Calculate Seasonal Error


DFUException

Exception Number


exception

1001 Demand Calendar not found

The demand calendar specified for the DFU in DFU:DmdCal, or the demand calendar specified in DBParam:DmdCal does not exist.

Error Calculate Model

1002 Demand calendar too short

The demand calendar does not extend to the forecast horizon. The forecast horizon begins with the Demand Post Date (DFU:DmdPostDate) and extends for the length of time defined in DFU:FcstHor.

Error Calculate Model and CalcNetFcstError

1003 DFU record not found

The DFU's demand unit, demand group, and location do not correspond to the demand units, demand groups, and locations specified in the search associated with the Calculate Model process.


1005 Demand post date not within demand calendar range

The date in DFU:DmdPostDate is not within the demand calendar.


1006 Hist starts before calendar

The date in DFU:HistStart is prior to the first effective date in the demand calendar (CalData:Eff).


1007 History not found or all zeros

This exception is generated when there is no history for this DFU, or there is history, but the date in DFU:HistStart is later than the last history period plus the duration. So, for example, if the last history period begins 1/1/00 with a duration of seven days, this exception would be generated if the date in DFU:HistStart were 1/8/00 or later.


1008 Invalid Cal:NumFcstPer

The calendar selected isn't valid. The NumFcstPer is not in (4, 9, 12, 13, 18, 19, 24, 26, 36, 48, 52, 364, 365). The fitting matrix could not be constructed. (Fourier, MLR, GenFcst)

Warning

Calculate Model


DFUException

Exception Number


exception

1010 Outlier(s) detected

History points for this DFU exist above or below the outlier band defined in LinRegParam:OutlierFactor. This message is produced during the second regression pass for Calculate Model. See 1303 for the system adjusted outlier message produced during the first regression pass.

Information

Calculate Model

1012 Serial correlation detected

This DFU has serial correlation—that is, a break in the demand pattern that causes a string of all positive or all negative forecast errors. This applies to Fourier only.

Information

Calculate Model

1013 Irregular Demand History

This DFU has a large variation in demand (standard deviation is greater than the level). This condition is sometimes referred to as “lumpy demand.”

Warning

Calculate Model

1014 Not enough History

For the Fourier and MLR algorithms, this exception occurs for DFUs that have short history—that is, DFUs for which DFU:DmdPostDate minus DFU:HistStart is less than DBParam:MinHist. When Calculate Model detects a Fourier DFU with short history, it gives the DFU a one-term model, calculating LinRegStats:ModelLevel as the average of all demand history. If it detects an MLR DFU, a model with only a level term and causal terms is returned.

Warning

Calculate Model

1015 DmdPostDate not found

There is no date specified for the field DFU:DmdPostDate. To store forecasts for the DFU, you must specify a date in the DmdPostDate field.

Error Calculate Model, Store Forecast


DFUException

Exception Number


exception

1016 Forecast does not exist

There is no existing model for this DFU; Calculate Model refits the existing model and recalculates the statistical forecast based on that model. (Produced by Calculate Model > Fourier with Smoothing (previously known as Update Model))


1017 DFU coefficients do not exist

There are no existing model coefficients for this DFU; Calculate Model refits the existing model and recalculates the statistical forecast based on that model. (Produced by Generate Forecast when there are no DFUCoefficients)

Warning

Calculate Model

1018 DFU level does not exist

There is no existing level coefficient for this DFU; to perform smoothing, Calculate Model uses the value in the previous level to calculate the new level. (Produced by Calculate Model > Fourier with Smoothing (previously known as Update Model))


1019 DFU trend does not exist

There is no existing trend coefficient for this DFU; to perform smoothing, Calculate Model uses the value in the previous trend to calculate the new trend. (Produced by Calculate Model > Fourier with Smoothing (previously known as Update Model))

Warning

Calculate Model

1021 Model date after today

The DFU:ModelDate is later than the system date. No smoothing has occurred. (Update Model only)

Warning

Calculate Model

1022 Number history periods > maximum

The number of history periods exceeds the 6-year limit. For the system to calculate the forecast for this DFUModel, you need to either set the HistStartDate or delete some history. (Produced by Calculate Model)



DFUException

Exception Number


exception

1023 Demand filter too high

The demand posted to date for the current period is unreasonable for this DFU—that is, actual demand is greater than the forecasted demand plus DmdFilter times the square root of Statistical Model Mean Squared Error (DmdFilter*SQRT(DFU:StatMSE). For example, if forecasted demand is 1000, DmdFilter is 3, and StatMSE is 10000, actual demand should be no greater than 1300. (Produced by Calculate Model > Fourier with Smoothing (previously known as Update Model))


1024 Demand filter too low

The demand posted to date for the current period is unreasonable for this DFU—that is, actual demand is less than the forecasted demand minus DmdFilter times the square root of Statistical Model Mean Squared Error (DmdFilter*SQRT(DFU:StatMSE). For example, if forecasted demand is 1000, DmdFilter is 3, and StatMSE is 10000, actual demand should be no less than 700. (Produced by Calculate Model > Fourier with Smoothing (previously known as Update Model))


1025 Number of viable history periods < 0

A forecast could not be calculated for this DFU because the number of usable history periods is less than zero. (Produced by Calculate Model > Fourier with Smoothing (previously known as Update Model))

Warning

Calculate Model

1029 LinRegParam record not found

Calculate Model could not find a record in the LinRegParam table for one of the DFUs in your search. The LinRegParam table defines the parameters that Calculate Model uses to fit a model for a DFU.



DFUException

Exception Number


exception

1030 Some causal factors have all zeros

At least one of the causal factors assigned to this DFU in DFUCausalFactor contains no historical data. If this situation is encountered by the regression method QR Decomposition or QR Decomposition with Pivoting, the system removes the causal factors without historical data from the calculation and continues processing. (Produced by Calculate Model > MLR).

Warning

Calculate Model

1032 Invalid regression method

The system has detected an invalid regression method in the RegressionMethod column of the LinRegParam table. This error typically occurs when values for the LinRegParam table are imported directly through Oracle and not through the Import tool, which checks for errors in the import code.


1033 Invalid subset selection method

The system has detected an invalid subselection method in the SubSelectionMethod column of the LinRegParam table. This error typically occurs when values for the LinRegParam table are imported directly through Oracle and not through the Import tool, which checks for errors in the import code.


1034 Too few history values (nhist < nterms)

Calculate Model is unable to fit a model for this DFU because there are too few history values -- that is, the value in LinRegStats:NumHistPerUsed is less than the value in LinRegStats:NumModelTerm.


1035 All history periods are masked

Calculate Model is unable to fit a model for this DFU because all history periods are masked. Clear some of the masked periods for the DFU, then rerun the Calculate Model process to refit the model.



DFUException

Exception Number


exception

1036 No columns in predictor matrix

The predictor matrix is the matrix of all explanatory variables--that is, all seasonal and causal factor variables--that are used by the Multiple Linear Regression algorithm. If this message occurs, contact Product Support. See Getting additional help from JDA.

Warning

Calculate Model

1037 Maximum number of iterations exceeded

Calculate Model has exceeded the number of regression steps you specified for the Maximum Number of Steps option on the Calculate Model Parameters dialog box in Demand Workbench. When the number of iterations needed to calculate a model is larger than the value in LinRegParam:MaxSteps, processing stops and Calculate Model generates an exception in the DFUException table. (Produced by Calculate Model > MLR)

Warning

Calculate Model

1038 Incorrect seasonality length

When you work with a DFUModel that is using the Lewandowski algorithm, you can define seasonality records for the model. If you enter seasonality records for a DFUModel, the number of seasonality records entered must be equal to the periodicity.


1040 DFU with multiple models

Calculate Model has found a DFU with multiple models in the FCST table. (Produced by the Calculate Model process)


1043 LewandowskiParam record not found

Calculate Model could not find a record in the LewandowskiParam table for one of the DFUs in your search. The LewandowskiParam table defines the parameters that Calculate Model uses to fit a model for a DFU. (Produced by Calculate Model > Lewandowski)



DFUException

Exception Number


exception

1044 Infinite values set to zero

This error can occur when using any algorithm. When using MLR, this error can occur when the values for one or more causal factors within the calendar period are all zero. The calendar period extends from the first history period to the demand post date. Typical cases in which this error can occur include: The Singular Value Decomposition regression method is being used and the system is calculating P-Values and T-Statistics. The system is calculating R-Squared and Adjusted R-Squared values for a model in which the history is level. When this error occurs, the MLR algorithm does not fail, but instead generates an exception. It is recommended that you remove the zero causal factors and rerun Calculate Model.

Information

Calculate Model

1045 F-to-Enter not >= F-to-Leave

In the Stepwise regression subset selection method, the value for F-to-Enter must be greater than or equal to the value for F-to-Leave. This is because a forward selection is followed by a backwards selection in this subset selection method. If F-to-Enter is not greater than or equal to F-to-Leave, the newly entered variable could be dropped immediately.


1047 Invalid algorithm

The algorithm defined for this DFU in the Model table is invalid. (Produced by Calculate Model).


1049 Duplicate DFU keys

Publish Forecast could not publish the forecast because your search contains more than one model for this DFU.

Error Calculate Model, Publish Forecast


DFUException

Exception Number


exception

1050 Forecast horizon exceed max

The length of the forecast horizon exceeds the maximum value of ten years. Note: Lewandowski does not support ten years of forcast for weekly calendars.

Information

Calculate Model

1051 Regr. matrix not full rank

This exception can occur in regressions using QR decomposition. It means that two or more of the causal factors are so highly correlated that the QR method cannot be used.


1053 Calendar not a demand calendar

The calendar specified in DFU:DmdCal or DBParam:DmdCal is not a demand calendar.


1054 HistStart > DmdPostDate

The date specified for the start of history (DFU:HistStart) occurs later than the demand post date (DFU:DmdPostDate).

Warning

Calculate Model

1056 Multiple PickBest selection

This exception is generated when the Calculate Model with Pick Best option is run and it finds multiple DFUs with the same Symmetric MAPE.

Information

Calculate Model

1057 Calendar mismatch

This exception is generated if the mean value modifications (MVM) or data driven events (DDE) DmdCal does not match the DFU:DmdCal. This exception is not generated for LewFactors. Creates a processing error.


1058 DDE bad date or calendar

This exception is generated if the DDE is out of range of history and forecast. There is no processing error.

Warning

Calculate Model

1059 Bad MVM date

This exception is generated if the MVM is out of range of history and forecast. There is no processing error.

Warning

Calculate Model


DFUException

Exception Number


exception

1060 Too many DDE/MVM records

This exception is generated if the maximum number of data driven events and mean value modifications is exceeded. The combined total of all data driven events and mean value modifications cannot exceed 98. A DDE with 6 periods counts as 1 DDE.


1061 DiscDate < DmdPostDate

The discontinue date (DFU:Disc) precedes the demand post date (DFU:DmdPostDate).

Warning

Calculate Model

1062 Invalid DFU coefficient

This exception is received if there is an invalid DFU coefficient in the DFUCoef table.


1063 Bad target date

This exception is received if an invalid target date is entered. For example: Case1: Target start date and enddate in history Case2: Target enddate after Forecast Horizon Case3: Target startdate before hist start date


1064 Target already met

The targeted forecast amount has already been met through historic demand data.


1065 Target could not be fulfilled

The targeted forecast amount cannot be reached within the allocated time period.


1066 All target periods locked

All of the time periods over which the target is allocated are already locked. Locked periods cannot be updated.


1067 Bad LewFactor/Lifecycle date

This exception occurs if the LEWANDOWSKIPARAM:LifecycleStartDate or LEWFACTOR:StartDate is out of the DmdCal range. A processing error is created.


1068 Daily calendar not supported

Daily calendars are not supported for the Lewandowski algorithm.



DFUException

Exception Number


exception

1069 No starting mean

The LewandowskiParam:InitMeanOverrideSw column must be set to 1 when using lifecycles.


1070 No linear external factor found

A Lewandowski linear external factor was specified in the LewandowskiParam table, but was not found in the LewFactor table.


1071 No lifecycle found

A lifecycle was specified in the LewandowskiParam table, but was not found in the LewFactor table.


1072 No Lifecycle/LewFactor StartDate

No start date (LEWFACTOR:StartDate or LEWANDOWSKIPARAM:LifecycleStartDate) was specified for the external factor or lifecycle.


1073 Lifecycle/LewFactor StartDate < HistStart

No start date (LEWFACTOR:StartDate or LEWANDOWSKIPARAM:LifecycleStartDate) was specified for the external factor or lifecycle.

Warning

Calculate Model

1074 Invalid LEWFACTOR calendar

This exception occurs if the LEWFACTOR:DmdCal does not match the DFU:DmdCal. Creates a processing error.


1075 Lifecycle/LewFactor StartDate > FcstHor

The LEWANDOWSKIPARAM:LifecycleStartDate or LEWFACTOR:StartDate occurs after the end of the forecast. The LEWFACTOR value is ignored. The exception may also be caused by a Lifecycle or Lewfactor starting after the DFU:Disc date.

Warning

Calculate Model

1076 Lewfactor norm value(s) = zero, impact set to 1

If one or more of the adjusted values (LewFactorValue:NormalizedValue) equals zero, the Factor Value (LewFactorValue:FactorValue) is set to one and the average value (LewFactorValue:AverageValue) is set to 0. The adjusted value is reset to 1.

Information

Calculate Model


DFUException

Exception Number


exception

1077 CrostonParam record not found

A record for this DFU was not found in the CrostonParam table.


1078 HoltWintersParam record not found

A record for this DFU was not found in the HoltWintersParam table.


1079 Algorithm not authorized

The configuration code does not include the these demand algorithms.


1080 Lewfactor Values are missing

The system found LewFactor, but no LewFactorValues (Lewandowski only).


1081 Unable to calculate SMAPE

This error occurs if no fitted history is generated by the algorithm or if there is no history at all. These conditions make it impossible to calculate the SMAPE, which, as a result, is set to 0.

Warning

Calculate Model

1084 Lifecycle/LewFactor range before HistStart

All LewFactor values are before history starts. The LewFactor is ignored.

Warning

Calculate Model

1085 MLR using QRPivot with EstimateTrendSw=0

If the EstimateTrendSw=0 (false) and RegressionMethod=QR, then MLR automatically switches to QRPivot.

Information

Calculate Model

1223 Forecast does not exist

No forecast found for the DFU. No new records will be added to HISTFCST table. (Produced by Store forecast process)

Error Store Forecast

1300 Holdout periods > max. Set to default(0)

The value entered for the holdout period is greater than the maximum (greater than the amount of history divided by 2). In this case, the algorithm will default the holdout period to 0 to perform optimization.

Information

Calculate Model


DFUException

Exception Number


exception

1301 Consecutive negative or zero history - using additive model

System will switch to use an additive model if the number of consecutive negative or zero history is greater than half of the periodicity. This message is displayed only when you have chosen the multiplicative model (Holt-Winters only).

Information

Calculate Model

1302 History is all negative

Displayed for Holt-Winters when all history values are negative. Displayed for Croston if the history is all negative and the CrostonParam:NegHistSw = 1 and the DFU:NegFcsttSw=0. No forecast is generated.

Warning

Calculate Model

1303 Outliers were adjusted based on outlier option

The system discovered outliers during the first regression pass of Calculate Model and adjusted them based on the setting of DBParam:OutlierOpt. See 1010 for the message for outliers on the second regression pass.

Information

Calculate Model

1304 Too Many History or Fcst values for Lewandowski

This warning message is displayed when a Lewandowski DFU has more than 265 periods of history (22 years of weekly periodicity or 5 years of monthly periodicity) or the forecast horizon is set to more than 159 periods.

Warning

Calculate Model

1305 Missing DFUCoefs for Fourier/MLR

Displayed when Calculate Model is run for a Fourier/MLR DFU that is in relationship created during the the process of introducing new DFUs through the New DFU Introduction functionality and has no DFUCoefs.



DFUException

Exception Number


exception

1306 Cannot run Update Model and new DFU introduction process

This error occurs when the DFU:NPISw is set to true and the Calculate Model process is run with the Update Fourier Model option set to yes. New DFU introduction process using the New DFU Introduction functionality, and Update Fourier Model are mutually exclusive.


1307 Switched from Multiplicative to Additive Model

New DFU is created from an old DFU whose seasonality is changed from multiplicative to additive due to zero or negative history.

Information

Calculate Model

1308 SeasonProfile record not found

A seasonality profile was specified in the DFU table, but was not found in the SeasonProfile table.


1309 Attached Profile and DFU Seasonality type mismatch

A seasonality type of a DFU and a type of attached profile does not match.


1310 MovAvgParam record not found

A record for this DFU was not found in the MovingAvgParam table


1312 AVSGravesParam record not found

A record for this DFU was not found in the AVSGravesParam table


1313 Invalid Event

This exception is displayed for following cases: Case1: When the attached event is missing in the MovingEvent table. Case2: When the attached event is crossed over between 2 years. For example, event starts in December 2006 and ends in February 2007. Case3: When MovingEvent:NumPeriods (on page 240) = 0.



DFUException

Exception Number


exception

1314 Invalid Event Data

This exception is displayed for following cases: Case 1: When there are overlapping periods in the MovingEventData table for any of the attached moving events. Case 2: When moving event data is missing from history start date to demand postdate date in the MovingEventData table for any of the attached moving events. Case 3: When moving event data is missing for the seasonality profile's reference year.


1315 Extreme Forecast Value Encountered

This exception is displayed when the forecast value for any period of the DFU exceeds high and low bands compared to the average history. The value for bands = +/- (average history * ExtremeForecastFactor value). Default value for ExtremeForecastFactor is 1000. You can set or modify this value in SRE_NODE_CONFIG_PROPS:PROP_NAME with SRE_NODE_CONFIG_PROPS:SERVICE_NAME as Demand.CalcModel.

Warning

Calculate Model


DFUException

Exception Number


exception

1316 Window Size exceeds the max limit

This exception is displayed for following cases: Case 1: When the History Size is less than the User Defined Window Size and the User Defined Window Size is greater than the Maximum Window Size. Case 2: When the History Size is equal to the User Defined Window Size and the User Defined Window Size is greater than the Maximum Window Size. Case 3: When the History Size is greater than the User Defined Window Size and the User Defined Window Size is greater than the Maximum Window Size. The Maximum Window Size is the minimum value of either periodicity or half the history size

Warning

Calculate Model

1317 Unstable regression model

For Fourier and MLR algorithms, this exception is displayed if the maximum number of terms is greater than or equal to half of the number of history observations. .

Warning

Calculate Model

4001 DFU over-allocated

The allocation defined in the DFUMap table for this FromModel is greater than 100 percent. (Produced by DFUMap Verify)

Warning

DFUMap Verify

4002 DFU under-allocated

The allocation defined in the DFUMap table for this FromModel is less than 100 percent. (Produced by DFUMap Verify)

Warning

DFUMap Verify


DFUException

Exception Number


exception

4021 DFU adjusted by multi parents

A FromModel receives forecast adjustments from more than one ToModel. As a result of reconciling the forecasts of all the ToModels that map to this FromModel's forecast, the differences between the totals at each level may no longer be reconciled. (Produced by Forecast Reconciliation)

Error MapDFU, Reconcile

4022 No unlocked FromModels found

All of the FromModels associated with a ToModel are locked. (Produced by Forecast Reconciliation)

Information

Reconcile

4023 Locked FromModels would cause a negative forecast

The total of the forecasts for the locked FromModels associated with a ToModel is greater than the forecast of the ToModel. Because this would cause negative total forecasts for the unlocked FromModels, no records will be written to the unlocked FromModels during reconciliation. (Produced by Forecast Reconciliation)

Information

Reconcile

4024 No forecast records for this DFU

The system could not perform reconciliation because the Forecast table does not contain any forecast records for this DFU. The system throws the exception for lower level DFUs while running the process from high to low level, and for higher level DFUs while running the process from low to high level. (Produced by Forecast Reconciliation)

Information

Reconcile

4025 To DFU contains a locked time bucket

While performing forecast reconciliation a locked time bucket was encountered. Nothing was reconciled for that period or periods. (Produced by Forecast Reconciliation)

Information

Reconcile


DFUException

Exception Number


exception

4026 Child DFUs contain both positive and negative forecast

This exception is generated when child dfus contain positive and negative forecast. For example: In a map TEST, A is the parent DFU and B and C are child DFUs. The forecast values for DFU A, B, and C are 100, -20, and 30 respectively. As child DFUs B and C have negative and positive forecast values, the system throws this exception as an informational message and generates Type 4 values.

Information

Reconcile

4027 DFU contains negative forecast

This exception is generated when the DFU contain negative forecast after distribution of total volume. (Produced by Forecast Reconciliation)

Information

Reconcile

4041 Model date not found in DFU record

The system could not store forecasts for this DFU because DFU:ModelDate is blank. (Produced by Store Forecast)


4042 Forecast horizon not found in DFU record

The system could not store forecasts for this DFU because DFU:FcstHor is blank. (Produced by Store Forecast)


4101 No DFU models exist

You try to copy DFU information but there are no existing DFU models in the DFU table.

Warning

Add/Update Model

4102 Model doesn’t exist

You try to copy DFU information in add/update model process, but the model you selected to copy from does not exist in a database.

Warning

Add/Update Model

4103 Lew data not copied. Calendars differ

You want to copy Lewandowski-related DFU data (MVM, DDEs, lifecycles, or external factors) but the calendars (DFU:DmdCal) of the source and target DFUs are different.

Warning

Add/Update Model


DFUException

Exception Number


exception

4105 Lock data not copied. Calendars differ

You want to copy Lock data of the DFU but the calendars (DFU:DmdCal) of the source and target DFUs are different. (Produced by Add/Update Model).

Warning

Add/Update Model

4106 Can not copy data from obsolete model

This exception is displayed when Add/Update model process tries to copy from an obsolete model (DFU:OBSOLETEFLAG = 1).

Error Add/Update Model

5001 Calculate Model has not been run on the Old DFU

The DFUMaintCopy process stops without creating the new DFU if the Old DFU’s ModelDate or AdjDmdPostDate is blank.

Error New Product Introduction

5002 Old DFU Model may be out of date

The DFUMaintCopy process creates the new DFU with a warning exception if the Old DFU’s ModelDate < DmdPostDate.

Warning

New Product Introduction

5003 New DFU already has a relation with another DFU

This exception is displayed when the New DFU selected is already in a relationship with another DFU that was created using the New DFU Introduction functionality. Example: In a relationship A -> B, created through the New DFU Introduction functionality, A is the Old DFU and B is the New DFU. If you try to create a new relationship C -> B, this relationship cannot be created as B is already in a relationship with A.

Error New Product Introduction


DFUException

Exception Number


exception

5004 Existing relation has been overridden

This exception is displayed when the relationship between the Old DFU and the New DFU is overridden with the new relationship of the New DFU. Example: In a relationship A -> B, created through the New DFU Introduction functionality, A is the old DFU and B is the new DFU. If you want to create a new relationship C -> B, this relationship is created by overwriting the relationship A -> B.

Warning

New Product Introduction

6001 DmdPostDate not same for the DFUs in the collection

This exception is displayed if the dfu does not have demand postdate equal to next bucket to provide history enddate in the optionset while running Build Seasonal Profile Collection process. This is not applicable if the process runs in the group mode.

Error Collection Builder

6002 Calendar mismatch,selected calendar does not match with DFU's calendar

This exception is displayed if the dfus calendar does not match with selected calendar in the option set while running Build Seasonal Profile Collection process.

Error Collection Builder

7001 History not moved. Calendars differ.

This exception is displayed when the calendars for the option set of the process and the CDS tables are different.

Error Move History

8001 HistFcst Data is not available.

This exception is displayed when there is no record for DFU in the HistFcst table. This is applicable only when the Historical Forecast Option is checked

Error Cleanse History

8002 Mismatch Seasonal Values with Periodicity.

This exception is displayed when there is a mismatch between the Calendar and the profile periodicity.



DFUException

Exception Number


exception

8003 History Data is not available

This exception is generated when there is no record for DFU in the History table


8004 False Out Of Stock signal for a DFU.

This exception is displayed if the actual sales are greater than the forecast generated. In this scenario it is not required to calculate lost sales


8005 FcstPerfStatic data not present for the period

This exception is displayed when there is no record for DFU in the FcstPerfStatic table. This is applicable only when the Forecast Performance Metrics option is selected.


9001 Multiple Short Lifecycle curves matched. Curve at primary attribute level is attached.

This exception is displayed when multiple curves are matching for a DFU.

Error Assign Short Lifecycle Curve

9002 No matching Short Lifecycle curve found, No Curve is attached.

This exception is displayed if primary attribute is not matching.

Error Assign Short Lifecycle Curve

9003 Short Lifecycle Param record not found.

This exception is displayed if there are no records for the DFU in the SLCParam (on page 271) table while assigning the best curve.

Error Assign Short Lifecycle Curve, Calculate Model

9004 Primary attribute not defined.

This exception is displayed for following processes: Build Short Lifecycle Curve: If the primary attribute is not defined for the DFU. Assign Short Lifecycle Curve: If the primary attribute is not defined for the DFU. No Curve is attached to the DFU.

Error Build Short Lifecycle Curve, Assign Short Lifecycle Curve


DFUException

Exception Number


exception

9005 Invalid Param data.

This exception is displayed in any of the following cases: • Smooth Constant <= 0

• Limit Constant <= 0

• Step Size <=0


9006 Curve at primary attribute level is attached.

This exception is displayed if there are multiple curves matching for a DFU and curve at primary attribute level is assigned to it.

Warning

Assign Short Lifecycle Curve

9007 History not found or invalid history length

This exception is displayed in any of the following cases while running the Build Short Lifecycle Curve process: • History is not found.

• History is less than the specified minimum history length in the option set.

• History is more than the specified maximum history length in the option set.

Error Build Short Lifecycle Curve

9301 Intermittent zeros or missing records for dependent demand

This exception is displayed when the dependent demand for the target DFU has missing data for some periods. These periods are not processed and the attach rate DFUs are created with the available data.

Warning

Calculate Historical Attach Rates

9302 Independent demand not found or all zeros

This exception is displayed when the independent demand for the source DFU is missing or all zeros. The Calculate Historical Attach Rates process skips this DFU from the processing.

Error Calculate Historical Attach Rates

9303 Intermittent zeros or missing records for independent demand

This exception is displayed when the independent demand for the source DFU has missing data for the intermittent periods. The Calculate Historical Attach Rates process skips this DFU from the processing.

Error Calculate Historical Attach Rates

9401 Independent demand not found

This exception is displayed when the independent demand for the source DFU is missing.

Error Calculate Dependent Demand


DFUException

Exception Number


exception

9402 Attach rate of target DFU not found.

This exception is displayed when the attach rate for the target DFU is missing.


9403 Demand Post Date of Source DFU follows Demand Post Date of Attach Rate DFU.

This exception is displayed when the demand post date of the source DFU is greater than the demand post date of the attach rate DFU.


9404 Effective Date of Source DFU follows Effective Date of Attach Rate DFU.

This exception is displayed when the effective date of the source DFU is greater than the effective date the attach rate DFU.


9405 Discontinue Date of Source DFU precedes Discontinue Date of Attach Rate DFU.

This exception is displayed when the discontinue date of the source DFU is less than the discontinue date the attach rate DFU.


FunctionName Name of the function that detected this exception.

FunctionNum Number that identifies the function that detected this exception:

• 7: Calculate Model

• 9: Store Forecast

• 13: DFUMap Verify

• 14: Reconciliation

• 32: CalcNetFcstError

• 62: DFUMaintenance

• 68: Lifecycle Create

• 90: AssignSLCurve

• 91: BuildSLCurve

• 251: Add/Update Model

Loc The location associated with the DFU whose exception is defined in this row. JDA Demand Management Foundation Reference Guide 108 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFUException

Model The model used by the Calculate Model process to identify the history stream and algorithm that is associated with the selected DFU.

UserID Identifier of the user who used the process that detected this exception.

When Date and time when the exception was detected.


DFUExternalFcst

DFUExternalFcst Table included with: Demand, Flowcasting

Column Name PK Included with

Data Type Valid Value

Default Value

DmdGroup Dmd, Flowcasting

TEXT

DmdUnit Dmd, Flowcasting

TEXT


INTEGER 1440

FcstID 1 Dmd, Flowcasting

TEXT

Loc Dmd, Flowcasting

TEXT

Model Dmd, Flowcasting

TEXT

Qty Dmd, Flowcasting

DECIMAL 0



Table description This table is used for storing the external forecast data. The data from this table can be viewed in the Demand Decision Support Workbench and if required, can be updated.

Column descriptions DmdGroup The DmdGroup associated with the external forecast.

DmdUnit The DmdUnit associated with the external forecast.

Dur The length of the time interval that starts at StartDate.

FcstID The unique identification of the external forecast.

Loc Location associated with the external forecast.

Model Model associated with the external forecast.

Qty The external forecast quantity.

StartDate


DFUExternalFcst

The beginning date and time for the time interval to which the external forecast quantity applies.


DFUMaintCopyDFU

DFUMaintCopyDFU Table included with: Demand, Flowcasting


Action_Group_Set_ID

Dmd, Flowcasting

NUMBER

Action_Number Dmd, Flowcasting

NUMBER

ErrorMsg Dmd, Flowcasting

TEXT

FromDiscDate Dmd, Flowcasting

DATE 1/1/1970

FromDmdGroup Dmd, Flowcasting

TEXT

FromDmdUnit Dmd, Flowcasting

TEXT

FromLCStartDate Dmd, Flowcasting

DATE 1/1/1970

FromLifeCycle Dmd, Flowcasting

TEXT

FromLoc Dmd, Flowcasting

TEXT

FromModel Dmd, Flowcasting

TEXT

FromSeasonProfile

Dmd VARCHAR2

HistStream Dmd, Flowcasting

TEXT

ProcErr Dmd, Flowcasting

INTEGER 0

RequestID Dmd, Flowcasting

TEXT

ToDmdGroup Dmd, Flowcasting

TEXT

ToDmdUnit Dmd, Flowcasting

TEXT

ToEffDate Dmd, Flowcasting

DATE 1/1/1970

ToLCStartDate Dmd, Flowcasting

DATE 1/1/1970

ToLifeCycle Dmd, Flowcasting

TEXT

ToLoc Dmd, Flowcasting

TEXT

ToModel Dmd, Flowcasting

TEXT

ToNPIIndDate Dmd, Flowcasting

DATE 1/1/1970


DFUMaintCopyDFU


ToNPIMeanSmooth

Dmd, Flowcasting

DECIMAL 0.5

ToNPIScalingFactor

Dmd, Flowcasting

DECIMAL 0.0-10.0 1.0

ToNPITrendSmooth

Dmd, Flowcasting

DECIMAL 0.0

ToSeasonProfile Dmd VARCHAR2

Table description The DFUMaintCopyDFU table is used by DFU Maintenance and New DFU Introduction to specify relationship between the old DFUs and new DFUs that will be created when the process is run. When running the process from UI this table will be populated automatically. When running the process from batch the user will populate this table using IGP.

Notes:

• You must provide all the primary keys of the FromDFU and ToDFU (DmdUnit, DmdGroup, Loc, and Model) to create a one-to-one NPI relationship.

• While running the New DFU Introduction process through the user interface, the rows that are marked with a value of 4 in the DFUMaintCopyDFU:ProcErr column will not be deleted. While running the New DFU Introduction process through batch, all rows that are marked with values of 1, 2, and 4 in the DFUMaintCopyDFU:ProcErr column will not be deleted. A manual cleanup of the DFUMaintCopyDFU table is required.

• If the FromDmdUnit, FromDmdGroup, FromLoc, and FromModel do not constitute a valid DFU, those entry rows are marked as invalid, and are not processed. The Number of Invalid Entry Rows field, present on the New DFUs Introduction by Component process jobstatus pop-up window while running the process through user interface or present in the log file while running the process through batch, displays the number of invalid entry rows. All these invalid entry rows are marked with a value of 4 in the DFUMaintCopyDFU:ProcErr column. Each time you run the process, invalid entry rows are not deleted. A manual cleanup of the DFUMaintCopyDFU table is required.

Column descriptions Action_Group_Set_ID This column initially needs to be populated with the value “1”. Once the process is run, the appropriate data is populated into it.

Action_Number Enter an initial value of “1”.

ErrorMsg Displays the descriptive error message for the processing error value stored in the ProcErr (on page 114) column.

FromDiscD ate The date from which the old DFU is discontinued.

FromDmdGroup The DmdGroup of the old DFU.

FromDmdUnit The DmdUnit of the old DFU.


DFUMaintCopyDFU

FromLCStartDate The start date of the life-cycle attached to the old DFU.

FromLifeCycle The name of the life-cycle attached to the old DFU.

Note: Applies only to Lewandowski DFUs.

FromLoc The location of the old DFU.

FromModel The model of the old DFU.

FromSeasonProfile The name of the seasonality profile attached to old DFU.

HistStream Indicates the history stream for both the old and new DFUs.

ProcErr Indicates if a process error has occurred during the process of introducing New DFUs through the New DFU Introduction functionality. The error details can be viewed in the ErrorMsg (on page 113) column.

Valid values for ProcErr and ErrorMsg columns are:

ProcError ErrorMsg

0 NO ERROR

1 CALCULATE MODEL NOT RUN ON FROMDFU 2 TO DFU ALREADY IN RELATION 3 INVALID FROMDFU 4 FROMMODEL AND TOMODEL SHOULD BE SAME 5 TODFU AND FROMDFU ARE SAME 6 MANY TO ONE RELATION 7 FROM DFU NOT IN SEQUENCE 8 INVALID TODFU - FAILED DFU VALIDATION 9 INVALID ENTRY ROW

RequestID Request ID uniquely identifies the data set that will be used when the process of introducing New DFUs through the New DFU Introduction functionality is run. The column is automatically populated if the process is run through the UI. When using IGP, you will need to provide a unique string as the Request ID.

ToDiscDate The date from which the new DFU is discontinued.

ToDmdGroup The DmdGroup of the new DFU.

ToDmdUnit The DmdUnit of the new DFU.

ToEffDate JDA Demand Management Foundation Reference Guide 114 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFUMaintCopyDFU

The date from which the new DFU becomes effective.

ToLCStartDate The start date of the life-cycle attached to the new DFU.

ToLifeCycle The name of the life-cycle attached to the new DFU.

Note: Applies only to Lewandowski DFUs.

ToLoc The location of the new DFU.

ToModel The model of the new DFU.

ToNPIIndDate The date from which the new DFU will become independent and have forecast based on its own history.

ToNPIMeanSmooth Mean smoothing coefficient used during the process of introducing New DFUs through the New DFU Introduction functionality. Default value is 0.5.

ToNPIScalingFactor The scaling factor used during the process of introducing New DFUs through the New DFU Introduction functionality. Default value is 1.0. Lowest value it can take is zero.

ToNPITrendSmooth Trend smoothing coefficient used during the process of introducing New DFUs through the New DFU Introduction functionality. Default value is 0.0.

ToSeasonProfile The name of the seasonality profile attached to new DFU.


DFUMap

DFUMap Table included with: Demand, Markdown Optimization, Promotions Management, Travel Price Optimization, Flowcasting

Column name

PK Included with Datatype Valid values

Default value

ConvFactor Dmd, Dmd Decomp, MDO, Flowcasting

DECIMAL 1.0

Disc Dmd, Dmd Decomp, MDO, Flowcasting


Eff 10 Dmd, Dmd Decomp, MDO, Flowcasting

DATE

Factor Dmd, Dmd Decomp, MDO, Flowcasting

DECIMAL 1.0

FcstType Dmd, Dmd Decomp, MDO, Flowcasting

UPPER_TEXT ALL

FromDFULoc 4 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

FromDmdGroup

3 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

FromDmdUnit 2 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

FromModel 5 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

HistType Dmd, Dmd Decomp, MDO, Flowcasting

OPTION_NUMBER

1,2,3 1

LevelNum Dmd, Dmd Decomp, MDO, Flowcasting

INTEGER -1

LockEnd Dmd, Dmd Decomp, MDO, Flowcasting


LockStart Dmd, Dmd Decomp, MDO, Flowcasting


Map 1 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT


DFUMap

Column name


Default value

ToDFULoc 8 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

ToDmdGroup 7 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

ToDmdUnit 6 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

ToModel 9 Dmd, Dmd Decomp, MDO, Flowcasting

TEXT

Table description Each row in this table identifies a map (a row in the Map table) used to aggregate and reconcile forecast or history data between DFU models. By using multiple rows, you can map multiple DFU models into one DFU model. Or, by using multiple rows and DFUMap:Factor, you can map one DFU model into multiple DFU models. The FromModel and ToModel columns identify which models are being aggregated and reconciled.

The Map DFUs function (in JDA Demand) and the Estimate Market Response Model process (in JDA Markdown) perform the mapping using data from the DFUMap and Map tables. You use Map DFUs properties to specify whether you want to map forecast data or history data.

When you add a row to this table, the system does not let you create a circular mapping, as in this example:

From DFUModel

To DFUModel

A B

B C

C A

Column descriptions ConvFactor Stores the value to be used as a conversion factor for the From DFUModel/To DFUModel pair specified in this row. The Map DFUs and Forecast Reconciliation functions and the Estimate MRM process use this value to convert forecast or history quantities to a different unit of measure.


DFUMap

You can specify a different conversion factor for each From DFUModel/To DFUModel pair in a mapping relationship. For example, in the figure shown below, you can specify conversion factors for the From DFUModel/To DFUModel pair B/D independently from the conversion factor for the From DFUModel/To DFUModel pair B/C. In this figure, the From DFUModel/To DFUModel pair A-C has a conversion factor of 2. The From DFUModel/To DFUModel pairs B-C and B-D both have a conversion factor of 3.

To convert forecast or history quantities to a different unit of measure, Map DFUs multiplies these quantities by the value contained in this column. The Forecast Reconciliation function also multiplies forecast or history quantities by this value when it is mapping from the lowest level in a mapping (from the first From DFUModel/To DFUModel pair). Forecast Reconciliation divides forecast or history quantities by this value when it is mapping from the highest level in a mapping (from the last From DFUModel/To DFUModel pair).

Disc The date when this DFU map is discontinued.

Disc and Eff work together to determine when the map is effective. (See the chart under the Eff column description for a summary of the results of all possible combinations of values for Eff and Disc.)

Eff The date when this DFU map becomes effective.

Together, Eff and Disc determine when the map is effective. The chart below summarizes the results of all possible combinations of values for Eff and Disc.







Date same as Disc Date same as Eff

Map is not effective.

Factor Value that determines what portion of the From DFUModel’s Quantity is allocated to the To DFUModel (by a Map DFUs process or a Forecast Reconciliation process), or what portion of the From DFUModel's forecast comes from the To DFUModel (as the result of a Forecast Reconciliation process). The total of Factors for all rows having the same From DFUModel should be 1.0. JDA Demand Management Foundation Reference Guide 118 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFUMap

MapDFUs and Forecast Reconciliation can both use a conversion factor—DFUMap:ConvFactor—to convert quantities to a different unit of measure. However, to simplify the following explanations, the effect of ConvFactor is not shown in the calculations.

MapDFUs allocates history or forecast from From DFUModels to To DFUModels, using this calculation:

From DFUModel Quantity × Factor = To DFUModel Quantity

If a From DFUModel maps into only one To DFUModel, Factor should be 1.0, so:

From DFUModel Quantity × 1.0 = To DFUModel Quantity

If a From DFUModel maps into multiple To DFUModels, the total of all the Factors for the From DFUModel should be 1.0:

From DFUModel Quantity × 0.5 = To DFUModel A Quantity

From DFUModel Quantity × 0.25 = To DFUModel B Quantity

From DFUModel Quantity × 0.25 = To DFUModel C Quantity

Forecast Reconciliation can begin its calculations with the first From DFUModel (working from the lowest level) or with the last To DFUModel (working from the highest level). To reconcile differences between the totals at each level, it adds forecast reconciliation records (rows in the Fcst table whose Fcst:Type is Reconcile) instead of changing values in existing forecast records. For example, to reconcile a forecast of 1000 that maps into a forecast of 800 at the next level, the system would add a forecast reconciliation record with a quantity of +200.

Given the following rows in the DFUMap table:

From DFUModel To DFUModel Factor

A D 0.5

B D 1.0 C D 1.0 DFUModels A, B, and C have forecasts of 400, 500, and 100, respectively. Through a Map DFUs process, they contribute 200, 500, and 100 to DFUModel D's forecast (a total of 800).

If you change DFUModel D's forecast to 1600 and then open a Forecast Reconciliation process (from highest level), the system spreads the new forecast to A, B, and C by determining the percentage contributed by each to the original forecast and then giving each the same percentage of the new forecast. To do that, it performs these calculations for each From DFUModel:

So, for example, it would calculate the new forecast for DFUModel A as:

0.25 x 1600=400

Similar calculations would be used if you changed the forecast for one From DFUModel that mapped into multiple To DFUModels, then opened a Forecast Reconciliation process (from lowest level).

FcstType


DFUMap

Option that controls which types of forecast are mapped into this DFUModel. The default value is ALL. Forecast types are based on the profiles defined in the DFUMapFcstProfile (on page 122) table.

FromDFULoc The location associated with the DFU from which forecast (or history) data is mapped.

FromDmdGroup The demand group associated with the DFU from which forecast (or history) data is mapped.

FromDmdUnit The demand unit associated with the DFU from which forecast (or history) data is mapped.

FromModel The model associated with the DFU from which forecast (or history) data is mapped.

HistType Option that controls which types of history are mapped into this DFUModel.

• 1: All Types

All quantities(except type 3) from the Hist table are mapped into this DFUModel.

• 2: Total Only

Type 1 history is mapped into this DFUModel.

• 3: Non-Base Only

Type 2 history is mapped into this DFUModel (history < > 1).

LevelNum Level number of this FromDmdUnit in the mapped network. The system determines the level of each FromDmdUnit in the mapped network and aggregates from the lowest level to the highest.

The level number of the FromModel, calculated by the system. The level number represents the relative position in the mapping of the FromModel/ToModel pair defined in that row. The first FromModel in a mapping is a FromModel that does not appear as a ToModel in any other row in the table. The first FromModel is at the lowest-numbered level in a mapping, which is level 0. The last FromModel in a mapping is a FromModel whose associated ToModel does not appear as a FromModel in any other row in the table. The last ToModel is at the highest-numbered level in a mapping.

The following diagram illustrates this relationship.

Figure 2: FromModel-ToModel relationship


DFUMap

When you add a new DFUMap table record, the system sets LevelNum to -1. When you execute a DFUMap process, the system determines the LevelNum for any row whose LevelNum is -1 and stores the value in the DFUMap table. (For each row in the DFUMap table, the system calculates the level number by determining whether the FromDmdUnit for the row appears as a ToDmdUnit in any other rows. If so, the system sets the LevelNum to one higher than the highest-numbered level in those other rows. If not, the system sets the level number to 0.) Thus, when the network has been set up and mapped once, the overhead of the leveling calculation is no longer incurred. A relevel option is provided in DFUMap processes, so levels may be compressed if there have been many deletions (resulting in empty levels).

LockEnd Indicates when locking ends for the From DFUModel in the row. As with LockStart, the demand calendar period containing the LockEnd date determines when the DFUModel is actually locked. For example, if forecast periods are weekly and begin 3/1/02, 3/8/02, 3/15/02, and so on, and the LockEnd date is 3/17/02, the entire forecast period that begins 3/15/02 would be locked.

Similarly, the system will also adjust the LockStart and LockEnd dates for a DFUModel to ensure that locking occurs when the DFU map is logically in effect. Therefore, the LockStart and LockEnd columns work with the DFUMap:Eff and DFUMap:Disc fields as follows:

• If a date is specified for DFUMap:Eff, the LockStart date will be adjusted if it occurs before the date the map becomes effective. The LockEnd date will also be adjusted if it occurs after the date for DFUMap:Disc.

• If LockStart is blank but a date is specified for LockEnd, the date for DFUMap:Eff is used as the start date. If DFUMap:Eff is also blank, the system will use the Demand Post Date for the DFU.

• If the LockEnd field is blank but a date is specified for DFUMap:Disc, the system uses the date for DFUMap:Disc. If that field is also blank, the DFU is always locked after the date specified for LockStart.

• If both the LockStart and LockEnd fields are blank or contain the same date, the DFUModel is always unlocked.

LockStart Indicates when locking begins for the From DFUModel in the DFU map row. Locking actually starts at the beginning of the demand calendar period that contains the LockStart date. For example, if you specify 3/10 as the LockStart date, but your forecast periods are weekly and begin 3/1, 3/8, 3/15, and so on, the DFUModel will actually start being locked on 3/8.

For more information about how the value for LockStart determines when a DFUModel is locked, see the description of the LockEnd (on page 121) column.

Map The map that maps data between the two DFUModels specified in this row. Up to 50 characters.

ToDFULoc The location associated with the DFU to which forecast (or history) data is mapped.

ToDmdGroup The demand group associated with DFU to which forecast (or history) data is mapped.

ToDmdUnit The demand unit associated with the DFU to which forecast (or history) data is mapped.

ToModel The model associated with the DFU to which forecast (or history) data is mapped.


DFUMapFcstProfile

DFUMapFcstProfile Table included with: Demand, Flowcasting


Default value

FcstTypeProfile 1 Demand, Flowcasting

TEXT ALL

Type1SW Demand, Flowcasting

OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1


OPTION_NUMBER

1 or 0 1

Table description The DFUMapFcstProfile table holds data about the various forecast profiles being used for mapping DFUs in the Map DFUs process.

Note: At least one type should be set to true.

Column descriptions FcstTypeProfile Name of the forecast profile.

The valid value for FcstTypeProfile must be any string.

Type1SW When selected, Base forecast will be mapped.

Type2SW When selected, Aggregate Market Activity forecast will be mapped.

Type3SW When selected, Static Lock Adjustment forecast will be mapped.

Type4SW When selected, Reconcile forecast will be mapped.

Type5SW JDA Demand Management Foundation Reference Guide 122 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFUMapFcstProfile

When selected, Promotion forecast will be mapped.

Type6SW When selected, Override forecast will be mapped.

Type7SW When selected, Market Activity forecast will be mapped.

Type8SW When selected, Data Driven Event forecast will be mapped.

Type9SW When selected, Impact of Target forecast will be mapped.


DFUMovingEventMap

DFUMovingEventMap Table included with: Demand, Flowcasting



TEXT


TEXT


TEXT

MovingEvent 4 Dmd, Flowcasting

TEXT

OverlapFactor Dmd, Flowcasting

DECIMAL 0.1

Table description The DFUMovingEventMap table stores the association between events and individual DFUs.




MovingEvent The name of the event attached to this DFU.

OverlapFactor The factor which decides the amount of overlap between two overlapping events. The default value for this column is 0.1.


DFUNPIRelation

DFUNPIRelation Table included with: Demand, Flowcasting


FromDmdUnit 1 Dmd, Flowcasting

TEXT

FromDmdGroup 2 Dmd, Flowcasting

TEXT

FromLoc 3 Dmd, Flowcasting

TEXT

FromModel 4 Dmd, Flowcasting

TEXT

ToDmdUnit 5 Dmd, Flowcasting

TEXT

ToDmdGroup 6 Dmd, Flowcasting

TEXT

ToLoc 7 Dmd, Flowcasting

TEXT

ToModel 8 Dmd, Flowcasting

TEXT

CreationDate Dmd, Flowcasting

DATE

Table description The DFUNPIRelation table defines the relationship between an old DFU and a new DFU involved in the process of introducing New DFUs through the New DFU Introduction functionality.

Column descriptions FromDmdUnit The DmdUnit of the old DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

FromDmdGroup The DmdGroup of the old DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

FromLoc The Location of the old DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

FromModel The Model of the old DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

ToDmdUnit The DmdUnit of the new DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

ToDmdGroup


DFUNPIRelation

The DmdGroup of the new DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

ToLoc The Location of the new DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

ToModel The Model of the new DFU that is in a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality.

CreationDate The date on which the new DFU is created using the New DFU Introduction functionality.


DFUProjDraftStatic

DFUProjDraftStatic Table included with: Demand


BaseFcst Dmd DECIMAL 0.0

BaseHist Dmd DECIMAL 0.0 DataDrivenEvents

Dmd DECIMAL 0.0

DmdGroup 2 Dmd TEXT DmdUnit 1 Dmd TEXT Dur Dmd DURATION 0 FcstOverride Dmd DECIMAL 0.0 InternalEvents Dmd DECIMAL 0.0 JobID Dmd INTEGER 0 Loc 3 Dmd TEXT MarketActivity Dmd DECIMAL 0.0 Model 5 Dmd TEXT NonBaseHist Dmd DECIMAL 0.0 StartDate 4 Dmd DATE TotFcst Dmd DECIMAL 0.0 TotHist Dmd DECIMAL 0.0 TotHistFcst Dmd DECIMAL 0.0 UserID Dmd TEXT ' '

Table description Each row in this table projects data for a DFU for a particular time period. When you run a Store Derived Table process in JDA Demand and select DFUProj data and FcstDraft table, the system stores the data for the DFUs you select in this table. You cannot edit the columns in this table.

You can view this table in Flexible Editor or using the DFUProjDraftStatic page in JDA Demand, and export the data to an external system.

Column descriptions BaseFcst Statistically forecasted demand for the period. For this DFU and period, BaseFcst is the sum of the values in the Fcst:Qty column for each Fcst table row whose Type is 1 (Statistical).

BaseHist Actual demand for the DFU as sold through regular channels. The system uses this quantity when fitting a model and when updating the forecast.

For Fourier, MLR, and Imported MLR models, Base History = Type 1 - Type 2 History. For Lewandowski models, Base History = Type 1 - Type 2 - Type 3 History.

DataDrivenEvents The quantity of the data driven event’s forecast (where Fcst:Type = 8 or Hist:Type = 3) for the demand period defined in this row.


DFUProjDraftStatic

This column is only used with Lewandowski models.


DmdUnit The demand unit associated with the DFU whose projections appear in this row.

Dur The duration in minutes of the time period whose values are stored in this row. The beginning date of this period is StartDate and the beginning date of the next period is StartDate + Dur.

FcstOverride The quantity of the forecast override (where Fcst:Type = 6) for the demand period defined in this row.

InternalEvents Internally-driven events for the period. For this DFU and period, InternalEvents is the sum of the values in the Fcst:Qty column for each Fcst table row whose Type is 2 (Internal Event).

JobID The identifier of the job that created the data stored in this table. When a user runs a Store Derived Table process, the system automatically assigns a job identifier, which is stored in this column.


MarketActivity The quantity of the market activity (where Fcst:Type=7) for the demand period defined in this row. This value is entered via JDA Market Manager application.


NonBaseHist Actual demand for the DFU not sold through regular channels (a promoted item, for example). The system does not use this quantity when fitting a model or when updating the forecast.

For each period, the system calculates NonBaseHist as the total of Hist:Qty with a Type of 2 (Non-Base History).

StartDate The beginning or ending date and time for the time interval associated with the projections in this row. (Allocation Period Date, set as a page property, determines whether Date represents the beginning or ending date of the period.) The system bases time intervals on the Calendar specified.

TotFcst Total forecast for the period. Sum of forecast types 1-9.

TotHist All Type 1 History.

TotHistFcst Displays total history and forecast values for the period. All values up to Demand Post Date are History and all values beyond Demand Post Date are Forecast.

UserID The identifier of the user that ran the Store Derived Table process that created the data stored in this table. When a user runs a Store Derived Table process, the system automatically detects the user identifier and stores it in this column. JDA Demand Management Foundation Reference Guide 128 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFUProjDraftStatic


DFUProjStatic

DFUProjStatic Table included with: Demand, Flowcasting


BaseFcst Dmd, Flowcasting

DECIMAL 0.0

BaseHist Dmd, Flowcasting

DECIMAL 0.0

DataDrivenEvents

Dmd, Flowcasting

DECIMAL 0


TEXT


TEXT


DURATION 0

FcstOverride Dmd, Flowcasting

DECIMAL 0

InternalEvents Dmd, Flowcasting

DECIMAL 0.0

JobID Dmd, Flowcasting

INTEGER 0


TEXT

MarketActivity Dmd, Flowcasting

DECIMAL 0


TEXT

NonBaseHist Dmd, Flowcasting

DECIMAL 0.0


DATE

TotFcst Dmd, Flowcasting

DECIMAL 0.0

TotHist Dmd, Flowcasting

DECIMAL 0.0

TotHistFcst Dmd, Flowcasting

DECIMAL 0.0


TEXT ' '

Table description Each row in the DFU Projections Static table projects data for a DFU for a particular time period. When you run a Store Derived Table process in JDA Demand and select DFUProj data and the Fcst table, the system stores the data for the DFUs you select in this table. You cannot edit the columns in this table.

You can view this table in Flexible Editor or using the DFUProjStatic page in JDA Demand, and export the data to an external system. JDA Demand Management Foundation Reference Guide 130 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFUProjStatic

Column descriptions BaseFcst Statistically forecasted demand for the period. For this DFU and period, BaseFcst is the sum of the values in the Fcst:Qty column for each Fcst table row whose Type is 1 (Statistical).

BaseHist Actual demand for the DFU as sold through regular channels. The system uses this quantity when fitting a model and when updating the forecast.

For Fourier, MLR, and Imported MLR models, Base History = Type 1 - Type 2 History. For Lewandowski models, Base History = Type 1 - Type 2 - Type 3 History.

DataDrivenEvents The quantity of the data driven event’s forecast (where Fcst:Type = 8 or Hist:Type = 3) for the demand period defined in this row.

This column is only used with Lewandowski models.


DmdUnit The demand unit associated with the DFU whose projections appear in this row.

Dur The duration of the time interval that applies to the data in this row, based on the calendar specified.


InternalEvents Internally-driven events for the period. For this DFU and period, InternalEvents is the sum of the values in the Fcst:Qty column for each Fcst table row whose Type is 2 (Internal Event).

JobID The identifier of the job that created the data stored in this table. When a user runs a Store Derived Table process, the system automatically assigns a job identifier, which is stored in this column.




NonBaseHist Actual demand for the DFU not sold through regular channels (a promoted item, for example). The system does not use this quantity when fitting a model or when updating the forecast.

For each period, the system calculates NonBaseHist as the total of Hist:Qty with a Type of 2 (Non-Base History).

StartDate


DFUProjStatic

The beginning or ending date and time for the time interval associated with the projections in this row. (Allocation Period Date, set as a page property, determines whether Date represents the beginning or ending date of the period.) The system bases time intervals on the Calendar specified.

TotFcst Total forecast for the period. Sum of forecast types 1-9.

TotHist All Type 1 History.

TotHistFcst Displays total history and forecast values for the period. All values up to Demand Post Date are History and all values beyond Demand Post Date are Forecast.

UserID The identifier of the user that ran the Store Derived Table process that created the data stored in this table. When a user runs a Store Derived Table process, the system automatically detects the user identifier and stores it in this column.


DFUTOE3FCST

DFUTOE3FCST Table included with: Demand, Fulfillment, Flowcasting


COMPANY Demand, FF, Flowcasting

TEXT

E3ERROR Demand, FF, Flowcasting

DECIMAL 0

E3LOC Demand, FF, Flowcasting

TEXT

FCSTDELETED Demand, FF, Flowcasting

OPTION 0

FCSTID 4 Demand, FF, Flowcasting

TEXT

ITEM 1 Demand, FF, Flowcasting

TEXT

LOCTYPE Demand, FF, Flowcasting

OPTION 0

PER1FCST - PER52FCST

Demand, FF, Flowcasting

DECIMAL 0

SKULOC 2 Demand, FF, Flowcasting

TEXT

STARTDATE Demand, FF, Flowcasting

DATE 01/01/1970

TYPE 3 Demand, FF, Flowcasting

OPTION

Table description The DFUtoE3Fcst table is used for receiving the forecast from the Transfer Forecast process for transferring to E3. The table stores the generated DFU level forecast as the corresponding SKU forecast. The table accommodates 52 periods of forecast

Column descriptions COMPANY Represents the name of the company to which the SKU corresponds in AWR.

E3 ERROR The MADP (Mean Absolute Deviation expressed as a Percentage) assigned to the item for expressing the forecast error of the forecast imported from Demand.

MADP is the amount of variability present in the demand of an item in AWR, which contributes to the amount of safety stock that is included in the ordering routines.

E3LOC The corresponding location of the SKU in E3 AWR.

FCSTDELETED This switch is used to identify deleted promotions. The switch allows E3 to cleanup outdated forecast records.


DFUTOE3FCST

FCSTID FcstID is the name of the forecast, the quantity for which appears in this row. FcstID can be the name of a promotion, event or market activity.

ITEM Item is the unique identity for a product / SKU.

LOC_TYPE Represents the type of location as defined in E3 AWR.

PER1FCST - PER52FCST Forecast value to be transferred to E3 AWR for period 1 to period 52.

SKULOC The location at which the SKU is based.

STARTDATE The startdate from which the forecast needs to be transferred to E3 AWR.

TYPE Represents the Demand forecast types that are eligible for import into E3 AWR. Type 1 in AWR indicates base forecast, which includes Type 1, Type 3, Type 4, Type 6, and Type 9 forecasts in Demand. Type 2 in AWR indicates promotional forecast, which includes Type 2, Type 5, Type 7, and Type 8 forecast in Demand.


DFUToEPFcst

DFUToEPFcst Table included with: Demand, Flowcasting



TEXT


TEXT


INTEGER


TEXT

Model Dmd, Flowcasting

TEXT


DECIMAL


DATETIME TO_DATE('01/01/1970','MM/DD/YYYY')

Table description The DFUtoEPFcst table is used to receive forecast values from the Transfer Forecast process and transfer them to JDA Enterprise Planning (EP). The table stores the forecast quantities generated by JDA Demand. In order to use Transfer Forecast process and the data in this table, you must be licensed for Demand as well as for EP.

Column descriptions DmdGroup The demand group associated with the DFU from which forecast demand data is mapped.

DmdUnit The demand unit associated with the DFU from which forecast demand data is mapped.

Dur The interval covered by the forecast defined in this row.

Loc The location associated with the DFU from which forecast demand data is mapped.

Model The model associated with the DFU from which forecast demand data is mapped.

Qty The quantity of the DFU forecast to be transferred during the given period.

StartDate The date from which the forecast needs to be transferred.


DFUToItxFcst

DFUToItxFcst Table included with: Demand, Flowcasting


Item 1 Dmd, Flowcasting

TEXT


TEXT


DATE


INTEGER

FiscalYear Dmd, Flowcasting

INTEGER

FiscalPeriod Dmd, Flowcasting

INTEGER


DECIMAL

Table description The DFUtoItxFcst table is used for receiving the forecast from the Transfer Forecast process for transferring to Intactix space management. The table stores the generated DFU level forecast as the corresponding SKU forecast.

Intactix Intactix uses the transferred forecast values as an input for space management.

Column descriptions Item The item associated with the SKU to which forecast demand data is mapped.


StartDate The start date of the mapped forecast.


FiscalYear Determines the fiscal year.

FiscalPeriod Determines the fiscal period.

Qty Determines the quantity of the DFU forecast to be transferred during the given period.


DFUToSKU

DFUToSKU Table included with: Demand, Dynamic Demand Response, Fulfillment, Inventory Policy Optimization, Master Planning, Supply, Flowcasting, Enterprise Supply Planning


Default value

AllocFactor Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

DECIMAL 1.0

ConvFactor Dmd, DDR, IPO, MP, Supp, Flowcasting, ESP

DECIMAL 1.0

DFULoc 5 Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

TEXT

Disc 7 FF, MP, Supp, Dmd, MDO, IPO, Flowcasting, ESP

DATETIME

DmdGroup 4 Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

TEXT

DmdUnit 3 Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

TEXT

Eff 6 Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

DATETIME

FcstType Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4 1

HistType Dmd, DDR, FF, MP, Supp, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4 1

Item 1 Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

TEXT

Model Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

TEXT ' '

SKULoc 2 Dmd, DDR, FF, IPO, MP, Supp, Flowcasting, ESP

TEXT

SupersedeSw FF, Flowcasting BOOLEAN 0

Table description


DFUToSKU

Each row in this table defines a mapping used to map data from one specific DFU to a specific SKU. A unique DFU can be mapped to many SKUs, and many DFUs can be mapped to the same SKU. This table is used by the Transfer Forecast process to map forecast from DFUs to SKUs. The resulting forecast is stored in the DFUToSKUFcst table. In order to use this process and the data in this table, you must be licensed for JDA Demand, as well as JDA Fulfillment, Master Planning, Supply, or Inventory Policy Optimization.

Column descriptions AllocFactor AllocFactor determines what portion of the DFU's quantity is allocated to the SKU. When you run the Calculate Plan or Statistical Safety Stock process or open a page that includes SKUProjStatic:TotFcst, the system calculates the amount to allocate to the SKU as:

Qty x AllocFactor x ConvFactor

ConvFactor Conversion Factor is used for converting from one unit of measure to another (for example, if forecasts use one unit of measure and plans use a different one). When you run the Forecast Transfer process, the system calculates the amount to allocate to the SKU as:

Qty x AllocFactor x ConvFactor

DFULoc The location associated with the DFU.

Disc The date when this mapping is discontinued.

Together, Disc and Eff (on page 138) determine when the mapping is effective. Following is a summary of the results of all possible combinations of values for Disc and Eff.







DmdGroup The demand group associated with the DFU.

DmdUnit The product associated with the DFU from which data is mapped.

Eff The date when this mapping becomes effective.

Eff and Disc (on page 138) work together to determine when the mapping is effective. The chart under Disc summarizes the results of all possible combinations of values for Eff and Disc.

FcstType


DFUToSKU

Used only on systems that also include either Fulfillment/Distribution, Master Planning, or IPO. Option that controls which types of forecast are mapped into this SKU.

• 1: All Types

All quantities from the Fcst table are mapped into this SKU.

• 2: Base Only

Only forecast quantities whose type is Base (Fcst:Type = 1) are mapped into this SKU.

• 3: Non-Base

All forecast quantities for locks, reconciliation, overrides, market activities, data driven events, and targets are mapped into this SKU.

• 4: None

No forecast quantities are mapped into this SKU.

HistType This column is not used in the current release.

Item The item associated with the SKU to which data is mapped.

Model The model associated with the DFU. This column is used by the Calculate Statistical Safety Stock process to determine from which model to get DFU:StatMSE or DFU:NetFcstError.

IPO Note: This column is not used by IPO in this release.

SKULoc The location associated with this SKU.

SupersedeSw Switch that identifies which mappings of demand data from a DFU to a SKU can be superseded and which cannot.

• Y: Can be superseded

• N: Cannot be superseded

This switch allows you to define customer-specific supersession rules. This rule may vary for each DmdGroup. For example, you can set this switch to No for all CustomerA DFUToSKU maps and Yes to all others for a new version of a particular product. In such a case, when you run the Supersession logic, the system considers CustomerA demand as not substitutable when it attempts to exhaust the older version of the product. On the other hand, the system sees other customer demand for this product with DFUToSKU mappings set to Yes as allowing the substitution of older product supply to meet the demand. See the JDA Fulfillment OnLine Expert for more information on working with the Supersession feature.


DFUToSKUFcst

DFUToSKUFcst Table included with: Fulfillment, Demand, Master Planning, Supply, Inventory Policy Optimization, Dynamic Demand Response, Flowcasting, Enterprise Supply Planning


DFULoc 5 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

TEXT

DmdGroup 4 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

TEXT

DmdUnit 3 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

TEXT

Dur 7 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

DURATION

Item 1 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

TEXT

SKULoc 2 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

TEXT

StartDate 6 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

DATETIME 01/01/1970

SupersedeSw 9 FF, Dmd, MP, Supp, IPO, Flowcasting

BOOLEAN 0

TotFcst FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

DECIMAL 0

Type 8 FF, Dmd, MP, Supp, IPO, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4,5,6,7,8,9,99

Table description Each row of this table represents a forecasted demand that has been mapped to a SKU from a DFU. The forecasted demand for the DFU is stored in the Fcst table and mapped to the SKU through the Transfer Forecast process using the mapping information in the DFUToSKU table.

IPO JDA Demand Management Foundation Reference Guide 140 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFUToSKUFcst

IPO uses the transferred forecast values to calculate the mean daily demand.

Column descriptions DFULoc The location associated with the DFU from which forecast demand data is mapped.

DmdGroup The demand group associated with the DFU from which forecast demand data is mapped.

DmdUnit The product associated with the DFU from which forecast demand data is mapped.


Item The item associated with the SKU to which forecast demand data is mapped.

SKULoc The location associated with this SKU.

StartDate The start date of the mapped forecast.

SupersedeSw Supersede switch (SupersedeSw) identifies which forecast demands that have been mapped to a SKU from a DFU can be superseded and which demands cannot.

• Y: Can be superseded

• N: Cannot be superseded

IPO, Master Planning, and Supply This column is only configured for these applications because it is a primary key column and all primary key columns must be configured for all applications that use a given table.

TotFcst The quantity of the mapped forecast.

Type Indicates the type of forecast that was mapped into this SKU and is represented by this data row. Valid values are 1 - 9 and 99.


DFUTotalVol

DFUTotalVol Table included with: Demand, Flowcasting



TEXT


TEXT


TEXT


TEXT

TotalVol Dmd, Flowcasting

DECIMAL 0

Table description The DFUTotalVol table stores the total volume for the DFU. This total volume of the DFU is distributed proportionally across associated periods specified in the option set of the Reconcile Forecast process. The distributed volume is allocated to the other DFUs present in the corresponding selected DFUMap. For example, the total volume of 5,000 for the ‘Office Furniture’ category level DFU is allocated across all selected periods and then across DFUs that contribute to this category.

Column descriptions DmdUnit The demand unit associated with the DFU.


Loc The location associated with the DFU.

Model The model used by the Calculate Model process to identify the history stream and algorithm associated with the DFU.

TotalVol The total volume allocated to the DFU. The total volume can be any positive number.


DFUToWFMFcst

DFUToWFMFcst Table included with: Demand, Flowcasting



TEXT


TEXT


INTEGER


TEXT


DECIMAL


DATETIME TO_DATE('01/01/1970','MM/DD/YYYY')

Table description The DFUtoWFMFcst table is used to receive and transfer forecast values from the Transfer Forecast process to JDA Workforce Management (WFM). The table stores the forecast quantities of WFM integrated DFUs generated by JDA Demand. In order to use Transfer Forecast process and the data in this table, you must be licensed for Demand as well as for WFM.

WFM WFM uses the transferred forecast values to calculate the mean daily demand.

Column descriptions DmdGroup The demand group associated with the DFU from which forecast demand data is mapped.




Qty The quantity of the DFU forecast to be transferred during the given period.

StartDate The date from which the forecast needs to be transferred.


DFUView

DFUView Table included with: Demand, Demand Decomposition, Markdown Optimization, Dynamic Demand Response, Promotions Management, Strategic Pricing, Travel Price Optimization, Fulfillment


Default value

AllocCal Dmd, DDR,PM, Flowcasting

TEXT

AllocCalGroup Dmd, DDR, Flowcasting

TEXT

AllocCalProfile Dmd, DDR, Flowcasting

TEXT ' '

AttachRateRelationType

Dmd, Flowcasting

INTEGER 0

CalculateDmdToDateSw

Dmd, DDR, Flowcasting

BOOLEAN 1

DDRParamProfileName


TEXT

DDRGroup Dmd, DDR, Flowcasting

TEXT ' '

DmdGroup 2 Dmd, Dmd Decomp, PM, MDO, SP, DDR, Flowcasting

UPPER_TEXT

DmdtoDateBase Dmd, DDR, Flowcasting

INTEGER 0

DmdToDateNonBase


INTEGER 0

DmdUnit 1 Dmd, Dmd Decomp PM, MDO, SP, DDR, Flowcasting

UPPER_TEXT

Loc 3 Dmd, Dmd Decomp PM, MDO, SP, DDR, Flowcasting

UPPER_TEXT

LLOverride Dmd, DDR, Flowcasting

DECIMAL 0

LogScaleSw Dmd, DDR, Flowcasting

INTEGER 0

MasterCal Dmd, DDR TEXT ' ' MasterCalRule Dmd, DDR,

Flowcasting INTEGER 2

PriceProfileName Dmd, Dmd Decomp PM, MDO, DDR, Flowcasting

TEXT ' '

PrimaryDFUSw Dmd, DDR, Flowcasting

BOOLEAN 0


DFUView


Default value

Image Dmd UPPER_TEXT

ULOverride Dmd, DDR, Flowcasting

DECIMAL 0

Table description For all processes that write data to the Fcst table—that is, where you select the Published option for Forecast Version—DFUView is used to derive the DmdUnit, DmdGroup, and Loc keys for the DFU search. The Fcst table is the only table that uses the DFU search; other demand tables use the DFUModel search, in which the primary key includes the Model column in addition to DmdUnit, DmdGroup, and Loc.

If you have only one model, you can define a search based on this table and it can be used for all DFU Model-based tables, all DFU-based tables, and all DFUHistStream tables.

If you would like to use a user-defined column to specify information for all DFU Models, you can add it to this table. Once user-defined columns are added to this table, you can add those columns to all DFU-based Flexible Editor pages, including DFU, Fcst, and Hist pages.

Column descriptions AllocCal The Generate Allocation Calendar for DFUs process updates the allocation calendar you define here with the daily allocation profile for the DFU based on the customer order history.

For more information on allocation calendars, refer SKUDemandParam: AllocCal.

AllocCalGroup Use AllocCalGroup to specify the allocation calendar name while generating allocation calendars. If a value is not specified for this column while generating allocation calendars the process throws an exception and the DFU will not be processed.

You can also use AllocCalGroup to group DFUs while generating allocation calendars. The Generate Allocation Calendar for DFUs process generates allocation calendars for DFUs based on the customer order history of a group of DFUs. You can group the DFUs by giving the same value to this column to all DFUs.

For example, you can set separate allocation calendars for retailers as follows:

DMDGroup DMDUnit AllocCalGroup

Retailer A small_red RetailerA_red

Retailer A medium_red RetailerA_red Retailer A large_red RetailerA_red Retailer B small_red RetailerB_red Retailer B medium_red RetailerB_red Retailer B large_red RetailerB_red By grouping the allocation calendar based on Retailer A and red shirts, the allocation weights provides a pattern in which red shirts (small, medium, and large) are ordered by Retailer A.

AllocCalProfile


DFUView

AllocCalProfile is used to generate time phased allocation calendar.

AttachRateRelationType A value that defines the type of the DFU according to the relationship. The values 1 and 2 are set when you define a relationship in the DFUAttachRateRelation table. The value 3 is set after the Calculate Historical Attach Rates process is run. The default value is blank.

• Blank: Generic DFU

• 1: Source DFU

• 2: Target DFU

• 3: Attach Rate DFU

CalculateDmdToDateSw This switch specifies whether the DmdToDate should be calculated automatically by the Calculate DDR process.

DDRParamProfileName The profile name attached to the parameters that are used to run Calculate Dynamic Demand Response process. The value you use here should exist in DDRParamProfile: DDRParamProfileName.

DDRGroup The DDRGroup associated with the DFU. For the DFUs to be in a group, they must have common DDRGroup name.


DmdToDateBase Base customer orders received between from base FCST: StartDate (on page 157) until the Start date you define in the process page. The proration logic of Calculate Dynamic Demand Response process (DDR) uses DmdToDateBase and DmdToDateNonBase to perform forecast proration when DDRParamProfile: BaseProrateOpt is set to 2.

For information on the proration logic of DDR process, see Understanding Calculate Dynamic Demand Response process in the OnLine Expert.

DmdToDateNonBase Nonbase customer orders received from first nonbase FCST:StartDate (on page 157) till the Start Date you define in the process page. The proration logic of the Calculate Dynamic Demand Response process (DDR) uses DmdToDateBase and DmdToDateNonBase to perform forecast proration when DDRParamProfile: NonBaseProrateOpt is set to 2.

For information on the proration logic of DDR process, see Understanding Calculate Dynamic Demand Response process in the OnLine Expert.



LLOverride LLOverride is the specified lower limit of the aggregated order values for identifying partial orders. If the order value is lower than this value, it is treated as a partial order and such orders are not used in calculating the statistics for identifying promotions. The usage of this value for identifying partial orders depends on the options selected on the Calculate Dynamic Demand Response process page.

LogScale


DFUView

LogScale specifies whether the statistics should be calculated using logarithmic values or the original values. The default value is 0, indicating the use of original values for calculating the statistics. If the value is changed to one (1), all statistics are calculated using the logarithmic values.

MasterCal The Master Calendar associated with the DFU.

MasterCalRule MasterCalRule is used to move the forecast quantity of the closed day as specified in master calendar. The transfer of this forecast quantity can be based on the following rules:

• 1: Move to prior open day

The allocated forecast quantity for the closed days is moved to the prior open day.

• 2: Re-adjust the week

The allocated forecast quantity for the closed days is re-adjusted across the week.

• 3: Move to next open day

The allocated forecast quantity for the closed days is moved to the next open day.

• 4: AllocCal Generation

Integrates master calendar with allocation calendar generation process.

PriceProfileName The name of the price profile, stored in the PriceProfile table, associated with this DFU.

PrimaryDFUSw Switch that determines PrimaryDFU in the DFU group. You select a DFU as a PrimaryDFU (that will set it to 1). There must be at least one primary DFU for a DFU group.

Valid values for PrimaryDFUSw are:

• 0 - Not a primary DFU

• 1 - Primary DFU

Notes:

• If more than one DFU is flagged as Primary DFU then the first Primary DFU in the list alphabetically, is considered as Primary DFU.

• If none of the DFUs in a DDRGroup is defined as primary DFU, the group will not get processed.

Image The product image URL for this DFU. The image stored in this URL is displayed on the Display Image panel of Demand Workbench. This URL can be a web URL or context-root URL in the Demand setup.

ULOverride ULOverride is the specified upper limit of the aggregated order values for identifying promotional orders. If the order value is greater than this value, it is identified as a promotional order. The usage of this value for identifying promotional orders depends on the options selected on the Calculate Dynamic Demand Response process page.


DmdGroup

DmdGroup Table included with: Demand, Demand Decomposition, Strategic Pricing, Markdown Optimization, Dynamic Demand Response, Promotions Management, Travel Price Optimization, Fulfillment


Descr Dmd, Dmd Decomp, SP, MDO, DDR, PM, Flowcasting

TEXT ' '

DmdGroup 1 Dmd, Dmd Decomp, SP, MDO, DDR, PM, Flowcasting

TEXT

Table description Each row in this table defines a demand group. A demand group, demand unit, and location make up a demand forecasting unit (DFU).

Column descriptions Descr An optional description of this demand group.

DmdGroup The demand group defined in this row. The demand group might be a customer account, for example.


DmdUnit

DmdUnit Table included with: Demand, Demand Decomposition, Strategic Pricing, Markdown Optimization, Dynamic Demand Response, Promotions Management,and Travel Price Optimization, Fulfillment



Brand SP TEXT ' '

Collection MDO TEXT ' ' Descr Dmd, Dmd

Decomp, SP, MDO, DDR, PM, Flowcasting

UPPER_TEXT ' '

DmdUnit 1 Dmd, Dmd Decomp, SP, MDO, DDR, PM

TEXT

IgnorePricingLvlSw

SP BOOLEAN 0, 1 0

OnOrderQty MDO DECIMAL 0.0 PackSize Dmd Decomp,

PM, SP INTEGER 1

PriceLink SP TEXT ' ' UnitSize Dmd Decomp,

PM, SP DECIMAL 1

UOM Dmd Decomp, PM, SP

INTEGER 0

WDDCategory Dmd UPPER_TEXT

Table description Each row in this table defines a demand unit. A demand unit, demand group, and location make up a demand forecasting unit (DFU).

This table is also used to link similar demand units to apply price recommendations for one, to all demand units with the same price link.

Column descriptions Collection Displays the collection value defined for this demand unit. A collection is a group of demand units on sale.

Demand units that belong to the same collection value are optimized together as a single collection during Markdown Optimization.

Note: The demand units in this collection must be marked down at the same time and for the same amounts.

Brand Product brand of the associated demand unit.


DmdUnit

Descr An optional description of this demand unit.

DmdUnit The demand unit defined in this row. A demand unit is a product —corresponding to the item in an SKU.

IgnorePricingLvlSw Retailer may have key items that they focus upon from a competitive standpoint. These items are often compared to local competitors and priced accordingly. The IgnorePricignLvlSw allows the retailer to identify specific items as being exceptions to the standard chain or zone pricing policies. Valid values are

• 0 - Adhere to the defined pricing level when pricing these items.

• 1 - Ignore the pricing level and recommended store-level prices when pricing this item.

OnOrderQty The total remaining quantitity to be received in the future. Markdown Optimization uses this value as the OnOrderQty in the Markdown Workbench when DRM.MD.UI.ONORDERQTY is set to DMDUnit.

PackSize Represents total number of units in a pack.

PriceLink The link between products that should be priced the same in a given location and dmdgroup.

For example, a brand of aerated beverage may be sold with multiple flavors.By assigning all flavors to a pricelink you force Strategic Pricing to recommend a single price for all items in the pricelink.

UnitSize Represents the quantity that each unit carries in a pack size. See PackSize (on page 150).

UOM The unit of measure ID is defined in this row. Following are the valid ranges for the UOM IDs:

• 0 - 11000 is reserved for system UOMs.

• 11000 - 19999 is reserved for user-defined UOMs that are migrated from the 6.2 release.

• 20000 and above is reserved for new user-defined UOMs.

The UOMs available are as follows:

1 - Acre 22 - Kilometer 43 - Cubic Meter

2 - Square Foot 23 - Meter 44 - Cubic Yard 3 - Square Centimeter 24 - Mile 45 - Fluid Ounce 4 - Square Inch 25 - Millimeter 46 - Gallon 5 - Square Kilometer 26 - Yard 47 - Liter 6 - Square Meter 27 - Foot 48 - Pint 7 - Square Mile 28 - hour 49 - Quart

8 - Square Yard 29 - 12 Hour 50 - Pound

9 - BRR 30 - 16 Hour 51 - Grain 10 - CAD 31 - 24 Hour 52 - Gram 11 - EUR 32 - 4 Hour 53 - Kilogram 12 - GBP 33 - 40 Hour 54 - Metric Pound 13 - JPY 34 - 8 hour 55 - Metric Ton


DmdUnit

14 - SEK 35 - Day 56 - Milligram 15 - USD 36 - Minute 57 - Ounce 16 - US Cent 37 - Month 58 - Ton 17 - Dozen 38 - Week 59 - Percent 18 - Unit 39 - Year 95 - Pallet

19 - P24Pack 40 - Cubic Centimeter 100 - Default Weight Unit

20 - Centimeter 41 - Cubic Foot 700 - Default Volume Unit

21 - Inch 42 - Cubic Inch 800 - AltShip Unit


Event

Event Table included with: Demand, Flowcasting


ConvCol Dmd, Flowcasting

INTEGER 0

ConvTab Dmd, Flowcasting

INTEGER 0

CreatedBy Dmd, Flowcasting

TEXT ' '

CreatedDate Dmd, Flowcasting



TEXT ' '


DURATION 0

Event 1 Dmd, Flowcasting

TEXT

EventType Dmd, Flowcasting

TEXT ' '

ModifiedBy Dmd, Flowcasting

TEXT ' '

ModifiedDate Dmd, Flowcasting




Table description Note: The Event Manager feature is no longer supported by JDA Demand. It is now supported by JDA Market Manager. Data stored in this table is transferred to Market Manager during Market Manager/Demand integration.

Each row in this table holds information about one master event. A master event can consist of multiple subevents. A subevent defines the relationship of the event to one DFUModel.

Note: This table is not used in this release.

Column descriptions ConvCol


Event

Column number of a numeric column used to convert Event quantities to a different unit of measure when displaying them in Event Manager. This may be a user-defined column but is should be the column number of an existing column in the database.

For example, you might create a column called SalesPrice. If you specify SalesPrice as the ConvCol for an event, the system multiplies the value of ConvCol by the event quantities before displaying them on the Event Manager.

ConvTab Table number of the table that contains the conversion column (ConvCol). This value should be the table number of an existing table in the database.

CreatedBy The user who created this event.

CreatedDate Date this event was created.

Descr Description of this event.

Dur Duration of this entire event.

Event Identifier of the master event defined in this row.

EventType The type of this event, such as Coupon or Trade Discount. Events types are defined in the EventType table.

ModifiedBy User who modified the event.

ModifiedDate Date the event was modified.

StartDate The beginning date and time of this entire event.


EventType

EventType Table included with: Demand, Flowcasting



TEXT ' '

EventType 1 Dmd, Flowcasting

TEXT

InternalEventSw Dmd, Flowcasting

BOOLEAN 0

Table description Note: The Event Manager feature is no longer supported by Demand. It is now supported by Market Manager. Data stored in this table is transferred to Market Manager during Market Manager/Demand integration.

Each row in this table identifies a specific event type such as Coupon or Trade Discount. This identification provides a way to categorize events by type.

Note: This table is not used in this release.

Column descriptions Descr Description of this event type.

EventType The event type described in this row.

InternalEventSw Determines whether quantities associated with this event type will be considered internal or external events.

This distinction is for your information only. The system uses this switch to determine the Fcst:Type when it puts quantities for an event of this type into the Fcst table. It treats both types the same except when calculating the total External Event Forecast and Internal Event Forecast for the DFUProjStatic table.

• No: External event

When quantities for an event of this type are put into the Fcst table, the Fcst:Type is 5 (External Event).

• Yes: Internal event

When quantities for an event of this type are put into the Fcst table, the Fcst:Type is 2 (Internal Event).


Fcst

Fcst Table included with: Master Planning, Supply, Demand, Strategic Pricing, Markdown Optimization, Dynamic Demand Response, Promotions Management, Travel Price Optimization, Flowcasting, Enterprise Supply Planning


DmdGroup 2 MP, Supp, Dmd, SP, MDO, PM, TPO, Flowcasting, ESP

TEXT

DmdUnit 1 MP, Supp, Dmd, SP, MDO, PM, TPO, Flowcasting, ESP

TEXT

Dur MP, Supp, Dmd, SP, MDO, PM, Flowcasting, ESP

DURATION 1440

FcstID 6 MP, Supp, Dmd, SP, MDO, PM, Flowcasting, ESP

TEXT

LewMeanQty MP, Supp, Dmd, SP, MDO, PM, Flowcasting, ESP

DECIMAL 0

Loc 3 MP, Supp, Dmd, SP, MDO, PM, TPO, Flowcasting, ESP

TEXT

MarketMgrVersionID

MP, Supp, Dmd, SP, MDO, PM, Flowcasting, ESP

INTEGER -1

Model MP, Supp, Dmd, SP, MDO, PM, Flowcasting, ESP

TEXT ' '

Qty MP, Supp, Dmd, SP, MDO, PM, TPO, Flowcasting, ESP

DECIMAL 0

StartDate 4 MP, Supp, Dmd, SP, MDO, PM, TPO, Flowcasting, ESP

DATE


Fcst


Type 5 MP, Supp, Dmd, SP, MDO, PM, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4,5,6,7,8, 9,99

Table description Each row in this table identifies a quantity of forecast demand associated with a particular DFUModel over a specified period of time.

Caution: Do not use Flexible Editor to edit the data in this table.

In JDA Demand, the Calculate Model process calculates forecasts and stores them in this table. For each time period, you can publish only one model per DFU. If multiple models exist in the FcstDraft table for a DFU, you select which model you would like to publish for that particular DFU.

If more than one model is published per time period for a DFU, the system saves only the last model you published for that time period.

Caution: If the FcstDraft table contains user-defined columns, include those columns in the Fcst table to ensure that draft and published forecasts reflect the same information.

Supply To use the data available in the Fcst table, you must be licensed for JDA Demand, as well as JDA Supply.

Column descriptions DmdGroup The demand group associated with the DFU whose forecast is defined in this row.

DmdUnit The demand unit associated with the DFU whose forecast is defined in this row.

Dur The length of the time interval that starts at StartDate. Valid values are 0 or greater.

FcstID The name of the forecast whose quantity appears in this row.

• If the Type is 1 (Base), the system leaves this column blank, regardless of whether you adjusted the forecast.

• If the Type is 2 (Aggregate Market Activity), the system set the FcstID to AGG_MKTACTIVITY if you are using DFU mapping and Type 7 forecast records exist for a lower-level DFU, those records are aggregated to create a Type 2 record for the higher-level DFU.

• If the Type is 3 (Total Forecast Lock Adjustment), the system assigns the name TotLock, if the lock was set using DFU:TotFcstLock. If the lock was set using the Lock Forecast feature, the system assigns the name FcstLock. If the lock is added through Flexible Allocation, the system assigns the name specified in Flexible Allocation.

• If the Type is 4 (Reconcile), the system sets FcstID to the name of the map used for forecast reconciliation. If the reconciliation was added through Flexible Allocation, the system assigns the name specified in Flexible Allocation.

• If the Type is 5 (Promotion), the Import Forecast process sets the FcstID to the corresponding value specified in the ForecastRecordImport (on page 171) table.


Fcst

• If the Type is 6 (Override), the system assigns the name Override.

• If the Type is 7 (Market Activity), the system assigns the first 50 characters of the name of the market activity (defined in JDA Market Manager) that created the forecast. (The maximum name length in Market Manager is 256.)

• If the Type is 8 (Data Driven Event), the system sets the FcstID to the name of the data driven event.

• If the Type is 9 (Target Impact), the system sets the FcstID to the target name.

LewMeanQty For Lewandowski models, this column stores the mean value for all time periods. Croston uses this column to store the mean demand rate. Valid values are 0 or greater.

Loc The location associated with the DFU whose forecast is defined in this row.

MarketMgrVersionID This column is populated by JDA Market Manager and maps to Market Manager’s planning items forecast identifier. This column should not be updated through Flexible Editor.

Model The model used by a Calculate Model process to identify the history stream and algorithm that is associated with the selected DFU. In the Fcst table, this column is for informational purposes only (note, however, that Model is not part of the primary key). Must be a valid model name in the Model table.

Qty The forecast demand quantity. This quantity is assumed to be spread evenly over the defined time interval. If Dur is 0, the entire demand quantity applies to the point in time specified by StartDate.

StartDate The beginning date for the time interval to which the demand quantity applies.

Type The forecast record type which indicates the source of the Quantity value in each row. Valid values are 1 - 9 and 99:

1 = Base:

The quantity in this row is part of the statistical forecast calculated by the system.

2 = Aggregate Market Activity:

This forecast type is used only for summary DFUs. If you have Type 7 forecasts defined for lower-level DFUs, the sum of those forecast records is stored as Type 2 forecast records when you aggregate data.

3 = Static Forecast Lock Adjustment:

The quantity in this row can be set in the following ways:

• The quantity is set by the Calculate Model process when you use the DFU:LockDur and DFU:StatFcstLocks columns to specify a range of forecast periods to lock (starting at the demand post date).

• The quantity is set by locking a forecast period using the Lock Forecast feature in Demand Workbench.

• The quantity is set by specifying to save locks entered via the Flexible Allocation page.


Fcst

If you lock the total forecast for a particular time period, the system still calculates a new base forecast quantity for that period. Then it creates Total Forecast Lock Adjustments so that the total of the new base forecast, any existing events, and the total forecast lock adjustment equals the original value of the locked total forecast.

4 = Reconcile

The quantity in this row is set by the system when you use the Reconcile Forecast process. Reconciliation ensures that the forecast at each level in a DFU mapping equals the sum of the forecasts mapped to that DFU from the previous level.

For example, one level of a mapping might consist of marketing DFUs with a forecast that includes a number of events. The next level might be made up of logistical DFUs with a statistical forecast that includes no events. If there are differences between the two levels, Forecast Reconciliation adds records (forecast quantities whose Type is 4 - Reconcile) to make them equal.

5 = Promotion:

This forecast is created by the Import Forecast process.

6 = Override:

The quantity in this row is a forecast override that you enter using the Override Manager page.

7 = Market Activity:

The quantity in this row is created by JDA Market Manager. Type 7 forecasts are similar to events in that they add a positive or negative quantity to the net forecast.

8 = Data Driven Event:

The quantity in this row was created by the system when you ran Calculate Model with a data driven event assigned to the DFU. This value represents the event impact. Type 8 forecasts only apply to Lewandowski models.

9 = Target Impacts:

The quantity in this row was created by the system when you ran Calculate Model with a target assigned to the DFU. This value represents the target impact.

99 = Migrated Events:

The quantity in this row is created as part of the migration from previous versions of Demand. When you migrate, all existing Type 2 and Type 5 records are changed to Type 99 records. If you integrate with Market Manager these records are then transferred to the Market Manager database and deleted from the Fcst table. If you do not integrate with Market Manager, you must delete these records manually.


FcstDraft

FcstDraft Table included with: Demand, Markdown Optimization, Promotions Management, Flowcasting


DmdGroup 2 Dmd, MDO, Flowcasting

TEXT

DmdUnit 1 Dmd, MDO, Flowcasting

TEXT

Dur Dmd, MDO, Flowcasting

DURATION 1440

FcstID 7 Dmd, MDO, Flowcasting

TEXT

LewMeanQty Dmd, MDO, Flowcasting

DECIMAL 0

Loc 3 Dmd, MDO, Flowcasting

TEXT

MarketMgrVersionID

Dmd, MDO, Flowcasting

INTEGER -1

Model 4 Dmd, MDO, Flowcasting

TEXT

Qty Dmd, MDO, Flowcasting

DECIMAL 0

StartDate 5 Dmd, MDO, Flowcasting

DATE

Type 6 Dmd, MDO, Flowcasting

OPTION_NUMBER

1,2,3,4,5,6,7,8,9,99

Table description Each row in this table identifies a quantity of forecast demand associated with a particular DFUModel for a given period of time.

Caution: The data in this table should not be edited using the Flexible Editor.

Many JDA Demand functions let you specify what forecast version you want to work with: published or draft. Published forecast data is stored in the Fcst table and is considered to be final, ready to be released to supply planners. Draft forecast data is considered to be in progress and is stored in the FcstDraft table. You can make changes to the draft forecast using Demand Workbench, and when you are satisfied with your changes, publish it using Publish Forecast. When you run a Publish Forecast process, the system copies forecast records from the FcstDraft table to the Fcst table for the periods you specify.

Note: Although you may have multiple models per DFU in the FcstDraft table, you may publish only one model per time period for a DFU.

Caution: If you have any user-defined columns in the Fcst table, you should also include them in the FcstDraft table. This ensures that your draft and published forecasts reflect the same information.

Column descriptions DmdGroup The demand group associated with the DFU whose forecast is defined in this row.


FcstDraft

DmdUnit The demand unit associated with the DFU whose forecast is defined in this row.

Dur The length of the time interval that starts at StartDate.


• If the Type is 1 (Base), the system leaves this column blank, regardless of whether you adjusted the forecast.

• If the Type is 2 (Aggregate Market Activity), the system set the FcstID to AGG_MKTACTIVITY if you are using DFU mapping and Type 7 forecast records exist for a lower-level DFU, those records are aggregated to create a Type 2 record for the higher-level DFU.

• If the Type is 3 (Total Forecast Lock Adjustment), the system assigns the name TotLock, if the lock was set using DFU:TotFcstLock. If the lock was set using the Lock Forecast feature, the system assigns the name FcstLock. If the lock is added through Flexible Allocation, system assigns the name specified in Flexible Allocation.

• If the Type is 4 (Reconcile), the system sets FcstID to the name of the map used for forecast reconciliation. If the reconciliation was added through Flexible Allocation, the system assigns the name specified in Flexible Allocation.

• If the Type is 5 (Promotion), the Import Forecast process sets the FcstID to the corresponding value specified in the ForecastRecordImport (on page 171) table.

• If the Type is 6 (Override), the system assigns the name Override.

• If the Type is 7 (Market Activity), the system assigns the first 50 characters of the name of the market activity (defined in JDA Market Manager) that created the forecast. (The maximum name length in Market Manager is 256.)

• If the Type is 8 (Data Driven Event), the system sets the FcstID to the name of the data driven event.

• If the Type is 9 (Target Impact), the system sets the FcstID to the target name.

LewMeanQty For Lewandowski models, the Lewandowski Mean Quantity column stores the mean value for all time periods. Croston uses this column to store the mean demand rate.

Loc The location associated with the DFU whose forecast is defined in this row.

MarketMgrVersionID This column is populated by JDA Market Manager and maps to Market Manager’s planning items forecast identifier. This column should not be updated through Flexible Editor.

Model The identifier of the model used by a Calculate Model process to identify the history stream and algorithm that is associated with the selected DFU. In the Fcst table, this column is for informational purposes only (note, however, that Model is not part of the primary key).

Qty The forecast demand quantity. This quantity is assumed to be spread evenly over the defined time interval. If Dur is 0, the entire demand quantity applies to the point in time specified by StartDate.

StartDate The beginning date and time for the time interval to which the demand quantity applies.

Type


FcstDraft

Forecast types (1-9 and 99, a value that indicates the source of the Quantity value in each row) are as follows:

• 1: Base: The quantity in this row is part of the statistical forecast calculated by the system.

• 2: Aggregate Market Activity: This forecast type is only used for summary DFUs. If you have Type 7 forecasts defined for lower-level DFUs, the sum of those forecast records is stored as Type 2 forecast records when you aggregate data.

• 3: Static Forecast Lock Adjustment: The quantity in this row can be set in three ways:

• The quantity is set by the Calculate Model process when you use the DFU:LockDur and DFU:StatFcstLocks columns to specify a range of forecast periods to lock (starting at the demand post date).

• The quantity is set by locking a forecast period using the Lock Forecast feature in Demand Workbench.

• The quantity is set by specifying to save locks entered via the Flexible Allocation page.

If you lock the total forecast for a particular time period, the system still calculates a new base forecast quantity for that period. Then it creates Total Forecast Lock Adjustments so that the total of the new base forecast, any existing events, and the total forecast lock adjustment equals the original value of the locked total forecast.

• 4: Reconcile

The quantity in this row is set by the system when you use the Forecast Reconciliation function. Forecast Reconciliation ensures that the forecast at each level in a DFU mapping equals the sum of the forecasts mapped to that DFU from the previous level.

For example, one level of a mapping might consist of marketing DFUs with a forecast that includes a number of events. The next level might be made up of logistical DFUs with a statistical forecast that includes no events. If there are differences between the two levels, Forecast Reconciliation adds records (forecast quantities whose Type is 4 —Reconcile) to make them equal.

• 5: Promotion: This forecast is created by the Import Forecast process.

• 6: Override: The quantity in this row is a forecast override that you enter using the Override Manager page.

• 7: Market Activity: The quantity in this row is created by JDA Market Manager. Type 7 forecasts are similar to events in that they add a positive or negative quantity to the net forecast.

• 8: Data Driven Event: The quantity in this row was created by the system when you ran Calculate Model with a data driven event assigned to the DFU. This value represents the event impact. Type 8 forecasts only apply to Lewandowski models.

• 9: Target Impacts: The quantity in this row was created by the system when you ran Calculate Model with a target assigned to the DFU. This value represents the target impact.

• 99: Migrated Events: The quantity in this row is created as part of the migration from previous versions of JDA Demand. When you migrate, all existing Type 2 and Type 5 records are changed to Type 99 records. If you integrate with JDA Market Manager these records are then transferred to the Market Manager database and deleted from the Fcst table. If you do not integrate with Market Manager, you must delete these records manually.


FcstPerfStatic

FcstPerfStatic Table included with: Demand, Flowcasting



Default value

AbsBaseError Dmd, Flowcasting

DECIMAL 0

AbsNonBaseError Dmd, Flowcasting

DECIMAL 0

AbsPctDFUToSKUFcstError

Dmd, Flowcasting

DECIMAL 0

AbsPctTotError Dmd, Flowcasting

DECIMAL 0

AbsTotError Dmd, Flowcasting

DECIMAL 0

BaseError Dmd, Flowcasting

DECIMAL 0


DECIMAL 0

BaseHist Dmd, Flowcasting

DECIMAL 0

DataDrivenEvents Dmd, Flowcasting

DECIMAL 0

DFUToSKUFcst Dmd, Flowcasting

DECIMAL 0.0

DFUToSKUFcstError Dmd, Flowcasting

DECIMAL 0


TEXT


TEXT

Dur 7 Dmd, Flowcasting

DURATION

ExternalEvents Dmd, Flowcasting

DECIMAL 0

FcstDate 5 Dmd, Flowcasting

DATE


DECIMAL 0


DECIMAL 0

JobID Dmd, Flowcasting

INTEGER 0

Lag Dmd, Flowcasting

INTEGER 0


TEXT

MAPE Dmd, Flowcasting

DECIMAL


FcstPerfStatic



Default value


DECIMAL 0

MaxBaseFcstHist Dmd, Flowcasting

DECIMAL 0

MaxNonBaseFcstHist Dmd, Flowcasting

DECIMAL 0

MaxTotFcstHist Dmd, Flowcasting

DECIMAL 0


TEXT

NonBaseError Dmd, Flowcasting

DECIMAL 0

NonBaseFcst Dmd, Flowcasting

DECIMAL 0

NonBaseHist Dmd, Flowcasting

DECIMAL 0

ReconciledFcst Dmd, Flowcasting

DECIMAL 0


DATE

TargetImpact Dmd, Flowcasting

DECIMAL 0.0

TotError Dmd, Flowcasting

DECIMAL 0


DECIMAL 0

TotFcstLockAdj Dmd, Flowcasting

DECIMAL 0

TotHist Dmd, Flowcasting

DECIMAL 0


TEXT ' '

WMAPE Dmd, Flowcasting

DECIMAL

Table description Each row in this table contains data on the accuracy of a previous forecast. When you run the Store Derived Table process in JDA Demand and select FcstPerf data, the system stores the data for the DFUs you select in this table. You cannot edit the columns in this table.

You can view this table in Flexible Editor and export the data to an external system.

Column descriptions AbsBaseError The absolute value of the error in the base forecast for the period, calculated as:

| BaseFcst - BaseHist | JDA Demand Management Foundation Reference Guide 163 © 1997 - 2014 JDA Software Group, Inc.- Confidential

FcstPerfStatic

For aggregate mode, the system totals the values in AbsBaseError. The value in this column is used to calculate the AbsPctBaseError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

AbsNonBaseError The absolute value of the error in the non-base forecast for the period, calculated as:

| NonBaseFcst - NonBaseHist |

For aggregate mode, the system totals the values in AbsNonBaseErrors. The value in this column is used to calculate the AbsPctNonBaseError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

AbsPctDFUToSKUFcstError The absolute percent of the error in the DFUToSKU forecast for the period, calculated as:

(| DFUToSKUFcst - TotHist |/TotHist)*100

AbsPctTotError The absolute percent of the error in the total forecast for the period, calculated as:

(| TotFcst - TotHist |/TotalHist)*100

For aggregate mode, the system totals the values in AbsPctTotErrors. The initial value is 0.

AbsTotError The absolute value of the error in the total forecast for the period, calculated as:

| TotFcst - TotHist |

For aggregate mode, the system totals the values in AbsTotErrors. The value in this column is used to calculate the AbsPctTotError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

BaseError The error in the base forecast for the period, calculated as:

BaseFcst - BaseHist

For aggregate mode, the system totals the values in BaseError. The value in this column is used to calculate the PctBaseError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

BaseFcst The quantity of the base (or statistical) forecast for the demand period defined in this row. This quantity is taken from Fcst:Qty where Fcst:Type = 1. For aggregate mode, the system totals the values in BaseFcst. The initial value is 0.

BaseHist The actual demand from the History table whose Hist:Type = Type 1 (Total History) - Type 2 (History overrides) - (if this is a Lewandowski DFU) Type 3 (Data Driven Events) for the period specified. For aggregate mode, the system totals the values in BaseHist. The initial value is 0.

DataDrivenEvents The quantity of the data driven events forecast (where Fcst:Type = 8) for the demand period defined in this row. The initial value is 0.

DFUToSKUFcst The quantity of the forecasted demand that has been mapped to a SKU from a DFU.

DFUToSKUFcstError The error in the DFUToSKU forecast for the period, calculated as: JDA Demand Management Foundation Reference Guide 164 © 1997 - 2014 JDA Software Group, Inc.- Confidential

FcstPerfStatic

DFUToSKUFcst - TotHist

DmdGroup The demand group associated with the DFU whose forecast performance data is defined in this row.

DmdUnit The demand unit associated with the DFU whose forecast performance data is defined in this row.

Dur The length of time covered by the forecast defined in this row. The value for Dur is dependent on the demand calendar used by the DFU.

ExternalEvents The quantity of the external event forecast (Fcst:Type = 5) for the demand period defined in this row. Initial value is 0.

FcstDate Date of the current forecast period when the Store Forecast function created this row. This value is taken directly from the HistFcst table.

FcstOverride The quantity of the forecast override (where Fcst:Type = 6) for the demand period defined in this row. Initial value is 0.

InternalEvents The quantity of the internal event forecast (where Fcst:Type = 2) for the demand period defined in this row. The initial value is 0.

JobID The identifier of the job that created the data stored in this table. When a user runs a Store Derived Table process, the system automatically assigns a job identifier, which is stored in this column. The initial value is 0.

Lag The number of forecast periods between FcstDate and StartDate. For example, if the beginning date of each forecast period is the first of the month, the forecast for April that was calculated February 1 would have a lag value of 2. Note that the forecast for February that was calculated February 1 would have a lag number “0.”

Loc The location associated with the DFU whose forecast performance data is defined in this row.

MAPE The mean absolute percent of the error in the total forecast for the period, calculated as:

MAPE=∑|Absolute Percent Total Error|/n

where, n is the number of items in the calculation.

MarketActivity The quantity of the market activity (where Fcst:Type=7) for the demand period defined in this row. This value is entered via JDA Market Manager application. The initial value is 0.

MaxBaseFcstHist The maximum of either the base forecast or the base history quantities. If you are viewing aggregate values, the system totals the values in MaxBaseFcstHist. The value in this column is used to calculate the SclPctBaseError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

MaxNonBaseFcstHist


FcstPerfStatic

The maximum of either the non-base forecast or the non-base history quantities. If you are viewing aggregate values, the system totals the values in MaxNonBaseFcstHist. The value in this column is used to calculate the SclPctNonBaseError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

MaxTotFcstHist The maximum of either TotFcst or TotHist quantities. If you are viewing aggregate values, the system totals the values in MaxNonBaseFcstHist. The value in this column is used to calculate the SclPctTotError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

Model The model used by Calculate Model to identify the history stream and algorithm that is associated with the selected DFU. Valid values are the identifier of a model.

NonBaseError The error in the non-base forecast for the period, calculated as:

NonBaseFcst - NonBaseHist

If you are viewing aggregate values, the system totals the values in NonBaseError. The value in this column is used to calculate the PctNonBaseError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

NonBaseFcst The quantity of all non-base forecasts for the demand period defined in this row. This column is calculated by adding all Fcst:Qty values over the demand period whose Fcst:Type is not equal to 1. If you are viewing aggregate values, the system totals the values in NonBaseFcst. The initial value is 0.

NonBaseHist The quantity of all non-base history for the demand period defined in this row. This column is calculated by adding all Type 2 (History overrides) and Type 3 (DDEs) history over the demand period.

ReconciledFcst The quantity of the reconciled forecast (where Fcst:Type = 4) for the demand period defined in this row. The initial value is 0.

StartDate The beginning date of the lag period covered by the forecast defined in this row. This date is dependent on the demand calendar used by the DFU.

TargetImpact The quantity of the target impact (where Fcst:Type = 9) for the demand period defined in this row. The initial value is 0.0.

TotError The error in the total forecast for the period, calculated as:

TotFcst - TotHist

For aggregate mode, the system totals the values in TotError. The value in this column is used to calculate the PctTotError column, a converted column that is included in the FcstPerfStatic Flexible Editor page. The initial value is 0.

TotFcst The quantity of all base and non-base forecasts for the demand period defined in this row. It is calculated by adding all Fcst:Qty values over the demand period. For aggregate mode, the system totals the values in TotFcst. The initial value is 0.

TotFcstLockAdj


FcstPerfStatic

The quantity of the total forecast lock adjustment (where Fcst:Type = 3) for the demand period defined in this row. The initial value is 0.

TotHist The total actual demand from the History table (Hist:Type = 1 or 2) for the period specified. For aggregate mode, the system totals the values in TotHist. The initial value is 0.

UserID The identifier of the user that ran the Store Derived Table process that created the data stored in this table. When a user runs Store Derived Table, the system automatically detects the user identifier and stores it in this column.

WMAPE The weighted mean absolute percent of the error in the total forecast for the period, calculated as:

WMAPE=[∑|(TotHist-TotFcst/TotHist)|*W]/∑W

where, W is the weight.


FittedHist

FittedHist Table included with: Demand, Flowcasting




TEXT


TEXT


DURATION 1440

LewMeanQty Dmd, Flowcasting

DECIMAL 0


TEXT

MeanAbsDeviation Dmd, Flowcasting

DECIMAL 0


TEXT

NormalizedFcstErr Dmd, Flowcasting

DECIMAL 0

OutlierSw Dmd, Flowcasting

BOOLEAN 0


DECIMAL 0.0


DATE

SysAdjOutlierSw Dmd, Flowcasting

BOOLEAN 0

TrackingSignal Dmd, Flowcasting

DECIMAL 0.0

Trend Dmd, Flowcasting

DECIMAL 0

TrendBrkSw Dmd, Flowcasting

BOOLEAN 0

Table description This table is used by JDA Demand to calculate DFU forecasts. Each row in this table contains a quantity of fitted history associated with a particular DFU for a given period of time. When you run Calculate Model, the system calculates the forecast in the historical timeframe using the actual values of the DFU’s demand history, then stores this information in the FittedHist table. The DFU:StoreFittedHistOpt value indicates the storage behavior of the fitted history for a DFU. The default value for DFU:StoreFittedHistOpt is 2, which indicates that the storage of fitted history is dependent on DBParam:CalcStoreFittedHistSw (on page 52). If the CalcStoreFittedHistSw switch is turned on, then fitted history is stored, and if not, the history is not stored. Calculate Model projects fitted history values forward into future periods to calculate the DFU’s forecast.

Though you cannot edit the columns in this table, you have the option to view additional information such as Total Error or Total Percent Error using expressions. The following steps briefly outline the procedure for viewing Total Error/Total Percent Error on this Flexible Editor page: JDA Demand Management Foundation Reference Guide 168 © 1997 - 2014 JDA Software Group, Inc.- Confidential

FittedHist

1. On the Tables and Column tab on the Grid Properties page, add the following columns to the Selected Columns list (if not already added):

• Qty

• Qty (Hist)

• {expression}

Note: You can add multiple expression columns to a Flexible Editor page.

2. Select {expression} in the Selected Columns list and click Properties.

Note: You can apply Column Filters or use dynamic filtering to view only Total History. The expression may not display correct values for other types of History.

3. In the General tab, type in Total Error or Total Percent Error as the Display name. In the Expression tab build the expression "FittedHist.Qty" - "Hist.Qty" or (("FittedHist.Qty"-"Hist.Qty")/"Hist.Qty")*100 using the Available Columns and Operators lists.

Note: If you type the expression directly in the edit box, be sure to spell the column names exactly as they are listed in the Available Columns list and enclose them in quotes. For more information, see Creating expressions in columns in the Flexible Editor on-line help.

4. Select pre-Aggregation.

5. Click Verify to validate the logic of the expression.

6. Click Done.

Note: The Total Error / Total Percent Error values are calculated using Fitted History. Hence these values may not always match with those displayed in the Demand Workbench, which considers overrides.

Column description DmdGroup The demand group associated with the DFU whose fitted history is defined in this row.

DmdUnit The demand unit associated with the DFU whose fitted history is defined in this row.

Dur The length of time covered by the fitted history defined in this row. Valid values are 0 or greater. Default value is 1440M.

LewMeanQty The column applies to Lewandowski and Croston models. Lewandowski uses this column to store the dynamic mean value. Croston uses this column to store the mean demand rate. Valid values are 0 or greater.

Loc The location associated with the DFU whose fitted history is defined in this row.

MeanAbsDeviation Stores the time series values for mean absolute deviation for Lewandowski models. Initial value is 0.

Model The model associated with the DFU whose fitted history is defined in this row. Valid values are the identifier of a model.

NormalizedFcstErr


FittedHist

Stores the time series normalized forecast values for Lewandowski models. A high NF represents high model error at a particular time period (an outlier). Fourier and MLR models use the LinRegParam:OutlierFactor column to determine which data points are outliers.

OutlierSw If set to 1, indicates this value is outside the normal range. Valid values are 0 and 1. Initial value is 0.

Qty The quantity of the fitted history for the DFU during this period. Initial value is 0.

StartDate The beginning of the period covered by the fitted history defined in this row.

SysAdjOutlierSw If set to 1 indicates that any outliers in the period were adjusted in the initial regression. Applies only to Fourier and MLR models. Valid values are 0 and 1. Initial value is 0.

TrackingSignal Specifies the value of the AWS tracking signal. The tracking signal is an indication of a DFU's trend. Generally, the farther the tracking signal is from 0, the more unstable the DFU.

Note: This column applies only to the Lewandowski model.

Trend The trend for each time period. For Fourier and MLR the trend value will be constant for all the time periods for a DFU. Lewandowski has a dynamic trend so the values will vary by time.

TrendBrkSw If set to 1, indicates the value in this row represents a break in the historical trend. Valid values are 0 and 1. Initial value is 0.

Note: This column applies only to the Lewandowski model.


ForecastRecordImport

ForecastRecordImport Table included with: Demand, Markdown Optimization, Promotions Management, Collaborative Shelf Planning and AnalyticsFlowcasting


DmdGroup 2 Dmd, MDO, PM, Flowcasting

TEXT

DmdUnit 1 Dmd, MDO, PM, Flowcasting

TEXT

Duration Dmd, MDO, PM, Flowcasting

UPPER_TEXT

FcstID 7 Dmd, MDO, PM, Flowcasting

TEXT ' '

Loc 3 Dmd, MDO, PM, Flowcasting

TEXT

Model 4 Dmd, MDO, PM, Flowcasting

TEXT

Qty Dmd, MDO, PM, Flowcasting

DECIMAL 0.000000

StartDate 5 Dmd, MDO, PM, Flowcasting

DATE

Type 6 Dmd, MDO, PM, Flowcasting

INTEGER

Table description The FcstRecordImport process uses this table to put the records into the Fcst or FcstDraft tables, respecting locks and targets.



Duration The length of the time interval that starts at StartDate. For example, 31D, 1440M.




Qty


ForecastRecordImport

The quantity being imported.

StartDate The beginning of the period for which this amount should be imported.

Type The type of forecast defined in this row. The options are:

• 3: Static Forecast Lock Adjustment

• 5: Promotion

• 6: Override


Hist

Hist Table included with: Fulfillment, Demand, Demand Decomposition, Dynamic Demand Response, Markdown Optimization, Promotions Management, Strategic Pricing, Travel Price Optimization, Flowcasting

Column name


Default value

DmdGroup 2 Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

TEXT

DmdUnit 1 Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

TEXT

Dur Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

DURATION 1D

Event 7 Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

TEXT

HistStream 4 Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

TEXT

Loc 3 Dmd, Dmd Decomp, MDO, DDR, PM, SP, TPO, Flowcasting

TEXT

Qty Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

DECIMAL 0

StartDate 5 Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

DATE

Type 6 Dmd, Dmd Decomp, DDR, MDO, PM, SP, TPO, Flowcasting

OPTION_NUMBER

1,2,3

Table description The History table stores the historical values for all history streams. Each row in this table represents an actual demand quantity. When you post current demand, enter it into the History table; then set DFU:DmdPostDate to the current date.

Column descriptions DmdGroup The demand group associated with the DFU whose history is defined in this row.

DmdUnit The demand unit associated with the DFU whose history is defined in this row.

Dur The length of time in minutes covered by the history defined in this row.

Event JDA Demand Management Foundation Reference Guide 173 © 1997 - 2014 JDA Software Group, Inc.- Confidential

Hist

The name of the event if History Type is 2 (History Override)—that is, if you want to associate this quantity with an event. If this value is added via the Demand Workbench, then no event ID is generated.

HistStream The history stream identifier associated with this row of history.

Loc The location associated with the DFU whose history is defined in this row.

Qty The quantity of the history for the DFU during this period.

StartDate The beginning of the period covered by the history defined in this row.

Type The type of history defined in this row. Initial value is 1. The options are:

• 1=Total History

Total demand for a DFU.

• 2=History Overrides

Non-base demand for a DFU (a promoted product, for example). Type 2 records may be created by the Adjust History for Pricing and Promotions process in Demand Decomposition.

• 3=Data Driven Events

Demand attributed to data driven events for Lewandowski models. Calculate Model uses this quantity when fitting a model or updating a forecast.

Calculate Model may use Type 1 or Type 1 + Type 2 history when fitting a model or updating a forecast.


HistFcst

HistFcst Table included with: Demand, Flowcasting, Promotions Management




DECIMAL 0

DataDrivenEvents Dmd, Flowcasting

DECIMAL 0

DFUToSKUFcst Dmd, Flowcasting

DECIMAL 0.0

DmdGroup 2 Dmd, Flowcasting, PM

TEXT

DmdUnit 1 Dmd, Flowcasting, PM

TEXT

Dur Dmd, Flowcasting, PM

DURATION 1440

ExternalEvents Dmd, Flowcasting

DECIMAL 0.0

FcstDate 5 Dmd, Flowcasting, PM

DATE


DECIMAL 0.0


DECIMAL 0.0

Lag Dmd, Flowcasting

INTEGER 0


TEXT


DECIMAL 0

Model 4 Dmd, Flowcasting, PM

TEXT

NonBaseFcst Dmd, Flowcasting

DECIMAL 0

PickBestSw Dmd, Flowcasting

BOOLEAN 0

Published Dmd, Flowcasting

BOOLEAN 0

ReconciledFcst Dmd, Flowcasting

DECIMAL 0.0

StartDate 6 Dmd, Flowcasting, PM

DATE


HistFcst



TargetImpact Dmd, Flowcasting

DECIMAL 0.0

TotFcstLockAdj Dmd, Flowcasting

DECIMAL 0.0

Table description Each row in this table represents the forecast demand quantities from previous forecasts. Since each forecast type is stored in its own column, you can create converted columns to represent the combinations that best fit your business needs. For example, for DFUs at the lowest level, you may want to compare your reconciled forecast (Type 1 + Type 4) to your total forecast (Types 1-8).

The Store Forecast function captures forecast data from the Fcst table on a particular forecast date and stores it in this table. Each time you close a demand period and then run Store Forecast, the system adds additional rows to the HistFcst table for that period's forecast date, allowing you to build a history of your forecasts over time. The Store Forecast process can copy data from either the Fcst or the FcstDraft table, so you can track forecast performance for some or all of the models you create. In the OnLine Expert, see “Storing historical forecast data” for more information on how the system moves forecast data from the Fcst table to the HistFcst table.

The FcstPerfStatic table generates a row for each row in the HistFcst table.

Column descriptions BaseFcst The quantity of the base (or statistical) forecast for the demand period defined in this row. This quantity is taken from Fcst:Qty where Fcst:Type is equal to 1.

DataDrivenEvents The quantity of the data driven event’s forecast (where Fcst:Type = 8) for the demand period defined in this row. This column is only used for Lewandowski models.

DFUToSKUFcst The quantity of the forecasted demand that has been mapped to a SKU from a DFU.

DmdGroup The demand group associated with the DFU whose historical forecast is defined in this row.

DmdUnit The demand unit associated with the DFU whose historical forecast is defined in this row.

Dur The length of time covered by the historical forecast defined in this row. Dur is dependent on the demand calendar used by the DFU.

ExternalEvents The quantity of the external event forecast (where Fcst:Type = 5) for the demand period defined in this row.

FcstDate Date of the current forecast period when the Store Forecast function was run.



HistFcst

InternalEvents The quantity of the internal event forecast (where Fcst:Type = 2) for the demand period defined in this row.

Lag The number of forecast periods between FcstDate and StartDate.

Loc The location associated with the DFU whose historical forecast is defined in this row.



NonBaseFcst The quantity of all non-base forecasts for the demand period defined in this row. It is calculated by adding all Fcst:Qty values over the demand period whose Fcst:Type is not equal to 1.

PickBestSw If set to 1, indicates this DFU Model was selected as the best fit when running the Calculate Model process with the Pick Best option selected. The best fit is determined by comparing the Symmetric MAPE for each model. The model with the lowest value is considered the best fit.

Published When multiple models exist in the database, this column provides users with a way to review which forecast was used historically when reviewing the forecast performance. This column is updated by the Store Forecast process when the “published” version is selected. The published version will be all forecast rows in the Fcst table. Valid values for this column are 0 - Stored from FcstDraft table and 1 - Stored from Fcst table.

ReconciledFcst The quantity of the reconciled forecast (where Fcst:Type = 4) for the demand period defined for this row.

StartDate The beginning date of the lag period covered by the historical forecast defined in this row. This date is dependent on the demand calendar used by the DFU. The lag numbers specified when the Store Forecast process was run determine which forecast lag periods the system saves to the HistFcst table.

For example, suppose the Demand Post Date (DFU:DmdPostDate) is August and you are storing lags 0, 1 and 2 (months of August, September, and October, respectively). The starting date of the lag periods would be:

• StartDate for lag 0 = August

• StartDate for lag 1 = September

• StartDate for lag 2 = October

TargetImpact The quantity of the target impact (where Fcst:Type = 9) for the demand period defined in this row.

TotFcstLockAdj The quantity of the total forecast lock adjustment (where Fcst:Type = 3) for the demand period defined in this row.


HistFcstEvents

HistFcstEvents Table included with: Demand, Flowcasting




TEXT


TEXT


INTEGER 1440

FcstDate 8 Dmd DATE FcstID 7 Dmd,

Flowcasting TEXT

Lag Dmd INTEGER 0 Loc 3 Dmd,

Flowcasting TEXT


TEXT


FLOAT(126) 0


DATE


FLOAT(126) 0

Type 6 Dmd, Flowcasting

INTEGER

Table description Each row in this table represents the historical forecast quantities for events with specific forecast types. When you run the Store Forecast process with the Publish Detailed Events Data switch ON, the system stores the total forecast quantity in the HistFcst table and detailed forecast quantities for specific events in the HistFcstEvents table.

Column description DmdGroup The demand group associated with the DFU whose historical forecast is defined in this row.

DmdUnit The demand unit associated with the DFU whose historical forecast is defined in this row.

Dur The length of time covered by the historical forecast defined in this row. Dur is dependent on the demand calendar used by the DFU.

FcstDate Date of the current forecast period when the Store Forecast function was run.

FcstID


HistFcstEvents

The name of the forecast whose quantity is displayed in this row. FcstID can be the name of a promotion, event or market activity.

Lag The number of forecast periods between FcstDate and StartDate.

Loc The location associated with the DFU whose historical forecast is defined in this row.

Model The model used by a Calculate Model process to identify the history stream and algorithm that are associated with the selected DFU.

Qty The forecast quantity for the forecast type defined in this row. Only quantities for Type 1, 2, 5, 6, and 7 are published.

StartDate The beginning date of the period covered by the historical forecast defined in this row.

TotFcst The total quantity of all base and non-base forecasts for the demand period defined in this row.

Type The forecast type that indicates the source of the quantity value in this row. Only quantities for Type 1, 2, 5, 6, and 7 are published.


HistStream

HistStream Table included with: Fulfillment, Demand, Demand Decomposition, Dynamic Demand Response, Markdown Optimization, Promotions Management, Strategic Pricing, Flowcasting


Descr Dmd, DDR, Dmd Decomp, MDO, PM, SP, Flowcasting

TEXT ' '

HistStream 1 Dmd, DDR, Dmd Decomp, MDO, PM, SP, Flowcasting

TEXT

Table description If you have more than one source for history, you can import all history types into JDA Demand and generate forecasts from each history type. To create a history stream in Demand, first set up the name and description of the history stream in the HistStream table, then import history (including the history stream name) into the Hist table.

Each row in this table represents a history stream such as point-of-sale (POS) or shipment (Ship).

Column descriptions Descr Description of this history stream.

HistStream The history stream described in this row.


HoltWintersParam

HoltWintersParam Table included with: Demand, Flowcasting



TEXT


TEXT

HoldOutPeriod Dmd, Flowcasting

INTEGER 0

InitialLevel Dmd, Flowcasting

DECIMAL 0

InitialTrend Dmd, Flowcasting

DECIMAL 0

InitMeanOverrideSw

Dmd, Flowcasting

BOOLEAN 0

LevelSmooth Dmd, Flowcasting

DECIMAL 0.19


TEXT


TEXT

MSESmooth Dmd, Flowcasting

DECIMAL 0.10


DECIMAL 2

ParamOptimizSw Dmd, Flowcasting

BOOLEAN 0

SeasonalityOpt Dmd, Flowcasting

INTEGER 1

SeasonalityProfileSw

Dmd, Flowcasting

BOOLEAN 0

SeasonalSmooth Dmd, Flowcasting

DECIMAL 0.30

SmoothProfileSw Dmd, Flowcasting

BOOLEAN 1

TrendDamp Dmd, Flowcasting

DECIMAL 1.00

TrendMethod Dmd, Flowcasting

INTEGER 1

TrendSmooth Dmd, Flowcasting

DECIMAL 0.05

Table description Contains the parameters for setting the Holt-Winters method.

Column descriptions JDA Demand Management Foundation Reference Guide 181 © 1997 - 2014 JDA Software Group, Inc.- Confidential

HoltWintersParam



HoldOutPeriod The number of periods to use to optimize the smoothing parameters (levelsmooth, trendsmooth, seasonal smooth). The maximum number you can specify is half the available historical periods. However, if you set this parameter to 0 and the ParamOptimizSw to 1 (Do optimization), then all historical periods are used to minimize the MSE.

Valid values for Holdout period are greater than or equal to zero.

InitialLevel Initial level value. Used to manually set the initial level value the algorithm uses when it begins its calculations, if InitMeanOverrideSw is set to Yes.

InitialTrend Used to manually set the initial trend value in the algorithm when it begins its calculations, if InitMeanOverrideSw is set to Yes.

InitMeanOverrideSw Uses system-supplied initial values when set to 0. Otherwise, lets you specify the initial estimates for the level and trend, which are set in InitialLevel and InitialTrend.

Valid values for Initial mean override switch are 0=No override and 1=Override.

LevelSmooth Weighting factor used for level smoothing.

Valid values for Level smoothing factor are in the range of 0.00 to 1.00.



MSESmooth Weighting factor used to smooth the mean squared error.

Valid values for MSE smoothing factor are in the range of 0.00 to 1.00.


The system multiplies OutlierFactor by the standard error of the model, then adds the result to and subtracts the result from the model demand value. Outliers are history period values that fall outside the resulting range of reasonable values. DFU:OutlierOpt and DBParam:OutlierOpt determine how Model and Update Model handle outliers.


Valid values for OutlierFactor are greater than or equal to 2.

ParamOptimizSW


HoltWintersParam

Indicates whether or not to optimize the forecast. If set to 1, then the number of periods specified in the HoltWintersParam:HoldOutPeriod (on page 182) is used to optimize the forecast. If this switch is set to 0, then HoldOutPeriod=0 (disabled).

Valid values for Parameter optimization switch are 0=No optimization and 1=Do optimization.

SeasonalityOpt Indicates whether to use seasonality, and if so, whether it should be calculated using the multiplicative or additive method.

Valid values for Seasonality option are 0=No seasonality, 1=Multiplicative seasonality, and 2=Additive seasonality.

SeasonalityProfileSw Indicates whether to use the seasonality profile created by Calculate Model or to use user-supplied values.

Valid values for Seasonality profile switch are 0=Create profile by CalcModel, 1=Do not create profile and use user input.

SeasonalSmooth Weighting factor used for seasonal smoothing.

Valid values for Seasonality smoothing factor are in the range of 0.00 to 1.00.

SmoothProfileSw Indicates whether or not to smooth the user-supplied seasonal adjusters.

Valid values for Smooth profile switch are 0=Maintain profile, do not smooth, 1=Smooth profile.

TrendDamp The degree to which you want to extend the long-term trend. The default of 1.0 corresponds to a pure linear trend.

Valid values for Trend damping factor are in the range of 0.00 to 1.00.

TrendMethod Whether or not to include a trend component in the forecast.

Valid values for Trend method factor are 0=No trend and 1=With trend.

TrendSmooth Weighting factor to use for trend smoothing.

Valid values for Trend smoothing factor are in the range of 0.00 to 1.00.


HoltWintersStats

HoltWintersStats Table included with: Demand, Flowcasting




TEXT


TEXT

LastLevel Dmd, Flowcasting

DECIMAL 0

LastTrend Dmd, Flowcasting

DECIMAL 0


TEXT


DECIMAL 0.0


TEXT


DECIMAL 0

SmoothErrorTracking

Dmd, Flowcasting

DECIMAL 0

SmoothMSE Dmd, Flowcasting

DECIMAL 0


DECIMAL 0

Table description An output table that stores values generated during a Holt-Winters forecast.

Notes:

• If period weighting is applied, all statistics are calculated based on weighted history. If a DFU has an attached moving event, only Mean, MSE, and SymmetricMAPE will be published.

• System will be able to use a multiplicative model if the number of consecutive negative or zero history is less than or equal to half of the periodicity. For this case, the Multiplicative model considers negative history as zero and all the stats will be calculated based on the modified history (negative history replaced with zero history).



LastLevel


HoltWintersStats

LastLevel is the last smoothed level value found by the Calculate Model process. During the process of introducing New DFUs through the New DFU Introduction functionality, the old DFU’s HoltWintersStats:LastLevel is copied to the HoltWintersParam:InitialLevel of the new DFU.

LastTrend LastTrend is the last smoothed trend value found by the Calculate Model process. During the process of introducing New DFUs through the New DFU Introduction functionality, the old DFU’s HoltWintersStats:LastTrend is copied to the HoltWintersParam:InitialTrend of the new DFU.







where N= number of history points.



SmoothErrorTracking Smoothed error tracking signal, reported at the last period of history. The formula used is as follows:

where:

• Tt = value of the smoothed error tracking signal at the end of period t

• zt= smoothed forecast error at the end of period t which equals:

where ω is a smoothing constant set by HoltWintersParam:MSESmooth.

• MADt = smoothed mean absolute deviation at the end of period t which equals:

where ω is a smoothing constant set by HoltWintersParam:MSESmooth.

SmoothMSE


HoltWintersStats

The smoothed forecast error for this DFU, reported at the last period of history. The formula used is as follows:

where ω is the smoothing constant set by HoltWintersParam:MSESmooth.

Valid values for Smoothed MSE are any real numbers greater than 0.

SymmetricMAPE Symmetric Mean Absolute Percent Error (Symmetric MAPE) compares the fitted history values (statistically generated forecast in the past) with the actual history for the entire duration of history. Only base history (total history minus history overrides) is used if the Calculate Model process is run with Base History. Total history is used if the Calculate Model process is run with Total History. Symmetric MAPE is calculated as the average of the absolute error divided by the average of history and fitted history, expressed as a percentage. It is always calculated when you run the Calculate Model process.

Note: If Symmetric MAPE = zero, and DFU:NPISw (on page 67) is enabled, it can be concluded that the DFU is new and does not yet have enough history for the model fit statistics to be meaningful. The statistical value will not be meaningful until the DFU reaches the Independence Date.


where:




• t = time period

Valid values for Symmetric MAPE are any real numbers greater than 0.


Item

Item Table included with: Fulfillment, Master Planning, Supply, Production and Sourcing Optimization, Demand, Inventory Policy Optimization, Dynamic Demand Response, Flowcasting, Enterprise Supply Planning


AllocPolicy FF, Flowcasting NUMBER 0

CalcCumLeadTimeSw

FF, Flowcasting NUMBER 0

CancelDepthLimit Not used in this release

INTEGER 0

DDSKUSw FF, Flowcasting BOOLEAN 0

DDSrcCostSw FF, Flowcasting BOOLEAN 0 DefaultUOM FF, Flowcasting INTEGER 18

Descr FF, MP, Supp, PSO, IPO, Dmd, Flowcasting, ESP

TEXT ' '

DynDepDecimals FF, Flowcasting INTEGER 0

DynDepOption FF, Flowcasting OPTION_NUMBER

1,2,3 1

DynDepPushOpt FF, Flowcasting OPTION_NUMBER

1,2,3,4,5,6,7,8

1

DynDepQty FF, Flowcasting DECIMAL 1

EnableSw PSO BOOLEAN 1 InvOptimizerType IPO OPTION_N

UMBER 1,2,3 1

Item 1 FF, MP, Supp, PSO, IPO, Dmd, Flowcasting, ESP

TEXT

ItemClass Flowcasting UPPER_TEXT

'DEFAULT'

PerishableSw MP, FF, Flowcasting, ESP

BOOLEAN 0

PlanLevel FF, MP, Flowcasting

INTEGER -1

PriItemPriority Not used in this release

INTEGER 0

Priority MP, ESP INTEGER 1 RestrictPlanMode FF, Flowcasting OPTION_N

UMBER 1,2,3 1


Item


StorageGroup ESP TEXT ' '

SupsnGroupNum FF, Flowcasting, MP

INTEGER

UnitPrice Not used in this release

DECIMAL 0

UnitsPerAltShip Not used in this release

DECIMAL 1

UnitsPerPallet ESP DECIMAL 1 UOM FF, Flowcasting TEXT ' ' Vol ESP DECIMAL 0 Wgt FF DECIMAL 0

Table description Each row in this table defines an individual product—a finished good, purchased finished good, raw material, or work-in-process item.

Column descriptions AllocPolicy Indicates the type of allocation policy to be applied for the item.

• 1 - Threshold

• 2 - Hierarchical: Imported

• 3 - Hierarchical: Computed

CalcCumLeadTimeSw When this column is set to 1, the CumLeadTimeDur column for the item is calculated by Calculate Plan from the original MPS source through each SKU in the item family. This column value is required in order for the TargetNetworkInv column to be stored in the AggSKUProjStatic table or displayed in the aggregate view in Plan Analysis.

DDSKUSw Determines which value Dynamic Deployment uses for the Dynamic Deployment duration.

Valid values for Dynamic Deployment SKU Switch are Yes or No.

• No: Use DynDep duration from process properties

Dynamic Deployment uses the Dynamic Deployment duration you specify on the Calculate Plan process page for all SKUs in all item families. If you do not specify a Dynamic Deployment duration, when you run Dynamic Deployment, it uses SKUDeploymentParam:StockAvailDur. If both durations are zero, Dynamic Deployment generates the following exception:

0049 Neither the DynDepDur nor the SKUDeploymentParam:SAD is valid

• Yes: Use DynDep duration from SKUDeploymentParam table

Dynamic Deployment uses individual durations by SKU as specified in SKUDeploymentParam:DynDeplDur. (Refer to the DynDeplDur column in the SKUDeploymentParam table for more information.)

DDSrcCostSw JDA Demand Management Foundation Reference Guide 188 © 1997 - 2014 JDA Software Group, Inc.- Confidential

Item

Determines whether Dynamic Deployment gets transportation costs from the DynDepSrc table or the Network table.

Valid values for Dynamic Deployment Source Cost Switch are Yes or No.

• No: Use transportation costs from the Network table

Dynamic Deployment takes transportation costs from Network:RatePerCWT. Transportation cost is calculated as:

Transportation cost (per unit) = Network:RatePerCst x (Item:Wgt/100)

• Yes: Use transportation costs from the DynDepSrc table

Dynamic Deployment takes transportation costs from DynDepSrc:DynDepSrcCost. With this option, transportation costs are considered as unit costs and are not calculated per 100 weight. In addition, this option allows you to specify different transportation costs for different items, and vary costs over time (using DynDepSrc:Eff).

DefaultUOM This is the default UOM. The RecShip quantities and the Sourcing:SplitQty expressed in terms of this default UOM. All conversion factors are defined with respect to the DefaultUOM in the Item table.

Descr A description of this item.

DynDepDecimals Defines the number of decimal places that Dynamic Deployment uses when it rounds surplus and shortage quantities. Use this column only if Item:DynDepQty (on page 191) is not an integer; it should be set to the number of significant decimal places in Item:DynDepQty (on page 191).

Valid values for Dynamic Deployment Decimals are 0 or any positive integer.

DynDepOption Determines which item families in the Calculate Plan search should be processed by Dynamic Deployment.

Valid values for Dynamic Deployment Option are 1 to 3.

• 1: Dynamic Deployment does not process this item.

• 2: Dynamic Deployment processes this item family if at least one of the SKUs in the family has Exception 0039 (Limited stock available, allocation strategy used).

• 3: Dynamic Deployment always processes this item, regardless of exceptions.

DynDepPushOpt Lets you implement either Push or Pull behavior in Dynamic Deployment.

Valid values for Dynamic Deployment Push Option are 1 to 8.

Note: Note that if circular sourcing is set up in the DynDepSrc table, and if DynDepPushOpt is set to 1, 2, 7 or 8, then shipping costs must be defined between the locations that have circular sourcing set up. Otherwise many unnecessary RecShips will be created back and forth between the circular sourcing locations.

• 1: Pull

Evokes pull behavior by creating a cost constraint within Dynamic Deployment. Effectively, it costs a small amount for stock to sit at a destination location, but it does not cost anything for stock to sit at a source location. Because of this virtual cost, Dynamic Deployment considers it cheaper to schedule recommended shipments as late as possible as long as they still arrive on time.

• 2: Push


Item

Evokes push behavior by creating a cost constraint within Dynamic Deployment. Effectively, it costs a small amount for stock to sit at a source location, but it does not cost anything for stock to sit at a destination location. Because of this virtual cost, Dynamic Deployment considers it cheaper to schedule recommended shipments as early as is feasible.

• 3: Fairshare Push

No longer available. If option 3 is selected then option 6 is used.

• 4: None

With this option, Dynamic Deployment uses neither Push nor Pull logic; it makes no distinction between a shipment scheduled just-in-time at the destination and one scheduled three weeks early.

• 5: Alternate Pull

Evokes pull behavior by creating a cost constraint within Dynamic Deployment. The effective shipping cost at the beginning of the Dynamic Deployment duration is increased by a certain amount; each day throughout the horizon, the shipping costs become gradually smaller. Because of this virtual cost, Dynamic Deployment considers it cheaper to schedule recommended shipments as late as possible as long as they still arrive on time.

For this rule to produce correct results, the value in SKUDeploymentParam:IncStkoutCost must be greater than zero. If IncStkoutCost = zero at the destination, a single RecShip is generated at the end of the Dynamic Deployment horizon, instead of multiple recommended shipments throughout the horizon.

• 6: Alternate Push

Evokes push behavior by creating a cost constraint within Dynamic Deployment. For each day throughout the Dynamic Deployment horizon, the shipping costs become gradually larger. Because of this virtual cost, Dynamic Deployment considers it cheaper to schedule recommended shipments as early as stock is available to ship.

• 7: Circular Pull Based on Carrying Cost

Evokes pull behavior by creating a cost constraint within Dynamic Deployment. Effectively, it costs a small amount for stock to sit at a destination location, but it does not cost anything for stock to sit at a source location. Because of this virtual cost, Dynamic Deployment considers it cheaper to schedule recommended shipments as late as possible as long as they still arrive on time.

Dynamic Deployment will choose to hold stock at a dynamic deployment source location (DynDepSrc:Source) in preference to holding it at another location. It will choose to hold stock at a location that is not a dynamic deployment destination location rather than at one that is (DynDepSrc:Dest).

This option can be used for circular sourcing situations in which Pull behavior is desired, and in which the net inventory situation at the location at the start of Dynamic Deployment is a likely indicator of whether that location will be sending or receiving shipments. If there are no circular sourcing relationships in the item family, and no more than three levels of sourcing, this rule will always produce the same results as Rule 1.

• 8: Circular Push Based on Carrying Cost

Evokes push behavior by creating a cost constraint within Dynamic Deployment. Effectively, it costs a small amount for stock to sit at a source location, but it does not cost anything for stock to sit at a destination location. Because of this virtual cost, Dynamic Deployment considers it cheaper to schedule recommended shipments as early as is feasible.

Dynamic Deployment will choose to hold stock at location that is not a dynamic deployment source location rather than at one that is (DynDepSrc:Source). It will choose to hold stock at a location that is a dynamic deployment destination location (DynDepSrc:Dest) rather than at one that is not.


Item

However, if a location serves as both a source and a destination, Dynamic Deployment examines the location’s inventory situation to determine whether the location is more likely to be the shipper or the recipient of Dynamic Deployment recommended shipments. If the location has a surplus at OHPost + DynDepDuration, it is treated as a source and not as a destination. If the location has a shortage at OHPost + DynDepDuration, it is treated as a destination and not as a source.

This option can be for circular sourcing situations in which Push behavior is desired, and in which the net inventory situation at the location at the start of Dynamic Deployment is a likely indicator of whether that location will be sending or receiving shipments. If there are no circular sourcing relationships in the item family, and no more than three levels of sourcing, then this rule will always produce the same results as Rule 2.

DynDepQty Value that Dynamic Deployment uses to round shortage and surplus quantities. Dynamic Deployment rounds up for shortages and down for surplus according to this value. For example, if DynDepQty is set to 10, the system rounds a shortage value of 13 up to 20.

Valid values for Dynamic Deployment Quantity are 0 or greater.

If you set DynDepQty to a decimal number, you can use Item:DynDepDecimals (on page 189) to control the number of decimal places that Dynamic Deployment uses when it rounds values. For example, if DynDepQty is set to 1.5, then DynDepDecimals should be set to 1.0. If DynDepQty is set to.65, then DynDepDecimals should be set to 2.0.

EnableSw This switch indicates if the item will be used while running the Production and Sourcing Optimization Optimizer. If set to false, the item will be ignored in building the model, along with all of its SKUs and all processes for which one of its SKUs is an input or output.

InvOptimizerType This column is used by JDA IPO to determine the type of service part. Valid values include:

• 1: Consumable

• 2: Repairable

• 3: Carcass

IPO only calculates stock levels (safety stock, reorder point, maximum stock levels) for SKUs whose item (SKU:Item) is configured to be a repairable or consumable part. Any SKU whose SKU:Item is configured to be a carcass cannot have any replenishment methods. IPO ignores the methods if they are defined for a carcass SKU. IPO only loads carcass SKUs when it is running with the replenishment plan costing model. Carcass items are specified as subordinate SKUs for repairable items in the BOM table. For more information, see the IPO OnLine Expert.

Item The item defined in this row.

ItemClass The item class to which the item defined in this row belongs. The various allocation business rules, defined in ATPInventoryAllocRuleAssoc, are specified for the Item:ItemClass and Cust:CustClass combination. Specifying the ItemClass and CustClass values allows for ease-of-use in setting up the database in situations where customers share the same business rules and groups of items share the same characteristics, or when a new customer is added.

PerishableSw Indicates whether this item family is perishable.

• No/Blank: Not perishable

• Yes: Perishable


Item

PlanLevel Defines the maximum level at which this item relates to other items. The value in this column is calculated by the Level SKU process. The default value of -1 indicates that the Level SKU process has not yet been run or was unable to set the level for this item due to BOM circularity or some other conflict. You cannot edit this column.

PriItemPriority Note: This column is not used in this release.

Priority This value indicates the importance of this item in relation to all other items. The Master Planning process uses this value when using item priority to determine which demand to satisfy next.

Valid values for Priority are 0 to 2,147,483,647.

A value of 1 is most important and higher values are less important.

A value of 0 means that no priority has been set for this item.

RestrictPlanMode Determines whether Calculate Plan implements restricted logic for calculating planned replenishment quantities and which method of restricted planning logic it uses.

• 1: No restriction

A planned replenishment is generated at the first point in time that projected availability is less than zero, and each subsequent time that the projected availability is less than zero, always without regard to any subsequent firm replenishments that occur beyond the coverage duration.

• 2: Simple restriction

No replenishments are scheduled prior to the latest firm supply or drop in safety stock that occurs within the restricted plan duration that brings the projected available above zero. You set the length of the restricted plan duration in SKUPlanningParam:RestrictDur.

• 3: Severe restriction

With this method, Plan observes all firm replenishments and drops in safety stock within the restricted plan duration (SKUPlanningParam:RestrictDur) and reduces or eliminates earlier planned replenishments accordingly. Whenever a planned arrival or planned order is created within the restricted plan duration, its quantity will be limited such that the projected available will not be greater than zero at any time between the end of the coverage duration and the end of the restricted planning duration.

With this option, Plan determines planned replenishment quantities and dates using the following rules, in order of priority:

• Respect minimum and incremental rounding quantities.

• Avoid future overstock within the restricted planning duration.

• Respect coverage duration and order up to quantity values, except that if the end of the coverage duration is later than the end of the restricted plan duration, the full coverage duration will be respected.

With severe restricted logic, some replenishments will be much smaller than they would be using normal coverage duration logic.

Since this option will always eliminate situations of excess inventory by producing temporary shortages, it is recommended for items for which excess inventory costs are significantly greater than stockout costs—for example, perishable items or items that become obsolete quickly.

For more information on restricted logic, see the OnLine Expert.

StorageGroup


Item

Group name of items grouped together for the purpose of defining a storage constraint.

SupsnGroupNum Supersession group number is a unique number which is grouped and allocated during LevelSKU process. The Calculate Plan uses the information.

UnitsPerAltShip Note: This column is not used in this release.

UnitsPerPallet Number of units of the item, defined in this row, that make a pallet.

UOM A textual description of the unit of measure in which quantities of this item are assumed to be expressed. For example, the unit of measure might be units, gallons, or cases.

You should use consistent units of measure for items that are logically linked. If you compare or sum quantities for items that have different units of measure, the results will have no meaning.

Vol Volume of the item defined in this row.

Wgt This column is used only by Dynamic Deployment, and is used there to calculate transportation costs when Item: DDSrcCostSw is set to No.


LewandowskiParam

LewandowskiParam Table included with: Demand, Flowcasting


Default value

DDEImpact Dmd, Flowcasting DECIMAL 1.0

DmdGroup 2 Dmd, Flowcasting TEXT DmdUnit 1 Dmd, Flowcasting TEXT HistDependency Dmd, Flowcasting DECIMAL 1.0 HybridFactor Dmd, Flowcasting DECIMAL 0.5 InitialLinearTrend Dmd, Flowcasting DECIMAL 0 InitialMeanValue Dmd, Flowcasting DECIMAL 0 InitialQuadTrend Dmd, Flowcasting DECIMAL 0 InitMeanOverrideSw

Dmd, Flowcasting BOOLEAN 0

LifecycleFactor Dmd, Flowcasting TEXT ' ' LifecycleStartDate Dmd, Flowcasting DATE TO_DATE('01/01

/1970','MM/DD/YYYY')

LinExtFactor Dmd, Flowcasting TEXT ' '

LinFactorImpact Dmd, Flowcasting DECIMAL 1.0 LinFactorOpt Dmd, Flowcasting OPTION_NU

MBER 1,2,3 1

Loc 3 Dmd, Flowcasting TEXT

MeanValueDynamic

Dmd, Flowcasting, Flowcasting

DECIMAL 1.0

MeanValueMax Dmd, Flowcasting DECIMAL 1.0 Model 4 Dmd, Flowcasting TEXT NonLinExtFactor Dmd, Flowcasting TEXT ' ' NonLinFactorAmp Dmd, Flowcasting DECIMAL 1.0 NonLinFactResponse

Dmd, Flowcasting DECIMAL 0.01

NumOptSteps Dmd, Flowcasting OPTION_NUMBER

1,2,3,4,5,6

3

SeasonalityImpact Dmd, Flowcasting DECIMAL 1.0

SeasonalitySw Dmd, Flowcasting BOOLEAN 1 SmoothedMAD Dmd, Flowcasting DECIMAL 1.0 SmoothProfileSw Dmd, Flowcasting BOOLEAN 1,0 1.0 StabilityRateNF Dmd, Flowcasting DECIMAL 1.0 TrackingSignalAWS

Dmd, Flowcasting DECIMAL 1.0

TrendCombination Dmd, Flowcasting INTEGER 5


LewandowskiParam


Default value

TrendMethod Dmd, Flowcasting OPTION_NUMBER

1,2,3,4,5,6

2

Table description The LewandowskiParam table stores all of the parameters you set for Lewandowski forecast models.

Note: Seasonality starting values are stored in the SeasonProfileValues table. The profile is attached to the DFU in DFU:SeasonProfile.

Column descriptions DDEImpact The value in this field influences the impact of the data driven events on the model.

Valid values for Data Driven Event Impact are 0.01 to 9.99.

DmdGroup The demand group associated with the DFU whose Lewandowski parameters are defined in this row.

DmdUnit The demand unit associated with the DFU whose Lewandowski parameters are defined in this row.

HistDependency Weights the history periods. The value in this field influences the development of the tracking signal (AWS) by determining how much previous error should be considered with more recent error during systematic trend changes. For example, if there is an end to systematic trend changes, the system resets this parameter to 0 to forget older errors and begin with a new AWS.

Valid values for History Dependency are 0.001 to 9.9.

HybridFactor Indicates how the system should use the remaining history, relative to the value you specified for TrendCombination, when it calculates the forecast. The system uses the trend signal of the last period to determine how much weighting to apply to the medium- to long-term history.

Valid values for Hybridization Factor are 0.01 to 0.7.

InitialLinearTrend If the Trend = 2 (Linear) and the InitialMeanOverrideSw = 1 (Manual), then the Initial Mean Value and the Initial Mean Value for Linear Trend may be used.

InitialMeanValue If the Trend = 1 (Constant) and the InitialMeanOverrideSw = 1 (Manual), then the Initial Mean Value must be specified.

InitialQuadTrend If the Trend = 3 and the InitMeanOverrideSw = 1 (Manual), then the Initial Mean Value, the Initial Mean Value for Linear Trend, and the Initial Mean Value for Quadratic Trend may be used.

InitMeanOverrideSw Set the starting mean value:

• 0: Let the system automatically calculate the mean starting value for the model, regardless of the type of model you are using.


LewandowskiParam

• 1: Manually set the mean starting value.

Valid values for Initial Mean Override Switch are 0 (Automatic) and 1 (Manual).

LifecycleFactor A lifecycle associated with this DFU. The lifecycle must be defined in the LewFactor table.

LifecycleStartDate The beginning of the period covered by the lifecycle defined in this row.

LinExtFactor The name of the Linear External Factor. The factor must be defined in the LewFactor table.

LinFactorImpact The impact that the linear factor will have on the forecast.

Valid values for Linear Factor Impact are -99.99 to 999.9.

LinFactorOpt Indicates whether or not there is a lifecycle factor or linear external factor.

Valid values for Linear Factor Option are 1=No lifecycle factor or linear external factor, 2=Linear external factor, and 3=Lifecycle factor.

Loc The location associated with the DFU whose Lewandowski parameters are defined in this row.

MeanValueDynamic Specifies how reactive the mean should be to recent history periods. Lower values imply a more stable mean value, while higher values imply a more dynamic mean value. Also referred to in the interface as Dynamic Mean Impact.

Valid values for Mean Value Dynamic are 0.01 to 9.99.

MeanValueMax Specifies the maximum degree to which the mean should be reactive to all of the DFU's history.

Valid values for Mean Value Maximum are 0.01 to 9.9999.

Note: If mean value max is higher than mean value dynamic, the Calculate Model process smoothes values from mean value dynamic till mean value max and provides better results for MSE, SymmetricMAPE, and fitted history.


Valid values for Model are identifiers of a model.

NonLinExtFactor The name of the Non-Linear External Factor. The factor must be defined in the LewFactor table. Non-Linear External Factors are not implemented in this release. This column is included to allow for data migration only.

NonLinFactorAmp The amplitude of the non-linear factor. Non-Linear External Factors are not implemented in this release. This column is included to allow for data migration only.

Valid values for Nonlinear Factor Amplitude are -9.99 to 99.99.

NonLinFactResponse


LewandowskiParam

The response of the non-linear factor. Non-Linear External Factors are not implemented in this release. This column is included to allow for data migration only.

Valid values for Nonlinear Factor Response are -9.99 to 99.99.

NumOptSteps Determines the number of times the model can be optimized (1-6). With each optimization, the system attempts to improve the accuracy of the forecast by refitting the data based on changes to model parameters.

Valid values for Number of Optimization Steps are 1 to 6.

SeasonalityImpact Specifies the degree of seasonality applied to the model.

Valid values for Seasonality Impact are 0.01 to 9.9999.

SeasonalitySw Determines whether the model includes adjustments for seasonal influences.




SmoothedMAD Specifies the amount of impact the mean absolute deviation (MAD) of the fitted forecast should have on the algorithm. The MAD is a measure of the difference between the historical forecast and the actual demand posted during those periods.

Valid values for Smoothed Mean Absolute Deviation are 0.001 to 9.9.

SmoothProfileSw Indicates if the Starting Seasonality values are smoothed or used without smoothing in calculating the forecast. Default value for the SmoothProfileSw is 1. Valid values are 1 and 0.

StabilityRateNF Specifies the amount of impact the relative forecast error (NF) should have on the algorithm. The relative error is a comparison of the forecast deviation of the current period to the average forecast deviation (MAD) of the DFU. This control signal can be used to indicate outlier values.

Valid values for Stability Rate NF are 0.001 to 9.9.

TrackingSignalAWS Specifies the amount of impact the AWS tracking signal should have on the algorithm. The tracking signal is an indication of a DFU's trend. Generally, the farther the tracking signal is from 0, the more unstable the DFU.

Valid values for Tracking Signal AWS are 0.001 to 9.9.

TrendCombination Indicates how the system should use history to calculate the forecast. The greater the value you specify for this parameter, the more weighting is placed on short-term history.

Valid values for Trend Combination are 0 to 9.

TrendMethod Valid values for Trend Method are 1 to 6.

Select the method to use as the basis for calculating the mean and trend:


LewandowskiParam

• 1: No trend

The mean is calculated based on a dynamic mean value without calculating a trend. This method is particularly applicable to DFUs that are forecasted on a weekly basis.

• 2: Linear trend

The mean is calculated using a dynamic mean value, with the system assigning a linear trend to the model. This method is appropriate for DFUs forecasted on a monthly basis.

• 3: Quadratic trend

The mean is calculated using a dynamic value, with a quadratic trend.

• 4: Automatic trend

The system selects the model best suited to fit the DFU.

• 5: Dynamic 1 trend

The system uses the constant model for the first cycle (for example, for the first year, if the DFU is forecasted monthly). After the first cycle, a linear model is used for the rest of the DFU periods.

• 6: Dynamic 2 trend

The system uses the constant model for the first cycle, the linear model for the second cycle, and then switches to the quadratic model for the remainder of the DFU.


LewandowskiStats

LewandowskiStats Table included with: Demand, Flowcasting


Default value

AvgRe lTrend Dmd, Flowcasting

DECIMAL 0.0


TEXT


TEXT

InitialLewMeanQty

Dmd, Flowcasting

DECIMAL 0

LastAWS Dmd, Flowcasting

DECIMAL 0.0

LastFittedFcst Dmd, Flowcasting

DECIMAL 0.0

LastHist Dmd, Flowcasting

DECIMAL 0.0

LastMAD Dmd, Flowcasting

DECIMAL 0.0

LastMADdivM Dmd, Flowcasting

DECIMAL 0.0

LastNormFcstErr Dmd, Flowcasting

DECIMAL 0.0

LastRelError Dmd, Flowcasting

DECIMAL 0.0

LastRelTrend Dmd, Flowcasting

DECIMAL 0.0


TEXT

MaxTrend Dmd, Flowcasting

DECIMAL 0.0


DECIMAL 0

MinTrend Dmd, Flowcasting

DECIMAL 0.0


TEXT


DECIMAL 0.0

NumHistObserv Dmd, Flowcasting

DECIMAL 0


DECIMAL 0.0

Table description


LewandowskiStats

The LewandowskiStats table stores the statistical output (system calculated values) for Lewandowski forecast models after the forecast has been generated (either through the Calculate Model process or the Demand Workbench).

Note: If period weighting is applied, all statistics are calculated based on weighted history. If a DFU has an attached moving event, only Mean, MSE, and SymmetricMAPE will be published.

Column description AvgRelTrend The average degree of growth of the mean value during the last period, derived by relating the trend in the forecast to the mean value.

DmdGroup The demand group associated with the DFU whose Lewandowski statistical output is defined in this row.

DmdUnit The demand unit associated with the DFU whose Lewandowski statistical output is defined in this row.

InitialLewMeanQty InitialLewMeanQty is the mean value of the first forecast period (FcstDraft:LewMeanQty) of a DFU. In a relationship defined by the process of introducing New DFUs through the New DFU Introduction functionality, the LewandowskiStats:InitialLewMeanQty of the old DFU is copied as the LewandowskiParam:InitialMeanValue of the new DFU.

LastAWS AWS of Last History Period (LastAWST) is an indicator of the DFU's trend for the last history period. The trend is the change in the mean value over consecutive periods and is expressed as a positive or negative number, or as zero. The farther away from zero the tracking signal is, the more unstable the DFU.

LastFittedFcst The fitted forecast for the last history period. A fitted forecast is a forecast based on historical demand values.To create the fitted forecast, the system calculates what the forecast would have been if the actual historical demand values were used. The fitted forecast is not the same as the historical forecast. The historical forecast is the calculated forecast of future demand after the forecast periods occur.

LastHist The historical data for the last history period.

LastMAD The last period’s mean absolute deviation for Lewandowski models.

LastMADdivM MAD/Mean of Last History Period is the degree of accuracy of the fitted forecast for the last history period. This is a measure of the quality of the DFU's forecast, expressed as a percentage. The forecast quality is calculated as the mean absolute deviation of the forecast over its mean value.

LastNormFsctError The adjusted forecast error for the last period before the demand post date.

LastRelError A comparison of the forecast deviation of the last history period to the average forecast deviation (MAD) of the DFU. This control signal can be used to indicate outlier values.

LastRelTrend The degree of growth of the mean value during the last period, derived by relating the trend in the forecast to the mean value. JDA Demand Management Foundation Reference Guide 200 © 1997 - 2014 JDA Software Group, Inc.- Confidential

LewandowskiStats

Loc The location associated with the DFU whose Lewandowski statistical output is defined in this row.

MaxTrend The maximum degree to which the trend should be reactive to all of the DFU's history. This value is set by the system.

Mean The mean in the history. LewandowskiStats:Mean is for reporting purposes only.


MinTrend The minimum degree to which the trend should be reactive to all of the DFU's history.


Valid values for Model Identifier are identifiers of a model.

MSE Mean squared error based on the historical fitting periods. The formula used is as follows:

where N= number of history points

NumHistObserv Number of history periods Calculate Model looked at when fitting the statistical model for the DFU.




where:




• t = time period


LewandowskiStats



Absolute Error


fitted history


SMAPE

H FH AE=|H-FH|


January -11 50 52 2 51 3.9 February -10 55 47 8 51 15.7 March -9 38 41 3 39.5 7.6 April -8 32 37 5 34.5 14.5 May -7 42 38 4 40 10.0 June -6 37 40 3 38.5 7.8 July -5 45 42 3 43.5 6.9 August -4 41 44 3 42.5 7.1 September -3 51 46 5 48.5 10.3 October -2 50 48 2 49 4.1 November -1 36 40 4 38 10.5 December 0 53 51 2 52 3.8 Total



LewFactor

LewFactor Table included with: Demand, Flowcasting




TEXT ' '


TEXT NULL

LewFactor 1 Dmd, Flowcasting

TEXT

LewFactorCategory

Dmd, Flowcasting

UPPER_TEXT ' '

LewFactorType Dmd, Flowcasting

OPTION_NUMBER

1,2,3 3



Table description This table is used to store the Lewandowski external factors and lifecycles.

Column descriptions Descr The description for the Lewandowski factor.

DmdCal The demand calendar associated with this Lewandowski factor.

Valid values for Demand Calendar are identifiers of a calendar whose Cal:Type is 5.

LewFactor The name of the Lewandowski factor.

LewFactorCategory The name of the Lewandowski factor category.

LewFactorType Valid Values for Lewandowski Factor Type are 1=Linear External Factor, 2=Non-Linear External Factor, and 3=Lifecycle Factor.

Indicates whether the Lewandowski factor is linear external, non-linear external, or a lifecycle factor. Non-linear external factors are saved in the database and will appear in Flexible Editor, but they are not implemented in this release.

StartDate The beginning date of the period to which this Lewandowski factor applies. This column only applies to linear external factors (LewFactorType = 1).


LewFactorCategory

LewFactorCategory Table included with: Demand, Flowcasting




TEXT ' '

LewFactorCategory 1 Dmd, Flowcasting

TEXT

Table description This table stores a list of Lewandowski factor categories that you can then assign to the factors stored in the LewFactor table. This table can be used with the LewFactorLibMap and LewFactorLibrary tables to allow you to easily group and organize your factors.

Column descriptions Descr The description of the Lewandowski factor category.

LewFactorCategory The name of the Lewandowski factor category.


LewFactorLibMap

LewFactorLibMap Table included with: Demand, Flowcasting



LewFactorCategory

2 Dmd, Flowcasting

TEXT

LewFactorLibrary 1 Dmd, Flowcasting

TEXT

Table description This table maps the categories stored in the LewFactorCategory table to the libraries stored in the LewFactorLibrary table. These tables allow you to easily group and organize your factors.

Column descriptions LewFactorCategory The name of the Lewandowski factor category.

LewFactorLibrary The name of the Lewandowski factor library.


LewFactorLibrary

LewFactorLibrary Table included with: Demand, Flowcasting



Default value


TEXT ' '

LewFactorLibrary 1 Dmd, Flowcasting

TEXT

LewFactorType Dmd, Flowcasting

OPTION_NUMBER 1,2,3 3

Table description This table stores a list of Lewandowski factor libraries that you can then assign to the factors stored in the LewFactor table. This table can be used with the LewFactorLibMap and LewFactorCategory tables to allow you to easily group and organize your factors.

Column descriptions Desc The description for the Lewandowski factor library.

LewFactorLibrary The name of the Lewandowski factor library.

LewFactorType Indicates whether the Lewandowski factor is linear external, nonlinear external, or a lifecycle factor.

Valid Values for Lewandowski Factor Type are 1=Linear External Factor, 2=Nonlinear External Factor, and 3=Lifecycle Factor.


LewFactorValue

LewFactorValue Table included with: Demand, Flowcasting



AverageValue Dmd, Flowcasting

DECIMAL 0.0

FactorValue Dmd, Flowcasting

DECIMAL 0.0

LewFactor 1 Dmd, Flowcasting

TEXT

NormalizedValue

Dmd, Flowcasting

DECIMAL 1.0


INTEGER

Table description This table stores values for the Lewandowski external factors and lifecycles.

Column descriptions AverageValue The average value of the factor values based on their position in a year with respect to periodicity. For example, if the periodicity (Cal:NumFcstPer) of the demand calendar is 12, then period 1 will be averaged with period 13. The result will be saved in this column for periods 1 and 13. Similarly, period 2 will be averaged with period 14 and the result saved in this column for periods 2 and 14.

FactorValue Starting value input by the user.

LewFactor The name of the Lewandowski factor associated with the data in this table.

NormalizedValue The adjusted value for this Lewandowski factor.

Period The period associated with this Lewandowski factor value.


LibraryCategoryMap

LibraryCategoryMap Table included with: Demand



Category 1 Dmd, Flowcasting

TEXT

Libname 2 Dmd, Flowcasting

TEXT

Table description The LibraryCategoryMap table stores the mapping relationship between category and library.

Column descriptions Category Name of the category.

Libname Name of the library.


LinRegParam

LinRegParam Table included with: Demand, Flowcasting



Default value

CorrFactor Dmd, Flowcasting

DECIMAL 2

DmdFilter Dmd, Flowcasting

DECIMAL 2


TEXT


TEXT

EstimateTrendSw Dmd, Flowcasting

BOOLEAN 1

FtoEnter Dmd, Flowcasting

DECIMAL 4.0

FtoLeave Dmd, Flowcasting

DECIMAL 4.0


TEXT

MaxNumTerms Dmd, Flowcasting

INTEGER 2

MaxSteps Dmd, Flowcasting

INTEGER 10000

MLROutlierRefit Dmd, Flowcasting

BOOLEAN 1

MLRSigAmpSw Dmd, Flowcasting

BOOLEAN 0


TEXT


DECIMAL 2

RegressionMethod Dmd, Flowcasting

OPTION_NUMBER 1,2,3 1

SigAmp Dmd, Flowcasting

DECIMAL 2

SmoothConstant Dmd, Flowcasting

DECIMAL 0

SmoothSw Dmd, Flowcasting

BOOLEAN 0

SubSelectionMethod

Dmd, Flowcasting

OPTION_NUMBER 1,2,3,4,5,6 1

TimeWgt Dmd, Flowcasting

DECIMAL 1

ToleranceFactor Dmd, Flowcasting

DECIMAL .00001

TrendFactor Dmd, Flowcasting

DECIMAL 0


LinRegParam

Table description Columns in the LinRegParam table are parameters to be used with the Fourier and Multiple Linear Regression (MLR) algorithms. Many of the columns were previously part of the DFU table. You can set the variables directly in the LinRegParam table or through the Demand Workbench while reviewing the models.

Column descriptions CorrFactor Value used by the Calculate Model process to detect serial correlation in Fourier models.

Valid values for Correlation Threshold Factor are 0 or greater.

In a statistical model without serial correlation, the sign of the forecast error (actual demand minus model demand) is random—positive in some periods and negative in others. Serial correlation occurs when a string of forecast errors have the same sign, indicating a break in the pattern of demand or seasonality that is not reflected in the model.

If you know when the break in demand occurred, you can fit a model without serial correlation by including only the history periods after the break. You might also try increasing the value of LinRegParam:SigAmp.

If you increase the value in CorrFactor, the system is less likely to find serial correlation. If you decrease the value, the system is more likely to find serial correlation.

Note: This option applies only to Fourier models.

DmdFilter Value used by the system (when refitting a model) to determine whether a DFU's actual demand values posted for the current period are within a reasonable range of the demand values forecasted for the period.

Valid values for Demand Filter Threshold are 1 or greater.

The system checks the demand to date for reasonableness. The system multiplies DmdFilter by the square root of the Statistical Model Mean Squared Error (DmdFilter*SQRT(DFU:StatMSE)). The resulting value is the range above and below the forecasted demand within which the actual demand should fall. (For example, if the forecasted demand is 1000, DmdFilter is 3, and StatMSE is 1000, the actual demand should be between 700 and 1300.) If the actual demand falls outside that range, the system sets DFUException:Exception to indicate a demand filter exception.

Note: This column is used when you run Calculate Model with the Update Fourier model and the Create demand filter exceptions options selected.

DmdGroup The demand group associated with the DFU whose Fourier and MLR parameters are defined in this row.

DmdUnit The demand unit associated with the DFU whose Fourier and MLR parameters are defined in this row.

EstimateTrendSw The EstimateTrend Sw switch allows for selectively turning off trend estimation to project forward the seasonality observed in one year’s worth of data.

FtoEnter


LinRegParam

The F-ratio for testing whether a particular regressor should be added to the model. This option is used for Forward and Stepwise subset selection methods; if you select 1 or 2 as the subset selection method, the algorithm ignores this parameter.

Valid values for F to Enter are 0.0 or greater.

Note: This column applies only to MLR models.

FtoLeave The F-ratio for testing whether a particular regressor should be removed from the model. This option is used for Backward and Stepwise subset selection methods; if you select 1 or 3 as the subset selection method, the algorithm ignores this parameter. This value should be less than or equal to FtoEnter; otherwise, the system generates an exception.

Valid values for F to Leave are 0.0 or greater.


Loc The location associated with the DFU whose Fourier and MLR parameters are defined in this row.

MaxNumTerms Maximum number of terms Calculate Model can use in the Fourier or MLR statistical model for the DFU. Can be up to the number of forecast periods per year plus one.

Valid values for Maximum Number of Model Terms are 1 up to 1 + the number of forecast periods per year in the demand calendar. It is recommended to keep this number as small as possible.

Note: This column applies to Fourier and MLR models.

MaxSteps Maximum number of regression steps that will be performed in No subset (1), Backward (2), Forward (3), and Stepwise (4) regression selection methods. This setting is helpful if you have a model that includes a large number of causal factors which could require a large number of regression steps. If the system exceeds its MaxSteps limit, the model stops running and the system sets DFUException:Exception to indicate that the model may have selected a less than optimal solution due to an exception in the maximum number of regression steps.

Valid values for Maximum # of Steps are 1 or greater.


MLROutlierRefit Used to turn off outlier refitting during Multiple-Linear Regression (MLR) calculations when using the Included Model subset selection method. This variable can be used in conjunction with the MLRIncludedModel ini variable to exactly reproduce the results of the initial fitting. If it is not important to reproduce the results of the initial fitting, you do not need to turn off outlier refitting even if the MlrIncludedModel ini variable is used. For a more detailed description of the effects, see the LinRegParam:SubSelectionMethod column.

Valid values for MLR Outlier Refit are 0 (N) and 1 (Y).

MLRSigAmpSw Indicates whether the MLR model should consider the significant amplitude factor (LinRegParam:SigAmp) when calculating a model’s seasonality.

Valid values for MLR Significant Amplitude Switch are 0 (N) and 1 (Y).



LinRegParam

Valid values for Model Identifier are 0 (N) and 1 (Y).


Valid values for Outlier Threshold Factor are 2.0 or greater.

The system multiplies the OutlierFactor by the standard error of the model, then adds the result to or subtracts the result from the model demand value. Outliers are history period values that fall outside the resulting range of reasonable values. DBParam:OutlierOpt determines how Calculate Model handles outliers.

If you decrease the value of OutlierFactor, the number of outliers increases. If you increase OutlierFactor, the number of outliers decreases.

When the system detects outliers, it generates an exception in DFUException.

RegressionMethod Value that indicates which regression model the MLR algorithm will use to solve a regression equation.

Valid values for Regression Method are 1,2, and 3.

• 1: QR Decomposition

Involves decomposing the regression matrix into the product of an orthogonal matrix (Q) and an upper triangular matrix (R). This method has good performance, but it can fail if the regression matrix is of less than full rank.

If the causal factors that are assigned to this DFU in DFUCausalFactor contain no historical data, processing stops and the system generates an exception.

• 2: QR Decomposition with Pivoting

Similar to the QR Decomposition method, except pivoting is used in the decomposition. Pivoting involves moving the columns of the input (regression) matrix to increase the robustness of the regression. It is only necessary when the input matrix is close to singular—that is, when one or more of the causal factors is very close to being a linear combination of the others. This method is more robust than QR, but it is slightly slower.

If the causal factors that are assigned to this DFU in DFUCausalFactor contain no historical data, processing stops and the system generates an exception.

• 3: Singular Value Decomposition

Involves decomposing the regression matrix into three matrices that have specific properties based upon the eigenvectors and eigenvalues of the regression matrix. This is the most robust (but slowest) method that is generally used to solve regression equations.


SigAmp The system uses this value to choose the best statistical model for the DFU. The larger the value in SigAmp, the more likely the system is to choose a more seasonal model (that is, a model with more terms). However, too large a value may introduce random noise into the model.

Valid values for Significant Amplitude Factor are 1.0 to 10.0.

If a model has more than two terms, the system uses SigAmp, the amplitude, and the standard deviation to determine whether the seasonal pattern is real or the model is just picking up noise in the history. Calculate Model tests each of the sine curves in the model and keeps all up to the highest frequency with significant amplitude. For example, with a value of 2 for SigAmp, the significant amplitude is a minimum of half the Standard Error. If you change SigAmp to 3, the significant amplitude is only one-third of the Standard Error.


LinRegParam

Note: This column applies only to Fourier models, or MLR models if MLRSigAmpSw is set to 1.

SmoothConstant Constant value used in the smoothing process if SmoothSw is set to Yes. To smooth, the system calculates the Level and Trend using the values in the previous Level or Trend (Old Coef) and the new Level or Trend (New Coef) in this equation:

[(1 - SmoothConstant) × OldCoef)] + (SmoothConstant × New Coef)

Reasonable values for the Smoothing Constant are between 0.1 and 0.3.

Valid values for Smoothing Constant are 0 to 1.

Note: Calculate Model performs smoothing for Fourier models when you select the Apply smoothing option and specify a Smoothing Constant.

SmoothSw Switch that determines whether Calculate Model smooths the model for this DFU (using the value in LinRegParam:SmoothConstant). Yes = Smooth, No = Do not smooth. Smoothing involves revising the model to account for actual demand.

Valid values for Smoothing Switch are 0 (N) and 1 (Y).

This feature is particularly useful if you have manually edited LinRegStats:ModelLevel or LinRegStats:ModelTrend. Smoothing will gradually adjust the edited values. Without smoothing, Calculate Model recalculates ModelLevel and ModelTrend based on history.

Note: Calculate Model performs smoothing for Fourier models when you select the Apply smoothing option.

SubSelectionMethod Method the system uses, along with seasonality, level, and trend, to select which causal factor variables to include in the forecast. For example, if there are three causal factors {a, b, and c}, then there are seven possible subsets: {a}, {b}, {c}, {a,b}, {b,c} {a,c}, {a,b,c}.

Valid values for Subset Selection Method are 1 to 6.

Choose from the following regression selection methods:

• 1: No subset – Use All Causal Factors

Regression includes all causal factors assigned to the DFU. This will only produce the same results as Fourier if there are no causal factors attached to the DFU and if no Fourier terms were dropped because they were less than the SigAmp value.

• 2: Backward

Starts by selecting all of the regressor variables, then iteratively removes the least significant, providing that its F-value is less than FtoLeave. The selection process ends when all of the variables remaining in the model are significant. As implemented, an intercept term (that is, level) is always included in the model.

• 3: Forward

Starts with none of the regressor variables selected, then iteratively adds the most significant, providing that its F-value is greater than FtoEnter. The selection process ends when there are no more significant variables to add. As implemented, an intercept term is always included in the model.

• 4: Stepwise

Involves a combination of forward and backward selection. After each forward iteration, a backward iteration is performed to determine whether the addition of a variable has made any of the variables already in the model lose their significance. To prevent cycling, FtoLeave must be less than or equal to FtoEnter. As implemented, an intercept term is always included in the model.


LinRegParam

• 5: Included Model

This option may only be selected by using the MlrIncludedModel ini variable or by directly editing this table using the Flexible Editor. When Calculate Model is executed using subset selection methods 1-4, the included columns in the DFUCoef and DFUCausalFactor tables are set to indicate the model’s Fourier coefficients and/or causal factors. To subsequently reuse these values when you run Calculate Model chose subset selection method 5.

To exactly reproduce the results of the initial fitting, the MlrOutlierRefit ini variable must be turned off both in the initial model fitting and in the included model fitting.

The steps to use subset selection method 5 include:

• Set the MlrIncludedModel ini variable to No and/or the MlrOutlierRefit ini variable to No.

• Run the Calculate Model process using subset selection method 1-4.

• Either set subset selection method to 5 by directly modifying the LinRegParam table using Flexible Editor and set the MLROutlierRefit ini variable to No; or leave the existing subset selection method and set the MLRIncludedModel ini variable to Yes (if MlrIncludedModel is set to either Yes or No, the MlrOutlierRefit ini variable is automatically set to No).

If it is not important to reproduce the results of the initial fitting, you do not need to turn off outlier refitting even if the MlrIncludedModel ini variable is used.

• 6: Reduced Model

This option may only be selected by using the MLRReducedModel ini variable or by directly editing this table using the Flexible Editor. The Reduced Model subset selection method is a limited stepwise model, in that it only performs two fittings. In the first fitting, all non-omitted regressors are added to the model and model parameters are calculated. In the second fitting, all regressors that are not significant based on the first fitting are dropped, and this becomes the final model.

Note: This columns applies only to MLR models.

TimeWgt Value used by Calculate Model to give greater weight to more recent observations. A value of 1 results in no time weighting.

Valid values for Time Weight are greater than 0.5 and less than or equal to 1.0.

The system uses TimeWgt to calculate the factor by which to multiply the model error in each period. If there are n history periods, the earliest of which is period 1, the weighted error for period t is calculated as:

Typical values are 0.996 for weekly forecasting or 0.98 for monthly forecasting. If you have 36 periods, a value of 0.98 will weight the most recent period twice as heavily as the earliest period. If you have 156 periods, a value of 0.996 will weight the most recent period twice as heavily as the earliest period.

ToleranceFactor Used with QR Decomposition with Pivoting and Singular Value Decomposition regression methods. The tolerance factor determines when the system should consider regression matrix elements (QR Decomposition with Pivoting) as zero, or when it should consider the singular values (Singular Value Decomposition) as zero. This should represent the accuracy to which you know entries in the input matrix. The MLR calculation using QR Decomposition with Pivoting will fail, however, if the causal factor matrix has a column of zeros—that is, if the value of the causal factor is zero for every time period.

Valid values for Tolerance Factor are 0 to 1.0.

Note: This column only applies to MLR models. JDA Demand Management Foundation Reference Guide 214 © 1997 - 2014 JDA Software Group, Inc.- Confidential

LinRegParam

TrendFactor Value used to lessen the effect of the trend on the DFU's statistical forecast. You might want to adjust the trend for a new DFU with demand that steeply increases at the outset but levels off over time.

Valid values for Trend Discount Factor are 0 to .5.

The system uses TrendFactor to calculate the factor by which to reduce the Trend in each period. The system calculates the new trend for each period t with this equation:

For example, if TrendFactor is 0.1, the trend is multiplied by 1, 0.9, and 0.81 in forecast periods 1, 2, and 3 respectively.


LinRegStats

LinRegStats Table included with: Demand, Flowcasting


AdjustedRSquare Dmd, Flowcasting

DECIMAL 0


TEXT


TEXT

DurbinWatsonStat Dmd, Flowcasting

DECIMAL 0


TEXT


DECIMAL 0


TEXT

ModelLevel Dmd, Flowcasting

DECIMAL 0

ModelTrend Dmd, Flowcasting

DECIMAL 0

NumEvent Dmd, Flowcasting

INTEGER 0

NumHistObserv Dmd, Flowcasting

INTEGER 0

NumHistPerUsed Dmd, Flowcasting

INTEGER 0

NumModelTerm Dmd, Flowcasting

INTEGER 0

NumOutlier Dmd, Flowcasting

INTEGER 0

NumPerMask Dmd, Flowcasting

INTEGER 0

NumPerSmooth Dmd, Flowcasting

INTEGER 0

NumSysAdjOutlier Dmd, Flowcasting

INTEGER 0

RSquare Dmd, Flowcasting

DECIMAL 0.0

SE Dmd, Flowcasting

DECIMAL 0.0

StatMSE Dmd, Flowcasting

DECIMAL 0.0


DECIMAL 0.0


LinRegStats

Table description The LinRegStats table stores the statistical output (system calculated values) from the Fourier and Multiple Linear Regression (MLR) forecast models. Most of the columns were previously part of the DFU table.

Note: If period weighting is applied, all statistics are calculated based on weighted history.

Column descriptions AdjustedRSquare RSquare value corrected for the number of degrees of freedom of residuals and regressors (that is, the number of history observations and the number of causal factor variables).

Note: If AdjustedRsquare = zero, and DFU:NPISw (on page 67) is enabled, it can be concluded that the DFU is new and does not yet have enough history for the model fit statistics to be meaningful. The statistical value will not be meaningful until the DFU reaches the Independence Date.

DmdGroup The demand group associated with the DFU whose Fourier and MLR statistical output is defined in this row.

DmdUnit The demand unit associated with the DFU whose Fourier and MLR statistical output is defined in this row.

DurbinWatsonStat Tests for both the positive and negative correlation in the residuals. The Durbin-Watson statistic is approximately equal to 2 * (1-r), where r is the estimated serial correlation coefficient of the residuals. If there is no serial correlation in the residuals, the Durbin-Watson statistic will be approximately 2.0. A Durbin-Watson value less than 2 is associated with positive serial correlation of the residuals, while a value greater than 2 is associated with negative serial correlation of the residuals. In general, a Durbin-Watson value less than 1.4 or greater than 2.6 is indicative of a possible problem.

Note: If DurbinWatsonStat = zero, and DFU:NPISw (on page 67) is enabled, it can be concluded that the DFU is new and does not yet have enough history for the model fit statistics to be meaningful. The statistical value will not be meaningful until the DFU reaches the Independence Date.

Loc The location associated with the DFU whose Fourier and MLR statistical output is defined in this row.

Mean The mean in the history, omitting masked values. LinRegStats:Mean is for reporting purposes only.




ModelLevel The level term in the statistical forecast model for the DFU. LinRegStats:ModelLevel is for reporting purposes only; the level value used by the system is in DFUCoef:Coef.

ModelTrend


LinRegStats

The trend term in the statistical model for the DFU, which is the number of units by which ModelLevel changes each period. You can use TrendFactor to temporarily dampen the trend without changing the value in this column. LinRegStats:ModelTrend is for reporting purposes only; the Trend value used by the system is in DFUCoef:Coef.

NumEvent An inactive column that can be used in place of a user-defined small integer column if you need one in the LinRegStats table. Use the Administration application to make this column updatable. Refer to the JDA Supply Chain Planning and Optimization Installation/Administration Guide for information on changing column attributes.

NumHistObserv Number of history periods Calculate Model looked at when fitting the statistical model for the DFU. If DBParam:OutlierOpt is 2 or 3, this value is calculated as LinRegStats:NumHistPerUsed + LinRegStats:NumPerMask. If DBParam:OutlierOpt is 1, the calculation of NumHistObserv can vary.

NumHistPerUsed The number of history periods Calculate Model used in fitting the DFU’s statistical model.

NumModelTerm The number of terms Calculate Model used to fit the statistical model for this DFU.

NumOutlier The number of outlier values Calculate Model found when it fit the DFU's statistical model.

NumPerMask Previously part of the DFU table; the number of history periods that were masked when Calculate Model fit the statistical model for the DFU. A period is masked by a user-defined mask specified in the DFU table or by the system if the period includes an event defined in the Subevent table.

NumPerSmooth Number of periods that smoothing has been used on this model. If LinRegParam:SmoothSw is set to Yes, Calculate Model increments NumPerSmooth by 1 each time it smooths the model; otherwise, Calculate Model sets NumPerSmooth to 0.

Note: Calculate Model performs smoothing for Fourier models when you select the Apply smoothing option.

NumSysAdjOutlier The number of history points that were automatically adjusted by the Calculate Model process during the first iteration of the process, based on the DBParam:OutlierOpt setting.

RSquare The amount of variance from the history observations that is accounted for by the model. The system calculates RSquare as:

Note: If RSquare = zero, and DFU:NPISw (on page 67) is enabled, it can be concluded that the DFU is new and does not yet have enough history for the model fit statistics to be meaningful. The statistical value will not be meaningful until the DFU reaches the Independence Date.

SE The standard error of the model is the square root of StatMSE.

StatMSE The value that measures the accuracy of the statistical model by comparing it to actual demand.


LinRegStats

To calculate StatMSE, Calculate Model finds the residual differences—actual demand minus forecasted demand—for each history period.

Calculate Model initially calculates StatMSE as:

If the DFU has short history or lumpy demand, the system calculates StatMSE using the variance law and the level term of the model.

If the model is set for smoothing, Calculate Model uses the forecast error to smooth the new StatMSE for each period:

(1-SmoothConstant x oldStatMSE)+(SmoothConstant x forecast error2)

Note: Calculate Model performs smoothing for Fourier models when you select the Apply smoothing option




where:




• t = time period



Absolute Error


fitted history


SMAPE

H FH AE=|H-FH|


January -11 50 52 2 51 3.9

February -10 55 47 8 51 15.7 March -9 38 41 3 39.5 7.6


LinRegStats


Absolute Error


fitted history


SMAPE

April -8 32 37 5 34.5 14.5 May -7 42 38 4 40 10.0 June -6 37 40 3 38.5 7.8 July -5 45 42 3 43.5 6.9 August -4 41 44 3 42.5 7.1 September -3 51 46 5 48.5 10.3 October -2 50 48 2 49 4.1 November -1 36 40 4 38 10.5 December 0 53 51 2 52 3.8 Total



Loc

Loc Table included with: Fulfillment, Master Planning, Supply, Production and Sourcing Optimization, Demand, Strategic Pricing, Markdown Optimization, Inventory Policy Optimization, Dynamic Demand Response, Promotions Management, Travel Price Optimization, Demand Decomposition, Flowcasting, Enterprise Supply Planning


AltPlantID PSO, SP, MDO, Dmd Decomp Dmd, PM, Flowcasting

TEXT ' '

BorrowingPct FF DECIMAL 5 CompanyID Dmd, MP, Supp, SP,

MDO, Dmd Decomp, IPO, PM, Flowcasting, ESP (Deep Tree)

TEXT ' '

Country PSO TEXT Null Currency SP, PM, MDO NUMBER Cust SP, MDO, Dmd Decomp,

Dmd, PM TEXT ' '

Descr FF, MP, Supp, PSO, Dmd, SP, MDO, Dmd Decomp, IPO, PM, Flowcasting, ESP

TEXT ' '

DestCal TEXT ' ' EnableSw PSO, SP, MDO, Dmd

Decomp, Dmd, PM BOOLEAN 1

FrzStart FF, MP, MDO, Dmd Decomp, SP, Dmd, PM, Flowcasting, ESP (Deep Tree)

DATETIME 01/01/1970

Lat PSO, SP, MDO, Dmd Decomp, Dmd, PM

DECIMAL 0

Loc 1 FF, MP, Supp, PSO, Dmd, SP, MDO, Dmd Decomp, IPO, PM, Flowcasting, ESP

TEXT

Loc_Type FF, PSO, SP, MDO, Dmd Decomp, Dmd, PM, Flowcasting

OPTION_NUMBER

Any value in LocType: Type column

0

Lon PSO, SP, MDO, Dmd Decomp, Dmd, PM, Flowcasting

DECIMAL 0

OHPost FF, MP, MDO, Dmd Decomp, SP, Dmd, IPO, PM, Flowcasting, ESP (Deep Tree)

DATETIME 01/01/1970

PostalCode PSO TEXT Null SeqIntExportDur

MP, ESP DURATION 0


Loc


SeqIntImportDur

MP, ESP DURATION 0

SeqIntLastExportedToSeq

MP, ESP DATE 01/01/1970

SeqIntLastImportedFromSeq

MP, ESP DATE 01/01/1970

SourceCal TEXT ' ' TransZone MDO, Dmd Decomp, SP,

Dmd, PM, Flowcasting TEXT ' '

Type FF, MDO, Dmd Decomp, SP, Dmd, PM, Flowcasting

OPTION_NUMBER

Any value in LocType: Type column

1

VendID Dmd, Supp, Dmd, SP, MDO, Dmd Decomp, IPO, PM, Flowcasting

TEXT ' '

WDDArea Dmd, Flowcasting VARCHAR2(50 CHAR)

' '

WorkingCal FF, PM, Flowcasting, ESP

UPPER_TEXT

Table description Each row in this table defines a location. A location can represent a supplier, vendor, plant, distribution center, warehouse, store, or other similar location. Sometimes a row can also represent a virtual location, that is, two rows in this table might represent two categories of planning and inventory management that occur at the same physical location.

Column descriptions AltPlantID Note: This column is not used in the current release.

BorrowingPct The borrowing percent represents the rate that would be paid if money were borrowed to purchase additional inventory. This value is used when calculating the forward buy duration based on the DealSKU: ExtraDatingDur.

CompanyID This column is required for integration with external applications.

Country This column is used to specify country code (example, USA).

Currency This column is used to specify currency.

Cust If this is a customer location, set this value to the customer’s identifier (Cust:Cust).

A customer—typically a business, such as SuperStores—is defined in the Cust table. That customer may have multiple locations, which are specified in the Loc table.

Descr JDA Demand Management Foundation Reference Guide 222 © 1997 - 2014 JDA Software Group, Inc.- Confidential

Loc

A description of the location.

DestCal Not used in this release.

EnableSw This switch indicates if the location will be used while running the Production and Sourcing Optimization Optimizer.

FrzStart The beginning date of the freeze period. Valid values include any value less than or equal to Loc:OHPost (on page 224).

Master Planning / Fulfillment Master Planning, Fulfillment/Production, and Fulfillment/Distribution use this value as the beginning date for the freeze period whose duration is specified in SKUPlanningParam:MfgFrzDur or SKUPlanningParam:DRPFrzDur. If FrzStart is blank, the system uses the value in Loc:OHPost (on page 224) instead. If that is also blank, the system uses SKU:OHPost if it has a value. If not, it uses the current system date.

Master Planning, ESP (Deep Tree) For Master Planning, the freeze period starts at the planning period start date.

Lat The location’s latitude on the geographic map. The valid values are -90 to +90.

Loc A unique identifier of the location.

Supply This is a reference only field.

Master Planning, ESP When transportation resources are not linked to a specific location, you may want to specify the ANY location, which already exists in the database, for those transportation resources (all resources whose Type is 5).

Loc_Type Identifies the location type.

• 1: 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.

• 2: Plant

Location at which SKUs are manufactured. SKUs that are input to, or output from, Make processes must be at plant locations. Plant locations cannot also be suppliers or customers. A plant can be the destination location of a Move process from a supplier. It can also be the source or destination of a Move process to/from a DC or another plant.

• 3: 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. DC locations cannot also be suppliers or customers.

• 4: Plant and DC

A location that is both a plant and a DC.


Loc

• 5: Customer

A location where a customer receives products from a location in your supply chain. Customer locations cannot also be another type of location. A customer can be the destination location of a Move process from a plant or DC.

• 6: Store

A location where various products are available for sale to the customer.

You can define additional location types in the LocType table.

Lon The location’s longitude on the geographic map. The valid values are -180 to +180.

OHPost The last time current on hand was posted for this location. Typically, you set this value after importing SKU:OH. You can set OHPost at the SKU level, using SKU:OHPost. If there is no value in SKU:OHPost, the system uses Loc:OHPost (on page 224).

Fulfillment OHPost is used as the default beginning date for a number of durations and processes, including:

• SKUPlanningParam:PlanLeadTime

• SKUPlanningParam:DRPTimeFenceDur

• SKUPlanningParam:MPSTimeFenceDur

• Calculate Plan process

• Forecast consumption

Master Planning, ESP (Deep Tree) Loc:OHPost (on page 224) is used as the default beginning date for:


• Calculate Master Plan process

• Stockorder Generation process

If the Loc:OHPost and SKU:OHPost are blank, the Plan Start Date (as specified on the corresponding process properties page) is used to compute the plan (using the greater of the dates).

IPO If SKU:OHPost is blank, IPO uses this column as the start date when running the Calculate Mean Daily Demand process and when using the replenishment plan cost model. If both Loc:OHPost and SKU:OHPost are blank, the Plan Start Date (as specified on the corresponding process properties page) is used to compute the plan (using the greater of the dates).

PostalCode ZIP code is used to identify a location in a country. Based on Zip code and Country code the latitude and longitude information is retrieved from Centroid table.

SeqIntExportDur When you run the Transfer Planned Orders to Sequencing process, the Master Planning Plan Orders (PlanOrder) whose PlanOrder:SchedDate falls within the export duration, which starts from Loc:OHPost until the Sequencing Integration Export Duration, will be exported to JDA Sequencing application.

Note: The plan orders of only those SKUs whose SKU:SeqIntEnableSw is enabled will be exported.

SeqIntImportDur


Loc

When you run the Import Scheduled Receipts from Sequencing process, the schedule receipts of JDA Sequencing application, whose start date and end date falls within the import duration, which starts from Loc:OHPost until the Sequencing Integration Import Duration, are imported to JDA Master Planning.

SeqIntLastExportedToSeq The Sequencing Integration Last Exported To Sequencing shows the last date/time when the Master Planning plan orders were exported to JDA Sequencing application.

SeqIntLastImportedFromSeq The Sequencing Last Imported From Sequencing shows the last date/time when the Schedule Receipts of JDA Sequencing where last imported into JDA Master Planning.

SourceCal Not used in this release.

Type3 Note: This column is not used in the current release.

Identifies the type of location.

• 1: GEMMS plant (manufacturing facility). SKU projection data is exported only for locations that are GEMMS plants.

• 2: Distribution center/warehouse

• 3: VMI location

VendID This column is required for integration with external applications.

WDDArea A unique identifier of an area which is impacted by weather.

WorkingCal The working calendar (Cal: Type 11) associated with this location.


LocType

LocType Table included with: Production and Sourcing Optimization, Flowcasting


Is_Default PSO, Flowcasting

INTEGER 0

Type 1 PSO, Flowcasting

INTEGER

Table description Each row in this table defines a location type.

Column descriptions Is_Default Indicates the default location type. Only one location type should be set to default.

Type The location type. The predefined location types include:

• 1: Supplier

• 2: Plant

• 3: DC

• 4: Plant and DC

• 5: Customer

• 6: Store

You can create additional location types using the Flexible Editor. Loc types are used only for display purpose at UI level, it is not an input to Production and Sourcing Optimization Optimizer.


Map

Map Table included with: Demand,Demand Decomposition, Flowcasting


Descr Dmd, Dmd Decomp, Flowcasting

TEXT ' '

LastMove Dmd, Dmd Decomp, Flowcasting


Map 1 Dmd, Dmd Decomp, Flowcasting

TEXT

Table description Each row in this table identifies a map, which you can use to map data from one DFUModel to another. In JDA Demand, the Forecast Reconciliation and Map DFUs functions use the maps defined in this table.

You can use the same map for many different DFUModels. Use the DFUMap table to identify the DFUModels that this map applies to.

Column descriptions Descr Optional description of the map defined in this row.

LastMove The most recent date/time when the system used this map to change data.

Map The map defined in this row. Up to 50 characters.


Mask

Mask Table included with: Demand, Demand Decomposition, Markdown Optimization, Promotions Management, Flowcasting


Description Dmd, Dmd Decomp, MDO, PM, Flowcasting

TEXT ' '

Mask 1 Dmd, Dmd Decomp, MDO, PM, Flowcasting

TEXT

Table description Each row in this table represents a mask, which is used for several different purposes.

Demand A mask causes the Calculate Model function to ignore specific periods of a DFU's history when fitting a model. Each mask can mask out multiple time periods, which are defined in the MaskData table. To apply a mask to a DFU, specify the mask in the DFU table.

JDA Pricing applications A mask causes a DFU to be unavailable for the Estimate Market Response Model process during a specified time period. To apply a mask, specify its name, along with Eff and Disc dates, in the DFUPriceParam table.

Column descriptions Descr Optional description of this mask.

Mask Identifier of this mask.


MaskData

MaskData Table included with: Demand, Markdown Optimization, Promotions Management, Demand Decomposition, Flowcasting


Dur Dmd, MDO, PM, Dmd Decomp, Flowcasting

DURATION 1440

Mask 1 Dmd, MDO, PM, Dmd Decomp, Flowcasting

TEXT

StartDate 2 Dmd, MDO, PM, Dmd Decomp, Flowcasting

DATE

Table description Each row in this table represents one period in a mask (defined in the Mask table). When the Calculate Model function fits a model for a DFU to which the mask is assigned, it ignores the history for each period in the mask. Masks are assigned to DFUs in the DFU table.Similarly, when the Estimate Market Response Model process is run the history for the masked periods is excluded from the model estimation.

Column descriptions Dur The duration in minutes of the time period whose values are stored in this row.

Mask Identifier of the Mask (defined in the Mask table) whose period is defined in this row.

StartDate The starting date and time of the period defined in this row.


MeanValueAdj

MeanValueAdj Table included with: Demand, Flowcasting


AdjRate Dmd, Flowcasting

DECIMAL 0

AdjVal Dmd, Flowcasting

DECIMAL 0


TEXT ' '


TEXT ' '


TEXT


TEXT

FixInFutureSw Dmd, Flowcasting

BOOLEAN 0


TEXT


TEXT

ModType Dmd, Flowcasting

OPTION_NUMBER

1,2,3 2


DATE

Table description The MeanValueAdj table stores the data associated with mean value adjustments made through the Demand Workbench.

Column descriptions AdjRate Percentage by which the mean value is adjusted.

Valid values for Adjustment Rate are 0 to 1.

AdjVal The value by which the mean is adjusted if ModType is Percent or Incremental Lift. This represents the new mean value if ModType is New Mean Value.

Valid values for Adjustment Value are 0 or greater.

Descr A description of this modification.

DmdCal The demand calendar assigned to the DFU in the DFU table when the mean value adjustment is calculated.


MeanValueAdj

Valid values for Calendar to Generate Model and Forecast are identifiers of a calendar whose Cal:Type is 5.



FixInFutureSw Valid values for Fixed In Future Switch are 0 (No) and 1 (Yes).

If set to 1, indicates the mean value modification represents a fixed value that will not be modified when the Calculate Model process runs. This column only applies to forecast time periods.




ModType Indicates the type of mean value modification.

Valid values for Modification Type are 1 to 3.

• 1: Incremental Lift

• 2: Percent

• 3: New Mean Value

StartDate The beginning of the period covered by the causal factor defined in this row.


Model

Model Table included with: Fulfillment, Demand, Dynamic Demand Response, Promotions Management, Travel Price Optimization, Flowcasting


Algorithm Dmd, Flowcasting INTEGER 1

Descr Dmd, Flowcasting TEXT ' ' HistStream Dmd, Flowcasting TEXT ' '

Model 1 Dmd, Flowcasting TEXT

Table description With Multi-Model Framework (MMF), each DFU can have multiple types of history and forecast data. To identify the history stream and forecast model used for a DFU, create a model to associate with the appropriate DFUs. To associate a model with a DFU, enter the model identifier in DFU:Model.

A model has two components: the history stream (which identifies the type of history, such as point-of-sale or shipment), and the forecast algorithm (such as Fourier, MLR, or Lewandowski). After you populate the HistStream table with the history streams for a database, create a model name to which you will associate the history stream and algorithm. If the model is an imported forecast (such as sales, marketing, or budget), the history stream and algorithm values may remain blank.

Each row in this table is used as an identifier for a specific forecast stream for a DFU. A demand unit, demand group, location, and model identifier make up a DFUModel.

Column descriptions Algorithm Value that indicates which algorithm the Calculate Model process should use for this DFUModel.

Valid values for Algorithm are 0 to 9 (updated by the user).

• 0: None

Use this for imported forecasts. Calculate Model will not change any values for DFUs where Algorithm = None.

• 1: Fourier

• 2: Multiple Linear Regression (MLR)

• 3: Generate Forecast (import MLR coefficients)

• 4: Lewandowski

If you select this option but the database is not configured for Lewandowski, the system generates an exception.

• 5: Holt-Winters

• 6: Croston

• 7: Moving Average

• 8: AVS-Graves

• 9: Short Lifecycle


Model

Note: Because Model is part of the primary key for the DFU table, the following row is added to the Model table during migration to version 6.1 and later:

Model=”DEFAULT-MODEL” and Descr=”Default Model”

To set the defaults for all existing DFUs, the migration utility also sets the following values for this row:

HistStream = “DEFAULT-HIST”

Algorithm = 1 (Fourier)

Descr Description of this history stream.

HistStream The history stream used for the DFUModel by a Calculate Model process.

Valid values for History Stream are identifiers of a history stream and cannot be blank.

Model The model identifier described in this row.


MovingAvgParam

MovingAvgParam Table included with: Demand, Flowcasting



TEXT


TEXT


TEXT


TEXT

NumPerForAvg Dmd, Flowcasting

NUMBER 1


NUMBER 0

ApplyWgtSW Dmd, Flowcasting

NUMBER (1) 0


DECIMAL 2

MovingAvgWgt Dmd, Flowcasting

TEXT “

InitialMeanValue

Dmd, Flowcasting

DECIMAL 0

InitMeanOverrideSw

Dmd, Flowcasting

NUMBER (1) 0

Table description The MovingAvgParam table contains the parameters for setting the Moving Average method.





NumPerForAvg The window size or the number of periods to be used for averaging. Minimum value for window size is 1. If the window size exceeds the minimum value of either periodicity or half the history size, the warning exception (1316) is generated.

SeasonalitySW


MovingAvgParam

This switch determines whether the model includes adjustments for seasonal influences.




ApplyWgtSW This switch determines whether the model includes weights.

Valid values for Apply Weight Switch are 0 (Off) and 1 (On).

• 0: without weights

• 1: with weights

If you make this switch On, then the weights from MovingAvgWgts:MovingAvgWgt will be applied to window periods.

Note: Weights will be normalized as per the window size before applying.


The system multiplies OutlierFactor by the standard error of the model, then adds the result to and subtracts the result from the model demand value. Outliers are history period values that fall outside the resulting range of reasonable values. DFU:OutlierOpt and DBParam:OutlierOpt determine how Model and Update Model handle outliers.


Valid values for OutlierFactor are greater than or equal to 2.

Note: System will set DBParam:OutlierOpt = 1 to 2 internally since Moving Average does not support mask.

MovingAvgWgt The name of the moving average weight profile.

InitialMeanValue If there is no history or short history and InitialMeanOverrideSw = 1 (Manual), then the Initial Mean Value must be specified.

During the process of introducing NewDFUs through the New DFU Introduction functionality, the old DFU’s MovingAvgStats:LastMean (on page 237) is copied to the MovingAvgParam:InitialMeanValue of the new DFU.

InitMeanOverrideSw This switch determines whether the initial mean values are overridden.

Valid values for Initial Mean Override Switch are 0 (Automatic) and 1 (Manual):

• 0: Let the system automatically calculate the initial mean value for the model.

• 1: Manually set the initial mean value.


MovingAvgStats

MovingAvgStats Table included with: Demand, Flowcasting



TEXT


TEXT


TEXT


TEXT


DECIMAL 0


DECIMAL 0.0

SE Dmd, Flowcasting

DECIMAL 0

CoefVariation Dmd, Flowcasting

DECIMAL 0

LastMean Dmd DECIMAL 0.0 SymmetricMAPE Dmd,

Flowcasting DECIMAL 0.0

Table description An output table that stores values generated during a Simple Moving Average forecast.

Note: If a DFU has an attached moving event, only Mean, MSE, SE, and SymmetricMAPE will be published.







MovingAvgStats

where N= number of history points


Notes:

• The first window size period will not be taking into account in the MSE calculation since history equals fittedhist.

• All the DFUs associated with calendar and has weights, the stats should be calculated based on the weights.






CoefVariation The coefficient of variation which can be calculated using the formula:

where

• Mean = Average of raw history

• n = Number of posted history periods

LastMean LastMean is the first deseasonalized forecast (if seasonality profile is attached) found by the Calculate Model process. During the process of introducing NewDFUs through the New DFU Introduction functionality, the old DFU’s MovingAvgStats:LastMean is copied to the MovingAvgParam:InitialMeanValue (on page 235) of the new DFU.

SymmetricMAPE Symmetric Mean Absolute Percent Error (Symmetric MAPE) compares the fitted history values (statistically generated forecast in the past) with the actual history for the entire duration of history. Only base history (total history minus history overrides) is used if the Calculate Model process is run with Base History. Total history is used if the Calculate Model process is run with Total History.

Note: If Symmetric MAPE = zero, and DFU:NPISw (on page 67) is enabled, it can be concluded that the DFU is new and does not yet have enough history for the model fit statistics to be valid. The statistical value will not be meaningful until the DFU reaches the Independence Date.


MovingAvgWgts

MovingAvgWgts Table included with: Demand


MovingAvgWgt 1 Dmd TEXT

Period 2 Dmd INTEGER 0 Value Dmd DECIMAL “

Table description The MovingAvgWgts table contains the profiles of the moving average weights. The weight profile name is assigned to the DFU in the MovingAvgParam:MovingAvgWgt (on page 235) column. Weighted Moving Average (WMA) for a moving average window size “p” and (t+1)th time period is given by the equation below:

where,

P = window size

i = time index

wi= weight

Qi = Posted history

(t+1) = Demand post date

For example, consider the window size as 4, the weighted profile will have the following to use with that window:

Window Size Period Weight Normalized weight

Posted History

4 1 4 0.8 400

4 2 6 1.2 300 4 3 3 0.6 200 4 4 7 1.4 600 The weightage moving average will be = 410

If the window size is greater than the no. of periods of the weighted profile, then the remaining periods weights will be considered equal to 1. For example, if the window size is 4 and the no. of periods for weighted profile are 3, then the 4th periods weight will be considered as 1.

If the window size is greater than minimum value of either half the history size or periodicity, calc model throws exception 1311. JDA Demand Management Foundation Reference Guide 238 © 1997 - 2014 JDA Software Group, Inc.- Confidential

MovingAvgWgts

Column descriptions MovingAvgWgt The name of the moving average weight profile.

Period The number of the period to which the data in this table applies. For example, 1 is the first period of the year, 2 the next, and so on. If the calendar is monthly then 1 corresponds with January. If the calendar is weekly then these are week numbers.

Value Input weight for the corresponding period in window.


MovingEvent

MovingEvent Table included with: Demand, Flowcasting, Fulfillment



TEXT


UPPER_TEXT

NumPeriods Dmd, Flowcasting

INTEGER 0

Table description The MovingEvent table stores the identifiers which make up a moving event.

Column descriptions MovingEvent The name of the event. This Moving Event must already exist in the MovingEvent table.

Descr The description for the event.

NumPeriods The number of periods in which the impact of the event is present. For example, consider Easter as a moving event. The impact of Easter does not only present in the week of Easter, but it occurs for two weeks before and one week after it. Therefore in this case, the NumPeriods would be 4.


MovingEventData

MovingEventData Table included with: Demand, Fulfillment, Flowcasting



TEXT

Year 2 Dmd, Flowcasting

INTEGER 1970


DATE 01/01/1970

Table description The MovingEventData table stores data for every event stored into the MovingEvent (on page 240) table.

Column descriptions MovingEvent The name of the event. This column entry refers to the MovingEvent (on page 240) column of the MovingEvent (on page 240) table.

Year The year in which the event occurs. The default value for Year is 1970.

StartDate The date from which the event impact starts.


NPISequence

NPISequence Table included with: Demand, Flowcasting


SequenceName 1 Dmd, Flowcasting

TEXT


TEXT

Table description The NPISequence table stores sequences and their descriptions. A sequence is a collection of searches which are used while creating new DFUs through the NPI By Sequence process.

Note: You must manually populate the NPISequence table for sequence data, the NPISequenceDetail (on page 243) table for sequence and parameters data, and the NPIValidDFU (on page 245) table for valid DFU data.

Column descriptions SequenceName The name of the sequence.

Descr The description of the sequence.


NPISequenceDetail

NPISequenceDetail Table included with: Demand, Flowcasting


SequenceName 1 Dmd, Flowcasting

TEXT

Search Dmd, Flowcasting

TEXT

NPIMeanSmooth Dmd, Flowcasting

DECIMAL 0.5

NPIScalingFactor Dmd, Flowcasting

DECIMAL 1

NPITrendSmooth Dmd, Flowcasting

DECIMAL 0

NPIIndDate Dmd, Flowcasting

DATE

SearchPriority 2 Dmd, Flowcasting

INTEGER 1

SearchScope Dmd, Flowcasting

INTEGER 0, 1, 2 1

ParamOverrideSW

Dmd, Flowcasting

INTEGER 0, 1 1

Table description The NPISequenceDetails table stores sequences, searches, and parameters used while creating new DFUs through the NPI By Sequence process.

Note: You must manually populate this table for sequence and parameters data.

Column descriptions SequenceName The name of the sequence.

Search The name of the search, which is based on the DFUMaintCopyDFU (on page 112) table and is used to filter FromDFUs and ToDFUs. The search is considered invalid if it is not a static search or the user does not have the permission to use the search. If the search is invalid, the process stops and an error message is displayed as the Invalid Sequence: sequence_name, on the process jobstatus pop-up window while running the process through user interface or in the log file while running the process through batch. This error message is not displayed in the Invalid Entry Row field.

NPIMeanSmooth The mean smoothing parameter used during the process of creating New DFUs through the NPI By Sequence process. Valid values range between 0.0 and 1.0. The default value is 0.5.

NPIScalingFactor The scaling factor used during the process of creating New DFUs through the NPI By Sequence process. Scaling factor can be any positive number. The default value is 1.

NPITrendSmooth JDA Demand Management Foundation Reference Guide 243 © 1997 - 2014 JDA Software Group, Inc.- Confidential

NPISequenceDetail

The trend smoothing parameter used during the process of creating New DFUs through the NPI By Sequence process. Valid values range between 0.0 and 1.0. The default value is 0.

NPIIndDate The date from which the new DFU, created using the NPI By Sequence process, becomes independent and can forecast based on its own history.

SearchPriority Defines the order in which searches in the sequence are run in the NPI By Sequence process.

SearchScope Defines the scope for the search indicating whether the search is Publish To, Public or Private.

Valid values for SearchScope are:

• 0 - Publish To

• 1 - Public

• 2 - Private

ParamOverrideSW Switch indicating whether to use the existing Mean Smoothing, Trend Smoothing, Scaling Factor, and Independent Date parameter values from the DFUMaintCopyDFU table or override them with the values specified in the NPISequenceDetails table.

The default value is 1, which is used to override the values with the values specified in the NPISequenceDetails table.


NPIValidDFU

NPIValidDFU Table included with: Demand, Flowcasting



TEXT


TEXT


TEXT

Table description Use this table to identify the valid DFUs that can be created by the NPI By Priority process. For example, when a store is opened at a new location, only certain products may be transported to that location. While identifying a similar location to model the DFU mix for the new location, this table is used to store the valid products that should be transported at the new store. The NPI By Priority process generates only those new DFUs for the new location that match the validity stored in this table.

Note: You must manually populate this table for valid DFUs data.

Column descriptions DmdUnit The demand unit associated with the new DFU.

DmdGroup The demand group associated with the new DFU.

Loc The location associated with the new DFU.


PriceProfile

PriceProfile Table included with: Demand, Flowcasting


BaseCurrency Dmd, Flowcasting

TEXT ' '

PriceProfileName

1 Dmd, Flowcasting

TEXT

Table description This table is used to store pricing profiles for currency conversion. This table is used with the PriceProfileVal tables to allow you to view data by revenue, if you are using Time Phase Conversion factors.

Column descriptions BaseCurrency The currency identifier for the base currency, such as USD, Euros, Yen. This currency must be defined in the Currency table.

PriceProfileName The name for the price profile.


PriceProfileVal

PriceProfileVal Table included with: Demand, Flowcasting



EndDate Dmd, Flowcasting


PriceProfileName 1 Dmd, Flowcasting

TEXT


DATE

Value Dmd, Flowcasting

DECIMAL 0.0

Table description This table is used to store price profile values for currency conversion. This table is used with the PriceProfile tables to allow you to view data by revenue, if you are using Time Phased Conversion factors.


PriceProfileName StartDate EndDate Value

USD 1/1/03 2/1/03 1.1

USD 2/1/03 3/1/03 1.25

USD 3/1/03 4/1/04 1.15

Column descriptions EndDate The date that the price was no longer in effect.

PriceProfileName The name for the price profile.

StartDate The date the price was effective.

Value Price for the given time period in units of the base currency type. Zero is a valid value; however, values cannot be negative numbers.


Profile

Profile Table included with: Demand, Flowcasting


Descr Dmd, Flowcasting TEXT ' '

NumInt Dmd, Flowcasting INTEGER 0 Profile 1 Dmd, Flowcasting TEXT

Table description Each row in this table defines a profile—a set of time intervals and factors that expresses the anticipated behavior of an event. The Profile table defines the profile and the total number of intervals it contains. The ProfileData table stores interval data for the profiles defined in this table. When you work with events in an Event Manager userview, the system uses the profile you specify to spread event demand through time. You can use a Profile Manager userview to easily add, change, and delete profiles.

Note: The Event Manager feature is no longer supported by JDA Demand. It is now supported by JDA Market Manager. Data stored in this table is transferred to Market Manager during Market Manager/Demand integration.

Column descriptions Descr Description of this profile.

NumInt The number of intervals in the profile.

Valid values for Number of Intervals are 0 or greater.

Profile The profile whose data is found in this row.


ProfileData

ProfileData Table included with: Demand, Flowcasting

Column name

PK Included with


Factor Dmd, Flowcasting

DECIMAL 0

IntNum 2 Dmd, Flowcasting

INTEGER

Profile 1 Dmd, Flowcasting

TEXT

RelativeLen Dmd, Flowcasting

DECIMAL 0

Table description Each row in this table defines data for one interval associated with a profile.

Note: The Event Manager feature is no longer supported by JDA Demand. It is now supported by JDA Market Manager. Data stored in this table is transferred to Market Manager during Market Manager/Demand integration.

Column descriptions Factor Fraction of demand in this interval.

IntNum Valid values for Interval Number are 0 or greater.

Profile The profile whose data is found in this row.

RelativeLen Fraction of total duration in this interval. For example, if there are 10 intervals of equal length, .1 is the RelativeLen for each interval.


SeasonError

SeasonError Table included with: Fulfillment, Demand, Master Planning, Flowcasting, Enterprise Supply Planning


DmdGroup 2 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT

DmdUnit 1 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT

Dur FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

DURATION 0

Factor FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

DECIMAL 0.0

Loc 3 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT

Model FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT ' '

PerNum FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

INTEGER 0

StartDate 4 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

DATETIME

Table description Each row in this table defines the seasonality factor (SeasonError:Factor (on page 251)) for a particular DFU. The seasonality factor is used to weight statistical safety stock by period according to seasonal patterns of demand.

Column descriptions DmdGroup The demand group associated with the DFU whose seasonality factor is defined in this row.

DmdUnit The demand unit associated with the DFU whose seasonality factor is defined in this row.

Dur


SeasonError

The length of the time interval that starts at StartDate.

Factor The value resulting from the calculation of seasonality of forecast error associated with this DFU.

Loc The location associated with the DFU whose seasonality factor is defined in this row.

Model The model used by the Calculate Model process to identify the history stream and algorithm that is associated with the selected DFU.

PerNum The number of the period for which the seasonality factor is being calculated.

StartDate The starting point of the time interval associated with the DFU defined in this row.


SeasonLib

SeasonLib Table included with: Demand, Flowcasting


LibName 1 Dmd, Flowcasting

TEXT


TEXT

Table description The SeasonLib table stores the library and description for this library. Seasonality profiles are stored in the library.

Column descriptions LibName Name of the library.

Descr Description for the library.


SeasonProfile

SeasonProfile Table included with: Demand, Flowcasting



TEXT


TEXT

Periodicity Dmd, Flowcasting

INTEGER 1

LibName Dmd, Flowcasting

TEXT Null

SeasonType Dmd, Flowcasting

INTEGER 1

Year Dmd, Flowcasting

INTEGER 1970

Table description The SeasonProfile table stores the identifiers which make up a seasonality profile. A profile name, periodicity, library and seasonality type make up a complete seasonality profile.

The input values and normalized values are set to the default of 1 for multiplicative models and 0 for additive models.

Column descriptions ProfileName Name of the seasonality profile.

Descr Description for the seasonality profile.

Periodicity The number of periods you want to display for a calender year.

LibName Name of the library you want this profile to be stored in.

SeasonType The default input and normalized values for the seasonality profile are generated depending on the seasonality type. Holt-Winters models exhibits two seasonality types: Multiplicative and Additive. Other models such as Lewandowski, Moving Average, AVS-Graves, and Short Lifecycle which feature seasonality, exhibit only Multiplicative seasonality type.

Calculate Model uses the following formulas to calculate the normalized value:

Multiplicative Type:


SeasonProfile

Additive Type:

Year Year which is used as a reference for shifting the profiles to other years. The default value for year is 1970.


SeasonProfileValues

SeasonProfileValues Table included with: Demand, Flowcasting



TEXT


INTEGER

NormVal Dmd DECIMAL 0 InputVal Dmd,

Flowcasting DECIMAL 0

Table description One of the features of the Lewandowski, Holt-Winters, Moving Average, AVS-Graves, and Short Lifecycle methods is the ability to provide a user-specified starting seasonal profile. The SeasonProfileValues table stores the starting values in the InputVal column. The values you enter may not necessarily add up to the sum of the periodicities (12, 52, and so on). To normalize the values so that the sum of the input values equals the periodicity, the system spreads the input values to equal the correct periodicity total and stores the results in the NormVal column.

The input values and normalized values are set to the default of 1 for multiplicative models and 0 for additive models. You can overwrite the input values to create a new seasonal profile.

Following is a sample seasonality profile for a periodicity of 12.

Period Input Value Normalized Value

1 1 1.00000

2 1 1.00000 3 1 1.00000 4 1 1.00000 5 2 1.00000 6 2 1.00000 7 3 1.00000 8 3 1.00000 9 2 1.00000 10 1 1.00000 11 1 1.00000 12 1 1.00000 Total: 12 Total: 19 When you run the Calculate Model process, the input values are distributed proportionally to equal the periodicity (see below); they are then stored in the NormalizedValue column.

Period Input Value

Normalized Value

1 1 .631579


SeasonProfileValues

Period Input Value

Normalized Value

2 1 .631579 3 1 .631579 4 1 .631579 5 2 1.263158 6 2 1.263158 7 3 1.894737 8 3 1.894737 9 2 1.263158 10 1 .631579 11 1 .631579 12 1 .631579 Total: 12 Total: 19 Total: 12

Column descriptions ProfileName Name of the seasonality profile.

Period The period number against which the Input Value is applied.


InputVal Value you specify for the period’s initial seasonality profile.

NormVal Initial seasonal profile of the model that is generated when the Calculate Model process distributes the input values proportionally so that the sum of the normalized values equals the periodicity. (Periodicity is determined by DFU:DmdCal.) Calculate Model uses the following formulas depending on the Seasonality Type of the profile either Multiplicative or Additive:

Multiplicative Type:

Additive Type:

Note: Starting from version 7.5.1, Calculate Model process does not write out normalized values.


SKU

SKU Table included with: Fulfillment, Master Planning, Supply, Production and Sourcing Optimization, Demand, Inventory Policy Optimization, Dynamic Demand Response, Flowcasting, Enterprise Supply Planning


CreationDate Flowcasting, Dmd DATE TO_DATE('01/01/1970','MM/DD?YYYYY')

CurrencyUOM PSO OPTION_NUMBER

Any value in the UOM:UOM column

0

EnableSw PSO BOOLEAN 1

InfCarryFwdSw PSO BOOLEAN 0 InfiniteSupplySw

PSO BOOLEAN 0

Item 1 FF, MP, Supp, PSO, Dmd, IPO, Flowcasting, ESP

TEXT

ItemStoreGarde

Dmd, FF, Flowcasting

INTEGER -1

Loc 2 FF, MP, Supp, PSO, Dmd, IPO, Flowcasting, ESP

TEXT

LTDGroup PSO TEXT ' '

MinOHCovRule PSO OPTION_NUMBER

1,2 1

MPBatchNum MP, ESP INTEGER 0

NetChgSw FF, Flowcasting BOOLEAN 1 NPITransDur Flowcasting DURATION 0

OH FF, MP, Supp, PSO, IPO, Flowcasting, ESP

DECIMAL 0

OHPost FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

PeggingSw ESP BOOLEAN 0,1 1

PlanLevel FF, MP, Supp, IPO, Flowcasting, ESP

INTEGER -1

QtyUOM PSO OPTION_NUMBER


0


SKU


ReplenMethod FF OPTION_NUMBER

1

ReplenType FF, MP, Supp, Flowcasting, ESP

OPTION_NUMBER

1,2,4,5, 1

RPBatchNum MP, ESP (Deep Tree)

INTEGER 0

SeqIntEnableSw

MP, ESP (Deep Tree)

BOOLEAN 0

SKUGroup ESP (LPOPT) TEXT SourcingGroup PSO TEXT ' ' StorableSw FF, PSO,

Flowcasting, ESP (LPOPT)

BOOLEAN 1

TargetOHCovRule

PSO OPTION_NUMBER

1,2 1

TimeUOM PSO OPTION_NUMBER


0

Table description Each row in this table defines a SKU (identified by item and location).

Column descriptions CreationDate The date on which the SKU is created. This column is updated when the SKU is created using NPI Creation Workflow.

CurrencyUOM The unit of measure applied to all currency values associated with the SKU.

EnableSw Indicates if the SKU will be used while running the Production and Sourcing Optimization Optimizer. If set to false, the SKU will be ignored in building the model, along with any processes for which it is an input or output.

InfCarryFwdSw Indicates if the independent demand not met in one period will be carried forward to future periods.

If you enable the option to carry forward unmet demand for a SKU, then demand not met in one period is carried forward to future periods and a penalty (Independent Demand penalty, see PenaltyCategory:Category) is incurred for every day that the demand is met late.

If this option is enabled and the Independent Demand constraint is set to hard, then it means that the demand will have to be met in some period in the model (it can be met late but it has to be met). If the Independent Demand constraint is set to soft, then you may not meet some independent demand in the model. In both hard or soft setting, the late demand incurs a penalty for every day that it is met late.


SKU

The following example illustrates the demand calculations. Consider a SKU with the independent demands and supplies, as shown. If the carry forward unmet demand option is enabled, then the demand calculations are as shown:

SKU Week 1

Week 2

Week 3 Week 4 Week 5 Week 6

Independent demand 100 95 105 50 80 150

Total supplies 90 90 90 90 (10 pre-build for week 6)

90 (10 pre-build for week 6)

90

Unmet independent demand from previous periods

0 10 15 30 0 0

Met demand 90 90 90 80 80 110

Unmet demand (not considered because carry forward is enabled)

0 0 0 0 0 0

Late demand 10 15 30 0 0 40

Met late penalty/unit/day

10 10 10 10 10 10

Unmet demand penalty/unit (not considered because carry forward is enabled)

10 10 10 10 10 10

Met late demand penalty incurred (penalty*number of days*number of units)

10*7*10 = 700

10*7*15 = 1050

10*7*30 = 2100

10*7*0 = 0

10*7*0 = 0

10*7*40 = 2800

Unmet demand penalty (not incurred because carry forward is enabled)

0 0 0 0 0 0

In this case, even if you set independent demand as a hard constraint, a met late penalty will be incurred. This is different from all other constraints, where penalties are not incurred when the constraint is set to hard.

If the carry forward unmet demand option is not enabled, then the demand calculations are as shown:

SKU Week 1

Week 2


Independent demand 100 95 105 50 80 150

Total supplies 90 90 90 90 (10 pre-build for week 6)

90 (10 pre-build for week 6)

90


SKU

SKU Week 1

Week 2


Unmet independent demand from previous periods (not relevant because demand is not carried forward)

0 0 0 0 0 0

Met demand 90 90 90 80 80 110

Unmet demand 10 5 15 0 0 40 Late demand (not considered because carry forward is not enabled)

0 0 0 0 0 0

Met late penalty/unit/day (not considered because carry forward is not enabled)

10 10 10 10 10 10

Unmet demand penalty/unit

10 10 10 10 10 10

Met late demand penalty (not incurred because carry forward is not enabled)

0 0 0 0 0 0

Unmet demand penalty incurred (penalty*number of units)

10*10 = 100

10*5 = 50

10*15 = 150

10*0 = 0 10*0 = 0 10*40 = 40

InfiniteSupplySw Indicates if the SKU is an infinite supply SKU. The default value is false.

If a SKU has no upstream processes and the InfiniteSupplySw is true, the Optimizer assumes the SKU has infinite supply. However, if the SKU is produced or sourced by any process, the Optimizer will assume there is no infinite supply, irrespective of the setting of the switch.

Item The item associated with the SKU defined in this row. Must be a valid item in the Item table.

ItemStoreGrade Grade assigned to the SKU based on Average Sales.

Loc The location associated with the SKU defined in this row. Must be a valid location in the Loc table.

LTDGroup The name of the lead time delivery constraint group this SKU belongs to.

Note: This column is used by the Lead Time Delivery Constraint feature, which is not included in the 7.2.2.0 release.

MinOHCovRule JDA Demand Management Foundation Reference Guide 260 © 1997 - 2014 JDA Software Group, Inc.- Confidential

SKU

Indicates if the safety stock is based on forward coverage of independent demand or sum of independent and dependent demand (total demand).

• 1: Total demand

• 2: Independent demand

The MinOHCovRule option is applicable only if you specify the Safety Stock constraint in terms of a time unit of measure (see ConstraintCategory:Category). If the Safety Stock constraint is specified as a quantity, the MinOHCovRule option is ignored.

The following example illustrates the safety stock calculations. Consider a SKU with the independent and dependent demands as shown: Consider the forward coverage duration is set as 5 days. In this case, the safety stock calculations are as shown for the different coverage rules:

SKU Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Week 2

Independent demand

10 30 20 25 30 50 20 150

Dependent demand

50 40 50 30 60 45 55 350

Total demand

60 70 70 55 90 95 75 500

SKU Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Week 2

Safety stock based on independent demand

155 145 146.43

142.86

134.29

105.71

107.14

0

Safety stock based on total demand

380 385 386.43

402.86

384.29

260.71

357.14

0

The safety stock level for Day 1 is calculated based on the demands on Days 2 - 6. Similarly for Day 2, it is calculated based on demands on Days 3 - 7. However, if the forward coverage days do not exactly coincide with the bucketed duration then the safety stock levels are prorated. For example, for Day 4, the safety stock level is calculated based on demands on Days 5 - 9. In this case, the independent demand for each bucket is calculated as follows:

Day 5 = 30

Day 6 = 50

Day 7 = 20

Day 8 = 21.43 (150/7 equal distribution across the bucket)

Day 9 = 21.43

The total safety stock for Day 4 based on independent demand = 142.86

Note: The forward coverage duration need not be greater than the planning bucket. For example, you can have a forward coverage of 5 days and monthly planning buckets. Production and Sourcing Optimization will prorate and calculate the safety stock levels accordingly.

The safety stock calculation for total demand would be similar to independent demand except that the calculations are based on the sum of independent and dependent demand. JDA Demand Management Foundation Reference Guide 261 © 1997 - 2014 JDA Software Group, Inc.- Confidential

SKU

MPBatchNum Indicates the batch numbers for the SKUs that are calculated using Calculate Master Plan process.

Calculate Master Plan process groups all related SKUs into a batch and assigns a batch number to the SKUs in the ProcessSKU table. Once the search related SKUs are populated into the ProcessSKU table with the batch number, the Calculate Master Plan process updates this column which stores the batch number of each SKU. Once the batch numbers are calculated for the SKUs that are part of the search, the same batch numbers can be used for subsequent Calculate Master Plan run with the new option un-checked.

Generate Supply and Demand Links & Generate Supply and Demand links based on priority use SKU:MPBatchNum to load demands and supplies for pegging.

The default value for SKU:MPBatchNum is 0, and if the batch number is not calculated even once for the SKUs, you will find that the processes will run for all SKUs even if you select a search.

NetChgSw Note: This value is updated by user interface edits, processes, batch updates and interface-generated program updates from the SQL loader. Do not change these values.

• No/Blank: Plan related values for this item have not changed

• Yes: Plan related values for this item have changed

If this switch is set to Yes, plan-related values for this item have been changed. The next time you open a Calculate Plan process for this SKU, the system will recalculate its plan, if the Calculate Plan process property “Respect Netchange Switch” is checked. If that property is not checked then all selected SKUs are processed by Calculate Plan and the value of NetChgSw does not have any impact on Plan logic.

When a change is made that may affect a SKU's plan, the system flags that SKU by setting its SKU:NetChgSw to Yes. A change to any of the following columns causes a SKU to be flagged for Plan:

• AllocStrat: AllocStratID, DmdSubType, DmdType, Priority

• BOM: Disc, DrawQty, Eff, Offset (if the SKU is a subordinate in the BOM)

• CalData: Opt or Repeat (if the SKU has an ArrivCal, AllocCal, ProdCal, or RecShipCal); AllocWgt (if the SKU has an AllocCal)

• CustOrder: FcstSw, Item, Loc, Qty, ShipDate, Status,

• Inventory: ExpDate, PrimaryItem, FirmSw, Qty, (flags all SKUs related to inventory)

• Item: PerishableSw, RestrictPlanMode (flags all SKUs for the item)

• Loc: FrzStart, OHPost (flags all SKUs at the location)

• Network: LoadTime, TransLeadTime (all destination SKUs are flagged)

• PlanArriv: ExpDate, Qty, TransMode (flags source and destination SKUs)

• PlanArriv: (if the SKU is the source) Source, SchedShipDate

• PlanArriv: (if the SKU is the destination) Item, Dest, FirmPlanSw, SchedArrivDate

• PlanOrder: Qty, FirmPlanSw, SchedDate

• SchedRcpts: ExpDate, Qty, SchedDate

• SKU: OH, OHPost, ReplenType

• SKUDemandParam: AllocCal, CustOrderDur, DmdRedID, FcstAdjRule

• SKUDeploymentParam: AllocStratID, LocPriority, PushOpt, StockAvailDur

• SKUExternalFcst: Begin, Dur, Qty


SKU

• SKUPerishableParam: MaxWasteFactor, ShelfLifeDur, ShelfLifeGroup

• SKUPlanningParam: DepDmdOpt, DRPCovDur, DRPFrzDur, DRPRule, DRPTimeFenceDate, DRPTimeFenceDur, ExpDate, ExternalSKUSw, IncDRPQty, IncMPSQty, LastFrzStart, LastPlanStart, MaxOH, MfgFrzDur, MfgLeadTime, MinDRPQty, MinMPSQty, MPSCovDur, MPSRule, MPSTimeFenceDate, MPSTimeFenceDur, PlanDur, PlanLeadTime, PlanLeadTimeRule, ProdCal

• SKUSafetyStockParam: MaxSS, MinSS, SSCov, SSRule, StatSSCSL

• Sourcing: ArrivCal, Factor, TransMode (flags source and destination SKUs)

• SS: Eff, Qty

• VehicleLoad: (if the SKU is the source of the changed load) Source, SourceStatus, ShipDate

• VehicleLoad: (if the SKU is the destination of the changed load) Dest, DestStatus, ArrivDate

• VehicleLoadLine: Item; Qty (if the SKU is the destination of the load)

NPITransDur The number of days for which a new product is in transition phase.

OH The quantity of this SKU in inventory as of SKU:OHPost (if it has a value) or Loc:OHPost.

Supply Using the options on the Calculate Supply Plan process page, you can specify whether to use on hand values from the SKU or the Inventory tables. If you select the SKU table, the value stored in this column is used as supply.

IPO This quantity can be used as the initial stock level for optimizing the inventory level in the Optimize Inventory Policy process.

Fulfillment If the SKU is perishable (Item:PerishableSw = Y) then this field is not read by Fulfillment logic.

ESP If the SKU is perishable (Item:PerishableSw = Y), this field is not read by the ESP solvers.

OHPost The last time Current On Hand was posted for this SKU. The initial value is 01/01/1970 (EPOCH). Typically, you set this value after importing SKU:OH. You can set OHPost at the SKU level, using SKU:OHPost.

Fulfillment SKU:OHPost is used as the default beginning date for a number of durations and processes, including:

• SKUPlanningParam:PlanLeadTime

• SKUPlanningParam:DRPTimeFenceDur

• SKUPlanningParam:MPSTimeFenceDur

• Calculate Plan process

With the Calculate Plan process, SKU:OHPost enables you to recalculate the replenishment plan for selected SKUs, rather than for all SKUs at a location, based on changes to the date when on hand was posted. If you change the value in SKU:OHPost, the system sets the value in SKU:NetChgSw to Yes. The next time you open a Calculate Plan process with this SKU selected, the system will recalculate the replenishment plan for the SKU. If you do not want to do this, leave SKU:OHPost blank; use Loc:OHPost instead, to set a new date for all SKUs at the location.

IPO


SKU

IPO uses this column as the start date when running the Calculate Mean Daily Demand process and when using the replenishment plan cost model. If this column is blank, the value in Loc:OHPost is used. If both Loc:OHPost and SKU:OHPost are blank, the Plan Start Date (as specified on the corresponding process properties page) is used to compute the plan (using the greater of the dates).

Master Planning, ESP SKU:OHPost is used as the default beginning date for:


• Calculate Master Plan process

If the Loc:OHPost and SKU:OHPost are blank, the Plan Start Date (as specified on the corresponding process properties page) is used to compute the plan (using the greater of the dates).

Production and Sourcing Optimization Production and Sourcing Optimization uses this column as the default beginning date for the following plan analysis attributes:

• Beginning On Hand

• Optimal On Hand

• OptimalOHInTime

Example:

Consider that item1 is present at loc1 with SKU:StorableSw selected. Then, independent demand (units) for item1 at loc1 for four months is as follows:

Duration (in months)

Independent demand

01/01 10

02/01 10 03/01 10 04/01 10 If SKU:OHPost (on page 263)= 02/01, SKU:OH =11 units and Scheduled Receipts Constraint=25 units on 01/01, then beginning OH(units) is calculated as follows:

Duration (in months)

Independent demand

01/01 0

02/01 26 03/01 16 04/01 6 The OH on 01/01 is 0 since the OHPost starts on 02/01. On 02/01, OH=26 units as 25-10=15 units. This is a carry forward inventory for Item1 and 11 units (input OH) are added to this to make it 26 units.

On 03/01 OH=16 as 10 units out of 26 units are utilized to meet the independent demand in the second time bucket.

On 04/01 OH=6 units as 10 units out of 16 units are utilized to meet the independent demand in the third time bucket.


SKU

PeggingSw Pegging switch indicates if pegging data for the SKU must be exported to the IndDmdLink and OrderLink tables.

PlanLevel Defines the level at which this SKU relates to other SKUs in the same item family. The value in this column is calculated by the Level SKU process and specifies the order in which the SKUs within the item are processed by Calculate Plan logic. The default value of -1 indicates that the Level SKU process has not yet been run or that there was an error condition related to this SKU when the process was run.

QtyUOM The unit of measure applied to all quantity values associated with the SKU.

Note: Production and Sourcing Optimization ignores SKUs whose quantity UOMs are not set (zero).

ReplenMethod The replenishment method column identifies if this SKU is eligible to receive allocation, replenishment or both allocation and replenishment. This column categorizes an item in following methods:

• Replenished only

These items are only replenished and never go through allocation cycle. These products are never processed in Dynamic Allocation.

For a destination SKU, Calculate Plan considers this SKU to be eligible to receive incoming RecArriv and RecShip. For a source SKU, Calculate Plan considers this SKU to be eligible to push outgoing RecArriv and RecShip.

Note: SKU related to replenished never receive SKUProjStatic:RecAllocArriv and SKUProjStatic:RecallocShip

• Allocated only

These items are only allocated and never go through replenishment cycle. These products are processed only in Dynamic Allocation and never processed in Calculate Plan.

For a destination SKU, Dynamic Allocation considers this SKU to be eligible to receive incoming RecAllocArriv and RecAllocShip. For a source SKU, Calculate Plan considers this SKU to be eligible to push outgoing RecAllocArriv and RecAllocShip.

Note: SKU related to Allocated never receive RecArriv and RecShip

• Replenished and Allocated

These items are processed through both replenishment and allocation cycle at some time in their life cycle.

Note: SKU related to replenished and allocated is eligible to receives RecArriv, RecShip, RecAllocArriv and RecAllocShip.

ReplenType Indicates how Calculate Plan, Calculate Supply Plan and Calculate Master Plan create replenishment plans for this SKU. The valid values are 1, 2, 4, 5, and 6. Calculate Plan works with ReplenType 1, 2, and 4. Master Planning works with ReplenTypes 4 and 5. Supply uses Replen type 1, 2, and 6.

• 1: Transferred items

Fulfillment Calculate Plan creates planned arrivals (stored in the PlanArriv table) to replenish the inventory of this SKU.

Supply


SKU

A value of 1 indicates that the SKU is a transferred SKU. Using the SOURCING table, you can define the source (Sourcing:Source) and destination (Sourcing:Dest) locations, and the fixed lead time (Sourcing:SupplyLeadTime) associated with a transferred SKU.

• 2: Assembled items

Fulfillment Calculate Plan creates planned orders (stored in the PlanOrder table) to replenish the inventory of this SKU.

Supply A value of 2 indicates that the SKU is a assembled SKU. Using the ProductionMethod and ProductionStep tables, you can define the parameters associated with an assembled SKU. Use the SKUSupplyParam table to define the lead times associated with an assembled SKU.

• 4: Interface SKU between Calculate Plan and Master Planning

Plan creates dependent demand orders for this SKU, based on demand for other SKUs.

Master Planning creates supply orders to meet that demand.

• 5: Master Planning SKU

Master Planning plans both demand and supply for this SKU.

RPBatchNum The batch numbers for the SKUs that are calculated using the Calculate Requirement Plan process.

SeqIntEnableSw The Sequencing Integration Enable Switch indicates whether the plan orders for the SKU should sent to JDA Sequencing when you run the Transfer Planned Orders to Sequencing process.

SKUGroup The group to which this SKU belongs.

ESP (LPOPT) When using the LPOPT solver, if you specify a SKU group name as the qualifier for an objective, the objective is applied to all SKUs in the specified group

SourcingGroup The name of the sourcing group this SKU belongs to.

StorableSw Indicates if the SKU is storable.

Fulfillment If StorableSw is set to zero, then the SKU is considered a Flow Through SKU and recommended shipments logic will create recommended shipments of all supply at the SKU exactly on the supply available date. To support this logic, Calculate Plan will schedule all planned arrivals to arrive at the Flow Through SKU on dates that are included in the Recommended Shipments Calendar (SKUDeploymentParam:RecShipCal). Calculate Plan will also determine as each planned arrival is calculated, which destinations will be able to receive shipments that would be shipped immediately based on that planned arrival, and considers only the demands at those destinations in the planned arrival quantity calculations. In addition, all local demands, safety stock, supplemental orders and display quantities on the Flow Through SKU will be disregarded by planning and deployment logic; only distribution demands will be considered in the plan. Only a DRP SKU (SKU:ReplenType = 1) is eligible to be planned as a Flow Through SKU.

TargetOHCovRule Indicates if the target on hand is based on forward coverage of independent demand or sum of independent and dependent demand.

• 1: Total demand JDA Demand Management Foundation Reference Guide 266 © 1997 - 2014 JDA Software Group, Inc.- Confidential

SKU

• 2: Independent demand

The TargetOHCovRule option is applicable only if you specify the Target On-hand constraint in terms of a time unit of measure (see ConstraintCategory:Category) If the Target On-hand constraint is specified as a quantity, the TargetOHCovRule option is ignored.

The target on-hand calculations are similar to safety stock calculations. See SKU:MinOHCovRule (on page 260) for details.

TimeUOM The unit of measure applied to all time values associated with the SKU.


SLCCurve

SLCCurve Table included with: Demand, Flowcasting


CurveID 1 Dmd, Flowcasting

UPPER_TEXT

MarketSize Dmd, Flowcasting

DECIMAL

InternalInfluenceCoef

Dmd, Flowcasting

DECIMAL

ExternalInfluenceCoef

Dmd, Flowcasting

DECIMAL

PctError Dmd, Flowcasting

DECIMAL

Table description The SLCCurve table defines the curve and its coefficients generated from the Build Short Lifecycle Curve process.

Column descriptions CurveID The system generated identifier for a given curve.

MarketSize The total number of consumers who can adopt the new product.

InternalInfluenceCoef The coefficient of imitation. It defines the possibility about the number of consumers who start using the product due to the ‘word-of-mouth’ effect or internal factors.

ExternalInfluenceCoef The coefficient of innovation. It defines the possibility about the number of consumers who start using the product due to an advertising effect or external factors.

PctError The percentage error for curve coefficients.


SLCCurveAttrib

SLCCurveAttrib Table included with: Demand, Flowcasting


CurveID 1 Dmd, Flowcasting

UPPER_TEXT

AttribName 2 Dmd, Flowcasting

UPPER_TEXT

Value Dmd, Flowcasting

UPPER_TEXT

DFUAttribGroup 3 Dmd UPPER_TEXT

Table description The SLCCurveAttribute table defines the curve generated from the Build Short Lifecycle Curve process and attributes associated with the curve. The curve is then assigned to a particular DFU according to attributes using the Assign Short Lifecycle Curve process.

Column descriptions CurveID The system generated identifier for a given curve.

AttribName A primary or secondary attribute associated with the curve.

Value The value of a primary or secondary attribute associated with the curve. This attribute value is used while assigning curves to the new DFUs.

DFUAttribGroup Name of the DFU attribute group to which this attribute belongs. This field is mapped to DFUAtrribGroup: DFUAtrribGroup.


SKUFactsData

SKUFactsData Table included with: Fulfillment, Flowcasting


AvailDate 3 FF, Flowcasting DATE 01/01/1970

BOHQty FF, Flowcasting FLOAT (126) -1

Dur FF, Flowcasting DURATION 1D Item 1 FF, Flowcasting TEXT Loc 2 FF, Flowcasting TEXT POSQty FF, Flowcasting FLOAT (126) 0

Table description Each row in this table contains the daily point-of-sale data for the SKU. This data is used as a input to the Detect Historical Out of Stock process.

Column descriptions AvailDate The date and time when this supply quantity is available to be used as supply.

BOHQty The actual Beginning On Hand quantity.

Dur The duration for which daily POS data is available.

Item The item associated with this quantity.

Loc The location associated with this quantity.

POSQty The point of sales quantity of the SKU for the specified duration.


SLCParam

SLCParam Table included with: Demand, Flowcasting



UPPER_TEXT


UPPER_TEXT


UPPER_TEXT


UPPER_TEXT


INTEGER 0

SmoothConstant

Dmd, Flowcasting

DECIMAL 0.01

StepSize Dmd, Flowcasting

DECIMAL 0.018

LimitConstant Dmd, Flowcasting

DECIMAL 0.95

ScalingFactor Dmd, Flowcasting

DECIMAL 1

MarketSize Dmd, Flowcasting

DECIMAL 0

ExternalInfluenceCoef

Dmd, Flowcasting

DECIMAL 0

InternalInfluenceCoef

Dmd, Flowcasting

DECIMAL 0

Table description The SLCParam table contains parameters to be set in order to run the Short Lifecycles method (see Short Lifecycle).





SeasonalitySW


SLCParam

This switch determines whether the model includes adjustments for seasonal influences.




SmoothConstant The constant value used by the Adaptive Estimation Procedure to calculate adjustments to curve coefficients. The default value for smooth constant is 0.001. The range of valid values is 0.001 to 1.

StepSize The constant value used by the Adaptive Estimation Procedure to calculate the adjustment size. The adjustment size is used for updating adjustment parameters to recalculate curve coefficients. The default value for step size is 0.001. The range of valid values is 0.001 to 1.

LimitConstant The constant value used by the Adaptive Estimation Procedure. It ensures that recalculated curve coefficients are within certain limits. As the new history moves in, curve coefficients are recalculated based on previous curve coefficients and recently posted history. The default value for limit constant is 0.95. The range of valid values is 0.001 to 1.

ScalingFactor The scaling factor used during the process of calculating the forecast for Short Lifecycle DFUs to scale the market size value. The default value is 1.

MarketSize The market size of the curve assigned to this DFU. It defines the total number of consumers who can ever adopt the new product. The market size value is generated by the Build Short Lifecycle Curve process based upon the past demand of similar DFUs. The Assign Short Lifecycle Curve process copies this market size value to the SLCParam table when the curve is assigned to the new DFU. You can change this value based upon your experience or market intelligence.

This value is copied from the SLCStats:LastMarketSize (on page 274) of the old DFU during the process of introducing the new DFU using the New DFU Introduction functionality.

The default value for market size is 0.

ExternalInfluenceCoef It is the rate of innovative adoption expressed as a percentage of those consumers who have not yet adopted the product. It defines the possibility about the number of consumers who start using the product due to an advertising effect or external factors.

This value is copied from the SLCStats:LastExternalInfluenceCoef (on page 274) of the old DFU during the process of introducing new DFU using the New DFU Introduction functionality.

The default value for external influence coefficient is 0. The range of valid values is 0 to 5.

InternalInfluenceCoef It is the rate of imitative adoption expressed as a percentage of those consumers who have not yet adopted the product. It defines the possibility about the number of consumers who start using the product due to the word-of-mouth effect or internal factors.

This value is copied from the SLCStats:LastInternalInfluenceCoef (on page 274) of the old DFU during the process of introducing new DFU using the New DFU Introduction functionality.

The default value for internal influence coefficient is 0. The range of valid values is 0 to 5.


SLCStats

SLCStats Table included with: Demand, Flowcasting



UPPER_TEXT


UPPER_TEXT


UPPER_TEXT


UPPER_TEXT


DECIMAL


DECIMAL

SE Dmd, Flowcasting

DECIMAL

SMAPE Dmd, Flowcasting

DECIMAL

LastMarketSize Dmd, Flowcasting

DECIMAL

LastInternalInfluenceCoef

Dmd, Flowcasting

DECIMAL

LastExternalInfluenceCoef

Dmd, Flowcasting

DECIMAL

Table description An output table that stores values generated from the Calculate Model process of a Short Lifecycle DFU.





Mean The average of the history points (on the second pass if there are outliers). This is used for the exception graph display.


SLCStats

The valid value for Mean is any real number.

MSE The Mean Squared Error based on historical fitting periods. The formula used is:

where

N= number of history points

Valid values for Mean Squared Error are any real numbers greater than 0.


SMAPE Symmetric Mean Absolute Percent Error compares the fitted history values (statistically generated forecast in the past) with the actual history for the entire duration of history.

SMAPE is calculated as the average of the absolute error divided by the average of history and fitted history, expressed as a percentage. It is always calculated when you run the Calculate Model process.

Note: If SMAPE = zero, and DFU:NPISw (on page 67) is enabled, it can be concluded that the DFU is new and does not yet have enough history for the model fit statistics to be valid. The statistical value will not be meaningful until the DFU reaches the Independence Date.

The formula for measuring SMAPE is:

where:




• t = time period

Valid values for SMAPE are any real numbers greater than 0.

LastMarketSize The last saved market size. The market size value is re-calculated each time the Calculate Model process is run on the Short Lifecycle DFU. This value is copied to SLCParam:MarketSize (on page 272) of new DFU during the process of introducing new DFU using the New DFU Introduction functionality.

LastInternalInfluenceCoef The last saved internal influence coefficient. The internal influence coefficient value is re-calculated each time the Calculate Model process is run on the Short Lifecycle DFU. This value is copied to the SLCParam:InternalInfluenceCoef (on page 272) of the new DFU during the process of introducing new DFU using the New DFU Introduction functionality.

LastExternalInfluenceCoef The last saved external influence coefficient. The external influence coefficient value is re-calculated each time the Calculate Model process is run on the Short Lifecycle DFU. This value is copied to SLCParam:ExternalInfluenceCoef (on page 272) of new DFU during the process of introducing new DFU using the New DFU Introduction functionality.


SmoothSeason

SmoothSeason Table included with: Demand, Flowcasting



TEXT


TEXT


TEXT


TEXT


INTEGER

OptimizedValue Dmd, Flowcasting

DECIMAL 0

Year 6 Dmd, Flowcasting

INTEGER 1970

Table description The SmoothSeason table calculates the optimized values for a seasonality according to DFU.

Note: When a NPI DFU (DFU with DFU:NPISw (on page 67)=1) is being processed, seasonality is not smoothed or updated, which means no seasonality data for this DFU is written to the SmoothSeason table.

Column descriptions DmdUnit The demand unit associated with the DFU whose seasonal profile is defined in this row

DmdGroup The demand group associated with the DFU whose seasonal profile is defined in this row.

Loc The location associated with the DFU whose seasonal profile is defined in this row.

Model Valid values for Model Identifier are identifiers of a model.

The model used by a Calculate Model process to identify the history stream and algorithm that is associated with the selected DFU.

Period The period number against which the Input Value is applied.


OptimizedValue Seasonality values that are a result of optimization by the Lewandowski method.

Note: Starting from version 7.5.1, Input values and Normalized values columns has been moved to the SeasonProfileValues (on page 255) table JDA Demand Management Foundation Reference Guide 275 © 1997 - 2014 JDA Software Group, Inc.- Confidential

SmoothSeason

Year The year in which the particular event occurs. Different years have different optimized values due to profile shifting. The default value for year is 1970.


SubEvent

SubEvent Table included with: Demand, Flowcasting



DmdGroup 3 Dmd, MDO, Flowcasting

TEXT

DmdUnit 2 Dmd, MDO, Flowcasting

TEXT

Dur Dmd, MDO, Flowcasting

DURATION 0

Event 1 Dmd, MDO, Flowcasting

TEXT

Loc 4 Dmd, MDO, Flowcasting

TEXT

Model 5 Dmd, MDO, Flowcasting

TEXT

Profile Dmd, MDO, Flowcasting

TEXT ' '

Qty Dmd, MDO, Flowcasting

DECIMAL 0

StartDate Dmd, MDO, Flowcasting


Table description Note: The Event Manager feature is no longer supported by JDA Demand. It is now supported by JDA Market Manager. Data stored in this table is transferred to Market Manager during Market Manager/Demand integration.

Each row in this table defines an event at the DFU level. Each row identifies a master event, links it to a DFU that is affected by the master event, and defines the attributes that apply to this DFU event.


DmdUnit The demand unit associated with the DFU identified in this row.

Dur Duration of the subevent. Valid values are 0 or greater. The initial value is 0.

Event Identifier of the master event for which one demand unit and demand group are identified in this row.


Model


SubEvent

The model used by a Calculate process to identify the history stream and algorithm that is associated with the selected DFU. Valid values are the identifier of a model.

Profile The profile used for this subevent. Valid values are the identifier of a profile from the Profile table.

Qty Total subevent quantity. Initial value is 0.

StartDate Date when the subevent begins.


Target

Target Table included with: Demand, Flowcasting


AllocMethod Dmd, Flowcasting

OPTION_NUMBER

1,2,3 2


TEXT ' '


TEXT

EndDate Dmd, Flowcasting

DATE SYSDATE


DATE SYSDATE

Target 1 Dmd, Flowcasting

TEXT

Table description This table stores the target profile information. It includes the target name, description, start and end dates, and the allocation method.

Targets are used to set the DFU’s net forecast to a specific targeted value. When you apply a target, the DFU’s net forecast is adjusted to equal this value. Using Demand workbench, you can apply other forecast adjustments, such as overrides, locks, and data driven events, to time periods that have already been assigned a target value. To apply targets within JDA Demand, see ’Working with targets" in "Adjusting the Statistical Forecast".

Column descriptions AllocMethod The allocation method. If 1 is selected, allocate by net forecast. If 2 is selected, allocate evenly by number of periods. If 3 is selected, allocate to the first forecast period. See the OnLine Expert for more detailed examples.

Valid Values for Allocation Method are 1 to 3.

Descr The description of the target.

DmdCal Specifies the Demand Calendar of the DFUs attached to a target.

EndDate The target end date.

StartDate The target start date.

Target The name of the target.


TargetDFUMap

TargetDFUMap Table included with: Demand, Flowcasting


DmdGroup 2 Dmd, Flowcasting TEXT

DmdUnit 1 Dmd, Flowcasting TEXT Loc 3 Dmd, Flowcasting TEXT Model 4 Dmd, Flowcasting TEXT Qty Dmd, Flowcasting DECIMAL 0.0 Target 5 Dmd, Flowcasting TEXT

Table description This table maps the targets defined in the Targets table to individual DFU Models.

Targets are used to set the DFU’s net forecast to a specific targeted value. When you apply a target, the DFU’s net forecast is adjusted to equal this value. Using Demand workbench, you can apply other forecast adjustments, such as overrides, locks, and data driven events, to time periods that have already been assigned a target value. To apply targets within JDA Demand, see ’Working with targets" in "Adjusting the Statistical Forecast".




Model The model associated with this target.


Qty The target quantity for this DFU.

Target The name of the target.


WDDArea

WDDArea Table included with: Demand, Flowcasting


Default value

WDDArea 1 Dmd, Flowcasting

VARCHAR2(50 CHAR)


VARCHAR2(50 CHAR)

Table description This table contains the information about the area for which the Weather Driven Demand is published. This area is mapped from the Loc table based on the selected DFU.

Column descriptions WDDArea A unique identifier of an area which is impacted by weather.

Descr The description for WDDArea.


WDDCategory

WDDCategory Table included with: Demand,Flowcasting


Default value

WDDCategory 1 Dmd, Flowcasting

VARCHAR2(50 CHAR)


VARCHAR2(50 CHAR)

Table description This table contains the information about a product category for which the Weather Driven Demand is published. This category is mapped from the DmdUnit table based on the selected DFU.

Column descriptions WDDCategory A unique identifier of a product category which is impacted by weather.

Descr The description for WDDCategory.


WDDCategoryAreaMap

WDDCategoryAreaMap Table included with: Demand, Flowcasting


Default value

WDDCategory 1 Dmd, Flowcasting

VARCHAR2(50 CHAR)

WDDArea 2 Dmd, Flowcasting

VARCHAR2(50 CHAR)

WDDGraphURL Dmd, Flowcasting

VARCHAR2(50 CHAR)

Table description This table contains the the mapping relationship between the product category and the area. It also contains the URL using which the Weather Driven Demand graph for a product category, is published in Demand Workbench and Exception graphs.



WDDGraphURL This URL contains the data required to publish the Weather Driven Demand graph of a product category. This graph displays the change in demand percentage for four weeks (LAST WEEK, THIS WEEK, NEXT WEEK, and NEXT NEXT WEEK) based on weather.


WDDData

WDDData Table included with: Demand, Flowcasting


Default value

WDDCategory 1 Dmd, Flowcasting VARCHAR2(50 CHAR)

WDDArea 2 Dmd, Flowcasting VARCHAR2(50 CHAR)

Weekend 3 Dmd DATE WDDImpact Dmd, Flowcasting FLOAT LastUpdated Dmd, Flowcasting DATE

Table description This table contains the information about the impact of Weather Driven Demand on a particular category, area and week of the selected DFU.



PeriodEnd The end date for a specific period for which the Weather Driven Demand is published.

WDDImpact The percentage of change in demand for subsequent weeks based on weather impact.

LastUpdated The date on which the record was last updated.


WFMFcstStruct

WFMFcstStruct Table included with: Demand, Flowcasting


ChangeDate Dmd, Flowcasting

DATE

ChangeType Dmd TEXT DmdGroup 2 Dmd,

Flowcasting TEXT

DmdGroupDescr

Dmd, Flowcasting

UPPER_TEXT


TEXT

DmdUnitDescr Dmd, Flowcasting

UPPER_TEXT


TEXT

LocDescr Dmd, Flowcasting

UPPER_TEXT

Table description The WFMFcstStruct table is populated with the data provided by WFM. This data is then processed by the Build WFM Data process that creates DFUs.

Column descriptions ChangeDate The date on which WFM changes or adds the data.

ChangeType The identifier which identifies whether the DFU is added, deleted or updated.

DmdGroup The demand group associated with the DFU from which forecast demand data is mapped.

DmdGroupDescr The description of the demand group.


DmdUnitDescr The description of the demand unit.


LocDescr The description of the location.


Table Relationships

Table Relationships The following table lists the parent/child relationship for the tables in the SCPO database. Values must exist in the parent column before they can be entered in the child column. This table may also include system tables.

CONSTRAINT NAME TABLE NAME COLUMN NAME PRIMARY KEY TABLE NAME

PRIMARY KEY COLUMN NAME

ACTIONFILTER_LOC_FK ACTIONFILTER - LOC LOC - LOC AGGSKU_SKU_FK1 AGGSKU - ITEM - LOC SKU - ITEM - LOC AGGSKU_SKU_FK2 AGGSKU - AGGITEM - AGGLOC SKU - ITEM - LOC ALLOCBASENEEDVARDETAILS_FK

ALLOCBASENEEDVAR - NAME ALLOCNEEDVARMASTER

- NAME

ALLOCCALPROFILEDATA_FK1 ALLOCCALPROFILEDATA

- ALLOCCALPROFILE ALLOCCALPROFILE - ALLOCCALPROFILE

ALLOCDATACOLLECTIONS_FK1

ALLOCDATACOLLECTIONS

- ALLOCATIONSETID ALLOCSET - ALLOCATIONSETID

ALLOCDERNEEDVAR_FK ALLOCDERNEEDVAR - NAME ALLOCNEEDVARMASTER

- NAME

ALLOCEXCEPTIONMASTER_EXCP_FK1

ALLOCEXCEPTION - EXCEPTIONNUM ALLOCEXCEPTIONMASTER

- EXCEPTIONNUM

ALLOCLIKELOCPARAM_LIK_LOC_FK

ALLOCLIKELOCPARAM - LIKELOC LOC - LOC

ALLOCLIKELOCPARAM_LOC_LOC_FK

ALLOCLIKELOCPARAM - LOC LOC - LOC

ALLOCNEED_ALLOCSET_FK1 ALLOCNEED - ALLOCATIONSETID ALLOCSET - ALLOCATIONSETID ALLOCNEED_ALLOCSET_FK2 ALLOCNEED - LOC LOC - LOC ALLOCPPKDTLS_ALLOCPPK_FK1

ALLOCSUPPLYPREPACKDETAILS

- SUPPLYID ALLOCSUPPLYPREPACK

- SUPPLYID

ALLOCPREPACKDETAILS_SKU_FK2

ALLOCSUPPLYPREPACKDETAILS

- ITEM - LOC SKU - ITEM - LOC

ALLOCPROFILEVALUES_FK ALLOCPROFILEVALUES - PROFILENAME ALLOCPROFILE - PROFILENAME ALLOCPROFILE_FK ALLOCPROFILE - CATEGORY ALLOCPROFILECATEG

ORY - CATEGORY

ALLOCRESSRCDTLS_ALLOCSET_FK1

ALLOCRESULTSOURCEDETAILS


ALLOCRESULTDETAILS_SKU_ ALLOCRESULTDETAILS - ITEM - LOC SKU - ITEM - LOC


Table Relationships



FK2 ALLOCRESULTDETAILS_SUMMARY_FK1

ALLOCRESULTDETAILS - ALLOCATIONSETID ALLOCRESULTSUMMARY

- ALLOCATIONSETID

ALLOCRSLTSMRY_ALLOCSET_FK1

ALLOCRESULTSUMMARY


ALLOCSTOREGRPSEL_FK ALLOCSTOREGRPSEL - NEEDVARNAME ALLOCNEEDVARMASTER

- NAME

ALLOCSUPPLIES_ALLOCSET_FK1

ALLOCSUPPLIES - ALLOCATIONSETID ALLOCSET - ALLOCATIONSETID

ALLOCSUPPLIES_SKU_FK2 ALLOCSUPPLIES - ITEM - LOC SKU - ITEM - LOC ALLOCSUPPLYPREPACK_LOC_FK1

ALLOCSUPPLYPREPACK - LOC LOC - LOC

ALTBOM_BOM_FK03 ALTBOM - ITEM - SUBORD - LOC - BOMNUM - EFF - OFFSET

BOM - ITEM - SUBORD - LOC - BOMNUM - EFF - OFFSET

ALTBOM_CAL_FK02 ALTBOM - YIELDCAL CAL - CAL ALTBOM_ITEM_FK01 ALTBOM - ALTSUBORD ITEM - ITEM ALTPRODNSTEP_PRODNSTEP_FK01

ALTPRODUCTIONSTEP - PRODUCTIONMETHOD - PRIMARYSTEPNUM - ITEM - LOC - EFF

PRODUCTIONSTEP - PRODUCTIONMETHOD - STEPNUM - ITEM - LOC - EFF

ALTPRODUCTIONSTEP_CAL_FK03

ALTPRODUCTIONSTEP - PRODRATECAL CAL - CAL

ALTPRODUCTIONSTEP_RES_FK02

ALTPRODUCTIONSTEP - ALTRES RES - RES

AVGDMD_SKU_FK1 AVGDMD - ITEM - LOC SKU - ITEM - LOC AVSGRAVESPARAM_DFU_FK1 AVSGRAVESPARAM - DMDUNIT - DMDGROUP - LOC -

MODEL DFU - DMDUNIT -

DMDGROUP - LOC - MODEL

AVSGRAVESSTATS_DFU_FK1 AVSGRAVESSTATS - DMDUNIT - DMDGROUP - LOC - MODEL

DFU - DMDUNIT - DMDGROUP - LOC - MODEL

BOM_CAL_FK01 BOM - YIELDCAL CAL - CAL


Table Relationships



BOM_LOC_FK1 BOM - LOC LOC - LOC BOM_SKU_FK1 BOM - ITEM - LOC SKU - ITEM - LOC BOM_SKU_FK2 BOM - SUBORD - LOC SKU - ITEM - LOC BOM_UOM_FK1 BOM - QTYUOM UOM - UOM BOOKINGGRPCURVE_BOOKINGGRP_FK1

BOOKINGGROUPCURVE - BOOKINGGROUP BOOKINGGROUP - BOOKINGGROUP

CALATTRIBUTE_CALPATTERN_FK01

CALATTRIBUTE - CAL - PATTERNSEQNUM CALPATTERN - CAL - PATTERNSEQNUM

CALDATAEXPANDED_CAL_FK CALDATAEXPANDED - CAL CAL - CAL CALDATASTATIC_CAL_FK01 CALDATASTATIC - CAL CAL - CAL CALDATA_CAL_FK1 CALDATA - CAL CAL - CAL CALDATA_CAL_FK2 CALDATA - ALTCAL CAL - CAL CALINTERVAL_CAL_FK1 CALINTERVAL - CAL CAL - CAL CALPATTERN_CAL_FK01 CALPATTERN - CAL CAL - CAL CANDIDATEFILTERVAL_FILTER_FK

PROMOCANDIDATEDFU_FILTER_VALUE

- CRITERIA_ID - FILTER_ID PROMOCANDIDATEDFU_FILTER

- CRITERIA_ID - FILTER_ID

CAUSALFACTORVALUE_CF_FK1

CAUSALFACTORVALUE - CAUSALFACTOR CAUSALFACTOR - CAUSALFACTOR

CAUSALFACTOR_CFTYPE_FK1

CAUSALFACTOR - TYPE CAUSALFACTORTYPE - TYPE

CHK_SKUDEMANDDPARAM_PRICECAL

SKUDEMANDPARAM - PRICECAL CAL - CAL

CLPFACTCURVDATA_CLPFACTCURV_FK

CLIPPINGFACTORCURVEDATA

- CLIPPINGFACTORCURVEID CLIPPINGFACTORCURVE

- CLIPPINGFACTORCURVEID

COMPDEFVAR_TO_COMPDEF COMPUTATIONVAR - COMPUTATIONNAME COMPUTATION - COMPUTATIONNAME

COMPDEFVAR_TO_MEASURE COMPUTATIONVAR - MEASUREID MEASURE - MEASUREID COMPETITORPRICE_COMPETITOR_FK1

COMPETITORPRICE - COMPETITOR - COMPETITORLOC COMPETITORINFO - COMPETITOR - COMPETITORLOC

COMPETITORPRICE_DMDUNIT_FK1

COMPETITORPRICE - DMDUNIT DMDUNIT - DMDUNIT


Table Relationships



COMPLOCMAP_COMPETITOR_FK1

COMPETITORLOCMAP - COMPETITOR - COMPETITORLOC COMPETITORINFO - COMPETITOR - COMPETITORLOC

COMPLOCMAP_LOC_FK2 COMPETITORLOCMAP - LOC LOC - LOC COMPSCALARVAR_TO_COMPDEF

COMPUTATIONSCALARVAR

- COMPUTATIONNAME COMPUTATION - COMPUTATIONNAME

COMPT_WT_FK3 NPO_RESRC_COMPETITOR_WGT

- RESRC_ID - COMPETITOR_ID NPO_RESRC_COMPETITOR_MAP

- RESRC_ID - COMPETITOR_ID

COSTELEMENT_SKU_FK1 COSTELEMENT - ITEM - LOC SKU - ITEM - LOC COSTTIER_COSTTIERCAT_FK1

COSTTIER - CATEGORY COSTTIERCATEGORY - CATEGORY

COSTTIER_COST_FK1 COSTTIER - COST COST - COST COST_CAL_FK1 COST - ACCUMCAL CAL - CAL COST_UOM_FK2 COST - QTYUOM UOM - UOM COST_UOM_FK3 COST - CURRENCYUOM UOM - UOM CPPALTRES_RES_FK1 CPPALTRES - RES RES - RES CPPALTRES_RES_FK2 CPPALTRES - ALTRES RES - RES CPPFAMILY_RES_FK1 CPPFAMILY - RES RES - RES CPPFAMILY_SKU_FK1 CPPFAMILY - ITEM - LOC SKU - ITEM - LOC CPPPLANARRIV_SKU_FK3 CPP_PLANARRIV - ITEM - SOURCE SKU - ITEM - LOC CPPSTRATSTEPP_CPPSTRAT_FK1

CPPSTRATSTEP - CPPSTRAT CPPSTRAT - CPPSTRAT

CPPSTRATSTEPP_CTB_FK1 CPPSTRATSTEP - CPPTIEBREAKER CPPTIEBREAKER - CPPTIEBREAKER CPPTIEBREAKERRULE_CTB_FK1

CPPTIEBREAKERRULE - CPPTIEBREAKER CPPTIEBREAKER - CPPTIEBREAKER

CPP_PLANARRIV_SKU_FK1 CPP_PLANARRIV - ITEM - DEST SKU - ITEM - LOC CPP_PLANORDER_SKU_FK1 CPP_PLANORDER - ITEM - LOC SKU - ITEM - LOC CPP_RESLOADDETAIL_SKU_FK1

CPP_RESLOADDETAIL - ITEM - LOC SKU - ITEM - LOC

CPP_SKUEXCEPTION_SKU_FK1

CPP_SKUEXCEPTION - ITEM - LOC SKU - ITEM - LOC

CRITERIAFILTER_FK PROMOCANDIDATEDFU - CRITERIA_ID PROMOCANDIDATEDF - CRITERIA_ID


Table Relationships



_FILTER U_CRITERIA CROSTONPARAM_DFU_FK CROSTONPARAM - DMDUNIT - DMDGROUP - LOC -



CROSTONSTATS_DFU_FK CROSTONSTATS - DMDUNIT - DMDGROUP - LOC - MODEL


CSLTEMPLTDATA_CSLTEMPLT_FK1

CSLTEMPLATEDATA - CSLTEMPLATE CSLTEMPLATE - CSLTEMPLATE

CURRENCYPROFILE_CURRENCY_FK1

CURRENCYPROFILE - FROMCURRENCY CURRENCY - CURRENCY

CURRENCYPROFILE_CURRENCY_FK2

CURRENCYPROFILE - TOCURRENCY CURRENCY - CURRENCY

CURRPROFILEVAL_CURRPROFILE_FK1

CURRENCYPROFILEVAL - FROMCURRENCY - TOCURRENCY CURRENCYPROFILE - FROMCURRENCY - TOCURRENCY

CUSTORDERHEADER_CUST_FK1

CUSTORDERHEADER - CUST CUST - CUST

CUSTORDERHIST_DFULOC_FK

CUSTORDERHIST - DFULOC LOC - LOC

CUSTORDERHIST_DFUVIEW_FK

CUSTORDERHIST - DMDUNIT - DMDGROUP - DFULOC

DFUVIEW - DMDUNIT - DMDGROUP - LOC

CUSTORDERHIST_DMDGROUP_FK

CUSTORDERHIST - DMDGROUP DMDGROUP - DMDGROUP

CUSTORDERHIST_DMDUNIT_FK

CUSTORDERHIST - DMDUNIT DMDUNIT - DMDUNIT

CUSTORDERHIST_SKU_FK1 CUSTORDERHIST - ITEM - LOC SKU - ITEM - LOC CUSTORDERSTATHIST_DFU_FK

CUSTORDERSTATHIST - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

CUSTORDERSTATHIST_DMDGROUP_FK

CUSTORDERSTATHIST - DMDGROUP DMDGROUP - DMDGROUP

CUSTORDERSTATHIST_DMDUNIT_FK

CUSTORDERSTATHIST - DMDUNIT DMDUNIT - DMDUNIT

CUSTORDERSTATHIST_LOC_FK

CUSTORDERSTATHIST - LOC LOC - LOC


Table Relationships



CUSTORDERSTATUS_CUSTORDER_FK1

CUSTORDERSTATUS - ITEM - LOC - ORDERID - SHIPDATE

CUSTORDER - ITEM - LOC - ORDERID - SHIPDATE

CUSTORDERSTAT_DFU_FK CUSTORDERSTAT - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

CUSTORDERSTAT_DMDGROUP_FK

CUSTORDERSTAT - DMDGROUP DMDGROUP - DMDGROUP

CUSTORDERSTAT_DMDUNIT_FK

CUSTORDERSTAT - DMDUNIT DMDUNIT - DMDUNIT

CUSTORDERSTAT_LOC_FK CUSTORDERSTAT - LOC LOC - LOC CUSTORDER_CUSTORDERHEADER_FK1

CUSTORDER - CUST - HEADEREXTREF CUSTORDERHEADER - CUST - EXTREF

CUSTORDER_DFULOC_FK1 CUSTORDER - DFULOC LOC - LOC CUSTORDER_DFUVIEW_FK CUSTORDER - DMDUNIT - DMDGROUP -

DFULOC DFUVIEW - DMDUNIT -

DMDGROUP - LOC CUSTORDER_DMDGROUP_FK1

CUSTORDER - DMDGROUP DMDGROUP - DMDGROUP

CUSTORDER_DMDUNIT_FK1 CUSTORDER - DMDUNIT DMDUNIT - DMDUNIT CUSTORDER_SKU_FK1 CUSTORDER - ITEM - LOC SKU - ITEM - LOC DASHBOARDGOALTARGETFK1

DASHBOARDGOALTARGET

- HIERARCHYNODEID DASHBOARDHIERARCHYNODE

- HIERARCHYNODEID

DASHBOARDGOALTARGETFK2

DASHBOARDGOALTARGET

- WIDGETID DASHBOARDWIDGET - WIDGETID

DASHBOARDHIERARCHYNODELVLFK1

DASHBOARDHIERNODELEVEL

- HIERARCHYNODEID DASHBOARDHIERARCHYNODE

- HIERARCHYNODEID

DASHBOARDWIDGETGROUPBYFK1

DASHBOARDWIDGETGROUPBY


DBCONNECT_LOC_FK SEQDBCONNECT - LOC LOC - LOC DBPARAM_CAL_FK1 DBPARAM - DMDCAL CAL - CAL DBPARAM_DMDGROUP_FK1 DBPARAM - SUMMARYDMDGROUP DMDGROUP - DMDGROUP DC_ALGMRANK_DC_DFUCLASS_FK1

DC_ALGORITHMRANK - DMDUNIT - DMDGROUP - LOC - HISTSTREAM

DC_DFUCLASS - DMDUNIT - DMDGROUP - LOC - HISTSTREAM


Table Relationships



DC_AVSGRAVES_DC_ALGMRANK_FK1

DC_AVSGRAVESPARAM - DMDUNIT - DMDGROUP - LOC - HISTSTREAM - ALGORITHM

DC_ALGORITHMRANK - DMDUNIT - DMDGROUP - LOC - HISTSTREAM - ALGORITHM

DC_CROSTNPARAM_DC_ALGMRANK_FK1

DC_CROSTONPARAM - DMDUNIT - DMDGROUP - LOC - HISTSTREAM - ALGORITHM


DC_DFUCLASS_DFUVIEW_FK2

DC_DFUCLASS - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DC_DFUCLASS_HISTSTREAM_FK1

DC_DFUCLASS - HISTSTREAM HISTSTREAM - HISTSTREAM

DC_DFUPARAM_CAL_FK2 DC_DFUPARAM - DMDCALUSED CAL - CAL DC_DFUPARAM_DC_DFUCLASS_FK1

DC_DFUPARAM - DMDUNIT - DMDGROUP - LOC - HISTSTREAM


DC_EXCEPTION_DFUVIEW_FK2

DC_EXCEPTION - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DC_EXCEPTION_HISTSTREAM_FK1

DC_EXCEPTION - HISTSTREAM HISTSTREAM - HISTSTREAM

DC_HOLTPARAM_DC_ALGMRANK_FK1

DC_HOLTPARAM - DMDUNIT - DMDGROUP - LOC - HISTSTREAM - ALGORITHM


DC_LEWPARAM_DC_ALGMRANK_FK1

DC_LEWPARAM - DMDUNIT - DMDGROUP - LOC - HISTSTREAM - ALGORITHM


DC_LINREGPARAM_DC_ALGMRANK_FK1

DC_LINREGPARAM - DMDUNIT - DMDGROUP - LOC - HISTSTREAM - ALGORITHM


DC_MOVAVGPARAM_DC_ALGMRANK_FK1

DC_MOVINGAVGPARAM

- DMDUNIT - DMDGROUP - LOC - HISTSTREAM - ALGORITHM

DC_ALGORITHMRANK - DMDUNIT - DMDGROUP - LOC - HISTSTREAM -


Table Relationships



ALGORITHM DC_STATS_DC_DFUCLASS_FK1

DC_STATS - DMDUNIT - DMDGROUP - LOC - HISTSTREAM


DDEPROFILE_DFU_FK DDEPROFILE - DMDUNIT - DMDGROUP - LOC - MODEL


DEALSKU_ITEM_FK1 DEALSKU - ITEM ITEM - ITEM DEALSKU_LOC_FK1 DEALSKU - SOURCE LOC - LOC DEALSKU_LOC_FK2 DEALSKU - DEST LOC - LOC DECOMPDFUHISTDIAG_DECOMPGRP_FK

DECOMPDFUHISTDIAGNOST

- DECOMPGROUP DECOMPGROUP - DECOMPGROUP

DECOMPDFUHISTDIAG_DFUPRM_FK1

DECOMPDFUHISTDIAGNOST

- DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DECOMPGROUPEXCEPTION_MRMEXP

DECOMPGROUPEXCEPTION

- EXPERIMENTID MRMEXPERIMENT - EXPERIMENTID

DECOMPGROUPEX_DECOMPG_FK



DECOMPGROUPEX_MRMG_FK DECOMPGROUPEXCEPTION

- MRMGROUP MRMGROUP - MRMGROUP

DECOMPGRPCONVDIAG_DECOMPGRP_FK

DECOMPGROUPCONVERGDIAGNOST


DECOMPGRPEXCEPTION_DFUVIEW_FK


- DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DECOMPGRPHISTDIAG_DECOMPGRP_FK

DECOMPGROUPHISTDIAGNOST


DEPDMDORDER_SKU_FK1 DEPDMDORDER - ITEM - LOC SKU - ITEM - LOC DEPDMDREQUIREMENT_SKU_FK1

DEPDMDREQUIREMENT - PARENT - LOC SKU - ITEM - LOC

DEPDMDSTATIC_SKU_FK1 DEPDMDSTATIC - PARENT - LOC SKU - ITEM - LOC DEPLOYMENTDEMAND_ITEM_FK1

DEPLOYMENTDEMAND - PRIMARYITEM ITEM - ITEM

DEPLOYMENTDEMAND_SKU_ DEPLOYMENTDEMAND - ITEM - SOURCE SKU - ITEM - LOC


Table Relationships



FK1 DEPLOYMENTDEMAND_SKU_FK2

DEPLOYMENTDEMAND - ITEM - DEST SKU - ITEM - LOC

DEPLOYMENTDEMAND_TRANSMODE_FK

DEPLOYMENTDEMAND - TRANSMODE TRANSMODE - TRANSMODE

DEPLOYMENTPRIORITY_ITEM_FK1

DEPLOYMENTPRIORITY - PRIMARYITEM ITEM - ITEM

DEPLOYMENTPRIORITY_SKU_FK1

DEPLOYMENTPRIORITY - ITEM - SOURCE SKU - ITEM - LOC

DEPLOYMENTPRIORITY_SKU_FK2

DEPLOYMENTPRIORITY - ITEM - DEST SKU - ITEM - LOC

DEPLOYMENTPRIORITY_TRANSMODE_F

DEPLOYMENTPRIORITY - TRANSMODE TRANSMODE - TRANSMODE

DFUALLOCPROFILEMAP_FK1 DFUALLOCPROFILEMAP - DMDUNIT - DMDGROUP - LOC - MODEL


DFUATTRIBGROUP_FK DFUATTRIB - DFUATTRIBGROUP DFUATTRIBGROUP - DFUATTRIBGROUP DFUAVAILSTATUS_DFURMPARAM_FK1

DFUAVAILSTATUS - DMDUNIT - DMDGROUP - LOC DFURMPARAM - DMDUNIT - DMDGROUP - LOC

DFUBASECOST_FK DFUBASECOST - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUBASEPRICE_FK1 DFUBASEPRICE - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DFUBOOKHISTUNCSTR_DFURMPARAM_F

DFUBOOKINGHISTUNCONSTR

- DMDUNIT - DMDGROUP - LOC DFURMPARAM - DMDUNIT - DMDGROUP - LOC

DFUBOOKINGHIST_DFURMPARAM_FK1

DFUBOOKINGHIST - DMDUNIT - DMDGROUP - LOC DFURMPARAM - DMDUNIT - DMDGROUP - LOC

DFUCAUSALFACTOR_CF_FK1 DFUCAUSALFACTOR - CAUSALFACTOR CAUSALFACTOR - CAUSALFACTOR DFUCAUSALFACTOR_DFU_FK1

DFUCAUSALFACTOR - DMDUNIT - DMDGROUP - LOC - MODEL


DFUCLEARANCEPRICE_DMDGROUP_FK

DFUCLEARANCEPRICE - DMDGROUP DMDGROUP - DMDGROUP


Table Relationships



DFUCLEARANCEPRICE_DMDUNIT_FK

DFUCLEARANCEPRICE - DMDUNIT DMDUNIT - DMDUNIT

DFUCLEARANCEPRICE_LOC_FK

DFUCLEARANCEPRICE - LOC LOC - LOC

DFUCMPTRPR_DFUPRPARAM_FK1

DFUCOMPETITORPRICE - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUCOEF_DFU_FK1 DFUCOEF - DMDUNIT - DMDGROUP - LOC - MODEL


DFUCOMPETITPRI_COMPETITOR_FK1

DFUCOMPETITORPRICE - COMPETITOR - COMPETITORLOC COMPETITORINFO - COMPETITOR - COMPETITORLOC

DFUCOSTELEMENT_FK DFUCOSTELEMENT - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUCOSTELEMENT_FKEY DFUCOSTELEMENT - TYPE DFUCOSTELEMENTTYPE

- TYPE

DFUCRELAST_PRICEPRM_FK1

DFUCROSSELASTICITY - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUCRELAST_PRICEPRM_IMPACT_FK1

DFUCROSSELASTICITY - IMPACTINGDMDUNIT - IMPACTINGDMDGROUP - IMPACTINGLOC

DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUCRSELASDFT_DFUPRCEPARAM_FK1

DFUCROSSELASTICITYDRAFT


DFUCRSELASDFT_DFUPRCEPARAM_FK2

DFUCROSSELASTICITYDRAFT

- IMPACTINGDMDUNIT - IMPACTINGDMDGROUP - IMPACTINGLOC


DFUDDEMAP_DDEPROFILE_FK

DFUDDEMAP - DDEPROFILEID DDEPROFILE - DDEPROFILEID

DFUDDEMAP_DFU_FK DFUDDEMAP - DMDUNIT - DMDGROUP - LOC - MODEL


DFUDEPDMDFCST_FK1 DFUDEPDMDFCST - RELATION DFUATTACHRATERELATION

- RELATION

DFUDEPDMDHIST_FK1 DFUDEPDMDHIST - RELATION DFUATTACHRATERELATION

- RELATION


Table Relationships



DFUEFFCOST_FK DFUEFFCOST - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUEFFPRICE_DFUVIEW_FK1 DFUEFFPRICE - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DFUELASDRFT_DFUPRCEPARAM_FK1

DFUELASTICITYDRAFT - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUEXCEPTION_DFUVIEW_FK1

DFUEXCEPTION - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DFUEXTERNALFCST_DFU_FK1

DFUEXTERNALFCST - DMDUNIT - DMDGROUP - LOC - MODEL


DFUINV_DFUPRICEPRM_FK DFUINVENTORY - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUMAINTCOPYDFU_DMDGROUP_FK3

DFUMAINTCOPYDFU - TODMDGROUP DMDGROUP - DMDGROUP

DFUMAINTCOPYDFU_DMDUNIT_FK2

DFUMAINTCOPYDFU - TODMDUNIT DMDUNIT - DMDUNIT

DFUMAINTCOPYDFU_FROMLIFCYC_FK6

DFUMAINTCOPYDFU - FROMLIFECYCLE LEWFACTOR - LEWFACTOR

DFUMAINTCOPYDFU_HISTSTREAM_FK8

DFUMAINTCOPYDFU - HISTSTREAM HISTSTREAM - HISTSTREAM

DFUMAINTCOPYDFU_LOC_FK4

DFUMAINTCOPYDFU - TOLOC LOC - LOC

DFUMAP_DFU_FK1 DFUMAP - TODMDUNIT - TODMDGROUP - TODFULOC - TOMODEL


DFUMAP_DFU_FK2 DFUMAP - FROMDMDUNIT - FROMDMDGROUP - FROMDFULOC - FROMMODEL


DFUMAP_FCSTPROFILE_FK1 DFUMAP - FCSTTYPE DFUMAPFCSTPROFILE - FCSTTYPEPROFILE DFUMAP_MAP_FK1 DFUMAP - MAP MAP - MAP DFUMOVINGEVENTMAP_DFUVIEW_FK1

DFUMOVINGEVENTMAP - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DFUNPIRELATION_DFU_FK1 DFUNPIRELATION - TODMDUNIT - TODMDGROUP - DFU - DMDUNIT - JDA Demand Management Foundation Reference Guide 296 © 1997 - 2014 JDA Software Group, Inc.- Confidential

Table Relationships



TOLOC - TOMODEL DMDGROUP - LOC - MODEL

DFUPLNREC_DFUPRICEPRM_FK

DFUPLANNEDRECEIPT - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUPRICECONS_DFUVIEW_FK1

DFUPRICECONSTRAINT - LHSDMDUNIT - LHSDMDGROUP - LHSLOC


DFUPRICECONS_DFUVIEW_FK2

DFUPRICECONSTRAINT - RHSDMDUNIT - RHSDMDGROUP - RHSLOC


DFUPRICEPARAM_DFU_FK3 PRICESCENARIORULECONFLICT

- LHSDMDUNIT - LHSDMDGROUP - LHSLOC


DFUPRICERELATIONMAP_DFUPP_FK1

DFUPRICERELATIONMAP

- IMPACTINGDMDUNIT - IMPACTINGDMDGROUP - IMPACTINGLOC


DFUPRICERELATIONMAP_DFUPP_FK3

DFUPRICERELATIONMAP


DFUPRICERELMAP_PRICEREL_FK2

DFUPRICERELATIONMAP

- RELATIONNAME PRICERELATION - RELATIONNAME

DFUPRIPRM_DECOMSUBGRP_FK1

DFUPRICEPARAM - DECOMPSUBGROUP - DECOMPGROUP

DECOMPSUBGROUP - DECOMPSUBGROUP - DECOMPGROUP


DFUPRICEPARAM - MASK MASK - MASK


DFUPRICEPARAM - MRMGROUP MRMGROUP - MRMGROUP


DFUPRICEPARAM - MBAGROUP MBAGROUP - MBAGROUP


DFUPRICEPARAM - PRICEGROUP PRICEGROUP - PRICEGROUP

DFUPROJDRAFTSTATIC_DFU_FK1

DFUPROJDRAFTSTATIC - DMDUNIT - DMDGROUP - LOC - MODEL


DFUPROJSTATIC_DFU_FK1 DFUPROJSTATIC - DMDUNIT - DMDGROUP - LOC - MODEL


DFUPRPARMET_PRICEPRM_F DFUPRICEPARAMMETRI - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -


Table Relationships



K1 C DMDGROUP - LOC DFUPRPARMET_PRMETSCEN_FK1

DFUPRICEPARAMMETRIC

- METRICSCENARIO PRICEMETRICSCENARIO

- METRICSCENARIO

DFUREFPRICE_FK1 DFUREFPRICE - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFURMEVENTTYPEMAP_EVENTTYPE_FK

DFURMEVENTTYPEMAP - EVENTTYPE RMEVENTTYPE - EVENTTYPE

DFURMEVENTTYPEMAP_RMMAP_FK1

DFURMEVENTTYPEMAP - FROMDMDUNIT - FROMDMDGROUP - FROMLOC - TODMDUNIT - TODMDGROUP - TOLOC - MAP

DFURMMAP - FROMDMDUNIT - FROMDMDGROUP - FROMLOC - TODMDUNIT - TODMDGROUP - TOLOC - MAP

DFURMMAP_DFURMPARAM_FK1

DFURMMAP - FROMDMDUNIT - FROMDMDGROUP - FROMLOC

DFURMPARAM - DMDUNIT - DMDGROUP - LOC

DFURMMAP_DFURMPARAM_FK2

DFURMMAP - TODMDUNIT - TODMDGROUP - TOLOC

DFURMPARAM - DMDUNIT - DMDGROUP - LOC

DFURMMAP_MAP_FK1 DFURMMAP - MAP MAP - MAP DFURMPARAM_BOOKINGGROUP_FK1

DFURMPARAM - BOOKINGGROUP BOOKINGGROUP - BOOKINGGROUP

DFURMPARAM_DFUVIEW_FK1

DFURMPARAM - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

DFURMPARAM_RMEVENTCAL_FK1

DFURMPARAM - EVENTCAL RMEVENTCAL - EVENTCAL

DFURMPARAM_SURVCURVE_FK

DFURMPARAM - SURVIVALCURVE SURVIVALCURVE - SURVIVALCURVE

DFURMPRM_CLPFACTCURVE_FK

DFURMPARAM - CLIPPINGFACTORCURVEID CLIPPINGFACTORCURVE

- CLIPPINGFACTORCURVEID

DFURMPRM_PDTAUCURVE_FK1

DFURMPARAM - PDTAUCURVEID PDTAUCURVE - PDTAUCURVEID

DFUTOE3FCST_SKU_FK1 DFUTOE3FCST - ITEM - SKULOC SKU - ITEM - LOC DFUTOEPFCST_DFUVIEW_FK1

DFUTOEPFCST - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC


Table Relationships



DFUTOITXFCST_SKU_FK1 DFUTOITXFCST - ITEM - LOC SKU - ITEM - LOC DFUTOSKUFCST_SKU_FK1 DFUTOSKUFCST - ITEM - SKULOC SKU - ITEM - LOC DFUTOSKU_DFUVIEW_FK1 DFUTOSKU - DMDUNIT - DMDGROUP -

DFULOC DFUVIEW - DMDUNIT -

DMDGROUP - LOC DFUTOSKU_MODEL_FK1 DFUTOSKU - MODEL MODEL - MODEL DFUTOSKU_SKU_FK1 DFUTOSKU - ITEM - SKULOC SKU - ITEM - LOC DFUTOTALVOL_DFU_FK1 DFUTOTALVOL - DMDUNIT - DMDGROUP - LOC -



DFUTOWFMFCST_DMDGROUP_FK1

DFUTOWFMFCST - DMDGROUP DMDGROUP - DMDGROUP

DFUTOWFMFCST_DMDUNIT_FK1

DFUTOWFMFCST - DMDUNIT DMDUNIT - DMDUNIT

DFUTOWFMFCST_LOC_FK1 DFUTOWFMFCST - LOC LOC - LOC DFUTPR_DFUPP_FK DFUTPR - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC DFUUNCSTRDATA_DFURMPARAM_FK

DFUUNCONSTRDATA - DMDUNIT - DMDGROUP - LOC DFURMPARAM - DMDUNIT - DMDGROUP - LOC

DFUVENDORCOST_FK DFUVENDORCOST - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

DFUVIEW_ALLOCCALPROFILE_FK1

DFUVIEW - ALLOCCALPROFILE ALLOCCALPROFILE - ALLOCCALPROFILE

DFUVIEW_CAL_FK1 DFUVIEW - ALLOCCAL CAL - CAL DFUVIEW_DDRPROFILE_FK1 DFUVIEW - DDRPARAMPROFILENAME DDRPARAMPROFILE -

DDRPARAMPROFILENAME

DFUVIEW_DMDGROUP_FK1 DFUVIEW - DMDGROUP DMDGROUP - DMDGROUP DFUVIEW_DMDUNIT_FK1 DFUVIEW - DMDUNIT DMDUNIT - DMDUNIT DFUVIEW_LOC_FK1 DFUVIEW - LOC LOC - LOC DFUVIEW_PRICEPROFILE_FK1

DFUVIEW - PRICEPROFILENAME PRICEPROFILE - PRICEPROFILENAME

DFUVWEVNTMAP_MOVINEVN DFUMOVINGEVENTMAP - MOVINGEVENT MOVINGEVENT - MOVINGEVENT


Table Relationships



T_FK1 DFU_CAL_FK1 DFU - DMDCAL CAL - CAL DFU_DFUATTRIBGROUP_FK DFU - DFUATTRIBGROUP DFUATTRIBGROUP - DFUATTRIBGROUP DFU_DFUVIEW_FK1 DFU - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT -

DMDGROUP - LOC DFU_DMDGROUP_FK1 DFU - DMDGROUP DMDGROUP - DMDGROUP DFU_DMDUNIT_FK1 DFU - DMDUNIT DMDUNIT - DMDUNIT DFU_LOC_FK1 DFU - LOC LOC - LOC DFU_MASK_FK1 DFU - MASK MASK - MASK DFU_MODEL_FK1 DFU - MODEL MODEL - MODEL DISTREQUIREMENT_SKU_FK1

DISTREQUIREMENT - ITEM - DEST SKU - ITEM - LOC

DISTREQUIREMENT_SKU_FK2

DISTREQUIREMENT - ITEM - SOURCE SKU - ITEM - LOC

DMDUNITPRCREL_DMDUNIT_FK

DMDUNITPRICERELATION

- DMDUNIT DMDUNIT - DMDUNIT

DMDUNITPRCREL_IMPACTDMDUNIT_FK

DMDUNITPRICERELATION

- IMPACTINGDMDUNIT DMDUNIT - DMDUNIT

DMDUNIT_UOM_FK1 DMDUNIT - UOM UOM - UOM DMDUNIT_WDDCATEGORY_FK1

DMDUNIT - WDDCATEGORY WDDCATEGORY - WDDCATEGORY

DMDVAR_SKU_FK1 DMDVAR - ITEM - LOC SKU - ITEM - LOC DPP_MRMCFVAL MRMDFUCAUSALFACTO

R - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC DYNDEPSCR_NETWRK_FK DYNDEPSRC - SOURCE - TRANSMODE - DEST NETWORK - SOURCE -

TRANSMODE - DEST DYNDEPSRC_CAL_FK1 DYNDEPSRC - ARRIVCAL CAL - CAL DYNDEPSRC_CAL_FK2 DYNDEPSRC - SHIPCAL CAL - CAL DYNDEPSRC_CAL_FK3 DYNDEPSRC - REVIEWCAL CAL - CAL DYNDEPSRC_SKU_FK1 DYNDEPSRC - ITEM - SOURCE SKU - ITEM - LOC DYNDEPSRC_SKU_FK2 DYNDEPSRC - ITEM - DEST SKU - ITEM - LOC


Table Relationships



DYNDEPSRC_TRANSMODE_FK1

DYNDEPSRC - TRANSMODE TRANSMODE - TRANSMODE

E3FCSTTRACK_SKU_FK1 E3FCSTTRACK - ITEM - SKULOC SKU - ITEM - LOC EVENT_EVENTTYPE_FK1 EVENT - EVENTTYPE EVENTTYPE - EVENTTYPE EXCEPTIONMAP_DEFINITION_FK2

PRICERULEEXCEPTIONMAP

- RULENAME PRICERULEDEFINITION

- RULENAME

EXCEPTIONMAP_EXCEPTION_FK1

PRICERULEEXCEPTIONMAP

- EXCEPTIONNAME PRICERULEEXCEPTION

- EXCEPTIONNAME

EXTRAUSAGE_SKU_FK1 EXTRAUSAGE - ITEM - LOC SKU - ITEM - LOC FCSTACCROOTCAUSES_DFU_FK1

FCSTACCROOTCAUSES - DMDUNIT - DMDGROUP - LOC - MODEL


FCSTDRAFT_DFU_FK1 FCSTDRAFT - DMDUNIT - DMDGROUP - LOC - MODEL


FCSTORDERSTATUS_FCSTORDER_FK1

FCSTORDERSTATUS - ITEM - LOC - SEQNUM FCSTORDER - ITEM - LOC - SEQNUM

FCSTORDER_SKU_FK1 FCSTORDER - ITEM - LOC SKU - ITEM - LOC FCSTPERFSTATIC_DFU_FK1 FCSTPERFSTATIC - DMDUNIT - DMDGROUP - LOC -



FCSTRCA_FCSTRCAMASTER_FK2

FCSTACCROOTCAUSES - ROOTCAUSEID FCSTACCROOTCAUSEMASTER

- ROOTCAUSEID

FCST_DFUVIEW_FK1 FCST - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

FITTEDHIST_DFU_FK1 FITTEDHIST - DMDUNIT - DMDGROUP - LOC - MODEL


FK_CANDMKTG PROMOCANDIDATEMKTGINSTRVALUE

- REQUESTID PROMOCANDIDATEREQUEST

- REQUESTID

FK_CANDRULEPARAM_RULEBASE

PROMOCANDIDATERULEPARAM

- RULENAME PROMOCANDIDATERULE

- RULENAME

FK_CANDRULEVALREQ_REQ PROMOCANDIDATERULEPARAMVAL


- REQUESTID


Table Relationships



FK_DFUPRICECOEF DFUPRICECOEF - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

FK_DFUPRICESENSITIVITY DFUPRICESENSITIVITY - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

FK_OFFERREQUEST PROMOCANDIDATEOFFERMAP

- PROMOTION PROMOTION - PROMOTION

FK_PARAMVAL_PARAM PROMOCANDIDATERULEPARAMVAL

- PARAMNAME - RULENAME PROMOCANDIDATERULEPARAM

- PARAMNAME - RULENAME

FK_REQMETRICS PROMOCANDIDATEDFU - REQUESTID PROMOCANDIDATEREQUEST

- REQUESTID

FK_REQUESTOFFER PROMOCANDIDATEOFFERMAP


- REQUESTID

FK_RQSTCRITERIA PROMOCANDIDATEDFU_CRITERIA


- REQUESTID

FK_RULEPARVAL_RULE PROMOCANDIDATERULEPARAMVAL

- RULENAME PROMOCANDIDATERULE

- RULENAME

FK_SSBAND_SKU SSBAND - ITEM - LOC SKU - ITEM - LOC GEOCOORDDT_GEOCOORD_FK1

GEOCOORDINATES_DETAIL

- POSTALCODE - COUNTRY GEOCOORDINATES - POSTALCODE - COUNTRY

HISTFCSTEVENTS_DFU_FK1 HISTFCSTEVENTS - DMDUNIT - DMDGROUP - LOC - MODEL


HISTFCST_DFU_FK1 HISTFCST - DMDUNIT - DMDGROUP - LOC - MODEL


HISTPURCHACTUAL_SKU_FK1

HISTPURCHACTUAL - ITEM - LOC SKU - ITEM - LOC

HISTPURCHPLAN_SKU_FK3 HISTPURCHPLAN - ITEM - LOC SKU - ITEM - LOC HISTTRANSACTUAL_SKU_FK1

HISTTRANSACTUAL - ITEM - SOURCE SKU - ITEM - LOC

HISTTRANSACTUAL_SKU_FK2

HISTTRANSACTUAL - ITEM - DEST SKU - ITEM - LOC

HISTTRANSACTUAL_TRANSMODE_FK3

HISTTRANSACTUAL - TRANSMODE TRANSMODE - TRANSMODE


Table Relationships



HISTTRANSPLAN_SKU_FK1 HISTTRANSPLAN - ITEM - SOURCE SKU - ITEM - LOC HISTTRANSPLAN_SKU_FK2 HISTTRANSPLAN - ITEM - DEST SKU - ITEM - LOC HISTTRANSPLAN_TRANSMODE_FK3

HISTTRANSPLAN - TRANSMODE TRANSMODE - TRANSMODE

HIST_DFUVIEW_FK1 HIST - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

HIST_HISTSTREAM_FK1 HIST - HISTSTREAM HISTSTREAM - HISTSTREAM HOLTWINTERSPARAM_DFU_FK

HOLTWINTERSPARAM - DMDUNIT - DMDGROUP - LOC - MODEL


HOLTWINTERSSTATS_DFU_FK

HOLTWINTERSSTATS - DMDUNIT - DMDGROUP - LOC - MODEL


IGNOREDDMD_SKU_FK1 IGNOREDDMD - ITEM - LOC SKU - ITEM - LOC IMPDEPDMDSTATIC_SCHEDRCPTS_FK1

IMPDEPDMDSTATIC - PARENT - LOC - PARENTSCHEDDATE - PARENTEXPDATE - STARTDATE - SEQNUM

SCHEDRCPTS - ITEM - LOC - SCHEDDATE - EXPDATE - STARTDATE - SEQNUM

IMPDEPDMDSTATIC_SKU_FK1

IMPDEPDMDSTATIC - ITEM - LOC SKU - ITEM - LOC

IMPRESLOADDETAIL_RES_FK1

IMPRESLOADDETAIL - RES RES - RES

IMPRESLOADDETAIL_SCHEDRCPTS_FK

IMPRESLOADDETAIL - ITEM - LOC - SCHEDDATE - EXPDATE - STARTDATE - SEQNUM


IMPRESLOADDETAIL_SKU_FK1

IMPRESLOADDETAIL - ITEM - LOC SKU - ITEM - LOC

INDDMDLINK_LOC_FK1 INDDMDLINK - LOC LOC - LOC INDDMDLINK_SKU_FK1 INDDMDLINK - DMDITEM - DMDLOC SKU - ITEM - LOC INVENTORY_SKU_FK1 INVENTORY - ITEM - LOC SKU - ITEM - LOC IPOFUNDPERF_IPOFUND_FK1 IPOFUNDPERFORMANC - FUNDNAME IPOFUND - FUNDNAME JDA Demand Management Foundation Reference Guide 303 © 1997 - 2014 JDA Software Group, Inc.- Confidential

Table Relationships



E IPOFUNDPERF_IPOPLANSTAT_FK1

IPOFUNDPERFORMANCE

- PLANNAME IPOPLANSTAT - PLANNAME

IPOFUNDPRD_IPOFUND_FK1 IPOFUNDPERIOD - FUNDNAME IPOFUND - FUNDNAME IPOGRAPH_IPOPLANSTAT_FK1

IPOGRAPH - PLANNAME IPOPLANSTAT - PLANNAME

IPOGROUPERF_IPOGROUP_FK1

IPOGROUPPERFORMANCE

- GROUPNAME IPOGROUP - GROUPNAME

IPOGROUPTARGET_IPOGROUP_FK1

IPOGROUPTARGET - GROUPNAME IPOGROUP - GROUPNAME

IPOGRPPERF_IPOPLANSTAT_FK1

IPOGROUPPERFORMANCE


IPOOPSSYSPERF_IPOPLANSTAT_FK1

IPOOPSSYSTEMPERFORMANCE


IPOOPSSYSPERF_OPSSYS_FK1

IPOOPSSYSTEMPERFORMANCE

- OPSSYSTEM - LOC OPSSYSTEM - OPSSYSTEM - LOC

IPOPLANSTAT_CAL_FK1 IPOPLANSTAT - CAL CAL - CAL IPOPROJ_IPOFUND_FK1 IPOPROJ - FUNDNAME IPOFUND - FUNDNAME IPOSKUCONS_SKUIPOPARAM_FK1

IPOSKUCONSTRAINT - ITEM - LOC SKUIPOPARAM - ITEM - LOC

IPOSKUPERF_IPOPLANSTAT_FK1

IPOSKUPERFORMANCE - PLANNAME IPOPLANSTAT - PLANNAME

IPOSKUPERF_SKUIPOPARAM_FK1

IPOSKUPERFORMANCE - ITEM - LOC SKUIPOPARAM - ITEM - LOC

IPOSTOCKINGPLAN_IPOGROUP_FK1

IPOSTOCKINGPLAN - GROUPNAME IPOGROUP - GROUPNAME

IPOSTOCKINGPLAN_SKUIPOPARAM

IPOSTOCKINGPLAN - ITEM - LOC SKUIPOPARAM - ITEM - LOC

ITEM_UOM_FK1 ITEM - DEFAULTUOM UOM - UOM LANEGROUPCAP_LANEGROUP_FK

LANEGROUPCAP - LANEGROUPID LANEGROUP - LANEGROUPID

LANEGROUPCAP_UOM_FK1 LANEGROUPCAP - UOM UOM - UOM


Table Relationships



LANEGROUP_CAL_FK1 LANEGROUP - TRANSCAL CAL - CAL LEWANDOWSKIPARAM_DFU_FK1

LEWANDOWSKIPARAM - DMDUNIT - DMDGROUP - LOC - MODEL


LEWANDOWSKIPARAM_LEWFACTOR_FK1

LEWANDOWSKIPARAM - LIFECYCLEFACTOR LEWFACTOR - LEWFACTOR


LEWANDOWSKIPARAM - LINEXTFACTOR LEWFACTOR - LEWFACTOR


LEWANDOWSKIPARAM - NONLINEXTFACTOR LEWFACTOR - LEWFACTOR

LEWANDOWSKISEASON_DFU_FK1

SMOOTHSEASON - DMDUNIT - DMDGROUP - LOC - MODEL


LEWANDOWSKISTATS_DFU_FK1

LEWANDOWSKISTATS - DMDUNIT - DMDGROUP - LOC - MODEL


LEWFACTORLIBMAP_LEWFACTCAT_FK1

LEWFACTORLIBMAP - LEWFACTORCATEGORY LEWFACTORCATEGORY

- LEWFACTORCATEGORY

LEWFACTORLIBMAP_LEWFACTLIB_FK1

LEWFACTORLIBMAP - LEWFACTORLIBRARY LEWFACTORLIBRARY - LEWFACTORLIBRARY

LEWFACTORVALUE_LEWFACTOR_FK1

LEWFACTORVALUE - LEWFACTOR LEWFACTOR - LEWFACTOR

LEWFACTOR_CAL_FK1 LEWFACTOR - DMDCAL CAL - CAL LEWFACTOR_LEWFACTCAT_FK1

LEWFACTOR - LEWFACTORCATEGORY LEWFACTORCATEGORY

- LEWFACTORCATEGORY

LIBNAME_FK SEASONPROFILE - LIBNAME SEASONLIB - LIBNAME LIBRARYCATEGORYMAP_FK LIBRARYCATEGORYMAP - CATEGORY ALLOCPROFILECATEG

ORY - CATEGORY

LIBRARYCATEGORYMAP_FK1 LIBRARYCATEGORYMAP - LIBNAME ALLOCPROFILELIB - LIBNAME LINREGPARAM_DFU_FK1 LINREGPARAM - DMDUNIT - DMDGROUP - LOC -




Table Relationships



LINREGSTATS_DFU_FK1 LINREGSTATS - DMDUNIT - DMDGROUP - LOC - MODEL


LOCCOST_COSTCATEGORY_FK1

LOCCOST - CATEGORY COSTCATEGORY - CATEGORY

LOCCOST_COST_FK1 LOCCOST - LOCALCOST COST - COST LOCCOST_COST_FK2 LOCCOST - TIEREDCOST COST - COST LOCCOST_LOC_FK1 LOCCOST - LOC LOC - LOC LOCTYPE_TRANS_LOCTYPE_FK1

LOCTYPE_TRANS - TYPE LOCTYPE - TYPE

LOC_CAL_FK1 LOC - SOURCECAL CAL - CAL LOC_CAL_FK2 LOC - DESTCAL CAL - CAL LOC_CAL_FK3 LOC - WORKINGCAL CAL - CAL LOC_LOCTYPE_FK1 LOC - LOC_TYPE LOCTYPE - TYPE LOC_WDDAREA_FK1 LOC - WDDAREA WDDAREA - WDDAREA LPDMDBANDS_LPLAYER_FK01

LPDMDBANDS - LAYER LPLAYER - LAYER

LTDGROUP_CAL_FK LTDGROUP - ACCUMCAL CAL - CAL LTDGROUP_UOM_FK LTDGROUP - QTYUOM UOM - UOM LTDPERCENT_LTDGROUP_FK LTDPERCENT - LTDGROUP LTDGROUP - LTDGROUP MARGINPRICEANDSLACKPROD_PM_FK

MARGINALPRICEANDSLACKPROD

- PRODUCTIONMETHOD - ITEM - LOC

PRODUCTIONMETHOD - PRODUCTIONMETHOD - ITEM - LOC

MARGINPRICEANDSLACKPROD_SKU_FK

MARGINALPRICEANDSLACKPROD

- OUTPUTITEM - LOC SKU - ITEM - LOC

MARGINPRICEANDSLACKRES_RES_FK

MARGINALPRICEANDSLACKRES

- RES RES - RES

MARGINPRICEANDSLACKSKU_SKU_FK

MARGINALPRICEANDSLACKSKU


MARGINPRICEANDSLACKSRC_SRC_FK

MARGINALPRICEANDSLACKSRCNG

- SOURCING - ITEM - SOURCE - DEST

SOURCING - SOURCING - ITEM - SOURCE - DEST

MASKDATA_MASK_FK1 MASKDATA - MASK MASK - MASK


Table Relationships



MDCANDIDATERULESET_FK1 MDCANDIDATERULESETVAL

- RULESET MDCANDIDATERULESET

- RULESET

MDCANDIDATERULESET_FK2 MDCANDIDATERULESETSTATUS


- RULESET

MDCANDIDATERULESET_FK3 MDDFUCANDIDATERULESET


- RULESET

MDCANDIDATE_FK1 MDCANDIDATE - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

MDCANDRULESET_DFUPP_FK MDDFUCANDIDATERULESET


MDDFUMETRICSFCST_FK1 MDDFUMETRICSFCST - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

MDDFUMETRICSSTATUS_FK1 MDDFUMETRICSSTATUS


MDDFUMETRICSSTATUS_FK2 MDDFUMETRICSSTATUS

- RULESET MDRULESET - RULESET

MDDFUMETRICS_FK1 MDDFUMETRICS - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

MDDFURECDETAIL_FK1 MDDFURECDETAIL - DMDUNIT - DMDGROUP - LOC MDDFUREC - DMDUNIT - DMDGROUP - LOC

MDDFUREC_FK1 MDDFUREC - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

MDDFUREC_FK2 MDDFUREC - RULESET MDRULESET - RULESET MDDFURULESET_FK1 MDDFURULESET - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC MDDFURULESET_FK2 MDDFURULESET - RULESET MDRULESET - RULESET MDRULESETSTATEVAL_FK1 MDRULESETSTATEVAL - RULESET - MDSTATE MDRULESETSTATE - RULESET -

MDSTATE MDRULESETSTATE_CAL_FK1 MDRULESETSTATE - MARKDOWNCAL CAL - CAL MDRULESETSTATE_FK1 MDRULESETSTATE - RULESET MDRULESET - RULESET MDSCENARIODFU_FK1 MDSCENARIODFU - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC MDSCENARIODFU_FK2 MDSCENARIODFU - SCENARIO MDSCENARIO - SCENARIO


Table Relationships



MDSCENARIODFU_FK3 MDSCENARIODFU - RULESET MDRULESET - RULESET MDSCENARIOMETRICSSTATUS_FK1

MDSCENARIOMETRICSSTATUS

- SCENARIO - DMDUNIT - DMDGROUP - LOC

MDSCENARIODFU - SCENARIO - DMDUNIT - DMDGROUP - LOC

MDSCENARIOMETRICSSTATUS_FK2



MDSCENARIOMETRICS_FK1 MDSCENARIOMETRICS - SCENARIO - DMDUNIT - DMDGROUP - LOC



MDSCENARIONODERULESET_FK1

MDSCENARIONODERULESET

- SCENARIO MDSCENARIO - SCENARIO

MDSCENARIONODERULESET_FK2

MDSCENARIONODERULESET


MDSCENARIORECDETAIL_FK1

MDSCENARIORECDETAIL


MDSCENARIOREC - SCENARIO - DMDUNIT - DMDGROUP - LOC

MDSCENARIOREC_FK1 MDSCENARIOREC - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

MDSCENARIOREC_FK2 MDSCENARIOREC - RULESET MDRULESET - RULESET MDSCENARIOREC_FK3 MDSCENARIOREC - SCENARIO - DMDUNIT -

DMDGROUP - LOC MDSCENARIODFU - SCENARIO -

DMDUNIT - DMDGROUP - LOC

MEANVALUEADJ_DFU_FK MEANVALUEADJ - DMDUNIT - DMDGROUP - LOC - MODEL


MODEL_HISTSTREAM_FK1 MODEL - HISTSTREAM HISTSTREAM - HISTSTREAM MOVEVENTDATA_MOVEVENT_FK1

MOVINGEVENTDATA - MOVINGEVENT MOVINGEVENT - MOVINGEVENT

MOVINGAVGPARAM_DFU_FK1

MOVINGAVGPARAM - DMDUNIT - DMDGROUP - LOC - MODEL


MOVINGAVGSTATS_DFU_FK MOVINGAVGSTATS - DMDUNIT - DMDGROUP - LOC - MODEL



Table Relationships



MRMBTCHINPUTVAL_MRMBTCHSTP_FK

MRMBATCHINPUTVAL - BATCHPROCESS - STEPNUM MRMBATCHSTEP - BATCHPROCESS - STEPNUM

MRMBTCHSTP_MRMBTCHPROCESS_FK

MRMBATCHSTEP - BATCHPROCESS MRMBATCHPROCESS - BATCHPROCESS

MRMCF_MRMCFVAL MRMCAUSALFACTORVALUE

- MRMCAUSALFACTOR MRMCAUSALFACTOR - MRMCAUSALFACTOR

MRMCF_MRMDFUCFVAL MRMDFUCAUSALFACTOR

- MRMCAUSALFACTOR MRMCAUSALFACTOR - MRMCAUSALFACTOR

MRMEXPERIMENTGROUP_EXPID__FK1

MRMEXPERIMENTGROUP


MRMEXPERIMENTGROUP_MRMODEL_FK

MRMEXPERIMENTGROUP

- MRMODEL MRMODEL - MRMODEL

MRMEXPERIMENTSUMMARY_MRMEXP

MRMEXPERIMENTSUMMARY


MRMEXPERIMENT_CAL_FK MRMEXPERIMENT - CALENDAR CAL - CAL MRMEXPERIMENT_MAP_FK1 MRMEXPERIMENT - FCSTMAP MAP - MAP MRMEXPERIMENT_MAP_FK2 MRMEXPERIMENT - SEASONMAP MAP - MAP MRMEXPERIMENT_MRMODEL_FK

MRMEXPERIMENT - MRMODEL MRMODEL - MRMODEL

MRMEXPFCST_MRMEXPDFU MRMEXPERIMENTFCST - EXPERIMENTID - DMDUNIT - DMDGROUP - LOC

MRMEXPERIMENTDFU - EXPERIMENTID - DMDUNIT - DMDGROUP - LOC

MRMEXPFCST_MRMEXPSTARTDATE

MRMEXPERIMENTFCST - EXPERIMENTID - STARTDATE MRMEXPERIMENTSUMMARY

- EXPERIMENTID - STARTDATE

MRMEXPMVNGEVNT_MRMEXP_FK1

MRMEXPERIMENTMOVINGEVENT


MRMEXPMVNGEVNT_MVNGEVNT_FK2

MRMEXPERIMENTMOVINGEVENT

- MOVINGEVENT MOVINGEVENT - MOVINGEVENT

MRMEXPRIMNTDFU_DFUPRICEPRM_FK

MRMEXPERIMENTDFU - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

MRMEXPRIMNTDFU_MRMEXPRIMNT_FK

MRMEXPERIMENTDFU - EXPERIMENTID MRMEXPERIMENT - EXPERIMENTID

MRMGROUP_MRMODEL_FK1 MRMGROUP - MRMODEL MRMODEL - MRMODEL


Table Relationships



MSE_SKU_FK1 MSE - ITEM - LOC SKU - ITEM - LOC NBRACKETSKU_NETWORKBRACKET_FK1

NETWORKBRACKETSKU - SOURCE - DEST - TRANSMODE - MAXQTY

NETWORKBRACKET - SOURCE - DEST - TRANSMODE - MAXQTY

NETWORKBRACKETSKU_ITEM_FK2

NETWORKBRACKETSKU - ITEM ITEM - ITEM

NETWORKBRACKET_NETWORK_FK1

NETWORKBRACKET - SOURCE - TRANSMODE - DEST NETWORK - SOURCE - TRANSMODE - DEST

NETWORKBRACKET_UOM_FK2

NETWORKBRACKET - UOM UOM - UOM

NETWORKCAP_NETWORK_FK1

NETWORKCAP - SOURCE - TRANSMODE - DEST NETWORK - SOURCE - TRANSMODE - DEST

NETWORKCAP_UOM_FK1 NETWORKCAP - UOM UOM - UOM NETWORK_CAL_FK1 NETWORK - TRANSCAL CAL - CAL NETWORK_CAL_FK2 NETWORK - SHIPCAL CAL - CAL NETWORK_CAL_FK3 NETWORK - ARRIVCAL CAL - CAL NETWORK_CAL_FK4 NETWORK - ORDERREVIEWCAL CAL - CAL NETWORK_LOC_FK1 NETWORK - SOURCE LOC - LOC NETWORK_LOC_FK2 NETWORK - DEST LOC - LOC NETWORK_TRANSMODE_FK1 NETWORK - TRANSMODE TRANSMODE - TRANSMODE NETWORK_UOM_FK4 NETWORK - DISTANCEUOM UOM - UOM NORMGROUP_FK DFUATTACHRATERELAT

ION - NORMGROUP DFUATTACHRATENOR

M - NORMGROUP

NPITODFUEXPRESSION_LCNAME_FK1

NPITODFUEXPRESSION - LIFECYCLENAME LEWFACTOR - LEWFACTOR

NPITODFU_DMDGROUP_FK2 NPITODFU - DMDGROUP DMDGROUP - DMDGROUP NPITODFU_DMDUNIT_FK1 NPITODFU - DMDUNIT DMDUNIT - DMDUNIT NPITODFU_LCNAME_FK4 NPITODFU - LIFECYCLENAME LEWFACTOR - LEWFACTOR NPITODFU_LOC_FK3 NPITODFU - LOC LOC - LOC NPIVALIDDFU_DMDGROUP_FK1

NPIVALIDDFU - DMDGROUP DMDGROUP - DMDGROUP


Table Relationships



NPIVALIDDFU_DMDUNIT_FK1

NPIVALIDDFU - DMDUNIT DMDUNIT - DMDUNIT

NPIVALIDDFU_LOC_FK1 NPIVALIDDFU - LOC LOC - LOC NPODFUDT_FK1 NPO_DFU_DT - DMD_TYPE NPO_DMD_TYPE - DMD_TYPE NPORSRCDTDMD_FK1 NPO_RESRC_DT_DMD - RESRC_ID - STARTDATE NPO_RESRC_DT - RESRC_ID -

STARTDATE NPORSRCDTDMD_FK2 NPO_RESRC_DT_DMD - DMD_TYPE NPO_DMD_TYPE - DMD_TYPE NPORSRCDTHIST_FK1 NPO_RESRC_DT_HIST - RESRC_ID NPO_RESRC - RESRC_ID NPORSRCDT_FK1 NPO_RESRC_DT - RESRC_ID NPO_RESRC - RESRC_ID NPORSRC_COMPT_WT_FK1 NPO_RESRC_COMPETI

TOR_WGT - RESRC_ID NPO_RESRC - RESRC_ID

NPORSRC_COMPT_WT_FK2 NPO_RESRC_COMPETITOR_WGT

- COMPETITOR_ID NPO_COMPETITOR - COMPETITOR_ID

NPO_CROSS_BKT_PARAM_FK1

NPO_CROSS_BKT_PARAM

- IMPACTING_BKT_ID NPO_BKT - BKT_ID

NPO_CROSS_BKT_PARAM_FK2

NPO_CROSS_BKT_PARAM

- IMPACTED_BKT_ID NPO_BKT - BKT_ID

NPO_DFU_DT_CROSS_PRICE_FK1

NPO_DFU_DT_CROSS_PRICE

- IMPACTING_DFU_ID - STARTDATE

NPO_DFU_DT - DFU_ID - STARTDATE



- IMPACTED_DFU_ID NPO_DFU - DFU_ID



- CROSS_PARAM_ID NPO_CROSS_DFU_PARAM

- CROSS_PARAM_ID

NPO_DFU_DT_FK1 NPO_DFU_DT - DFU_ID NPO_DFU - DFU_ID NPO_DFU_DT_FK2 NPO_DFU_DT - PARAM_ID NPO_DFU_PARAM - PARAM_ID NPO_DFU_DT_FK3 NPO_DFU_DT - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT -

DMDGROUP - LOC NPO_DFU_DT_INTERVAL_FK1

NPO_DFU_DT_INTERVAL

- DFU_ID - STARTDATE NPO_DFU_DT - DFU_ID - STARTDATE

NPO_DFU_DT_INTERVAL_FK2

NPO_DFU_DT_INTERVAL


NPO_DFU_DT_INTERVAL_HI NPO_DFU_DT_INTERV - DFU_ID NPO_DFU - DFU_ID


Table Relationships



ST_FK1 AL_HIST NPO_DFU_DT_INTERVAL_REC_FK1

NPO_DFU_DT_INTERVAL_REC


NPO_DFU_DT_PRICE_BKT_FK1

NPO_DFU_DT_PRICE_BKT




- BKT_ID NPO_BKT - BKT_ID



- PRICE_POINT_ID NPO_PRICE_PT - PRICE_POINT_ID

NPO_DFU_DT_REC_FK1 NPO_DFU_DT_REC - DFU_ID - STARTDATE NPO_DFU_DT - DFU_ID - STARTDATE

NPO_DFU_DT_REC_HIST_FK1

NPO_DFU_DT_REC_HIST


NPO_DFU_PKG_DT_MAP_FK1 NPO_DFU_PKG_DT_MAP

- DFU_ID - DFU_STARTDATE NPO_DFU_DT - DFU_ID - STARTDATE

NPO_DFU_PKG_DT_MAP_FK2 NPO_DFU_PKG_DT_MAP

- PKG_ID - PKG_STARTDATE NPO_PKG_DT - PKG_ID - STARTDATE

NPO_OPT_GROUP_FK1 NPO_OPT_GROUP - RESRC_ID NPO_RESRC - RESRC_ID NPO_PKG_BKT_PARAM_FK1 NPO_PKG_BKT_PARAM - PKG_ID NPO_PKG - PKG_ID NPO_PKG_BKT_PARAM_FK2 NPO_PKG_BKT_PARAM - BKT_ID NPO_BKT - BKT_ID NPO_PKG_CAL_PARAM_FK1 NPO_PKG_CAL_PARAM - PKG_ID NPO_PKG - PKG_ID NPO_PKG_COMPETITOR_MAP_FK1

NPO_PKG_COMPETITOR_MAP

- PKG_ID NPO_PKG - PKG_ID

NPO_PKG_COMPETITOR_MAP_FK2

NPO_PKG_COMPETITOR_MAP


NPO_PKG_COMPETITOR_WGT_FK1

NPO_PKG_COMPETITOR_WGT







- PKG_ID - COMPETITOR_ID NPO_PKG_COMPETITOR_MAP

- PKG_ID - COMPETITOR_ID

NPO_PKG_DT_FK1 NPO_PKG_DT - PKG_ID NPO_PKG - PKG_ID


Table Relationships



NPO_PKG_DT_HIST_FK1 NPO_PKG_DT_HIST - PKG_ID NPO_PKG - PKG_ID NPO_PKG_DT_INTERVAL_FK1

NPO_PKG_DT_INTERVAL

- PKG_ID - STARTDATE NPO_PKG_DT - PKG_ID - STARTDATE

NPO_PKG_DT_INTERVAL_HIST_FK1

NPO_PKG_DT_INTERVAL_HIST


NPO_PKG_DT_INTERVAL_REC_FK1

NPO_PKG_DT_INTERVAL_REC


NPO_PKG_DT_PP_INTERVAL_REC_FK1

NPO_PKG_DT_PP_INTERVAL_REC


NPO_PKG_DT_PP_INTERVAL_REC_FK2

NPO_PKG_DT_PP_INTERVAL_REC


NPO_PKG_DT_PRICE_PT_FK1 NPO_PKG_DT_PRICE_PT


NPO_PKG_DT_PRICE_PT_FK2 NPO_PKG_DT_PRICE_PT

- PKG_PRICE_POINT_ID NPO_PRICE_PT - PRICE_POINT_ID

NPO_PKG_DT_PRICE_PT_REC_FK1

NPO_PKG_DT_PRICE_PT_REC


NPO_PKG_DT_PRICE_PT_REC_FK2

NPO_PKG_DT_PRICE_PT_REC


NPO_PKG_DT_PRICE_SHOP_FK1

NPO_PKG_DT_PRICE_SHOP


NPO_PKG_DT_PRICE_SHOP_FK2



NPO_PKG_DT_PRICE_SHOP_HIST_FK1

NPO_PKG_DT_PRICE_SHOP_HIST


NPO_PKG_DT_PRICE_SHOP_HIST_FK2

NPO_PKG_DT_PRICE_SHOP_HIST


NPO_PKG_DT_PRICE_SHOP_PKG


- PROXY_PKG_ID NPO_PKG - PKG_ID

NPO_PKG_DT_UPGRADE_FK1 NPO_PKG_DT_UPGRADE

- FROM_PKG_ID NPO_PKG - PKG_ID

NPO_PKG_DT_UPGRADE_FK2 NPO_PKG_DT_UPGRADE

- TO_PKG_ID NPO_PKG - PKG_ID


Table Relationships



NPO_PKG_PRICE_PRIORITY_FK


- PRICE_PRIORITY_SEQ NPO_PRICE_SHOP_PRIORITY

- PRICE_PRIORITY_SEQ

NPO_RESRC_BKT_PARAM_FK1

NPO_RESRC_BKT_PARAM

- RESRC_ID NPO_RESRC - RESRC_ID

NPO_RESRC_BKT_PARAM_FK2

NPO_RESRC_BKT_PARAM


NPO_RESRC_CAL_PARAM_FK1

NPO_RESRC_CAL_PARAM


NPO_RESRC_COMPETITOR_MAP_FK1

NPO_RESRC_COMPETITOR_MAP


NPO_RESRC_COMPETITOR_MAP_FK2

NPO_RESRC_COMPETITOR_MAP


NPO_RESRC_DT_BKT_REC_FK1

NPO_RESRC_DT_BKT_REC


NPO_RESRC_DT_BKT_REC_FK2

NPO_RESRC_DT_BKT_REC


NPO_RESRC_DT_INTERVAL_FK1

NPO_RESRC_DT_INTERVAL

- RESRC_ID - STARTDATE NPO_RESRC_DT - RESRC_ID - STARTDATE

NPO_RESRC_DT_INTERVAL_HIST_FK1

NPO_RESRC_DT_INTERVAL_HIST


NPO_RESRC_DT_INV_FK1 NPO_RESRC_DT_INV - RESRC_ID - STARTDATE NPO_RESRC_DT - RESRC_ID - STARTDATE

NPO_RESRC_DT_INV_FK2 NPO_RESRC_DT_INV - INV_TYPE NPO_INV_TYPE - INV_TYPE NPO_RESRC_DT_PP_INTL_REC_FK1

NPO_RESRC_DT_PP_INTRVL_REC


NPO_RESRC_DT_PP_INTL_REC_FK2

NPO_RESRC_DT_PP_INTRVL_REC


NPO_RESRC_DT_PRICE_PT_FK1

NPO_RESRC_DT_PRICE_PT


NPO_RESRC_DT_PRICE_PT_FK2

NPO_RESRC_DT_PRICE_PT


NPO_RESRC_DT_PRICE_PT_REC_FK2

NPO_RESRC_DT_PRICE_PT_REC



Table Relationships



NPO_RESRC_DT_PRICE_SHOP_FK1

NPO_RESRC_DT_PRICE_SHOP







- RESRC_ID - COMPETITOR_ID NPO_RESRC_COMPETITOR_MAP

- RESRC_ID - COMPETITOR_ID

NPO_RESRC_DT_REC_INTERVAL_FK1

NPO_RESRC_DT_REC_INTERVAL


NPO_RESRC_GROUP_PARAM_FK

NPO_RESRC_GROUP_PARAM


NPO_RESRC_PKG_DT_MAP_FK1

NPO_RESRC_PKG_DT_MAP

- RESRC_ID - RESRC_STARTDATE NPO_RESRC_DT - RESRC_ID - STARTDATE

NPO_RESRC_PKG_DT_MAP_FK2

NPO_RESRC_PKG_DT_MAP

- PKG_ID - PKG_STARTDATE NPO_PKG_DT - PKG_ID - STARTDATE

NPO_RESR_DT_PRICE_PT_REC_FK1

NPO_RESRC_DT_PRICE_PT_REC


NPO_USER_EVENT_FK1 NPO_USER_EVENT - RESRC_ID NPO_RESRC - RESRC_ID OGBRACKETSKU_OGBRACKET_FK1

ORDERGROUPBRACKETSKU

- ORDERGROUP - ORDERGROUPMEMBER - MAXQTY

ORDERGROUPBRACKET

- ORDERGROUP - ORDERGROUPMEMBER - MAXQTY

OGBRACKET_ORDERGROUP_FK1

ORDERGROUPBRACKET - ORDERGROUP ORDERGROUP - ORDERGROUP

OGM_ORDERGROUPPARAM_FK1

ORDERGROUPMEMBER - ORDERGROUPPARAM ORDERGROUPPARAM - ORDERGROUPPARAM

OGM_ORDERGROUP_FK1 ORDERGROUPMEMBER - ORDERGROUP ORDERGROUP - ORDERGROUP OGM_TRANSMODE_FK1 ORDERGROUPMEMBER - TRANSMODE TRANSMODE - TRANSMODE OPSSYSPART_OPSSYS_FK2 OPSSYSTEMPART - OPSSYSTEM - LOC OPSSYSTEM - OPSSYSTEM - LOC OPSSYSPART_SKUIPOPARAM_FK1

OPSSYSTEMPART - ITEM - LOC SKUIPOPARAM - ITEM - LOC

OPSSYS_IPOGROUP_FK1 OPSSYSTEM - GROUPNAME IPOGROUP - GROUPNAME OPSSYS_LOC_FK2 OPSSYSTEM - LOC LOC - LOC OPTIMCOST_OPTIMEXCEPTION_FK1

OPTIMIZERCOSTEXCEPTION

- SERVICEID - FUNCTIONNUM - EXCEPTIONID

OPTIMIZEREXCEPTION

- SERVICEID - FUNCTIONNUM -


Table Relationships



EXCEPTIONID OPTIMIZERCOSTEXCEPTION_COST_FK

OPTIMIZERCOSTEXCEPTION

- COST COST - COST

OPTIMIZERLTDMAP_LTDGROUP_FK

OPTIMIZERLTDMAP - LTDGROUP LTDGROUP - LTDGROUP

OPTIMIZERLTDMAP_UOM_FK OPTIMIZERLTDMAP - QTYUOM UOM - UOM OPTIMIZERRESEXCEPTION_RES_FK1

OPTIMIZERRESEXCEPTION

- RES RES - RES

OPTIMIZERRESSTAT_RES_FK1

OPTIMIZERRESSTAT - RES RES - RES

OPTIMIZERSETUPEXCEPTION_FK2

OPTIMIZERSETUPEXCEPTION

- SETUP SETUP - SETUP

OPTIMIZERSETUPEXCEPTION_FK3


- RES RES - RES

OPTIMIZERSKUEXCEPTION_SKU_FK1

OPTIMIZERSKUEXCEPTION


OPTIMIZERSKUSTAT_SKU_FK1

OPTIMIZERSKUSTAT - ITEM - LOC SKU - ITEM - LOC

OPTIMPRODEXCEPT_PRODMETHOD_FK1

OPTIMIZERPRODEXCEPTION



OPTIMPROD_OPTIMEXCEPTION_FK1

OPTIMIZERPRODEXCEPTION


OPTIMIZEREXCEPTION


OPTIMRES_OPTIMEXCEPTION_FK1

OPTIMIZERRESEXCEPTION


OPTIMIZEREXCEPTION


OPTIMSETUP_OPTIMEXCEPTION_FK1



OPTIMIZEREXCEPTION


OPTIMSKU_OPTIMEXCEPTION_FK1

OPTIMIZERSKUEXCEPTION


OPTIMIZEREXCEPTION


OPTIMSOURCINGEXC_SOUR OPTIMIZERSOURCINGE - SOURCING - ITEM - SOURCE - SOURCING - SOURCING - ITEM -


Table Relationships



CING_FK1 XCEPTION DEST SOURCE - DEST OPTIMSOURC_OPTIMEXCEPTION_FK1

OPTIMIZERSOURCINGEXCEPTION


OPTIMIZEREXCEPTION


OPTOBJECTIVESEQDETAIL_FK_01

OPTOBJECTIVESEQDETAIL

- OPTIONSETID - SEQNUM OPTOBJECTIVESEQ - OPTIONSETID - SEQNUM

OPTOBJECTIVESEQ_FK_01 OPTOBJECTIVESEQ - OPTIONSETID OPTOBJECTIVESET - OPTIONSETID ORDEREXCMSTR_ORDEREXCSUBCAT_FK

ORDEREXCEPTIONMASTER

- SUBCATEGORY ORDEREXCEPTIONSUBCATEGORY

- SUBCATEGORY

ORDEREXCSUBCAT_ORDEREXCCAT_FK

ORDEREXCEPTIONSUBCATEGORY

- CATEGORY ORDEREXCEPTIONCATEGORY

- CATEGORY

ORDERGROUPBRACKETSKU_ITEM_FK2

ORDERGROUPBRACKETSKU

- ITEM ITEM - ITEM

ORDERGROUPBRACKET_UOM_FK2

ORDERGROUPBRACKET - UOM UOM - UOM

ORDERGROUPCAP_ORDERGROUP_FK1

ORDERGROUPCAP - ORDERGROUP ORDERGROUP - ORDERGROUP

ORDERGROUPCAP_UOM_FK1 ORDERGROUPCAP - UOM UOM - UOM ORDERGROUPPARAM_CAL_FK1

ORDERGROUPPARAM - TRANSCAL CAL - CAL

ORDERGROUPPARAM_CAL_FK2

ORDERGROUPPARAM - SHIPCAL CAL - CAL


ORDERGROUPPARAM - ARRIVCAL CAL - CAL


ORDERGROUPPARAM - ORDERREVIEWCAL CAL - CAL


ORDERGROUPPARAM - SOURCEWORKCAL CAL - CAL


ORDERGROUPPARAM - DESTWORKCAL CAL - CAL

ORDERGROUP_ORDERGROUPPARAM_FK1

ORDERGROUP - ORDERGROUPPARAM ORDERGROUPPARAM - ORDERGROUPPARAM

ORDERGROUP_TRANSMODE_ ORDERGROUP - TRANSMODE TRANSMODE - TRANSMODE


Table Relationships



FK1 ORDERLINK_SKU_FK1 ORDERLINK - ITEM - LOC SKU - ITEM - LOC ORDERSKUDETAIL_ORDERSKU_FK1

ORDERSKUDETAIL - ORDERID - ITEM - DEST ORDERSKU - ORDERID - ITEM - DEST

ORDERSKUTOTAL_ORDERSKU_FK1

ORDERSKUTOTAL - ORDERID - ITEM - DEST ORDERSKU - ORDERID - ITEM - DEST

ORDERSKU_ORDERHEADER_FK1

ORDERSKU - ORDERID ORDERHEADER - ORDERID

ORDERTOTAL_ORDER_FK1 ORDERTOTAL - ORDERID ORDERHEADER - ORDERID PARENTACTIVITY_FK PROMOACTIVITY - PARENTACTIVITYID PROMOACTIVITY - PROMOACTIVITYID PCADETAIL_ITEM_FK1 PCADETAIL - SUBORD ITEM - ITEM PCADETAIL_ITEM_FK2 PCADETAIL - NEWSUBORD ITEM - ITEM PCADETAIL_SKU_FK1 PCADETAIL - ITEM - LOC SKU - ITEM - LOC PCARESULT_SKU_FK1 PCARESULT - ITEM - LOC SKU - ITEM - LOC PDTAUCURVEDATA_PDTAUCURVE_FK1

PDTAUCURVEDATA - PDTAUCURVEID PDTAUCURVE - PDTAUCURVEID

PERSONAHIERARCHYCOLUMNSFK1

PERSONAHIERARCHYCOLUMNS

- PERSONANAME PERSONA - PERSONANAME

PERSONAWORKFLOWACTIONFK1

PERSONAWORKFLOWACTION

- PERSONANAME - WORKFLOWNAME

PERSONAWORKFLOWS


PERSONAWORKFLOWNAVFILTERSFK1

PERSONAWORKFLOWNAVFILTERS

- PERSONANAME PERSONA - PERSONANAME

PERSONAWORKFLOWNAVFILTERSFK2

PERSONAWORKFLOWNAVFILTERS


PERSONAWORKFLOWS


PERSONAWORKFLOWSFK1 PERSONAWORKFLOWS - PERSONANAME PERSONA - PERSONANAME PERSONAWORKFLOWWIDGETFK1

PERSONAWORKFLOWWIDGET


PERSONAWORKFLOWS


PERSONAWORKFLOWWIDGETFK2

PERSONAWORKFLOWWIDGET


PLANARRIV_SKU_FK2 PLANARRIV - ITEM - DEST SKU - ITEM - LOC PLANARRIV_SKU_FK3 PLANARRIV - ITEM - SOURCE SKU - ITEM - LOC PLANARRIV_TRANSMODE_FK PLANARRIV - TRANSMODE TRANSMODE - TRANSMODE


Table Relationships



1 PLANORDER_SKU_FK1 PLANORDER - ITEM - LOC SKU - ITEM - LOC PLANPEGCOLS1 PLANPEGCOLS - PEGNAME PLANPEGINFO - PEGNAME PLANPROXYINVENTORY_SKU_FK1

PLANPROXYINVENTORY - ITEM - LOC SKU - ITEM - LOC

PLANPROXYINVENTORY_SKU_FK2

PLANPROXYINVENTORY - ALTITEM - LOC SKU - ITEM - LOC

PLANPURCH_SKU_FK1 PLANPURCH - ITEM - LOC SKU - ITEM - LOC PLANSHIP_SKU_FK1 PLANSHIP - ITEM - SOURCE SKU - ITEM - LOC PORANGE_LOC_FK1 PORANGE - LOC LOC - LOC PRAVAILGRMAP_DFUPRPARAM_FK2

PRICEAVAILGROUPMAP - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

PRAVAILGRMAP_PRAVAILGR_FK1

PRICEAVAILGROUPMAP - PRICEAVAILGROUP PRICEAVAILGROUP - PRICEAVAILGROUP

PRAVAILGRVAL_PRAVAILGR_FK1

PRICEAVAILGROUPVAL - PRICEAVAILGROUP PRICEAVAILGROUP - PRICEAVAILGROUP

PRCRELTNDETAIL_PRCRELTN_FK1

PRICERELATIONDETAIL - RELATIONNAME PRICERELATION - RELATIONNAME

PRCRULEATRIBCMPVAL_RULENM_FK

PRICERULEATTRIBCOMPVAL


- RULENAME

PRCRULECPI_PRCRULEDEF_FK1

PRICERULECOMPPRICEINDEX


- RULENAME

PRCSCENARIO_PRCSCENARIO_FK1

PRICESCENARIORULECONFLICT

- PRICESCENARIO PRICESCENARIO - PRICESCENARIO

PRDFAMILYCHGOVER_PRDFAMILY_FK1

PRODUCTIONFAMILYCHGOVER

- FROMFAMILY PRODUCTIONFAMILY - PRODFAMILY

PRDFAMILYCHGOVER_PRDFAMILY_FK2


- TOFAMILY PRODUCTIONFAMILY - PRODFAMILY

PRDFAMLYSKULOAD_PRODFAMILY_FK

PRODUCTIONFAMILYSKULOAD

- PRODFAMILY PRODUCTIONFAMILY - PRODFAMILY

PRDUCTIONFAMILYSKULOAD_RES_FK

PRODUCTIONFAMILYSKULOAD

- RES RES - RES


Table Relationships



PRICELIST_ITEM_FK1 PRICELIST - ITEM ITEM - ITEM PRICEPROFILE_CURRENCY_FK1

PRICEPROFILE - BASECURRENCY CURRENCY - CURRENCY

PRICEPROFVAL_PRICEPROF_FK1

PRICEPROFILEVAL - PRICEPROFILENAME PRICEPROFILE - PRICEPROFILENAME

PRICERULEDEFINITION_FK PRICERULELASTDIGITVAL


- RULENAME

PRICERULERANGEVAL_R01 PRICERULERANGEVAL - RULENAME PRICERULEDEFINITION

- RULENAME

PRICERULESELATTRIB_RULENAME_FK

PRICERULESELATTRIB - RULENAME PRICERULEDEFINITION

- RULENAME

PRICESCENARIODFUVIOLATION_FK1

PRICESCENARIODFUVIOLATION





- RULENAME






- DMDGROUP DMDGROUP - DMDGROUP



- LOC LOC - LOC

PRICESCENARIOEXCPTN_PRCSCN_FK

PRICESCENARIOEXCEPTION


PRICESCENARIORULESETMAP_FK1

PRICESCENARIORULESETMAP


PRICESCENARIOVIOLATION_FK1

PRICESCENARIOVIOLATION


PRICESCENARIOVIOLATION_FK2

PRICESCENARIOVIOLATION


- RULENAME

PRMETSCENMAP_PRMETSCEN_FK1

PRICEMETRICSCENARIOMAP

- METRICSCENARIO PRICEMETRICSCENARIO

- METRICSCENARIO

PRMTNRULESETMAP_PRMTN_FK1

PROMOTIONRULESETMAP



Table Relationships



PRMTNRULESETMAP_PRRULESET_FK2

PROMOTIONRULESETMAP

- RULESETNAME PRICERULESET - RULESETNAME

PROCESSMARKDOWNMETRICS_FK1

PROCESSMARKDOWNMETRICS


PROCESSOPTSVALUES_FK1 PROCESSOPTSVALUES - OPTIONNAME - UVP - USERID - SCOPE - ALGNAME

PROCESSOPTS - OPTIONNAME - UVP - USERID - SCOPE - ALGNAME

PRODCONSTRAINT_CONSTRCAT_FK1

PRODUCTIONCONSTRAINT

- CATEGORY CONSTRAINTCATEGORY

- CATEGORY

PRODCONSTRAINT_PRODMETHOD_FK1




PRODCONSTRAINT_UOM_FK1


- QTYUOM UOM - UOM

PRODCOST_COSTCATEGORY_FK1

PRODUCTIONCOST - CATEGORY COSTCATEGORY - CATEGORY

PRODCOST_PRODMETHOD_FK1

PRODUCTIONCOST - PRODUCTIONMETHOD - ITEM - LOC


PRODFAMILYCHGOVER_RES_FK


- RES RES - RES

PRODFAMILYLOAD_PRODFAMILY_FK

PRODUCTIONFAMILYLOAD


PRODFAMILYLOAD_PRODFAMILY_FK2

PRODUCTIONFAMILYLOAD

- CHGOVERPRODFAMILY PRODUCTIONFAMILY - PRODFAMILY

PRODFAMILYLOAD_RES_FK PRODUCTIONFAMILYLOAD

- RES RES - RES

PRODFAMILYRESMAP_PRODFAMILY_FK

PRODUCTIONFAMILYRESMAP


PRODITEMPROJ_ITEM_FK1 PRODITEMPROJ - PRODUCTIONMETHODITEM ITEM - ITEM PRODITEMPROJ_UOM_FK1 PRODITEMPROJ - NUMERATORUOM UOM - UOM PRODITEMPROJ_UOM_FK2 PRODITEMPROJ - DENOMINATORUOM UOM - UOM PRODITEMPROJ_UOM_FK3 PRODITEMPROJ - ADDITIONALUOM UOM - UOM


Table Relationships



PRODLEADTIME_PRODMETHOD_FK1

PRODUCTIONLEADTIME



PRODMETHOD_FINISHCAL_FK

PRODUCTIONMETHOD - FINISHCAL CAL - CAL

PRODMETHOD_LEADTIMECAL_FK

PRODUCTIONMETHOD - LEADTIMECAL CAL - CAL

PRODMETRIC_METRICCATEGORY_FK1

PRODUCTIONMETRIC - CATEGORY METRICCATEGORY - CATEGORY

PRODMETRIC_PRODMETHOD_FK1

PRODUCTIONMETRIC - PRODUCTIONMETHOD - ITEM - LOC


PRODPENALTY_PENALTYCAT_FK1

PRODUCTIONPENALTY - CATEGORY PENALTYCATEGORY - CATEGORY

PRODPENALTY_PRODMETHOD_FK1

PRODUCTIONPENALTY - PRODUCTIONMETHOD - ITEM - LOC


PRODPENALTY_UOM_FK1 PRODUCTIONPENALTY - QTYUOM UOM - UOM PRODPENALTY_UOM_FK2 PRODUCTIONPENALTY - CURRENCYUOM UOM - UOM PRODPROJ_PRODUCTIONMETHOD_FK1

PRODPROJ - PRODUCTIONMETHOD - ITEM - LOC


PRODPROJ_SKU_FK1 PRODPROJ - ITEM - LOC SKU - ITEM - LOC PRODPROJ_UOM_FK1 PRODPROJ - NUMERATORUOM UOM - UOM PRODPROJ_UOM_FK2 PRODPROJ - DENOMINATORUOM UOM - UOM PRODPROJ_UOM_FK3 PRODPROJ - ADDITIONALUOM UOM - UOM PRODREQUIREMENT_SKU_FK1

PRODREQUIREMENT - ITEM - LOC SKU - ITEM - LOC

PRODRESMETRIC_METRICCAT_FK

PRODUCTIONRESMETRIC

- CATEGORY METRICCATEGORY - CATEGORY

PRODRESMETRIC_PRODMETHOD_FK

PRODUCTIONRESMETRIC




Table Relationships



PRODRESPROJ_PRODMETHOD_FK1

PRODRESPROJ - PRODUCTIONMETHOD - ITEM - LOC


PRODRESPROJ_RES_FK1 PRODRESPROJ - RES RES - RES PRODRESPROJ_UOM_FK1 PRODRESPROJ - NUMERATORUOM UOM - UOM PRODRESPROJ_UOM_FK2 PRODRESPROJ - DENOMINATORUOM UOM - UOM PRODRESPROJ_UOM_FK3 PRODRESPROJ - ADDITIONALUOM UOM - UOM PRODSTEP_UOM_FK1 PRODUCTIONSTEP - QTYUOM UOM - UOM PRODTARGET_PRODMETHOD_FK1

PRODUCTIONTARGET - PRODUCTIONMETHOD - ITEM - LOC


PRODUCTIONCONSTRAINT_SKU_FK1



PRODUCTIONCOST_COST_FK1

PRODUCTIONCOST - LOCALCOST COST - COST

PRODUCTIONCOST_COST_FK2

PRODUCTIONCOST - TIEREDCOST COST - COST

PRODUCTIONMETHOD_SKU_FK1

PRODUCTIONMETHOD - ITEM - LOC SKU - ITEM - LOC

PRODUCTIONMETRIC_CURRUOM_FK

PRODUCTIONMETRIC - CURRENCYUOM UOM - UOM

PRODUCTIONMETRIC_QTYUOM_FK

PRODUCTIONMETRIC - QTYUOM UOM - UOM

PRODUCTIONMETRIC_SKU_FK1

PRODUCTIONMETRIC - OUTPUTITEM - LOC SKU - ITEM - LOC

PRODUCTIONPENALTY_SKU_FK1

PRODUCTIONPENALTY - OUTPUTITEM - LOC SKU - ITEM - LOC

PRODUCTIONRESMETRIC_CURRUOM_FK

PRODUCTIONRESMETRIC

- CURRENCYUOM UOM - UOM

PRODUCTIONRESMETRIC_QTYUOM_FK

PRODUCTIONRESMETRIC

- QTYUOM UOM - UOM

PRODUCTIONRESMETRIC_RES_FK

PRODUCTIONRESMETRIC

- RES RES - RES


Table Relationships



PRODUCTIONSTEP_CAL_FK01

PRODUCTIONSTEP - PRODRATECAL CAL - CAL

PRODUCTIONSTEP_PRODFAMILY_FK

PRODUCTIONSTEP - PRODFAMILY PRODUCTIONFAMILY - PRODFAMILY

PRODUCTIONSTEP_PRODMETHOD_FK1

PRODUCTIONSTEP - PRODUCTIONMETHOD - ITEM - LOC


PRODUCTIONSTEP_RES_FK1 PRODUCTIONSTEP - RES RES - RES PRODUCTIONSTEP_SETUP_FK

PRODUCTIONSTEP - SETUP SETUP - SETUP

PRODUCTIONYIELD_CAL_FK01

PRODUCTIONYIELD - YIELDCAL CAL - CAL

PRODUCTIONYIELD_SKU_FK2

PRODUCTIONYIELD - OUTPUTITEM - LOC SKU - ITEM - LOC

PRODYIELD_PRODMETHOD_FK1

PRODUCTIONYIELD - PRODUCTIONMETHOD - ITEM - LOC


PRODYIELD_UOM_FK1 PRODUCTIONYIELD - QTYUOM UOM - UOM PROFILEDATA_PROFILE_FK1 PROFILEDATA - PROFILE PROFILE - PROFILE PROJORDERSKUDETAIL_SKU_FK1

PROJORDERSKUDETAIL - ORDERID - ITEM - DEST PROJORDERSKU - ORDERID - ITEM - DEST

PROJORDERSKUTOTAL_SKU_FK1

PROJORDERSKUTOTAL - ORDERID - ITEM - DEST PROJORDERSKU - ORDERID - ITEM - DEST

PROJORDERSKU_SUMMARY_FK1

PROJORDERSKU - ORDERID PROJORDERSUMMARY - ORDERID

PROJORDERTOTAL_SUMMARY_FK1

PROJORDERTOTAL - ORDERID PROJORDERSUMMARY - ORDERID

PROJSUMMARYDETAIL_SUMMARY_FK1

PROJORDERSUMMARYDETAIL

- ORDERID PROJORDERSUMMARY - ORDERID

PROMOACTIVITYMAP_FK1 PROMOACTIVITYMAP - PROMOTION PROMOTION - PROMOTION PROMOACTIVITYMAP_FK2 PROMOACTIVITYMAP - PROMOACTIVITYID PROMOACTIVITY - PROMOACTIVITYID PROMOACTIVITYSPACEALLOC_FK1

PROMOACTIVITYSPACEALLOC

- PROMOACTIVITYID PROMOACTIVITY - PROMOACTIVITYID


Table Relationships



PROMOACTIVITYTASK_ACTIVITY_FK

PROMOACTIVITYTASK - PROMOACTIVITYID PROMOACTIVITY - PROMOACTIVITYID

PROMOACTIVITYTYPE_TRANS_FK1

PROMOACTIVITYTYPE_TRANS

- ACTIVITYTYPE PROMOACTIVITYTYPE - ACTIVITYTYPE

PROMOACTMKTINST_MKTGINST_FK2

PROMOACTIVITYMKTGINSTRUMENT

- MKTGINSTRUMENT MKTGINSTRUMENT - MKTGINSTRUMENT

PROMOACTMKTINST_PROMOACT_FK1

PROMOACTIVITYMKTGINSTRUMENT


PROMOACTTASKDEF_ACTTYPE_FK

PROMOACTIVITYTASKDEF

- ACTIVITYTYPE PROMOACTIVITYTYPE - ACTIVITYTYPE

PROMOACTTASKDEF_MKTGINSTR_FK

PROMOACTIVITYTASKDEF


PROMOANALYPRM_PROMO_FK1

PROMOANALYSISPARAMS


PROMOCAMPAIGNACTIVITYID_FK

PROMOCAMPAIGN - PROMOACTIVITYID PROMOACTIVITY - PROMOACTIVITYID

PROMOCANDACTIVITYMAP_FK1

PROMOCANDIDATEACTIVITYMAP


- REQUESTID

PROMOCANDACTIVITYMAP_FK2

PROMOCANDIDATEACTIVITYMAP


PROMODFUATTVAL_PROMODFU_CRI_FK

PROMODFUATTRIBVALUE

- CRITERIAID PROMODFU_CRITERIA - CRITERIA_ID

PROMODFUEXCEPTION_FK1 PROMODFUEXCEPTION - PROMOTION - PARENTEXCEPTION

PROMOEXCEPTION - PROMOTION - EXCEPTION

PROMODFUFCST_IMPORT_FK1

PROMODFUFCST_IMPORT

- PROMOTION PROMOTION_IMPORT - PROMOTION

PROMODFUFCST_PROMOTION_FK1

PROMODFUFCST - PROMOTION PROMOTION - PROMOTION

PROMODFUFILTVAL_PRMDFUFILT_FK1

PROMODFU_FILTER_VALUE

- CRITERIA_ID - FILTER_ID PROMODFU_FILTER - CRITERIA_ID - FILTER_ID

PROMODFURVNUCOGS_PRMTION_FK1

PROMODFUREVENUECOGS


PROMODFUVENDORCOST_FK1

PROMODFUVENDORCOST



Table Relationships



PROMODFU_CRITERIA_PROMO_FK1

PROMODFU_CRITERIA - PROMOTION PROMOTION - PROMOTION

PROMODFU_EXCLU_PRMDFU_CRI_FK1

PROMODFU_EXCLUSION

- CRITERIA_ID PROMODFU_CRITERIA - CRITERIA_ID

PROMODFU_FILTER_PRO_CRIOPR_FK1

PROMODFU_FILTER - OPERATOR_ID PROMODFU_CRITERIA_OPERATOR

- OPERATOR_ID

PROMODFU_FILTER_PRO_CRI_FK1

PROMODFU_FILTER - CRITERIA_ID PROMODFU_CRITERIA - CRITERIA_ID

PROMODFU_PROMODFUCRI_FK1

PROMODFU - CRITERIAID PROMODFU_CRITERIA - CRITERIA_ID

PROMOEVENTACTIVITYID_FK PROMOEVENT - PROMOACTIVITYID PROMOACTIVITY - PROMOACTIVITYID PROMOEXCLUDELOCACTIVITYID_FK

PROMOACTIVITYEXCLUDELOC


PROMOEXCLUDELOC_LOC_FK

PROMOACTIVITYEXCLUDELOC

- LOC LOC - LOC

PROMOFACTSHEET_FEAPROD_FK1

PROMOFEATUREDPRODUCT

- PROMOTION PROMOFACTSHEET - PROMOTION

PROMOFACTSHEET_PROMO_FK1

PROMOFACTSHEET - PROMOTION PROMOTION - PROMOTION

PROMOFACTSHEET_SAVESTORY_FK1

PROMOSAVESTORY - PROMOTION PROMOFACTSHEET - PROMOTION

PROMOFEAPROD_DMDUNIT_FK2

PROMOFEATUREDPRODUCT


PROMOFEATPRODIMAGE_FEATPROD_FK

PROMOFEATUREDPRODUCTIMAGE

- PROMOTION - DMDUNIT PROMOFEATUREDPRODUCT

- PROMOTION - DMDUNIT

PROMOINCLUDELOCACTIVITYID_FK

PROMOACTIVITYINCLUDELOC


PROMOINCLUDELOC_LOC_FK PROMOACTIVITYINCLUDELOC

- LOC LOC - LOC

PROMOLIFTFACTOR_CRITERIA_FK1

PROMOLIFTFACTOR - CRITERIAID PROMODFU_CRITERIA - CRITERIA_ID

PROMOMDALLOC_FK1 PROMOMDALLOC - PROMOTION PROMOTION - PROMOTION PROMOOPTTARGETS_FK1 PROMOOPTTARGETS - PROMOTION PROMOTION - PROMOTION


Table Relationships



PROMOPRICESTRATTR_CRITERIA_FK1

PROMOPRICESTRATEGYTIER


PROMOPRICESTRA_CRITERIA_FK1

PROMOPRICESTRATEGY


PROMOPRICESTRA_PRMOPRSTRAT_FK1

PROMOPRICESTRATEGYTIER

- CRITERIAID - NODEKEYID PROMOPRICESTRATEGY

- CRITERIAID - NODEKEYID

PROMOPROFILE_PROMOTION_FK

PROMOPROFILE - PROMOTION PROMOTION - PROMOTION

PROMOSCORECARD_PROMOTION_FK1

PROMOSCORECARD - PROMOTION PROMOTION - PROMOTION

PROMOSPACEALLOCATION_FK

PROMOSPACEALLOC - PROMOTION PROMOTION - PROMOTION

PROMOSPACEALLOCSECOWNERS_FK1

PROMOSPACEALLOCSECOWNERS

- PROMOACTIVITYID - PAGE PROMOACTIVITYSPACEALLOC

- PROMOACTIVITYID - PAGE

PROMOTIONREPORT_FK1 PROMOTIONREPORT - PROMOTION PROMOTION - PROMOTION PROMOVEHICLEACTIVITYID_FK

PROMOVEHICLE - PROMOACTIVITYID PROMOACTIVITY - PROMOACTIVITYID

PRRULEAGGTYPE_PRAGGTYPE_FK1

PRICERULEAGGTYPE - AGGTYPE PRICEAGGTYPE - AGGTYPE

PRSCENRULEMAP_PRRULEDEF_FK1

PRICESCENARIORULEMAP


- RULENAME

PRSCENRULEMAP_PRSCEN_FK2

PRICESCENARIORULEMAP


PRSENSITIVITY_DFUPRPARAM_FK2

PRICESENSITIVITY - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

PRSENSITIVITY_PRSCENARIO_FK1

PRICESENSITIVITY - PRICESCENARIO PRICESCENARIO - PRICESCENARIO

PSDFUE_DFUPP_FK PRICESCENARIODFUEXCEPTION


PSDFUE_PS_FK PRICESCENARIODFUEXCEPTION


PURCHLEADTIMEPARAM_SKU_FK1

PURCHLEADTIMEPARAM



Table Relationships



PURCHMETHOD_CAL_FK PURCHMETHOD - ARRIVCAL CAL - CAL PURCHMETHOD_SKU_FK1 PURCHMETHOD - ITEM - LOC SKU - ITEM - LOC PURCHORDER_SKU_FK1 PURCHORDER - ITEM - LOC SKU - ITEM - LOC PURCHREQUIREMENT_SKU_FK1

PURCHREQUIREMENT - ITEM - LOC SKU - ITEM - LOC

RECSHIP_ITEM_FK1 RECSHIP - PRIMARYITEM ITEM - ITEM RECSHIP_SKU_FK1 RECSHIP - ITEM - SOURCE SKU - ITEM - LOC RECSHIP_SKU_FK2 RECSHIP - ITEM - DEST SKU - ITEM - LOC RECSHIP_TRANSMODE_FK1 RECSHIP - TRANSMODE TRANSMODE - TRANSMODE RECSUBINVENTORY_ITEM_FK1

RECSUBINVENTORY - PRIMARYITEM ITEM - ITEM

RECSUBINVENTORY_SKU_FK1

RECSUBINVENTORY - ITEM - LOC SKU - ITEM - LOC

REDUCEDCOSTPRODUCTION_SKU_FK

REDUCEDCOSTPRODUCTION


REDUCEDCOSTPROD_PRODMETHOD_FK

REDUCEDCOSTPRODUCTION



REDUCEDCOSTRES_RES_FK REDUCEDCOSTRES - RES RES - RES REDUCEDCOSTSKU_SKU_FK REDUCEDCOSTSKU - ITEM - LOC SKU - ITEM - LOC REDUCEDCOSTSRC_SOURCING_FK

REDUCEDCOSTSOURCING



RELATIONNAME_FK PRICERELATIONGROUP - RELATIONNAME PRICERELATION - RELATIONNAME REPORTHISTFCSTDATA_SKU_FK1

REPORTHISTFCSTDATA - ITEM - LOC SKU - ITEM - LOC

RESCONSTRAINT_RES_FK1 RESCONSTRAINT - RES RES - RES RESCONSTRAINT_UOM_FK1 RESCONSTRAINT - QTYUOM UOM - UOM RESCONST_CONSTRCATEGORY_FK1

RESCONSTRAINT - CATEGORY CONSTRAINTCATEGORY

- CATEGORY

RESCONTRAINT_TIMEUOM_FK

RESCONSTRAINT - TIMEUOM UOM - UOM

RESCOST_COSTCATEGORY_F RESCOST - CATEGORY COSTCATEGORY - CATEGORY


Table Relationships



K1 RESCOST_COST_FK1 RESCOST - LOCALCOST COST - COST RESCOST_COST_FK2 RESCOST - TIEREDCOST COST - COST RESCOST_RES_FK1 RESCOST - RES RES - RES RESEXCEPTION_PRODFAMILY_FK

RESEXCEPTION - PRODFAMILY PRODUCTIONFAMILY - PRODFAMILY

RESEXCEPTION_RES_FK1 RESEXCEPTION - RES RES - RES RESLOADDETAIL_ITEM_FK1 RESLOADDETAIL - ITEM ITEM - ITEM RESLOADDETAIL_LOC_FK2 RESLOADDETAIL - LOC LOC - LOC RESLOADREQUIREMENT_SKU_FK1

RESLOADREQUIREMENT


RESMETRIC_CURRUOM_FK RESMETRIC - CURRENCYUOM UOM - UOM RESMETRIC_METRICCATEGORY_FK1

RESMETRIC - CATEGORY METRICCATEGORY - CATEGORY

RESMETRIC_QTYUOM_FK RESMETRIC - QTYUOM UOM - UOM RESMETRIC_RES_FK1 RESMETRIC - RES RES - RES RESMETRIC_SETUP_FK RESMETRIC - SETUP SETUP - SETUP RESMETRIC_TIMEUOM_FK RESMETRIC - TIMEUOM UOM - UOM RESOINDEPENDENTDMD_SKU_FK1

RESOINDEPENDENTDMD


RESOIN_SKU_FK1 RESOIN - ITEM - LOC SKU - ITEM - LOC RESOSUPPLYDETAIL_LOC_FK1

RESOSUPPLYDETAIL - SUBSTLOC LOC - LOC

RESOSUPPLYDETAIL_SKU_FK1

RESOSUPPLYDETAIL - ITEM - LOC SKU - ITEM - LOC

RESPENALTY_PENALTYCAT_FK1

RESPENALTY - CATEGORY PENALTYCATEGORY - CATEGORY

RESPENALTY_RES_FK1 RESPENALTY - RES RES - RES RESPENALTY_TIMEUOM_FK RESPENALTY - TIMEUOM UOM - UOM RESPENALTY_UOM_FK1 RESPENALTY - QTYUOM UOM - UOM RESPENALTY_UOM_FK2 RESPENALTY - CURRENCYUOM UOM - UOM


Table Relationships



RESPROJ_RES_FK1 RESPROJ - RES RES - RES RESPROJ_RES_FK3 RESPROJ - ADDITIONALUOM UOM - UOM RESPROJ_UOM_FK1 RESPROJ - NUMERATORUOM UOM - UOM RESPROJ_UOM_FK2 RESPROJ - DENOMINATORUOM UOM - UOM RESSUBTYPE_TRANS_RESSUBTYPE_FK

RESSUBTYPE_TRANS - SUBTYPE RESSUBTYPE - SUBTYPE

RES_CAL_FK1 RES - CAL CAL - CAL RES_ITEM_FK1 RES - CRITICALITEM ITEM - ITEM RES_LOC_FK1 RES - LOC LOC - LOC RES_LOC_FK2 RES - SOURCE LOC - LOC RES_RESSUBTYPE_FK1 RES - SUBTYPE RESSUBTYPE - SUBTYPE RES_UOM_FK2 RES - QTYUOM UOM - UOM RES_UOM_FK3 RES - CURRENCYUOM UOM - UOM RETAILFCST_SKU_FK1 RETAILFCST - ITEM - LOC SKU - ITEM - LOC RMEVENTCALDATA_RMEVENTCAL_FK

RMEVENTCALDATA - EVENTCAL RMEVENTCAL - EVENTCAL

RMEVENTCALDATA_RMEVENTTYPE_FK

RMEVENTCALDATA - EVENTTYPE RMEVENTTYPE - EVENTTYPE

RMF_FCST_HIER_FK RMF_FCST_HIER - MAP MAP - MAP RMF_INPUT_ATTRIB_FK1 RMF_INPUT_ATTRIB - ANALYSIS_TYPE RMF_ANALYSIS_TYPE - ANALYSIS_TYPE RMF_METRIC_INTERVAL_FK RMF_METRIC_INTERVA

L - ANALYSIS_TYPE RMF_ANALYSIS_TYPE - ANALYSIS_TYPE

RMF_METRIC_TREE_FK RMF_METRIC_TREE - ANALYSIS_TYPE RMF_ANALYSIS_TYPE - ANALYSIS_TYPE RMF_METRIC_TREE_LOG_FK RMF_METRIC_TREE_LO

G - ANALYSIS_TYPE RMF_ANALYSIS_TYPE - ANALYSIS_TYPE

RMF_MET_TREE_ATT_GRP_FK1

RMF_METRIC_TREE - ATTRIB_GROUP_ID RMF_ATTRIB_GROUP - ATTRIB_GROUP_ID

RMF_MET_TREE_LOG_ATT_GRP_FK1

RMF_METRIC_TREE_LOG

- ATTRIB_GROUP_ID RMF_ATTRIB_GROUP - ATTRIB_GROUP_ID

RMF_ORDERED_ATTRIB_FK RMF_ORDERED_ATTRIB

- ANALYSIS_TYPE RMF_ANALYSIS_TYPE - ANALYSIS_TYPE


Table Relationships



RMF_ORDERED_ATT_ATT_GRP_FK1

RMF_ORDERED_ATTRIB

- ATTRIB_GROUP_ID RMF_ATTRIB_GROUP - ATTRIB_GROUP_ID

RULEDEFINITION_RULENAME_FK2

PRICESCENARIORULECONFLICT


- RULENAME

RULEDETAILS_RULE_FK RULEDETAILS - RULESET - SERVICENAME - RULESEQNUM

RULE - RULESET - SERVICENAME - SEQNUM

RULEORDERBYDETAILS_RULE_FK

RULEORDERBYDETAILS - RULESET - SERVICENAME - RULESEQNUM

RULE - RULESET - SERVICENAME - SEQNUM

RULESETNAME_PRICERULESET_FK2

PRICESCENARIORULESETMAP

- RULESETNAME PRICERULESET - RULESETNAME

RULE_RULESET_FK RULE - RULESET - SERVICENAME RULESET - RULESET - SERVICENAME

R_120 HISTPROMOINCENTIVEVAL

- INCENTIVE INCENTIVE - INCENTIVE

R_127 DECOMPGROUPCOEF - DECOMPGROUP DECOMPGROUP - DECOMPGROUP R_141 DECOMPSUBGROUPCO

EF - DECOMPSUBGROUP - DECOMPGROUP


R_143 VIEWHIERARCHYCOL - VIEWHIERARCHY VIEWHIERARCHY - VIEWHIERARCHY R_145 PROMODFUMKTGINSTR

VAL - DMDUNIT - DMDGROUP - LOC - PROMOTION

PROMODFU - DMDUNIT - DMDGROUP - LOC - PROMOTION

R_146 MRMCOEFDRAFT - MRMGROUP MRMGROUP - MRMGROUP R_147 MRMCOEF - MRMGROUP MRMGROUP - MRMGROUP R_148 SMEARINGFACTORDRA

FT - MRMGROUP MRMGROUP - MRMGROUP

R_149 SMEARINGFACTOR - MRMGROUP MRMGROUP - MRMGROUP R_152 PROCESSPRICEGROUP - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_153 PROCESSDECOMPGRO

UP - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_155 PROCESSDECOMPGRO - DECOMPGROUP DECOMPGROUP - DECOMPGROUP


Table Relationships



UP R_156 PROCESSDECOMPSUB

GROUP - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_157 PROCESSDECOMPSUB

GROUP - DECOMPSUBGROUP - DECOMPGROUP


R_158 PROCESSPRICEGROUP - PRICEGROUP PRICEGROUP - PRICEGROUP R_161 DECOMPSUBGROUP - DECOMPGROUP DECOMPGROUP - DECOMPGROUP R_162 DECOMPGROUPNORMF

ACTOR - DECOMPGROUP DECOMPGROUP - DECOMPGROUP

R_171 DECOMPHIST - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

R_173 PRICERULEMAP - RULENAME PRICERULEDEFINITION

- RULENAME

R_218 SALESORDERLINEITEM - ORDERID SALESORDER - ORDERID R_24 DMDUNITBUNDLEMAP - DMDUNITBUNDLE DMDUNITBUNDLE - DMDUNITBUNDLE R_309 LIFESTAGE - LIFECYCLE LIFECYCLE - LIFECYCLE R_312 SALESORDER - LOC LOC - LOC R_320 MBARESULT - MBAGROUP MBAGROUP - MBAGROUP R_321 DECOMPGROUP - DECOMPMRMODEL MRMODEL - MRMODEL R_358 DECOMPSUBGROUPMK

TGINST - DECOMPSUBGROUP - DECOMPGROUP


R_359 DECOMPSUBGROUPMKTGINST

- MKTGINSTRUMENTATTRIB - MKTGINSTRUMENT

MKTGINSTRUMENTATTRIB


R_360 PROCESSPRICEOPTGROUP


R_361 DFUPRICERATIO - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

R_364 DFUPRICECONSTRAINT - RULENAME PRICERULEDEFINITION

- RULENAME

R_366 DFUAPPROVEDPRICE - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -


Table Relationships



DMDGROUP - LOC R_373 PROMODFUALLOWANC

EVAL - DMDUNIT - DMDGROUP - LOC - PROMOTION


R_377 PROMODFUMKTGINSTRVAL

- MKTGINSTRUMENT - PROMOTION

PROMOMKTGINSTRUMENT

- MKTGINSTRUMENT - PROMOTION

R_381 PROMOINCENTIVE - INCENTIVE INCENTIVE - INCENTIVE R_382 PROMODFU - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_391 PROMOINCENTIVE - PROMOTION PROMOTION - PROMOTION R_393 PROMODFUINCENTIVE

VAL - INCENTIVE - PROMOTION PROMOINCENTIVE - PROMOTION -

INCENTIVE R_394 PROMODFU - PROMOTION PROMOTION - PROMOTION R_399 MKTGINSTRUMENTATT

RIB - MKTGINSTRUMENT MKTGINSTRUMENT - MKTGINSTRUMENT

R_401 HISTPROMOMKTGINSTRUMENTVAL

- PROMOTION HISTPROMO - PROMOTION


- PROMOTION HISTPROMO - PROMOTION









R_407 DFUPRICERELATION - IMPACTINGDMDUNIT - IMPACTINGDMDGROUP - IMPACTINGLOC


R_415 MRMGROUPLRSTAT - MRMGROUP MRMGROUP - MRMGROUP R_416 MRMGROUPLRSTATDRA

FT - MRMGROUP MRMGROUP - MRMGROUP


Table Relationships



R_422 PROMOMKTGINSTRUMENT


R_423 PROMODFUMKTGINSTRVAL




R_426 PROMOMKTGINSTRUMENT


R_428 PROMOALLOWANCE - ALLOWANCE ALLOWANCE - ALLOWANCE R_429 PROMOALLOWANCE - PROMOTION PROMOTION - PROMOTION R_430 PROMODFUALLOWANC

EVAL - PROMOTION - ALLOWANCE PROMOALLOWANCE - PROMOTION -

ALLOWANCE R_432 MRMPROXY - MRMGROUP MRMGROUP - MRMGROUP R_435 VARIANTMRMCAUSALF

ACTORVAL - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_437 VARIANTMRMCAUSALF

ACTORVAL - MRMCAUSALFACTOR MRMCAUSALFACTOR -

MRMCAUSALFACTOR R_439 MRMCAUSALFACTOR - DATATYPE PRICEDATATYPE - DATATYPE R_440 MKTGINSTRUMENTATT

RIB - DATATYPE PRICEDATATYPE - DATATYPE

R_441 DFUELASTICITY - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC

R_444 ALLOWANCE - MKTGINSTRUMENT MKTGINSTRUMENT - MKTGINSTRUMENT R_452 DFUPRICEPARAM - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT -

DMDGROUP - LOC R_453 PRICEPOINTGENRULE - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_454 DFUPRICEPOINT - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_46 PROMODFUINCENTIVE

VAL - DMDUNIT - DMDGROUP - LOC - PROMOTION


R_466 DFUPRICERELATION - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -


Table Relationships



DMDGROUP - LOC R_467 DFURULEPRICEPOINT - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_468 APPLICATIONPRICEPOI

NT - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_469 INCENTIVE - TERM1DATATYPE PRICEDATATYPE - DATATYPE R_470 INCENTIVE - TERM2DATATYPE PRICEDATATYPE - DATATYPE R_471 INCENTIVE - TERM3DATATYPE PRICEDATATYPE - DATATYPE R_472 INCENTIVE - TERM4DATATYPE PRICEDATATYPE - DATATYPE R_476 SALESORDERLINEITEM - DMDUNIT DMDUNIT - DMDUNIT R_477 MBARESULT - FROMDMDUNIT DMDUNIT - DMDUNIT R_478 MBARESULT - TODMDUNIT DMDUNIT - DMDUNIT R_63 DFUSTOCKOUT - DMDUNIT - DMDGROUP - LOC DFUPRICEPARAM - DMDUNIT -

DMDGROUP - LOC R_91 PRICERULESETMAP - RULESETNAME PRICERULESET - RULESETNAME R_92 PRICERULESETMAP - RULENAME PRICERULEDEFINITIO

N - RULENAME

R_94 PRICESCENARIODETAIL


R_95 PRICESCENARIOFCST - DMDUNIT - DMDGROUP - LOC - PRICESCENARIO

PRICESCENARIODETAIL

- DMDUNIT - DMDGROUP - LOC - PRICESCENARIO

R_99 PRICERULESELECTION - RULENAME PRICERULEDEFINITION

- RULENAME

SAFETYSTOCKPARAM_SKU_FK1

SKUSAFETYSTOCKPARAM


SALESTARGET_DFUVIEW_FK1

SALESTARGET - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

SCENARIOINPUTDETAILS_FK SCENARIOINPUTDETAILS

- SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SCENDETAILS_SIM_CATALOG_FK1

SCENARIOTYPEDETAILS


- SIMULATION_NAME


Table Relationships



SCHEDRCPTSDTL_SCHEDRCPTS_FK01

SCHEDRCPTSDETAIL - ITEM - LOC - SCHEDDATE - EXPDATE - STARTDATE - SEQNUM


SCHEDRCPTSDTL_SKU_FK02 SCHEDRCPTSDETAIL - ITEM - LOC SKU - ITEM - LOC SCHEDRCPTS_SKU_FK1 SCHEDRCPTS - ITEM - LOC SKU - ITEM - LOC SEASONERROR_DFUVIEW_FK1

SEASONERROR - DMDUNIT - DMDGROUP - LOC DFUVIEW - DMDUNIT - DMDGROUP - LOC

SEASONPROFILEVALUES_FK SEASONPROFILEVALUES

- PROFILENAME SEASONPROFILE - PROFILENAME

SETUPCONSTR_CONSTRCATG_FK

SETUPCONSTRAINT - CATEGORY CONSTRAINTCATEGORY

- CATEGORY

SETUPCONSTR_SETUP_FK SETUPCONSTRAINT - SETUP SETUP - SETUP SETUPCONSTR_UOM_FK SETUPCONSTRAINT - QTYUOM UOM - UOM SETUPCOST_COSTCATG_FK SETUPCOST - CATEGORY COSTCATEGORY - CATEGORY SETUPCOST_COST_FK1 SETUPCOST - LOCALCOST COST - COST SETUPCOST_COST_FK2 SETUPCOST - TIEREDCOST COST - COST SETUPCOST_SETUP_FK SETUPCOST - SETUP SETUP - SETUP SHELFLIFEGROUPDATA_SLG_FK1

SHELFLIFEGROUPDATA - SHELFLIFEGROUP SHELFLIFEGROUP - SHELFLIFEGROUP

SIMULATION_LOAD_ERRORS_FK1

SIMULATION_LOAD_ERRORS


- SIMULATION_NAME

SIM_ACTIONFILTER_FK SIM_ACTIONFILTER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_AGGSKUPROJSTATIC_FK

SIM_AGGSKUPROJSTATIC


- SIMULATION_NAME

SIM_AGGSKU_FK SIM_AGGSKU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_ALLOCPROFILECATEGORY_FK

SIM_ALLOCPROFILECATEGORY


- SIMULATION_NAME

SIM_ALLOCPROFILELIB_FK SIM_ALLOCPROFILELIB - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_ALLOCPROFILEVALUES_FK

SIM_ALLOCPROFILEVALUES


- SIMULATION_NAME

SIM_ALLOCPROFILE_FK SIM_ALLOCPROFILE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_ALLOCSTRAT_FK SIM_ALLOCSTRAT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_ALTBOM_FK01 SIM_ALTBOM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_ALTPRODUCTIONSTEP_FK01

SIM_ALTPRODUCTIONSTEP


- SIMULATION_NAME

SIM_AVGDMD_FK SIM_AVGDMD - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_AVSGRAVESPARAM_FK SIM_AVSGRAVESPARAM


- SIMULATION_NAME

SIM_AVSGRAVESSTATS_FK SIM_AVSGRAVESSTATS


- SIMULATION_NAME

SIM_BOM_FK SIM_BOM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CALATTRIB_CALPATTERN_FK01

SIM_CALATTRIBUTE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CALDATA_FK SIM_CALDATA - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CALINTERVAL_FK SIM_CALINTERVAL - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CALPATTERN_CAL_FK01 SIM_CALPATTERN - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CAL_FK SIM_CAL - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CAT_PROP_SIM_CAT_FK1

SIMULATION_CATALOG_PROPERTIES


- SIMULATION_NAME

SIM_CAUSALFACTORTYPE_FK

SIM_CAUSALFACTORTYPE


- SIMULATION_NAME

SIM_CAUSALFACTORVALUE_FK

SIM_CAUSALFACTORVALUE


- SIMULATION_NAME


Table Relationships



SIM_CAUSALFACTOR_FK SIM_CAUSALFACTOR - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_COMPAREOUTPUT_FK SIM_COMPAREOUTPUT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CONSTRAINTCATEGORY_FK

SIM_CONSTRAINTCATEGORY


- SIMULATION_NAME

SIM_COSTCATEGORY_FK SIM_COSTCATEGORY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_COSTELEMENT_FK SIM_COSTELEMENT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_COSTTIER_FK SIM_COSTTIER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_COST_FK SIM_COST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CPPALTRES_FK SIM_CPPALTRES - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CPPFAMILY_FK SIM_CPPFAMILY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CPPSTRATSTEP_FK SIM_CPPSTRATSTEP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CPPSTRAT_FK SIM_CPPSTRAT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CPPTIEBREAKERRULE_FK

SIM_CPPTIEBREAKERRULE


- SIMULATION_NAME

SIM_CPPTIEBREAKER_FK SIM_CPPTIEBREAKER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CRITICALPARTSAGGREGATES_FK

SIM_CRITICALPARTSAGGREGATES


- SIMULATION_NAME

SIM_CRITICALPARTSOUTPUT_FK

SIM_CRITICALPARTSOUTPUT


- SIMULATION_NAME

SIM_CRITICALPATHOUTPUT_FK

SIM_CRITICALPATHOUTPUT


- SIMULATION_NAME

SIM_CROSTONPARAM_FK SIM_CROSTONPARAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_CROSTONSTATS_FK SIM_CROSTONSTATS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CSLTEMPLATEDATA_FK1

SIM_CSLTEMPLATEDATA


- SIMULATION_NAME

SIM_CSLTEMPLATE_FK1 SIM_CSLTEMPLATE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CUSTORDERHEADER_FK SIM_CUSTORDERHEADER


- SIMULATION_NAME

SIM_CUSTORDERHIST_FK SIM_CUSTORDERHIST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CUSTORDERSTATHIST_FK

SIM_CUSTORDERSTATHIST


- SIMULATION_NAME

SIM_CUSTORDERSTATUS_FK SIM_CUSTORDERSTATUS


- SIMULATION_NAME

SIM_CUSTORDERSTAT_FK SIM_CUSTORDERSTAT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CUSTORDER_FK SIM_CUSTORDER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_CUST_FK SIM_CUST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DC_ALGORITHMRANK_FK

SIM_DC_ALGORITHMRANK


- SIMULATION_NAME

SIM_DC_AVSGRAVESPARAM_FK

SIM_DC_AVSGRAVESPARAM


- SIMULATION_NAME

SIM_DC_CROSTONPARAM_FK

SIM_DC_CROSTONPARAM


- SIMULATION_NAME

SIM_DC_DFUCLASSHIST_FK SIM_DC_DFUCLASSHIST


- SIMULATION_NAME

SIM_DC_DFUCLASS_FK SIM_DC_DFUCLASS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DC_DFUPARAM_FK SIM_DC_DFUPARAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DC_EXCEPTION_FK SIM_DC_EXCEPTION - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_DC_HOLTPARAM_FK SIM_DC_HOLTPARAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DC_LEWPARAM_FK SIM_DC_LEWPARAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DC_LINREGPARAM_FK SIM_DC_LINREGPARAM


- SIMULATION_NAME

SIM_DC_MOVINGAVGPARAM_FK

SIM_DC_MOVINGAVGPARAM


- SIMULATION_NAME

SIM_DC_STATS_FK SIM_DC_STATS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DDEPROFILE_FK SIM_DDEPROFILE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DDRPARAMPROFILE_FK SIM_DDRPARAMPROFILE


- SIMULATION_NAME

SIM_DEPDMDREQUIREMENT_FK

SIM_DEPDMDREQUIREMENT


- SIMULATION_NAME

SIM_DEPDMDSTATIC_FK SIM_DEPDMDSTATIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DEPLOYMENTDEMAND_FK

SIM_DEPLOYMENTDEMAND


- SIMULATION_NAME

SIM_DEPLOYMENTPRIORITY_FK

SIM_DEPLOYMENTPRIORITY


- SIMULATION_NAME

SIM_DFUALLOCPROFILEMAP_FK

SIM_DFUALLOCPROFILEMAP


- SIMULATION_NAME

SIM_DFUATTRIB_FK SIM_DFUATTRIB - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUCAUSALFACTOR_FK SIM_DFUCAUSALFACTOR


- SIMULATION_NAME

SIM_DFUCOEF_FK SIM_DFUCOEF - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUDDEMAP_FK SIM_DFUDDEMAP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUEXCEPTION_FK SIM_DFUEXCEPTION - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_DFUMAINTCOPYDFU_FK SIM_DFUMAINTCOPYDFU


- SIMULATION_NAME

SIM_DFUMAPFCSTPROFILE_FK

SIM_DFUMAPFCSTPROFILE


- SIMULATION_NAME

SIM_DFUMAP_FK SIM_DFUMAP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUMOVINGEVENTMAP_FK

SIM_DFUMOVINGEVENTMAP


- SIMULATION_NAME

SIM_DFUNPIRELATION_FK SIM_DFUNPIRELATION - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUPROJDRAFTSTATIC_FK

SIM_DFUPROJDRAFTSTATIC


- SIMULATION_NAME

SIM_DFUPROJSTATIC_FK SIM_DFUPROJSTATIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUTOE3FCST_FK SIM_DFUTOE3FCST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUTOITXFCST_FK SIM_DFUTOITXFCST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUTOSKUFCST_FK SIM_DFUTOSKUFCST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUTOSKUSEASONERR_FK

SIM_DFUTOSKUSEASONERR


- SIMULATION_NAME

SIM_DFUTOSKU_FK SIM_DFUTOSKU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUTOTALVOL_FK SIM_DFUTOTALVOL - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUTOWFMFCST_FK SIM_DFUTOWFMFCST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFUVIEW_FK SIM_DFUVIEW - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DFU_FK SIM_DFU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DIFFERENCEOUTPUT_FK SIM_DIFFERENCEOUTPUT


- SIMULATION_NAME


Table Relationships



SIM_DISTREQUIREMENT_FK SIM_DISTREQUIREMENT


- SIMULATION_NAME

SIM_DMDGROUP_FK SIM_DMDGROUP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DMDRED_FK SIM_DMDRED - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DMDUNIT_FK SIM_DMDUNIT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DMDVAR_FK SIM_DMDVAR - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_DYNDEPSRC_FK SIM_DYNDEPSRC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_E3FCSTTRACK_FK SIM_E3FCSTTRACK - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_EXCEPTIONORDERRELATION_FK

SIM_EXCEPTIONORDERRELATION


- SIMULATION_NAME

SIM_EXCESSINVOUTPUT_FK SIM_EXCESSINVOUTPUT


- SIMULATION_NAME

SIM_EXTRAUSAGE_FK SIM_EXTRAUSAGE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_FCSTDRAFT_FK SIM_FCSTDRAFT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_FCSTORDERSTATUS_FK SIM_FCSTORDERSTATUS


- SIMULATION_NAME

SIM_FCSTORDER_FK SIM_FCSTORDER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_FCSTPERFSTATIC_FK SIM_FCSTPERFSTATIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_FCST_FK SIM_FCST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_FITTEDHIST_FK SIM_FITTEDHIST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_HISTFCSTEVENTS_FK SIM_HISTFCSTEVENTS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_HISTFCST_FK SIM_HISTFCST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_HISTSTREAM_FK SIM_HISTSTREAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_HIST_FK SIM_HIST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_HOLTWINTERSPARAM_FK

SIM_HOLTWINTERSPARAM


- SIMULATION_NAME

SIM_HOLTWINTERSSTATS_FK

SIM_HOLTWINTERSSTATS


- SIMULATION_NAME

SIM_IGNOREDDMD_FK SIM_IGNOREDDMD - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IMPDEPDMDSTATIC_FK SIM_IMPDEPDMDSTATIC


- SIMULATION_NAME

SIM_IMPRESLOADDETAIL_FK SIM_IMPRESLOADDETAIL


- SIMULATION_NAME

SIM_INDDMDLINK_FK SIM_INDDMDLINK - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_INVENTORY_FK SIM_INVENTORY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IPOFUNDPERIOD_FK1 SIM_IPOFUNDPERIOD - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IPOFUND_FK1 SIM_IPOFUND - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IPOGRAPH_FK1 SIM_IPOGRAPH - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IPOGROUPPERFORMANCE_FK1

SIM_IPOGROUPPERFORMANCE


- SIMULATION_NAME

SIM_IPOGROUPTARGET_FK1 SIM_IPOGROUPTARGET


- SIMULATION_NAME

SIM_IPOGROUP_FK1 SIM_IPOGROUP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IPOOPSSYSTEMPERFORMANCE_FK

SIM_IPOOPSSYSTEMPERFORMANCE


- SIMULATION_NAME


Table Relationships



SIM_IPOPLANSTAT_FK SIM_IPOPLANSTAT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IPOPROJ_FK1 SIM_IPOPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_IPOSKUCONSTRAINT_FK1

SIM_IPOSKUCONSTRAINT


- SIMULATION_NAME

SIM_IPOSKUPERFORMANCE_FK1

SIM_IPOSKUPERFORMANCE


- SIMULATION_NAME

SIM_IPOSTOCKINGPLAN_FK SIM_IPOSTOCKINGPLAN


- SIMULATION_NAME

SIM_ITEM_FK SIM_ITEM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LANEGROUPCAP_FK SIM_LANEGROUPCAP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LANEGROUP_FK SIM_LANEGROUP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LEWANDOWSKIPARAM_FK

SIM_LEWANDOWSKIPARAM


- SIMULATION_NAME

SIM_LEWANDOWSKISTATS_FK

SIM_LEWANDOWSKISTATS


- SIMULATION_NAME

SIM_LEWFACTORCATEGORY_FK

SIM_LEWFACTORCATEGORY


- SIMULATION_NAME

SIM_LEWFACTORLIBMAP_FK SIM_LEWFACTORLIBMAP


- SIMULATION_NAME

SIM_LEWFACTORLIBRARY_FK

SIM_LEWFACTORLIBRARY


- SIMULATION_NAME

SIM_LEWFACTORVALUE_FK SIM_LEWFACTORVALUE


- SIMULATION_NAME

SIM_LEWFACTOR_FK SIM_LEWFACTOR - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LIBRARYCATEGORYMAP_FK

SIM_LIBRARYCATEGORYMAP


- SIMULATION_NAME

SIM_LINREGPARAM_FK SIM_LINREGPARAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_LINREGSTATS_FK SIM_LINREGSTATS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LOCCOST_FK SIM_LOCCOST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LOCTYPE_FK SIM_LOCTYPE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LOC_FK SIM_LOC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LPDMDBANDS_FK01 SIM_LPDMDBANDS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LPLAYER_FK01 SIM_LPLAYER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LTDGROUP_FK SIM_LTDGROUP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_LTDPERCENT_FK SIM_LTDPERCENT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_MAP_FK SIM_MAP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_MARGINPRICEANDSLACKPROD_FK

SIM_MARGINALPRICEANDSLACKPROD


- SIMULATION_NAME

SIM_MARGINPRICEANDSLACKRES_FK

SIM_MARGINALPRICEANDSLACKRES


- SIMULATION_NAME

SIM_MARGINPRICEANDSLACKSKU_FK

SIM_MARGINALPRICEANDSLACKSKU


- SIMULATION_NAME

SIM_MARGINPRICEANDSLACKSRC_FK

SIM_MARGINALPRICEANDSLACKSRCNG


- SIMULATION_NAME

SIM_MASKDATA_FK SIM_MASKDATA - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_MASK_FK SIM_MASK - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_MEANVALUEADJ_FK SIM_MEANVALUEADJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_METRICCATEGORY_FK SIM_METRICCATEGORY


- SIMULATION_NAME


Table Relationships



SIM_MODEL_FK SIM_MODEL - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_MOVINGAVGPARAM_FK SIM_MOVINGAVGPARAM


- SIMULATION_NAME

SIM_MOVINGAVGSTATS_FK SIM_MOVINGAVGSTATS


- SIMULATION_NAME

SIM_MOVINGAVGWGTS_FK SIM_MOVINGAVGWGTS


- SIMULATION_NAME

SIM_MSE_FK SIM_MSE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_NETWORKCAP_FK SIM_NETWORKCAP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_NETWORK_FK SIM_NETWORK - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_NPIDFUERROR_FK SIM_NPIDFUERROR - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_NPIEXPLODEDTODFU_FK

SIM_NPIEXPLODEDTODFU


- SIMULATION_NAME

SIM_NPIFROMDFUPRIORITY_FK

SIM_NPIFROMDFUPRIORITY


- SIMULATION_NAME

SIM_NPITODFUEXPRESSION_FK

SIM_NPITODFUEXPRESSION


- SIMULATION_NAME

SIM_NPITODFU_FK SIM_NPITODFU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_NPIVALIDDFU_FK SIM_NPIVALIDDFU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_OPSSYSTEMPART_FK1 SIM_OPSSYSTEMPART - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_OPSSYSTEM_FK1 SIM_OPSSYSTEM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_OPTIMIZERCOSTEXCEPTION_FK

SIM_OPTIMIZERCOSTEXCEPTION


- SIMULATION_NAME

SIM_OPTIMIZEREXCEPTION_FK

SIM_OPTIMIZEREXCEPTION


- SIMULATION_NAME


Table Relationships



SIM_OPTIMIZERPRODEXCEPTION_FK

SIM_OPTIMIZERPRODEXCEPTION


- SIMULATION_NAME

SIM_OPTIMIZERRESEXCEPTION_FK

SIM_OPTIMIZERRESEXCEPTION


- SIMULATION_NAME

SIM_OPTIMIZERRESSTAT_FK SIM_OPTIMIZERRESSTAT


- SIMULATION_NAME

SIM_OPTIMIZERSETUPEXP_FK

SIM_OPTIMIZERSETUPEXCEPTION


- SIMULATION_NAME

SIM_OPTIMIZERSKUEXCEPTION_FK

SIM_OPTIMIZERSKUEXCEPTION


- SIMULATION_NAME

SIM_OPTIMIZERSKUSTAT_FK SIM_OPTIMIZERSKUSTAT


- SIMULATION_NAME

SIM_OPTIMIZERSOURCINGEXCEPT_FK

SIM_OPTIMIZERSOURCINGEXCEPTION


- SIMULATION_NAME

SIM_ORDERLINK_FK SIM_ORDERLINK - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PCADETAIL_FK SIM_PCADETAIL - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PCARESULT_FK SIM_PCARESULT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PLANARRIV_FK SIM_PLANARRIV - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PLANORDER_FK SIM_PLANORDER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PLANPROXYINVENTORY_FK

SIM_PLANPROXYINVENTORY


- SIMULATION_NAME

SIM_PLANPURCH_FK SIM_PLANPURCH - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PLANSHIP_FK SIM_PLANSHIP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PROCESSALGBATCH_FK SIM_PROCESSALGBATCH


- SIMULATION_NAME

SIM_PROCESSSKU_FK SIM_PROCESSSKU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_PRODFAMILYRESMAP_FK

SIM_PRODUCTIONFAMILYRESMAP


- SIMULATION_NAME

SIM_PRODFAMILYSKULOAD_FK

SIM_PRODUCTIONFAMILYSKULOAD


- SIMULATION_NAME

SIM_PRODITEMPROJ_FK SIM_PRODITEMPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PRODPROJ_FK SIM_PRODPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PRODREQUIREMENT_FK SIM_PRODREQUIREMENT


- SIMULATION_NAME

SIM_PRODRESPROJ_FK SIM_PRODRESPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PRODUCTIONCONSTRAINT_FK

SIM_PRODUCTIONCONSTRAINT


- SIMULATION_NAME

SIM_PRODUCTIONCOST_FK SIM_PRODUCTIONCOST


- SIMULATION_NAME

SIM_PRODUCTIONFAMILYCHGOVER_FK

SIM_PRODUCTIONFAMILYCHGOVER


- SIMULATION_NAME

SIM_PRODUCTIONFAMILYLOAD_FK

SIM_PRODUCTIONFAMILYLOAD


- SIMULATION_NAME

SIM_PRODUCTIONFAMILY_FK

SIM_PRODUCTIONFAMILY


- SIMULATION_NAME

SIM_PRODUCTIONLEADTIME_FK

SIM_PRODUCTIONLEADTIME


- SIMULATION_NAME

SIM_PRODUCTIONMETHOD_FK

SIM_PRODUCTIONMETHOD


- SIMULATION_NAME

SIM_PRODUCTIONMETRIC_FK

SIM_PRODUCTIONMETRIC


- SIMULATION_NAME

SIM_PRODUCTIONPENALTY_FK

SIM_PRODUCTIONPENALTY


- SIMULATION_NAME

SIM_PRODUCTIONRESMETRIC_FK

SIM_PRODUCTIONRESMETRIC


- SIMULATION_NAME

SIM_PRODUCTIONSTEP_FK SIM_PRODUCTIONSTEP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_PRODUCTIONYIELD_FK SIM_PRODUCTIONYIELD


- SIMULATION_NAME

SIM_PURCHMETHOD_FK SIM_PURCHMETHOD - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PURCHORDER_FK SIM_PURCHORDER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_PURCHREQUIREMENT_FK

SIM_PURCHREQUIREMENT


- SIMULATION_NAME

SIM_PWTORDACTOUTPUT_FK

SIM_PWTORDACTOUTPUT


- SIMULATION_NAME

SIM_RECSHIP_FK SIM_RECSHIP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RECSUBINVENTORY_FK SIM_RECSUBINVENTORY


- SIMULATION_NAME

SIM_REDUCEDCOSTPROD_FK

SIM_REDUCEDCOSTPRODUCTION


- SIMULATION_NAME

SIM_REDUCEDCOSTRES_FK SIM_REDUCEDCOSTRES


- SIMULATION_NAME

SIM_REDUCEDCOSTSKU_FK SIM_REDUCEDCOSTSKU


- SIMULATION_NAME

SIM_REDUCEDCOSTSOURCING_FK

SIM_REDUCEDCOSTSOURCING


- SIMULATION_NAME

SIM_REDUCEDCOSTTIER SIM_REDUCEDCOSTTIER


- SIMULATION_NAME

SIM_REPORTAGGREGATES_FK

SIM_REPORTAGGREGATES


- SIMULATION_NAME

SIM_RESCONSTRAINT_FK SIM_RESCONSTRAINT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESCOST_FK SIM_RESCOST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESEXCEPTION_FK SIM_RESEXCEPTION - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESLOADDETAIL_FK SIM_RESLOADDETAIL - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_RESLOADREQUIREMENT_FK

SIM_RESLOADREQUIREMENT


- SIMULATION_NAME

SIM_RESMETRIC_FK SIM_RESMETRIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESOINDEPENDENTDMD_FK

SIM_RESOINDEPENDENTDMD


- SIMULATION_NAME

SIM_RESOIN_FK SIM_RESOIN - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESOSUPPLYDETAIL_FK SIM_RESOSUPPLYDETAIL


- SIMULATION_NAME

SIM_RESPENALTY_FK SIM_RESPENALTY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESPROJSTATIC_FK SIM_RESPROJSTATIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESPROJ_FK SIM_RESPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RESSUBTYPE_FK SIM_RESSUBTYPE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_RES_FK SIM_RES - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SCHEDRCPTSDETAIL_FK01

SIM_SCHEDRCPTSDETAIL


- SIMULATION_NAME

SIM_SCHEDRCPTS_FK SIM_SCHEDRCPTS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SEASONLIB_FK SIM_SEASONLIB - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SEASONPROFILEVALUES_FK

SIM_SEASONPROFILEVALUES


- SIMULATION_NAME

SIM_SEASONPROFILE_FK SIM_SEASONPROFILE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SETUPCONSTRAINT_FK SIM_SETUPCONSTRAINT


- SIMULATION_NAME

SIM_SETUPCOST_FK SIM_SETUPCOST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_SETUP_FK SIM_SETUP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUCLASSOPTIONS_FK1

SIM_SKUCLASSOPTIONS


- SIMULATION_NAME

SIM_SKUCLASS_FK1 SIM_SKUCLASS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUCONSTRAINT_FK SIM_SKUCONSTRAINT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUCOST_FK SIM_SKUCOST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUDEMANDPARAM_FK SIM_SKUDEMANDPARAM


- SIMULATION_NAME

SIM_SKUDEMANDTYPEPARAM_FK

SIM_SKUDEMANDTYPEPARAM


- SIMULATION_NAME

SIM_SKUDEPLOYMENTPARAM_FK

SIM_SKUDEPLOYMENTPARAM


- SIMULATION_NAME

SIM_SKUDISPLAY_FK SIM_SKUDISPLAY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUEFFINVPARAM_FK01

SIM_SKUEFFINVENTORYPARAM


- SIMULATION_NAME

SIM_SKUEXCEPTION_FK SIM_SKUEXCEPTION - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUEXTERNALFCST_FK SIM_SKUEXTERNALFCST


- SIMULATION_NAME

SIM_SKUHIST SIM_SKUHIST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUHISTFCST_FK SIM_SKUHISTFCST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUIPOPARAM_FK1 SIM_SKUIPOPARAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUMATALOCPARAM_FK SIM_SKUMATALLOCPARAM


- SIMULATION_NAME

SIM_SKUMETRIC_FK SIM_SKUMETRIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_SKUPENALTY_FK SIM_SKUPENALTY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUPERISHABLEPARAM_FK

SIM_SKUPERISHABLEPARAM


- SIMULATION_NAME

SIM_SKUPLANNINGPARAM_FK

SIM_SKUPLANNINGPARAM


- SIMULATION_NAME

SIM_SKUPROJSTATIC_FK SIM_SKUPROJSTATIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUPROJ_FK SIM_SKUPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKURESPROJ_FK SIM_SKURESPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUSAFETYSTOCKPARAM_FK

SIM_SKUSAFETYSTOCKPARAM


- SIMULATION_NAME

SIM_SKUSTATSTATIC_FK SIM_SKUSTATSTATIC - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKUSUPPLYPARAM_FK SIM_SKUSUPPLYPARAM


- SIMULATION_NAME

SIM_SKU_FK SIM_SKU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SKU_NETCHANGE_SIM_CAT_FK1

SIMULATION_SKU_NETCHANGE


- SIMULATION_NAME

SIM_SLCCURVEATTRIB_FK SIM_SLCCURVEATTRIB - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SLCCURVE_FK SIM_SLCCURVE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SLCPARAM_FK SIM_SLCPARAM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SLCSTATS_FK SIM_SLCSTATS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SMOOTHSEASON_FK SIM_SMOOTHSEASON - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SOURCINGCONSTRAINT_FK

SIM_SOURCINGCONSTRAINT


- SIMULATION_NAME


Table Relationships



SIM_SOURCINGCOST_FK SIM_SOURCINGCOST - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SOURCINGDRAW_FK SIM_SOURCINGDRAW - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SOURCINGGROUP_FK SIM_SOURCINGGROUP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SOURCINGLEADTIME_FK

SIM_SOURCINGLEADTIME


- SIMULATION_NAME

SIM_SOURCINGMETRIC_FK SIM_SOURCINGMETRIC


- SIMULATION_NAME

SIM_SOURCINGPENALTY_FK SIM_SOURCINGPENALTY


- SIMULATION_NAME

SIM_SOURCINGPROJ_FK SIM_SOURCINGPROJ - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SOURCINGREQUIREMENT_FK

SIM_SOURCINGREQUIREMENT


- SIMULATION_NAME

SIM_SOURCINGRESMETRIC_FK

SIM_SOURCINGRESMETRIC


- SIMULATION_NAME

SIM_SOURCINGRESPROJ_FK SIM_SOURCINGRESPROJ


- SIMULATION_NAME

SIM_SOURCINGUOMCONVFACTOR_FK

SIM_SOURCINGUOMCONVFACTOR


- SIMULATION_NAME

SIM_SOURCINGYIELD_FK SIM_SOURCINGYIELD - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SOURCING_FK SIM_SOURCING - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SSBAND_FK SIM_SSBAND - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SSPRESENTATION_FK SIM_SSPRESENTATION - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SSTEMPLATEDATA_FK SIM_SSTEMPLATEDATA - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SSTEMPLATE_FK SIM_SSTEMPLATE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_SS_FK SIM_SS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_STATSS SIM_STATSS - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_STATSSCOV_FK1 SIM_STATSSCOV - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_STOCKORDERSTATUS_FK

SIM_STOCKORDERSTATUS


- SIMULATION_NAME

SIM_STOCKORDER_FK SIM_STOCKORDER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_STORAGEREQUIREMENT_FK

SIM_STORAGEREQUIREMENT


- SIMULATION_NAME

SIM_SUBSTITEM_FK SIM_SUBSTITEM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SUBSTLEVEL_FK SIM_SUBSTLEVEL - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SUBSTRULE_FK SIM_SUBSTRULE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SUPERSESSION_FK SIM_SUPERSESSION - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_SUPPLYPLANACTION_FK SIM_SUPPLYPLANACTION


- SIMULATION_NAME

SIM_SUPPLYPLANRESULT_FK SIM_SUPPLYPLANRESULT


- SIMULATION_NAME

SIM_SUPPORDERSKU_FK SIM_SUPPORDERSKU - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_TARGETDFUMAP_FK SIM_TARGETDFUMAP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_TARGET_FK SIM_TARGET - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_TRANSMODECAP_FK SIM_TRANSMODECAP - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_TRANSMODE_FK SIM_TRANSMODE - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SIM_TRANSORDERDEPDMD_FK

SIM_TRANSORDERDEPDMD


- SIMULATION_NAME

SIM_TRANSORDER_FK SIM_TRANSORDER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_TRANSPORTSCHED_FK SIM_TRANSPORTSCHED


- SIMULATION_NAME

SIM_TYPEEFFECTIVITY_FK SIM_TYPEEFFECTIVITY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_UOMCATEGORYCONVFACTOR_FK

SIM_UOMCATEGORYCONVFACTOR


- SIMULATION_NAME

SIM_UOMCATEGORY_FK SIM_UOMCATEGORY - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_UOM_FK SIM_UOM - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_VEHICLELOADLINE_FK SIM_VEHICLELOADLINE


- SIMULATION_NAME

SIM_VEHICLELOADTOTAL_FK SIM_VEHICLELOADTOTAL


- SIMULATION_NAME

SIM_VEHICLELOAD_FK SIM_VEHICLELOAD - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_VENDORMASTER_FK1 SIM_VENDORMASTER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_WFMFCSTSTRUCT_FK SIM_WFMFCSTSTRUCT - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME

SIM_WORKCENTERLOADDETAILS_FK

SIM_WORKCENTERLOADDETAILS


- SIMULATION_NAME

SIM_WORKCENTERLOADPROFILE_FK

SIM_WORKCENTERLOADPROFILE


- SIMULATION_NAME

SIM_WORKORDERDEPDMD_FK

SIM_WORKORDERDEPDMD


- SIMULATION_NAME

SIM_WORKORDERPROFILE_FK

SIM_WORKORDERPROFILE


- SIMULATION_NAME

SIM_WORKORDER_FK SIM_WORKORDER - SIMULATION_NAME SIMULATION_CATALOG

- SIMULATION_NAME


Table Relationships



SKUBREAKPOINT_SKU_FK1 SKUBREAKPOINT - ITEM - SOURCE SKU - ITEM - LOC SKUBREAKPOINT_SKU_FK2 SKUBREAKPOINT - ITEM - DEST SKU - ITEM - LOC SKUBREAKPOINT_UOM SKUBREAKPOINT - UOM UOM - UOM SKUCLASSDEFDETAIL_FK1 SKUCLASSDEFINITION

DETAIL - CLASSNAME SKUCLASSDEFINITIO

N - CLASSNAME

SKUCLASS_SKUCLASSOPT_FK2

SKUCLASS - SKUCLASSRUN SKUCLASSOPTIONS - SKUCLASSRUN

SKUCLASS_SKU_FK1 SKUCLASS - ITEM - LOC SKU - ITEM - LOC SKUCOLLABFCSTDATA_RC_FK

SKUCOLLABFCSTDATA - REASONCODEID REASONCODES - REASONCODEID

SKUCOLLABFCSTDATA_SKU_FK1

SKUCOLLABFCSTDATA - ITEM - LOC SKU - ITEM - LOC

SKUCONSTRAINT_SKU_FK1 SKUCONSTRAINT - ITEM - LOC SKU - ITEM - LOC SKUCONSTRAINT_UOM_FK1 SKUCONSTRAINT - QTYUOM UOM - UOM SKUCONSTR_CONSTRCATEGORY_FK1

SKUCONSTRAINT - CATEGORY CONSTRAINTCATEGORY

- CATEGORY

SKUCOST_COSTCATEGORY_FK1

SKUCOST - CATEGORY COSTCATEGORY - CATEGORY

SKUCOST_COST_FK1 SKUCOST - LOCALCOST COST - COST SKUCOST_COST_FK2 SKUCOST - TIEREDCOST COST - COST SKUCOST_SKU_FK1 SKUCOST - ITEM - LOC SKU - ITEM - LOC SKUDEMANDPARAM_CAL_FK1

SKUDEMANDPARAM - ALLOCCAL CAL - CAL

SKUDEMANDPARAM_DMDRED_FK1

SKUDEMANDPARAM - DMDREDID DMDRED - DMDREDID

SKUDEMANDPLAN_SKU_FK1 SKUDEMANDPARAM - ITEM - LOC SKU - ITEM - LOC SKUDEMANDTYPEPARAM_SKU_FK1

SKUDEMANDTYPEPARAM


SKUDEPLOYMENTPARAM_CAL_FK1

SKUDEPLOYMENTPARAM

- RECSHIPCAL CAL - CAL

SKUDEPLOYMENTPLAN_SKU_FK1

SKUDEPLOYMENTPARAM



Table Relationships



SKUDISPLAY_SKU_FK1 SKUDISPLAY - ITEM - LOC SKU - ITEM - LOC SKUEFFINVPARAM_SKU_FK1 SKUEFFINVENTORYPAR

AM - ITEM - LOC SKU - ITEM - LOC

SKUEXCEPTION_SKU_FK1 SKUEXCEPTION - ITEM - LOC SKU - ITEM - LOC SKUEXTERNALFCST_SKU_FK SKUEXTERNALFCST - ITEM - LOC SKU - ITEM - LOC SKUFACTSDATA_SKU_FK1 SKUFACTSDATA - ITEM - LOC SKU - ITEM - LOC SKUHISTFCST_SKU_FK SKUHISTFCST - ITEM - LOC SKU - ITEM - LOC SKUHIST_SKU_FK SKUHIST - ITEM - LOC SKU - ITEM - LOC SKUIPOPARAM_IPOFUND_FK1

SKUIPOPARAM - FUNDNAME IPOFUND - FUNDNAME

SKUIPOPARAM_IPOGROUP_FK2

SKUIPOPARAM - GROUPNAME IPOGROUP - GROUPNAME

SKUIPOPARAM_SKU_FK3 SKUIPOPARAM - ITEM - LOC SKU - ITEM - LOC SKUMATALLOCPARAM_SKU_FK1

SKUMATALLOCPARAM - ITEM - LOC SKU - ITEM - LOC

SKUMETRIC_CURRUOM_FK SKUMETRIC - CURRENCYUOM UOM - UOM SKUMETRIC_METRICCATEGORY_FK1

SKUMETRIC - CATEGORY METRICCATEGORY - CATEGORY

SKUMETRIC_QTYUOM_FK SKUMETRIC - QTYUOM UOM - UOM SKUMETRIC_SKU_FK1 SKUMETRIC - ITEM - LOC SKU - ITEM - LOC SKUPENALTY_PENALTYCAT_FK1

SKUPENALTY - CATEGORY PENALTYCATEGORY - CATEGORY

SKUPENALTY_SKU_FK1 SKUPENALTY - ITEM - LOC SKU - ITEM - LOC SKUPENALTY_UOM_FK1 SKUPENALTY - QTYUOM UOM - UOM SKUPENALTY_UOM_FK2 SKUPENALTY - CURRENCYUOM UOM - UOM SKUPERISHABLEPARAM_SKU_FK1

SKUPERISHABLEPARAM - ITEM - LOC SKU - ITEM - LOC

SKUPLANNINGPARAM_CAL_FK1

SKUPLANNINGPARAM - PRODCAL CAL - CAL

SKUPLANNINGPARAM_CAL_FK2

SKUPLANNINGPARAM - WORKINGCAL CAL - CAL


Table Relationships



SKUPLANNINGPARAM_SKU_FK1

SKUPLANNINGPARAM - ITEM - LOC SKU - ITEM - LOC

SKUPLANNINGPARAM_UOM_FK1

SKUPLANNINGPARAM - COSTUOM UOM - UOM

SKUPROJ_SKU_FK1 SKUPROJ - ITEM - LOC SKU - ITEM - LOC SKUPROJ_UOM_FK1 SKUPROJ - NUMERATORUOM UOM - UOM SKUPROJ_UOM_FK2 SKUPROJ - DENOMINATORUOM UOM - UOM SKUPROJ_UOM_FK3 SKUPROJ - ADDITIONALUOM UOM - UOM SKURESPROJ_RES_FK1 SKURESPROJ - RES RES - RES SKURESPROJ_SKU_FK1 SKURESPROJ - ITEM - LOC SKU - ITEM - LOC SKURESPROJ_UOM_FK1 SKURESPROJ - NUMERATORUOM UOM - UOM SKURESPROJ_UOM_FK2 SKURESPROJ - DENOMINATORUOM UOM - UOM SKURESPROJ_UOM_FK3 SKURESPROJ - ADDITIONALUOM UOM - UOM SKUROOTCAUSE_FK1 SKUROOTCAUSE - ITEM - LOC SKU - ITEM - LOC SKUSAFETYSTKPRM_CSLTEMPLT_FK1

SKUSAFETYSTOCKPARAM

- CSLTEMPLATE CSLTEMPLATE - CSLTEMPLATE

SKUSAFETYSTOCKPARAM_CAL_FK1

SKUSAFETYSTOCKPARAM

- AVGDMDCAL CAL - CAL

SKUSAFETYSTOCKPARAM_CAL_FK2

SKUSAFETYSTOCKPARAM

- DMDCAL CAL - CAL

SKUSAFETYSTOCKPARAM_SST_FK

SKUSAFETYSTOCKPARAM

- SSTEMPLATE SSTEMPLATE - SSTEMPLATE

SKUSSHIST_SKU_FK1 SKUSSHIST - ITEM - LOC SKU - ITEM - LOC SKUSTOCKHIST_SKU_FK1 SKUSTOCKHIST - ITEM - LOC SKU - ITEM - LOC SKUSUPPLYPARAM_CAL_FK1 SKUSUPPLYPARAM - CAL CAL - CAL SKUSUPPLYPARAM_SKU_FK1 SKUSUPPLYPARAM - ITEM - LOC SKU - ITEM - LOC SKU_ITEM_FK1 SKU - ITEM ITEM - ITEM SKU_LOC_FK1 SKU - LOC LOC - LOC SKU_LTDGROUP_FK SKU - LTDGROUP LTDGROUP - LTDGROUP SKU_SOURCINGGROUP_FK1 SKU - SOURCINGGROUP SOURCINGGROUP - SOURCINGGROUP SKU_UOM_FK3 SKU - CURRENCYUOM UOM - UOM


Table Relationships



SKU_UOM_FK4 SKU - QTYUOM UOM - UOM SKU_UOM_FK5 SKU - TIMEUOM UOM - UOM SLCCURATTRIB_SLCCURVE_FK1

SLCCURVEATTRIB - CURVEID SLCCURVE - CURVEID

SLCPARAM_DFU_FK1 SLCPARAM - DMDUNIT - DMDGROUP - LOC - MODEL


SLCSTATS_DFU_FK1 SLCSTATS - DMDUNIT - DMDGROUP - LOC - MODEL


SLCURATTRIBUTE_DFUATTRIB_FK1

SLCCURVEATTRIB - ATTRIBNAME - DFUATTRIBGROUP

DFUATTRIB - ATTRIBNAME - DFUATTRIBGROUP

SMFILTER_TO_STOREDMEASURE

STOREDMEASUREFILTERCRITERIA

- MEASUREID STOREDMEASURE - MEASUREID

SOURCINGCONSTRAINT_SOURCING_FK

SOURCINGCONSTRAINT



SOURCINGCONSTRAINT_UOM_FK1

SOURCINGCONSTRAINT

- QTYUOM UOM - UOM

SOURCINGCONSTR_CONSTRCAT_FK1

SOURCINGCONSTRAINT

- CATEGORY CONSTRAINTCATEGORY

- CATEGORY

SOURCINGCOST_COSTCATEGORY_FK1

SOURCINGCOST - CATEGORY COSTCATEGORY - CATEGORY

SOURCINGCOST_COST_FK1 SOURCINGCOST - LOCALCOST COST - COST SOURCINGCOST_COST_FK2 SOURCINGCOST - TIEREDCOST COST - COST SOURCINGCOST_SOURCING_FK1

SOURCINGCOST - SOURCING - ITEM - SOURCE - DEST


SOURCINGDRAW_SOURCING_FK1

SOURCINGDRAW - SOURCING - ITEM - SOURCE - DEST


SOURCINGDRAW_UOM_FK1 SOURCINGDRAW - QTYUOM UOM - UOM SOURCINGGROUP_UOM_FK1 SOURCINGGROUP - QTYUOM UOM - UOM SOURCINGLEADTIME_SOURCING_FK1

SOURCINGLEADTIME - SOURCING - ITEM - SOURCE - DEST


SOURCINGMETRIC_CURRUO SOURCINGMETRIC - CURRENCYUOM UOM - UOM


Table Relationships



M_FK SOURCINGMETRIC_METRICCAT_FK1

SOURCINGMETRIC - CATEGORY METRICCATEGORY - CATEGORY

SOURCINGMETRIC_QTYUOM_FK

SOURCINGMETRIC - QTYUOM UOM - UOM

SOURCINGMETRIC_SOURCING_FK1

SOURCINGMETRIC - SOURCING - ITEM - SOURCE - DEST


SOURCINGPENALTY_PENALTYCAT_FK1

SOURCINGPENALTY - CATEGORY PENALTYCATEGORY - CATEGORY

SOURCINGPENALTY_SOURCING_FK1

SOURCINGPENALTY - SOURCING - ITEM - SOURCE - DEST


SOURCINGPENALTY_UOM_FK1

SOURCINGPENALTY - QTYUOM UOM - UOM

SOURCINGPENALTY_UOM_FK2

SOURCINGPENALTY - CURRENCYUOM UOM - UOM

SOURCINGPROJ_SOURCING_FK1

SOURCINGPROJ - SOURCING - ITEM - SOURCE - DEST


SOURCINGPROJ_UOM_FK1 SOURCINGPROJ - NUMERATORUOM UOM - UOM SOURCINGPROJ_UOM_FK2 SOURCINGPROJ - DENOMINATORUOM UOM - UOM SOURCINGPROJ_UOM_FK3 SOURCINGPROJ - ADDITIONALUOM UOM - UOM SOURCINGREQMT_SOURCING_FK1

SOURCINGREQUIREMENT



SOURCINGREQUIREMENT_RES_FK1

SOURCINGREQUIREMENT

- RES RES - RES

SOURCINGREQUIREMENT_UOM_FK1

SOURCINGREQUIREMENT

- QTYUOM UOM - UOM

SOURCINGRESMETRIC_CURRUOM_FK

SOURCINGRESMETRIC - CURRENCYUOM UOM - UOM

SOURCINGRESMETRIC_METRICCAT_FK

SOURCINGRESMETRIC - CATEGORY METRICCATEGORY - CATEGORY

SOURCINGRESMETRIC_QTYUOM_FK

SOURCINGRESMETRIC - QTYUOM UOM - UOM

SOURCINGRESMETRIC_RES_ SOURCINGRESMETRIC - RES RES - RES


Table Relationships



FK SOURCINGRESMETRIC_SOURCING_FK

SOURCINGRESMETRIC - SOURCING - ITEM - SOURCE - DEST


SOURCINGRESPROJ_RES_FK1

SOURCINGRESPROJ - RES RES - RES

SOURCINGRESPROJ_SOURCING_FK1

SOURCINGRESPROJ - SOURCING - ITEM - SOURCE - DEST


SOURCINGRESPROJ_UOM_FK1

SOURCINGRESPROJ - NUMERATORUOM UOM - UOM


SOURCINGRESPROJ - DENOMINATORUOM UOM - UOM


SOURCINGRESPROJ - ADDITIONALUOM UOM - UOM

SOURCINGTARGET_SOURCING_FK1

SOURCINGTARGET - SOURCING - ITEM - SOURCE - DEST


SOURCINGUOMCONVFACTOR_UOM_FK1

SOURCINGUOMCONVFACTOR

- SOURCEUOM UOM - UOM

SOURCINGUOMCONVFACTOR_UOM_FK2


- TARGETUOM UOM - UOM

SOURCINGUOMCONVF_ITEM_FK1


- ITEM ITEM - ITEM

SOURCINGUOMCONVF_NETWORK_FK1


- SOURCE - TRANSMODE - DEST NETWORK - SOURCE - TRANSMODE - DEST

SOURCINGUOMCONVF_UOMCATG_FK1


- SOURCECATEGORY UOMCATEGORY - CATEGORY

SOURCINGUOMCONVF_UOMCATG_FK2


- TARGETCATEGORY UOMCATEGORY - CATEGORY

SOURCINGYIELD_SOURCING_FK1

SOURCINGYIELD - SOURCING - ITEM - SOURCE - DEST


SOURCINGYIELD_UOM_FK1 SOURCINGYIELD - QTYUOM UOM - UOM SOURCING_CAL_FK1 SOURCING - ARRIVCAL CAL - CAL SOURCING_CAL_FK3 SOURCING - REVIEWCAL CAL - CAL SOURCING_OG_FK1 SOURCING - ORDERGROUP ORDERGROUP - ORDERGROUP


Table Relationships



SOURCING_SHIPCAL_FK SOURCING - SHIPCAL CAL - CAL SOURCING_SKU_FK1 SOURCING - ITEM - SOURCE SKU - ITEM - LOC SOURCING_SKU_FK2 SOURCING - ITEM - DEST SKU - ITEM - LOC SOURCING_TRANSMODE_FK1

SOURCING - TRANSMODE TRANSMODE - TRANSMODE

SRCDMD_FK DFUATTACHRATERELATION

- SOURCEDMDUNIT DMDUNIT - DMDUNIT

SSPRESENTATION_SKU_FK1 SSPRESENTATION - ITEM - LOC SKU - ITEM - LOC SSTEMPLATEDATA_SSTEMPLATE_FK1

SSTEMPLATEDATA - SSTEMPLATE SSTEMPLATE - SSTEMPLATE

SS_SKU_FK1 SS - ITEM - LOC SKU - ITEM - LOC STATSS_SKU_FK1 STATSS - ITEM - LOC SKU - ITEM - LOC STOCKORDER_SKU_FK1 STOCKORDER - ITEM - LOC SKU - ITEM - LOC STOCKORDSTATUS_STOCKORDER_FK1

STOCKORDERSTATUS - ITEM - LOC - SEQNUM STOCKORDER - ITEM - LOC - SEQNUM

STORAGEREQUIREMENT_RES_FK1

STORAGEREQUIREMENT

- RES RES - RES

STORAGEREQUIREMENT_SKU_FK1

STORAGEREQUIREMENT


STOREDMEASURE_TO_MEASURE

STOREDMEASURE - MEASUREID MEASURE - MEASUREID

SUBEVENT_DFU_FK1 SUBEVENT - DMDUNIT - DMDGROUP - LOC - MODEL


SUBEVENT_EVENT_FK1 SUBEVENT - EVENT EVENT - EVENT SUBEVENT_PROFILE_FK1 SUBEVENT - PROFILE PROFILE - PROFILE SUBSTITEM_ITEM_FK1 SUBSTITEM - ITEM ITEM - ITEM SUBSTITEM_ITEM_FK2 SUBSTITEM - SUBSTITUTE ITEM - ITEM SUBSTRULE_SKU_FK1 SUBSTRULE - SUBSTITEM - SUBSTLOC SKU - ITEM - LOC SUBSTRULE_SKU_FK2 SUBSTRULE - PARENTITEM - PARENTLOC SKU - ITEM - LOC SUBSTRULE_SKU_FK3 SUBSTRULE - COMPONENTITEM -

COMPONENTLOC SKU - ITEM - LOC


Table Relationships



SUBSTRULE_SUBSTLEVEL_FK1

SUBSTRULE - SUBSTLEVEL SUBSTLEVEL - SUBSTLEVEL

SUPERSESSION_ITEM_FK1 SUPERSESSION - ITEM ITEM - ITEM SUPERSESSION_ITEM_FK2 SUPERSESSION - ALTITEM ITEM - ITEM SUPERSESSION_LOC_FK SUPERSESSION - LOC LOC - LOC SUPPLYMETHOD_SKU_FK1 SUPPLYMETHOD - ITEM - LOC SKU - ITEM - LOC SUPPLYPLANACTION_SKU_FK1

SUPPLYPLANACTION - ITEM - LOC SKU - ITEM - LOC

SUPPLYPLANRESULT_ITEM_FK

SUPPLYPLANRESULT - SUBSTITEM ITEM - ITEM

SUPPLYPLANRESULT_LOC_FK SUPPLYPLANRESULT - SUBSTLOC LOC - LOC SUPPLYPLANRESULT_SKU_FK1

SUPPLYPLANRESULT - ITEM - LOC SKU - ITEM - LOC

SUPPORDERSKU_R01 SUPPORDERSKU - ITEM - LOC SKU - ITEM - LOC SURVCURVEDATA_SURVCURVE_FK1

SURVIVALCURVEDATA - SURVIVALCURVE SURVIVALCURVE - SURVIVALCURVE

TARGETDFUMAP_DFU_FK1 TARGETDFUMAP - DMDUNIT - DMDGROUP - LOC - MODEL


TARGETDFUMAP_TARGET_FK1

TARGETDFUMAP - TARGET TARGET - TARGET

TARGET_CAL_FK1 TARGET - DMDCAL CAL - CAL TGTDMD_FK DFUATTACHRATERELAT

ION - TARGETDMDUNIT DMDUNIT - DMDUNIT

TIME_HIERARCHY_FK TIMEHIERARCHY - DMDCAL CAL - CAL TRANSLEADTIMEPARAM_SKU_FK1

TRANSLEADTIMEPARAM

- ITEM - SOURCE SKU - ITEM - LOC

TRANSLEADTIMEPARAM_SKU_FK2

TRANSLEADTIMEPARAM

- ITEM - DEST SKU - ITEM - LOC

TRANSMODECAP_TRANSMODE_FK1

TRANSMODECAP - TRANSMODE TRANSMODE - TRANSMODE

TRANSMODECAP_UOM_FK1 TRANSMODECAP - UOM UOM - UOM


Table Relationships



TRANSORDERDEPDMD_SKU_FK1

TRANSORDERDEPDMD - ITEM - SOURCE SKU - ITEM - LOC

TRANSORDERDEPDMD_SKU_FK2

TRANSORDERDEPDMD - ITEM - DEST SKU - ITEM - LOC

TRANSORDERDEPDMD_TRANSORDER_FK

TRANSORDERDEPDMD - ORDERLINE - ORDERNUM TRANSORDER - ORDERLINE - ORDERNUM

TRANSORDER_SKU_FK1 TRANSORDER - ITEM - SOURCE SKU - ITEM - LOC TRANSORDER_SKU_FK2 TRANSORDER - ITEM - DEST SKU - ITEM - LOC TRANSPORTSCHED_NETWORK_FK1

TRANSPORTSCHED - SOURCE - TRANSMODE - DEST NETWORK - SOURCE - TRANSMODE - DEST

TYPEEFFECTIVITY_SKU_FK1 TYPEEFFECTIVITY - ITEM - LOC SKU - ITEM - LOC UDT_CONSENSUS_PLANNING_1_FK

UDT_CONSENSUS_PLANNING_1


UDT_CONSENSUS_PLANNING_2_FK

UDT_CONSENSUS_PLANNING_2


UDT_EXTERNAL_INPUTS_1_FK

UDT_EXTERNAL_INPUTS_1


UDT_RETAIL_MEASURES_1_FK

UDT_RETAIL_MEASURES_1


UOMCATCONVFACTOR_ITEM_FK1

UOMCATEGORYCONVFACTOR

- ITEM ITEM - ITEM

UOMCATCONVFACTOR_SOURCEUOM_FK


- SOURCEUOM UOM - UOM

UOMCATCONVFACTOR_TARGETUOM_FK


- TARGETUOM UOM - UOM

UOMCATCONVFACTOR_UOMCAT_FK1


- SOURCECATEGORY UOMCATEGORY - CATEGORY

UOMCATCONVFACTOR_UOMCAT_FK2


- TARGETCATEGORY UOMCATEGORY - CATEGORY

UOMCATEGORY_UOM_FK2 UOMCATEGORY - STDUOM UOM - UOM UOM_FK PRICERULESELATTRIB - BASEUOM UOM - UOM UOM_UOMCATEGORY_FK1 UOM - CATEGORY UOMCATEGORY - CATEGORY


Table Relationships



USERPERSONAFK1 USERPERSONA - PERSONANAME PERSONA - PERSONANAME VEHICLELOADLINE_ITEM_FK2

VEHICLELOADLINE - PRIMARYITEM ITEM - ITEM

VEHICLELOADLINE_SKU_FK1 VEHICLELOADLINE - ITEM - SOURCE SKU - ITEM - LOC VEHICLELOADLINE_SKU_FK2 VEHICLELOADLINE - ITEM - DEST SKU - ITEM - LOC VEHICLELOADLINE_VL_FK1 VEHICLELOADLINE - LOADID VEHICLELOAD - LOADID VEHICLELOADTOTAL_VLOAD_FK1

VEHICLELOADTOTAL - LOADID VEHICLELOAD - LOADID

VEHICLELOAD_TRANSMODE_FK1

VEHICLELOAD - TRANSMODE TRANSMODE - TRANSMODE

VENDORMASTER_SKU_FK1 VENDORMASTER - ITEM - LOC SKU - ITEM - LOC WDDCATAREAMAP_WDDAREA_FK2

WDDCATEGORYAREAMAP

- WDDAREA WDDAREA - WDDAREA

WDDCATAREAMAP_WDDCATEGORY_FK1

WDDCATEGORYAREAMAP

- WDDCATEGORY WDDCATEGORY - WDDCATEGORY

WDDDATA_WDDAREA_FK2 WDDDATA - WDDAREA WDDAREA - WDDAREA WDDDATA_WDDCATEGORY_FK1

WDDDATA - WDDCATEGORY WDDCATEGORY - WDDCATEGORY

WEBPEGCOLOPTS_FK1 WEBPEGCOLOPTS - USERID - INSTANCE - PEGNAME - LISTING_NAME

WEBPEGOPTS - USERID - INSTANCE - PEGNAME - LISTING_NAME

WORKORDERDEPDMD_SKU_FK1

WORKORDERDEPDMD - ITEM - LOC SKU - ITEM - LOC

WORKORDERDEPDMD_SKU_FK2

WORKORDERDEPDMD - PARENTITEM - LOC SKU - ITEM - LOC

WORKORDERDEPDMD_WORKORDER_FK1

WORKORDERDEPDMD - WORKORDERNUM - LOT WORKORDER - WORKORDERNUM - LOT

WORKORDER_SKU_FK1 WORKORDER - ITEM - LOC SKU - ITEM - LOC XIF3PRICESCENARIODETAIL PRICESCENARIODETAI

L - PRICESCENARIO PRICESCENARIO - PRICESCENARIO


Processes part 1: input and output tables

Chapter 4. Processes part 1: input and output tables Table name Process name

Add/ Updat

e Model

s proces

s

Assign Short

Lifecycle Curve process

Build Seasonal Profile Collecti

on Process

Build Short


Calculate E3 Error

process

Calculate

Model proces

s

Classify DFUs and

Tune Paramet

ers process

Delete Foreca

st proces

s

Expand

Calendar

process

Import

Forecast

process

Load Workforc

e Management DFUs process

AVSGravesParam IO I I O O AVSGravesStats Cal I CalData I CalDataExpanded O CausalFactor IO CausalFactorType IO CausalFactorValue IO I I Collection_Info CrostonParam IO I O O DBParam I

DC_AlgorithmRank IO O DC_AVSGravesParam IO O DC_CrostonParam IO O DC_DFUClass IO O DC_DFUClassHist O DC_DFUParam IO O DC_Exception O DC_HoltParam IO O DC_LewParam IO O DC_LinRegParam IO O DC_MovingAvgParam IO O



Table name Process name

Add/ Updat

e Model

s proces

s

Assign Short



on Process

Build Short


Calculate E3 Error

process

Calculate

Model proces

s

Classify DFUs and

Tune Paramet

ers process

Delete Foreca

st proces

s

Expand

Calendar

process

Import

Forecast

process

Load Workforc


DC_Stats O DDEProfile IO I DFU IO IO I I I I O DFUAttrib I I DFUCausalFactor O I I DFUCoeff I IO

DFUDDEMap O I DFUException O O O O O DFUMaintCopyDFU DFUMap IO DFUMovingEventMap I I DFUNPIRelation DFUProjDraftStatic DFUProjStatic DFUtoSKUFcst DFUTotalVal DFUView IO O DmdGroup IO O DmdUnit IO I O Fcst IO IO I FcstDraft IO IO O O FcstLewMeanQtyWide O FcstDraftNarrow IO IO O O FcstDraftWide IO IO O




Add/ Updat

e Model

s proces

s

Assign Short



on Process

Build Short


Calculate E3 Error

process

Calculate

Model proces

s

Classify DFUs and

Tune Paramet

ers process

Delete Foreca

st proces

s

Expand

Calendar

process

Import

Forecast

process

Load Workforc


FcstNarrow IO O FCSTPerfStatic FcstWide IO O FittedHistory O ForecastRecordImport I I Hist I I I I I HistFcst HistFcstEvents HistNarrow I I HistStream IO HistWide I HoltwintersParam IO I I O O HoltwintersStats O LewandoskiParam IO I IO O LewandoskiStats O LewFactor I I LewFactorValue I I LinRegParam IO I O O LinRegStats O Loc IO I O Map IO Mask IO MaskData IO I MeanValueAdj I




Add/ Updat

e Model

s proces

s

Assign Short



on Process

Build Short


Calculate E3 Error

process

Calculate

Model proces

s

Classify DFUs and

Tune Paramet

ers process

Delete Foreca

st proces

s

Expand

Calendar

process

Import

Forecast

process

Load Workforc


Model IO Moving AvgParam IO I I O O MovingAvgStats O MovingAvgWgts I MovingEvent I I MovingEventData I I NPIValidDFU PriceProfileVal ProcessDFU I SCPO_Delete_All I SCPO_Load_All IO SeasonalError SeasonProfile I I SeasonProfileValues I I SKUMap SLCCurve IO O SLCCurveAttrib I O SLCParam I I O SLParam I I SLStats O SmoothSeason I I O SSD_Assignments O SSD_Collection O SSD_Exp_Assignmetn




Add/ Updat

e Model

s proces

s

Assign Short



on Process

Build Short


Calculate E3 Error

process

Calculate

Model proces

s

Classify DFUs and

Tune Paramet

ers process

Delete Foreca

st proces

s

Expand

Calendar

process

Import

Forecast

process

Load Workforc


s SSD_Exp_Profiles SSD_Item_Desc IO SSD_Library O SSD_Loc_Desc IO SSD_POS_Data IO SSD_Profiles O Target IO I TargetDFUMap IO I WFMFcststruct I



Chapter 5. Processes part 2: input and output tables Table name Process name

Map DFUs

process

Merge Foreca

st proces

s

Move History proces

s

NPI by Priority proces

s

Publish

Forecast

process

Reconcile

Forecast process

Reconcile

Forecast Subset process

Store Derive

d Tables proces

s

Store Foreca

st proces

s

Transfer Seasonal

ity Profiles process

Verify DFU Maps

process

AVSGravesParam IO AVSGravesStats Cal CalData CalDataExpanded CausalFactor CausalFactorType CausalFactorValue Collection_Info I CrostonParam IO DBParam I

DC_AlgorithmRank DC_AVSGravesParam DC_CrostonParam DC_DFUClass DC_DFUClassHist DC_DFUParam DC_Exception DC_HoltParam DC_LewParam DC_LinRegParam DC_MovingAvgParam DC_Stats




Map DFUs

process

Merge Foreca

st proces

s

Move History proces

s


s

Publish

Forecast

process

Reconcile

Forecast process

Reconcile


Store Derive

d Tables proces

s

Store Foreca

st proces

s

Transfer Seasonal


Verify DFU Maps

process

DDEProfile IO DFU I I IO I I DFUAttrib DFUCausalFactor IO DFUCoeff IO

DFUDDEMap IO DFUException O IO O O O O O DFUMaintCopyDFU DFUMap I IO I I I DFUMovingEventMap IO DFUNPIRelation IO DFUProjDraftStatic O DFUProjStatic O DFUtoSKUFcst I DFUTotalVal I I DFUView IO DmdGroup DmdUnit Fcst IO O IO O IO IO I FcstDraft IO O IO IO IO I FcstLewMeanQtyWide FcstDraftNarrow IO I I I I I FcstDraftWide IO I I IO IO I FcstNarrow O I I I FCSTPerfStatic O




Map DFUs

process

Merge Foreca

st proces

s

Move History proces

s


s

Publish

Forecast

process

Reconcile

Forecast process

Reconcile


Store Derive

d Tables proces

s

Store Foreca

st proces

s

Transfer Seasonal


Verify DFU Maps

process

FcstWide IO O IO IO I FittedHistory ForecastRecordImport Hist IO I O HistFcst IO I O HistFcstEvents O HistNarrow IO O HistStream HistWide IO O HoltwintersParam IO HoltwintersStats LewandoskiParam IO LewandoskiStats LewFactor IO LewFactorValue IO LinRegParam IO LinRegStats Loc Map Mask MaskData MeanValueAdj IO Model Moving AvgParam IO MovingAvgStats




Map DFUs

process

Merge Foreca

st proces

s

Move History proces

s


s

Publish

Forecast

process

Reconcile

Forecast process

Reconcile


Store Derive

d Tables proces

s

Store Foreca

st proces

s

Transfer Seasonal


Verify DFU Maps

process

MovingAvgWgts MovingEvent MovingEventData NPIValidDFU PriceProfileVal I I ProcessDFU IO SCPO_Delete_All SCPO_Load_All SeasonalError SeasonProfile IO IO SeasonProfileValues IO SKUMap IO SLCCurve SLCCurveAttrib SLCParam SLParam IO SLStats SmoothSeason IO SSD_Assignments SSD_Collection IO SSD_Exp_Assignmetns

I

SSD_Exp_Profiles I SSD_Item_Desc SSD_Library




Map DFUs

process

Merge Foreca

st proces

s

Move History proces

s


s

Publish

Forecast

process

Reconcile

Forecast process

Reconcile


Store Derive

d Tables proces

s

Store Foreca

st proces

s

Transfer Seasonal


Verify DFU Maps

process

SSD_Loc_Desc SSD_POS_Data SSD_Profiles Target IO TargetDFUMap WFMFcststruct



Index A AbsBaseError • 163 AbsNonBaseError • 164 AbsPctDFUToSKUFcstError • 164 AbsPctTotError • 164 AbsTotError • 164 Action_Group_Set_ID • 113 Action_Number • 113 AdjDmdPostDate • 62 AdjRate • 230 AdjustedRSquare • 217 AdjVal • 230 Aggregate_Key • 39 Algorithm • 232 AllocCal • 145 AllocCalGroup • 145 AllocCalProfile • 145 AllocFactor • 138 AllocMethod • 279 AllocPolicy • 188 AllocProfile • 11 AllocProfileCategory • 12 AllocProfileLib • 13 AllocProfileValues • 14 AllocWgt • 27 AltCal • 28 AltPlantID • 222 Applications that include the table • 4 Applications that use the columns • 5 ApplyWgtSW • 235 AttachRateRelationType • 146 Attrib • 79 AttribName • 76, 269 Avail • 30 AvailDate • 270 AverageValue • 207 AvgInterval • 43 AvgRelTrend • 200 AVSGravesParam • 15 AVSGravesStats • 18

B BaseCurrency • 246 BaseError • 164 BaseFcst • 127, 131, 164, 176

BaseHist • 127, 131, 164 BOHQty • 270 Boolean • 7 BorrowingPct • 222 Brand • 149

C Cal • 21, 30, 34 CalcCumLeadTimeSw • 188 CalcModel_KeepReconImpacts • 51 CalcModel_PurgeOpt • 51 CalcModel_UseWeightedStats • 51 CalcStoreFittedHistSw • 52 CalculateDmdToDateSw • 146 CalData • 26 CalDataExpanded • 34 Category • 11, 12, 208 CausalFactor • 35, 38, 78 CausalFactorType • 36 CausalFactorValue • 37, 38 ChangeDate • 285 ChangeType • 285 Coef • 78, 79 CoefVariation • 237 Collection • 149 Collection_Info • 39 Collection_Name • 39 ColName • 76 Column description • 169, 178, 200 Column descriptions • 11, 12, 13, 14, 15, 19, 21, 27, 34, 35,

36, 38, 39, 40, 43, 46, 47, 48, 51, 56, 62, 72, 74, 75, 76, 78, 79, 81, 83, 84, 86, 110, 113, 117, 122, 124, 125, 127, 131, 133, 135, 136, 138, 141, 142, 143, 145, 148, 149, 152, 154, 156, 159, 163, 171, 173, 176,ꁌ180, 181, 184, 188, 195, 203, 204, 205, 206, 207, 208, 210, 217, 222, 226, 227, 228, 229, 230, 232, 234, 236, 239, 240, 241, 242, 243, 245, 246, 247, 248, 249, 250, 252, 253, 256, 258, 268, 269, 270, 271, 273, 275, 277, 279, 280, 281, 282, 283, 284, 285

COMPANY • 133 CompanyID • 222 ConvCol • 152 ConversionValue • 48 ConvFactor • 117, 138 ConvTab • 153 CopyDate • 62 CopyFromDmdGroup • 63 CopyFromDmdUnit • 63 CopyFromLoc • 63 CopyFromModel • 63



CorrFactor • 210 Country • 222 CovDur • 30 CreatedBy • 153 CreatedDate • 153 CreationDate • 126, 258 CrostonParam • 40 CrostonStats • 43 CumActualDmd • 44 CumPredDmd • 44 Currency • 46, 222 CurrencyProfile • 47 CurrencyProfileVal • 48 CurrencyUOM • 258 CurveID • 268, 269 Cust • 222

D Database conventions • 4 Database information • 1 DataDrivenEvents • 127, 131, 164, 176 Datatype • 6 Date and DateTime • 7 DBName • 52 DBParam • 50 DCRank • 63 DDEImpact • 195 DDEProfile • 56 DDEProfileID • 56, 81 DDRGroup • 146 DDRParamProfileName • 146 DDSKUSw • 188 DDSrcCostSw • 188 Decimal • 7 Default values • 8 DefaultDFUMapSw • 52 DefaultUOM • 189 Desc • 206 Descr • 11, 12, 13, 21, 30, 35, 36, 46, 56, 86, 148, 150, 153,

154, 180, 189, 203, 204, 222, 227, 228, 230, 233, 240, 242, 248, 252, 253, 279, 281, 282

DestCal • 223 DFU • 58 DFUAllocProfileMap • 72 DFUAttachRateNorm • 74 DFUAttachRateRelation • 75 DFUAttrib • 76 DFUAttribGroup • 76, 269 DFUCausalFactor • 77

DFUCoef • 79 DFUDDEMap • 81 DFUDepDmdFcst • 83 DFUDepDmdHist • 84 DFUException • 85 DFUExternalFcst • 110 DFULoc • 138, 141 DFUMaintCopyDFU • 112 DFUMap • 116 DFUMapFcstProfile • 122 DFUMovingEventMap • 124 DFUNPIRelation • 125 DFUProjDraftStatic • 127 DFUProjStatic • 130 DFUTOE3FCST • 133 DFUToEPFcst • 135 DFUToItxFcst • 136 DFUToSKU • 137 DFUToSKUFcst • 140, 164, 176 DFUToSKUFcstError • 164 DFUTotalVol • 142 DFUToWFMFcst • 143 DFUView • 144 Disc • 63, 118, 138 DmdCal • 52, 57, 64, 203, 230, 279 DmdFilter • 210 DmdGroup • 15, 19, 39, 40, 44, 57, 64, 72, 78, 79, 81, 83,

84, 86, 110, 124, 128, 131, 135, 138, 141, 142, 143, 146, 148, 156, 159, 165, 169, 171, 173, 176, 178, 182, 184, 195, 200, 210, 217, 231, 234, 236, 245, 250, 271, 273, 275, 277, 280, 285

DmdGroupDescr • 285 DmdPostDate • 64 DmdRateSE • 44 DmdToDateBase • 146 DmdToDateNonBase • 146 DmdUnit • 15, 19, 39, 40, 44, 57, 64, 72, 78, 79, 81, 86,

110, 124, 128, 131, 135, 138, 141, 142, 143, 146, 149, 150, 156, 160, 165, 169, 171, 173, 176, 178, 182, 184, 195, 200, 210, 217, 231, 234, 236, 245, 250, 271, 273, 275, 277, 280, 285

DmdUnitDescr • 285 Documentation information • 1 Dur • 34, 83, 84, 110, 128, 131, 135, 136, 141, 143, 153,

156, 160, 165, 169, 173, 176, 178, 229, 250, 270, 277 Duration • 8, 171 DurbinWatsonStat • 217 DynDepDecimals • 189 DynDepOption • 189 DynDepPushOpt • 189



DynDepQty • 191

E E3 ERROR • 133 E3Error • 64 E3ErrorDate • 64 E3LOC • 133 Eff • 30, 65, 118, 138 EnableDraftPDMs • 52 EnableSw • 191, 223, 258 EndDate • 48, 247, 279 ErrorMsg • 113 EstimateTrendSw • 210 Event • 152, 153, 173, 277 EventType • 79, 153, 154 Exception • 86 ExternalEvents • 165, 176 ExternalInfluenceCoef • 268, 272

F Factor • 118, 249, 251 FactorValue • 207 Fcst • 155 FcstDate • 165, 176, 178 FCSTDELETED • 133 FcstDraft • 159 FcstHor • 65 FcstID • 110, 156, 160, 171, 178 FCSTID • 134 FcstOverride • 128, 131, 165, 176 FcstPerfStatic • 162 FcstType • 119, 138 FcstTypeProfile • 122 FiscalPeriod • 136 FiscalYear • 136 FittedHist • 168 FixInFutureSw • 231 Force • 78 ForecastRecordImport • 171 FromCurrency • 47, 48 FromDFULoc • 120 FromDiscD ate • 113 FromDmdGroup • 113, 120, 125 FromDmdUnit • 113, 120, 125 FromLCStartDate • 114 FromLifeCycle • 114 FromLoc • 114, 125 FromModel • 114, 120, 125

FromSeasonProfile • 114 FrzStart • 223 FtoEnter • 210 FtoLeave • 211 FunctionName • 108 FunctionNum • 108

G Get additional help from JDA • 2

H Help information • 1 Hist • 173 HistDependency • 195 HistFcst • 175 HistFcstEvents • 178 HistStart • 65 HistStream • 83, 84, 114, 174, 180, 233 HistType • 120, 139 HoldOutPeriod • 182 HoltWintersParam • 181 HoltWintersStats • 184 HwModelSw • 65 HybridFactor • 195

I IgnoreEffDiscDateSw • 52 IgnorePricingLvlSw • 150 Image • 147 Include_In_SLCCurve • 65 Included • 78, 80 InfCarryFwdSw • 258 InfiniteSupplySw • 260 Information about columns • 5 Information about tables • 4 InitE3Error • 65 InitE3ErrorDate • 65 InitialInterval • 40 InitialLevel • 182 InitialLewMeanQty • 200 InitialLinearTrend • 195 InitialMeanValue • 17, 195, 235 InitialQuadTrend • 195 InitialSize • 41 InitialTrend • 182 InitialValSw • 41 InitMeanOverrideSw • 17, 182, 195, 235 InputVal • 14, 256



Installation/administration information • 1 Integer • 7 InternalEvents • 128, 131, 165, 177 InternalEventSw • 154 InternalInfluenceCoef • 268, 272 IntervalSmooth • 41 IntervalSmoothSw • 41 IntNum • 249 InvOptimizerType • 191 Is_Default • 226 Item • 136, 139, 141, 187, 191, 260, 270 ITEM • 134 ItemClass • 191 ItemStoreGrade • 260

J JobID • 128, 131, 165

K KeepReconImpacts • 52

L Lag • 165, 177, 179 LastAWS • 200 LastDeseasonFittedHist • 20 LastExternalInfluenceCoef • 274 LastFittedFcst • 200 LastHist • 200 LastInternalInfluenceCoef • 274 LastLevel • 184 LastMAD • 200 LastMADdivM • 200 LastMarketSize • 274 LastMean • 237 LastMove • 227 LastNormFsctError • 200 LastPeriod • 44 LastRelError • 200 LastRelTrend • 200 LastTMax • 20 LastTrend • 185 LastUpdated • 284 Lat • 223 LaunchEndDate • 72 LaunchStartDate • 72 Legal notice • i LevelID • 75 LevelNum • 120

LevelSmooth • 182 LewandowskiParam • 194 LewandowskiStats • 199 LewFactor • 203, 207 LewFactorCategory • 203, 204, 205 LewFactorLibMap • 205 LewFactorLibrary • 205, 206 LewFactorType • 203, 206 LewFactorValue • 207 LewMeanQty • 157, 160, 169 Libname • 208 LibName • 13, 252, 253 LibraryCategoryMap • 208 LifecycleFactor • 196 LifecycleStartDate • 196 LimitConstant • 272 LinExtFactor • 196 LinFactorImpact • 196 LinFactorOpt • 196 LinRegParam • 209 LinRegStats • 216 LLOverride • 146 LoadID • 52 Loc • 15, 19, 39, 41, 44, 57, 65, 72, 78, 80, 81, 83, 84, 108,

110, 124, 128, 131, 135, 136, 142, 143, 146, 157, 160, 165, 169, 171, 174, 177, 179, 182, 185, 196, 201, 211, 217, 221, 223, 231, 234, 236, 245, 251, 260, 270, 271, 273, 275, 277, 280, 285

Loc_Type • 223 LOC_TYPE • 134 LocDescr • 285 LockDur • 65 LockEnd • 121 LockStart • 121 LocType • 226 LogScale • 146 Lon • 224 LTDGroup • 260

M MADP • 19 Map • 121, 227 MAPE • 165 MapUsed • 65 MarketActivity • 128, 131, 165, 177 MarketMgrVersionID • 157, 160 MarketSize • 268, 272 Mask • 65, 228, 229 MaskData • 229



Master • 21 MasterCal • 147 MasterCalRule • 147 MaxBaseFcstHist • 165 MaxDmd • 20 MaxHist • 66 MaxNonBaseFcstHist • 165 MaxNumTerms • 211 MaxSteps • 211 MaxTotFcstHist • 166 MaxTrend • 201 Mean • 19, 44, 185, 201, 217, 237, 273 MeanAbsDeviation • 169 MeanDmdRate • 44 MeanValueAdj • 230 MeanValueDynamic • 196 MeanValueMax • 196 MinDmd • 20 MinHist • 52 MinModelDur • 53 MinOHCovRule • 260 MinSeasonVal • 16 MinTrend • 201 MLRAutoSvd • 53 MLROutlierRefit • 211 MLRSigAmpSw • 211 Model • 15, 19, 39, 41, 44, 57, 66, 72, 78, 80, 81, 109, 110,

128, 131, 135, 139, 142, 157, 160, 166, 169, 171, 177, 179, 182, 185, 196, 201, 211, 217, 231, 232, 233, 234, 236, 251, 271, 273, 275, 277, 280

ModelDate • 66 ModelLevel • 217 ModelTrend • 217 ModifiedBy • 153 ModifiedDate • 153 ModType • 231 MovingAvgParam • 234 MovingAvgStats • 236 MovingAvgWgt • 235, 239 MovingAvgWgts • 238 MovingEvent • 124, 240, 241 MovingEventData • 241 MPBatchNum • 262 MSE • 19, 44, 185, 201, 236, 274 MSEHistDur • 66 MSESmooth • 41, 182 MSESmoothSw • 41

N NegFcstSw • 66 NegHistSw • 41 NetChgSw • 262 NetFcstError • 66 NetFcstMSE • 66 NetFcstMSESmConst • 66 NewDFUSw • 66 NonBaseError • 166 NonBaseFcst • 166, 177 NonBaseHist • 128, 131, 166 NonLinExtFactor • 196 NonLinFactorAmp • 196 NonLinFactResponse • 196 NormalizedFcstErr • 169 NormalizedValue • 207 NormGroup • 74, 75 NormVal • 14, 256 NPIFromDmdPostDate • 66 NPIFromMSE • 67 NPIIndDate • 67, 244 NPIMeanDmdRate • 41 NPIMeanSmooth • 67, 243 NPIScalingFactor • 67, 243 NPISequence • 242 NPISequenceDetail • 243 NPISw • 67 NPITMax • 16 NPITransDur • 263 NPITrendSmooth • 67, 243 NPIValidDFU • 245 NumEvent • 218 NumFcstPer • 22 NumHistObserv • 201, 218 NumHistPerUsed • 218 NumInt • 248 NumModelTerm • 218 NumOptSteps • 197 NumOutlier • 218 NumPerForAvg • 234 NumPerForInitialVal • 41 NumPeriods • 11, 240 NumPerMask • 218 NumPerSmooth • 218 NumSysAdjOutlier • 19, 218 NumYears • 67



O ObsoleteFlag • 67 OH • 263 OHPost • 224, 263 OnOrderQty • 150 Opt • 30 OptimizedValue • 275 OptimPct1 • 82 OptimPct2 • 82 OptimPct3 • 82 OptimPct4 • 82 OptimPct5 • 82 OptimPct6 • 82 Option_Number and Option_Text • 7 OutlierFactor • 16, 182, 212, 235 OutlierOpt • 53, 67 OutlierSw • 170 OverlapFactor • 124

P PackSize • 150 ParamOptimizSW • 182 ParamOverrideSW • 244 Parent/Child tables and columns (foreign keys) • 5 Paths between tables • 9 PatternSw • 22 PctError • 268 PeggingSw • 265 PER1FCST - PER52FCST • 134 Period • 14, 207, 239, 256, 275 PeriodEnd • 284 Periodicity • 253 PerishableSw • 191 PerNum • 251 PerWgt • 31 PickBestDate • 67 PickBestSw • 68, 177 PlanLevel • 192, 265 POSQty • 270 PostalCode • 224 Predefined pages • 4 PriceLink • 150 PriceProfile • 246 PriceProfileName • 147, 246, 247 PriceProfileVal • 247 PriItemPriority • 192 Primary key columns • 5 Primary key columns in the table • 4

PrimaryAttribSW • 76 PrimaryDFUSw • 147 Priority • 76, 192 ProcErr • 114 Processes part 1

input and output tables • 366 Processes part 2

input and output tables • 371 Profile • 248, 249, 278 ProfileData • 249 ProfileName • 11, 14, 72, 253, 256 Provide feedback on this document • i Publish_ZeroForecast • 53 PublishDate • 68 Published • 177 PublishSSSw • 53 PValue • 78, 80

Q Qty • 83, 84, 110, 135, 136, 143, 157, 160, 170, 171, 174,

179, 278, 280 QtyUOM • 265

R Recon_CircMapCheck • 54 Recon_SkipRelevel • 54 ReconAllowNetNegative • 53 ReconciledFcst • 166, 177 ReconFcstSigAdj • 53 ReconNullValues • 54 ReconUseNegQtySw • 54 RefitDate • 68 RegressionMethod • 212 Relation • 75, 83, 84 RelativeLen • 249 Release Notes • 1 Repeat • 32 ReplenMethod • 265 ReplenType • 265 RequestID • 114 RestrictPlanMode • 192 RollingSw • 22 RPBatchNum • 266 RSquare • 218 RunCalcModelSw • 68

S ScalingFactor • 272



SE • 19, 218, 237, 274 Search • 243 SearchPriority • 244 SearchScope • 244 SeasonalityImpact • 197 SeasonalityOpt • 183 SeasonalityProfileSw • 183 SeasonalitySw • 197 SeasonalitySW • 16, 234, 271 SeasonalSmooth • 183 SeasonError • 250 SeasonErrorLag • 69 SeasonLib • 252 SeasonProfile • 69, 253 SeasonProfileValues • 255 SeasonType • 253 SEOutlierFactor • 69 SEOutlierOpt • 69 SeqIntEnableSw • 266 SeqIntExportDur • 224 SeqIntImportDur • 224 SeqIntLastExportedToSeq • 225 SeqIntLastImportedFromSeq • 225 Sequence • 8 SequenceName • 242, 243 SigAmp • 212 SignedError • 19 SizeSmooth • 41 SKU • 257 SKUFactsData • 270 SKUGroup • 266 SKULoc • 139, 141 SKULOC • 134 SLCCurve • 268 SLCCurveAttrib • 269 SLCParam • 271 SLCStats • 273 SMAPE • 274 SmoothConstant • 15, 213, 272 SmoothDmdSize • 19 SmoothedMAD • 197 SmoothErrorTracking • 185 SmoothMSE • 45, 185 SmoothProfileSw • 183, 197 SmoothSeason • 275 SmoothSw • 213 SourceCal • 225 SourceDmdUnit • 75

SourcingGroup • 266 SPI_Periodicity • 54 StabilityRateNF • 197 StartDate • 34, 38, 49, 57, 83, 84, 110, 128, 131, 135, 136,

141, 143, 153, 157, 160, 166, 170, 172, 174, 177, 179, 203, 229, 231, 241, 247, 251, 278, 279

STARTDATE • 134 StartPct • 57 StartPct2 • 57 StartPct3 • 57 StartPct4 • 57 StartPct5 • 57 StartPct6 • 57 StaticCFDescr • 69 StaticCFValue • 69 StaticRelationVal • 75 StatMSE • 69, 218 StdDevDemand • 45 StdDevInterval • 45 StepSize • 272 StorableSw • 266 StorageGroup • 192 StoreFittedHistOpt • 69 STRAT_USE_SCPO_PRODRATE • 54 SubEvent • 277 SubSelectionMethod • 213 SummaryDmdGroup • 54 SummaryModel • 55 SupersedeSw • 139, 141 SupsnGroupNum • 193 SymmetricMAPE • 20, 45, 70, 186, 201, 219, 237 SysAdjOutlierSw • 170

T Table description • 11, 12, 13, 14, 15, 18, 21, 26, 34, 35, 36,

37, 39, 40, 43, 46, 47, 48, 51, 56, 62, 72, 74, 75, 76, 77, 79, 81, 83, 84, 85, 110, 113, 117, 122, 124, 125, 127, 130, 133, 135, 136, 137, 140, 142, 143, 145, 148, 149, 152, 154, 156, 159, 163, 168, 171, 173,ꁌ176, 178, 180, 181, 184, 188, 195, 199, 203, 204, 205, 206, 207, 208, 210, 217, 222, 226, 227, 228, 229, 230, 232, 234, 236, 238, 240, 241, 242, 243, 245, 246, 247, 248, 249, 250, 252, 253, 255, 258, 268, 269, 270, 271, 273, 275, 277, 279, 280, 281, 282, 283, 284, 285

Table Relationships • 286 TableName • 76 Tables in the database (technical documentation) • 10 Target • 279, 280 TargetDFUMap • 280 TargetDmdUnit • 75 TargetImpact • 166, 177



TargetOHCovRule • 266 Text and Upper_Text • 6 The SCPO database (technical documentation) • 4 TimeUOM • 267 TimeWgt • 214 ToCurrency • 47, 49 ToDFULoc • 121 ToDiscDate • 114 ToDmdGroup • 114, 121, 125 ToDmdUnit • 114, 121, 125 ToEffDate • 114 ToLCStartDate • 115 ToleranceFactor • 214 ToLifeCycle • 115 ToLoc • 115, 126 ToModel • 115, 121, 126 ToNPIIndDate • 115 ToNPIMeanSmooth • 115 ToNPIScalingFactor • 115 ToNPITrendSmooth • 115 ToSeasonProfile • 115 TotalSalesQty • 72 TotalVol • 142 TotError • 166 TotFcst • 128, 132, 141, 166, 179 TotFcstLock • 71 TotFcstLockAdj • 166, 177 TotHist • 128, 132, 167 TotHistFcst • 128, 132 TrackingSignal • 19, 170 TrackingSignalAWS • 197 Trend • 19, 170 TrendBrkSw • 170 TrendCombination • 197 TrendDamp • 183 TrendFactor • 215 TrendMethod • 16, 183, 197 TrendSmooth • 183 TStatistic • 78, 80 Type • 22, 35, 36, 134, 141, 157, 160, 172, 174, 179, 226 Type1SW • 122 Type2SW • 122 Type3 • 225 Type3SW • 122 Type4SW • 122 Type5SW • 122 Type6SW • 123 Type7SW • 123

Type8SW • 123 Type9SW • 123

U ULOverride • 147 UnitSize • 150 UnitsPerAltShip • 193 UnitsPerPallet • 193 UOM • 150, 193 UpdateFreqFactor • 16 URL • 8 UseLeadingBlanks • 55 UserID • 109, 128, 132, 167

V Valid values • 8 Value • 74, 239, 247, 269 VendID • 225 Vol • 193

W WDDArea • 225, 281, 283, 284 WDDCategory • 282, 283, 284 WDDCategoryAreaMap • 283 WDDData • 284 WDDGraphURL • 283 WDDImpact • 284 WDDSw • 55 WFMFcstStruct • 285 Wgt • 193 When • 109 WMAPE • 167 WorkingCal • 225

Y Year • 241, 254, 276


Documents

dmf_ref_guide.pdf