ddr_ref_guide.pdf

Reference Guide JDA® Dynamic Demand Response Release 8.1.0.0

JDA Software Group, Inc.

Legal notice Rights to the content of this document

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

Printed in the United States of America.

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

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

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

Modifications to the contents of this document

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

Rights to the functionality of this document

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

Technical documentation

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

Patents

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

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

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

http://jda.com/JDAPatents


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


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

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

mailto:[email protected]


Table of Contents Chapter 1. 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 AllocCalProfile................................................................................................... 11 AllocCalProfileData ............................................................................................ 12 Cal .................................................................................................................. 13 CalData ........................................................................................................... 18 CustOrder ........................................................................................................ 26 CustOrderHist ................................................................................................... 35 CustOrderStat .................................................................................................. 37 CustOrderStatHist ............................................................................................. 40 DDRParamProfile .............................................................................................. 43 DFU ................................................................................................................ 48 DFUException ................................................................................................... 62 DFUToSKU ....................................................................................................... 87 DFUToSKUFcst.................................................................................................. 90 DFUView .......................................................................................................... 92 DmdGroup ....................................................................................................... 96 DmdUnit .......................................................................................................... 97 Fcst ............................................................................................................... 100 Hist ............................................................................................................... 104 HistStream ..................................................................................................... 106 Item.............................................................................................................. 107 Loc ............................................................................................................... 114 Model ............................................................................................................ 119 SKU .............................................................................................................. 121 SKUDemandParam .......................................................................................... 132 SKUException ................................................................................................. 148 Table Relationships ......................................................................................... 180

Index ........................................................................................................................... 260

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 Dynamic Demand Response 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 each table.

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

• Paths between tables (on page 9) explains the paths from each table to other tables. When the system allows you to use data from multiple tables, or to navigate between two tables, there is said 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 180).

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 13) 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.


AllocCalProfile

AllocCalProfile Table included with: Dynamic Demand Response

Column name PK Included with Datatype Valid values

Default value

AllocCalProfileName 1 DDR TEXT ‘ ‘

Descr DDR TEXT

Table Description AllocCalProfile is used to create a time-phased allocation calendar. The system uses AllocCalProfile data to generate a time-phased calendar for the defined AllocCalProfile. While generating the time-phased calendar, the system considers CalStartDate, ObsStartDate and ObsEndDate which are specified in the AlloCalProfileData table. AllocCalProfileData uses the AllocCalProfile table to generate the allocation calendar.

Column descriptions AllocCalProfileName The name of the allocation calendar profile, associated with this DFU.

Descr An optional description of this Allocation Calendar Profile.


AllocCalProfileData

AllocCalProfileData Table included with: Dynamic Demand Response


Default value

AllocCalProfileName 1 DDR TEXT

CalStartDate DDR DATE 1 ObsStartDate 2 DDR DATE 1 ObsEndDate DDR DATE UseMultipleYearsHistSw

DDR INTEGER 1

Table description The AllocCal generation process loads all the Customer Order history records as specified in the process page and divides it into observation periods as per the AllocCalProfileData.

Column descriptions AllocCalProfileName The name associated with allocation calendar profile, defined in the AllocCalProfile table.

CalStartDate This date defines the beginning of the calendar period. The process generates allocation weights for the defined set of observation periods.

ObsStartDate This date defines the beginning of the observation period. The process takes customer orders (CustOrderHist) within the observation period for calculating period weights.

ObsEndDate The date defines the end of the observation period. The process takes the customer orders (CustOrderHist) up to the observation end date.

UseMultipleYearsHistSw Switch that determines whether to use history of multiple years. When you select a profile as a UseMultipleYearsHistSw (that will set it to 1), the profile considers multiple years history which is set between ObsStartDate and ObsEndDate.

Valid values for UseMultipleYearsHistSw are:

• 0 - Do not use MultipleYearsHist

• 1 - Uses MultipleYearsHist


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


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 22) is 7, the identifier of a calendar whose Cal:Type is the same as this calendar's

• If CalData:Opt (on page 22) 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 22).

If you specify a value for AltCal, CalData:Opt (on page 22) 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 22) 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 22) 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 22)) 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 22). 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 Dynamic Demand Response Reference Guide 22 © 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 22).

• 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 22)). 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.


CustOrder

CustOrder Table included with: Dynamic Demand Response, Fulfillment, Master Planning, Supply, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


Default value

ArrivLeadTime Flowcasting DURATION 0 ArrivTransMode Flowcasting UPPER_TEXT ' ' ArrivTransZone Flowcasting UPPER_TEXT ' ' CalcPriority MP, ESP (Deep

Tree) DECIMAL 0

Cost Supp DECIMAL 0 Cust MP, Supp, IPO, ESP

(Deep Tree) TEXT ' '

DFULoc DDR TEXT DmdGroup DDR TEXT DmdUnit DDR TEXT FcstSw FF, MP, IPO, DDR,

Flowcasting, ESP (Deep Tree)

BOOLEAN 0

FcstType FF, DDR, Flowcasting

OPTION_NUMBER

0,1,2,3,4,5, 6,7,8,9

1

FirmSw Supp BOOLEAN 0 HeaderExtRef MP, Supp, IPO, ESP

(Deep Tree) TEXT ' '

Item 1 FF, MP, Supp, IPO, DDR, Flowcasting, ESP

TEXT

LifecycleStatus Not used in this release

OPTION_NUMBER

1,2,3,4,5 1

LineItemExtRef MP, Supp, ESP (Deep Tree)

TEXT ' '

Loc 2 FF, MP, Supp, IPO, DDR, Flowcasting, ESP

TEXT

Margin MP, Supp, ESP (Deep Tree)

DECIMAL -1

MaxEarlyDur MP, IPO, ESP (MAP and Deep Tree)

DURATION 0

MaxLateDur MP, IPO, ESP DURATION 0 MinShelfLifeDur ESP DURATION 0

OrderID 3 FF, MP, Supp, IPO, DDR, Flowcasting, ESP

TEXT

OrderLineItem FF, Flowcasting DECIMAL 0


CustOrder


Default value

OrderSeqNum FF, MP, Supp, Flowcasting, ESP

SEQUENCE 0

OrderType Supp OPTION_NUMBER

105,110,115,120,125,130,135,140,145,-103,-105,-110,-115,-120,-125,-130,-135,-140,-150

-115

OverrideFcstTypeSw

DDR OPTION_NUMBER

0,1 1

Priority FF, MP, Flowcasting, ESP (Deep Tree)

INTEGER 0

PrioritySeqNum MP, ESP (Deep Tree)

INTEGER 0

Project Supp TEXT ' ' PromisedDate Flowcasting DATETIME 01/01/1970

PromisedQty Flowcasting DECIMAL 0 Qty FF, MP, Supp, IPO,

DDR, Flowcasting, ESP

DECIMAL 0

Reservation FF, Flowcasting BOOLEAN 0 ResExp FF, Flowcasting DATETIME 01/01/1970

Revenue MP, Supp, ESP (Deep Tree)

DECIMAL -1

ShipCompleteSw Not used in this release

BOOLEAN 0

ShipDate 4 FF, MP, Supp, IPO, DDR, Flowcasting, ESP

DATETIME

ShipSw FF, Flowcasting BOOLEAN 0 Status FF, DDR,

Flowcasting, ESP OPTION_NUMBER

1,2,3 1

SubstLevel Supp INTEGER 0 SubstOperator Supp OPTION_NU

MBER 0,1,2,3,4,5,6

0

SupersedeSw FF, MP, Flowcasting BOOLEAN 0 TargetEarlyDur ESP (LPOPT) DURATION UnitPrice Supp, ESP (LPOPT) DECIMAL 0 WorkScope Supp TEXT ' '

Table description Each row in this table defines one line item in an order from a customer. JDA Dynamic Demand Response Reference Guide 27 © 1997 - 2014 JDA Software Group, Inc.- Confidential

CustOrder

IPO IPO users only need to populate this table if they intent to model customer orders for the replenishment plan cost model.

Supply The CustOrder table contains all customer orders representing independent demand that are imported from the host ERP system. Most JDA Supply applications like the Calculate Supply Plan and the Fetch Resource Optimization Inputs (Fetch) processes use the CustOrder table as an input table.

Column descriptions CalcPriority The sequence number generated for a customer order if you choose to run the Calculate Sigmoid Priority process. CalcPriority indicates the importance of this customer order line in relation to other customer order lines. A value of 0 is most important and higher values are less important.

Valid values for Calculated Priority are 0 to 100.

Cost This is the cost of satisfying this customer order, as calculated by the MIP algorithm.

Cust Unique identifier of this customer. The value in this column must match the value in the CustOrderHeader:Cust column and the Cust:Cust column.

Supply Unique identifier of this customer. (CustOrderHeader:Cust = CustOrder:Cust and CustOrderHeader:ExtRef=CustOrder:LineItemExtRef)

DFULoc The location associated with this DFU.

DmdGroup The demand group associated with this DFU.

DmdUnit The demand unit associated with this DFU.

FcstSw Switch that determines whether the order was part of the forecast for the SKU. This determines how the order affects demand.

Valid values for Forecasted Switch are No and Yes.

• Yes: Part of forecasted demand

This order is considered part of the forecast.

Fulfillment The forecast adjustment logic in the Calculate Plan process uses this order if CustOrder:ShipDate is earlier than or equal to the end of the Customer Order Duration (SKUDemandParam:CustOrderDur).

If ShipDate is earlier than or equal to SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank) and CustOrder:Status (on page 33) is 1, this is a backorder—included in SKU statistic Backorders. The system considers backorders to fall within the Customer Order Duration for the purposes of forecast adjustment, but demand is placed on the ShipDate.

Master Planning, IPO, ESP (Deep Tree)


CustOrder

If this order is within the customer order duration (that is, if CustOrder:ShipDate (on page 33) is earlier than or equal to SKUDemandParam:CustOrderDur), the forecast adjustment logic in the Generate Forecast Orders process uses this order.

If the order is outside the customer order duration, the forecast consumption logic uses this order to consume the forecast.

• No: Not part of forecasted demand

This order is not considered part of the forecast. The forecast adjustment logic and forecast consumption logic do not use it. This order is included in SKUProj:TotDmd in the time period within which its CustOrder:ShipDate (on page 33) falls. The system considers backorders to fall in the time period that includes SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank).

IPO Note: IPO does not store SKUProj data.

FcstType Determines the adjustment and consumption of customer orders based on the selected forecast type. Valid values are 0-9. The valid values for the customer order to be consumed by a specific FcstType are:

• 0: None

• 1: Base

• 2: Aggregate Market Activity

• 3: Total Forecast Lock

• 4: Reconcile

• 5: Auto

• 6: Override

• 7: MktActivity

• 8: Data Driven

• 9: TargetImpact

For example, you can specify a "Base" customer order to adjust or consume only a "Base" forecast by selecting CustOrder:FcstType = 1.

Note: If you do not specify the forecast type for a forecasted customer order, it will be adjusted and consumed by the Type 1 forecast type (Base type).

For more information on types of forecasts, see DFUToSKUFcst:Type.

FirmSw Indicates if an order is firm or not.

HeaderExtRef Identifier of the customer order with which this order line is associated. The value in this column must match the value in the CustOrderHeader:ExtRef column.

Item The item associated with this line item. Must be a valid item in the Item table.

LineItemExtRef If this customer order line was imported from an external (non-JDA) system, you may use this column in Master Planning for the line item identifier provided by the external system. If you specify a value for LineItemExtRef, it should be unique for each line item within the same customer order.

If you do not specify a value for LineItemExtRef, Master Planning sets it to the value in OrderLineItem.


CustOrder

Supply imports the customer order line information into this column.

Loc The location associated with this line item. Must be a valid location in the Loc table.

Margin The profit expected from this customer order line item.

If Master Planning process properties have a high relative weight for Margin (on the Priority Weights tab), Master Planning will favor orders with larger unit margin values over those with smaller unit margins when determining which demand to meet next.

If the value in this column is greater than or equal to 0, Master Planning uses it as the margin value. Otherwise, it calculates the margin as:

CustOrder:Revenue (on page 33) – (CustOrder:Qty (on page 32) × SKUSupplyParam:StdCost)

The unit margin is calculated as:

MaxEarlyDur The number of earlier time buckets that the algorithm can use when it searches for supply to satisfy the customer order. This value limits how early the customer will accept this order line. If this value is greater than 0, the Master Planning algorithm will not try to find supply that will result in meeting the order line earlier than:

CustOrder:ShipDate (on page 33) – CustOrder:MaxEarlyDur (on page 30)

If this value is blank, the Master Planning algorithm uses the maximum early duration specified for the entire customer order in CustOrderHeader:MaxEarlyDur.

If the CustOrderHeader:MaxEarlyDur is also 0, the algorithm uses the value specified in the Duration field on the Calculate Master Plan process page. When you run the Master Planning algorithm, you can override the CustOrder:MaxEarlyDur (on page 30) and the CustOrderHeader:MaxEarlyDur values for the current algorithm run. To do that, on the Calculate Master Plan process page, check the Meet Early Durations > Customer Order Override check box and specify a value in the Duration field.

Note: This option does not guarantee that the demand will not be met earlier than the MaxEarlyDur. MaxEarlyDur works in conjunction with other options.

IPO IPO uses this column in its time-phased replenishment plan cost model in the same way as Master Planning, as described above.

MaxLateDur The limit on how late the customer will accept this order line. If this value is greater than 0, the Master Planning algorithm will not try to find supply that will result in meeting the order line later than:

CustOrder:ShipDate (on page 33) + CustOrder:MaxLateDur (on page 30)

If CustOrder:MaxLateDur (on page 30) is 0, the algorithm uses the maximum late duration specified for the entire customer order in CustOrderHeader:MaxLateDur.

If the CustOrderHeader:MaxLateDur is also 0, the algorithm uses the value specified in the Duration field on the Calculate Master Plan process page. When you run the Master Planning algorithm, you can override the CustOrder:MaxLateDur (on page 30) and the CustOrderHeader:MaxLateDur values for the current algorithm run. To do that, on the Calculate Master Plan process page, check the Meet Late Durations > Customer Order Override check box and specify a value in the Duration field.


CustOrder

IPO IPO uses this column in its time-phased replenishment plan cost model in the same way as Master Planning, as described above.

ESP Limit on how late a customer can accept this demand order.

If this value is greater than zero, the ESP solvers do not try to find supply to meet the demand order later than CustOrder:ShipDate (on page 33) + CustOrder:MaxLateDur

If this value is zero, the ESP solvers use the maximum lateness tolerance specified for the entire customer order in CustOrderHeader:MaxLateDur. If the CustOrderHeader:MaxLateDur is also zero, the ESP solvers use the value specified in the Duration field in the Generate Master Plan process page.

When the ESP solvers generate a plan, to override the CustOrder:MaxLateDur (on page 30) and CustOrderHeader:MaxLateDur values, in the Generate Master Plan process page, select the Meet Late Durations > Customer Order Override check box and specify a value in the Duration field.

MinShelfLifeDur The remaining shelf life that an item must have in order to be accepted by customers.

OrderID Unique identifier of the line item defined in this row.

OrderLineItem Unique identifier of this order line item.

To have the system generate a unique value for this order line item, specify a value of 0. Otherwise, specify a unique value for this column.

OrderSeqNum The demand order identifier used to map output records to input order information.

OrderType This column contains a numeric type representing the demand order type. This is an information only field and holds a default value of -115.

OverrideFcstTypeSw The value in this column specifies whether or not to update the FcstType (flag) for a particular CustOrder.

Priority This value indicates the importance of this customer order line in relation to all other customer order lines. The Master Planning process and Calculate Recommended Shipments logic within the Calculate Plan process each use this priority when determining which demand to satisfy first.

Valid values for Priority are 0 or greater.

A value of 1 is most important and larger values are less important. A value of 0 means that no priority has been set.

Master Planning, ESP (Deep Tree) Master Planning process uses the priority for the whole order (CustOrderHeader:Priority).

You can set customer order priorities in several places, which Master Planning checks in the following sequence:

• CustOrder:Priority (on page 31) (priority of a specific customer order line)

• CustOrderHeader:Priority (priority of all the customer order lines in one customer order)


CustOrder

• Cust:Priority (priority of all the customer order lines for one customer)

• SKUDemandParam:CustOrderPriority (priority of all customer order lines for one SKU)

Fulfillment This value indicates the importance of this customer order in relation to all demands that share the same AllocStrat:Priority. The value of CustOrder:Priority is compared to the value of AllocStrat:SubPriority to determine the relative priority of a customer order versus a non-order demand type that shares the same Priority value. A value of 0 means that this customer order is to be treated as a non-priority demand.

Note: This column is only respected in Fulfillment Deployment when SKUDeploymentParam:SecRSAllocRule = 2

PrioritySeqNum The sequence number generated for a customer order if you choose to run the Calculate Rules Based Priority process.

Project JDA Supply uses this column to read the project code that is used by the matched sets logic in the Resource Optimization process. When the Matched Project Sets option is selected, Resource Optimization checks for independent demands that have been assigned the same project ID as the supply kept aside for those specific demands. Resource Optimization will use only those supplies that match. If matches are not found, then Resource Optimization uses supplies from the open stock.

Qty The number of units of the SKU specified by this order.

Fulfillment If you are using the Build Transportation Loads feature, quantity should be defined in terms of the Unit of Measure specified for this item in the Item table.

Reservation Reservation indicates whether this customer order is a reservation customer order—a future customer order that has not yet been fully processed but for which existing stock is reserved immediately.

Unlike regular customer orders, which are processed and then imported into the CustOrder table, reservation customer orders are brought into the CustOrder table on a real-time basis. This makes them immediately available to the Available to Promise SKU projection calculation (see SKUProjStatic:ATP for a description) or the Plan Analysis ATP column where, like regular customer orders, they are subtracted from available stock. Because there is no delay between the time when the customer order is placed with the order-taker and the time when it is actually reflected in the ATP calculation, the next order-taker can review the ATP without worrying that the quantity includes stock that has already been committed to another customer.

Reservation customer orders have an expiration date associated with them (see CustOrder:ResExp (on page 33), below).

Consider the following example:

A customer calls a supplier and wants to place an order for a particular item.

After checking the SKU projection ATP column to be sure that there is enough stock to cover the order quantity, the order-taker places a reservation order for the number of units the customer has requested.

The reservation order is immediately added to the CustOrder table. The order ID (CustOrder:OrderID (on page 31)) and expiration date (CustOrder:ResExp (on page 33)) are added at the same time.


CustOrder

When the next order-taker views the SKU projection ATP column, the change in the ATP based on the quantity of the reservation customer order is reflected.

Note: The SKUProjStatic table requires the Store SKU Projections process to be run to recalculate values.

ResExp The date/time that the reservation customer order expires. Unexpired customer orders are treated as regular customer orders—that is, they are subtracted from available supply in the Available to Promise (SKU projection ATP) calculation.

The system does not automatically remove expired reservation customer orders from the database; you will need to do this manually.

The system does not include reservation customer orders with an expiration date prior to SKU:OHPost when it calculates ATP values.

Revenue The selling price associated with this order line item.

Valid values for Revenue are –1, 0 or greater.

If the Demand Unit Revenue Weight field on the Calculate Sigmoid Priority process page has a high relative weight for Revenue, Master Planning will favor orders with larger unit revenue values over those with smaller unit revenues when determining which demand to meet next.

If the value in this column is greater than or equal to 0, Master Planning uses it as the revenue value. Otherwise, it calculates the revenue as:

CustOrder:Qty (on page 32) × (SKUDemandParam:IndDmdUnitCost + SKUDemandParam:IndDmdUnitMargin)

The unit revenue is calculated as:

ShipDate The date and time when this line item must be shipped in order to meet the date needed by the customer. Valid values are date/time and cannot be blank.

ShipSw This column is not used in the current release.

Status Option that indicates whether the Quantity of this order is still included in the current values for SKU:OH at the source. Status is also used in determining whether the quantity is used in the forecast adjustment process and whether it is a backorder.

• 1: Part of On Hand, Not Shipped

This order has not been shipped; the quantity is still included in SKU:OH for the source.

The quantity is used in the forecast adjustment process if CustOrder:FcstSw (on page 28) is Yes and if CustOrder:ShipDate (on page 33) is greater than SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank).

If ShipDate is on or before OHPost, the system will use the order quantity in forecast adjustment logic. That quantity is included in SKU statistic Backorders. Backorders will be included in SKU projection TotDmd in the time period that includes SKU:OHPost (or Loc:OHPost).

• 2: Part of On Hand, Shipped


CustOrder

The quantity is still included in SKU:OH, but the order has been shipped. The system will calculate SKU projection ProjOH as SKU:OH minus the order quantity.

The quantity is used in the forecast adjustment process if CustOrder:FcstSw (on page 28) is Yes and if CustOrder:ShipDate (on page 33) is greater than SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank).

If ShipDate is on or before OHPost, the system will use the order quantity in forecast adjustment logic. Those order quantities are included in SKU statistic Backorders. Backorders will be included in SKU projection TotDmd in the time period that includes SKU:OHPost (or Loc:OHPost).

• 3: Not Part of On Hand, Shipped

The quantity is not used in the Forecast Adjustment process.

SubstLevel This column contains the substitution level used by JDA Supply’s Perform Resource Optimization process to select rules. Substitution levels and operators are used to sequence the processing of substitution rules as defined in the SubstRule table. For example, if substitution level and operator are specified as < 3, only rules with a level < 3 are considered. Use the Level option on the Perform Resource Optimization process page to set a global level and operator to restrict rules within a process execution.

Regardless of what levels are being considered, levels with lower numbers are processed before levels with higher numbers. Levels are also stored in the SubstLevel table, where each level can be given a descriptive name.

Note: The level you specify in this column overrides the level that you select in the Perform Resource Optimization process.

SubstOperator This column contains the substitution operator used by JDA Supply’s Perform Resource Optimization process to select rules. Substitution levels and operators are used to sequence the processing of substitution rules as defined in the SubstRule table. For example, if substitution level and operator are specified as < 3, only rules with a level < 3 are considered. Use the Level option on the Perform Resource Optimization process page to set a global level and operator to restrict rules within a process execution.

Note: The operator you specify in this column overrides the operator that you select in the Perform Resource Optimization process.

SupersedeSw Switch that indicates which customer orders can be categorized as demand that can be superseded and, if product transition relationships exist, can be filled with supply of alternate items.

• Y: Can be superseded

• N: Cannot be superseded

TargetEarlyDur Specifies the duration that helps to reduce delay in meeting a customer order on the customer requested delivery date.

UnitPrice This column indicates the unit price of an item.

WorkScope The number that distinctly selects a production method while executing the Generate Finite Resource Plan process during resource loading of Planned Supply Orders.


CustOrderHist

CustOrderHist Table included with: Dynamic Demand Response

Column name PK Included with Datatype Valid values Default value

DmdGroup DDR TEXT

DFULoc DDR TEXT

DmdUnit DDR TEXT

FcstType DDR OPTION_NUMBER

0-9 0

FcstSW DDR OPTION_NUMBER

0,1 0

Item 1 DDR TEXT

Loc 2 DDR TEXT OrderID 3 DDR TEXT OverrideFcstTypeSw

DDR OPTION_NUMBER

0,1 1

Qty DDR DECIMAL

ShipDate 4 DDR DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

Table Description Each row in this table defines the customer orders received for a SKU or DFU. The Generate Allocation Calendar for SKUs and Generate Allocation Calendar for DFUs process uses these parameters to generate allocation calendars for SKUs and DFUs respectively.

DmdGroup The demand group associated with the DFU. This must be a valid DmdGroup in the DFUView table.

DFULoc The demand location associated with the DFU. This must be a valid Loc in the DFUView table.

DmdUnit The demand unit associated with the DFU. This must be a valid DmdUnit in the DFUView table.

Fcst Type Identifies the forecast type (Base or Non-base) for a particular CustOrder. If the OverrideFcstType switch is set to 1 for a CustOrder, the value in this column is updated to Non-Base (Promotional) forecast. Valid values are 0-9, where 0 and 1 are considered Base Forecast and 2-9 are considered as Non-Base Forecast.

FcstSw Switch that determines whether the order was part of the forecast for the SKU. This determines how the order affects demand.


CustOrderHist

Valid values for Forecasted Switch are No and Yes.

• Yes: Part of forecasted demand

This order is considered part of the forecast.

Fulfillment The forecast adjustment logic in the Calculate Plan process uses this order if CustOrder:ShipDate is earlier than or equal to the end of the Customer Order Duration (SKUDemandParam:CustOrderDur).

If ShipDate is earlier than or equal to SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank) and CustOrder:Status (on page 33) is 1, this is a backorder—included in SKU statistic Backorders. The system considers backorders to fall within the Customer Order Duration for the purposes of forecast adjustment, but demand is placed on the ShipDate.

Master Planning and IPO If this order is within the customer order duration (that is, if CustOrder:ShipDate (on page 33) is earlier than or equal to SKUDemandParam:CustOrderDur), the forecast adjustment logic in the Generate Forecast Orders process uses this order.

If the order is outside the customer order duration, the forecast consumption logic uses this order to consume the forecast.

• No: Not part of forecasted demand

This order is not considered part of the forecast. The forecast adjustment logic and forecast consumption logic do not use it. This order is included in SKUProj:TotDmd in the time period within which its CustOrder:ShipDate (on page 33) falls. The system considers backorders to fall in the time period that includes SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank).

IPO Note: IPO does not store SKUProj data.

Item The name of the item for which you are defining the customer order. This must be a valid Item in the Item table.

Loc The location associated with the SKU. This must be a valid location in the Location table.

OrderID The unique identifer of the customer order.

OverrideFcstTypeSw The value in this column specifies whether or not to update the FcstType (Base or Non-Base) for a particular CustOrder.

Qty The quantity associated with the customer order.

ShipDate The date and time when this line item was shipped in order to meet the need date of the customer.


CustOrderStat

CustOrderStat Table included with: Dynamic Demand Response

Column Name PK Included with

Datatype Valid Value

Default Value

AggCal DDR UPPER_TEXT

CalcPartialOrderQty DDR DECIMAL 0 CalcPromoOrderQty DDR DECIMAL 0 DDRGroup DDR TEXT ' ' DmdGroup 2 DDR TEXT DmdUnit 1 DDR TEXT Loc 3 DDR TEXT LogScaleSw DDR INTEGER 1 and

0 0

Max DDR DECIMAL 0 Mean DDR DECIMAL 0 Median DDR DECIMAL 0 Min DDR DECIMAL 0 StartDate DDR DATE TRUNC(

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

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

StdDev DDR DECIMAL 0

TotHistPeriods DDR INTEGER 0 TotPosHistPeriods DDR INTEGER 0

Table description The CustOrderStat table is used to store Customer Order Statistics by DFU. This table is updated when Calculate Dynamic Demand Response process is run with Calculate Statistics option. These statistics are used by the promotion identification algorithm to identify promotional orders.

Note: Every time the statistics are calculated, the existing statistical values are transferred to the CustOrderStatHist table.

Column descriptions AggCal AggCal specifies the aggregation calendar (Demand Calendar) to be used for aggregating the CustOrders History present in the Hist table for calculating the statistics.


CustOrderStat

CalcPartialOrderQty The CalcPartialOrderQty stores the calculated value of the partial order quantity that is used to identify partial shipments. This column is updated when Calculate Dynamic Demand Response process is run with Calculate Statistics option and exclude partial orders option.

CalcPromoOrderQty The CalcPromoOrderQty stores the calculated value of the promotional order quantity that is used to identify promotional orders. This column is updated when Calculate Dynamic Demand Response process is run with Identify Promotional Orders option.

DDRGroup The DDRGroup associated with the DFU. For the DFUs to be in a group, must have common DDRGroup name.

DmdGroup The demand group associated with the DFU.

DmdU nit The demand unit associated with the DFU.

Loc The location associated with the DFU.

LogScaleSw Log Scale specifies whether the statistical calculation was done using log of original values(1) or just original values(0).

Max This column stores the maximum of all aggregated order size quantities within the specified duration.

Mean This column stores the calculated mean of all positive aggregated order sizes. The calculated value may vary depending upon the option specified in DFUView:LogScale. Mean is calculated as below:

where, di > 0

Note: If LogScale is used, mean is calculated as below:

Median This column stores the calculated median of all positive aggregated order size quantities within the specified duration.

Min This column stores the minimum of all positive aggregated order size quantities within the specified duration.

StartDate StartDate is the date from which the history data present in the Hist table is considered for the Calculate Dynamic Demand Response process.


CustOrderStat

StatCalcDate StartCalcDate is the date on which the statistics were calculated.

StdDev This column stores the calculated standard deviation of all positive aggregated order size quantities. The calculated value may vary depending upon the option specified in DFUView:LogScale. Standard Deviation is calculated as below:

Note: If LogScale is used, Standard Deviation is calculated as below:

TotHistPeriods TotHistPeriods stores the total number of buckets within the specified duration.

TotPosHistPer iods TotPosHistPeriods stores the total number of buckets that have positive aggregate order quantities within the specified duration.


CustOrderStatHist

CustOrderStatHist Table included with: Dynamic Demand Response

Column Name PK Included with

Datatype Valid Value

Default Value

AggCal DDR TEXT

CalcPartialOrderQty DDR FLOAT 0 CalcPromoOrderQty DDR FLOAT 0 DDRGroup DDR TEXT ' ' DmdGroup 2 DDR TEXT DmdUnit 1 DDR TEXT Loc 3 DDR TEXT LogScaleSw DDR INTEGER 1 and 0 0 Max DDR FLOAT 0 Mean DDR FLOAT 0 Median DDR FLOAT 0 Min DDR FLOAT 0 StartDate DDR DATE TRUNC(

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

StatCalcDate 4 DDR DATE TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

StdDev DDR FLOAT 0

TotHistPeriods DDR INTEGER 0 TotPosHistPeriods DDR INTEGER 0

Table description The CustOrderStatHist table is used to store history of Customer Order Statistics by DFU. Every time the Calculate Dynamic Demand Response process is run with the option to Calculate Statistics, the existing data in the CustOrderStat table is transferred to the CustOrderStatHist table. Storing historical statistics allows you to further analyze the statistics for seasonal trends and behavior. Statistics stored in this table are mainly identified based on the date (CustOrderStat:StatCalcDate (on page 39)) the statistics were generated.

Column descriptions AggCal AggCal specifies the aggregation calendar (Demand Calendar) to be used for aggregating the CustOrders History present in Hist table for calculating the statistics.

CalcPartialOrderQty


CustOrderStatHist

The CalcPartialOrderQty stores the calculated value of the partial order quantity that is used to identify partial shipments. This column is updated when Calculate Dynamic Demand Response process is run with Calculate Statistics option and exclude partial orders option.

CalcPromoOrderQty The CalcPromoOrderQty stores the calculated value of the promotional order quantity that is used to identify promotional orders. This column is updated when Calculate Dynamic Demand Response process is run with Identify Promotional Orders option.

DDRGroup The DDRGroup associated with the DFU. For the DFUs to be in a group, must have common DDRGroup name.


DmdU nit The demand unit associated with the DFU.

Loc The location associated with the DFU.

LogScaleSw LogScaleSw specifies whether the statistical calculation was done using log of original values(1) or just original values(0).

Max This column stores the maximum of all aggregated order size quantities within the specified duration.

Mean This column stores the calculated mean of all positive aggregated order size quantities. The calculated value may vary depending upon the option specified in DFUView:LogScale. Mean is calculated as below:

where, di > 0

Note: If LogScale is used, mean is calculated as below:

Median This column stores the calculated median of all positive aggregated order size quantities within the specified duration.

Min This column stores the minimum of all positive aggregated order size quantities within the specified duration.

StartDate StartDate is the date from which the history data present in Hist table is considered for the Calculate Dynamic Demand Response process.


CustOrderStatHist

StatCalcDate StartCalcDate is the date on which the statistics were calculated.

StdDev This column stores the calculated standard deviation of all positive aggregated order size quantities. The calculated value may vary depending upon the option specified in DFUView:LogScale. Standard Deviation is calculated as below:

Note: If LogScale is used, Standard Deviation is calculated as below:

TotHistPeriods TotHistPeriods stores the total number of buckets within the specified duration.

TotPosHistPer iods TotPosHistPeriods stores the total number of buckets that have positive aggregate order quantities within the specified duration.


DDRParamProfile

DDRParamProfile Table included with: Dynamic Demand Response.


BaseProrateOpt DDR INTEGER 1 and 2 1

ConsumptionType DDR INTEGER 0,1, and 2 1 ConsumptionRule DDR INTEGER 1,2, and 3 1 DDRParamProfileName

1 DDR TEXT

FcstPeriodRestriction

DDR INTEGER 1,2, and 3 2

IncrConsDur DDR INTEGER 1440 MaxEarlyConsDurBase

DDR INTEGER 10080

MaxEarlyConsDurNonBase

DDR INTEGER 10080

MaxLaterConsDurBase

DDR INTEGER 10080

MaxLaterConsDurNonBase

DDR INTEGER 10080

NonBaseProrateOpt

DDR INTEGER 1 and 2 1

NonBaseProrationPeriod

DDR INTEGER 1

OrderLeadTime DDR INTEGER 0

Table description Each row in this table defines the parameters associated in running the Calculate Dynamic Demand Response (DDR) process. The Calculate DDR process uses these parameters to perform the following logic:

1. Proration logic

2. Consumption logic

3. Adjustment logic

To understand the Calculate Dynamic Demand Response (DDR) process, refer Understanding Calculate Dynamic Demand Response process in the JDA Fulfillment OnLine Expert.

Column descriptions BaseProrateOpt The proration logic of DDR process performs base forecast proration based on the below settings.

You can set the following options for BaseProrateOpt:

• 1: By time

The process allocates all base forecast records in FCST table within the JDA Dynamic Demand Response Reference Guide 43 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DDRParamProfile

proration period and deletes the allocated forecasts prior to the Start Date you set in the DDR process page.

• 2: By demand-to-date

The process first prorates the nonbase forecast. After prorating, if DFUView:DmdToDateNonBase (on page 94) is greater than the total forecast during the proration period, the difference is added to DFUView:DmdToDateBase (on page 94) and then base forecast proration is performed.

For more information on the proration logic, refer Understanding Calculate Dynamic Demand Response process in the OnLine Expert.

ConsumptionType The consumption logic of DDR uses this parameter to determine whether to anchor on the forecasts or forecasted customer orders during forecast consumption.

• 0: None

The forecasted customer orders do not consume the forecast

• 1: Anchor on Forecast

Anchors over the forecast, finding forecasted customer orders to consume the forecasts. While consuming the forecasts, the process looks for earlier or later forecasted customer orders based on the ConsumptionRule (on page 44).

• 2: Anchor on CustOrder

Anchors over the forecasted customer orders, finding forecasts to consume the forecasts. While consuming the forecasts, the process looks for earlier or later forecasts based on the ConsumptionRule (on page 44).

ConsumptionRule The consumption logic of DDR uses consumption rule to determine the direction and the order in which the forecasts are consumed by the forecasted customer orders.

• 1: Consume Earlier Then Later

The consumption logic behavior differs based on the ConsumptionType (on page 44) you select.

• When you set the ConsumptionType (on page 44) to 1, the process anchors over each forecast and first looks for forecasted customer orders on the same date as that of the forecast. The process then looks for earlier forecasted customer order in the increment of IncrConsDur (on page 45) and then later forecasted customer order in the increment of IncrConsDur (on page 45). This iteration continues back and forth to consume the forecast quantity by the forecasted customer orders within the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) to MaxLaterConsDurBase (on page 46)/ MaxLaterConsDurNonBase (on page 46) duration.

• When you set the ConsumptionType (on page 44) to 2, the process anchors over each forecasted customer order and first looks for forecasts on the same date as that of the forecasted customer orders. The process than looks for earlier forecast in the increment of IncrConsDur (on page 45) and then later forecast in the increment of IncrConsDur (on page 45). This iteration continues back and forth to consume the forecast quantity by the forecasted customer orders within the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) to MaxLaterConsDurBase (on page 46)/ MaxLaterConsDurNonBase (on page 46) duration.

• 2: Consume Later Then Earlier



DDRParamProfile

• When you set the ConsumptionType (on page 44) to 1, the process anchors over each forecast and first looks for forecasted customer orders on the same date as that of the forecast. The process then looks for later forecasted customer order in the increment of IncrConsDur (on page 45) and then earlier forecasted customer order in the increment of IncrConsDur (on page 45). This iteration continues back and forth to consume the forecast quantity by the forecasted customer orders within the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) to MaxLaterConsDurBase (on page 46)/ MaxLaterConsDurNonBase (on page 46) duration.

• When you set the ConsumptionType (on page 44) to 2, the process anchors over each forecasted customer order and first looks for forecasts on the same date as that of the forecasted customer orders. The process than looks for later forecasts in the increment of IncrConsDur (on page 45) and then earlier forecasts in the increment of IncrConsDur (on page 45). This iteration continues back and forth to consume the forecast quantity by the forecasted customer orders within the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) to MaxLaterConsDurBase (on page 46)/ MaxLaterConsDurNonBase (on page 46) duration.

• 3: Consume Earliest


• When you set the ConsumptionType (on page 44) to 1, the process anchors over each forecast and looks for the earliest forecasted customer order starting from the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) and moves forward until either the entire forecast is consumed or there are no forecasted customer orders within the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) to MaxLaterConsDurBase (on page 46)/ MaxLaterConsDurNonBase (on page 46).

• When you set the ConsumptionType (on page 44) to 2, the process anchors over each forecasted customer orders and looks for the earliest forecast starting from the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) and moves forward until either the entier forecast is consumed or there are no forecasted customer orders within the MaxEarlyConsDurBase (on page 46)/ MaxEarlyConsDurNonBase (on page 46) to MaxLaterConsDurBase (on page 46)/ MaxLaterConsDurNonBase (on page 46).

DDRParamProfileName The unique profile name associated with the DDR parameters.

FcstPeriodRestriction The consumption logic of Calculate DDR process (ConsumptionType=1 and any ConsumptionRule) uses this parameter to select the CustOrders for consumption based on the below settings:

• 1: Consume across forecast period

When FcstPeriodRestriction is set to 1, forecast is consumed with CustOrders beyond the Current Fcst period.

• 2: Consume first within and then across forecast period

When FcstPeriodRestriction is set to 2, the consumption takes place in a two step process. In the first step, forecast is consumed as per ‘Consume within Fcst Period’ (3). During the second step, the remaining forecast is consumed as per ‘Consume across Fcst Period’ (1).

• 3: Consume within forecast period

When FcstPeriodRestriction is set to 3, forecast is consumed with CustOrders within the current forecast period.

Note: While working with non-base forecast, FcstPeriodRestriction-2 and FcstPeriodRestriction-3 are not applicable.

IncrConsDur


DDRParamProfile

The incremental duration by which the customer orders are consumed by the forecast when ConsumptionRule (on page 44) is set to 1 or 2.

Note: When the consumption logic consumes the forecasts in the backward direction and if IncrConsDur is greater than MaxEarlyConsDurBase/ MaxEarlyConsDurNonBase then IncrConsDur is rounded down to MaxEarlyConsDurBase/ MaxEarlyConsDurNonBase. Similarly, when the consumption logic consumes the forecasts in the forward direction and if IncrConsDur is greater than MaxLaterConsDurBase/ MaxLaterConsDurNonBase then IncrConsDur is rounded down to MaxLaterConsDurBase/ MaxLaterConsDurNonBase.

MaxEarlyConsDurBase The consumption logic of Calculate DDR process uses this duration to determine the maximum early duration from the forecast or customer order until which it can consume the base forecast against the base customer order.

MaxEarlyConsDurNonBase The consumption logic of Calculate DDR process uses this duration to determine the maximum early duration from the forecast or customer order until which it can consume the nonbase forecast against the nonbase customer order.

MaxLaterConsDurBase The consumption logic of Calculate DDR process uses this duration to determine the maximum later duration from the forecast or customer order until which it can consume the base forecast against the base customer order.

MaxLaterConsDurNonBase The consumption logic of Calculate DDR process uses this duration to determine the maximum later duration from the forecast or customer order until which it can consume the nonbase forecast against nonbase customer order.

NonBaseProrateOpt The proration logic of DDR process performs non base forecast proration based on the below settings.

You can set the following options for NonBaseProrateOpt:

• 1: By time

The process allocates all non base forecast records in FCST table within the proration period and deletes the allocated forecasts prior to the Start Date you set in the DDR process page.

• 2: By demand-to-date

The process first prorates the nonbase forecast. After prorating, if DFUView: DmdToDateNonBase (on page 94) is greater than the total forecast during the proration period, the difference is added to DFUView: DmdToDateBase and then base forecast proration is performed.

For more information on the proration logic, See Understanding Calculate Dynamic Demand Response process in the OnLine Expert.

NonBaseProrationPeriod The proration logic of the Calculate DDR process performs proration on the nonbase forecasts from the earliest FCST: StartDate to the duration specified in this column.

OrderLeadTime The adjustment logic of DDR allocates all unconsumed forecasts within the adjustment period (starting from the Start Date (defined in the process page) until the OrderLeadTime) to the subsequent days within the forecast period. The allocation weights for the subsequent days is renormalized before allocation.


DDRParamProfile

For example, if there are two days left in the current forecast period from the Start Date and OrderLeadTime is set to 3 then the forecasts for this two days are not carried to the next forecast period. Thus, the adjustment of forecasts falling within the OrderLeadTime is only within the forecast period.

For information on the adjustment logic of DDR See Understanding Calculate Dynamic Demand Response process in the OnLine Expert.


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

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

CopyDate Dmd, Dmd Decomp, MDO, Flowcasting

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

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

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

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 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 54).

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

Loc The location associated with this DFU.

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 Dynamic Demand Response Reference Guide 55 © 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.

Note: If Symmetric MAPE is zero and DFU:NPISw (on page 57) 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.

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 Dynamic Demand Response Reference Guide 60 © 1997 - 2014 JDA Software Group, Inc.- Confidential

DFU

Month Time History Fitted History

Absolute Error

Average of history and

fitted history

Calculations required for

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).


DFUException

DFUException Table included with: Demand, Flowcasting


Descr Dmd, Flowcasting

TEXT ' '

DmdGroup 2 Dmd, Flowcasting

TEXT

DmdUnit 1 Dmd, Flowcasting

TEXT

Exception 6 Dmd, Flowcasting

INTEGER

FunctionName 5 Dmd, Flowcasting

TEXT ' '

FunctionNum 7 Dmd, Flowcasting

INTEGER

Loc 3 Dmd, Flowcasting

TEXT

Model 4 Dmd, Flowcasting

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 = 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 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 Dynamic Demand Response Reference Guide 85 © 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.


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 88) determine when the mapping is effective. Following is a summary of the results of all possible combinations of values for Disc and Eff.

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


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 88) 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.



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 Dynamic Demand Response Reference Guide 90 © 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.

Dur The interval covered by the forecast defined in this row.

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.



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.


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 (on page 133).

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 (on page 45).

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 102) 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 102) 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.


Loc The location associated with this DFU.

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.


DFUView

LogScale 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

Column name PK Included with

Datatype Valid values Default value

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 98).

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


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 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.


Hist

Hist Table included with: Fulfillment, Demand, Demand Decomposition, Dynamic Demand Response, Markdown Optimization, Promotions Management, Strategic Pricing, Travel Price Optimization, Flowcasting

Column name

PK Included with Datatype Valid values

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 Dynamic Demand Response Reference Guide 104 © 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.


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.


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 Dynamic Demand Response Reference Guide 108 © 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 111) is not an integer; it should be set to the number of significant decimal places in Item:DynDepQty (on page 111).

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 109) 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.


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 Dynamic Demand Response Reference Guide 115 © 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 117).

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 117) 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 117).

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 117) 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.


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.


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 Dynamic Demand Response Reference Guide 124 © 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 Dynamic Demand Response Reference Guide 125 © 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 127)= 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 Dynamic Demand Response Reference Guide 130 © 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 124) for details.

TimeUOM The unit of measure applied to all time values associated with the SKU.


SKUDemandParam

SKUDemandParam Table included with: Dynamic Demand Response, Fulfillment, Master Planning, Supply, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


AllocCal FF, MP, IPO, DDR, Flowcasting, ESP

TEXT ' '

AllocCalGroup DDR TEXT CCPSw MP, Supp, IPO,

ESP (Deep Tree)

BOOLEAN 0

CustOrderDur FF, MP, Supp, IPO, Flowcasting, ESP

DURATION 0

CustOrderPriority MP, Supp, ESP (Deep Tree)

INTEGER -1

DmdRedID FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT ' '

DmdToDate FF, MP, Supp, IPO, Flowcasting, ESP

DECIMAL 0

FcstAdjRule FF, MP, Supp, IPO, Flowcasting, ESP

OPTION_NUMBER 1,2,3,4,5,6,7,8

1

FcstConsumptionRule

FF, MP, Supp, IPO, Flowcasting, ESP

OPTION_NUMBER 0,1,2,3,4 0

FcstMeetEarlyDur MP, Supp, IPO, ESP

DURATION 0

FcstMeetLateDur MP, Supp, IPO, ESP

DURATION 0

FcstPrimConsDur MP, Supp, IPO, ESP

DURATION 0

FcstPriority MP, Supp, ESP (Deep Tree)

INTEGER -1

FcstSecConsDur FF, MP, Supp, IPO, Flowcasting, ESP

DURATION 0

IndDmdUnitCost FF, MP, Supp, Flowcasting, ESP (Deep Tree)

DECIMAL 0.0


SKUDemandParam


IndDmdUnitMargin MP, Supp, FF, ESP (Deep Tree)

DECIMAL 0.0

Item 1 FF, MP, Supp, IPO, Flowcasting, ESP

TEXT

Loc 2 FF, MP, Supp, IPO, Flowcasting, ESP

TEXT

MasterCal DDR TEXT ' '

MaxCustOrderSysDur

FF, MP, Supp, IPO, Flowcasting, ESP

DURATION 0

PriceCal ESP (LPOPT) TEXT ' ' ProrateByTypeSw FF, Flowcasting BOOLEAN 0 ProrateSw FF, MP, Supp,

IPO, Flowcasting, ESP

BOOLEAN 0

ProrationDur FF, MP, Supp, IPO, Flowcasting, ESP

DURATION 0

TargetEarlyDur ESP (LPOPT) DURATION UnitCarCost FF, Supp,

Flowcasting, ESP

DECIMAL 0.0

UnitPrice ESP (LPOPT) FLOAT (126) WeeklyAvgHist Demand, FF FLOAT (126) 0

Table description Each row in this table defines demand parameters associated with the SKU, , the settings that are used by RecShip, Dynamic Deployment, BTL and Load Manager.

Note: The item and location columns are required to run the inventory policy related processes.

IPO If you are using forecast data to compute the mean daily demand, this table is required. IPO uses this table to calculate the allocated total forecast which is stored in memory and used to compute the mean daily demand. See AllocCal (on page 133) for more information about allocation forecasts. Note that IPO does not use the SKUProjStatic table.

Column descriptions AllocCal


SKUDemandParam

Allocation calendar is a calendar that defines an allocation profile for this SKU's forecast demand (including adjustments), and, if there is no calendar specified in Sourcing:ShipCal, determines whether a source is open or closed for shipping.

Valid values for AllocCal are the identifiers of an existing Allocation Calendar (Cal:Cal whose Cal:Type is 7), or blank.

Both uses of this calendar are explained below.

Defining an allocation profile to spread the forecast (Master Planning, IPO, ESP, and Fulfillment/Distribution) The system uses the allocation profile 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.

To ensure that the forecast is allocated accurately, the Allocation Calendar should use the same or smaller periods than the forecast periods. For example, a forecast in daily periods will not be allocated accurately using a weekly Allocation Calendar, but a forecast in weekly periods will be allocated accurately with an Allocation Calendar in daily periods.

In the CalData table, each row in an Allocation Calendar includes an Allocation Weight to be used for spreading the forecast. For each forecast period, the system totals the Allocation Weights for all the rows whose time periods are within the forecast period. Then it calculates the forecast for each period in the calendar as:

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 adjustments) 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


SKUDemandParam

Period Alloc. Weight Spread 1 Spread 2 Spread 3 Total Spread

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 Determining whether a source is open or closed for shipping (Fulfillment/Distribution, Fulfillment/Deployment) If the Sourcing:ShipCal is blank, the allocation calendar is used to indicate whether a source is open or closed for shipping. If a period has no Allocation Weight (CalData:AllocWgt = 0), the source is closed for shipping and Calculate Plan will not schedule shipments in that period.

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 SKU will not be processed.

You can also use AllocCalGroup to group SKUs while generating allocation calendars. The Generate Allocation Calendar for SKUs process generates allocation calendars for SKUs based on the customer order history of a group of SKUs. You can group the SKUs by giving the same value to this column for all SKUs.

For example:

To group SKUs, set same values for AllocCalGroup

Item Location AllocCalGroup

small_red A XXX

medium_red A XXX

large_red A XXX

To set as individual SKUs, set different values for AllocCalGroup

Item Location AllocCalGroup

small_red A XXX

medium_red A YYY

large_red A ZZZ

CCPSw Customer Order Promising Point Switch (CCPSw) is the switch that determines whether the SKU is a customer commit point. Typically, a customer commit point is a SKU that is kept in inventory to serve as a component in multiple finished goods. The finished goods are assembled to order after receiving a customer commitment. The demand for customer commit point SKUs is forecasted, in contrast to the demand for the finished goods, which is based on customer orders.

• Yes: Customer Commit Point SKU


SKUDemandParam

The forecast for a customer commit point SKU is consumed by both independent demand for the SKU and dependent demand arising from demands for its parent (and other ancestor) SKUs.

If this SKU uses a postponement strategy, such as make-to-order or assemble-to-order, you should project the forecast for ancestor SKUs into this SKU. Consumption of dependent demand from those ancestors will allow orders for ancestors to consume that forecast.

• No: Not a Customer Commit Point SKU

This SKU is not a customer commit point SKU, so its forecast is consumed only by independent demand.

CustOrderDur When the Calculate Master Plan (Master Planning), Generate Master Plan (ESP), or the Calculate Plan process supplements the forecast with customer orders (when FcstAdjRule is 2, 3, 4, or 5), it uses Customer Order Duration (CustOrderDur). CustOrderDur starts at SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank). This column defines the duration for which the system considers customer orders when adjusting the forecast based on the FcstAdjRule (on page 137) setting.

Outside the CustOrderDur, the forecast is consumed according to the rule specified in the FcstConsumptionRule (on page 144) column.

CustOrderPriority Customer Order Priority (CustOrderPriority) is the value that indicates the importance of customer order lines for this SKU in relation to all other customer order lines. If the priority for a specific customer order line, customer order, or customer has not been set, the Master Planning process uses this priority when determining which demand to satisfy first.

Valid values for CustOrderPriority are between 0 to 2,100,000,000.

A value of 1 is most important and higher values are less important. A value of 0 means that no priority has been set, and the system will use the priority that has been set in Master Planning process properties.

You can set customer order priorities in several places, which Master Planning checks in the following sequence:

• CustOrder:Priority (priority of a specific customer order line)

• CustOrderHeader:Priority (priority of all the customer order lines in one customer order)

• Cust:Priority (priority of all the customer order lines for one customer)

• SKUDemandParam:CustOrderPriority (priority of all customer order lines for one SKU)

• Customer Order Priority (priority of all customer order lines) set on the Calculate Master Plan process page.

DmdRedID If you specify a value in Demand Reduction Identifier (DmdRedID), planning logic will reduce total demand by the amount of demand that cannot be met before the first replenishment is scheduled. DmdRedID determines which components of demand will be used to reduce total demand—forecasted customer orders, non-forecasted customer orders, adjusted forecast, distribution demand, or dependent demand.

Valid values for DmdRedID are an existing DmdRedID in the DmdRed table, or blank.

Each row in the DmdRed table specifies one or more of those components. If you want planning logic to reduce total demand, pick the DmdRedID whose combination of components you want the system to use when reducing the demand for this SKU, then enter its ID in this column. When the types of demand you specify cannot be met on time, planning logic reduces total demand by removing those demands from the total forecast.

If you leave this column blank, planning logic does not reduce total demand. JDA Dynamic Demand Response Reference Guide 136 © 1997 - 2014 JDA Software Group, Inc.- Confidential

SKUDemandParam

See Eliminating unmet demand in the JDA Fulfillment OnLine Expert for more information.

DmdToDate The value that the process uses to prorate the forecast by demand to date when the Proration Switch (ProrateSw (on page 146)) is set to Y.

To prorate the forecast, the system subtracts the value in this column from the forecasted demand (the portion of the allocated forecast that occurs between the beginning of the proration period and OHPost). It displays result in ProratedAllocTotFcst from OHPost through the end of the proration period. The system spreads this quantity based on the Allocation Weight (CalData:AllocWgt) defined for the SKU’s Allocation Calendar (AllocCal (on page 133)). Prorated forecast quantities are shown in SKUProjStatic:ProratedAllocTotFcst.

If DmdToDate (on page 137) is larger than the forecasted demand, the quantity that is added to the remaining forecast is negative. In this case, the allocated forecast beyond OHPost decreases instead of increases, but does not become negative.

Refer to ProrationDur (on page 146) for information on how the system determines the length of the proration period.

FcstAdjRule This option determines whether and how the processes supplement forecasted demand with customer orders. They adjust the forecast within the Customer Order Duration, which is calculated as the period starting at SKU:OHPost. Outside the CustOrderDur, the forecast is consumed according to the rule specified in the FcstConsumptionRule (on page 144) column).

The forecast adjustment logic uses customer orders where both of the following are true:

CustOrder:FcstSw = Yes

CustOrder:ShipDate is earlier than or equal to the end of the Customer Order Duration

Past due customer orders (where ShipDate is earlier than SKU:OHPost) will be slotted and displayed on the ShipDate in Plan Analysis, but will be considered to fall on SKU:OHPost for the purposes of forecast adjustment when CustOrder:FcstSw is set to Y. The quantity of the customer order is counted as if it falls within the customer order duration, but the customer order itself still counts on the date it is scheduled. So, for example, with forecast adjustment rule 3, (greater of the forecast or customer order), you might still see a forecast on OHPost since the customer order was actually scheduled earlier.

The forecast adjustment rules use the following values from the SKUProjStatic columns:

ProratedAllocTotFcst (the total prorated forecast, allocated according to the weights and time periods in the SKU’s allocation calendar)

FcstCustOrders (the total quantity of all forecasted customer orders for each period)

The rules adjust those values and store the results in these SKUProjStatic columns:

AdjAllocTotFcst (the total allocated forecast, adjusted according to the rule used)

AdjFcstCustOrders (total forecasted customer orders, adjusted according to the rule used)

Specify the number of a forecast adjustment rule from the following:

1 = None

The system does not supplement the forecast with customer orders.

When using Rule 1, AdjFcstCustOrders = 0.

If your system includes Fulfillment/Distribution:


SKUDemandParam

AdjAllocTotFcst = ProratedAllocTotFcst

If you system includes MasterPlanning:

AdjAllocTotFcst=ProratedAllocTotFcst and AdjFcstCustOrders=FcstCustOrders

Otherwise:

AdjAllocTotFcst = TotFcst

2 = Customer orders

Within the Customer Order Duration, Rule 2 ignores the forecast and uses customer orders as the demand. It slots the customer orders into time intervals based on the reporting calendar being used.

With this rule:

• AdjAllocTotFcst = 0

• AdjFcstCustOrders = FcstCustOrders

3 = Maximum, follow customer order curve

For this rule to work correctly, the SKU must have an allocation calendar (AllocCal (on page 133)).

Within the Customer Order Duration, Rule 3 considers the total forecasted demand quantity to be equal to the greater of the forecast or forecasted customer orders.

If the customer order quantity is greater:



• Total forecasted demand = AdjAllocTotFcst + AdjFcstCustOrders

When the forecast is greater, if CalData:AllocWgt has the same value in each period, Rule 3 spreads the difference between the forecast and customer orders so the total forecasted demand in each period follows the customer order curve, as illustrated in the figure below:

Figure: Forecast adjustment using rule 3


SKUDemandParam

Compare this to Rule 4, which causes total forecasted demand to follow the curve representing the difference between forecast and customer orders.

When calculating total forecasted demand, Rule 3 uses the following calculations for each period in the Customer Order Duration:

• AdjAllocTotFcst = allocation factor × (ProratedAllocTotFcst – FcstCustOrds)



The next example illustrates the use of Rule 3 for a SKU whose Customer Order Duration covers four periods. In this example, CalData:AllocWgt is not the same in every period.

Adjust the forecast with Rule 3

Period ProratedAllocTotFcst

FcstCustOrds

Total

ProratedAllocTotFcst –

Total

FcstCustOrders

Alloc

Wgt

Alloc

factor

AdjAllocTotFcst

Total demand

(FcstCustOrds +

AdjAllocTotFcst)

1 400 800 50 .25 150 950

2 650 50 30 .15 90 140 3 200 200 20 .10 60 260 4 600 200 100 .50 300 500 Total 1850 1250 600 200 1 600 1850

4 = Maximum, reallocate unmet forecast

For this rule to work correctly, the SKU must have an allocation calendar (AllocCal (on page 133)). However, the system ignores CalData:AllocWgt when using Rule 4.

Within the Customer Order Duration, Rule 4 considers the total forecasted demand quantity to be equal to the greater of the forecast or forecasted customer orders.

If the customer order quantity is greater:





SKUDemandParam

When the forecast is greater, Rule 4 spreads the difference between the two so the total forecasted demand in each period follows the curve of the difference between forecast and customer orders, as illustrated in the figure below:.

Figure: Forecast adjustment using rule 4.

Compare this to Rule 3, which causes total forecasted demand to follow the customer order curve if the Allocation Weight is the same in every period. "Adjust the forecast with Rule 4" illustrates how Rule 4 works, using the same data that was used in "Adjust the forecast with Rule 3".


Period SKUProj-

Static:

ProratedAllocTotFcst

SKUProj-

Static:

FcstCustOrds

Excess forecast

(ProratedAllocTotFcst

– FcstCustOrds)

Forecast

adjustment

weight

AdjAlloc

TotFcst

Total forecasted demand

(FcstCustOrders

+AdjAllocTotFcst)

1 400 800 –400 0 0 800

2 650 50 600 .6 360 410 3 200 200 0 0 0 200 4 600 200 400 .4 240 440 Total 1850 1250 600 1.0 600 1850

Rule 4 determines how much excess forecast must be allocated to individual periods in the Customer Order Duration:

Excess forecast = total ProratedAllocTotFcst – total FcstCustOrders = 1850 – 1250 = 600


SKUDemandParam

For each period in which the forecast exceeds customer orders, Rule 4 calculates a forecast adjustment weight:

It calculates the adjusted forecast for each period in the Customer Order Duration:

It calculates the total forecasted demand for each period in the Customer Order Duration as:

AdjAllocTotFcst + AdjFcstCustOrders

5 = Carry backward

For this rule to work correctly, the SKU must have an allocation calendar (AllocCal (on page 133)).

Rule 5 is useful for companies that want to develop forecasts for products that have many possible combinations of optional features. It is impractical to forecast specific configurations for such products. Instead, you could forecast the demand for a generic product, such as a computer, and take customer orders for a specific configuration of that computer.

For example:

• Sales forecast (for the generic product) = 60

• Forecasted customer orders (for specific product versions) = 50

• Excess forecast (ProratedAllocTotFcst) = forecast – customer orders = 10

No specific configurations for the remaining 10 forecasted units have been ordered, so the excess forecast of 10 is used to reserve assembly capacity at the generic level, driving material requirements for components based on the bill of material.

The system allocates the excess forecast, beginning with the last period of the Allocation Calendar that falls within the Customer Order Duration and working backward. For each period, Rule 5 calculates the AdjAllocTotFcst like this:

Excess forecast = the greater of:

• This period’s ProratedAllocTotFcst – This period’s FcstCustOrds

• 0

AdjAllocTotFcst = the smaller of:

• Excess forecast

• Remaining AdjAllocTotFcst from the previous period

Remaining AdjAllocTotFcst = the greater of:

• Previous remaining Total AdjAllocTotFcst – This period’s AdjAllocTotFcst

• 0

The result of this example appears in the following table.


SKUDemandParam

Period 1 2 3 4 5 Total

ProratedAllocTotFcst 20 20 20 20 20 100

FcstCustOrds 40 0 0 0 30 70 Excess forecast 0 20 20 20 0 — AdjAllocTotFcst 0 0 10 20 0 30 Remaining AdjAllocTotFcst at the end of this period

0 0 0 10 30 —

6 = Short term customer orders

To use Rule 6, you must specify a duration in MaxCustOrderSysDur (on page 146).

With Rule 6, two Customer Order Durations are considered, as follows:

• From OHPost through the duration specified in CustOrderDur (on page 136):


• AdjFcstCustOrds = Fcst Cust Orders

• From the end of the Customer Order Duration through the Maximum Customer Order Duration, the forecast is adjusted based on Forecast Adjustment Rule 3 (Maximum, Follow Customer Order Curve).

For more information on Rule 6, refer to:

• Implementing Rule 6 (on page 143)

• SKU:MaxCustOrderSysDur

• JDA Fulfillment OnLine Expert, Inventory management in JDA Fulfillment.

7 = Short term customer orders and forecast

For this rule to work correctly, you must specify a duration in MaxCustOrderSysDur (on page 146).

Rule 7, similar to Rule 6, determines whether and how Calculate Plan and Master Planning supplement forecasted demand with customer orders. Both Rules 6 and 7 use two Customer Order Durations, but while Rule 6 adjusts the second Customer Order Duration using FcstAdjRule 3, Rule 7 adjusts the second Customer Order Duration using FcstAdjRule 4.

Rule 7 is a combination of existing FcstAdjRules 2 and 4. In the first Customer Order Duration, only customer orders are considered, not forecast (Rule 2 – Customer orders). In the second duration, forecast and customer orders are adjusted according to Rule 4 (Maximum, reallocate unmet forecast). The absolute difference between forecast and customer orders in the first duration is reconciled over the second duration. "Adjust the forecast with Rule 7" illustrates how Rule 2 and Rule 4 works together..



SKUDemandParam

Period SKUProj-

Static:

ProratedAllocTotFc

st

SKUProj-

Static:

FcstCustOrds

Excess forecast

(ProratedAllocTotFcst

– FcstCustOrds)

Forecast

adjustment

weight

AdjAlloc

TotFcst

Total forecasted

demand

(FcstCustOrders

+AdjAllocTotFcst)

1 100 25 75 0 0 25

2 50 25 25 0 0 25 3 30 30 0 0 0 30 Total 100

4 100 50 50 0.5 85 135

5 50 80 -30 0 0 80 6 50 0 50 0.5 85 85 Total 380 70

Periods 1,2 and 3 follows Rule 2 which ignores the forecast and uses only customer orders as the demand within custorder duration. Therefore, the total forecast demand in period 1,2 and 3 is equal to forecasted custorder.

Total excess forecast from period 1 to period 3 is 100.

Periods 4,5 and 6 follows Rule 4 within MaxCustOrderSysDur. The forecast and customer orders are adjusted according to Rule 4. This rule determines how much excess forecast must be allocated to individual periods in the MaxCustOrderSysDur.

For each period in which the forecast exceeds customer orders, Rule 4 calculates a forecast adjustment weight and calculates the adjusted forecast for each period in the customer order duration:

The excess forecast in the CustOrder duration is reconciled within MaxCustOrderSys duration.

Therefore, in the above example the total AdjAllocTotFcst in periods 4 and 6 will be 35+50=85 and the total demand is equal to AdjAllocTotFcst + AdjFcstCustOrders.

8 = Dynamic Demand Response (DDR) Integration

Selecting Rule 8 enables you to integrate Fulfillment with Dynamic Demand Response (DDR).

The values of AdjAllocTotFcst after selecting Forecast Adjustment Rule 8 are Allocated, Prorated, Consumed, and adjusted by Dynamic Demand Response (DDR) Process.

Implementing Rule 6

All forecast adjustment rules (with the exception of Rule 1) adjust the forecast with customer orders within the duration defined by CustOrderDur (on page 136). This duration extends from SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank) through the length of time defined by CustOrderDur.

When you set FcstAdjRule (on page 137) to 6:

• From OHPost through the duration specified in CustOrderDur, the adjusted forecast is equal to zero.


SKUDemandParam

• From the end of the Customer Order Duration through the Maximum Customer Order Duration (specified in MaxCustOrderSysDur (on page 146)), the forecast is adjusted based on Forecast Adjustment Rule 3 (Maximum, Follow Customer Order Curve).

FcstConsumptionRule The forecast consumption rule for this SKU. This rule impacts the calculation of AdjAllocTotFcst for the time period starting with OHPost + CustOrderDur, or starting with OHPost + CustOrderDur + MAxCustOrderSysDur, if FcstAdjRule = 6 or 7. Only customer orders that fall after that point in time are considered, and only forecasts that fall after that point in time are consumed by the customer orders.

• 0: The forecasted customer orders do not consume any forecasts.

• 1: Use SKU level primary forecast consumption duration specified in the FcstPrimConsDur (on page 144) as forward consumption duration and FcstSecConsDur (on page 145) as backward consumption duration. Iterate over forecast orders change quantity one by one, finding customer orders to consume the forecast.

• 2: Use SKU level primary forecast consumption duration specified in the SKU column FcstPrimConsDur (on page 144) as backward consumption duration and FcstSecConsDur (on page 145) as forward consumption duration. Iterate over forecast orders change quantity one by one, finding customer orders to consume the forecast.

• 3: Use SKU level primary forecast consumption duration specified in the SKU column FcstPrimConsDur (on page 144) as forward consumption duration and FcstSecConsDur (on page 145) as backward consumption duration. Iterate over customer orders change quantity one by one, finding forecast orders to consume.

• 4: Use SKU level primary forecast consumption duration specified in the SKU column FcstPrimConsDur (on page 144) as backward consumption duration and FcstSecConsDur (on page 145) as forward consumption duration. Iterate over customer orders change quantity one by one, finding forecast orders to consume.

FcstMeetEarlyDur The duration (in minutes) that the algorithm uses while stepping early to search for supplies to satisfy forecast orders for this SKU.

You can use this value to prevent supply for forecast orders from consuming resources too far before the actual need date. If this value is greater than 0, the process will try to find supply that will result in meeting the order earlier than:

FcstOrder:NeedDate – SKUDemandParam:FcstMeetEarlyDur

Master Planning, ESP To override this value, check the Override check box and specify a value in the Forecast Order Meet Early Duration field on the Calculate Master Plan or Generate Master Plan process page.

FcstMeetLateDur The duration (in minutes) that the algorithm uses while stepping late to search for supplies to satisfy forecast orders for this SKU.

You can use this value to prevent supply for forecast orders from consuming resources too far after the actual need date. If this value is greater than 0, the process will try to find supply that will result in meeting the order not later than:

FcstOrder:NeedDate + FcstMeetLateDur

Master Planning, ESP To override this value, check the Override check box and specify a value in the Forecast Order Meet Late Duration field on the Calculate Master Plan or Generate Master Plan process page.

FcstPrimConsDur


SKUDemandParam

The duration (in minutes) that the algorithm considers for the primary pass of the forecast consumption process. The primary consumption direction is determined by the chosen FcstConsumptionRule (on page 144).

FcstPriority Master Planning, ESP The value that indicates the importance of forecast orders for this SKU in relation to all other forecast orders. The Calculate Master Plan process uses this priority when determining which demand to satisfy first. When a forecast order is created, this value is used in FcstOrder:Priority.

Valid values for FcstPrimConsDur are 0 to 2,100,000,000.

A value of 1 is most important and larger values are less important. The default database value is -1. A value of -1 means that no priority has been set. If the FcstPriority = -1, then the Calculate Master Plan process will use the priority set in Generate Forecast Orders process page.

FcstSecConsDur The duration (in minutes) that the algorithm considers for the secondary pass of the forecast consumption process. The secondary consumption direction is determined by the chosen FcstConsumptionRule (on page 144).

IndDmdUnitCost User-defined standard cost for this SKU.

Master Planning, ESP Master Planning uses this value to calculate revenue for customer orders when CustOrder:Revenue has a value of -1. Master Planning always uses this value to calculate revenue for forecast orders and stock orders. IndDmdUnitCost is also used to calculate demand order cost on the Master Planning Scorecard.

Fulfillment Fulfillment/Order Optimization uses this column to specify the weight of the items within an order. For more information, refer Setting up item weights section in the Order Optimization chapter of JDA Fulfillment OnLine Expert.

Other applications All other applications use IndDmdUnitCost to calculate Inventory Cost (SKUProjStatic:InvCarCost) and the standard cost (SKUProjStatic:StandardCost) of replenishing a SKU in a material-constrained supply plan.

IndDmdUnitMargin Master Planning, ESP Represents the profit expected after selling one unit of this SKU—that is, the difference between the selling price and the manufacturing cost. IndDmdUnitMargin is used in calculating the revenue or margin for a customer order if CustOrder:Revenue or CustOrder:Margin is less than 0. IndDmdUnitMargin is always used in calculating the revenue and margin for forecast orders and stock orders.

Fulfillment Represents the profit expected after selling one unit of this SKU, that is, the difference between the selling price and the manufacturing cost. This column is used in calculating the revenue or margin for a particular SKU based on demand.

Item The item associated with the SKU defined in this row. Must be a valid item in the Item table.

Loc The location associated with the SKU defined in this row. Must be a valid location in the Loc table.

MasterCal


SKUDemandParam

The Master Calendar associated with the DFU.

MaxCustOrderSysDur Defines the maximum customer order duration. The system uses the maximum customer order duration when FcstAdjRule (on page 137) is set to 6 or 7 to define a second duration, in addition to the one defined by CustOrderDur (on page 136), during which the system adjusts the forecast with customer orders.

PriceCal This field specifies a calendar that defines the time varying pricing of a SKU.

ProrateByTypeSw This switch enables forecast allocation, proration, and adjustment / consumption for an SKU to be performed separately for each type of forecast. For a SKU, if the switch is set to 1, the process generates adjusted allocated forecasts and adjusted forecasted customer orders for each forecast type (see SKUDemandTypeParam:FcstType) that you select. In addition, it also generates allocated forecasts for that SKU.

If this switch is set to 0, the forecast allocation, proration, adjustment, and consumption is done at the SKU level, considering all forecast types at once.

ProrateSw Switch that the system uses to determine whether to preserve the allocated forecast or to prorate the allocated forecast by demand to date.

A setting of N causes the system to preserve the allocated forecast regardless of the demand to date. By preserving the allocated forecast, the system assumes that if a certain percentage of time has passed within a forecast period, then an identical percentage of the allocated forecast as of that point in time has been consumed.

A setting of Y tells the system to prorate the forecast by demand to date, using the value in DmdToDate (on page 137).

Refer to DmdToDate, ProrationDur (on page 146), and SKUProjStatic:AllocTotFcst for more information on forecast proration.

ProrationDur Defines the length of the proration period. The proration period is the period of time during which the system prorates the forecast, if ProrateSw (on page 146) is set to Y. The start date of the proration period is the start date of the earliest non-zero forecast record for this SKU in either the DFUtoSKUFcst table or the SKUExternalFcst table.

Refer to DmdToDate (on page 137), ProrateSw (on page 146), and SKUProjStatic:AllocTotFcst for more information on forecast proration.

TargetEarlyDur Specifies the duration that helps to reduce delay in shipping a SKU on the date that is good to have it shipped.

UnitCarCost A user-defined value the system uses to calculate the Inventory Carrying Cost (SKU projection InvCarCost). UnitCarCost should be the cost per year for holding one unit of this SKU in inventory, divided by the Standard Cost.

ESP The cost of holding a unit of this SKU, for a day, as inventory.

UnitPrice The selling price of a unit of SKU.


SKUDemandParam

WeeklyAvgHist It is the average value of the history for the selected period.


SKUException

SKUException Table included with: Fulfillment, Master Planning, Supply, Inventory Policy Optimization, Dynamic Demand Response, Flowcasting, Enterprise Supply Planning


Default value

BatchNum 2 FF, MP, Supp, IPO, Flowcasting, ESP

INTEGER 0

BOMNum MP, Supp, IPO, ESP

INTEGER 0

DemandQty MP, Supp, Flowcasting, ESP

DECIMAL 0

Descr FF, MP, Supp, IPO, Flowcasting, ESP

TEXT ' '

Eff FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

Exception FF, MP, Supp, IPO, Flowcasting, ESP

INTEGER

ExceptionDate FF, MP, Supp, IPO, Flowcasting, ESP

DATETIME 01/01/1970

FunctionName FF, MP, Supp, IPO, Flowcasting, ESP

TEXT ' '

FunctionNum 4 FF, MP, Supp, IPO, Flowcasting, ESP

INTEGER

Item FF, MP, Supp, IPO, Flowcasting, ESP

TEXT

LevelNum 5 FF, MP, Supp, IPO, Flowcasting, ESP

INTEGER 0

Loc FF, MP, Supp, IPO, Flowcasting, ESP

TEXT


SKUException


Default value

Offset FF, MP, Supp, Flowcasting, ESP

DURATION 0

ParentItem FF, MP, Supp, IPO, Flowcasting, ESP

TEXT ' '

ParentLoc FF, MP, Supp, IPO, Flowcasting, ESP

TEXT ' '

ProcessID 1 FF, MP, Supp, IPO, Flowcasting, ESP

OPTION_NUMBER

Any value in the PROCESSOPTIONSET: PROCESSID column

0

ProductionMethod

FF, MP, Supp, Flowcasting, ESP

TEXT ' '

PurchMethod FF, MP, Supp, Flowcasting, ESP

TEXT ' '

SeqNum 3 FF, MP, Supp, IPO, Flowcasting, ESP

INTEGER

Sourcing FF, MP, Supp, IPO, Flowcasting, ESP

TEXT ' '

UserID FF, MP, Supp, IPO, Flowcasting, ESP

TEXT ' '

When FF, MP, Supp, IPO, Flowcasting, ESP

DATETIME 01/01/1970

ReviewedStatus MP, ESP INTEGER 1, 2, 3, 4, 5

1

Category MP, ESP INTEGER 0 Severity MP, ESP INTEGER 1, 2, 3 0 LastUpdatedOn MP, ESP DATE 01/01/1970

LastUpdatedBy MP, ESP UPPER_TEXT ' '

Table description


SKUException

Each row in this table identifies an exception found while processing a SKU. The process or page that detects the exception inserts rows into the table. Processes clear the existing rows the next time they process the SKU.

For example, if the Calculate Master Plan process (Master Planning) or Calculate Plan process (Fulfillment) tries to plan a SKU for which the OHPost date is blank, it inserts a row identifying the process, SKU, and exception 9 or 5510. If you set a valid OHPost date for the SKU, then run the process again, the row is removed from the table. You cannot edit the values in this table.

To locate an exception quickly, you can use the ExceptionDate (on page 176) column to filter for the date and time that the exception occurred within the planning horizon.

Master Planning, Supply, ESP This table stores all SKU exceptions. The ExceptionOrderRelation table maintains a relationship between the independent demands and the exceptions generated against them. Exceptions can be SKU (material) or resource (capacity) related. Resource exceptions are stored in the ResException table.

Column descriptions BatchNum The value used to identify the batch in which the independent demands were processed.

BOMNum Bill of Material Number (BOMNum) is a value used to identify the bill of material for a parent item. Copied from the BOM:BOMNum column.

Category The exception is now associated with a ‘Category’. This new column indicates the type of the exception and is used to relate the exception to its cause of generation.

DemandQty The demand quantity associated with this exception.

Descr Description of this exception.

Eff The effectivity date used to populate the BOM:Eff, if an exception occurs in the BOM record.

Exception Exception code number.

Fulfillment The Calculate Plan process generates the following exceptions:

• 0003 Invalid SKU:ReplenType

This SKU cannot be planned because the value in SKU:ReplenType is not valid.

• 0005 Invalid SKUPlanningParam:DRPRule

This SKU cannot be planned because the value in DRPRule is not valid.

• 0006 Location is closed on SchedArrivDate

The destination is not open for receiving on the SchedArrivDate. Calculate Plan has tried to adjust the SchedArrivDate. After checking both the source’s shipping calendar (Sourcing:ShipCal/SKUDemandParam:AllocCal as applicable) and the destination’s arrival calendar (Sourcing:ArrivCal), Calculate Plan could not find any other common shipping and receiving dates within the planning duration.

• 0007 No sources available for the location specified in the SKU.


SKUException

This SKU cannot be planned because Sourcing table does not include a row for the location specified in the SKU.

• 0008 Invalid SKUPlanningParam:MinDRPQty.

This DRP SKU cannot be planned because the value in MinDRPQty is less than zero and therefore not valid.

• 0009 Invalid OHPost.

This SKU cannot be planned because the value is 0 in both SKU:OHPost for this SKU and Loc:OHPost for this location.

• 0011 SKU does not exist.

It is not used in the current release.

• 0013 RecShip could not be scheduled prior to Recommended Shipments Duration and was cancelled.

The source is not open for shipping on the Scheduled Departure Date (RecShip:DepartureDate). Calculate Plan has tried to adjust DepartureDate. After checking the source’s shipping calendar (Sourcing:ShipCal/SKUDemandParam:AllocCal as applicable), the destination’s arrival calendar (Sourcing:ArrivCal), and the source’s recommended shipments calendar (SKUDeploymentParam:RecShipCal), Calculate Plan could not find any viable shipping and receiving dates within the recommended shipments duration, so Calculate Plan did not create the recommended shipment. For more information, see the Deployment overview: Calculate Dates. This exception is generated only when Calculate Plan is recommending shipments and is using limited-stock allocation procedures.

• 0014 Location is closed on RecShip:SchedArrivDate.

The destination is not open for receiving on the SchedArriv Date. Calculate Plan tries to adjust the SchedArrivDate. After checking the source’s shipping calendar (Sourcing:ShipCal/SKUDemandParam:AllocCal as applicable), the destination’s arrival calendar (Sourcing:ArrivCal), and the source’s recommended shipments calendar (SKUDeploymentParam:RecShipCal), Calculate Plan could not find any viable shipping and receiving dates within the recommended shipments duration, so Calculate Plan did not create the recommended shipment.

This exception occurs only when Plan is recommending shipments and is using limited-stock allocation procedures.

• 0015 Invalid SKUPlanningParam:MPSRule.

This MPS SKU cannot be planned because the value in MPSRule for the SKU is less than zero and therefore invalid.

• 0016 Invalid SKUPlanningParam:MinMPSQty.

This SKU cannot be planned because the value in MinMPSQty is invalid.

• 0017 Production is closed

This SKU cannot be planned because its production calendar (SKUPlanningParam: ProdCal) is closed for the planning period.

• 0022 Invalid Allocation Strategy.

This SKU cannot be planned because the value in SKUDeploymentParam:AllocStratID is not valid or blank. AllocStratID must be specified for the source SKU—that is, AllocStratID must be an existing row in the AllocStrat table. This exception appears only if stock at the source SKU is limited.

• 0023 Invalid Sourcing:MajorShipQty.

This SKU cannot be planned because the value in Sourcing:MajorShipQty is less than zero and therefore not valid.


SKUException

• 0024 RecShip:SchedShipDate moved out.

The Scheduled Shipping Date (RecShip:SchedShipDate) for a recommended shipment was moved later in time because one of these conditions occurred:

• Stock was not available on the original SchedShipDate, so Calculate Plan selected the next available date within SKUDeploymentParam:StockAvailDur on which stock became available.

• The source’s allocation calendar (SKUDemandParam:AllocCal) was closed on the original SchedShipDate, so Calculate Plan selected the next available date within the recommended shipments duration on which the calendar was open.

• the RecShip is not limited, but is matching a PlanShip whose NeedShipDate is earlier than OHPost.

• the SKU is set to push (RecShipPushOpt = 2 or 3) but the SKU is ReplenType 2 and is not in the Sourcing table.

This exception occurs when Calculate Plan is recommending shipments and is using limited-stock allocation procedures. For more information, see the OnLine Expert.

If the SKU is both a source and a destination SKU, this exception occurs for the source SKU (i.e. the exception applies to a RecShip coming from this SKU, not a RecArriv coming into this SKU).

• 0025 RecShipCal does not exist.

This SKU cannot be planned because the Cal table does not include a row for the recommended shipment calendar specified for the SKU, or because the calendar specified is not a recommended shipment calendar.

• 0027 NeedShipDate at or before OHPost.

Calculate Plan has created a planned arrival whose NeedShipDate is on or before SKU:OHPost and Loc:OHPost. When NeedShipDate is on or before OHPost, Plan sets SchedShipDate to OHPost. If a SKU has this exception, it will also have exception 0042 SchedShipDate moved out.

If the SKU is both a source and a destination SKU, this exception occurs for the source SKU (i.e. the exception applies to a PlanShip coming from this SKU, not a PlanArriv coming into this SKU).

• 0028 PlanDur < LeadTime/TimeFence:

This SKU was not planned because one or more of the following conditions are occurring

• SKUPlanningParam:PlanDur is shorter than the larger of SKUPlanningParam:PlanLeadTime and SKUPlanningParam:DRPTimeFenceDur.

• Sources are available for the DRP SKU, but not throughout the entire planning horizon.

• Either the Arrival calendar or Shipping calendar is closed throughout the entire planning horizon.

• Both Loc:OHPost and SKU:OHPost are blank.

• Sourcing rows are defined for this destination SKU, but all rows have Sourcing:Factor set to zero.

• SKUPlanningParam:Expdate is earlier than the earliest potential replenishment date.

This exception occurs at a destination SKU if all its source SKUs have their Sourcing:Factor set to zero.

• 0029 SKUPlanningParam:MaxOH < Safety Stock.

This SKU was planned but the value in MaxOH is less than the safety stock level.

• 0030 SKU with circular network/BOM.


SKUException

This SKU was not planned because its network or bill of material (BOM) is circular or because the combination of Supersession relationships has made it impossible to assign feasible PlanLevel values to this and related Item records. When the Level SKUs process detects circularity, it sets SKU:PlanLevel or Item:PlanLevel to -1.

In a simple circular network, one row in the Sourcing table has SKU A as the source and SKU B as the destination; in another row, SKU B is the source and SKU A is the destination. In a simple circular BOM, one row in the BOM table has SKU A as the parent item and SKU B as the subordinate; in another row, SKU B is the parent item and SKU A is the subordinate.

Plan requires that two or more items in a Supersession relationship share the same Item:PlanLevel value and also requires that any parent item has a lower PlanLevel value than its subordinate items. Sometimes the array of Supersession and BOM relationships does not allow for this to occur.

• 0032 Invalid SKUPlanningParam:IncMPSQty.

This MPS SKU was not planned because the value in IncMPSQty must be greater than 0.

• 0033 Invalid SKUPlanningParam:IncDRPQty.

This DRP SKU was not planned because the value in IncDRPQty must be greater than 0.

• 0034 MaxPlan reached.

Calculate Plan has scheduled the maximum number of planned orders or planned arrivals for this SKU and will schedule no more. This maximum number is specified in the Maximum number of replenishments options on the Calculate Plan process options page. For information on how to set process options, see the section called Running processes in Process Manager in the Fulfillment OnLine Expert. If this exception occurs on a perishable SKU, check for exception 56.

• 0035 Invalid Sourcing:ArrivCal.

This SKU was not planned because the value in Sourcing:ArrivCal for one of its sources is not an arrival calendar. When this exception is generated, the Plan and Deployment logics stop processing all the SKUs with this item.

• 0036 Invalid SKUDemandParam:AllocCal.

This SKU was not planned because the value in AllocCal is not an allocation calendar.

• 0037 Invalid SKUPlanningParam:ProdCal.

This SKU was not planned because the value in SKUPlanningParam:ProdCal is not a production calendar.

• 0038 SKUProjStatic:ProjOH is greater than SKU:MaxOH.

• 0039 Limited stock available, allocation strategy used.

Calculate Plan used limited-stock allocation procedures when recommending shipments for this SKU because its stock was limited within the minimum allocation period and SKUDeploymentParam:ConstrRecShipSw is set to Yes. (This exception appears even if there is no stock available.) For an explanation of limited-stock allocation procedures, in the JDA Fulfillment OnLine Expert, see Deployment: the basics.

This exception occurs for the source SKU (i.e. the one the RecShips are coming from). When determining whether stock is limited the logic considers all destination demands, rounded if necessary, all available source supplies within the stock available duration, and all local source demands. Source safety stock is considered or ignored based on the value of SKUDeploymentParam:SourceSSRule. When considering all of these factors, if all of the demands can be met on time with the source supply, then the source is unlimited; else it is limited and this exception is written.

Note: For Supersession SKUs, Proxy Supplies are not taken into account when determining whether the source is limited.

Exception 39 may be generated for ultimate destinations in Supersession deployment. JDA Dynamic Demand Response Reference Guide 153 © 1997 - 2014 JDA Software Group, Inc.- Confidential

SKUException

• 0040 RecShip:SchedArrivDate moved out.

The Scheduled Arrival Date (RecShip:SchedArrivDate) for a recommended shipment was moved forward in time because the arrival calendar at the destination (Sourcing:ArrivCal) was closed on the original date. This exception occurs only when Calculate Plan is forced to move a date because of a closed arrival calendar; it is not used when Plan moves the Scheduled Arrival Date to correspond to a change in the Scheduled Ship Date (RecShip:SchedShipDate).

This exception occurs only when Plan is recommending shipments and is using limited-stock allocation procedures. For an explanation of limited-stock allocation procedures, in the JDA Fulfillment/Deployment OnLine Expert, see Deployment: the basics.

If the SKU is both a source and a destination SKU, this exception occurs for the source SKU (i.e. the exception applies to a RecShip coming from this SKU, not a RecArriv coming into this SKU).

• 0042 SchedShipDate moved out.

The Scheduled Ship Date (PlanArriv:SchedShipDate) for a planned arrival was moved forward in time because the source’s allocation calendar (SKUDemandParam:AllocCal) was closed on the original date. Calculate Plan also moves the corresponding scheduled arrival date (PlanArriv:SchedArrivDate) forward in time. If the destination is not open for receiving on the new date (based on Sourcing:ArrivCal), Plan may move SchedArrivDate farther out.

If the SKU is both a source and a destination SKU, this exception occurs for the source SKU (i.e. the exception applies to a RecShip/PlanShip coming from this SKU, not a RecArriv/PlanArriv coming into this SKU).

• 0043 SchedArrivDate moved out.

The Scheduled Arrival Date (PlanArriv:SchedArrivDate or RecShip:SchedArrivDate) for a planned arrival was moved forward in time because the arrival calendar at the destination (Sourcing:ArrivCal) was closed on the original date. This exception occurs only when Calculate Plan is forced to move a date because of a closed arrival calendar; it is not used when Plan moves the Scheduled Arrival Date to correspond to a change in the Scheduled Ship Date (PlanArriv:SchedShipDate).

If the SKU is both a source and a destination SKU, this exception occurs for the source SKU (i.e. the exception applies to a RecShip/PlanShip coming from this SKU, not a RecArriv/PlanArriv coming into this SKU).

• 0044 RecShip:NeedShipDate at or before OHPost.

Calculate Plan has created a recommended shipment whose NeedShipDate is on or before SKU:OHPost and Loc:OHPost. If a SKU has this exception, it will also have exception 0024: RecShip:SchedShipDate moved out.

This exception occurs only when Plan is recommending shipments and is using limited-stock allocation procedures. See the OnLine Expert for more information.

• 0045 PlanArriv(s) removed because of SKUPlanningParam:MaxOH.

Because SKUPlanningParam:DRPRule is set to 2 (Order Up to Quantity), Calculate Plan had to remove one or more planned arrivals (beginning with the smallest quantity) so that the on hand at the destination would not exceed the value in MaxOH. If, after removing planned arrivals, the on hand at the destination still exceeds MaxOH, the SKU will have this exception.

• 0048 SKUDeploymentParam:SurplusSSFactor < SKUDeploymentParam:ShortageSSFactor.

The SurplusSSFactor is lesser than ShortageSSFactor, then the SurplusSSFactor value will be set to ShortageSSFactor value and the SKUs will be processed in case of Dynamic Deployment.

• 0049 Neither the DynDepDur nor the SKUDeploymentParam:SAD is valid

The system cannot run the Dynamic Deployment option in Calculate Plan for this SKU because:

• The Dynamic Deployment duration (specified on the Calculate Plan process page) is set to zero; and


SKUException

• SKUDeploymentParam:DynDeplDur is set to zero; and

• The Stock Available Duration column (SKUDeploymentParam:StockAvailDur) is set to zero.

• 0050 SKUDeploymentParam:ShortageDur exceeds horizon (DynDepDur or SAD)

The Shortage Duration (SKUDeploymentParam:ShortageDur) is longer than the Dynamic Deployment Duration (specified on the Calculate Plan process page or in SKUDeploymentParam:DynDeplDur) or the Stock Available Duration (SKUDeploymentParam:StockAvailDur). Dynamic Deployment ignores ShortageDur for the SKU and continues processing.

• 0051 Shortage exists within Dynamic Deployment Horizon

The system ran the Dynamic Deployment option in Calculate Plan for this SKU, but a shortage still exists. Note that the Recommend Substitute Shipments process does not delete exception 0051, so shortages may have been resolved by the Recommend Substitute Shipments process.

This exception occurs for the destination SKU.

• 0053 Dynamic Deployment - Problem Infeasible

During Dynamic Deployment processing, an exception was generated for this SKU that the optimizer could not resolve because the problem was too complex. This exception applies to the whole item family to which the SKU belongs. To resolve this exception, try one of the following:

• Reduce the length of the Dynamic Deployment horizon.

• Eliminate either the initial stockout cost (InitStkoutCost) or the incremental stockout cost (IncStkoutCost) from the SKU table.

Usually either one of these solutions is sufficient.

• 0054 Demand ignored prior to first replenishment date

The demand reduction feature has been set for this SKU (SKUDemandParam:DmdRedID is not blank), and there were demands on the SKU that could not be met. The demands have been ignored.

• 0055 DRPCovDur has been adjusted

During processing, Calculate Plan found that the shelf life for a planned arrival at the scheduled arrival date was less than the DRP coverage duration plus the minimum shelf life duration plus the plan lead time to the source. Calculate Plan adjusted the DRP coverage duration as follows:

SKUPerishableParam:ResidualShelfLifeDur - (SKUPerishableParam:MinShelfLifeDur + PlanArriv:SchedArrivDate - PlanArriv:NeedArrivDate)

• 0056 Unable to meet shelf life requirements

After adjusting the coverage duration for a planned arrival or a planned order, Calculate Plan found that it could not meet the freshness requirement for some or all demands on this SKU. The SKUPerishableParam:MinCovDur, MinShelfLifeDur, MaxShelfLifeDur, or ultimate source ShelfLifeDur may need to be adjusted.

• 0057 MPSCovDur has been adjusted.

While processing, Calculate Plan found that the shelf life for a planned order at the scheduled date was less than the MPS coverage duration plus the minimum shelf life duration. Calculate Plan adjusted the MPS coverage duration as follows:

SKUPerishableParam:ShelfLifeDur - SKUPerishableParam:MinShelfLifeDur

• 0058 Unusable firm inventory found

In processing this SKU, Calculate Plan has encountered the first instance of stock that has either reached its minimum shelf life duration or has reached the end of its effective shelf life.

• 0059 Expired inventory found


SKUException

The inventory for this SKU has reached its expiration date.

• 0062 Quantity reduced to avoid waste

Calculate Plan has reduced the replenishment quantity of a planned order or a planned arrival to avoid waste. The process determined the maximum allowable waste, as follows:

Maximum Allowable Waste = SKUPerishableParam:MaxWasteFactor x the largest replenishment quantity

• 0066 Invalid SKU:PlanLevel

Generated by the Level SKUs process when a SKU cannot be processed. The Level SKUs process sets the PlanLevel column for that SKU to -1.

A SKU cannot be processed when one of the following conditions exists:

• Circularity is detected during the Level SKUs process and the level codes of all affected SKUs are set to -1. See exception 0030 to find the SKUs causing the circularity.

• You did not run the Level SKUs process on the search before running Plan.

• 0067 Invalid ShelfLifeDur

Calculate Plan skipped this SKU because the value specified in the SKUPerishableParam:ShelfLifeDur column was invalid. This exception occurs in the following conditions:

• ShelfLifeDur for an MPS SKU is zero

• Leadtime from MPS SKU to DRP SKU is larger than the ShelfLifeDur for the MPS SKU

• Cumulative leadtime from ultimate source SKU to ultimate destination SKU exceeds the ShelfLifeDur for the ultimate source SKU

• ShelfLifeRule is set to manual for a DRP SKU and ShelfLifeDur = zero for that DRP SKU

• 0068 Invalid ShelfLifeGroup

Calculate Plan skipped this SKU because the value specified in the SKUPerishableParam:ShelfLifeGroup column was invalid.

• 0069 FirsReplenDate is After SKUPlanningParam:ExpDate

Calculate Plan skipped this SKU because the first date when a replenishment can be scheduled for this SKU (considering the specified lead time) is later than the expiration date for the SKU.

• 0070 Shortage exists within Dynamic Deployment Horizon but is met with later shipment

Calculate Plan skipped this SKU because a shortage within the Dynamic Deployment horizon exists. However, this shortage is met with a later shipment.

• 0071 Surplus exists at alternate location with no sourcing relationship

Dynamic Deployment skipped this SKU because no surplus exists within the Dynamic Deployment sourcing network (DynDepSrc:Source). However, surplus exists at an alternate location outside the sourcing network.

• 0072 Invalid Item:DynDepQty; default to 1

Dynamic Deployment skipped this SKU because the value in Item:DynDepQty must be greater than zero. When this quantity is invalid, the system defaults to 1 in order to continue processing.

• 0073 Demand Outside the ProdStopDate.

Calculate Plan did not generate planned orders to meet the demands for this SKU. Calculate Plan ignores demands that exist after the SKUPlanningParam:ProdStopDate when generating planned orders.

• 0074 Demands at or after ExpDate ignored.


SKUException

Calculate Plan did not generate replenishments for this SKU. Calculate Plan ignores demands that exist at or after SKUPlanningParam:ExpDate.

• 0075 Invalid expiration date.

• 0076 Unusable quantity in planned replenishment.

During processing this SKU, Calculate Plan has found a planned replenishment that has either reached its minimum shelf life duration or has reached the end of its effective shelf life.

• 0077 Unable to meet demand ExpDate, demand ignored.

Calculate Plan has found a demand that does not meet shelf life requirements. Ignore it.

• 0078 SKU projections are not generated

Time phased projections such as projected on-hand, are not generated for the SKU. This occurs when an expected record is missing from one or more SKU related tables.

• 0079 Allocation strategy has an invalid priority

An allocation strategy priority record has a demand sub type for a demand type that does not have sub types.

Note: The only demand types that have sub types are adjusted forecasts (type 1) and adjusted forecasted orders (type 2).

• 0080 Meets the demand though not able to satisfy the expiry date

When InfeasibleOpt is set to 3 and DRP or MPS Plan encounters infeasible expiration date, this exception occurs . If that happens, Plan continues to plan for that SKU and creates a replenishment to meet that demand.

• 0081 Invalid Supply Expiration Date (EarlyDate), Assuming LateDate

This exception is only raised for SKUs having Item:PerishableSw set to Yes.

While processing, Calculate Plan found a supply like Inventory, Schedrcpts and IntransIns with the expiry date set to EarlyDate. For perishable item supply, an expiry date of 1/1/1970 is considered invalid and the process treats it as having an expiry date of LateDate. This results in these supplies being treated as if they never expire.

• 0082 Invalid Distribution Demand ExpDate (EarlyDate or LateDate), assuming as Independent Demand

This exception is only raised for SKUs having Item:PerishableSw set to Yes. While processing, Calculate Plan found a distribution demand like Intransouts with the expiry date set to EarlyDate or LateDate.

For perishable item demand, an expiry date of EarlyDate or LateDate is considered invalid and the process treats it as having an expiry date similar to that of an Independent Demand. Therefore, the expiry date is taken as NeedDate + SKUPerishableParam:MinShelfLifeDur.

• 0083 No effective sourcing found for alternate SKU

This exception is generated in the following circumstances if Supersession is enabled for the SKU.

When a particular primary SKU has a sourcing relation with another destination SKU and the AltItem does not have a corresponding sourcing relation between the same two locations then this exception is raised by the Calculate Plan process.

• 0084 Overlap of BOM records exist

During processing, if Calculate Plan finds multiple BOM records between the same parent SKU and subordinate SKU with overlapping effectivity and offset then, this exception is generated. If the SKU is MPS and has a valid Production method, then BOMNUM is also considered while searching for multiple overlapping BOMs between parent SKU and subordinate SKU. The process uses the first such valid BOM relation which is loaded and ignores the rest.


SKUException

• 0085 SecRSAllocRule 3 is not supported with DSI and/or Supersession. Defaulting to rule 1

Perishable Item deployment and Supersession Items deployment is not supported with SKUs having SecRSAllocRule set to 3 (FairShare Need ship date). The SecRSAllocRule defaults to rule 1 (None) with RSAllocRule 3 (Need ship date).

• 0086 SecRSAllocRules 2 and 3 do not support DeployDetailLevel > 1. Defaulting DeployDetailLevel to 1

The combinations of SKUDeploymentParam:SecRSAllocRule = 2 (Equal Days of Coverage) or 3 (Deployment FairShare) and SKUDeploymentParam:DeployDetailLevel = 2 (Priority details) or 3 (Demand details) are not supported. In such cases, Calculate Plan defaults the value of SKUDeploymentParam: DeployDetailLevel to 1 (No Details).

• 0090: Cumulative Lead Time not calculated because of Invalid Sourcing Records.

Valid effective sourcing data is not found for this SKU or one of its source SKUs, so cumulative lead time cannot be calculated. Cumulative lead time is required in order for the TargetNetworkInv column to be stored in the AggSKUProjStatic table or displayed in the aggregate view in Plan Analysis.

• 0091 RecShipDur less than MinAllocDur, extending deployment horizon until MinAllocDur.

Calculate Plan Process generates this exception whenever the Recommended Shipments Duration (read from SKU:RecShipDur or from the Plan process properties page) is shorter than the Minimum Allocation Duration. When this exception is written, the recommended shipments logic extends the deployment horizon to MinAllocDur. This exception and behavior do not apply to SecRSAllocRule = 1 (None) and are temporarily not used by SecRSAllocRule = 3.

• 0092 Supersession is not Supported with DSI.

This exception is generated if DSI item is running with supersession relation, in such a case DSI item is excluded to be processed by Supersession Plan.

• 0100 Invalid Sourcing:ShipCal or DynDepSrc:ShipCal.

The calendar type for Sourcing:ShipCal or DynDepSrc:ShipCal is invalid. The correct calendar type is 6.

• 0101 Incomplete data in related SKU table.

This SKU was not planned because there is missing data in one of the related SKU parameter tables (for example, SKUPlanningParam, SKUDemandParam, and so forth).

In case of Calculate Plan process this exception is raised only under the following conditions:

• For non-perishable item, non-supersession SKUs: If data is present in SKU, SKUPlanningParam, SKUDeploymentParam, SKUDemandParam and missing from one of the other tables like SKUSafetyStockParam, SKUDemandTypeParam.

If data is missing from SKUPlanningParam, SKUDeploymentParam, SKUDemandParam then no exception will be raised and the SKU will not be processed either.

• For perishable item SKUs: If data is present in SKU, SKUPlanningParam, SKUDeploymentParam, SKUDemandParam and missing from one of the other tables like SKUPerishableParam, SKUSafetyStockParam, SKUDemandTypeParam.

If data is missing from SKUPlanningParam, SKUDeploymentParam, SKUDemandParam then no exception will be raised and the SKU will not be processed either.

• For supersession SKUs: If data is present in SKU, SKUPlanningParam, SKUDeploymentParam, SKUSafetyStockParam and missing from one of the other tables like SKUDemandTypeParam

In case of Calculate Statistical Safety Stock process, this exception is raised only under the following condition:

• If data is present in SKU, SKUPlanningParam, SKUSafetyStockParam and missing from one of the other tables like SKUDemandParam


SKUException

• 0102 Supplement Order created for an invalid SKU type

A Supplemental Order should only be created for DRP SKUs. If it is created for any other ReplenType then this exception is raised. The Supplemental Orders are ignored.

• 0103 Supplemental Order: ReleaseStartDate is before NeedArrivDate

This exception is raised by Calculate Plan process if Supplemental Order ReleaseStartDate is earlier than the NeedArrivdate. The ReleaseStartDate then defaults to the NeedArrivDate.

• 0104 Supplemental Order partially late or unmet, needed prior to FirstReplenDate

This exception is raised by Calculate Plan process if a Supplemental Order is releasing before FirstReplenDate and the Supply available before FirstReplenDate is not able to meet the Supplemental Order.

• 0105 Active Supplemental Order falls within the coverage duration for SKU

This exception is raised by Calculate Plan process if any Supplemental order exists with a NeedArrivDate that falls between FirstReplenDate and FirstReplenDate + DRPCovDur.

• 0106 Supplemental Order not supported for perishable SKUs

Calculate Plan process raises this exception if Supplemental Orders are defined for SKUs having Item:PerishableSw set to Yes. This combination is not supported.

• 0107 MaxCovDur constraint violation

Calculate Plan raises this exception when MaxCovDur has been violated by one or more planned replenishments. This occurs if respecting MaxCovDur would have caused the projected available inventory to drop below zero.

• 0108 Invalid SKUPlanningParam:WorkingCal.

Calculate Plan raises this exception when a SKU was not planned because the value in SKUPlanningParam:WorkingCal is not a working calendar.

• 0109 Projected on-hand violates MaxOH constraint.

Calculate Plan raises this exception when SKUPlanningParam:MaxOHRule=2 or 3 and a replenishment causes projected on hand to exceed the latest effective SSPresentation:MaxOH. If SSPresentation:MaxOH is configured as the default value, then SKUPlanningParam: MaxOH value is considered.

• 0110: Forced Supplemental Orders are not supported for Supersession SKUs

• 0111: Supplemental Orders are not respected while deploying SKUs with SecRSAllocRule 3

• 0112: Bad SS Template. No SSTemplateData records are defined for the SSTemplate that is assigned to this SKU.

• 0113 Remaining Supply at Immediate Push Source within StockAvailDur.

• 0114: EDC Respected Over Supersession

This source SKU has SKUDeploymentParam:SecRSAllocRule = 2 (Equal Days of Coverage) and the item is in a Supersession relationship. This SKU will be deployed using Equal Days of Coverage logic and Supersession logic will not be run in Deployment.

• 0115: ConvenientShipQty is not a multiple of IncDRPQty.

• 0116: Convenience rounding is not respected when DRPRule is set to Order up to quantity.

• 0151 Planned arrival supply cannot be allocated to any destinations

A portion of a planned arrival quantity at a flow through SKU (SKU:StorableSw = 0) was not mapped to a demand that could consume it at any eligible destination

• 0152 Firm Supply cannot be allocated to any destinations.


SKUException

All or a portion of a firm supply quantity at a flow through SKU (SKU:StorableSw = 0) was not mapped to a demand that could consume it at any eligible destination

• 0153 FlowThrough plan logic ignored for OrderUpto SKU.

Flowthrough plan logic is ignored for SKUs whose SKUPlanningParam:DRPRule=2

• 0154 MaxOH constraint not respected in Flowthrough Plan.

• 0155 Rounding factor constraint not respected in Flowthrough Plan.

• 0156 MaxCovDur constraint not respected in Flowthrough Plan.

• 0157 Demand Reduction not respected in Flowthrough Plan.

• 0158 Restrict plan logic not respected in Flowthrough Plan.

• 0159 FlowThrough plan logic ignored for perishable SKU.

• 0160 Supersession plan logic ignored for Flow Through SKU

Supersession is not supported for Flow through SKUs.

• 0161 Leadtime on PlanArriv into Flowthrough SKU extended in order to align SchedArrivDate with RecShipcal.

• 0162 Distribution demand at Flow-Through SKU cannot be met by any firm or planned supplies.

The source SKU for this SKU is a flow through SKU, and no planned arrival could be scheduled into that source SKU at a time at which it could be shipped to this destination.

• 0163: Demand ignored due to MaxWasteFactor.

The quantity of a planned arrival or planned order was decreased in order to respect the MaxWasteFactor, causing actual demands to go unmet.

• 0164: Safety Stock ignored due to MaxWasteFactor.

The quantity of a planned arrival or planned order was decreased in order to respect the MaxWasteFactor, causing a projected available quantity to be less than zero. The safety stock quantity that was ignored may be met by a later replenishment or may not be met at all.

• 0203 Invalid SKUPlanningParam:RecSchedRcptsDur.

• 0204 SKU not found in SKUStatStatic table.

• 0221 No daily calendar.

• 0226 Missing Data in SkuHistfcst

Required data was missing from the SKUHistFcst table during the calculation of SKU MSE.

• 0227 No effective destinations found for this location.

No effective destination was found during processing of the Centralized MSE calculation.

• 0241 DFUtoSKU not found.

The Statistical Safety Stock process skipped this SKU because it is not associated with any row in the DFUtoSKU table.

• 0242 Demand post date not found.

No value is specified in DFU:DmdPostDate. As a result, the system did not use the value in DFUtoSKU:ConvFactor when you ran the Statistical Safety Stock process. If ConvFactor has a value other than 1, the results of the Statistical Safety Stock process may be incorrect.

• 0244 Annual Forecast Frequency Exceeds 52

The number of forecast periods specified for the Demand calendar in Cal:NumFcxtPer is greater than 52.


SKUException

• 0245 Inconsistent DemandPostDate on DFUs

The values in DFU:DmdPostDate for two or more DFUs for this SKU do not match, or the values in SKUSafetyStockParam:DmdPostDate for the related SKUs during processing of the Centralized MSE calculation do not match.

• 0246 Inconsistent Demand Calendar on DFUs

The values in DFU:DmdCal for two or more DFUs for this SKU do not match.

• 0247 Invalid Demand Calendar Data

The seasonality error for this SKU was not calculated because the value specified in the DFU:DmdCal or the DBParam:DmdCal was invalid. The DmdCal must be an identifier whose calendar type (Cal:Type) is 5.

• 0248 DmdCal not specified in DFU or DBPARAM table

The Calculate Seasonality Error process has detected that a Demand calendar has not been specified in the DFU or the DBParam table. A value must be specified in the DFU:DmdCal and the DBParam:DmdCal columns in order for the system to calculate the seasonality error.

• 0249 Invalid SkuSafetyStockParam.MsePer.

This SKU was not planned because the value of MSEPer must be greater than 0.

• 0250 No Effective DFUTOSKUMap for the period

Note: This exception is not used in the current release.

This SKU was not planned for the period specified, because either there is no DFU to SKU mapping or the mapping is ineffective.

• 0251 Invalid SKUSafetyStockParam:DmdDistType/CSLMetric.

The current release supports only a SKUSafetyStockParam:DmdDistType/CSLMetric (demand distribution type/customer service level) combination of 1 and 2, 1 and 3, 2 and 3, 1 and 1, or 3 and 1, respectively.

• 0252 Invalid SKUSafetyStockParam:StatSSCSL.

StatSSCSL (Statistical Safety Stock customer service level) must be a decimal number greater than or equal to zero and less than 1.

• 0253 Invalid MSE:MSE.

The value for MSE (mean squared error) in the SKU table is invalid.

The MSE cannot be less than 0. If your system does not include Demand, an invalid value was imported into MSE.

• 0254 Invalid SKUSafetyStockParam:FcstDur.

The value for FcstDur (forecast duration) in the SKU table is invalid. The Calculate Statistical Safety Stock process uses the value in this column to calculate statistical safety stock for the SKU and requires a value for forecast duration that is greater than 0.

• 0255 Invalid lead time.

The value specified for lead time cannot be used by the Calculate Statistical Safety Stock process. The value for lead time must be greater than 0. If Calculate Plan uses Fulfillment/Distribution to replenish the SKU, first it checks the SKUSafetyStockParam:AvgLeadTime. If AvgLeadTime is not greater than 0, then it checks the PlanLeadTime/MfgLeadTime, depending on the replenishment type. If SKU:ReplenType = 1, the AvgDmd is dependent on the SKUPlanningParam:PlanLeadTime. If Calculate Plan replenishes the SKU using MPS (ReplenType = 2), the lead time is the value specified in SKUPlanningParam:MfgLeadTime.

• 0256 Invalid SKUSafetyStockParam:NumReplenYr.


SKUException

The value specified for NumReplenYr (number of replenishments per year) is invalid. To calculate statistical safety stock, you must use a value greater than 0.

• 0257 Invalid SKUSafetyStockParam:AvgNumLines.

The value specified for AvgNumLines (average number of lines per customer order) is invalid. To calculate statistical safety stock, you must use a value greater than 0.

• 0258 Invalid or no forecast.

Note: This exception is not used in the current release.

The Calculate Statistical Safety Stock process could not calculate statistical safety stock because either no forecast for the SKU exists or the forecast is invalid. Verify that a forecast exists by checking SKUProj:TotFcst (Total Forecast), and ensure that the forecast is a positive number.

• 0259 Invalid DmdVar:DmdVar Value

The value specified for DmdVar:DmdVar (demand variance) is invalid. The demand variance for this SKU must be a decimal number.

• 0260 Invalid AvgDmd:Qty Value

The value specified for AvgDmd:Qty is invalid. The value must be a decimal number.

• 0261 Statistical Safety Stock Exceeds Coverage Limit

The Calculate Statistical Safety Stock process could not calculate statistical safety stock because the safety stock is greater than the specified coverage limit.

• 0262 Forward coverage calculation is not supported for time phased StatSS.

This SKU was not processed because the forward coverage calculation is not supported for time-phased statistical safety stock.

• 0264 Time phased MSE calculation/smoothing is not supported.

This SKU was not processed because the time-phased MSE calculation/smoothing is not supported.

• 0265 Invalid SkuSafetyStockParam.MseLag.

This SKU was not processed because an invalid value was specified for SKUSafetyStockParam:MSELag. This value must be greater than or equal to 0.

• 0266 Invalid SkuSafetyStockParam.LeadTimeSD.

This SKU was not processed because an invalid value was specified for SKUSafetyStockParam:LeadTimeSD. This value must be greater than or equal to 0.

• 0267 Invalid SkuSafetyStockParam.AvgDmdCal.

This SKU was not processed because an invalid value was specified for SKUSafetyStockParam:AvgDmdCal. This value must be of calendar type 3 (Cal:Type = 3).

• 0268 SkuSafetyStockParam.DmdPostDate after OhPost.

This SKU was not processed because the value specified in SKUSafetyStockParam:DmdPostDate is later than SKU:OHPost. The value in DmdPostDate must be on or before OHPost.

• 0269 Invalid MSE rule.

MSE rules are valid in the increasing order corresponding to the increasing order of the level in the network with the following observations:

• MSE rule 1 is valid at all levels.

• MSE rules 3 and 4 are valid at all levels.

• MSE rule 4 behaves like rule 3 at 0 plan level.

• MSE rule 4 is not a valid rule, if lower plan level has MSE rule 1.


SKUException

• At other levels MSE rule 4 and MSE rule 5 follow the hierarchy of levels and rules. In other words, it is invalid to specify MSE rule 4 at a higher plan level when MSE rule 5 exists at a lower plan level.

• MSE rule 5 is not a valid rule at 0 plan level.

• 0270 Too few observations to compute SKU MSE.

This exception is generated if the number of observations in SKUHist and SKUHistFcst is less than 30.

• 0271 Invalid min/max values for ratio masking.

This exception is generated if one or both of the following conditions exists:

• SKUSafetyStockParam:MSEMaskMinVal and SKUSafetyStockParam:MSEMaskMaxVal are not in the range from 0 to 1.

• SKUSafetyStockParam:MSEAbsToleranceLimit is equal to zero and absolute of SKUHist:Qty - SKUHistFcst:(BaseFcst+NonBaseFcst) is greater than SKUSafetyStockParam:MSEAbsToleranceLimit.

• 0272 Invalid min/max values for percentage masking.

This exception is generated if one or both of the following conditions exists:

• SKUSafetyStockParam:MSEMaskMinVal and SKUSafetyStockParam:MSEMaskMaxVal are not in the range from 1 to 100.

• SKUSafetyStockParam:MSEAbsToleranceLimit is equal to zero, absolute of SKUHist:Qty - SKUHistFcst:(BaseFcst+NonBaseFcst) is greater than SKUSafetyStockParam:MSEAbsToleranceLimit.

• 0273 Multiple BOM Entries exist for the same parent because of different Eff and Offset Values.

• 0274 No effective parents for the given BOM component.

• 0275 Zero draw Quantity.

• 0276 Since MSE information of parents is not available, it is not considered.

• 0300 Alternate Transmode used for this SKU.

When the load is not satisfactory on the highest priority TransMode, the algorithm tries to load the next alternate Transmode. If this is successful, this exception is generated.

• 0301 Buffer logic applied to RecShip:AvailToShipDate.

We can define buffer lead time on the Build Transportation Loads process page to relax the available to ship date. This exception is generated when the load is built using one of the RecShips whose available to ship date has been relaxed.

• 0302 Splitting the RecShips resulted in a new RecShip with quantity less than the Sourcing:SplitQty.

This exception is generated when the RecShips (created as a result of splitting RecShips) quantity is less than the Sourcing:SplitQty.

• 0303 Unable to find a conversion to a constraint UOM category

This exception is generated when the conversion factor between the TransModeCap:UOM/NetworkCap:UOM and the default UOM is missing in the UOMCategoryConversionFactor/SourcingUOMConvFactor table.

• 0304 Invalid multi-pickup load. Check for inconsistent VehicleLoad:ShipDate or VehicleLoad:ArrivDate.

This exception is generated in MultiPickedUp when there are existing vehicleloads from different sources (all are attached to a common VehicleLoad:ConsolidatedLoadSeqnum) and have different VehicleLoad:ShipDate or VehicleLoad:ArrivDate


SKUException

• 0305 Maximum limit on the VehicleLoads has been reached, skipping the lane for BTL run. All RecShips in this lane are affected.

This exception is generated when too many loads were getting created for a particular lane and it reaches specified max limit. In this case no loads are built and RecShips will not be deleted. In case of PTP this limit will apply for each lane. In case of MPU this limit will apply for each consolidated lane. In case of PTP with rolling this limit will apply to each rolling cycle for lane, if it reaches this limit in any rolling cycle BTL will not build loads for all the rolling cycles of the lane. This exception is raised for all scenarios except AltTrans mode.

• 0500 History Not Found or All Zeros given in Store Segmentation process.

This exception is generated when there is no record or when you find all zeros for DFU in the History table.

• 3000 Invalid Start date given in the Out Of Stock detection process.

This exception is generated when Start date of the process is greater than OHPost date

• 3001 Invalid History Stream given in the Out Of Stock detection process.

This exception is generated at SKU level, when there is no DFU with the selected history stream on the process page. This is applicable only when user selects Statistical method.

• 3002 No History data available given in the Out Of Stock detection process.

This exception is generated when there is no history data available in the history table. This is applicable only when the user selects Statistical Method.

• 3003 No valid Beginning On Hand given in the Out Of Stock detection process.

This exception is generated when there is no BOH available in SKUFactsData table.

• 3004 No Valid Weekly Average given in the Out Of Stock detection process.

This exception is generated when there is no weekly average in SKUDemandParam table.

• 3005 Invalid Calendar given in Out Of Stock detection process.

This exception is generated comes when the process Start date and duration is not covered by the Calendar duration.

• 3006 Invalid Category given in Out Of Stock detection process.

This exception is generated when there is no Valid Category available for SKU in SKUSalesProbability table.

• 3007 No SKUPlanningParam was found for this SKU given in Out Of Stock detection process.

This exception is generated when the record is not available in the SKUPlanningParam table for the SKU selected.

• 3008 No SKUDemandParam was found for this SKU given in Out Of Stock detection process.

This exception is generated when the record is not available in the SKUDemandParam table for he SKU selected.

• 3100 Invalid Process Start Date for the SKU in Identify and Analyze Root Causes process.

This exception is generated when the process start date exceeds the SKU OH post date.

• 3101 Missing DFU Data in Identify and Analyze Root Causes process.

This exception is generated when the process can not associate any DFU with the SKU.

• 3102 Missing previous lag Hist Forecast for the SKU in Identify and Analyze Root Causes process.

This exception is generated when the previous lag Hist Forecast is missing for the SKU.

• 5009 Excess Inventory of Subordinate SKU


SKUException

This exception is generated when not all of a Bulk SKU’s inventory can be consumed. It may be due to rounding or Parent SKU parameters.

• 5021 Insufficient inventory to meet firm demands.

This exception occurs when a Subordinate SKU is unable to meet its firm demands in full and on time. Depending on the SKU’s infeasibility option, it may or may not be processed.

• 5022 Unable to meet firm demands on time

This exception occurs when a Subordinate SKU is unable to meet its firm demands on time.

• 5023 Shares a parent with another selected Subordinate SKU.

This exception occurs when more than one subordinate SKU selected for the Material Allocation process shares a common parent. The Material Allocation process does not have logic to handle this condition, so the SKUs will not be processed.

• 5024 Parent SKU has more than one selected Subordinate SKU.

This exception occurs when a parent SKU has more than one selected subordinate. These SKUs will not be processed.

• 5025 Member of an invalid tree.

This exception occurs when a Subordinate SKU receives either 5023 or 5021 exception. These SKUs will not be processed.

• 5026 Bulk SKU consumption delayed due to Production calendar.

This exception occurs when a Parent SKU is unable to consume a Bulk SKU supply on the supply’s available date due to the Parent SKU’s production calendar. Inventory will be consumed as if the date can be met, but the consumption will be scheduled at the next valid time.

• 5027 Production delay duration violated due to Production calendar.

This exception occurs if production of a parent is delayed because of subordinate availability and the parent production calendar is closed when subordinate supply is available. If the delay is lengthened beyond the Parent SKU’s production delay duration due to this closure, this exception is generated and the parent production is still created as if the production calendar were open at the available date of the subordinate inventory and rescheduled to the next open production calendar date.

• 5028 Does not have a record in the SKUMatAllocParam table.

This exception occurs if the SKU does not have a record in SKUMatAllocParam.

• 5029 Does not have a record in the SKUPlanningParam table.

This exception occurs if the SKU does not have a record in SKUPlanningParam.

• 5030 Does not have a valid level.

• 5603: Forecast records cannot be merged as DmdCals are different

This exception is generated when the Transfer Forecast process is run with Merge to Base/ Merge to base, and non-base for a DFU that have multiple forecast records with different demand calendars and different forecast types.

• 5604: Number of forecast periods in DFUToSKUFcstWide is insufficient

This exception is generated when the number of forecast periods for the DFUToSKUFcst table is less than the Fcst table) and the process attempts to publish the forecast period beyond the last period.

• 5605:DFUToSKUFcstWide:DmdCal does not match with FcstWide:DmdCal

This exception is displayed when the forecast demand calendar does not match with the existing DFUToSKUFcst demand calendar.


SKUException

Master Planning, ESP The Generate Forecast Orders process generates the following SKU exceptions:

Exception

Number

Exception Text Category Id

Category Description

Related

Objects

5500 Plan Arrival is not converted to forecast order because the Plan Arrival Expiration Date is earlier than the Scheduled Arrival Date.

507 Invalid Plan Arrival

5501 Vehicle Load Line is not converted to forecast order because the Vehicle Load Line Expiration Date is earlier than the Schedule Arrival Date.

523 Invalid VehicleLoadLine

The Calculate Master Plan or Generate Master Plan process generates the following SKU exceptions:

Exception

Number



Related

Objects

5507 SKU has an invalid MPSCovDur. MPSCovDur is either negative or zero or isn’t an integer multiple of bucket duration. The process will consider the bucket duration specified on the process page as the MPSCovDur.

520 Invalid SKU Parameter

5508 SKU has an invalid MPS Rule, using rule 1 instead. 520 Invalid SKU Parameter

5510 SKU has an invalid OH Post Date. 520 Invalid SKU Parameter

5511 SKU has an invalid Price Calendar, neglecting the prices instead.

605 Invalid Calendar

5512 ProductionYield has an invalid Yield Calendar, considering the yield as 1 instead.


5514 Item in ImpDepDmdStatic is not defined as an alternate for the SKU in AltBOM. Ignoring the record.

503 Invalid ImpDepDemandStatic Parameter

5522 BOM has an invalid Effective Date, using OH post date as effective date instead.

502 Invalid BOM Parameter

5523 BOM has an invalid Discontinue Date, using OH post date as discontinue date instead.


5524 BOM has an invalid Draw Quantity, using 0 instead. 502 Invalid BOM Parameter

5525 BOM has an invalid Mix Factor, using 100 instead. 502 Invalid BOM Parameter

5526 BOM has an invalid Shrinkage Factor, using 0 instead.


5527 BOM has an invalid Yield Factor, using 100 instead. 502 Invalid BOM Parameter

5529 BOM has an invalid parent SKU. 501 Invalid BOM 5530 BOM has an invalid Subordinate SKU. 501 Invalid BOM


SKUException

Exception

Number



Related

Objects

5531 Working Calendar has an invalid master calendar, using a default all-open calendar instead.


5532 Production Capacity Calendar has an invalid master calendar, using a default all-open calendar instead.


5533 Shipping or Arrival Calendar has an invalid master calendar, using a default all-open calendar instead.


5549 Production Method has an invalid Effective Date, using OH post date as Effective Date instead.

511 Invalid ProdMethod Parameter

5550 Production Method has an invalid Discontinue Date, using OH post date as Discontinue Date instead.


5551 Production Method has an invalid Incremental Quantity, using 1 instead.


5552 Production Method has an invalid Minimum Quantity, using 1 instead.


5553 Production Method has an invalid Maximum Quantity, using 999,999,999 instead.


5554 Production Method has an invalid Lead Time, using 0 instead.


5555 Production Method has an invalid output SKU. 510 Invalid ProdMethod 5558 Parallel Dependent step has the same resource

name as in previous production step. 512 Invalid ProdStep

Parameter

5559 Resource has an invalid Production Capacity Calendar, neglecting the production step instead.


5560 ProductionStep has an invalid ProdRateCal, neglecting the ProdRateCal instead.


5562 Sourcing has an invalid Source SKU. 521 Invalid Sourcing 5563 Sourcing has an invalid Destination SKU. 521 Invalid Sourcing 5565 Sourcing has an invalid Factor. 522 Invalid Sourcing

Parameter

5566 Sourcing has an invalid Shrinkage Factor, using 0 instead.

522 Invalid Sourcing Parameter

5569 Sourcing has an invalid Major Shipping Quantity, using 1 instead.


5570 Sourcing has an invalid Minor Shipping Quantity, using 0 instead.


5572 Sourcing has an invalid Maximum Shipping Quantity, using 0 instead.


5573 Sourcing has an invalid Ship Calendar, using a default all-open calendar instead.


5576 Location has an invalid Working Calendar, using a default all-open calendar instead


5583 Resource has an invalid Storage Calendar, neglecting the calendar instead.


5584 Scheduled Receipt has an invalid Supply Method, none will be used.

519 Invalid SchedReceipts


SKUException

Exception

Number



Related

Objects

5609 Planned Order has an invalid Supply Method. 508 Invalid Plan Order 5621 Purchase Method has an invalid SKU. 514 Invalid PurchMethod 5622 Purchase Method has an invalid Minimum Order

Quantity, using 1 instead. 515 Invalid PurchMethod

Parameter

5623 Purchase Method has an invalid Incremental Order Quantity, using 1 instead.

515 Invalid PurchMethod Parameter

5624 Purchase Method has an invalid Maximum Order Quantity, using 0 instead.


5625 Purchase Method has an invalid Lead Time, using 0 day instead.


5626 Production Method has an invalid BOM Number. 511 Invalid ProdMethod Parameter

5627 Purchase Method has an invalid Factor. 515 Invalid PurchMethod Parameter

5628 Purchase Method has an invalid Arrival Calendar, using a default all-open calendar instead.


5629 Sourcing has an invalid Shipping Calendar, using a default all-open calendar instead.


5632 Production Method has an invalid Finish Calendar, using a default all-open calendar instead.


5636 Production Method has an invalid Priority, using 1 instead.


5637 Sourcing has an invalid Priority, using 1 instead. 522 Invalid Sourcing Parameter

5638 Purchase Method has an invalid Priority, using 1 instead.


5640 Calendar defined for a resource is not a Storage Calendar.


5653 Recommended shipment has an invalid Sourcing. 516 Invalid RecShip 5666 Production Method has an invalid Factor. 511 Invalid ProdMethod

Parameter

5672 Vehicle Load Line has an invalid Supply Method. 523 Invalid VehicleLoadLine

5702 Production Method has an invalid LoadOpt, using 1 instead.


5703 Production Method Step has an invalid FixedLoadDur when the Production Method is of Fixed Loading type. The Production Method will be used as Variable Loading type.

512 Invalid ProdStep Parameter

5704 Production Method Step has insufficient lead time for the total of all the steps FixedLoadDur. The Production Method leadtime will be changed to total of all steps FixedLoadDur.



SKUException

Exception

Number



Related

Objects

5709 Shelf Life Duration of the perishable SKU was set to zero in the database. Plan duration in the process page is considered as the shelf life duration for the SKU.

506 Invalid Perishable Parameter

5710 SKUPerishableParam record does not exist for the perishable SKU. The SKU will be considered as non-perishable by process.


5711 The Minimum Shelf Life Duration is treated as zero because Minimum Shelf Life Duration is greater than Shelf Life Duration.


5712 The Minimum Shelf Life Duration is treated as zero because Minimum Shelf Life Duration is equal to Shelf Life Duration.


5714 Perishable SKU has non-zero on-hand specified in SKU table. Ignoring on-hand.


5716 Inventory ignored because it has expiration date earlier than the Avail Date.

505 Invalid Inventory Parameter

5717 Vehicle Load Line ignored because it has expiration date earlier than the Schedule Arrival Date.

523 Invalid VehicleLoadLine

5718 Purchase Order ignored because it has expiration date earlier than the Due Date.

513 Invalid Purch Order Parameter

5719 Firm Planned Arrival ignored because it has expiration date earlier than the Schedule Arrival Date.

507 Invalid Plan Arrival

5720 Firm Planned Order ignored because it has expiration date earlier than the Schedule Date.

508 Invalid Plan Order

5721 Firm Planned Purchase ignored because it has expiration date earlier than the Scheduled Date.

509 Invalid Plan Purchase

5722 Schedule Receipt ignored because it has expiration date earlier than the Scheduled Date.

519 Invalid SchedReceipts

5723 ImpResloaddetails:WhenLoaded date is later than the expiration date of the supply.

504 Invalid ImpResLoadDetails Parameter

5728 Imported dependent demand start/need date is later than the requirement expiration date of the dep demand.

503 Invalid ImpDepDemand Parameter

5729 Item of a CCP SKU is defined as perishable. Considering the SKU as a non-perishable CCP SKU.


5730 Time phased production steps of this production method has different Next step timing specified. Production Method is ignored.


5745 ProductionStep has invalid NextStepTiming, instead the next step is considered as sequential.



SKUException

Exception

Number


Category Descriptio

n

Related Objects

6006 Cannot meet demand on time using this Production Method. Production Method lead time places the need date before the OHPost date on the supplying SKU.

610 Production Lead Time

Manufactured SKU Production Method

6007 Cannot meet demand on time using this Sourcing Method. Sourcing lead time places the need date before the OHPost date on the supplying SKU.

616 Sourcing Lead Time

Destination SKU Sourcing Method

6008 Insufficient inventory projected to be available within freeze period, or inventory not available until after demand order's need finish date.

604 Freeze Period

Demand Order SKU

6013 Cannot meet demand on time using this Purchase Method. Purchase Method lead time places the supply order start date before the planning start date.

611 Purchase Lead Time

Purchased SKU Purchase Method

6019 Cannot meet demand on time using this Supply Method. Independent demand places the need date before the planning start date or the OHPost date on the supplying SKU.

612 Resource loading time

Demand Order SKU

6020 Cannot meet demand on time using this Production Method. Production method lead time is less than minimum loading time on manufacturing resource.


Resource Manufactured SKU RouteStep

6021 Cannot meet demand on time using this Sourcing Method. Sourcing lead time is less than minimum loading time on transportation or handling resource.


Resource Destination SKU RouteStep

6023 Cannot meet demand on time using this Production Method. Production Method lead time places the need date before the planning start date.



6030 Cannot meet supply order on time using this Production Method. Production Method lead time places the need date before the OHPost date on the supplying SKU.



6031 Cannot meet supply order on time using this Sourcing Method. Sourcing lead time places the need date before the OHPost date on the supplying SKU.


Destination SKU Sourcing Method

6033 Cannot meet supply order on time using this Purchase Method. Purchase Method lead time places the supply order start date before the planning start date.

611 Purchase Lead Time

Purchased SKU Purchase Method

6036 Cannot meet supply order on time using this Production Method. Production Method lead time places the need date before the planning start date.




SKUException

Exception

Number


Category Descriptio

n

Related Objects

6037 Cannot meet supply order on time using this Sourcing Method. Sourcing lead time places the need date before the planning start date.


Supply Order SKU Sourcing Method

6051 Demand Order is late or unmet because Supply Method can not be utilized to start a new supply before No New Supply Date or Planning Fence.

604 Freeze Period

Supply Method Supply Order SKU

6060 Cannot meet demand on time using the production method as the PlanOrder could not be scheduled to finish within the production method MaxFinDur from its need date.

609 Pre-Build Restriction

6061 Cannot meet demand on time. Independent demand had a material constraint as SKU has no supply methods on need date.

608 Material Shortage

6062 Cannot meet scheduled supply on time. Scheduled Supply had a material constraint as dependent demand SKU has no supply methods on need date.


6063 Cannot meet demand on time. Independent demand had a material constraint as SKU has no effective supply methods on need date.

607 Invalid Supply Method

6064 Cannot meet Scheduled supply on time. Scheduled supply had a material constraint as dependent demand SKU has no effective supply methods on need date.

607 Invalid Supply Method

6065 The demand could not be met using the Supply Method because the Supply Order's Scheduled Start Date would need to be earlier than the Plan Start Date due to the SourceCal at the Source for the given Supply Method being set as not open on or before ExceptionDate.


6066 The demand could not be met using the Supply Method because the Supply Order's Scheduled Finish Date would need to be earlier than the Plan Start Date due to the FinishCal of the given Supply Method being set as not open on or before ExceptionDate.

606 Invalid Firm Plan Order

6072 Demand Order is late or unmet because Supply Method can not be utilized to finish a new supply before No New SupplyDate or Planning fence.

604 Freeze Period

Supply Order SKU Supply Method

6073 Firm Supply SchedDate is before the planning start date or the OHPost date.

606 Invalid Firm Plan Order

6074 Unable to meet shelf life requirement. 614 Shelf Life Restriction

6077 Coverage duration is exceeded due to constraints.


SKUException

Exception

Number


Category Descriptio

n

Related Objects

6078 The aggregated supply order has violated the specified MaxQty for the supply method in a coverage duration

6080 Cannot meet demand on time. Independent demand had a material constraint as the alternate subordinate is not effective on need date.


Aggregate Exceptions

Exception

Number

Exception Text Related Objects

6301 Manufacturing resource is at or near capacity by ExceptionDate. The additional capacity needed is LoadQty. Unable to utilize resource because an overload would occur.

Dependent Demand SKU Parent Supply SKU Independent Demand SKU

6302 Transportation resource is at or near capacity by ExceptionDate. The additional capacity needed is LoadQty. Unable to utilize resource because an overload would occur.

Dependent Demand SKU Parent Supply SKU Firm Supply SKU

6303 InHandling/OutHandling resource is at or near capacity by ExceptionDate. The additional capacity needed is LoadQty. Unable to utilize resource because an overload would occur.

Dependent Demand SKU Parent Supply SKU Firm Supply SKU

6402 Existing supply on SKU can not be pushed to exception date, likely due to capacity constraint.

6403 Existing supply on SKU can not be pushed to exception date. Production method is not effective.

6404 Existing supply on SKU can not be pushed to exception date. Sourcing is not effective.

6405 Existing supply on SKU can not be pushed to exception date. Purchase method is not effective.

Exception Number

Exception Text

7006 There is no effective production method defined for the SKU.

7503 No supply available for the BOM item to meet the dependent demand for the newly added or edited planned order.

The Master Planning integration with JDA Sequencing generates the following exceptions:


SKUException

Exception Number

Exception Text

11000 Unknown sequencing model for SKU Indicates that the SKU for which orders are being transferred is not defined properly in the destination Sequencing model. The SKU is not defined as a finished good SKU in the Sequencing model.

11001 Multiple Sequencing model defined for the SKU The SKU is defined as finished good for multiple Sequencing model

11002 SCPO SKU not enabled for integration The SKU:SeqEnableIntSw is not enabled for the SKU

Supply The Validate Input Data process generates the following SKU exceptions:

Exception Number

Exception Text

9000 BOM Number Not Equal to one OR BOM DRAWQTY is <= 0

9001 The Negative Offset of child part is greater than parent parts lead time 9002 SkuSupplyParam.EffCodeSW = 1 and TypeEffectivity Doesn't not contain

Effective Definitions

9003 SkuSupplyParam.MaxQty < SkuSupplyParam.MultQty <= 0

9004 If SkuSupplyParam.ORDPOL = 6, then SkuSuppyParam.ABC should not be null.

9005 MinQty > MaxQty OR Multqty > maxQty OR (maxqty > multqty and multqty>0 and maxqty not a multiple of multqty)

9006 Mismatch of Effectivity defined in BOM, Sourcing and TypeEffectivity

9007 Transfer Part without an sourcing record 9008 Over Lapping Effectivity 9009 Invalid Sourcing Entry 9010 Non Nettable Inventory 9011 Invalid Transfer Order Part 9012 Negative Extra Usage Revenue 9013 Negative Customer Order Revenue 9014 Negative Workorder draw Quantity 9015 Invalid Work Order 9016 SKU Without Production Method 9017 Unmatched SKU Supply Param records 9018 Invalid Substitution Rule 9019 The Purchase Lead Time and Production Lead Time are not multiples of

1440. 9020 The Supply Lead Time of Sourcing is not a multiple of 1440. 9021 The BOM Record does not exist for an Assembled item. 9022 A Phantom SKU has been defined as Subst Item in SubstRule Table.


SKUException

Exception Number

Exception Text

9023 Negative Customer Order quantity 9024 All lead times defined in the SKUSupplyParam table should be less than

2147483647. 9025 The ProductionStep:ProdRate value is less than 1. 9026 Res:CheckMaxCap cannot have a value of 2. It will be treated as

unconstrained (1). 9027 Time Phased Safety Stock demand exists for a Pseudo SKU. 9028 Customer Order demand exists for a Pseudo SKU. 9029 Extra Usage demand exists for a Pseudo SKU. IPO The Optimize Inventory policy process generates the following exceptions::

Exception Number

Exception Text

10001 BOM has an invalid draw quantity

10002 This sourcing causing multiple sourcing for IPOSKU 10003 SKU has an invalid survival rate 10004 SKU is connected to other SKUs with different group names by BOM or

sourcing relationship 10005 SKU corresponding to operational system part has zero quantity per

assembly 10006 SKU corresponding to operational system part has zero mean time

between failure 10007 Parent SKU is not loaded 10008 Subordinate SKU is not loaded 10009 Zero value for economic order quantity (EOQ) 10010 Zero value for mean daily demand 10011 Forward coverage duration as zero 10012 Zero value for quantity per assembly 10013 Zero value for OpsSystem:Usage 10014 Zero value for OpsSystem:UsageInterval 10015 Zero value of OpsSystem:NumInUse 10016 Sourcing does not match 10017 SKU is connected to operational systems with multiple group names 10018 SKU is not connected to any target group in the connected tree 10019 Validation errors were found in the model. Please review the

SKUExceptions table. 10020 SKU is ignored as plan level is -1 10021 Invalid initial stock level for SKU. The stock level should be greater than

or equal to the reorder quantity. The stock level has been adjusted to the reorder quantity for performance evaluation.


SKUException

Exception Number

Exception Text

10022 Invalid initial stock level for SKU. Because the variance of Procurement Problem Variable(PPV) is zero, the stock level should be greater than mean PPV in order to prevent infinite back orders. The stock level has been adjusted to the mean PPV for performance evaluation.

10023 SKU with PurchaseSw = 0 and no sourcing cannot have survival rate less than 100

10024 SKU with PurchaseSw = 0 and no sourcing cannot have carcass return rate less than 100

10025 SKU has an invalid purchase lead time. It cannot be negative. 10026 SKU has an invalid repair lead time. It cannot be negative. 10027 Mean time between failures of operational system part cannot be less

than its mean remove and replace time

10028 Invalid entry for PurchaseSW. If SKU is sourced, it cannot be purchased.

10029 No replenishment method defined for this SKU. Zero cost, zero lead time purchase method is created

10030 Operational system usage cannot be greater than usage period. Override value has been used and will continue processing with that value.

10031 For percentage of uptime, the mean remove and replace time for operational system parts cannot be greater than available working time. Override value has been used and will continue processing with that value.

10032 The mean remove and replace time for operational system corresponding to part cannot be greater than available working time. Override value has been used and will continue processing with that value.

10033 For average part failure rate, operational system mean failure rate should not be more than number in use.

10034 SKU has an invalid purchase lead time standard deviation. It cannot be greater than zero when the purchase lead time is zero.

10035 SKU has an invalid repair lead time standard deviation. It cannot be greater than zero when the repair lead time is zero.

10036 SKU has an invalid trans lead time standard deviation. It cannot be greater than zero when the trans lead time is zero.

10037 SKU had an order quantity less than 1, so it is set to 1.

10038 SKU with PurchaseSw = 1 has purchase fraction = 0 as the sum of sourcing and repair fractions is greater than 1.

10039 This SKU has negative safety stock, so the quantity is published as 0.

10040 The cumulative lead time of the network is greater than the plan bucket duration.

10041 SKU has no BOM. It cannot be repaired. 10068 Validation errors were found in the model. Please review the

SKUException table. 10055 Deficit quantity is assumed to arrive on arrival post date. 10056 Deficit quantity is assumed to arrive on order post date.


SKUException

Exception Number

Exception Text

10057 Surplus arrival quantity is ignored. 10058 Surplus order quantity is ignored.

10059 Missing data in HistTransPlan. 10060 Missing data in HistPurchPlan. 10061 Missing data in HistTransActual. 10062 Missing data in HistPurchActual. 10063 Missing data in HistTransPlan and HistTransActual. 10064 Missing data in HistPurchPlan and HistPurchActual. 10065 Too few planned observations to compute transportation lead time and

transportation lead time standard deviation. 10066 Too few planned observations to compute purchase lead time and

purchase lead time standard deviation. 10067 Too few actual observations to compute transportation lead time and

transportation lead time standard deviation. 10068 Too few actual observations to compute purchase lead time and purchase

lead time standard deviation. 10074 BOM has 100 percentage shrinkage, ignoring shrinkage factor.

10075 BOM has 0 percentage yield, ignoring yield factor.

ExceptionDate The date and time that the exception occurred within the planning horizon. This information can help to identify the cause of the exception and take appropriate action. Exceptions which are not having a specific related date will have the OHPost date for the SKU.

Fulfillment • 7 No sources found for this location

• 13 Location is closed on RecShip:SchedShipDate

• 14 Location is closed on RecShip:SchedArrivDate

• 17 Production is closed

• 23 Sourcing:MajorShipQty less than 1; value 1 used

• 24 RecShip:SchedShipDate moved out

• 27 NeedShipDate at or before OHPost

• 28 SKU:PlanDur < leadtime/timefence

• 29 SKU:MaxOH < safey stock

• 30 SKU with circular Network/BOM

• 38 SKUProjStatic:ProjOH > SKU:MaxOH

• 40 RecShip:SchedArrivDate moved out

• 42 SchedShipDate moved out

• 43 SchedArrivDate moved out

• 45 PlanArriv removed because of SKU:MaxOH


SKUException

• 51 Shortage exists within horizon and is not met



• 55 DRPCovDur has been adjusted

• 56 Unable to meet shelf life requirements

• 57 MPSCovDur has been adjusted

• 58 Unusable firm inventory found

• 59 Expired inventory found

• 62 Quantity reduced to avoid waste

• 70 Shortage is met with later shipment

• 71 Surplus at alternate location with no sourcing

• 73 Demand outside the ProdStopDate

• 74 Demands at or after expiration date ignored

• 76 Unusable quantity in planned replenishment

• 77 Unable to meet demand expiration date, demand ignored

• 80 Unable to meet dmd expDate, dmd met anyway

• 83 No effective sourcing found for alternate SKU

• 84 Invalid BOM relation:BOM Overlap found

• 102 Supplemental Order Created for an invalid SKU TYPE

• 103 Supplemental Order: ReleaseStartDate is before NeedArrivDate

• 104 Supplemental Order Partially Late or Unmet, Needed prior to FirstReplenDate

• 105 Active Supplemental Order falls within the coverage duration for SKU

• 107 MaxCovDur constraint violation

• 300 Alternate TransMode used

• 302 Splitting RecShip resulted in a new RecShip with quantity less than the Sourcing:SplitQty

• 303 Unable to find a conversion to a constraint UOM category

• 304 Invalid multi-pickup load. Check for inconsistent VehicleLoad:ShipDate or ArrivDate.

• 305 Maximum limit on the VehicleLoads has reached, skipping the lane for BTL run. All RecShips in this lane are affected.

• 5009 Excess Inventory of Subordinate SKU

• 5021 Insufficient inventory to meet firm demands

• 5022 Unable to meet firm demands on time

FunctionName The name of the function that detected this exception.

FunctionNum The number that identifies the function that detected this exception.

Item The item associated with the SKU whose exception is identified in this row. Must be a valid item in the Item table.


SKUException

LastUpdatedBy Records the user who has last updated the status of the exception, using the Exception Navigator workbench.

LastUpdatedOn Records when the status of the exception was last updated, using the Exception Navigator workbench.

LevelNum Note: This column is not used in this release.

Loc The location associated with this SKU. Must be a valid location in the Loc table.

Offset The Offset column is used to calculate the need date of an exploded part when a Planned Supply Order is exploded. The exploded part need date is defined as the Planned Supply Order’s start date, minus the Offset value. The default value for the offset is 0, which means the exploded part is needed at the start of the Planned Supply Order production step. If the offset value positive, the component is needed early. If it is negative, the component is not needed until after the start of production. This allows us to stagger the entry of inputs to an assembly operation.

ParentItem The item associated with the parent SKU. Must be a valid item in the Item table.

ParentLoc The location associated with the parent SKU. Must be a valid location in the Loc table.

ProcessID The identifier associated with the process in which the exception was raised.

ProductionMethod The production method associated with the SKU that has raised this exception.

PurchMethod The purchase method associated with the SKU that has raised this exception.

ReviewedStatus The review status of the exception record.

SeqNum The unique number associated with this exception record. This number is used if multiple exceptions are written.

Master Planning and Supply

This column also links the exception record to its corresponding record in the ExceptionOrderRel table (SKUException:SeqNum = ExceptionOrderRelation:ExceptionSeqNum).

Severity Indicates the severity level of an exception, based on how the constraint has impacted. Currently, there are three levels of defining severity: ‘Critical’, ‘Warning’ and ‘Informational’. Severity is populated by the Master Planning process in the SKU and RES exception tables with business rules defined by the planner in the exceptionseverity table. Different rules are defined considering the three parameters: Schestatus of demand, supply method option, and type of demand. Different combinations of these parameters are available to you by default with the flexibility of redefining the severity using Flexible Editor.

Sourcing The sourcing method associated with this exception.


SKUException

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

When While running a process, this column is updated with the system date when the exception is generated.


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 Dynamic Demand Response Reference Guide 190 © 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 Dynamic Demand Response Reference Guide 197 © 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



Index 1 1 = None • 137

2 2 = Customer orders • 138

3 3 = Maximum, follow customer order curve • 138

4 4 = Maximum, reallocate unmet forecast • 139

5 5 = Carry backward • 141

6 6 = Short term customer orders • 142

7 7 = Short term customer orders and forecast • 142

8 8 = Dynamic Demand Response (DDR) Integration • 143

A AdjDmdPostDate • 52 AggCal • 37, 40 Algorithm • 119 AllocCal • 93, 133 AllocCalGroup • 93, 135 AllocCalProfile • 11, 93 AllocCalProfileData • 12 AllocCalProfileName • 11, 12 AllocFactor • 88 AllocPolicy • 108 AllocWgt • 19 AltCal • 20 AltPlantID • 115 Applications that include the table • 4 Applications that use the columns • 5 AttachRateRelationType • 94 Avail • 22

B BaseProrateOpt • 43

BatchNum • 150 BOMNum • 150 Boolean • 7 BorrowingPct • 115 Brand • 97

C Cal • 13, 22 CalcCumLeadTimeSw • 108 CalcPartialOrderQty • 38, 40 CalcPriority • 28 CalcPromoOrderQty • 38, 41 CalculateDmdToDateSw • 94 CalData • 18 CalStartDate • 12 Category • 150 CCPSw • 135 Collection • 97 Column descriptions • 11, 12, 13, 19, 28, 37, 40, 43, 52, 63,

88, 91, 93, 96, 97, 101, 104, 106, 108, 115, 119, 122, 133, 150

CompanyID • 115 ConsumptionRule • 44 ConsumptionType • 44 ConvFactor • 88 CopyDate • 52 CopyFromDmdGroup • 53 CopyFromDmdUnit • 53 CopyFromLoc • 53 CopyFromModel • 53 Cost • 28 Country • 115 CovDur • 22 CreationDate • 122 Currency • 115 CurrencyUOM • 122 Cust • 28, 115 CustOrder • 26 CustOrderDur • 136 CustOrderHist • 35 CustOrderPriority • 136 CustOrderStat • 37 CustOrderStatHist • 40

D Database conventions • 4 Database information • 1 Datatype • 6 Date and DateTime • 7



DCRank • 53 DDRGroup • 38, 41, 94 DDRParamProfile • 43 DDRParamProfileName • 45, 94 DDSKUSw • 108 DDSrcCostSw • 108 Decimal • 7 Default values • 8 DefaultUOM • 109 DemandQty • 150 Descr • 11, 13, 22, 63, 96, 98, 106, 109, 115, 120, 150 DestCal • 116 DFU • 48 DFUException • 62 DFULoc • 28, 35, 88, 91 DFUToSKU • 87 DFUToSKUFcst • 90 DFUView • 92 Disc • 53, 88 DmdCal • 54 DmdGroup • 28, 35, 38, 41, 54, 63, 88, 91, 94, 96, 101, 104 DmdPostDate • 54 DmdRedID • 136 DmdToDate • 137 DmdToDateBase • 94 DmdToDateNonBase • 94 DmdU nit • 38, 41 DmdUnit • 28, 35, 54, 63, 88, 91, 94, 97, 98, 101, 104 Documentation information • 1 Dur • 91, 101, 104 Duration • 8 DynDepDecimals • 109 DynDepOption • 109 DynDepPushOpt • 109 DynDepQty • 111

E E3Error • 54 E3ErrorDate • 54 Eff • 22, 55, 88, 150 EnableSw • 111, 116, 122 Event • 104 Exception • 63, 150 ExceptionDate • 176

F Fcst • 100 Fcst Type • 35

FcstAdjRule • 137 FcstConsumptionRule • 144 FcstHor • 55 FcstID • 101 FcstMeetEarlyDur • 144 FcstMeetLateDur • 144 FcstPeriodRestriction • 45 FcstPrimConsDur • 144 FcstPriority • 145 FcstSecConsDur • 145 FcstSw • 28, 35 FcstType • 29, 88 FirmSw • 29 FrzStart • 116 FunctionName • 85, 177 FunctionNum • 85, 177

G Get additional help from JDA • 2

H HeaderExtRef • 29 Help information • 1 Hist • 104 HistStart • 55 HistStream • 105, 106, 120 HistType • 89 HwModelSw • 55

I IgnorePricingLvlSw • 98 Image • 95 Implementing Rule 6 • 143 Include_In_SLCCurve • 55 IncrConsDur • 45 IndDmdUnitCost • 145 IndDmdUnitMargin • 145 InfCarryFwdSw • 122 InfiniteSupplySw • 124 Information about columns • 5 Information about tables • 4 InitE3Error • 55 InitE3ErrorDate • 55 Installation/administration information • 1 Integer • 7 InvOptimizerType • 111 Item • 29, 36, 89, 91, 107, 111, 124, 145, 177 ItemClass • 111



ItemStoreGrade • 124

L LastUpdatedBy • 178 LastUpdatedOn • 178 Lat • 116 Legal notice • i LevelNum • 178 LewMeanQty • 102 LineItemExtRef • 29 LLOverride • 94 Loc • 30, 36, 38, 41, 55, 85, 94, 102, 105, 114, 116, 124,

145, 178 Loc_Type • 116 LockDur • 55 LogScale • 95 LogScaleSw • 38, 41 Lon • 117 LTDGroup • 124

M MapUsed • 55 Margin • 30 MarketMgrVersionID • 102 Mask • 55 Master • 13 MasterCal • 95, 145 MasterCalRule • 95 Max • 38, 41 MaxCustOrderSysDur • 146 MaxEarlyConsDurBase • 46 MaxEarlyConsDurNonBase • 46 MaxEarlyDur • 30 MaxHist • 56 MaxLateDur • 30 MaxLaterConsDurBase • 46 MaxLaterConsDurNonBase • 46 Mean • 38, 41 Median • 38, 41 Min • 38, 41 MinOHCovRule • 124 MinShelfLifeDur • 31 Model • 56, 86, 89, 102, 119, 120 ModelDate • 56 MPBatchNum • 126 MSEHistDur • 56

N NegFcstSw • 56 NetChgSw • 126 NetFcstError • 56 NetFcstMSE • 56 NetFcstMSESmConst • 56 NewDFUSw • 56 NonBaseProrateOpt • 46 NonBaseProrationPeriod • 46 NPIFromDmdPostDate • 56 NPIFromMSE • 57 NPIIndDate • 57 NPIMeanSmooth • 57 NPIScalingFactor • 57 NPISw • 57 NPITransDur • 127 NPITrendSmooth • 57 NumFcstPer • 14 NumYears • 57

O ObsEndDate • 12 ObsoleteFlag • 57 ObsStartDate • 12 Offset • 178 OH • 127 OHPost • 117, 127 OnOrderQty • 98 Opt • 22 Option_Number and Option_Text • 7 OrderID • 31, 36 OrderLeadTime • 46 OrderLineItem • 31 OrderSeqNum • 31 OrderType • 31 OutlierOpt • 57 OverrideFcstTypeSw • 31, 36

P PackSize • 98 Parent/Child tables and columns (foreign keys) • 5 ParentItem • 178 ParentLoc • 178 Paths between tables • 9 PatternSw • 14 PeggingSw • 129 PerishableSw • 111 PerWgt • 23



PickBestDate • 57 PickBestSw • 58 PlanLevel • 112, 129 PostalCode • 117 Predefined pages • 4 PriceCal • 146 PriceLink • 98 PriceProfileName • 95 PriItemPriority • 112 Primary key columns • 5 Primary key columns in the table • 4 PrimaryDFUSw • 95 Priority • 31, 112 PrioritySeqNum • 32 ProcessID • 178 ProductionMethod • 178 Project • 32 ProrateByTypeSw • 146 ProrateSw • 146 ProrationDur • 146 Provide feedback on this document • i PublishDate • 58 PurchMethod • 178

Q Qty • 32, 36, 102, 105 QtyUOM • 129

R RefitDate • 58 Release Notes • 1 Repeat • 24 ReplenMethod • 129 ReplenType • 129 Reservation • 32 ResExp • 33 RestrictPlanMode • 112 Revenue • 33 ReviewedStatus • 178 RollingSw • 14 RPBatchNum • 130 RunCalcModelSw • 58

S SeasonErrorLag • 59 SeasonProfile • 59 SEOutlierFactor • 59 SEOutlierOpt • 59

SeqIntEnableSw • 130 SeqIntExportDur • 117 SeqIntImportDur • 117 SeqIntLastExportedToSeq • 118 SeqIntLastImportedFromSeq • 118 SeqNum • 178 Sequence • 8 Severity • 178 ShipDate • 33, 36 ShipSw • 33 SKU • 121 SKUDemandParam • 132 SKUException • 148 SKUGroup • 130 SKULoc • 89, 91 SourceCal • 118 Sourcing • 178 SourcingGroup • 130 StartDate • 38, 41, 91, 102, 105 StatCalcDate • 39, 42 StaticCFDescr • 59 StaticCFValue • 59 StatMSE • 59 Status • 33 StdDev • 39, 42 StorableSw • 130 StorageGroup • 112 StoreFittedHistOpt • 59 SubstLevel • 34 SubstOperator • 34 SupersedeSw • 34, 89, 91 SupsnGroupNum • 113 SymmetricMAPE • 60

T Table description • 12, 13, 18, 27, 37, 40, 43, 52, 62, 87, 90,

93, 96, 97, 101, 104, 106, 108, 115, 119, 122, 133, 149 Table Description • 11, 35 Table Relationships • 180 Tables in the database (technical documentation) • 10 TargetEarlyDur • 34, 146 TargetOHCovRule • 130 Text and Upper_Text • 6 The SCPO database (technical documentation) • 4 TimeUOM • 131 TotFcst • 91 TotFcstLock • 61 TotHistPeriods • 39, 42



TotPosHistPer iods • 39, 42 Type • 14, 91, 102, 105 Type3 • 118

U ULOverride • 95 UnitCarCost • 146 UnitPrice • 34, 146 UnitSize • 98 UnitsPerAltShip • 113 UnitsPerPallet • 113 UOM • 98, 113 URL • 8 UseMultipleYearsHistSw • 12 UserID • 86, 179

V Valid values • 8 VendID • 118 Vol • 113

W WDDArea • 118 WeeklyAvgHist • 147 Wgt • 113 When • 86, 179 WorkingCal • 118 WorkScope • 34


Documents

ddr_ref_guide.pdf