esp_ref_guide.pdf

Reference Guide JDA® Enterprise Supply Planning Release 8.1.0.0

JDA Software Group, Inc.

Legal notice Rights to the content of this document

Copyright © 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 AggSKUProjStatic ............................................................................................ 11 AltBOM .......................................................................................................... 46 AltProductionStep ........................................................................................... 49 AvgDmd ........................................................................................................ 52 BOM .............................................................................................................. 54 Cal ................................................................................................................ 62 CalAttribute ................................................................................................... 67 CalData ......................................................................................................... 68 CalInterval ..................................................................................................... 76 CalPattern ...................................................................................................... 78 Cust .............................................................................................................. 81 CustOrder ...................................................................................................... 82 CustOrderHeader ............................................................................................ 91 CustOrderStatus ............................................................................................. 95 DepDmdStatic ................................................................................................ 98 DFU ............................................................................................................ 103 DFUToSKU ................................................................................................... 117 DFUToSKUFcst .............................................................................................. 120 DFUToSKUSeasonErr ..................................................................................... 122 DmdVar ....................................................................................................... 124 ExceptionCategoryAssoc ................................................................................ 125 ExceptionOrderRelation .................................................................................. 128 ExceptionSeverity ......................................................................................... 134 Fcst ............................................................................................................ 136 FcstOrder ..................................................................................................... 140 FcstOrderStatus ............................................................................................ 145 ImpDepDmdStatic ......................................................................................... 148 ImpResLoadDetail ......................................................................................... 150 IndDmdLink ................................................................................................. 152 IndDmdView ................................................................................................ 157 Inventory .................................................................................................... 161


Item ........................................................................................................... 164 Loc ............................................................................................................. 171 LPDmdBands ................................................................................................ 176 LPLayer ....................................................................................................... 177 MSE ............................................................................................................ 178 Network ...................................................................................................... 180 OrderLink .................................................................................................... 191 PlanArriv ...................................................................................................... 196 PlanOrder .................................................................................................... 204 PlanProxyInventory ....................................................................................... 211 PlanPurch .................................................................................................... 213 ProductionMethod ......................................................................................... 217 ProductionStep ............................................................................................. 229 ProductionYield ............................................................................................. 237 PurchMethod ................................................................................................ 239 PurchOrder .................................................................................................. 243 Res ............................................................................................................. 247 ResException ................................................................................................ 254 ResLoadDetail .............................................................................................. 264 ResProjStatic ................................................................................................ 270 SchedRcpts .................................................................................................. 278 SchedRcptsDetail .......................................................................................... 283 SeasonError ................................................................................................. 285 SKU ............................................................................................................ 287 SKUDemandParam ........................................................................................ 298 SKUEffInventoryParam .................................................................................. 314 SKUException ............................................................................................... 316 SKUExternalFcst ........................................................................................... 348 SKUHist ....................................................................................................... 351 SKUHistFcst ................................................................................................. 353 SKUPerishableParam ..................................................................................... 355 SKUPlanningParam ........................................................................................ 359 SKUProjStatic ............................................................................................... 379 SKUSafetyStockParam ................................................................................... 427 SKUStatStatic ............................................................................................... 440 Sourcing ...................................................................................................... 451 SourcingRequirement .................................................................................... 463 SS .............................................................................................................. 466 SSBand ....................................................................................................... 468 SSTemplate ................................................................................................. 470 SSTemplateData ........................................................................................... 471 StatSS ........................................................................................................ 474 StockOrder .................................................................................................. 475 StockOrderStatus .......................................................................................... 478 StorageRequirement ...................................................................................... 481 Supersession ................................................................................................ 482 TimeHorizon ................................................................................................. 486 TransMode ................................................................................................... 488 VehicleLoad .................................................................................................. 490 VehicleLoadLine ............................................................................................ 496 Table Relationships ....................................................................................... 501

Chapter 4. Process: input and output tables ................................................................ 581

Index ........................................................................................................................... 588

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 Enterprise Supply Planning Reference Guide 1 © 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 501).

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


AggSKUProjStatic

AggSKUProjStatic Table included with: Fulfillment, Master Planning, Supply, Flowcasting, Enterprise Supply Planning

Column name PK Included with

Datatype Valid values

Default value

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

DECIMAL 0

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

DECIMAL 0

AdjAllocAggMktActvtyFcst

FF, Flowcasting

DECIMAL 0

AdjAllocAutoFcst FF, Flowcasting

DECIMAL 0

AdjAllocBaseFcst FF, Flowcasting

DECIMAL 0

AdjAllocDataDrvnFcst FF, Flowcasting

DECIMAL 0

AdjAllocMktActvtyFcst FF, Flowcasting

DECIMAL 0

AdjAllocNonBaseFcst FF, Flowcasting

DECIMAL 0

AdjAllocOvrideFcst FF, Flowcasting

DECIMAL 0

AdjAllocReconcileFcst FF, Flowcasting

DECIMAL 0

AdjAllocTargtImpactFcst

FF, Flowcasting

DECIMAL 0

AdjAllocTotalLockFcst FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

AggMktActvtyCustOrders

FF, Flowcasting

DECIMAL 0

AggMktActvtyFcst FF, Flowcasting

DECIMAL 0

AggValue 1 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT


AggSKUProjStatic



Default value

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

DECIMAL 0

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

DECIMAL 0

AllocAggMktActvtyFcst FF, Flowcasting

DECIMAL 0

AllocAutoFcst FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

AllocDataDrvnFcst FF, Flowcasting

DECIMAL 0

AllocMktActvtyFcst FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

AllocOvrideFcst FF, Flowcasting

DECIMAL 0

AllocReconcileFcst FF, Flowcasting

DECIMAL 0

AllocTargtImpactFcst FF, Flowcasting

DECIMAL 0

AllocTotalLockFcst FF, Flowcasting

DECIMAL 0

AllocTotFcst FF, MP, Flowcasting

DECIMAL 0

AltConstrCovDur FF DURATION

AltConstrainedUnuseOH

FF, MP, Flowcasting, ESP (Deep Tree)

DECIMAL 0

AltConstrPOH FF, Flowcasting

DECIMAL 0

AltSubConstProjOH FF, Flowcasting

DECIMAL 0.0

AltSupsdConstrProjOH FF, Flowcasting

DECIMAL 0

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

DECIMAL 0


AggSKUProjStatic



Default value

AutoCustOrders FF, Flowcasting

DECIMAL 0

AutoFcst FF, Flowcasting

DECIMAL 0

AvailShipOH FF, Flowcasting

DECIMAL 0

AvgCycleStock FF, Flowcasting

DECIMAL 0

AvgIntransitStock FF, Flowcasting

DECIMAL 0

BaseCustOrders FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

CBMPAdjFcstOrd Not used in this release

DECIMAL 0

CBMPBuyOrd Not used in this release

DECIMAL 0

CBMPConstProjAvail Not used in this release

DECIMAL 0

CBMPDepDmd Not used in this release

DECIMAL 0

CBMPIndependentDmd Not used in this release

DECIMAL 0

CBMPMakeOrd Not used in this release

DECIMAL 0

CBMPMetAdjFcstCo Not used in this release

DECIMAL 0

CBMPMetAdjFcstOrd Not used in this release

DECIMAL 0

CBMPMetIndDmd Not used in this release

DECIMAL 0

CBMPMetNonFCo Not used in this release

DECIMAL 0

CBMPMoveOrd Not used in this release

DECIMAL 0

CBMPOHInventory Not used in this release

DECIMAL 0

CBMPProjAvail Not used in this release

DECIMAL 0

CBMPProjOH Not used in this release

DECIMAL 0


AggSKUProjStatic



Default value

CBMPSafetyStockOrd Not used in this release

DECIMAL 0

CBMPSSInventory Not used in this release

DECIMAL 0

CBMPSSLevel Not used in this release

DECIMAL 0

CBMPTotDmd Not used in this release

DECIMAL 0

CBMPTotSupply Not used in this release

DECIMAL 0

CMPFirmDepDmd FF, Flowcasting

DECIMAL 0

CMPFirmPlanArriv FF, Flowcasting

DECIMAL 0

CMPFirmPlanOrd FF, Flowcasting

DECIMAL 0

CMPFirmPlanShip FF, Flowcasting

DECIMAL 0

COMetEarlyCount FF, MP, ESP (Deep Tree)

INTEGER 0

COMetLateCount FF, MP, ESP (Deep Tree)

INTEGER 0

CoMetOnTimeCount FF, MP, ESP (Deep Tree)

INTEGER 0

COMetPartialCount FF, MP, ESP (Deep Tree)

INTEGER 0

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

DECIMAL 0

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

DECIMAL 0

ConCancel Supp DECIMAL 0 ConCustOrder Supp DECIMAL 0 CONeedUnit Supp INTEGER 0 ConExtraUsage Supp DECIMAL 0 ConIntersiteOrder Supp DECIMAL 0 ConInventory Supp DECIMAL 0 ConMasterSched Supp DECIMAL 0 ConNew Supp DECIMAL 0 ConNoAction Supp DECIMAL 0 ConPull Supp DECIMAL 0

ConPurchaseOrder Supp DECIMAL 0 ConPurchaseReq Supp DECIMAL 0


AggSKUProjStatic



Default value

ConPush Supp DECIMAL 0 ConReschedSupply Supp DECIMAL 0 ConSafetyStock Supp DECIMAL 0 ConSchedSupply Supp DECIMAL 0 ConShCustOrder Supp DECIMAL 0 ConShExtraUsage Supp DECIMAL 0 ConShMasterSched Supp DECIMAL 0 ConShortage Supp DECIMAL 0 ConShSafetyStock Supp DECIMAL 0 ConsolidatedPlanShip FF,

Flowcasting DECIMAL

ConstrCovDur FF, Flowcasting

DURATION 0

ConstrExpOH FF, Flowcasting

DECIMAL 0

ConstrNetReqts FF, Flowcasting

DECIMAL 0

ConstrProjAvail FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

ConstrProxyDemand FF, Flowcasting

DECIMAL 0

ConstrProxySupply FF, Flowcasting

DECIMAL 0

ConstrSchedExpOH FF, Flowcasting

DECIMAL 0

ConstrSchedUnuseOH FF, Flowcasting

DECIMAL 0

ConstrUnuseOH FF, Flowcasting

DECIMAL 0

ConSubstSupply Supp DECIMAL 0 ConTotalDemand Supp DECIMAL 0 ConWorkOrder Supp DECIMAL 0 COProjMargin FF, MP,

Flowcasting, ESP (Deep Tree)

INTEGER 0

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

INTEGER 0


AggSKUProjStatic



Default value

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

COUnmetCount MP, ESP (Deep Tree)

INTEGER 0

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

INTEGER 0

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

DURATION 0

DataDrvnCustOrders FF, Flowcasting

DECIMAL 0

DataDrvnFcst FF, Flowcasting

DECIMAL 0

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

INTEGER 0

DemandSKUExcepCount

FF, MP, ESP (Deep Tree)

INTEGER 0

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

DECIMAL 0

DepDmdEarliestNeed MP, Flowcasting, ESP (Deep Tree)

DATETIME 01/01/1970

DetailedPlanShip FF, Flowcasting

DECIMAL

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

DECIMAL 0

DisplayQty FF, Flowcasting

DECIMAL 0


AggSKUProjStatic



Default value

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

DURATION 0

ExpOH FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

FirmProxyInventory FF, Flowcasting

DECIMAL 0

FirmSchedRcpts MP, ESP (Deep Tree)

DECIMAL 0

FirmSubinventory FF, Flowcasting

DECIMAL 0

FirmSupplyCovDur FF, Flowcasting

DURATION 0

FirmSupplyProjOH FF, Flowcasting

DECIMAL 0

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0


AggSKUProjStatic



Default value

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

ForcedSuppOrderQty FF, Flowcasting

DECIMAL

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

HoldOutQty FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

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

DURATION 0

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

DURATION 0

IndDmd MP INTEGER 0


AggSKUProjStatic



Default value

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

INTEGER 0

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

INTEGER 0

InvCarCost FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

MetIndDmd MP, ESP (Deep Tree)

INTEGER 0

MetSSLevel MP, ESP (Deep Tree)

INTEGER 0

MktActvtyCustOrders FF, Flowcasting

DECIMAL 0

MktActvtyFcst FF, Flowcasting

DECIMAL 0

MPConstProjAvail MP, ESP (Deep Tree)

INTEGER 0

NetProfit FF, Flowcasting

DECIMAL 0

NetReqts FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

NonBaseHist MP, ESP (Deep Tree)

DECIMAL 0

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

DECIMAL 0

NonSupsdAdjAllocTotalFcst


DECIMAL 0

NonSupsdAdjFcstCustOrders


DECIMAL 0

NonSupsdAllocBaseFcst FF, Flowcasting

DECIMAL 0

NonSupsdAllocNonBaseFcst

FF, Flowcasting

DECIMAL 0


AggSKUProjStatic



Default value

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

DECIMAL 0

NonSupsdBaseFcst FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

NonSupsdDFUToSKUFcst


DECIMAL 0

NonSupsdFcstCustOrders


DECIMAL 0

NonSupsdFirmPlanArriv FF, Flowcasting

DECIMAL 0

NonSupsdFirmPlanOrder

FF, Flowcasting

DECIMAL 0

NonSupsdFirmPlanShip FF, Flowcasting

DECIMAL 0

NonSupsdNonBaseFcst FF, Flowcasting

DECIMAL 0

NonSupsdNonFcstCustOrders


DECIMAL 0

NonSupsdPlanArriv FF, Flowcasting

DECIMAL 0

NonSupsdPlanOrders FF, Flowcasting

DECIMAL 0

NonSupsdPlanShip FF, Flowcasting

DECIMAL 0

NonSupsdRecArriv FF, Flowcasting

DECIMAL 0

NonSupsdRecShip FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

OptionSet 3 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT ' '

OvrideCustOrders FF, Flowcasting

DECIMAL 0


AggSKUProjStatic



Default value

OvrideFcst FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

PlanIntransIn FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

PlanProjAvail FF, Flowcasting

DECIMAL 0

PlanProjOH FF, Flowcasting

DECIMAL 0

PlanPurch MP, ESP (Deep Tree)

INTEGER 0

PlanPurchFirm MP, ESP (Deep Tree)

INTEGER 0

PlanShip FF, MP, Flowcasting

DECIMAL 0

PresentationQty FF, Flowcasting

DECIMAL 0

ProcessDate FF, Flowcasting

DATETIME 01/01/1970

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

DECIMAL 0

ProjAvailEarliestNeed MP, Flowcasting

DATETIME 01/01/1970

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

DECIMAL 0

ProjOHEarliestNeed MP, Flowcasting, ESP (Deep Tree)

DATETIME 01/01/1970

ProjOrderOptTotDmd FF DECIMAL 0

ProjOrderOptIntransOut

FF DECImal 0

ProjOrderOptSOQ FF DECIMAL 0 ProjOrderOptIntransIn FF DECIMAL 0 ProjOrderOptTotSupply FF DECIMAL 0 ProjOrderOptProjOH FF DECIMAL 0 ProjOrderOptProjAvail FF DECIMAL 0


AggSKUProjStatic



Default value

ProAllocBaseFcst FF DECIMAL ProratedAllocTotFcst FF, MP,


DECIMAL 0

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

DECIMAL 0

ProxyIntransIn FF, Flowcasting

DECIMAL 0

ProxyIntransOut FF, Flowcasting

DECIMAL 0

ProxyInventory FF, Flowcasting

DECIMAL 0

ProxyRecArriv FF, Flowcasting

DECIMAL 0

ProxyRecShip FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

PSOLoad Supp DECIMAL 0.0 PurchOrder MP, ESP

(Deep Tree) INTEGER 0

RecAllocArriv FF FLOAT 0 RecAllocShip FF FLOAT 0 RecArriv FF,

Flowcasting DECIMAL 0

ReconcileCustOrders FF, Flowcasting

DECIMAL 0

ReconcileFcst FF, Flowcasting

DECIMAL 0

RecShip FF, Flowcasting

DECIMAL 0

SchedExpOH FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

SchedSupplyExceptionCount


INTEGER 0


AggSKUProjStatic



Default value

SchedSupplyExceptionQty


INTEGER 0

SchedUnuseOH FF, Flowcasting

DECIMAL 0

SeasonFactor FF, Flowcasting

DECIMAL 0

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

INTEGER 0

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

INTEGER 0

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

DECIMAL 0

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

INTEGER 0

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

INTEGER 0

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

TEXT ' '

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

DECIMAL 0

SSInventory MP, ESP (Deep Tree)

INTEGER 0

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0


AggSKUProjStatic



Default value

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

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

INTEGER 0

StandardCost FF, Flowcasting

DECIMAL 0

StartDate 2 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

DATETIME

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

DECIMAL 0

StockLowCost FF, Flowcasting

DECIMAL 0

StockOutCost FF, Flowcasting

DECIMAL 0

SubConstrProjAvail FF, Flowcasting

DECIMAL 0

SubConstrProjOH FF, Flowcasting

DECIMAL 0

SubIntransIn FF, Flowcasting

DECIMAL 0

Subinventory FF, Flowcasting

DECIMAL 0

SubRecArriv FF, Flowcasting

DECIMAL 0

SubRecShip FF, Flowcasting

DECIMAL 0

SuppOrderQty FF, Flowcasting

DECIMAL 0


AggSKUProjStatic



Default value

SupsdAdjAllocTotalFcst FF, MP, Flowcasting

DECIMAL 0

SupsdAdjFcstCustOrders


DECIMAL 0

SupsdAllocBaseFcst FF, Flowcasting

DECIMAL 0

SupsdAllocNonBaseFcst FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

SupsdBaseFcst FF, Flowcasting

DECIMAL 0

SupsdConstrProjOH FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

SupsdFirmPlanArriv FF, Flowcasting

DECIMAL 0

SupsdFirmPlanOrder FF, Flowcasting

DECIMAL 0

SupsdFirmPlanShip FF, Flowcasting

DECIMAL 0

SupsdNonBaseFcst FF, Flowcasting

DECIMAL 0

SupsdNonFcstCustOrders


DECIMAL 0

SupsdPlanArriv FF, Flowcasting

DECIMAL 0

SupsdPlanOrders FF, Flowcasting

DECIMAL 0

SupsdPlanShip FF, Flowcasting

DECIMAL 0


AggSKUProjStatic



Default value

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

DECIMAL 0

SupsdProjOH FF, MP, ESP (Deep Tree)

DECIMAL 0

SupsdRecArriv FF, Flowcasting

DECIMAL 0

SupsdRecShip FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

TargetNetworkInv FF, Flowcasting

FLOAT 0

TargtImpactBaseFcst FF, Flowcasting

DECIMAL 0

TargtImpactCustOrders FF, Flowcasting

DECIMAL 0

TotalCost FF, Flowcasting

DECIMAL 0

TotalLoad Supp DECIMAL 0.0 TotalLockCustOrders FF,


TotalLockFcst FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

TotContribMargin FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

TotDmdSatisfied FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

TotHist MP, ESP (Deep Tree)

DECIMAL 0

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

DECIMAL 0


AggSKUProjStatic



Default value

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

DECIMAL 0

TotRecArriv FF, Flowcasting

DECIMAL 0

TotRecShip FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

TotTransCost FF, Flowcasting

DECIMAL 0

TotUseRecArriv FF, Flowcasting

DECIMAL 0

TotUseRecShip FF, Flowcasting

DECIMAL 0

UnconActualReq Supp DECIMAL 0 UnconCancel Supp DECIMAL 0 UnconCustOrder Supp DECIMAL 0 UnconDependantDmd Supp DECIMAL 0 UnconExtraUsage Supp DECIMAL 0 UnconIntersiteDmd Supp DECIMAL 0 UnConIntersiteOrder Supp DECIMAL 0 UnconInventory Supp DECIMAL 0 UnconMasterSched Supp DECIMAL 0 UnconNetAvailable Supp DECIMAL 0 UnconNetDaysSupply Supp DECIMAL 0 UnconNetOnHand FF,


UnconNew Supp DECIMAL 0 UnconNoAction Supp DECIMAL 0 UnconPlannedOrder Supp DECIMAL 0 UnconPrjDaysSupply Supp DECIMAL 0 UnconProjAvailable Supp DECIMAL 0 UnconProjOnHand FF,


UnconPull Supp DECIMAL 0 UnconPurchaseOrder Supp DECIMAL 0 UnconPurchaseReq Supp DECIMAL 0 UnconPush Supp DECIMAL 0 JDA Enterprise Supply Planning Reference Guide 27 © 2014 JDA Software Group, Inc.- Confidential

AggSKUProjStatic



Default value

UnconReschedInFrom Supp DECIMAL 0 UnconReschedOutFrom Supp DECIMAL 0

UnconReschedSupply Supp DECIMAL 0

UnconSafetyStock Supp DECIMAL 0 UnconSubstDmd Supp DECIMAL 0 UnconSubstSupply Supp DECIMAL 0 UnConTotalDemand Supp DECIMAL 0 UnconTotalSupply Supp DECIMAL 0 UnconTVSS FF,


UnconWorkOrder Supp DECIMAL 0 UnuseOH FF, MP,


DECIMAL 0

UserFirmDepDmd FF, Flowcasting

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

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

DECIMAL 0

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

TEXT ' '

WOLoad Supp DECIMAL 0.0

Table description The aggregate value for a column is equal to the sum of the individual values for each included SKU unless otherwise indicated. This table contains the same columns that the SKUProjStatic table contains, with the following exceptions:

• Contains the AggValue column which stores the value by which the aggregation of SKU projections is processed.

• Does not contain the Item or Loc column, because the aggregated projections stored in this table are derived from multiple SKU projections.


AggSKUProjStatic

Note: Since the AggSKUProjStatic table stores static data, you must run the Store SKU Projections process with the Aggregation Column Name option selected to recalculate data after any changes.

When you rerun the Store SKU Projections process with aggregation for a specific option set (see the OptionSet column), the rows for that option set is replaced.

Column descriptions ActualIntransIn See SKUProjStatic:ActualIntransIn (on page 393).

ActualIntransOut See SKUProjStatic:ActualIntransOut (on page 394).

AdjAllocAggMktActvtyFcst See SKUProjStatic:AdjAllocAggMktActvtyFcst (on page 394).

AdjAllocAutoFcst See SKUProjStatic:AdjAllocAutoFcst (on page 394).

AdjAllocBaseFcst See SKUProjStatic:AdjAllocBaseFcst (on page 394).

AdjAllocDataDrvnFcst See SKUProjStatic:AdjAllocDataDrvnFcst (on page 394).

AdjAllocMktActvtyFcst See SKUProjStatic:AdjAllocMktActvtyFcst (on page 394).

AdjAllocNonBaseFcst See SKUProjStatic:AdjAllocNonBaseFcst (on page 394).

AdjAllocOvrideFcst See SKUProjStatic:AdjAllocOvrideFcst (on page 394).

AdjAllocReconcileFcst See SKUProjStatic:AdjAllocReconcileFcst (on page 394).

AdjAllocTargtImpactFcst See SKUProjStatic:AdjAllocTargtlmpactFcst (on page 394).

AdjAllocTotalLockFcst See SKUProjStatic:AdjAllocTotalLockFcst (on page 394).

AdjAllocTotFcst See SKUProjStatic:AdjAllocTotFcst (on page 395).

AdjFcstCustOrders See SKUProjStatic:AdjFcstCustOrders (on page 395).

AggMktActvtyCustOrders See SKUProjStatic:AggMktActvtyCustOrders (on page 395).

AggMktActvtyFcst See SKUProjStatic:AggMktActvtyFcst (on page 395).

AggValue Aggregation Value (AggValue) stores the value by which the aggregation of SKU projections is processed. This value is based upon the column selected for aggregation in the Store SKU Projections process options. JDA Enterprise Supply Planning Reference Guide 29 © 2014 JDA Software Group, Inc.- Confidential

AggSKUProjStatic

AllDmd See SKUProjStatic:AllDmd (on page 395).

AllIntransIn See SKUProjStatic:AllIntransIn (on page 395).

AllocAggMktActvtyFcst See SKUProjStatic:AllocAggMktActvtyFcst (on page 395).

AllocAutoFcst See SKUProjStatic:AllocAutoFcst (on page 396).

AllocBaseFcst See SKUProjStatic:AllocBaseFcst (on page 396).

AllocDataDrvnFcst See SKUProjStatic:AllocDataDrvnFcst (on page 396).

AllocMktActvtyFcst See SKUProjStatic:AllocMktActvtyFcst (on page 396).

AllocNonBaseFcst See SKUProjStatic:AllocNonBaseFcst (on page 396).

AllocOvrideFcst See SKUProjStatic:AllocOvrideFcst (on page 396).

AllocReconcileFcst See SKUProjStatic:AllocReconcileFcst (on page 396).

AllocTargtImpactFcst See SKUProjStatic:AllocTargtlmpactFcst (on page 396).

AllocTotalLockFcst See SKUProjStatic:AllocTotalLockFcst (on page 396).

AllocTotFcst See SKUProjStatic:AllocTotFcst (on page 396).

AltConstrCovDur See SKUProjStatic:AltConstrCovDur (on page 397)

AltConstrainedUnuseOH See SKUProjStatic:AltConstrainedUnuseOH (on page 397).

AltConstrPOH If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: RecShip, RecAllocShip, RecArriv, RecAllocArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect.

See SKUProjStatic:AltConstrPOH (on page 397).

AltSubConstProjOH


AggSKUProjStatic

If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: RecShip, RecAllocShip, RecArriv, RecAllocArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect.

Note: This column is not used in this release.

AltSupsdConstrProjOH If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: RecShip, RecAllocShip, RecArriv, RecAllocArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect.

ATP See SKUProjStatic:ATP (on page 398).

AutoCustOrders See SKUProjStatic:AutoCustOrders (on page 399).

AutoFcst See SKUProjStatic:AutoFcst (on page 399).

AvailShipOH See SKUProjStatic:AvailShipOH (on page 399).

AvgCycleStock See SKUProjStatic:AvgCycleStock (on page 399).

AvgIntransitStock See SKUProjStatic:AvgIntransitStock (on page 399).

BaseCustOrders See SKUProjStatic:BaseCustOrders (on page 399).

BaseFcst See SKUProjStatic:BaseFcst (on page 399).

BaseHist See SKUProjStatic:BaseHist (on page 400).

CMPFirmDepDmd See SKUProjStatic:CMPFirmDepDmd (on page 400).

CMPFirmPlanArriv See SKUProjStatic:CMPFirmPlanArriv (on page 400).

CMPFirmPlanOrd See SKUProjStatic:CMPFirmPlanOrd (on page 400).

CMPFirmPlanShip See SKUProjStatic:CMPFirmPlanShip (on page 400).

COMetEarlyCount See SKUProjStatic:COMetEarlyCount (on page 400).


AggSKUProjStatic

COMetLateCount See SKUProjStatic:COMetLateCount (on page 400).

COMetOntimeCount See SKUProjStatic:COMetOntimeCount (on page 400).

COMetPartialCount See SKUProjStatic:COMetPartialCount (on page 400).

CommitIntransIn See SKUProjStatic:CommitIntransIn (on page 400).

CommitIntransOut See SKUProjStatic:CommitIntransOut (on page 400).

ConCancel See SKUProjStatic:ConCancel (on page 400).

ConCustOrder See SKUProjStatic:ConCustOrder (on page 400).

CONeedUnit See SKUProjStatic:CONeedUnit (on page 400).

ConExtraUsage See SKUProjStatic:ConExtraUsage (on page 400).

ConIntersiteOrder See SKUProjStatic:ConIntersiteOrder (on page 400).

ConInventory See SKUProjStatic:ConInventory (on page 401).

ConMasterSched See SKUProjStatic:ConMasterSched (on page 401).

ConNew See SKUProjStatic:ConNew (on page 401).

ConNoAction See SKUProjStatic:ConNoAction (on page 401).

ConPull See SKUProjStatic:ConPull (on page 401).

ConPurchaseOrder See SKUProjStatic:ConPurchaseOrder (on page 401).

ConPurchaseReq See SKUProjStatic:ConPurchaseReq (on page 401).

ConPush See SKUProjStatic:ConPush (on page 401).

ConReschedSupply See SKUProjStatic:ConReschedSupply (on page 401).

ConSafetyStock See SKUProjStatic:ConSafetyStock (on page 401).


AggSKUProjStatic

ConSchedSupply See SKUProjStatic:ConSchedSupply (on page 401).

ConShCustOrder See SKUProjStatic:ConShCustOrder (on page 401).

ConShExtraUsage See SKUProjStatic:ConShExtraUsage (on page 401).

ConShMasterSched See SKUProjStatic:ConShMasterSched (on page 401).

ConShortage See SKUProjStatic:ConShortage (on page 402).

ConShSafetyStock See SKUProjStatic:ConShSafetyStock (on page 402).

ConsolidatedPlanShip See SKUProjStatic:ConsolidatedPlanShip (on page 402)

ConstrCovDur The aggregated values of ConstrProjOH and TotDmd are used to calculate the aggregated constrained coverage duration.

See SKUProjStatic:ConstrCovDur (on page 402).

ConstrExpOH See SKUProjStatic:ConstrExpOH (on page 402).

ConstrNetReqts See SKUProjStatic:ConstrNetReqts (on page 402).

ConstrProjAvail If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: RecShip, RecAllocShip, RecArriv, RecAllocArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect, ConstrProjOH, SubConstrProjAvail, SubConstrProjOH, SupsdConstrProjOH.

See SKUProjStatic:ConstrProjAvail (on page 402).

ConstrProjOH See SKUProjStatic:ConstrProjOH (on page 402).

ConstrProxyDemand See SKUProjStatic:ConstrProxyDemand (on page 403).

ConstrProxySupply See SKUProjStatic:ConstrProxySupply (on page 403).

ConstrSchedExpOH See SKUProjStatic:ConstrSchedExpOH (on page 403).

ConstrSchedUnuseOH See SKUProjStatic:ConstrSchedUnuseOH (on page 403).

ConstrUnuseOH


AggSKUProjStatic

See SKUProjStatic:ConstrUnuseOH (on page 404).

ConSubstSupply See SKUProjStatic:ConSubstSupply (on page 396).

ConTotalDemand See SKUProjStatic:ConTotalDemand (on page 404).

ConWorkOrder See SKUProjStatic:ConWorkOrder (on page 404).

COProjMargin See SKUProjStatic:COProjMargin (on page 404).

COProjRevenue See SKUProjStatic:COProjRevenue (on page 404).

CORealMargin See SKUProjStatic:CORealMargin (on page 404).

CORealRevenue See SKUProjStatic:CORealRevenue (on page 404).

COSchedUnit See SKUProjStatic:COSchedUnit (on page 404).

COUnmetCount See SKUProjStatic:COUnmetCount (on page 404).

COUnplannedCount See SKUProjStatic:COUnplannedCount (on page 404).

CovDur The aggregated values of ProjOH and TotDmd are used to calculate the aggregated coverage duration.

See SKUProjStatic:CovDur (on page 404).

DataDrvnCustOrders See SKUProjStatic:DataDrvnCustOrders (on page 405).

DataDrvnFcst See SKUProjStatic:DataDrvnFcst (on page 405).

DemandResExcepCount See SKUProjStatic:DemandResExcepCount (on page 405).

DemandSKUExcepCount See SKUProjStatic:DemandSKUExcepCount (on page 405).

DepDmd See SKUProjStatic:DepDmd (on page 405).

DepDmdEarliestNeed Projection of dependent demand need quantity at the earliest need date.

DetailedPlanShip See SKUProjStatic:DetailedPlanShip (on page 405)

DFUToSKUFcst See SKUProjStatic:DFUToSKUFcst (on page 406).


AggSKUProjStatic

DisplayQty See SKUProjStatic:DisplayQty (on page 405).

Dur See SKUProjStatic:Dur (on page 406).

ExpOH See SKUProjStatic:ExpOH (on page 406).

FcstCustOrders See SKUProjStatic:FcstCustOrders (on page 406).

FirmPlanArriv See SKUProjStatic:FirmPlanArriv (on page 406).

FirmPlanOrder See SKUProjStatic:FirmPlanOrder (on page 406).

FirmPlanShip See SKUProjStatic:FirmPlanShip (on page 406).

FirmProxyInventory See SKUProjStatic:FirmProxyInventory (on page 406).

FirmSchedRcpts See SKUProjStatic:FirmSchedRcpts (on page 406).

FirmSubInventory See SKUProjStatic:FirmSubInventory (on page 407).

FirmSupplyCovDur See SKUProjStatic:FirmSupplyCovDur (on page 407).

FirmSupplyProjOH See SKUProjStatic:FirmSupplyProjOH (on page 407)

FOMetEarlyCount See SKUProjStatic:FOMetEarlyCount (on page 407).

FOMetLateCount See SKUProjStatic:FOMetLateCount (on page 407).

FOMetOntimeCount See SKUProjStatic:FOMetOntimeCount (on page 407).

FOMetPartialCount See SKUProjStatic:FOMetPartialCount (on page 407).

FONeedUnit See SKUProjStatic:FONeedUnit (on page 407).

FOProjMargin See SKUProjStatic:FOProjMargin (on page 407).

FOProjRevenue See SKUProjStatic:FOProjRevenue (on page 407).

ForcedSuppOrderQty See SKUProjStatic:ForcedSuppOrderQty (on page 407)


AggSKUProjStatic

FORealMargin See SKUProjStatic:FORealMargin (on page 407).

FORealRevenue See SKUProjStatic:FORealRevenue (on page 408).

FOSchedUnit See SKUProjStatic:FOSchedUnit (on page 408).

FOUnmetCount See SKUProjStatic:FOUnmetCount (on page 408).

FOUnplannedCount See SKUProjStatic:FOUnplannedCount (on page 408).

HoldOutQty See SKUProjStatic:HoldOutQty (on page 408)

IgnoredDmd See SKUProjStatic:IgnoredDmd (on page 408).

IncMaxCovDur See SKUProjStatic:IncMaxCovDur (on page 408).

IncMinCovDur See SKUProjStatic:IncMinCovDur (on page 409).

IndDmd See SKUProjStatic:IndDmd (on page 409).

IndDmdExceptionCount See SKUProjStatic:IndDmdExceptionCount (on page 409).

IndDmdExceptionQty See SKUProjStatic:IndDmdExceptionQty (on page 409).

InvCarCost See SKUProjStatic:InvCarCost (on page 409).

Inventory See SKUProjStatic:Inventory (on page 409).

MetIndDmd See SKUProjStatic:MetIndDmd (on page 410).

MetSSLevel See SKUProjStatic:MetSSLevel (on page 410).

MktActvtyCustOrders See SKUProjStatic:MktActvtyCustOrders (on page 410).

MktActvtyFcst See SKUProjStatic:MktActvtyFcst (on page 410).

MPConstProjAvail See SKUProjStatic:MPConstProjAvail (on page 410).

NetProfit See SKUProjStatic:NetProfit (on page 410).


AggSKUProjStatic

NetReqts See SKUProjStatic:NetReqts (on page 410).

NonBaseFcst See SKUProjStatic:NonBaseFcst (on page 410).

NonBaseHist See SKUProjStatic:NonBaseHist (on page 410).

NonFcstCustOrders See SKUProjStatic:NonFcstCustOrders (on page 410).

NonSupsdAdjAllocTotalFcst See SKUProjStatic:NonSupsdAdjAllocTotalFcst (on page 411).

NonSupsdAdjFcstCustOrders See SKUProjStatic:NonSupsdAdjFcstCustOrders (on page 411).

NonSupsdAllocBaseFcst See SKUProjStatic:NonSupsdAllocBaseFcst (on page 411).

NonSupsdAllocNonBaseFcst See SKUProjStatic:NonSupsdAllocNonBaseFcst (on page 411).

NonSupsdAllocTotFcst See SKUProjStatic:NonSupsdAllocTotFcst (on page 411).

NonSupsdBaseFcst See SKUProjStatic:NonSupsdBaseFcst (on page 411).

NonSupsdDepDmd See SKUProjStatic:NonSupsdDepDmd (on page 411).

NonSupsdDFUToSKUFcst See SKUProjStatic:NonSupsdDFUToSKUFcst (on page 411).

NonSupsdFcstCustOrders See SKUProjStatic:NonSupsdFcstCustOrders (on page 411).

NonSupsdFirmPlanArriv See SKUProjStatic:NonSupsdFirmPlanArriv (on page 411).

NonSupsdFirmPlanOrder See SKUProjStatic:NonSupsdFirmPlanOrder (on page 411).

NonSupsdFirmPlanShip See SKUProjStatic:NonSupsdFirmPlanShip (on page 411).

NonSupsdNonBaseFcst See SKUProjStatic:NonSupsdNonBaseFcst (on page 412).

NonSupsdNonFcstCustOrders See SKUProjStatic:NonSupsdNonFcstCustOrders (on page 412).

NonSupsdPlanArriv See SKUProjStatic:NonSupsdPlanArriv (on page 412).

NonSupsdPlanOrders See SKUProjStatic:NonSupsdPlanOrders (on page 412).


AggSKUProjStatic

NonSupsdPlanShip See SKUProjStatic:NonSupsdPlanShip (on page 412).

NonSupsdRecArriv See SKUProjStatic:NonSupsdRecArriv (on page 412).

NonSupsdRecShip See SKUProjStatic:NonSupsdRecShip (on page 412).

NonSupsdTotDmd See SKUProjStatic:NonSupsdTotDmd (on page 412).

OptionSet See SKUProjStatic:OptionSet (on page 412).

Master Planning, 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.

OvrideCustOrders See SKUProjStatic:OvrideCustOrders (on page 412).

OvrideFcst See SKUProjStatic:OvrideFcst (on page 412).

PlanArriv See SKUProjStatic:PlanArriv (on page 412).

PlanIntransIn See SKUProjStatic:PlanIntransIn (on page 412).

PlanOrders See SKUProjStatic:PlanOrders (on page 412).

PlanProjAvail See SKUProjStatic:PlanProjAvail (on page 413).

PlanProjOH See SKUProjStatic:PlanProjOH (on page 413).

PlanPurch See SKUProjStatic:PlanPurch (on page 413).

PlanPurchFirm See SKUProjStatic:PlanPurchFirm (on page 413).

PlanShip See SKUProjStatic:PlanShip (on page 413).

PresentationQty See SKUProjStatic:PresentationQty (on page 413).

ProcessDate See SKUProjStatic:ProcessDate (on page 413).

ProjAvail


AggSKUProjStatic

If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: RecShip, RecAllocShip, RecArriv, RecAllocArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect, ConstrProjOH, SubConstrProjAvail, SubConstrProjOH, SupsdConstrProjOH.

See SKUProjStatic:ProjAvail (on page 413).

ProjAvailEarliestNeed The calculation of projected available as of the earliest need date (rather than actual scheduled date of the component).

ProjOH If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: PlanShip, PlanArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect, ConstrProjOH, SubConstrProjAvail, SubConstrProjOH, SupsdConstrProjOH.

See SKUProjStatic:ProjOH (on page 413).

ProjOHEarliestNeed The calculation of projected on hand as of the earliest need date (rather than the actual scheduled date of the component).

ProjOrderOptTotDmd The projected total demand is a projection of the total demand used by the Project Optimized Order process. These demands include forecast, customer orders, and firm and planned shipments.

ProjOrderOptIntransOut The projected in transit out is a projection of the vehicle load information that is scheduled to leave a location. For example, if the destination is a DC, the ProjOrderOptIntransOut represents the demand that is set to ship to stores on vehicle loads. This value is also included in the total demand.

ProjOrderOptSOQ The projected SOQ is a projection of the SOQ created by the Project Optimized Order process. This SOQ represents future orders that are expected to be placed based on the due order logic within Order Optimization.

ProjOrderOptIntransIn The projected in transit in is a projection of the orders that have been approved and are going to be received at a destination. This value does not include orders created by the Optimize Order process until those order have been approved.

ProjOrderOptTotSupply The projected total supply is a supply available to a SKU during a given time period. The supplies include on hand, firm orders, and future SOQs.

ProjOrderOptProjOH The projected on hand calculated as of the SKU projection date. This projected on hand is based on the inputs from the Project Optimized Order process.

ProjOrderOptProjAvail The projected available supply it the projected on hand less safety stock, holdout quantity and display quantity. This value is based on the ProjOrderOptSOQ that is calculated in the Project Optimized Order process. JDA Enterprise Supply Planning Reference Guide 39 © 2014 JDA Software Group, Inc.- Confidential

AggSKUProjStatic

ProAllocBaseFcst See SKUProjStatic:ProAllocBaseFcst (on page 414)

ProratedAllocTotFcst See SKUProjStatic:ProratedAllocTotFcst (on page 414)

ProxyDemand See SKUProjStatic:ProxyDemand (on page 415).

ProxyIntransIn See SKUProjStatic:ProxyIntransIn (on page 415).

ProxyIntransOut See SKUProjStatic:ProxyIntransOut (on page 415).

ProxyInventory See SKUProjStatic:ProxyInventory (on page 415).

ProxyRecArriv See SKUProjStatic:ProxyRecArriv (on page 415).

ProxyRecShip See SKUProjStatic:ProxyRecShip (on page 415).

ProxySupply See SKUProjStatic:ProxySupply (on page 415).

PSOLoad See SKUProjStatic:PSOLoad (on page 415).

PurchOrder See SKUProjStatic:PurchOrder (on page 415).

RecAllocArriv See SKUProjStatic:RecAllocArriv (on page 415).

RecAllocShip See SKUProjStatic:RecAllocShip (on page 416).

RecArriv See SKUProjStatic:RecArriv (on page 416).

ReconcileCustOrders See SKUProjStatic:ReconcileCustOrders (on page 416).

ReconcileFcst See SKUProjStatic:ReconcileFcst (on page 416).

RecShip See SKUProjStatic:RecShip (on page 416).

SchedExpOH See SKUProjStatic:SchedExpOH (on page 416).

SchedRcpts See SKUProjStatic:SchedRcpts (on page 416).

SchedSupplyExceptionCount See SKUProjStatic:SchedSupplyExceptionCount (on page 416).


AggSKUProjStatic

SchedSupplyExceptionQty See SKUProjStatic:SchedSupplyExceptionQty (on page 416).

SchedUnuseOH See SKUProjStatic:SchedUnuseOH (on page 417).

SeasonFactor See SKUProjStatic:SeasonFactor (on page 417).

SKUExceptionCount See SKUProjStatic:SKUExceptionCount (on page 417).

SKUExceptionQty See SKUProjStatic:SKUExceptionQty (on page 417).

SKUExternalFcst See SKUProjStatic:SKUExternalFcst (on page 417).

SKUResExceptionCount See SKUProjStatic:SKUResExceptionCount (on page 417).

SKUResExceptionQty See SKUProjStatic:SKUResExceptionQty (on page 417).

Sources See SKUProjStatic:Sources (on page 417).

SS See SKUProjStatic:SS (on page 417).

SSInventory See SKUProjStatic:SSInventory (on page 417).

SSMetEarlyCount See SKUProjStatic:SSMetEarlyCount (on page 417).

SSMetLateCount See SKUProjStatic:SSMetLateCount (on page 417).

SSMetOntimeCount See SKUProjStatic:SSMetOntimeCount (on page 417).

SSMetPartialCount See SKUProjStatic:SSMetPartialCount (on page 417).

SSNeedUnit See SKUProjStatic:SSNeedUnit (on page 418).

SSSchedUnit See SKUProjStatic:SSSchedUnit (on page 418).

SSUnmetCount See SKUProjStatic:SSUnmetCount (on page 418).

SSUnplannedCount See SKUProjStatic:SSUnplannedCount (on page 418).

StandardCost See SKUProjStatic:StandardCost (on page 418).


AggSKUProjStatic

StartDate See SKUProjStatic:StartDate (on page 418).

Supply

This column is configured for this application only because it is a primary key column and all primary key columns must be configured for all applications that use a given table.

StatSS See SKUProjStatic:StatSS (on page 418).

StockLowCost See SKUProjStatic:StockLowCost (on page 418).

StockOutCost See SKUProjStatic:StockOutCost (on page 418).

SubConstrProjAvail See SKUProjStatic:SubConstrProjAvail (on page 418).

SubConstrProjOH See SKUProjStatic:SubConstrProjOH (on page 418).

SubIntransIn See SKUProjStatic:SubIntransIn (on page 418).

SubInventory See SKUProjStatic:SubInventory (on page 418).

SubRecArriv See SKUProjStatic:SubRecArriv (on page 418).

SubRecShip See SKUProjStatic:SubRecShip (on page 418).

SuppOrderQty See SKUProjStatic:SuppOrderQty (on page 418)

SupsdAdjAllocTotalFcst See SKUProjStatic:SupsdAdjAllocTotalFcst (on page 418).

SupsdAdjFcstCustOrders See SKUProjStatic:SupsdAdjFcstCustOrders (on page 419).

SupsdAllocBaseFcst See SKUProjStatic:SupsdAllocBaseFcst (on page 419).

SupsdAllocNonBaseFcst See SKUProjStatic:SupsdAllocNonBaseFcst (on page 419).

SupsdAllocTotFcst See SKUProjStatic:SupsdAllocTotFcst (on page 419).

SupsdBaseFcst See SKUProjStatic:SupsdBaseFcst (on page 419).

SupsdConstrProjOH See SKUProjStatic:SupsdConstrProjOH (on page 419).

SupsdDepDmd See SKUProjStatic:SupsdDepDmd (on page 419). JDA Enterprise Supply Planning Reference Guide 42 © 2014 JDA Software Group, Inc.- Confidential

AggSKUProjStatic

SupsdDFUToSKUFcst See SKUProjStatic:SupsdDFUToSKUFcst (on page 419).

SupsdFcstCustOrders See SKUProjStatic:SupsdFcstCustOrders (on page 419).

SupsdFirmPlanArriv See SKUProjStatic:SupsdFirmPlanArriv (on page 419).

SupsdFirmPlanOrder See SKUProjStatic:SupsdFirmPlanOrder (on page 419).

SupsdFirmPlanShip See SKUProjStatic:SupsdFirmPlanShip (on page 420).

SupsdNonBaseFcst See SKUProjStatic:SupsdNonBaseFcst (on page 420).

SupsdNonFcstCustOrders See SKUProjStatic:SupsdNonFcstCustOrders (on page 420).

SupsdPlanArriv See SKUProjStatic:SupsdPlanArriv (on page 420).

SupsdPlanOrders See SKUProjStatic:SupsdPlanOrders (on page 420).

SupsdPlanShip See SKUProjStatic:SupsdPlanShip (on page 420).

SupsdProjAvail If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: PlanShip, PlanArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect, ConstrProjOH, SubConstrProjAvail, SubConstrProjOH, SupsdConstrProjOH.

See SKUProjStatic:SupsdProjAvail (on page 420).

SupsdProjOH If both source SKU and destination SKU are included in the data selection, then the following data members are excluded from the calculations: PlanShip, PlanArriv, and all Intransits in or out. The result is that supply that is enroute from the source to the destination continues to be reflected in the total projected inventory. However, if both source and destination are included in the data selection, but the aggregation is done by location rather than by item, then the inventory calculations for the aggregate value that includes the source or destination SKU will be incorrect, ConstrProjOH, SubConstrProjAvail, SubConstrProjOH, SupsdConstrProjOH.

See SKUProjStatic:SupsdProjOH (on page 420).

SupsdRecArriv See SKUProjStatic:SupsdRecArriv (on page 420).

SupsdRecShip See SKUProjStatic:SupsdRecShip (on page 420).

SupsdTotDmd See SKUProjStatic:SupsdTotDmd (on page 420). JDA Enterprise Supply Planning Reference Guide 43 © 2014 JDA Software Group, Inc.- Confidential

AggSKUProjStatic

TargetNetworkInv This column provides visibility on whether the current projected inventory for the item is adequate to meet the demands in the projection period.

The Initial Target Network Inventory is calculated for each location that has local demands and the results are summed to create the total target inventory for the item. Where initial target inventory equals Total of local demands from Time T through Time (T + SKUSafetyStockParam:SSCov (on page 437) + SKUPlanningParam:CumLeadTimeDur (on page 364) + SKUPlanningParam:CumLeadTimeAdjDur (on page 364)).

Local demands include Forecast, CustOrders, Dependent Demands, and Proxy Demands.

Note: The calculation of Target Network Inventory assumes that all SKUs in the item family are included in the aggregation and in the data selection.

TargtImpactBaseFcst See SKUProjStatic:TargtlmpactBaseFcst (on page 421).

TargtImpactCustOrders See SKUProjStatic:TargtlmpactCustOrders (on page 421).

TotalCost See SKUProjStatic:TotalCost (on page 421).

TotalLoad See SKUProjStatic:TotalLoad (on page 421).

TotalLockCustOrders See SKUProjStatic:TotalLockCustOrders (on page 421).

TotalLockFcst See SKUProjStatic:TotalLockFcst (on page 421).

TotArriv See SKUProjStatic:TotArriv (on page 421).

TotContribMargin See SKUProjStatic:TotContribMargin (on page 421).

TotDmd See SKUProjStatic:TotDmd (on page 421).

TotDmdSatisfied See SKUProjStatic:TotDmdSatisfied (on page 421).

TotFcst See SKUProjStatic:TotFcst (on page 421).

TotHist See SKUProjStatic:TotHist (on page 421).

TotIntransIn See SKUProjStatic:TotIntransIn (on page 421).

TotIntransOut See SKUProjStatic:TotIntransOut (on page 421).

TotRecArriv See SKUProjStatic:TotRecArriv (on page 422).


AggSKUProjStatic

TotRecShip See SKUProjStatic:TotRecShip (on page 422).

TotShip See SKUProjStatic:TotShip (on page 422).

TotSupply See SKUProjStatic:TotSupply (on page 422).

TotTransCost See SKUProjStatic:TotTransCost (on page 422).

TotUseRecArriv See SKUProjStatic:TotUseRecArriv (on page 422).

TotUseRecShip See SKUProjStatic:TotUseRecShip (on page 423).

UnconActualReq See SKUProjStatic:UnconActualReq (on page 423).

UnconCancel See SKUProjStatic:UnconCancel (on page 423).

UnconCustOrder See SKUProjStatic:UnconCustOrder (on page 423).

UnconDependantDmd See SKUProjStatic:UnconDependantDmd (on page 423).

UnconExtraUsage See SKUProjStatic:UnconExtraUsage (on page 423).

UnconIntersiteDmd See SKUProjStatic:UnconIntersiteDmd (on page 423).

UnconIntersiteOrder See SKUProjStatic:UnconIntersiteOrder (on page 423).

UnconInventory See SKUProjStatic:UnconInventory (on page 423).

UnconMasterSched See SKUProjStatic:UnconMasterSched (on page 423).

UnconNetAvailable See SKUProjStatic:UnconNetAvailable (on page 423).

UnconNetDaysSupply See SKUProjStatic:UnconNetDaysSupply (on page 424).

UnconNetOnHand See SKUProjStatic:UnconNetOnHand (on page 424).

UnconNew See SKUProjStatic:UnconNew (on page 424).


AltBOM

AltBOM Table included with: Enterprise Supply Planning

Column name PK Included with Datatype Valid values Default value

AltSubord 7 ESP TEXT

AltSubordDisc ESP DATETIME 01/01/1970

AltSubordEff 8 ESP DATETIME 01/01/1970

BOMNum 4 ESP INTEGER DrawQty ESP DECIMAL 1

Eff 5 ESP DATETIME 01/01/1970

Item 1 ESP TEXT

Loc 2 ESP TEXT Offset 6 ESP DURATION 0

Priority ESP INTEGER 0

Subord 3 ESP TEXT UsageSw ESP NUMBER 1,0 1 YieldCal ESP TEXT ' ' YieldFactor ESP DECIMAL 0 to 100 100

Table description Each row of this table identifies an alternate component for a component in a specific BOM.

ESP

Only the LPOPT and MAP solvers use this table.

Column descriptions AltSubord Item that is used to substitute a subordinate item.

AltSubordDisc Date until which an alternate identified by a row of this table is effective. This value is used with AltSubordEff to define the effective duration of an alternate item. See AltSubordEff (on page 46) for the results of all combinations of AltSubordEff and AltSubordDisc.

AltSubordEff Date used to define the effective period of an alternate subordinate item identified by a row of this table. This value is used with AltSubordDisc to define the effective duration of an alternate item. The results of all combinations of AltSubordEff and AltSubordDisc are as follows:


AltBOM

AltSubordEff

value

AltSubordDisc

value

The alternate subordinate item is:

1/1/1970 1/1/1970 Effective Date 1/1/1970 Not effective till AltSubordEff; effective on

AltSubordEff 1/1/1970 Date Effective till AltSubordDisc; discontinued from

AltSubordDisc Date earlier than AltSubordDisc

Date Not effective till AltSubordEff; effective on AltSubordEff; discontinued from AltSubordDisc

BOMNum Bill of Material Number (BOMNum) is a value used to identify the bill of material for a parent item. A group of subordinate items with the same Item, Loc, and BOMNum defines the bill of material for the parent item.

DrawQty Consumption or production quantity of an alternate, expressed as number of subordinate SKU units necessary for one parent SKU unit.

Eff Date from which the BOM relationship identified by a row of this table is effective. Same as BOM:Eff.

Item The parent item for which you are defining a subordinate.

Loc Location of the parent, subordinate, and alternate subordinate item.

Offset This is a primary key of BOM and hence used here.

Priority Priority of an alternate SKU over other alternate SKUs.

ESP (LPOPT and MAP)

If a primary component has more than one alternate, this field specifies the priority of an alternate component over other alternate components. If this value is 1 for all alternate components, the alternate components have the same priority as the primary component. A low Priority number means high priority value. If this field value is lower for an alternate component than the other alternate components of a primary component, the component with the lowest value has the highest priority for substitution.

If this field value is zero for an alternate component, the alternate component has a lower priority than the primary component.

Subord The subordinate item defined in this row. The subordinate is assumed to be at the same location as its parent.

The subordinate must not create a circular BOM. That would happen if SKU A had SKU B as a subordinate while SKU B had SKU A as a subordinate. A circular BOM must not be created even at the item level. That is, if Item A at is a subordinate to Item B at Loc X and Item B is a subordinate to item A at loc Y, these items will not be processed, even if there are no direct or indirect sourcing relationships on either item between locations X and Y.


AltBOM

UsageSw If 1 ESP uses the alternate BOM component defined by this row.

YieldCal Optional calendar attached to the alternate subordinate SKU with time varying yield. In YieldCal, specify the factor to adjust the yield specified in YieldFactor.

YieldFactor Use this factor to model less than perfect manufacturing processes that produce some parent SKUs that cannot be used. Use this column to specify the percentage of usable parent SKUs expected to result from the manufacturing process.

YieldFactor affects the quantity of this alternate subordinate SKU required to produce the intended number of usable parent SKUs.


AltProductionStep

AltProductionStep Table included with: Enterprise Supply Planning


AltRes 6 ESP TEXT

Descr ESP TEXT ' '


Item 1 ESP TEXT Loc 2 ESP TEXT ' '

PrimaryStepNum 4 ESP INTEGER 0

Priority ESP INTEGER 1 ProdRate ESP DECIMAL 0

ProdRateCal ESP TEXT ' ' ProductionMethod 3 ESP TEXT UsageSw ESP BOOLEAN 1

Table description Each row of this table defines an alternate resource that is available for a manufacturing operation.

ESP

Only the MAP and LPOPT solvers use this table.

Column descriptions AltRes Alternate resource name.

Descr Name of the operation that uses the alternate resource.

Eff Starting date from which the alternate resource is effective.

ESP

The MAP and LPOPT solvers do not use this field. You can use the ProdRateCal (on page 50) to model time varying production rates.

Item Item associated with the resource.

Loc Location of the resource.

PrimaryStepNum JDA Enterprise Supply Planning Reference Guide 49 © 2014 JDA Software Group, Inc.- Confidential

AltProductionStep

Sequence number of the production step, associated with the alternate resource, in relation to other steps. Must be consistent with ProductionStep:StepNum (on page 236).

Priority Specifies the priority of an alternate resource over other alternate resources. A low Priority number means high priority value. If priority is zero, the alternate resource has the same priority as the primary resource.

ProdRate The rate at which the specified SKU or process uses resource capacity.

ESP

ESP calculates the load on a resource as:

Resource capacity may be defined in terms of days, hours, standard cases, or any other unit of measure that makes sense in your company. For production capacity calendars, the same unit of measure is used for CalData:Avail (Deep Tree) and CalAtrribute:Attribute value of Avail, which specifies the number of resource capacity units available in a calendar period. The valid values for ProdRate are 0 or greater.

If CalData:Avail (or CalAtrribute:Attribute value of Avail) is based on a unit of time, ProdRate is the number of units of this SKU produced in one of those time units. For example, if CalData:Avail is defined in terms of hours, ProdRate is the number of units of the SKU produced in one hour.

Instead of a unit of time, CalData:Avail (or CalAtrribute:Attribute value of Avail) may be the SKU’s unit of measure, defined in Item:UOM. Or it may be any unit of measure consistent with the SKU’s unit of measure. For example, Item:UOM may be cases and the unit of measure for CalData:Avail may be cans. ProdRate would then be calculated as:

In that example, if there are 12 cans per case, ProdRate would be calculated as:

In ESP (Deep Tree), there are no ramp-up curves or yield curves; the production rate is assumed to be constant. ProdRate does not normally include changeover time. However, you can use ProductionStep:FixedResReq (on page 230) to model changeover times.

ProdRateCal Calendar in which capacity yields are modeled.

ESP

The MAP and LPOPT solvers use this field to model time varying production rates, through a production rate efficiency calendar.

ProductionMethod Combination of ProductionMethod:Item-ProductionMethod:ProductionMethod used to identify the manufacturing operation.

UsageSw Specifies whether the alternate production step defined in this row must be used when planning.


AltProductionStep

ESP (LPOPT and MAP)

If UsageSw is 1, the LPOPT and MAP solvers, when planning, use the alternate resource information specified by this row.


AvgDmd

AvgDmd Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


Eff 1 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DATETIME

Item 2 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT

Loc 3 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT

Qty FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DECIMAL 0.000000

Table description IPO

The Calculate Mean Daily Demand process calculates the time-phased mean daily demand and stores it in this table. Alternatively, you could populate mean daily demand (Qty (on page 53)) values directly with respective effectivity (Eff (on page 53)).

This table is used as an output table.

Fulfillment

The AvgDmd table stores time-phased average replenishment quantities for a SKU. Each row in this table defines the average replenishment quantity over a particular time period for the associated SKU.

This table is used both as an input and an output table.

As an input table, it stores user-specified, time-phased average replenishment quantities acquired from an external system. If you bring data into this table as input, ensure that you also populate the SKUSafetyStockParam:NumReplenYr column (which specifies an approximate number of replenishments in a year).

As an output table, it stores the time-phased average replenishment quantity values resulting from the computations of the Calculate Statistical Safety Stock process with the Average Demand option selected.

Note: The Calculate Statistical Safety Stock process computes average demand as follows:

• If you specify the centralized rule option (CalcMSERule (on page 431) = 4), the Calculate Statistical Safety Stock process uses total demand, which includes non-forecasted customer orders to calculate average demand.

• If you do not specify the centralized rule option (CalcMSERule (on page 431) = 4), the Calculate Statistical Safety Stock process uses total forecast to calculate average demand.


AvgDmd

• If the average demand calculated is negative, the system sets it to 0, and hence the statistical safety stock is 0.

For more information on how Fulfillment uses AvgDmd in computing Statistical Safety Stock, see Mean demand per unit time in Inventory management of JDA Fulfillment OnLine Expert.

Column descriptions Eff The date and time at which the average replenishment quantity defined in this row becomes active.

Item The item associated with the SKU.

Loc The location associated with the SKU.

Qty IPO

The time-phased mean daily demand for the SKU.

Fulfillment

The time-phased average replenishment quantity defined as the:

Mean demand per unit time x number of minutes per year / SKUSafetyStockParam:NumReplenYr


BOM

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

Column name PK Included with Datatype Valid values

Default value

BOMNum 4 FF, MP, Supp, PSO, IPO, Flowcasting, ESP

INTEGER

Disc IPO, FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

DrawQty FF, MP, Supp, PSO, IPO, Flowcasting, ESP

DECIMAL 0

DrawType MP, Supp, ESP (Deep Tree)

OPTION_NUMBER

1,2,3 2

ECN Supp TEXT ' ' Eff 5 FF, MP, Supp, PSO,

IPO, Flowcasting, ESP

DATETIME 01/01/1970

EnableSw Supp, PSO BOOLEAN 1 ExplodeSw Supp BOOLEAN 0 Item 1 FF, MP, Supp, PSO,


TEXT

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

TEXT

MixFactor MP, Supp DECIMAL 100 Offset 6 FF, MP, Supp, PSO,


DURATION 0

QtyPerAssembly

IPO DECIMAL 0

QtyUOM PSO INTEGER 0 ShrinkageFactor

MP, Supp, IPO DECIMAL 0

Subord 2 FF, MP, Supp, PSO, IPO, ESP

TEXT

SupersedeSw FF, MP, Flowcasting BOOLEAN 0 UnitConvFactor Supp DECIMAL 0

YieldFactor MP, Supp, IPO, ESP DECIMAL 100.00 YieldCal ESP DECIMAL

Table description Each row in this table defines a subordinate raw material or component for producing the associated parent SKU.


BOM

Fulfillment

Dependent demand is stored in the DepDmdStatic table when the Calculate Plan process is run. The system uses this table in calculating dependent demand on the subordinate SKU based on the value in SKUPlanningParam:DepDmdOpt of the subordinate.

Master Planning

For Master Planning, dependent demand is stored in the DepDmdStatic table when the Calculate Master Plan process is run.

Inventory Policy Optimization

IPO considers only one set of BOM records for a given repairable SKU. The SKUIPOParam table uses the BOMNum to identify the parts of a repairable SKU. The BOM table allows modeling of multiple BOM records with the same combination of Item, Loc, SubOrd, and BOMNum since there are other primary key columns in this table. However, IPO does not use these other columns; therefore, it is possible for multiple records for the same parent-subordinate relationship to be present in the database. In this case, the system will sum the DrawQty and QtyPerAssembly for all of these records and use the summed DrawQty and Qty PerAssembly as the DrawQty and QuantityPerAssembly for that component. The Calculate Mean Daily Demand process also uses the summed DrawQty when calculating the mean daily demand for this subordinate.

Whereas in the case of consumable SKU, the system considers maximum DrawQty from the multiple records and use the maximum DrawQty as the DrawQty for that component. The Calculate Mean Daily Demand process and Calculate SKU MSE process uses this maximum DrawQty for calculating the mean daily demand and MSE respectively for this subordinate.

Production and Sourcing Optimization

BOM (Bill of materials) table is used to describe the raw materials (subordinate items) and the quantities of each needed(draw quantity) to manufacture an end item (final product).

JDA Production and Sourcing Optimization supports only single level BOM. A single-level BOM describes only one level of child item.

Supply

For Supply, work order dependent demands and transfer order dependent demands are stored in the WorkOrderDepDmd and TransOrderDepDmd respectively.

ESP

• Dependent demand is stored in the DepDmdStatic table when the Generate Master Plan process is run.

• The Generate Master Plan(MAP) and Generate Master Plan(LPOpt) processes require at least one effective BOM to create a plan order.

• The Generate Master Plan(MAP) and Generate Master Plan(LPOpt) processes do not support intermittent discontinuity periods for the BOM components that have predefined alternates in the AltBOM (on page 46) table

Column descriptions BOMNum Bill of Material Number (BOMNum) is a value used to identify the bill of material for a parent item. A group of subordinate items with the same Item, Loc, and BOMNum defines the bill of material for the parent item.

Fulfillment

If your JDA Fulfillment application includes Fulfillment/Production, the system uses the BOM number defined in ProductionMethod:BOMNum.

IPO

JDA IPO only uses the BOM records that match the SKUIPOParam:BOMNum value. JDA Enterprise Supply Planning Reference Guide 55 © 2014 JDA Software Group, Inc.- Confidential

BOM

Supply

JDA Supply uses a BOM record only if BOMNum = 1.

Disc Disc is the ending effective date.

Discontinue Date (Disc) and Eff work together to determine when the subordinate is effective. The chart under Eff summarizes the results of all possible combinations of values for Eff and Disc.

DrawQty The consumption/production quantity, expressed as the number of subordinate SKU units needed for one parent SKU unit.

Fulfillment

Note: Negative draw quantities are not supported in the current release.

IPO

Repairable SKU - In IPO, the draw quantity is the average number of items that are broken when the parent SKU is repaired. For example, for each axel that is broken (the parent SKU) only one wheel may need to be replaced. The DrawQty and QtyPerAssembly (on page 59) are used by IPO to calculate the probability that an item will require repair.

When generating subordinate requirements as part of the time-phased replenishment model, the subordinate requirements are calculated as:

Demand for Subord = (Demand for Parent * DrawQty for the Subordinate) / (SKUIPOParam:SurvivalRate of the parent SKU)

Consumable SKU - In IPO, the draw quantity of a consumable SKU is the average number of subordinate SKU units needed for one parent SKU unit. For example: Two SKU units of subassembly-1 and one SKU unit of subassembly-2 may need to produce to one finished good. In this case, DrawQty is 2 for subordinate subassembly -1, whereas DrawQty is 1 for subordinate subassembly -2 with respect to item finished good.

Master Planning

If the DrawQty is less than 0, Master Planning interprets the value as 0. If the DrawQty is equal to 0, Master Planning accepts that value and does not generate dependent demand for the subordinate SKU. Negative draw quantities and negative values are not supported in Master Planning.


In the Model Management page, the default value for the draw quantity is set to 1 across the entire time period.

ESP (LPOPT and MAP)

If DrawQty is zero or less than zero, the solvers convert it to 1.

DrawType • 1 (Continuous) — Multiple dependent demands are generated.

• 2 (Start) — Dependent demands are generated at the start of the plan order. The default value is 2.

• 3 (Finish)

Master Planning, ESP (Deep Tree)

Master Planning supports DrawTypes of 1 and 2 only.

ECN Engineering Change Number (ECN) is the Engineering Change Number assigned to indicate change in the design or aspect of an item.


BOM

Eff The effectivity of the BOM relationship. Eff and Disc work together to determine when the subordinate defined in this row is effective. The following chart summarizes the results of all possible combinations of values for Eff and Disc.

Eff value Disc value This subordinate is:

1-1-1970 1-1-1970 Effective

Date 1-1-1970 Not effective until Eff; effective as of Eff 1-1-1970 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 ESP

The MAP and LPOPT solvers do not support this combination.


Production and Sourcing Optimization uses only the Eff column to determine when the BOM defined in this row is effective.

IPO

Repairable SKU: This column is configured for this application only because it is a primary key column and all primary key columns must be configured for all applications that use a given table.

Consumable SKU: IPO uses Eff column to determine when the BOM defined in this row is effective.

EnableSw Indicates if the BOM will be used while running the Production and Sourcing Optimization Optimizer.

ExplodeSw This switch indicates if this record should be used when exploding the BOM for the parent item. If ExplodeSw is “0”, the BOM record is ignored.

Item The parent item for which you are defining a subordinate.

Loc The location of both the parent and subordinate items.

MixFactor For a raw material or component that comes in multiple versions (different colors or flavors, for example), you can use MixFactor to model the expected product mix. The valid values for MixFactor are 0 to 100.

For example, one component of the telephones you make may be a faceplate that comes in three different colors. You want to produce a certain percentage of telephones in each color. To do that, create a BOM row for each color. For the parent in each row, specify a generic faceplate SKU. For each subordinate SKU, specify a particular color of faceplate. Set MixFactor to the percentage of the total you expect to sell in each color, so that the total of the MixFactors for all the subordinates is 100.

When calculating dependent demand for each subordinate, Master Planning/Supply applies the MixFactor to the total parent demand, as in this example:

Total parent demand: 500

DrawQty: 1 JDA Enterprise Supply Planning Reference Guide 57 © 2014 JDA Software Group, Inc.- Confidential

BOM

Percentage of demand for each subordinate:

• Beige: 50

• White: 35

• Black: 15

Offset Value that determines when the subordinate must be available for the production process.

Fulfillment

Offset is the length of time that must be allowed in advance of the scheduled date for a production run (PlanOrder:SchedDate) or planned arrival (PlanArriv:SchedShipDate).

For example, if the production process uses the subordinate five hours before the product is available as inventory or available to ship, Offset should be set to 5 hours.

When creating a planned order for a subordinate SKU, Plan calculates the subordinate's DepDmdStatic:StartDate as the parent’s PlanOrder:SchedDate minus BOM:Offset (on page 58). Dependent demand on the subordinate is placed on the appropriate date, even if that date is earlier than the on-hand post date.

A Negative offset indicates that the subordinate is required later than the scheduled date, rather than earlier.

ESP (LPOPT and MAP)

This column is configured because it is a part of the primary key.


Offset from the manufacturing lead time.

When creating a dependent demand for a subordinate SKU, Master Planning calculates the DepDmdOrder:NeedDate as:

parent’s PlanOrder:NeedDate – the associated (ProductionMethod:LeadTime + BOM:Offset (on page 58))

(A ProductionMethod is associated with the BOM through the ProductionMethod table.)

A positive Offset effectively increases the lead time for the subordinate. For example:

• ProductionMethod:LeadTime = 2 days

• BOM:Offset (on page 58) = 1 day

• DepDmdOrder:NeedDate for subordinate = parent’s PlanOrder:NeedDate – 3 days.

A Negative offset indicates that the subordinate is required later than the scheduled date, rather than earlier.

Supply

The Offset lead time 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 is 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.

IPO


BOM


QtyPerAssembly The number of subordinate SKUs required to assemble one parent SKU. For example, if the parent SKU were an axel and the subordinate SKUs were wheels, the quantity per assembly is 2. The DrawQty (on page 56) and QtyPerAssembly are used by IPO to calculate the probability that an item will require repair.

QtyUOM The unit of measure applied to all quantity values associated with the BOM.

ShrinkageFactor Use this factor to account for losses that occur during storage or through other circumstances such as spoilage, evaporation, or theft. Set ShrinkageFactor to the percentage of shrinkage you expect. Valid values for ShrinkageFactor are 0 to 100 and can be greater than 100.

ShrinkageFactor affects the quantity of this subordinate SKU required to produce the desired number of usable parent SKUs.

Master Planning, IPO

When calculating dependent demand for the subordinate SKU, Master Planning applies the ShrinkageFactor as shown in this example:

• Demand for the parent SKU= 1000 units

• DrawQty = 1

• ShrinkageFactor = 10

• Subordinate demand = (Parent demand X DrawQty) * (1+Shrinkage/100)

That is, to get 1,000 units of the parent SKU, you will need 1,100 units of the subordinate.

Supply

Shrinkage is applied to a demand before assigning supply. For example, if shrinkage is 10%, a demand for 100 will be inflated to 110 before assigning supply. So the expanded quantity is calculated as shown in the following example:

The SKUSupplyParam table stores the default Shrinkage values for independent and dependent demands. For dependent demands, these default values can be overridden by specifying relevant and non-zero values in the BOM and Sourcing tables.

The main differences between shrinkage and supply yield are:

• The shrinkage formula is (qty * (1 + shrinkage / 100)) but yield is (qty * 100 / yield).

• Shrinkage is applied to demand for the SKU; supply yield is applied to planned orders for the SKU.

• Supply yield generates scrap; that is, the difference between the expanded quantity and the original quantity is saved in a scrap field in the SupplyPlanResult table.

Subord


BOM

The subordinate item defined in this row. The subordinate is assumed to be at the same location as its parent.

The subordinate must not create a circular BOM. That would happen if SKU A had SKU B as a subordinate while SKU B had SKU A as a subordinate. A circular BOM must not be created even at the item level. That is, if Item A at is a subordinate to Item B at Loc X and Item B is a subordinate to item A at loc Y, these items will not be processed, even if there are no direct or indirect sourcing relationships on either item between locations X and Y.

SupersedeSw Switch that identifies which demands placed on a subordinate SKU (BOM:Subord (on page 47)) by a parent SKU (BOM:Item (on page 47)) can be superseded and, if product transition relationships exist, can be met with supply of alternate items.

• Y: Can be superseded

• N: Cannot be superseded

UnitConvFactor This column stores the Unit of Measure (UOM) factor for the dependent demand of a demand order item. The dependent demand’s quantity is multiplied with the factor specified in BOM:UnitConvFactor. If BOM:UnitConvFactor reads zero, then the dependent demand is multiplied by the factor specified in SKUSupplyParam:UnitConvFactor.

YieldFactor Use this factor to account for less-than-perfect manufacturing processes, which produce some parent SKUs that cannot be used. Specify the percentage of usable parent SKUs you expect to result from the manufacturing process. The valid values for YieldFactor are 0 to 100.

YieldFactor affects the quantity of this subordinate SKU required to produce the desired number of usable parent SKUs.

Master Planning, IPO, ESP

When calculating dependent demand for the subordinate SKU, Master Planning applies the YieldFactor as shown in this example:

• Demand for the parent SKU = 1000 units

• DrawQty = 1

• YieldFactor = 90

Supply

Yield accounts for loss during manufacturing. So if yield is 50% and you need 30 units, you have to start building 30 * (100/50) = 60. This means you need to explode the BOM as if you were building 60, even though you only end up with 30. Yield can be applied to either new supply or dependent demand from new supply, depending on the setting of an option (described below). We will call these supply yield and demand yield respectively.

The formula for yield is as shown below:

The SKUSupplyParam table stores the default Yield values for independent and dependent demands. For dependent demands, these default values can be overridden by specifying relevant and non-zero values in the BOM and Sourcing tables.


BOM

For supply yield, the default value may be overridden for planned orders when the SKU, with the yield factor, is a component of the BOM record (or source part of a sourcing record) containing the overriding value. For example: If A is a SKU with component B with the BOM record for A/B having a non-zero yield, then it will override the default value for B when supply yield is enabled. Thus a planned order for B will be created.

For demand yield, the overriding BOM record is for the parent SKU for which the planned order was created. For example, suppose the BOM record for the SKU A and component B has anon-zero yield, then if the demand yield is enabled, the BOM value will override the default value for A when calculating the dependent demand for B.

The main differences between supply yield and demand yield are as follows:

• Demand yield is applied one step later than supply yield; that is, it is applied to the dependent demand quantity, instead of the planned order quantity.

• Demand yield does not generate scrap, as in the case of supply yield.

Note that demand yield uses the parent's yield value, not the component's. From a timing perspective the sequence is as follows:

• Shrinkage (demand)

• Supply yield (planned orders)

• Demand yield (new dependent demands)

Note: However, if supply yield is enabled, demand yield is disabled (except in the case of Work Order dependent demands created when Work Orders are exploded in the BOM).

YieldCal Optional calendar attached to the subordinate SKU with time varying yield. In YieldCal, specify the factor to adjust the yield specified in YieldFactor.


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


CalAttribute

CalAttribute Table included with: Enterprise Supply Planning.


Attribute 3 ESP INTEGER


VARCHAR2 (50CHAR)

' '

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

NUMBER(4) ' '

PatternSeqNum

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

INTEGER

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

NUMBER(4)

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

FLOAT (126) 0

Table description Stores the attribute data of pattern calendars.

Column descriptions Attribute Attribute of the pattern.

Cal Unique identifier for the calendar.

EndTime End time for the attribute.

StartTime Start time for the attribute.

Value Value of the attribute.

For example, the value of the Allocation Weight attribute is 10 lb.


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

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

If you specify a value for AltCal, CalData:Opt (on page 72) 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 72) 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 72) 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 72)) 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 72). 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 Enterprise Supply Planning Reference Guide 72 © 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 72).

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


CalInterval

CalInterval Table included with: Supply, Production and Sourcing Optimization, Enterprise Supply Planning


Cal 1 Supp, PSO, ESP (LPOPT)

TEXT

Dur Supp, PSO, ESP (LPOPT)

INTEGER 0

DurType Supp, PSO, ESP (LPOPT)

OPTION_NUMBER

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

Interval 2 Supp, PSO, ESP (LPOPT)

INTEGER

RepeatTimes Supp, PSO, ESP (LPOPT)

INTEGER 1

Value Supp, PSO, ESP (LPOPT)

DECIMAL 0

Table description The CalInterval table defines rolling calendars.

Rolling calendars are set up by defining intervals of a specified duration, but without specifying explicit dates. Each row in this table represents one interval/period of the associated calendar. To set up rolling calendars, the Cal:RollingSw should be set to 1.

Note: Rolling calendars are supported only by Production and Sourcing Optimization, JDA Supply, and Enterprise Supply Planning in this release.

Column descriptions Cal The unique identifier/name for the calendar.

Dur The number, that along with DurType, defines the duration of this interval. For example, a Dur of 4 and a DurType of weeks, means the length of this interval is 4 weeks.

DurType The duration type. The valid values are:

• 1 = Duration is specified in minutes

• 2 = Duration is specified in hours

• 3 = Duration is specified in days

• 4 = Duration is specified in weeks

• 5 = Duration is specified in months

• 6 = Duration is specified in quarters

• 7 = Duration is specified in years

Interval


CalInterval

Interval values must be unique within a given calendar and ordered. 0 is the earliest interval in the calendar and the largest value is the latest interval in the calendar.

RepeatTimes The number of times an interval is to repeat consecutively.

Value A (floating-point) value associated with this calendar interval.


CalPattern

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



VARCHAR2 (50CHAR)

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

INTEGER 0

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

VARCHAR2 (50CHAR)

' '

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

DATE

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

NUMBER(1) 0

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

NUMBER(1) 0

PatternSeqNum


INTEGER

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

INTEGER

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

INTEGER

RepeatEveryNDays


INTEGER 0

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

NUMBER(1) 0

StartDate 3 DATE


CalPattern


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

NUMBER(1) 0

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

NUMBER(1) 0

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

NUMBER(1) 0

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

NUMBER(1) 0

Table description Stores the data of pattern calendars.

Column descriptions Cal Unique identifier for the calendar.

Day User entered value for the Day of the Month or Day of the Year pattern.

Descr Description of the pattern.

EndDate End date for the pattern.

FridaySw Value of the switch is 1 only when the Days of the week pattern is selected. The default value is 0.

MondaySw Value of the switch is 1 only when the Days of the week pattern is selected. The default value is 0.

PatternSeqNum System generated sequence number for the pattern.

Pattern Predefined pattern for the calendar.

Rank Rank that enables prioritization among the patterns.

RepeatEveryNDays User entered value for the Every N Days pattern.

SaturdaySw JDA Enterprise Supply Planning Reference Guide 79 © 2014 JDA Software Group, Inc.- Confidential

CalPattern

Value of the switch is 1 only when the Days of the week pattern is selected. The default value is 0.

StartDate Start date for the pattern.

SundaySw Value of the switch is 1 only when the Days of the week pattern is selected. The default value is 0.

ThursdaySw Value of the switch is 1 only when the Days of the week pattern is selected. The default value is 0.

TuesdaySw Value of the switch is 1 only when the Days of the week pattern is selected. The default value is 0.

WednesdaySw Value of the switch is 1 only when the Days of the week pattern is selected. The default value is 0.


Cust

Cust Table included with: Master Planning, Supply, Inventory Policy Optimization, Enterprise Supply Planning


Cust 1 MP, Supp, IPO, ESP

TEXT

Descr MP, Supp, IPO, ESP

TEXT ' '

Priority MP, ESP INTEGER 0

Table description Each row in this table defines one customer—an entity that purchases goods from your company.

A customer may have many physical locations. For example, you may have a customer called SuperStore, which has locations in New York, Tokyo, and Paris. If you want to model customer locations as part of your supply chain, first model the customer in the Cust table, then add a row for each location to the Loc table.

Orders for customers appear in the CustOrderHeader table. Each order may consist of one or more line items, which appear in the CustOrder table.

IPO

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

Column descriptions Cust A unique identifier of this customer.

Descr A description of the customer.

Priority This value indicates the importance of the customer order lines for this customer in relation to all other customer order lines. If the priority for a specific customer order line or customer order has not been set, the system uses this priority when determining which demand to satisfy first.

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 Master Planning process will use the priority for all customer order lines for this SKU (SKUDemandParam:CustOrderPriority).

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 (on page 81) (priority of all the customer order lines for one customer)

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


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,


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 Enterprise Supply Planning Reference Guide 83 © 2014 JDA Software Group, Inc.- Confidential

CustOrder

IPO


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 89) 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 89) 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 89) 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 89) – (CustOrder:Qty (on page 88) × 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 89) – CustOrder:MaxEarlyDur (on page 86)

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 86) 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 89) + CustOrder:MaxLateDur (on page 86)

If CustOrder:MaxLateDur (on page 86) 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 86) 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


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 89) + 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 86) 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 process uses the priority for the whole order (CustOrderHeader:Priority).


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



CustOrder

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


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 89), 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 87)) and expiration date (CustOrder:ResExp (on page 89)) 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 88) × (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 84) is Yes and if CustOrder:ShipDate (on page 89) 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 84) is Yes and if CustOrder:ShipDate (on page 89) 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.



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.


CustOrderHeader

CustOrderHeader Table included with: Master Planning, Supply, Inventory Policy Optimization, Enterprise Supply Planning

Column name PK Included with Datatype Valid values Default value CreationDate Not used in this

release DATETIME TO_DATE('01.0

1.1970.00:00', 'MM.DD.YYYY.HH24:MI')

Cust 1 MP, Supp, IPO, ESP

TEXT

ExtRef 2 MP, Supp, IPO, ESP

TEXT

HasExceptionSw

MP, ESP BOOLEAN 0

LastUpdated Not used in this release

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

LifecycleStatus Not used in this release

INTEGER 1

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

DURATION 0

MaxLateDur MP, IPO, ESP DURATION 10080 Priority MP, ESP ((Deep

Tree and MAP) INTEGER 0,1,2... 0

PromisedDate Not used in this release

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

SchedDate MP, ESP DATETIME TO_DATE('01.01.1970.00:00', 'MM.DD.YYYY.HH24:MI')

SchedStatus MP, ESP OPTION_NUMBER

1,2,3,4,5,6 5

ShipCompleteSw

Not used in this release

BOOLEAN 0

ShipDate MP, ESP DATETIME TO_DATE('01.01.1970.00:00', 'MM.DD.YYYY.HH24:MI')

ShipToAddr Supp TEXT ' '

Table description Each row in this table defines one customer order. A customer order contains one or more customer order line items, which are defined in the CustOrder table.

IPO JDA Enterprise Supply Planning Reference Guide 91 © 2014 JDA Software Group, Inc.- Confidential

CustOrderHeader


Column descriptions Cust The unique identifier for this customer. Must equal Cust:Cust.

ExtRef Unique identifier for the CustOrderHeader. For customer orders imported from an external (non-JDA) system, use this column for the external identifier of the order. It must be unique for each Customer Order Header row in the database.

HasExceptionSw The system sets this switch to Yes if it generates an exception for this customer order.

MaxEarlyDur For Master Planning, 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 – CustOrder:MaxEarlyDur

If this column is 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 and the CustOrderHeader:MaxEarlyDur (on page 92) 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.

IPO


ESP (Deep Tree and MAP)

The number of earlier time buckets that the ESP solver 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 ESP solver will not try to find supply that will result in meeting the order line earlier than CustOrder:ShipDate – CustOrder:MaxEarlyDur.

If this column is 0, the ESP solver uses the value specified in the Duration field on the Generate Master Plan process page. To override the CustOrder:MaxEarlyDur and the CustOrderHeader:MaxEarlyDur (on page 92) values, 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.

MaxLateDur The limit on how late the customer will accept this order. You can specify a maximum late duration for the entire order by entering a value in this column.

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 + CustOrder:MaxLateDur

If this column is 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 and the CustOrderHeader:MaxLateDur (on page 92) 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.


CustOrderHeader


ESP

Limit on how late a customer can accept this demand order. This value specifies the maximum late duration for the entire 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 89) + CustOrder:MaxLateDur

If this value is 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 86) 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.

Priority This value indicates the importance of the customer order lines in this customer order in relation to all other customer order lines. If the priority for a specific customer order line has not been set, the system uses 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 higher values are less important. A value of 0 means that no priority has been set, and the system will use the priority for all customer order lines for this SKU (SKUDemandParam:CustOrderPriority).

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


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


SchedDate The date and time when this order is actually scheduled to be shipped. This is the latest CustOrder:SchedDate from the line items in this order.

SchedStatus For the current Calculate Supply Plan process, this value indicates whether the entire Quantity of all the order line items associated with this CustOrderHeader has been met on the ShipDate.

The system sets this value to the most significant SchedStatus among all the associated order line items, with a status of 5 (Not Met) considered the most significant. For example, if some of the line items have a SchedStatus of 4, some have 2, and some have 1, the SchedStatus for the CustOrderHeader is 4.

• 1 = Met

This order is met on or before the needed ship date (ShipDate).

This status is used for order line items whose SchedDate is earlier than ShipDate only if the order is satisfied from existing inventory. Otherwise, the system assigns a status of 2 (Met Early).

• 2 = Met Early

At least one order line item is satisfied before the needed ship date (ShipDate) from a supply other than inventory.

This status overrides status 1 (Met). JDA Enterprise Supply Planning Reference Guide 93 © 2014 JDA Software Group, Inc.- Confidential

CustOrderHeader

• 3 = Met Late

At least one order line item will be satisfied after the needed ship date (ShipDate). That is, the scheduled shipping date (SchedDate) is after the needed shipping date (ShipDate).

This status overrides status 2 (Met Early).

• 4 = Partially Met

At least one order line item has a SchedStatus of 4 (Partially Met). Only part of the quantity of that order line item is satisfied by the supply. You can determine how much of the order line item is not satisfied by using this calculation:

CustOrder:Qty - CustOrder:SchedQty

To find the supply orders meeting this demand, and determine the quantity supplied by those orders, use the OrderLink table.

This status overrides status 3 (Met Late).

• 5 = Not Met

At least one order line item is not satisfied, in whole or in part, by the supply.

This status overrides status 4 (Partially Met).

ShipDate The date and time when this line item must be shipped in order to meet the date needed by the customer.

Valid values for Shipping Date are Date/time and cannot be blank.

ShipToAddr The ship-to-address for this order. This column, when combined with CustOrderHeader:Cust (on page 92), refers to the ship-to-address for this order.


CustOrderStatus

CustOrderStatus Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning


CalcMargin ESP (LPOPT) FLOAT

CalcRevenue ESP (LPOPT) FLOAT DmdPlanTime MP INTEGER 0 ExpDate MP DATETIME 01/01/1970 HasExceptionSw MP, ESP BOOLEAN 0

Item 2 FF, MP, Flowcasting, ESP

TEXT ' '

Loc 3 FF, MP, Flowcasting, ESP

TEXT ' '

OrderID 1 FF, MP, Flowcasting, ESP

TEXT ' '

ProcessSeqNum MP INTEGER

SchedDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

SchedQty FF, MP, Flowcasting, ESP

DECIMAL 0

SchedStatus FF, MP, Flowcasting, ESP

OPTION_NUMBER

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

ShipDate 4 FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

Table description The customer order status record is updated by the following processes. Each of these processes creates one CustOrderStatus row for each CustOrder for each item on which the process was run.

• Calculate Master Plan - This process updates customer order status of the Master Planning SKUs.

• Generate Supply and Demand Links based on Priority - When this process is run, it updates the customer order status of Master Planning and Fulfillment SKUs based on the scope you select in the process page. In the case of Master Planning SKUs it overwrites the status created by Calculate Master Plan process.

Column descriptions CalcMargin ESP (LPOPT)

For this customer order (demand), this value is calculated as Revenue - Total cost of supply.


CustOrderStatus

CalcRevenue ESP (LPOPT)

Revenue generated from meeting this customer order (demand).

DmdPlanTime Time elapsed in milliseconds to process a demand. If the time taken to process a demand is less than a millisecond then it is reported as zero.

ExpDate The requirement expiration date of customer order.

HasExceptionSw The system sets this switch to Yes if it generates an exception for the customer order.

Item The item associated with this line item.

Loc The location associated with this line item.

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

ProcessSeqNum The sequence number generated for a demand order by the Calculate Master Plan process.

SchedDate The date and time when this order is scheduled to be shipped.

SchedQty The quantity that must be shipped on the scheduled date.

SchedStatus Based on the results of Calculate Master Plan or Generate Supply and Demand Links, this value indicates whether the CustOrder quantity has been met for the associated CustOrder record.

• 1: Met

This order is met on or before the needed ship date (ShipDate).

This status is used for order line items whose SchedDate is earlier than ShipDate only if the order is satisfied from existing inventory. Otherwise, the system assigns a status of 2 (Met Early).

• 2: Met Early

At least one order line item is satisfied before the needed ship date (ShipDate) from a supply other than inventory.

This status overrides status 1 (Met).

• 3: Met Late

At least one order line item will be satisfied after the needed ship date (ShipDate). That is, the scheduled shipping date (SchedDate) is after the needed shipping date (ShipDate).


• 4: Partially Met

At least one order line item has a SchedStatus of 4 (Partially Met). Only part of the quantity of that order line item is satisfied by the supply. You can determine how much of the order line item is not satisfied by using this calculation:

CustOrder:Qty - CustOrderStatus:SchedQty


CustOrderStatus



• 5: Not Met

At least one order line item is not satisfied, in whole or in part, by the supply.

This status overrides status 4 (Partially Met).

• 6: Not processed by Master Planning

This option is displayed only in the IndDmdView.

• 7: Met Ontime with Plan Arrival

The customer order is met on or before the needed ship date (ShipDate) by Plan Arrival.

This status is used for order line items whose SchedDate is earlier than ShipDate and the order is satisfied Plan Arrival. Otherwise, the system assigns a status of 8 (Met Early).

• 8: Met Early with Plan Arrival

At least one order line item is satisfied before the needed ship date (ShipDate) by Plan Arrival.

This status overrides status 7 (Met Ontime).

• 9: Met Late with Plan Arrival

At least one order line item will be satisfied after the needed ship date (ShipDate) by Plan Arrival. That is, the scheduled shipping date (SchedDate) is after the needed shipping date (ShipDate).


• 10: Met Partially with Plan Arrival

At least one order line item has a SchedStatus of 10 (Met Partially). Only part of the quantity of that order line item is satisfied by the Plan Arrival. You can determine how much of the order line item is not satisfied by using this calculation:


To find the plan arrivals meeting this demand, and determine the quantity supplied by those plan arrivals, use the OrderLink table.


ShipDate The date and time when this order must be shipped.


DepDmdStatic

DepDmdStatic Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning


BOMNum 6 FF, MP, Flowcasting, ESP

INTEGER 0

CalcPriority MP, ESP DECIMAL 0 Dur FF, MP,

Flowcasting, ESP

DURATION 0

EarliestNeedDate

MP, ESP DATETIME 01/01/1970

Expdate MP, ESP DATETIME 01/01/1970

FirmSw 5 FF, MP, Flowcasting, ESP

BOOLEAN 0


TEXT


TEXT

Parent 3 FF, MP, Flowcasting, ESP

TEXT

ParentExpDate 9 FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

ParentOrderType

10 FF, MP, Flowcasting, ESP

OPTION_NUMBER

2,6,9 2

ParentSchedDate

8 FF, MP, ESP DATETIME 01/01/1970

ParentSeqNum 7 FF, MP, Flowcasting, ESP

INTEGER 0

ParentStartDate 12 FF DATETIME 01/01/1970 Qty FF, MP,

Flowcasting, ESP

DECIMAL 0


DATETIME 01/01/1970


DECIMAL 0


DepDmdStatic


SchedStatus FF, MP, Flowcasting, ESP

OPTION_NUMBER

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

SeqNum FF, MP, Flowcasting, ESP

INTEGER 0

StartDate 4 FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

SupersedeSw 11 FF, MP, Flowcasting, ESP

BOOLEAN 0

Table description Each row in this table represents the demand placed on a subordinate (BOM:Subord) by a particular parent (BOM:Item) during a particular reporting period or at a specific point in time.

Fulfillment

The system creates the contents of this table according to the method specified in SKUPlanningParam:DepDmdOpt when the Calculate Plan process is run with the Calculate Plan process option selected.

When CPP Workbench or the Level Loads process moves planned orders, the DepDmdStatic table is updated.

Master Planning, ESP

Each row in this table represents the dependent demands generated for Plan Orders, Firm Plan Orders, and Scheduled Receipts when the Calculate Master Plan, Generate Master Plan (MAP), or Generate Master Plan (LPOPT) process is run.

Column descriptions BOMNum The BOMNum associated with the ProductionMethod that is specified on the parent PlanOrder or parent SchedRcpt placing the load.

CalcPriority The calculated priority of this demand. A generated dependent demand inherits the calculated priority of the independent demand that caused its creation.

For imported dependent demands (ImpDepDmdStatic), this value is ignored, since imported dependent demands must be associated with a scheduled receipt. The dependent demand is then processed at the same time as its associated scheduled receipts. All scheduled supplies, including scheduled receipts, are processed first, before any independent demands. Scheduled supplies are processed by SKU, components before finished goods (The scheduled receipts for each SKU are then processed in ascending order by need date). After processing scheduled receipts, the dependent demands (stored in the ImpDepDmdStatic table) are written to the DepDmdStatic table. For these dependent demands, the CalcPriority would be equal to zero.

Dur Not used in current release - this value is always zero.

EarliestNeedDate


DepDmdStatic

Earliest need date is the earliest/unconstrained need date when the dependent demand is required.

ExpDate The requirement expiration date of dependent demand.

FirmSw Firm Switch (FirmSw) indicates whether the dependent demand row has been generated based on a firm planned order, scheduled receipt (if SKUPlanningParam:DepDmdOpt = 2), or firm planned arrival (if DepDmdOpt = 3).

Item The subordinate item on which the dependent demand is being placed.

Loc The location of the subordinate to which the dependent demand applies.

Parent The parent of the associated subordinate item.

ParentExpDate The expiration date of the related supply order. For example, if this dependent demand exists because of a planned order, ParentExpDate of the Planned Order.

ParentOrderType Note: Master Planning and ESP use ParentOrderTypes of 2, 6, and 9.

The type of the related supply order. For example, if this dependent demand exists because of a planned order, ParentOrderType is Planned Order.

• 1: Planned Arrival (PlanArriv table)

• 2: Planned Order (PlanOrder table)

• 5: Vehicle Load Line (VehicleLoadLine table)

• 6: Scheduled Receipt (SchedRcpts table)

• 9: Firm Planned Order (Plan Order table)

For this parent order type: Correspond to these columns in the parent order table

Planned order [For ParentOrderType = 2]

PlanOrder:Item = DepDmdStatic:Parent (on page 100) PlanOrder:Loc = DepDmdStatic:Loc (on page 100) PlanOrder:SeqNum = DepDmdStatic:ParentSeqNum (on page 101)

Scheduled receipts [For ParentOrderType = 6]

SchedRcpts:Item = DepDmdStatic:Parent (on page 100) SchedRcpts:Loc = DepDmdStatic:Loc (on page 100) SchedRcpts:OrderNum = DepDmdStatic:ParentSeqNum (on page 101)

Firm planned order [For ParentOrderType = 9]

PlanOrder:Item = DepDmdStatic:Parent (on page 100) PlanOrder:Loc = DepDmdStatic:Loc (on page 100) PlanOrder:SeqNum = DepDmdStatic:ParentSeqNum (on page 101)

ParentSchedDate Parent Scheduled Date (ParentSchedDate) is the scheduled date of the related dependent demand.


DepDmdStatic

ParentSeqNum Parent Sequence Number (ParentSeqNum) is the sequence number of the related dependent demand.

ParentStartDate Parent Start Date is the start date of the related dependent demand.

Qty The scheduled dependent demand for this item from the specified parent during the indicated period of time.

SchedDate Scheduled Date (SchedDate) is the date when the dependent demand is scheduled to be met.

SchedQty Scheduled Quantity (SchedQty) is the quantity of the dependent demand met or available. This field is populated in Fulfillment only if the Generate Supply & Demand Link process is run.

SchedStatus Scheduled Status (SchedStatus) is the value that indicates whether the entire Quantity of this demand has been met on the need date. This field is populated in Fulfillment only if the Generate Supply & Demand Link process is run.

• 1: Met

This demand is met on or before the needed ship date (ShipDate).

This status is used for demands whose SchedDate is earlier than ShipDate only if the order is satisfied from existing inventory. Otherwise, the system assigns a status of 2 (Met Early).

• 2: Met Early

This demand is satisfied before the needed ship date (ShipDate) from a supply other than inventory.

• 3: Met Late

This demand is satisfied after the needed ship date (ShipDate). That is, the scheduled shipping date (SchedDate) is after the needed shipping date (ShipDate).


Only part of the quantity of this demand is satisfied by the supply. You can determine how much of this demand is not satisfied by using this calculation:

Qty - SchedQty


• 5: Not Met

This demand is not satisfied, in whole or in part, by the supply.

SeqNum The sequence number generated for a dependent demand. This number is populated by the Calculate Master Plan/ Generate Master Plan/ Calculate Plan process for a given SKU.

StartDate This date represents the NeedDate for the constrained subordinate supply that will meet the dependent demand.

SupersedeSw Supersede switch that identifies which demand placed on a subordinate SKU (BOM:Subord) by a parent SKU (BOM:Item) can be superseded and, if product transition relationships exist, can be met with supply of alternate items.


DepDmdStatic




This column is configured only because it is a primary key column and all primary key columns must be configured for all applications that use a given table.


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

DmdGroup The demand group associated with this DFU.

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.

DmdUnit The demand unit associated with this DFU.

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

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 Enterprise Supply Planning Reference Guide 110 © 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 112) 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 Enterprise Supply Planning Reference Guide 115 © 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).


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





Date later than Disc

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

DmdGroup The demand group associated with the DFU.

DmdUnit The product associated with the DFU from which data is mapped.

Eff The date when this mapping becomes effective.

Eff and Disc (on page 118) 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.


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.


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


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.


DFUToSKUSeasonErr

DFUToSKUSeasonErr Table included with: Fulfillment, Master Planning, Supply, Flowcasting, Enterprise Supply Planning


DFULoc 5 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT

DmdGroup 4 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT

DmdUnit 3 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT

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

DURATION 0

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

DECIMAL 0.0

Item 1 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT

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

INTEGER 0

SKULoc 2 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT

StartDate 6 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

DATETIME

Table description Each row of this table contains data that defines a seasonality error that has been calculated by the Calculate Seasonality Error process and mapped to a SKU from a DFU. The seasonality error for the DFU is stored in the SeasonError table and mapped to the SKU through the Transfer Forecast process using the mapping information in the DFUToSKU table.

Column descriptions DFULoc The location associated with the DFU from which forecast demand data is mapped. JDA Enterprise Supply Planning Reference Guide 122 © 2014 JDA Software Group, Inc.- Confidential

DFUToSKUSeasonErr

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 length of the time interval covered by the forecast defined in this row.

Factor The value resulting from the calculation of seasonality of forecast error associated with this SKU.

Item The item associated with the SKU to which seasonality error data is mapped.

PerNum The number of the period for which the seasonality factor is being calculated.


StartDate The start date of the mapped forecast.


DmdVar

DmdVar Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning


DmdVar FF, MP, Flowcasting, ESP

DECIMAL 0.000000

Eff 1 FF, MP, Flowcasting, ESP

DATETIME


TEXT


TEXT

Table description Each row in this table describes the variance of demand over the replenishment lead time for a SKU. Demand variance is calculated assuming lead time variability and demand variability.

This table is used both as an input and an output table.

As an input table, it stores user-specified, time-phased demand variance from an external system.

As an output table, it stores the demand variance values resulting from the calculation of the Calculate Statistical Safety Stock process with the Demand Variance option selected.

Column descriptions DmdVar Demand Variance is the variance of demand for a particular SKU over the replenishment lead time. This value can be input by you from an external source or calculated by the Calculate Statistical Safety Stock process.

Fulfillment

See Working with statistical safety stock based on customer service targets in the Inventory Management in JDA Fulfillment section of the JDA Fulfillment OnLine Expert for information on this value.

Eff Effective Date is the date and time at which the demand variance defined in this row becomes active.

Item The item associated with the SKU whose demand variance is defined in this row.

Loc The location associated with the SKU whose demand variance is defined in this row.


ExceptionCategoryAssoc

ExceptionCategoryAssoc Table included with: Master Planning, Enterprise Supply Planning


Exception 1 MP, ESP INTEGER 0

Category MP, ESP INTEGER 0

Table description Each row in this table defines the relation between an exception and the exception category.

Master Planning

The exceptions in Master Planning are now associated with specific categories and this association is defined here. This is a system table which has some predefined entries. The Master Planning process considers the records stored in this table as input.

Exception

Number

Category Id

Category Description

5529 501 Invalid BOM

5525 502 Invalid BOM Parameter

5728 503 Invalid ImpDepDemand Parameter

5723 504 Invalid ImpResLoadDetails Parameter

5716 505 Invalid Inventory Parameter

5712 506 Invalid Perishable Parameter

5719 507 Invalid Plan Arrival

5720 508 Invalid Plan Order

5721 509 Invalid Plan Purchase

510 Invalid ProdMethod



Exception

Number

Category Id


5666 511 Invalid ProdMethod Parameter

5704 512 Invalid ProdStep Parameter

5718 513 Invalid Purch Order Parameter

5621 514 Invalid PurchMethod

5638 515 Invalid PurchMethod Parameter

5653 516 Invalid RecShip

5615 517 Invalid ResLoadDetail

5700 518 Invalid Resource load

5722 519 Invalid SchedReceipts

5510 520 Invalid SKU Parameter

5563 521 Invalid Sourcing

5637 522 Invalid Sourcing Parameter

5672 523 Invalid VehicleLoadLine

601 Batch Size Exceeded

6045 602 Capacity Shortage

603 Coverage Dur. Exceeded

6008 604 Freeze Period

6065 605 Invalid Calendar

6066 606 Invalid Firm Plan Order



Exception

Number

Category Id


6064 607 Invalid Supply Method

6061 608 Material Shortage

6060 609 Pre-Build Restriction

6006 610 Production Lead Time

6013 611 Purchase Lead Time

6019 612 Resource Loading Time

6002 613 Resource Overload

6074 614 Shelf Life Restriction

6007 616 Sourcing Lead Time

617 Finish Calendar Restriction

Column descriptions Exception Unique exception number or code to identify an exception.

Category The category to which an exception is associated.


ExceptionOrderRelation

ExceptionOrderRelation Table included with: Master Planning, Supply, Enterprise Supply Planning


Datatype Valid values Default value

AvailDate Supp DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

BatchNum 2 MP, Supp, ESP

INTEGER 0

DemandQty MP, Supp, ESP

DECIMAL 0

DemandSeqNum MP, Supp, ESP

INTEGER 0

DemandType MP, Supp, ESP

INTEGER 0

Exception 6 MP, Supp, ESP

INTEGER

ExceptionDate MP, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

ExceptionRelationType MP, Supp, ESP

INTEGER 1,2

ExceptionSeqNum 3 MP, Supp, ESP

INTEGER

ExpDate Supp DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

FunctionNum 4 MP, Supp, ESP

INTEGER

Item MP, Supp, ESP

TEXT ' '

LoadQty MP, Supp, ESP

DECIMAL 0

Loc MP, Supp, ESP

TEXT ' '

Margin MP, ESP DECIMAL 0 OrderID MP, Supp,

ESP TEXT





ProcessID 1 MP, Supp, ESP

INTEGER Any value in the PROCESSOPTIONSET: PROCESSID column

0

Project Supp TEXT Revenue MP, ESP DECIMAL 0 SeqNum 5 MP, Supp,

ESP INTEGER

ShipDate MP, Supp, ESP

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

Store Supp TEXT ' ' SupplySeqNum MP, Supp,

ESP INTEGER 0

SupplyType MP, Supp, ESP

INTEGER 1,2,4,5,6,7,8,9, 10,11,12,13,14

0

When MP, Supp, ESP


OrderType MP, ESP NUMBER 1,2 0

Table description Master Planning

This table maintains a relationship between the independent demands, scheduled supplies and the exceptions generated against them. Exceptions can be SKU [material] or resource [capacity] related. Associated SKU exceptions are stored in the SKUException table while resource exceptions are stored in the ResException table.

The following table defines that relationships between the independent demand orders and the ExceptionOrderRelation table.

Column in

ExceptionOrderRelation table

Independent Demand table

Column in Independent Demand table

Item CustOrder Item

FcstOrder



Column in


Independent Demand table

Column in Independent Demand table

StockOrder Loc CustOrder Loc

FcstOrder

StockOrder ShipDate CustOrder ShipDate

FcstOrder

StockOrder OrderID CustOrder OrderID

FcstOrder

StockOrder DemandSeqNum CustOrder

FcstOrder SeqNum

StockOrder SeqNum DemandType CustOrder 1

FcstOrder 2

StockOrder 3 The following table defines that relationships between the scheduled supplies and the ExceptionOrderRelation table.

Column in


Supply Order table

Column in Supply Order table

Item PlanOrder Item

PlanArriv

SchedRcpts VehicleLoadLine

Loc PlanOrder Loc

PlanArriv Dest

SchedRcpts Loc VehicleLoadLine

SupplySeqNum PlanOrder SeqNum

PlanArriv SeqNum

SchedRcpts SeqNum VehicleLoadLine OrderNum



Column in


Supply Order table

Column in Supply Order table

SupplyType PlanOrder 9

PlanArriv 11

SchedRcpts 6 VehicleLoadLine 5

Supply

This table stores customer and purchase related exceptions generated by the Validate Input Data process.

Column descriptions AvailDate The date and time when this supply or demand quantity is available or needed.

BatchNum The value used to identify the batch in which the independent demands were processed. This can be either SKUException:BatchNum or a ResException:BatchNum.

DemandQty The demand quantity that could not be planned by Master Planning associated with this exception record (Need Quantity – Sched Quantity).

DemandSeqNum The sequence number associated with the independent demand for which the exception was generated.

DemandType Indicates what kind of demand is associated with this row, and which database table and column the demand comes from.

• 1: Customer order

• 2: Forecast order

• 3: Safety stock order

• 4: Dependent demand plan order

• 5: Dependent demand firm plan order

• 6: Dependent demand scheduled receipt

• 7: Distribution demand plan arrival

• 8: Distribution demand firm plan arrival

• 9: Distribution demand instransit out.

Exception The exception code number. The exception stored can be a SKU exception or a resource exception.

ExceptionDate For details, see SKUException:ExceptionDate and ResException:ExceptionDate.

ExceptionRelationType • 1: SKU exception



• 2: Resource exception

The type of exception (SKUException = 1, ResException = 2) associated with this record.

ExceptionSeqNum The sequence number which links the exception relation record to its corresponding record in the SKUException or the ResException tables (ExceptionOrderRelation:ExceptionSeqNum (on page 132) = ResException:SeqNum / SKUException:SeqNum).

ExpDate The date on which the date-sensitive, on-hand inventory for the primary item expires.

FunctionNum The number of the function that generated this exception. For details, see SKUException:FunctionNum and ResException:FunctionNum.

Item The independent demand or scheduled supply item.

LoadQty Note: Master Planning does not use this column in this release.

The load quantity (in resource units) for which this exception was generated.

Loc The independent demand or scheduled supply location. For a PlanArriv, Firm PlanArriv, and a VehicleLoadLine this location is equal to the destination location.

Margin The margin value proportional to the demand quantity for this exception record.

OrderID Unique identifier of the line item defined in this row. This is needed to identify customer orders.

OrderType Denotes whether an exception is generated while planning an independent demand or scheduled supply.

1: Independent Demand

2: Scheduled Supplies

ProcessID The identifier associated with the process in which the exception was raised. This can be either SKUException:ProcessID or a ResException:ProcessID.


Revenue The revenue value proportional to the demand quantity for this exception record.

SeqNum The sequence number generated for the independent demand or the vehicle load line.

ShipDate The date and time when this order must be shipped. This is needed to identify customer orders. JDA Enterprise Supply Planning Reference Guide 132 © 2014 JDA Software Group, Inc.- Confidential


Store Description of where this quantity is stored, such as a rack, a row, or a bin code. This column can also contain the name of a store, within a location.

SupplySeqNum The sequence number of the supply associated with this exception.

SupplyType The SupplyType indicates the supply order associated with this exception, and which database table and column the supply order comes from. For details, see OrderLink table.



• 4: Recommended arrival

• 5: Vehicle Load Lines

• 6: Scheduled Receipt

• 7: Inventory

• 8: Safety Stock

• 9: Firm Planned Order (PlanOrder table)

• 10: Firm Recommended Shipment (RecShip table)

• 11: Firm Planned Arrival (PlanArriv table)

• 12: Plan Purchase (PlanPurch table)

• 13: Firm Plan Purchase (PlanPurch table)

• 14: Purchase Order (PurchOrder table)

Note: The SupplyTypes that are applicable to Master Planning are 5, 6, 9, and 11.

When The system date and time or the date when a process is run.


ExceptionSeverity

ExceptionSeverity Table included with: Master Planning, Enterprise Supply Planning


DemandSupplyType 1 MP, ESP INTEGER 1, 2, 3 0 SchedStatus 2 MP, ESP INTEGER 1, 2, 3, 4, 5 0 SupplyMethodOption 3 MP, ESP INTEGER 1, 2, 3 0 ExceptionSw MP, ESP INTEGER 0, 1 1 Severity MP, ESP INTEGER 1, 2, 3 0

Table description Each row in this table defines the relation between an exception and the exception category.

Master Planning

The Calculate Master Plan process of Master Planning uses the different business rules setup in this table to populate the severity column in both SKUException and RESException tables for every exception generated during the planning process.

Column descriptions DemandSupplyType Note: In the current release, the ExceptionSeverity table supports only independent demands with values of 1, 2 and 3.

The type of demand (and the associated table), as follows:

• 1 = Customer Order (CustOrder table). The demand order maps to the CustOrder.

• 2 = Forecast (FcstOrder table). The demand order maps to the FcstOrder.

• 3 = Safety Stock Requirement (StockOrder table). The demand order maps to the StockOrder.

• 5 = Intransit In (VehicleLoadLine table). The supply order maps to the VehicleLoadLine .

• 6 = Scheduled Receipt (SchedRcpts table). The supply order maps to the SchedRcpts.

• 9 = Firm Plan Order (PlanOrder table). The supply order maps to the PlanOrder.

• 11 = Firm Planned Arrival (PlanArriv table). The supply order maps to the PlanArriv.

• 13 = Firm Planned Purchase (PlanPurch table). The supply order maps to the PlanPurch.

• 14 = Purchase Order (PurchOrder table). The supply order maps to the PurchOrder.

SchedStatus This parameter is used along with DemandSupplyType and SupplyMethodOption to decide the severity to be generated for the exception.

Based on the results of Calculate Master Plan, the following values indicate whether the independent demand quantity has been met for the associated demand.

• 1 = Met. The order is met on or before the needed ship date (ShipDate). This status is used for order line items, whose scheduled shipping date (SchedDate) is earlier than ShipDate, only if the order is satisfied from the existing inventory. Otherwise, the system assigns status 2 (Met Early).

• 2 = Met Early. At least one order line item is satisfied before the needed ship date from a supply other than inventory. This status overrides status 1 (Met).


ExceptionSeverity

• 3 = Met Late. At least one order line item is satisfied after the needed ship date, that is, SchedDate is after ShipDate. This status overrides status 2 (Met Early).

• 4 = Partially Met. At least one order line item has a SchedStatus of 4 (Partially Met). Only part of the quantity of that order line item is satisfied by the supply. You can determine how much of the order line item is not satisfied by using this calculation: CustOrder:Qty - CustOrderStatus:SchedQty. To find the supply orders meeting this demand and to determine the quantity supplied by those orders, use the OrderLink table. This status overrides status 3 (Met Late).

• 5 = Not Met. At least one order line item is not satisfied, in whole or in part, by the supply. This status overrides status 4 (Partially Met).

SupplyMethodOption Defines the applicability and importance of priority for the available supply methods.

• 0 = Priority of the supply method is not considered in populating this prescribed severity.

• 1 = Prescribed severity is populated only if the exception is encountered due to a supply method (ProductionMethod, PurchMethod or Sourcing), and if the supply method has the highest priority.

• 2 = Prescribed severity is populated only if the exception is encountered due to a supply method (ProductionMethod, PurchMethod or Sourcing), and if the supply method does not have the highest priority.

ExceptionSw Select this check box only if an exception needs to be generated for a particular condition. This helps in reducing the number of exceptions generated for the Master Planning process as exceptions pertaining to certain required scenarios only are generated.

Severity Stores the value that needs to be populated for an exception in consideration with the corresponding values for DemandSupplyType, PrimarySupplyMethodOption and SchedStatus.


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.


FcstOrder

FcstOrder Table included with: Fulfillment, Master Planning, Supply, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


CalcPriority MP, Supp, ESP (Deep Tree)

DECIMAL 0

ConsumedQty FF, MP, Supp, IPO, Flowcasting, ESP (Deep Tree)

DECIMAL 0

DmdType MP, ESP INTEGER 1,2,3 1 Dur FF, MP, Supp,


DURATION 0

ExpDate MP DATETIME 01/01/1970

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

TEXT

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

TEXT

MaxEarlyDur FF, MP, Supp, IPO, Flowcasting, ESP (MAP and Deep Tree)

DURATION 0

MaxLateDur FF, MP, Supp, IPO, Flowcasting, ESP

DURATION 0

NeedDate FF, MP, Supp, IPO, Flowcasting, ESP

DATETIME 01/01/1970

OrderType Supp INTEGER -125

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

INTEGER -1

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

INTEGER 0

Project Supp TEXT ' '


FcstOrder


Qty FF, MP, Supp, IPO, Flowcasting, ESP

DECIMAL 0

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

INTEGER

SupersedeSw MP BOOLEAN 0

Table description Each row in this table defines one forecast demand order. Each application writes forecast order rows to this table after the Generate Forecast Orders process is run.

Fulfillment

In Fulfillment, this table is used only by the Generate Supply and Demand Links process. Prior to running the Generate Supply and Demand LInks process, the Generate Forecast Orders process must be run to generate FcstOrder records.

Master Planning

Master Planning uses this table as input for the Calculate Rules Based Priority process which generates a priority sequence number for independent demand orders, and as independent demand for the Calculate Master Plan process.

Supply

Optionally, for Supply, the FcstOrder table can also contain the forecasted independent demand as imported from a host ERP system.

IPO

IPO uses the data in this table as independent demand when using the replenishment plan cost model. If another cost model is selected, this table is not used.

ESP

Uses this table as input to the Calculate Rules Based Priority process which generates a priority sequence number for independent demand orders, and as independent demand for the Generate Master Plan process.

Column descriptions CalcPriority Calculated Priority (CalcPriority) is the sequence number generated for a forecast order if you choose to run the Calculate Sigmoid Priority process. The importance of this forecast order in relation to other forecast orders. A value of 0 is most important and higher values are less important. The valid values for CalcPriority is 0 or greater.

ConsumedQty The total number of SKU units in this order that have been consumed through forecast adjustment/consumption.

DmdType


FcstOrder

The Generate Forcast Order process converts the plan ship demands placed on the Interface SKU as independent demand and converts them into forecast orders. In order to peg to the independent demands of both the DRP SKUs (SKU: ReplenType 1) and the Interface SKU (SKU: Replentype 4), the Interface SKU’s demand should be separated from the normal forecast demand. Also while using aggregate SKU functionality, the lower level demands (Style/Color/Size) are aggregated at aggregate SKU (Style/Color) level by Generate Forecast Order process. Also the aggregate SKU demand should be separated from the normal forecast demand.

This is done by setting the DmdType column value as follows:

• 1: Time Phased Forecast

• 2: Interface SKU Demand

• 3: Aggregate SKU Demand

Dur The bucket duration for which the forecast order was generated.

ExpDate The requirement expiration date of the forecast order. The expiration date will be populated for the forecast order, which are converted from plan shipments/firm plan shipments and in transit-outs.

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

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

MaxEarlyDur The limit on how early this forecast order may be met. The Calculate Master Plan or process will not try to find supply that will result in meeting this order earlier than:

FcstOrder:NeedDate (on page 143) - FcstOrder:MaxEarlyDur (on page 142)

The system sets MaxEarlyDur equal to the SKUDemandParam:FcstMeetEarlyDur during the execution of Generate Forecast Orders process.


IPO


ESP (MAP and Deep Tree)

Limit on how early this forecast order may be met. The Generate Master Plan or process will not try to find supply that will result in meeting this order earlier than FcstOrder:NeedDate (on page 143) - FcstOrder:MaxEarlyDur (on page 142).

The system sets MaxEarlyDur equal to the SKUDemandParam:FcstMeetEarlyDur when the Generate Forecast Orders process is run.


MaxLateDur The limit on how late this forecast order may be met. The Calculate Master Plan process will not try to find supply that will result in meeting this order later than:

FcstOrder:NeedDate (on page 143) + FcstOrder:MaxLateDur (on page 142)


FcstOrder

The system sets MaxLateDur equal to the SKUDemandParam:FcstMeetLateDur during the execution of Generate Forecast Orders process. Valid values are 0 or greater.

IPO


ESP

ESP

Limit on how late this forecast order can be met.

The ESP solvers do not try to find supply to meet the forecast order later than FcstOrder:NeedDate (on page 143) + FcstOrder:MaxLateDur. When the Generate Forecast Orders process is run, this value is set to the SKUDemandParam:FcstMeetLateDur value.

The valid values are 0 or greater values.

NeedDate The date and time when this order needs to be shipped. The valid values are date/time and cannot be blank.


Priority This value indicates the importance of this forecast order in relation to all other forecast orders. The Calculate Master Plan process (Master Planning) or Generate Master Plan process (ESP) uses this priority when determining which demand to satisfy first.

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 forecast priority has been set for this SKU. The Calculate Sigmoid Priority process uses the priority (Default Forecast Order Priority) value set on its process page as the default priority.

PrioritySeqNum The sequence number generated for a forecast order if you choose to run the Calculate Rules Based Priority (Master Planning) / Run Rules Based Optimization (Supply) process.

Project JDA Supply uses this column to read the project code that is used by the matched sets logic in the Perform 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 total number of units of the SKU specified by this order. This is the quantity after the forecast adjustment/consumption logic is applied.

SeqNum The sequence number generated for a forecast order when you run the Generate Forecast Orders process.

SupersedeSw Switch that indicates which forecast order can be superseded.

• Y – Can be superseded


FcstOrder

• N – Cannot be superseded.


FcstOrderStatus

FcstOrderStatus Table included with: Fulfillment, Master Planning, Supply, Flowcasting, Enterprise Supply Planning


CalcMargin ESP (LPOPT) FLOAT

CalcRevenue ESP (LPOPT) FLOAT DmdPlanTime MP INTEGER ExpDate MP DATETIME 01/01/1970 HasExceptionSw MP, Supp, ESP BOOLEAN 0

Item 2 FF, MP, Supp, Flowcasting, ESP

TEXT

Loc 3 FF, MP, Supp, Flowcasting, ESP

TEXT

ProcessSeqNum MP, Supp INTEGER

SchedDate FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970)

SchedQty FF, MP, Supp, Flowcasting, ESP

DECIMAL 0

SchedStatus FF, MP, Supp, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4,5,6,7,8,9, and 10

SeqNum 1 FF, MP, Supp, Flowcasting, ESP

INTEGER

Table description The forecast order status record is updated by the following processes:

• Calculate Master Plan (Master Planning) or Generate Master Plan (ESP): This process updates the forecast order status of SKUs.

• Generate Supply and Demand Links based on Priority: When this process is run, it deletes existing FcstOrderStatus records for the selected SKUs and creates records in this table that correspond to the current supply and demand picture for SKUs based, on the scope you select in the process page. In the case of Master Planning SKUs it overwrites the status created by the Calculate Master Plan process. In the case of ESP SKUs it overwrites the status created by the Generate Master Plan process.

Column descriptions CalcMargin ESP (LPOPT)

For this forecast order, this value is calculated as Revenue - Total cost of supply.


FcstOrderStatus

CalcRevenue ESP (LPOPT)

Revenue generated from meeting this forecast order.

DmdPlanTime Time elapsed in milliseconds to process a demand. If the time taken to process a demand is less than a millisecond then it is reported as zero.

ExpDate The requirement expiration date of forecast order.

HasExceptionSw This switch is YES when a plan exception has been generated for this forecast order.

Item The item associated with this order.

Loc The location associated with this order.

ProcessSeqNum The sequence number generated for a forecast order by the Calculate Master Plan process.

SchedDate The date and time when this order is scheduled to be shipped.

SchedQty The quantity that is satisfied by the supply. Only for SchedStatus of 4 (Partially Met) and 5 (Not Met) will SchedQty be different from the Qty. The SchedQty will be equal to the Qty when their are no supply restrictions.

SchedStatus Scheduling Status of Order (SchedStatus) is the option that indicates whether the quantity (Qty) of this demand order has been met, was met but not by the date needed (NeedDate), was partially met, or was entirely not met.

• 1: Met

This demand order will be satisfied by the supply on or before the needed ship date (ShipDate). The planned ship date on this order (SchedDate) is before the needed ship date (ShipDate) only when the order has been satisfied out of inventory, otherwise it will be considered to be Met Early (2).

• 2: Met Early

This demand order will be satisfied by the supply before the needed ship date (Shipdate) from a supply other than inventory.

• 3: Met Late

This demand order will be satisfied by the supply, but after the needed ship date (NeedDate). The planned ship date on this order (SchedDate) is after the needed ship date (NeedDate).


Only part of the quantity of this demand order will be satisfied by the supply. The quantity (FcstOrder:Qty) minus the scheduled quantity (SchedQty) reflects the quantity of this demand order that is not satisfied. Use the OrderLink table to locate the orders supplying this demand order to determine how much of the quantity is supplied.

• 5: Not Met

This demand order will NOT be satisfied, in whole or in part, by the supply.


FcstOrderStatus



The customer order is met on or before the needed ship date (ShipDate) by Plan Arrival.



At least one order line item is satisfied before the needed ship date (ShipDate) by Plan Arrival.



At least one order line item will be satisfied after the needed ship date (ShipDate) by Plan Arrival. That is, the scheduled shipping date (SchedDate) is after the needed shipping date (ShipDate).



At least one order line item has a SchedStatus of 10 (Met Partially). Only part of the quantity of that order line item is satisfied by the Plan Arrival. You can determine how much of the order line item is not satisfied by using this calculation:




SeqNum The unique sequence number stored in FcstOrder table.


ImpDepDmdStatic

ImpDepDmdStatic Table included with: Master Planning, Inventory Policy Optimization, Enterprise Supply Planning


Item 8 MP, IPO, ESP TEXT

Loc 1 MP, IPO, ESP TEXT NeedDate 7 MP, IPO, ESP DATETIME TRUNC(

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

Parent 2 MP, IPO, ESP TEXT ' ' ParentExpDate 4 MP, IPO, ESP DATETIME TRUNC

(TO_DATE('01011970', 'MMDDYYYY'))

ParentSchedDate

6 MP, IPO, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

Qty MP, IPO, ESP DECIMAL 0 SeqNum 5 MP, IPO, ESP INTEGER StartDate 3 MP, IPO, ESP DATETIME TRUNC


Table description Each row in this table represents an imported dependent demand. You can only import dependent demand for scheduled receipts.

ESP (LPOPT and MAP)

Each row represents the dependent demands details of an alternate BOM component.

Column descriptions Item The subordinate item on which the dependent demand is being placed.

Loc The location of the subordinate item or scheduled receipt to which the dependent demand applies.

NeedDate The date and time when this demand needs to be met.

Parent The parent of the associated subordinate item or scheduled receipt item.

ParentExpDate The expiration date of the related scheduled receipt. This column only needs to be populated for referential integrity. It is not used for any calculations.


ImpDepDmdStatic

ParentSchedDate The date of the related scheduled receipt.

Qty The scheduled dependent demand for this item from the specified parent during the indicated period of time.

ESP (LPOPT and MAP)

This value is recalculated when the Generate Master Plan process if run.

SeqNum The sequence number of the related scheduled receipt.

StartDate The starting point of the time interval associated with the data in this row.


ImpResLoadDetail

ImpResLoadDetail Table included with: Master Planning, Enterprise Supply Planning



ExpDate 2 MP, ESP DATETIME TRUNC (TO_DATE('01011970', 'MMDDYYYY'))

Item 4 MP, ESP TEXT

LoadQty MP, ESP DECIMAL 0 Loc 5 MP, ESP TEXT Res 6 MP, ESP TEXT SchedDate 1 MP, ESP DATETIME SeqNum 8 MP, ESP INTEGER StartDate 7 MP, ESP DATETIME TRUNC


StepNum ESP INTEGER 0

WhenLoaded 3 MP, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

Table description Each row in this table describes the imported load on a resource caused by a single supply order (Scheduled Receipt) in a single planning bucket.

ESP (LPOPT and MAP)

Each row describes the load on an alternate resource, caused by a scheduled receipt.

Column descriptions ExpDate The expiration date used to link to the related scheduled receipt.

Item The item of the scheduled receipt causing the load on this resource.

LoadQty The total load on the resource, in terms of the capacity units of the resource. The capacity of the resource is specified in the production capacity calendar (Res:Cal) in terms of the same unit of measure.

ESP (LPOPT and MAP)

This value is recalculated when the Generate Master Plan process is run.

Loc The location of the scheduled receipt whose load is described in this row.


ImpResLoadDetail

Res The resource whose load is associated with this row.

SchedDate The SchedDate of the related scheduled receipt.

SeqNum This column is populated by the user during the import of resloaddetail to distinguish between multiple resloaddetail records that are for the same SKU and have the same SchedDate and StartDate combinations, but different quantities. Otherwise, this column can be left at its default of 0.

StartDate The start date associated with the resloaddetail.

StepNum ESP (LPOPT and MAP)

This field is used to identify the production step to which the alternate resource, whose resource load details are defined in this table, is associated.

WhenLoaded The date and time of the load on the resource.


IndDmdLink

IndDmdLink Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning


DmdItem 1 FF, MP, Flowcasting, ESP

TEXT

DmdLoc 2 FF, MP, Flowcasting, ESP

TEXT

DmdNeedDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

DmdNeedQty FF, MP, ESP DECIMAL

DmdPegQty FF, MP, Flowcasting, ESP

DECIMAL 0

DmdSchedDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

DmdSubType FF, Flowcasting, ESP

INTEGER 1,2,3,4,5

DmdSeqNum 6 FF, MP, Flowcasting, ESP

INTEGER 0

DmdType 7 FF, MP, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4,5,6,7,8, 9, and 10

InhandlingCost ESP (LPOPT) FLOAT InvCarryingCost ESP (LPOPT) FLOAT Loc FF, MP,

Flowcasting, ESP

TEXT ' '


TEXT ' '

OuthandlingCost ESP (LPOPT) FLOAT

ProdCost ESP (LPOPT) FLOAT PurchCost ESP (LPOPT) FLOAT RelatedSeqNum 3 FF, MP,

Flowcasting, ESP

INTEGER


DATETIME 01/01/1970

SourcingCost ESP (LPOPT) FLOAT


IndDmdLink


SupplyAvailDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

SupplyItem FF, MP, Flowcasting, ESP

TEXT ' '

SupplyLoc FF, MP, Flowcasting, ESP

TEXT ' '

SupplyPegQty FF, MP, Flowcasting, ESP

DECIMAL 0

SupplySeqNum FF, MP, Flowcasting, ESP

INTEGER 0

SupplyType FF, MP, Flowcasting, ESP

OPTION_NUMBER

1,2,4,5,6,7,8,9, 10,11,12,13,14, 18

Table description This table associates independent demand orders (forecast, customer orders, and safety stock orders) with all the supply orders that satisfy some or all of their demand.

When planned orders in the database are updated by anything other than Calculate Master Plan or the Generate Demand and Supply Links process, the data of this table become invalid. You cannot edit the data of this table.

Column descriptions DmdItem The independent demand item.

DmdNeedDate The date and time when this independent demand order is needed.

DmdNeedQty The independent demand quantity needed at this SKU.

DmdPegQty Demand Peg Quantity (DmdPegQty) is the quantity of the independent demand that can be fulfilled as a result of the supplying order.

DmdPegQty is valid values 0 or greater.

DmdSchedDate Demand Scheduled Date (DmdSchedDate) is the date when the independent demand order is needed.

DmdSeqNum Demand Sequence Number (DmdSeqNum) is the sequence number associated with this independent demand order.

DmdSubType JDA Enterprise Supply Planning Reference Guide 153 © 2014 JDA Software Group, Inc.- Confidential

IndDmdLink

The demand subtype is populated only when the RecShip: Type is set to 10 (Distribution Demand Recommended Shipment). This indicates the type of recommended shipment. For information on recommended shipment types, refer RecShip: Type.

Note: This column is not applicable for Master Planning.

DmdType Note: The IndDmdLink table supports only those demands that have a DmdType value of 1, 2, and 3.

The type of demand (and the associated table):

• 1: Customer Order (CustOrder table)

The demand order maps to the CustOrder.

• 2: Forecast (FcstOrder table)

Forecast demand order. The demand order maps to the FcstOrder.

• 3: Safety Stock Requirement (StockOrder table)

Safety stock demand order. The demand order maps to the StockOrder.

• 4: Dependent Demand Plan Order (PlanOrder table)

The DmdOrder maps to the Dependent Demand Plan Order.

• 5: Dependent Demand Firm Plan Order (PlanOrder table)

The DmdOrder maps to the Dependent Demand Firm Plan Order.

• 6: Dependent Demand Scheduled Receipt (SchedRcpts table)

The DmdOrder maps to the Dependent Demand Scheduled Receipt.

• 7: Distribution Demand Plan Arrival (PlanArriv table)

The DmdOrder maps to the Distribution Demand Plan Arrival.

• 8: Distribution Demand Firm Plan Arrival (PlanArriv table)

The DmdOrder maps to the Distribution Demand Firm Plan Arrival.

• 9: Distribution Demand InstransitOut

The DmdOrder maps to the Distribution Demand InstransitOut.

• 10: Distribution Demand Recommended Shipment (RecShip table)

The DmdOrder maps to the Distribution Demand Recommended Shipment.

InhandlingCost The total handling cost for receiving the pegged quantity, at a location.

InvCarryingCost The total inventory carrying cost.

Loc The independent demand location.

OrderID Unique identifier of the line item defined in this row. This is needed to identify customer orders. OrderID is also populated for the stock orders of perishable SKUs. This is needed typically when the single stock order demand is pegged to multiple supplies due to supply shelf life. When single stock order is pegged to multiple supplies, the OrderID for each row is incremental.

For non-perishable SKUs, OrderID is populated for customer orders only. Whereas for perishable SKUs, apart from customer orders OrderID is populated for virtual stock orders.


IndDmdLink

OuthandlingCost The total handling cost for shipping the pegged quantity, from a location.

ProdCost The total production cost of the pegged quantity.

PurchCost The total purchase cost of the pegged quantity.

RelatedSeqNum Related Sequence Number (RelatedSeqNum) is the same supply order that is linked to the independent demand order several times, typically when the bills of material have more than one entry of the same SKU. RelatedSeqNum uniquely identifies each link.

Valid values for RelatedSeqNum are 0 or greater.

ShipDate The ship date of the associated customer order.

SourcingCost The total distribution cost of the pegged quantity.

SupplyAvailDate The available date of the supply order that is linked to the independent demand order.

SupplyItem The individual item of the supply order that is linked to the independent demand order.

SupplyLoc The location of the supply order that is linked to the independent demand order.

SupplyPegQty Supply Peg Quantity (SupplyPegQty) is the quantity of the supply order that is linked to the independent demand order.

Valid values for SupplyPegQty are 0 or greater.

SupplySeqNum The sequence number of the supply order that is linked to the independent demand order.

SupplySubType The supply subtype is populated only when the SupplyType (on page 155) is set to 4 or 10. The SupplySubType indicates the type of recommended shipment. For information on recommended shipment types, refer RecShip: Type.

Note: This column is not applicable for Master Planning.

SupplyType The type of supply:


IndDmdLink:SupplyOrder = PlanArriv:Dest


IndDmdLink:SupplyOrder = PlanOrder

• 4: Recommended Arrival (RecShip table)

IndDmdLink:SupplyOrder = RecShip:OrderID

IndDmdLink:Loc (on page 154) = RecShip:Dest


IndDmdLink

Note: This option is not applicable to Master Planning.

• 5: Intransit In (VehicleLoadLine table)

IndDmdLink:SupplyOrder = VehicleLoadLine:LoadID

IndDmdLink:Item = VehicleLoadLine:Item

IndDmdLink:Loc (on page 154) = VehicleLoad:Dest (for the parent Vehicle Load, where VehicleLoadLine:LoadID = VehicleLoad:LoadID)


IndDmdLink:SupplyOrder = SchedRcpts:SchedRcptsID

• 7: Inventory (Inventory table; Type = 1)

IndDmdLink:Item = Inventory:Item

IndDmdLink:Loc (on page 154) = Inventory:Loc

• 8: Safety Stock (Inventory table; Type = 2)

IndDmdLink:Item = Inventory:Item

IndDmdLink:Loc (on page 154) = Inventory:Loc


IndDmdLink:SupplyOrder = PlanOrder


IndDmdLink:SupplyOrder = RecShip:OrderID

IndDmdLink:Loc (on page 154) = RecShip:Dest

Note: This option is not applicable to Master Planning.


IndDmdLink:SupplyOrder = PlanArriv:Dest


IndDmdLink:SupplyOrder = PlanPurch


IndDmdLink:SupplyOrder = PlanPurch


IndDmdLink:SupplyOrder = PurchOrder

• 18: Superseded Supply


IndDmdView

IndDmdView Database view

Table description Each Independent Demand View row defines one independent demand—either a customer order, a forecast order, or a stock order.

Column descriptions Most Independent Demand columns contain data taken directly from the CustOrder, FcstOrder, StockOrder, CustOrderStatus, FcstOrderStatus, and StockOrderStatus tables. The following table lists each column whose data is displayed in IndDmdView.

Margin, Priority, and Revenue values are calculated as explained in this table.

For other columns, the table shows the actual value, in italics, that will appear in the column.

Column in Independent Demand View

Source table Column in source table, or calculations used, or actual value

AvailDate CustOrder FcstOrder

Default date of 1/1/1970 Note: AvailDate is not applicable to CustOrder and FcstOrder tables.

StockOrder AvailDate

CalcMargin CustOrderStatus FcstOrderStatus

CustOrderStatus:CalcMargin FcstOrderStatus:CalcMargin

CalcRevenue CustOrderStatus FcstOrderStatus

CustOrderStatus:CalcRevenue FcstOrderStatus:CalcRevenue

CalcPriority CustOrder FcstOrder StockOrder

CalcPriority

ConsumedQty CustOrder 0

FcstOrder ConsumedQty

StockOrder 0 Cost CustOrder Cost

FcstOrder SKUDemandParam:IndDmdUnitCost × FcstOrder:Qty

StockOrder SKUDemandParam:IndDmdUnitCost × StockOrder:Qty

Cust CustOrder (blank)

DmdType CustOrder 1

FcstOrder 2

StockOrder 3


IndDmdView



ExtOrderID CustOrder OrderID

FcstOrder (blank)

StockOrder (blank) FcstSeqNum CustOrder 0

FcstOrder SeqNum

StockOrder 0 FcstSw CustOrder FcstSw

FcstOrder 1 (Forecasted order)

StockOrder 0 (Not a forecasted order) HeaderExtRef CustOrder HeaderExtRef

Note: CustOrder:HeaderExtRef must match CustOrderHeader:ExtRef for this userview to work properly.

FcstOrder 0

StockOrder 0 Item CustOrder

FcstOrder StockOrder

Item

Loc CustOrder FcstOrder StockOrder

Loc

Margin CustOrder

Calculated as follows: • If CustOrder:Margin ≠ –1:

IndDmdView:Margin = CustOrder:Margin

Note: Negative CustOrder:Margin values other than –1 are invalid.

• If CustOrder:Margin = –1 and CustOrder:Revenue ≠ –1:

IndDmdView:Margin = CustOrder.Revenue - (SKUDemandParam.IndDmdUnitCost × CustOrder.Qty)

• If CustOrder:Margin = –1 and CustOrder:Revenue = –1:

IndDmdView:Margin = SKUDemandParam.IndDmdUnitMargin × CustOrder.Qty

FcstOrder SKUDemandParam:IndDmdUnitMargin × FcstOrder:Qty Margin


IndDmdView



StockOrder SKUDemandParam.IndDmdUnitMargin × StockOrder.Qty

MaxLateDur CustOrder FcstOrder StockOrder

MaxLateDur

NeedDate CustOrder ShipDate

FcstOrder NeedDate

StockOrder NeedDate Priority CustOrder Uses the first non-zero value from the

following columns, or 0 if all these values are 0: • CustOrder:Priority

• CustOrderHeader:Priority

• Cust:Priority

• SKU:Priority


Priority

PrioritySeqNum CustOrder FcstOrder StockOrder

PrioritySeqNum

ProcessSeqNum CustOrder CustOrderStatus:ProcessSeqNum

FcstOrder FcstOrderStatus:ProcessSeqNum

StockOrder StockOrderStatus:ProcessSeqNum Qty CustOrder


Qty

Revenue CustOrder • If CustOrder:Revenue ≠ –1:

IndDmdView:Revenue = CustOrder:Revenue

Note: Negative CustOrder:Revenue values other than –1 are invalid.

• If CustOrder:Revenue = –1:

IndDmdView:Revenue = (SKUDemandParam:IndDmdUnitMargin + SKUDemandParam:IndDmdUnitCost) × CustOrder:Qty


IndDmdView



FcstOrder (SKUDemandParam:IndDmdUnitCost + SKUDemandParam:IndDmdUnitMargin) × FcstOrder:Qty

StockOrder (SKUDemandParam:IndDmdUnitCost + SKUDemandParam:IndDmdUnitMargin) × StockOrder:Qty

SchedDate CustOrder FcstOrder StockOrder

CustOrderStatus:SchedDate FcstOrderStatus:SchedDate StockOrderStatus:SchedDate

SchedQty CustOrder FcstOrder StockOrder

CustOrderStatus:SchedQty FcstOrderStatus:SchedQty StockOrderStatus:SchedQty

SchedStatus CustOrder FcstOrder StockOrder

CustOrderStatus:SchedStatus FcstOrderStatus:SchedStatus StockOrderStatus:SchedStatus A SchedStatus = 6 (Unplanned) is available in the IndDmdView table. This status refers to all orders which do not have a record in their corresponding status tables. For more information on other SchedStatus options, refer to CustOrderStatus:SchedStatus, FcstOrderStatus:SchedStatus, and StockOrderStatus:SchedStatus columns.

SeqNum CustOrder 0

FcstOrder SeqNum

StockOrder SeqNum SSSeqNum CustOrder 0

FcstOrder 0

StockOrder SeqNum


Inventory

Inventory Table included with: Fulfillment, Master Planning, Supply, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


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

DATETIME 01/01/1970

ExpDate 4 FF, MP, Supp, IPO, Flowcasting

DATETIME 01/01/1970


TEXT


TEXT

NeedDate MP DATETIME 01/01/1970

OrderSeqNum FF, MP, Supp, ESP

SEQUENCE 0

OrderType Supp INTEGER 135 Project 5 FF, MP, Supp,

IPO, ESP TEXT ' '

Qty FF, MP, Supp, IPO, Flowcasting, ESP

DECIMAL 0

SftyFct FF, Supp DECIMAL 0 SupplyID FF UPPER_TEX

T

Store 6 FF, MP, Supp, IPO, ESP

TEXT ' '

UsageSw Supp BOOLEAN 0

Table description Each row in this table contains on-hand values or future supplies for an SKU. This table may contain multiple on-hand inventory supplies for the same SKU. Each inventory supply might represent, for example, a separate inventory store in the manufacturing plant, or different expiration dates for date-sensitive inventory. While generating a plan, these inventory quantities are consumed to meet demand.

IPO

IPO only uses this table when the replenishment plan cost model is selected. If another cost model is selected, this table is not used.


Inventory

Column descriptions AvailDate The date and time when this supply quantity is available to be used as supply.

Supply


ExpDate The date on which the date-sensitive, on-hand inventory expires.

IPO, Master Planning and Supply


Item The item associated with this quantity.

Loc The location associated with this quantity.

NeedDate The date and time when this inventory is needed to meet demand.

OrderSeqNum The unique identifier automatically generated by the system.

Master Planning

This sequence number identifies the inventory in the Orderlink table. When the OrderLink table or the IndDmdLink table contains a row with the SupplyType=7, the SupplySeqNum refers to the Inventory:OrderSeqNum.

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


Fulfillment, IPO, Master Planning and Supply


Qty The total number of units of the SKU.

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.

SftyFct The safety stock factor.

SupplyID Represents a unique ID for the supply that is used by the Dynamic Allocation logic. JDA Enterprise Supply Planning Reference Guide 162 © 2014 JDA Software Group, Inc.- Confidential

Inventory

Store Description of where this quantity is stored, such as a rack, a row, or a bin code. This column can also contain the name of a store, within a location.

Fulfillment, IPO and Master Planning


UsageSw • If UsageSw is set to 1, JDA Supply will use this inventory record.

• If UsageSw is set to 0, JDA Supply will not use this inventory record.


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 Enterprise Supply Planning Reference Guide 165 © 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 168) is not an integer; it should be set to the number of significant decimal places in Item:DynDepQty (on page 168).

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 166) 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 Enterprise Supply Planning Reference Guide 172 © 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 174).

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 174) instead. If that is also blank, the system uses SKU:OHPost if it has a value. If not, it uses the current system date.


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.


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

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


Loc:OHPost (on page 174) 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 (on page 204)) whose PlanOrder:SchedDate (on page 209) 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.


LPDmdBands

LPDmdBands Table included with: Enterprise Supply Planning


DmdBandVal ESP (LPOPT) DECIMAL 100

Layer ESP (LPOPT) STRING SeqNum ESP (LPOPT) INTEGER

Table description This table defines the fair-share percentage associated with the demand bands into which a layer is split.

Column descriptions DmdBandVal Demand band value is the supply percentage that must be allocated for a demand band layer.

Layer Layer name.

SeqNum An identifier for a demand band within a layer.


LPLayer

LPLayer Table included with: Enterprise Supply Planning


DmdPriorityEnd ESP (LPOPT) DECIMAL

DmdPriorityStart ESP (LPOPT) DECIMAL Layer ESP (LPOPT) STRING Priority ESP (LPOPT) INTEGER

Type ESP (LPOPT) STRING(1) 1, 2 1

Table description This table contains the definitions of a layer and the demand priorities associated with a layer.

• DmdPriorityStart and DmdPriorityEnd must not be defined such that an independent demand priority falls across multiple layers. This scenario may lead to unexpected results such as the independent demand being considered in one of the layers only.

• DmdPriorityStart and DmdPriorityEnd must include all prioritized independent demands. The independent demand is not planned if its priority does not fall in any layer. In such cases, adding the objective Maximize Demand Satisfaction for all layers to the objective set may resolve the issue.

Column descriptions DmdPriorityEnd The priority number till which demands are grouped into this layer.

DmdPriorityStart The priority number starting from which demands are grouped into this layer.

Layer Layer name.

Priority Layer priority.

Type Specifies if the demands in the layer can be backlogged. If the demands can be backlogged, this column value is 2. If the demands are to be shorted, this column value is 1.


MSE

MSE Table included with: Fulfillment, Inventory Policy Optimization, Master Planning, Flowcasting, Enterprise Supply Planning


ADJBias IPO FLOAT 0

ADJCV IPO FLOAT 0

CoeffVar FF, MP, IPO, Flowcasting, ESP (Deep Tree)

FLOAT >=0 0


DATETIME


TEXT


TEXT

MSE FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DECIMAL 0.000000

MSEBias FF, MP, IPO, Flowcasting, ESP (Deep Tree)

FLOAT 50

Table description Stores time-phased mean squared error (MSE) of demand values for a SKU. This table is used both as an input and output table.

As an input table, it stores user-specified time-phased or time-invariant MSE values from an external system.

As an output table, it stores a single time invariant MSE value resulting from the calculation of the Calculate Statistical Safety Stock process with the SKU MSE option selected.

Column descriptions ADJBias The Adjusted Bias is the difference between the Average Historical Sales from the Average Historical Forecast with respect to the Adjusted Mean,where Adjusted Mean is the maximum of the Mean Historical sales and the Mean Historical Forecast.

ADJCV


MSE

The Adjusted Coefficient of Variation is the value obtained from the variance of the Historical Sales and the Adjusted Mean, where Adjusted Mean is the maximum of the Mean Historical sales and the Mean Historical Forecast.

CoeffVar Coefficient of Variation. Calculated as:

Note: If this column is greater than 6, the demand is considered to be very unstable.

Eff Effective Date (Eff) is the date and time at which the MSE defined in this row becomes active.

Item The item associated with the SKU for which an MSE is defined in this row.

Loc The location associated with the SKU for which an MSE is defined in this row.

MSE Mean Squared Error (MSE) is the value of the mean squared error of demand. This value is based on the rule specified in the CalcMSERule column of the SKUSafetyStockParam table.

Note: When time-phased MSEs are imported from an external system, care must be taken to ensure that the MSEs populated in this table are prorated over the value specified in SKUSafetyStockParam:FcstDur. The Calculate Statistical Safety Stock process interprets user-specified MSEs (in the event that you input MSEs) as MSE of demand over FcstDur. So make sure you populate FcstDur with the appropriate value so that the system properly interprets the MSE that you have defined.

Fulfillment

See Working with statistical safety stock based on customer service targets in the Inventory Management in JDA Fulfillment section of the JDA Fulfillment OnLine Expert for information on this value.

MSEBias The percentage of occurrence where forecasted demand values are greater than the actual demand values. (In a random demand situation, there is an equal possibility of the forecast being greater or lesser than the actuals).


Network

Network Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning



ArrivCal FF TEXT ' '

AutoApprovalSw FF OPTION_NUMBER 0

Carrier FF, MP, Flowcasting

TEXT ' '

CovDurAdjTolerance

FF DURATION 0

Dest 3 FF, MP, IPO, Flowcasting, ESP

TEXT

Distance PSO DECIMAL 0 DistanceUOM PSO OPTION_NUMBER 0

FwdBuyActiveDur

FF DURATION 7D

FwdBuyEffectPct FF DECIMAL 100 LaneGroupID FF,

Flowcasting TEXT ' '

LoadBuildAdjDownTolerance

FF DECIMAL 100

LoadBuildAdjUpTolerance

FF DECIMAL 999999

LoadBuildRule FF OPTION_NUMBER 1

LoadMinimumRule

FF OPTION_NUMBER 1

LoadSeqRule FF OPTION_NUMBER 1 LoadTime FF, MP, IPO,

Flowcasting DURATION 0

LoadTolerance FF, Flowcasting

DECIMAL 0

LookAheadDays FF, Flowcasting

DURATION 0

MustGoDays FF, Flowcasting

DURATION 0

OrderReviewCal FF UPPER_TEXT PrimaryLSDur FF,


PrimaryLSRule FF, Flowcasting

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

1

ProjOrderDur FF DURATION 43200


Network



Rank FF, Flowcasting

INTEGER 1

RatePerCWT FF, Flowcasting

DECIMAL 0.0

RIOSelectSw FF BOOLEAN 0

RIOMinCovDur FF DURATION 0

RIOMaxCovDur FF DURATION

OrderCost FF DECIMAL 0 SecondaryLSRule

FF, Flowcasting

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

1

ShipCal FF TEXT

SKUPerPalletSw FF BOOLEAN 0,1 0 Source 1 FF, MP, IPO,

Flowcasting, ESP

TEXT

TransCal FF, MP, Flowcasting

TEXT ' '

TransLeadTime FF, MP, IPO, Flowcasting, ESP

DURATION 0

TransLeadTimeSD

IPO DURATION 0

TransMode 2 FF, MP, IPO, Flowcasting, ESP

TEXT

TransModeMinRule

FF, Flowcasting

OPTION_NUMBER 1,2 1

TransModeName FF, MP, Flowcasting, ESP

TEXT ' '

UnloadTime MP, IPO DURATION 0 UseAltTransModeSw

FF, Flowcasting

BOOLEAN 1

VendorMinRule FF, Flowcasting

OPTION_NUMBER 1,2 1

Table description Each row in this table defines information about a distribution network — a lane between two locations, using one mode of transportation. The Network table defines all possible connections between locations for each of your transportation modes. A row must be defined in this table for each source, destination, and transportation mode (TransMode) combination.

Fulfillment


Network

The Build Transportation Loads (BTL) process and Load Manager tool use this table to group recommended shipments into feasible vehicle loads.

Fulfillment/Order Optimization uses this table to group the ordered items together from one vendor source location into purchase orders.

Note: Each sub-component of Fulfillment uses only some of the columns in this table.

Column descriptions ArrivCal The Arrival Calendar (Cal: Type: 6) attached to this network.

When the Optimize Orders process is generating arrivals into a destination in the network, it checks the destination’s arrival calendar to be sure that it is open at the date/time when the arrival is scheduled. If not, the process changes the scheduled arrival for an earlier date/time when the arrival calendar is open. If there is none, the process tries to schedule the arrival at the next date/time.

This column is not used by Fulfillment/Distribution or Fulfillment/Deployment.

AutoApprovalSw • Determines whether an order is approved during the Optimize Orders process or manually by the

user.

• 0 : No. The order is not approved when the Optimize Orders process is run. The order is approved manually by the user.

• 1 : Yes. The order is automatically approved during the Optimized Orders process.

Note: The orders are only approved automatically when they are in Due or Forced Due status. See Order Optimization .

Carrier The name of the carrier associated with the transportation mode.

You can define weekend travel patterns for a carrier with the Carrier_Weekend_Info environment variable. Build Transportation Loads process will take these travel patterns into account when it calculates the ship date of a load (VehicleLoad:ShipDate). Refer to the information on environment variables in the Supply Chain Planning and Optimization Installation/Administration Guide for more information.

CovDurAdjTolerance When the Optimize Orders process arrives at the OrderSKU: AdjSKUCovDate, the CovDurAdjTolerance is the tolerance level within which it looks for closest “Forced/ AsNeeded” date, where “Forced” takes the first priority.

That is, the process first looks for “Forced” ArrivDate closest to the (ArrivDate + SKUPlanningParam: DRPCovDur) that is within the Network:CovDurAdjTolerance which is also greater than OrderSKU: ArrivDate. If a “Forced” ArrivDate is found, it is used as OrderSKU: AdjSKUCovDate. If not, it looks for “As Needed” ArrivDate closest to the (ArrivDate + SKUPlanningParam: DRPCovDur) that is within the Network: CovDurAdjTolerance which is also greater than OrderSKU: ArrivDate. If “As Needed” ArrivDate is found, it is used as OrderSKU: AdjSKUCovDate.

Dest Destination location associated with the link defined in this row. Valid values for Dest are an existing location from the Loc table or blank.

Distance This column stores the geographic coordinates which are calculated by Distance Calculation process.

The Distance Calculation process computes the nearest (crow fly) distance between two locations based on latitude and longitude and populates this column with the computed distance. JDA Enterprise Supply Planning Reference Guide 182 © 2014 JDA Software Group, Inc.- Confidential

Network

DistanceUOM The unit of measure applied to all distance values.

FwdBuyActiveDur The Forward Buy Active Duration (FwdBuyActiveDur) is the number of days prior to the DealSKU: Disc when the Optimize orders process will calculate the FwdBuyDur for a Deal.

FwdBuyEffectPct The Forward Buy Effect Percentage (FwdBuyEffectPct) is the percentage of the optimum FwdBuyDur calculated for a Deal. Please refer to the Forward Buy for further details.

LaneGroupID The unique ID corresponding to this lane group. This is used by the BTL process and Load Manager tool when working with multi-pickup loads.

LoadBuildAdjDownTolerance This is the preferred percentage decrease from current OrderTotal:Qty when adjusting loads. This tolerance is used by the load building solution of the Optimize Orders process when it tries to adjust the OrderTotal:Qty to the maximum number of loads.

LoadBuildAdjUpTolerance This is the preferred percentage increase from current OrderTotal:Qty when adjusting loads. This tolerance is used by the load building solution of the Optimize Orders process when it tries to adjust the OrderTotal:Qty to the minimum number of loads.

LoadBuildRule This rule is used by Order Optimization to determine how to adjust an order to utilize vehicle loads.

• 1 - Split Only

No adjustment is made to the order for vehicle utilization. The SKUs in the order are simply loaded onto as many vehicles as needed.

• 2 - Build To Minimum

When the Build To Minimum rule is specified, the order will be adjusted so that vehicles are fully utilized up to their minimum capacities as defined by the load minimum rule. So, if an unadjusted order requires 1.5 vehicles, the process will determine the adjustment required to fully maximize the load on one vehicle. Then it will determine the adjustment required to meet the minimum load of the second vehicle.

Preference is given to load adjustment that has the smallest percentage deviation from the unadjusted order but is within LoadBuildAdjDownTolerance (on page 183) for the single vehicle load adjustment and LoadBuildAdjUpTolerance (on page 183) for the two vehicle load adjustment.

• 3 - Build To Maximum

When the Build To Maximum rule is specified, the order will be adjusted so that vehicles are fully utilized up to their maximum capacities. So, if an unadjusted order requires 1.5 vehicles, the process will determine the adjustment required to fully maximize the load on one vehicle. Then it will determine the adjustment required to meet the maximum load of two vehicles.

Preference is given to load adjustment that has the smallest percentage deviation from the unadjusted order but is within LoadBuildAdjDownTolerance for the single vehicle load adjustment and LoadBuildAdjUpTolerance for the two vehicle load adjustment.

LoadMinimumRule Order Optimization uses Load Minimum Rule to specify the minimum transmode utilization satisfaction criteria (minimum quantity the vehicle (load) should meet.)

You can set the following options:

• 1 - No Minimums JDA Enterprise Supply Planning Reference Guide 183 © 2014 JDA Software Group, Inc.- Confidential

Network

Use this when you do not want to set any load minimums.

• 2 - Meet only TransMode Minimums

The minimum quantity is met when the OrderTotal.Qty has met the TransModeCap: MinCap. The process looks for enabled Transmode.MinCap greater than zero.

• 3 - Meet Capacity Tolerance only

The minimum quantity is met when the OrderTotal: Qty has met the LoadTolerance (on page 185) The process looks for enabled Transmode:MinCap greater than zero.

• 4 - Meet both TransMode Minimums and Capacity Tolerance

The minimum quantity is met when the OrderTotal:Qty has met both the TransModeCap:MinCap and the LoadTolerance.

Notes:

• When TransModeMinRule is set to 1, the load minimum is considered to be met only when all OrderTotal UOMs qualify in the conditions defined in this column. When TransModeMinRule is set to 2, the load minimum is considered to be met when any one of the OrderTotal UOMs qualify in the conditions defined in this column.

• The load minimum check is done only when the TransModeCap:CheckCapSw is set to 1. This column is not used by Building Transportation Loads.

LoadSeqRule LoadSeqRule column defines the sequence in which the items should be loaded on to VehicleLoads in Order Optimization.

• 1 - Items are loaded in alphabetical order

• 2 - Items are loaded based on need order

Need order is used to determine the order in which the items will be loaded. The items are sorted in the ascending order of the StockLowDate, where StockLowDate is the date when the item’s stock drops below safety stock. The item with the earliest Stock Low Date is the most needed item and thereby, is loaded first.

LoadTime Vehicle Loading Time (LoadTime) is the fixed time required to load the vehicle used for this mode between this source and destination. If the value for Network:TransLeadTime (on page 188) consists only of actual transportation time, you can use LoadTime to allow for additional time that may be required before the vehicle leaves the source.

Fulfillment

If LoadTime is greater than 0 and SKUPlanningParm:PlanLeadTimeRule is not 1, Calculate Plan, Build Transportation Loads, and the Load Manager process add LoadTime to TransLeadTime when calculating the leadtime required for shipments, also taking applicable calendars into account. However, if Sourcing:LoadDur is populated, then this field is not considered.

Master Planning

If a valid resource is specified in OuthandlingRes, Master Planning ignores this value. Instead, it calculates a loading time based on the order quantity.

The algorithm calculates the leadtime required for planned arrivals/shipments as the total of:

• Network:TransLeadTime — transportation time.

• Network:LoadTime — Time required to load the vehicle used for this mode between the source and destination.

• Network:UnloadTime — Time required to unload the vehicle used for this mode between the source and destination.


Network

• Variable portion of loading and unloading times, based on shipment quantities. Specify the rates for loading at the source and unloading at the destination in SourcingRequirement:Rate.

LoadTime is independent of any SKUPlanningParam:BufferLeadTime. If the model specifies a LoadTime, UnLoadTime, TransLeadTime, and BufferLeadTime, then the total lead time for the planned arrival will be:

LoadTime + UnLoadTime + TransLeadTime + BufferLeadTime

LoadTolerance Load Tolerance is used by Build Transportation Loads and Order Optimization and is interpreted as a strictly negative percentage tolerance. A load is considered to meet the capacity tolerance criterion if at least one of the UOM’s utilization is within the load tolerance percentage. For example, if volume and weight are the applicable UOMs in terms of which maximum capacity has been specified, and if the load tolerance is 5%, a load that is 95% full either in terms of volume or weight is said to meet the capacity tolerance criterion.

The algorithm looks at the Load Tolerance percentage defined in this row while evaluating the capacity tolerance criterion. If this field is blank, Build Transportation Loads uses the load tolerance percentage defined in the Build Transportation Loads process options.

LookAheadDays This column is used by the Build Transporataion Loads process to determine which RecShips are look ahead RecShips. All non Must Go RecShips whose RecShip:OrderPlaceDate <= Dispatch Date (Specified in the Build Transporation Load process) + MustGoDays+ LookAheadDays are called as Lookahead RecShips.

If the UseLookAheadSw switch (from the sourcing or Lane Group table)is set to Yes, the algorithm will determine that using look ahead RecShips is allowed and using these lookahead RecShips , it tries to fill the unsatisfied loads to the level where they satisfy the LSRule .

If the LookAhead Days is blank, then BTL process will use the lookahead days value specified on the BTL process page.

MustGoDays A number of days that Build Transportation Loads process uses to define a period of time during which recommended shipments using this transportation mode must leave the source in order to arrive at the destination by the Need Arrive Date (RecShip:NeedArrivDate). The system adds the number of days you specify in this column to the Dispatch Date (the starting date for the load, which you specify on the Build Transportation Loads process page) to define a window; shipments whose RecShip:OrderPlaceDate falls within this window are considered to be MustGo shipments. The Build Transportation Loads process includes at least one MustGo shipment on every load that it creates.

If this column is left blank, the system uses the MustGo duration you specify on the Build Transportation Loads process page.

For more information on MustGo shipments, see Building transportation loads and the Build Transportation Loads process page in the JDA Fulfillment OnLine Expert.

OrderReviewCal The Order Review calendar (Cal:Type 13) attached to this network. For more information on setting up the Order Review calendar, refer Setting up an Order Review Calendar section in the Order Optimization chapter of the JDA Fulfillment OnLine Expert.

PrimaryLSDur The value in the PrimaryLSDur is used by Build Transportation Load process and dictates where PrimaryLSRule applies and where SecondaryLSRule applies. Due to the presence of long lead time items, two different load satisfaction criteria (one near term and the other, for loads that are built 30 days out that do not necessarily require the same stringent criteria) are required.

PrimaryLSRule JDA Enterprise Supply Planning Reference Guide 185 © 2014 JDA Software Group, Inc.- Confidential

Network

The Load Satisfaction Rules define whether loads built by the Build Transportation Loads process are satisfactory or not. Resolution strategies like using look ahead RecShips and alternate transmodes are only used if loads do not meet the load satisfaction criteria. The PrimaryLSRule is the load satisfaction rule used for all loads created by the algorithm whose ship dates fall within the Build Transportation Loads Dispatch Date + PrimaryLSDur. PrimaryLSRule can take 9 values:

• 1 – None

• 2 – Meet Only Network Minimum

• 3 – Meet Only Transmode Minimum

• 4 – Meet only Capacity Tolerance

• 5 – Meet Network Minimum and Transmode Minimum

• 6 – Meet Network Minimum and Capacity Tolerance

• 7 – Meet Transmode Minimum and Capacity Tolerance

• 8 – Meet Network Minimum, Transmode Minimum and Capacity Tolerance

• 9 – Meet Full Capacity

Notes:

• In the case where the PrimaryLSRule specified is 9 (Meet Full Capacity), the Build Transportation Loads process loads the look ahead recommended shipments in a multiple of the specified split quantity (Sourcing:SplitQty), as long as the total load quantity does not exceed the full capacity for any of the units of measure (UOM) defined in TransModeCap:MaxCap.

ProjOrderDur The projected order duration controls the amount of time from the start date that the Project Optimize Orders process should create the order projection.

Rank Used by the Build Transportation Loads process to determine the priority assigned to the transportation mode defined in this row. A value of 1 indicates that the transportation mode is the preferred mode of transportation for this lane. Higher values indicate a lower ranking. When the Build Transportation Loads process builds a load, it selects the preferred transportation mode for the source and destination it is working with. If it cannot fill the load using the preferred mode, it selects the transportation mode with the next highest rank and tries to fill the load using that mode. If it cannot fill a load using any of the transportation modes specified for the source and destination it is working with, it selects the mode with the best fill (based on the Load Tolerance you specify on the Build Transportation Loads process page). The load will have a status of 4 (Not full, not primary transmode).

Valid values for Rank are greater than or equal to 1.

RatePerCWT Value used to calculate the cost of shipping one unit of product from one location to another using this transportation mode.

Transportation cost is one of the factors that Dynamic Deployment considers when it tries to find the lowest cost solution for moving product from alternate sources with a surplus to destinations with a shortage.

If Item:DDSrcCostSw = 0, then transportation cost is calculated as:

OrderCost


Network

The order cost column is used as an input to the Replenishment Interval Optimization process. The order cost includes the fixed costs of placing an order. These can include the cost of the user approving the order, placing the order with the vendor and the costs of processing the invoice for the order when it is paid. This column is only used in the integration with Inventory Optimization.

RIOSelectSw The RIO select switch is the trigger set by the user that will initiate the data transfer for this network’s data when the RIO process is submitted from Replenishment Interval Optimization. This column is only used in the integration with Inventory Optimization.

RIOMinCovDur The RIO minimum coverage duration is the minimum coverage value that can be calculated by the Replenishment Interval Optimization process. If the RIOMinCovDur is set to 3 days then when the RIO process is run, the lowest coverage duration that can be calculated is 3D. This column is only used in the integration with Inventory Optimization.

RIOMaxCovDur The RIO maximum coverage duration is the maximum coverage value that can be calculated by the Replenishment Interval Optimization process. If the RIOMaxCovDur is set to 90 days then when the RIO process is run, the highest coverage duration that can be calculated is 90D. This column is only used in the integration with Inventory Optimization.

SecondaryLSRule The Load Satisfaction Rules define whether loads built by the Build Transportation Loads process are satisfactory or not. Resolution strategies like using look ahead RecShips and alternate transmodes are only used if loads do not meet the load satisfaction criteria. The Secondary LSRule is the load satisfaction rule used for all loads created by the algorithm whose ship dates fall outside the Build Transportation Loads Dispatch Date + PrimaryLSDur. SecondaryLSRule can take 9 values:

• 1 – None

• 2 – Meet Only Network Minimum

• 3 – Meet Only Transmode Minimum

• 4 – Meet only Capacity Tolerance

• 5 – Meet Network Minimum and Transmode Minimum

• 6 – Meet Network Minimum and Capacity Tolerance

• 7 – Meet Transmode Minimum and Capacity Tolerance

• 8 – Meet Network Minimum, Transmode Minimum and Capacity Tolerance

• 9 – Meet Full Capacity

Notes:

• In the case where the SecondaryLSRule specified is 9 (Meet Full Capacity), the Build Transportation Loads process loads the look ahead recommended shipments in a multiple of the specified split quantity (Sourcing:SplitQty), as long as the total load quantity does not exceed the full capacity for any of the units of measure (UOM) defined in TransModeCap:MaxCap.

ShipCal The Shipping Calendar (Cal: Type: 6) attached to this network. The Shipping Calendar indicates the days when the source is open or closed for shipping.

This Column is used by Optimize Orders logic and is not used by Fulfillment/Distribution or Fulfillment/Deployment.

SKUPerPalletSw


Network

The SKU per pallet switch is used by Order Optimization when loading trucks. When this switch is set to 1, only one SKU is loaded onto a pallet when trucks are loaded. The normal logic used when loading trucks is to merge SKUs together on a pallet in order to maximize the space on the pallet. For example, consider item A has an SOQ of 50 units and 100 units fit on a pallet. When the SOQ is converted to pallets, the pallet quantity is .5 pallets. This normally means that there is space on the pallet for another SKU to maximize the pallet space available. When the SKUPerPalletSw switch is turned on, only one SKU can be placed on the pallet. In the example above the SOQ is converted into one pallet so that when the truck is loaded no other SKUs are placed on the pallet. This means that it is acceptable to have some empty space on the pallets when the SKUPerPalletSw switch is set to 1.

When the SKUPerPalletSw switch is turned on, a constraint for pallets needs to be included in one of the following tables:

• NetworkCap

• OrderGroupCap

• TransModeCap

This is necessary so that order totals are calculated for the pallet UOM.

Source The source location associated with the link defined in this row. Valid values for source are the existing location from the Loc table, or blank.

TransCal Calendar that specifies when the actual truck movement can occur.

Fulfillment In Fulfillment/Distribution, Fulfillment/Deployment, and Order Optimization, TransLeadTime is extended so that the total travel time reflects open periods in the TransCal that sum to the value of TransLeadTime.

This extended duration represents the period from DepartureDate to DeliveryDate on PlanArrivs and RecShips and the period from ShipDate to ArrivDate on VehicleLoads.

TransLeadTime The transit time between this source and destination, using this mode.

To determine the replenishment leadtime for a SKU, the system first uses the Sourcing table to determine where the SKU may be sourced from and which transportation mode may be used. Then, in the Network table, it finds the TransLeadTime for the planned source/destination/mode combination.

Master Planning

The fixed lead time required to move product from source to destination. You can specify additional time for loading and unloading product using Inhandling and Outhandling resources in several ways:

The algorithm calculates the leadtime required for planned arrivals/shipments as the total of:

• Network:TransLeadTime — transportation time.

• Network:LoadTime — Time required to load the vehicle used for this mode between the source and destination.

• Network:UnloadTime — Time required to unload the vehicle used for this mode between the source and destination.

• Variable portion of loading and unloading times, based on shipment quantities. Specify the rates for loading at the source and unloading at the destination in SourcingRequirement:Rate.

• TransLeadTime is independent of any SKUPlanningParam:BufferLeadTime. If the model specifies a LoadTime, UnLoadTime, TransLeadTime, and BufferLeadTime, then the total lead time for the recommended shipment will be:


Network

LoadTime + UnLoadTime + TransLeadTime + BufferLeadTime

Note: When Vessel Scheduling is used (that is, if a schedule is specified in the TransportSched table for this Source/Dest/TransMode), Master Planning does not use TransLeadTime.

Fulfillment

The actual transportation lead time between this source and destination, using this mode. If you do not set a value in Network:LoadTime, you can let TransLeadTime include any extra time required before the vehicle leaves the source.

On the same transportation mode, many source-destination combinations may have the same lead time. You can set a default TransLeadTime instead of adding a row to this table for each of those source-destination combinations. To set a default TransLeadTime, add a row for the TransMode.

Unless SKUPlanningParam:PlanLeadTimeRule is set to 1(manual), the system uses TransLeadTime in calculating SKUPlanningParam:PlanLeadTime.

Note: Transportation Lead Time is counted over open instances of Network:TransCal (on page 188).

IPO

This value is used as the fixed time required to move the item from the source to the destination. It is used when developing a multi-echelon plan.

TransLeadTimeSD The observed standard deviation on the transit time. The square of TransLeadTimeSD is the estimate of the variance of the transit time.

TransMode The transportation mode associated with the link defined in this row.

TransModeMinRule The rule that defines the conditions under which the transportation mode minimum is met for loads corresponding to this network. There are two settings for this rule:

• 1 – The transportation mode minimum condition is met only if all transmode minimums modeled in the TransModeCap table are met.

• 2 – The transportation mode minimum condition is met if any of the transmode minimums modeled in the TransmodeCap table are met.

TransModeName Transportation Mode Name (TransModeName) is the description of the transportation mode associated with the link defined in this row. This column is for information only.

UnloadTime Time required to unload the vehicle used for this mode between the source and destination.

If a valid resource is specified in SourcingRequirement:Res column, the application calculates an unloading time based on the order quantity instead.

Note: This column is not used by Fulfillment. To define an UnLoadTime in Fulfillment, use the column Sourcing:UnLoadDur

UseAltTransModeSw Used by Build Transportation Loads to specify whether using an alternate transportation mode is a valid load-building strategy for a particular source/destination pair or not.

• 1 - Yes. If this switch is set to Yes, the Build Transportation Loads process determines that using alternate transmodes is allowed.

• 0 - No. If this switch is set to No, the Build Transportation Loads process cannot resolve the failed loads on the current transportation mode by using an alternate transportation mode.


Network

VendorMinRule The rule that defines the conditions under which the vendor minimum is met for loads corresponding to this network. There are two settings for this rule:

• 1 – Vendor Minimum condition is met only if all the vendor minimums modeled in the NetworkCap Table are met.

• 2 – Vendor Minimum condition is met if any one of the vendor minimums modeled in the NetworkCap table is met.


OrderLink

OrderLink Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning



Action FF, MP, Flowcasting, ESP

INTEGER 0

DmdNeedDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

DmdSchedDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

DmdSeqNum 4 FF, MP, Flowcasting, ESP

INTEGER

DmdSubType FF,MP, ESP OPTION NUMBER

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

DmdType 3 FF, MP, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4,5,6,7,8,9, and 10


TEXT


TEXT


TEXT ' '

ParentItem 10 FF, MP, Flowcasting, ESP

TEXT ' '

ParentLoc 9 FF, MP, ESP TEXT ' ' ParentSupplySeqNum

FF, MP, Flowcasting, ESP

INTEGER 0

ParentSupplyType


OPTION_NUMBER

1,2,5,6,9,11 0

PegQty FF, MP, Flowcasting, ESP

DECIMAL 0


DATETIME 01/01/1970

SupplyAvailDate


DATETIME 01/01/1970


OrderLink



SupplySeqNum 8 FF, MP, Flowcasting, ESP

INTEGER

SupplySubType FF,MP, ESP OPTION NUMBER

1,2,3,4

SupplyType 7 FF, MP, Flowcasting, ESP

OPTION_NUMBER

1,2,4,5,6,7,8,9,10,11,12,13,14

Table description This table is populated by the Generate Supply and Demand Links/Generate Supply and Demand Links based on priority process. This table describes dependent as well as independent demand, by linking demand orders with supply orders (orders supplying the demand). Production and movement of material may create many layers of dependent demand and supply. This table associates each demand with the order supplying it.

Each row in this table describes an order link—the relationship between a demand order and a supply order.

The supply chain begins with independent demand, which consists of:

• Forecast

• Customer orders

• Safety stock requirements

It ends with stock on hand and supply orders:

• Inventory

• Scheduled receipts of items that are purchased or manufactured

• Planned purchases for SKUs

• Planned orders for manufacturing SKUs that create no further dependent demand

• Vehicle loads of quantity not on hand

When order records in the database are modified in any manner other than by the Generate Supply and Demand Links/Generate Supply and Demand Links based on priority process, the supply chain described by this table becomes invalid.

Column descriptions Action For Master Planning, it is the action (Push, Pull, or Cancel) recommended by the Demand and Supply Links process if the supply ActionAllowedSw is enabled.

DmdNeedDate The date and time when this order is needed.

DmdSchedDate The date when the independent demand order is scheduled.

DmdSeqNum


OrderLink

Identifier of the demand order associated with this row.

DmdSubType If DmdType is 1 (Customer Order) or 2 (Forecast) then the demand subtype indicates the forecast subtype for this demand. The values of forecast subtype are enumerated in the following column listings: AllocStrat:DmdSubType and DeploymentDemand:DmdSubType

DmdType Indicates what kind of demand is associated with this row, and which database table and column the demand comes from.

The type of demand (and the associated table):

• 1: Customer Order (CustOrder table)

The demand order maps to the CustOrder.

• 2: Forecast (FcstOrder table)

Forecast demand order. The demand order maps to the FcstOrder.

• 3: Safety Stock Requirement (StockOrder table)

Safety stock demand order. The demand order maps to the StockOrder.

• 4: Dependent Demand Plan Order (PlanOrder table)

The DmdOrder maps to the Dependent Demand Plan Order.

• 5: Dependent Demand Firm Plan Order (PlanOrder table)

The DmdOrder maps to the Dependent Demand Firm Plan Order.

• 6: Dependent Demand Scheduled Receipt (SchedRcpts table)

The DmdOrder maps to the Dependent Demand Scheduled Receipt.

• 7: Distribution Demand Plan Arrival (PlanArriv table)

The DmdOrder maps to the Distribution Demand Plan Arrival.

• 8: Distribution Demand Firm Plan Arrival (PlanArriv table)

The DmdOrder maps to the Distribution Demand Firm Plan Arrival.

• 9: Distribution Demand InstransitOut

The DmdOrder maps to the Distribution Demand InstransitOut.

• 10: Distribution Demand Recommended Shipment (RecShip table)

The DmdOrder maps to the Distribution Demand Recommended Shipment.

Item The item associated with this order link.

Loc The location associated with this order link.

OrderID Unique identifier of the line item defined in this row. This is needed to identify customer orders. OrderID is also populated for the stock orders of perishable SKUs. This is needed typically when the single stock order demand is pegged to multiple supplies due to supply shelf life. When single stock order is pegged to multiple supplies, the OrderID for each row is incremental.

For non-perishable SKUs, OrderID is populated for customer orders only. Whereas for perishable SKUs, apart from customer orders OrderID is populated for virtual stock orders.


OrderLink

ParentItem The parent of the associated subordinate item.

ParentLoc The parent of the associated subordinate location.

ParentSupplySeqNum The sequence number of the parent supply order linked to the demand.

ParentSupplyType The supply type of the parent supply order linked to the demand. The valid values for ParentSupplyType are 1, 2, 5, 6, 9, 11.

• 1: PlanArriv

• 2: PlanOrder

• 5: Instransit In

• 6: SchedRcpts

• 9: Firm Plan Order

• 11: Firm PlanArriv

PegQty The quantity of the supply order that is linked to the independent demand order.

ShipDate The date the independent demand order is required to be shipped.

SupplyAvailDate Master Planning

The date when the supply from this order is available. For example, this is the date when any dependent demands are satisfied and the supply has completed its manufacturing or transportation routing, if there is one.

Master Planning sets the value in this column based on the value of SupplyType:

If SupplyType is: SupplyDate is equal to:

2 (Planned order) PlanOrder:SchedDate

5 (Intransit in) VehicleLoad:ArrivDate 6 (Scheduled receipt) SchedRcpts:SchedDate 7 (Inventory) If Inventory:Type is 1 (Inventory) If Inventory:Type is 2 (Safety stock)

SKU:OHPost Inventory:AvailDate

SupplySeqNum The supply order supplying the demand.

SupplySubType If SupplyType = 4: Recommended arrival, then SupplySubType indicates the value in the RecShip:Type field.

SupplyType Indicates what kind of supply order is associated with this row, and which database table and column the supply order comes from.


OrderLink


The supply order is associated with PlanArriv:Dest.

• 2: Planned order

The supply order is associated with PlanOrder

• 4: Recommended arrival

The supply order is associated with RecShip:OrderID

The location is associated with RecShip:Dest.

Note: This option is not valid for Master Planning.

• 5: Intransit in

The supply order is associated with VehicleLoadLine:LoadLineID

The item is associated with VehicleLoadLine:Item

The location is associated withVehicleLoad:Dest of the parent VehicleLoad (VehicleLoadLine:LoadID = VehicleLoad:LoadID)

• 6: Scheduled Receipt

The supply order is associated with SchedRcpts:SchedRcptsID

• 7: Inventory

The item is associated with Inventory:Item

The location is associated with Inventory:Loc

• 8: Safety Stock

The item is associated with Inventory:Item

The location is associated with Inventory:Loc


The supply order is associated with PlanOrder


The supply order is associated with RecShip:OrderID

The location is associated with RecShip:Dest

Note: This option is not valid for Master Planning.


The supply order is associated with PlanArriv:Dest


The supply order is associated with PlanPurch


The supply order is associated with PlanPurch


The supply order is associated with PurchOrder


PlanArriv

PlanArriv Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning



INTEGER 0

ActionAllowedSw FF, MP, Flowcasting, ESP

INTEGER 0

ActionDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

ActionQty FF, MP, Flowcasting, ESP

DECIMAL 0

AvailToShipDate MP, IPO, ESP DATETIME 01/01/1970

CovDurSchedDate MP DATETIME 01/01/1970

DeliveryDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

DepartureDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

Dest 2 FF, MP, IPO, Flowcasting, ESP

TEXT

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

DATETIME 01/01/1970

FirmPlanSw FF, MP, IPO, Flowcasting, ESP

BOOLEAN 0

HeaderSeqNum MP, ESP INTEGER 0 Item 1 FF, MP, IPO,

Flowcasting, ESP

TEXT

NeedArrivDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

NeedShipDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

NonIgnorableQty FF, Flowcasting DECIMAL 0


PlanArriv


OrderPlaceDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

Qty FF, MP, IPO, Flowcasting, ESP

DECIMAL 0

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

DATETIME 01/01/1970

RevisedExpDate MP, ESP (Deep Tree)

DATETIME 01/01/1970

SchedArrivDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

SchedShipDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

SeqNum 3 FF, MP, IPO, Flowcasting, ESP

INTEGER

ShrinkageFactor MP, ESP (Deep Tree)

INTEGER 0

Source FF, MP, IPO, Flowcasting, ESP

TEXT ' '

Sourcing FF, MP, IPO, Flowcasting, ESP

TEXT ' '

SubstQty FF, Flowcasting DECIMAL 0 SuppOrderQty FF, Flowcasting DECIMAL 0 TransMode FF, MP, IPO,

Flowcasting, ESP

TEXT ' '

TransName MP TEXT ' '

Table description Each row in this table defines a planned arrival between a source and a destination for an item. You can add or modify planned arrivals manually, using the PlanArriv Flexible Editor page. To prevent the system from deleting a particular planned arrival, set its FirmPlanSw to Yes

Fulfillment

The Calculate Plan process generates planned arrivals for all SKUs for which SKU:ReplenType is 1. Unlike recommended shipments (stored in the RecShip table), planned arrivals are not affected by inventory constraints at the source.

Master Planning

The system generates planned arrivals using the Calculate Master Plan process. The planned arrivals are constrained by inventory at the source. JDA Enterprise Supply Planning Reference Guide 197 © 2014 JDA Software Group, Inc.- Confidential

PlanArriv

Fulfillment/Master Planning

The Generate Supply and Demand Links based on Priority process of Master Planning/Fulfillment and Generate Supply and Demand Links process of Master Planning use this table to recommend that a Firm Plan Arrival be cancelled, or that its SchedDate be changed, to prevent the generation of additional unneeded supplies.

IPO

IPO users only need to populate this table if they intend to use the replenishment plan cost model. Firm planned arrivals are only used to generate the time-phased replenishment cost model. IPO does not write, update, or delete planned arrivals.

ESP

The Generate Master Plan process generates plan arrivals. The plan arrivals are constrained by the inventory available at a source.

Column descriptions Action For Master Planning, Fulfillment, and ESP, it is the action (Push, Pull, or Cancel) recommended by the Generate Supply and Demand Links/Generate Supply and Demand Links based on Priority process when the supply ActionAllowedSw is enabled:

• 0 None

• 1: Pull

• 2: Push

• 3: Cancel

ActionAllowedSw If the ActionAllowedSw = 0, the firm planned arrival is recognized at the SchedArrivDate. If the ActionAllowedSw = 1, the firm planned arrival is recognized at the RevisedDate.

Also if ActionAllowedSw = 1, the Generate Supply and Demand Links/Generate Supply and Demand based on Priority process will recommend a Push/Pull/Cancel action.

ActionDate The date associated with the action recommended for this supply.

ActionQty The supply quantity for which the action is recommended.

AvailToShipDate The earliest date when inventory is available at the source for a recommended shipment and the source is open for shipping. The date when the distribution demand at the source is satisfied and the source is open for shipping.

CovDurSchedDate The coverage duration scheduled date is generated by the Calculate Master Plan process, if Master Planning uses MPS planning rule (SKUPlanningParam:MPSRule (on page 372)) to calculate supplies for SKUs that are replenished by MPS.

Within a coverage duration per supply method for a SKU all the PlanArriv are aggregated to a single PlanArriv. Hence, the aggregated SchedArrivDate and CovDurSchedDate are same.

DeliveryDate Master Planning

DeliveryDate is the date when this arrival is actually scheduled to be delivered at the destination.


PlanArriv

If the sourcing arrival calendar is open on NeedArrivDate, DeliveryDate is the same date. If not, Calculate Master Plan adjusts DeliveryDate to a date when the calendar is open. If possible, Calculate Master Plan sets DeliveryDate to a date earlier than NeedArrivDate (but no earlier than SKU:OHPost, or Loc:OHPost if SKU:OHPost is blank). If that is not possible, the system sets DeliveryDate to a date later than NeedArrivDate (but no later than the end of the period specified by Plan).

Note: Master Planning uses this column to run Deployment for Master Planning SKUs.

Fulfillment

Delivery Date is the date when a planned arrival reaches the destination location; DepartureDate+TransLeadTime, where TransLeadTime considers only open dates in the Transportation calendar if a TransCal is specified, and then moved later to an open date in the ArrivCal if an ArrivCal is specified.

ESP

Date when this plan arrival is actually scheduled to be delivered at destination.

If the sourcing arrival calendar is open on NeedArrivDate, DeliveryDate is the same date. If not, the Generate Master Plan process adjusts DeliveryDate to a date when the calendar is open. If possible, the Generate Master Plan process sets DeliveryDate to a date earlier than NeedArrivDate (but no earlier than SKU:OHPost, or Loc:OHPost if SKU:OHPost is blank). If that is not possible, the system sets DeliveryDate to a date later than NeedArrivDate (but no later than the end of the period specified by Plan).

DepartureDate Master Planning

The date when this arrival can actually be shipped.

If the source SKU's allocation calendar is open on NeedShipDate, DepartureDate is set to the same date.

If the source SKU’s allocation calendar is not open on NeedShipDate, Calculate Master Plan adjusts DepartureDate to a date when the calendar is open. If possible, it sets DepartureDate to a date earlier than NeedShipDate (but no earlier than SKU:OHPost, or Loc:OHPost if, SKU:OHPost is blank). If not possible, the system sets DepartureDate to the value in NeedShipDate and notes an exception.


Fulfillment

Date when a planned arrival leaves the source location; SchedShipDate+LoadTime, where LoadTime considers only open dates in the Working Calendar if a WorkingCal is specified, and then moved later to an open date in the ShipCal if a ShipCal is specified.

ESP

Date when this plan arrival can actually be shipped.

If the source SKU's allocation calendar is open on NeedShipDate, DepartureDate is set to the same date.

If the source SKU’s allocation calendar is not open on NeedShipDate, the Generate Master Plan process adjusts DepartureDate to a date when the calendar is open. If possible, it sets DepartureDate to a date earlier than NeedShipDate (but no earlier than SKU:OHPost, or Loc:OHPost if SKU:OHPost is blank). If not possible, the system sets DepartureDate to the value in NeedShipDate and creates an exception.

Dest The destination location for this arrival.

ExpDate


PlanArriv

The earliest allowable expiration date for the inventory that the source can use to meet this shipment. See Planning distribution of date-sensitive inventory in the JDA Fulfillment OnLine Expert for information on how the Calculate Plan process calculates expiration dates for planned arrivals and how the user parameters impact those calculations.

FirmPlanSw Indicates whether this is a planned or a firm planned arrival. This value can be set by the Fulfillment, Master Planning, or ESP system or the user.

• No: Not a Firm Planned Arrival

Planned arrival generated by the Calculate Plan, Calculate Master Plan, Generate Master Plan or created by the user and not firmed. The process deletes these planned arrivals when it begins calculating a new plan.

In Calculate Plan in Fulfillment, non-firm planned arrivals whose arrival date falls after the new planning leadtime and the new freeze date but before the old time fence are retained.

Master Planning and ESP delete all planned arrivals whose FirmPlanSw = No.

• Yes: Is a Firm Planned Arrival

Fulfillment

Option assigned by the user or CMP to firm or preserve a planned arrival—that is, to prevent the Calculate Plan process from changing it. In Fulfillment/Material Allocation, the CMP process sets this switch to Yes for all planned arrivals that fall within the time period specified by SKUPlanningParam:CMPFirmDur.

The Calculate Plan process will not delete a Firm Planned Arrival unless it falls prior to Loc:FrzStart plus SKUPlanningParam:DRPFrzDur.


Does not delete any plan arrivals whose FirmPlanSw is Yes.

HeaderSeqNum Plan arrival sequence number from which this planned arrival was split.

This value is the same for all planned arrivals that resulted from splitting the same original planned arrival. The system splits planned arrivals while using the Inventory Visibility feature. Depending on the constraints placed by the finish calendar, each split order will have a SchedDate. The CovDurSchedDate for each split order will be calculated based on the CoveragePeriod within which the SchedDate falls. These split orders will be linked through the HeaderSeqNum.

While using the Coverage Duration feature, multiple orders (at a SKU, for a particular production, sourcing, or purchase method, in a particular CoveragePeriod), that are created without MinOrdQty, will be linked to each other through the HeaderSeqNum. All the linked orders will have their HeaderSeqNum same as that of the first of the linked orders created with the MinOrdQty.

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

NeedArrivDate Date when this arrival is needed at the destination. This value is computed based on the demand need date.

Fulfillment

For Fulfillment, if Item:RestrictPlanMode specifies restricted planning, then the NeedArrivDate reflects the demand date of a demand that occurs during the period of time that restricted planning logic considers eligible for a replenishment. See Item:RestrictPlanMode for more information on restricted planning.

NeedShipDate


PlanArriv

Date when this arrival must be shipped in order to arrive at the destination on NeedArrivDate.

Master Planning

The Calculate Master Plan calculates the NeedShipDate as:

NeedArrivDate - (Network:TransLeadTime + Network:LoadTime + Network:UnLoadTime)

While using the Vessel Scheduling feature, the NeedShipDate is calculated as:

Departure date of the vessel - LoadTime

Fulfillment

Calculate Plan calculates the NeedShipDate as the time that the arrival would need to ship in order to arrive at NeedArrivDate while respecting all applicable durations and calendars that affect the source, destination, and shipping lane.

ESP (Deep Tree)

The Generate Master Plan process calculates the NeedShipDate as, NeedArrivDate - (Network:TransLeadTime + Network:LoadTime + Network:UnLoadTime)

When using the Vessel Scheduling feature, the NeedShipDate is calculated as, Departure date of the vessel - LoadTime

NonIgnorableQty Represents the portion of the PlanArriv quantity that should not be ignored by demand reduction logic at the source if distribution demands are ignored at the source. This quantity represents supply that is intended to meet demands that occur later than the source SKU FirstReplenDate offset by the leadtime and calendars. The quantity can represent safety stock, round up, supplemental order, or any other quantity that is not intended for demands prior to the source adjusted FirstReplenDate. This value is populated only if the sre property “RetainSSinDemandReduction” is enabled.

OrderPlaceDate Master Planning, ESP

Date when this plan arrival can actually be shipped.

If the source SKU's allocation calendar is open on NeedShipDate, OrderPlaceDate is set to the same date.

If the source SKU’s allocation calendar is not open on NeedShipDate, the Calculate Master Plan or Generate Master Plan process adjusts OrderPlaceDate to a date when the calendar is open. If possible, it sets OrderPlaceDate to a date earlier than NeedShipDate (but no earlier than SKU:OHPost, or Loc:OHPost if SKU:OHPost is blank). If not possible, the system sets OrderPlaceDate to the value in NeedShipDate and creates an exception.


Fulfillment

OrderPlaceDate is the SchedShipDate calendarized by Review calendar, that is, the latest date on or prior to SchedShipDate that is a defined date-time in the ReviewCalendar. OrderPlaceDate must be greater than or equal to OHPost. If no ReviewCalendar is defined, then OrderPlaceDate is the same as SchedShipDate.

Qty The quantity of this arrival.

RevisedDate Master Planning, ESP (Deep Tree)

The available date after constraining Firm Plan Arrivals as per the Firm Supply Constraint option (Only Material, Only Capacity or Both Material and Capacity). The Firm Supply Constraint option, necessary for processing scheduled supplies, is set in the Calculate Master Plan process or Generate Master Plan process page. JDA Enterprise Supply Planning Reference Guide 201 © 2014 JDA Software Group, Inc.- Confidential

PlanArriv

The supply will be recognized at the RevisedDate if the ActionAllowedSw = 1. Else, the supply will continue to be recognized at the SchedArrivDate.

If the Firm Supply Constraint option is Capacity only: RevisedDate is the greater of the SchedArrivDate (for a Firm PlanArriv this is the SchedArrivDate) and the capacity loading completion date, irrespective of the material available date.

If the Firm Supply Constraint option is Material only: RevisedDate is the greater of the SchedArrivDate (for a Firm PlanArriv this is the SchedArrivDate) and the material available date, irrespective of the capacity loading completion date.

If the Firm Supply Constraint option is Capacity & Material: RevisedDate is the greater of the SchedArrivDate (for a Firm PlanArriv this is the SchedArrivDate) and the date when adequate capacity and material are both available for the successful processing of the scheduled supply.

RevisedExpDate The revised expiry date of the Firm Plan Arrival. If ActionAllowedSw = 1, then RevisedExpDate is calculated as:

RevisedExpDate = RevisedDate + difference between scheduled FirmPlanArriv’s expiry date and scheduled date.

If ActionAllowedSw = 0, then revised exp date will be 01/01/1970, that is, default value.

SchedArrivDate Date when this arrival is actually scheduled to be received at the destination.

Fulfillment

Date on the arrival is scheduled to be posted to inventory at the destination, equal to DeliveryDate + UnLoadDur where UnLoadDur considers only open dates in the Working Calendar if a WorkingCal is specified.

This date will fall on or before the NeedArrivDate unless an arrival on or before that date is prohibited by calendar limitations. When UnLoadDur is zero, the SchedArrivDate will usually be equal to the DeliveryDate, but may be later if required in order to fall later than the Sourcing effective date.

SchedShipDate Fulfillment

The date when this planned shipment is scheduled to be removed from inventory at the source SKU.


The date when this arrival is scheduled to be shipped.

SeqNum The sequence number of the plan arrival. The sequence numbers are generated to be unique per SKU. If firm planned arrivals exist for a given SKU or if planned arrivals are retained prior to the time fence, then the sequence numbers for system generated planned arrivals will start from the maximum of all existing sequence numbers on the retained firm and non-firm planned arrivals for the SKU.

ShrinkageFactor The shrinkage factor associated with this planned arrival. For more information see Sourcing:ShrinkageFactor.

Source The source location for this arrival.

Sourcing Master Planning, ESP

The sourcing (method) that will be used to constrain the capacity.


PlanArriv

Fulfillment

The sourcing method associated with this planned arrival, from Sourcing:Sourcing.

SubstQty If Plan is run in Superession mode, this field is populated with a value that reflects that portion of the entire PlanArriv quantity that is permitted to be met by the supply of an alternate item.

SuppOrderQty Supplemental Order Quantity indicates the portion of PlanArriv:Qty (on page 201) that was allocated to meet supplemental order demands at the destination.

TransMode The mode of transportation for this arrival, copied from Sourcing:Transmode (on page 461).

TransName Transportation Name (TransName) is the transport name from the transport schedule used. This column is populated when there is a vessel schedule associated with the generation of the plan arrival.


PlanOrder

PlanOrder Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning



Default value


INTEGER 0

ActionAllowedSw FF, MP, Flowcasting, ESP

BOOLEAN 0

ActionDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

ActionQty FF, MP, Flowcasting, ESP

DECIMAL 0

CovDurSchedDate MP, ESP (Deep Tree)

DATETIME 01/01/1970

CoProdOrderType MP, ESP (Deep Tree)

TEXT 0

CoProdPrimaryItem MP UPPER_TEXT ' '

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

DATETIME 01/01/1970

FirmPlanSw FF, MP, IPO, Flowcasting, ESP

BOOLEAN 0

HeaderSeqNum MP, ESP (Deep Tree)

INTEGER 0

Item 1 FF, MP, IPO, Flowcasting, ESP

TEXT

Loc 2 FF, MP, IPO, Flowcasting, ESP

TEXT

NeedDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

PrimarySeqNum MP, ESP (Deep Tree)

INTEGER 0

ProductionMethod FF, MP, Flowcasting, ESP

TEXT ' '


DECIMAL 0


PlanOrder



Default value

RecSchedRcptsOpt FF, MP, Flowcasting

OPTION_NUMBER

1,2,3 1

RevisedDate MP, Flowcasting, ESP (Deep Tree)

DATETIME 01/01/1970

RevisedExpDate MP DATETIME 01/01/1970

SchedDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970


INTEGER

StartDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

SubstQty FF, Flowcasting

DECIMAL 0

Table description A planned order represents a SKU replenishment by means of manufacturing. Each row in this table defines one planned order.

Fulfillment/Master Planning, ESP

Plan orders can be:

• Generated by the Calculate Plan, Calculate Master Plan (Master Planning), Generate Master Plan (ESP) process.

• Imported from another system.

• Created or modified manually on the Planned Orders page.

To prevent Calculate Plan, Master Planning, ESP or Load Leveler from deleting a particular planned order set its FirmPlanSw to Yes.

The Generate Supply and Demand Links based on Priority process of Master Planning, Fulfillment, and ESP and Generate Supply and Demand Links process of Master Planning and ESP use this table to recommend that a Firm Plan Order be canceled, or that its SchedDate be changed, to prevent the generation of additional unneeded supplies.

Fulfillment

The Calculate Plan process generates planned orders for SKUs with ReplenType = 2. Planned Orders represent the ideal unconstrained replenishment schedule. You can use Constrained Production Planning to constrain based on material availability and production capacity.

IPO

IPO users only need to populate this table if they intend to use the replenishment plan cost model. Planned orders are only used to generate the time-phased replenishment cost model. IPO does not write, update, or delete planned orders.


PlanOrder

Column descriptions Action It is the action (Push, Pull, or Cancel) recommended by the Generate Supply and Demand Links/Generate Supply and Demand Links based on Priority process when the supply ActionAllowedSw is enabled:

• 0: None

• 1: Pull

• 2: Push

• 3: Cancel

ActionAllowedSw If the ActionAllowedSw = 0, the firm planned order will be recognized at the SchedDate. If the ActionAllowedSw = 1, the firm planned order will be recognized at the RevisedDate.




CovDurSchedDate Coverage Duration Scheduled Date (CovDurSchedDate) is the coverage duration scheduled date generated, by the Calculate Master Plan process or Generate Master Plan process, if Master Planning or ESP use MPS planning rule (SKUPlanningParam:MPSRule (on page 372)) to calculate supplies for SKUs that are replenished by MPS.

If ProductionMethod:SplitOrderSw (on page 227) = True, the supplies within coverage duration are not aggregated. By observing CovDurSchedDate, you can identify the coverage durations in which different split plan orders are created/present. All the split plan orders of a plan order have the same CovDurSchedDate, irrespective whether they are scheduled in the same or different coverage duration.

If ProductionMethod:SplitOrderSw (on page 227) = False, the supplies within coverage duration are aggregated. In such case, aggregated SchedDate and CovDurSchedDate are the same. For more information on aggregated supply in a coverage duration, see Single supply in a coverage duration per supply method.

The CovDurSchedDate is set to the start of the next coverage period.

CoProdOrderType Co-product Order Type indicates whether the order is a primary planned order or one of the co-product order listed below (1 or 2 or 3).

• 0: Primary planned order

• 1: Co-product order generated due to normal planned order

• 2: Co-product order generated due to firm planned order

• 3: Co-product order generated due to a scheduled receipt

CoPrdoPrimaryItem This is the item associated with the planned order. This column is used only when the CoProdOrderType is '1' or '2' or '3'.

EditSw


PlanOrder

The Edit Switch is enabled (value set to 1), when you edit planned orders or SKU loads from the MP Workbench Details page. The default value of Edit Switch is 0.

ExpDate The date on which this planned order replenishment expires.

PlanOrder:ExpDate = PlanOrder:SchedDate + SKUPerishableParam:ShelfLifeDur (possibly modified by data from the ShelfLifeGroupData table.)

FirmPlanSw Firm Planned Switch indicates whether this Planned Order has been firmed and is thus protected from deletion by the Calculate Plan, Master Planning, ESP and Load Leveler.

• No: Not Firm

This planned order was generated by the Calculate Plan, Calculate Master Planning, Generate Master Plan process or was created by a user and has not been firmed.

Calculate Plan deletes all non-firm planned orders with the exception of those that occur after the new manufacturing lead time and the new manufacturing freeze date but before the old manufacturing time fence.

Master Planning and ESP delete all planned orders whose FirmPlanSw = No.

• Yes: Firm


Does not delete any planned order whose FirmPlanSw is Yes.

Fulfillment

In Fulfillment/Material Allocation, the CMP process sets this switch to Yes for firm planned orders that fall within the time period specified by SKU:CMPFirmDur.

The Preserve firm planned orders within manufacturing freeze date option for the Calculate Plan process indicates whether some Firm Planned Orders are deleted by Calculate Plan.

• If you clear this option, Plan deletes firm planned orders whose schedule dates (PlanOrder:SchedDate) fall prior to either the manufacturing freeze period (SKUPlanningParam:MfgFrzDur) or the manufacturing lead time (SKUPlanningParam:MfgLeadTime), whichever is longer.

• If you check this option, Plan retains all firm planned orders within the freeze period or lead time.

For information about setting options for the Calculate Plan process, refer to JDA Fulfillment OnLine Expert.

HeaderSeqNum The plan order sequence number from which this planned order was split.

This value is the same for all planned orders that resulted from splitting the same original planned order. Master Planning or ESP (Deep Tree) split planned orders while using the Inventory Visibility feature. Depending on the constraints placed by the finish calendar, each split order will have a SchedDate. The CovDurSchedDate for each split order will be calculated based on the CoveragePeriod within which the SchedDate falls. These split orders will be linked through the HeaderSeqNum.

While using the Coverage Duration feature, multiple orders (at a SKU, for a particular production, sourcing, or purchase method, in a particular CoveragePeriod), that are created without MinOrdQty, will be linked to each other through the HeaderSeqNum. All the linked orders will have their HeaderSeqNum same as that of the first of the linked orders created with the MinOrdQty.

Item The Item associated with the SKU whose planned order is defined in this row.


PlanOrder

Loc The location associated with the SKU whose planned order is defined in this row.

NeedDate Date when this order is needed to fulfill demand on the SKU.

Fulfillment

For Fulfillment, if Item:RestrictPlanMode specifies restricted planning, then the NeedArrivDate reflects the demand date of a demand that occurs during the period of time that restricted planning logic considers eligible for a replenishment. See Item:RestrictPlanMode for more information on restricted planning.

PrimarySeqNum Primary Header Sequence Number is the header sequence number generated for primary planned order which generated the co-product order. This column is computed only when the CoProdOrderType is '1' or '2' or '3'.

ProductionMethod This is the production method assigned to this planned order. Because this column is not required (even though it is a primary key column), you can import or copy PlanOrder rows where it is blank. You should do this if your system does not include Constrained Production Planning.

Valid values for ProductionMethod are identifiers of an existing ProductionMethod in the ProductionMethod table.

Fulfillment

When a planned order is created by Calculate Plan process, CPP Load Leveler or CPP Workbench, initially the SKU’s primary production method is used; that is, the one whose ProductionMethod:Priority has the smallest value. If a planned order is associated with a production method that no longer exists or is not effective, Constrained Production Planning will replace it with the highest priority effective production method. If there is no effective production method for a planned order, CPP will generate an exception. With no effective production method, the planned order does not contribute to the load on the resource, but it does contribute to the planned order quantity, projected on hand, and projected available stock.


When Master Planning or ESP create a plan order, they initially use a SKU’s highest-priority production method.

Qty The quantity associated with this planned order.

RecSchedRcptsOpt Recommended Scheduled Receipts Option (RecSchedRcptsOpt) can have following valid values:

• 1: Regular planned order

The Recommend Scheduled Receipts process has not recommended this planned order for release.

• 2: Recommended for release

The Recommend Scheduled Receipts process has recommended this planned order for release.

• 3: Confirmed by user for release

The user has confirmed that this planned order is to be released. If you do not want all planned orders with Option 2 to be exported to the external execution system, set those to be exported to Option 3 and use a column filter to select only those rows when exporting.

RevisedDate


PlanOrder

For Master Planning and ESP (Deep Tree) this is the available date after constraining Firm Plan Orders as per the Firm Supply Constraint option (Only Material, Only Capacity or Both Material and Capacity). The Firm Supply Constraint option, necessary for processing scheduled supplies, is set in the Calculate Master Plan process or Generate Master Plan process page.

The supply will be recognized at the RevisedDate if the ActionAllowedSw = 1. Else, the supply will continue to be recognized at the SchedDate.

If the Firm Supply Constraint option is Capacity only: RevisedDate is the greater of the SchedDate and the capacity loading completion date, irrespective of the material available date.

If the Firm Supply Constraint option is Material only: RevisedDate is the greater of the SchedDate and the material available date, irrespective of the capacity loading completion date.

If the Firm Supply Constraint option is Capacity & Material: RevisedDate is the greater of the SchedDate and the date when adequate capacity and material are both available for the successful processing of the scheduled supply.

RevisedExpDate The revised expiry date of the Firm Plan Order. If ActionAllowedSw = 1, then RevisedExpDate is calculated as:

RevisedExpDate = RevisedDate + difference between FirmPlanOrder’s expiry date and scheduled date.


SchedDate The date when production from this run is actually scheduled to be available as part of the projected on hand. SchedDate may be different from NeedDate.

Fulfillment

Calculate Plan adjusts the SchedDate to a time when the Production Calendar (SKUPlanningParam:ProdCal) is open. If possible, it sets SchedDate to a date earlier than NeedDate (but no earlier than SKU:OHPost, or Loc:OHPost if SKU:OHPost is blank). If that is not possible, the system sets SchedDate to the earliest open date later than NeedDate (but no later than the end of the planning period).

When the CPP Workbench or CPP Load Leveler creates a new planned order as a result of adding or moving a load, the new order will have a unique SchedDate. If there is no unique SchedDate available within the period at a time when the SKU’s production calendar is open, CPP will not create the order.


This must be an open date in the finish calendar (ProductionMethod:FinishCal) used by the ProductionMethod associated with this plan order.

SeqNum The sequence number of the plan order. The sequence numbers are generated to be unique per SKU. If firm plan orders exist for a given SKU or if planned orders are retained prior to the time fence, then the sequence numbers for system generated planned orders will start would start from the maximum of all existing sequence numbers on the retained firm and non-firm planned orders for the SKU.

StartDate The date when the load is applied to the resource referenced in the first production method step. The production method is indicated in PlanOrder:ProductionMethod. The step with the lowest value ProductionStep:StepNum is the first production method step. When SKUPlanningParam: MfgLeadTime is greater than zero, then PlanOrder: StartDate is calculated as SchedDate - MfgLeadTime.

IPO

Within IPO, repairs are tracked as planned orders and schedule receipts (see the SchedRcpt table). Start date is the date when repairs begin. On this date, funds will be committed to the repair.


PlanOrder

SubstQty If Plan is run in Supersession mode, this field is populated with a value that reflects that portion of the entire PlanOrder quantity that can be met by the supply of an alternate item.


PlanProxyInventory

PlanProxyInventory Table included with: Fulfillment, Flowcasting, Master Planning and Enterprise Supply Planning


AltItem 2 FF, Flowcasting, MP, ESP

TEXT ' '

Item 1 FF, Flowcasting, MP, ESP

TEXT ' '

Loc 3 FF, Flowcasting, MP, ESP

TEXT ' '

PrimaryItemQty FF, Flowcasting, MP, ESP

DECIMAL 0

ProxyEndDate 5 FF, Flowcasting, MP, ESP

DATETIME 01/01/1970

ProxyStartDate 4 FF, Flowcasting, MP, ESP

DATETIME 01/01/1970

Qty FF, Flowcasting, MP, ESP

DECIMAL 0

SeqNum MP, ESP INTEGER

Table description This table is an output table and contains proxy inventory records representing supplies of alternate SKUs that have been allocated to other SKUs based on relationships defined in the Supersession table.

Fulfillment and Flowcasting

Note: For more information on Calculate Plan with Supersession, see Planning for product transitions with Supersession.

Column descriptions AltItem The Alternate Item whose supply has been allocated to meet the demands of the item represented by the PlanProxyInventory:Item.

Item This is the actual item which is receiving the supply (proxy inventory) from AltItem.

Loc Location of both Item and AltItem.

PrimaryItemQty This quantity represents the units of demand of the Primary Item that this PlanProxyInventory record meets. This quantity is equal to Qty (on page 211)/Supersession:DrawQty (on page 484)

ProxyEndDate The end date until which the alternate item is supplied for the actual item.

ProxyStartDate The start date from which the alternate item is supplied for the actual item.

Qty


PlanProxyInventory

Quantity of supply that is being provided by the alternate item to meet primary item demands. This quantity is represented in units of the alternate item, and always a multiple of Supersession:RoundingQty.

ESP

This value is a multiple of Supersession:DrawQty.

SeqNum This field is defined because it is a part of the primary key.


PlanPurch

PlanPurch Table included with: Master Planning, Inventory Policy Optimization, Enterprise Supply Planning


Action MP, ESP (Deep Tree)

INTEGER 0

ActionAllowedSw MP, ESP (Deep Tree)

INTEGER 0

ActionDate MP, ESP (Deep Tree)


ActionQty MP, ESP (Deep Tree)

DECIMAL 0

CovDurSchedDate MP, ESP (Deep Tree)


ExpDate MP, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

FirmPlanSw MP, IPO, ESP INTEGER 0

HeaderSeqNum MP, ESP INTEGER 0 Item 2 MP, IPO, ESP TEXT

Loc 3 MP, IPO, ESP TEXT NeedDate MP, IPO, ESP DATETIME TRUNC(

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

PurchMethod MP, ESP TEXT ' '

Qty MP, IPO, ESP DECIMAL 0 RevisedDate MP, ESP (Deep

Tree) DATETIME TRUNC(

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

RevisedExpDate MP, ESP (Deep Tree)



PlanPurch


SchedDate MP, IPO, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

SeqNum 1 MP, IPO, ESP INTEGER

StartDate MP, IPO, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

Table description Each row in this table defines a planned purchase for an item as determined by the Calculate Master Plan process. You can also add or modify planned purchases manually, using the PlanPurch Flexible Editor page.

IPO

IPO users only need to populate this table if they intend to use the replenishment plan cost model. Planned purchases are only used to generate the time-phased replenishment cost model. IPO does not write, update, or delete planned purchases.

Column descriptions Action The action (Push, Pull, or Cancel) recommended by the Generate Supply and Demand Links process if the supply ActionAllowedSw is enabled:

• 0: None

• 1: Pull

• 2: Push

• 3: Cancel

ActionAllowedSw If the ActionAllowedSw = 0, the firm planned purchase will be recognized at the SchedDate/ArrivDate. If the ActionAllowedSw = 1, the firm planned purchase will be recognized at the RevisedDate. Also if ActionAllowedSw = 1, the Generate Supply and Demand Links process will recommend a Push/Pull/Cancel action.



CovDurSchedDate Coverage Duration Scheduled Date (CovDurSchedDate) is the coverage duration scheduled date is generated, by the Calculate Master Plan process, if Master Planning uses MPS planning rule (SKUPlanningParam:MPSRule (on page 372)) to calculate supplies for SKUs that are replenished by MPS.


PlanPurch

Within a coverage duration per supply method for a SKU all the PlanPurch are aggregated to a single PlanPurch. Hence, the aggregated SchedDate and CovDurSchedDate are same.

ExpDate The expiration date of the planned/firm planned purchase.

FirmPlanSw Firm Planned Switch (FirmPlanSw) is the switch that indicates whether this is a planned or a firm planned purchase. This value can be set by JDA Master Planning or the user.

• No: Planned

Planned purchase generated by the Calculate Master Plan process or created by a user. The process deletes planned purchases when they begin calculating a new plan. (Planned purchases whose date falls after the new manufacturing lead time and the new manufacturing freeze date but before the old manufacturing time fence are retained.)

Master Planning deletes all planned purchases whose FirmPlanSw = No.

• Yes: Firm Planned

Master Planning does not delete any planned purchase whose FirmPlanSw is Yes.

HeaderSeqNum The plan purchase sequence number from which this planned purchase was split.

This value is the same for all planned purchases that resulted from splitting the same original planned purchase. Master Planning splits planned purchases while using the Inventory Visibility feature. Depending on the constraints placed by the finish calendar, each split order will have a SchedDate. The CovDurSchedDate for each split order will be calculated based on the CoveragePeriod within which the SchedDate falls. These split orders will be linked through the HeaderSeqNum.

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

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

NeedDate The date when production from this run is needed to meet demand.

PurchMethod When Master Planning creates a planpurch, it initially uses the SKU’s highest-priority Purchase Method.

The system may be unable to use the purchase method specified in this column—for example, if this planned purchase was created manually, if the purchase method is not effective, or if the purchase method was deleted after the planned purchase was created. In that case, the system uses the effective purchase method with the highest priority (the one with the smallest value in PurchMethod:Priority). If there is none, the system generates an exception. With no effective purchase method, the planned purchase does not contribute to the load on the resource, but it does contribute to the planned purchase quantity, projected on hand, and projected available stock.

Qty The quantity associated with this planned purchase.

RevisedDate If the Master Planning function recommends changing the SchedDate for this order, it specifies the recommended new date in this column.

RevisedExpDate JDA Enterprise Supply Planning Reference Guide 215 © 2014 JDA Software Group, Inc.- Confidential

PlanPurch

The revised expiration date of the plan purchase.

Note: This column is not used in current release.

SchedDate The date on which the supply order is scheduled to arrive.


This must be an open date in the finish calendar (PurchMethod:ArrivCal) used by the PurchMethod associated with this planned purchase.

SeqNum The sequence number for the plan purchase. The sequence numbers are generated for SKUs. If firm plan purchases exist in the system, then the sequence number would start from the maximum of all sequence numbers.

StartDate The date on which the supply order is shipped from location.

IPO

Date when purchase begins. On this date, funds will be committed to the purchase.


ProductionMethod

ProductionMethod Table included with: Fulfillment, Master Planning, Production and Sourcing Optimization, Supply, Flowcasting, Enterprise Supply Planning


BOMNum FF, MP, PSO INTEGER 0

Descr FF, MP, PSO, Supp, ESP

TEXT ' '

Disc FF, MP, Supp, ESP

DATETIME 01/01/1970

Eff FF, MP, Supp, ESP

DATETIME 01/01/1970

EnableSw PSO BOOLEAN 1

FinishCal MP TEXT ' '

IncQty FF, MP, PSO DECIMAL 0

Item 2 FF, MP, PSO, Supp, Flowcasting, ESP

TEXT

LeadTime MP DURATION

0

LeadTimeCal Not used in this release

TEXT ' '

LoadOpt MP OPTION_NUMBER

1,2,3,4,5 1

Loc 3 FF, MP, PSO, Supp, Flowcasting, ESP

TEXT

LotSizesEnabledSw

PSO BOOLEAN 0

MaxFinDur MP DURATION

0

MaxLeadTime PSO DURATION

36500D

MaxQty MP, PSO, ESP DECIMAL 0 MaxStartDur MP DURATIO

N 0

MinLeadTime PSO DURATION

0

MinQty FF, MP, PSO, ESP

DECIMAL 0

NoNewSupplyDate

MP, ESP DATETIME 01/01/1970


ProductionMethod


OffsetType FF OPTION_NUMBER

1,2,3 1

Priority FF, MP, Supp, ESP

INTEGER 1

ProductionMethod

1 FF, MP, PSO, Supp, Flowcasting, ESP

TEXT

ProdCost ESP (LPOPT) FLOAT (126)

0

ProdGroup ESP (LPOPT) TEXT SplitFactor MP, ESP DECIMAL 0.0 SplitOrderSw MP, ESP (Deep

Tree) INTEGER 0

WorkScope Supp TEXT ' ' YieldQty Not used in this

release DECIMAL 0

Table description Each row in this table defines a production method, which is used by Master Planning, Fulfillment Constrained Production Planning, Supply, or Production and Sourcing Optimization when calculating the load on resources. A production method consists of one or more steps defined in the ProductionStep table. Each step refers to a resource in the Res table.


The planned orders and scheduled receipts (and planned arrivals for Master Planning only) for the SKUs that are assigned in this table, place load on the resource based on:

The resources on which the loads are placed are identified in the ProductionStep records. The production method defines a single lot-sizing rule (MinQty and IncQty) for all included steps.

Fulfillment

For use with CPP Level Loads, you can define multiple production methods for a SKU, then assign a relative priority to each production method in the Priority column.

Master Planning

In Master Planning, you can also set a split quantity rule instead of a lot-sizing rule, to avoid creating excess supply. Master Planning uses production methods to define resource requirements for manufacturing supply methods. ProductionMethod:ProductionMethod (on page 227) is specified for each production method whose Type is 1 (Manufacturing) if the production method has resource requirements.

Note: In JDA Master Planning, you can model a production method without any production steps.

Supply

This table defines the Make processes in the supply chain network.


ProductionMethod

The planned orders and scheduled receipts for the SKUs that are assigned in this table, place load on the resource based on:

Important: For JDA Supply, ensure that all production methods have production steps associated with them. Also all production steps defined must have a resource specified in the ProductionStep:Res column.


This table defines the Make processes in the supply chain network. This is used to relate the item to the corresponding BOM and to calculate the process execution lead times.

Column descriptions BOMNum A value used to identify the bill of material for a parent item (as defined in BOM:BOMNum). A group of subordinate items with the same parent Item, parent Loc, and BOMNum defines the bill of material for the parent item. The valid values for BOMNum are 1 to 99.

Fulfillment

When using Constrained Production Planning, this number is tied to the production method so that a different BOM can be used if an alternative production method is chosen.

Master Planning

For a ProductionMethod, enter the Bill of Material number (BOM:BOMNum) for the SKU being made. Otherwise, leave a value of 0 in this column.

Descr A description of this production method.

Disc The date and time when this production method is no longer in effect. Disc and Eff work together to determine when the production method is effective.

Master Planning

The system does not use this production method for orders that are needed after the Discontinue Date.

Fulfillment

The system does not use the production method defined in this row for planned orders whose SchedDate is after the Discontinue Date

Master Planning and Fulfillment

Eff and Disc work together to determine when the production method is effective. The following chart summarizes the results of all possible combinations of values for Eff and Disc.






ProductionMethod


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

Supply

The following chart summarizes the results of all possible combinations of values for Eff and Disc.





ESP (MAP and LPOPT)



01/01/1970 01/01/1970

Effective

Date 01/01/1970

Not effective until Eff; effective as of Eff

01/01/1970 Date Effective until Disc, then discontinued Date earlier than Disc


Eff The date and time when the production method becomes effective. Eff and Disc work together to determine when the production method is effective. See the chart under Disc for information.

Fulfillment

The system does not use the production method defined in this row for planned orders whose SchedDate is prior to the Effective Date.

Master Planning

The system does not use this production method for orders that are needed prior to the Effective Date.

EnableSw Indicates if the production method will be used while running the Production and Sourcing Optimization Optimizer.

FinishCal Optional calendar, used by Master Planning, that determines when orders using this production method are allowed to be completed. If a finish calendar is assigned, then supply orders from this production method can finish only during a time period when the calendar is open.

Valid values for FinishCal are identifiers of an Arrival or Production calendar, or blank.

If you specify a Finish Calendar for a production method, it must be a Production calendar (Cal:Type = 9). The SchedDate, computed based on the NeedDate, for planned orders based on this production method must be within an open period in this calendar. The finish dates that must fall into an open period on this calendar are:


ProductionMethod

PlanOrder:NeedDate

PlanOrder:SchedDate

SchedRcpts:RevisedDate

IncQty This value is used as either the incremental planning quantity or the incremental split quantity.

The system uses IncQty in conjunction with ProductionMethod:MinQty (on page 223). It calculates quantities that are equal to MinQty plus (if needed) an integer multiple of IncQty. IncQty and MinQty are used, rather than SKUPlanningParam:IncMPSQty and SKUPlanningParam:MinMPSQty, whenever production methods are effective. See also ProductionMethod:MinQty (on page 223).

Incremental planning quantity

In Fulfillment/Production, IncQty is the incremental value the system will plan for this SKU when using this production method. If the MinimumOrderSwitchOff environment variable is On, Master Planning also uses it as the incremental planning quantity.

For Master Planning, the Calculate Master Plan process uses MinQty, MaxQty, and IncQty for lot-sizing when creating a planned order.

For Fulfillment, Calculate Plan, Level Loads, and CPP Workbench use MinQty and IncQty for lot-sizing (and creating PlanOrder:Qty and ResLoadDetail:Qty) when rounding load quantities (explained in the JDA Fulfillment OnLine Expert), and when manually moving or firming partial loads.

For Production and Sourcing Optimization, the Optimize Supply Chain process uses MinQty,MaxQty, and IncQty for lot-sizing when calculating the quantities for production runs.

Caution: Use this feature only when absolutely necessary. Excessive usage may hinder the performance of the algorithm/model run time to a large extent.

If this value is 0:

• Master Planning/Production and Sourcing Optimization does not enforce an incremental quantity. Any values between MinQty and MaxQty are valid.

• Fulfillment/Production uses the value in SKUPlanningParam:IncMPSQty. If IncMPSQty is also 0, Fulfillment/Production uses a value of 1 as the incremental quantity.

Incremental split quantity

On the Calculate Master Plan process page, select the Minimum Order Switch Off option to turn the Minimum Split Quantity feature off. If this option is off, Master Planning uses IncQty as the incremental split quantity. See ProductionMethod:MinQty (on page 223) for an explanation of the minimum split quantity rule.

Item The item associated with this production method.

LeadTime Fixed amount of time required to replenish supply by means of this production method. LeadTime applies to manufacturing supply orders whose production methods are set for fixed loading (ProductionMethod:LoadOpt (on page 221) = 2 or 3).

If LoadOpt is 2 or 3 (Fixed loading), this is the total time required to replenish supply by means of this production method. This lead time is used only for manufacturing orders whose supply method includes this Production Method. Set LeadTime to be equal to or greater than the total of all resource load times for the steps in this production method (ProductionStep:ProdDur). If you leave the lead time as 0, or if the value you set is too small, the system will be unable to meet demand on time.

LoadOpt


ProductionMethod

This option determines how this production method will plan lead times.

• 1: Variable sequential loading

Order lead time is calculated as the sum of the load times on all production method steps. The load time for each step is based on the production rate specified in ProductionStep:ProdRate. The steps are loaded sequentially, from the last step through the first step.

• 2: Fixed load at start

The system assumes a fixed lead time, as specified in ProductionMethod:LeadTime (on page 221). The associated resources are loaded relative to the beginning of the fixed lead time interval.

Note: The resource loading time is defined by ProductionStep:ProdDur for the steps associated with this production method, and so may be different from the fixed lead time.

• 3: Fixed load at end

The system assumes a fixed lead time, as specified in ProductionMethod:LeadTime (on page 221). The associated resources are loaded relative to the end of the fixed lead time interval.

Note: The resource loading time is defined by ProductionStep:ProdDur for the steps associated with this production method, and so may be different from the fixed lead time.

• 4: Bucketed variable

Order lead time is calculated as the elapsed time between the loaded time of the first step in the first bucket and the loaded time of the last step in the last bucket. The steps are loaded sequentially, from the last step through the first step, in each bucket.

• 5: Contiguous Loading

When you select this option, manufacturing resource is loaded in contiguous time buckets in order to complete a plan order or firm plan order or scheduled receipt.

The behavior of LoadOpt = 5 is similar to Load Opt=1 where the planned order is loaded in variable sequential manner, but respects the contiguous loading constraint. If the resource is not operational at the weekend (saturday & sunday), the order is loaded on friday and monday, and is treated as contiguous. An order can be split across down times and still be considered contiguous. In case of parallel dependent resources in a production method, the loading is treated as contiguous across the downtime when both the parallel dependent resources are down on the same days or buckets. In such case, SKU is contiguously loaded as both the parallel dependent resources are down at the same time.

Loc The location of the SKU that is produced using this production method.

LotSizesEnabledSw Lot Sizes Enabled Switch determines whether to enable or disable the lot sizes for Production and Sourcing Optimization.

MaxFinDur Maximum Finish Duration (MaxiFinishDur) is the value constrains the generation of planned orders relative to their need date. MaxFinDur is the maximum duration allowed between the NeedDate and SchedDate of a planned order. Value in this field is considered while pre-building the supply due to various constraints. This value is not considered when demand is met by stepping late.

MaxLeadTime The maximum production lead time for this production method, specified in minutes.

MaxQty Lot Size Maximum Quantity (MaxQty) is the largest PlanOrder:Qty that Master Planning will create using this production method. If MaxQty is 0, Master Planning does not enforce a maximum quantity.

Valid values for MaxQty are 0 or greater. JDA Enterprise Supply Planning Reference Guide 222 © 2014 JDA Software Group, Inc.- Confidential

ProductionMethod

When SKU has SKUPlanningParam:MPSRule (on page 372) = 1 (coverage duration), while aggregating the supplies for a SKU, for a supply method within coverage duration, if aggregated supply exceeds the specified MaxQty, an exception is generated and aggregated supply exceeds the MaxQty. For more information on aggregated supply in a coverage duration, see Single supply in a coverage duration per supply method.

JDA Production and Sourcing Optimization

Whenever a MinQty for a Make process or MajorShipQty for Move process is used, Production and Sourcing Optimization implicitly creates an upper bound for the Make and Move processes. By default this upper bound value is 100,000 and if it is required to be changed (beyond 100,000), then ProductionMethod:MaxQty and Sourcing:MaxShipQty (on page 457) need to be updated accordingly. Also, changing this parameter to an arbitrarily high value will hinder the performance.

MinQty is used in combination with MaxQty. When MinQty is utilized, the MaxQty has to be set as close as possible to the expected ProductionMethod executions. This will invoke MIP (mix integer programming) feature and the performance time is heavily depended on MaxQty's proximity to the expected ProductionMethod executions.

MaxStartDur Maximum Start Duration (MaxStartDur) is the value that constrains the generation of planned orders relative to their start date and scheduled date. MaxStartDur is the maximum duration allowed between the start date and scheduled date of a planned order.

MinLeadTime The minimum production lead time for this production method, specified in minutes.

MinQty This value is used as either the minimum planning quantity or the minimum split quantity.

Valid values for MinQty are 0 or greater.

The system uses MinQty in conjunction with IncQty. It calculates quantities that are equal to MinQty plus (if needed) an integer multiple of IncQty. MinQty and IncQty are used, rather than SKUPlanningParam:MinMPSQty and SKUPlanningParam:IncMPSQty whenever production methods are effective. See also IncQty (on page 221).

When MinQty is same as IncQty, the MinQty should be set to 0 for better performance. This is a performance impacting parameter and has to use only on an absolute necessity. Recommended to avoid MinQty with values as '1'.

Minimum planning quantity

In Fulfillment/Production, MinQty is the minimum quantity that the system will plan for this SKU when using this production method. JDA recommends that you define MinQty as an integer multiple of IncQty.

For Master Planning, on the Calculate Master Plan process page, select the Minimum Order Switch Off option to turn the Minimum Split Quantity feature off. The Calculate Master Plan process uses MinQty, MaxQty, and IncQty for lot-sizing when creating a planned order.

For Fulfillment, CPP Workbench uses MinQty and IncQty for lot-sizing when rounding load quantities (explained in the JDA Fulfillment OnLine Expert section Level Loads: removing resource overloads), and when manually moving or firming partial loads.

If this value is 0:

• Master Planning does not enforce a minimum quantity.

• Fulfillment/Production uses the value in SKUPlanningParam:MinMPSQty. If MinMPSQty is also 0, no minimum quantity is applied.


ProductionMethod

Minimum split quantity

If the Minimum Order Switch Off option is On, Master Planning uses MinQty as the minimum demand quantity that the system will split between multiple supply methods. This feature may prevent the creation of excess supply when meeting demand.

If the demand is equal to or greater than the minimum split quantity and it can’t be satisfied using only one production method, the system may use more than one production method to meet it. If the demand is less than the minimum split quantity, the system will create supply only for the amount of the demand.

In Example 1, the demand is greater than the minimum split quantity, and it can all be met on the need date. On the lower-priority supply method, the system creates a supply order whose quantity is equal to MinQty. It meets the rest of the demand on the higher-priority production method.

Example 1: Demand greater than minimum split quantity

MinQty = 400 Period 1 Period 2 Period 3

Demand 0 1100 0

Production method 1

Available capacity

0 1000 1000

Load 0 700 0

Production method 2

Available capacity

1000 1000 1000

Load 0 400 0

When meeting a demand order that is smaller than the minimum split quantity, the system creates only one supply order, as shown in Example 2. When using a minimum split quantity, there is no minimum lot size if all the demand can be met by one supply order.

Example 2: Demand less than minimum split quantity


Demand 0 200 0

Production method 1

Available capacity

0 1000 1000

Load 0 200 0

Production method 2

Available capacity

1000 1000 1000

Load 0 0 0

When using a minimum split quantity, if the system must create multiple supply orders to meet one demand, the quantity of each supply order must be equal to or greater than MinQty, as shown in Example 3.

Example 3: After splitting, no supply order can be less than MinQty


Demand 0 1000 0


ProductionMethod


Production method 1

Available capacity

0 400 400

Load 0 400 400

Production method 2

Available capacity

0 400 400

Load 0 400 0

A minimum split quantity that is larger than the available capacity in a time period may result in unmet demand at a time when there is unused capacity, as shown in Example 4. In this example, the constraints on resource capacity are hard constraints.

Example 4: Capacity constraints result in unused capacity


Demand 0 1300 0

Production method 1

Available capacity

0 500 0

Load 0 500 0

Production method 2

Available capacity

0 500 200

Load 0 500 0

NoNewSupplyDate Time fence you can use to prevent creating new supply with this production method.

NoNewSupplyDate is a variable used to control creation of new supplies. When you select the No Start before NoNewSupplyDate option, new supplies cannot start before NoNewSupplyDate. When you do not select the No Start before NoNewSupplyDate option, new supplies cannot be scheduled to complete before NoNewSupplyDate.

Master Planning

The No Start before NoNewSupplyDate option can be set on the Calculate Master Plan process page.

ESP

The No Start before NoNewSupplyDate option can be set on the Generate Master Plan process page.

OffsetType Option that specifies how Fulfillment/Production determines load offset durations and resource load dates.

• 1: Do not compute load offset duration

Load offset duration will be considered to be zero for any production method steps belonging to this production method. Specifically, the ProductionStep columns LoadOffsetDur and ProdDur are ignored.

• 2: Use Production Step:LoadOffsetDur


ProductionMethod

The ProductionStep:LoadOffsetDur will be used to determine load offset durations and resource load dates for all production method steps belonging to this production method. Load offset durations are calculated as the number of calendar days between load date and schedule date.

• 3: Use Production Step:ProdDur

ProductionStep:ProdDur will be used to determine load offset durations and resource load dates for all production method steps belonging to this production method. When the Calculate Plan process is run, load offset durations are calculated based on the values in ProductionStep:ProdDur and ProductionStep:StepNum, and on information defined for the calendar specified in Res:Cal. The system first calculates load offset for the final production method, then for each earlier load date in turn.

Priority Fulfillment/Production

For SKUs that have more than one production method, the Calculate Plan process uses the one with the smallest Priority when it creates an unconstrained master production plan.

Valid values for Priority Value are 1 to 99.

When CPP Level Loads moves a load to a different resource, the system tries to use the highest priority production method in which the new resource is used—that is, the production method with the smallest Priority value. If a hard constraint prevents that production method from being used, the system tries each of the other production methods in Priority order, until the move can be successfully completed or until there are no more production methods to try.

Each CPP production method for the same SKU should have a unique Priority value.

For each row for one SKU, the combination of Eff and Priority must be unique. For example, these two rows are valid:

Item Loc Eff Priority

1 A 1/2/04 3

1 A 1/2/04 6 But these two rows are not valid:

Item Loc Eff Priority

1 A 1/2/04 3

1 A 1/2/04 3 Master Planning

This value indicates the importance of this production method in relation to all other supply methods. The Calculate Master Plan process uses this priority to choose between a production method, a sourcing method, and a purchase method (all put together).

The Calculate Master Plan process first tries to satisfy a demand with the highest priority production method, but if this production method cannot satisfy the demand, then the Calculate Master Plan process will investigate a lower priority production method. A value of 1 is most important and higher values are less important.

It is valid to have multiple production methods with the same priority (see ProductionMethod:SplitFactor (on page 227)). Use the SplitFactor to select the method to be used where more than one method has the same "priority" for a production method.

Supply

This value indicates the importance of this production method in relation to all other production methods. JDA Enterprise Supply Planning Reference Guide 226 © 2014 JDA Software Group, Inc.- Confidential

ProductionMethod

ESP

This value specifies the priority of a production method over other supply methods. The Generate Master Plan process uses this priority to select a production, sourcing, or purchase method (all put together). The Generate Master Plan process tries to satisfy a demand with the highest priority production method. If this production method cannot satisfy the demand, the Generate Master Plan process tries a lower priority production method. A value of 1 has the highest priority and higher values have low priorities.

If all production methods of a SKU have the same priority, the portion of demand satisfied by each production method is determined by the SplitFactor (on page 227) associated with the production method.

ProdCost Cost of producing a unit of item using this method.

ProdGroup The group to which this production method belongs.

ESP (LPOPT)

When using the LPOPT solver, if you specify a production method group name as the qualifier for an objective, the objective is applied to all production methods in the specified group.

ProductionMethod The name used to identify this production method. This name does not determine the priority of one production method in relation to another (see the ProductionMethod:Priority (on page 226) column).

SplitFactor Factor that determines what portion of a SKU’s demand should be satisfied by this production method, if the SKU has other production methods with the same Priority. The system uses Factor to calculate the portion of demand to be met by each of the production methods that is effective during a time period.

Valid values for Split Factor are 0 to 1.0.

The following example illustrates how the system calculates the portion of demand to be met by each production method.

Production Methods A and B supply the same SKU, have the same Priority, and are the only production methods effective for this SKU during this time period. Their Factors are:

• A: 1.0

• B: 0.25

Percentage of demand met by Production Method A = (Factor for Production Method A/ Sum of factors for Production Methods A and B) * 100 = (1/1.25) * 100 = 80

If you want the system to satisfy equal portions of the demand from each of the production methods at a given Priority level, leave all their Factors set to 1.0. If Factor is 0, the system will not use this production method.

ESP (LPOPT and MAP)

When all production methods of a SKU have the same priority, to specify factorization set SplitFactor to a value other than 1 (the default value). To specify that instead of factorization the alternate production methods must be used based on Priority, set the SplitFactor of all production methods of a SKU to 1.

SplitOrderSw This column supports the Inventory Visibility feature in Master Planning.


ProductionMethod

• N: Planned orders created with this production method may not be split into multiple planned orders.

• Y: Planned orders created with this production method may be split into multiple planned orders. Use this setting for production methods that must split planned orders by resource load, enabling you to see available inventory in the bucket in which it is produced.

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

YieldQty Yield quantity of the primary SKU (item, loc) for this production method.


ProductionStep

ProductionStep Table included with: Fulfillment, Master Planning, Production and Sourcing Optimization, Supply, Flowcasting, Enterprise Supply Planning


Descr FF, MP, PSO, Supp, Flowcasting, ESP

TEXT ' '

Eff 5 FF, MP, PSO, Supp, Flowcasting, ESP (Deep Tree)

DATETIME 01/01/1970


FixedResReq MP, Supp, ESP (Deep Tree)

DECIMAL 0

InUseBeforeSw PSO BOOLEAN 0 Item 3 FF, MP, PSO,

Supp, Flowcasting, ESP

TEXT

LoadOffsetDur FF DURATION

0

Loc 4 FF, MP, PSO, Supp, Flowcasting, ESP

TEXT

MaxStartDur MP, ESP (Deep Tree)

DURATION

0

NextStepTiming MP, ESP OPTION_NUMBER

1,2,3 3

ProdCost FF DECIMAL 0

ProdDur FF, MP, PSO, ESP

DURATION

0

ProdFamily MP, ESP (Deep Tree)

TEXT " "

ProdOffset PSO, Supp INTEGER >=0 0 ProdRate FF, MP, PSO,

Supp, ESP DECIMAL 0

ProdRateCal ESP TEXT ' ' ProductionMethod

1 FF, MP, PSO, Supp, Flowcasting, ESP

TEXT


ProductionStep


QtyUOM PSO OPTION_NUMBER

Any value in the UOM:UOM column

0

Res FF, MP, PSO, Supp, Flowcasting, ESP

TEXT ' '

Setup PSO TEXT ' ' Spread Supp DURATIO

N 0

StepNum 2 FF, MP, PSO, Supp, Flowcasting, ESP

INTEGER 0

Table description Each row in this table defines one step in a specific production method.

The step specifies one resource used in the production method, the cost of producing one unit of the SKU, and the rate at which the SKU is produced.

The system uses this table to calculate the load on all resources used by one production method.

For more information on how this table is used in each applicable product, see the table description for the ProductionMethod table.


This table is used to specify resource requirements.

Column descriptions Descr A description of this step.

Eff The effective or starting date for this production step.

Fulfillment


EnableSw Indicates if the production step will be used while running the Production and Sourcing Optimization Optimizer.

FixedResReq Fixed Resource Requirement (FixedResReq) is a fixed number of resource capacity units required to produce any number of lots of the SKU associated with this step. It may be the setup time, or any other fixed time requirement, that is required whenever this SKU is produced. This value must be specified in terms of the resource’s capacity units.

Valid values for FixedResReq are 0 or greater.


ProductionStep

InUseBeforeSw Indicates if this production step was active just prior to the start of the planning calendar.

Item The item associated with this step.

LoadOffsetDur Fulfillment

Fulfillment/Production uses the following calculation to determine when planned order load on a resource will occur:

date/time of resource load = PlanOrder:SchedDate - LoadOffsetDur

Note: This field is not used when ProductionMethod:OffsetType is 3.

Loc The location associated with this step.

MaxStartDur Maximum duration between the end of this production step and the beginning of the next.

This value is used only with sequential loading and parallel dependent loading.

NextStepTiming This option determines the timing relationship between the resource defined in this step and the resource defined in the next step. (The next step is the one whose StepNum is the next in sequence after this step’s StepNum.)

By default, the steps in a production method cannot run concurrently. That is, the second step cannot begin until the first step has ended. You can change the value in NextStepTiming to allow parallel loading of resources, so that two steps may occur at the same time.

For each step except the last one, choose one of the following options. (For the last step, the option selected has no effect, since there is no next step.)

• 1: Sequential loading

The next step cannot begin until this one ends.

• 2: Parallel independent loading


ProductionStep

The next step may begin at any time after its input material is available.

• 3: Parallel dependent loading

The next step must begin and end at the same time as this one.

The preceding examples illustrate production methods whose steps all have the same setting for NextStepLoading. By using different settings for NextStepLoading, you can sequence the loading of resources in a variety of ways, including:

• All steps use parallel loading, but some are dependent and some are independent.


ProductionStep

• Some steps use parallel loading, and some use sequential.

Before a sequential step can begin, all the preceding parallel steps must have finished.

ESP (LPOPT and MAP)

Parallel independent loading (NextStepTiming value 2) is not supported by the LPOPT and MAP solvers.

ProdCost The cost for this step to produce one unit of this SKU. You can define a ProdCost in monetary units, or any other unit that makes sense in your company.

To calculate how much this resource contributes to the total cost for a CPP Workbench plan, the system multiplies each ProdCost by the planned production quantities for the SKU.

Valid values for ProdCost are 0 or greater.

ProdDur Fulfillment

When ProductionMethod:OffsetType = 3, then along with StepNum, this field is used to calculate the resource load dates for the resources used by each production step that is part of the production method. The production duration represents the amount of open calendar time that a planned order needs to spend on the resource specified in that production method step before moving to the next production method step. The sequence of production method steps is determined by the StepNum. The step with the lowest number is run first; the step with the highest number is run last.

Valid values for ProdDur are 0 or greater.

For example, if a crafted item requires three days of a craft person’s time at one step in the production process, then the item cannot move to the next phase of production until three days have passed during which that department was staffed and open for production.


ProductionStep

The use of production duration differs from the use of load offset duration in two ways. First, when applied to the planned order, the production duration translates into a longer actual calendar duration than the time specified, since the duration is stretched around weekends or other closed calendar periods. Second, the load offset duration for step one, in a five-step process, is the cumulative value of all five durations, each translated from a specified duration into an equal or greater number of calendar days.

Master Planning

If the associated ProductionMethod:LoadOpt is set to 2 or 3 (fixed loading), ProdDur is the duration for which the production steps are loaded.


The length of time (in minutes) that the resource is used.

ProdFamily It denotes the production family of this SKU.

You can use “?” to indicate unknown production family and “*” to indicate any production family.

ProdOffset Supply

The ProdOffset is the number of days before the supply order’s (work orders as well as planned supply orders) DueDate that the production must be completed. Offsets are specified in minutes. They are then converted to days by dividing with a factor of 1440. The value obtained is then rounded to the next higher number. For example, if the offset is 1728 minutes, the calculation gives a value of 1.2. The offset is then taken to be 2 days.

Important: To implement block scheduling successfully and avoid parallel operations, ensure that you provide appropriate increasing production offsets for each production step.


The length of time (in minutes) from the start of the process execution to when the resource begins to be used.

ProdRate The rate at which the specified SKU or process uses resource capacity.

Master Planning, Fulfillment/Production, and ESP

Master Planning (if ProductionMethod:LoadOpt is 1), Fulfillment/Production, and ESP calculate the load on a resource as:

Resource capacity may be defined in terms of days, hours, standard cases, or any other unit of measure that makes sense in your company. For production capacity calendars, the same unit of measure is used for CalData:Avail, which specifies the number of resource capacity units available in a calendar period. The valid values for ProdRate are 0 or greater.

If CalData:Avail is based on a unit of time, ProdRate is the number of units of this SKU produced in one of those time units. For example, if CalData:Avail is defined in terms of hours, ProdRate is the number of units of the SKU produced in one hour.


ProductionStep

Instead of a unit of time, CalData:Avail may be the SKU’s unit of measure, defined in Item:UOM. Or it may be any unit of measure consistent with the SKU’s unit of measure. For example, Item:UOM may be cases and the unit of measure for CalData:Avail may be cans. ProdRate would then be calculated as:

In that example, if there are 12 cans per case, ProdRate would be calculated as:

In Master Planning and Fulfillment/Production, there are no ramp-up curves or yield curves; the production rate is assumed to be constant. ProdRate does not normally include changeover time. However, in Master Planning, you can use ProductionStep:FixedResReq (on page 230) to model changeover times.

Supply

The ProdRate value can be zero. The Generate Finite Resource Plan process considers all production steps that have a production rate of zero to be valid and will load the resource based on the fixed quantity as specified in the FixedResReq (on page 230) column. No variable quantity will be loaded for that production step.


• If DBPARAM.STRAT_USE_SCPO_PRODRATE = TRUE, then ProdRate is defined as the quantity of the primary output SKU that is produced by a unit resource.

• If DBPARAM.STRAT_USE_SCPO_PRODRATE = FALSE, then ProdRate is defined as the number of units of resource utilized by each run of the production process.

ProdRateCal Calendar in which capacity yields are modeled.

ESP

The MAP and LPOPT solvers use this field to model time varying production rates, through a production rate efficiency calendar.

ProductionMethod The production method associated with this step.

QtyUOM The unit of measure applied to all quantity values associated with this production step.

Res The resource associated with this step. For every production method step, one resource is defined in the database—the resource that most constrains production for that step. When calculating load on resources, the system assigns load resulting from this step to this resource.

Setup The setup attached to this production step.

Spread The number of days over which the computed load is divided and then placed on a work center. Spreads are generally non-negative and are specified in minutes. They are then converted to days by dividing with a factor of 1440. The value obtained is then rounded to the next higher number. For example, if the spread is 1728 minutes, the calculation gives a value of 1.2. The spread is then taken to be 2 days.


ProductionStep

If you do not specify the spread, then all computed load appears on the work center at the computed load date.

StepNum The number of this step.

Fulfillment/Production

When using ProductionMethod:OffsetType = 1 or 2, StepNum is ignored by CPP Level Loads, CPP Workbench, and Calculate Plan. The order of steps is determined by the respective values of load offset duration (LoadOffsetDur) for the steps. If multiple steps have the same load offset duration, these steps are considered to be simultaneous.

When using ProductionMethod:OffsetType = 3, StepNum is respected. Each step in the production method must have a unique StepNum. CPP Level Loads, CPP Workbench, and Calculate Plan will sequence the production steps per increasing order of StepNum. In this case, LoadOffsetDur is ignored and the values in ProdDur are used to determine the length of each step in turn.

Master Planning, Supply, ESP

The number of a step implies its sequence in relation to other production steps.


ProductionYield

ProductionYield Table included with: Production and Sourcing Optimization, Master Planning, Enterprise Supply Planning



Eff 5 PSO, MP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

Item 2 PSO, MP, ESP

TEXT

Loc 4 PSO, MP, ESP

TEXT

OutputItem 3 PSO, MP, ESP

TEXT

ProductionMethod

1 PSO, MP, ESP

TEXT ' '



0

YieldCal ESP TEXT ' '

YieldQty PSO, MP, ESP

DECIMAL 0

Table description This table defines the co-products produced in a given production method.

Column descriptions Eff The effective or starting date for this time-phased yield quantity.

Item The primary item produced utilizing this production method.

Loc The location associated with this production method.

OutputItem The co-product items produced utilizing this production method. The Item and OutputItem columns will have the same value if there are no co-products.

ProductionMethod The name of this production method.

QtyUOM The unit of measure applied to the attributes associated with this production method.

YieldCal


ProductionYield

Name of the Yield Calendar (Cal:Type is 16) that specifies the time phased yields for the primary SKU , subordinate SKU, and co-products.

YieldQty The yield quantity for the output item produced in this production method by consuming the draw quantities of the input (raw) material for this production method. In the Model Management page, the default value for the yield quantity is set to 1 across the entire time period.


PurchMethod

PurchMethod Table included with: Master Planning, Enterprise Supply Planning



Abbr MP TEXT ' '

ArrivCal MP, ESP TEXT ' ' Disc MP, ESP DATETIME TRUNC(

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

Eff MP, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

Factor MP, ESP DECIMAL 1

IncOrderQty MP DECIMAL 0 Item 2 MP, ESP TEXT LeadTime MP DURATION 0 Loc 3 MP, ESP TEXT MaxOrderQty MP, ESP DECIMAL 0 MinOrderQty MP, ESP DECIMAL 0 NoNewSupplyDate

MP, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

Priority MP, ESP INTEGER 1

PurchCost ESP (LPOPT) FLOAT (126) 0 PurchGroup ESP (LPOPT) TEXT PurchMethod 1 MP, ESP TEXT

Table description Each row in this table defines a purchase method that can be used to purchase a SKU.

Column descriptions Abbr Short label, useful for identifying purchase methods when displayed on userviews. Does not have to be unique.

ArrivCal Optional calendar, used by Master Planning, that determines when orders using this purchase method will arrive. If a arrival calendar is assigned, then supply orders from this purchase method can arrive only during a time period when the calendar is open.


PurchMethod

The arrival dates that must fall into an open period on this calendar are:

PlanPurch:NeedDate

PlanPurch:SchedDate

Disc The system does not use this purchase method for orders that are needed after the Discontinue Date.

Eff and Disc work together to determine when the purchase method is effective. The following chart summarizes the results of all possible combinations of values for Eff and Disc.





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

ESP (MAP and LPOPT)



01/01/1970 01/01/1970 Effective

Date 01/01/1970 Not effective until Eff; effective as of Eff 01/01/1970 Date Effective until Disc, then discontinued Date earlier than Disc


Eff This is the date and time when this purchase method becomes effective. The system does not use this purchase method for orders that are needed prior to the Effective Date. Eff and Disc work together to determine when the purchase method is effective. See the chart under Disc for information.

Factor Factor that determines what portion of a SKU’s demand should be satisfied by this purchase method, if the SKU has other purchase methods with the same Priority. Master Planning uses Factor to calculate the portion of demand to be met by each of the purchase methods that is effective during a time period.

Valid values for Factor are 0 to 1.0.

The following example illustrates how Master Planning calculates the portion of demand to be met by each purchase method.

Purchase Methods A and B supply the same SKU, have the same Priority, and are the only purchase methods effective for this SKU during this time period. Their Factors are:

A: 1.0

B. 0.25


PurchMethod

Percentage of demand met by Purchase Method A = (Factor for Purchase Method A/ Sum of factors for Purchase Methods A and B) * 100 = (1/1.25) * 100 = 80

If you want Master Planning to satisfy equal portions of the demand from each of the purchase methods at a given Priority level, leave all their Factors set to 1.0. If Factor is 0, Master Planning will not use this purchase method.

ESP (LPOPT and MAP)

When all purchase methods of a SKU have the same priority, to specify factorization set Factor to a value other than 1 (the default value). To specify that instead of factorization the alternate purchase methods must be used based on Priority, set the Factor of all purchase methods of a SKU to 1.

IncOrderQty The incremental quantity that Master Planning will plan for this SKU when using this purchase method. The system uses IncOrderQty in conjunction with MinOrderQty (on page 241) and MaxOrderQty (on page 241). It calculates quantities that are equal to MinOrderQty plus (if needed) an integer multiple of IncOrderQty. A value of 0 indicates that no incremental order quantity is to be enforced.

Minimum split quantity

If the Minimum Order Switch Off option is On, Master Planning uses MinOrderQty as the minimum demand quantity that the system will split between multiple supply methods. This feature may prevent the creation of excess supply when meeting demand.

If the demand is equal to or greater than the minimum split quantity and it can’t be satisfied using only one purchase method, the system may use more than one purchase method to meet it. If the demand is less than the minimum split quantity, the system will create supply only for the amount of the demand.

Item The item supplied by this purchase method.

LeadTime The time required to replenish supply by means of this purchase method.

Loc The location supplied by this purchase method.

MaxOrderQty The largest quantity that Master Planning will plan for this SKU when using this purchase method. A value of 0 indicates that no maximum order quantity is to be enforced.

Valid values for MaxOrderQty are 0 or greater.

When SKU has SKUPlanningParam:MPSRule (on page 372) = 1 (coverage duration), while aggregating the supplies for a SKU, for a supply method within coverage duration, if aggregated supply exceeds the specified MaxQty, an exception is generated and aggregated supply exceeds the MaxQty. For more information on aggregated supply in a coverage duration see Single supply in a coverage duration per supply method.

MinOrderQty The smallest quantity that Master Planning will plan for this SKU when using this purchase method. A value of 0 indicates that no minimum order quantity is to be enforced.

Valid values for MinOrderQty are0 or greater

NoNewSupplyDate Time fence you can use to prevent creating new supply with this purchase method.


PurchMethod

NoNewSupplyDate is a variable used to control creation of new supplies. When you select the No Start before NoNewSupplyDate option, new supplies cannot start before NoNewSupplyDate. When you do not select the No Start before NoNewSupplyDate option, new supplies cannot be scheduled to complete before NoNewSupplyDate.

Master Planning


ESP


Priority This value indicates the importance of this purchase method in relation to all other supply methods. The Calculate Master Plan process uses this priority to choose between a production method, a sourcing method, and a purchase method (all put together).

The Calculate Master Plan process first tries to satisfy a demand with the highest priority purchase method, but if this purchase method cannot satisfy the demand, then the Calculate Master Plan process will investigate a lower priority purchase method. A value of 1 is most important and higher values are less important.

It is valid to have multiple purchase methods with the same priority (see Factor (on page 240)). Use the Factor to select the method to be used where more than one method has the same "priority" for a purchase method.

ESP

This value specifies the priority of a purchase method over other supply methods. The Generate Master Plan process uses this priority to select a production, sourcing, or purchase method (all put together). The Generate Master Plan process tries to satisfy a demand with the highest priority purchase method. If this purchase method cannot satisfy the demand, the Generate Master Plan process tries a lower priority purchase method. A value of 1 has the highest priority and higher values have low priorities.

If all purchase methods of a SKU have the same priority, the portion of demand satisfied by each purchase method is determined by the Factor associated with the purchase method.

PurchCost Cost of procuring a unit of SKU using this method.

PurchGroup The group to which this purchase method belongs.

ESP (LPOPT)

When using the LPOPT solver, if you specify a purchase group name as the qualifier for an objective, the objective is applied to all purchase methods in the specified group.

PurchMethod The name of the purchasing method.


PurchOrder

PurchOrder Table included with: Master Planning, Supply, Inventory Policy Optimization, Enterprise Supply Planning


Action MP, ESP (Deep Tree)

OPTION_NUMBER

0,1,2,3 0

ActionAllowedSw MP, ESP (Deep Tree)

BOOLEAN 0

ActionDate MP, ESP (Deep Tree)


ActionQty MP, ESP (Deep Tree)

DECIMAL 0.0

ApproveSw Supp BOOLEAN 0 DueDate MP, Supp, IPO,

ESP DATETIME

ExpDate MP, ESP DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))

FirmSw Supp BOOLEAN 0

Item MP, Supp, IPO, ESP

TEXT

LineNum 2 MP, Supp, IPO, ESP

TEXT

Loc MP, Supp, IPO, ESP

TEXT

OrderNum 1 MP, Supp, IPO, ESP

TEXT

OrderSeqNum MP, Supp, ESP SEQUENCE 0

OrderType_PO Supp OPTION_NUMBER

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

125


PurchOrder


OrderType_PR Supp OPTION_NUMBER

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

120

Project Supp TEXT ' '

PurchMethod MP, ESP TEXT ' ' Qty MP, Supp, IPO,

ESP DECIMAL 0

ReceivedQty Supp DECIMAL 0.0 RemainingQty Supp DECIMAL 0.0 Vendor Supp TEXT ' '

Table description Purchase orders are committed supplies that must be imported from an external system. Each row in this table defines a purchase order. Purchase orders can also be created or modified manually on the PurchaseOrder Flexible Editor page.

Supply

Each row in this table defines one purchase order or one purchase requisition depending on the value as specified in the PurchOrder:ApproveSw column.

IPO

IPO users only need to populate this table if they intend to use the replenishment plan cost model.

Column descriptions Action It is the action (Push, Pull, or Cancel) recommended by the Generate Supply and Demand Links/Generate Supply and Demand Links based on Priority process if the supply ActionAllowedSw is enabled:

• 0: None

• 1: Pull

• 2: Push

• 3: Cancel

ActionAllowedSw If the ActionAllowedSw = 0, the scheduled supplies will be recognized at the ActionDate. If the ActionAllowedSw = 1, the firm purch order will be recognized at the DueDate. Also if ActionAllowedSw = 1, the Generate Supply and Demand Links/Generate Supply and Demand Links based on Priority will recommend a Push/Pull/Cancel action.



PurchOrder


ApproveSw If this switch enabled, then a Purchase Order is generated. If this switch is not enabled, a Purchase Requisition is generated.

DueDate The expected arrival date of the purchase order or purchase requisition.

ExpDate The expiration date of the purchase order.

FirmSw FirmSw indicates a firm purchase order. If this switch is enabled and the Respect Firm Orders option is selected on the Calculate Supply Plan: Scheduling process page, then the process does not reschedule this order.

Item The item associated with the SKU whose purchase order or purchase requisition is defined in this row. Must be a valid item in the Item table.

LineNum Line (sub-order) identifier.

Loc The location associated with the SKU whose purchase order or purchase requisition is defined in this row. Must be a valid location in the Loc table.

OrderNum The order identifier.

OrderSeqNum The purchase order or purchase requisition identifier used for mapping output records to input order information.

OrderType_PO This column contains a numeric type representing the supply order type. This is an information only field and holds a default value of 125.

OrderType_PR This column contains a numeric type representing the supply order type. This is an information only field and holds a default value of 120.


PurchMethod The purchase method associated with this purchase order.

Qty The quantity associated with this purchase order or purchase requisition.

ReceivedQty The purchase order or purchase requisition quantity that has already been received.


PurchOrder

RemainingQty The purchase order or purchase requisition quantity yet to be received.

Vendor The vendor code. This is a reference only column.


Res

Res Table included with: Fulfillment, Master Planning, Production and Sourcing Optimization, Supply, Flowcasting, Enterprise Supply Planning


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

DECIMAL 1

AvgFamilyChg FF DECIMAL 0 AvgFamilyChgCost FF DECIMAL 0 AvgSKUChg FF DECIMAL 0 AvgSKUChgCost FF DECIMAL 0 Cal FF, MP, Supp,

ESP TEXT ' '

CheckMaxCap MP, Supp, ESP OPTION_NUMBER

1,2,3 1

Cost FF DECIMAL 0

CriticalItem FF, Flowcasting TEXT ' '

CurrencyUOM PSO INTEGER 0

Descr FF, MP, PSO, Supp, ESP

TEXT ' '


LevelLoadSw FF BOOLEAN 0 LevelSeqNum FF INTEGER 1 Loc FF, MP, PSO,

Supp, Flowcasting, ESP

TEXT ' '

OvertimeSw ESP (MAP and LPOPT)

BOOLEAN 0,1 1

PeggingSw ESP NUMBER 0,1 1 ProductionFamily ChgOverOpt

MP, ESP (Deep Tree)

INTEGER 0,1,2,3 0



0

ReleaseFenceDur ESP (LPOPT) DURATION

0

Res 1 FF, MP, PSO, Supp, Flowcasting, ESP

TEXT


Res


Source PSO TEXT ' ' Stage ESP (LPOPT) TEXT ' '

StorageClass ESP TEXT 1, 2 ' ' StorageGroup ESP TEXT ' ' SubType PSO OPTION_N

UMBER Any value in the RESSUBTYPE:SUBTYPE column

0

Type FF, MP, PSO, Supp, ESP

OPTION_NUMBER

4,5,6,7,8,9 4

UnitPenalty Not used in this release

DECIMAL 0

Table description Each row in this table defines a resource—a machine, labor pool, subordinate material, or other resource used in the production or transport of SKUs. For the list of resource type, see Type (on page 252).

The Calculate Master Plan process (JDA Master Planning), Calculate Plan process (JDA Fulfillment), Plan Resource Requirements process (JDA Supply), Generate Finite Resource Plan process (JDA Supply), several workbenches, CPP Level Loads, and Optimize Supply Chain (JDA PSO) use this table.

However, the Calculate Plan process only uses this table if ProductionMethod and ProductionStep records are defined that link SKUs to resources.

Column descriptions AdjFactor You can use this value to adjust resource production capacity without changing the production capacity calendar. For example, to change resource capacity in all periods to 90 percent of the capacity specified in CalData:Avail for the production capacity calendar, put a value of 0.9 in AdjFactor.

For constrained production planning, transportation, inhandling, and outhandling resources (Res:Type (on page 252) = 4, 5, 7, or 8), the system calculates capacity as:

AdjFactor × CalData:Avail

For critical subordinate materials (Res:Type = 6), Workbenches and Level Loads calculates capacity as:

AdjFactor × (ProjOH - dependent demand)

AvgFamilyChg Average Load per Family Changeover (AvgFamilyChg) is the average number of CPP resource capacity units required for a changeover between changeover families on this resource. (Families are defined in the CPPFamily table.)

Valid values for AvgFamilyChg are 0 or greater.


Res

In assigning a value for this column, you must determine the size of the time period to which it applies. For example, if you assign an average weekly value, looking at CPP load data in monthly time buckets could cause changeover load to be underestimated.

To calculate total changeover load on a resource, CPP Workbench and CPP Level Loads use these calculations:

• Family changeover load = (number of families with planned order load in this period - 1) × Res:AvgFamilyChg (on page 248)

• SKU changeover load = (number of SKUs with planned order load in this period - the number of families) × Res:AvgSKUChg (on page 249)

• Total changeover load = Family changeover load + SKU changeover load

AvgFamilyChgCost Average Cost per Family Changeover (AvgFamilyChgCost) is the average cost of a changeover between changeover families on this resource. (Families are defined in the CPPFamily table.)

Valid values for AvgFamilyChgCost are 0 or greater.

In assigning a value for this column, you must determine the size of the time period to which it applies. For example, if you assign an average weekly value, looking at CPP load data in monthly time buckets could cause changeover costs to be underestimated.

To calculate total changeover costs on a resource, CPP Workbench and CPP Level Loads use these calculations:

• Family changeover cost = (number of families with planned order load in this period - 1) × Res:AvgFamilyChgCost (on page 249)

• SKU changeover cost = (number of SKUs with planned order load in this period - the number of families) × Res:AvgSKUChgCost (on page 249)

• Total changeover cost = Family changeover cost + SKU changeover cost

AvgSKUChg Average Load per SKU Changeover (AvgSKUChg) is the average number of CPP resource capacity units required for a changeover between SKUs on this resource.

Valid values for AvgSKUChg are 0 or greater.

For an explanation of how CPP Workbench and CPP Level Loads calculate changeover load on a resource, see AvgFamilyChg.

AvgSKUChgCost Average Cost per SKU Changeover (AvgSKUChgCost) is the average cost of a changeover between SKUs on this resource.

For an explanation of how CPP Workbench and CPP Level Loads calculate changeover cost on a resource, see AvgFamilyChgCost.

Valid values for AvgSKUChgCost are 0 or greater.

Cal The calendar associated with this resource.

The valid values for Cal are blank, or the identifier of an existing calendar in the Cal table. If Res:Type (on page 252) is 4, 5, 7, or 8, Res:Cal must be a production capacity calendar (Cal:Type = 10). Res:Cal is also used in calculating data when writing to the ResProjStatic table.

Supply

This column is used by the Plan Resource Requirements (RRP) process, the Generate Finite Resource Plan (FRP) process, the Resource Workbench, and all the RRP and FRP reports. JDA Enterprise Supply Planning Reference Guide 249 © 2014 JDA Software Group, Inc.- Confidential

Res

CheckMaxCap This column determines whether the capacity of this resource constrains the plan created by the Calculate Master Plan process (For JDA Master Planning) or the Generate Finite Resource Plan process (For JDA Supply).

Master Planning

• 1: Hard

The resource will not be loaded beyond its capacity.

• 2: Soft

Master Planning is allowed to generate a plan that exceeds the capacity of this resource. However, the system will generate an exception if the resource is over-committed.

• 3: None/Off

The resource can be loaded beyond its capacity. No exceptions are generated if the resource is over-committed.

Supply

The CheckMaxCap columns can have the following values:

• 1: Hard

The resource will not be loaded beyond its capacity.

• 2 and 3: None/Off


In JDA Supply, you can also set global options to constrain a resource by using the Global Infinite Option option on the Generate Finite Resource Plan process page. If the Res:CheckMaxCap column for a resource is set to "Hard" and the Global Infinite Option is set to true, then forward scheduling will not be constrained by capacity of that resource.

For example, assume the following:

• There are two supply orders each requiring a capacity of 30 units on a work center with a daily capacity of 10 units.

• The NeedDate for both the supply orders are the same.

The first supply order will be loaded on D1, D2, and D3 consuming a capacity of 10 units each. The second supply order will also be loaded on D1, D2, and D3 again consuming a capacity of 10 units each.

Note: You can specify the Global Infinite Option option only if you select Forward as the Scheduling Type.

ESP

The valid values of this field are as follows:

• 1: Hard

The resource is not loaded beyond its capacity.

• 2: Soft

The resource can be loaded beyond its capacity but an exception is generated if the resource is over-committed.

Note: This value is not applicable to the MAP and LPOPT solvers. If you specify CheckMaxCap as 2 and use the MAP solver to generate a plan, the plan is generated considering CheckMaxCap as 3.

• 3: None/Off


Res


• 4: Flexible

The resource is considered as a flexible resource with infinite capacity.

Note: This value is not applicable to the MAP and Deep Tree solvers. If you specify CheckMaxCap as 4 and use the MAP or Deep Tree solvers to generate a plan, the plan is generated considering CheckMaxCap as 3.

Cost For a CPP resource (Res:Type (on page 252) = 4 or 6), the cost per capacity unit for using this resource. The valid values for Cost are 0 or greater.

CriticalItem A subordinate material (defined in BOM:Subord) whose supply is limited. By defining this material as a critical resource, you enable CPP Level Loads and CPP Workbench to level its load, as with any other resource. For information about all the database components needed to enable CPP Workbench and CPP Level Loads to level critical material resources, see the JDA Fulfillment OnLine Expert.

CurrencyUOM The unit of measure applied to the attributes associated with the resource.

Descr A description of this resource.

EnableSw Indicates if the resource will be used while running the Production and Sourcing Optimization Optimizer.

LevelLoadSw For the CPP Level Loads, the search includes all the resources whose loads you want to level, for which this switch should be set to On.

The pool of data available to the CPP Level Loads may also need to include other resources, for which this switch should be set to Off. Include any resources used by a production method that also uses the resources that are to be leveled. For example, you may want to level loads on Packaging Line 1. That resource is used by a step in CPP Production Method 1. That production method includes other steps that use Blender 4 and Oven 2, whose loads you do not want to level. Include Blender 4 and Oven 2 in your search and set their LevelLoadSw to Off.

LevelSeqNum For resources whose LevelLoadSw is Yes, the CPP Level Loads process uses LevelSeqNum to determine the sequence in which to process resources. Set a lower value in this field for your most critical resources to increase the likelihood that their loads can be leveled successfully. Use higher values for less critical resources, which will be leveled last.

Loc The location of this resource.


Transportation resources (Type 5) do not have to be associated with a specific location. You may assign the predefined ANY location to all transportation resources.

OvertimeSw Overtime switch indicates if overtime capacity is used for this resource.

PeggingSw If pegging switch is 1 the pegging results, for this resource, are exported to the ResLoadDetail table.


Res

ProductionFamilyChangeOverOpt This column enables you to run OPC process either bucketed mode or continuous mode. Depending upon the value specified in this column, the resource will be identified as critical or non-critical to run OPC on. Value 0 indicates that resource is non-critical and OPC will not consider the resource for optimization. For remaining values, that is, 1, 2, 3 this column enables you to run OPC either bucketed mode or continuous mode. The default value is 0 and following are the valid values:

• 0: No production family changeover

• 1: Bucketed optimization for changeover

• 2: Continuous optimization for changeover

• 3: Loads entire plan order

When you select option 0, OPC will not consider this as a critical resource and it will not run on Res.

When you select option 1, only single production family is loaded within a bucket with this logic.

When you select option 2, multiple production families can be loaded in a single bucket.

When you select option 3, multiple production families may be loaded in the same bucket and entire plan order will be loaded.

Multiple critical resources in a single production method are not supported. Hence you need to specify only one critical resource in a single production method. If you specify more than one critical resource in a single production method, an exception will be generated and the first resource (alphabetically) will be considered as critical resource.

QtyUOM The unit of measure applied to the attributes associated with the resource.

ReleaseFenceDur If CheckMaxCap is 4, ReleaseFenceDur specifies the duration, from the plan start date, from which the resource is flexible.

Res The resource or resource group defined in this row.

Source The source location for transportation type of resources.

Stage Stage to which this resource belongs. Resources are grouped into stages.

ESP (LPOPT)

When using the LPOPT solver, if you specify a stage name as the qualifier for an objective, the objective is applied to all resources in the specified stage.

StorageClass Specifies if the storage capacity for this resource must be modeled in terms of volume or number of pallets. If this value is 1, the storage capacity is modeled in volume. If it is 2, the storage capacity is modeled in number of pallets.

StorageGroup Item group name.

SubType The resource subtype. The valid values of resource subtypes are defined in ResSubtype:Subtype.

Type Valid values for Resource Type are 4 to 9. JDA Enterprise Supply Planning Reference Guide 252 © 2014 JDA Software Group, Inc.- Confidential

Res

• 4 = Manufacturing (Supply, Master Planning and Fulfillment/Production)

A resource associated with a production method step. For every production method step, one resource is defined in the database—the resource that most constrains production for that step.

• 5 = Transportation (Master Planning)

A resource, such as a vehicle, used to transport products from one location to another. Transportation resources on a lane are specified in the SourcingRequirement:Res for SourcingRequirement:StepNum = 2.

• 6 = Critical Subordinate Material (Fulfillment/Production)

A subordinate SKU whose supply is limited. (Capacity for a critical resource is the projected on hand at the end of the period, which is defined by the calendar specified in CPP Level Loads or CPP Workbench). By defining this material as a critical resource, you enable CPP Workbench and CPP Level Loads to calculate the load placed on it by all parents. As with any CPP resource, CPP Level Loads tries to level its load, and you can manually level its load with CPP Workbench. See Working with CPP Workbench and Res

• 7 = Inhandling (used with Master Planning)

A resource such as a loading dock at a destination location. Inhandling resources on a lane are specified in SourcingRequirement:Inhandling for SourcingRequirement:StepNum = 3.

• 8 = Outhandling (Master Planning)

A resource such as a loading dock at a source location on a lane. Outhandling resources on a lane are specified in SourcingRequirement:Outhandling for SourcingRequirement:StepNum = 1.

• 9 = Storage resource

A resource such as warehouse or pallet. Ideally, the SKUs attached with this resource should have SKU: StorableSw as 1.


ResException

ResException Table included with: Fulfillment, Master Planning, Supply, Enterprise Supply Planning


BatchNum 2 FF, MP, Supp, ESP

INTEGER 0

Descr FF, MP, Supp, ESP

TEXT ' '

Exception FF, MP, Supp, ESP

INTEGER

ExceptionDate FF, MP, Supp, ESP

DATETIME 01/01/1970

FunctionName FF, MP, Supp, ESP

TEXT ' '

FunctionNum 4 FF, MP, Supp, ESP

INTEGER

Item FF, MP, Supp, ESP

TEXT ' '

LoadQty FF, MP, Supp, ESP

DECIMAL 0

Loc FF, MP, Supp, ESP

TEXT ' '

ProdFamily MP, ESP TEXT

ProcessID 1 FF, MP, Supp, ESP

OPTION_NUMBER

Any value in the PROCESSOPTIONSET: PROCESSID column

0

ProductionMethod

FF, MP, Supp, ESP

TEXT

Res FF, MP, Supp, ESP

TEXT

SeqNum 3 FF, MP, Supp, ESP

INTEGER

Source FF, MP, Supp, ESP

TEXT ' '

Sourcing FF, MP, Supp, ESP

TEXT ' '

StepNum FF, MP, Supp, ESP

INTEGER 0

SupplyQty FF, MP, Supp, ESP

DECIMAL 0

UserID FF, MP, Supp, ESP

TEXT ' '


ResException


When FF, MP, Supp, 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 Each row in this table identifies an exception found while working with a resource. The exception may be resource-specific and/or SKU specific or associated with another resource-related data object.

Fulfillment

In Fulfillment, this table is only used by Constrained Production Planning logic. Within CPP an exception is generated by violating a soft constraint. For use with the CPP Level Loads process, constraints can be configured as soft in the CPPStratStep table. For use with CPP Workbench, constraints can be configured as soft through CPP Workbench Properties.

Level Loads inserts a row into this table for each exception it finds. For each resource whose load is being leveled, Level Loads deletes all previously existing Level Loads exceptions.

To see any exceptions generated as you work with Workbench, select the Exceptions tab on the Workbench: Details tab. In the JDA Fulfillment OnLine Expert, see Working with CPP Workbench for more information.

You cannot edit the values in this table.


This table stores all resource 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. SKU exceptions are stored in the SKUException table.

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

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.

Descr Description of this exception.

Exception Exception code number.

Fulfillment

The Calculate Plan process generates the following exceptions:

• 5201 No effective ProdMethod available for SKU _______on _______.Orders scheduled on this date will have a computed load of zero.


ResException

This exception is generated when you move the load for a SKU to a resource that does not have a production method.

The exception is also generated when the Level Loads process tries to move the load for a SKU to a resource that does not have a production method. If the exception is

Generated in the Level Loads process, the data is saved in the database.

• 5202 Planned order for SKU/family ____, using ProdMethod ____ violates lot size requirements on ____.

Lot-size requirements are specified in ProductionMethod:MinQty and IncQty, or (if those columns are blank) in SKUPlanningParam:MinQty (DRP or MPS) and IncQty (DRP or MPS). The constraint on violating lot-size requirements is configured as soft. A change to the planned order described in this exception has violated that constraint on the specified date.

• 5203 Soft Violation: Available capacity exceeded on resource ____, moving SKU/family ____; Load=____, Capacity=____, using ProdMethod ____ during period ____.

The available capacity for a Fulfillment/Production resource is specified in CalData:Avail for the CPP production capacity calendar. The constraint on exceeding resource capacity has been configured as soft. A change to the planned order described in this exception has violated that constraint.

• 5204 Soft Violation: Maximum onhand inventory exceeded for SKU/family ____, using ProdMethod ____, during period ____.

The maximum on-hand for a SKU is specified in SKUPlanningParam:MaxOH. The constraint on exceeding that maximum has been configured as soft. A change to the planned order described in this exception has violated that constraint.

• 5205 Soft Violation: Maximum coverage duration exceeded for SKU/family ____, using ProdMethod ____ during period ____.

The maximum coverage duration for a SKU is specified in SKUPlanningParam:MaxCovDur. The constraint on exceeding that maximum has been configured as soft. A change to the planned order described in this exception has violated that constraint.

• 5206 Soft Violation: Minimum safety stock violated for SKU/family ____, using ProdMethod ____ during period ____.

The minimum safety stock for a SKU is specified in SKUSafetyStockParam:MinSS. The constraint on falling below that minimum has been configured as soft. A change to the planned order described in this exception has violated that constraint.

• 5207 Soft Violation: Stockout quantity increased for SKU/family ____, using ProdMethod ____ during period ____.

The constraint on increasing the amount of stockout for a SKU in any period has been configured as soft. A change to the planned order described in this exception has violated that constraint.

• 5209 Violation: Period _____ still overloaded on resource _____ after leveling. Load _____, capacity _____.

After completely processing the specified resource, the Level Loads process could not eliminate the overload in this period.

• 5210 Violation: Planned Arrival for _____ to ship from _____ on _____. Ship date closed.

On the SchedShipDate shown for this planned arrival, the source location’s allocation calendar is closed.

• 5211 Violation: Planned Arrival for _____ to ship from _____ on _____ will be shipped late.

On the SchedShipDate shown for this planned arrival, the source location’s allocation calendar is closed. SchedShipDate has been changed to a later date, when the calendar is open.

• 5212 Violation: Planned Arrival for _____ to arrive at _____ on _____. Arrival date closed.


ResException

On the SchedArrivDate for this planned arrival, the destination location’s arrival calendar is closed.

• 5213 Violation: Planned Arrival for _____ to arrive at _____ on _____will arrive late.

On the SchedArrivDate for this planned arrival, the destination location’s arrival calendar is closed. SchedArrivDate has been changed to a later date, when the calendar is open.

• 5214 Violation: Planned Arrival quantity of _____ for _____ at _____ could not be met.

Level Loads moved a load for this item to a different location. It did not create firm planned arrivals because the total quantity of existing planned arrivals from the old location was less than the quantity being moved.

• 5217 ProductionMethod______ not found or not effective for planned order _______ in period ____.

The ProductionMethod (PlanOrder:ProductionMethod) for this planned order is not valid.

• 5218 Violation:PlanOrder for ____ on _____ has invalid schedule date.

The new schedule date for this planned order for this SKU (PlanOrder:SchedDate) is invalid. CPP does not create the planned order.

• 5219 Violation:Production Calendar for _____ is closed on _____.

CPP has attempted to create a new planned order with the specified schedule date (PlanOrder:SchedDate) as a result of adding or moving load, but the Production Calendar is closed on that date. CPP does not create the planned order.

• 5220 Resource has no availability

The production method for a SKU has a load offset type of three (ProductionMethod:OffsetType = 3), and there is not enough open time available for a resource within the planning period (SKU:OHPost + SKUPlanningParam:PlanDur).For example, if you try to use a type -3 production method for which there is no open time for a resource, this exception is generated. You will also get this exception if you try to use a production method step with a production duration of two days when there is only one day of available resource capacity within the planning period.

• 5221 Warning: ProdMethod ____ for SKU ____ has duplicate resources.

Level Loads or Workbench did not level the load for this SKU and production method, because duplicate resources were defined for them. If a resource is loaded more than once for a single production method, neither Level Loads nor Workbench will manipulate the load.

In the case of critical materials, multiple instances of the critical material subordinate SKU in the Bill of Materials (BOM) will also generate this message.

• 5222 Warning: Resource _____is a critical resource and doesn't have a valid critical item defined.

This exception generates when Level Production loads process is run for Critical Resource ( Type 6) but there is no critical item defined for the critical resource.


The Calculate Master Plan and Generate Master Plan process generates the following resource exceptions:

Exception

Number

Exception Text Category Id


Related Objects

5513 Resource in ImpResLoadDetail is not defined as an alternate resource for the SKU in AltProductionStep. Ignoring the record.

504 Invalid ImpResLoadDetail Parameter

5615 Resource Load Detail has an invalid SKU. 517 Invalid ResLoadDetail


ResException

Exception

Number



Related Objects

5616 Resource Load Detail has an invalid Resource. 517 Invalid ResLoadDetail

5617 Resource Load Detail has an invalid Supply Order. 517 Invalid ResLoadDetail

5619 Resource Load Detail has an invalid When Loaded Time, using supply order's finish date instead.

517 Invalid ResLoadDetail

5620 Resource Load Detail has an invalid Load Quantity. 517 Invalid ResLoadDetail

5639 Resource is not a storage resource. 525 Invalid Resource Parameter

5641 Resource and Location in Resource do not match with Resource and Location in StorageRequirement.

525 Invalid Resource Parameter

5734 Resource in ImpResLoadDetail is not defined as an alternate resource for the SKU in AltProductionStep. Ignoring the record.

504 Invalid ImpResLoadDetail Parameter

5642 Multiple resources are defined for an Item and Loc combination in StorageRequirement. Considering the Item, Loc, and Res mentioned in ResException.


5643 Multiple records are defined for a Loc, StorageGroup, and StorageClass in Res. Considering the Res and Loc mentioned in ResException.


5644 StorageGroup mentioned in Item and Res do not match with Item and Res defined in StorageRequirement. Ignoring the storage resource.


5700 Resource is overloaded at exceptiondate as a result of imported Resource Load Detail that has a load quantity in excess of available capacity.

518 Invalid Resource Load

5707 ProductionMethod: MinQty is greater than zero and less than ProductionMethod: IncQty. The process will use the ProductionMethod: IncQty value for ProductionMethod: MinQty.

511 Invalid ProdMethod Parameter

5708 Sourcing: MajorShipQty is greater than zero and less than Sourcing: MinorShipQty. The process will use the Sourcing: MinorShipQty value for Sourcing: MajorShipQty.

522 Invalid Sourcing Parameter

6000 Manufacturing resource is overloaded as a result of a soft constraint setting.

613 Resource Overload

Resource

6001 Transportation resource is overloaded as a result of a soft constraint setting.


Resource

6002 InHandling/OutHandling resource is overloaded as a result of a soft constraint setting.


Resource

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

602 Capacity Shortage

Resource Manufactured SKU RouteStep


ResException

Exception

Number



Related Objects

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


Resource Destination SKU RouteStep

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



6024 Cannot meet demand on time using this Supply Method. Sourcing lead time places the need date before the planning start date.

616 Sourcing Lead Time

Destination SKU Supply Method

6045 Cannot load firm plan order. Insufficient capacity of LoadQty. Firm plan order is met only RevisedQty.


Manufactured SKU

6046 Cannot load firm scheduled receipt. Insufficient capacity of LoadQty. Firm scheduled receipt is met only RevisedQty.


Manufactured SKU

6047 Cannot load firm RecShipment. Insufficient capacity of LoadQty. Firm RecShipment is met only RevisedQty.


Supply Order SKU

6048 Cannot load firm VehicleLoadLine. Insufficient capacity of LoadQty. Firm VehicleLoadLine is met only RevisedQty.


Supply Order SKU

6075 Cannot load firm plan order. Insufficient contiguous capacity of load quantity. Firm plan order is not loaded.


Supply Order SKU

6076 Cannot load scheduled receipt. Insufficient contiguous capacity of load quantity. Firm scheduled receipt is not loaded.


Supply Order SKUs

The Master Planner Workbench generates the following resource exceptions:

Exception

Number

Exception Text

7000 Adding planned order aborted due to hard resource constraint violation on resources for load quantity.

7001 Adding SKU load aborted due to hard resource constraint violation on resources for load quantity.

7002 Editing planned order aborted due to hard resource constraint violation on resources for load quantity.

7003 Editing SKU load aborted due to hard resource constraint violation on resources for load quantity.

7004 Firming action aborted due to hard resource constraint violation on resources for load quantity.


ResException

Exception

Number

Exception Text

7005 Action date is outside the planning horizon defined in planning properties.

7009 Add Plan Order action aborted due to non contiguous capacity on resources res for qty LoadQty.

7010 Edit Plan Order action aborted due to non contiguous capacity on resources res for qty LoadQty.

7500 Resource capacity exceeded when planned order loads were considered. Hard constraint on resource was violated.

7501 Resource capacity exceeded when planned order loads were considered. Soft constraint on resource was violated.

7502 Capacity on resource exceeded due to firming. Soft constraint on resource was violated.

The Optimize Production Changeover process generates the following resource exceptions:

Exception Number

Exception Text

6501 ProductionFamily: MinProdDur is zero; hence, it is set to bucket duration.

6502 ProductionFamily: MinProdDur is not an integer multiple of bucket duration; hence, it is converted to integer multiple of bucket duration.

6503 ProductionFamily: IncProdDur is not an integer multiple of bucket duration; hence, it is converted to integer multiple of bucket duration.

6504 ProductionFamily: MaxProdDur is not an integer multiple of bucket duration; hence, it is converted to integer multiple of bucket duration.

6505 ProductionFamily: MaxProdDur is nonzero and less than MinProdDur; hence, it is set to MinProdDur.

6506 ProductionFamily: MaxProdDur is not equal to the sum of MinProdDur and integer multiple of IncProdDur; hence, it is converted to respect it.

6507 ProductionFamily: IncProdDur is zero when MaxProdDur is nonzero; hence, IncProdDur is set to bucket duration.

6508 Unutilized capacity exists within the bucket after loading the resource with a production family.

6509 MinProdDur is not satisfied due to inadequate ResLoadDetail load of the production family SKUs until LookAheadDur.

6510 Production family load is split across the downtime.

6511 ProductionFamily:IncProdDur is not satisfied due to inadequate ResLoadDetail load of the production family SKUs until LookAheadDur.

6512 A production family is loaded on the resource beyond ProductionFamily: MaxProdDur.

6513 The ResLoadDetail: WhenLoaded date of a supply lies before the Optimize Production Changeover process Start Date.


ResException

Exception Number

Exception Text

6514 Scheduled receipts and/ or firm plan orders are loaded in the same bucket.

6515 Scheduled receipts and / or firm plan orders of different production families are loaded in the same bucket.

6516 Scheduled receipts and / or firm plan orders bucket is assigned to certain production family.

6517 The sum of scheduled receipts and/ or firm plan orders load is less than the maximum capacity of the bucket.

6518 The sum of scheduled receipts and/ or firm plan orders load is greater than the maximum capacity of the bucket.

6519 Plan orders of the assigned production family as that of the scheduled receipts or firm plan orders are pulled to utilize the remaining capacity of the bucket.

6520 The SKU’s LookAheadDur is violated to utilize the remaining capacity of the scheduled receipt or firm plan order’s bucket.

6521 The Production method has more then one critical resource. Hence, the resource mentioned in RES column is considered as a critical resource.

6522 MAXPRODLOAD exceeded while loading the entire plan order.

6523 Production family is loaded beyond the MAXPRODLOAD 6524 MINPRODLOAD is not satisfied due to inadequate planned order of the

family till look-ahead duration.

6525 INCPRODLOAD is not satisfied due to inadequate planned order of the family till the look-ahead duration.

6526 MINPRODLOAD is zero hence it is converted to maximum available capacity.

6527 Production Family: INCPRODLOAD is zero when MAXPRODLOAD is not zero. Hence INCPRODLOAD is adjusted.

6528 Critical resource loading is moved to the next bucket, leaving remaining capacity in the current bucket due to parallel dependent resource constraint in the current bucket.

6529 Optimize production changeover has not considered any resource for optimization as RES: PRODUCTIONFAMILYCHGOVEROPT is set to "No production family change over" for all the resources.

6530 Maximum production load is not zero and is less than minimum production load. Hence Maximum Production Load is adjusted.

6532 No valid production family specified for the critical resource. Hence the resource is ignored.

Supply

The Validate Input Data process generates the following resource exceptions:


ResException

Exception Number

Exception Text

9026 Res:CheckMaxCap can't have a value of 2. It is treated as Unconstrained (1)

ExceptionDate The date and time, during the planning horizon, when an exception occurs.

FunctionName The name of the function that generated this exception.

FunctionNum The number of the function that generated this exception.

Item The item associated with the SKU for which this exception was generated.

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.

LoadQty The load quantity (in resource units) for which this exception was generated.

Loc The location associated with the SKU for which this exception was generated.

ProdFamily The name of the production family for which the exception is raised.

ProcessID The identifier associated with the process in which the exception was raised.

ProductionMethod The production method associated with this exception.

Res The resource associated with this exception.

ReviewedStatus The review status of the exception record.

SeqNum The unique number associated with this exception record. This SeqNum will be used to link (ResException:SeqNum = ExceptionOrderRelation:ExceptionSeqNum) the exception record to its corresponding record in the ExceptionOrderRel table.

Severity


ResException

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.

Source The source location associated with this exception.

Sourcing The sourcing associated with the SKU that has raised this exception.

StepNum The step number associated with the method generating this exception.

SupplyQty The supply quantity associated with this exception.

UserID ID of the user who opened the process or page that generated this exception.

When The date and time when this exception was generated.


ResLoadDetail

ResLoadDetail Table included with: Fulfillment, Master Planning, Supply, Flowcasting, Enterprise Supply Planning


CustOrdLoadQty MP, ESP DECIMAL 0.0

DmdNeedDate 15 FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

DmdOrderSeqNum

16 FF, MP, Supp, Flowcasting, ESP

INTEGER -1

DmdOrderType 17 FF, MP, Supp, Flowcasting, ESP

INTEGER -1

ExpDate 10 FF,, Flowcasting MP, Flowcasting, ESP

DATETIME 01/01/1970

FcstOrdLoadQty MP, ESP DECIMAL 0.0


TEXT

LoadQty FF, MP, Supp, Flowcasting, ESP

DECIMAL 0


TEXT

NeedDate 11 FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

Offset MP, Supp, ESP DURATION 0

OptionSetName Supp TEXT ' ' ProcessID 8 FF, MP, Supp,

Flowcasting, ESP

OPTION_NUMBER


0

ProductionMethod

5 FF, MP, Supp, Flowcasting, ESP

TEXT

Res 3 FF, MP, Supp, Flowcasting, ESP

TEXT

ResLoc MP, Supp, ESP TEXT ' ' RoutingNeedCompleteDate

Supp DATETIME 01/01/1970


ResLoadDetail


SchedDate 12 FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

Source 9 Flowcasting TEXT ' '

SourceOpt Not used in this release

OPTION_NUMBER

1,2 1

SSLoadQty MP DECIMAL 0

StartDate 14 FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

StepNum 6 FF, MP, Supp, Flowcasting, ESP

INTEGER

SupplyOrderSeqNum

Supp INTEGER -1

SupplyQty FF, MP, Supp, Flowcasting, ESP

DECIMAL 0

SupplySeqNum 13 FF, MP, Supp, Flowcasting, ESP

INTEGER

SupplyType 4 FF, MP, Supp, Flowcasting, ESP

OPTION_NUMBER

1,2,3,4,5,6,7,8, 9,10,11,12,13, 14,17,105,110, 115,120,125,130, 135,140,145,-103, -105,-110,-115, -120,-125,-130, 135,-140,-150

WhenLoaded 7 FF, MP, Supp, Flowcasting, ESP

DATETIME

Table description Fulfillment

This table is used by Fulfillment only if ProductionMethod and ProductionStep records are defined that link SKUs to resources.


ResLoadDetail

Each row in the ResLoadDetail table describes the load placed on a resource by a single supply order (PlanOrder or SchedRcpt). Calculate Plan populates this table based on the ProductionMethod that is specified on the SchedRcpt and any firm or non-firm PlanOrder that is retained by Plan. Calculate Plan populates this table based on the highest priority effective production method for each PlanOrder that is created or for an existing order for which no ProductionMethod is specified. Whenever Constrained Production Planning (Load Leveler or Workbench) creates, modifies or deletes a PlanOrder, the corresponding ResLoadDetail data is appropriately updated. See the descriptions of the ProductionMethod and ProductionStep tables for information on how the dates and quantities of resource loads are determined by Calculate Plan and CPP.


Each row in the ResLoadDetail table describes the load on a resource caused by a single supply order (PlanOrder, SchedRcpt, or VehicleLoadLine) in a single planning bucket. This table may contain several rows for a given supply order and resource pair since it may take several buckets to complete building that supply order on that resource. For these multiple rows, the LoadQty will not necessarily have the same value. Resource Load Details are an output from the plan process.

Supply

Each row in the ResLoadDetail table describes the load on a resource caused by a single supply order (WorkOrder, Planned Supply Orders as generated by the Calculate Supply Plan process) in a single planning bucket. Resource Load Details are outputs from the Plan Resource Requirements and the Generate Finite Resource Plan processes. You can use the Resource Workbench to review the information as stored in this table. To manipulate data in this table use Flexible Editor.

Column descriptions CustOrdLoadQty CustOrdLoadQty is the resource load quantity (in resource units) that is pegged to customer orders.

Valid values for CustOrdLoadQty are 0.0 or greater.

DmdNeedDate The need date of the demand to which the supply order is pegged.

Fulfillment, Master Planning, ESP


DmdOrderSeqNum The order sequence number of the demand to which the supply order is pegged.



DmdOrderType The order type of the demand to which the supply order is pegged.



ExpDate The ExpDate value from the PlanOrder, SchedRcpt, or other order type record with which this ResLoadDetail record is associated.

FcstOrdLoadQty The resource load quantity (in resource units) that is pegged to forecast orders. The valid values for FcstOrdLoadQty are 0.0 or greater. JDA Enterprise Supply Planning Reference Guide 266 © 2014 JDA Software Group, Inc.- Confidential

ResLoadDetail

Item The item causing the load on this resource.

LoadQty The load on the resource, in terms of the capacity units of the resource. The capacity of the resource is specified in the production capacity calendar (Res:Cal) in terms of the same unit of measure.


LoadQty can be expressed as:

CustOrdLoadQty + FcstOrdLoadQty + SSLoadQty + any uncommitted load resulting from lot-sizing excesses

Loc Fulfillment

The location where the resource exists, which is the same as the location of the PlanOrder or SchedRcpt that is causing the load.


For Master Planning, the location of the supply order that results in the resource load described in this row. If this row describes the load on a transportation resource, Loc may be different from the location of the resource (Res:Loc).

Supply

The location of the supply order that results in the resource load described in this row.

NeedDate Master Planning, ESP

The date when production from this run is needed to meet demand.

Supply

This column contains the Need Date of the supply order that results in resource load.

Fulfillment

The NeedDate value from the PlanOrder that resulted in this resource load, or 1/1/1970 if the load is associated with a SchedRcpt.

Offset Offset is the difference between the supply due date and the load date.

OptionSetName Plan Resource Requirements or Generate Finite Resource Plan option set name. For the Generate Finite Resource Plan, the corresponding Reso run optionset is populated.

ProcessID This column contains the process ID of the output option set of the JDA Supply Resource Requirements Plan (RRP) process.



ProductionMethod The production method associated with this ResLoadDetail record.

Res The resource whose load is described in this row.

ResLoc


ResLoadDetail

The location of the resource used for this supply order. For some resources, such as transportation, this location may be different from the supply order location (Loc), which is a selection key for this table.

RoutingNeedCompleteDate The last date on which the step can be completed without causing the order to be late.

SchedDate Master Planning, ESP

The date when production from this run is actually scheduled to be available as part of the projected on hand.

Fulfillment

The SchedDate value from the PlanOrder or SchedRcpt that resulted in this resource load.

Supply

SchedDate is the date when the supply order is actually scheduled to be completed.

Source Note: This column is not used in this release.

SourceOpt Note: This column is not used in this release.

SSLoadQty The resource load quantity (in resource units) that is pegged to stock orders.

StartDate Fulfillment

The start date value associated with the Plan Order that is placing this resource load.

Supply

The start date of the current step.

StepNum The number of the ProductionStep used to calculate the load on the resource.

SupplyOrderSeqNum The sequence number of supply order.

SupplyQty Fulfillment

PlanOrder:Qty or SchedRcpt:Qty - the SKU quantity of the order that is placing this load.


The scheduled quantity of the associated supply order. Unlike LoadQty which is measured in terms of the capacity units of the resource, SupplyQty is measured in terms of SKU units.

Supply

This is the quantity of supply orders such as Work Orders, Planned Supply Orders (PSO), that imply a planning load on the supply quantity resource.

SupplySeqNum Needed to identify the supply order for which this resource load record was created. The ResLoadDetail record is related to the supply record through the DmdOrderSeqNum, DmdOrderType, DmdNeedDate, and SupplySeqNum.

SupplyType


ResLoadDetail

Valid values for SupplyType are 1, 2, 4 - 14, 17, 105, 110, 115, 120, 125, 130, 135, 140, 145, -103, -105, -110, -115, -120, -125, -130, -135, -140, -150.

Note: Fulfillment allows only supply types 2, 6, and 9.

Type of supply order placing load on the resource.


The supply order is associated with PlanArriv.


SupplyOrder = PlanOrder:OrderID

If ProductionMethod:OffsetType is set to 3 (Use ProductionStep:ProdDur), SupplyType must be set to 2.

• 4: Recommended Arrival (RecShip table)

SupplyOrder = RecShip:OrderID

• 5: Intransit In (VehicleLoadLine table)

SupplyOrder = VehicleLoadLine:LoadID

Item = VehicleLoadLine:Item


SupplyOrder = SchedRcpts:SchedRcptsID

• 9: Firm Planned Order

SupplyOrder = PlanOrder:OrderID

• 10: Firm Recommended Shipment

SupplyOrder = RecShip:OrderID


The supply order is associated with PlanArriv:Dest

• 17: The change over load or loss between the families on the resource

• 105 = PSO

SupplyPlanResult:OrderSeqNum

• 130: Work Order

WorkOrder:WorkOrderNum

Note: The SupplyType values of 1, 2, 5, 6, 9, 11 are applicable to Master Planning.

WhenLoaded The date and time of the load on the resource.


ResProjStatic

ResProjStatic Table included with: Fulfillment, Master Planning, Supply, ESP


AvailCap MP, Supp, ESP DURATION 0

CBMPTotLoad Not used in this release

DECIMAL 0.0

CBMPTotLoadCustOrd


DECIMAL 0.0

CBMPTotLoadFcstOrd


DECIMAL 0.0

CBMPTotLoadSSOrd Not used in this release

DECIMAL 0.0

CBMPTotLoadUncomm


DECIMAL 0.0

ChgCost FF DECIMAL 0.0

CPPCostResUtil FF DECIMAL 0.0 CPPCostSKUProd FF DECIMAL 0.0 CPPLoadFirmOrder FF DECIMAL 0.0 CPPLoadPlanOrder FF DECIMAL 0.0 CPPLoadSchedRcpt FF DECIMAL 0.0 CPPOverCap FF DECIMAL 0.0 CPPTotCap FF, MP, ESP DECIMAL 0.0 CPPTotLoad FF DECIMAL 0.0 CPPTotLoadChg FF DECIMAL 0.0 CPPTotLoadProd FF DECIMAL 0.0 CPPUnusedCap FF DECIMAL 0.0 DistRequirementLoad

MP DECIMAL 0

Dur FF, MP, Supp, ESP

DURATION 0

FirmArrivalRequirementLoad

MP, ESP DECIMAL 0

FirmPlanOrderRequirementLoad

MP, ESP DECIMAL 0

IdealUtilization ESP FLOAT 0 Loc 1 FF, MP, Supp,

ESP TEXT

MaxUtilization ESP FLOAT 0

MinUtilization ESP FLOAT 0 MPChgOverLoad MP, ESP DOUBLE 0 MPFirmPlanArrivLoad

MP, ESP DECIMAL 0.0

MPFirmPOLoad MP, ESP DECIMAL 0.0


ResProjStatic


MPOvertimeCap ESP FLOAT 0 MPOvertimeLoad ESP FLOAT 0 MPFirmRecShipLoad Not used in

this release DECIMAL 0.0

MPInventory Not used in this release

DECIMAL 0.0

MPPlanArrivLoad MP, ESP DECIMAL 0.0

MPPOLoad MP, ESP DECIMAL 0.0 MPRegularCap ESP FLOAT 0

MPRegularLoad ESP FLOAT 0 MPRecShipLoad Not used in

this release DECIMAL 0.0

MPSchedRcptLoad MP, ESP DECIMAL 0.0

MPTotLoad MP, ESP DECIMAL 0.0 MPTotLoadCustOrder

MP, ESP DECIMAL 0.0

MPTotLoadFcstOrder MP, ESP DECIMAL 0.0 MPTotLoadSSOrder MP, ESP DECIMAL 0.0

MPTotLoadUncomm MP, ESP DECIMAL 0.0 MPVehLoadLineLoad MP, ESP DECIMAL 0.0

OptionSet 4 FF, MP, Supp, ESP

TEXT

OvertimeAvailCap ESP FLOAT 0

PctUsed FF, MP, Supp, ESP

DECIMAL 0.0

PlannedSupplyOrderLoad

Supp DECIMAL 0

ProcessDate FF, MP, Supp, ESP

DATETIME 01/01/1970

ProdRequirementLoad

MP, ESP DECIMAL 0

RequirementPlanAvailCap

MP, ESP DECIMAL 0

Res 2 FF, MP, Supp, ESP

TEXT

ResCost FF DECIMAL 0.0

ResCountException FF, MP, Supp, ESP

INTEGER 0

ResSourceException FF, MP, ESP DECIMAL 0.0 SchedRcptsRequirementLoad

MP, ESP DECIMAL 0

StartDate 3 FF, MP, Supp, ESP

DATETIME


ResProjStatic


TotalRequirementLoad

MP, ESP DECIMAL 0

TotLoad Supp DECIMAL 0 UserID FF, Supp TEXT ' ' VehicleLoadLineRequirementLoad

MP, ESP DECIMAL 0

WorkOrderLoad Supp DECIMAL 0

Table description Each row in this table presents projections for a resource for a particular time period. Rows are written to this table as a result of running the Store Resource Projections process. When you rerun the Store Resource Projections process for a specific option set (see the OptionSet column), the rows for that option set is replaced. See the Store Resource Projections process page in the OnLine Expert for more information.

Note: Since the ResProjStatic table simply stores static data, you must run the Store Resource Projections process to recalculate data after changes have been saved by Workbench or if Calculate Plan/Calculate Master Plan or Generate Master Plan has been rerun.

For JDA Master Planning, the resource loads and capacities for a bucketing calendar will be extracted to this table.

Fulfillment

This table is used by Fulfillment only if ProductionMethod and ProductionStep records are defined that link SKUs to resources.

Supply

JDA Supply does not use the Store Resource Projections process. This is a reference only table.

Column descriptions AvailCap Master Planning

The available capacity on a resource.

Supply

This is a reference only column.

ESP

AvailCap = MPRegularCap - MPTotLoad

If the AvailCap, by the previous calculation is negative, it is made 0.

ChgCost The total cost for all changeovers on this resource in this time period.

For Fulfillment/Production, ChgCost is the total changeover costs for planned orders. The system calculates this as follows:

(Res:AvgFamilyChgCost × (number of families - 1)) +

(Res:AvgSKUCHgCost × (number of SKUs - number of families))


ResProjStatic

CPPCostResUtil CPP Resource Utilization Cost (CPPCostResUtil) is the cost of using this resource for the production planned in this period, calculated as:

Res:Cost × resource load excluding changeovers

This value does not include raw material and other SKU-specific costs, which are included in CPPCostSKUProd. It also does not include changeover costs, which are included in ChgCost.

CPPCostSKUProd CPP SKU Production Cost (CPPCostSKUProd) is the cost of producing the SKUs planned for this period, including raw materials and any other costs necessary to produce the SKUs. CPPCostSKUProd is calculated as the sum of:

for all the SKUs planned for the period.

This value does not include the cost of using the resource (CPPCostResUtil) or changeover costs (ChgCost).

CPPLoadFirmOrder CPP Firm Planned Order Load (CPPLoadFirmOrder) is the load on this resource due to firm planned orders in this period, expressed in resource capacity units. This value does not include changeover load, which is found in CPPLoadOtherChg.

CPPLoadPlanOrder CPP Planned Order Load (CPPLoadPlanOrder) is the load on this resource due to non-firm planned orders in this period, expressed in resource capacity units. This value does not include changeover load, which is found in CPPLoadOtherChg.

CPPLoadSchedRcpt CPP Scheduled Receipts Load (CPPLoadSchedRcpt) is the load on this resource due to scheduled receipts in this period, expressed in resource capacity units. This value does not include changeover load, which is found in CPPLoadOtherChg.

CPPOverCap CPP Capacity Overload (CPPOverCap) is the amount by which the load on this resource exceeds total capacity in this period, expressed in resource capacity units. The system calculates CPPOverCap as the negative of CPPUnusedCap.

CPPTotCap CPP Total Capacity (CPPTotCap) is the total number of resource capacity units that can be used for production on this resource in this period, based on the CPP production capacity calendar (Res:Cal) specified for this resource. That calendar defines the resource’s daily capacity in CalData:Avail. To calculate the value of CPPTotCap, the system converts Avail into capacity per minute.

CPPTotCap = minutes in period × capacity per minute × Res:AdjFactor

(If the value of CalData:Avail varies during a calendar period, the system applies the appropriate value to each segment of the period.)

CPPTotLoad The total load on this resource due to both production load and changeover load in the specified period. The system calculates CPPTotLoad as:

CPPTotLoad = CPPTotLoadProd + CPPTotLoadChg

CPPTotLoadChg CPP Total Changeover Load (CPPTotLoadTot) is the total load on this resource due to changeovers in this period, expressed in resource capacity units.


ResProjStatic

CPPTotLoadProd CPP Total Capacity Consumed (CPPTotLoadProd) is the total load on this resource due to production in this period, expressed in resource capacity units. The system calculates CPPTotLoadProd as:

CPPLoadFirmOrder + CPPLoadPlanOrder + CPPLoadSchedRcpt.

CPPUnusedCap CPP Unused Capacity (CPPUnusedCap) is the unused capacity on this resource in this period, expressed in resource capacity units. The system calculates CPPUnusedCap as:

CPPTotCap - CPPTotLoadChg - CPPTotLoadProd

DistRequirementLoad The load on this resource resulting from distribution requirements.

Dur The duration of the time interval that applies to the data in this row. The values for Dur are based on the Calendar specified for the userview.

Supply


FirmArrivalRequirementLoad The load on this resource resulting from firm plan arrivals.

FirmPlanOrderRequirementLoad The load on this resource resulting from firm plan orders.

IdealUtilization User specified ideal utilization value in the CalAttribute table. The associated CalAttribute:Attribute is IdealUtilization (db value is 15).

Loc The location of this resource.

Supply


MaxUtilization User specified maximum utilization value in the CalAttribute table. The associated CalAttribute:Attribute is MaxUtilization (db value is 16).

MinUtilization User specified minimum utilization value in the CalAttribute table. The associated CalAttribute:Attribute is MinUtilization (db value is 14).

MPChgOverLoad The change over load/loss between the families on the resource.

MPFirmPlanArrivLoad Master Planning Firm Planned Arrival Load (MPFirmPlanArrivalLoad) is the load placed on the resource due to firm plan arrivals.

MPFirmPOLoad Master Planning Firm Planned Order Load (MPFirmPOLoad) is the load on this resource resulting from firm planned orders.

MPOvertimeCap


ResProjStatic

Overtime capacity for all overtime levels specified in the CalAttribute table. The associated CalAttribute:Attribute values are OvertimeAvail-Level1 (db value is 7), OvertimeAvail-Level2 (db value is 8), and OvertimeAvail-Level3 (db value is 9).

ESP (Deep Tree)

MPOvertimeCap = 0

MPOvertimeLoad This value is calculated as MPTotLoad – MPRegularCap.

• If MPOvertimeLoad is negative, it is calculated to be zero.

• If MPOvertimeLoad > MPOvertimeCap, MPOvertimeLoad = MPOvertimeCap. This is to handle soft loading of a resource with overtime.

• If Res:OvertimeSw = 0, MPOvertimeload = 0. This is to handle soft loading of a resource with overtime but OvertimeSw as 0.

ESP (Deep Tree)

MPOvertimeLoad = 0

MPPlanArrivLoad The load placed on the resource due to plan arrivals.

MPPOLoad Master Planning Planned Order Load (MPPOLoad) is the load on this resource resulting from planned orders.

MPRegularCap Regular capacity specified for the resource.

ESP (Deep Tree)

MPRegularCap = CPPTotCap

MPRegularLoad This value is calculated as MPTotLoad – MPOvertimeLoad.

ESP (Deep Tree)

MPRegularLoad = MPTotLoad

MPSchedRcptLoad Master Planning Scheduled Receipts Load (MPSchedRcptLoad) is the load on this resource resulting from scheduled receipts.

MPTotLoad Master Planning Total Load (MPTotLoad) is the total load on a resource. The MPTotLoad can be due to the load generated by supplies like PlanOrders, FirmPlanOrders, PlanArrivs, FirmPlanArrivs, SchedRcpts, and the VehicleLoadLines.

The MPTotLoad can also be expressed as:

MPTotLoadUncomm + TotIndDmdLoad

where TotIndDmdLoad consists of MPTotLoadCustOrder, MPTotLoadFcstOrder, and MPTotLoadSSOrder

MPTotLoadCustOrder Master Planning Total Load Customer Order (MPTotLoadCustOrder) is the load on this resource resulting from customer orders.

MPTotLoadFcstOrder


ResProjStatic

Master Planning Total Load Forecast Order (MPTotLoadFcstOrder) is the load on this resource resulting from forecast orders.

MPTotLoadSSOrder Master Planning Total Load Safety Stock Order (MPTotLoadSSOrder) is the load on this resource resulting from safety stock orders.

MPTotLoadUncomm Master Planning Total Uncommitted Load ((MPTotLoadUncomm) is the total resource load from production that is not committed to any demand order. This includes excess production as a result of lot-sizing and unused scheduled supplies (SchedRcpts, VehicleLoadLines, PlanOrders with FirmPlanSw = Yes).

MPVehLoadLineLoad Master Planning Vehicle Load Line Load (MPVehLoadLine) is the load on this resource resulting from vehicle load lines.

OptionSet The name of the option set used when running the Store Resource Projections process.

Note: When viewing data in this table, you must always include OptionSet to prevent double-counting of data from multiple options sets.

Supply


Master Planning


OvertimeAvailCap This value is calculated as MPOvertimeCap - MPOvertimeLoad.

ESP (Deep Tree)

OvertimeAvailCap = 0

PctUsed Master Planning

The percent of the load on this resource that is used in the specified period. The system calculates PctUsed as:

PctUsed = (MPTotLoad / MPTotCap) x 100

Supply


ESP

PctUsed = (MPTotLoad / MPRegularCap) * 100

PlannedSupplyOrderLoad The load on a resource because of a planned supply order for a defined bucket. For JDA Supply, this is a reference only column.

ProcessDate The date and time when the Store Resource Projections process was run.

Supply


ProdRequirementLoad JDA Enterprise Supply Planning Reference Guide 276 © 2014 JDA Software Group, Inc.- Confidential

ResProjStatic

The load on this resource resulting from production requirements.

RequirementPlanAvailCap The available capacity on this resource.

Res The resource associated with these projections.

Supply


ResCost The production cost for this period, calculated as:

CPPCostResUtil + CPPCostSKUProd

ResCountException The count of exceptions for a resource as associated in the ResException table.

Supply


ResSourceException The load on the resources corresponding to the exceptions.

SchedRcptsRequirementLoad The load on this resource resulting from scheduled receipts.

StartDate The beginning date and time for the time interval associated with the projections in this row. The system bases time intervals on the calendar specified in the process option set.

Supply


TotalRequirementLoad The total load on this resource resulting from the loads generated by production requirements, distribution requirements, firm plan orders, firm plan arrivals, scheduled receipts, and vehicle load lines.

TotLoad The total load placed on a resource. For JDA Supply, this is a reference only column.

UserID The identifier of the user who ran the Store Resource Projections process.

Supply


VehicleLoadLineRequirementLoad The load on this resource resulting from vehicle load lines.

WorkOrderLoad The load on a resource because of a work order for a defined bucket. For JDA Supply, this is a reference only column.


SchedRcpts

SchedRcpts Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


Action FF, MP, Flowcasting

OPTION_NUMBER

0,1,2,3 0

ActionAllowedSw FF, MP, Flowcasting

BOOLEAN 0

ActionDate FF, MP, Flowcasting

DATETIME 01/01/1970

ActionQty FF, MP, Flowcasting

DECIMAL 0

ExpDate 4 FF, MP, IPO, Flowcasting

DATETIME 01/01/1970

ExplodeSw FF, MP, IPO, Flowcasting, ESP

BOOLEAN 0


TEXT

LastCompletedStep

FF, MP, Flowcasting

INTEGER 0


TEXT

OrderNum FF, MP, Flowcasting, ESP

INTEGER 0

PctComplete MP DECIMAL 0 ProductionMethod FF, MP,

Flowcasting, ESP

TEXT ' '


DECIMAL 0

QtyReceived MP, IPO, Flowcasting, ESP

DECIMAL 0

RevisedDate MP DATETIME 01/01/1970


SchedDate 3 FF, MP, IPO, Flowcasting, ESP

DATETIME


INTEGER 0


SchedRcpts


SourceOpt MP OPTION_NUMBER

1

StartDate 5 FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

SupplyID FF TEXT

Table description Each row in this table contains a scheduled receipt that has been imported from an external execution system.

Fulfillment

All Fulfillment processes and views consider a scheduled receipt to be a firm replenishment for the SKU. You can import your replenishment schedule into the SchedRcpts table.

Fulfillment processes do not create, update, or delete quantity, date, or production method data in the Scheduled Receipts table. Therefore, you can use SchedRcpts effectively to interface with data from external systems.

The Generate Supply and Demand Links based on Priority process uses this table to recommend that a scheduled receipt be canceled, or that its SchedDate be changed, to prevent the generation of additional unneeded supplies.


The application can recommend that a scheduled receipt be canceled, or that its SchedDate be changed, to prevent the generation of additional unneeded supplies.

IPO


Column descriptions Action The action (Push, Pull, or Cancel) recommended by the Generate Supply and Demand Links/Generate Supply and Demand Links based on Priority process, if the supply ActionAllowedSw is enabled.

• 0: None

• 1: Pull

• 2: Push

• 3: Cancel

ActionAllowedSw If the ActionAllowedSw = 0, the scheduled receipts will be recognized at the SchedDate. If the ActionAllowedSw = 1, the scheduled receipts will be recognized at the RevisedDate.



ActionQty


SchedRcpts

The supply quantity for which the action is recommended.

ExpDate The date that the perishable supply represented by the scheduled receipt is scheduled to expire.

ExplodeSw This switch determines whether or not to create dependent demands for a scheduled receipt.

• Yes: This order must be exploded according to the BOM structure of the associated SKU to create dependent demands in the DepDmdStatic table.

• No: No dependent demand is created on the subordinate for this scheduled receipt.

IPO

IPO uses this switch to determine if dependent demand should be calculated in memory. IPO does not use the DepDmdStatic table.

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

LastCompletedStep Master Planning

For Master Planning, if this scheduled receipt is work in process (WIP) resulting from a multi-step production method, set LastCompletedStep to the ProductionStep:StepNum of the last production method step that has been completed. If LastCompletedStep is 0, Master Planning assumes the multi-step production method has not yet started.

For WIP orders, Master Planning uses the following SchedRcpt columns to determine which row in the ProductionStep table represents the last completed step in a multi-step production method:

• Item

• Loc

• ProductionMethod

• LastCompletedStep

If the last step in the production method has not been completed, this scheduled receipt will create loads on the resources associated with the remaining steps in the production method.


For JDA Fulfillment/Production, set the ProductionStep:StepNum of the last production method step that has been completed. For any step that is less than or equal to the LastCompletedStep, this scheduled receipt will not place load on the resources in those steps.

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

OrderNum The sequence number generated for the scheduled receipts by the Calculate Master Plan process.

PctComplete If you have specified a value for LastCompletedStep, specify the percentage of the current step (the one following the LastCompletedStep) that has been completed.

Master Planning first calculates the total load this scheduled receipt would create on the resource associated with this ProductionStep. It then reduces that total load by the percentage specified in PctComplete.


SchedRcpts

ProductionMethod The production method associated with this scheduled receipt.

Qty The quantity of this scheduled receipt.

QtyReceived For work in progress orders, this is the amount of product that has already been manufactured or received. If QtyReceived is greater than 0, the system plans the remaining quantity (Qty – QtyReceived). This remaining quantity determines the dependent demand quantities (if ExplodeSw = Yes) and the loads placed on resources.

RevisedDate This is the available date after constraining this SchdRcpt as per the Firm Supply Constraint option (Only Material, Only Capacity or Both Material and Capacity). The Firm Supply Constraint option, necessary for processing scheduled supplies, is set in the Calculate Master Plan process page. The supply will be recognized at the RevisedDate if the ActionAllowedSw = Yes (1). Else, the supply will continue to be recognized at the SchedDate.

If the Firm Supply Constraint option is Capacity only: RevisedDate is the greater of the SchedDate and the capacity loading completion date, irrespective of the material available date.

If the Firm Supply Constraint option is Material only: RevisedDate is the greater of the SchedDate and the material available date, irrespective of the capacity loading completion date.

If the Firm Supply Constraint option is Capacity & Material: RevisedDate is the greater of the SchedDate and the date when adequate capacity and material are both available for the successful processing of the scheduled supply.

RevisedExpDate The revised expiry date of the scheduled receipts. If ActionAllowedSw = 1, then RevisedExpDate is calculated as:

RevisedExpDate = RevisedDate + difference between scheduled supply exp date and scheduled date.


SchedDate The date when production from this run is actually scheduled to be available as part of on hand inventory.


This must be an open date in the finish calendar (ProductionMethod:FinishCal) used by the ProductionMethod associated with this scheduled receipt. If Master Planning recommends changing the SchedDate, it specifies a new value in RevisedDate.

Note: This field is not editable once a value is entered. The reason for this is that SchedDate is a primary key column and if the value is changed, an integrity constrained error may result.

SeqNum This column is populated by the user during the import of scheduled receipts to distinguish between multiple scheduled receipts that are for the same SKU and have the same SchedDate and StartDate combinations, but different quantities. Otherwise, this column can be left at its default of 0.

IPO


SourceOpt The Source Option column defines the source of the scheduled receipt.


SchedRcpts

• 1: User Imported

• 2: Imported From Sequencing

StartDate Master Planning, IPO, ESP

The start date associated with the scheduled receipt.


Specifies the date when a particular scheduled receipt is applied to the resource referenced in the first production method step.

SupplyID Represents a unique ID for the supply that is used by the Dynamic Allocation logic.


SchedRcptsDetail

SchedRcptsDetail Table included with: Enterprise Supply Planning


ExpDate 4 ESP DATETIME 01/01/1970

Item 1 ESP TEXT

Loc 2 ESP TEXT QtyInMove ESP FLOAT 0

QtyInQueue ESP FLOAT 0 QtyInRun ESP FLOAT 0 SchedDate 3 ESP DATETIME 01/01/1970

SeqNum 6 ESP INTEGER 0

StartDate 5 ESP DATETIME 01/01/1970

StepNum 7 ESP INTEGER StepSchedDate ESP DATETIME 01/01/1970

StepStartDate ESP DATETIME 01/01/1970

Table description This table defines the Work in Process (WIP) quantities associated with a scheduled receipt. The Item, Loc, SchedDate, ExpDate, StartDate, and SeqNum fields in this table must match the fields with the same names in the SchedRcpts table. These fields identify the scheduled receipt whose WIP details are defined in this table.

Column description ExpDate Expiry date of a perishable supply represented by the scheduled receipt whose WIP details are defined in this table.

Item Item whose WIP quantities are defined in this table.

Loc Location associated with the SKU whose WIP quantities are defined in this table.

QtyInMove Quantity of the item processed in an operation and ready to move to the next operation or stage. This does not consume capacity or material.

QtyInQueue Quantity of the item in front of an operation, waiting to be processed. This consumes capacity but does not consume material.

QtyInRun


SchedRcptsDetail

Quantity of the item involved currently in an operation. This consumes capacity but does not consume material.

SchedDate Date on which the quantity produced, based on the scheduled receipt, is available as on-hand inventory.

SeqNum User defined value to distinguish between multiple scheduled receipts, of the same SKU, that have the same SchedDate and StartDate combinations but different quantities.

StartDate Scheduled receipt's start date.

StepNum Identifier for the step, in the production method, for which WIP quantities are defined in this table.

StepSchedDate Date on which the quantity produced by this step (identified by StepNum) is available as oh-hand inventory.

StepStartDate Step's start date. The step is identified by StepNum.


SeasonError

SeasonError Table included with: Fulfillment, Demand, Master Planning, Flowcasting, Enterprise Supply Planning


DmdGroup 2 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT

DmdUnit 1 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT

Dur FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

DURATION 0

Factor FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

DECIMAL 0.0

Loc 3 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT

Model FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

TEXT ' '

PerNum FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

INTEGER 0

StartDate 4 FF, Dmd, MP, Flowcasting, ESP (Deep Tree)

DATETIME

Table description Each row in this table defines the seasonality factor (SeasonError:Factor (on page 286)) for a particular DFU. The seasonality factor is used to weight statistical safety stock by period according to seasonal patterns of demand.

Column descriptions DmdGroup The demand group associated with the DFU whose seasonality factor is defined in this row.

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

Dur


SeasonError

The length of the time interval that starts at StartDate.

Factor The value resulting from the calculation of seasonality of forecast error associated with this DFU.

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

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

PerNum The number of the period for which the seasonality factor is being calculated.

StartDate The starting point of the time interval associated with the DFU defined in this row.


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


0


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



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 Enterprise Supply Planning Reference Guide 290 © 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 Enterprise Supply Planning Reference Guide 291 © 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).


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 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 293)= 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 (on page 152) and OrderLink (on page 191) 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 Enterprise Supply Planning Reference Guide 296 © 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 290) 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


TEXT


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,


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 299) 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 303) setting.

Outside the CustOrderDur, the forecast is consumed according to the rule specified in the FcstConsumptionRule (on page 310) 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.






• 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 Enterprise Supply Planning Reference Guide 302 © 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 312)) 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 299)). Prorated forecast quantities are shown in SKUProjStatic:ProratedAllocTotFcst (on page 414).

If DmdToDate (on page 303) 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 312) 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 310) 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 299)).

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

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

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

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


• 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 309)

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

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 302). 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 303) 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 312)), 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 310) as forward consumption duration and FcstSecConsDur (on page 311) 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 310) as backward consumption duration and FcstSecConsDur (on page 311) 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 310) as forward consumption duration and FcstSecConsDur (on page 311) 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 310) as backward consumption duration and FcstSecConsDur (on page 311) 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


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


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

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

IndDmdUnitCost User-defined standard cost for this SKU.


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 303) is set to 6 or 7 to define a second duration, in addition to the one defined by CustOrderDur (on page 302), 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 303).

Refer to DmdToDate, ProrationDur (on page 312), 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 312) 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 303), ProrateSw (on page 312), 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.


SKUEffInventoryParam

SKUEffInventoryParam Table included with: Enterprise Supply Planning



Item 1 ESP TEXT

Loc 2 ESP TEXT

MaxCovDur ESP DURATION MaxOHQty ESP DECIMAL

MinSSQty ESP DECIMAL 0.0

SSCovDur ESP DURATION 0

Table description Defines an item’s inventory levels that must be maintained at a location.

The inventory levels are specified in time units or quantity. Use this table to specify the time varying inventory levels.

Column description Eff The inventory levels of an item can vary with time. For example, in a peak season the minimum safety stock level must be high. This field is used to specify the effective start date from which the inventory levels specified in this table are applicable.

Item Item for which inventory levels are specified in this table.

Loc Location where the item, for which the inventory levels are specified in this table, exists.

MaxCovDur Maximum coverage duration is the maximum safety stock level that must be maintained at a location, in terms of time units. For example, if this value is 525600, the inventory quantity to be maintained as the safety stock level must not be more than what is required to meet the next 365 days (525600 minutes) of demand, starting from the Eff date.

If prebuild is enabled, a plan cannot prebuild beyond this duration.

MaxOHQty Maximum on-hand quantity is the maximum safety stock level that must be maintained at a location, in terms of quantity.

MinSSQty


SKUEffInventoryParam

Minimum safety stock quantity is the minimum safety stock level that must be maintained at a location, in terms of quantity.

SSCovDur Safety stock coverage duration is the minimum the safety stock level that must be maintained at a location, in terms of time units. For example, if this value is 7200, the inventory quantity maintained as safety stock must be sufficient to meet the next five days (7200 minutes) of demand, starting from the Eff date.


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


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 344) column to filter for the date and time that the exception occurred within the planning horizon.


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 (on page 376)) 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 Enterprise Supply Planning Reference Guide 321 © 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 (on page 357) - SKUPerishableParam:MinShelfLifeDur (on page 356)

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


SKUException

• 0059 Expired inventory found

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.


SKUException

• 0074 Demands at or after ExpDate ignored.

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


SKUException

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.

• 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


SKUException

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

• 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 (on page 370)=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


SKUException

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.

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.


SKUException

• 0244 Annual Forecast Frequency Exceeds 52

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

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


SKUException

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.

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.


SKUException

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.

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

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

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


SKUException

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 (on page 494) or VehicleLoad:ArrivDate (on page 491).

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

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


SKUException

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

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.


SKUException

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


The Generate Forecast Orders process generates the following SKU exceptions:

Exception

Number



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


SKUException

Exception

Number



Related

Objects

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 5531 Working Calendar has an invalid master calendar,

using a default all-open calendar instead. 605 Invalid Calendar

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.


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.


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.



SKUException

Exception

Number



Related

Objects

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

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.



SKUException

Exception

Number



Related

Objects

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.


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.



SKUException

Exception

Number



Related

Objects

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.


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.


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.



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.




SKUException

Exception

Number


Category Descriptio

n

Related Objects

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.



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


SKUException

Exception

Number


Category Descriptio

n

Related Objects

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.

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.


SKUException

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:

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


SKUException

Exception Number

Exception Text

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


SKUException

Exception Number

Exception Text

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.

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.


SKUException

Exception Number

Exception Text

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. 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 JDA Enterprise Supply Planning Reference Guide 344 © 2014 JDA Software Group, Inc.- Confidential

SKUException

• 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

• 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. JDA Enterprise Supply Planning Reference Guide 345 © 2014 JDA Software Group, Inc.- Confidential

SKUException

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.

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


SKUException

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.

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.


SKUExternalFcst

SKUExternalFcst Table included with: Fulfillment, Master Planning, Supply, Inventory Policy Optimization, Flowcasting


Dur FF, MP, IPO, Flowcasting

DURATION 0

Item 1 FF, MP, Supp, IPO, Flowcasting

TEXT

Loc 2 FF, MP, Supp, IPO, Flowcasting

TEXT

OrderSeqNum FF, MP, Supp, Flowcasting

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

-125

Project 4 FF, MP, Supp, IPO, Flowcasting

TEXT ' '

Qty FF, MP, Supp, IPO, Flowcasting

DECIMAL 0

Revenue Supp DECIMAL 0 StartDate 3 FF, MP, Supp,

IPO, Flowcasting

DATETIME

SubstLevel Supp INTEGER 0 SubstOperator Supp,

Flowcasting OPTION_NUMBER

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

SupersedeSw FF, MP, Flowcasting

BOOLEAN 0

Table description Each row in this table identifies a quantity of forecast demand for one SKU during a specific period. Forecast for an SKU can originate from JDA Demand or from another forecasting system. If the forecast originates from JDA Demand, the DFU forecast data is placed in the DFUtoSKUFcst table by the Transfer Forecast process. If the forecast originates in another forecasting system, the SKU forecast must be imported into the SKUExternalFcst table.

Fulfillment

Any logic that relies on SKU forecast data sums any rows in this table together with any corresponding rows in the DFUTOSKUFcst table to determine the SKU forecast over time.


SKUExternalFcst

Master Planning

The Generate Forecast Orders process and Calculate Master Plan processes use this SKU-level demand.

Supply

Using the Calculate Supply Plan: Onhand/Forecast Source process, you can specify the forecast source as either the SKUExternalFcst or FcstOrder table.

IPO

The Generate Forecast Orders process uses this SKU-level demand and the forecast is used in the mean daily demand computation (after allocation).

Column descriptions Dur The duration of this period.

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

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

OrderSeqNum Order Sequence Number (OrderSeqNum) is a system generated number. This Supply Order identifier is used for mapping output records to input order information.


Supply

This is an information only field and holds a default value of -115.


IPO


Qty External forecast quantity.

Revenue The selling price associated with this order line item. The valid values for revenue are -1, 0 or greater.

StartDate The starting date and time of the period whose external forecast appears in this row.

Supply

The need date for the external forecast defined in this row.

SubstLevel


SKUExternalFcst

Substitution Level (Substevel) contains the substitution level used by Supply. Substitution levels are also used to sequence the processing of rules. A global operator and level can be specified to restrict rules within a process execution.

For example, if substitution level is specified as < 3, only rules with a level < 3 are considered.

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

SubstOperator Substitution Operator (SubstOperator) contains the Substitution operator used by Supply. An operator and level can be specified in each demand table, so different rules can apply to different demands. 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.

The validations for this field are described as follows:

• 0 = Global criteria

• 1 = Greater than or equal to

• 2 = Greater than

• 3 = Equal to

• 4 = Not equal to

• 5 = Less than

• 6 = Less than or equal to

SupersedeSw Supersede Switch (SupersedeSw) is the switch that identifies which forecast demands imported from an external system can be superseded and which cannot.




SKUHist

SKUHist Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


Dur 3 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DURATION 0


TEXT


TEXT

Qty FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DECIMAL >=0 0

StartDate 1 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DATETIME

Type 2 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

INTEGER

Table description This table stores the SKU-level historic demand data (history). This table is used both as an input and an output table.

As an input table, it stores the SKU-level history to be used in the calculation of the mean squared error (MSE) for this SKU when the SKUSafetyStockParam:CalcMSERule is 3 or 4, which in turn is used as input to the Calculate Statistical Safety Stock process.

As an output table, it stores the SKU-level history resulting from the calculation of the Transfer History process, which maps the DFU-level history to the SKU-level history using the information in DFUToSKU table.

Column descriptions Dur The length of time covered by the history defined in this row.

Item The item associated with the SKU whose history is defined in this row.

Loc The location associated with the SKU whose history is defined in this row.


SKUHist

Qty The quantity of the historic demand data for the SKU during the period defined in this row.

StartDate The beginning of the time interval covered by the history for the SKU defined in this row.

Type The type of history defined in this row. The options are:

• 1=Net Total History

The Transfer History process transfers only the rows that have Type set to 1 since that represents the net total history.

• 2=Non-Base History

Unusual or one-time demand for a SKU (a promoted product, for example). It is not used for updating the forecast.


SKUHistFcst

SKUHistFcst Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Collaborative Shelf Planning and AnalyticsFlowcasting, Enterprise Supply Planning


BaseFcst FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DECIMAL >=0 0

Dur 3 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DURATION 0

FcstDate 1 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DATETIME


TEXT

Lag FF, MP, IPO, Flowcasting, ESP (Deep Tree)

INTEGER >=0 0


TEXT

NonBaseFcst FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DECIMAL >=0 0

StartDate 2 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DATETIME

Table description This table stores the SKU-level historical forecast data. This table is used both as an input and an output table.

As an input table, it stores the SKU-level historical forecast to be used in the calculation of the mean squared error (MSE) for this SKU when the SKUSafetyStockParam:CalcMSERule is 3 or 4, which in turn is used as input to the Calculate Statistical Safety Stock process.

As an output table, it stores the SKU-level historical forecast resulting from the calculation of the Transfer History process, which maps the DFU-level historical forecast to the SKU-level historical forecast using the information in DFUToSKU table.

Column descriptions JDA Enterprise Supply Planning Reference Guide 353 © 2014 JDA Software Group, Inc.- Confidential

SKUHistFcst

BaseFcst Base Forecast (BaseFcst) is the quantity of the base (or statistical) forecast for the demand period defined in this row. This quantity is taken from HistFcst:Qty where HistFcst:Type is equal to1.

Dur The length of time covered by the historical forecast defined in this row. Dur is dependent on the demand calendar used by the SKU.

FcstDate Forecast Date (FcstDate) is the date of the current forecast period when the Transfer History process was run.

Item The item associated with the SKU whose historical forecast is defined in this row.

Lag The number of forecast periods between FcstDate and StartDate.

Loc The location associated with the SKU whose historical forecast is defined in this row.

NonBaseFcst Non-Base Forecast (NonBaseFcst) is the quantity of all non-base forecasts for the demand period defined in this row. This value is calculated by adding all HistFcst:NonBaseFcst values over the demand period.

StartDate The beginning date of the lag period covered by the historical forecast defined in this row. This date is dependent on the demand calendar used by the SKU. The lag numbers specified when the Transfer History process was run determine which forecast lag periods the system saves to the SKUHistFcst table.


SKUPerishableParam

SKUPerishableParam Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning


AgeFactor FF, Flowcasting DECIMAL 1


TEXT


TEXT

MaxShelfLifeDur FF, Flowcasting DURATION

0

MaxWasteFactor FF, Flowcasting DECIMAL 999 MinCovDur FF, Flowcasting DURATIO

N 0

MinEffShelfLifeDur FF, Flowcasting DURATION

0

MinShelfLifeDur FF, MP, Flowcasting, ESP

DURATION

0

MinShelfLifeTolDur FF, Flowcasting DURATION

0

PlanInfeasibleOpt FF, Flowcasting OPTION_NUMBER

1,2,3,4 1

RecShipSSOpt FF, Flowcasting OPTION_NUMBER

1,2 1

ResidualShelfLifeDur

FF, Flowcasting DURATION

0

ShelfLifeDur FF, MP, Flowcasting, ESP

DURATION

0

ShelfLifeGroup FF, Flowcasting TEXT ' ' ShelfLifeRule FF, Flowcasting OPTION_N

UMBER 1,2,3,4 1

VLLTolerance FF, Flowcasting DURATION

0

Table description Each row in this table defines parameters associated with the SKU that are used in planning for date-sensitive inventory (Item:PerishableSw = Y).

Column descriptions AgeFactor Note: This column is not supported in the current release.


SKUPerishableParam

Item The item associated with the SKU defined in this row.

Loc The location associated with the SKU defined in this row.

MaxShelfLifeDur The maximum duration of the remaining shelf life of an item.

If this value is greater than 0, then the latest allowable ExpDate on the planned arrival is the smaller value of:

PlanArriv:SchedArrivDate + SKUPerishableParam:MaxShelfLifeDur

or,

PlanArriv:SchedArrivDate + SKUPerishableParam:ResidualShelfLifeDur (on page 357).

If this value is equal to 0, then the latest allowable ExpDate on the planned arrival is:

PlanArriv:SchedArrivDate + SKUPerishableParam:ResidualShelfLifeDur (on page 357)

MaxWasteFactor Specifies the maximum allowable waste for a SKU replenishment. A MaxWasteFactor between 0 and 999, allows a maximum waste for a single replenishment equal to MaxWasteFactor multiplied by the larger of the minimum replenishment quantity (SKUPlanningParam:MinMPSQty or SKUPlanningParam:MinDRPQty) and the incremental replenishment quantity (SKUPlanningParam:IncMPSQty or SKUPlanningParam:IncDRPQty). A MaxWasteFactor equal to or greater than 999 allows for unlimited waste in a replenishment.

MinCovDur The minimum possible value for the coverage duration, when it must be reduced. The coverage duration will be adjusted for all planned arrivals if DRPCovDur + SSCov + MinShelfLifeDur is longer than the lesser of ResidualShelfLifeDur and MaxShelfLifeDur. Or the coverage duration may be adjusted for an individual planned arrival or planned order in order to keep the planned waste below the maximum allowable waste. In either case, the shortest allowable interval between planned arrivals or planned orders is MinCovDur.

MinEffShelfLifeDur The lower limit placed on the effective shelf life of a product for a planned arrival. The minimum allowable expiration date for a planned arrival is PlanArriv:SchedArrivDate + MinEffShelfLifeDur.

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

MinShelfLifeTolDur Note: This column is no longer supported.

PlanInfeasibleOpt Plan Infeasible option allows you to specify the desired behavior for Calculate Plan logic when a distribution demand is encountered that has an infeasible expiration date. An outgoing planned arrival is infeasible if PlanArriv:Expdate is later then the latest allowable expiration date on a potential replenishment scheduled just in time to meet the demand.

• 1 - Stop planning item

Plan will stop planning the affected SKU as well as the item family.

• 2 - Stop Planning SKU

DRP or MPS Plan stops planning for that SKU which has an infeasible demand and generates an exception, but it continues planning for all the remaining SKUs in the item family.


SKUPerishableParam

• 3 - Meet infeasible requirement

DRP or MPS Plan continues to plan for that SKU which has an infeasible demand and creates a replenishment to meet the demand. The replenishment is created on the scheduled shipping date of the distribution demand, or to the closest date when constrained by calendars and time fences. The expiration date on this replenishment is the latest allowable expiration date for the replenishment. Plan generates an exception to indicate that it was unable to meet the expiration date for the demand, but has created a replenishment for the same.

• 4 - Ignore infeasible requirement

DRP or MPS Plan continues planning for that SKU which has an infeasible demand, but will not create any replenishment for the infeasible demand. It generates an exception to indicate that it was unable to meet the demand expiration date, and the demand is ignored.

RecShipSSOpt Note: Field is not used in this release.

ResidualShelfLifeDur For DRP SKUs, the Residual Shelf Life Duration (ResidualShelfLifeDur) is the ShelfLifeDur of this DRP SKU's ultimate source minus the cumulative lead time from the plant to this DRP. This value is computed by Calculate Plan based on the rule you set in the ShelfLifeRule table. This field is used to constrain the freshness of the planned arrivals for the SKU. The maximum allowable expiration date on a planned arrival is PlanArriv:SchedArrivDate + ResidualShelfLifeDur.

ShelfLifeDur For an MPS SKU, an amount of time between the item’s production or purchase date and its expiration date. When Calculate Plan creates a Planned Order, the PlanOrder:Expdate is set equal to PlanOrder:SchedDate + ShelfLifeDur. The system does not use this column when it is populated for a DRP SKU.

ShelfLifeGroup The name of a group of SKUs that share a common shelf life variance over time. The tables used to manage variable shelf life group information are the ShelfLifeGroup and ShelfLifeGroupData tables.

ShelfLifeRule ShelfLifeRule determines the exact calculation of the residual shelf life duration within the Plan process for instances of multi-sourcing. For any SKUs in the network that are unaffected by multi-sourcing, rules 2, 3 and 4 will all yield the same result.

In the following equations, SourceShelfLifeDur equals ShelfLifeDur for an MPS source and equals SKUPerishableParam:ResidualShelfLifeDur (on page 357) for a DRP source.

ShelfLifeRule values:

• 1: Manual

The value for ResidualShelfLifeDur is set by the user; the system does not calculate it.

• 2: Maximum lead time from the Network table

The system uses the largest of SourceShelfLifeDur – (Network: TransLeadTime + Network: LoadTime + Network:UnloadDur) values calculated for each of its sourcing relations.

• 3: Minimum lead time from the Network table

The system uses the smallest of SourceShelfLifeDur – (Network: TransLeadTime + Network: LoadTime + Network:UnloadDur) values calculated for each of its sourcing relations.

• 4: Weighted average

This rule directs the Calculate Plan process to use the weighted average remaining shelf life between all source locations.


SKUPerishableParam

ResidualShelfLifeDur = the sum of all values for (SourceShelfLifeDur – (Network:TransLeadTime (on page 188) + Network:LoadTime (on page 184)) X Sourcing Factor)

For example:

Source Network:TransLeadTime + Network:LoadTime

Sourcing:Factor ShelfLifeDur at the source

LA 1 day 50 7D

NY 2 days 30 7D ATL 2 days 20 7D

VLLTolerance Indicates that the expiration date on a VehicleLoadLine record does not need to be fully respected by the source supply in order for that supply to be considered eligible to meet the vehicle load line requirement. Note that this allowable deviation from the requirement is relevant only to vehicle load lines for which the VehicleLoad:SourceStatus = 1 or 2. Normally, a source supply (Inventory, SchedRcpts, PlanOrder) can be used for a vehicle load line only if the expiration date of the source supply >= VehicleLoadLine:ExpDate. When the VLLTolerance column is used, supply is eligible as long as:

ExpDate of the source supply >= VehicleLoadLine:ExpDate - SKUPerishableParam:VLLTolerance

The following example illustrates the primary business case for this column:

A scheduled receipt is imported or created with an expiration date equal to SchedRcpts:SchedDate + SKUPerishableParam:ShelfLifeDur. The Calculate Plan/Recommend Shipment process is run to generate recommended shipments based on that scheduled receipt supply (in other words, those recommended shipments have a RecShip:ExpDate that is equal to the SchedRcpts:ExpDate). Then, either Load Manager or the Build Transportation Loads process is run generating outgoing vehicle load lines based on those recommended shipments (in other words, those vehicle load lines have a VehicleLoadLine:ExpDate, which is equal to the RecShip:ExpDate, which is equal to the SchedRcpts:ExpDate). The scheduled receipt is rescheduled to an earlier production date with an expiration date that is equal to a new SchedRcpts:SchedDate + SKUPerishableParam:ShelfLifeDur. Now the expiration date on the scheduled receipt is earlier than the expiration date on the vehicle load line that scheduled receipt is expected to meet.

The VLLTolerance column should be set to the maximum duration such that a scheduled receipt may be rescheduled to an earlier date that falls within that duration.

The value in this column is respected by all system calculations, including Calculate Plan, Recommend Shipments, Plan Analysis, and Generate SKU Exceptions.


SKUPlanningParam

SKUPlanningParam Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


Default value

AggExcessSupplyRule

Flowcasting INTEGER 2

AggSKURule MP INTEGER 0,1 and 2 0

AggUnderSupplyRule Flowcasting INTEGER 1

AllocBatchSw FF, Flowcasting BOOLEAN 0

ATPDur FF, Flowcasting DURATION 0 ATPRule FF, Flowcasting OPTION_NUM

BER 1,2 1

BufferLeadTime MP DURATION 0

CMPFirmDur F , Flowcasting DURATION 0 ConstrInvOpt FF OPTION_NUM

BER 1,2 1

ConstrSupplyAllocRule

FF OPTION_NUMBER

1,2 2

CostUOM FF OPTION_NUMBER

0

CPPLockSw FF, Flowcasting BOOLEAN 0 CPPPriority FF, Flowcasting INTEGER 1 CriticalMaterialSw FF, Flowcasting BOOLEAN 1 CumLeadTimeAdjDur

FF, Flowcasting INTEGER 0

CumLeadTimeDur FF, Flowcasting INTEGER 0 CumLeadTimeRule FF, Flowcasting INTEGER 1 CustServiceLevel FF, Flowcasting DECIMAL 0.9 DepDmdOpt FF, Flowcasting OPTION_NUM

BER 1,2,3 3

DRPCovDur FF, Flowcasting DURATION 7D

DRPFrzDur FF, Flowcasting DURATION 0 DRPRule FF, Flowcasting OPTION_NUM

BER 1,2 1

DRPTimeFenceDate FF, Flowcasting DATETIME 01/01/1970

DRPTimeFenceDur FF, Flowcasting DURATION 0

EOQ FF, Flowcasting DECIMAL 1.0 ExpDate FF, Flowcasting DATETIME 01/01/1970


SKUPlanningParam


Default value

ExternalSKUSw FF, MP , Flowcasting

BOOLEAN 0

FirstReplenDate FF, Flowcasting DATETIME 01/01/1970

FwdBuyMaxDur FF INTEGER 0

HoldingCost FF, Flowcasting DECIMAL 1.0 IncDRPQty FF, Flowcasting DECIMAL 1 IncMPSQty FF, Flowcasting,

ESP (MAP and LPOPT)

DECIMAL 1

InhandlingCost ESP (LPOPT) FLOAT 0


TEXT

LastFrzStart FF, Flowcasting DATETIME 01/01/1970

LastPlanStart FF, Flowcasting DATETIME 01/01/1970


TEXT

LookAheadDur MP DURATION 0

LimitPlanArrivPublishDur

FF, Flowcasting DURATION 0

LimitPlanArrivPublishSw

FF, Flowcasting INTEGER 0,1 0

MaxChangeFactor Not used in this release

DECIMAL 1

MaxCovDur FF, Flowcasting DURATION 728D

MaxOH FF, Flowcasting DECIMAL 999999999.0 MaxOHRule FF, Flowcasting OPTION_NUM

BER 1,2,3 1

MfgFrzDur FF, MP, Flowcasting, ESP

DURATION 0

MfgLeadTime FF, Flowcasting, ESP (Deep Tree)

DURATION 0

MinDRPQty FF, Flowcasting DECIMAL 0 MinMPSQty FF, Flowcasting,

ESP (MAP and LPOPT)

DECIMAL 0

MPSCovDur FF, MP , Flowcasting

DURATION 7D


SKUPlanningParam


Default value

MPSRule FF, MP , Flowcasting

OPTION_NUMBER

1,2,3,4,5 1

MPSTimeFenceDate FF, MP , Flowcasting

DATETIME 01/01/1970

MPSTimeFenceDur FF, MP , Flowcasting

DURATION 0

OrderingCost FF, Flowcasting DECIMAL 1.0 OrderPointMinDur FF INTEGER 0 OrderPointMinQty FF DECIMAL 0 OrderPointMinRule FF INTEGER 1 OrderPointRule FF INTEGER 2 OrderSKUDetailSw FF INTEGER 0 OrderUptoLevelMaxDur

FF INTEGER 0

OrderUptoLevelMaxQty

FF DECIMAL 0

OrderUptoLevelMaxRule

FF INTEGER 1

OuthandlingCost ESP (LPOPT) FLOAT 0

PlanDur FF, Flowcasting DURATION 364D PlanLeadTime FF, Flowcasting,

ESP (Deep Tree)

DURATION 0

PlanLeadTimeRule FF, Flowcasting OPTION_NUMBER

1,2,3,4 2

PlanShipFrzDur FF Flowcasting DURATION 0

ProdCal FF, Flowcasting TEXT ' '

ProdStartDate FF, Flowcasting DATETIME 01/01/1970

ProdStopDate FF, Flowcasting DATETIME 01/01/1970

RecSchedRcptsDur FF, Flowcasting DURATION 0

RestrictDur FF, Flowcasting DURATION 0 RoundingFactor FF, Flowcasting DECIMAL 0 ShrinkageFactor MP INTEGER 0 SupsdMinDmdCovDur

FF, Flowcasting INTEGER 728D


SKUPlanningParam


Default value

WorkingCal FF, Flowcasting TEXT ' '

Table description Each row in this table defines planning parameters associated with the SKU.

Column descriptions AggSKURule The rule you define for the aggregate SKU to calculate supplies (planned orders and recommended shipments) replenished by Calculate Master Plan.

• 0: Not an Aggregate SKU

• 1: Aggregate SKU (Master Planning), with multiple supply orders permitted in a single aggregation period.

This is an aggregate SKU whose demand may be satisfied by multiple supply methods in an aggregation period (used only with Master Planning).

• 2: Aggregate SKU (Master Planning), with multiple supply orders not permitted in a single aggregation period.

This is an aggregate SKU whose demand must be satisfied by only one supply method in each aggregation period (used only with Master Planning).

AllocBatchSw Note: This column is not used in the current release. For information on parameters related to allocating bulk and constrained materials, see SKUMatAllocParam table.

ATPDur Available to Promise Duration (ATPDur) specifies the duration of a period of time, starting from OHPost, during which ATP values are calculated. For example, if you enter a value of 3W in this column, ATP calculations begin at OHPost and extend for 3 weeks.

This column works in conjunction with ATPRule.

• If this column is blank, the system determines the duration using the cumulative lead time for each SKU as of OHPost. For this purpose, the cumulative lead time is the total of the transportation lead times (Network:TransLeadTime) to the SKU’s source and for each of its sources (not including Network:LoadTime), plus the MPS lead time at the manufacturing location (the greater of the manufacturing freeze duration or the manufacturing lead time). If multiple sources are defined in Fulfillment/Distribution, the system uses the longest lead time.

• If SKU:OHPost is blank for a SKU, the system uses Loc:OHPost.

• If the ATPDur exceeds the length of the planning horizon, the system uses the planning horizon as the ATP time fence.

ATPRule Available to Promise Rule (ATPRule) determines the period of time during which the system calculates ATP values and the manner in which those values are calculated.

• 1: The system calculates ATP values beginning at OHPost, over the duration you define when you open a Plan Analysis page. The ATP value reflects all supplies to date and all demands through the ATP duration.


SKUPlanningParam

• 2: The system calculates ATP values beginning at OHPost over the duration you specify in SKUPlanningParam:ATPDur (on page 362). The ATP value reflects the smallest projected inventory value from this point in time through the end of the ATP duration where the projected inventory reflects all time phased firm supplies and all demands through the ATP duration.

BufferLeadTime Buffer Lead Time (BufferLeadTime) is a fixed time period that Master Planning can add to the lead time required for a supply order for this SKU. For example, you may want to use buffer lead time to represent the time needed to move the product from the loading dock into inventory.

To use the BufferLeadTime value, set in this column, in your calculations, check Planning Options > Buffer Lead Time option on the Calculate Master Plan process page. This process adds BufferLeadTime to the lead times for all supply orders for this SKU.

CMPFirmDur Note: This column is not used in the current release. For information on parameters related to allocating bulk and constrained materials, see SKUMatAllocParam table.

ConstrInvOpt The constrained inventory option controls when the SOQ should be impacted by the supply available on the source SKU. By default, the Optimize Order process assumes the supply at the source is unconstrained. This option allows the process to limit the total SOQ for the destination SKUs to the quantity available from the source. This option is only valid for source SKUs. The valid values are:

• 1: Unconstrained (default)

The Optimize Orders process calculates the SOQs without considering the available supply at the source.

• 2: Constrained

The Optimize Orders process restricts the total SOQ for the destinations to the amount of supply available at the source.

ConstrSupplyAllocRule The constrained supply allocation rule is used to determine how the limited supply at a source location is allocated to the destinations. The valid values are:

• 1: Fair Share

Allocates the entire SOQ for each destination equally based on the total SOQ and the location priority of each destinations.

• 2: Prioritize SuppOrder

To allocate the limited supply at the source, supplemental orders are given priority over other demands. When the SOQ contains SuppOrderQty, it is allocated first based on location priority. Within supplemental orders, forced supplemental orders are prioritized over regular supplemental orders.

CostUOM This column defines which Unit Of Measure (UOM) contains the cost for each SKU. This is the cost used when applying deal information to the SKU.

Note: This column is used by Order Optimization only.

CPPLockSw When the CPP Lock Switch (CPPLockSw) switch is set to Yes, you cannot manually move a load for this SKU on the CPP Workbench and the CPP Level Loads process will not move loads for this SKU. You can set this switch manually in a SKU Flexible Editor page or by using the Lock/Unlock action on the CPP Workbench.

CPPPriority


SKUPlanningParam

Use this value to define the priority of SKUs when leveling loads in a master production plan. A value of 1 has the highest priority. The priority of a view family is the average of the priorities of all SKUs in that family.

During automatic load leveling, if using a CPP tie-breaker with a Rule of 1 or 2, the CPP Level Loads process uses CPPPriority to determine which SKU or family to level next.

Initially, all SKUs have the highest priority (1). If multiple SKUs have the same CPPPriority, the sequence in which their loads are leveled does not matter.

The priority of a view family is the average of the priorities of all SKUs in that family, as illustrated in the following example.

SKUs in Family A CPPPriority SKUs in Family B CPPPriority

1 1 4 2

2 4 5 6

3 10 In this example, Family B has the higher priority.

Family A priority =

Family B priority =

If the rule is “move lowest priority first,” Family A is moved before Family B. If the rule is “move highest priority first,” Family B is moved before Family A.

CriticalMaterialSw Note: This column is not used in the current release. For information on parameters related to allocating bulk and constrained materials, see SKUMatAllocParam table.

CumLeadTimeAdjDur Calendars and rounding is not considered while calculating CumLeadTimeDur (on page 364). Hence, the actual CumLeadTimeDur for a SKU is likely to be consistently greater than system calculated CumLeadTimeDur. Hence you can adjust the system calculated CumLeadTimeDur by defining a value in the CumLeadTimeAdjDur column, where by the new CumLeadTimeDur = CumLeadTimeDur + CumLeadTimeAdjDur.

CumLeadTimeDur The CumLeadTimeDur for a DRP SKU with only one source will be set to Source:CumLeadTime + Network:TransLeadTime + LoadTime + UnLoadDur, where LoadDur and UnLoadDur are not calendarized.

The CumLeadTime for multi-sourced SKUs are calculated based on the rule you set in the CumLeadTimeRule column. For more information on the calculation, refer CumLeadTimeRule (on page 364) column.

The value is calculated by Calculate Plan process whenever the Item:CalcCumLeadTimeSw (on page 165) is set to 1.

CumLeadTimeRule Cumulative Lead Time Rule determines the exact calculation of the CumLeadTimeDur within the Calculate Plan process for instances of multi-sourcing. For any SKUs in the network that are unaffected by multi-sourcing, rules 2, 3 and 4 will all yield the same result.

The values for this column are:


SKUPlanningParam

• 1: Manual

When it is set to 1, you define the CumLeadTimeDur manually.

• 2: Maximum Lead-time from Network Table

The CumLeadTime for a DRP SKU would be set to the largest of Source:CumLeadTime + Network:TransLeadTime + LoadTime + UnLoadDur calculated for each of the SKU’s sourcing relations. Note that the LoadDur and UnLoadDur mentioned here are not calendarized.

• 3: Minimum Lead-time from Network Table

The CumLeadTime for a DRP SKU would be set to the smallest of Source:CumLeadTime + Network:TransLeadTime + LoadTime + UnLoadDur calculated for each of the SKU’s sourcing relations. Note that the LoadDur and UnLoadDur mentioned here are not calendarized.

• 4: Average Lead-time from the Network Table

This rule directs Calculate Plan process to calculate the weighted average cumulative lead time duration between all source locations. For example:

Source Network:TransLeadTime + Network:LoadTime Sourcing:Factor

LA 1 day 50

NY 2 days 30 ATL 2 days 20

CustServiceLevel Note: This column is not used in this release.

DepDmdOpt Dependent Demand Option (DepDmdOpt) determines how dependent demand is calculated for this SKU. Dependent demand is calculated for a SKU that is a subordinate (BOM:Subord) in a Bill of Material.

• 1: Do not explode dependent demand

The system does not calculate dependent demand.

• 2: Planned orders and scheduled receipts

The system calculates dependent demand as the total of all planned orders (PlanOrder:Qty) plus all scheduled receipts (SchedRcpt:Qty), where SchedRcpt:ExplodeSw is set to Y. Dependent demand rows will be created in the DepDmdStatic table, even if DepDmdStatic:StartDate is earlier than SKU:OHPost.

If this column is set to option 2 for a subordinate SKU, dependent demand will be created for the subordinate SKU when the parent SKU has SKU:ReplenType set to 2.

• 3: All arrivals

The system calculates dependent demand as the total of all planned and firm planned arrivals (PlanArriv:Qty) for which this SKU is the source. Dependent demand rows will be created in the DepDmdStatic table, even if DepDmdStatic:StartDate is earlier than SKU:OHPost.


SKUPlanningParam

If this column is set to option 3 for a subordinate SKU, dependent demand will be created for the subordinate SKU when the parent SKU has SKU:ReplenType set to 1.

DRPCovDur For Calculate Plan, DRP Coverage Duration (DRPCovDur) is the length of time for which demand is to be covered by planned arrivals, when it uses DRP Planning Rule 1 (SKUPlanningParam:DRPRule (on page 366)=1).

The Optimize Orders process uses DRPCovDur as ideal coverage duration to buy and then determine the adjusted coverage that aligns with the ordering schedule. If DRPCovDur is greater than 6 months, no adjustment is done.

DRPFrzDur DRP Freeze Duration (DRPFrzDur) is the period during which Calculate Plan will not create planned arrivals at this destination. The system uses Loc:FrzStart as the beginning date of DRPFrzDur.

Typically, if you use DRPFrzDur, you set it to end later than SKUPlanningParam:PlanLeadTime (on page 376). This provides an additional period beyond the Planning Lead Time when Calculate Plan will not create new arrivals.

When you run a Calculate Plan process, the system deletes any planned arrivals whose PlanArriv:SchedArrivDate falls within DRPFrzDur.

DRPRule The system uses DRP Planning Rules to calculate planned arrivals for SKUs that are distributed between locations in a distribution network. The Calculate Plan process calculates planned arrivals for the SKU based on the objectives of its DRPRule.

If you want to set replenishment plans manually, set the SKU Planning Duration (SKUPlanningParam:PlanDur (on page 376)) to zero, or you can set DRPTimeFenceDur = PlanDur.

• 1: Coverage

When using Rule 1, Calculate Plan schedules a planned arrival at any time in which stock on hand at the destination is projected to fall below the minimum stock level. (The minimum stock level is calculated according to the Safety Stock Rule—SKUSafetyStockParam:SSRule.)

The system calculates planned arrival quantities in two steps. First, it calculates the net requirement quantity as the demand during the period specified in DRPCovDur. Then, if the net requirement is greater than MinDRPQty, the system rounds the net requirement up to the next higher multiple of IncDRPQty; the result is the planned arrival quantity. Or, if the net requirement is less than MinDRPQty, the system uses MinDRPQty as the planned arrival quantity. However, depending on the value of RoundingFactor (on page 377), the replenishment may be rounded down rather than rounded up. Also, depending on the value of MaxCovDur (on page 369), the replenishment may be rounded down by multiple IncDRPQty amounts.

• 2: Order up to quantity

When using Rule 2, Calculate Plan schedules planned arrivals that bring stock on hand up to a maximum storage amount at any time in which stock on hand is projected to fall below the minimum stock level.

This rule is appropriate when a storage facility, such as a tank, is dedicated to a single SKU. The tank is used more efficiently if it is filled when stock has been used up. This rule is also useful for SKUs with lumpy demand, whose net requirements are difficult to predict.

The amount planned is the difference between the maximum storage amount (SKUPlanningParam:MaxOH (on page 370)) and the stock projected to be on hand when the planned arrival reaches the destination.


SKUPlanningParam

The system calculates planned arrival quantities in two steps. First, it calculates the net requirement as the amount needed to bring stock on hand up to the maximum storage amount. Then, if the net requirements are not a multiple of IncDRPQty, it calculates the planned arrival quantity as the next lower increment of IncDRPQty.

If there is a value in MaxOH, the planned arrival should be equal to or less than the value.

DRPTimeFenceDate With DRP Time Fence End Date (DRPTimeFenceDate), you can establish a time fence to protect your manual changes to the plan from being deleted by Plan. For SKUs that are replenished by Calculate Plan (that is, whose SKU:ReplenType is DRP), the end of the time fence is the greater of DRPTimeFenceDate and (SKUPlanningParam:DRPTimeFenceDur (on page 367) + SKU:OHPost, or Loc:OHPost if SKU:OHPost is blank).

When Plan calculates a new plan for this SKU, it deletes planned arrivals whose PlanArriv:SchedArrivDate precedes the end of the new lead time or freeze period. It retains planned arrivals inside the DRP time fence—that is, whose PlanArriv:SchedArrivDate is later than the new lead time and the new freeze period but earlier than or equal to the old time fence. After the old time fence, Plan retains firm planned arrivals (those whose PlanArriv:FirmPlanSw is Yes) and deletes all others. It calculates new planned arrivals between the end of the old time fence and the end of the planning duration.

You may want to use DRPTimeFenceDate so you can manually plan shipments or arrivals during a short-term problem—for example, when there is a shortage in supply. As the calendar rolls forward, this fixed date will eventually be passed by—that is, fall earlier than the end of DRPTimeFenceDur.

If you need a set duration during which the system will not replan the schedule, you can use DRPTimeFenceDur (on page 367) and SKU:OHPost or Loc:OHPost.

DRPTimeFenceDur With DRP Time Fence Duration ( DRPTimeFenceDur), you can establish a time fence to protect your manual changes to the plan from being deleted by the Calculate Plan process. For SKUs that are replenished by Plan (that is, whose SKU:ReplenType is DRP), the end of the time fence is the greater of DRPTimeFenceDur + SKUPlanningParam:LastPlanStart (or OHPost if LastPlanStart is blank) and SKUPlanningParam:DRPTimeFenceDate.

When Plan calculates a new plan for this SKU, it deletes planned arrivals whose PlanArriv:SchedArrivDate precedes the end of the new lead time or freeze period. It retains planned arrivals inside the DRP time fence—that is, whose PlanArriv:SchedArrivDate is later than the new lead time and the new freeze period but earlier than or equal to the old time fence. After the old time fence, Plan retains firm planned arrivals (those whose PlanArriv:FirmPlanSw is Yes) and deletes all others. It calculates new planned arrivals between the end of the old time fence and the end of the planning duration. After generating a new schedule, Plan moves the time fence forward if there is a value in DRPTimeFenceDur.

If you need a set duration during which the system will not replan the schedule, you can use DRPTimeFenceDur. If you want the end date of the time fence to pass by as the schedule moves forward, use DRPTimeFenceDate instead.

EOQ The Economic Order Quantity (EOQ) output from the Calculate Statistical Safety stock process with the EOQ option selected. EOQ values are determined by your selection from the Type process option. The types of economic order quantity values are:

• Incremental DRP Qty / Incremental MPS Qty - Populates the SKUPlanningParam:IncDRPQty (on page 368) and IncMPSQty (on page 368) columns.

• Minimum DRP Qty / Minimum MPS Qty - Populates the SKUPlanningParam:MinDRPQty (on page 371) and MinMPSQty (on page 371) columns.

• Maximum On Hand - Populates the SKUPlanningParam:MaxOH (on page 370) column.


SKUPlanningParam

• Maximum Coverage Duration - Populates the SKUPlanningParam:MaxCovDur (on page 369) column.

ExpDate The date beyond which no planning is done for this SKU. All demands and supplies outside the ExpDate are ignored for planning purposes.

ExternalSKUSw Switch that indicates that a SKU is in the database; for reference only. If the switch is set to Yes, Calculate Plan will not generate Planned Orders and Planned Arrivals for this SKU. Also, Calculate Plan will not generate any recommended shipments with this SKU as the source. However, depending on the data setup, Calculate Plan may generate Planned Arrivals with this SKU as the source, and may generate recommended shipments with this SKU as the destination.

FirstReplenDate First Replenishment Date (FirstReplenDate) is the first date when a replenishment can be scheduled for a SKU. For DRP SKUs (SKU:ReplenType =1), this date is first open date in arrival calendar after considering greatest of DRPTimeFenceDate OR OHPost + DRPFrzDur OR OHPost+DRPLeadTime. For MPS SKUs (SKU:ReplenType = 2), this date is first open date in production calendar after considering greatest of MPSTimeFenceDate OR OHPost + MPSFrzDur OR OHPost+MPSLeadTime. Planning logic uses this date to determine the period of time during which it reduces total demand (if SKUDemandParam:DmdRedID is not blank). For an SKU with SKU:ReplenMethod (on page 295) as Allocated only or Replenished and Allocated, Calculate Plan ensures that FirstReplenDate is on after EarliestReplenDate. Between OHPost and this date, planning logic reduces total demand by the amount that cannot be met before the first replenishment is scheduled.

FwdBuyMaxDur The Forward Buy Maximum Duration (FwdBuyMaxDur) is the maximum duration allowed for the FwdBuyDur. If the system calculates a FwdBuyDur which is greater than FwdBuyMaxDur, then the FwdBuyDur is adjusted to the maximum.

HoldingCost Specifies the holding cost for this SKU. The holding cost is defined as the dollar cost per unit per year. This value is used by the Calculate Statistical Safety Stock process to compute Economic Order Quantities (EOQ) for this SKU.

IncDRPQty Incremental DRP Planning Quantity (IncDRPQty) is the incremental quantity that Calculate Plan uses for destination SKUs in calculating planned arrival quantities.

The planned arrival quantity calculated by Calculate Plan is always equal to a planning quantity. A planning quantity equals MinDRPQty, or MinDRPQty plus a multiple of IncDRPQty.

When using DRP Planning Rule 1, Calculate Plan rounds the planned arrival quantity up to the next higher planning quantity. When using DRP Planning Rule 2, it rounds the planned arrival quantity down to the next lower planning quantity.

If the value in MinDRPQty is equal to 0, Calculate Plan uses IncDRPQty as both the minimum and the increment.

IncMPSQty Incremental MPS Planning Quantity (IncMPSQty) is the incremental quantity that Calculate Plan adds to MinMPSQty when scheduling planned orders.

The planned order quantity calculated by Plan is always equal to a planning quantity. A planning quantity equals MinMPSQty, or MinMPSQty plus a multiple of IncMPSQty.

When using MPS Planning Rule 1, Calculate Plan rounds the planned order quantity up to the next higher planning quantity. When using MPS Planning Rule 2, it rounds the planned order quantity down to the next lower planning quantity.


SKUPlanningParam

If the value in MinMPSQty is 0, Calculate Plan uses IncMPSQty as both the minimum and the increment.

InhandlingCost Cost to handle a unit of an item when receiving it.


LastFrzStart Last Freeze Start Date (LastFrzStart) is the value of Loc:FrzStart for this SKU's location the last time Calculate Plan was run for this SKU.

LastPlanStart Last Plan Start Date (LastPlanStart) is the Start date used the last time a Calculate Plan process was run for this SKU. This date is the starting point for SKUPlanningParam:MPSTimeFenceDur (on page 373) and SKUPlanningParam:DRPTimeFenceDur (on page 367). If this column is blank, these two durations start at SKU:OHPost. If you run a Calculate Plan process, and then you move OHPost earlier (while working with a prototype or pilot database, for example); be sure to set the date in this column to blank.


LookAheadDur This column is used by the Optimize Production Changeovers process in the optimize mode. The look ahead duration determines the time that the process can look ahead after the ProductionFamily: MinProdDur and pull ResLoadDetail (on page 264) of the SKUs belonging to the same production family.

While the Optimize Production Changeovers process does not specifically compute inventory carrying costs, altering the LookAheadDur helps you to influence the inventory carrying costs. A long look-ahead duration increases the likelihood that orders will be pulled forward, which would increase the inventory carrying costs. However, if the look-ahead duration is too short, the process may have problems filling the ProdFamily: MinProdDur for production families that have sporadic demand. You can tune the LookAheadDur based on Exception (on page 255) 6509 raised (MinProdDur is not satisfied on account of inadequate plan order of the production family until the look-ahead duration) in ResException table and how early the plan orders are being met.

LimitPlanArrivPublishDur If Limit Plan Publishing is selected on the Calculate Plan process options page and the LimitPlanArrivPublishSw is set to Yes for this destination SKU, then this column specifies the duration within which planned arrival records for the destination are published to the database. Any planned arrival with a scheduled arrival date prior to OHPost + LimitPlanArrivPublishDur is published to the PlanArriv table. Any later planned arrival is published as part of a consolidated PlanShip table record associated with the source SKU.

LimitPlanArrivPublishSw This column indicates that if Limit Plan Arrival publishing has been specified on Calculate Plan process options page, then this destination SKU must have planned arrivals published only within the duration specified by LimitPlanArrivPublishDur

MaxChangeFactor Note: Field is not used in this release.

MaxCovDur Maximum Coverage Duration (MaxCovDur) is the maximum length of time this SKU can be retained in inventory. For example, you might use MaxCovDur as a shelf life.

Valid values for MaxCovDur are 0, or greater. JDA Enterprise Supply Planning Reference Guide 369 © 2014 JDA Software Group, Inc.- Confidential

SKUPlanningParam

Calculate Plan attempts to reduce the quantity of each Planned Arrival or Planned Order so that it can be fully consumed by projected demands prior to PlanArriv:SchedArrivDate (on page 202) + MaxCovDur or PlanOrder:SchedDate (on page 209) + MaxCovDur. However, the PlanArriv or PlanOrder quantity will not be reduced to a level that causes the Projected Available inventory to fall below zero.

Note: MaxCovDur is not respected in perishable planning logic.

In CPP Level Loads and CPP Workbench, MaxCovDur can be used as soft constraint which produces an exception, or can be used as hard constraint which prohibits the load from being moved.

In Fulfillment/Material Allocation, CMP uses MaxCovDur when allocating batch materials (SKUPlanningParam:AllocBatchSw (on page 362) = Yes).

In Fulfillment/Order Optimization, the Optimize Orders process uses MaxCovDur to restrict the Suggested Order Quantity (SOQ) such that the calculated SOQ will not be greater than the total demands between the OrderSKU:ArrivDate and the RestrictedSOQCovDate.

MaxCovDur is also used to calculate the SKUStatStatic OverStock columns: OverStockDate, OverStockQty, OverStockExcessCovDur, OverStockDur and OverStockInvStartDate

MaxOH MaxOH is the maximum quantity of this SKU that may be kept in inventory. This can be based on storage limits or financial considerations.

Valid values for MaxOH are 0 or greater, provided that the value is greater than SKUSafetyStockParam:MinSS.

In Fulfillment/Distribution, Calculate Plan respects MaxOH depending on the value of SKUPlanningParam:DRPRule or MPSRule.

For DRPRule = 2 or MPSRule = 2 (Order Up To Quantity), each Planned Arrival or Planned Order is scheduled in the appropriate quantity so that the resultant Projected on-hand value is equal to or slightly less than MaxOH.

For DRPRule = 1 or MPSRule = 1 (Coverage), MaxOH is respected according to the value in SKUPlanningParam:MaxOHRule.

Note: RoundingFactor is not respected in perishable planning logic when DRPRule = 1 or MPSRule = 1 .

In Fulfillment/Order Optimization, the Optimize Orders process uses MaxOH to restrict the Suggested Order Quantity (SOQ) based on the value in SKUPlanningParam:MaxOHRule.

MaxOH is not respected by Fulfillment/Deployment.

MaxOHRule MaxOHRule tells planning logic whether to constrain the plan based on the value in SSPresentation:MaxOH, or SKUPlanningParam:MaxOH if there is no effective value defined in SSPresentation:MaxOH.

The available options are None, Soft or Hard.

These values are respected by Order Optimization for all SKUs and by Calculate Plan/Distribution for SKUs with DRPRule = 1 or MPSRule = 1. This field is not considered for SKUs with DRPRule = 2 or MPSRule = 2.

• 1 - None

When MaxOHRule = 1, any value in the MaxOH column is ignored.

• 2 - Soft


SKUPlanningParam

When MaxOHRule = 2, when the planning logic calculates an order or replenishment that will cause the projected on-hand to exceed the MaxOH, the order or replenishment is created and an exception 109 (projected on-hand violates MaxOH constraint) is generated.

• 3 - Hard

When MaxOHRule = 3, each order or replenishment is reduced as necessary so that the projected on-hand does not exceed MaxOH.

In Fulfillment/Order Optimization, each order is reduced so that the projected on-hand between the OrderSKU:ArrivDate and the OrderSKU:OrderUpToLevelDate never exceeds MaxOH.

In Fulfillment/Distribution, each replenishment is reduced so that the projected on-hand between the replenishment date and needdate of the next replenishment never exceeds MaxOH. However, if respecting MaxOH would cause the ProjAvail to become negative prior to the next available replenishment date, then MaxOH will be violated despite the hard constraint, in order to avoid a stock low situation. When this occurs an exception 109 (projected on-hand violates MaxOH constraint) is generated.

MfgFrzDur Manufacturing Freeze Duration (MfgFrzDur) is the length of time required to manufacture this SKU. During this period, Calculate Plan will not create planned orders and Master Planning will not create any new supply (PlanOrder, PlanArriv or PlanPurch). The system uses Loc:FrzStart as the beginning date for this freeze period.

MfgLeadTime Manufacturing Lead Time (MfgLeadTime) is the lead time used to determine which existing planned orders are deleted at the beginning of the Calculate Plan process. The Manufacturing Lead Time begins at SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank).

If SKU:ReplenType is 2, before Plan calculates new planned orders, it deletes all existing unfirm planned orders whose PlanOrder:SchedDate is earlier than the end of the new MfgLeadTime.

For SKUs whose ReplenType is 2 MfgLeadTime is used in calculating statistical safety stock.

MinDRPQty Minimum DRP Planning Quantity (MinDRPQty) is the minimum quantity for which Calculate Plan will schedule a planned arrival at a destination SKU. Or, if this value is 0, Plan uses the value in SKUPlanningParam:IncDRPQty (on page 368) as both the minimum and the incremental quantity.

The planned arrival quantity calculated by Plan is always equal to a planning quantity. A planning quantity equals MinDRPQty, or MinDRPQty plus a multiple of IncDRPQty.

When using DRP Planning Rule 1, Plan rounds the planned arrival quantity up to a planning quantity. When using DRP Planning Rule 2, it rounds the quantity down.

MinMPSQty Minimum MPS Planning Quantity (MinMPSQty) is the minimum quantity for which Calculate Plan will schedule a planned order. Or, if this value is 0, Plan uses the value in SKUPlanningParam:IncMPSQty (on page 368) as both the minimum and the incremental quantity.

The planned order quantity calculated by Plan is always equal to a planning quantity. A planning quantity equals MinMPSQty, or MinMPSQty plus a multiple of IncMPSQty.

When using MPS Planning Rule 1, Plan rounds the planned order quantity up to a planning quantity. When using MPS Planning Rule 2, it rounds the quantity down.

MPSCovDur MPSCovDur stands for MPS Coverage Duration.


SKUPlanningParam

If MPSRule = 1, this is the length of time for which demand is to be covered by planned orders and planned arrivals.

If MPSRule = 4 or 5, MPSCovDur defines the aggregation duration.

If MPSRule = 1, 4, or 5, MPSCovDur must be greater than 0.

MPSRule Calculate Plan uses MPS Planning Rule (MPSRule) to calculate supplies (planned orders and recommended shipments) for SKUs that are replenished by MPS. It checks MPSRule to determine which MPS Planning Rule to use for a SKU. The system calculates supplies for the SKU based on the objectives of that rule.

Master Planning uses MPS Planning Rules to calculate supplies for all SKUs.

• 1: Coverage (Calculate Plan and Master Planning)

When using Rule 1, Calculate Plan and Master Planning schedule supplies at any time in which stock on hand is projected to fall below the minimum stock level. The supply quantities equal the demand during the period specified in MPSCovDur, rounded up to the next higher planning quantity. (For Master Planning, the planning quantity respects the lot-sizing quantities for the selected production method, purchase method, or sourcing method. For Plan, the planning quantity is equal to the quantity specified in MinMPSQty, or MinMPSQty plus any number of IncMPSQty quantities.)

If you use this rule, MPSCovDur must be greater than 0.

Master planning: For perishable items (Date Sensitive Inventory), though you select MPSRule 1, Calculate Master Plan process will consider MPSRule as 3. MPSRule 1 is not supported for perishable items.

• 2: Order up to quantity (Plan)

When using Rule 2, Calculate Plan schedules supplies that bring stock on hand up to a maximum storage amount at any time in which stock on hand is projected to fall below the minimum stock level.

This rule is appropriate when a storage facility, such as a tank, is dedicated to a single SKU. The tank is used more efficiently if it is filled when stock has been used up. This rule is also useful for SKUs with lumpy demand, whose net requirements are difficult to predict.

The amount planned is the difference between the maximum storage amount (SKUPlanningParam:MaxOH (on page 370)) and the stock projected to be on hand when stock produced for this supply is available.

When calculating supplies using Rule 2, Calculate Plan uses MinMPSQty and IncMPSQty to round the amount down to the next lower planning quantity. (The planning quantity is equal to the quantity specified in MinMPSQty, or MinMPSQty plus any number of IncMPSQty quantities.)

• 3: Lot for Lot (Master Planning)

When using Rule 3, Master Planning schedules supplies that exactly match the needed order quantity.

This rule is appropriate when a SKU should be produced exactly to customer order and it is unnecessary (because there are no economies of scale in production) or undesirable (due to shrinkage, obsolescence, product value, or uncertain demand) to produce extra inventory.

Master Planning always applies the lot-sizing restrictions specified in the selected production method, purchase method, or sourcing method.

• 4: Aggregate SKU with multiple supply orders permitted in a single aggregation period.

This is an aggregate SKU whose demand may be satisfied by multiple supply methods in an aggregation period.


SKUPlanningParam

• 5: Aggregate SKU with multiple supply orders not permitted in a single aggregation period

This is an aggregate SKU whose demand must be satisfied by only one supply method in each aggregation period.

Note: The MPS Planning Rules 4 and 5 are not used by Master Planning.

MPSTimeFenceDate Note: Master Planning does not use this column in this release.

For Fulfillment/Production, you can establish a MPS Time Fence End Date (MPSTimeFenceDate) to protect your manual changes to the plan from being deleted by Calculate Plan. For SKUs that are replenished by MPS (that is, whose SKU:ReplenType is MPS), the end of the time fence is the greater of MPSTimeFenceDate and (SKUPlanningParam:MPSTimeFenceDur (on page 373) + SKUPlanningParam:LastPlanStart (on page 369)). If SKUPlanningParam:LastPlanStart (on page 369) is blank, the system tries Loc:OHPost, SKU:OHPost, or finally the current system date.

When Plan calculates a new plan for this SKU, it deletes planned orders whose PlanOrder:SchedDate precedes the end of the new lead time or freeze period. It retains planned orders inside the MPS time fence—that is, whose PlanOrder:SchedDate is later than the new lead time and the new freeze period but earlier than or equal to the old time fence. It calculates new planned orders between the end of the old time fence and the end of the planning duration.

You may want to use MPSTimeFenceDate so you can manually plan orders during a short-term problem—for example, when there is a shortage in supply. As the calendar rolls forward, this fixed date will eventually be passed by.

If you need a set duration during which the system will not replan the schedule, you can use SKUPlanningParam:MPSTimeFenceDur (on page 373) and SKU:OHPost or Loc:OHPost.

MPSTimeFenceDur Note: Master Planning does not use this column in this release.

For Fulfillment/Production, you can establish a MPS Time Fence Duration (MPSTimeFenceDur) to protect your manual changes to the plan from being deleted by Plan. For SKUs that are replenished by MPS (that is, whose SKU:ReplenType is MPS), the end of the time fence is the greater of:

• MPSTimeFenceDur + SKUPlanningParam:LastPlanStart (on page 369) (if LastPlanStart is blank, the system tries Loc:OHPost, SKU:OHPost, or finally the current system date)

• SKUPlanningParam:MPSTimeFenceDate (on page 373).

When Plan calculates a new plan for this SKU, it deletes planned orders whose PlanOrder:SchedDate precedes the end of the new lead time or freeze period. It retains planned orders inside the MPS time fence—that is, whose PlanOrder:SchedDate is later than the new lead time and the new freeze period but earlier than or equal to the old time fence. It calculates new planned orders between the end of the old time fence and the end of the planning duration. After generating a new schedule, Plan moves the time fence forward if there is a value in MPSTimeFenceDur.

If you need a set duration during which the system will not replan the schedule, you can use MPSTimeFenceDur and LastPlanStart. If you want the end date of the time fence to pass by as the schedule moves forward, use MPSTimeFenceDate instead.

OrderingCost Specifies the fixed cost per order that is incurred every time a replenishment order for this SKU is planned. Ordering costs include costs related to the clerical work of preparing, releasing, monitoring, and receiving orders, the physical handling of goods, inspections and setup costs, as applicable. This value is used by the Calculate Statistical Safety Stock process to compute Economic Order Quantities (EOQ) for this SKU.

OrderPointMinDur


SKUPlanningParam

You can use Order Point Minimum Duration to set the minimum (or user-specified) order point date. When system calculated order point date falls beyond the minimum order point date, the order point date is set to the minimum order point date. The system calculated orderpointdate is retained if it is greater than or equal to minimum order point date.

The minimum orderpointdate is calculated by extending the OrderPlaceDate by OrderPointMinDur.

Note: The minimum orderpointdate is calculated only if OrderPointDur is greater than zero.

If the OrderPointMinQty is also defined resulting in a user-specified order point date, the greater of the two becomes the user-specified order point date.

Note: OrderPointMinDur is only used if OrderPointMinRule is set to either “Both” or “User”.

OrderPointMinQty Order Optimization process uses OrderPointMinQty to set the minimum (or user-specified) order point date.

If the quantity is greater than zero, the Optimize Orders process calculates the user-specified order point date by determining the coverage duration of total demand from the Order’s OrderPlaceDate that reflects the specified quantity.

Note: If the OrderPointMinDur is also defined resulting in a user-specified order point date, the greater of the two becomes the user-specified order point date.

Note OrderPointMinQty is only used if OrderPointMinRule is set to either “Both” or “User”.

OrderPointMinRule Use the Order Point Minimum Rule to determine whether to follow system generated order point date or override the order point date or set a minimum on the date. It is used in calculating the OrderSKU: OrderPointDate.

You can set the following options for OrderPointMinRule:

• 1 - Both

The process will use the greater of the system calculated date versus the user-specified date.

• 2 - System

The Optimize Orders process will use the system calculated order point date.

• 3 - User

The process will override the system calculated date with the user-specified date.

You should specify values in OrderPointMinDur and/or OrderPointMinQty that get converted to a user-specified order point date.

Note: This is used by the Optimize Orders process. For more information, refer to the Order Optimization section of the JDA Fulfillment OnLine Expert.

OrderPointRule You use the Order Point Rule to determine whether the SKU is part of joint ordering or single product ordering. It is used in determining the OrderSKU: OrderPointDate, which is the time that the next order arrives.

You can set following options for OrderPointRule:

• 1 - Product

The order for this SKU is placed separately without considering other SKUs in the network. That is, the SKU’s order timing is irrespective of other SKUs in the network. So the “Product” method results in OrderSKU’s ordering quantities that align with the order schedule but not aligned in a synchronized fashion.


SKUPlanningParam

If OrderPointrule=1 (product), OrderSKU:OrderPointDate=OrderSKU: MinCovDate

• 2 - Joint

The order for this SKU is placed along with set of SKUs, which fall, in the same network. In joint ordering, the SKUs order timing depends upon other SKUs in the network.

The “Joint” method is used to synchronize all the SKUs on the order to the order schedule described by Order Review calendar.

If OrderPointrule=2 (joint), OrderSKU: OrderPointDate = Max(OrderSKU: MinCovDate, OrderSKU: OrderCovDate)

Note: This is used by the Optimize Orders process. For more information, refer to the Order "Optimization section" of the JDA Fulfillment OnLine Expert.

OrderSKUDetailSw You use the Order SKU Detail Switch to decide whether you want to populate the OrderSKUDetail table with Optimize Orders process output.

• 0 - Indicates that OrderSKUDetail table will not be populated.

• 1 - Indicates that the OrderSKUDetail table will be populated.

OrderUptoLevelMaxDur The Order Upto Level Maximum duration in Order Optimization process can determine the maximum order upto level date.

If duration is greater than zero, the Optimize Orders process calculates the user-specified order upto level date by adding this duration to the Order’s OrderPlaceDate.

If the OrderUpToLevelMaxQty is also defined resulting in a user-specified order upto level date, the lesser of the two becomes the user-specified order upto level date.

Note: OrderUptoLevelMaxDur is only used if OrderUptoLevelMaxRule is set to either “Both” or “User”.

OrderUptoLevelMaxQty Order Optimization process uses OrderUptoLevelMaxQty to determine the maximum order upto level date.

If the quantity is greater than zero, the Optimize Orders process calculates the user-specified order upto level date by determining the coverage duration of total demand from the Order’s OrderPlaceDate that reflects the specified quantity.

If the OrderUpToLevelMaxDur is also defined resulting in a user-specified order upto level date, the lesser of the two becomes the user-specified order upto level date.

Note: OrderUptoLevelMaxQty is only used if OrderUptoLevelMaxRule is set to either “Both” or “User”.

OrderUptoLevelMaxRule Use the Order Upto Level Maximum Rule to determine whether to follow the system generated order upto level date or override the order upto level date or set a maximum on the date, when using Optimize Orders process. It is used in calculating the OrderSKU: OrderUptoLevelDate.

You can set following options for OrderUptoLevelMaxRule:

• 1 - Both

The process will use the lesser (more restrictive) of the system calculated date versus the user-specified date.

• 2 - System

The Optimize Orders process will use the system calculated order upto level date.

• 3 - User


SKUPlanningParam

The process will override the system calculated date with the user-specified date.

You should specify values in OrderUpToLevelMaxDur and/or OrderUpToLevelMaxQty that get converted to a user-specified order upto level date.

Note: This is used by the Optimize Orders process. For more information, see the "Order Optimization" section of the JDA Fulfillment OnLine Expert.

OuthandlingCost Cost to handle a unit of an item when shipping it.

PlanDur The length of time, beginning at SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank), for which the Calculate Plan process calculates a plan for this SKU.

PlanLeadTime Unless PlanLeadTimeRule is set to 1 (manual), this value is calculated by the Plan Process based on the expected total LeadTime (LoadDur + LeadTime + UnloadDur including the affects of calendars) for a planned arrival scheduled as early as possible after OHPost. The PlanLeadTime is the SchedArrivDate minus SchedShipDate for a Planned Arrival that is scheduled at the beginning of the planning horizon.

PlanLeadTime is also used to calculate statistical safety stock (see StatSS (Statistical Safety Stock).

Before Plan calculates new planned arrivals, it deletes all existing planned arrivals whose PlanArriv:SchedArrivDate is earlier than the end of the new PlanLeadTime.

PlanLeadTimeRule Planning Lead Time Rule (PlanLeadTimeRule) determines how the system calculates Planning Lead Time (SKUPlanningParam:PlanLeadTime).

• 1: Manual

You set a value for PlanLeadTime; the system does not calculate it.

• 2: Maximum leadtime

The largest value for (LoadDur + LeadTime + UnloadDur including the affects of calendars) for all sourcing rows in effect at FirstReplenDate.

• 3 - Minimum leadtime

The smallest value for (LoadDur + LeadTime + UnloadDur including the affects of calendars) for all sourcing rows in effect at FirstReplenDate.

• 4 - Weighted average leadtime

The weighted average of all values for (LoadDur + LeadTime + UnloadDur including the affects of calendars) for all sourcing rows in effect at FirstReplenDate. The values are weighted according the values in Sourcing:Factor.

PlanShipFrzDur Plan Ship Freeze Duration (PlanShipFrzDur) specifies a duration after OHPost during which, from the source perspective, no planned shipments can be scheduled.

When generating planned shipments, the Calculate Plan process respects the DRPTimeFenceDate and DRPFrzDur at the destination, and does not schedule any new planned arrivals prior to either of those time periods. The PlanShipFrzDur is the corresponding freeze period from the source perspective. If the value in this column is zero days, then the generated planned shipments do respect the source allocation calendar, but can be scheduled to be shipped from the source as early as OHPost.

ProdCal Production Calendar (ProdCal) determines when this location can produce this item. (The system can set PlanOrder:SchedDate only to a date when the location is open for production.) The location is open for production of the item during any period when CalData:Opt for this calendar is 2. JDA Enterprise Supply Planning Reference Guide 376 © 2014 JDA Software Group, Inc.- Confidential

SKUPlanningParam

Valid values for ProdCal are identifiers of an existing Production Calendar (Cal:Cal whose Cal:Type is 9), or blank.

If CPP Level Loads tries to create a new planned order, or if you try to create a new planned order with CPP Workbench, the system checks to see whether the destination SKU’s production calendar is open at any time during the destination period. If so, the planned order is created with a PlanOrder:SchedDate of either the earliest or latest time when ProdCal is open during the period. (CPP Workbench Properties and CPP Level Loads process options determine whether the earliest or latest date is used.) If the production calendar is closed during the entire period, a planned order cannot be created.

ProdStartDate The production start date defined for an MPS SKU. No planned orders are generated by Calculate Plan before this date. If any demands exist before ProdStartDate, Calculate Plan creates a planned order on ProdStartDate to meet those demands.

ProdStopDate The production stop date defined for an MPS SKU. No planned orders are generated by Calculate Plan after this date. If any demands exist after ProdStopDate, Calculate Plan will pre-build to meet those demands.

RecSchedRcptsDur Recommended Scheduled Receipts Duration (RecSchedRcptsDur) is the length of time, starting at SKU:OHPost (or at Loc:OHPost or SKU:OHPost is blank) during which a SchedRcpts process will mark planned orders to become scheduled receipts.

RestrictDur Restricted Plan Duration (RestrictPlanDur) specifies the duration of a period of time, beginning at OHPost, during which Calculate Plan observes firm replenishments that may restrict planned replenishments. This period of time is referred to as the restricted plan duration. For example, a value of 2W in this column defines a restricted plan duration beginning at OHPost and extending for 2 weeks.

Note: For optimal results, you should specify a restricted plan duration that is shorter than the planning duration. For example, if the planning duration is 52 weeks and the safety stock coverage duration is two weeks, the restricted plan duration could be set to 50 weeks.

For detailed examples of how Calculate Plan generates planned replenishments with enhanced planning logic, refer to OnLine Expert.

RoundingFactor Calculate Plan uses this factor to determine whether a Planned Arrival or Planned Order will be rounded up or rounded down. If RoundingFactor is left at the default value of zero, then all replenishments are rounded up.

If the unrounded replenishment quantity is greater than the MinQty, and RoundingFactor > 0, then the following logic is used:

Replenishment is rounded up only if (unrounded quantity - rounded down quantity)/IncQty >= RoundingFactor, where IncQty = IncDRPQty or IncMPSQty. However, the replenishment will also be rounded up if the rounding down will cause the ProjAvail to fall below zero within one minute of the NeedArrivDate of the replenishment.

Note: RoundingFactor is not respected in perishable planning logic.

ShrinkageFactor Use this factor to account for losses that occur during storage or through other circumstances such as spoilage, evaporation, or theft. Set ShrinkageFactor to the percentage of shrinkage you expect. For example, if you expect shrinkage of two percent, set ShrinkageFactor to 2.

Valid values for ShrinkageFactor are 0 - 100 and can be greater than 100.


SKUPlanningParam

The value in this column should be specified to inflate the independent demands.

Master Planning increases independent demand orders for this SKU (customer orders, forecast orders, and safety stock) by the percentage specified.

SupsdMinDmdCovDur SupsdMinDmdCovDur is the minimum duration of demand to be covered before giving up supply as excess to another SKU that has a supersession relationship with this SKU. This is used by both Calculate Plan and Optimize Orders process that support the modeling of Supersession relationships.

Note: This column is used only when the Supersession items are in a circular relationship.

For more information, refer to the Plan/Deployment Supersession section and Order Opt Supersesssion Sections of the JDA Fulfillment OnLine Expert.

WorkingCal Calendar used by Fulfillment/Distribution and Fulfillment/Deployment, to define the periods when the location is open for loading and unloading an order for the item. Valid values for WorkingCal are identifiers of an existing Working Calendar (Cal:Cal whose Cal:Type is 11).

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.


SKUProjStatic

SKUProjStatic Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Supply, Flowcasting, Enterprise Supply Planning



Default value

ActualIntransIn FF, MP, Flowcasting

DECIMAL 0

ActualIntransOut FF, MP, Flowcasting

DECIMAL 0

AdjAllocAggMktActvtyFcst

FF, Flowcasting

DECIMAL 0

AdjAllocAutoFcst FF, Flowcasting

DECIMAL 0

AdjAllocBaseFcst FF, Flowcasting

DECIMAL 0

AdjAllocDataDrvnFcst FF, Flowcasting

DECIMAL 0

AdjAllocMktActvtyFcst FF, Flowcasting

DECIMAL 0

AdjAllocNonBaseFcst FF, Flowcasting

DECIMAL 0

AdjAllocOvrideFcst FF, Flowcasting

DECIMAL 0

AdjAllocReconcileFcst FF, Flowcasting

DECIMAL 0

AdjAllocTargtImpactFcst

FF, Flowcasting

DECIMAL 0

AdjAllocTotalLockFcst FF, Flowcasting

DECIMAL 0

AdjAllocTotFcst FF, MP, Flowcasting, ESP

DECIMAL 0

AdjFcstCustOrders FF, MP, Flowcasting, ESP

DECIMAL 0

AggMktActvtyCustOrders

FF, Flowcasting

DECIMAL 0

AggMktActvtyFcst FF, Flowcasting

DECIMAL 0

AggNegConstrProjOH FF, Flowcasting

DECIMAL 0

AggNegProjOH FF, Flowcasting

DECIMAL 0

AggPosConstrProjOH FF, Flowcasting

DECIMAL 0

AggPosProjOH FF, Flowcasting

DECIMAL 0

AllDmd FF, MP, Flowcasting

DECIMAL 0


SKUProjStatic



Default value

AllIntransIn FF, MP, Flowcasting

DECIMAL 0

AllocAggMktActvtyFcst FF, Flowcasting

DECIMAL 0

AllocAutoFcst FF, Flowcasting

DECIMAL 0

AllocBaseFcst FF, MP, Flowcasting

DECIMAL 0

AllocDataDrvnFcst FF, Flowcasting

DECIMAL 0

AllocMktActvtyFcst FF, Flowcasting

DECIMAL 0

AllocNonBaseFcst FF, MP, Flowcasting

DECIMAL 0

AllocOvrideFcst FF, Flowcasting

DECIMAL 0

AllocReconcileFcst FF, Flowcasting

DECIMAL 0

AllocTargtImpactFcst FF, Flowcasting

DECIMAL 0

AllocTotalLockFcst FF, Flowcasting

DECIMAL 0

AllocTotFcst FF, MP, Flowcasting, ESP

DECIMAL 0

AllocTotFcstNoProration FF, Flowcasting

DECIMAL 0

AltConstCantMeetQty Not used in this release

AltConstrCovDur FF, Flowcasting

DURATION 0

AltConstrainedUnuseOH

FF, MP, Flowcasting

DECIMAL 0

AltConstrPOH FF, Flowcasting

DECIMAL 0

AltConstrUseableProjOH

FF FLOAT

AltConstrUnuseableSupply

FF, Flowcasting

FLOAT 0

AltSubConstProjOH FF, Flowcasting

DECIMAL 0.0

AltSuspdConstrProjAvail

FF, Flowcasting

FLOAT

AltSupsdConstrProjOH FF DECIMAL 0 ATP FF,


AutoCustOrders FF, Flowcasting

DECIMAL 0


SKUProjStatic



Default value

AutoFcst FF, Flowcasting

DECIMAL 0

AvailShipOH FF, Flowcasting

DECIMAL 0

AvgCycleStock Flowcasting DECIMAL 0 AvgIntransitStock Flowcasting DECIMAL 0 BaseCustOrders FF,


BaseFcst FF, MP, Flowcasting

DECIMAL 0

BaseHist FF, Dmd, MP, Supp, Flowcasting

DECIMAL 0

CBMPAdjFcstOrd Not used in this release

DECIMAL 0

CBMPBuyOrd Not used in this release

DECIMAL 0

CBMPConstProjAvailSupsdConstrProjAvail


DECIMAL 0

CBMPDepDmd Not used in this release

DECIMAL 0

AltConstrOH Not used in this release

DECIMAL 0

CBMPMakeOrd Not used in this release

DECIMAL 0

CBMPMetAdjFcstCO Not used in this release

DECIMAL 0

CBMPMetAdjFcstOrd Not used in this release

DECIMAL 0

CBMPMetIndDmd Not used in this release

DECIMAL 0

CBMPMetNonFCO Not used in this release

DECIMAL 0

CBMPMoveOrd Not used in this release

DECIMAL 0

CBMPOHInventory Not used in this release

DECIMAL 0

CBMPProjAvail Not used in this release

DECIMAL 0

CBMPProjOH Not used in this release

DECIMAL 0

CBMPSafetyStockOrd Not used in this release

DECIMAL 0

CBMPSSInventory Not used in this release

DECIMAL 0

CBMPSSLevel Not used in this release

DECIMAL 0


SKUProjStatic



Default value

CBMPTotDmd Not used in this release

DECIMAL 0

CBMPTotSupply Not used in this release

DECIMAL 0

CMPFirmDepDmd Flowcasting DECIMAL 0 CMPFirmPlanArriv Flowcasting DECIMAL 0 CMPFirmPlanOrd Flowcasting DECIMAL 0 CMPFirmPlanShip Flowcasting DECIMAL 0 COMetEarlyCount FF, MP DECIMAL 0 COMetLateCount FF, MP DECIMAL 0 COMetOntimeCount FF, MP DECIMAL 0 COMetPartialCount FF, MP DECIMAL 0 CommitIntransIn FF, MP,


CommitIntransOut FF, MP, Flowcasting

DECIMAL 0

ConCancel Supp DECIMAL 0 ConCustOrder Supp DECIMAL 0 CONeedUnit FF, MP,


ConExtraUsage Supp DECIMAL 0 ConIntersiteOrder Supp DECIMAL 0 ConInventory Supp DECIMAL 0 ConMasterSched Supp DECIMAL 0 ConNew Supp DECIMAL 0 ConNoAction Supp DECIMAL 0 ConPull Supp DECIMAL 0 ConPurchaseOrder Supp DECIMAL 0 ConPurchaseReq Supp DECIMAL 0 ConPush Supp DECIMAL 0 ConReschedSupply Supp DECIMAL 0 ConSafetyStock Supp DECIMAL 0 ConSchedSupply Supp DECIMAL 0 ConShCustOrder Supp DECIMAL 0 ConShExtraUsage Supp DECIMAL 0 ConShMasterSched Supp DECIMAL 0 ConShortage Supp DECIMAL 0 ConShSafetyStock Supp DECIMAL 0 ConsolidatedPlanShip FF,

Flowcasting DECIMAL

ConstrCantMeetQty Not used in this release

FLOAT


SKUProjStatic



Default value

ConstrCovDur FF, Flowcasting

DURATION 0

ConstrExpOH FF, Flowcasting

DECIMAL 0

ConstrNetReqts FF, Flowcasting

DECIMAL 0

ConstrProjAvail FF, Flowcasting

DECIMAL 0

ConstrProjOH FF, MP, Flowcasting

DECIMAL 0

ConstrProxyDemand FF, Flowcasting

DECIMAL 0

ConstrProxySupply FF, Flowcasting

DECIMAL 0

ConstrSchedExpOH FF, Flowcasting

DECIMAL 0

ConstrSchedUnuseOH FF, Flowcasting

DECIMAL 0

ConstrUseableProjOH FF, Flowcasting

FLOAT

ConstrUnuseableSupply FF, Flowcasting

FLOAT

ConstrUnuseOH FF, Flowcasting

DECIMAL 0

ConSubstSupply Supp DECIMAL 0 ConTotalDemand Supp DECIMAL 0 ConWorkOrder Supp DECIMAL 0 CoProductPlanOrders MP,


CoProductProdReqt MP DECIMAL 0 COProjMargin FF, MP,


COProjRevenue FF, MP, Flowcasting

DECIMAL 0

CORealMargin FF, MP, Flowcasting

DECIMAL 0

CORealRevenue FF, MP, Flowcasting

DECIMAL 0

COSchedUnit FF, MP, Flowcasting

DECIMAL 0

COUnmetCount MP DECIMAL 0 COUnplannedCount FF, MP,


CovDur FF, MP, Flowcasting

DURATION 0

CovDurCantMeetQty Not used in this release

FLOAT


SKUProjStatic



Default value

DataDrvnCustOrders FF, Flowcasting

DECIMAL 0

DataDrvnFcst FF, Flowcasting

DECIMAL 0

DemandResExcepCount FF, MP, Flowcasting

DECIMAL 0

DemandSKUExcepCount

FF, MP, Flowcasting

DECIMAL 0

DepDmd FF, MP, Flowcasting

DECIMAL 0

DepDmdEarliestNeed MP, Flowcasting

DATETIME 01/01/1970

DepDmdRequirement MP DECIMAL 0 DetailedPlanShip FF,

Flowcasting DECIMAL

DisplayQty FF, Flowcasting

DECIMAL 0

DistRequirement MP DECIMAL 0 DistShipRequirement MP DECIMAL 0 DFUToSKUFcst FF, MP,


Dur FF, MP, Supp, Flowcasting

DURATION 0

ExpiredRequiredOH MP DECIMAL 0 ExpOH FF, MP,


FcstCustOrders FF, MP, Flowcasting, ESP

DECIMAL 0

FirmPlanArriv FF, MP, Flowcasting

DECIMAL 0

FirmPlanOrder FF, MP, Flowcasting

DECIMAL 0

FirmPlanShip FF, MP, Flowcasting

DECIMAL 0

FirmProxyInventory FF, Flowcasting

DECIMAL 0

FirmSchedRcpts MP DECIMAL 0 FirmSubInventory FF,


FirmSupplyCovDur FF, Flowcasting

DURATION 0

FirmSupplyProjOH FF, Flowcasting

DECIMAL 0

FOMetEarlyCount FF, MP, Flowcasting

DECIMAL 0


SKUProjStatic



Default value

FOMetLateCount FF, MP, Flowcasting

DECIMAL 0

FOMetOntimeCount FF, MP, Flowcasting

DECIMAL 0

FOMetPartialCount FF, MP, Flowcasting

DECIMAL 0

FONeedUnit FF, MP, Flowcasting

DECIMAL 0

FOProjMargin FF, MP, Flowcasting

DECIMAL 0

FOProjRevenue FF, MP, Flowcasting

DECIMAL 0

ForcedSuppOrderQty FF, Flowcasting

DECIMAL 0

FORealMargin FF, MP, Flowcasting

DECIMAL 0

FORealRevenue FF, MP, Flowcasting

DECIMAL 0

FOSchedUnit FF, MP, Flowcasting

DECIMAL 0

FOUnmetCount FF, MP, Flowcasting

DECIMAL 0

FOUnplannedCount FF, MP, Flowcasting

DECIMAL 0

HoldOutQty FF, Flowcasting

DECIMAL 0

IgnoredDmd FF, MP, Flowcasting

DECIMAL 0

IncMaxCovDur FF, MP, Flowcasting

DURATION 0

IncMinCovDur FF, MP, Flowcasting

DURATION 0

IndDmd MP INTEGER 0 IncDmdExceptionCount FF, MP,


IncDmdExceptionQty FF, MP, Flowcasting

INTEGER 0

InvCarCost Flowcasting DECIMAL 0 Inventory FF, MP,


IPOAvgStock IPO, MP, Flowcasting

FLOAT

IPOExpBackOrder IPO, MP, Flowcasting

FLOAT

IPOFcstBias IPO, Flowcasting

FLOAT 0


SKUProjStatic



Default value

IPODmd IPO, MP, Flowcasting

FLOAT

IPOProjOH IPO, MP, Flowcasting

FLOAT

IPOReorderPoint IPO, MP, Flowcasting

FLOAT

IPOReorderQty IPO, MP, Flowcasting

FLOAT

IPOSafetyStock IPO, MP, Flowcasting

FLOAT

IPOSKUHist IPO, Flowcasting

FLOAT 0

IPOSKUHistFcst IPO, Flowcasting

FLOAT 0

Item 1 FF, MP, Supp, Flowcasting

TEXT

Loc 2 FF, MP, Supp, Flowcasting

TEXT

MetIndDmd MP INTEGER 0 MetSSLevel MP INTEGER 0 MktActvtyCustOrders FF,


MktActvtyFcst FF, Flowcasting

DECIMAL 0

MPConstProjAvail MP INTEGER 0 NetProfit Flowcasting DECIMAL 0 NetReqts Flowcasting DECIMAL 0 NonBaseFcst FF, MP,


NonBaseHist MP DECIMAL 0 NonFcstCustOrders FF, MP,

Flowcasting, ESP

DECIMAL 0

NonSupsdAdjAllocTotalFcst

FF, MP DECIMAL 0

NonPriorityForcedSuppOrderQty

Flowcasting

NonSupsdAdjFcstCustOrders

FF, Flowcasting

DECIMAL 0

NonSupsdAllocBaseFcst FF, Flowcasting

DECIMAL 0

NonSupsdAllocNonBaseFcst

FF, Flowcasting

DECIMAL 0

NonSupsdAllocTotFcst FF, MP, Flowcasting

DECIMAL 0

NonSupsdBaseFcst FF, Flowcasting

DECIMAL 0


SKUProjStatic



Default value

NonSupsdDepDmd FF, MP, Flowcasting

DECIMAL 0

NonSupsdDFUToSKUFcst

FF, MP, Flowcasting

DECIMAL 0

NonSupsdFcstCustOrders

FF, MP, Flowcasting

DECIMAL 0

NonSupsdFirmPlanArriv FF, Flowcasting

DECIMAL 0

NonSupsdFirmPlanOrder

FF, Flowcasting

DECIMAL 0

NonSupsdFirmPlanShip FF, Flowcasting

DECIMAL 0

NonSupsdNonBaseFcst FF, Flowcasting

DECIMAL 0

NonSupsdNonFcstCustOrders

FF, MP, Flowcasting

DECIMAL 0

NonSupsdPlanArriv FF, Flowcasting

DECIMAL 0

NonSupsdPlanOrders FF, Flowcasting

DECIMAL 0

NonSupsdPlanShip FF, Flowcasting

DECIMAL 0

NonSupsdRecArriv FF, Flowcasting

DECIMAL 0

NonSupsdRecShip FF, Flowcasting

DECIMAL 0

NonSupsdTotDmd FF, MP, Flowcasting

DECIMAL 0

OptionSet 4 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT ' '

OvrideCustOrders FF, Flowcasting

DECIMAL 0

OvrideFcst FF, Flowcasting

DECIMAL 0

PlanArriv FF, MP, Flowcasting

DECIMAL 0

PlanIntransIn FF, Flowcasting

DECIMAL 0

PlanOrders FF, MP, Flowcasting

DECIMAL 0

PlanProjAvail FF, Flowcasting

DECIMAL 0

PlanProjOH FF, Flowcasting

DECIMAL 0

PlanPurch MP INTEGER 0 PlanPurchFirm MP INTEGER 0 JDA Enterprise Supply Planning Reference Guide 387 © 2014 JDA Software Group, Inc.- Confidential

SKUProjStatic



Default value

PlanShip FF, MP, Flowcasting

DECIMAL 0

PresentationQty FF, Flowcasting

DECIMAL 0

ProcessDate FF, Flowcasting

DATETIME 01/01/1970

ProdRequirement MP DECIMAL 0 ProjAvail FF, MP,


ProjAvailEarliestNeed MP, Flowcasting

DATETIME 01/01/1970

ProjOH FF, MP, Flowcasting

DECIMAL 0

ProjOHEarliestNeed MP, Flowcasting

DATETIME 01/01/1970

ProjOrderOptTotDmd FF DECIMAL 0 ProjOrderOptIntransOut

FF DECIMAL 0

ProjOrderOptSOQ FF DECIMAL 0 ProjOrderOptIntransIn FF DECIMAL 0 ProjOrderOptTotSupply FF DECIMAL 0 ProjOrderOptProjOH FF DECIMAL 0 ProjOrderOptProjAvail FF DECIMAL 0 ProAllocBaseFcst FF DECIMAL ProxyDemand FF, MP,


ProxyIntransIn FF, Flowcasting

DECIMAL 0

ProxyIntransOut FF, Flowcasting

DECIMAL 0

ProxyInventory FF, Flowcasting

DECIMAL 0

ProxyRecArriv FF, Flowcasting

DECIMAL 0

ProxyRecShip FF, Flowcasting

DECIMAL 0

ProxySupply FF, MP, Flowcasting

DECIMAL 0

PSOLoad Supp DECIMAL 0.0 PurchOrder MP INTEGER 0 PurchRequirement MP DECIMAL 0 RecAllocArriv FF FLOAT 0 RecAllocShip FF FLOAT 0 RecArriv FF,



SKUProjStatic



Default value

ReconcileCustOrders FF, Flowcasting

DECIMAL 0

ReconcileFcst FF, Flowcasting

DECIMAL 0

RecShip FF, Flowcasting

DECIMAL 0

RequiredProjAvail MP DECIMAL 0 RequiredProjOH MP DECIMAL 0 SchedExpiredRequiredOH

MP DECIMAL 0

SchedExpOH FF, MP, Flowcasting

DECIMAL 0

SchedRcpts FF, MP, Flowcasting

DECIMAL 0

SchedSupplyExceptionCount

FF, MP, Flowcasting

INTEGER 0


FF, MP, Flowcasting

INTEGER 0

SchedUnusedRequiredOH

MP DECIMAL 0

SchedUnuseOH FF, MP, Flowcasting

DECIMAL 0

SeasonFactor FF, Flowcasting

DECIMAL 0

SKUExceptionCount FF, MP INTEGER 0 SKUExceptionQty FF, MP,


SKUExternalFcst FF, MP, Flowcasting

DECIMAL 0

SKUResExceptionCount FF, MP, Flowcasting

INTEGER 0

SKUResExceptionQty FF, MP, Flowcasting

INTEGER 0

Sources Flowcasting TEXT ' ' SS FF, MP,


SSInventory MP INTEGER 0 SSMetEarlyCount MP,


SSMetLateCount MP, Flowcasting

DECIMAL 0

SSMetOnTimeCount MP, Flowcasting

DECIMAL 0

SSMetPartialCount MP, Flowcasting

DECIMAL 0

SSNeedUnit MP, Flowcasting

DECIMAL 0


SKUProjStatic



Default value

SSSchedUnit MP, Flowcasting

DECIMAL 0

SSUnmetCount MP, Flowcasting

DECIMAL 0

SSUnplannedCount MP, Flowcasting

DECIMAL 0

StandardCost Flowcasting DECIMAL 0 StartDate 3 FF, MP, Supp,

Flowcasting DATETIME

StatSS FF, MP, Flowcasting

DECIMAL 0

StockLowCost Flowcasting DECIMAL 0 StockOutCost Not used in

this release DECIMAL 0

SubConstrProjAvail FF, Flowcasting

DECIMAL 0

SubConstrProjOH FF, Flowcasting

DECIMAL 0

SubIntransIn FF, Flowcasting

DECIMAL 0

SubInventory FF, Flowcasting

DECIMAL 0

SubRecArriv FF, Flowcasting

DECIMAL 0

SubRecShip FF, Flowcasting

DECIMAL 0

SuppOrderPlanShip FF, Flowcasting

DECIMAL 0

SuppOrderQty FF, Flowcasting

DECIMAL 0

SupsdAdjAllocTotalFcst FF, MP, Flowcasting

DECIMAL 0

SupsdAdjFcstCustOrders

FF, MP, Flowcasting

DECIMAL 0

SupsdAllocBaseFcst FF, Flowcasting

DECIMAL 0

SupsdAllocNonBaseFcst FF, Flowcasting

DECIMAL 0

SupsdAllocTotFcst FF, MP, Flowcasting

DECIMAL 0

SupsdBaseFcst FF, Flowcasting

DECIMAL 0

SupsdConstrProjAvail FF, MP, Flowcasting

DECIMAL 0

SupsdConstrProjOh FF, MP, Flowcasting

DECIMAL 0


SKUProjStatic



Default value

SupsdDepDmd FF, MP, Flowcasting

DECIMAL 0

SupsdDFUToSKUFcst FF, MP, Flowcasting

DECIMAL 0

SupsdFcstCustOrders FF, MP, Flowcasting

DECIMAL 0

SupsdFirmPlanArriv FF, Flowcasting

DECIMAL 0

SupsdFirmPlanOrder FF, Flowcasting

DECIMAL 0

SupsdFirmPlanShip FF, Flowcasting

DECIMAL 0

SupsdNonBaseFcst FF, Flowcasting

DECIMAL 0

SupsdNonFcstCustOrders

FF, MP, Flowcasting

DECIMAL 0

SupsdPlanArriv FF, Flowcasting

DECIMAL 0

SupsdPlanOrders FF, Flowcasting

DECIMAL 0

SupsdPlanShip FF, Flowcasting

DECIMAL 0

SupsdProjAvail FF, MP, Flowcasting

DECIMAL 0

SupsdProjOH FF, MP, Flowcasting

DECIMAL 0

SupsdRecArriv FF, Flowcasting

DECIMAL 0

SupsdRecShip FF, Flowcasting

DECIMAL 0

SupsdTotDmd FF, MP, Flowcasting

DECIMAL 0

TargetNetworkInv FF, Flowcasting

FLOAT 0

TargtImpactBaseFcst FF, Flowcasting

DECIMAL 0

TargtImpactCustOrders FF, Flowcasting

DECIMAL 0

TotalCost Flowcasting DECIMAL 0 TotalLoad Supp DECIMAL 0.0 TotalLockCustOrders FF,


TotalLockFcst FF, Flowcasting

DECIMAL 0

TotArriv FF, MP, Flowcasting

DECIMAL 0

TotContribMargin Flowcasting DECIMAL 0


SKUProjStatic



Default value

TotDmd FF, MP, Flowcasting, ESP

DECIMAL 0

TotDmdRequirement MP DECIMAL 0 TotDmdSatisfied Flowcasting DECIMAL 0

TotFcst FF, MP, Flowcasting

DECIMAL 0

TotHist MP DECIMAL 0 TotIntransIn FF, MP,


TotIntransOut FF, MP, Flowcasting

DECIMAL 0

TotRecArriv FF, Flowcasting

DECIMAL 0

TotRecShip FF, Flowcasting

DECIMAL 0

TotShip FF, MP, Flowcasting

DECIMAL 0

TotSupply FF, MP, Flowcasting

DECIMAL 0

TotSupplyRequirement MP DECIMAL 0 TotTransCost Flowcasting DECIMAL 0 TotUseRecArriv FF,


TotUseRecShip FF, Flowcasting

DECIMAL 0

UnconActualReq Supp DECIMAL 0 UnconCancel Supp DECIMAL 0 UnconCustOrder Supp DECIMAL 0 UnconDependentDmd Supp DECIMAL 0 UnconExtraUsage Supp DECIMAL 0 UnconIntersiteDmd Supp DECIMAL 0 UnconIntrsiteOrder Supp DECIMAL 0 UnconInventory Supp DECIMAL 0 UnconMasterSched Supp DECIMAL 0 UnconNetAvailable Supp DECIMAL 0 UnconNetDaysSupply Supp DECIMAL 0 UnconNetOnHand Supp DECIMAL 0 UnconNew Supp DECIMAL 0 UnconNoAction Supp DECIMAL 0 UnconPlannedOrder Supp DECIMAL 0 UnconPrjDaysSupply Supp DECIMAL 0 UnconProjAvailable Supp DECIMAL 0 UnconProjOnHand Supp DECIMAL 0


SKUProjStatic



Default value

UnconPull Supp DECIMAL 0 UnconPurchaseOrder Supp DECIMAL 0 UnconPurchaseReq Supp DECIMAL 0 UnconPush Supp DECIMAL 0 UnconReschedInFrom Supp DECIMAL 0 UnconReschedOutFrom Supp DECIMAL 0

UnconReschedSupply Supp DECIMAL 0 UnconSafetyStock Supp DECIMAL 0 UnconSubstDmd Supp DECIMAL 0 UnconSubstSupply Supp DECIMAL 0 UnconTotalDemand Supp DECIMAL 0 UnconTotalSupply Supp DECIMAL 0 UnconTVSS Supp DECIMAL 0 UnconWorkOrder Supp DECIMAL 0 UseableProjOH FF,

Flowcasting FLOAT

UnuseableSupply FF, Flowcasting

FLOAT

UnusedRequiredOH MP DECIMAL 0 UnuseOH FF, MP,


UserFirmDepdmd FF, Flowcasting

DECIMAL 0

UserFirmPlanArriv FF, MP, Flowcasting

DECIMAL 0

UserFirmPlanOrd FF, MP, Flowcasting

DECIMAL 0

UserFirmPlanShip FF, MP, Flowcasting

DECIMAL 0

UserID FF, MP, Flowcasting

TEXT ' '

WOLoad Supp DECIMAL 0.0

Table description Each row in this table presents projections for a SKU for a particular time period. Rows are written to this table as a result of running the Store SKU Projections process. When you rerun the Store SKU Projections process for a specific option set (see the OptionSet column), the SKU data with that option set is replaced.

Note: Since the SKUProjStatic table simply stores static data, you must run the Store SKU Projections process to recalculate data after any changes.

Column descriptions ActualIntransIn


SKUProjStatic

Actual Intransits In is the total Actual Intransits arriving at this destination SKU in this period that are being used to meet the demand of this item. The system calculates this value based on values in the VehicleLoad and VehicleLoadLine tables where the destination is this SKU, VehicleLoad:SourceStatus is 2 or 3 (Shipped), and VehicleLoad:DestStatus is 1 (Not Received) or 2 (Received, but not part of destination on hand).

ActualIntransOut Actual Intransits Out is the total Actual Intransits shipped from this source SKU in this period. The system calculates this value based on values in the VehicleLoad and VehicleLoadLine tables where the source is this SKU and VehicleLoad:SourceStatus is 2 (Shipped, but part of on hand).

AdjAllocAggMktActvtyFcst Adjusted Allocated Aggregated Market Activity Forecast is the allocated aggregated market activity forecast after being adjusted with the aggregated market activity customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on adjusted allocated aggregated market activity forecast.

AdjAllocAutoFcst Adjusted Allocated Auto Forecast is the allocated auto forecast after being adjusted with the auto customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated auto forecast.

AdjAllocBaseFcst Adjusted Allocated Base Forecast is the allocated base forecast after being adjusted with the base customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated base forecast.

AdjAllocDataDrvnFcst Adjusted Allocated Data Driven Forecast is the allocated data driven forecast after being adjusted with the base customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated data driven forecast.

AdjAllocMktActvtyFcst Adjusted Allocated Market Activity Forecast is the allocated market activity forecast after being adjusted with the market activity customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated market activity forecast.

AdjAllocNonBaseFcst Adjusted Allocated Non Base Forecast is the allocated non base forecast after being adjusted with the non base customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated non base forecast.

AdjAllocOvrideFcst Adjusted Allocated Override Forecast is the allocated override forecast after being adjusted with the override customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated override forecast.

AdjAllocReconcileFcst Adjusted Allocated Reconcile Forecast is the allocated reconcile forecast after being adjusted with the reconcile customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated reconcile forecast.

AdjAllocTargtlmpactFcst Adjusted Allocated Target Impact Base Forecast is the allocated target impact base forecast after being adjusted with the target impact base customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated target impact base forecast.

AdjAllocTotalLockFcst


SKUProjStatic

Adjusted Allocated Total Lock Forecast is the allocated total lock forecast after being adjusted with the total lock customer orders. See AdjAllocTotFcst (on page 395) to understand the impact of forecast adjustment rules on the adjusted allocated total lock forecast.

AdjAllocTotFcst Adjusted Allocated Total Forecast is the Allocated Total Forecast after being adjusted and consumed with customer orders. For more information, see FcstAdjRule (on page 303) and FcstConsumptionRule (on page 310).

AdjFcstCustOrders Adjusted Forecasted Customer Orders is the total demand due to forecasted customer orders. The system calculates AdjFcstCustOrders by the method specified in SKUDemandParam:FcstAdjRule.

Within the Customer Order Duration, (SKUDemandParam:CustOrderDur), the sum of AdjAllocTotFcst and AdjFcstCustOrders is equivalent to the true adjusted forecast, as explained under the AdjAllocTotFcst column.

AggMktActvtyCustOrders Forecasted customer order whose FcstType is ‘aggregate market activity’.

AggMktActvtyFcst Forecast of type ‘aggregate market activity’, allocated by time and not by the allocation calendar.

AggNegConstrProjOH Aggregated Negative Constrained Projected OH is the sum of all negative ConstrProjOH (on page 402) for the SKU aggregation you have set in the Plan Analysis page. For more information on SKU aggregation, refer Using SKU aggregation section in the Working with Plan Analysis chapter of the JDA Fulfillment OnLine Expert.

AggNegProjOH Aggregated Negative Projected OH is the sum of all negative ProjOH (on page 413) for the SKU aggregation you have set in the Plan Analysis page. For more information on SKU aggregation, refer Using SKU aggregation section in the Working with Plan Analysis chapter of the JDA Fulfillment OnLine Expert.

AggPosConstrProjOH Aggregated Positive Constrained Projected OH is the sum of all positive ConstrProjOH (on page 402) for the SKU aggregation you have set in the Plan Analysis page. For more information on SKU aggregation, refer Using SKU aggregation section in the Working with Plan Analysis chapter of the JDA Fulfillment OnLine Expert.

AggPosProjOH Aggregated Positive Projected OH is the sum of all positive ProjOH (on page 413) for the SKU aggregation you have set in the Plan Analysis page. For more information on SKU aggregation, refer Using SKU aggregation section in the Working with Plan Analysis chapter of the JDA Fulfillment OnLine Expert.

AllDmd The sum of aggregation of all demand types (AdjAllocTotFcst, DepDmd, TotShip, TotIntransOut, AdjFcstCustOrders, NonFcstCustOrders,AllocRecShip, and Backorders) including those portions of each demand type that are considered ignored. AllDmd = TotDmd + IgnoredDmd.

AllIntransIn All Intransits In is the total quantity of inbound intransits for this SKU. This column is the sum of:

• TotIntransIn (inbound intransits of this SKU used to meet the demand of this SKU)

• ProxyIntransIn (inbound intransits of this SKU used to meet the demand of other SKUs)

AllocAggMktActvtyFcst


SKUProjStatic

Allocated Aggregate Market Activity Forecast is the aggregate market activity forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated aggregate market activity forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocAutoFcst Allocated Auto Forecast is the auto forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated auto forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocBaseFcst Allocated Base Forecast is the base forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated base forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocDataDrvnFcst Allocated Data Driven Forecast is the data driven forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated data driven forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocMktActvtyFcst Allocated Market Activity Forecast is the market activity forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated market activity forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocNonBaseFcst Allocated Non-Base Forecast is the sum of the rows from the DFUToSKUFcst table where DFUToSKUFcst:Type is not equal to 1.

AllocOvrideFcst Allocated Override Forecast is the override forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated override forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocReconcileFcst Allocated Reconcile Forecast is the reconcile forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated reconcile forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocTargtlmpactFcst Allocated Target Impact is the allocated target impact base forecast , based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated target impact forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocTotalLockFcst Allocated Total Lock Forecast is the total lock forecast for this period, based on the profile defined by the allocation calendar. If the SKUDemandParam:ProrateByTypeSw is set to Yes, the allocated total lock forecast is prorated by SKUDemandTypeParam:DmdToDate. See AllocTotFcst (on page 396) to understand how the system prorates the demand.

AllocTotFcst


SKUProjStatic

Allocated Total Forecast is the total forecast for this period, based on the profile defined by the Allocation Calendar (SKUDemandParam:AllocCal). (If no allocation calendar is specified, TotFcst and AllocTotFcst have the same value.)

AllocTotFcstNoProration This is the total forecast for this period based on the profile defined by the allocation calendar (SKUDemandParam: AllocCal) without proration. If SKUDemandParam: ProrateSw is set to N, AllocTotFcstNoProration and AllocTotFcst have the same value.

AltConstCantMeetQty Note: This column is not used in this release.

AltConstrCovDur Alternate Constrained Coverage Duration is the duration of constrained coverage, taking into account both constrained supply and constrained demand. AltConstrCovDur is based on constrained total demand, that is, a calculation of total demand that includes total recommended shipments instead of total planned shipments, and on constrained supply (similar to AltConstrPOH), but which also reflects constrained supplies and demands that are generated from Supersession inventory transfers. The coverage duration value reflects the duration until the first point in time at which the inventory level falls below zero, based on the projected on hand and demands. The calculation respects DisplayQty values as a temporary demand; that is, for the effective duration of each SSPresentation:DisplayQty row, the value of DisplayQty is considered not to be a part of the alternate constrained planned projected onhand.

The maximum coverage duration is 10 years.

For perishable SKUs, instead of AltConstrProjOH, the sum of ( AltConstrProjOH - AltConstrUnuseableSupply) is used for the calculation

For SuperSession SKUs, instead of PlanShip, ConstrProxyDemand and RecShip are considered as part of constrained demand and instead of AltConstrProjOH, the AltSupsdConstrProjOH is used.

AltConstrainedUnuseOH Alternate Constrained Unusable On-Hand is the constrained inventory that, based on supply and demand projections, will expire before it is used. It differs from ConstrUnuseOH (on page 404) in that it considers recommended shipments as demand and not the total shipment. The inventory in this column is displayed on the date when the effective shelf life ends. (The effective shelf life is the difference between the SKUPerishableParam:ShelfLifeDur and the SKUPerishableParam:MinShelfLifeDur of an item.) Alternate Constrained Unusable On-Hand is calculated as:

Total Constrained Supply - Total Constrained Demand - Total Planned Shipments + Recommended Shipments - ConstrUnuseOH (on page 404)

AltConstrPOH Alternative Constrained Projected On Hand is the constrained projected on hand at the source SKU as of the SKU projection Date. (ConstrProjOH shows you projected on hand for destination SKUs.) AltConstrPOH provides an alternate method of calculating constrained projected on hand that considers recommended shipments, rather than total shipments (TotShip), as a component of demand.

AltConstrPOH is calculated as follows:

AltConstrPOH = AltConstrPOH (previous period) + SchedRcpts + Inventory + RecArriv + RecAllocArriv + TotIntransIn – AltTotDmd, where for each period, AltTotDmd* = AdjAllocTotFcst + DepDmd + RecShip + RecAllocShip + TotIntransOut + AdjFcstCustOrders + NonFcstCustOrders (*AltTotDmd is used only in the calculation of AltConstrPOH; it is not an actual column in the SKUProjStatic table.)

When SKUDeploymentParam:RecShipSupplyRule is set to 2 (Yes) for a source SKU, the calculation for AltConstrPOH includes planned orders and firm planned orders as part of supply.


SKUProjStatic

AltConstrPOH, when RecShipSupplyRule = 2, is calculated as shown below:

AltConstrPOH (previous period) + SchedRcpts +Inventory + RecArriv + RecAllocArriv + TotIntransIn + PlanOrder + FirmPlanOrder – AltTotDmd, where for each period, AltTotDmd = AdjAllocTotFcst + DepDmd + RecShip + TotIntransOut + AdjFcstCustOrders + NonFcstCustOrders

AltConstrUseableProjOH The Alternate Constrained Useable Projected Onhand shows the projected inventory excluding any supply that is projected to not be sold before its Unuseable Date, as shown in ConstrUnuseableSupply.

This projection is significant for perishable SKUs only, and differs from AltConstrProjOH as follows. When AltConstrProjOH calculates projected inventory, it subtracts out any unuseable supply on its unuseable date. AltConstrUseableProjOH also excludes unuseable supplies, but it excludes those supplies starting on their available date, so that the unuseable portions of supply are never reflected in the projection at all. This projection is used in the calculation of AltConstrCovDur for perishable items.

AltConstrUnuseableSupply For a perishable SKU, Alternate Constrained Unuseable Supply shows the portions of supply that will become unuseable before it is sold, based on all constrained projected supplies and constrained projected demands. This projection of unuseable supply is shown on the supply available date.

AltSubConstProjOH This column is not used in this release.

AltSuspdConstrProjAvail Alternate Supersession Constrained Projected Available shows the projected available on a supersession SKU. This column is equal to AltSupsdConstrProjOH minus SS.

AltSupsdConstrProjOH Alternate Supersedable Constrained Projected On Hand displays the alternate supersedable constrained projected on hand inventory calculated as:

AltSupsdConstrProjOH= AltConstrPOH + ConstrProxySupply - ConstrProxyDemand + ProxyRecArriv - ProxyRecShip

ATP Available to Promise is the quantity of product that is or will be available at any given point in time to meet new customer demand. Available to Promise reflects product that is being produced over and above the requirements for existing customer orders and committed shipments.

The system calculates ATP values by subtracting demand (forecasted and non-forecasted customer orders) from point-in-time supply.

Available supply is calculated as:

OH + SchedRcpts + PlanOrders + RecArriv + TotIntransIn

– (RecShip + TotIntransOut + CustOrder + FirmedDepDmd)

where:

• SKU projections PlanOrders and FirmPlanOrders are included in supply only if

SKUDeploymentParam:RecShipSupplyRule is set to 2=Yes

• CustOrders include non-forecasted customer orders and forecasted adjusted customer orders.

• Total intransits in (TotIntransIn) is the total of:

CommitIntransIn + ActualIntransIn

• Recommended shipments are considered as committed shipments and are thus subtracted from the supply that is available to meet customer orders.


SKUProjStatic

• Total intransits out (TotIntransOut) is the total of:

CommitIntransOut + ActualIntransOut

ATP values can be calculated in two ways, depending on the value of SKUPlanningParam:ATPRule that is specified. For both rules, the ATP calculations start at OHPost.

For ATPRule = 1, the start date and duration from the Plan Analysis page determine the end point of the ATP calculations. For each date, the calculations consider all supply to date against all demand throughout the full duration. With this method, you will not see an ATP value unless the stock available to date exceeds the total demand within the Plan Analysis duration.

For ATPRule = 2, the ATP duration is read from SKUPlanningParam:ATPDur. The logic calculates a projected inventory value for each date, considering all demands and supplies. Then the ATP value for any point in time reflects the smallest projected inventory value from that date through the end of the ATP duration.

The following example illustrates both methods for calculating ATP. Note that with the calculation for ATPRule 2, ATP values for the fourth period are set to zero, since this period falls outside of the ATP duration.

• OH=100

• ATPDur=3W

• Plan Analysis Dur = 28D

Week Demand Supply ATP calculation using ATPRule = 1

ATP calculation using ATPRule = 2

100 0

1 50 0 50 2 50 400 200 300 3 100 200 300 4 100 200 0

AutoCustOrders Forecasted customer order whose FcstType is ‘auto’.

AutoFcst Forecast of type ‘auto’, allocated by time and not by the allocation calendar.

AvailShipOH Available to Ship On Hand is the amount of OH that is available to ship. This quantity is calculated as:

ProjOH for this period - Sum of CommitIntransOut values that are later than this period and within the Calculate Plan duration.

AvgCycleStock Note: This column is not used in the current release.

AvgIntransitStock Note: This column is not used in the current release.

BaseCustOrders Forecasted customer order whose FcstType is ‘base’.

BaseFcst


SKUProjStatic

The sum of rows from the DFUToSKUFcst table where DFUToSKUFcst:Type is equal to 1 and the external forecast for the SKU (SKUExternalFcst column) is allocated by time, not by an allocation calendar.

BaseHist Note: This column is not used in the current release.

CMPFirmDepDmd Note: This column is not used in the current release.

CMPFirmPlanArriv Note: This column is not used in the current release.

CMPFirmPlanOrd Note: This column is not used in the current release.

CMPFirmPlanShip Note: This column is not used in the current release.

COMetEarlyCount Customer Order Met Early Count is the number of customer orders met before the need date.

COMetLateCount Customer Order Met Late Count is the number of customer orders met after the need date.

COMetOntimeCount Customer Order Met Ontime Count is the number of customer orders met by the need date.

COMetPartialCount Customer Order Met Partial Count is the number of customer orders met partially.

CommitIntransIn Committed Intransits In is the total load quantities arriving at this destination SKU in this period that are being used to meet the demand of this item. The system calculates this value based on values in the VehicleLoad and VehicleLoadLine tables where the destination is this SKU and VehicleLoad:SourceStatus is 1 (Not Shipped).

CommitIntransOut Committed Intransits Out is the total load quantities being shipped from this source SKU in this period. The system calculates this value based on values in the VehicleLoad and VehicleLoadLine tables where the source is this SKU and VehicleLoad:SourceStatus is 1 (Part of On Hand).

ConCancel Constrained Cancel is the sum of supplies of the SKU whose available date falls within the display bucket and has been recommended for Cancel.

ConCustOrder Constrained Customer Order is the sum of all the Customer Order Demand for the SKU whose need date falls within the display time bucket (Based on the selected Reporting Calendar).

CONeedUnit Customer Order Need Unit is the number of units based on the need date and the need quantity.

ConExtraUsage Constrained Extra Usage is the sum of all the Extra Usage Demand for the SKU whose need date falls within the display time bucket (Based on the selected Reporting Calendar).

ConIntersiteOrder Constrained Inter Site Order is the sum of all the supplies of type Inter Site Order of SKU whose scheduled date falls within the display bucket.


SKUProjStatic

ConInventory Constrained Inventory is the On-hand free inventory available to meet the demand.

ConMasterSched Constrained Master Schedule is the sum of all the Master Schedule Demand for the SKU whose need date falls within the display time bucket (Based on the selected Reporting Calendar).

ConNew Constrained New is the sum of supplies of the SKU whose need date belongs to the display bucket and has been recommended as New Supplies.

ConNoAction Constrained No Action is the sum of all the supplies for which No Action has been recommended and whose need date falls within the display bucket.

CoProductPlanOrders The sum of all PlanOrder:Qty (on page 208) for this SKU whose PlanOrder:SchedDate falls within this time period and whose value in PlanOrder:CoProdOrderType (on page 206) is not Primary Planned Order.

ConPull Constrained Pull is the sum of supplies of the SKU whose need date falls within the display bucket and has been recommended for Pull.

ConPurchaseOrder Constrained Purchase Order is the sum of all the supplies of type Purchase Order of SKU whose scheduled date falls within the display bucket.

ConPurchaseReq Constrained Purchase Requisition is the sum of all the supplies of type Purchase Requisition of SKU whose scheduled date falls within the display bucket.

ConPush Constrained Push is the sum of supplies of the SKU whose need date belongs to the display bucket and has been recommended for Push.

ConReschedSupply Constrained Rescheduled Supply is the sum of scheduled supplies that have been rescheduled by Resource Optimization algorithm and new supplies that have been recommended to meet the demand.

ConSafetyStock Constrained Safety Stock is the sum of all the Safety Stock Demand for the SKU whose need date falls within the display time bucket (Based on the selected Reporting Calendar).

ConSchedSupply Constrained Scheduled Supply is the sum of all the Purchase Order, Work Order, Inter-Site Order, Purchase Requisition, and Inventory Supply of SKU, whose scheduled date falls within the display Bucket.

ConShCustOrder Constrained Shortage Customer Order is the sum of Shortage in Customer Order Demand (scheduled date > need date) whose need date falls within the bucket in which it is displayed.

ConShExtraUsage Constrained Shortage Extra Usage is the sum of Shortage in Extra Usage Demand (scheduled date > need date) whose need date falls within the bucket in which it is displayed.

ConShMasterSched


SKUProjStatic

Constrained Shortage Master Schedule is the sum of Shortage in Master Schedule Demand (scheduled date > need date) whose need date falls within the bucket in which it is displayed.

ConShortage Constrained Shortage is the sum of all shortages (scheduled date > need date) whose need date falls within the bucket in which it is displayed.

ConShSafetyStock Constrained Shortage Safety Stock is the sum of Shortage in Safety Stock Demand (scheduled date > need date) whose need date falls within the bucket in which it is displayed.

ConstrCantMeetQty Note: This column is not used in this release.

ConsolidatedPlanShip The total amount of planned shipments from this source SKU for this period. The Calculate Plan process generates these shipments which are published in PlanShip table. The system calculates ConsolidatedPlanShip as the total of the values in PlanShip:Qty for rows whose source is this SKU.

ConstrCovDur Constrained Coverage Duration is the duration of constrained forward coverage.

ConstrCovDur is based on Total Demand (TotDmd) and a constrained version of Planned Projected on Hand (ConstrProjOH) as of Date, which includes supplies and demands that are generated from Supersession inventory transfers. The coverage duration value reflects the duration until the first point in time at which the inventory level falls below zero, based on the projected on hand and demands. The calculation respects DisplayQty values as a temporary demand; that is, for the effective duration of each SSPresentation:DisplayQty row, the value of DisplayQty is considered not to be a part of the constrained planned projected onhand.


For perishable SKUs, instead of ConstrProjOH, the sum of (ConstrProjOH - ConstrUnuseableSupply) is used for the calculation.

For SuperSession SKUs, instead of TotDmd and ConstrProjOH, the sum of (TotDmd + ProxyDemand) and SupsdConstrProjOH are used for the calculation.

ConstrExpOH Constrained Expired On-Hand is the constrained inventory that, based on supply and demand projections, will expire before it is used. (ConstrExpOH differs from ExpOH in that it includes recommended arrivals (based on stock that is actually available), not planned arrivals and planned orders.) The inventory in this column is displayed on the date that it expires.

The quantities in the columns ConstrUnuseOH and ConstExpOH will always match, but will be offset by the SKUPerishableParam:MinShelfLifeDur, with the ConstUnuseOH displaying earlier than the ConstExpOH.

ConstrNetReqts Note: This column is not used in the current release.

ConstrProjAvail Constrained Projected Available is the constrained projected available as of SKU projection Date. The system calculates ConstrProjAvail as ConstrProjOH - SS as of Date.

ConstrProjOH Constrained Projected On Hand is the constrained projected on hand at the destination SKU as of SKU projection Date.

Fulfillment


SKUProjStatic

ConstrProjOH differs from ProjOH in that it includes recommended arrivals (based on stock that is actually available), not planned arrivals.

If the page's Allocation Period Date is Begin and RecShipSupplyRule is 2, the system calculates ConstrProjOH as:

ConstrProjOH (previous period) + SchedRcpts + RecArriv + ReacAllocArriv + TotIntransIn + Inventory + PlanOrder + PlanOrderFirm - TotDmd

where for each period:

TotDmd = AdjAllocTotFcst + DepDmd + TotShip + RecAllocShip + TotIntransOut + AdjFcstCustOrders + NonFcstCustOrders

If the Allocation Period Date is End, the system uses ProjOH from the previous interval and all other values from the current interval.

If the RecShipSupplyRule is 1 then ConstrProjOh does not consider plan order and firm plan order in the formula.

ConstrProxyDemand Constrained Proxy Demand displays the constrained inventory transfers created by the Recommended Shipments with Supersession portion of Calculate Plan, where inventory from this SKU has been reassigned to meet the demands of a different SKU and item. This data is read from the RecSubInventory table, where RecSubInventory:Type = 2 and RecSubInventory:Item is this item.

ConstrProxySupply Constrained Proxy Supply displays the constrained inventory transfers created by the Recommended Shipments with Supersession portion of Calculate Plan, where inventory from a different SKU and item has been reassigned to meet the demands of this SKU. This data is read from the RecSubInventory table, where RecSubInventory:Type = 2 and SKUSubInventory:PrimaryItem is this item.

ConstrSchedExpOH Constrained Scheduled Expired On-Hand is the constrained inventory originally scheduled for the SKU, displayed on the date that the inventory would expire if it were not used. (ConstrSchedExpOH differs from SchedExpOH in that it includes recommended arrivals (based on stock that is actually available), not planned arrivals and planned orders.)

ConstrSchedUnuseOH Constrained Scheduled Unusable On-Hand is the constrained inventory originally scheduled for the SKU, displayed on the date that the inventory's effective shelf life would end if it were not used. (ConstrSchedUnuseOH differs from SchedUnuseOH in that it includes recommended arrivals (based on stock that is actually available), not planned arrivals and planned orders.) The effective shelf life is the difference between the SKUPerishableParam:ShelfLifeDur and the SKUPerishableParam:MinShelfLifeDur of an item.)

ConstrUseableProjOH The Constrained Useable Projected Onhand shows the projected inventory excluding any supply that is projected not to be sold before its unuseable date, as shown in ConstrUnuseableSupply. This projection is significant for perishable SKUs only and differs from ConstrProjOH as follows. When ConstrProjOH calculates the projected inventory it subtracts out any unuseable supply on its unuseable date. UseableProjOH also excludes unuseable supplies, but it excludes those supplies starting on their available date, so that the unuseable portions of supply are never reflected in the projection at all. This projection is used in the calculation of ConstrCovDur for perishable items.

ConstrUnuseableSupply For a perishable SKU, Constrained Unuseable Supply shows the portions of supply that will become unuseable before it is sold, based on all constrained projected supplies and total projected demands. This projection of unuseable supply is shown on the supply available date.


SKUProjStatic

ConstrUnuseOH Constrained Unusable On-Hand is the constrained inventory that, based on supply and demand projections, will expire before it is used. (ConstrUnuseOH differs from UnuseOH in that it includes recommended arrivals (based on stock that is actually available), not planned arrivals and planned orders.) The inventory in this column is displayed on the date that it becomes unusable, that is when the effective shelf life ends. (The effective shelf life is the difference between the SKUPerishableParam:ShelfLifeDur and the SKUPerishableParam:MinShelfLifeDur of an item.)

The quantities in the columns ConstrUnuseOH and ConstExpOH will always match, but will be offset by the SKUMinShelfLifeDur, with the ConstUnuseOH displaying earlier than the ConstExpOH.

ConSubstSupply Constrained Substitution Supply is the sum of all the supplies of the SKU which is being recommended to be fulfilled by a substitute SKU, and whose need date falls within the display bucket.

ConTotalDemand Constrained Total Demand is the sum of all the Constrained Customer Order, Safety Stock, Extra Usage, and Master Schedule Demand. This is bucketed on the NeedDate of the demand.

ConWorkOrder Constrained Work Order is the sum of all the supplies of type Work Order of SKU whose scheduled date falls within the display bucket.

CoProductProdReqt The sum of all ProdRequirement:Qty for this SKU, whose ProdRequirement:SchedDate falls within this time period and PlanOrder:CoProdOrderType is not the primary production requirement.

COProjMargin Customer Order Projected Margin is the projected margin for customer orders based on the need date and the need quantity.

COProjRevenue Customer Order Projected Revenue is the projected revenue for customer orders based on the need date and the need quantity.

CORealMargin Customer Order Realized Margin is the realized margin for customer orders based on the scheduled date and the scheduled quantity.

CORealRevenue Customer Order Realized Revenue is the realized revenue for customer orders based on the scheduled date and the scheduled quantity.

COSchedUnit Customer Order Scheduled Unit is the number of units based on the scheduled date and the scheduled quantity.

COUnmetCount Customer Order Unmet Count is the number of unmet customer orders.

COUnplannedCount Customer Order Unplanned Count is the number of unplanned customer orders.

CovDur


SKUProjStatic

Coverage Duration is the duration of forward coverage, based on planned projected onhand (SKU projection PlanProjOH) and total demand (SKU projection TotDmd) as of SKU projection Date. The coverage duration value reflects the duration until the first point in time at which the inventory level falls below zero, based on the projected on hand and demands. The calculation respects DisplayQty values as a temporary demand; that is, for the effective duration of each SSPresentation:DisplayQty row, the value of DisplayQty is considered not to be a part of the planned projected onhand. The maximum coverage duration is 10 years.

For perishable SKUs, instead of ProjOH, the sum of (PlanProjOH - UnuseableSupply) is used for the calculation.

For Supersession SKUs, instead of TotDmd, the sum of (TotDmd + ProxyDemand) is used. Any DisplayQty value is subtracted from PlanProjOH and is not considered as part of the supply upon which the coverage duration is based.

CovDurCantMeetQty Note: This column is not used in this release.

DataDrvnCustOrders Forecasted customer order whose FcstType is ‘data driven’.

DataDrvnFcst Forecast of type ‘data driven’, allocated by time and not by the allocation calendar.

DemandResExcepCount IDemand Resource Exception Count is the number of exceptions raised due to resource loads. These exceptions are stored in the ResException table.

DemandSKUExcepCount Demand SKU Exception Count is the number of SKU related exceptions. These exceptions are stored in the SKUException table.

DepDmd The sum of all dependent demand in the time period. The system derives DepDmd from the DepDmdStatic table.

DepDmdEarliestNeed Projection of dependent demand need quantity at the earliest need date.

DepDmdRequirement The sum of all dependent demand requirements within this time period. Dependent demands are obtained from the DepDmdRequirement table.

DetailedPlanShip The total amount of planned shipments from this source SKU for this period. The Calculate Plan process generates these shipments which are published in PlanArriv table. The system calculates DetailedPlanShip as the total of the values in PlanArriv:Qty for rows whose source is this SKU and whose value in PlanArriv:FirmPlanSw is No.

DisplayQty Displays the sum of the values for the active rows in SSPresentation:DisplayQty. This values represents inventory that is not considered saleable and is also separate from the safety stock total.

DistRequirement The sum of all distribution requirements for this destination SKU for this time period. This is calculated based on the rows in the DistRequirement table whose destination is this SKU.

DistShipRequirement


SKUProjStatic

The sum of all planned shipments from this source SKU for this time period. The Calculate Requirement Plan process generates and publishes the results of these shipments in the DistRequirement table.

DFUToSKUFcst The forecast from the DFUToSKUFcst table where DFUToSKUFcst:Type is equal to 1, and the forecast is allocated by time, not by an allocation calendar. Specifically, this is the base forecast from the DFUToSKUFcst table, and does not include the quantity from the SKUExternalFcst table.

Dur The duration of the time interval that applies to the data in this row, based on the Calendar specified.

ExpiredRequiredOH The inventory that, based on supply and demand projections, expires before being used. The inventory in this column is displayed on the expiry date.

The quantities in the SKU projection columns UnusedRequiredOH and ExpiredRequiredOH always match, but are offset by SKUPerishableParam:MinShelfLifeDur, with UnusedRequiredOH displayed earlier than ExpiredRequiredOH.

ExpOH Expired On-Hand is the inventory that, based on supply and demand projections, will expire before it is used. The inventory in this column is displayed on the date that it expires.

The quantities in the columns SKU projections UnuseOH and ExpOH will always match, but will be offset by the minimum shelf life (SKUPerishableParam:MinShelfLifeDur), with the UnuseOH displaying earlier than the ExpOH.

FcstCustOrders Customer orders that were part of the forecast. If SKUDemandParam:FcstAdjRule is 2 or 3, the system uses these orders to adjust the forecast.

FcstCustOrders is the sum of all orders where:

• CustOrder:Status = 1 or 2

• CustOrder:FcstSw = Yes

• CustOrders:ResExp is greater than SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank) and is within this time period; or CustOrders:Reservations = 0

The system calculates the value in this column from the CustOrder table.

FirmPlanArriv The total amount of firm planned arrivals for this destination SKU for this period. The system calculates this value based on the values in the PlanArriv table for rows whose destination is this SKU and whose value in PlanArriv:FirmPlanSw is Yes.

FirmPlanOrder The total of all PlanOrder:Qty values for planned orders whose PlanOrder:SchedDate falls within this time period and whose PlanOrder:FirmPlannedSw is Yes.

FirmPlanShip The total amount of firm planned shipments from this source SKU for this period. The system calculates FirmPlanShip as the total of the values in PlanArriv:Qty for rows whose source is this SKU and whose value in PlanArriv:FirmPlanSw is Yes.

FirmProxyInventory This column is not used in this release.

FirmSchedRcpts


SKUProjStatic

Total quantity of all scheduled receipts whose SchedRcpt:ActionAllowedSw is set to Yes.

FirmSubInventory This column is not used in this release.

FirmSupplyCovDur FirmSupplyCovDur is the duration of constrained forward coverage that is based on Total Demand(TotDmd) and Firm Supply Projected on-hand(FirmSupplyProjOH) as of date.


FirmSupplyProjOH FimrSupplyProjOH is the constrained projected on hand, based on firm supplies excluding RecArriv, at the destination SKU as of SKU projection Date.

Fulfillment

FirmSupplyProjOH differs from ConstrProjOH in that it excludes recommended arrivals.

If the page’s allocation period is Begin, the system calculates FirmSupplyProjOH as:

FirmSupplyProjOH = FirmSupplyProjOH (previous period) + SchedRcpts + TotInTransIn + ReacAllocArriv + Inventory - TotDmd.

Where for each period:

TotDmd = AdjAllocTotFcst + ReacAllocShip + DepDmd + TotShip + TotIntransOut + AdjFcstCustOrders + NonFcstCustOrders.

If the allocation period is End, the system uses FirmSupplyProjOH from the previous interval and all other values from the current interval.

FOMetEarlyCount Forecast Order Met Early Count is the number of forecast orders met before the need date.

FOMetLateCount Forecast Order Met Late Count is the number of forecast orders met after the need date.

FOMetOntimeCount Forecast Order Met Ontime Count is the number of forecast orders met by the need date.

FOMetPartialCount Forecast Order Met Partial Count is the number of forecast orders met partially.

FONeedUnit Forecast Order Need Unit is the number of units based on the need date and the need quantity.

FOProjMargin Forecast Order Projected Margin is the projected margin for forecast orders based on the need date and the need quantity.

FOProjRevenue Forecast Order Projected Revenue is the projected revenue for forecast orders based on the need date and the need quantity.

ForcedSuppOrderQty Forced Supplemental Order Quantity represents the total quantity for all forced supplemental orders (SuppOrderSKU:Type=2) defined for the SKU by records in the SuppOrderSKU table. The SuppOrderSKU:NeedQty is displayed on SKUPlanningParam:FirstReplenDate.

FORealMargin


SKUProjStatic

Forecast Order Realized Margin is the realized margin for forecast orders based on the scheduled date and the scheduled quantity.

FORealRevenue Forecast Order Realized Revenue is the realized revenue for forecast orders based on the scheduled date and the scheduled quantity.

FOSchedUnit Forecast Order Scheduled Unit is the number of units based on the scheduled date and the scheduled quantity.

FOUnmetCount Forecast Order Unmet Count is the number of unmet forecast orders.

FOUnplannedCount Forecast Order Unplanned Count is the number of unplanned forecast orders.

HoldOutQty Hold Out Quantity indicates the current effective supplemental order holdout quantity for a SKU. The HoldOutQty for a SKU is considered unavailable to meet any demands until its release, and thus is subtracted from projected on hand, along with the safety stock, when calculating projected available for the SKU. For each regular supplemental order (Type = 1) the HoldoutQty reflects the supplemental order quantity from SuppOrderSKU:NeedArrivDate through SuppOrderSKU:HoldOutReleaseStart.

For each Forced Supplemental Order (Type = 2 or 3) the HoldOutQty displays the supplemental order quantity from SKUPlanningParam:FirstReplenDate until SuppOrderSKU:HoldOutReleaseStart. If SKUPlanningParam:FirstReplenDate is blank, supplemental order quantity is displayed from OHPost until SuppOrderSKU:HoldOutReleaseStart. For a forced supplemental order with SuppOrderSKU:HoldOutReleaseStart earlier than SKUPlanningParam:FirstReplenDate, no HoldOutQty is displayed.

For any supplemental order for which SuppOrderSKU:HoldOutReleaseStart is blank, no HoldOutQty is displayed.

IgnoredDmd Represents the quantity of demands ignored by the Calculate Plan and Optimize Orders process.

For all items, this column displays the quantity of ignorable demands that cannot be met on time by firm supplies between OHPost and FirstReplenDate, and that are ignored by the Calculate Plan or Optimize Orders process. Demands are ignored only if they are designated as ignorable in the demand reduction strategy referenced by SKUDemandParam:DmdRedID.

For items processed by Calculate Plan with SKU:StorableSw = zero, ignored demands are read from the IgnoredDmd table. The calculation of ignored demands is informed by all data in the DmdRed table and by the following SRE properties: ConsumeIgnoreableFirst; RetainSSinDmdReduction.

Demands are not ignored in Master Planning.

For more information on ignored demands, see Eliminate unmet demand

For perishable items, demands ignored after FirstReplenDate and stored in the IgnoredDmd table are also displayed in this column.

IncMaxCovDur Incremental Maximum Coverage Duration displays the upper limit for forward coverage duration defined in SSTemplateData:IncMaxCovDur for the safety stock template assigned to the SKU (in SKUSafetyStockParam:SSTemplate). You can use this value for purposes of comparison with the incremental coverage duration (SSTemplateData:IncCovDur) and the actual coverage duration CovDur.


SKUProjStatic

IncMinCovDur Incremental Minimum Coverage Duration is the incremental coverage duration in effect for this SKU. The duration is derived from the duration specified for the safety stock template (SSTemplateData:IncCovDur) assigned to the SKU (SKUSafetyStockParam:SSTemplate). The value in this column, plus the duration in SKUSafetyStockParam:SSCov, equal the total number of days’ forward coverage to be used in calculating safety stock for SKUs that use Safety Stock Rules 2, 3, or 4.

IndDmd The total customer order and forecast order quantity. This quantity does not include safety stock orders.

IndDmdExceptionCount Independent Demand Exception Count is the count of exceptions that are generated for independent demand orders (CustOrders, FcstOrders, and SafetyStockOrders).

IndDmdExceptionQty Independent Demand Exception Quantity is the total number of independent demand (CustOrders, FcstOrders, and SafetyStockOrders) exceptions that are generated.

InvCarCost Note: This column is not used in the current release.

Inventory Total quantities from the Inventory table, slotted by available date, for all inventory whose Inventory:Type is 1 (Inventory).

IPOAvgStock The average stock level maintained in the system to meet the desired target.

IPOExpBackOrder The average number of back orders that can be expected in the operational system, provided the specified inventory policy is maintained. It is a measure of the demand waiting to be satisfied for SKUs because of the unavailability of stock on hand.

IPOFcstBias The IPO Forecast Bias column is calculated as the difference between IPOSKUHistFcst (on page 410) and IPOSKUHist (on page 410) column.

IPODmd The average daily demand expected for this SKU.

IPOProjOH The projected on-hand inventory at the destination SKU as of the SKUProjDate. Calculated based on on-hand inventory, Mean Daily Demand, Reorder Point and Reorder Quantity.

When the on-hand inventory reaches the Reorder Point, the Reorder Quantity is added to arrive at new on-hand inventory levels. When the on-hand inventory = 0, then R + Q (maximum stock levels).

IPOReorderPoint The stock point at which replenishment (purchase or repair) orders should be generated. When the inventory position (on-hand + on-order – backorders) reaches the Reorder Point, you should place a replenishment order. Reorder Point is an inventory policy recommended by IPO and is equal to the difference between StockLevel and ReorderQty.

IPOReorderQty The number of units of a SKU that should be ordered when the SKU’s StockLevel reaches the ReorderPoint. This value is calculated based on the value selected in SKUIPOParam: ReorderOpt. If ReorderOpt is 1, the order quantity is equal to the value in SKUIPOParam: EOQ (on page 367). If ReorderOpt is 2, the order quantity is calculated as:


SKUProjStatic

SKUIPOParam: FwdCovDur x mean daily demand

IPOSafetyStock The IPO-recommended quantity of stock to be maintained in order to achieve the desired long-run average performance measures (unit fill rate, customer wait time, and operational system availability). Calculated as:

ReorderLevel – expected demand during the expected lead time

IPOSKUHist The SKU-level historical demand quantity (history) taken from SKUHist:Qty for the time bucket set in SKUHist table, that is, from SKUHist:StartDate to SKUHist:Dur.

Note: When you view this column using JDA Fulfillment Plan Analysis page, the value displayed depends on the calendar you select in the Plan Analysis page.

IPOSKUHistFcst The SKU-level historical forecast data taken from SKUHistFcst:Qty for the time bucket set in SKUHistFcst table, that is, from SKUHistFcst:StartDate to SKUHistFcst:Dur.

Note: When you view this column using JDA Fulfillment Plan Analysis page, the value displayed depends on the calendar you select in the Plan Analysis page.

Item The item associated with the SKU whose projections appear in this row.

Loc The location associated with the SKU whose projections appear in this row.

MetIndDmd For a SKU, Met Independent Demand is the total number of independent demands (CustOrders and FcstOrders) met on time.

MetSSLevel For a SKU, Met Safety Stock Level is the total number of safety stock orders met on time.

MktActvtyCustOrders Forecasted customer order whose FcstType is ‘market activity’.

MktActvtyFcst Forecast of type ‘market activity’, allocated by time and not by the allocation calendar.

MPConstProjAvail Master Planning Constrained Projected Available is the MPConstProjAvail can be expressed as:

(SupplyTot - DepDmd - InTransitOutTot - PlanShipTot - MPMetIndDmd - SS)

NetProfit Note: This column is not used in the current release.

NetReqts Note: This column is not used in the current release.

NonBaseFcst Forecast from the DFUToSKUFcst table where DFUToSKUFcst:Type is not equal to 1 and the forecast is allocated by time, not by an allocation calendar.

NonBaseHist Note: This column is not used in the current release.

NonFcstCustOrders


SKUProjStatic

Nonforecasted Customer Orders are the Customer orders that were not part of the forecast. The system does not use these orders to adjust the forecast.

NonFcstCustOrders is the sum of all orders where:


• CustOrder:FcstSw = No

• CustOrder:Reservation = 0 or CustOrder:ResExp is later than the OHPost date.

The system derives the value in this column from the CustOrder table.

NonSupsdAdjAllocTotalFcst Non-Supersedable Adjusted Allocated Total Forecast is the portion of demand specified in SKU projection AllocTotFcst (on page 396) that cannot be superseded by an alternate supply.

NonSupsdAdjFcstCustOrders Non-Supersedable Adjusted Forecasted Customer Orders is the portion of demand specified in SKU projection AdjFcstCustOrders (on page 395)that cannot be superseded by an alternate supply.

NonSupsdAllocBaseFcst Non-Supersedable Allocated Base Forecast is the portion of demand specified in SKU projection AllocBaseFcst (on page 396) that cannot be superseded by an alternate supply.

NonSupsdAllocNonBaseFcst Non-Supersedable Allocated Non-Base Forecast is the portion of demand specified in SKU projection AllocNonBaseFcst (on page 396) that cannot be superseded by an alternate supply.

NonSupsdAllocTotFcst Non-Supersedable Allocated Total Forecast is the portion of demand specified in SKU projection ProratedAllocTotFcst (on page 414) that cannot be superseded by an alternate supply.

NonSupsdBaseFcst Non-Supersedable Base Forecast is the portion of demand specified in SKU projection BaseFcst (on page 399) that cannot be superseded by an alternate supply.

NonSupsdDepDmd Non-Supersedable Dependent Demand is the portion of demand specified in SKU projection DepDmd (on page 405) that cannot be superseded by an alternate supply.

NonSupsdDFUToSKUFcst Non-Supersedable DFU To SKU Forecast is the portion of demand specified in SKU projection DFUToSKUFcst (on page 406) that cannot be superseded by an alternate supply.

NonSupsdFcstCustOrders Non-Supersedable Forecasted Customer Orders is the portion of demand specified in SKU projection FcstCustOrders (on page 406) that cannot be superseded by an alternate supply.

NonSupsdFirmPlanArriv Non-Supersedable Firm Planned Arrivals is the portion of demand specified in SKU projection FirmPlanArriv (on page 406) that cannot be superseded by an alternate supply.

NonSupsdFirmPlanOrder Non-Supersedable Firm Planned Orders is the portion of demand specified in SKU projection FirmPlanOrder (on page 406) that cannot be superseded by an alternate supply.

NonSupsdFirmPlanShip Non-Supersedable Firm Planned Shipments is the portion of demand specified in SKU projection FirmPlanShip (on page 406) that cannot be superseded by an alternate supply.


SKUProjStatic

NonSupsdNonBaseFcst Non-Supersedable Non-Base Forecast is the portion of demand specified in SKU projection NonBaseFcst (on page 410) that cannot be superseded by an alternate supply.

NonSupsdNonFcstCustOrders Non-Supersedable Non-Forecasted Customer Orders is the portion of demand specified in SKU projection NonFcstCustOrders (on page 410) that cannot be superseded by an alternate supply.

NonSupsdPlanArriv Non-Supersedable Planned Arrival is the portion of demand specified in SKU projection PlanArriv (on page 412) that cannot be superseded by an alternate supply.

NonSupsdPlanOrders Non-Supersedable Planned Orders is the portion of demand specified in SKU projection PlanOrders (on page 412) that cannot be superseded by an alternate supply.

NonSupsdPlanShip Non-Supersedable Planned Shipment is the portion of demand specified in SKU projection PlanShip (on page 413) that cannot be superseded by an alternate supply.

NonSupsdRecArriv Non-Supersedable Planned Arrival is the portion of demand specified in SKU projection RecArriv (on page 416) that cannot be superseded by an alternate supply.

NonSupsdRecShip Non-Supersedable Recommended Shipment is the portion of demand specified in SKU projection RecShip (on page 416) that cannot be superseded by an alternate supply.

NonSupsdTotDmd Non-Supersedable Total Demand is the portion of demand specified in SKU projection AllDmd (on page 395) that cannot be superseded by an alternate supply.

OptionSet The name of the option set used when running the Store SKU Projections process.

Note: When viewing data in this table, you must always include OptionSet to prevent double-counting of data from multiple options sets.



OvrideCustOrders Forecasted customer order whose FcstType is ‘override’.

OvrideFcst Forecast of type ‘override’, allocated by time and not by the allocation calendar.

PlanArriv The total amount of planned arrivals for this destination SKU for this period. The system calculates this value based on the values in the PlanArriv table for rows whose destination is this SKU and whose value in PlanArriv:FirmPlanSw is No.

PlanIntransIn The total inbound intransits considered by the planning logic as supply for this SKU. This is the sum of SKU projection TotIntransIn (inbound intransits of this SKU used to meet the demand of this SKU) and SKU projection SubIntransIn (inbound intransits of substitute SKUs used to meet the demand of this SKU).

PlanOrders JDA Enterprise Supply Planning Reference Guide 412 © 2014 JDA Software Group, Inc.- Confidential

SKUProjStatic

The sum of all PlanOrder:Qty (on page 208) for this SKU whose PlanOrder:SchedDate (on page 209) falls within this time period and whose value in PlanOrder:FirmPlanSw (on page 207) is No and PlanOrder:CoProdOrderType (on page 206) is Primary Planned Order.

Note: The column CoProdOrderType is used by MP only.

PlanProjAvail The planned projected available as of SKU projection Date. The system calculates PlanProjAvail as PlanProjOH minus SS.

PlanProjOH The planned projected on hand as of SKU projection Date. The system calculates PlanProjOH as:

TotSupply - TotDmd - DisplayQty + ProxySupply - ProxyDemand - UnusedOH + FirmRecSubInventory + SubIntransIn.

PlanPurch The sum of all PlanPurchases:Qtys for this SKU whose PlanPurch:SchedDate falls within this time period and whose value in PlanPurch:FirmPlanSw is No.

PlanPurchFirm The total quantity of firm planned purchases.

PlanShip The total amount of planned shipments from this source SKU for this period. The Calculate Plan process generates and publish the results of these shipments in PlanArriv and PlanShip tables. PlanShip is the sum of DetailedPlanShip and ConsolidatedPlanShip.

PresentationQty This value is read from SSPresentation:PresentationQty and serves as a time-phased minimum SS requirement. For more information, see SSPresentation:PresentationQty.

ProcessDate The date and time when the Store SKU Projections process was run.

ProdRequirement The sum of all ProdRequirement:Qty for this SKU, whose ProdRequirement:SchedDate falls within this time period and ProdRequirement:CoProdOrderType is the primary production requirement.

ProjAvail The projected available as of SKU projection Date. The system calculates ProjAvail as:

(projected on hand - SS – HoldOutQty - DisplayQty) as of Date.

ProjAvailEarliestNeed The calculation of projected available as of the earliest need date (rather than actual scheduled date of the component).

ProjOH The projected on hand as of SKU projection Date. At the date of the last stock posting—SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank)—the value of ProjOH is the value of SKU:OH.

If the page’s Allocation Period Date is Begin, the system calculates ProjOH (using SKU projection values from the previous time interval) as:

(ProjOH + SchedRcpts + FirmPlanOrders + Inventory + PlanOrders + TotArriv + TotIntransIn + RecAllocArriv ) - TotDmd

If the Allocation Period Date is End, the system uses ProjOH from the previous interval and all other values from the current interval.


SKUProjStatic

ProjOH always includes Inventory:OH regardless of whether the SKU is date-sensitive (DSI) or non-DSI. If the SKU is date-sensitive, SKU:OH is not used because it has no expiration associated with it. Therefore, non-DSI SKUProjStatic:ProjOH is calculated as:

Inventory:OH + SKU:OH + SchedRcpts + PlanOrders + RecAllocArriv + TotArriv + TotIntransIn - TotDmd

On the other hand, date-sensitive ProjOH is calculated as:

Inventory:OH + SchedRcpts + PlanOrders + RecAllocArriv + TotArriv + TotIntransIn - TotDmd

ProjOHEarliestNeed The calculation of projected on hand as of the earliest need date (rather than the actual scheduled date of the component).

ProjOrderOptTotDmd The projected total demand is a projection of the total demand used by the Project Optimized Order process. These demands include forecast, customer orders, and firm and planned shipments.

ProjOrderOptIntransOut The projected in transit out is a projection of the vehicle load information that is scheduled to leave a location. For example, if the destination is a DC, the ProjOrderOptIntransOut represents the demand that is set to ship to stores on vehicle loads. This value is also included in the total demand.

ProjOrderOptSOQ The projected SOQ is a projection of the SOQ created by the Project Optimized Order process. This SOQ represents future orders that are expected to be placed based on the due order logic within Order Optimization.

ProjOrderOptIntransIn The projected in transit in is a projection of the orders that have been approved and are going to be received at a destination. This value does not include orders created by the Optimize Order process until those order have been approved.

ProjOrderOptTotSupply The projected total supply is a supply available to a SKU during a given time period. The supplies include on hand, firm orders, and future SOQs.

ProjOrderOptProjOH The projected on hand calculated as of the SKU projection date. This projected on hand is based on the inputs from the Project Optimized Order process.

ProjOrderOptProjAvail The projected available supply it the projected on hand less safety stock, holdout quantity and display quantity. This value is based on the ProjOrderOptSOQ that is calculated in the Project Optimized Order process.

ProAllocBaseFcst Prorated Allocated Base Forecast is the allocated base forecast for this period, based on the profile defined by the allocation calendar after being prorated.

ProratedAllocTotFcst If SKUDemandParam:ProrateSw is set to Y, Forecast in this column reflect the forecast prorated by DmdToDate. To prorate the forecast, the system:

Subtracts the value in SKUDemandParam:DmdToDate from the forecasted demand (the portion of the allocated forecast that occurs between the beginning of the proration period and OHPost)

Adds the result to the allocated forecast from OHPost through the end of the proration period


SKUProjStatic

Spreads this quantity based on the Allocation Weight (CalData:AllocWgt) defined for the SKU’s Allocation Calendar (SKUDemandParam:AllocCal).

Refer to SKUDemandParam:DmdToDate, SKUDemandParam:ProrateSw, and SKUDemandParam:ProrationDur for more information on forecast proration.

ProxyDemand Demand placed on the SKU defined in this row by other SKUs (items) that participate in a supersession relationship with this SKU. The system reads these values from the PlanProxyInventory table. This value is computed by Plan portion of Calculate Plan.

ProxyIntransIn Total quantity of inbound intransits of this SKU that are used to meet the demand of other SKUs.

ProxyIntransOut Total quantity of outbound intransits of this SKU that are used to meet the demand of other SKUs.

ProxyInventory This column is not used in this release.

ProxyRecArriv Proxy Recommended Arrivals is the total quantity of recommended arrivals of this SKU that are used to cover the demand of other SKUs. A proxy recommended arrival is one in which this SKU is used as a proxy—that is, it is “standing in” to meet the demand of a different item. This column allows you to track the results of substitution logic in Fulfillment/Deployment.

Compare this column to SKU projection RecArriv, which shows the total quantity of recommended arrivals of this SKU that are used to cover the demand of this SKU.

ProxyRecShip Proxy Recommended Shipments is the total quantity of recommended shipments of this SKU that are used to cover the demand of other SKUs. A proxy recommended shipment is a shipment in which this SKU is used as a proxy—that is, it is “standing in” to cover the demand of a different SKU. Proxy recommended shipments are created by substitution logic in Fulfillment/Deployment.

Compare this column to SKU projection RecShip, which shows the total quantity of recommended shipments of this SKU that are used to cover the demand of this SKU (created by normal Fulfillment/Deployment logic).

For more information on standard and proxy recommended shipments, refer to the Item and PrimaryItem columns in the RecShip table.

ProxySupply Supply of other SKUs in a supersession relationship with this SKU that is being used to meet the demand of this SKU. The system reads these values from the PlanProxyInventory table. This value is computed by the Plan portion of Calculate Plan.

PSOLoad Plan Supply Order Load is the total plan supply order load for a SKU as computed by the Plan Resource Requirements process.

PurchOrder The sum of all PurchOrder:Qtys for this SKU whose PurchOrder:DueDate falls within this time period and whose value in PurchOrder:FirmSw is No.

PurchRequirement The sum of all PurchRequirement:Qty for this SKU, whose PurchRequirement:SchedDate falls within this time period.

RecAllocArriv JDA Enterprise Supply Planning Reference Guide 415 © 2014 JDA Software Group, Inc.- Confidential

SKUProjStatic

Recommended Allocation Arrivals is the total quantity of recommended arrivals of this SKU that are being used to meet the demand of this SKU. The value in this column is generated by normal planning logic.

RecAllocShip Recommended Allocation Shipments is the total quantity of recommended shipments of this item that are being used to meet the demand for this item. The value in this column is generated by normal planning logic.

RecArriv Recommended Arrivals is the total quantity of recommended arrivals of this SKU that are being used to meet the demand of this SKU. The value in this column is generated by normal planning logic.

Compare this column to the values in SKU projections ProxyRecArriv and SupsdRecArriv, which both contain recommended arrivals generated by supersession logic.

ReconcileCustOrders Forecasted customer order whose FcstType is ‘reconcile’.

ReconcileFcst Forecast of type ‘reconcile’, allocated by time and not by the allocation calendar.

RecShip Recommended Shipments is the total quantity of recommended shipments of this item that are being used to meet the demand for this item. The value in this column is generated by normal planning logic.

Compare this column to the values in SKU projection ProxyRecShip, SupsdRecShip and SubRecShip, which both contain recommended shipments generated by supersession or substitution logic.

RequiredProjAvail The projected available as on the SKU projection date. RequiredProjAvail is calculated as RequiredProjOH – SS, as on the date.

RequiredProjOH The projected on-hand as on the SKU projection date. On the last stock posting date (SKU:OHPost; or Loc:OHPost, if SKU:OHPost is blank), RequiredProjOH is the same as SKU:OH.

If you select the End option for Allocation Period Date, the system uses RequiredProjOH from the previous interval and all other values from the current interval.

RequiredProjOH always includes Inventory:OH, regardless of whether the SKU is date-sensitive (DSI) or not. If the SKU is DSI, SKU:OH is not used because it has no expiration. Therefore, non-DSI SKUProjStatic:RequiredProjOH is calculated as TotSupplyRequirement – TotDmdRequirement, while DSI ProjOH is calculated as TotSupplyRequirement – TotDmdRequirement – UnusedRequiredOH.

SchedExpiredRequiredOH The inventory originally scheduled for the SKU, displayed on the date it expires, if none of it is used.

SchedExpOH Scheduled Expired On-Hand is the entire inventory originally scheduled for the SKU, displayed on the date that it would expire if none of it were used.

SchedRcpts Scheduled Receipts is the total of all SchedRcpts:Qtys for scheduled receipts for this SKU.

SchedSupplyExceptionCount The count of exceptions that are generated for scheduled supplies (FirmPlanOrders, FirmPlanArrivs, FirmPlanPurchs, SchedRcpts, and VehicleLoadLines).



SKUProjStatic

Scheduled Supply Exception Quantity is the total number of scheduled supplies (FirmPlanOrders, FirmPlanArrivs, FirmPlanPurchs, SchedRcpts, and VehicleLoadLines) exceptions that are generated.

SchedUnusedRequiredOH The inventory originally scheduled for the SKU, displayed on the date when its effective shelf life ends, if none of it is used.

Note: The effective shelf life of an item is the difference between SKUPerishableParam:ShelfLifeDur and SKUPerishableParam:MinShelfLifeDur.

SchedUnuseOH Scheduled Unusable On-Hand is the entire inventory originally scheduled for the SKU, displayed on the date that its effective shelf life would end if none of it were used. (The effective shelf life is the difference between the SKUPerishableParam:ShelfLifeDur and the SKUPerishableParam:MinShelfLifeDur of an item).

SeasonFactor Seasonality Factor is the value used to weight statistical safety stock by period. It is calculated at a DFU level and mapped to a particular SKU. Viewed in SKU projections, this value changes over time.

SKUExceptionCount SKU Exception Count is the number of generated SKU exceptions.

SKUExceptionQty SKU Exception Qty is the quantity of SKU exceptions generated for a SKU.

SKUExternalFcst SKU External Forecast is the forecast from the SKUExternalFcst table, allocated by time, not by an allocation calendar.

SKUResExceptionCount SKU Resource Exception Count is the number of generated resource exceptions.

SKUResExceptionQty For a SKU, SKU Resource Exception Quantity is the quantity of resource exceptions generated.

Sources Note: This column is not used in the current release.

SS Safety Stock is included with, but not used by, Master Planning.

The target safety stock level as of SKU projection Date. The system calculates the value in this column in accordance with the Safety Stock Rule (SKUSafetyStockParam:SSRule).

SSInventory Safety Stock Inventory is the scheduled quantity at the available date.

SSMetEarlyCount Safety Stock Met Early Count is the number of stock orders met before the need date.

SSMetLateCount Safety Stock Met Late Count is the number of stock orders met after the need date.

SSMetOntimeCount Safety Stock Met Ontime Count is the number of stock orders met by the need date.

SSMetPartialCount Safety Stock Met Partial Count is the number of stock orders met partially.


SKUProjStatic

SSNeedUnit Safety Stock Need Unit is the number of units based on the need date and the need quantity.

SSSchedUnit Safety Stock Scheduled Unit is the number of units based on the scheduled date and the scheduled quantity.

SSUnmetCount Safety Stock Unmet Count is the number of unmet stock orders.

SSUnplannedCount Safety Stock Unplanned Count is the number of unplanned stock orders.

StandardCost Note: This column is not used in the current release.


StatSS Statistical Safety Stock stores the value of the time-phased, seasonally adjusted statistical safety stock.

StockLowCost Note: This column is not used in the current release.

StockOutCost Note: Field is not used in this release.

SubConstrProjAvail This column is not used in this release.

SubConstrProjOH This column is not used in this release.

SubIntransIn Substitute Intransits In is the total quantity of inbound intransits of other (substitute) items that are being used to meet the demand of this SKU.

SubInventory This column is not used in this release.

SubRecArriv This column is not used in this release.

SubRecShip This column is not used in this release.

SuppOrderPlanShip Supplemental Order Plan Ship Quantity is the total of PlanArriv:SuppOrderQty values for all (non-firm) planned arrivals in this period for which this SKU is the source SKU.

SuppOrderQty Supplemental Order Quantity is the total quantity of all supplemental orders defined on this SKU by records in the SuppOrderSKU table where Type = 1. The SuppOrderSKU:NeedQty is displayed in this column based on the NeedArrivDate of the supplemental order. If a holdout is defined for the supplemental order, then the holdout is displayed in the SKUProjStatic:HoldoutQty.

SupsdAdjAllocTotalFcst


SKUProjStatic

Supersedable Adjusted Allocated Total Forecast is the portion of demand specified in SKU projection AllocTotFcst (on page 396) that can be superseded by an alternate supply.

SupsdAdjFcstCustOrders Supersedable Adjusted Forecasted Customer Orders is the portion of demand specified in SKU projection AdjFcstCustOrders (on page 395)that can be superseded by an alternate supply.

SupsdAllocBaseFcst Supersedable Allocated Base Forecast is the portion of demand specified in SKU projection AllocBaseFcst (on page 396) that can be superseded by an alternate supply.

SupsdAllocNonBaseFcst Supersedable Allocated Non-Base Forecast is the portion of demand specified in SKU projection AllocNonBaseFcst (on page 396) that can be superseded by an alternate supply.

SupsdAllocTotFcst Supersedable Allocated Total Forecast is the portion of demand specified in SKU projection ProratedAllocTotFcst (on page 414) that can be superseded by an alternate supply.

SupsdBaseFcst Supersedable Base Forecast is the portion of demand specified in SKU projection BaseFcst (on page 399) that can be superseded by an alternate supply.

SupsdConstrProjAvail Superseded Constrained Projected Available is the effective projected ConstrProjAvail for the SKU taking into account any substitutions that are calculated by supersession.

The system calculates SupsdConstrProjAvail as:

SupsdConstrProjOH – (SS + HoldoutQty) as of Date.

SupsdConstrProjOH Superseded Constrained Projected OH is the effective projected ConstrProjOH for the SKU taking into account any substitutions that are calculated by supersession.

The system calculates SupsdConstrProjOH as:

ConstrProjOH + ConstrProxySupply + ProxyRecArriv + SupsdRecShip – ConstrProxyDemand – ProxyRecShip.

SupsdDepDmd Supersedable Dependent Demand is the portion of demand specified in SKU projection DepDmd (on page 405) that can be superseded by an alternate supply.

SupsdDFUToSKUFcst Supersedable DFU to SKU Forecast is the portion of demand specified in SKU projection DFUToSKUFcst (on page 406) that can be superseded by an alternate supply.

SupsdFcstCustOrders Supersedable Forecasted Customer Orders is the portion of demand specified in SKU projection FcstCustOrders (on page 406) that can be superseded by an alternate supply.

SupsdFirmPlanArriv Supersedable Firm Planned Arrivals is the portion of demand specified in SKU projection FirmPlanArriv (on page 406) that can be superseded by an alternate supply.

SupsdFirmPlanOrder Supersedable Firm Planned Orders is the portion of demand specified in SKU projection FirmPlanOrder (on page 406) that can be superseded by an alternate supply.


SKUProjStatic

SupsdFirmPlanShip Supersedable Firm Planned Shipments is the portion of demand specified in SKU projection FirmPlanShip (on page 406) that can be superseded by an alternate supply.

SupsdNonBaseFcst Supersedable Non-Base Forecast is the portion of demand specified in SKU projection NonBaseFcst (on page 410) that can be superseded by an alternate supply.

SupsdNonFcstCustOrders Supersedable Non-Forecasted Customer Orders is the portion of demand specified in SKU projection NonFcstCustOrders (on page 410) that can be superseded by an alternate supply.

SupsdPlanArriv Supersedable Planned Arrivals is the portion of demand specified in SKU projection PlanArriv (on page 412) that can be superseded by an alternate supply.

SupsdPlanOrders Supersedable Planned Orders is the portion of demand specified in SKU projection PlanOrders (on page 412) that can be superseded by an alternate supply.

SupsdPlanShip Supersedable Planned Shipments is the portion of demand specified in SKU projection PlanShip (on page 413) that can be superseded by an alternate supply.

SupsdProjAvail Supersedable Projected Available is the effective projected ProjAvail for the SKU taking into account any substitutions that are calculated by supersession. The system calculates this column as SupsdProjOH (on page 420) - SS.

SupsdProjOH Supersedable Projected On Hand is the effective projected ProjOH for the SKU taking into account any substitutions that are calculated by supersession.

The system calculates SupsdProjOH as:

ProjOH + ProxySupply - ProxyDemand + SubIntransIn

SupsdRecArriv Substitute Recommended Arrivals is the total quantity of recommended arrivals generated by Supersession logic in which other (alternate) items are being used to meet the demand of this SKU and where RecShip:Type = 4.

Compare this column to SKU projection RecArriv, which shows the recommended arrivals generated by normal planning logic in which an item is being used to meet its own demand.

SupsdRecShip Substitute Recommended Shipments is the total quantity of recommended shipments generated by supersession logic in which other (alternate) items are being used to meet the demand of this SKU and where RecShip:Type = 4.

Compare this column to SKU projection RecShip, which shows the recommended shipments generated by normal planning logic in which an item is being used to meet its own demand.

SupsdTotDmd Supersedable Total Demand is the portion of demand specified in SKU projection AllDmd (on page 395) that can be superseded by an alternate supply.

TargetNetworkInv See AggSKUProjStatic:TargetNetworkInv (on page 44).


SKUProjStatic

TargtlmpactBaseFcst Forecast of type ‘target impact base’, allocated by time and not by the allocation calendar.

TargtlmpactCustOrders Forecasted customer order whose FcstType is ‘target impact’.

TotalCost Note: This column is not used in the current release.

TotalLoad The total supply order load for a SKU as computed by the Plan Resource Requirements process.

TotalLockCustOrders Forecasted customer orders whose FcstType is‘total forcast lock’.

TotalLockFcst Forecast of type ‘total forecast lock’, allocated by time and not by the allocation calendar.

TotArriv Sum of SKU projections PlanArriv and FirmPlanArriv.

TotContribMargin Note: This column is not used in the current release.

TotDmd The sum of aggregation of all demand types (AdjAllocTotFcst, DepDmd, TotShip, TotIntransOut, AdjFcstCustOrders, NonFcstCustOrders, RecAllocShip, and Backorders) less ignored demand (SKU projection IgnoredDmd) for the time period. The system derives TotDmd from the BOM, Cal, CalData, CustOrder, DFUToSKUFcst, Fcst, VehicleLoad, VehicleLoadLine, RecAllocShip, and PlanArriv tables.

TotDmdRequirement The sum of all demand types (AdjAllocTotFcst, DepDmdRequirement, TotShip, TotIntransOut, AdjFcstCustOrders, NonFcstCustOrders, and Backorders) – ignored demand (SKU projection IgnoredDmd) for this time period.

TotDmdRequirement is calculated from the BOM, Cal, CalData, CustOrder, DFUToSKUFcst, Fcst, VehicleLoad, VehicleLoadLine, and PlanArriv tables as DepDmdRequirement + TotIntransitOut + FirmPlanShip + DistShipRequirement + PlanShipConsolidated + AdjFcstCustOrders + AdjAllocTotFcst + NonFcstCustOrders.

TotDmdSatisfied Note: This column is not used in the current release.

TotFcst Total independent demand for this period—that is, statistical forecast plus DFU forecast adjustments. TotFcst is allocated only by time, not by the Allocation Calendar.

TotFcst can be derived from the sum of BaseFcst and NonBaseFcst.

TotHist Note: This column is not used in the current release.

TotIntransIn Total Intransits In is the total quantity of inbound intransits of this item that are being used to meet the demand of this item. This column is the sum of SKU projections CommitIntransIn and ActualIntransIn.

TotIntransOut Total Intransits Out is the total quantity of outbound intransits of this item. This column is the sum of the quantity of outbound intransits of this item that are used to meet the demand of this item (sum of CommitIntransOut and ActualIntransOut). JDA Enterprise Supply Planning Reference Guide 421 © 2014 JDA Software Group, Inc.- Confidential

SKUProjStatic

TotLockCustOrders Forecasted customer order whose FcstType is ‘total forecast lock’.

TotLockFcst Forecast of type ‘total forecast lock’, allocated by time and not by the allocation calendar.

TotRecArriv Total Recommended Arrivals is the total of all recommended arrivals of this SKU. This is the sum of:

• SKU projection RecArriv (recommended arrivals of this SKU to meet its own demand).

• SKU projection RecAllocArriv (recommended arrivals generated by Dynamic Allocation for this SKU to meet its own demand).

• SKU projection ProxyRecArriv (recommended arrivals of this SKU to meet the demand of other items).

TotRecShip Total Recommended Shipments is the total of all recommended shipments of this SKU. This is the sum of:

• SKU projection RecShip (recommended shipments of this SKU to meet its own demand).

• SKU projection RecAllocShip (recommended shipments generated by Dynamic Allocation for this SKU to meet its own demand).

• SKU projection ProxyRecShip (recommended shipments of this SKU to meet the demand of other items).

TotShip Sum of SKU projections DetailedPlanShip, ConsolidatedPlanShip and FirmPlanShip.

TotSupply Total supply for the SKU in the time period. Total supply consists of on-hand inventory, scheduled receipts, intransit stock, frozen assignments, all planned orders, and all planned arrivals. The system calculates TotSupply from the following SKU projection columns:

Inventory + SchedRcpts + PlanOrders + FirmPlanOrder + CoProductPlanOrders + TotArriv + RecAllocArriv + TotIntransIn

Note: In aggregation mode, when both the source and destination are selected in the search, the vehicle load quantities with SourceStatus 3 is added to TotSupply and ConstrTotSupply on the ShipDate rather than the ArrivDate.

TotSupplyRequirement The total supply requirement for the SKU for this time period, which consists of on-hand inventory, scheduled receipts, in-transit stock, frozen assignments, and all production and distribution requirements.

TotSupplyRequirement is calculated from SKU projection columns as Inventory + SchedRcpts + ProdRequirement + FirmPlanOrder + CoProductProdReqt + TotIntransIn + PurchOrder + FirmPlanPurch + PurchRequirement + DistRequirement + FirmPlanArriv.

TotTransCost Note: This column is not used in the current release.

TotUseRecArriv Total Used Recommended Arrivals is the total recommended arrivals of all items used to meet demand for this SKU when SKU Substitution is being used. This is the sum of:

• SKU projection RecArriv (recommended arrivals in which this SKU is meeting its own demand)


SKUProjStatic

• SKU projection RecAllocArriv (recommended arrivals generated by Dynamic Allocation in which this SKU is meeting its own demand)

• SKU projection SubRecArriv (recommended arrivals in which substitute SKUs are meeting the demand for this SKU)

TotUseRecShip Total Used Recommended Shipments is the total recommended shipments of all items used to meet demand for this SKU when SKU Substitution is being used. This is the sum of:

• SKU projection RecShip (recommended shipments in which this SKU is meeting its own demand)

• SKU projection RecAllocShip (recommended shipments generated by Dynamic Allocation in which this SKU is meeting its own demand)

• SKU projection SubRecShip (recommended shipments in which substitute SKUs are meeting the demand for this SKU)

UnconActualReq Unconstrained Actual Requirement is the sum of imported work order dependent demand for the SKU whose need date falls within the display bucket.

UnconCancel Unconstrained Cancel is the sum of all supplies for which “Cancel” has been recommended, where the due date (PlanDate) of supplies falls within the display bucket.

UnconCustOrder Unconstrained Customer Order is the sum of Customer Order Demand for the SKU whose need date falls within the display bucket.

UnconDependantDmd Unconstrained Dependent Demand is the sum of all the Exploded Demand, Inter Site Demand of Action Type “New” and Work Order Dependent Demand of Action Type “New” where the need date falls within the display bucket.

UnconExtraUsage Unconstrained Extra Usage is the sum of Extra Usage demand for the SKU whose need date falls within the display bucket.

UnconIntersiteDmd Unconstrained Inter Site Demand is the sum of Imported Inter Site Demand for the SKU whose need date falls within the display bucket.

UnconIntersiteOrder Unconstrained Inter Site Order is the sum of Inter Site Order supply type whose due date falls within the display bucket.

UnconInventory Unconstrained Inventory is the sum of available inventory on-hand.

UnconMasterSched Unconstrained Master Schedule Demand is the sum of Master Schedule Demand for the SKU whose need date falls within the display bucket.

UnconNetAvailable The Unconstrained Net Available is a calculated field. It takes the previous bucket’s closing balance, adds the supplies for this bucket, subtracts the total demand for this bucket, and determines the net available. The net available for this bucket becomes equal to its closing balance and is used as an opening balance for the next bucket. For the first bucket at plan start, the opening balance is the inventory plus any supplies coming in before the first bucket minus any past due demand.


SKUProjStatic

UnconNetDaysSupply If the net available is <= 0, then the unconstrained net days of supply is 0. If the net available is >0, then it lists the demands on that by date looking forward, decrements that until all the net available is used up. The difference in the date of the last demand met by this and the end of the bucket equals the days of supply.

UnconNetOnHand The unconstrained net on hand value, not considering the time varying safety stock and safety stock demands.

UnconNew Unconstrained New is the sum of all new supplies for which “New” has been recommended, where the plan date of supplies falls within the display bucket.

UnconNoAction Unconstrained No Action is the sum of all supplies for which “No Action” has been recommended, where the plan date of supplies falls within the display bucket.

UnconPlannedOrder Unconstrained Planned Order is the sum of all new supplies whose start date for ordering the supplies falls within the display bucket.

UnconPrjDaysSupply If the Projected available is <= 0, then the unconstrained projected days of supply is 0. If the Projected available is >0, then it lists the demands on that by date looking forward, decrements that until all the Projected available is used up. The difference in the date of the last demand met by this and the end of the bucket equals the days of supply.

UnconProjAvailable The unconstrained projected available value, considering the time varying safety stock and safety stock demands.

UnconProjOnHand The unconstrained projected on hand value, not considering the time varying safety stock and safety stock demands.

UnconPull Unconstrained Pull is the sum of all supplies for which “Pull” has been recommended, where the plan date of supplies falls within the display bucket.

UnconPurchaseOrder Unconstrained Purchase Order is the sum of Purchase Order supply type whose due date falls within the display bucket.

UnconPurchaseReq Unconstrained Purchase Requisition is the sum of Purchase Requisition supply type whose due date falls within the display bucket.

UnconPush Unconstrained Push is the sum of all supplies for which “Push” has been recommended, where the plan date of supplies falls within the display bucket.

UnconReschedInFrom Unconstrained Rescheduled In From is the sum of all the supplies for which "Pull" has been recommended where the due date of supplies falls within the display bucket.

UnconReschedOutFrom Unconstrained Rescheduled Out From is the sum of all the supplies for which "Push" has been recommended where the due date of supplies falls within the display bucket.


SKUProjStatic

UnconReschedSupply Unconstrained Rescheduled Supply is the sum of all Rescheduled Supplies (supplies with action type No Action, Push, Pull, Cancel, New, and Substitute Supply), where available date (PlanDate) of supplies falls within the display bucket.

UnconSafetyStock Unconstrained Safety Stock is the sum of Safety Stock demand for the SKU whose need date falls within the display bucket.

UnconSubstDmd Unconstrained Substitution Demand is the sum of Substitution Demand for the SKU whose need date falls within the display bucket.

UnconSubstSupply Unconstrained Substitution Supply is the sum of all supplies that are going to meet demand as a substitute component, where the available date (PlanDate) of supplies falls within the display bucket.

UnconTotalDemand The unconstrained Total Demand is the sum of customer orders, safety stock orders, transfer orders, extra usage orders, forecast orders, and work order dependent demands for the SKU whose NeedDate falls within the display bucket.

UnconTotalSupply Unconstrained Total Supply is the sum of Schedule Supplies (Purchase Order + Purchase Requisition + Work Orders + Inter Site Orders + Inventory). These are displayed based on due date of supplies.

UnconTVSS The unconstrained time varying safety stock level available.

UnconWorkOrder UnConWorkOrderis the sum of Work Order supply type whose due date falls within the display bucket.

UnusedRequiredOH The inventory that, based on supply and demand projections, expires before it is used. The inventory in this column is displayed on the date when its effective shelf life ends.

Note: The effective shelf life of an item is the difference between SKUPerishableParam:ShelfLifeDur and SKUPerishableParam:MinShelfLifeDur.

The quantities in the SKU projection columns UnusedRequiredOH and ExpiredRequiredOH always match, but are offset by MinShelfLifeDur, with UnusedRequiredOH displayed earlier than ExpiredRequiredOH.

UseableProjOH The Useable Projected Onhand shows the projected inventory excluding any supply that is projected to not be sold before its unuseable date, as shown in UnuseableSupply. This projection is significant for perishable SKUs only, and differs from ProjOH as follows. When ProjOH calculates the projected inventory, it subtracts out any unuseable supply on its unuseable date. UseableProjOH also excludes unuseable supplies, but it excludes those supplies starting on their available date, so that the unuseable portions of supply are never reflected in the projection at all. This projection is used in the calculation of CovDur for perishable items.

UnuseableSupply For a perishable SKU, Unuseable Supply shows the portions of supply that will become unuseable before it is sold, based on all total projected supplies and total projected demands. This projection of unuseable supply is shown on the supply available date. Note that sometimes there is ambiguity about which precise supply is unused, when there is an overall excess of supply within a subset of the planning duration. So the designation of a supply as UnusableSupply does not necessarily mean that this precise supply is projected to be wasted.


SKUProjStatic

UnuseOH Unusable On-Hand is the inventory that, based on supply and demand projections, will expire before it is used. The inventory in this column is displayed on the date that it becomes unusable, that is, when the effective shelf life ends. (The effective shelf life is the difference between the SKUPerishableParam:ShelfLifeDur and the SKUPerishableParam:MinShelfLifeDur of an item.)

The quantities in the SKU projection columns UnuseOH and ExpOH will always match, but will be offset by the MinShelfLifeDur, with the UnuseOH displaying earlier than the ExpOH.

UserFirmDepDmd Note: This column is not used in the current release.

UserFirmPlanArriv Note: This column is not used in the current release.

UserFirmPlanOrd Note: This column is not used in the current release.

UserFirmPlanShip Note: This column is not used in the current release.

UserID The identifier of the user who ran the Store SKU Projections process.

WOLoad The total work order load for a SKU as computed by the Plan Resource Requirements process.


SKUSafetyStockParam

SKUSafetyStockParam Table included with: Fulfillment, Inventory Policy Optimization, Master Planning, Flowcasting, Enterprise Supply Planning


AccumDur FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DURATION >=1 1D

AllowEarlyArrivSW

IPO INTEGER 0,1 1

AllowEarlyOrderSW

IPO INTEGER 0,1 1

ArrivalPostDate IPO DATETIME

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

TEXT ' '

AvgDmdLookBwdDur


DURATION 0

AvgDmdLookFwdDur


DURATION 365D

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

DURATION 0

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

INTEGER 0

CalcMSERule FF, MP, IPO, Flowcasting, ESP (Deep Tree)

OPTION_NUMBER

1,2,3,4,5,6 1

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

OPTION_NUMBER

1,2 1

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

OPTION_NUMBER

1,2,3 2

CSLTemplate FF UPPER_TEXT


SKUSafetyStockParam


DmdAllocCal FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT ' '

DmdCal FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT ' '

DmdCorrelationFactor

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

DECIMAL >0 1

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

OPTION_NUMBER

1,2,3 1

DmdPostDate FF, MP, IPO, Flowcasting, Flowcasting, ESP (Deep Tree)

DATETIME 01/01/2000

FcstDur FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DURATION 7D


TEXT

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

DURATION 0

Loc 2 FF, MP, IPO, ESP

TEXT

MaxSS IPO, FF, MP, Flowcasting, ESP (Deep Tree)

DECIMAL 999999999.0

MaxSSCovSkipDur

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

DURATION

MaxSSFactor IPO >=0 0

MfgLeadTimeRule


OPTION_NUMBER

1,2,3,4,5 1

MinSS IPO, FF, MP, Flowcasting, ESP (Deep Tree)

DECIMAL 0.0


SKUSafetyStockParam


MSEAbsToleranceLimit


INTEGER >=0 0

MSELag FF, MP, IPO, Flowcasting, ESP (Deep Tree)

INTEGER 0

MSEMaskMaxVal


FLOAT Ratio masking (> 1), Percentage masking (>0% and <=100%)

100

MSEMaskMinVal FF, MP, IPO, ESP (Deep Tree)

FLOAT Ratio masking (>= 0 and < 1), Percentage masking (>=0% and <100%)

0

MSEMaskOpt FF, MP, IPO, Flowcasting, ESP (Deep Tree)

INTEGER 0, 1, 2 0

MSEModelOpt IPO NUMBER 1 and 2 1

MSEPer FF, MP, IPO, Flowcasting, ESP (Deep Tree)

INTEGER 0

NetFcstMSESMConst


DECIMAL 0.0

NumReplenYr FF, MP, IPO, Flowcasting, ESP (Deep Tree)

INTEGER 12

OrderDataDur IPO DURATION >=0 0 OrderLag IPO INTEGER >=0 0 OrderPostDate IPO DATETIME ShipDataDur IPO DURATION >=0 0 ShipLag IPO INTEGER >=0 0 SSCov FF, MP,


DURATION 0


SKUSafetyStockParam


SSCovUseBaseOnlySw

FF, Flowcasting BOOLEAN 0

SSMeetEarlyDur


DURATION 0

SSPresentationOpt

FF, Flowcasting OPTION_NUMBER

1 and 2 1

SSPriority MP, ESP (Deep Tree)

INTEGER -1

SSRule FF, MP, Flowcasting, ESP

OPTION_NUMBER

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

1

SSTemplate FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT ' '

StatSSAdjOpt FF, MP, FlowcastingStatSSAdjOpt, ESP (Deep Tree)

OPTION_NUMBER

1,2,3 1

StatSSCovLimitDur


DURATION 0

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

DECIMAL 0.0

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

INTEGER 1

TOHRule Not used in this release

INTEGER 3

Table description Each row in this table lists the parameters that define the way that the safety stock is calculated for an SKU.

Master Planning

Note: SKUSafetyStockParam is a required Master Planning table.


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

Column descriptions AccumDur JDA Enterprise Supply Planning Reference Guide 430 © 2014 JDA Software Group, Inc.- Confidential

SKUSafetyStockParam

Accumulation Duration (AccumDur) specifies the duration for which the forecasted plan is frozen. The default is 1440 minutes.

Note: Fulfillment and Master Planning does not use this column.

AllowEarlyArrivSW Switch to allow early arrivals.

• 1 - Consider early arrivals

• 0 - Not consider early arrivals

AllowEarlyOrderSW Switch to allow early orders.

• 1 - Consider early orders received

• 0 - Not consider early order received

ArrivalPostDate The date on which all the arrival data is posted at the destination.

AvgDmdCal Average Demand Calendar (AvgDmdCal) specifies the name of a valid Type 3 (Reporting) calendar in the Cal table. If this column specifies the name of a valid calendar, time-phased values of average demand are computed by the Average Demand option of the Calculate Statistical Safety Stock process according to the time buckets specified by this calendar. If this column does not specify any calendar, time-phased values are not computed for average demand. Instead, a single value is used for the entire planning horizon.

AvgDmdLookBwdDur Average Demand Look Backward Duration (AvgDmdLookBwdDur) specifies the look-backward window of time to be used for average demand calculations. For details about how this look backward window is used, refer to Working with statistical safety stock based on customer service in the Inventory Management in JDA Fulfillment section of the JDA Fulfillment OnLine Expert.

AvgDmdLookFwdDur Average Demand Look Forward Duration ((AvgDmdLookFwdDur) specifies the look-ahead window of time to be used for average demand calculations. For details about how this look ahead window is used, refer to Working with statistical safety stock based on customer service in the Inventory Management in JDA Fulfillment section of the JDA Fulfillment OnLine Expert.

AvgLeadTime A user input column specifying the average replenishment lead time used in the Calculate Statistical Safety Stock process for calculating demand variance (DmdVar:Initial value: 0.000000) for this SKU.

AvgNumLines Average Number of Lines (AvgNumLines) is the average number of lines per customer order. A line represents a request for some quantity of a SKU. If you calculate statistical safety stock using the combination of CSLMetric (on page 433) = 3 (Order Fill) and DmdDistType (on page 433) = 1 (Normal), the value in this column is used to calculate the safety stock needed to fill a percentage of customer orders during a planning period.

CalcMSERule Calculate Mean Squared Error Rule (CalcMseRule) specifies whether and how the SKU MSE option on the Calculate Statistical Safety Stock process will calculate the mean squared error (MSE) for the associated SKU.

• 1: User-defined

The Calculate Statistical Safety Stock process does not compute MSE. Instead, the system assumes that the user will import MSEs for these SKUs.


SKUSafetyStockParam

• 2: Map DFUs MSE

The Calculate Statistical Safety Stock process computes MSE for this SKU by mapping MSE from associated DFUs.

• 3: Compute lagged MSE

Using history data as well as historical forecast data retrieved from the SKUHist and SKUHistFcst tables, the Calculate Statistical Safety Stock process gives an approximation of error in the forecasted demand as compared to the actual demand data based on the lag specified in SKUSafetyStockParam:MSELag (on page 435).

• 4: Compute centralized MSE

MSE is computed at a central location (for example, at the distribution center, rather than at individual stores).

• 5: Compute aggregate MSE

MSE is calculated taking into account the correlation between demand at different locations in the network.

• 6: Compute BOM Component MSE

MSE is calculated for BOM components by considering the variability of its independent demand and the parent item

Note: This rule (6: Compute BOM Component MSE) is only used by JDA Inventory Policy Optimization.

Following table lits a matrix that recommends the application of various rules at various echelon levels.

Note: It is assumed that actual and forecast demand values are populated at the lowest echelon, level 0. Masking is applied to all SKUs which have Rules 3 and 4 applied.

Rule applied at Echelon level 0

Rule applied at Echelon level 1

Rule applied at Echelon level 2 and above

1 1 1 1 1 5 1 5 5 3 4 4 3 4 5 3 5 5 For details about how the CalcMSERule column is used, refer to Working with statistical safety stock based on customer service in the Inventory Management in JDA Fulfillment section of the JDA Fulfillment OnLine Expert.

CalcStatSSRule Calculate Statistical Safety Stock Rule (CalcStatSSRule) determines how statistical safety stock quantities will be computed:

• 1: Compute quantities

Statistical safety stock quantities are populated in the StatSS table.

• 2; Compute coverage durations

A coverage duration corresponding to the statistical safety stock quantities computed by the Statistical Safety Stock process are populated in the SKUSafetyStockParam:SSCov column of the associated SKU.


SKUSafetyStockParam

Note: CalcStatSSRule = 2 does not work for cases where time varying statistical safety stock is being computed. In other words, if either the AvgDmd or MSE is time-phased for the SKU, CalcStatSSRule = 2 does not work for that SKU.

CSLMetric Customer Service Level Metric (CSLMetric) specifies the type of customer service metric used for this SKU in the calculation of statistical safety stock.

• 1: Cycle Service

This metric signifies the fraction of cycles in which a stockout does not occur. A stockout is defined as an occasion where the on-hand inventory drops to a level of zero.

• 2: Unit Fill

This metric is specified as the percentage of demand, measured in units, that can be directly supplied out of inventory during a replenishment cycle.

• 3: Order Fill

This metric is specified as the total number of customer orders filled completely from stock divided by the total number of customer orders.

For details about how this column is used, refer to Working with statistical safety stock based on customer service in the Inventory Management in JDA Fulfillment section of the JDA Fulfillment OnLine Expert.

CSLTemplate The template that defines time-phased customer service levels for this SKU. The time-phased data is defined in the CSLTemplate and CSLTemplateData tables.

DmdAllocCal The Demand Allocation Calendar (DmdAllocCal) specifies the information about the calendar for which historical demand is allocated.

IPO If the DmdAllocCal value is not specified, the system uses the Allocation Calendar specified in the AllocCal column of the SKUDemandParam table.

DmdCal The demand calendar populated from the DFU table when the Transfer History process is run.

If DFU:DmdCal is blank, the system uses the default calendar specified for the database in DBParam:DmdCal.

DmdCorrelationFactor Demand Correlation Factor (DmdCorrelationFactor) specifies the correlation values between various destination demand.

DmdDistType Demand Distribution Type (DmdDistType) specifies the type of probability distribution to be used for modeling the distribution of demand over the replenishment lead time in the calculation of statistical safety stock.

• 1: Normal

Statistical safety stock is calculated based on the assumption that demand in replenishment lead time follows a normal distribution. Normal distribution is where most of the demand observations fall fairly close to the mean, and a deviation from the mean is as likely to be plus as it is to be minus. When graphed, the normal distribution takes the form of a bell-shaped curve.

• 2: Poisson


SKUSafetyStockParam

Statistical safety stock is calculated based on the assumption that demand in replenishment lead time follows a Poisson distribution. With Poisson distribution, the standard deviation is equal to the square root of the mean. This option is best used when orders are small and infrequent and the quantity per order is constant.

• 3: LogNormal

Statistical safety stock is calculated based on the assumption that demand in replenishment lead time follows a lognormal distribution. Lognormal distribution is where the natural logarithm of the demand follows a normal distribution.

DmdPostDate The date up to which demand for this SKU has been posted.

FcstDur Forecast Duration (FcstDur) specifies a value that corresponds to the frequency with which forecasting is done for this SKU. For example, if this SKU uses weekly forecasting, set FcstDur to seven days. This value is used in the calculation of statistical safety stocks.


LeadTimeSD Lead Time Standard Deviation (LeadTimeSD) is the replenishment lead time standard deviation. The standard deviation of the replenishment lead time must be estimated for this SKU externally, based on statistics of actual observed replenishment lead times.


MaxSS Defines the upper limit constraint on the safety stock to be held for this SKU.

Valid values for MaxSS are between 0 to 999,999,999.0.

If the value that results from the use of SKUSafetyStockParam:SSRule (on page 438) is greater than MaxSS, the system uses MaxSS as the safety stock. However, a larger temporary value for MaxSS may be defined in the SSPresentation table, thus allowing for SS values that exceed the value in this field.

IPO

A value of zero indicates that there is no constraint on maximum safety stock.

MaxSSCovSkipDur While calculating safety stock using forward coverage duration, use MaxSSCovSkipDur to specify the number of consecutive days with zero allocation weights that the process can skip to accommodate SSCov (on page 437). When you set this column to zero, the process does not skip any days with zero allocation weights.

Note: While calculating safety stock, if at any point the safety stock is greater than MaxSS (on page 434), MaxSS is respected.

The following example illustrates how safety stock is calculated when MaxSSCovSkipDur is defined.

The MaxSSCovSkipDur and SSCov (on page 437) are set to 4320 (that is, 3 days). Calculate display date field in the Plan Analysis page is set to End of time period.

Consider two weeks with the following demand allocation:


SKUSafetyStockParam

Day Mon

Tue Wed Thu Frid Sat Sun Mon Tue Wed Thu Frid Sat Sun

Demand Allocation

10

10 10 0 0 0 0 10 10 10 10 0 0 0

Safety stock on Monday = Demand allocation on (Tuesday + Wednesday + Sunday) = 10 + 10 + 0 = 20

As MaxSSCovSkipDur is set to 3, the process skips the three consecutive zero demands on Thursday, Friday, and Saturday and takes the zero demand on Sunday for calculation.

Similarly, safety stock on Tuesday = Demand allocation on (Wednesday + Sunday + Monday) = 10 + 0 + 10 = 20

Hence, you get the following results

Day Mon

Tue Wed Thu Frid Sat Sun Mon Tue Wed Thu Frid Sat Sun

Demand Allocation

20

20 20 30 30 30 30 30 20 30 30 30 30 30

MaxSSFactor The maximum safety stock factor is utilized to determine the maximum safety stock allowed at the SKU. This column value is used to constrain the safety stock based on the standard deviation of lead time demand. A value of zero in this column will be ignored.

MfgLeadTimeRule Note: This column is not used in the current release.

MinSS Defines the lower limit constraint on the safety stock to be held for this SKU. A value of zero indicates that there is no constraint on maximum safety stock.

The inventory for the SKU should never fall below Absolute Minimum Stock (MinSS). If the value that results from the use of SKUSafetyStockParam:SSRule (on page 438) is less than MinSS, the system uses MinSS as the safety stock.

MSEAbsToleranceLimit MSE Absolute Tolerance Limit (MSEAbsToleranceLimit) specifies the absolute tolerance limit between the forecast and actual. If the absolute difference between the forecast and actual of any observation is less than the absolute tolerance limit, the observation will be considered for MSE calculation regardless of masking rules, otherwise the observation will be screened by masking rules.

MSELag The number of lag periods used by the Statistical Safety Stock process in retrieving historical forecast data from the HistFcst table for the calculation of MSE:MSE when the CalcMSERule (on page 431) is set to 3 or 4.

For example, if the forecast is carried on a monthly basis, a lag value of 2 implies that the forecasted date should be two months prior to the start date. Similarly, a lag of 0 implies that the forecast date is the same as the start date.

MSEMaskMaxVal


SKUSafetyStockParam

MSE Masking Maximum Value (MSEMaskMaxVal) specifies the maximum value for masking the observation. It should be read as decimal when the masking option is Ratio masking and as percentage when the masking option is Percentage masking.

MSEMaskMinVal MSE Masking Minimum Value (MSEMaskMinVal) specifies the minimum value for masking the observation. Should be read as decimal when the masking option is Ratio masking and as percentage when the masking option is Percentage masking.

MSEMaskOpt MSE Masking Option (MSEMaskOpt) specifies the masking options within demand MSE calculation. The options are:

0 - No Masking. MinVal and MaxVal are not taken into account

1 - Ratio Masking. MinVal >0, <1 and MaxVal >1

2 - Percentage Masking. MinVal 0-100 and MaxVal >MinVal, <=100

MSEModelOpt Select the MSE model option. The options are:

• 1: Static

The Calculate SKU MSE process calculates a single MSE value on the OHPost date.

Note: When you set the MSE rule to 1, the MSE value effective on OHPost is used.

• 2: Time Phased

The Calculate SKU MSE process calculates the following:

• Time-phased MSE values using the mean daily demand in AvgDmd:Qty. The MSE values effectivity is based on the mean daily demand’s effectivity

Note: When you set the MSE rule to 1, the effective MSE of the calendar day is used.

MSEPer The number of demand periods used in calculating the lagged or centralized MSE (CalcMSERule (on page 431) = 3 or 4) for this SKU. The value in this column specifies the number of periods of demand data to be retrieved from the SKUHist and the SKUHistFcst tables during the calculation, starting with the date set in SKUSafetyStockParam:DmdPostDate (on page 434) and moving back in time. For every demand quantity that is retrieved from the SKUHist table, a corresponding historical forecast quantity, with the same start date and with a lag value of SKUSafetyStockParam:MSELag (on page 435), is retrieved from the SKUHistFcst table.

NetFcstMSESmConst Net Forecast Mean Squared Error Smoothing Constant (NetFcstMSESmConst) is the constant value used by the Calculate Statistical Safety Stock process, SKU MSE option to smooth the SKU-level Net Forecast Mean Squared Error (MSE:MSE) using this equation:

New MSE:MSE = ((1 - NetFcstMSESmConst) × old MSE:MSE) + (NetFcstMSESmConst × (total of DFU errors2))

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

NumReplenYr Number of Replenishments per Year (NumReplenYr) is the number of times you expect to replenish the stock for a SKU during the year. Populate this field if you are bringing in user-defined replenishment quantities/average demand.

OrderDataDur


SKUSafetyStockParam

Number of observations considered to compute purchase lead time and purchase lead time standard deviation.

OrderLag The number of periods between order plan date and order place date.

OrderPostDate The date on which all the order related data is posted at a SKU.

ShipDataDur Number of observations considered to compute transportation lead time and transportation lead time standard deviation.

ShipLag The number of periods between plan shipment date and plan shipment start date.

SSCov Safety Stock Duration Forward Cover is the duration of time that Safety Stock Rules 2, 3, 4 and 6 use.

SSCovUseBaseOnlySw This switch specifies whether Safety Stock Duration Forward Cover (SSCov (on page 437)) calculations only consider base forecast or all forecast.

• Yes: SSCov (on page 437) calculations will only consider base forecast (DFUtoSKUFcst:Type (on page 121)=1)

• No: SSCov (on page 437) calculations will consider all forecast

SSMeetEarlyDur Safety Stock Meet Early Duration (SSMeetEarlyDur) is the number of earlier time buckets that the algorithm can use when it searches for supply to satisfy the customer order.

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

StockOrder:NeedDate – SKUSafetyStockParam:SSMeetEarlyDur

When you run the Master Planning Calculate Master Plan algorithm, you can override this value for the current algorithm run. To do that, on the Calculate Master Plan process page, check the Override check box and specify a value in the Duration field.

SSPresentationOpt This option determines whether the Minimum Presentation Quantity (SSPresentation:PresentationQty) should be considered while calculating safety stock.

• 1: Do not consider MPQ while calculating safety stock

• 2: Consider MPQ while calculating safety stock

Note: For more information on MPQ, see "Including Minimum Presentation Quantity (MPQ) in safety stock calculation" in JDA Fulfillment OnLine Expert.

SSPriority This value indicates the importance of safety stock orders for this SKU in relation to all other safety stock orders. The Master Planning process uses this priority when determining which demand to satisfy first. When Master Planning creates a safety stock order (a stock order whose Type is 2), it uses this value in StockOrder:Priority. 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 SKUSafetyStockParam:SSPriority = -1, then the Calculate Master Plan process will use the priority set in Generate Stock Orders process page.


SKUSafetyStockParam

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

SSRule A rule that determines how the system calculates the target safety stock value for this SKU.

• 1 = Manual

• 2 = Duration Forward Coverage for Adjusted Independent Demand

• 3 = Duration Forward Coverage for Total Demand

• 4 = Duration Forward Coverage for Total Demand Plus Statistical Safety Stock for Independent Demand

• 5 = Statistical Safety Stock for Independent Demand

• 6 = Duration Forward Coverage for Adjusted Forecasted Customer Orders

• 7 = Duration Forward Coverage for Total Independent Demand

• 8 = Duration Forward Coverage Plus Statistical Safety Stock for Total Independent Demand

• 9 = Manual - quantity based

• 10 = Independent demand - coverage based

• 11 = Total demand - coverage based

If you use rules 4, 5, or 8, safety stock is calculated as a statistical safety stock value. Statistical safety stock is the minimum stock required to achieve a given customer service level during each planning period. Statistical safety stock is based on the accuracy of the forecast for the SKU.

Regardless of the rule you select, the system reports the larger of two values: the safety stock based on SSRule or the Absolute Minimum Stock (SKUSafetyStockParam:MinSS (on page 435) or SKUEffInventoryParam:MinSSQty (on page 314)). Likewise, the system reports the lesser of two values: the safety stock based on SSRule or the Absolute Maximum Stock (SKUSafetyStockParm:MaxSS (on page 434) or SKUEffInventoryParam:MaxOHQty (on page 314)).

Several of these rules include independent demand in their calculations. When FcstAdjRule = 6, adjusted independent demand includes forecasted customer orders within the Customer Order Duration.

ESP (LPOPT and MAP)

Rules 9 and 11 are supported by LPOPT and MAP. Rule 10 is supported only by LPOPT. If you specify this field value as 10 and use the MAP solver to generate a master plan, the plan is generated considering the SSRule value to be 11.

SSTemplate Safety Stock Calendar (SSTemplate) is the name of the safety stock template assigned to the SKU. Assign a safety stock template if the SKU uses Safety Stock Rule (SSRule (on page 438)) 2, 3, or 4 and you want the system to calculate forward coverage using a time-phased coverage duration. The SSTemplate table defines the incremental coverage duration to be used in each time period. The time-phased value determined by the SSTemplate data is added to the value in SSCov.

StatSSAdjOpt After preadjusted statistical safety stock has been computed for a particular SKU, Statistical Safety Stock Adjustment Option (StatSSAdjOpt) determines how it is to be increased or reduced with time-phased increase or reduction factors and applied to that SKU. The options are:

StatSSCovLimitDur Statistical Safety Stock Coverage Limit Duration column defines the statistical safety stock limit in terms of a coverage duration calculated from the OHPost date.

Note: The minimum value for StatSSCovLimitDur is 0.


SKUSafetyStockParam

Fulfillment

The Calculate Statistical Safety Stock process considers the duration specified in this column as the limit duration. Also, the process calculates limit forecast as follows:

Limit Forecast = SKUProjStatic:AllocTotFcst (SKU:OHPost + Limit Duration) - SKUProjStatic:AllocTotFcst (SKU:OHPost)

If the statistical safety stock is greater than the limit forecast, the process sets the statistical safety stock to the limit forecast value, and generates exception 261.

IPO

Statistical Safety Stock Coverage Limit Duration column value is used to constraint the safety stock based on coverage duration demand. It is ignored when SKUSafetyStockParam:StatSSCovLimitDur is zero. The valid input for this column is any non-negative values.

StatSSCSL Statistical Safety Stock Customer Service Level (StatSSCSL) defines the numerical target for the customer service metric. You specify this percentage as a value greater than 0 and less than 1. The numerical target works in conjunction with the metric type you specify in SKUSafetyStockParam:CSLMetric (on page 433). For example, CSLMetric = 1 (Cycle Service) and StatSSCSL = 0.8 implies that statistical safety stock should be computed in such a way as to allow for stockouts in, at most, 20% of replenishment cycles.

SupersedeSSSw This switch determines whether the safety stock requirements of the new item can be superceeded (i.e. supplied) through alternate items. The alternate items are defined in Supersession table.

• Yes: Safety stock requirements can be met through alternate items.

• No: Safety stock requirements cannot be met through alternate items.

Note: In case of circular supersession, SupersedeSSSw governs the excess Qty due to PlanArriv rounding irrespective of whether planarriv rounding is supersedable or non supersedable. This value reflects in the PlanArriv:SubstQty.

Note: SafetyStock is supersedable by default.

TOHRule Note: This column is not used in the current release.


SKUStatStatic

SKUStatStatic Table included with: Fulfillment, Master Planning, Supply, Flowcasting, Enterprise Supply Planning



Default value

AltConstrOverStockDate FF, Flowcasting

DATETIME 01/01/1970

AltConstrOverstockQty FF, Flowcasting

DECIMAL 0.0

AltConstrOverstockExcessCovDur

FF, Flowcasting

DURATION 0

AltConstrOverStockDur FF, Flowcasting

DURATION 0

AltConstrOverstockInvStartDate

FF, Flowcasting

DATETIME 01/01/1970

AltConstrStockLowDate FF, Flowcasting

DATETIME 01/01/1970

AltConstrStockLowDur FF, Flowcasting

DURATION 0

AltConstrStockLowQty FF, Flowcasting

DECIMAL 0.0

AltConstrStockOutDate FF, Flowcasting

DATETIME 01/01/1970

AltConstrStockOutDur FF, Flowcasting

DURATION 0

AltConstrStockOutQty FF, Flowcasting

DECIMAL 0

Backorders FF, MP, Flowcasting, ESP

DECIMAL 0.0

ConstrStockLowDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

ConstrStockLowDur FF, MP, Flowcasting, ESP

DURATION 0

ConstrStockLowQty FF, MP, Flowcasting, ESP

DECIMAL 0.0

ConstrStockOutDate FF, MP, ESP DATETIME 01/01/1970

ConstrStockOutDur FF, MP, ESP DURATION 0

ConstrStockOutQty FF, MP, ESP DECIMAL 0.0 ConstrOverStockDate FF,

Flowcasting DATETIME 01/01/197

0 ConstrOverstockQty FF,

Flowcasting DECIMAL 0.0

ConstrOverstockExcessCovDur

FF, Flowcasting

DURATION 0


SKUStatStatic



Default value

ConstrOverStockDur FF, Flowcasting

DURATION 0

ConstrOverstockInvStartDate

FF, Flowcasting

DATETIME 01/01/1970

CurAvailShipOH Not used in this release

DECIMAL 0.0

CurConstrCovDur FF, MP, Flowcasting, ESP

DURATION 0

CurCovDur FF, MP, Flowcasting, ESP

DURATION 0

CurReservedOH Not used in this release

DECIMAL 0.0

Dur FF, MP, Supp, Flowcasting, ESP

DURATION 0

FirstPlanArrivDate FF, Flowcasting

DATETIME 01/01/1970

FirstPlanArrivQty FF, Flowcasting

DECIMAL 0.0


TEXT

LateIntransIn FF, MP, Flowcasting, ESP

DECIMAL 0.0


TEXT

MaxCnstrProjOHDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

MaxConstrCovDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

MaxConstrCovDur FF, MP, Flowcasting, ESP

DURATION 0

MaxConstrProjOH FF, MP, Flowcasting, ESP

DECIMAL 0.0

MaxCovDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970


SKUStatStatic



Default value

MaxCovDur FF, MP, Flowcasting, ESP

DURATION 0

MaxProjOH FF, MP, Flowcasting, ESP

DECIMAL 0.0

MaxProjOHDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

MinConstrCovDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

MinConstrCovDur FF, MP, Flowcasting, ESP

DURATION 0

MinCovDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

MinCovDur FF, MP, Flowcasting, ESP

DURATION 0

OptionSet FF, MP, Supp, Flowcasting, ESP

TEXT

OverstockDate FF, Flowcasting

DATETIME 01/01/1970

OverstockQty FF, Flowcasting

DECIMAL 0.0

OverstockExcessCovDur FF, Flowcasting

DURATION 0

OverstockDur FF, Flowcasting

DURATION 0

OverstockInvStartDate FF, Flowcasting

DATETIME 01/01/1970

ProcessDate FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

StartDate FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

StockLowDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

StockLowDur FF, MP, Flowcasting, ESP

DURATION 0


SKUStatStatic



Default value

StockLowQty FF, MP, Flowcasting, ESP

DECIMAL 0.0

StockOutDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

StockOutDur FF, MP, Flowcasting, ESP

DURATION 0

StockOutQty FF, MP, Flowcasting, ESP

DECIMAL 0.0

UnconNetAvlNegDate MP, Supp, ESP

DATETIME 01/01/1970

UnconNetAvlQtyAtLT MP, Supp, ESP

DECIMAL 0

UnconNetOHLT Supp DECIMAL 0

UnconNetOHNegDate Supp DATETIME 01/01/1970

UnconNumCancel MP, Supp, ESP

DECIMAL 0

UnconNumNew MP, Supp, ESP

DECIMAL 0

UnconNumPull MP, Supp, ESP

DECIMAL 0

UnconNumPush MP, Supp, ESP

DECIMAL 0

UnconRevCancel MP, Supp, ESP

DECIMAL 0

UnconRevNew MP, Supp, ESP

DECIMAL 0

UnconRevPull MP, Supp, ESP

DECIMAL 0

UnconRevPush MP, Supp, ESP

DECIMAL 0

UnmetIntransOut Not used in this release

DECIMAL 0.0

UserID FF, MP, Flowcasting, ESP

TEXT ' '

Table description


SKUStatStatic

Rows are written to this table as a result of running the Store SKU Projections process. Each row in this table presents statistics for a particular SKU. The calculations described here are used by the Generate SKU Exceptions process when it generates exceptions; however, Generate SKU Exceptions re-derives these calculations; the rows in these columns are not used. All references in this table are valid for the Generate SKU Exceptions process. You cannot edit this table.

Note: Since the SKUStatStatic table simply stores static data, you must run the Store SKU Projections process to recalculate data after changes have been made.

Column descriptions AltConstrOverStockDate The date when AltConstrCov Dur exceeds the SKUPlanningParam:MaxCovDur

AltConstrOverstockQty The quantity you are overstock on the AltConstrOverstockDate. AltConstrProjOH (on AltConstrOverstock Date) – Demands starting from AltConstOverstock Date up to MaxCovDur.

AltConstrOverstockExcessCovDur The number of days you are overstock on the AltConstrOverstock Date.

AltConstrOverStockDur The duration you are overstock starting on the AltConstrOverstock Date. This is the number of days AltConstCovDur is over MaxCovDur starting on the AltConstOverstock Date

AltConstrOverstockInvStartDate AltConstrOverstock Date + MaxCovDur. This date represents the date you start incurring unnecessary carrying costs.

AltConstrStockLowDate AltConstrained Stock Low Date(AltConstrStockLowDate) is the first date when SKU projection AltConstrProjOH falls below the value that represents the sum of the safety stock quantity plus all active Supplemental Order Holdout Quantities, plus the instantaneous quantity of any Supplemental Order for which no Holdout is defined. If the constrained stock does not fall below this value within the userview duration, the value in this column is NoDate.

AltConstrStockLowDur AltConstrained Stock Low Duration (AltConstrStockLowDur) is the duration of the first period when SKU projection AltConstrProjOH is below the safety stock plus Supplemental Order quantity explained underAltConstrStockLowDate. If AltConstrProjOH never exceeds the safety stock plus Supplemental Order quantity within the userview duration after the first time it drops below that quantity, the value in this column is the length of time to the end of the userview duration. If AltConstrProjOH does not fall below the safety stock plus Supplemental Order quantity within the userview duration, the value in this column is 0.

AltConstrStockLowQty AltConstrained Stock Low Quantity (AltConstrStockLowQty) is the largest quantity by which SKU projection AltConstrProjOH falls below the safety stock plus Supplemental Order quantity, from the first time it falls below until it is above again. If AltConstrProjOH does not fall below the safety stock plus Supplemental Order quantity within the userview duration, the value in this column is 0.

AltConstrStockOutDate AltConstrained Stock Out Date (AltConstrStockOutDate) is the first date when SKU projection AltConstrProjOH is negative. The value in this column is blank if that does not happen within the userview duration.

AltConstrStockOutDur


SKUStatStatic

AltConstrained Stock Low Duration (AltConstrStockLowDur) is the duration of the first period when SKU projection AltConstrProjOH is negative, beginning from the date/time when SKU projection AltConstrProjOH first becomes negative until it becomes non-negative again. If AltConstrProjOH never exceeds zero within the userview duration after the first time it drops below zero, the value in this column is the length of time to the end of the userview duration. If AltConstrProjOH does not fall negative within the userview duration, the value in this column is 0.

AltConstrStockOutQty SKU statistic AltConstrStockOutQty is the largest absolute value for negative AltConstrained Projected on Hand within the userview duration, beginning from the date/time when SKU projection AltConstrProjOH first becomes negative until it becomes non-negative again. If AltConstrProjOH never becomes positive again within the userview duration, AltConstrStockOutQty is its largest negative value within the userview duration. If no altconstrained stockout occurs, the value in this column is 0.

BackOrders Forecasted and nonforecasted customer orders that have not yet been met. Backorders is the sum of all customer orders where:


• CustOrder:ShipDate is less than or equal to SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank)

The system considers Backorders to fall in the time period that includes SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank).

ConstrStockLowDate Constrained Stock Low Date (ConstrStockLowDate) is the first date when SKU projection ConstrProjOH falls below the value that represents the sum of the safety stock quantity plus all active Supplemental Order Holdout Quantities, plus the instantaneous quantity of any Supplemental Order for which no Holdout is defined. If the constrained stock does not fall below this value within the userview duration, the value in this column is NoDate.

ConstrStockLowDur Constrained Stock Low Duration (ConstrStockLowDur) is the duration of the first period when SKU projection ConstrProjOH is below the safety stock plus Supplemental Order quantity explained under ConstrStockLowDate (on page 445).

If ConstrProjOH never exceeds the safety stock plus Supplemental Order quantity within the userview duration after the first time it drops below that quantity, the value in this column is the length of time to the end of the userview duration.

If ConstrProjOH does not fall below the safety stock plus Supplemental Order quantity within the userview duration, the value in this column is 0.

ConstrStockLowQty Constrained Stock Low Quantity (ConstrStockLowQty) is the largest quantity by which SKU projection ConstrProjOH falls below the safety stock plus Supplemental Order quantity, from the first time it falls below until it is above again.

If ConstrProjOH does not fall below the safety stock plus Supplemental Order quantity within the userview duration, the value in this column is 0.

ConstrStockOutDate Constrained Stock Out Date (ConstrStockOutDate) is the first date when SKU projection ConstrProjOH is negative. The value in this column is blank if that does not happen within the userview duration.

ConstrStockOutDur Constrained Stock Low Duration (ConstrStockLowDur) is the duration of the first period when SKU projection ConstrProjOH is negative, beginning from the date/time when SKU projection ConstrProjOH first becomes negative until it becomes non-negative again.


SKUStatStatic

If ConstrProjOH never exceeds zero within the userview duration after the first time it drops below zero, the value in this column is the length of time to the end of the userview duration.

If ConstrProjOH does not fall negative within the userview duration, the value in this column is 0.

ConstrStockOutQty Constrained Stock Out Quantity (ConstrStockOutQty) is the largest constrained stockout quantity within the first constrained stockout duration. If no constrained stockout occurs, the value in this column is 0.

SKU statistic ConstrStockOutQty is the largest absolute value for negative Constrained Projected on Hand within the userview duration, beginning from the date/time when SKU projection ConstrProjOH first becomes negative until it becomes non-negative again. If ConstrProjOH never becomes positive again within the userview duration, ConstrStockOutQty is its largest negative value within the userview duration.

ConstrOverStockDate The date when ConstrCovDur exceeds the MaxCovDur

ConstrOverstockQty The quantity you are overstock on the ConstrOverstock Date. ConstrProjOH (on Overstock Date) – Demands starting from Overstock Date up to MaxCovDur.

ConstrOverstockExcessCovDur The number of days you are overstock on the ConstrOverstock Date.

ConstrOverStockDur The duration you are overstock starting on the ConstrOverstock Date. This is the number of days ConstrCovDur is over MaxCovDur starting on the Overstock Date

ConstrOverstockInvStartDate ConstrOverstock Date + MaxCovDur. This date represents the date you start incurring unnecessary carrying costs.

CurAvailShipOH Note: This column is not used in the current release.

CurConstrCovDur Current Constrained Coverage Duration (CurConstrCovDur) is the coverage duration of Constrained Projected On Hand (SKU projection ConstrProjOH), beginning at SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank). The maximum value for this column in 10 years.

CurCovDur Current Coverage Duration (CurCovDur) is the coverage duration of projected on hand (SKUProjStatic:CovDur) as of SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank). The maximum value for this column is 10 years.

CurReservedOH Note: This column is not used in the current release.

Dur The duration of the time interval that applies to the data in this row, based on the Calendar specified.

FirstPlanArrivDate Date of the Planned Arrival with the earliest SchedArrivDate.

FirstPlanArrivQty Total quantity of Planned Arrivals at time of the first planned arrivals. If there the multiple Planned arrivals, with the same SchedArrivDate, then they are summed up.


SKUStatStatic

Item The item associated with the SKU whose statistics appear in this row.

LateIntransIn Late Intransits In (LateIntransitsIn) is the sum of all loads into this destination whose VehicleLoadLine:SchedArrivDate is less than or equal to SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank) and whose VehicleLoad:DestStatus is 1 (Not received) or 2 (Received, but not part of on hand).

Loc The location associated with the SKU whose statistics appear in this row.

MaxCnstrProjOHDate Maximum Constrained Projected on Hand Date and Time (MaxConstrProjOHDate) is the first date and time within the userview duration when MaxConstrProjOH occurs.

MaxConstrCovDate Maximum Constrained Coverage Date and Time (MaxConstrCovDate) is the date and time within the userview duration when MaxConstrCovDur occurs.

MaxConstrCovDur Maximum Constrained Coverage Duration (MaxConstrCovDur) is the duration of the longest constrained Coverage Duration period (SKUProjStatic:ConstrCovDur) within the period specified for the user view. You can compare the value in this column to see whether it exceeds the shelf life (SKUPlanningParam:MaxCovDur). The maximum value for this column is 10 years.

The system bases the value in MaxConstrCovDur on the value of Constrained Projected on Hand (ConstrProjOH) at the end of each time interval in the userview period. In determining this value for each time interval, the system does not consider any coverage that extends past the end of the userview period.

The value of ConstrProjOH might have been higher at some earlier point in a time interval. If you want the system to check the value of ConstrProjOH at some other time, you must specify a different userview period.

MaxConstrProjOH Maximum Constrained Projected on Hand (MaxConstrProjOH) is the maximum constrained projected on-hand quantity in the userview period.

MaxCovDate Maximum Coverage Date and Time (MaxCovDate) is the date and time within the userview duration when MaxCovDur occurs.

MaxCovDur Maximum Coverage Duration (MaxCovDur) is the duration of the longest Coverage Duration period (SKU projection CovDur) within the period specified for the userview. You can compare the value in this column to see whether it exceeds the shelf life (SKUPlanningParam:MaxCovDur). The maximum value for this column is 10 years.

The system bases the value in MaxCovDur on the value of projected on hand at the end of each time interval in the userview period. The SKUProjStatic:DisplayQty (on page 405) is deducted from the projected on hand when performing these calculations. In determining the Cov value for each time interval, the system does not consider any coverage that extends past the end of the userview period.

The value of projected on hand might have been higher at some earlier point in a time interval. If you want the system to check the value of projected on hand at some other time, you must specify a different userview period.

MaxProjOH Maximum Projected on Hand (MaxProjOH) is the maximum projected on-hand quantity in the userview period. JDA Enterprise Supply Planning Reference Guide 447 © 2014 JDA Software Group, Inc.- Confidential

SKUStatStatic

MaxProjOHDate Maximum Projected on Hand Date and Time (MaxProjOHDate) is the first date and time within the userview duration when MaxProjOH occurs.

MinConstrCovDate Minimum Constrained Coverage Date (MinConstrCovDate) is the date and time within the userview duration when MinConstrCovDur occurs.

MinConstrCovDur Minimum Constrained Coverage Duration (MinConstrCovDur) is the shortest constrained Coverage Duration (SKUProjStatic:ConstrCovDur) within the userview period, based on the smallest value for Constrained Projected on Hand (ConstrProjOH) in that period. The maximum value for this column is 10 years.

MinCovDate Minimum Coverage Date (MinCovDate) is the date and time within the userview duration when MinCov occurs.

MinCovDur Minimum Coverage Duration (MinCovDur) is the shortest Coverage Duration (SKU projection CovDur) within the userview period, based on the smallest value for projected on hand in that period. The maximum value for this column is 10 years.

OptionSet The name of the option set used when running the Store SKU Projections process.

OverstockDate The date when CovDur exceeds the SKUPlanningParam:MaxCovDur

OverstockQty The quantity that is overstock on the Overstock Date.

ProjOH (on Overstock Date) – Demands starting from Overstock Date up to Overstock Date+ MaxCovDur.

OverstockExcessCovDur The number of days that are overstock on the Overstock Date.

OverstockDur The duration you are overstock starting on the Overstock Date. This is the number of days CovDur is over MaxCovDur starting on the Overstock Date

OverstockInvStartDate Overstock Date + MaxCovDur. This date represents the date you start incurring unnecessary carrying costs.

ProcessDate The date and time when the Store SKU Projections process was run.


StockLowDate The first date when the projected available falls below zero, which happens when the projected on hand falls below a value that represents the sum of the safety stock quantity plus all active Supplemental Order Holdout Quantities, plus the instantaneous quantity of any Supplemental Order for which no Holdout is defined plus any active Display Quantities. If the stock does not fall below this value within the userview duration, the value in this column is NoDate.


SKUStatStatic

StockLowDur Duration of the first period when the projected available falls below zero as explained under StockLowDate. If the projected available never exceeds zero within the userview duration after the first time it drops below zero, the value in this column is the length of time to the end of the userview duration. If the projected available does not fall below zero within the userview duration, the value in this column is 0.

StockLowQty The largest quantity by which the projected available falls below zero, from the first time it falls below until it is above again.

If the projected available does not fall below zero within the userview duration, the value in this column is 0.

StockOutDate The date of first stockout, where a stockout is defined as the planned projected onhand (SKUProj:PlanProjOH) going below zero. The stockout date is blank if no stockout occurs within the userview duration.

StockOutDur The duration of the first stockout, where a stockout is defined as the planned projected onhand (SKUProj:PlanProjOH) going below zero, beginning from the date/time when the SKUs planned projected on hand first becomes negative until it becomes non-negative again. If the planned projected on hand never becomes a positive number within the userview duration after the first stockout, the value in this column is the length of time to the end of the userview duration.

StockOutQty The largest stockout quantity within the first stockout duration. If no stockout occurs, the value in this column is 0.

StockOutQty is the largest absolute value for negative planned projected on hand (SKUProj:PlanProjOH) within the userview duration, beginning from the date/time when the SKUs planned projected on hand first becomes negative until it becomes non-negative again. If the planned projected on hand never becomes positive again within the userview duration, StockOutQty reflects its largest negative value within the userview duration.

UnconNetAvlNegDate This is the net available negative date.

Unconstrained Net Available Negative Date (UnConNetAvlNegDate) is the first date on which the net available for the SKU becomes a negative quantity. Starting with the on-hand date, the first date that this part goes negative is displayed here.

UnconNetAvlQtyAtLt Unconstrained Net Available Quantity at Lead Time (UnConNetAvlQtyAtLt) is the net available at lead-time of the product.

Supply

This is a calculated field. It takes the previous bucket’s closing balance, adds the supplies for this bucket, subtracts the total demand for this bucket and determines the net available. The net available for this bucket becomes equal to its closing balance and is used as an opening balance for the next bucket. For the first bucket at plan start, the opening balance is the inventory plus any supplies coming in before the first bucket minus any past due demand. The lead-time used for the item is the cumulative lead-time from the SKUSupplyParam Table. The value of the Net available at that time period is the value for this SKU Statistic.

UnconNetOHLt The lead-time used for the SKU is the cumulative lead-time from the SKUSupplyParam Table. The value of the net on hand lead-time at that time period is the value for this SKU Statistic.


SKUStatStatic

UnconNetOHNegDate The first date on which the net on hand quantity, for a SKU, becomes a negative quantity.

UnconNumCancel Unconstrained Total Cancel Actions (UnconNumCancel) is the number of Cancel actions.

UnconNumNew Unconstrained Total New Actions (UnConNumNew) is the number of New actions.

UnconNumPull Unconstrained Total Pull Actions (UnConNumPull) is the number of Pull actions.

UnconNumPush Unconstrained Total Push Actions (UnConNumPush) is the number of Push actions.

UnconRevCancel Unconstrained Total Revenue of Cancel Actions (UnConRevCancel) is the summed up cost of the Supply to determine the Dollar value of the actions.

UnconRevNew Unconstrained Total Revenue of New Actions (UnConRevNew) is the summed up cost of the Supply to determine the Dollar value of the actions.

UnconRevPull Unconstrained Total Revenue of Pull Actions (UnConRevPull) is the summed up cost of the Supply to determine the Dollar value of the actions.

UnconRevPush Unconstrained Total Revenue of Push Actions (UnConRevPush) is the summed up cost of the Supply to determine the Dollar value of the actions.

UnmetIntransOut Note: This column is not used in the current release.

UserID The identification of the user who ran the Store SKU Projections process.


Sourcing

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


Default value

Abbr Supp TEXT ' '

ArrivCal FF, MP, Flowcasting, ESP

TEXT ' '

ConvenientAdjDownPct

FF DECIMAL 0

ConvenientAdjUpPct

FF, Flowcasting DECIMAL 0

ConvenientOverrideThreshold


ConvenientShipQty

FF, Flowcasting DECIMAL 0

CostPercentage Supp INTEGER 100.00 Dest 4 FF, MP, Supp,

PSO, IPO, Flowcasting, ESP

TEXT

Disc FF, MP, Supp, Flowcasting, ESP

DATETIME 01/01/1970

Eff FF, MP, Supp, PSO, IPO, Flowcasting, ESP

DATETIME 01/01/1970

EnableDynDepSw FF, Flowcasting BOOLEAN 1

EnableSw PSO BOOLEAN 1 Factor FF, MP, IPO,

Flowcasting, ESP

DECIMAL 1.0

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

TEXT

LoadDur FF, Flowcasting, MP

DURATION 0

LotSizesEnabledSw

PSO BOOLEAN 0

MajorShipQty FF, MP, PSO, Flowcasting, ESP

DECIMAL 0

MaxLeadTime PSO DURATION 36500D MaxShipQty MP, PSO, ESP DECIMAL 0 JDA Enterprise Supply Planning Reference Guide 451 © 2014 JDA Software Group, Inc.- Confidential

Sourcing


Default value

MinLeadTime PSO DURATION 0 MinorShipQty FF, MP, PSO,

Flowcasting, ESP

DECIMAL 0

NoNewSupplyDate MP, ESP DATETIME 01/01/1970

OrderGroup FF TEXT

OrderGroupMember

FF UPPER_TEXT

Priority MP, Supp, ESP INTEGER 1 PullForwardDur FF, MP,


ReviewCal FF, MP, Flowcasting

TEXT ' '

RoundingFactor FF, Flowcasting DECIMAL 0 ShipCal FF, MP,

Flowcasting, ESP

TEXT ' '

ShrinkageFactor MP, Supp DECIMAL 0 Source 3 FF, MP, Supp,,

Flowcasting PSO, IPO, ESP

TEXT

Sourcing 1 FF, MP, Supp, PSO, IPO, ESP

TEXT ' '

SourcingCost ESP (LPOPT) FLOAT 0

SourcingGroup ESP (LPOPT) TEXT SplitQty FF, Flowcasting DECIMAL 0 SupplyLeadTime Supp DURATION 0 SupplyTransferCost

Supp DECIMAL 0

TransMode FF, MP, Supp, IPO, Flowcasting, ESP

TEXT ' '

UnloadDur FF, Flowcasting, MP

DURATION 0

UseLookAheadSw FF, Flowcasting BOOLEAN 1 YieldFactor Supp INTEGER 100.00

Table description Each row in this table defines a lane — a source location and a destination location between which a specific item can be shipped. For items that can be shipped on multiple lanes, there are multiple rows.

Supply


Sourcing

The Sourcing table defines transfer relationships on a part-by-part basis for transferred SKUs.

Master Planning

Each row in this table specifies an item that can be shipped between a specific source and destination location. There may be multiple rows for an item, defining all the lanes on which the item may be shipped.

Fulfillment

For Fulfillment/Deployment and Fulfillment/Distribution, each row in this table defines the portion of a destination SKU's replenishments that come from a particular source SKU. In the example below, 11001.SEA receives 100 percent of its product from 11001.LA; 11001.DEN receives 20 percent of its product from 11001.LA and 80 percent from 11001.CHI.

Item Dest Source Eff Factor Mode ArrivCal

11001 SEA LA 1/1/04 1.0 Truck Cal1

11001 DEN LA 1/1/04 0.2 Truck Cal1 11001 DEN CHI 1/1/04 0.8 Truck Cal1 For systems that include both Fulfillment/Production and Fulfillment/Distribution, this table may include rows whose Factor is 0. In Fulfillment/Distribution, Calculate Plan does not use those rows. But if Fulfillment/Production moves planned orders to a different location, it tries to replace existing planned arrivals from the old location with new firm planned arrivals from the new location. To do that, Fulfillment/Production must find a row in the Sourcing table whose item is the item whose planned orders are moved and whose source is the new location of those planned orders.

For Fulfillment/Order Optimization, on a given day, orders are created only for a single combination of Item and Dest columns. The Optimize Orders process currently does not support split-source scenarios, in which source of the supply is distributed. For example, in a typical split-source scenario, a certain percentage of supply is obtained from one source and the remainder is obtained from others. This scenario will be supported in future releases.

When there are multiple rows in the Sourcing table for the same combination of Item and Dest columns, the Optimize Orders process creates an OrderSKU for the sourcing row that is ‘most effective’ at the SKU's Arrival date. ‘Most effective’ is defined as follows:

• The Effective date (Eff) must be on or before the Arrival date, and the Discontinue date (Disc) must be later than the Effective date. If there are multiple rows, then the row with the latest Effective date is used.

• If multiple rows have the same Effective date, then the row with the earliest Discontinue date is used.

• If multiple rows have the same Effective and Discontinue dates, then the rows are sorted alphabetically by the Sourcing column and the first row in the list is used.

• If all rows have the same Effective date, Discontinue date, and Sourcing, then the rows are sorted alphabetically by the Source column and the first row in the list is used.

IPO

In this release, IPO does not support more than one source for consumable SKUs, two sources (one purchase and one repair) for repairable SKUs. In addition, no replenishment sources can be defined for carcass SKUs. See the IPO OnLine Expert for more detailed sourcing examples.

Column descriptions Abbr Abbreviation is the short label for this sourcing, useful for displaying on pages. Does not have to be unique.


Sourcing

ArrivCal Arrival Calendar used by Fulfillment/Distribution, Fulfillment/Deployment and Master Planning to define the times when this destination is allowed to receive product from this source.

Valid values for ArrivCal are identifiers of an existing Arrival Calendar (Cal:Cal whose Cal:Type is 6), or blank.

When Calculate Plan/Calculate Master Plan process is generating arrivals into a destination, it checks the destination's arrival calendar to be sure that it is open at the date/time when the arrival is scheduled. If not, the system changes the scheduled arrival for an earlier date/time when the arrival calendar is open. If there is none, the system tries to schedule the arrival at the next date/time.

If Sourcing:ArrivCal is blank, Calculate Plan/Calculate Master Plan assumes that the destination is always open.

In Fulfillment/Distribution, PlanArriv:DeliveryDate must fall on an open time in the ArrivCal.

In Fulfillment/Deployment, RecShip:DeliveryDate must fall on an open time in the ArrivCal.

Master Planning

PlanArriv: SchedArrivDate must fall on an open time in the ArrivCal.

ConvenientAdjDownPct Used by Calculate Plan in conjunction with Convenient RoundingDefines the percentage of ConvenientShipQty that determines whether planned arrival is rounded down to the earlier ConvenientShipQty. The value in this column must fall between 0 and 100.

Note: This column is not used by OrderOptimization.

ConvenientAdjUpPct Used by Order Optimization and Calculate Plan in conjunction with Convenient Rounding. This column defines the percentage of ConvenientShipQty that determines whether SOQ is rounded to the next ConvenientShipQty (on page 454). The value in this column must fall between 0 and 100.

ConvenientOverrideThreshold Used by Order Optimization and Calculate Plan in conjunction with Convenient Rounding. This column defines the threshold value in multiples of ConvenientShipQty (on page 454). For an Order Optimization SKU this value must be a positive integer. For Calculate Plan the value can be any positive number.

ConvenientShipQty Used by Order Optimization and Calculate Plan in conjunction with Convenient Rounding. The Convenient Rounding Shipment Quantity is used within the SOQ rounding logic in Order Optimization and is used to round planned arrivals in Calculate Plan. This value is used in combination with ConvenientAdjUpPct (on page 454) and ConvenientOverrideThreshold (on page 454). In Calculate Plan, ConvenientAdjDownPct is also used.

This column is typically used to model shipment/packing efficiencies when large quantities of an item are ordered, where you want to use a larger rounding quantity than the normal major and minor rounding shipment quantities (MajorShipQty (on page 457)/MinorShipQty (on page 458)) for Order Optimization and MinDRPQty/IncDRPQty for Calculate Plan).

Here is the logic for rounding the SOQ or the planned arrival:

• Round the quantity up to the next multiple of the major and minor rounding quantities.

• If the rounded quantity is greater than or equal to ConvenientShipQty*ConvenientOverrideThreshold, then round the quantity up to the next larger multiple of ConvenientShipQty.


Sourcing

• If the original rounded quantity is smaller than ConvenientShipQty*ConvenientOverrideThreshold, then compare the remainder after removing multiples of ConvenentShipQty. If that remainder is greater than or equal to ConvenientAdjUpPct*ConvenientShipQty/100, then round the quantity up to the next larger multiple of ConvenientShipQty.

• In Order Optimization, the logic is now complete. In Calculate Plan if the remainder did not meet the round up criteria, then if the remainder is smaller than or equal to the ConvenientAdjDownPct*ConveneintShipQty/100, then round the quantity down to the next smaller multiple of ConvenientShipQty. However, if this rounding down will cause a stock low, then round up by the major and minor quantities sufficient to avoid a stock low.

Note: ConvenientShipQty value cannot be negative.

CostPercentage This field is used by Supply for cost rollup calculation. In case of transferred SKUs, the transfer cost is obtained by adding the supply transfer cost to (SKU material cost * Cost percentage).

Dest The destination location for this sourcing.

Disc Discontinue is the date and time when this sourcing is no longer in effect.

Disc and Eff work together to determine when the sourcing is effective. The chart under Eff summarizes the results of all possible combinations of values for Eff and Disc. Disc is the ending effective date. A Sourcing row is in effect exactly on its Eff date. It is not in effect exactly on its Disc date, but is in effect one minute earlier.

Fulfillment

Setting a Disc date on a sourcing record is not an effective way to cease replenishment in Calculate Plan. If a sourcing row is discontinued and no replacement sourcing from the same or a different source is enabled, then Calculate Plan generates a large planned arrival prior to Sourcing:Disc. The generated planned arrival is large enough to meet all subsequent demands for which there is no effective sourcing.

Eff Eff is the date when this sourcing becomes effective, from the perspective of the destination.

Eff and Disc work together to determine when the sourcing defined in this row is effective. The following chart summarizes the results of all possible combinations of values for Eff and Disc.

Eff value Disc value This sourcing is:

01/01/1970 01/01/1970 Effective



Date later than Disc Date Effective until Disc; discontinued as of Disc; effective as of Eff ESP (MAP and LPOPT)

This combination is not supported by the MAP and LPOPT solvers.

ESP (MAP and LPOPT)

The Generate Master Plan(MAP) and Generate Master Plan(LPOpt) processes respect the Sourcing:Eff value only for PlanArriv:SchedShipDate.


Sourcing

EnableDynDepSw Note: This column is not used in this release.

EnableSw Indicates if this sourcing will be used while running the Production and Sourcing Optimization Optimizer.

Factor Fulfillment

The factor used to determine what portion of the destination SKU's product comes from this source SKU.

If SKUPlanningParam:PlanLeadTimeRule is 4, Calculate Plan and Calculate Forecast Error processes use Factor in calculating SKUPlanningParam:PlanLeadTime. If Factor is 0, the Calculate Plan process does not use this row. Fulfillment/Production may use it when creating new firm planned arrivals, as explained in the introduction to this table.

Note: This column is not supported by Fulfillment/Order Optimization.


Factor that determines what portion of a SKU’s demand should be satisfied by this sourcing method, if the SKU has other sourcing methods with the same Priority. Master Planning uses Factor to calculate the portion of demand to be met by each of the sourcing methods that is effective during a time period.

The following example illustrates how Master Planning calculates the portion of demand to be met by each sourcing method.

Sourcing Methods A and B supply the same SKU, have the same Priority, and are the only sourcing methods effective for this SKU during this time period. Their Factors are:

A: 1.0

B. 0.25

Percentage of demand met by Sourcing Method A = (Factor for Sourcing Method A/ Sum of factors for Sourcing Methods A and B) * 100 = (1/1.25) * 100 = 80.

If you want Master Planning to satisfy equal portions of the demand from each of the sourcing methods at a given Priority level, leave all their Factors set to 1.0. If Factor is 0, Master Planning will not use this sourcing method.

If Factor is 0, the Calculate Master Plan process does not use this row.

IPO

For consumable SKUs, IPO uses this column in a manner similar to Master Planning.

For repairable SKUs, the Factor column represents the portion of the demand filled by this sourcing. In this case, the Factor on the sourcing at the primary location contains the value (between 0 and 1) of the amount of demand that is satisfied by the sourcing location (usually a higher-level repair facility).

ESP (LPOPT and MAP)

When all sourcing methods of a SKU have the same priority, to specify factorization set Factor to a value other than 1 (the default value). This value determines the portion of a SKU's demand satisfied by this sourcing method. To specify that instead of factorization the alternate purchase methods must be used based on Priority, set the Factor of all purchase methods of a SKU to 1.

Item The item whose sourcing is defined in this row. Must be a valid item in the Item table.

LoadDur


Sourcing

Load Duration is the duration required to load a single planned arrival or a recommended shipment at the source. It is counted over open instances of the source SKU’s working calendar.

LotSizesEnabledSw Lot Sizes Enabled Switch determines whether to enable or disable the lot sizes for Production and Sourcing Optimization.

MajorShipQty The minimum quantity used by Calculate Master Plan (Master Planning), Calculate Plan (Fulfillment), and Order Optimization(Fulfillment) when planning planned arrivals (Master Planning) / recommended shipments (Fulfillment)/ vehicle load lines(Order Optimization) to meet requirements. That is, each process calculates replenishments whose quantity is at least the MajorShipQty. It is best to set MajorShipQty as a multiple of MinorShipQty.

In Production and Sourcing Optimization, this is the minimum process lot size, during a Move process.

Fulfillment/Deployment

When SecRSAllocRule = 1 or 3, the quantity of any recommended shipment is equal to one MajorShipQty plus a integer number of MinorShipQty values.

See the OnLine Expert for more information on how Calculate Plan uses MajorShipQty.

The table below shows the resultant behavior if MajorShipQty or MinorShipQty=zero.

MajorShipQty

equals:

MinorShipQty

equals:

Recommended shipment logic:

0 Uses the value in Sourcing:MinorShipQty; no exception is generated.

0 0 No minimum value for RecShips; RecShips are created to meet demand.

0 Creates RecShips greater than or equal to MajorShipQty to meet demand.

When MajorShipQty is same as MinorShipQty, setting the database value of MajorShipQty to zero can improve performance.

OrderOptimization

In Order Optimization , the MajorShipQty is the minimum order quantity for an SKU, but all order quantities are rounded by the MinorShipQty only. For more details see Calculate Suggest Order Quantity (SOQ).

MaxLeadTime The maximum lead time for this sourcing, specified in minutes.

MaxShipQty Master Planning will not create a planned arrival whose quantity is larger than MaxShipQty. If MaxShipQty is 0, no maximum shipment quantity is enforced.

When SKU has SKUPlanningParam:MPSRule (on page 372) = 1 (coverage duration), while aggregating the supplies for a SKU, for a supply method within coverage duration, if aggregated supply exceeds the specified MaxQty, an exception is generated and aggregated supply exceeds the MaxQty. For more information on aggregated supply in a coverage duration, see Single supply in a coverage duration per supply method.


Sourcing

JDA Production and Sourcing Optimization

Whenever a MajorShipQty for Move process is used, Production and Sourcing Optimization implicitly creates an upper bound for the Move processes. By default this upper bound value is 100,000 and if it is required to be changed (beyond 100,000), then Sourcing:MaxShipQty (on page 457) need to be updated accordingly. Also, changing this parameter to an arbitrarily high value will hinder the performance.

MaxShipQty is used in combination with MajorShipQty. When MajorShipQty is utilized, the MaxShipQty has to be set as close as possible to the expected sourcing executions. This will invoke MIP (mix integer programming) feature and the performance time is heavily depended on the proximity of this column value to the expected sourcing executions.

MinLeadTime The minimum lead time for this sourcing, specified in minutes.

MinorShipQty An incremental shipping unit size, such as a case or a tier. When Master Planning or Calculate Plan recommends shipments, it uses a combination of MajorShipQty and MinorShipQty to meet requirements (see MajorShipQty, above).

Valid values for Minor Ship Quantity are 0 up to the value in MajorShipQty.

Companies that ship in pallet-load quantities typically set MinorShipQty equal to the number of units per pallet. If you want the system to recommend shipments of partial pallets for times when requirements cannot be covered by the amount in MajorShipQty, set MinorShipQty to a quantity smaller than MajorShipQty, such as one tier or one case.

Order Optimization

In Order Optimization, all orders are created in direct multiples of MinorShipQty. For more information, refer to the Calculating Suggest Order Quantity (SOQ) section in the Order Optimization chapter of the JDA Fulfillment OnLine Expert.

NoNewSupplyDate Time fence you can use to prevent creating new supply with this sourcing method.

NoNewSupplyDate is a variable used to control creation of new supplies. If you select the No Start before NoNewSupplyDate option, new supplies cannot start before NoNewSupplyDate. If you do not select the No Start before NoNewSupplyDate option, new supplies cannot be scheduled to complete before NoNewSupplyDate.

Master Planning


ESP


OrderGroup The Order Group this SKU is assigned to for the purposes of Order Optimization. This value must exist in the OrderGroup table.

OrderGroupMember The Order Group Member this SKU is assigned to. This value needs to exist in the OrderGroupMember table.

Once an SKU is assigned to an Order Group Member, it is not added to traditional network orders.

Priority Master Planning JDA Enterprise Supply Planning Reference Guide 458 © 2014 JDA Software Group, Inc.- Confidential

Sourcing

This value indicates the importance of this sourcing method in relation to all other supply methods. The Calculate Master Plan process uses this priority to choose between a production method, a sourcing method, and a purchase method (all put together).

The Calculate Master Plan process first tries to satisfy a demand with the highest priority sourcing method, but if this sourcing method cannot satisfy the demand, then the Calculate Master Plan process will investigate a lower priority sourcing method. A value of 1 is most important and higher values are less important.

It is valid to have multiple sourcing methods with the same priority (see Factor (on page 456)). Use the Factor to select the method to be used where more than one method has the same "priority" for a sourcing method.

Note: The default value for the Priority column is 1.

Supply

This value indicates the importance of this sourcing method in relation to all other sourcing methods. The Calculate Supply Plan process uses this priority when determining which sourcing method to use first.

ESP

This value specifies the priority of a sourcing method over other supply methods. The Generate Master Plan process uses this priority to select a production, sourcing, or purchase method (all put together). The Generate Master Plan process tries to satisfy a demand with the highest priority sourcing method. If this sourcing method cannot satisfy the demand, the Generate Master Plan process tries a lower priority sourcing method. A value of 1 has the highest priority and higher values have low priorities.

If all sourcing methods of a SKU have the same priority, the portion of demand satisfied by each sourcing method is determined by the Factor associated with the sourcing method.

PullForwardDur A duration of time that limits the dates upon which a RecShip can be placed on a VehicleLoad by the Build Transportation Loads process. Within Build Transportation Loads, a RecShip can be placed on a VehicleLoad if the earliest allowable departure date (RecShip:DepartureDate minus PullForwardDur) is equal to or less than the vehicleload:ShipDate (on page 494).

ReviewCal Review Calendar used by Fulfillment/Distribution and Fulfillment/Deployment to specify when the orders can be placed for items. It identifies open instances on the source SKU’s order review cycle. Valid values for ReviewCal are identifiers of an existing Review Calendar (Cal:Cal whose Cal:Type is 12). Review calendar is used where periodic review cycles are employed in inventory management.

RoundingFactor Order Optimization uses the Rounding Factor to determine if the Unrounded SOQ is rounded up or rounded down. If the Unrounded SOQ is 14, the MinorShipQty is 10 and the RoundingFactor is .30, the SOQ can be rounded up to 20. However, if the RoundingFactor is .5 then the SOQ would be rounded down to 10.

Similarly, Calculate Plan logic uses the rounding factor to determine whether a planned arrival or planned order is rounded up or down. However, a planned arrival or planned order is always rounded up if rounding down results in a stockout or stock low situation.

ShipCal Fulfillment

For Fulfillment, identifies the shipping calendar (Cal:Type = 6) for the defined sourcing relationship. You can define open or closed shipping periods in the CalData table. If this column is left blank, Calculate Plan respects the value specified in the SKUDemandParam:AllocCal column.

In Fulfillment/Distribution, PlanArriv:DepartureDate must fall on an open time in the ShipCal.


Sourcing

In Fulfillment/Deployment, RecShip:DepartureDate must fall on an open time in the ShipCal.

Master Planning

The shipping calendar is used to determine when a source location is open to ship a load.

PlanArriv:SchedShipDate must fall on an open time in the ShipCal.

ShrinkageFactor Shrinkage accounts for losses that occur during shipment—for example, as a result of spoilage, evaporation, or theft. Set this value to the percent of shrinkage you anticipate. For example, if you expect shrinkage of two percent, set ShrinkageFactor to 2.

Valid values for Shrinkage Factor are 0 to 100.

For planned arrivals that use this sourcing, Master Planning increases the quantity by the percentage specified.

Supply

Shrinkage accounts for loss of inventory due to factors such as limited shelf life, theft, or evaporation. Shrinkage is applied to a demand before assigning supply. For example, if shrinkage is 10%, a demand for 100 will be inflated to 110 before assigning supply. So the expanded quantity is calculated as shown in the following example:

The SKUSupplyParam table stores the default Shrinkage values for independent and dependent demands. For dependent demands, these default values can be overridden by specifying relevant and non-zero values in the BOM and Sourcing tables.


• The shrinkage formula is (qty * (1 + shrinkage / 100)) but yield is (qty * 100 / yield)

• Shrinkage is applied to demand for the SKU; supply yield is applied to planned orders for the SKU


To use the ShrinkageFactor, select the Planning Options > Shrinkage option on the Calculate Master Plan (Master Planning) process page.

Source The source location for this sourcing. Must be a valid location in the Loc table.

Sourcing The name of this sourcing method.

SourcingCost Cost of sourcing a unit of item by this method.

SourcingGroup The group to which this sourcing method belongs.

ESP (LPOPT)

When using the LPOPT solver, if you specify a sourcing group name as the qualifier for an objective, the objective is applied to all sourcing methods in the specified group.

SplitQty


Sourcing

Split Quantity defines the minimum increment by which a RecShip that corresponds to this sourcing row can be split by Build Transportation Loads or Load Manager. It is defined in terms of Item:DefaultUOM.

SupplyLeadTime The lead time taken for the SKU to be transferred from the source location to the destination location.

SupplyTransferCost This field is used by Supply for cost rollup calculation. For transferred SKUs, the transfer cost is calculated as:

Supply fixed transfer cost + (SKU’s material cost x CostPercentage)

TransMode The mode of transportation used for this sourcing. Must be a valid transportation mode in the TransMode table.

UnloadDur The duration of time required to unload planned arrivals or recommended shipments at the destination. It is counted over open instances of the destination SKU’s working calendar.

UseLookAheadSw This field is used by Build Transportation Loads, and indicates whether the use of look-ahead recommended shipments to fill loads that did not meet the load satisfaction criteria is a valid load strategy for this network lane.

• If UseLookAheadSw = 1, the use of look-ahead recommended shipments is a valid strategy.

• If UseLookAheadSw = 0, the use of look-ahead recommended shipments is not allowed.

YieldFactor Supply

Yield accounts for loss during manufacturing. So if yield is 50% and you need 30 units, you have to start building 30 * (100/50) = 60. This means you need to explode the BOM as if you were building 60, even though you only end up with 30. Yield can be applied to either new supply or dependent demand from new supply, depending on the setting of an option (described below). We will call these supply yield and demand yield respectively.

Valid values for Yield Factor are 0 to100.

The formula for yield is as shown below:

The SKUSupplyParam table stores the default Yield values for independent and dependent demands. For dependent demands, these default values can be overridden by specifying relevant and non-zero values in the BOM and Sourcing tables.

For supply yield, the default value may be overridden for planned orders when the SKU, with the yield factor, is a component of the BOM record (or source part of a sourcing record) containing the overriding value. For example: If A is a SKU with component B with the BOM record for A/B having a non-zero yield, then it will override the default value for B when supply yield is enabled. Thus a planned order for B will be created.

For demand yield, the overriding BOM record is for the parent SKU, that is for which the planned order was created. For example, suppose the BOM record for the SKU A and component B has anon-zero yield, then if the demand yield is enabled, the BOM value will override the default value for A when calculating the dependent demand for B.


Sourcing

The main differences between supply yield and demand yield are as follows:

• Demand yield is applied one step later than supply yield; that is, it is applied to the dependent demand quantity, instead of the planned order quantity.

• Demand yield does not generate scrap, as in the case of supply yield.

Note that demand yield uses the parent's yield value, not the component's. From a timing perspective the sequence is as follows:

• Shrinkage (demand)

• Supply yield (planned orders)

• Demand yield (new dependent demands)

Note: However, if supply yield is enabled, demand yield is disabled (except in the case of Work Order dependent demands created when Work Orders are exploded in the BOM).


• The shrinkage formula is (qty * (1 + shrinkage / 100)) but yield is (qty * 100 / yield).

• Shrinkage is applied to demand for the SKU; supply yield is applied to planned orders for the SKU.



SourcingRequirement

SourcingRequirement Table included with: Master Planning, Production and Sourcing Optimization, Enterprise Supply Planning



Dest 5 MP, PSO TEXT

Eff 3 MP, PSO DATETIME TRUNC( TO_DATE( '01/01/1970', 'MM/DD/YYYY'))


Item 4 MP, PSO TEXT LeadTime PSO DURATION 0 NextStepTiming Not used in

this release INTEGER 3

Offset PSO INTEGER 0



0

Rate MP, PSO DECIMAL 0

Res MP, PSO, ESP

TEXT ' '

Source 6 MP, PSO TEXT Sourcing 2 MP, PSO,

ESP TEXT ' '

StepNum 1 MP, PSO, ESP

INTEGER 0

Table description Each row in this table defines the resource requirements associated with a given sourcing process.

Master Planning

A maximum of three rows per sourcing identifier are defined in this table.

• For an Outhandling resource, the StepNum defined should be 1.

• For a Transportation resource, the StepNum defined should be 2.

• For an Inhandling resource, the StepNum defined should be 3.

Column descriptions Dest The destination location of the sourcing associated with this requirement.

Eff Eff is the date when this sourcing becomes effective, from the perspective of the destination. JDA Enterprise Supply Planning Reference Guide 463 © 2014 JDA Software Group, Inc.- Confidential

SourcingRequirement

Master Planning


EnableSw Indicates if this resource will be used while running the Production and Sourcing Optimization Optimizer.

Item The item associated with the sourcing for which this requirement is defined.

LeadTime The lead time for this sourcing.

Offset The amount of time by which resource utilization is offset from the start of an execution of the sourcing process.

QtyUOM The unit of measure applied to the sourcing requirement associated with this sourcing.

Rate Master Planning

The number of units of the item handled by one unit of capacity of the inhandling, outhandling, or transportation resource when using this sourcing relationship. For a shipment, the load on the resource is calculated as:

(Item quantity / Rate)

Valid values for Rate are 0 or greater.

Caution: Do not specify a value of 0 if you want the system to generate a constrained plan based on the transportation resource for this TransMode/Source/Dest combination.


The resource utilization for this execution of the sourcing process.

Res Master Planning

The Inhandling, Outhandling, or Transportation resource associated with this lane. When using Vessel Scheduling, this resource is loaded during the fixed vessel schedule.


The resource associated with this sourcing process.

Source The source location for the sourcing method associated with this requirement.

Sourcing The name of the sourcing method associated with this requirement.

StepNum Master Planning

Step Number (StepNum) is the sequence number for this particular stage during the execution of the sourcing process.

• For an Outhandling resource, StepNum = 1

• For a Transportation resource, StepNum = 2

• For an Inhandling resource, StepNum = 3 JDA Enterprise Supply Planning Reference Guide 464 © 2014 JDA Software Group, Inc.- Confidential

SourcingRequirement


Step Number (StepNum) is the sequence number for this particular stage during the execution of the sourcing process.


SS

SS Table included with: Fulfillment, Master Planning, Supply, Flowcasting, Enterprise Supply Planning


Eff 3 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

DATETIME

Item 1 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT

Loc 2 FF, MP, Supp, Flowcasting, ESP (Deep Tree)

TEXT

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

INTEGER 0

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

DECIMAL 0

Table description Each row in this table defines the desired safety stock level for a particular SKU beginning at a specific date and time and continuing until a new level is specified.

The system uses this table only when the Safety Stock Rule is Manual (SKUSafetyStockParam:SSRule = 1). The system also uses the SS table for calculating projected safety stock.

Supply

Each row in this table defines a level of time varying safety stock over time for a particular SKU. Using the Calculate Supply Plan:General process, you can specify if you want to use time varying safety stock as a source of demand. With this option selected, the Calculate Supply Plan process considers demands from the SS table and the associated releases. When the level of a SKU as specified in this table increases, supply is created for the demand.

Whenever the time varying safety stock for a particular SKU falls below the immediately preceding level, the difference is treated as release and is used as supply to meet demand.

Column descriptions Eff The date and time at which this desired safety stock level becomes effective.

Item The item whose desired safety stock level is defined in this row.

Loc The location of the SKU whose desired safety stock level is defined in this row.


SS

OrderSeqNum Note: This column is not used in the current release.

Qty The desired safety stock level.

Note: Quantity cannot be a negative value.


SSBand

SSBand Table included with: Enterprise Supply Planning


BandCovDur ESP INTEGER 0

BandLevel 5 ESP NUMBER 0 to 99

BandQty ESP FLOAT 0 Eff 3 ESP DATETIME

Item 1 ESP TEXT Loc 2 ESP TEXT

Type 4 ESP INTEGER 1, 2

Table description This table defines the safety stock bands that enable fair-sharing an item across multiple locations, such that the defined safety stock levels are met to the maximum possible extent. The absolute safety stock levels are defined in the SKUEffInventoryParam (on page 314) table. The SSBand: Item, SSBand: Loc, and SSBand :Eff values are used to identify the item at a location that must be fair-shared. These values must match the SKUEffInventoryParam: Item, SKUEffInventoryParam: Loc, and SKUEffInventoryParam: Eff values.

Column description BandCovDur The safety stock level, associated with a fair-share level, in terms of time units.

BandLevel Identifier of a fair-share level. The safety stock level (BandQty or BandCovDur) associated with the lowest fair-share level is first met for all locations before trying to meet the safety stock level of the next fair-share level.

BandQty The safety stock level, associated with a fair-share level, in terms of quantity.

Eff The start date from which the inventory levels specified for Item are applicable.

Item The item that must be fair-shared across multiple locations.

Loc The location where the fair-shared item exists.

Type


SSBand

Specifies if the fair-share band defined by this row is a minimum (Type is 1) or maximum (Type is 2) band. If it is a minimum band, for a specified level, the BandQty and BandCovDur are the minimum safety stock levels that must be met. If it is a maximum band, for a specified level, the BandQty and BandCovDur are the maximum safety stock levels that must be met.


SSTemplate

SSTemplate Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


SSCalcDesc FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT ' '

SSTemplate 1 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT

Table description This table is used to define time-phased forward coverage for safety stock calculations. With time-phased forward coverage, you can specify a different forward coverage duration for different portions of the planning horizon for any SKU that uses Safety Stock Rule (SKU:SSRule) 2, 3, 4, 6, 7 and 8.

Each row in the SSTemplate table defines the name of a safety stock template. For each template defined, the SSTemplateData table defines the incremental forward coverage duration to be used in each time period. To assign a template to a SKU, enter the template name in SKUSafetyStockParam:SSTemplate.


This data can be populated by the Publish IPO Output process.

Column descriptions SSCalcDesc Safety Stock Calculation Description (SSCalcDesc) is the description of the safety stock template.

SSTemplate Safety Stock Template is the name of the safety stock template.


SSTemplateData

SSTemplateData Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning



DATETIME 01/01/1970

IncCovDur FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DURATION 0

IncMaxCovDur FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DURATION 0

RepeatDur FF, MP, IPO, Flowcasting, ESP (Deep Tree)

DURATION 0

RepeatOpt FF, MP, IPO, Flowcasting, ESP (Deep Tree)

BOOLEAN 0

SSTemplate 1 FF, MP, IPO, Flowcasting, ESP (Deep Tree)

TEXT

Table description This table is used along with the SSTemplate table to define time-phased forward coverage for safety stock calculations.

Each row in this table defines the incremental forward coverage duration to be used in a given time period when calculating safety stock for an SKU that is assigned to this SS Template through SKUSafetyStockParam:SSTemplate (on page 438).


This data can be populated by the Publish IPO Output process.

Column descriptions Eff The date and time when the coverage duration (SSTemplateData:IncCovDur) for this row takes effect. The IncCovDur specified in any row is in effect from the Effective Date of that row until the next Effective Date of a row for the same template.

For periods that fall prior to the earliest Effective Date, the system uses a value of zero both for the base forward coverage (in SKUSafetyStockParam:SSCov) and the incremental forward coverage (SSTemplateData:IncCovDur).


SSTemplateData

If you are using both an incremental and a maximum coverage duration, Effective Date applies to both the incremental coverage duration in IncCovDur and the maximum coverage duration in IncMaxCovDur.

IncCovDur Incremental Coverage Duration (IncCovDur) is the coverage duration to be added to the value in SKUSafetyStockParam:SSCov. The system adds the number of days of forward coverage specified in this row to the number of days of forward coverage in SSCov to get the total number of days of forward coverage, or the forward coverage duration. Forward coverage duration is used to calculate safety stock for SKUs that use Safety Stock Rules 2, 3, or 4 (SKUSafetyStockParam:SSRule = 2, 3, or 4).

Using either total demand (safety stock Rules 3 and 4) or adjusted demand (safety stock Rule 2), the system totals the units of demand within the forward coverage duration. For Rules 2 and 3, this number is the safety stock (SKU projection SS) as of SKU projection Date. For Rule 4, this number is added to the calculated statistical safety stock value (StatSS:Qty); the result is placed in SKU projection SS.

Each row in the following example defines a coverage duration for safety stock template SSTEMP1. The coverage duration is in effect from the Effective Date in a row until the Effective Date in the next row. So, from 1/1/04 until 1/30/04, IncCovDur is 10 days; the system adds 10 days’ forward coverage to the value in SKUSafetyStockParam:SSCov. From 1/31/04 to 5/9/04, IncCovDur is 0, so no additional days are added to SSCov during that time period. IncCovDur changes to 5 days beginning on 5/10/04, so the system adds 5 days’ forward coverage to SSCov.

Template Eff IncCov Dur Repeat Opt Repeat Dur Descr

SSTEMP1 01/01/04 10D Seasonal Cycle


SSTEMP1 5/10/04 5D Seasonal Cycle You can view the incremental coverage duration in SKU projection IncMinCovDur.

IncMaxCovDur Incremental Maximum Coverage Duration (IncMaxCovDur) defines an upper limit for forward coverage duration that you can use for purposes of comparison with the incremental coverage duration (SSTemplateData:IncCovDur) and the actual coverage duration SKU projection CovDur.

You can view IncMaxCovDur in both a SKUProjStatic and a SourceProj page.

If you define a repeating pattern for IncCovDur in SSTemplateData:RepeatOpt and SSTemplateData:RepeatDur, note that the maximum coverage duration does not respect the Repeat option. To vary the maximum coverage duration over time, you need to add a row to the SSTemplateData table for each date on which you want the duration to change.

RepeatDur The length of time for which the template repeats a defined pattern of coverage durations. The pattern continues to repeat until the Effective Date of a new coverage duration.

Valid values for RepeatDur are between 0 to 2103840.

You can specify any pattern of coverage durations, then repeat them by specifying a Repeat Duration that is exactly the length of the pattern.

For example, suppose you want to define a year’s worth of forward coverage durations with a pattern of longer durations for the fourth quarter to avoid stockouts during the Christmas rush. You would define the forward coverage you want to use for each period, then specify a repeating pattern of 365 days, as shown below:


SSTemplateData




SSTEMP1 5/10/04 5D Seasonal Cycle SSTEMP1 10/01/04 10D 4th Quarter SSTEMP1 11/15/04 15D 4th Quarter SSTEMP1 01/01/05 10D Y 365D Seasonal Cycle You can interrupt a repeating pattern, then resume the pattern as if it had not been interrupted. To do that, specify a RepeatOpt of Y but do not specify a repeat duration.

For example, suppose you want to define the same pattern as in the previous example, but also interrupt the pattern to specify longer coverage durations for a fall promotion. The SSTemplateData table would look like this:




SSTEMP1 5/10/04 5D Seasonal Cycle SSTEMP1 10/01/04 10D 4th Quarter SSTEMP1 11/15/04 15D 4th Quarter SSTEMP1 01/01/05 10D Y 365D Seasonal Cycle SSTEMP1 10/06/05 15D Start 25%

Discount SSTEMP1 10/20/05 Y End 25%

Discount

RepeatOpt Whether this option will repeat. If this column is set to Y, the template will begin or resume a repeat pattern.

SSTemplate Safety Stock Template (SSTemplate) is the name of the safety stock template. The safety stock template specified in this column must be defined in the SSTemplate table.


StatSS

StatSS Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


Eff 1 FF, MP, IPO, Flowcasting, ESP

DATETIME


TEXT


TEXT


DECIMAL 0.000000

Table description Each row in this table identifies the time-phased statistical safety stock value for a SKU.

This table is used both as an input and an output table. As an input table, it stores user-specified, time-phased statistical safety stock values from an external system.


As an output table, Publish IPO Output Process publishes time phased safety stock values

from IPOSKUPerformance (output table of IPO) to StatSS.

Fulfillment

As an output table, this table is populated by the Calculate Statistical Safety Stock process.

Column descriptions Eff The date and time at which the statistical safety stock defined in this row becomes active.

Item The item associated with the SKU for which statistical safety stock is defined in this row.

Loc The location associated with the SKU for which statistical safety stock is defined in this row.

Qty The level of statistical safety stock to be held for this SKU, effective at the date and time in StatSS:Eff (on page 474).


StockOrder

StockOrder Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning


AvailDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

CalcPriority FF, MP, Flowcasting, ESP

DECIMAL 0


TEXT


TEXT

MaxEarlyDur FF, MP, Flowcasting, ESP

DURATION 0

MaxLateDur FF, MP, Flowcasting, ESP

DURATION 0

NeedDate FF, MP, Flowcasting, ESP

DATETIME 01/01/1970

Priority FF, MP, Flowcasting, ESP

INTEGER -1

PrioritySeqNum FF, MP, Flowcasting, ESP

INTEGER 0

Qty FF, MP, Flowcasting, ESP

DECIMAL 0

SeqNum 3 FF, MP, Flowcasting, ESP

INTEGER

SupersedeSw MP, ESP BOOLEAN 0

Table description This table stores all safety stock orders that are created by the Generate Safety Stock Orders process using the SKUSafetyStockparam:SSRule and other safety stock parameters (defined in the SKUSafetyStockParam table). The safety stock orders are generated to replenish SKUs.

Fulfillment

The safety stock orders are required as inputs into the Generate Supply and Demand Links process.

Column descriptions AvailDate JDA Enterprise Supply Planning Reference Guide 475 © 2014 JDA Software Group, Inc.- Confidential

StockOrder

The date and time when this supply quantity is available to be used as supply. The AvailDate is computed based on the decreasing safety stock level for a SKU.

For example:

If the PlanStartDate = 5/31, PlanDur = 60 D, then:

The safety stock level in the SS (Safety Stock) table is:

Eff Qty

11-Jun 100

12-Jun 150

13-Jun 250

26-Jun 200

28-Jun 100

The corresponding stock orders generated in the StockOrder (Stock Order) table will be:

NeedDate AvailDate Qty MaxLateDur (in hours)

11-Jun 30-Jul 100 1176

12-Jun 28-Jun 50 384

13-Jun 28-Jun 50 360

13-Jun 26-Jun 50 312

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

Item The item associated with this order.

Loc The location associated with this order.

MaxEarlyDur The limit on how early this stock order may be met. The system sets MaxEarlyDur equal to the SKUSafetyStockParam:SSMeetEarlyDur during the execution of Generate Safety Stock Orders process.

The Master Planning process will not try to find supplies that will result in meeting this order earlier than:

StockOrder:NeedDate - StockOrder:MaxEarlyDur


MaxLateDur


StockOrder

The limit on how late this stock order will be met. Master Planning calculates this value for stock orders based on the safety stock levels that it is trying to maintain for the SKU. The Calculate Master Plan process will not try to find supply that will result in meeting this order later than:

StockOrder:NeedDate + StockOrder:MaxLateDur

If the Calculate Master Plan process cannot satisfy this demand within the specified duration, it stops trying to find supply to meet it.

The MaxLateDur can be expressed as:

StockOrder:AvailDate - StockOrder:NeedDate

NeedDate The date and time when this stock order is needed. This is also the date and time when the safety stock level changes from an existing level to a higher level.

Priority This value indicates the importance of this stock order in relation to all other stock orders. The Calculate Master Plan process uses this priority when determining which demand to satisfy first.

A value of 1 is most important and higher values are less important. A SKUSafetyStockParam:SSPriority value of 0 means that no priority has been set for this SKU, and the Calculate Master Plan process will use the Default Stock Order Priority, which is set on the Calculate Sigmoid Priority process page.

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

Qty The total number of units of the SKU specified by this order, using the unit of measure specified in Item:UOM. Master Planning calculates this value based on this SKU’s safety stock levels and safety stock rules.

SeqNum The sequence number generated for a stock order when you run the Generate Stock Orders process. This column can take values from 1 to n for a given SKU.

SupersedeSw Switch that indicates which stock order can be superseded.

• Y – Can be superseded

• N – Cannot be superseded.


StockOrderStatus

StockOrderStatus Table included with: Fulfillment, Master Planning, Flowcasting, Enterprise Supply Planning



DmdPlanTime MP INTEGER

ExpDate MP, ESP DATETIME 01/01/1970 HasExceptionSw MP, ESP BOOLEAN 0


TEXT


TEXT

ProcessSeqNum MP, Flowcasting, ESP

INTEGER


DATETIME 01/01/1970


DECIMAL 0

SchedStatus FF, MP, ESP OPTION_NUMBER

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

SeqNum 3 FF, MP, Flowcasting, ESP

INTEGER

Table description The stock order status record is updated by the following processes:

• Calculate Master Plan - This process updates stock order status of the Master Planning SKUs.

• Generate Supply and Demand Links based on Priority - When this process is run, it updates the stock order status of both Master Planning and Fulfillment SKUs based on the scope you select in the process page. In the case of Master Planning SKUs, it overwrites the status created by Calculate Master Plan process.

Column descriptions DmdPlanTime Time elapsed in milliseconds to process a demand. If the time taken to process a demand is less than a millisecond then it is reported as zero.

ExpDate The requirement expiration date of stock order.

HasExceptionSw The system sets this switch to Yes if it generates an exception for the stock order.


StockOrderStatus

Item The item associated with this stock order.

Loc The location associated with this stock order.

ProcessSeqNum The sequence number generated for a demand order by the Calculate Master Plan process.

SchedDate The date and time when this stock order is available. If this order is met on time, SchedDate is the same as NeedDate. If hard constraints prevent this order from being met on time, Master Planning sets SchedDate to the date when the demand is actually met.

SchedQty The stock quantity that can actually be supplied. If all the demand can be met, SchedQty is the same as Qty. If not, Master Planning sets SchedQty to the quantity that can actually be supplied.

SchedStatus Indicates whether the quantity (Qty) of this stock order has been met on time, early, or late; fully or partially met; or unmet.

• 1: Met

This stock order will be satisfied by the supply on or before the NeedDate. If SchedDate is before the NeedDate, the order has been satisfied from inventory.

• 2: Met Early

This stock order will be satisfied before the NeedDate, from a supply other than inventory.

• 3: Met Late

This order will be satisfied by the supply, but it will be late. SchedQty is the same as Qty, but SchedDate is later than NeedDate.


Only part of this demand quantity of this demand will be satisfied. SchedQty is less than Qty. You can calculate the unmet quantity as:

Qty - SchedQty

To find the supply orders that are meeting this demand, and determine the quantity being supplied by each order, use the OrderLink table.

• 5: Not Met

None of this stock order is satisfied by the supply.



The stock order is met on or before the needed ship date (ShipDate) by Plan Arrival.



This stock order is satisfied before the needed ship date (ShipDate) by Plan Arrival.




StockOrderStatus

This stock order will be satisfied after the needed ship date (ShipDate) by Plan Arrival. That is, the scheduled shipping date (SchedDate) is after the needed shipping date (ShipDate).



At least one order line item has a SchedStatus of 10 (Met Partially). Only part of the quantity of the order stock item is satisfied by the Plan Arrival. You can determine how much of the order line item is not satisfied by using this calculation:




SeqNum The unique sequence number stored in StockOrder table.


StorageRequirement

StorageRequirement Table included with: Production and Sourcing Optimization, Enterprise Supply Planning

Column name

PK Included with


EnableSw PSO, ESP (LPOPT)

BOOLEAN 1

Item 2 PSO, ESP (LPOPT)

TEXT

Loc 3 PSO, ESP (LPOPT)

TEXT

Res 1 PSO, ESP (LPOPT)

TEXT

Table description Each row in this table defines the storage resource associated with a SKU.

Column descriptions EnableSw Indicates if the storage resource will be used while running the Production and Sourcing Optimization Optimizer.

ESP (LPOPT)

Indicates if the storage resource is used when the Generate Master Plan (LPOPT) process is run.

Item The item associated with the SKU.

Loc The location associated with the SKU.

Res The storage resource associated with the SKU.


Supersession

Supersession Table included with: Fulfillment, Flowcasting, Master Planning and Enterprise Supply Planning.


Default value

AltItem 2 FF, Flowcasting, MP, ESP

TEXT

AltItemPriority FF, Flowcasting, MP, ESP

INTEGER 1

Disc 5 FF, Flowcasting, MP, ESP

DATETIME 01/01/1970

DmdUsageRule FF, MP, Flowcasting

OPTION_NUMBER

1

DrawQty FF, Flowcasting, MP, ESP

DECIMAL >0 1.0

Eff 4 FF, Flowcasting, MP, ESP

DATETIME 01/01/1970

Item 1 FF, Flowcasting, MP, ESP

TEXT

Loc 3 FF, Flowcasting, MP, ESP

TEXT ' '

RespectSSLevelSw

FF, Flowcasting

BOOLEAN 0

RoundingQty FF, Flowcasting

NUMBER >=0 1.0

UseUntilLevel FF, Flowcasting

INTEGER 0

MinAlllocQty FF, Flowcasting

DECIMAL

SupplyCap FF, Flowcasting

DECIMAL 0

Table description This table defines Supersession relationships, the transitional relationships between a product and a newer or promotional version of that product or between an obsolete product and a completely new product. There can be multiple obsolete relationships effective at the same time for the same item, or multiple promotional or circular relationships. However, the configuration is not supported where both an obsolete and a circular relationship are defined which reference the same item, even if the relationships are defined at isolated locations or during distinct time intervals.


Supersession

Define the relationship between the old product and the new product in this table only if you wish that the supply of the old one be used to satisfy the demand of the new one before replenishments of the new one are generated. Do not define a relationship in this table if the supply of the old product cannot be used for the demand of the new product.

Fulfillment and Flowcasting

For Calculate Plan Distribution and Deployment planning, you can specify which demand types on the new item may be met with supply of the old item. This is specified in the following columns: CustOrder:SupersedeSw, DFUToSKUFcst: SupersedeSw, SKUExternalFcst:SupersedeSw, SKUSafetyStockParam:SupersedeSSSw. All supplemental orders are treated as being supersedeable. However, the release of a supplemental order or the release of supersedable safety stock is used by Plan logic to meet any supersedable or non-supersedable demand type.

These columns are not respected by Order Optimization; all demands are supersedable in Order Optimization.

Supersession logic is respected in Calculate Plan Distribution Planning and Recommended Shipments logic as well as in Order Optimization. In Calculate Plan, if Item:PerishableSw is set to Yes for an item, then the Supersession relationships that are defined for that item will be disregarded. Some of the other options or rules within Distribution Planning and Deployment may also not be supported in conjunction with relationships defined in this table.

See the Planning for product transitions with Supersession chapter in the JDA Fulfillment OnLine Expert.

Column descriptions AltItem The alternate or supply item that you are willing to consume to satisfy the demand of the item defined in this row.

AltItemPriority The value in this column defines the sequence in which excess inventory is consumed if there are multiple supply items available to meet demand for a product. Specify this value only if you are modeling a many-to-one Supersession scenario.

For example, if you are transitioning from product A to B, then to C, there may be multiple transition relationships defined for how to meet demand for C. In other words, you might meet demand for C with supply of A or supply of B. In this case, while planning C, if supplies of multiple AltItems (A and B) are available to meet a demand of C, the system selects the supply of the AltItem with the higher AltItem priority. A value of 1 signifies the highest priority, and higher values are of lower priority.

Disc Specifies the hard-stop date for the transition relationship defined in this row. The relationship ends when this date is reached or when the inventory level of the supply SKU reaches the level defined in Supersession:UseUntilLevel. If the value in this column is blank, the system assumes that the relationship will continue until it reaches the level in UseUntilLevel or until it reaches the SKUProjStatic:SS level, depending on the setting in Supersession:RespectSSLevelSw.

ESP

Specifies the hard-stop date for the transition relationship defined in this row. The relationship ends when this date is reached.



01/01/1970 01/01/1970 Effective


Supersession




DmdUsageRule The rule that allows you to determine if the relationship defined in this row will apply to independent demand only, or distribution demand and dependable demand as well.

• 1: All demand (default)

• 2: Independent demand, only

Note: At this time, this rule is not supported by Optimize Orders process. All demands are considered supersedable by the Optimize Orders process regardless of this rule and the SupersedeSw column on the various other demand tables.

DrawQty This value represents the amount of Alternate Item consumed for every unit of Supersedable demand on the Primary Item.

The default value for draw quantity is 1.

Eff The date and time at which the transitional relationship defined in this row can begin. If the value in this column is blank, the system assumes that this relationship is effective immediately.

Item A new or promotional version of an item for which there is demand, and for which you are willing to use supply of another item as defined in Supersession:AltItem.

Loc The location at which the product transition occurs. This is an optional setting. If this column is blank, the transitional relationship applies to all locations where the items defined in this row exist. If there is another row defined with the same items but with a location specified, that relationship takes priority over the global setup if rules vary between the two.

MinAllocQty Note: This column is not used in this release.

RespectSSLevelSw Respect Safety Stock Level Switch (RespectSSLevelSw) tells SKU Supersession logic whether to respect safety stock levels for the transition from the supply SKU or not.

• Y: Respect safety stock levels at the supply SKU

• Blank (No): Do not respect safety stock levels at the supply SKU

If the value in this column is set to Y, Supersession logic will reserve a component of inventory at the supply SKU equal to its safety stock target, and will only allocate to other items any supply in excess of that amount.

RoundingQty


Supersession

Represents the rounding increment that is used by Supersession logic when creating transfers in Calculate Plan and Deployment. If this value is greater than zero, then the values of PlanProxyInventory:Qty and RecSubInventory:Qty will always be multiples of this value.

The default value is 0.

SupplyCap Note: This column is not used in this release.

UseUntilLevel Defines the level to which you want the system to exhaust supply inventory for this SKU. Supersession logic consumes older product inventory to this level depending on the settings in Supersession:RespectSSLevelSw or the SKU projection SS level as of SKU projection Date, whichever comes first.

Note: At this time, this level is not supported by Optimize Orders process.


TimeHorizon

TimeHorizon Table included with: Enterprise Supply Planning


Day 1 ESP DATE

DayDescr ESP VARCHAR2(100 CHAR)

‘ ’

Week ESP VARCHAR2(30 CHAR)

WeekDescr ESP VARCHAR2(100 CHAR)

‘ ’

Month ESP VARCHAR2(30 CHAR)

MonthDescr ESP VARCHAR2(100 CHAR)

‘ ’

Qtr ESP VARCHAR2(30 CHAR)

QtrDescr ESP VARCHAR2(100 CHAR)

‘ ’

Year ESP VARCHAR2(30 CHAR)

YearDescr ESP VARCHAR2(100 CHAR)

‘ ’

Table description Each row in the TimeHorizon table defines the time hierarchy of the day and its relevant buckets in the hierarchy.

Column descriptions Day Value used to identify the date. The format is MM/DD/YYYY.

Example: 8/1/2013

DayDescr Value used to identify the Day field description. The format is DD/MON/YY.

Example: 01-AUG-13

Week Value used to identify the underlying days in the week.


TimeHorizon

For example: 29-JUL-13 is the weekly bucket, starting from 29 July to August 4 .

WeekDescr Value used to identify the Week field description.

Month Value used to identify the underlying days and weeks in the month.

MonthDescr Value used to identify the Month field description.

Qtr Value used to identify underlying days, weeks, and months in the quarter.

QtrDescr Value used to identify the Qtr field description.

Year Value used to identify underlying days, weeks, months, and quarters in the year.

YearDescr Value used to identify the Year field description.


TransMode

TransMode Table included with: Fulfillment, Master Planning, Supply, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


AltShipCap Flowcasting DECIMAL 999999999.0

Descr IPO, Flowcasting, ESP

TEXT ' '

NumTrailers Flowcasting DECIMAL 0 PalletsPerVehicle Flowcasting DECIMAL 999999999.0 QtyCap Flowcasting DECIMAL 999999999.0 TransMode 1 FF, MP, Supp,


TEXT

VolCap Flowcasting DECIMAL 999999999.0

WgtCap Flowcasting DECIMAL 999999999.0

Table description Each row in this table defines a mode of transportation, such as truck, rail, or tank-car.

Supply

This is a reference only table.

Column descriptions AltShipCap Note: This column is not used in this release.

Descr Note: This column is not used in this release.

NumTrailers Note: This column is not used in this release

PalletsPerVehicle Note: This column is not used in this release.

QtyCap Note: This column is not used in this release.

TransMode The mode of transportation defined in this row.

Supply


VolCap Note: This column is not used in this release.

WgtCap JDA Enterprise Supply Planning Reference Guide 488 © 2014 JDA Software Group, Inc.- Confidential

TransMode

Note: This column is not used in this release.


VehicleLoad

VehicleLoad Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply, Planning


ApprovalStatus FF, Flowcasting BOOLEAN 0

ArrivDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

ConsolidatedLoadSeqNum


Descr FF, MP, IPO, Flowcasting, ESP

TEXT ' '

DestStatus FF, MP, IPO, Flowcasting, ESP

OPTION_NUMBER

1,2,3 1

Exported FF, Flowcasting BOOLEAN 0

GroupOrderID FF INTEGER 0 LaneGroupID FF, Flowcasting TEXT ' ' LaneGroupMinMetSw


LBSource FF, Flowcasting INTEGER 0

LBStatus FF, Flowcasting INTEGER 1 LoadID 1 FF, MP, IPO,

Flowcasting, ESP

TEXT

LoadSw FF, Flowcasting BOOLEAN 1 LSRuleMetSw FF, Flowcasting BOOLEAN 0 MaxCapacityExceededSw


MaxCapacityMetSw

FF BOOLEAN 0

OrderID FF INTEGER

OrderOptSeqNum

FF INTEGER 0

ShipDate FF, MP, IPO, Flowcasting, ESP

DATETIME 01/01/1970

SourceStatus FF, MP, IPO, Flowcasting, ESP

OPTION_NUMBER

1,2,3 1

StatusDescr FF, MP, Flowcasting, ESP

TEXT ' '


VehicleLoad


ToleranceCapMetSw


TransMode FF, MP, Flowcasting, ESP

TEXT ' '

TransModeMinMetSw


Updated FF, Flowcasting BOOLEAN 0

VendorMinMetSw


Table description Each row in this table defines a vehicle load. A vehicle load consists of one or more items being shipped on a single vehicle (by a specific transportation mode, such as truck or rail) between a specified source and destination. The actual items included in the load are defined in the VehicleLoadLine table.

If you have the Fulfillment/Deployment component, you can use the Build Transportation Loads process to create loads. If not, you can import loads from another system.

IPO

IPO users only need to populate this table if they intend to use the replenishment plan cost model. Note that IPO does not use the SKUProjStatic or SKUStatStatic tables.

Column descriptions ApprovalStatus Indicates that this load is approved for export to an external system.

ArrivDate The date when this load is scheduled to arrive at the destination location.


This must be an open date in the finish calendar (SupplyMethod:FinishCal) used by the SupplyMethod associated with each vehicle load line in this load (unless the load line uses VehicleLoadLine:RevisedDate instead of ArrivDate).

ConsolidatedLoadSeqnum Consolidated Load Sequence Number links various loads that are part of the same consolidated load.

Desc Description of this load.

DestStatus Option that indicates whether the quantities associated with this load (through the VehicleLoadLine table) have been received and whether they have been added to on hand at the destination.

• 1: Not Received, Not Part of Destination On Hand

The quantities associated with this load have not been received and are not included in SKU:OH for the destination SKU.


VehicleLoad

If SourceStatus (on page 494) is 1, the load quantities are included in the destination's SKUProjStatic:CommitIntransIn. If SourceStatus (on page 494) is 2 or 3, the load quantities are included in SKUProjStatic:ActualIntransIn.

If ArrivDate (on page 491)is greater than SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank), the system calculates the destination's SKUProjStatic:ProjOH as SKU:OH plus the load quantities as of ArrivDate (on page 491).

If ArrivDate (on page 491) is less than or equal to OHPost, the load quantities are included in the destination's SKUStatStatic:LateIntransIn. When calculating SKUProjStatic:ProjOH, the system adds the load quantities to SKU:OH as of SKU:OHPost (or Loc:OHPost).

• 2: Received, Not Part of Destination On Hand

The quantities associated with this load have been received but are not included in SKU:OH for the destination SKU.

If SourceStatus (on page 494) is 1, the load quantities are included in the destination's SKUProjStatic:CommitIntransIn. If SourceStatus (on page 494) is 2 or 3, the load quantities are included in SKUProjStatic:ActualIntransIn.

If ArrivDate (on page 491) is greater than SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank), the system calculates the destination's SKUProjStatic:ProjOH as SKU:OH plus the load quantities as of ArrivDate (on page 491).

If ArrivDate (on page 491) is less than or equal to OHPost, the load quantities are included in the destination's SKUStatStatic:LateIntransIn. When calculating SKUProjStatic:ProjOH, the system adds the load quantities to SKU:OH as of SKU:OHPost (or Loc:OHPost).

With a DestStatus of 2, the load should have a SourceStatus (on page 494) of 2 or 3.

• 3: Received, Part of Destination On Hand

The quantities associated with this load have been received and are included in SKU:OH for the destination. When the system calculates values for SKUProjStatic:ProjOH, it will not add the load quantities to SKU:OH. The load quantities are not used in calculating intransits in.

Note: With a DestStatus of 3, the load should have a SourceStatus (on page 494) of 2 or 3. If you set the DestStatus to 3 when the SourceStatus is 1 then the system treats the DestStatus as 1 only.

ExpDate Expiration date of vehicle load.

Exported Indicates if the load defined in this row has been exported through an export page. This column allows the system to distinguish between loads that have already been exported to an external system and loads that have not. Load Manager and Build Transportation Loads process automatically set this column to No when a load record is created or updated. You can then set this column to Yes when the load record is exported.

GroupOrderID The Group Order ID associated with this vehicle load.

LaneGroupID Unique identifier of the lane group.

LaneGroupMinMetSw Lane Group Minimum Met Switch indicates whether the load meets the applicable lane group minimum. It is applicable for consolidated multi pick up loads only.

LBSource Indicates the source, or origin, of this load.


VehicleLoad

• 1 - Imported (set by user)

Imported from an external system.

• 2 - ALB (automatically set by Build Transportation Loads process)

Created by Build Transportation Loads process.

• 3 - Load Manager (default)

Created by Load Manager.

• 4 - Other (set by user)

Manually entered into the VehicleLoad table.

• 6 - Optimize Orders process

Created by the Optimize Orders process.

LBStatus Option that indicates the results of running an Build Transportation Loads process. Build Transportation Loads process assigns a status to each load that it writes to the VehicleLoad table. This column contains the status number. VehicleLoad:StatusDesc contains a description of the status.

LBStatus will contain one of the following values:

• 1: No errors

• 2: Not full

• 3: Not primary transmode

• 4: Not full, not primary transmode

If the load was not created by Build Transportation Loads process —if it was created by Load Manager or imported into the system, for example—this column will be set to 1 (No errors).

Refer to VehicleLoad:StatusDesc for details.

LoadID Unique identifier of the load defined in this row. LoadID cannot be blank. If the LoadID is not provided by the user, then the LoadID is obtained from the value in DBParam:LoadID, and the DBParam value is incremented.

LoadSw Load Switch indicates whether the algorithm can create additional load lines on an imported load. The load building algorithm tries to fill up existing loads (imported loads) before creating new loads. If the load switch is set to “Yes” for a given load, it indicates that the algorithm can create additional load lines on the imported load.

LSRuleMetSw Load Satisfaction Rule Met Switch indicates whether the load has met the applicable load satisfaction criteria. A value of 1 indicates that the load has met the load satisfaction criteria.

MaxCapacityExceededSw Maximum Capacity Exceeded Switch indicates whether the load is above capacity. A value of 1 indicates that the load is above the load capacity.

Note: This column is used by only Fulfillment/Order Optimization.

MaxCapacityMetSw Maximum Capacity Met Switch indicates whether the load is 100% full. A value of 1 indicates that the load is 100% full.

OrderID


VehicleLoad

The unique identifier for the Order in this vehicle load.

OrderOptSeqNum The sequence number of this vehicle load in the set of vehicle loads for the OrderID in the row.

ShipDate The date when this load left or is expected to leave the source. (This is not the date when stock was pulled from inventory.)

SourceStatus Option that indicates whether the quantities associated with this load (through the VehicleLoadLine table) have been shipped and whether they have been deducted from on hand at the source.

• 1: Part of Source On Hand, Not Shipped

The quantities associated with this load are still included in the source SKU's On Hand (SKU:OH), and the load has not been shipped. The system will use the load quantities in calculating Committed Intransits Out (SKUProjStatic:CommitIntransOut) and Current Reserved On Hand (SKUStatStatic:CurReservedOH) for the source SKU.

If SchedDate is greater than SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank), the system calculates the source's SKUProjStatic:ProjOH by subtracting load quantities from SKU:OH as of the ship date.

If SchedDate is less than or equal to OHPost, the load is included in the source's Unmet Intransits Out (SKUStatStatic:UnmetIntransOut). To calculate SKUProjStatic:ProjOH, the system subtracts the load quantities from SKU:OH as of SKU:OHPost (or Loc:OHPost).

With a SourceStatus of 1, the load should have a DestStatus (on page 491) of 1 (Not Received).

• 2: Part of Source On Hand, Shipped

The quantities associated with this load are still included in the source's SKU:OH, but the load has been shipped. The load quantities are included in SKUProjStatic:ActualIntransOut for the source SKU.

If SchedDate is greater than SKU:OHPost (or Loc:OHPost if SKU:OHPost is blank), the system will calculate the source's SKUProjStatic:ProjOH for the source SKU as SKU:OH minus the load quantities as of ship date.

If SchedDate is less than or equal to OHPost, the load is included in the source's Unmet Intransits Out (SKUStatStatic:UnmetIntransOut). To calculate SKUProjStatic:ProjOH, the system subtracts the load quantity from SKU:OH as of SKU:OHPost (or Loc:OHPost).

• 3: Not Part of On Hand, Shipped

The quantities associated with this load are not included in the source's SKU:OH.

When the system calculates values for the source's SKUProjStatic:ProjOH, it will not subtract the load quantities from SKU:OH. The load quantity is not used in calculating intransits out for the source SKU.

StatusDescr Contains a description that corresponds to a status value in the LBStatus (on page 493) column. The Build Transportation Loads process writes the status description in this column and the status number in LBStatus (on page 493) for every load that it writes to the VehicleLoad table. This column contains one of the following descriptions:

ToleranceCapMetSw ToleranceCapMetSw indicates whether this load is within the applicable capacity tolerance criteria. A value of 1 indicates that the load is within tolerance.

TransMode The mode of transportation for this load, such as rail or a specific size of truck.


VehicleLoad

TransmodeMinMetSw TransmodeMinMetSw indicates whether this load meets the applicable transmode minimum. A value of 1 indicates that the transmode minimum has been met.

Updated When you work with Load Manager and edit a load, you can set this column to indicate that the load has been changed by Load Manager.

• Y—you changed this load using Load Manager.

• N—you did not change this load using Load Manager.

VendorMinMetSw VendorMinMetSw indicates whether this load meets the applicable vendor minimum. A value of 1 indicates that the vendor minimum has been met.


VehicleLoadLine

VehicleLoadLine Table included with: Fulfillment, Master Planning, Inventory Policy Optimization, Flowcasting, Enterprise Supply Planning


Action FF, MP, Flowcasting

OPTION_NUMBER

0,1,2,3 0

ActionAllowedSw FF, MP, Flowcasting

BOOLEAN 0

ActionDate FF, MP, Flowcasting

DATETIME 01/01/1970

ActionQty FF, MP, Flowcasting

DECIMAL 0

CancelSw FF, Flowcasting BOOLEAN 0

Dest FF, OP/ATP, MP, IPO, Flowcasting, ESP

TEXT ' '

DrawQty FF, MP, Flowcasting

DECIMAL 1.0

ExpDate 3 FF, MP, IPO, Flowcasting

DATETIME 01/01/1970

GroupOrderID FF INTEGER 0


TEXT

LBSource FF, Flowcasting OPTION_NUMBER

1,2,3,4,5,6 1

LoadID 1 FF, MP, IPO, Flowcasting, ESP

TEXT

LoadLineID FF, Flowcasting DECIMAL 0

MustGoQty FF, Flowcasting DECIMAL 0 OrderID FF INTEGER OrderNum MP,

Flowcasting, ESP

INTEGER 0

PrimaryItem 2 FF, MP, IPO, Flowcasting, ESP

TEXT

PrimaryItemQty FF, Flowcasting DECIMAL 0


DECIMAL 0



VehicleLoadLine


RevisedDate MP, Flowcasting DATETIME 01/01/1970

SchedArrivDate FF, Flowcasting DATETIME 01/01/1970

SchedShipDate FF, Flowcasting DATETIME 01/01/1970 SeqNum FF, Flowcasting,

ESP INTEGER 0

Source FF, OP/ATP, MP, IPO, Flowcasting, ESP

TEXT

Sourcing FF, MP, IPO, Flowcasting, ESP

TEXT ' '

SupplyID FF TEXT

SupplyMethod Not used in this release

DECIMAL 0

SuppOrderQty FF, Flowcasting DECIMAL 0

Table description Each row in this table identifies an item that is part of a load identified in the VehicleLoad table.

Fulfillment

If you have the Fulfillment/Deployment component, you can use the Build Transportation Loads process to create vehicle loads. If not, you can import loads from another system.


The Generate Supply and Demand Links based on Priority process of Master Planning/Fulfillment and Generate Supply and Demand Links process of Master Planning use this table to recommend that a vehicle load line be cancelled, or that its SchedDate be changed, to prevent the generation of additional unneeded supplies.

IPO


ESP (MAP and LPOPT)

The Generate Master Plan(MAP) and Generate Master Plan(LPOpt) processes require a valid sourcing to be defined in this table, to place a distribution demand at source.

Column descriptions Action For Master Planning/Fulfillment, it is the action (Push, Pull, or Cancel) recommended by the Generate Supply and Demand Links/Generate Supply and Demand Links based on Priority process when the supply ActionAllowedSw is enabled:

• 0: None

• 1: Pull

• 2: Push


VehicleLoadLine

• 3: Cancel

ActionAllowedSw If the ActionAllowedSw = 0, the vehicle load line will be recognized at the SchedDate/ArrivDate. If the ActionAllowedSw = 1, the vehicle load line will be recognized at the RevisedDate.




CancelSw This column is no longer used in this release.

Dest The location associated with the destination for this load. The value must be a valid location in the Loc table.

DrawQty The quantity of the substitute item that is equivalent to a single unit of the primary item when the load was created from a substitute recommended shipment. With a substitute shipment, PrimaryItem (the item whose demand is being met by this shipment) and Item (the item that is being shipped to cover the demand of PrimaryItem) contain different item numbers. This discrepancy indicates that the demand of the primary item is being met by a substitute item.

ExpDate The date on which the intransit replenishment for this SKU expires.

IPO, Master Planning


GroupOrderID The Group Order ID associated with this vehicle load line.

Item An item in this load that is being shipped. Must be a valid item in the Item table.

Fulfillment, Master Planning

If PrimaryItem (on page 499) is not equal to item, then the item in this row is used to cover the demand of PrimaryItem (on page 499).

LBSource Indicates the source, or origin, of this load.

• 1 - Imported (set by user)

Imported from an external system.

• 2 - Build Transportation Loads process (automatically set by the process)

Created by the Build Transportation Loads process

• 3 - Load Manager (default)

Created by Load Manager

• 4 - Other (set by user)


VehicleLoadLine

Manually entered into the VehicleLoad table.

• 5 - Modified by BTL

Existing load lines modified by Build Transportation Loads process

• 6 - Optimize Orders process

Created by the Optimize Orders process

LoadID Identifier of the load to which this item belongs. Must be a valid load in the VehicleLoad table.

Fulfillment

Unique identifier for the load. When the Build Transportation Loads process is used to create loads, the load ID includes the suffix defined in the DBParam:LoadID column.

LoadLineID Identifier of the load line.

Note: LoadLineID is not used in the current release.

MustGoQty MustGo Quantity indicates the amount of the load line created by a MustGo RecShip.

OrderID The unique identifier for the Order in this vehicle load.

OrderNum The sequence number generated for the VehicleLoadLine by the Calculate Master Plan process.

PrimaryItem The item whose demand is being covered by this load.

The item number in this column and in the Item column determine whether this load was created from a standard recommended shipment or from either a superseded or substitute recommended shipment.

If the load was created from a standard recommended shipment, an item is being shipped to meet demand for the same item at the destination. (VehicleLoadLine:Item and VehicleLoadLine:PrimaryItem contain the same item numbers.)

If the load was created from either a superseded or substitute recommended shipment, an item is being shipped to meet demand for a different item at the destination. (VehicleLoadLine:Item and VehicleLoadLine:PrimaryItem contain different item numbers.)

In the JDA Fulfillment/Deployment OnLine Expert, see Deploying alternate items for detailed information on substitute shipments.

PrimaryItemQty This field is only meaningful for Superseded VehicleLoadLine records, that is, records where PrimaryItem <> Item. This quantity represents the units of demand of the Primary Item that this VehicleLoadLine record meets. This quantity is equal to VehicleLoadLine: Qty (on page 499)/Supersession: DrawQty (on page 484).

IPO


Qty The number of units of this item.

RevisedExpDate


VehicleLoadLine

The revised expiry date of the intransit replenishment. If ActionAllowedSw = 1, then RevisedExpDate is calculated as:

RevisedExpDate = RevisedDate + difference between scheduled supply exp date and scheduled date.


RevisedDate This is the available date after constraining this vehicle load line as per the Firm Supply Constraint option (Only Material, Only Capacity or Both Material and Capacity). The Firm Supply Constraint option, necessary for processing scheduled supplies, is set on the Calculate Master Plan process page. The supply will be recognized at the RevisedDate if the ActionAllowedSw = 1. Else, the supply will continue to be recognized at the VehicleLoad:ArrivDate.

If the Firm Supply Constraint option is Capacity only: RevisedDate is the greater of the ArrivDate and the capacity loading completion date, irrespective of the material available date.

If the Firm Supply Constraint option is Material only: RevisedDate is the greater of the ArrivDate and the material available date, irrespective of the capacity loading completion date.

If the Firm Supply Constraint option is Capacity & Material: RevisedDate is the greater of the ArrivDate and the date when adequate capacity and material are both available for the successful processing of the scheduled supply.

SchedArrivDate SchedArrivDate of the load line obtained by adding unload duration (applied over open instances of the destination SKU’s working calendar) to VehicleLoad:ArrivDate.

SchedShipDate SchedShipDate of the load line obtained by subtracting load duration (applied over open instances of source SKU’s working calendar) to the VehicleLoad:ShipDate.

SeqNum Sequence Number of the load line used to identify the deployment priority and deployment demand details associated with the RecShip.

Source The location associated with the source for this load.

Sourcing The name of the sourcing method associated with this vehicle load line.

SupplyID Represents a unique ID for the supply that is used by the Dynamic Allocation logic.

SuppOrderQty Supplemental Order Quantity indicates the sum of the SuppOrderQty values of the recommended shipments for which the VehicleLoadLine was created to fulfill. This reflects the portions of those RecShips that were allocated to meet supplemental order demands at the destination.


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 Enterprise Supply Planning Reference Guide 511 © 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 Enterprise Supply Planning Reference Guide 518 © 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


Process: input and output tables

Chapter 4. Process: input and output tables Table Name Processes

Level SKUs

Transfer

Forecast

Generate

Forecast

Order

Generate

Stock Order

Calculate

Sigmoid

Priority

Calculate

Rules Based

Priority

Calculate

Master Plan

Order Pegging without priority

Order Pegging

with priority

Optimize Productio

n Changeov

er

Publish OPC

AggSKUProjStatic AltBOM AltProductionStep AvgDmd BOM I I Cal I O CalAttribute CalData I O CalInterval CalPattern Cust I I I CustOrder I IO IO I I I CustOrderHeader I I IO CustOrderStatus O IO O DBParam I DepDmdStatic O IO IO DFUToSKU I DFUToSKUFcst O I DFUToSKUSeasonErr DFUView DmdVar ExceptionCatagoryAssoc

I



ExceptionSeverity I ExceptionOrderRelation O Fcst I FcstOrder O IO IO I I I FcstOrderStatus O IO O ImpDepDmdStatic I ImpResLoadDetail I IndDmdLink O O IndDmdOrderView I IndDmdView IO I Inventory I I I Item O I I I Loc I I LPDmdBands LPLayer MSE Network I OrderLink IO IO PlanArriv IO IO IO PlanOrder IO IO IO PlanProxyInventory O PlanPurch IO IO IO ProductionFamily I ProductionFamilyChgOver

I

ProductionFamilyLoad O I ProductionFamilySKULoad

O

ProductionMethod I ProductionStep I I O ProductionYield I PurchMethod I



PurchOrder IO IO IO Res I I O ResException O O ResLoadDetail O IO IO I O ResProjStatic SchedRcpts IO IO IO SchedRcptsDetail SeasonError SKU O I IO I I SKUDemandParam I I I I SKUEffInventoryParam SKUException O O SKUExternalFcst I SKUHist SKUHistFcst SKUPerishableParam I SKUPlanningParam I I I SKUProjStatic SKUSafetyStockParam I I I SKUStatStatic Sourcing I I SourcingRequirement I SourcingTarget I SS I SSBand SSTemplate I SSTemplateData I StatSS I StockOrder O IO IO I I I StockOrderStatus O IO O StorageRequirement



Supersession I TimeHorizon TransMode I TransportSched I VehicleLoad I I I VehicleLoadLine IO IO IO

Table Name Processes

Generate Master Plan

(MAP)

Generate Master Plan (LpOpt)

Transfer Calendar Generate Time Horizon

AggSKUProjStatic AltBOM I I AltProductionStep I I AvgDmd BOM I I Cal I I I CalAttribute I I I CalData O CalInterval I CalPattern I I I Cust I I CustOrder I I CustOrderHeader I I CustOrderStatus O O DBParam DepDmdStatic O O DFUToSKU DFUToSKUFcst DFUToSKUSeasonErr DFUView





(MAP)



DmdVar ExceptionCatagoryAssoc

I I

ExceptionSeverity ExceptionOrderRelation O O Fcst FcstOrder I I FcstOrderStatus O O ImpDepDmdStatic I I ImpResLoadDetail I I IndDmdLink O O IndDmdOrderView I I IndDmdView Inventory I I Item I I Loc I I LPDmdBands I LPLayer I MSE Network I I OrderLink O O PlanArriv IO IO PlanOrder IO IO PlanProxyInventory O O PlanPurch IO IO ProductionFamily ProductionFamilyChgOver





(MAP)



ProductionFamilyLoad ProductionFamilySKULoad

ProductionMethod I I ProductionStep I I ProductionYield I I PurchMethod I I PurchOrder I I Res I I ResException O O ResLoadDetail O O ResProjStatic SchedRcpts I I SchedRcptsDetail I I SeasonError SKU I I SKUDemandParam I I SKUEffInventoryParam I I SKUException O O SKUExternalFcst SKUHist SKUHistFcst SKUPerishableParam I I SKUPlanningParam I I SKUProjStatic SKUSafetyStockParam I I SKUStatStatic





(MAP)



Sourcing I I SourcingRequirement I I SourcingTarget SS SSBand I SSTemplate SSTemplateData StatSS StockOrder O O StockOrderStatus O O StorageRequirement I Supersession I I TimeHorizon O TransMode I I TransportSched VehicleLoad I I VehicleLoadLine I I



Index 1 1 = None • 303

2 2 = Customer orders • 304

3 3 = Maximum, follow customer order curve • 304

4 4 = Maximum, reallocate unmet forecast • 305

5 5 = Carry backward • 307

6 6 = Short term customer orders • 308

7 7 = Short term customer orders and forecast • 308

8 8 = Dynamic Demand Response (DDR) Integration • 309

A Abbr • 239, 453 AccumDur • 430 Action • 192, 198, 206, 214, 244, 279, 497 ActionAllowedSw • 198, 206, 214, 244, 279, 498 ActionDate • 198, 206, 214, 244, 279, 498 ActionQty • 198, 206, 214, 245, 279, 498 ActualIntransIn • 29, 393 ActualIntransOut • 29, 394 AdjAllocAggMktActvtyFcst • 29, 394 AdjAllocAutoFcst • 29, 394 AdjAllocBaseFcst • 29, 394 AdjAllocDataDrvnFcst • 29, 394 AdjAllocMktActvtyFcst • 29, 394 AdjAllocNonBaseFcst • 29, 394 AdjAllocOvrideFcst • 29, 394 AdjAllocReconcileFcst • 29, 394 AdjAllocTargtImpactFcst • 29 AdjAllocTargtlmpactFcst • 394 AdjAllocTotalLockFcst • 29, 394 AdjAllocTotFcst • 29, 395

ADJBias • 178 ADJCV • 178 AdjDmdPostDate • 107 AdjFactor • 248 AdjFcstCustOrders • 29, 395 AgeFactor • 355 AggMktActvtyCustOrders • 29, 395 AggMktActvtyFcst • 29, 395 AggNegConstrProjOH • 395 AggNegProjOH • 395 AggPosConstrProjOH • 395 AggPosProjOH • 395 AggSKUProjStatic • 11 AggSKURule • 362 AggValue • 29 AllDmd • 30, 395 AllIntransIn • 30, 395 AllocAggMktActvtyFcst • 30, 395 AllocAutoFcst • 30, 396 AllocBaseFcst • 30, 396 AllocBatchSw • 362 AllocCal • 299 AllocCalGroup • 301 AllocDataDrvnFcst • 30, 396 AllocFactor • 118 AllocMktActvtyFcst • 30, 396 AllocNonBaseFcst • 30, 396 AllocOvrideFcst • 30, 396 AllocPolicy • 165 AllocReconcileFcst • 30, 396 AllocTargtImpactFcst • 30 AllocTargtlmpactFcst • 396 AllocTotalLockFcst • 30, 396 AllocTotFcst • 30, 396 AllocTotFcstNoProration • 397 AllocWgt • 69 AllowEarlyArrivSW • 431 AllowEarlyOrderSW • 431 AltBOM • 46 AltCal • 70 AltConstCantMeetQty • 397 AltConstrainedUnuseOH • 30, 397 AltConstrCovDur • 30, 397 AltConstrOverStockDate • 444 AltConstrOverStockDur • 444 AltConstrOverstockExcessCovDur • 444 AltConstrOverstockInvStartDate • 444 AltConstrOverstockQty • 444



AltConstrPOH • 30, 397 AltConstrStockLowDate • 444 AltConstrStockLowDur • 444 AltConstrStockLowQty • 444 AltConstrStockOutDate • 444 AltConstrStockOutDur • 444 AltConstrStockOutQty • 445 AltConstrUnuseableSupply • 398 AltConstrUseableProjOH • 398 AltItem • 211, 483 AltItemPriority • 483 AltPlantID • 172 AltProductionStep • 49 AltRes • 49 AltShipCap • 488 AltSubConstProjOH • 30, 398 AltSubord • 46 AltSubordDisc • 46 AltSubordEff • 46 AltSupsdConstrProjOH • 31, 398 AltSuspdConstrProjAvail • 398 Applications that include the table • 4 Applications that use the columns • 5 ApprovalStatus • 491 ApproveSw • 245 ArrivalPostDate • 431 ArrivCal • 182, 239, 454 ArrivDate • 491 ATP • 31, 398 ATPDur • 362 ATPRule • 362 Attribute • 67 AutoApprovalSw • 182 AutoCustOrders • 31, 399 AutoFcst • 31, 399 Avail • 72 AvailCap • 272 AvailDate • 131, 162, 475 AvailShipOH • 31, 399 AvailToShipDate • 198 AvgCycleStock • 31, 399 AvgDmd • 52 AvgDmdCal • 431 AvgDmdLookBwdDur • 431 AvgDmdLookFwdDur • 431 AvgFamilyChg • 248 AvgFamilyChgCost • 249 AvgIntransitStock • 31, 399

AvgLeadTime • 431 AvgNumLines • 431 AvgSKUChg • 249 AvgSKUChgCost • 249

B BackOrders • 445 BandCovDur • 468 BandLevel • 468 BandQty • 468 BaseCustOrders • 31, 399 BaseFcst • 31, 354, 399 BaseHist • 31, 400 BatchNum • 131, 255, 318 BOM • 54 BOMNum • 47, 55, 99, 219, 318 Boolean • 7 BorrowingPct • 172 BufferLeadTime • 363

C Cal • 62, 67, 72, 76, 79, 249 CalAttribute • 67 CalcCumLeadTimeSw • 165 CalcMargin • 95, 145 CalcMSERule • 431 CalcPriority • 84, 99, 141, 476 CalcRevenue • 96, 146 CalcStatSSRule • 432 CalData • 68 CalInterval • 76 CalPattern • 78 CancelSw • 498 Carrier • 182 Category • 127, 255, 318 CCPSw • 301 CheckMaxCap • 250 ChgCost • 272 CMPFirmDepDmd • 31, 400 CMPFirmDur • 363 CMPFirmPlanArriv • 31, 400 CMPFirmPlanOrd • 31, 400 CMPFirmPlanShip • 31, 400 CoeffVar • 179 Column description • 283, 314, 468



Column descriptions • 29, 46, 49, 53, 55, 62, 67, 69, 76, 79, 81, 84, 92, 95, 99, 107, 118, 121, 122, 124, 127, 131, 134, 137, 141, 145, 148, 150, 153, 157, 162, 165, 172, 176, 177, 178, 182, 192, 198, 206, 211, 214, 219, 230, 237, 239, 244, 248, 255, 266, 272, 279, 285, 288, 299, 318, 349, 351, 353, 355, 362, 393, 430, 444, 453, 463, 466, 470, 471, 474, 475, 478, 481, 483, 486, 488, 491, 497

COMetEarlyCount • 31, 400 COMetLateCount • 32, 400 COMetOntimeCount • 32, 400 COMetPartialCount • 32, 400 CommitIntransIn • 32, 400 CommitIntransOut • 32, 400 CompanyID • 172 ConCancel • 32, 400 ConCustOrder • 32, 400 CONeedUnit • 32, 400 ConExtraUsage • 32, 400 ConIntersiteOrder • 32, 400 ConInventory • 32, 401 ConMasterSched • 32, 401 ConNew • 32, 401 ConNoAction • 32, 401 ConPull • 32, 401 ConPurchaseOrder • 32, 401 ConPurchaseReq • 32, 401 ConPush • 32, 401 ConReschedSupply • 32, 401 ConSafetyStock • 32, 401 ConSchedSupply • 33, 401 ConShCustOrder • 33, 401 ConShExtraUsage • 33, 401 ConShMasterSched • 33, 401 ConShortage • 33, 402 ConShSafetyStock • 33, 402 ConsolidatedLoadSeqnum • 491 ConsolidatedPlanShip • 33, 402 ConstrCantMeetQty • 402 ConstrCovDur • 33, 402 ConstrExpOH • 33, 402 ConstrInvOpt • 363 ConstrNetReqts • 33, 402 ConstrOverStockDate • 446 ConstrOverStockDur • 446 ConstrOverstockExcessCovDur • 446 ConstrOverstockInvStartDate • 446 ConstrOverstockQty • 446 ConstrProjAvail • 33, 402 ConstrProjOH • 33, 402

ConstrProxyDemand • 33, 403 ConstrProxySupply • 33, 403 ConstrSchedExpOH • 33, 403 ConstrSchedUnuseOH • 33, 403 ConstrStockLowDate • 445 ConstrStockLowDur • 445 ConstrStockLowQty • 445 ConstrStockOutDate • 445 ConstrStockOutDur • 445 ConstrStockOutQty • 446 ConstrSupplyAllocRule • 363 ConstrUnuseableSupply • 403 ConstrUnuseOH • 33, 404 ConstrUseableProjOH • 403 ConSubstSupply • 34, 404 ConsumedQty • 141 ConTotalDemand • 34, 404 ConvenientAdjDownPct • 454 ConvenientAdjUpPct • 454 ConvenientOverrideThreshold • 454 ConvenientShipQty • 454 ConvFactor • 118 ConWorkOrder • 34, 404 CoPrdoPrimaryItem • 206 CoProdOrderType • 206 CoProductPlanOrders • 401 CoProductProdReqt • 404 COProjMargin • 34, 404 COProjRevenue • 34, 404 CopyDate • 107 CopyFromDmdGroup • 108 CopyFromDmdUnit • 108 CopyFromLoc • 108 CopyFromModel • 108 CORealMargin • 34, 404 CORealRevenue • 34, 404 COSchedUnit • 34, 404 Cost • 84, 251 CostPercentage • 455 CostUOM • 363 COUnmetCount • 34, 404 COUnplannedCount • 34, 404 Country • 172 CovDur • 34, 72, 404 CovDurAdjTolerance • 182 CovDurCantMeetQty • 405 CovDurSchedDate • 198, 206, 214 CPPCostResUtil • 273



CPPCostSKUProd • 273 CPPLoadFirmOrder • 273 CPPLoadPlanOrder • 273 CPPLoadSchedRcpt • 273 CPPLockSw • 363 CPPOverCap • 273 CPPPriority • 363 CPPTotCap • 273 CPPTotLoad • 273 CPPTotLoadChg • 273 CPPTotLoadProd • 274 CPPUnusedCap • 274 CreationDate • 288 CriticalItem • 251 CriticalMaterialSw • 364 CSLMetric • 433 CSLTemplate • 433 CumLeadTimeAdjDur • 364 CumLeadTimeDur • 364 CumLeadTimeRule • 364 CurAvailShipOH • 446 CurConstrCovDur • 446 CurCovDur • 446 Currency • 172 CurrencyUOM • 251, 288 CurReservedOH • 446 Cust • 81, 84, 92, 172 CustOrder • 82 CustOrderDur • 302 CustOrderHeader • 91 CustOrderPriority • 302 CustOrderStatus • 95 CustOrdLoadQty • 266 CustServiceLevel • 365

D Database conventions • 4 Database information • 1 DataDrvnCustOrders • 34, 405 DataDrvnFcst • 34, 405 Datatype • 6 Date and DateTime • 7 Day • 79, 486 DayDescr • 486 DCRank • 108 DDSKUSw • 165 DDSrcCostSw • 165 Decimal • 7

Default values • 8 DefaultUOM • 166 DeliveryDate • 198 DemandQty • 131, 318 DemandResExcepCount • 34, 405 DemandSeqNum • 131 DemandSKUExcepCount • 34, 405 DemandSupplyType • 134 DemandType • 131 DepartureDate • 199 DepDmd • 34, 405 DepDmdEarliestNeed • 34, 405 DepDmdOpt • 365 DepDmdRequirement • 405 DepDmdStatic • 98 Desc • 491 Descr • 49, 62, 72, 79, 81, 166, 172, 219, 230, 251, 255,

318, 488 Dest • 182, 199, 455, 463, 498 DestCal • 173 DestStatus • 491 DetailedPlanShip • 34, 405 DFU • 103 DFULoc • 84, 118, 121, 122 DFUToSKU • 117 DFUToSKUFcst • 34, 120, 406 DFUToSKUSeasonErr • 122 Disc • 56, 108, 118, 219, 240, 455, 483 DisplayQty • 35, 405 Distance • 182 DistanceUOM • 183 DistRequirement • 405 DistRequirementLoad • 274 DistShipRequirement • 405 DmdAllocCal • 433 DmdBandVal • 176 DmdCal • 109, 433 DmdCorrelationFactor • 433 DmdDistType • 433 DmdGroup • 84, 109, 118, 121, 123, 137, 285 DmdItem • 153 DmdNeedDate • 153, 192, 266 DmdNeedQty • 153 DmdOrderSeqNum • 266 DmdOrderType • 266 DmdPegQty • 153 DmdPlanTime • 96, 146, 478 DmdPostDate • 109, 434



DmdPriorityEnd • 177 DmdPriorityStart • 177 DmdRedID • 302 DmdSchedDate • 153, 192 DmdSeqNum • 153, 192 DmdSubType • 153, 193 DmdToDate • 303 DmdType • 141, 154, 193 DmdUnit • 84, 109, 118, 121, 123, 137, 285 DmdUsageRule • 484 DmdVar • 124 Documentation information • 1 DrawQty • 47, 56, 484, 498 DrawType • 56 DRPCovDur • 366 DRPFrzDur • 366 DRPRule • 366 DRPTimeFenceDate • 367 DRPTimeFenceDur • 367 DueDate • 245 Dur • 35, 76, 99, 121, 123, 137, 142, 274, 285, 349, 351,

354, 406, 446 Duration • 8 DurType • 76 DynDepDecimals • 166 DynDepOption • 166 DynDepPushOpt • 166 DynDepQty • 168

E E3Error • 109 E3ErrorDate • 109 EarliestNeedDate • 99 ECN • 56 EditSw • 206 Eff • 47, 49, 53, 57, 72, 110, 118, 124, 179, 220, 230, 237,

240, 314, 318, 455, 463, 466, 468, 471, 474, 484 EnableDynDepSw • 456 EnableSw • 57, 168, 173, 220, 230, 251, 288, 456, 464, 481 EndDate • 79 EndTime • 67 EOQ • 367 Exception • 127, 131, 255, 318 ExceptionCategoryAssoc • 125 ExceptionDate • 131, 262, 344 ExceptionOrderRelation • 128 ExceptionRelationType • 131 ExceptionSeqNum • 132 ExceptionSeverity • 134

ExceptionSw • 135 ExpDate • 96, 100, 132, 142, 146, 150, 162, 199, 207, 215,

245, 266, 280, 283, 368, 478, 492, 498 ExpiredRequiredOH • 406 ExplodeSw • 57, 280 ExpOH • 35, 406 Exported • 492 ExternalSKUSw • 368 ExtRef • 92

F Factor • 123, 240, 286, 456 Fcst • 136 FcstAdjRule • 303 FcstConsumptionRule • 310 FcstCustOrders • 35, 406 FcstDate • 354 FcstDur • 434 FcstHor • 110 FcstID • 137 FcstMeetEarlyDur • 310 FcstMeetLateDur • 310 FcstOrder • 140 FcstOrderStatus • 145 FcstOrdLoadQty • 266 FcstPrimConsDur • 310 FcstPriority • 311 FcstSecConsDur • 311 FcstSw • 84 FcstType • 85, 118 FinishCal • 220 FirmArrivalRequirementLoad • 274 FirmPlanArriv • 35, 406 FirmPlanOrder • 35, 406 FirmPlanOrderRequirementLoad • 274 FirmPlanShip • 35, 406 FirmPlanSw • 200, 207, 215 FirmProxyInventory • 35, 406 FirmSchedRcpts • 35, 406 FirmSubInventory • 35, 407 FirmSupplyCovDur • 35, 407 FirmSupplyProjOH • 35, 407 FirmSw • 85, 100, 245 FirstPlanArrivDate • 446 FirstPlanArrivQty • 446 FirstReplenDate • 368 FixedResReq • 230 FOMetEarlyCount • 35, 407



FOMetLateCount • 35, 407 FOMetOntimeCount • 35, 407 FOMetPartialCount • 35, 407 FONeedUnit • 35, 407 FOProjMargin • 35, 407 FOProjRevenue • 35, 407 ForcedSuppOrderQty • 35, 407 FORealMargin • 36, 407 FORealRevenue • 36, 408 FOSchedUnit • 36, 408 FOUnmetCount • 36, 408 FOUnplannedCount • 36, 408 FridaySw • 79 FrzStart • 173 FunctionName • 262, 345 FunctionNum • 132, 262, 346 FwdBuyActiveDur • 183 FwdBuyEffectPct • 183 FwdBuyMaxDur • 368

G Get additional help from JDA • 2 GroupOrderID • 492, 498

H HasExceptionSw • 92, 96, 146, 478 HeaderExtRef • 85 HeaderSeqNum • 200, 207, 215 Help information • 1 HistStart • 110 HistType • 119 HoldingCost • 368 HoldOutQty • 36, 408 HwModelSw • 110

I IdealUtilization • 274 IgnoredDmd • 36, 408 ImpDepDmdStatic • 148 Implementing Rule 6 • 309 ImpResLoadDetail • 150 IncCovDur • 472 IncDRPQty • 368 Include_In_SLCCurve • 110 IncMaxCovDur • 36, 408, 472 IncMinCovDur • 36, 409 IncMPSQty • 368 IncOrderQty • 241

IncQty • 221 IndDmd • 36, 409 IndDmdExceptionCount • 36, 409 IndDmdExceptionQty • 36, 409 IndDmdLink • 152 IndDmdUnitCost • 311 IndDmdUnitMargin • 311 IndDmdView • 157 InfCarryFwdSw • 288 InfiniteSupplySw • 290 Information about columns • 5 Information about tables • 4 InhandlingCost • 154, 369 InitE3Error • 110 InitE3ErrorDate • 110 Installation/administration information • 1 Integer • 7 Interval • 76 InUseBeforeSw • 231 InvCarCost • 36, 409 InvCarryingCost • 154 Inventory • 36, 161, 409 InvOptimizerType • 168 IPO • 433 IPOAvgStock • 409 IPODmd • 409 IPOExpBackOrder • 409 IPOFcstBias • 409 IPOProjOH • 409 IPOReorderPoint • 409 IPOReorderQty • 409 IPOSafetyStock • 410 IPOSKUHist • 410 IPOSKUHistFcst • 410 Item • 47, 49, 53, 57, 85, 96, 100, 119, 121, 123, 124, 132,

142, 146, 148, 150, 162, 164, 168, 179, 193, 200, 207, 211, 215, 221, 231, 237, 241, 245, 262, 267, 280, 283, 290, 311, 314, 346, 349, 351, 354, 356, 369, 410, 434, 447, 456, 464, 466, 468, 474, 476,479, 481, 484, 498

ItemClass • 168 ItemStoreGrade • 290

L Lag • 354 LaneGroupID • 183, 492 LaneGroupMinMetSw • 492 LastCompletedStep • 280 LastFrzStart • 369 LastPlanStart • 369



LastUpdatedBy • 262, 346 LastUpdatedOn • 262, 346 Lat • 173 LateIntransIn • 447 Layer • 176, 177 LBSource • 492, 498 LBStatus • 493 LeadTime • 221, 241, 464 LeadTimeSD • 434 Legal notice • i LevelLoadSw • 251 LevelNum • 346 LevelSeqNum • 251 LewMeanQty • 138 LimitPlanArrivPublishDur • 369 LimitPlanArrivPublishSw • 369 LineItemExtRef • 85 LineNum • 245 LoadBuildAdjDownTolerance • 183 LoadBuildAdjUpTolerance • 183 LoadBuildRule • 183 LoadDur • 456 LoadID • 493, 499 LoadLineID • 499 LoadMinimumRule • 183 LoadOffsetDur • 231 LoadOpt • 221 LoadQty • 132, 150, 262, 267 LoadSeqRule • 184 LoadSw • 493 LoadTime • 184 LoadTolerance • 185 Loc • 47, 49, 53, 57, 86, 96, 100, 110, 124, 132, 138, 142,

146, 148, 150, 154, 162, 171, 173, 179, 193, 208, 211, 215, 222, 231, 237, 241, 245, 251, 262, 267, 274, 280, 283, 286, 290, 311, 314, 346, 349, 351, 354, 356, 369, 410, 434, 447, 466, 468, 474, 476,479, 481, 484

Loc_Type • 173 LockDur • 110 Lon • 174 LookAheadDays • 185 LookAheadDur • 369 LotSizesEnabledSw • 222, 457 LPDmdBands • 176 LPLayer • 177 LSRuleMetSw • 493 LTDGroup • 290

M MajorShipQty • 457 MapUsed • 110 Margin • 86, 132 MarketMgrVersionID • 138 Mask • 110 Master • 62 MasterCal • 311 MaxCapacityExceededSw • 493 MaxCapacityMetSw • 493 MaxChangeFactor • 369 MaxCnstrProjOHDate • 447 MaxConstrCovDate • 447 MaxConstrCovDur • 447 MaxConstrProjOH • 447 MaxCovDate • 447 MaxCovDur • 314, 369, 447 MaxCustOrderSysDur • 312 MaxEarlyDur • 86, 92, 142, 476 MaxFinDur • 222 MaxHist • 111 MaxLateDur • 86, 92, 142, 476 MaxLeadTime • 222, 457 MaxOH • 370 MaxOHQty • 314 MaxOHRule • 370 MaxOrderQty • 241 MaxProjOH • 447 MaxProjOHDate • 448 MaxQty • 222 MaxShelfLifeDur • 356 MaxShipQty • 457 MaxSS • 434 MaxSSCovSkipDur • 434 MaxSSFactor • 435 MaxStartDur • 223, 231 MaxUtilization • 274 MaxWasteFactor • 356 MetIndDmd • 36, 410 MetSSLevel • 36, 410 MfgFrzDur • 371 MfgLeadTime • 371 MfgLeadTimeRule • 435 MinAllocQty • 484 MinConstrCovDate • 448 MinConstrCovDur • 448 MinCovDate • 448 MinCovDur • 356, 448



MinDRPQty • 371 MinEffShelfLifeDur • 356 MinLeadTime • 223, 458 MinMPSQty • 371 MinOHCovRule • 290 MinOrderQty • 241 MinorShipQty • 458 MinQty • 223 MinShelfLifeDur • 87, 356 MinShelfLifeTolDur • 356 MinSS • 435 MinSSQty • 314 MinUtilization • 274 MixFactor • 57 MktActvtyCustOrders • 36, 410 MktActvtyFcst • 36, 410 Model • 111, 119, 138, 286 ModelDate • 111 MondaySw • 79 Month • 487 MonthDescr • 487 MPBatchNum • 292 MPChgOverLoad • 274 MPConstProjAvail • 36, 410 MPFirmPlanArrivLoad • 274 MPFirmPOLoad • 274 MPOvertimeCap • 274 MPOvertimeLoad • 275 MPPlanArrivLoad • 275 MPPOLoad • 275 MPRegularCap • 275 MPRegularLoad • 275 MPSchedRcptLoad • 275 MPSCovDur • 371 MPSRule • 372 MPSTimeFenceDate • 373 MPSTimeFenceDur • 373 MPTotLoad • 275 MPTotLoadCustOrder • 275 MPTotLoadFcstOrder • 275 MPTotLoadSSOrder • 276 MPTotLoadUncomm • 276 MPVehLoadLineLoad • 276 MSE • 178, 179 MSEAbsToleranceLimit • 435 MSEBias • 179 MSEHistDur • 111 MSELag • 435

MSEMaskMaxVal • 435 MSEMaskMinVal • 436 MSEMaskOpt • 436 MSEModelOpt • 436 MSEPer • 436 MustGoDays • 185 MustGoQty • 499

N NeedArrivDate • 200 NeedDate • 143, 148, 162, 208, 215, 267, 477 NeedShipDate • 200 NegFcstSw • 111 NetChgSw • 292 NetFcstError • 111 NetFcstMSE • 111 NetFcstMSESmConst • 111, 436 NetProfit • 36, 410 NetReqts • 37, 410 Network • 180 NewDFUSw • 111 NextStepTiming • 231 NonBaseFcst • 37, 354, 410 NonBaseHist • 37, 410 NoNewSupplyDate • 225, 241, 458 NonFcstCustOrders • 37, 410 NonIgnorableQty • 201 NonSupsdAdjAllocTotalFcst • 37, 411 NonSupsdAdjFcstCustOrders • 37, 411 NonSupsdAllocBaseFcst • 37, 411 NonSupsdAllocNonBaseFcst • 37, 411 NonSupsdAllocTotFcst • 37, 411 NonSupsdBaseFcst • 37, 411 NonSupsdDepDmd • 37, 411 NonSupsdDFUToSKUFcst • 37, 411 NonSupsdFcstCustOrders • 37, 411 NonSupsdFirmPlanArriv • 37, 411 NonSupsdFirmPlanOrder • 37, 411 NonSupsdFirmPlanShip • 37, 411 NonSupsdNonBaseFcst • 37, 412 NonSupsdNonFcstCustOrders • 37, 412 NonSupsdPlanArriv • 37, 412 NonSupsdPlanOrders • 37, 412 NonSupsdPlanShip • 38, 412 NonSupsdRecArriv • 38, 412 NonSupsdRecShip • 38, 412 NonSupsdTotDmd • 38, 412 NPIFromDmdPostDate • 111



NPIFromMSE • 112 NPIIndDate • 112 NPIMeanSmooth • 112 NPIScalingFactor • 112 NPISw • 112 NPITransDur • 293 NPITrendSmooth • 112 NumFcstPer • 63 NumReplenYr • 436 NumTrailers • 488 NumYears • 112

O ObsoleteFlag • 112 Offset • 47, 58, 267, 346, 464 OffsetType • 225 OH • 293 OHPost • 174, 293 Opt • 72 Option_Number and Option_Text • 7 OptionSet • 38, 276, 412, 448 OptionSetName • 267 OrderCost • 186 OrderDataDur • 436 OrderGroup • 458 OrderGroupMember • 458 OrderID • 87, 96, 132, 154, 193, 493, 499 OrderingCost • 373 OrderLag • 437 OrderLineItem • 87 OrderLink • 191 OrderNum • 245, 280, 499 OrderOptSeqNum • 494 OrderPlaceDate • 201 OrderPointMinDur • 373 OrderPointMinQty • 374 OrderPointMinRule • 374 OrderPointRule • 374 OrderPostDate • 437 OrderReviewCal • 185 OrderSeqNum • 87, 162, 245, 349, 467 OrderSKUDetailSw • 375 OrderType • 87, 132, 143, 162, 349 OrderType_PO • 245 OrderType_PR • 245 OrderUptoLevelMaxDur • 375 OrderUptoLevelMaxQty • 375 OrderUptoLevelMaxRule • 375

OuthandlingCost • 155, 376 OutlierOpt • 112 OutputItem • 237 OverrideFcstTypeSw • 87 OverstockDate • 448 OverstockDur • 448 OverstockExcessCovDur • 448 OverstockInvStartDate • 448 OverstockQty • 448 OvertimeAvailCap • 276 OvertimeSw • 251 OvrideCustOrders • 38, 412 OvrideFcst • 38, 412

P PalletsPerVehicle • 488 Parent • 100, 148 Parent/Child tables and columns (foreign keys) • 5 ParentExpDate • 100, 148 ParentItem • 194, 346 ParentLoc • 194, 346 ParentOrderType • 100 ParentSchedDate • 100, 149 ParentSeqNum • 101 ParentStartDate • 101 ParentSupplySeqNum • 194 ParentSupplyType • 194 Paths between tables • 9 Pattern • 79 PatternSeqNum • 79 PatternSw • 63 PctComplete • 280 PctUsed • 276 PeggingSw • 251, 295 PegQty • 194 PerishableSw • 168 PerNum • 123, 286 PerWgt • 73 PickBestDate • 112 PickBestSw • 113 PlanArriv • 38, 196, 412 PlanDur • 376 PlanInfeasibleOpt • 356 PlanIntransIn • 38, 412 PlanLeadTime • 376 PlanLeadTimeRule • 376 PlanLevel • 169, 295 PlannedSupplyOrderLoad • 276



PlanOrder • 204 PlanOrders • 38, 412 PlanProjAvail • 38, 413 PlanProjOH • 38, 413 PlanProxyInventory • 211 PlanPurch • 38, 213, 413 PlanPurchFirm • 38, 413 PlanShip • 38, 413 PlanShipFrzDur • 376 PostalCode • 174 Predefined pages • 4 PresentationQty • 38, 413 PriceCal • 312 PriItemPriority • 169 Primary key columns • 5 Primary key columns in the table • 4 PrimaryItem • 499 PrimaryItemQty • 211, 499 PrimaryLSDur • 185 PrimaryLSRule • 185 PrimarySeqNum • 208 PrimaryStepNum • 49 Priority • 47, 50, 81, 87, 93, 143, 169, 177, 226, 242, 458,

477 PrioritySeqNum • 88, 143, 477 ProAllocBaseFcst • 40, 414 Process

input and output tables • 581 ProcessDate • 38, 276, 413, 448 ProcessID • 132, 262, 267, 346 ProcessSeqNum • 96, 146, 479 ProdCal • 376 ProdCost • 155, 227, 233 ProdDur • 233 ProdFamily • 234, 262 ProdGroup • 227 ProdOffset • 234 ProdRate • 50, 234 ProdRateCal • 50, 235 ProdRequirement • 413 ProdRequirementLoad • 276 ProdStartDate • 377 ProdStopDate • 377 ProductionFamilyChangeOverOpt • 252 ProductionMethod • 50, 208, 217, 227, 235, 237, 262, 267,

281, 346 ProductionStep • 229 ProductionYield • 237

ProjAvail • 38, 413 ProjAvailEarliestNeed • 39, 413 Project • 88, 132, 143, 162, 245, 349 ProjOH • 39, 413 ProjOHEarliestNeed • 39, 414 ProjOrderDur • 186 ProjOrderOptIntransIn • 39, 414 ProjOrderOptIntransOut • 39, 414 ProjOrderOptProjAvail • 39, 414 ProjOrderOptProjOH • 39, 414 ProjOrderOptSOQ • 39, 414 ProjOrderOptTotDmd • 39, 414 ProjOrderOptTotSupply • 39, 414 ProrateByTypeSw • 312 ProratedAllocTotFcst • 40, 414 ProrateSw • 312 ProrationDur • 312 Provide feedback on this document • i ProxyDemand • 40, 415 ProxyEndDate • 211 ProxyIntransIn • 40, 415 ProxyIntransOut • 40, 415 ProxyInventory • 40, 415 ProxyRecArriv • 40, 415 ProxyRecShip • 40, 415 ProxyStartDate • 211 ProxySupply • 40, 415 PSOLoad • 40, 415 PublishDate • 113 PullForwardDur • 459 PurchCost • 155, 242 PurchGroup • 242 PurchMethod • 215, 239, 242, 245, 346 PurchOrder • 40, 243, 415 PurchRequirement • 415

Q Qtr • 487 QtrDescr • 487 Qty • 53, 88, 101, 138, 143, 149, 162, 201, 208, 211, 215,

245, 281, 349, 352, 467, 474, 477, 499 QtyCap • 488 QtyInMove • 283 QtyInQueue • 283 QtyInRun • 283 QtyPerAssembly • 59 QtyReceived • 281 QtyUOM • 59, 235, 237, 252, 295, 464



R Rank • 79, 186 Rate • 464 RatePerCWT • 186 RecAllocArriv • 40, 415 RecAllocShip • 40, 416 RecArriv • 40, 416 ReceivedQty • 245 ReconcileCustOrders • 40, 416 ReconcileFcst • 40, 416 RecSchedRcptsDur • 377 RecSchedRcptsOpt • 208 RecShip • 40, 416 RecShipSSOpt • 357 RefitDate • 113 RelatedSeqNum • 155 Release Notes • 1 ReleaseFenceDur • 252 RemainingQty • 246 Repeat • 74 RepeatDur • 472 RepeatEveryNDays • 79 RepeatOpt • 473 RepeatTimes • 77 ReplenMethod • 295 ReplenType • 295 RequiredProjAvail • 416 RequiredProjOH • 416 RequirementPlanAvailCap • 277 Res • 151, 235, 247, 252, 262, 267, 277, 464, 481 ResCost • 277 ResCountException • 277 Reservation • 88 ResException • 254 ResExp • 89 ResidualShelfLifeDur • 357 ResLoadDetail • 264 ResLoc • 267 RespectSSLevelSw • 484 ResProjStatic • 270 ResSourceException • 277 RestrictDur • 377 RestrictPlanMode • 169 Revenue • 89, 132, 349 ReviewCal • 459 ReviewedStatus • 262, 346 RevisedDate • 201, 208, 215, 281, 500 RevisedExpDate • 202, 209, 215, 281, 499

RIOMaxCovDur • 187 RIOMinCovDur • 187 RIOSelectSw • 187 RollingSw • 63 RoundingFactor • 377, 459 RoundingQty • 484 RoutingNeedCompleteDate • 268 RPBatchNum • 296 RunCalcModelSw • 113

S SaturdaySw • 79 SchedArrivDate • 202, 500 SchedDate • 93, 96, 101, 146, 151, 209, 216, 268, 281, 284,

479 SchedExpiredRequiredOH • 416 SchedExpOH • 40, 416 SchedQty • 96, 101, 146, 479 SchedRcpts • 40, 278, 416 SchedRcptsDetail • 283 SchedRcptsRequirementLoad • 277 SchedShipDate • 202, 500 SchedStatus • 93, 96, 101, 134, 146, 479 SchedSupplyExceptionCount • 40, 416 SchedSupplyExceptionQty • 41, 416 SchedUnusedRequiredOH • 417 SchedUnuseOH • 41, 417 SeasonError • 285 SeasonErrorLag • 114 SeasonFactor • 41, 417 SeasonProfile • 114 SecondaryLSRule • 187 SEOutlierFactor • 114 SEOutlierOpt • 114 SeqIntEnableSw • 296 SeqIntExportDur • 174 SeqIntImportDur • 174 SeqIntLastExportedToSeq • 175 SeqIntLastImportedFromSeq • 175 SeqNum • 101, 132, 143, 147, 149, 151, 176, 202, 209, 212,

216, 262, 281, 284, 346, 477, 480, 500 Sequence • 8 Setup • 235 Severity • 135, 262, 346 SftyFct • 162 ShelfLifeDur • 357 ShelfLifeGroup • 357 ShelfLifeRule • 357 ShipCal • 187, 459



ShipDataDur • 437 ShipDate • 89, 94, 97, 132, 155, 194, 494 ShipLag • 437 ShipSw • 89 ShipToAddr • 94 ShrinkageFactor • 59, 202, 377, 460 SKU • 287 SKUDemandParam • 298 SKUEffInventoryParam • 314 SKUException • 316 SKUExceptionCount • 41, 417 SKUExceptionQty • 41, 417 SKUExternalFcst • 41, 348, 417 SKUGroup • 296 SKUHist • 351 SKUHistFcst • 353 SKULoc • 119, 121, 123 SKUPerishableParam • 355 SKUPerPalletSw • 187 SKUPlanningParam • 359 SKUProjStatic • 379 SKUResExceptionCount • 41, 417 SKUResExceptionQty • 41, 417 SKUSafetyStockParam • 427 SKUStatStatic • 440 Source • 188, 202, 252, 263, 268, 460, 464, 500 SourceCal • 175 SourceOpt • 268, 281 Sources • 41, 417 SourceStatus • 494 Sourcing • 202, 263, 347, 451, 460, 464, 500 SourcingCost • 155, 460 SourcingGroup • 296, 460 SourcingRequirement • 463 SplitFactor • 227 SplitOrderSw • 227 SplitQty • 460 Spread • 235 SS • 41, 417, 466 SSBand • 468 SSCalcDesc • 470 SSCov • 437 SSCovDur • 315 SSCovUseBaseOnlySw • 437 SSInventory • 41, 417 SSLoadQty • 268 SSMeetEarlyDur • 437 SSMetEarlyCount • 41, 417

SSMetLateCount • 41, 417 SSMetOntimeCount • 41, 417 SSMetPartialCount • 41, 417 SSNeedUnit • 41, 418 SSPresentationOpt • 437 SSPriority • 437 SSRule • 438 SSSchedUnit • 41, 418 SSTemplate • 438, 470, 473 SSTemplateData • 471 SSUnmetCount • 41, 418 SSUnplannedCount • 41, 418 Stage • 252 StandardCost • 41, 418 StartDate • 42, 80, 101, 121, 123, 138, 149, 151, 209, 216,

268, 277, 282, 284, 286, 349, 352, 354, 418, 448 StartTime • 67 StaticCFDescr • 114 StaticCFValue • 114 StatMSE • 114 StatSS • 42, 418, 474 StatSSAdjOpt • 438 StatSSCovLimitDur • 438 StatSSCSL • 439 Status • 89 StatusDescr • 494 StepNum • 151, 236, 263, 268, 284, 464 StepSchedDate • 284 StepStartDate • 284 StockLowCost • 42, 418 StockLowDate • 448 StockLowDur • 449 StockLowQty • 449 StockOrder • 475 StockOrderStatus • 478 StockOutCost • 42, 418 StockOutDate • 449 StockOutDur • 449 StockOutQty • 449 StorableSw • 296 StorageClass • 252 StorageGroup • 169, 252 StorageRequirement • 481 Store • 133, 163 StoreFittedHistOpt • 114 SubConstrProjAvail • 42, 418 SubConstrProjOH • 42, 418 SubIntransIn • 42, 418



SubInventory • 42, 418 Subord • 47, 59 SubRecArriv • 42, 418 SubRecShip • 42, 418 SubstLevel • 90, 349 SubstOperator • 90, 350 SubstQty • 203, 210 SubType • 252 SundaySw • 80 SupersedeSSSw • 439 SupersedeSw • 60, 90, 101, 119, 121, 143, 350, 477 Supersession • 482 SupplyAvailDate • 155, 194 SupplyCap • 485 SupplyID • 162, 282, 500 SupplyItem • 155 SupplyLeadTime • 461 SupplyLoc • 155 SupplyMethodOption • 135 SupplyOrderSeqNum • 268 SupplyPegQty • 155 SupplyQty • 263, 268 SupplySeqNum • 133, 155, 194, 268 SupplySubType • 155, 194 SupplyTransferCost • 461 SupplyType • 133, 155, 194, 268 SuppOrderPlanShip • 418 SuppOrderQty • 42, 203, 418, 500 SupsdAdjAllocTotalFcst • 42, 418 SupsdAdjFcstCustOrders • 42, 419 SupsdAllocBaseFcst • 42, 419 SupsdAllocNonBaseFcst • 42, 419 SupsdAllocTotFcst • 42, 419 SupsdBaseFcst • 42, 419 SupsdConstrProjAvail • 419 SupsdConstrProjOH • 42, 419 SupsdDepDmd • 42, 419 SupsdDFUToSKUFcst • 43, 419 SupsdFcstCustOrders • 43, 419 SupsdFirmPlanArriv • 43, 419 SupsdFirmPlanOrder • 43, 419 SupsdFirmPlanShip • 43, 420 SupsdMinDmdCovDur • 378 SupsdNonBaseFcst • 43, 420 SupsdNonFcstCustOrders • 43, 420 SupsdPlanArriv • 43, 420 SupsdPlanOrders • 43, 420 SupsdPlanShip • 43, 420

SupsdProjAvail • 43, 420 SupsdProjOH • 43, 420 SupsdRecArriv • 43, 420 SupsdRecShip • 43, 420 SupsdTotDmd • 43, 420 SupsnGroupNum • 170 SymmetricMAPE • 115

T Table description • 28, 46, 49, 52, 54, 62, 67, 68, 76, 79, 81,

83, 91, 95, 99, 107, 117, 120, 122, 124, 125, 129, 134, 137, 141, 145, 148, 150, 153, 157, 161, 165, 172, 176, 177, 178, 181, 192, 197, 205, 211, 214, 218, 230, 237, 239, 244, 248, 255, 265, 272, 279, 283, 285, 288, 299, 314, 317, 348, 351, 353, 355, 362, 393, 430, 443, 452, 463, 466, 468, 470, 471, 474, 475, 478, 481, 482, 486, 488, 491, 497

Table Relationships • 501 Tables in the database (technical documentation) • 10 TargetEarlyDur • 90, 312 TargetNetworkInv • 44, 420 TargetOHCovRule • 296 TargtImpactBaseFcst • 44 TargtImpactCustOrders • 44 TargtlmpactBaseFcst • 421 TargtlmpactCustOrders • 421 Text and Upper_Text • 6 The SCPO database (technical documentation) • 4 ThursdaySw • 80 TimeHorizon • 486 TimeUOM • 297 TOHRule • 439 ToleranceCapMetSw • 494 TotalCost • 44, 421 TotalLoad • 44, 421 TotalLockCustOrders • 44, 421 TotalLockFcst • 44, 421 TotalRequirementLoad • 277 TotArriv • 44, 421 TotContribMargin • 44, 421 TotDmd • 44, 421 TotDmdRequirement • 421 TotDmdSatisfied • 44, 421 TotFcst • 44, 121, 421 TotFcstLock • 116 TotHist • 44, 421 TotIntransIn • 44, 421 TotIntransOut • 44, 421 TotLoad • 277 TotLockCustOrders • 422



TotLockFcst • 422 TotRecArriv • 44, 422 TotRecShip • 45, 422 TotShip • 45, 422 TotSupply • 45, 422 TotSupplyRequirement • 422 TotTransCost • 45, 422 TotUseRecArriv • 45, 422 TotUseRecShip • 45, 423 TransCal • 188 TransLeadTime • 188 TransLeadTimeSD • 189 TransMode • 189, 203, 461, 488, 494 TransmodeMinMetSw • 495 TransModeMinRule • 189 TransModeName • 189 TransName • 203 TuesdaySw • 80 Type • 63, 121, 138, 177, 252, 352, 468 Type3 • 175

U UnconActualReq • 45, 423 UnconCancel • 45, 423 UnconCustOrder • 45, 423 UnconDependantDmd • 45, 423 UnconExtraUsage • 45, 423 UnconIntersiteDmd • 45, 423 UnconIntersiteOrder • 45, 423 UnconInventory • 45, 423 UnconMasterSched • 45, 423 UnconNetAvailable • 45, 423 UnconNetAvlNegDate • 449 UnconNetAvlQtyAtLt • 449 UnconNetDaysSupply • 45, 424 UnconNetOHLt • 449 UnconNetOHNegDate • 450 UnconNetOnHand • 45, 424 UnconNew • 45, 424 UnconNoAction • 424 UnconNumCancel • 450 UnconNumNew • 450 UnconNumPull • 450 UnconNumPush • 450 UnconPlannedOrder • 424 UnconPrjDaysSupply • 424 UnconProjAvailable • 424 UnconProjOnHand • 424

UnconPull • 424 UnconPurchaseOrder • 424 UnconPurchaseReq • 424 UnconPush • 424 UnconReschedInFrom • 424 UnconReschedOutFrom • 424 UnconReschedSupply • 425 UnconRevCancel • 450 UnconRevNew • 450 UnconRevPull • 450 UnconRevPush • 450 UnconSafetyStock • 425 UnconSubstDmd • 425 UnconSubstSupply • 425 UnconTotalDemand • 425 UnconTotalSupply • 425 UnconTVSS • 425 UnconWorkOrder • 425 UnitCarCost • 312 UnitConvFactor • 60 UnitPrice • 90, 312 UnitsPerAltShip • 170 UnitsPerPallet • 170 UnloadDur • 461 UnloadTime • 189 UnmetIntransOut • 450 UnuseableSupply • 425 UnusedRequiredOH • 425 UnuseOH • 426 UOM • 170 Updated • 495 URL • 8 UsageSw • 48, 50, 163 UseableProjOH • 425 UseAltTransModeSw • 189 UseLookAheadSw • 461 UserFirmDepDmd • 426 UserFirmPlanArriv • 426 UserFirmPlanOrd • 426 UserFirmPlanShip • 426 UserID • 263, 277, 347, 426, 450 UseUntilLevel • 485

V Valid values • 8 Value • 67, 77 VehicleLoad • 490 VehicleLoadLine • 496



VehicleLoadLineRequirementLoad • 277 VendID • 175 Vendor • 246 VendorMinMetSw • 495 VendorMinRule • 190 VLLTolerance • 358 Vol • 170 VolCap • 488

W WDDArea • 175 WednesdaySw • 80 Week • 486 WeekDescr • 487 WeeklyAvgHist • 313 Wgt • 170 WgtCap • 488 When • 133, 263, 347 WhenLoaded • 151, 269 WOLoad • 426 WorkingCal • 175, 378 WorkOrderLoad • 277 WorkScope • 90, 228

Y Year • 487 YearDescr • 487 YieldCal • 48, 61, 237 YieldFactor • 48, 60, 461 YieldQty • 228, 238


Documents

esp_ref_guide.pdf