EIS 610 User Guide en v2

SAP Enterprise Inventory and
Service-Level Optimization User

Guide, Version 6.10
Table of Contents
1. Portal ______________________________________________________________________________________ 1
Welcome to the Portal 1
Administration 1
Privileges 1
Preferences 2
Alerts 2
Alerts 2
2. MIPO_______________________________________________________________________________________ 3
Welcome to Multistage Inventory Planning & Optimization 3
Getting Started 3
Signing In and Out 3
Navigating 4
Maximizing Your Work Area 5
Using Selectors 5
Copyrights & Trademarks 19
Managing Data Sets 19
Importing Data 19
Exporting Data 22
Viewing Supply Chain Networks 23
Modeling a Supply Chain 23
Viewing a Network 23
Choosing a Network View 24
Displaying Data for Nodes and Paths 26
Modifying the Network Layout 27
Searching the Network 27
Printing a Network Diagram 27
Editing Your Display Preferences 28
Viewing and Editing Data in the Network Window 29
Exporting a Network Diagram 31
Editing Supply Chain Data 31
Values of Input and Output Data Properties 31
Input Data 34
Output Data 64
Auditing Data Changes 69
Deleting Nodes and Paths 70
Changing Data Management Preferences 71
Printing Stocking Point and Supply Path Data 72
Analyzing Scenarios 72
Analyzing and Managing Scenarios (MIPO) 72
Creating a Supply Chain 76
Creating a User Scenario 80
Using the Item Filter 83
Duplicating Scenarios 84
Validating Scenarios 87
Optimizing Scenarios 88
Upgrading Scenarios 89
Postprocessing SLO Scenarios 91
Validating Business Alerts (Inputs and Outputs) 91
Reviewing Inventory Targets 92
Managing Scenario Access 99
Deleting a Supply Chain or a Scenario 99
Deleting Multiple Scenarios 100
iii
SAP Enterprise Inventory and Service-Level Optimization User Guide
Exception Management Workflow 101

Creating Reports 109
Input Reports 109
Output Reports 117
Processor Reports 137
Published Reports 138
Editing Report Preferences 152
Comparing Reports 153
Printing Reports 153
Exporting Reports to Excel 154
Managing Alerts 154
Managing Business Alerts 154
Managing Scenario Business Alerts 161
Managing Alerts 168
Viewing Alerts 172
MIPO Alert Definitions 175
Related Topics: 181
Managing User Accounts 181
For Users 181
For Administrators 185
Managing MIPO Settings 215
Module Settings 215
Scenario Settings 240
3. Analytics _________________________________________________________________________________ 243

Welcome to Analytics 243
Administration 243
Analytics Privilege Definitions 243
Analytics module settings 243
4. Data Gateway _____________________________________________________________________________ 245

Welcome to Data Gateway 245
Topology Overview 245
Creating an Initial Supply Chain Network 246
Step 1: Data Gathering 247
Step 2: Network Creation 247
Step 3: Data Augmentation 247
Step 4: Data Loading 248
Features 248
Creating Reports 253
Administration 267
Data Gateway Privilege Definitions 267
Data Gateway Preference Definitions 267
Gateway Data Connector module settings 269
Gateway Data Loader module settings 270
Gateway Export module settings 271
Alerts 271
Gateway Connector Alerts 271
Gateway Data Loader Alerts 272
Gateway Export Alerts 272
5. Data Store ________________________________________________________________________________ 273

Welcome to Data Store 273
Features 273
Data Store Management 273
iv
Table of Contents
Published Reports 274

Administration 276
Configuring Scenario Comparison - Data Store Privileges 276
Data Store Privilege Definitions 276
Data Store Preference Definitions 276
Compare Scenario module settings 277
Data Store module settings 278
Data Store scenario settings 279
Alerts 279
Data Store Alerts 279
6. DIM ______________________________________________________________________________________ 281

Welcome to Demand Intelligence Module 281
Features 281
DIM Features Overview 281
Analyzing DIM Data 284
Creating DIM Reports 295
Administration 301
Demand Intelligence Privilege Definitions 301
Demand Intelligence Preference Definitions 301
DIM module settings 302
DIM scenario settings 303
Alerts 305
Demand Intelligence Alerts 305
7. SIM ______________________________________________________________________________________ 307

Welcome to Supply Intelligence Module 307
Features 307
Viewing SIM Data 307
Creating SIM Reports 309
Administration 320
Supply Intelligence Privilege Definitions 320
SIM module settings 320
8. SLO _____________________________________________________________________________________ 323

Welcome to Service Level Optimization (SLO) 323
Sample business problem addressed 323
SLO's approach 323
Fit within the SAP Enterprise Inventory and Service-Level Optimization solution 324
Benefits 324
Features 324
SLO Features Overview 324
Editing SLO Data 326
Analyzing SLO Data 337
Creating SLO Reports 350
Administration 374
SLO Privilege Definitions 374
SLO Preference Definitions 374
SLO module settings 374
SLO scenario settings 375
Alerts 378
SLO Alert Definitions 378
v
9. Data Protection and Privacy _________________________________________________________________ 381

Introduction 381
Notification 381
Glossary 381
Read Access Logging 382
Information Report 382
Erasure of personal data 383
Simplified Blocking and Deletion 383
Deletion of personal data 383
Change Log 383
10. Index ____________________________________________________________________________________ 384
vi
Portal
Welcome to the Portal
The Portal lets you access the various application modules designed to perform various functions relating to supply chain
performance and inventory optimization. The Portal design provides an intuitive user interface that includes feature
consistency between modules.
For help on a specific module, click the associated link:
MIPO
Analytics
Data Gateway
Data Store
DIM
SIM
SLO
Other Help links:
How-to Topics
Instructional Topics
Additional references
Glossary
Copyrights and Trademarks
Administration
Privileges
SAP Enterprise Inventory and Service-Level Optimization consists of several applications designed to perform specific
features with your supply chain data.
Click on a link below to view privilege definitions for a specific application:
Analytics
Data Gateway
1
Data Store
DIM - Demand Intelligence Module
MIPO - Multistage Inventory Planning & Optimization
SIM - Supply Intelligence Module
Preferences
SAP Enterprise Inventory and Service-Level Optimization consists of several applications designed to perform specific
features with your supply chain data.
Click on a link below to view preference definitions for a specific application:
Data Gateway
Data Store
Alerts
Alerts
The Enterprise Inventory and Service-Level Optimization solution consists of several applications designed to perform
specific features with your supply chain data.
Click on a link below to view alert definitions for a specific application:
Data Gateway
Data Store
2
MIPO
Welcome to Multistage Inventory Planning & Optimization
The purpose of Multistage Inventory Planning & Optimization (MIPO) application is to simultaneously optimize inventory
(and service levels, if desired) for a product (and its components) at every location within the supply chain by minimizing
costs or maximizing profits.
The general approach to achieving these goals involves three steps:
• Create a graphical representation of the supply chain.

• Determine the demand at each location. Demand throughout the network can be derived based on demand at
customer-facing locations or supplied directly by the client. The result is that a demand stream is available for
each item-location pair.
• Optimize inventory levels at each location. Based on the item-location parameters, the demand stream, and
other settings, the optimal inventory positions for a given item are determined.
This application calculates target and average inventory positions and service levels for each item at each location in a
single or multistage assembly or distribution system. MIPO considers random demand and variable lead times as well as
capacity and manufacturing constraints.
Output reports in MIPO display information about a specific location within a supply chain network for a specified time
period. You can also view reports about optimal inventory positions, demand, and service level information aggregated by
sets of items, nodes, or locations.
You can save user scenarios, which are scenarios containing “what-if” or edited data, and generate reports to compare
the results of the user scenarios with the your current real-world supply chain.
How-to Topics
Instructional Topics
Glossary
Getting Started
Signing In and Out
Signing in
You can access the application by using the Microsoft Internet Explorer (IE) Web browser for Microsoft Windows. The
instructions in this guide assume that you have working knowledge of IE and of Web browsers in general. For more
information about using IE, click Help in your browser window.
3
To launch the application:
1. Start IE, type the URL of the Portal in the Address text box, and press ENTER. You can bookmark this address
for future use.
2. The Status window opens. Ensure that the system is running, and click Go To Sign In.
3. The Sign In window opens. You should have received your User Name and Password from your system
administrator. Type these into the appropriate text boxes and click Sign In.
Monitor resolution and browser version requirements
Logging Out
To log out, click the Log Off button on the menu bar. For security purposes, you are automatically logged out after a
period of inactivity. The length of time that an inactive session can remains opens varies, depending on how the
application is configured for your organization.
Related Topics:
Changing Your Password
Navigating
Several tabsets, menus, hyperlinks, and other tools allow you to navigate the application, perform various tasks, and
select entities that make up supply chains in the application. The most prevalent tools are the toolbar buttons, the main
tabset, and selectors.
The menu bar near the top left side of the window allows you to access the various tasks you can perform in the
application:
• Data Set - Lets you open the Import Data Set and Export Data Set windows. These features allow you to
import the data required to create scenarios for new or existing supply chains, as well as select flat files
containing data to export to the application server.
• Edit - Lets you view the graphical representation of a supply chain network and scenarios and to edit the data
related to nodes, paths, and other entities.
• Analyze - Opens the Manage Scenarios window, from which you can create new supply chains and user
scenarios, upgrade, validate, and optimize supply chains, and view scenario audit information.
• Reports - Accesses the Input and Output reports that you can generate in the application.
• Alerts - Lets you manage and view generated alerts.
• Settings - Opens the Alert Settings, User Settings, and Profile Settings windows, which allow you to
manage alerts, user accounts, and profiles, respectively.
• Portal - Allows you to move between different component modules without logging off.
• Help - Accesses context-sensitive online Help at any time. Also provides information pertaining to the
application including version number and copyright information
On the top right side of the window, you will find more menu items:
4
MIPO
• Home - Lets you return to the main window.
• History - Invokes the History feature.
• Log Off - Click to log off of the system.
• Clock - Displays the current date and time.
Note: If you do not have privileges to access scenarios in the application, menu items that
require that a scenario be selected are disabled. In addition, you cannot select a supply
chain in the Supply Chain Selector or a scenario in the Scenario Selector.
Selectors allow you choose the entities with which you want to work in the application. For example, you can choose a
specific supply chain, select whether you want to work with the base or user scenario, or change the current period. The
following selectors are available:
• Supply Chain Selector
• Scenario Selector
• Period Selector
• Item Selector
• Location Selector
• Node Selector
• Path Selector
• Demand Stream Selector
• Attribute Selector
• Quick Links
• History feature
Maximizing Your Work Area

Throughout the application, some windows contain a button labeled POPUP. Clicking POPUP allows you to open the
current window in a new, separate window. Use this when:
• Viewing a large supply chain network or comparing two networks
• Editing data for a significant number of nodes or periods
• Comparing two or more reports
Using Selectors
Supply Chain Selector
Use the Supply Chain Selector to select a supply chain. The selector is located on the left side of the screen. Click the
arrow button in the upper right corner of the Supply Chain Selector to maximize it.
5
The Supply Chain Selector lists all of the supply chains that exist in your system in alphabetical order. While you may
not have privileges to access every supply chain, you can view the entire list. The supply chains you can access are
located at the top of the Supply Chains list and are differentiated from the ones you cannot access by color. By default,
the first supply chain you can access is selected when you open the Supply Chain Selector. The Description text box
can contain a brief description related to the selected supply chain.
If a supply chain is added to the system, or if its name or description are modified, the contents of the Supply Chain
Selector are automatically refreshed. Click the REFRESH button to manually refresh the contents of the Supply Chain
Selector. When the Supply Chain Selector is minimized, the name of the selected supply chain is displayed.
Note: If you do not have privileges to access scenarios, you cannot select a supply chain
in the Supply Chain Selector or a scenario in the Scenario Selector. In addition, menu
items that require that a scenario be selected are disabled.
Related Topics:
Scenario Selector
Period Selector
Scenario Selector
Use the Scenario Selector to select a scenario .The selector is located on the left side of the screen, under the Supply
Chain Selector. Click the arrow button in the upper right corner of the Scenario Selector to maximize it.
A scenario is a collection of data that represents a supply chain and the results of optimization for a selected time period.
The Scenarios list in the Scenario Selector contains the base scenario and user scenarios for the selected supply chain.
While you may not have privileges to access every scenario, you can view the entire list. The scenarios that you can
access are located at the top of the Scenarios list and are differentiated from the ones that you cannot access by color.
The Scenarios list is specific to the supply chain selected in the Supply Chain Selector. By default, the base scenario
for the selected supply chain is automatically selected. If you want to view supply chain data associated with a different
scenario than the base scenario, select a user scenario. Click on a scenario name in the Scenarios list to select it. The
Description text box can contain a brief description related to the selected scenario.
If a scenario is added to the system, or if its name, description, or data are modified, the contents of the Scenario
Selector are automatically refreshed. Click the REFRESH button to manually refresh the contents of the Scenario
Selector. When the Scenario Selector is minimized, the name of the selected scenario is displayed.
Note: If you do not have privileges to access scenarios in MIPO, you cannot
select a supply chain in the Supply Chain Selector or a scenario in the
Scenario Selector. In addition, menu items that require that a scenario be
selected are disabled.
Related Topics:
Period Selector
Period Selector
Use the Period Selector to select a period. Click the arrow button in the upper right corner of the Period Selector to
maximize it.
6
MIPO
Note: The Period Selector is displayed only when you are using a
window that requires that you select a period.
The dates shown in the Period Selector depend on several factors. By default, the Period Selector displays all periods
in the data horizon that contain data starting with the base period, for the selected scenario. The data horizon is the
number of periods of data available for computation (optimization). The base period is the latest recognized date in the
database when historical data transitions to forecast data. It is determined by the start period for the latest available
forecast (defines “future") and the latest period for which sales data is available, if it is later than the available forecast
(defines “historical”).
In addition, each scenario is associated with a period length that is specified in the database when the scenario is
uploaded from a .zip file or created by using the application interface. The period length is the length of time for which
time varying data is provided. For example, if a forecast is given in weekly time buckets, the period length is one week.
The filters available in the Period Selector depend on the amount of data in your system and the period length for the
scenario. For example, if forecast data is input into the system each month, the period length is months. If your
organization uploads forecasts for twenty-four months, the Period Selector would contain drop-down menus that allow
you to filter periods based on Years and Quarters and select from Periods of one month. By default, the base period for
the current scenario is selected.
Related Topics:
Scenario Selector
Item Selector
Use the Item Selector to select single or multiple items.
Searching by Item Code
By default, the Item Selector prompts you to filter the list of items displayed by Item Code. As a result, the Items list will
include only items whose code begins with a specific text string. The filter is automatically set to display only items
relevant to the selected scenario, as indicated by the checkbox.
To search for items by Item Code, type the beginning of the desired code in the Item Code field. Click the Show button to
view the set of items whose code matches your search string. The Items list is automatically sorted alphabetically.
Select all items in the Items list or a single item, as follows:
• Click OK to select all items in the Items list and close the Item Selector.
• To select a single item, click the desired item and click OK to close the Item Selector.
Displaying All Items
In addition to filtering items by Item Code, you can use the Item Selector to display all items in the system. To display all
items in the system, select All from the Search by drop-down menu. If a description exists for a selected item, it is
displayed in the Description text box.
If you want to sort the Items list alphabetically, ensure that the Sort list check box is selected.
7
If your installation includes a large number of items, you can page through the Items list by using the arrow buttons in the
lower left corner of the selector. To go directly to a specific page in a multi-page list, type a page number in the Page field,
and press ENTER. If an item is added to the system, or its code or description are modified, the contents of the Item
Selector are automatically updated.
Select all items in the Items list or a single item, as follows:
1.
Filtering by Item Attribute
You can filter the list of items displayed in the Item Selector based on an attribute associated with a group of items.
To filter items by item attribute:
1. Select Attribute from the Search by drop-down menu.
2. Click the Browse (...) button next to the Attribute field to open the Attribute Selector. The attributes that you
can use to identify a group of items are displayed in the Attribute Name drop-down menu. The contents of this
menu is filtered, displaying only valid item attribute names.
Note: The contents of the drop-down menus in the Attribute

Selector are specific to your MIPO system. Attribute Values must
be created and assigned to appropriate entities. For example, an
item attribute could be “Component” for component items or “FG” for
finished goods.
3. Select the desired attribute from the Attribute Name drop-down menu.
4. The items associated with the Attribute Name you selected are displayed in the Attribute Values list.
5. Select an attribute value and click OK to close the Attribute Selector.
6. The Item Selector displays the selected attribute value in the Attribute field. The Items list displays all items
that possess the selected attribute value.
7. Select all items in the Items list or a single item, as follows:
Related Topics:
Attribute Selector
Location Selector
Use the Location Selector to select single or multiple locations.
Searching by Location Code
By default, the Location Selector prompts you to filter the list of locations displayed by Location Code. As a result, the
Locations list will include only locations whose code begins with a specific text string.
8
MIPO
To search for locations by Location Code, type the beginning of the desired code in the Location Code field. The
application automatically sorts the results, displaying only locations relevant to the selected scenario, as indicated by the
Relevant locations only check box. Click the Show button to view the set of locations whose code matches your search
string.
Select all locations in the Locations list or a single location, as follows:
• Click OK to select all locations in the Locations list and close the Location Selector.
• To select a single location, click the desired entry and click OK to close the Location Selector.
Displaying All Locations
In addition to filtering locations by Location Code, you can use the Location Selector to display all locations in the
system. To display all locations in the system, select All from the Search by drop-down menu. If a description exists for a
selected location, it is displayed in the Description text box.
If you want to sort the Locations list alphabetically, ensure that the Sort list check box is selected.
If your installation includes a large number of locations, you can page through the Locations list by using the arrow
buttons in the lower left corner of the selector. To go directly to a specific page in a multi-page list, type a page number in
the Page field, and press ENTER. If a location is added to the system, or its code or description are modified, the contents
of the Location Selector are automatically updated.
Select all locations in the Locations list or a single location, as follows:
Filtering by Location Attribute
You can filter the list of locations displayed in the Location Selector based on an attribute associated with a group of
locations.
To filter by location attribute:
2. Click the Browse (...) button next to the Attribute field to open the Attribute Selector. The attributes that you
can use to identify a group of locations are displayed in the Attribute Name drop-down menu. The contents of
this menu is filtered, displaying only valid location attribute names.
Note: The contents of the drop-down menus in the Attribute Selector are specific to your
MIPO system. Attribute Values must also be created and assigned to appropriate entities. For
example, a location attribute could be “City” or “State”.
3. Select the desired attribute from the Attribute Name drop-down menu.
4. The locations associated with the Attribute Name you selected are displayed in the Attribute Values list.
5. Select an attribute value and click OK to close the Attribute Selector.
6. The Location Selector displays the selected attribute value in the Attribute field. The Locations list displays
all locations that possess the selected attribute value.
9
7. Select all locations in the Locations list or a single location, as follows:
Related Topics:
Attribute Selector
Node Selector
Use the Node Selector to select single or multiple nodes.
Filtering by Node Type
You can filter the list of nodes displayed in the Node Selector according to Node Type. To do so, select a node type from
the Node Type drop-down menu and click Show. The Nodes list contains all nodes of that type.
If you want to sort the Nodes list alphabetically, ensure that the Sort list check box is selected.
If your installation includes a large number of nodes, you can page through the Nodes list by using the arrow buttons in
the lower left corner of the selector. To go directly to a specific page in a multi-page list, type a page number in the Page
field, and press ENTER. If a node is added to the system, or its name is modified, the contents of the Node Selector are
automatically updated.
Note: The entries available for selection in the Node Type drop-down menu vary depending on the task
you are currently performing. For example, if you are editing time-varying data for stocking points
(View/Edit > Stocking Point Data > Time Varying), the only node types displayed in the Node Selector
are Stocking Point, Internal Stocking Point, and CF Stocking Point. The node types Process Point
and Supplier Node are not available for selection.
Select all nodes in the Nodes list or a single node, as follows:
• Click OK to select all nodes in the Nodes list and close the Node Selector.
• To select a single node, click the desired entry and click OK to close the Node Selector.
Searching by Node Code
By default, the Node Selector prompts you to filter the list of nodes displayed by Node Code. As a result, the Nodes list
will include only nodes of the selected Node Type whose code begins with a specific text string.
To search for nodes by Node Code, type the beginning of the desired code in the Node Code field. MIPO automatically
sorts the Nodes list alphabetically. Click the Show button to view the set of nodes whose code matches your search
string.
Select all nodes in the Nodes list or a single node, as follows:
10
MIPO
Filtering by Item
You can filter the list of nodes displayed in the Node Selector based on a single item associated with a group of nodes.
Perform the following steps to filter nodes by item:
1. Select the desired node type by using the Node Type drop-down menu.
2. Select Item from the Search by drop-down menu.
3. Click the Browse (...) button next to the Item field to open the Item Selector. Use the Item Selector to select an
item for which you want to view related nodes.
4. Click OK to close the Item Selector.
5. The Node Selector displays the selected item in the Item field. The Nodes list displays all nodes that are
associated with the selected item.
6. If you want to sort the Nodes list alphabetically, ensure that the Sort list check box is selected.
7. Select all nodes in the Nodes list or a single node, as follows:
Filtering by Location
You can filter the list of nodes displayed in the Node Selector based on a single physical location associated with a group
of nodes.
Perform the following steps to filter nodes by location:
2. Select Location from the Search by drop-down list.
3. Click the Browse (...) button next to the Location field to open the Location Selector. Use the Location
Selector to select a location for which you want to view related locations.
4. Click OK to close the Location Selector.
5. The Node Selector displays the selected location in the Location field. The Nodes list displays all nodes that
are associated with the selected location.
Filtering by Attribute
You can filter the list of nodes displayed in the Node Selector based on an attribute associated with a group of nodes.
Perform the following steps to filter nodes by attribute:
11
3. Click the Browse (...) button next to the Attribute field to open the Attribute Selector. Use the Attribute
Selector to select an attribute value for which you want to view related nodes.
MIPO system.
4. Click OK to close the Attribute Selector.
5. The Node Selector displays the selected attribute value in the Attribute field. The Nodes list displays all nodes
Related Topics:
Item Selector
Location Selector
Attribute Selector
Path Selector
Use the Path Selector to select single or multiple paths.
Searching by Path Code
By default, the Path Selector prompts you to filter the list of paths displayed by Path Code. As a result, the Paths list will
include only paths whose code begins with a specific text string.
To search for paths by Path Code, type the beginning of the desired code in the Path Code field. The application
automatically sorts the Paths list alphabetically. Click the Show button to view the set of paths whose code matches your
search string.
Select all paths in the Paths list or a single path, as follows:
1. Click OK to select all paths in the Paths list and close the Path Selector.
2. To select a single path, click the desired entry and click OK to close the Path Selector.
Displaying All Paths
In addition to filtering paths by Path Code, you can use the Path Selector to display all paths in the system. To display all
paths in the system, select All from the Search by drop-down menu. If a description exists for a selected path, it is
displayed in the Description text box.
If you want to sort the Paths list alphabetically, ensure that the Sort list check box is selected.
12
MIPO
If your installation includes a large number of paths, you can page through the Paths list by using the arrow buttons in the
lower left corner of the selector. To go directly to a specific page in a multi-page list, type a page number in the Page field,
and press ENTER. If a path is added to the system, or its name is modified, the contents of the Path Selector are
automatically updated.
Select all paths in the Paths list or a single path, as follows:
• Click OK to select all paths in the Paths list and close the Path Selector.
• To select a single path, click the desired entry and click OK to close the Path Selector.
Filtering by Item
You can filter the list of paths displayed in the Path Selector based on a single item associated with a group of paths.
Perform the following steps to filter paths by item:
item for which you want to view related paths.
4. The Path Selector displays the selected item in the Item field. The Paths list displays all paths that are
associated with the selected item.
5. If you want to sort the Paths list alphabetically, ensure that the Sort list check box is selected.
6. You can further filter the Paths list by clicking the Incoming, Outgoing, or Both radio buttons to view either
incoming paths, outgoing paths, or all paths for the selected item, respectively.
7. Select all paths in the Paths list or a single path, as follows:
You can filter the list of paths displayed in the Path Selector based on a single physical location associated with a group
of paths.
Perform the following steps to filter paths by location:
1. Select Location from the Search by drop-down menu.
Selector to select a location for which you want to view related paths.
4. The Path Selector displays the selected location in the Location field. The Paths list displays all paths that are
associated with the selected location.
incoming paths, outgoing paths, or all paths for the selected location, respectively.
13
Filtering by Node
You can filter the list of paths displayed in the Path Selector based on a node associated with a group of paths.
Perform the following steps to filter paths by node:
1. Select Node from the Search by drop-down menu.
2. Click the Browse (...) button next to the Node field to open the Node Selector. Use the Node Selector to select
a node for which you want to view related paths.
3. Click OK to close the Node Selector.
4. The Path Selector displays the selected node in the Node field. The Paths list displays all paths that are
associated with the selected node.
incoming paths, outgoing paths, or all paths for the selected node, respectively.
You can filter the list of paths displayed in the Path Selector based on an attribute value associated with a group of paths.
Perform the following steps to filter paths by attribute value:
Selector to select an attribute value for which you want to view related paths.
MIPO system.
4. The Path Selector displays the selected attribute type in the Attribute field. The Paths list displays all paths
1. Click OK to select all paths in the Paths list and close the Path Selector.
2. To select a single path, click the desired entry and click OK to close the Path Selector.
Related Topics:
14
MIPO
Item Selector
Location Selector
Node Selector
Attribute Selector
Demand Stream Selector

Use the Demand Stream Selector to select single or multiple demand streams.
Searching by Demand Stream Code
By default, the Demand Stream Selector prompts you to filter the list of paths displayed by Demand Stream Code. As a
result, the Demand Stream list will include only paths whose code begins with a specific text string.
To search for demand streams by Demand Stream Code, type the beginning of the desired code in the Demand Stream
Code field. The application automatically sorts the Demand Stream list alphabetically. Click the Show button to view the
set of paths whose code matches your search string.
Select all demand streams in the Demand Stream list or a single path, as follows:
• Click OK to select all demand streams in the list and close the selector.
• To select a single path, click the desired entry and click OK to close the selector.
Displaying All Demand Streams
In addition to filtering paths by Demand Stream Code, you can use the Demand Stream Selector to display all demand
streams in the system. To display all demand streams in the system, select All from the Search by drop-down menu.
If your installation includes a large number of demand streams, you can page through the Demand Streams list by using
the arrow buttons in the lower left corner of the selector. To go directly to a specific page in a multi-page list, type a page
number in the Page field, and press ENTER. If a path is added to the system, or its name is modified, the contents of the
Demand Stream Selector are automatically updated.
Select all paths in the Demand Streams list or a single demand stream, as follows:
Filtering by Item
You can filter the list of paths displayed in the Demand Stream Selector based on a single item associated with a group
of paths.
Perform the following steps to filter demand streams by item:
15
item for which you want to view related paths.
4. The Demand Stream Selector displays the selected item in the Item field. The Demand Streams list displays
all demand streams that are associated with the selected item.
5. Select all paths in the Demand Streams list or a single demand stream, as follows:
You can filter the list of demand streams displayed in the Demand Stream Selector based on a single physical location
associated with a group of demand streams.
Perform the following steps to filter paths by location:
1. Select Location from the Search by drop-down menu.
Selector to select a location for which you want to view related paths.
4. The Demand Stream Selector displays the selected location in the Location field. The Demand Stream list
displays all paths that are associated with the selected location.
Filtering by Node
You can filter the list of demand streams displayed in the Demand Stream Selector based on a node associated with a
group of paths.
Perform the following steps to filter paths by node:
1. Select Node from the Search by drop-down menu.
2. Click the Browse (...) button next to the Node field to open the Node Selector. Use the Node Selector to select
a node for which you want to view related paths.
4. The Demand Stream Selector displays the selected node in the Node field. The Demand Stream list displays
all paths that are associated with the selected node.
16
MIPO
You can filter the list of demand streams displayed in the Demand Stream Selector based on an attribute value
associated with a group of paths.
Perform the following steps to filter paths by attribute value:
Selector to select an attribute value for which you want to view related paths.
MIPO system.
4. The Demand Stream Selector displays the selected attribute type in the Attribute field. The Demand Streams
list displays all paths that possess the selected attribute value.
Related Topics:
Item Selector
Location Selector
Node Selector
Attribute Selector
Attribute Selector
Use the Attribute Selector to select single or multiple attribute values. By default, the Attribute Selector displays all
attribute values for the selected Attribute Name in the Attribute Values list. The Attribute Type drop-down menu
indicates All and the first Attribute Name listed alphabetically is selected.
If your installation includes a large number of attribute values, you can page through the Attribute Values list by using the
arrow buttons in the lower left corner of the selector. To go directly to a specific page in a multi-page list, type a page
number in the Page field, and press ENTER. If an attribute is added to the system, or its name is modified, the contents of
the Attribute Selector are automatically updated.
Filtering by Attribute Type and Name
You can filter the list of attributes displayed in the Attribute Selector based on an Attribute Type and Attribute Name
associated with a group of attributes.
Note: The contents of the drop-down menus in the Attribute Selector are specific to your system.
Perform the following steps to filter attributes by attribute type and name:
1. Select the desired attribute type from the Attribute Type drop-down menu. The attributes associated with
the Attribute Type you selected are displayed in the Attribute Values list.
17
2. Select the desired attribute name from the Attribute Name drop-down menu. The attributes associated
with the Attribute Type and Attribute Name you selected are displayed in the Attribute Values list.
3. Click OK to select all attributes in the Attribute Values list and close the Attribute Selector.
Related Topics:
Assigning the STAGE Attribute
Quick Links
The Quick Links feature lets you navigate from one screen to other possible destination screens with a single click. This
feature appears as one of the selectors on the left-hand side of the portal user interface.
Use the Quick Link Selector to navigate to another workflow-related screen. Click the arrow button in the upper right
corner of the Quick Link Selector to maximize it
Quick Links associated with the MIPO Import Data Set screen:
• Manage MIPO Scenarios
Quick Links associated with the MIPO View Network screen:
• MIPO Stocking Point Static Inputs Report
• MIPO Supply Path Static Inputs Report
• Audit Data Changes
Quick Links associated with the MIPO Manage Scenarios screen:
• View Alerts
• View Network
• Review Inventory Targets
• Manage DIM Scenarios (if associated scenario is available)
• Manage Data Store
Quick Links associated with the MIPO Review Inventory Targets screen:
Quick Links associated with the DIM Manage Scenarios screen:
18
MIPO
History Feature
The History feature provides a list of links to previously visited application screens. These links are displayed with the
most recently visited screen at the top of the list. Scrolling the mouse over the list displays specific data information
associated with each link as a Tooltip. This information includes the portal, supply chain name, scenario name, etc.,
associated with the link.
To use the History feature:
1. Click History from the bar menu. The History dialog box appears.
2. Scroll through the list of links. Use the mouse to view Tooltip information associated with the links.
3. Click on a link to return to a previously visited screen.
Copyrights & Trademarks

Copyright © 2013 SAP AG. All rights reserved.
SAP® Enterprise Inventory and Service-Level Optimization
This online help facility, as well as the software described herein, is furnished under license and may be used or copied
only within the terms of such license. The content of this manual is furnished for informational use only, is subject to
change without notice, and should not be construed as a commitment by SAP Corporation. SAP assumes no
responsibility or liability for any errors or inaccuracies that may appear in this documentation. Except as permitted by
license, no part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or by any
means, electronic, mechanical, recorded, or otherwise, without the prior written permission of SAP.
Adobe, the Adobe logo, RoboHelp are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation in the United States or other
countries. Adobe Acrobat Reader is a registered trademark of Adobe Systems Incorporated. All other trademarks are the
property of their respective owners.
This product includes unmodified open source libraries from Rhino, a Mozilla.org project (http://www.mozilla.org/rhino/),
covered under the Mozilla Public License (MPL) http://www.mozilla.org/MPL/MPL-1.1.html.
Managing Data Sets

Importing Data
Importing a Data Set (MIPO)
To create a new supply chain or new user scenario for an existing supply chain:
• use the Gateway Loading Tool (SGLT) to generate a .zip file containing validated data
19
• use the Import Data Set window to import the validated .zip file
Data sets are sometimes referred to as loadsets.
Preparing a Data Set
You can install the SGLT by downloading the installation package from the Import Data Set window to your local
machine.
Note: You must have Windows Administrator privileges to install the SGLT on your PC.
To download and install the SGLT used to prepare data sets:
1. Click Data Set > Import Data Set to open the Import Data Set window.
2. Click Download in the row indicating setup.exe. The File Download dialog opens.
3. Click Save to copy the installation package to your local PC. The Save As dialog opens.
4. Specify the directory in which you want to save the installation package and click Save.
5. Double-click the file named setup.exe and follow the prompts to install the SGLT and examples.
Importing a Data Set
1. Click Data Set > Import Data Set to open the Import Data Set window.
Note: You must have privileges to access the Import Data Set window and create a new
scenario in order to import data.
2. Enter the full path and file name of the .zip file you want to import in the File Name field or click Browse ... to
open the Choose File window.
3. Navigate to the directory containing the .zip file that you want to import, select it, and click Open.
4. Click OK.
The Data Set Import History table is updated to include information based on the selected data set, including
the status of the import process.
Once the selected file is successfully imported, you will see the status change to “Completed” in the Data Set
Import History table.
Additionally, the Supply Chain and Scenario Selectors> will include the names of the supply chain specified in
the file you imported.
Note: You do not have privileges to view or edit a supply chain or user scenario you
imported until you log out and sign in again. To verify your user privileges, click Settings >
User Settings > User Privileges tab, and select Scenario Access Control from the
Select Module drop-down menu.
Importing via the Data Loader listener directory
1. Ensure that you have permissions to access the application server and the Data Loader listener directory.
Note: The listener directory is the value specified for the

smartops.dataloader.service.listener.listen_directory property in the smartops.properties
file. The smartops.properties file is located in C:\MIPO_install_dir\myserver\SmartOps on
the application server, where MIPO_install_dir is the root directory where MIPO is
installed (for example, /MIPO).
2. Open Windows Explorer and navigate to the directory containing the .zip file you want to copy to the application
server.
3. Select the correct .zip file and press ctrl+c to copy it.
20
MIPO
4. Use Windows Explorer to navigate to the application server machine and listener directory.
5. Press ctrl+v to paste the .zip file into the listener directory. The Data Loader automatically detects the presence
of a new archive and queues the data set for processing.
Note: If supply chain being loaded in unattended mode has the same name as a
previously loaded supply chain, the application automatically renames the existing
scenario by appending a time date stamp to the file name.
Data loaded via the Data Loader listener directory undergoes the Data Gateway
verification process, even if the data has been previously verified by the SGLT.
Reviewing Import history
At the bottom of the Import Data Set window, there is a list of Import transactions as logged by the application. The
Import history list includes the following information:
• Queued date/time
• Loading Start and End date/time
• User
• Status
• Supply Chain/Scenario
• File name
The Import history is not limited to manual imports, but includes all unattended or attended loads as well.
The Import history list defaults to 50 records. This default value can be changed in the
ImportConfigResources.properties file.
Related Topics:
Viewing a Network
Quick Links
Canceling a data set import

You can cancel importing a data set after the data loading process has started, or if a data set is queued up to be
imported.
To cancel a data set, click the blue X next to the data set record listed in the Data Set Import History. A dialog box
appears, requesting confirmation of the cancellation.
21
Click OK to initiate the cancellation process. The application will stop importing the data set and remove any data that had
been loaded prior to the cancellation.
Exporting Data
Exporting Data Sets (Data Gateway)
The Export Data Set screen allows you to export a selected module scenario to a .zip file on the application server
machine. The .zip file can then be downloaded to your PC and opened in Excel or another spreadsheet program.
Note: Exporting data sets is a user privilege. You must have privileges both to export data
sets and to view and modify the specific data sets you want to export.
To export a scenario to the application server:

1. Use the Product Module Selector to select the application associated with the data set you wish to export
2. Use the Supply Chain Selector to choose the supply chain containing the scenario.
3. Use the Scenario Selector to choose a base or user scenario.
4. Click Data Set > Gateway Export to open the Export Data Set screen.
5. For MIPO data sets only, use the Options selectors to specify demand variability, schedule attainment, and
lead time data sources. See below for more information about these MIPO options.
6. Click the appropriate check boxes to review the export history for all modules and/or all users.
7. Click Export. A .zip file containing the optimized scenario data will be created and saved to the MIPO
application server.
Note: You can cancel exporting a data set after the data loading process has started, or if
a data set is queued up to be exported. To cancel a data set, click the blue X next to the
data set record listed in the History table. A dialog box appears, requesting confirmation of
the cancellation. Click OK to initiate the cancellation process. The Data Gateway will stop
exporting the data set and remove any data that had been loaded prior to the cancellation.
8. Click Refresh. A link to the .zip file will appear in the lower panel of the Export Data Set window. Exported
scenario files are named for the scenario, followed by a number identifying their place in the sequence of other
exported files for the same scenario.
9. To open or save the .zip file containing the scenario data, click on its named link. A File Download dialog will
appear prompting you to open or save the .zip file.
10. To export a different scenario, select it from the list in the scenario selector, then click the Refresh button in the
Export Data Set window and repeat steps 4 through 8 above.
MIPO Export options
When exporting a MIPO data set, the following Forecast Error data source options are available:
• Calculated Forecast Demand: Exports the MIPO scenario inputs for calculated forecast demand.
• Future Forecast & DIM Scenario: Exports future forecast demand only for entities with revision period equal to
the base period of the scenario. Also exports DIM Export processor settings as enabled. If the scenario did not
originally have processor settings, they are added at the end of the processing order.
• DIM Input Data (default): Exports the DIM forecast and sales input data. Also exports DIM Error processor
settings as enabled. If the scenario did not originally have processor settings, they are added at the end of the
processing order.
22
MIPO
When exporting a MIPO data set, the following Lead Time data source options are available:
• User Input or Calculated: Does not export purchase order data. If the original scenario included settings for the
Supply Lead Time processor and the Lead Time processor, those settings are disabled.
• SIM Input Data (default): Exports purchase order data. Also exports Supply Lead Time processor settings as
enabled. If the scenario did not originally have processor settings, they are added at the end of the processing
order.
When exporting a MIPO data set, the following Schedule Attainment data source options are available:
• User Input or Calculated: Exports historical production data. If the original scenario included settings for the
Supply processor and the Production Intelligence processor, those settings are disabled.
• PIM Input Data (default): Exports historical production data. Also exports Production Intelligence processor
processing order.
Viewing Supply Chain Networks

Modeling a Supply Chain
A supply chain model is a graphical representation of a supply chain network and the entities it contains. In MIPO, supply
chains are modeled using different icons to represent each entity. For example, a stocking point is represented by a
triangular symbol.
Since MIPO topology uses demand nodes to satisfy demand stream calculations, these nodes must also be represented
in the supply chain model. Demand nodes are different from physical nodes and are created when more than one demand
stream runs through one physical node. For example, when a node has demand from both a downstream customer facing
node and an internal node, a demand node will be created to separate the two demand streams. They are also used for
customer facing nodes that have demands from multiple customers. By separating multiple demand streams at a single
physical node, MIPO can more accurately calculate demand on upstream nodes. MIPO treats demand nodes as non-
stocking nodes and they are represented in the supply chain model as a pair of brackets surrounding a square.
MIPO data sets can be manually modified to identify all non-managed nodes, which informs MIPO not to include any data
associated with the node in its optimization calculations. Non-managed nodes are represented in the supply chain model
as an empty pair of brackets.
Viewing a Network
In the application, you can view a graphical representation of a supply chain network and the information associated with
the nodes, paths, items, and locations it contains. After you have created or selected a user scenario, you can edit the
information and view how your changes impact the entire network.
Note: Viewing networks requires Java plug-in version specified in the software
requirements of the Installation Guide. If a compatible version of the plug-in is not
currently installed on your machine, you are prompted to download one when you select
View/Edit > View Network for the first time. You must have Windows Administrator
privileges to install the Java plug-in. You are also asked to accept a signed security
certificate.
Perform the following steps to view a network:
1. Click Edit > View Network to open the Network window.
2. Use the Supply Chain Selector to choose a supply chain to display in the Network window.
23
3. By default, the base scenario associated with the selected supply chain, which contains real-world supply chain
data, is selected. If desired, use the Scenario Selector to choose a different scenario to display in the Network
window.
4. By default, the base period is selected. You can choose to view supply chain data for a different period by using
the Period Selector.
5. After you have selected a supply chain, scenario, and period, the network shown is Grouped by Location in
the Network window, by default. Use the Network View selector to choose a different view.
Note: Large networks can take extra time to load. The Network Visualization feature has a
default setting to automatically display the data values associated with the nodes and
paths of the supply chain network. This setting may affect the time to generate the
graphical representation of large supply chains. You can change the default setting for
retrieving data by clicking on Settings > Module Settings from the portal menu, then
clicking the dropdown list to select Network Visualization. The application server must
be restarted in order for the change to take effect.
6. In addition, you can choose specific parameters to display for nodes and paths. Specifically, you can choose
from numerous inputs and output to display for nodes and from several inputs to display for paths by using the
Display Data on Network selector.
At any time you can use the Supply Chain Selector or the Scenario Selector to display a different network. You can
also change the period by using the Period Selector.
Related Topics:
Choosing a Network View
Displaying Data for Nodes and Paths
Modifying the Network Layout
Searching the Network
Printing a Network
Editing Your Display Preferences
Viewing and Editing Data in the Network Window
Quick Links
Choosing a Network View

By default, when you choose a supply chain and scenario to view, you see the network Grouped by Location in the
Network window. You can choose to view the network:
• in its entirety, with each location and node displayed individually
• associated with a specific item
• grouped according to the locations in the network
• grouped according to node attribute
Use the Network View selector to choose a different view. You can change views while the network diagram is loading.
24
MIPO
Viewing the Entire Network

To view the entire network, with each location and node displayed individually, uncheck the Grouped by check box and
ensure the View single item check box is not selected in the Network View selector.
Viewing an Item
You can identify a single item to display and the network for that item is shown. To identify a single item for which to
display the network, you can filter the list of items to include only those whose code begins with a particular text string.
Perform the following steps to select an item for which you want to display the network:
1. Check the View single item check box in the Network View selector located in the selector pane to open the
Item Selector. Use the Item Selector choose an item whose network you want to view.
3. The network for the item you selected is displayed in the Network window.
Grouping by Location
To group entities and their associated data according to their physical location, click the Grouped by check box and the
Location radio button in the Network View selector.
Note:
• When the Grouped by check box is selected, each network that you view
during this MIPO session is displayed grouped according to location or node
attribute. To view the entire network in non-grouped or a different mode,
uncheck the Grouped by check box in the Network View selector.
• If the Grouped by check box is selected, the outputs shown are aggregated for
all items at the selected location. In addition, you cannot select a path and only
outputs for nodes can be displayed in the Network window.
• You can simultaneously use the View single item and Grouped by options in
the Network View selector. The network and data displayed is for the item you
selected and is grouped according to location or node attribute.
Grouping by Attribute
To view a network grouped according to a node attribute, click the Grouped by check box and Attribute radio button in
the Network View selector. Then choose a node attribute from the drop-down menu in the Attribute Selector. Node
attributes are specific to your installation and supply chain structure. For example, unless there exists an attribute named
“STAGE” in your system, it is not displayed in the Attribute Selector.
Note: If node attributes do not exist, or are not assigned to some nodes in a network, you
can encounter problems viewing the network grouped by node attribute. For example,
assume that your supply chain categorizes nodes according to the following "STAGES":
Supplier > Manufacturing In > Manufacturing Out > Assembly > Dealer. If too few nodes,
or no nodes, are assigned the Manufacturing Out attribute, the network diagram appears
disjointed, with the Manufacturing Out STAGE missing:
Supplier > Manufacturing In > ? > Assembly > Dealer
In some situations, the absence of node attributes can prevent the network diagram from
being displayed altogether if you choose to view the network grouped by node attribute.
25
Related Topics:
Creating Attributes
Printing a Network Diagram
Exporting a Network Diagram
Showing and Editing Data in the Network Window
Displaying Data for Nodes and Paths

When displaying a network in the Network window, you can choose specific parameters to display for nodes and paths.
You can choose from numerous inputs and output to display for nodes and from several inputs to display for paths. None
of these input and output parameters are displayed for nodes or paths by default.
• Inputs displayed on a node - The values for these parameters are loaded into the database from external
systems and are used by the optimization engine to generate optimal inventory and service level values.
• Outputs displayed on a node - The values of these parameters calculated by the optimization engine based on
the input parameters to this specific item-location and other locations in the network.
• Inputs displayed on a path - The values for these parameters are loaded into the database from external
systems. These parameters are not used by the optimization engine and are displayed for informational
purposes only.
To select a parameter for which you want to display information for nodes and paths in the Network window, select it from
the Node or Path drop-down menu using the Display Data on Network selector. The network diagram in the Network
window is refreshed and nodes or paths show the inputs or outputs you selected.
At any time, you can select a different parameter or path or node in the network as well as change the period, scenario, or
supply chain being displayed. You can also use the Network View selector to view the network for a specific Item, or
choose to view the network in Grouped by Location or Attribute mode.
Note: If the Grouped by check box is selected, the outputs shown are aggregated for all items at the
selected location. In addition, you cannot select a path and only outputs for nodes can be displayed in the
Network window.
Related Topics:
26
MIPO
Modifying the Network Layout

You can modify the layout of the supply chain network by changing the magnification at which you are viewing it and by
editing your network preferences.
Click Zoom in to increase the magnification at which you are viewing the network, or enter a percentage
less than 100 in the field located to the right and press ENTER.
Click Zoom out to decrease the magnification at which you are viewing the network, or enter a percentage
greater than 100 in the field located to the right and press ENTER.
Click Zoom to fit to resize the network to fit entirely in the Network window.
Related Topics:

The SEARCH tool in the Network window allows you to find a specific item, location, path, or node name in the network
by entering the name of the entity, or the first few letters of the name, to uniquely identify it. Note that the SEARCH tool
identifies only those entities that start with the text string that you enter. The entities that contain the text string in the
middle of the name are not included as valid results.
Note: The SEARCH tool in the Network window is case-insensitive. For example, if you
enter the text “ABC” and click SEARCH, items, locations, paths, and node names
beginning with “ABC” and “abc” are valid results.
To search for a item, location, path, or node name, enter the first few letters of the name in the text box and click
SEARCH. The first entity found that starts with the text string you entered is highlighted in the Network window. To find
the next occurrence of the same text string, click SEARCH again. Note that when identifying network entities that match
the text string you entered, paths are the last entity searched; items, locations, and node names are identified first.
Related Topics:

You can print the network displayed in the Network window, including information specific to that network, such as the
name of the supply chain, scenario, the date it was last modified, and which user made the modifications.
27
Note: If you are printing a network diagram containing a large number of nodes, it cannot
be scaled to fit on a page. To work around this problem, click EXPORT to export the
network diagram you want to print, save it as a bitmap, then open the file using a graphics
editing application such as Microsoft Paint, and scale the image for printing.
Perform the following steps to print a network diagram:
1. Ensure that the Network window contains the network that you want to print and click Print. The network
diagram opens in a new window.
2. The Print dialog opens. Choose your printing options and click Print.
3. Close the window containing the printable network diagram, if desired.
Related Topics:

You can change your network display preferences to specify the orientation and contents of the supply chain you are
viewing in the Network window. After you set your preferences, the settings apply to all of the networks you view. If you
view a network whose structure is significantly different from one you have viewed in the past, or if the structure of a
supply chain changes significantly, you can readjust your settings.
To change your preferences for viewing supply chain networks:
1. Click Preferences in the Network window to open the Display Preferences window.
2. To change how items display in the network, select or deselect the following check boxes in the Network
Display panel:
• Show node names – Displays node names in the network view.
• Show supplier nodes – Displays supplier nodes in the network view.
• Show customer nodes – Displays customer nodes in the network view.
3. To change the layout, modify the following settings in the Layout panel:
Minimum distance between nodes in a layer – The horizontal distance between nodes in pixels. The default is
100 pixels.
• Distance between stages – The vertical distance between stages in the network in pixels. The default is 130
pixels.
• Distance between layers in a stage – The vertical distance between layers in a stage in pixels. The default
distance is 80 pixels.
• Maximum number of nodes in a layer – The maximum number of nodes in a layer. The default number is 20
nodes.
4. To change the orientation, select one of the following layouts: left to right, top to bottom, right to left, bottom to
top.
28
MIPO
5. To view the updated network, click Apply.
6. To save your changes and close the Display Preferences window, click OK.
Note: You can also change your network preferences by clicking Settings > User
Settings to open the User Settings window. The ability to access to the User Settings
window is a user privilege in MIPO.
Related Topics:
Viewing and Editing Data in the Network Window

In addition to the data displayed in the main Network window, such as inputs and outputs for nodes and inputs for paths,
you can view and edit additional information about a network entity that you have selected, in the window below the main
Network window.
Viewing Data in the Network Window

Perform the following steps to view node or path data in the Network window:
1. Use the Supply Chain Selector to select the supply chain for which you want to generate the report.
2. Use the Scenario Selector to select the base or user scenario for which you want to generate the report.
3. Click Edit > View Network to open the Network window.
4. Ensure that you have selected the appropriate network view by using the Network View selector.
5. Select the desired node or path.
Note: The INPUT DATA, OUTPUT DATA, or SHOW DATA buttons are not displayed
when you select a supplier node or customer node in the Network window. No additional
data is displayed for these node types, and the properties associated with them cannot be
edited in the Network window. Also, you cannot edit data for supply paths between
stocking points and process points, and between customer facing stocking points and
customer nodes in the Network window.
6. If you selected a stocking point or a customer facing stocking point, click INPUT DATA or OUTPUT DATA and
one of the following options:
• Input Data Static to open the Edit Stocking Point Data - Static window
• Input Data Time Varying to open the Edit Stocking Point Data - Time Varying (Single Period) window
• Output Data Static to open the Stocking Point Static Outputs Report window
• Output Data Time Varying to open the Stocking Point Time Varying Outputs Report window
Note: If you select a node when viewing a network in Group by Location mode, the
values displayed are aggregated for all items at that location.
7. If you selected a process point, click SHOW DATA > Manufacturing BOM. The Edit Bill of Materials -
Manufacturing window opens.
29
8. If you selected a supply path, click SHOW DATA and one of the following options:
• Input Data Static to open the Edit Path Data - Static window
• Input Data Time Varying to open the Edit Path Data - Time Varying (Single Period) window
Note: When you select a supply path in the network diagram, the INPUT DATA and
OUTPUT DATA menus are enabled only if the view is not Grouped by and the path you
selected has a target node that is a stocking point.
9. You can select a different path or node, as well as change the period, scenario, or supply chain being
displayed. You can also use the Network View selector to specify a different item or that you want to view a
network in Grouped by Location or Grouped by Attribute mode.
Note: The lower portion of the Network window is not automatically updated when you
select an entity that has different properties than your previous selection. For example,
select a stocking point and click INPUT DATA > Input Data Static, to open the Edit
Stocking Point Data - Static window. Then, click on a path. You must
re-select an entry from the INPUT DATA menu, since the inputs for a path differ from a
stocking point.
10. Close the bottom window to view more of the network diagram.
Editing Data in the Network Window

Editing data in the Network window is similar to editing data by using the main windows you access by using the
View/Edit menu. To edit data in the Network window, use the instructions outlined in the following topics:
Editing Stocking Point Static Input Data
Editing Stocking Point Time Varying Input Data (Single Period)
Editing Stocking Point Static Output Data
Editing Stocking Point Time Varying Output Data (Single Period)
Editing Supply Path Static Input Data
Editing Supply Path Time Varying Input Data (Single Period)
Editing Manufacturing BOM
Changing Data Management Preferences
Exporting Stocking Point and Supply Path Data
Printing Stocking Point and Supply Path Data
Note: When you edit data in the Network window, your changes cannot be viewed in the
network diagram until you click REFRESH.
Related Topics:
Stocking Point Time Varying Outputs Report
Stocking Point Static Outputs Report
Maximizing Your Work Area

30
MIPO

You can export a network diagram and save it as a bitmap (.bmp) file. Exported diagrams include the name of the supply
chain and scenario you selected, today's date, and the network view, period, and data you selected to display on nodes
and paths, if any.
Perform the following steps to export a network diagram:
1. Ensure that you are viewing the network that you want to export.
2. Click EXPORT. The Save Picture dialog opens.
3. Choose a directory in which to save the exported file, enter a name the File Name field, and click Save. The
diagram is saved as a bitmap in the directory you specified.
Related Topics:
Editing Supply Chain Data

Values of Input and Output Data Properties
Node Properties
Static Inputs for Nodes Menu Selection
Desired Service Level To access static inputs for

nodes, click Edit > Input
Input Mechanism Data > Stocking Point
Data > Static
Holding Cost Percent
Unit Cost
Unit Purchase Cost
Unit Transfer Price
On Hand Inventory
Unusable On Hand Inventory
Unit of Measure
Periods Between Review
Periods Since Last Review
Pooling Factor
31
Maximum Ship Life
Coverage Duration
Schedule Attainment
Schedule Attainment CV
Storage Capacity
Minimum Service Level
Maximum Service Level
Lost Sales Percentage
Inventory Allocation Policy
Processing Cost
Transportation Cost
Order Administration Cost
Handling Cost
Other Cost
Custom Properties (if any)
Static Outputs for Nodes Menu Selection
Calculated Service Level To access static outputs for

nodes, click Edit > Output
Non-stockout Probability Data > Stocking Point
Data > Static
Average Safety Stock Coverage
Effective Lead Time
End Horizon
Implied Initial On Hand
Modified Service Time
First Reliable Output Period
Average Lost Demand
Average Forecast Mean
Average Forecast CV
Average Safety Stock
Effective Lost Sales Percentage
Time Varying Inputs for Nodes
32
MIPO
Forecast Demand Mean To access time-varying

inputs for nodes, click Edit
Forecast Demand Standard Deviation > Input Data > Stocking
Point Data > Time Varying
Minimum Required Stock
Custom Properties (if any)
Time Varying Outputs for Menu Selection

Nodes
Forecast Demand Mean To access time-varying

outputs for nodes, click Edit
Forecast Demand Standard Deviation > Output Data > Stocking
Point Data > Time Varying
Safety Stock
Cycle Stock
Prebuild Stock
Merchandising Stock
Expected On Hand Stock
Physical Pipeline Stock
Total Pipeline Stock
Target Inventory Position
On Hand Stock (Periods)
Planned Receipts
Safety Stock (Periods)
Unshifted Safety Stock
Unshifted Safety Stock (Periods)
Unshifted Merchandising Stock
Backlog Safety Stock
Lost Sales
Additional Storage Capacity
Additional Supply Capacity
Production Quantity
Reorder Point
Priority Level
Path Properties
33
Static Inputs for Paths Menu Selection
Physical Lead Time To access static inputs for

paths, click Edit > Input
Order Processing Lead Time Data > Supply Path Data
> Static
Other Lead Time
Total Lead Time Mean
Total Lead Time Standard Deviation
Frozen Window
Service Time
Packaging BOM
Yield
Minimum Batch Size (units)
Minimum Batch Size (periods)
Batch Size
Reliability
Mode
Time Varying Inputs for Paths Menu Selection
Maximum Process Capacity To access time-varying

inputs for paths, click Edit
Minimum Process Quantity > Input Data > Supply
Path Data > Time Varying
Supply Ratio
Planned Receipts
Input Data
Editing Stocking Point Data
In the application, a supply chain is modeled as a network of nodes where each node represents an item-location pair.
Each node may have upstream nodes, downstream nodes, or both. Each node is connected to its upstream and
downstream nodes by paths.
Data that does not vary with time is considered to be static data. Examples of static node data include target service
level, holding cost percent, and inventory unit cost. You can edit static inputs for one or multiple stocking points.
Perform the following steps to edit static data for stocking points:
34
MIPO
1. Ensure that you have selected the correct supply chain and a user scenario; you cannot edit the base scenario.
2. Click Edit > Input Data > Stocking Point Data > Static to open the Edit Stocking Point Data - Static window.
3. Click the blue pushpin button to generate a report based on a previously saved filter selection. Otherwise, click
the Browse (...) button to open the Node Selector. Use the Node Selector to choose stocking points to edit.
5. The Edit Stocking Point Output Data - Static window is reloaded and contains the stocking point or stocking
points you selected on the left and all of the editable properties on the right.
6. If numerous stocking points are returned, you can page through them by clicking the arrows in the lower left
corner of the window, or by entering a number in the Page field and pressing ENTER.
7. Select the stocking points that you want to edit:
• Click an individual radio button to edit an individual stocking point.
• Click the All stocking points on all pages radio button to edit all stocking points.
8. Choose the method you want to use to specify your changes by clicking the =x, +x or -x, or the +x% or -x%
radio button.
Note: When editing values that have a pre-defined valid range (such as, .50-.99 for Target
Service Level or 0-1 for Holding Cost Percentage) and you attempt to enter an absolute
value (=x) outside of that range, a status message indicates that the value you entered is
invalid and you are prompted to enter a different value.
However, if you specify a relative change (+x or -x) or a percentage change (+x% or -x%)
that results in a value outside the valid range, the value is automatically rounded up or
down to the closest valid value. For example, if the valid range is 0-1, the current value is
.75, and you increase it by 200%, the resultant value exceeds the valid range. In this
case, the new value that is saved for this property and displayed in the user interface is
one (1).
9. Identify the stocking point properties that you want to edit and enter new values in the fields at the bottom of the
appropriate columns.
Note: Viewing costs is a user privilege. If you are not authorized to view cost information,
the Unit Cost property is not displayed. As a result, you cannot edit this property.
Note: If the Initialization mode for this scenario is set to Automatic in the Scenario
Management window, you cannot edit the value for On Hand Inventory.
10. Click OK to save your changes. The Edit Stocking Point Input Data - Static window is reloaded and displays
a status message indicating that the data was updated successfully. The columns on the right reflect the
changes you made.
Note: The Advanced Report Filtering feature can be used to save the current filter
selection by clicking the black pushpin button.
Related Topics:
Inputs for Nodes
Editing Stocking Point Time Varying Input Data (Single Node)
Editing Stocking Point Time Varying Input Data (Single Property)
35
Advanced Report Filtering for stocking points
Each node can have upstream nodes, downstream nodes, or both. Each node is connected to its upstream and
downstream nodes by paths. Data that varies with time is considered to be time varying data. Examples of time varying
node data include forecast demand mean, forecast demand standard deviation, and minimum required stock.
Perform the following steps to edit time-varying data for stocking points for a single period:
2. Use the Period Selector to choose the period for which you want to edit data.
3. Click Edit > Input Data > Stocking Point Data > Time Varying to open the Edit Stocking Point Input Data -
Time Varying (Single Period) window.
6. The Edit Stocking Point Input Data - Time Varying (Single Period) window is reloaded and contains the
stocking point or stocking points you selected on the left and all of the editable properties on the right.
radio button.
Note: You can edit Forecast Demand Mean and Forecast Demand Standard Deviation for
Customer Facing Stocking Points only. Also, if you select more than one Node Type (for
example, a combination of Internal and Customer Facing nodes), the Forecast Demand
Mean and Forecast Demand Standard Deviation fields are not editable.
11. Click OK to save your changes. The Edit Stocking Point Input Data - Static (Single Period) window is
reloaded and displays a status message indicating that the data was updated successfully. The columns on the
right reflect the changes you made for the nodes you selected.
Related Topics:
Inputs for Nodes

36
MIPO
Navigating Time Varying Data Editing and Reports Windows
Perform the following steps to edit multiple properties for a single node for all selected periods:
4. Click the Browse (...) button to open the Node Selector. Use the Node Selector to choose stocking points to
edit.
6. The Edit Stocking Point Data - Time Varying (Single Period) window is reloaded. It contains the stocking
point or stocking points you selected on the left and all of the editable properties on the right. Note that the
stocking point and property names are hyperlinks.
8. To edit time-varying data for a single node for multiple periods, click on a stocking point name.
9. The Edit Stocking Point Input Data - Time Varying (Single Node) window opens. It contains the time-varying
properties on the left and each of the periods in the display horizon on the right. Note that the name of the node
you are editing is listed in the Choose Nodes to Edit field near the top of the window.
radio button.
11. Specify the length of time for which you want to apply your changes by specifying values for the Edit Period
From and Edit Period To fields. To do so, click the Browse (...) button and use the Period Selector.
12. Identify the properties that you want to edit and enter new values in the fields to the right of the appropriate
rows. Note that your changes are applied for all periods you specified.
13. Click OK to save your changes. The Edit Stocking Point Input Data - Time Varying (Single Node) window is
reloaded and displays a status message indicating that the data was updated successfully. The window reflects
the change you made for the nodes and all properties and periods you specified.
Note: You can change the stocking point for which you editing time-varying properties by
clicking the Browse (...) button next to the Choose Nodes to Edit field. Using the Node
Selector to choose a different node or group of nodes to edit.
37
Related Topics:
Inputs for Nodes
Perform the following steps to edit a single property for multiple nodes and periods:
6. The Edit Stocking Point Input Data - Time Varying (Single Period) window is reloaded. It contains the
stocking point or stocking points you selected on the left and all of the editable properties on the right. Note that
the stocking point and property names are hyperlinks.
7. To edit a single property for single or multiple nodes and periods, click on a property name.
8. The Edit Stocking Point Input Data - Time Varying (Single Property) window opens. It contains the nodes
on the left and each of the periods in the display horizon on the right. Note that the name of the property you
selected is listed in the Choose Time Varying Properties drop-down menu near the top of the window.
radio button.
11. Identify the periods that you want to edit and enter new values in the fields at the bottom of the appropriate
columns or enter the same value for all periods by entering it in the field in the first column.
12. Click OK to save your changes. The Edit Stocking Point Input Data - Time Varying (Single Property)
window is reloaded and displays a status message indicating that the data was updated successfully. The
window reflects the change you made for the property, nodes, and periods you specified.
38
MIPO
Related Topics:
Inputs for Nodes
Editing Supply Path Data
A supply path is a connection between two nodes in a supply chain. It represents the physical movement of material in a
supply chain. Data that does not vary with time is considered to be static data. Examples of static data on paths include
lead time, yield, and batch size. You can edit static inputs for one or multiple supply paths.
Perform the following steps to edit static data for supply paths:
2. Click Edit > Input Data > Supply Path Data > Static to open the Edit Path Data - Static window.
3. Click the Browse (...) button to open the Path Selector. Use the Path Selector to choose paths that you want to
edit.
Note: You can only view and edit restricted paths, which are paths whose downstream
node is a stocking node.
4. Click OK to close the Path Selector.
5. The Edit Path Data - Static window is reloaded and contains the path or paths you selected on the left and all
of the editable properties on the right.
6. If numerous paths are returned, you can page through them by clicking the arrows in the lower left corner of the
window, or by entering a number in the Page field and pressing ENTER.
7. Select the paths that you want to edit:
• Click an individual radio button to edit an individual path.
• Click the All Paths on all pages radio button to edit all paths.
radio button.
39
Note: When editing values that have a pre-defined valid range (such as, 0-1 for Yield or
Reliability) and you attempt to enter an absolute value (=x) outside of that range, a status
message indicates that the value you entered is invalid and you are prompted to enter a
different value.
one (1).
9. Identify the path properties that you want to edit and enter new values in the fields at the bottom of the
10. Click OK to save your changes. The Edit Path Data - Static window is reloaded and displays a status message
indicating that the data was updated successfully. The columns on the right reflect the changes you made.
Related Topics:
Inputs for Paths
Editing Supply Path Time Varying Input Data (Single Path)
Editing Supply Path Time Varying Input Data (Single Property)
Editing Supply Path Time Varying Data (Single Period)
supply chain. Data that varies with time is called time varying data. Examples of time varying data on paths include
maximum process capacity, minimum process quantity, and supply ratio.
To edit time-varying data for paths for a single period:
3. Click Edit > Input Data > Supply Path Data > Time Varying to open the Edit Path Data - Time Varying
(Single Period) window.
4. Click the Browse (...) button to open the Path Selector. Use the Path Selector to choose the paths you want to
edit:
• To choose an individual path, filter paths by using the Search by drop-down menu. Click the path you want
to edit and click OK.
• To choose all paths, choose All from the Search by menu and click OK.
5. The Edit Path Data - Time Varying (Single Period) window is reloaded and contains the path or paths you
selected on the left and all of the properties on the right.
40
MIPO
7. Select the paths you want to edit:
• Click the radio button beside a path name to edit an individual path.
• Click the All paths on all pages radio button to edit all paths.
radio button.
Note: When editing values that have a pre-defined valid range (such as, 0-1 for Supply
Ratio) and you attempt to enter an absolute value (=x) outside of that range, a status
different value.
one (1).
When specifying a value for Maximum Process Capacity, you can enter a numeric
value (a capacity constraint) or set the value to Unconstrained. Unconstrained capacity
describes a supply path that can process an infinite number of units each period in order
to satisfy demand.
Click this icon to set capacity on a supply path to Unconstrained.
Click this icon and enter a numeric value for Maximum Process Capacity to apply a
capacity constraint to a supply path. Capacity can be specified in all periods, regardless
of the PBR value.
Planned Receipts can only be entered and edited for user scenarios that have
Initialization set to User Specified.
10. Click OK to save your changes. The Edit Path Data - Static (Single Period) window is reloaded and displays a
status message indicating that the data was updated successfully. The columns on the right reflect the changes
you made for the paths you selected.
Related Topics:
Inputs for Paths
41
supply chain. Data that varies with time is considered to be time varying data. Examples of time varying data on paths
include maximum process capacity, minimum process quantity, and supply ratio.
Perform the following steps to edit multiple properties for a path for all selected periods:
edit.
selected on the left and all of the properties on the right. Note that the path and property names are hyperlinks.
8. To edit multiple properties for a single path for multiple periods, click on a path name.
9. The Edit Path Data - Time Varying (Single Path) window opens. It contains the time-varying properties on the
left and each of the periods in the display horizon on the right. Note that the name of the path you are editing is
displayed in the Choose Path to Edit field near the top of the window.
radio button.
different value.
one (1).
42
MIPO
Note: When specifying a value for Maximum Process Capacity, you can enter a numeric
to satisfy demand.
capacity constraint to a supply path. Capacity can be specified in all periods, irrespective
of the PBR value.
13. Click OK to save your changes. The Edit Path Data - Time Varying (Single Path) window is reloaded and
displays a status message indicating that the data was updated successfully. The window reflects the changes
you made for the path and all properties and periods you specified.
Note: You can change the path for which you editing time-varying properties by clicking
the Browse (...) button next to the Choose Path to Edit field. Use the Path Selector to
choose a different path or group of paths to edit.
Related Topics:
Inputs for Paths
Editing Supply Path Time Varying Data (Single Property)
supply chain. Data that varies with time is considered to be time varying data. Examples of time varying data on paths
include maximum process capacity, minimum process quantity, and supply ratio.
Perform the following steps to edit a single property for multiple paths and periods:
edit.
selected on the left and all of the properties on the right. Note that the supply path and property names are
hyperlinks.
43
7. To edit a single property for single or multiple paths and periods, click on a property name.
8. The Edit Path Data - Time Varying (Single Property) window opens. It contains the paths on the left and each
of the periods in the display horizon on the right. Note that the name of the property you selected is listed in the
Choose Time Varying Properties drop-down menu near the top of the window.
• Click the All paths on all pages radio button to edit all paths.
radio button.
different value.
one (1).
to satisfy demand.
capacity constraint to a supply path. Capacity can be specified in all periods, irrespective
of the PBR value.
12. Click OK to save your changes. The Edit Path Data - Time Varying (Single Property) window is reloaded and
displays a status message indicating that the data was updated successfully. The window reflects the change
you made for the property, paths, and periods you specified.
Note: You can change the time-varying property you are editing by selecting a different
one from the Choose Time Varying Properties drop-down menu.
Related Topics:
Inputs for Paths
44
MIPO
Editing Demand Stream Data
Editing Demand Stream Static Input Data
The demand stream is the supply path between the customer-facing stocking point and the customer. The static data
associated with the demand stream includes the desired service level, frozen window, and service time. You can edit
static inputs for one or multiple demand streams.
To edit static data for demand streams:

2. Click Edit > Input Data > Demand Stream > Static to open the Edit Demand Stream Data - Static window.
3. Click the Browse (...) button to open the Demand Stream Selector. Use the Demand Stream Selector to
choose paths that you want to edit.
4. Click OK to close the selector.
5. The Edit Demand Stream Data - Static window is reloaded and contains the demand stream or streams you
selected on the left and all of the editable properties on the right.
6. If numerous demand streams are returned, you can page through them by clicking the arrows in the lower left
• Click the All Demand Streams on all pages radio button to edit all demand streams.
radio button.
different value.
one (1).
9. Identify the demand stream properties that you want to edit and enter new values in the fields at the bottom of
the appropriate columns.
10. Click OK to save your changes. The Edit Demand Stream Data - Static window is reloaded and displays a
you made.
Related Topics:
Inputs for Paths
45
Editing Demand Stream Lag Specific Data (Single Lag)
Editing Demand Stream Lag Specific Data (Single Lag)
The demand stream is the supply path between the customer-facing stocking point and the customer. The lag-specific
data associated with the demand stream includes the CV and the bias. You can edit lag specific inputs for one or multiple
demand streams.
To edit lag-specific demand stream data for a single lag:

2. Click Edit > Input Data > Demand Stream > Lag Specific to open the Edit Demand Stream Input Data
(Single Lag) window.
5. Click REFRESH. The Edit Demand Stream Input Data (Single Lag) window is reloaded and contains the
demand stream or streams you selected on the left and all of the editable properties on the right.
7. By default, the values for Lag 0 are displayed. To change the lag of all the displayed demand streams, select a
new lag value from the Lag drop-down in the upper right side of the window and click REFRESH.
radio button.
different value.
one (1).
11. Click OK to save your changes. The Edit Demand Stream Input Data (Single Lag) window is reloaded and
displays a status message indicating that the data was updated successfully. The columns on the right reflect
the changes you made.
46
MIPO
Related Topics:
Inputs for Paths
Editing Demand Stream Static Data
Demand Stream Lag Specific Data (Single Property)
Demand Stream Lag Specific Data (Single Property)
The demand stream is the supply path between the customer-facing stocking point and the customer. The lag-specific
data associated with the demand stream includes the CV and the bias. You can edit lag specific inputs for one or multiple
demand streams.
To edit lag-specific demand stream data for a single property:

2. Click Edit > Input Data > Demand Stream > Lag Specific to open the Edit Demand Stream Input Data
(Single Lag) window.
4. Click OK to close the Demand Stream Selector.
5. Click REFRESH. The Edit Demand Stream Input Data (Single Lag) window is reloaded and contains the
demand stream or streams you selected on the left and all of the editable properties on the right. Note that the
property names are hyperlinks.
7. To edit a single property for single or multiple demand streams and lags, click on a property name.
8. The Edit Demand Stream Input Data (Single Property) window opens. It contains the demand streams on the
left and each of the lags for the demand stream on the right. Note that the name of the property you selected is
listed in the Choose Property to Edit drop-down menu near the top of the window
radio button.
different value.
47
one (1).
10. Identify the lags for which you want to edit the property and enter new values in the fields at the bottom of the
11. Click OK to save your changes. The Edit Demand Stream Input Data (Single Property) window is reloaded
and displays a status message indicating that the data was updated successfully. The columns on the right
reflect the changes you made.
Related Topics:
Inputs for Paths
Editing Demand Stream Static Data
Demand Stream Lag Specific Data (Single Lag)
Editing Network Structure
Creating Nodes
Creating an Internal Stocking Node

Each node may have upstream nodes (suppliers), downstream nodes (customers), or both. Each node is connected to its
upstream and downstream nodes by paths.
By default, a stocking node is represented by this icon in the Network window. However,
your organization can specify different icons to represent different types of nodes.
Note: If you want to associate the node you are creating with an item, attribute, or
physical location that does not yet exist in the MIPO system, you must create the item,
attribute, or location before creating the node.
Perform the following steps to create an internal stocking node:
2. Click Edit > Input Data > Network Structure > Nodes to open the Edit Network Structure - Node window.
3. Click CREATE to open the Create Network Structure - Node window.
4. Select Internal Stocking Node from the Node Type drop-down menu.
5. Select the Stocking Node Type from the drop-down menu (e.g., either stocking node, non-managed node, or
non-stocking node).
6. Enter the name of the node in the Name field.
Note: The following special characters are not supported for use in node names: single
quote ('), double quote (”), backslash (\), angle brackets (>,<), ampersand (&), and pipe
(|).
7. Click the Browse (...) button to open the Item Selector. Use the Item Selector to choose an item associated
with the node you are creating. Click OK to close the Item Selector.
8. Click the Browse (...) button to open the Location Selector. Use the Location Selector to choose a physical
location associated with the node you are creating. Click OK to close the Location Selector.
9. If you want to add attributes for the node you are creating, click ADD to open the Attribute Selector. Select the
attribute you want to add, and click OK to close the Attribute Selector.
48
MIPO
10. Click NEXT to open the Create Network Structure - Node window, Step 2.
11. Enter appropriate values for the node's static inputs. Note that values for Target Service Level, Holding Cost
Percent, and Unit Cost are required.
Note: Viewing costs is a user privilege in MIPO. If you are not authorized to view cost
information, the Unit Cost column is not displayed. As a result, you can create the node,
but the scenario containing it cannot be validated successfully because it is missing unit
cost data. An authorized user must enter the unit cost for the node before the scenario
can be validated successfully.
Note: If the Initialization mode for this scenario is set to User-specified in the Scenario
Management window, you must enter a value for On Hand Inventory when creating a
stocking point. Failing to enter a value for On Hand Inventory causes a Missing On
Hand alert to be generated during validation.
12. Enter values for each time period for the time-varying input, Minimum Required Stock, if desired. Note that the
Data Horizon shown for time-varying properties is specified in the Scenario Management window.
13. Click NEXT. Depending on how the application is implemented for your organization, you may be prompted to
enter values for Custom time-varying properties:
• If your organization's supply chain contains Custom inputs, enter appropriate values for each time period,
and click NEXT.
• If your organization's supply chain does not contain Custom inputs, click FINISH to create the node.
14. The Edit Network Structure - Node window opens, containing a text message indicating that the node was
created successfully.
15. Click Edit > View Network. By default, the node you created is displayed in the Network window when you are
viewing the entire network. To incorporate this node into your network, create a path or paths attaching it.
Related Topics:
Creating a Customer Facing Stocking Node
Creating a Process Node
Creating a Supplier Node
Deleting Nodes

Customer facing stocking nodes are locations at which end-customer demand occurs. Only stocking locations with no
downstream stocking locations can be customer facing locations. In general, however, it is possible for all stocking
locations to serve end-customer demand.
By default, a stocking node is represented by this icon in the Network window. However,
physical location that does not yet exist in the system, you must create the item, attribute,
or location before creating the node.
Perform the following steps to create a customer facing stocking node:
49
4. Select Customer Facing Stocking Node from the Node Type drop-down menu.
5. Select the Stocking Node Type from the drop-down menu (e.g., either stocking node, non-managed node, or
non-stocking node).
(|).
7. Click the Browse (...) button to open the Item Selector. Use the Item Selector to choose an item associated
with the node you are creating. Click OK to close the Item Selector.
11. Enter appropriate values for the node's static inputs. Note that values for Target Service Level, Holding Cost
Percent, and Unit Cost are required.
Note: Viewing costs is a user privilege. If you are not authorized to view cost information,
the Unit Cost column is not displayed. As a result, you can create the node, but the
scenario containing it cannot be validated successfully because it is missing unit cost
data. An authorized user must enter the unit cost for the node before the scenario can be
validated successfully.
Note: If the Initialization mode for this scenario is set to User-specified in the Scenario
Management window, you must enter a value for On Hand Inventory when creating a
stocking point. Failing to enter a value for On Hand Inventory causes a Missing On
Hand alert to be generated during validation.
12. Enter values for each time period for the time-varying input, Forecast Demand Mean, if desired. Note that the
Data Horizon shown for time-varying properties is specified in the Scenario Management window.
14. Enter values for each time period for the time-varying input, Forecast Demand Standard Deviation, if desired.
16. Enter values for each time period for the time-varying input, Minimum Required Stock, if desired.
17. Click NEXT. Depending on how MIPO is implemented for your organization, you may be prompted to enter
values for Custom time-varying properties:
• If your organization's supply chain contains Custom inputs, enter appropriate values for each time period,
and click NEXT.
• If your organization's supply chain does not contain Custom inputs, click FINISH to create the node.
19. Click Edit > View Network. By default, the node you created is in the Network window when you are viewing
the entire network.
Note: When you create a customer facing stocking node, a path connecting it to a
customer node is automatically created. If no customer nodes exist, one is automatically
created.
50
MIPO
By default, a customer node is represented by this icon in the Network window. However,
Related Topics:
Deleting Nodes

A supply chain is modeled as a network of nodes where each node represents an item-location pair. Each node can have
upstream nodes (suppliers), downstream nodes (customers), or both. Each node is connected to its upstream and
By default, a process node is represented by this icon in the Network window. However,
Perform the following steps to create a process node:
4. Select Process Node from the Node Type drop-down menu.
(|).
6. Click the Browse (...) button to open the Item Selector. Use the Item Selector to choose an Outgoing Item
associated with the node you are creating. Click OK to close the Item Selector.
7. Click the ADD to open the Item Selector. Use the Item Selector to choose an Incoming Item associated with
the node you are creating. Click OK to close the Item Selector.
10. Click OK to create the process node.
13. If desired, specify a manufacturing BOM relationship for this process node by using the instructions in Editing
Manufacturing BOM.
51
Related Topics:
Deleting Nodes

A supply chain is modeled as a network of nodes where each node represents an item-location pair. Each node may have
By default, a supplier node is represented by this icon in the Network window. However,
Perform the following steps to create a supplier node:
4. Select Supplier Node from the Node Type drop-down menu.
(|).
8. Click OK to create the supplier node.
Related Topics:
Deleting Nodes
52
MIPO
Editing Network Structure - Nodes
A supply chain is modeled as a network of nodes where each node represents an item-location pair. Each node can have
Perform the following steps to edit a node:
3. Click the Browse (...) button next to the Name field to open the Node Selector. Use the Node Selector to
choose a node to edit. Click OK to close the Node Selector.
4. The Node Type field specifies the type of node you selected. Depending on the type of node you selected, you
can edit different data:
• Process Node - Outgoing Item, Incoming Items, Location, and Attributes can be edited.
• Stocking Node (Internal and Customer Facing) - Item, Location, and Attributes can be edited. This is the
default Node Type in the Node Selector.
• Supplier Node - Location and Attributes can be edited.
5. If you selected a process node, click the Browse (...) button next to the Outgoing Item field to open the Item
Selector. Use the Item Selector to choose a different outgoing item for this node, if desired. Click OK to close
the Item Selector.
6. If you selected a process node, and you want to add an incoming item, click ADD to open the Item Selector.
Use the Item Selector to choose an incoming item for this node. Click OK to close the Item Selector.
7. If you selected a process node, and want to remove existing incoming items, check the check box for the
Incoming Item you want to remove, and click REMOVE.
8. If you selected an internal or customer facing stocking node, and want to change the item, click the Browse (...)
button next to the Item field to open the Item Selector. Use the Item Selector to choose a new item. Click OK
to close the Item Selector.
9. If you want to change the physical location associated with a node, click the Browse (...) button next to the
Location field to open the Location Selector. Use the Location Selector to choose a new location for the node.
Click OK to close the Location Selector.
10. If you want to add attributes to a node, click ADD to open the Attribute Selector. Select the attribute you want to
add, and click OK to close the Attribute Selector.
11. If you want to remove existing attributes from a node, check the check box for the attribute you want to remove,
and click REMOVE.
12. Click OK to save your changes. The Edit Network Structure - Node window is reloaded and contains a status
message indicating that the node was updated successfully.
Related Topics:
Deleting Nodes
53
Creating Paths
A path is a connection between two nodes in a supply chain. It represents the physical movement of material in a supply
chain.
Note: If you want to associate the path you are creating with node or attribute that does
not yet exist in the system, you must create the node or attribute before creating the path.
Perform the following steps to create a path:
2. Click Edit > Input Data > Network Structure > Paths to open the Edit Network Structure - Path window.
3. Click CREATE to open the Create Network Structure - Path window.
4. Enter the name of the path in the Path Name field.
Note: The following special characters are not supported for use in path names: single
(|).
5. Click the Browse (...) button to open the Node Selector. Use the Node Selector to choose a Source Node
associated with the path you are creating. Source node types are Supplier Nodes, Process Nodes, and Internal
Stocking Nodes. Click OK to close the Node Selector.
6. Click the Browse (...) button to open the Node Selector. Use the Node Selector to choose a Destination
Node associated with the path you are creating. Destination node types are Process Nodes, Internal Stocking
Nodes, and CF Stocking Nodes. Click OK to close the Node Selector.
7. If you want to add attributes for the path you are creating, click ADD to open the Attribute Selector. Select the
8. Click NEXT to open the Create Network Structure - Path window, Step 2.
9. Enter appropriate values for the path's static inputs, if desired.
11. Enter values for each time period for the time-varying input, Maximum Process Capacity, if desired. Note that
the Data Horizon shown for time-varying properties is specified in the Scenario Management window.
to satisfy demand.
capacity constraint to a supply path.
13. Enter values for each time period for the time-varying input, Minimum Process Quantity, if desired.
15. Enter values for each time period for the time-varying input, Supply Ratio if desired.
16. Click FINISH to create the path.
17. The Edit Network Structure - Path window opens, containing a status message that indicates that the path
was created successfully.
54
MIPO
18. Click Edit > View Network. By default, the path you created is displayed in the Network window connecting the
nodes you specified.
Related Topics:
Deleting Paths
Deleting Nodes
Editing Network Structure - Paths
A path is a connection between two nodes in a supply chain. It represents the physical movement of material in a supply
chain.
Perform the following steps to edit a path:
3. Click the Browse (...) button next to the Path Name field to open the Path Selector. Use the Path Selector to
choose a path to edit. Click OK to close the Path Selector. If any attributes exist for this path, they are
displayed automatically.
4. Click the Browse (...) button next to the Source Node field to open the Node Selector. Use the Node Selector
to choose a different source node for the path. Click OK to close the Node Selector. The Node Type field
indicates the node type of the source node you selected.
Note: While you can change the source node of a path, you cannot choose a source node
that is a different node type.
5. Click the Browse (...) button next to the Destination Node field to open the Node Selector. Use the Node
Selector to choose a different destination node for the path. Click OK to close the Node Selector. The Node
Type field indicates the node type of the destination node you selected.
Note: While you can change the destination node of a path, you cannot choose a
destination node that is a different node type.
6. If you want to add attributes to this path, click ADD to open the Attribute Selector. Select the attribute you want
to add, and click OK to close the Attribute Selector.
7. If you want to remove existing attributes from this path, check the check box for the attribute you want to
remove, and click REMOVE.
8. Click OK to save your edits. The Edit Network Structure - Path window is reloaded and contains a status
message indicating that the path was updated successfully.
Related Topics:
Creating Paths
Deleting Paths
55
Editing Master Data
Editing Master Data - Items
An item is a uniquely identified, single product in inventory.
Perform the following steps to edit an item:
2. Click Edit > Input Data > Master Data > Items to open the Edit Master Data - Items window.
3. Click the Browse (...) button next to the Item field to open the Item Selector. Use the Item Selector to choose
an item to edit. Click OK to close the Item Selector. The Unit of Measure and Product Family fields are
automatically populated with values if they exist in the supply chain.
4. Enter a description in the Description field if desired.
5. If you want to add attributes to this item, click ADD to open the Attribute Selector. Select the attribute you want
to add, and click OK to close the Attribute Selector.
6. If you want to remove existing attributes from this item, check the check box for the attribute you want to
7. Click OK to save your edits. The Edit Master Data - Items window is reloaded and contains a status message
indicating that the item was updated successfully.
Related Topics:
Creating Items
Editing Master Data - Locations
A location is any physical point in the supply chain at which inventory is stored. Factories, warehouses, distribution
centers, and retail stores are all types of locations.
Perform the following steps to edit a location:
2. Click Edit > Input Data > Master Data > Locations to open the Edit Master Data - Locations window.
Selector to choose a location to edit. Click OK to close the Location Selector.
4. Enter a description in the Description field if desired.
5. If you want to add attributes to this location, click ADD to open the Attribute Selector. Select the attribute you
want to add, and click OK to close the Attribute Selector.
6. If you want to remove existing attributes from this location, check the check box for the attribute you want to
7. Click OK to save your edits. The Edit Master Data - Locations window is reloaded and contains a status
message indicating that the location was updated successfully.
Related Topics:
56
MIPO
Creating Locations
Editing Master Data - Attributes
Attributes are user-defined characteristics of an item that allow you to group sets of like items. For example, an attribute
of a person might be eye color. You could group people into those with blue eyes, those with brown eyes, etc. Attributes
can be used to select a group on which to perform analysis.
You can define several types of attributes:
• Location attributes are characteristics of a location or locations and are custom defined for each
implementation. Examples include geographical district, location type (warehouse, factory, distribution center).
• Item attributes are characteristics of an item or set of items and are custom defined for each implementation.
Examples include language, item type, and usage.
• Node attributes are characteristics of a node or set of nodes and are custom defined for each implementation.
Examples include node type or stage such as supplier or vendor.
• Path attributes are characteristics of a path or set of paths and are customer defined for each implementation.
Examples include transportation type, such as ground or air.
Perform the following steps to edit an attribute value:
2. Click Edit > Input Data > Master Data > Attributes to open the Edit Master Data - Attributes window.
Selector to choose an attribute to edit. Click OK to close the Attribute Selector. The list of Current Attribute
values is populated automatically if values already exist.
4. If you want to add an attribute value to this attribute, enter a new attribute value in the Attribute Value field and
click the Add (+>>) button.
5. If you want to remove an existing attribute value from this attribute, check the check box for the attribute value
you want to remove, and click Remove (<<).
6. Click OK to save your edits. The Edit Master Data - Attributes window is reloaded and contains a status
message indicating that the attribute was updated successfully.
Related Topics:
Creating Attributes
Creating Items
An item is a uniquely identified, single product in inventory.
Perform the following steps to create an item:
2. Click Edit > Input Data > Master Data > Items to open the Edit Master Data - Items window.
3. Click CREATE to open the Create Master Data - Items window.
57
4. Enter the name of the item in the Item field.
Note: The following special characters are not supported for use in item names: single
(|).
5. Specify a Unit of Measure for the item by selecting it from the drop-down menu.
6. Specify a Product Family for the item by selecting it from the drop-down menu.
7. Enter a description in the Description field, if desired.
8. If you want to add attributes for the item you are creating, click ADD to open the Attribute Selector. Select the
9. Click OK. The Edit Master Data - Items window opens containing a status message indicating that the item
was created successfully.
Note: Items cannot be deleted by using the MIPO interface.
Related Topics:
Editing Master Data - Items
Creating Locations
A location is any physical point in the supply chain at which inventory is stored. Factories, warehouses, distribution
centers, and retail stores are all types of locations.
Perform the following steps to create a location:
2. Click Edit > Input Data > Master Data > Locations to open the Edit Master Data - Locations window.
3. Click CREATE to open the Create Master Data - Locations window.
4. Enter the name of the location in the Location field.
Note: The following special characters are not supported for use in location names: single
(|).
5. Enter a description in the Description field, if desired.
6. If you want to add attributes for the location you are creating, click ADD to open the Attribute Selector. Select
the attribute you want to add, and click OK to close the Attribute Selector.
7. Click OK. The Edit Master Data - Locations window opens containing a status message indicating that the
location was created successfully.
Note: Locations cannot be deleted by using the MIPO interface.
Related Topics:
Editing Master Data - Locations
58
MIPO
Creating Attributes
Attributes are user-defined characteristics of an item that allow you to group sets of like items. For example, an attribute
of a person might be eye color. You could group people into those with blue eyes, those with brown eyes, etc. Attributes
can be used to select a group on which to perform analysis.
You can define several types of attributes:
• Location attributes are characteristics of a location or locations and are custom defined for each
implementation. Examples include geographical district, location type (warehouse, factory, distribution center).
• Item attributes are characteristics of an item or set of items and are custom defined for each implementation.
Examples include language, item type, and usage.
• Node attributes are characteristics of a node or set of nodes and are custom defined for each implementation.
Examples include node type or STAGE such as supplier or vendor.
• Path attributes are characteristics of a path or set of paths and are customer defined for each implementation.
Examples include transportation type, such as ground or air.
Perform the following steps to create an attribute:
3. Click CREATE to open the Create Master Data - Attributes window.
4. Enter a new attribute name in the Attribute field.
Note: The following special characters are not supported for use in attribute names: single
(|).
5. Enter a new attribute value in the Attribute Value field and click the ADD (+>>) button to add it to the Current
Attribute Values field.
6. If you want to remove an attribute value that you created, check the check box for the attribute value you want
to remove, and click REMOVE (<<).
7. When you are finished adding and removing attribute values, click OK. The Edit Master Data - Attributes
window opens containing a status message indicating that the attribute was created successfully.
8. Select the Edit Network Structure or Edit Master Data menu to add this attribute to nodes, paths, items, or
locations.
Note: Attributes cannot be deleted by using the MIPO interface. However, you can
remove attribute values.
Related Topics:
Editing Master Data - Attributes
59
Editing Bill of Materials (BOM)
Filtering and Sorting Manufacturing BOMs
You can limit which manufacturing BOMs you view by filtering them based on the items with which they are associated
and also according to BOM Name. The following sections provide instructions about how to filter manufacturing BOMs
using each method.
Filtering by Item
Perform the following steps to filter manufacturing BOMs by item:
1. Click Edit > Input Data > Bill of Materials > Manufacturing to open the Edit Bill of Materials -
Manufacturing window.
2. Enter the name of an item or click Browse (...) to open the Item Selector. Use the Item Selector to choose an
item associated with the manufacturing BOM you want to view.
4. Check the Components or Where Used check box, or both, as follows:
• Check the Components check box to view all of the component items that were required to produce a
material (the outgoing item from a process node).
• Ensure that the Where Used check box is checked to view all of the materials that use the component
item (the incoming item for a process node).
• Check both the Components and Where Used check boxes to view all manufacturing BOMs for selected
item, whether it is a component or a material item.
5. If you want to further filter the manufacturing BOMs returned for the selected item, select the name of a
manufacturing BOM associated with the item from the BOM Name drop-down menu.
6. Click REFRESH. The window is updated and contains the manufacturing BOMs for the item and, optionally, the
BOM Name you selected.
Filtering by BOM Name

Perform the following steps to filter manufacturing BOMs by name:
1. Click Edit > Input Data > Bill of Materials > Manufacturing to open the Edit Bill of Materials -
2. Select the name of manufacturing BOM whose data you want to view, or Click View/Edit > Edit Bill of
Materials > Manufacturing BOM to open the Edit Bill of Materials - Manufacturing window to view data for
all manufacturing BOMs, from the BOM Name drop-down menu.
3. Click REFRESH. The window is updated and contains manufacturing BOMs for the BOM Name you selected.
Sorting Manufacturing BOMs

In addition to limiting the manufacturing BOMs displayed, you can choose the order in which they are listed. By default,
the manufacturing BOM list is displayed in ascending alphabetical order, according to BOM Name, then Material, and
then Component. In addition, you can view the manufacturing BOM list alphabetically in ascending or descending order
according to:
• Material, then BOM Name, and then Component
• Component, then Material, and then BOM Name
Perform the following steps to sort manufacturing BOMs:
60
MIPO
1. Filter the manufacturing BOMs by using the instructions above.
2. Choose one of the following sort options:
• To sort the list alphabetically by BOM Name, Material, and Component in descending order, click the
BOM Name column heading. The arrow next to the column header points downward and the
manufacturing BOMs are displayed in descending order. To view the list in ascending order, click the BOM
Name column heading so that the arrow is pointing upward.
• To sort the list alphabetically by Material, BOM Name, and Component in descending order, click the
Material column heading. The arrow next to the column header points downward and the manufacturing
BOMs are displayed in descending order. To view the list in ascending order, click the Material column
heading so that the arrow is pointing upward.
• To sort the list alphabetically by Component, Material, and BOM Name in descending order, click the
Component column heading. The arrow next to the column header points downward and the
manufacturing BOMs are displayed in descending order. To view the list in ascending order, click the
Component column heading so that the arrow is pointing upward.
Related Topics:
Editing Manufacturing BOMs
Creating a Manufacturing BOM
Deleting Components and Manufacturing BOMs
The bill of materials is a description of the component items, including individual quantities, that go into the assembly of
a single finished good at the factory or stocking location. The bill of materials may also include the formula, recipe, or
instructions for creating the product.
Manufacturing BOM is a many-to-one relationship between multiple incoming items and a single outgoing item at a
process or manufacturing node in a supply chain. It determines the quantity of each incoming item required to produce
one unit of each outgoing item, when each is represented in their base unit of measure.
Note: Unit of Measure (UOM) is specified when an item is created. It cannot be edited in
the Edit Bill of Materials - Manufacturing window.
Editing a Manufacturing BOM

Perform the following steps to edit an existing manufacturing BOM:
2. Click Edit > Input Data > Bill of Materials > Manufacturing BOM to open the Edit Bill of Materials -
3. Filter and sort the manufacturing BOM list.
4. Click the radio button next to the BOM Name you want to edit.
5. Click EDIT BOM. The BOM Name, Master BOM, Material, Component, and Quantity columns become
editable all for rows that possess the selected BOM Name.
6. Edit the BOM Name, Master BOM, Material, Component, and Quantity information for the selected
manufacturing BOM, as desired.
7. Click OK to save your changes. The window is updated and displays a status message indicating that the
manufacturing BOM was updated.
61
Adding a Component Item

Perform the following steps to add a component item to an existing manufacturing BOM:
4. Click the radio button next to the BOM Name you want to edit.
5. Click ADD COMPONENT. A new row is created. It contains the selected BOM Name and Master BOM status,
but only the Material, Component, and Quantity columns are editable.
6. Edit the Material, Component, and Quantity information for the selected manufacturing BOM, as desired.
7. Click OK to save your changes. The window is updated and displays a status message indicating that the
manufacturing BOM was updated.
Related Topics:
Perform the following steps to create a manufacturing BOM:
3. Click ADD BOM to create an empty row into which you can enter information about the BOM you are creating.
4. Enter the name of the manufacturing BOM you are creating in the BOM Name field.
5. If this manufacturing BOM is the Master BOM for the selected scenario, check the Master BOM check box.
6. Under the Material heading, enter an item code or click Browse (...) to open the Item Selector. Use the Item
Selector to choose an outgoing item for the process node.
Note: If you want to create a manufacturing BOM for an item that does not yet exist in the
system, you must first create the item.
8. Under the Component heading, enter an item code or click Browse (...) to open the Item Selector. Use the
Item Selector to choose an incoming item that is required to produce the material item at the process node.
10. Under the Quantity heading, enter the number of Components required to produce the Material.
11. Click OK to add the manufacturing BOM. The window is updated and displays a status message indicating that
the manufacturing BOM was added.
62
MIPO
Related Topics:
Creating Items
Editing Packaging BOMs
A bill of materials is a description of the component items, including individual quantities, that go into the assembly of a
single finished good at the factory or stocking location. A bill of materials may also include the formula, recipe, or
instructions for creating the product.
A Packaging BOM is a one-to-one relationship between upstream and downstream items in the distribution portion of a
supply chain. It determines the quantity of the upstream item in each package of the downstream item, when each is
expressed in their respective units of measure.
Perform the following steps to edit a packaging BOM:
1. Ensure that you have selected the correct supply chain and scenario.
2. Click Edit > Input Data > Bill of Materials > Packaging to open the Edit Bill of Materials - Packaging
window.
3. Enter an Item or click the Browse (...) button next to the Source Item field to open the Item Selector. Use the
Item Selector to choose an item whose BOM data is the downstream component of the BOM you want to view.
Click OK to close the Item Selector.
4. Enter an Item or click the Browse (...) button next to the Destination Item field to open the Item Selector. Use
the Item Selector to choose an item whose BOM data is the upstream component of the BOM you want to
view. Click OK to close the Item Selector.
5. For the BOM Quantity field, enter a number indicating the ratio of destination items required to package each
source item.
Note: The ratio of source items (4 Wheels) to each destination item (1 Lawn Mower) can
also be viewed inversely (1 Wheel is .25 to each Lawn Mower).
6. Click OK. You will see a message stating "Packaging BOM updated."
Related Topics:
Creating Paths
Deleting a component
Perform the following steps to delete a component item from an existing manufacturing BOM:
2. Click Edit > Bill of Materials > Manufacturing to open the Edit Bill of Materials - Manufacturing window.
63
4. Click the radio button next to the BOM Name for which you want to delete a component item.
5. Click DELETE COMPONENT. The row you selected is no longer displayed.
6. Click OK. A dialog opens, prompting you to confirm your action.
7. Click OK to close the dialog and delete the component. The window is updated and displays a status message
indicating that the manufacturing BOM was updated.
Deleting a manufacturing BOM

Perform the following steps to delete a manufacturing BOM:
2. Click Edit > Bill of Materials > Manufacturing to open the Edit Bill of Materials - Manufacturing window.
4. Click the radio button next to the BOM Name for which you want to delete all entries.
5. Click DELETE BOM. All rows for the BOM Name you selected are no longer displayed.
6. Click OK. A dialog opens, prompting you to confirm the deletion.
7. Click OK to close the dialog and delete the manufacturing BOM. The window is updated and displays a status
message indicating that the manufacturing BOM was deleted.
Related Topics:
Output Data
In the MIPO application, a supply chain is modeled as a network of nodes where each node represents an item-location
pair. Each node may have upstream nodes, downstream nodes, or both. Each node is connected to its upstream and
Data that does not vary with time is considered to be static data in MIPO. Examples of static node data include target
service level, holding cost percent, and inventory unit cost. You can edit static outputs for one or multiple stocking points
in MIPO.
2. Click Edit > Output Data > Stocking Point Data > Static to open the Edit Stocking Point Data - Static
window.

64
MIPO
radio button.
one (1).
information, the Unit Cost property is not displayed. As a result, you cannot edit this
property.
10. Click OK to save your changes. The Edit Stocking Point Output Data - Static window is reloaded and
Related Topics:
Outputs for Nodes
Editing Stocking Point Time Varying Output Data (Single Node)
Editing Stocking Point Time Varying Output Data (Single Property)
65
pair. Each node can have upstream nodes, downstream nodes, or both. Each node is connected to its upstream and
downstream nodes by paths. Data that varies with time is considered to be time varying data in MIPO. Examples of time
varying node data include forecast demand mean, forecast demand standard deviation, and minimum required stock.
3. Click Edit > Output Data > Stocking Point Data > Time Varying to open the Edit Stocking Point Output
Data - Time Varying (Single Period) window.
6. The Edit Stocking Point Output Data - Time Varying (Single Period) window is reloaded and contains the
radio button.
11. Click OK to save your changes. The Edit Stocking Point Output Data - Static (Single Period) window is
Related Topics:
Outputs for Nodes

66
MIPO
6. The Edit Stocking Point OutData - Time Varying (Single Period) window is reloaded. It contains the stocking
9. The Edit Stocking Point Output Data - Time Varying (Single Node) window opens. It contains the time-
varying properties on the left and each of the periods in the display horizon on the right. Note that the name of
the node you are editing is listed in the Choose Nodes to Edit field near the top of the window.
radio button.
13. Click OK to save your changes. The Edit Stocking Point Output Data - Time Varying (Single Node) window
is reloaded and displays a status message indicating that the data was updated successfully. The window
reflects the change you made for the nodes and all properties and periods you specified.
67
Related Topics:
Outputs for Nodes
6. The Edit Stocking Point Output Data - Time Varying (Single Period) window is reloaded. It contains the
8. The Edit Stocking Point Output Data - Time Varying (Single Property) window opens. It contains the nodes
radio button.
68
MIPO
12. Click OK to save your changes. The Edit Stocking Point Output Data - Time Varying (Single Property)
Related Topics:
Outputs for Nodes
Auditing Data Changes

The Audit Data Changes feature lets you see what changes were made to specific scenario data, who made specific
changes, and when these changes were made. The Audit Data Changes window can display all changes to Input and
Output data for specific scenarios. You can also filter the display to narrow the list of audit information.
To view the Audit history, click Edit > Audit Data Changes. You will see the Audit Data Changes window, which defaults
to the last audit transaction, if any exists.
From the Audit Data Changes window, you can do the following:
1. Set filters
2. Select a specific audit transaction, including associated component if necessary
3. Compare original data record to modified data record
Filtering Audit records

When setting filters to display Audit data, You can use the following categories:
• Data Type: Defaults to All data. You can select Input data or Output data.
• Audit Date: The default value is Today. You can select Last Five Days, Last Ten Days, Last Thirty Days.
You can also use the Calendar button to select a Date Range.
• Screen: Use dropdown list to view data changes associated with a specific MIPO screen.
• User: Use dropdown list to view data changes associated with a specific MIPO account.
69
Click any dropdown list to change the filter, and then click Refresh.
Selecting a specific Audit transaction

The Audit Data Changes window lists transaction information, including:
• Date and time when the change was made
• Account name of user who made the change
• Type of change that was made
• Specific MIPO screen used to make the change
To select a specific audit transaction, click its associated radio button.
Note: Certain audit transaction may involve multiple components. This is indicated by an
activated Component dropdown list. Click the Component dropdown list to select
specific component.
The associated records involved with the change appear at the bottom of the screen. You will see two sets of records, the
original and the modified record (yellow background). You can identify the change by comparing the data in the original
record to the modified record.
Adjusting Date periods for specific Audit transaction

You can further filter out unnecessary information by adjusting the Start and End periods.
1. Click the [...] button. The Period -- Web Page dialog box appears.
2. Scroll through the list of periods and click which one you wish to view.
3. Click OK.
Deleting Nodes and Paths

Deleting Nodes
Note: When you delete a node, all paths connected to it are also deleted. When you
delete a customer facing stocking node that is the only node connected to a customer
node, the customer facing stocking node, path, and customer node are all deleted.
Perform the following steps to delete a node:
3. Click the Browse (...) button to open the Node Selector. Use the Node Selector to choose the node that you
want to delete. Click OK to close the Node Selector.
4. Click DELETE.
5. You are prompted to confirm the deletion. Note that all paths connected to the node are also deleted. Click OK
to continue.
6. The Network Structure - Node window opens, containing a text message indicating that the node was deleted.
70
MIPO
Related Topics:
Deleting Paths
Deleting Paths
Perform the following steps to delete a path:
3. Click the Browse (...) button to open the Path Selector. Use the Path Selector to choose the path that you
want to delete. Click OK to close the Path Selector.
4. Click DELETE. A dialog box opens and prompts you to confirm the actions. Click OK.
Note: You cannot delete a path whose destination node is a customer node.
5. The Network Structure - Path window opens, containing a text message indicating that the path was deleted.
Related Topics:
Creating Paths
Deleting Nodes

The data management preference that you can modify is the length of the display horizon. The display horizon is the
number of periods in history for which time-varying properties (such as TIP, demand, forecast, and capacity) are displayed
in the MIPO user interface.
Perform the following steps to change your data management preferences:
1. Ensure that you are editing data in one of the windows listed above.
2. Click PREFERENCES to open the Preferences window.
3. Enter a new value in the Before Selected Period field, if desired. The selected period is the period that you
have selected using the Period Selector.
4. Enter a new value in the After Selected Period field, if desired.
5. Click OK. The number of periods displayed for editing is updated to reflect your changes.
Related Topics:
71

You can print reports that contain information about stocking point and supply path data. Printed reports include the name
of the report, the name of the supply chain and scenario you selected, and information about when the scenario was last
modified and by whom.
Note: If the report you want to print contains multiple pages, they are all exported for
printing.
Perform the following steps to print a report about stocking point and supply path data:
1. Ensure that you are viewing the window whose contents you want to print.
2. Click PRINT. The contents of the window you are viewing is opened in a new window.
3. Click Print. The Print dialog opens.
4. Adjust your printer settings if desired, and click Print.
Related Topics:
Analyzing Scenarios
Analyzing and Managing Scenarios (MIPO)
There are two types of scenarios: base scenarios and user scenarios. Each supply chain is associated with a base
scenario. The base scenario is a protected (read-only) scenario that contains real-world supply chain data. In contrast, a
user scenario can be edited to reflect the changes you want to apply to a supply chain then validated and optimized. You
can then view the results of your changes in the Network window and create reports by using the Reports menu and
compare them to the base scenario.
When you apply changes to a user scenario, validate, optimize it, and view the new results (or outputs), you are
analyzing a scenario. You manage scenarios by duplicating, upgrading, and deleting them.
Note: The ability to analyze and manage scenarios is a user privilege. If you are not
authorized to analyze or manage scenarios, the Analyze > Manage Scenarios menu
item is disabled. In addition, you cannot view any scenario-related alerts.
Note: Scenario Access Control privileges are dynamically generated when a scenario is
created. If a you create a scenario and want other users to be able to access it, use the
Manage Scenario Access feature to add users..
Editing information about the base scenario

If you select a supply chain and its associated base scenario, you can edit a limited amount of related information, such
as Supply Chain Name, Description, and Owner in the Manage Scenarios window. When you select the base
scenario, you can view, but not edit information in the following fields:
• Scenario Name - the name of the scenario
• Period Length - the length of time for which time varying data is provided. For example, if a forecast is given in
weekly time buckets, the period length is one week.
72
MIPO
• Start Period - the period from which calculation must begin for the selected scenario. All horizons are
measured relative to this period, which must be equal to Base Period for base scenarios and greater than or
equal to the value specified for user scenarios.
• Analysis Horizon - the number of periods beyond the start period (in other words, in the future) for which
accurate results are desired
• Data Horizon - the number of periods of data available for computation (optimization).
• Historical Data Horizon - the amount of historical data available for creating a timeline.
• Service Level - is a metric that refers to the probability that demand is met from stock.
• Distribution Type - Identifies the algorithm used during optimization calculations, either normal or gamma.
• Initialization - this setting determines if the user specifies values for On Hand or if the value is inferred by the
application
• Lost Sales Model - model for computing lost sales; can either be Proportional or Constant.
• Storage Capacity Constraints - determines whether to consider storage capacity constraints during
optimization calculations
• Storage Penalty Option - which storage penalty option to use during optimization, minimize impact or minimize
cost
• Storage Penalty Cost - the cost of adding new storage capacity
• Adjust for Bias - determines whether to adjust forecast or safety stock for bias (or not adjust at all).
• Demand Timing Uncertainty - determines whether DIM module outputs are used during optimization
calculations.
• Business Alerts On Inputs Stop Severity - signals the application to halt the validation process whenever an
Input business alert of the selected severity is generated.
• Business Alerts On Outputs Stop Severity - signals the application to halt the validation process whenever
an Output business alert of the selected severity is generated.
• Order Delivery with Lead Time Uncertainty – Indicates whether the application should consider order
crossover when calculating safety stock, ignore order crossover, or use a less comprehensive method of order
crossover when calculating safety stock.
• Scenario Status - indicates the status of the scenario
• Base scenario modified?- indicates whether or not changes have been made to the base scenario
• Last Modified - the date and time that the supply chain was last changed
• Modified By - the user name of the person who last modified the supply chain
• Base Period - the latest recognized date in the database when historical data transitions to forecast data
• Calculation Horizon - represents the number of periods forward that the application provides calculations. If
the start period is the same as the base period, this number will be equal to the data horizon. If the start period
is after the base period (e.g., 3 periods), then the calculation horizon will be less than the data horizon (e.g.,
data horizon - 3).
• End Horizon - the last period deemed as having reliable output data throughout the supply chain.
73
• Audit History Exists? - identifies if input or output data had been updated in the scenario via a check box
indicator.
Perform the following steps to edit information about the base scenario:
1. Use the Supply Chain Selector to select a supply chain. The base scenario is automatically selected in the
Scenario Selector.
2. Click Analyze > Analyze/Manage Scenarios to open the Manage Scenarios window.
3. Change the name of the supply chain by entering a new name in the Supply Chain Name field, if desired.
Note: The following special characters are not supported for use in supply chain names:
single quote ('), double quote (”), backslash (\), angle brackets (>,<), ampersand (&), and
pipe (|).
4. Add or edit the description in the Description field.
5. To choose a different Owner for the scenario, click the Browse (...) button to open the User Selector:
a. Select All or User Name from the Search by: drop-down menu.
b. If you select All, a list of all users is displayed; click the desired user name and click OK to close the User
Selector.
c. if you select User Name, the User Name field is displayed.
d. Enter the first few letters of the name and click Show. The Users list is populated with user names that start
with the text you entered. If there are many users, you can page through the list.
e. Click the desired user name and click OK to close the User Selector.
6. Click OK to save your changes.
7. You can now perform the following tasks:
• Upgrade the scenario
• Create a user scenario edit its data by using the Edit menu, then validate and optimize it
• Create and compare reports based on the scenario by using the Reports menu
• View the network diagram in the Network window
Editing information about a user scenario
If you select a supply chain and a user scenario, you can edit the Scenario Name, Description, Owner, Start Period,
Analysis Horizon, Data Horizon, and Initialization, in addition to viewing all of the fields listed for the base scenario in
the Scenario Management window. Also, the TASKS menu is displayed when you select a user scenario.
Perform the following steps to edit information about a user scenario:
1. Use the Supply Chain Selector to select a supply chain.
2. Use the Scenario Selector to select the user scenario that you want to edit.
3. Click Analyze > Manage Scenarios to open the Scenario Management window.
74
MIPO
4. Change the name of the scenario by entering a new name in the Scenario Name field, if desired.
Note: The following special characters are not supported for use in entity names: single
quote ('), double quote ("), and the backslash (\).
Selector.
c. If you select User Name, the User Name field is displayed.
with the text you entered. If there are many users, you can page through the list.
7. Click the Browse (...) button to open the Period Selector. Use the Period Selector to specify a different Start
Period for the scenario, if desired.
Note: For user scenarios, the value you enter for the Start Period must be greater than or
equal to the value entered for the Base Period.
8. Edit the value in the Analysis Horizon field, if desired. The analysis horizon is the number of periods beyond
the start period (in other words, in the future) for which accurate results are desired.
9. Edit the value in the Data Horizon field, if desired. The data horizon is the number of periods of data available
for computation (optimization). The value entered for data horizon must be greater than or equal to the value
entered for the analysis horizon.
10. If desired, select a different Initialization option from the drop-down menu:
• If you select User-specified, you must enter a value for On Hand when creating or editing a stocking point.
Failing to enter a value for On Hand causes a Missing On Hand alert to be generated during validation. In
addition, entering a value for Planned Receipts for each supply path is optional.
• If you select Automatic, the system calculates a value for On Hand for each stocking point and Planned
Receipts for each supply path. You cannot enter or edit these values for On Hand or Planned Receipts
when creating or editing stocking points or supply paths.
Note: If you change the Initialization option of a supply chain (Base scenario, not
upgraded) or user scenario, it must be re-validated and re-optimized. In addition, if you
change the Initialization option from Automatic to User-specified, you must enter On
Hand values for stocking points to avoid a validation alert.
12. You can now perform the following tasks:
• Validate the scenario
• Optimize the scenario
• Upgrade the scenario
• Analyze the scenario by using the Edit menu to edit its data, then validate and optimize it
• Create and compare reports based on the scenario by using the Reports menu
• View the network diagram in the Network window
75
Related Topics:
Creating a Supply Chain
Creating a User Scenario
Duplicating Scenarios
Validating Scenarios
Optimizing Scenarios
Upgrading Scenarios
Deleting Supply Chains and Scenarios
Reviewing Inventory Targets
Quick Links

You can create a supply chain in the application in multiple ways, depending on the supply chain's size and complexity.
For example, you could use the Gateway Loading Tool (SGLT) to create a supply chain and then import it, or you could
create a smaller supply chain, adding its locations, items, nodes, and paths manually. The instructions below outline how
to manually create a supply chain using the MIPO interface.
Note: The ability to create a supply chain is a user privilege. If you are not authorized to
create a supply chain, the Analyze > Create Supply Chain menu item is disabled.
Perform the following steps to create a supply chain using the application:
1. Click Analyze > Create Supply Chain to open the Scenario Management window.
2. Enter the name of the supply chain you are creating in the Supply Chain Name field. Note that the name of the
base scenario associated with the new supply chain is "Base Scenario not upgraded."
pipe (|).
3. Enter a brief description of the supply chain in the Description field, if desired.
4. Select an Owner of the supply chain. If it is a different user, click the Browse (...) button to open the User
Selector:
Selector.
with the text you entered. If there are many users, you can page through the list
76
MIPO
5. Select Days, Weeks, Months, or Quarters from the Period Length drop-down menu to specify the Period
Length of the supply chain.
Note: Ensure that the period length you select is correct. You cannot modify the period
length for the supply chain after you click OK to save the values you entered.
6. Click the Browse (...) button to open the Period Selector. Use the Period Selector to specify a Start Period for
the supply chain.
Note: When creating a supply chain, the value entered for the Start Period is equal to the
value entered for the Base Period.
7. Enter a value in the Analysis Horizon field. The analysis horizon is the number of periods beyond the start
period (in other words, in the future) for which accurate results are desired.
8. Enter a value in the Data Horizon field. The data horizon is the number of periods of data available for
computation (optimization). The value entered for data horizon must be greater than or equal to the value
9. Enter a value in the Historical Data Horizon field.
10. Select the desired Service Level option from the drop-down menu:
• If you select Fill Rate, your service level will be calculated as a ratio of the total number of units to be
delivered divided by units ordered over a given period.
• If you select Non-stockout Probability, your service level will be calculated as the number of
customer orders you plan to service in full as a proportion of the total number of orders received.
Note: If you change the Service Level option of a supply chain (Base
scenario, not upgraded) or user scenario, it must be re-validated and re-
optimized.
11. Select the desired Distribution Type option from the drop-down menu:
• If you select Normal, the application will use its normal distribution algorithms for its inventory target
calculations.
• If you select Gamma, the application will use its Gamma distribution algorithms for its inventory target
calculations.
12. Select the desired Initialization option from the drop-down menu:
• If you select User-specified, you must enter a value for On Hand when creating or editing a stocking
point. Failing to enter a value for On Hand causes a Missing On Hand alert to be generated during
validation. In addition, entering a value for Planned Receipts for each supply path is optional. If no
value is entered, the Planned Receipts will be set to zero by default.
• If you select Automatic, the system calculates a value for On Hand for each stocking point and
Planned Receipts for each supply path. You cannot enter or edit these values for On Hand or
Planned Receipts when creating or editing stocking points or supply paths.
13. Select the desired Lost Sales Model option from the drop-down menu:
• If you select Constant (default), you must enter a value for On Hand Inventory when creating or
editing a stocking point. Failing to enter a value for On Hand Inventory causes a "Missing On Hand"
alert to be generated during validation. In addition, entering a value for Planned Receipts for each
supply path is optional.
77
14. Select the desired Storage Capacity Constraints from the drop-down menu:
• The default is Ignore, meaning that any storage capacity limitations are determined post-optimization
and used to calculate additional storage capacity.
• If you set the Storage Capacity Constraints field to Consider, storage capacity limitations are
considered during optimization, using the Storage Penalty Option and the Storage Penalty Cost
values.
15. If storage capacity constraints are considered, select the desired Storage Penalty Option from the drop-down
menu:
• Minimize Impact – recommends inventory allocations based on the storage penalty cost for adding a
new fixed-cost storage location (such as a storage tank).
• Minimize Cost – recommends inventory allocations based on the storage cost for adding new
variable-cost storage (such as additional space in a warehouse).
16. If storage capacity constraints are considered, enter the storage penalty cost into the Storage Penalty Cost
field:
• If Minimize Impact has been selected as the Storage Penalty Option, then the Storage Penalty Cost is
the cost of adding a new fixed-cost storage location (such as a storage tank).
• If Minimize Cost has been selected as the Storage Penalty Option, then the Storage Penalty Cost is
the cost of adding a new variable-cost storage location (such as additional space in a warehouse).
• If the field is left blank, the optimization assumes that the cost is very expensive.
17. Choose the appropriate Adjust for Bias option from the drop-down menu:
• Defaults to None; that is no bias adjustment.
• When Safety Stock is selected, enables the application to apply DIM-calculated bias adjustment to
safety stock.
• When Forecast is selected, enables the application to apply DIM-calculated bias adjustment to
forecast.
18. Choose the appropriate Demand Timing Uncertainty option from the drop-down menu:
• Defaults to Ignore.
• When Consider is selected, the application will adjust safety stock requirements by the positive
forecast bias determined by DIM.
19. Select the Business Alerts Stop Severity for both Inputs and Outputs by clicking the corresponding dropdown
list. This signals the application to halt the validation process whenever a business alert of the selected severity
is generated.
20. Choose the appropriate Order Delivery with Lead Time Uncertainty option from the drop-down menu:
• Sequential – Ignores the impact of order crossover in the calculation of safety stock.
• Crossover – Dynamically determines and considers the impact of order crossover when calculating
safety stock. (Default)
• Simplistic Crossover – Uses an earlier, less comprehensive calculation of the impact of order
crossover.
Note: Processes invoked when you create a supply chain can take some time to execute.
During this time, you can continue using the application. To determine the status of a
scenario-related process, click Analyze > Analyze/Manage Scenarios to open the
Scenario Management window. Then click REFRESH to view the Scenario Status.
22. The Scenario Management window is refreshed, and contains a status message indicating whether the supply
chain was saved successfully. If the supply chain was saved successfully, and you are the owner, the Supply
Chain Selector displays the name of the supply chain you created and the Scenario Selector contains a
scenario named "Base Scenario not upgraded." In addition, the following fields contain updated information:
78
MIPO
• Base scenario modified? - indicates whether or not changes have been made to the base
scenario
• Base Period - the latest recognized date in the database when historical data transitions to
forecast data
• Calculation Horizon - represents the number of periods for which calculations must be performed
to ensure valid results throughout the Analysis Horizon. The value of calculation horizon
determines how far into the future the effect of capacity constraints are considered.
• End Horizon - the last period deemed as having reliable output data throughout the supply chain.
23. Create locations, nodes, paths, items, and attributes, if desired, for the supply chain. To do so, use the
instructions outlined in the following topics:
• Creating Locations
• Creating a Supplier Node
• Creating an Internal Stocking Node
• Creating a Process Node
• Creating a Customer Facing Stocking Node
• Creating Paths
• Creating Items
• Creating Attributes
24. In the Scenario Management window, click TASKS > Validate to ensure that the structure of the scenario and
its data are correct.
25. Click TASKS > Optimize to compute the data you input for the entities associated with the scenario.
26. Upgrade the base scenario. After you upgrade the base scenario, you can create user scenarios based on this
supply chain.
Note: The privileges to view or edit the supply chain you created, although they exist, are
not displayed in the Settings > User Settings > User Privileges tab, until you log out
and sign in again.
Related Topics:
Analyzing and Managing Scenarios
Upgrading Scenarios
79

There are two types of scenarios: base scenarios and user scenarios. Each supply chain is associated with a base
scenario that is a protected (read-only) scenario that contains real-world supply chain data.
Note: The ability to create a user scenario is a user privilege. If you are not authorized to
create a scenario, the Analyze > Create User Scenario menu item is disabled.
created. If a you create a scenario and want other users to be able to access it, a user
with administrative privileges must grant them access privileges for the scenario.
In contrast, a user scenario can be edited and optimized to reflect the changes you want to apply to a supply chain. You
can then view the results of your changes in the Network window and Reports menu and compare them to the base
scenario.
Note: You cannot create a user scenario for a supply chain if the base scenario
associated with it has not yet been upgraded. You must first upgrade the base scenario.
Perform the following steps to create a user scenario:
1. Use the Supply Chain Selector to select the supply chain for which you want to create a user scenario.
2. Click Analyze > Create User Scenario to open the Scenario Management window. Note that the Supply
Chain Name field contains the name of the supply chain you selected.
3. Enter the name of the user scenario you are creating in the Scenario Name field.
Note: The following special characters are not supported for use in scenario names:
pipe (|).
4. Enter a brief description of the scenario in the Description field, if desired.
5. Select an Owner of the scenario. If it is a different user, click the Browse (...) button to open the User Selector:
Selector.
6. Note that the Period Length of the scenario cannot be edited; it specified when the supply chain is created.
the scenario.
Note: For user scenarios, the value you enter for the Start Period must be greater than or
equal to the value entered for the Base Period.

80
MIPO
Note: If you change the Service Level option of a supply chain (Base
scenario, not upgraded) or user scenario, it must be re-validated and re-
optimized.
calculations.
calculations.
validation. In addition, entering a value for Planned Receipts for each supply path is optional. By
default, Planned Receipts will be zero unless you specify a greater value (either via data loading or
by editing within the application).
values.
menu:
field:
safety stock.
81
forecast.
is generated.
21. If you want to create a new scenario for a select number of items in this supply chain, click the Item Filter
browse (...) button. The Item Selector displays. Use the Item Selector to choose the item you want to filter,
then click OK.
Note: This action creates a new base scenario for a new supply chain with the name you
entered in the scenario field. Limiting the items in a supply chain changes the topology of
that supply chain. Creating a new supply chain eliminates the chance of a user scenario
with a changed topology might be upgraded to a base scenario.
crossover.
Note: Processes invoked when you create a scenario can take some time to execute.
During this time, you can continue using the MIPO application. To determine the status of
a scenario-related process, click Analyze > Analyze/Manage Scenarios to open the
24. The Scenario Management window is refreshed, and contains a status message indicating whether the user
scenario was saved successfully. If the scenario was saved successfully, and you are the owner, the Scenario
Selector displays the name of the user scenario you created.
Note: If you used the Item Filter to limit the number of items in the supply chain, a new
supply chain with the scenario name you entered and base scenario are created. To use
the new scenario, you must upgrade the new base scenario.
In addition, the following fields contain updated information:
• Scenario Status - indicates the status of the scenario; if the user scenario was created
successfully, this field reads "Created, not validated."
• Base scenario modified? - indicates whether or not changes have been made to the base
scenario
• Base Period - the latest recognized date in the database when historical data transitions to
forecast data
82
MIPO
• Calculation Horizon - represents the number of periods for which calculations must be performed
to ensure valid results throughout the Analysis Horizon. The value of calculation horizon
determines how far into the future the effect of capacity constraints are considered.
• End Horizon - the last period deemed as having reliable output data throughout the supply chain
25. The Scenario Audit Information panel is displayed in the Scenario Management window. It displays
information about tasks performed on the selected scenario, including when the scenario was created, the
Scenario Status of validation and optimization, and the Date & Time (GMT) that the tasks occurred.
26. Click TASKS > Validate in the Scenario Management window to verify that the structure of the scenario and
its data are correct, if desired.
27. Click TASKS > Optimize to compute the data you input for the entities associated with the scenario, if desired.
28. You can view the supply chain in the Network window, generate reports by using the Reports menu, or edit the
data associated with the user scenario by using the View/Edit menu.
Related Topics:
Upgrading Scenarios
Using the Item Filter

The item filter on the Manage Scenario screen allows you to select a set of items and create a new supply chain with just
those items, using the same scenario settings as you’ve selected in the current scenario. The new supply chain has the
same name as entered into the scenario name field.
Limiting the items in a supply chain changes the topology of that supply chain. Creating a new supply chain eliminates the
chance of a user scenario with a changed topology might be upgraded to a base scenario.
To use the item filter:
1. Click the Item Filter browse (...) button to open the Item Selector.
2. Use the selector to choose the item you want to filter.
4. On the Manage Scenario screen, click OK.
The Manage Scenarios window is refreshed, and contains a status message indicating whether the new supply chain was
saved successfully. If the supply chain was saved successfully, and you are the owner, the Supply Chain Selector
displays the name of the supply chain you created. In addition, several fields at the bottom of the screen display
information.
83
If there is an existing user scenario to which you want to make small changes, duplicating it and making changes to the
copy can save time and decrease the likelihood that you will introduce errors.
Note: To create a duplicate of the base scenario, select the base scenario name in the
Scenario Selector, and click Analyze > Create User Scenario.
Perform the following steps to duplicate a user scenario:

1. Use the Supply Chain Selector to select the supply chain containing the user scenario you want to duplicate.
2. Use the Scenario Selector to select the user scenario that you want to duplicate.
Note: You can duplicate a scenario that has not been validated or optimized. However, if
the scenario you are duplicating contains validation errors, they will also be present in the
copied version.
3. Click Analyze > Manage Scenarios to open the Manage Scenarios window.
4. Click TASKS > Duplicate Scenario. A dialog opens and prompts you to enter a name for the copy of the
scenario.
5. Enter a name in the Enter the new scenario name field and click OK.
Note: The following special characters are not supported for use in scenario names:
pipe (|).
Note: Processes invoked when you duplicate a scenario can take some time to execute.
a scenario-related process, click Analyze > Analyze/Manage Scenarios to open the
7. The Scenario Management window is reloaded and displays a status message indicating that scenario copy
was created successfully. The name you entered for the copy of the scenario is displayed in the Scenario
Selector.
8. Enter a brief description of the scenario in the Description field, if desired.
9. Select an Owner of the scenario. If it is a different user, click the Browse (...) button to open the User Selector:
b. If you select All, a list of all users is displayed; click the desired user name and click OK to close the
User Selector.
d. Enter the first few letters of the name and click Show. The Users list is populated with user names
that start with the text you entered. If there are many users, you can page through the list
10. Note that the Period Length of the scenario cannot be edited; it is the same as for the selected supply chain.
the scenario.
84
MIPO
Note: If you change the Service Level option of a supply chain (Base scenario, not
upgraded) or user scenario, it must be re-validated and re-optimized.
calculations.
calculations.
validation. In addition, entering a value for Planned Receipts for each supply path is optional.
values.
menu:
field:
85
safety stock.
forecast.
is generated.
24. If you want to create a new scenario for a select number of items in this supply chain, click the Item Filter
browse (...) button. The Item Selector displays. Use the Item Selector to choose the item you want to filter,
then click OK.
Note: This action creates a new base scenario for a new supply chain with the name you
entered in the scenario field. Limiting the items in a supply chain changes the topology of
that supply chain. Creating a new supply chain eliminates the chance of a user scenario
with a changed topology might be upgraded to a base scenario.
crossover.
27. The Scenario Management window is refreshed, and contains a status message indicating whether the user
scenario was saved successfully. If the scenario was saved successfully, and you are the owner, the Scenario
Selector displays the name of the user scenario you created.
Note: If you used the Item Filter to limit the number of items in the supply chain, a new
supply chain with the scenario name you entered and base scenario are created. To use
the new scenario, you must upgrade the new base scenario.
In addition, the following fields contain updated information:

• Scenario Status - indicates the status of the scenario; if the user scenario was created successfully,
this field reads "Created, not validated."
• Base scenario modified - indicates whether or not changes have been made to the base scenario
• Last Modified (GMT) - the date and time (in Greenwich Mean Time) that the supply chain was last
changed
• Base Period - the latest recognized date in the database when historical data transitions to forecast
data
• Calculation Horizon - field contains a hyphen (-) until the scenario is optimized; represents the
number of periods for which calculations must be performed to ensure valid results throughout the
Analysis Horizon. The value of calculation horizon determines how far into the future the effect of
capacity constraints are considered.
• End Horizon - field contains a hyphen (-) until the scenario is optimized; the last period deemed as
having reliable output data throughout the supply chain
86
MIPO
28. In the Scenario Management window, click TASKS > Validate to ensure that the structure of the scenario and
its data are correct.
29. Click TASKS > Optimize to compute the data you input for the entities associated with the scenario.
30. You can view the supply chain in the Network window, generate reports by using the Reports menu, or edit the
data associated with the user scenario as desired by using the View/Edit menu.
Related Topics:
Upgrading Scenarios
Data that is imported or manually input into the application is validated at several different levels. For example, before
importing a data set, the .zip file that you import contains data that was validated by the SGLT. When you create a node in
the within the application, the values you enter for static and time varying properties are verified as you enter them into the
fields of the user interface. Validation ensures that data added to the system is compatible with the algorithms used to
calculate (or optimize) outputs.
When you validate a scenario, a set of predetermined criteria is the basis for verifying its structural and logical
consistency. If a scenario contains validation errors, it cannot be optimized until they are corrected.
Note: The ability to validate a user scenario is a user privilege. If you are not authorized to
validate a scenario, the TASKS > Validate Scenario menu item is disabled in the
Manage Scenarios window.
Perform the following steps to validate a scenario:

1. Use the Supply Chain Selector to select the supply chain containing the scenario you want to validate.
2. Use the Scenario Selector to select the scenario that you want to validate.
4. Click TASKS > Validate Scenario. The Scenario Management window is refreshed and displays a status
message indicating that the scenario is being validated. In addition, the Scenario Audit Information is updated
to reflect the status of the validation process.
Note: Processes invoked when you validate a scenario can take some time to execute.
a scenario-related process, click Analyze > Manage Scenarios to open the Manage
Scenarios window. Then click REFRESH to view the Scenario Status.
Note: The amount of time it takes to validate a scenario depends on the quantity of data it
contains. While a scenario is being validated, the Manage Scenarios window is
periodically reloaded. To manually reload the Manage Scenarios window during
validation, click REFRESH. To cancel validation, click TASKS > Cancel Validation.
6. When validation of the scenario is complete, the Manage Scenarios window displays a status message
indicating that validation is complete. In addition, the Scenario Audit Information indicates that validation is
complete, and whether or not the scenario was validated successfully:
• If the scenario was validated successfully, you can now optimize it.
87
• If the scenario contains validation errors, you must correct them before continuing. To determine the
origin of errors, click Alerts > View Alerts to view the alerts associated with the scenario. For specific
information about the incorrect data, identify the specific alert and view the alert details.
Related Topics:
Upgrading Scenarios
Viewing Alert Short Entries
Viewing Alert Details
Before you can view the results (or outputs) of the changes you make to a user scenario, it must be validated and
optimized. Validation ensures that the scenario is structurally and logically consistent with the algorithms used to calculate
outputs. When you optimize a scenario, the data it contains is used by algorithms to calculate new results based on the
changes you made.
Note: The ability to optimize a user scenario is a user privilege. If you are not authorized
to optimize a scenario, the TASKS > Optimize Scenario menu item is disabled in the
Perform the following steps to optimize a scenario:

1. Use the Supply Chain Selector to select the supply chain containing the scenario you want to optimize.
2. Use the Scenario Selector to select the scenario that you want to optimize.
3. Click Analyze >Manage Scenarios to open the Manage Scenarios window.
Note: If you select a scenario for optimization that has not yet been validated, it will be
validated automatically before the optimization process begins.
4. Click TASKS > Optimize Scenario. The Manage Scenarios window is refreshed and displays a status
message indicating that the scenario is being optimized. In addition, the Scenario Audit Information is
updated to reflect the status of the optimization process.
Note: The amount of time it takes to optimize a scenario depends on the quantity of data
it contains. While a scenario is being optimized, the Manage Scenarios window is
optimization, click REFRESH. To cancel optimization, click TASKS > Cancel
Optimization.
5. When optimization of the scenario is complete, the Manage Scenarios window displays a status message
indicating that optimization is complete. In addition, the Scenario Audit Information indicates that optimization
is complete, and whether or not the scenario was optimized successfully:
• If the scenario was optimized successfully, you can now upgrade it.
• If the scenario contains validation errors that prevent it from being optimized successfully, you must
correct them before continuing. To determine the origin of errors, click Alerts > View Alerts to view
the alerts associated with the scenario. For specific information about the incorrect data, identify the
specific alert and view the alert details.
Related Topics:
88
MIPO
Upgrading Scenarios
Upgrading Scenarios
After you've created a scenario and it has been validated and optimized, you can upgrade the changes that it contains to
the parent supply chain or to a new supply chain:
• If you upgrade a scenario to the parent supply chain, the parent supply chain is overwritten.
• If you upgrade a scenario to a new supply chain, you create a new supply chain that contains your changes and
has no associated user scenarios.
You can also optimize and upgrade a scenario at the same time, as well as optimize, upgrade and generate reports on
data inputs and outputs.
Note: The ability to create, edit, validate, optimize, upgrade and delete scenarios is a user
privilege. If you are not authorized to analyze or manage scenarios, the Analyze >
Analyze/Manage Scenarios menu item is disabled. In addition, you cannot view any
scenario-related alerts.
Upgrading a Scenario to the Parent Supply Chain

Perform the following steps to upgrade a scenario to the parent supply chain:
1. Use the Supply Chain Selector to select the supply chain containing the scenario you want to upgrade.
2. Use the Scenario Selector to select the scenario that you want to upgrade.
4. Verify that the scenario you selected has been optimized by ensuring that the Scenario Status field contains
the text "Optimized."
5. Click TASKS > Upgrade to Parent Supply Chain. A confirmation dialog opens, prompting you to confirm the
action.
Note: Upgrading a scenario to a parent supply chain overwrites the parent supply chain.
This action is irreversible.
Note: Processes invoked when you upgrade a scenario can take some time to execute.
scenario-related process, click Analyze > Manage Scenarios to open the Manage
7. Click OK to upgrade the scenario. The Manage Scenarios window is reloaded and contains a status message
indicating that the scenario was upgraded successfully. Also, the Scenario Audit Information panel contains a
message "Upgraded to Parent Supply Chain" and the name of the scenario you upgraded is no longer
displayed in the Scenario Selector.
Upgrading a Scenario to a New Supply Chain

Perform the following steps to upgrade a scenario to a new supply chain:
89
5. Click TASKS > Upgrade to New Supply Chain. A confirmation dialog opens, prompting you to confirm the
action.
Note: Upgrading a scenario to a new supply chain is irreversible.
indicating that the scenario was upgraded successfully. In addition, the following fields and selectors are
updated:
• the Scenario Audit Information panel contains a message "Upgraded to New Supply Chain"
• the name of the scenario you upgraded is no longer displayed in the Scenario Selector
• the name of the scenario you upgraded is displayed in the Supply Chain Selector and the base
scenario is automatically selected in the Scenario Selector
• no user scenarios are listed for the new supply chain in the Scenario Selector
Optimizing and upgrading a scenario

You can optimize and upgrade a scenario at the same time after you have validated changes made to the scenario inputs
and/or outputs. The changes made will be upgraded to the parent supply chain, overwriting the previous data.
To optimize and upgrade a scenario to the parent supply chain:
4. Click TASKS > Optimize and Upgrade. A confirmation dialog opens, prompting you to confirm the action.
Scenarios window. Then check Scenario Audit Information for the latest status.
6. Click OK to optimize and upgrade the scenario. The Manage Scenarios window is reloaded and contains a
status message indicating that the scenario was optimized and upgraded successfully. Also, the Scenario
Audit Information panel contains a message "Upgraded to Parent Supply Chain" and the name of the scenario
you upgraded is no longer displayed in the Scenario Selector.
Optimizing, upgrading, and generating reports

You can optimize and upgrade a scenario at the same time, as well as generate input and output reports, after you have
validated changes made to the scenario inputs and/or outputs. The changes made will be upgraded to the parent supply
chain, overwriting the previous data.
To optimize and upgrade a scenario to the parent supply chain, and generate reports:
90
MIPO
4. Click TASKS > Optimize, Upgrade and Generate Reports. A confirmation dialog opens, prompting you to
confirm the action.
6. Click OK to optimize and upgrade the scenario, and generate reports. The Manage Scenarios window is
reloaded and contains a status message indicating that the scenario was optimized and upgraded successfully.
Also, the Scenario Audit Information panel contains a message "Upgraded to Parent Supply Chain" and the
name of the scenario you upgraded is no longer displayed in the Scenario Selector.
Note: You can view the input and output reports generated by the application under the
Reports menu.
Related Topics:
Postprocessing SLO Scenarios

After a scenario has been optimized, you can run processors designed to perform specific postprocessing tasks on the
data. See the Installation and Upgrade Guide for information on the specific processors. To postprocess a scenario:
Note: If you select a scenario for postprocessing that has not yet been optimized, it will be
optimized automatically before the optimization process begins.
4. Click TASKS > Postprocess Scenario. A message appears at the top of the window informing you that the
postprocess procedure has been started. The application also posts the status in the Scenario Audit
Information panel. At the successful conclusion of postprocessing, you’ll see a message stating
“Postprocessing completed.”
Validating Business Alerts (Inputs and Outputs)

You can validate a selected scenario using business rules configured with the Manage Business Alerts feature.
After a scenario has been optimized or computed (DIM), you can run processors designed to perform specific
postprocessing tasks on the data. See the Installation and Upgrade Guide for information on configuring Business Alerts.
Validate scenario inputs on Business Alerts rules

To validate scenario inputs:
91
2. Use the Scenario Selector to select the scenario that you want to optimize or compute (DIM).
4. Click TASKS > Validate Rules on Input. A message appears at the top of the window informing you that the
scenario inputs are being verified against the business rules. The application also posts the status in the
Scenario Audit Information panel. At the successful conclusion of verification, you’ll see a message stating
“Business Rules on Inputs Validation Completed.”
Validate scenario outputs on Business Alerts rules

To validate scenario outputs:
1. Use the Supply Chain Selector to select the supply chain containing the scenario you want to optimize or
compute (DIM).
4. Click TASKS > Validate Rules on Output. A message appears at the top of the window informing you that the
scenario outputs are being verified against the business rules. The application also posts the status in the
“Business Rules on Outputs Validation Completed.”
Reviewing Inventory Targets

Reviewing Inventory Targets Overview
Note: The ability to review and compare inventory targets is a user privilege. If you are not
authorized to review and compare inventory targets, the Analyze > Review Inventory
Targets menu item is disabled.
The Review Inventory Targets feature is a planning tool designed to support the Exception Management work flow. It
allows the planner to review and compare key output values from a selected scenario side-by-side with the same values
previously generated in another scenario from the same supply chain. Key outputs available for comparison include:
1. Safety Stock
2. Safety Stock (Periods)
3. Reorder Point
4. Target Inventory Position
5. Unshifted Safety Stock
6. Expected On Hand Stock
7. On Hand Stock (Periods)
The Review Inventory Targets window is used to perform the key output comparisons. Follow the steps below to review
inventory targets:
Step 1: Generate output report
Step 2: Review key output target comparison data
92
MIPO
Step 3: Review key output target details
Step 4: Update necessary output targets
Step 5: Approve output targets
Note: The application tracks the editing changes to key outputs in the Key Output Audit Report.
Related Topics:
Quick Links
Step 1: Generate key output comparison data

In order to generate key output comparison data, the Review Inventory Target window provides a set of configuration
parameters at the top of the screen:
1. Use the Supply Chain Selector to select the supply chain for which you want to compare key output data.
2. Use the Scenario Selector to select the user scenario for which you want to compare key output data.
Note: The scenario you select must be optimized before you can view key output
comparison data.
3. Click Analyze > Review Inventory Targets to open the Review Inventory Targets window.
4. If necessary, click the dropdown list to select the Comparison Scenario (base scenario selected by default).
5. Click the associated [...] buttons to select the Start and End period dates.
6. If necessary, define the Percent Change Minimum (%) value to be used to limit the data results.
7. Click Generate.
The MIPO application generates the comparison data for the selected key output, which is displayed in the
Review Inventory Targets window.
Back to Overview Go to Step 2
Step 2: Review key output comparison data

The Review Inventory Targets window displays a list of key output values in a side-by-side format for all comparable
stocking points, as indicated by item-location. Also displayed are the value differences between current and comparison
scenarios for each stocking point, represented in either units or cost (based on the preference setting), along with the
percentage of change between the two scenarios.
Note: Viewing report contents that are expressed as a monetary amount (cost) is a user
privilege. If you are not authorized to view monetary amounts, you can only view this
report in units.
93
Along with the key output data, the screen also shows the percentage change, by comparison of each stocking point, for
the following key inputs:
• Demand Mean
• Demand Standard Deviation
• Total Lead Time Mean
• Total Lead Time Standard Deviation
• Minimum Batch Size
• Incremental Batch Size
If the Key Outputs list includes a large number of stocking point records, you can page through the list by clicking PREV
and NEXT. To go directly to a specific page in a multi-page list, type a page number in the Page field and press ENTER.
To increase the viewing area, hide the Filters section of the screen by clicking the Hide Filters link located in the top right
corner of the window. To view the Filters section of the screen, click the Show Filters link.
Filtering the Key Outputs list

You can filter the key output results to view specific subsets of data. The following filters can be used:
• Key Output
• Item
• Location
• Status
• Percent change threshold
• Include increased from zero
• Include new stocking points
• Sort by absolute percentage change
An Item is a uniquely identified, single product in inventory. By default, the Review Inventory Targets window displays
results for all items. Use the Item Selector to select single or multiple items.
A Location is any physical point in the supply chain at which inventory is stored. By default, the Review Inventory
Targets window displays results for all locations. Use the Location Selector to select single or multiple locations.
94
MIPO
The Status filter lets you display records assigned with a specific planner work flow status. By default, the Review
Inventory Targets window displays results for all status assignments. Selecting <blank> will display all optimized
stocking points that have not yet been approved or modified. Selecting Accepted or Modified will display only records
with the associated status.
The Percent Change Threshold filter lets you display only records whose percentage change is greater than the
threshold value. By default, this filter is blank.
By default, a check box associated with Include Increased from Zero filter displays all stocking points whose key output
value changed from zero (0) in the comparison scenario to a different value in the current scenario. Turn this filter off by
clicking the check box to deactivate it.
The Include New filter also is activated by default to display stocking points in the current scenario that were not part of
the comparison scenario. Turn this filter off by clicking the check box to deactivate it.
The Sort By Absolute Percentage Change filter provides the ability to sort records by absolute values. This allows key
outputs with high change percentages to be grouped together, regardless of whether the change is positive or negative.
Back to Step 1 Go to Step 3
Step 3: Review details for selected key output data

The Review Inventory Targets window also includes a dedicated area to display various input data comparisons
associated with any selected stocking point. The following input categories are available:
• Demand
• Supply
• Cost
• Inventory Components
• Time Varying inputs
Select any stocking point record by clicking on its associated radio button. You can then click one of the Input category
tabs in the Details section to review input data related to the selected stocking point.
To increase the Input Data Details viewing area, first hide the Filters section of the screen by clicking the Hide Filters link
located in the top right corner of the window, then click the Show More link. Click Show Less to return to the previous
view.
The Demand tab displays the following scenario comparison data:
95
• Demand Mean
• Calculated Service Level
• Risk Pooling Factor
• Minimum Required Stock
• Service Time
The Supply tab displays the following scenario comparison data:
• Periods Between Reviews
• Periods Since Last Review
• Schedule Attainment
• Schedule Attainment CV
• Storage Capacity
• Physical Lead Time
• Order Processing Lead Time
• Other Lead Time
• Total Lead Time Mean
• Total Lead Time Standard Deviation
• Periods Between Shipments
• Minimum Batch Size
• Batch Size
• Supply Ratio
• Reliability
• Frozen Window
• Service Time
• Yield
Note: All Supply data values that include Supplier in the Source column are displayed for
each upstream supply path.
96
MIPO
The Cost tab displays the following scenario comparison data:
• Unit Cost
• Holding Cost Percentage (0-1)
• Unit Purchase Cost
The Inventory Components tab displays the following scenario comparison data:
• Safety Stock
• Cycle Stock
• Prebuild Stock
• Merchandise Stock
• Expected On Hand Stock
• Physical Pipeline Stock
• Total Pipeline Stock
• Target Inventory Position
• On Hand Stock (Periods)
• Planned Receipts
• Safety Stock (Periods)
• Unshifted Safety Stock
• Unshifted Merchandising Stock
• Backlog Safety Stock
• Additional Supply Capacity (units)
• Additional Storage Capacity (units)
• Production Quantity
• Reorder Point
• Demand over Lead Time
The Time Varying tab displays the following scenario comparison data:
• Demand Mean
97
• Safety Stock
• Backlog Safety Stock
• Reorder Point
Step 4: Accept key output targets

The Review Inventory Targets window includes a planner work flow status feature that indicates stocking point records
have been reviewed and accepted. You can accept all output targets by clicking ACCEPT ALL. The Status field for each
stocking point is updated to Accepted.
Note: You can accept a subset of output targets by filtering the list to display the subset, then clicking ACCEPT ALL. The
Status field for each filtered stocking point is updated to Accepted.
You can accept a specific output target by selecting the radio button for the stocking point, then clicking ACCEPT. The
Status field for the selected stocking point is updated to Accepted.
Step 5: Update selected key output targets

The Review Inventory Targets window allows you to edit the key output value for any selected stocking point record.
1. Select the stocking point you wish to edit by clicking its associated radio button.
2. If necessary, click the Edit tab.
3. Either use the All Periods field to update the key output for every displayed time period, or scroll through the
time periods to find the specific period whose key output you wish to change and type the new value in the field
at the bottom of the appropriate time period column.
4. Choose the method you want to use to specify your changes by clicking the one of the following radio buttons:
• Click =x to assign a new value.
• Click +x or -x to increase or decrease by a specific value.
• Click +x% or -x% to increase or decrease a value by percentage.

98
MIPO
Note: When editing values that have a predefined valid range (such as, .50 to 1.0 for Calculated Service Level,
and you attempt to enter an absolute value (=x) outside of that range, a status message indicates that the value
you entered is invalid and you are prompted to enter a different value. However, if you specify a relative change
(+x or -x) or a percentage change (+x% or -x%) that results in a value outside the valid range, the value is
automatically rounded up or down to the closest valid value.
For example, if the valid range is 0-1, the current value is .75, and you increase it by 200%, the resultant value
exceeds the valid range. In this case, the new value that is saved for this property and displayed in the user
interface is one (1).
A status message indicates that the data was updated successfully. The updated value is displayed in the corresponding
time period. The Status field for the selected stocking point is updated to Modified. The status message “Data used to
create this UI page has changed” is displayed.
Back to Step 4 Return to Overview
Managing Scenario Access

This feature lets the owners of specific user scenarios to provide access privileges to other user accounts. Perform the
following steps to provide scenario access to another user account:
1. Use the Supply Chain Selector to select the supply chain containing the base, historical, or user scenario for
which you want to provide access.
2. If you want to provide access to a user scenario, use the Scenario Selector to select it.
3. Click Analyze > Manage Scenario Access to open the Manage Scenario Access screen.
4. If the user account hasn't been assigned access privileges, click the account name listed under the
Unassigned Users window. To assign Read-Only privileges, click the [>] arrow next to the Read-Only Users
window. The account name will move from the Unassigned Users window to the Read-Only window. Similarly,
you can assign Full-Access privileges the same way.
Note: You must be have read-only or full access to at least one scenario in order to
view the Manage Scenario Access screen. You must have full access for the selected
supply chain or user scenario to use this feature. The blue user account indicates the
scenario owner.
5. If you want to change access privileges for a user account, click the user account and use the arrow keys to
change access to either Read-Only, Unassigned or Full-Access.
6. Click OK. You will see a message indicating that the scenario access privileges have been saved.
Deleting a Supply Chain or a Scenario

Note: The ability to delete supply chains (base scenarios), historical scenarios, and user
scenarios are user privileges. If you are not authorized to delete supply chains and
scenarios, the TASKS > Delete menu items are disabled.
Perform the following steps to delete a scenario:

1. Use the Supply Chain Selector to select the supply chain containing the base, historical, or user scenario you
want to delete.
99
2. If you want to delete a user scenario, use the Scenario Selector to select it.
4. Choose one of the following deletion options:

• If you have selected a base scenario, click TASKS > Delete Supply Chain or TASKS > Delete
Historical Scenario.
Note: By default, the application will create a historical scenario whenever a base
scenario is updated. This feature can be turned off clicking Settings > Manage
Module to open the Manage Module Settings window. Then select Analyze
Scenario from the Module dropdown list.
Refer to the “Manage module settings” section in the Installation Guide.
• If you have selected a user scenario, click TASKS > Delete Scenario.
Note: This feature also removes scenario data from the optional Data Store module
based on the Data Store configuration settings. Refer to the "Data Store Properties
file settings" section in the Installation and User’s Guide.
5. A confirmation dialog opens and prompts you confirm the deletion.
Note: Processes invoked when you delete a supply chain or scenario can take some time
to execute. During this time, you can continue using the application. To determine the
status of a scenario-related process, click Analyze > Analyze/Manage Scenarios to
open the Scenario Management window. Then click REFRESH to view the Scenario
Status.
6. Click OK to delete the supply chain or scenario. The Scenario Management window is reloaded and it displays
a status message indicating that the supply chain or scenario has been deleted.
Note: All published reports associated with the deleted supply chain or scenario will also
be deleted by default. You can change the default through the Published Reports
module configuration settings, found under Settings > Manage Module Settings.
Related Topics:
Deleting Multiple Scenarios
Deleting Multiple Scenarios

scenarios are user privileges. If you are not authorized to delete supply chains/models
and scenarios, the Analyze > Delete Scenarios menu item is disabled.
To delete multiple scenarios at the same time:
1. Click Analyze > Delete Scenarios to open the Delete Scenarios window.
2. If necessary, select the scenario type from the Type dropdown list to list only scenarios from a specific module.
3. Click the checkbox associated with each scenario you wish to delete. Click Select All to delete all data from the
application.
100
MIPO
based on the Data Store configuration settings. Refer to the "Data Store Properties file
settings" section in the Installation and Upgrade Guide.
4. Click Delete.
A confirmation dialog opens and prompts you confirm the deletion.
status of a scenario-related process, click Analyze > Manage Scenarios to open the
Manage Scenarios window. Then click REFRESH to view the Scenario Status.
5. Click OK to delete the selected scenarios. The Delete Scenarios window is reloaded and it displays a status
message indicating that the selected scenarios have been successfully deleted.
be deleted by default. You can change the default through the
PublisherModule.properties file.
Related Topics:
Exception Management Workflow

What is Exception Management?
Exception Management identifies specific instances where a data set containing the latest updates from your supply chain
set deviates from the previous data set loaded and optimized. Using business alerts, the application identifies exceptions
in both Input and Output data.
You can edit both Input and Output data associated with the data set in order to resolve these exceptions.
The application tracks the data editing changes in the Audit Data Changes window.
The Manage Scenarios window is used to perform the Exceptions Management workflow. Follow the steps below to
perform exception management:
Step 1: Set up business alerts
Step 2: Prepare data set for loading
Step 3: Import data set
Step 4: Validate data set
Step 5: Run Input Rules Validations
101
Step 6: Manage Input Business Alerts
Step 7: Optimize Scenario
Step 8: Postprocess Scenario (optional)
Step 9a: Validate Rules on Outputs (skip Postprocess)
Step 9b: Validate Rules on Outputs
Step 10: Manage Output Business Alerts
Step 11: Export optimized data set with latest updates
Step 1: Set up Business Alerts

Use the Manage Business Alerts screen to activate the Business Alerts or make any configuration setting changes
associated with the Business Alerts.
You can also define Business Alert settings for a specific data set with the Gateway Loading Tool (SGLT). See the
Installation Guide for more information on configuring Business Alerts.
Click here for more information about Business Alerts.
Next step
Step 2: Prepare data set for loading

See the Installation Guide for more information on preparing a data set to be loaded into the application.
Note: For SAP enterprise solutions, the Data Gateway can be used to extract SAP data through the SAP Standard
Interface (SSI) and import it directly into the application.
Previous step Next step
Step 3: Import data set

See Importing a Data Set for more information on loading a data set into the application.
Note: You can also perform the Exception Management process on a duplicated scenario. See Duplicating Scenarios for
more information on this feature.
102
MIPO
Step 4: Validate data set

Open the Manage Scenarios window by clicking Analyze > Manage Scenarios. Use the Scenario Selector to choose
the scenario you wish to validate. You will see the information associated with the selected scenario in the Manage
Scenarios window.
Click Tasks > Validate Scenario.
You will see a message stating that the scenario is being validated. You can check Scenario Audit Information at the
bottom of the window to see the current status. When you see Validation Completed, you can check your scenario Input
data for exceptions based on your Business Alert configurations.
Step 5: Run Input Rules Validations

The Manage Scenarios window lets you set the severity level that would shut down the Validation process. Click the
dropdown list labeled Business Alerts Inputs Stop Severity to select one of six choices:
• Disabled
• None
• Fatal Error
• Error
• Warning
• Informational
When you are ready to validate the scenario, click Tasks > Run Input Rules Validations.
You will see a message stating that business rules are being verified on the scenario's Input data. You can check
Scenario Audit Information at the bottom of the window to see the current status. When you see Business Rules on
Inputs Validation Completed you can determine if the application detected any exceptions on Input data by reviewing
the business alerts.
Step 6: Manage Input Business Alerts

You can view alerts to see if there were any exceptions identified. You can use the View Alerts window to review, sort,
acknowledge and dismiss relevant alerts.
If any alerts indicate the need to change scenario Input data, you can use the application to update stocking points and
supply paths, as well as network nodes and paths.
If you make any changes to your scenario, repeat Step 4.
103
Any changes you make to the scenario's Input data will be tracked by the application, as shown by a checkmark in the
Audit history exists? Input indicator on the Manage Scenarios window. You can review Input changes to the scenario
in the Audit Data Changes window.
If necessary, you may also edit data in the source system and start back at Step 2.
Once you are satisfied with your scenario's Input data, you can optimize the scenario.
Step 7: Optimize Scenario

Click Tasks > Optimize Scenario.
You will see a message stating that the scenario is being optimized. You can check Scenario Audit Information at the
bottom of the window to see the current status. When you see Optimization Completed, you can either run any optional
post-processing calculations on your scenario data, or else check your scenario Output data for exceptions based on your
Business Alert configurations.
If the optimization fails, you can view Alerts to see the specific reason for the failure. You will need to correct any errors
associated with the optimization failure, then repeat Step 4.
Step 8: Postprocess Scenario (optional)

If your system includes optional processors that perform TIP calculations and generate reports, you can perform this task
to launch the processors. Otherwise, go to Step 9a.
Click Tasks > Postprocess Scenario (optional).
You will see a message stating that the scenario is being postprocessed. You can check Scenario Audit Information at
the bottom of the window to see the current status. When you see Postprocessing Completed, you can check your
scenario Output data for exceptions based on your Business Alert configurations by performing Step 9b.
Step 9a: Validate Rules on Outputs (skip Postprocess)

Click Tasks > Validate Rules on Outputs (skip Postprocess).
You will see a message stating that business rules are being verified on the scenario's Output data. You can check
Outputs Validation Completed, you can view alerts to see if there were any exceptions identified.
104
MIPO
If any alerts indicate the need to change scenario Output data, you can use the application to update stocking points.
Once you are satisfied with your scenario's Output data, you can use the application tools to export the optimized scenario
data.
Step 9b: Validate Rules on Outputs

The Manage Scenarios window lets you set the severity level that would shut down the Validation process. Click the
dropdown list labeled Business Alerts Outputs Stop Severity to select one of six choices:
• Disabled
• None
• Fatal Error
• Error
• Warning
• Informational
When you are ready to validate the scenario, click Tasks > Validate Rules on Outputs.
You will see a message stating that business rules are being verified on the scenario's Output data. You can check
Outputs Validation Completed, you can determine if the application detected any exceptions on Output data by
reviewing the business alerts.
Step 10: Manage Output Business Alerts

You can view alerts to see if there were any exceptions identified. You can use the View Alerts window to review, sort,
acknowledge and dismiss relevant alerts.
If any alerts indicate the need to change scenario Output data, you can use the application to update stocking points.
105
Any changes you make to the scenario's Output data will be tracked by the application, as shown by a checkmark in the
Audit history exists? Output indicator on the Manage Scenarios window. You can review Output changes to the
scenario in the Audit Data Changes window.
Once you are satisfied with your scenario’s Output data, you can use the application tools to export the optimized
scenario data.
Step 11: Review Inventory Targets

The Key Output Comparison feature allows the planner to review and compare key output values from a selected
scenario side-by-side with the same values previously generated in another scenario from the same supply chain. Key
outputs available for comparison include:
• Safety Stock
• Reorder Point
The Review Inventory Targets window is used to perform the key output comparisons.
Step 12: Export optimized data set with latest updates

After you are satisfied with all changes regarding scenario updates, you can export the optimized data set using the
Export feature.
If your system includes the optional Data Store, you can transfer the optimized data set to the Data Store.
Note: For SAP enterprise solutions, the optional Data Gateway can be used to export the optimized data back into SAP.
Business Alerts supplied by MIPO
Alert Name Description Default Severity Default

Active Trigger
Setting Value
106
MIPO
DEMAND_CV Generated on Input validation between No Error 1.0%

scenarios when the demand CV
between scenarios has exceeded the
specified criteria, as defined by a
percentage.
DEMAND_CV_COMPARISON Generated on Input validation between No Error 1.0%

scenarios when the forecast demand
CV between scenarios has changed
more than the specified criteria, as
defined by a percentage.
DEMAND_MEAN_COMPARISON Generated on Input validation between No Error 1.0%

mean has changed more than the
specified criteria.
DEMAND_STD_COMPARISON Generated on Input validation between No Error 1.0%

standard deviation has changed more
than the specified criteria.
ISL_SPT_COMPARISON Generated on Output validation between No Error 1.0%

scenarios when the implied service level
from the Stocking Point TIP table has
changed more than the specified
criteria.
LT_CV_PRF Generated on Input validation between No Error 1.0%

scenarios when the Lead time CV of the
Process Resource Forecast table has
exceeded the specified criteria.
LT_CV_SPF Generated on Input validation between No Error 1.0%

Supply Path Forecast table has
LT_MEAN_PRF_COMPARISON Generated on Input validation between No Error 1.0%

scenarios when the Lead time mean of
the Process Resource Forecast table
has changed more than the specified
criteria.
LT_MEAN_SPF_COMPARISON Generated on Input validation between No Error 1.0%

the Supply Path Forecast table has
criteria.
LT_STD_PRF_COMPARISON Generated on Input validation between No Error 1.0%

scenarios when the Lead time standard
deviation of the Process Resource
Forecast table has changed more than
the specified criteria.
LT_STD_SPF_COMPARISON Generated on Input validation between No Error 1.0%

deviation of the Supply Path Forecast
table has changed more than the
107
specified criteria.
OHSP_SPT_COMPARISON Generated on Output validation between No Error 1.0%

scenarios when the On hand stock in
periods from the Stocking Point TIP
specified criteria.
OHS_SPT_COMPARISON Generated on Output validation between No Error 1.0%

scenarios when the On hand stock from
the Stocking Point TIP table has
criteria.
RATIO_SPF_COMPARISON Generated on Input validation between No Error 1.0%

scenarios when the Supply ratio of the
criteria.
SSP_SPT_COMPARISON Generated on Output validation between No Error 1.0%

scenarios when the Safety stock in
specified criteria.
SS_SPT_COMPARISON Generated on Output validation between No Error 1.0%

scenarios when the Safety stock from
criteria.
TIP_SPT_COMPARISON Generated on Output validation between No Error 1.0%

scenarios when the TIP from the
Stocking Point TIP table has changed
more than the specified criteria.
Custom Defined Any number of custom defined business Custom Custom Custom
rules Defined Defined Defined
Related Topics:
Managing Alerts
108
MIPO
Creating Reports
Input Reports
Forecast Demand Report
The Forecast Demand Report is a read-only, non-interactive report that shows forecast demand mean over time for a
customer facing stocking point. Forecast demand mean at a stocking location is an estimate of the mean demand for the
product at a stocking location during a given period. Customer facing stocking points are stocking locations at which end-
customer demand occurs. Only stocking points with no downstream stocking locations can be customer facing stocking
points.
report in units.
Perform the following steps to create a Forecast Demand report:
3. Click Reports > Input Reports > Forecast Demand to open the Forecast Demand Report window. By
default, the window displays results for all customer facing stocking points.
4. Click the blue pushpin button to generate a report based on a previously saved filter selection. If you want to
select a different set of customer facing stocking points, click the Browse (...) button next to the Customer
Facing Stocking Points for Report field to open the Node Selector. Use the Node Selector to select a
different set of customer facing stocking points for which to generate the report. Click OK to close the Node
Selector.
5. To change the period for which you are creating the report, specify different Start and End periods for the
report. If you select starting and ending periods that are the same, the results of the report are based on a
single period.
Notes: The Advanced Report Filtering feature can be used to save the current filter
The default period on which this report is based is determined by the values of the Base
Period and Data Horizon for the scenario.
6. Click Refresh. The Forecast Demand Report window is refreshed containing the report results in a table.
7. Click SHOW CHART to view the results in a chart. The Forecast Demand report opens in a separate window, in
chart format.
Related Topics:
Editing Report Preferences
Exporting Reports to Excel
Printing Reports
Comparing Reports
Stocking Point Static Inputs Report

The Stocking Point Static Inputs Report displays inputs for stocking points. The report results are non-interactive and can
be viewed only in a table.
109
privilege. If you are not authorized to view monetary amounts, you can only view the
sections of this report that are expressed in units.
Perform the following steps to create a Stocking Point Static Inputs Report:
3. Click Reports > Input Reports > Stocking Points > Static Data to open the Stocking Point Static Inputs
Report window. By default, the window displays results for all customer facing stocking points.
the Browse (...) button to open the Node Selector. Use the Node Selector to select a different set of nodes for
which to generate the report, if desired. Click OK to close the Node Selector.
6. Click Refresh. The Stocking Point Static Inputs Report window is reloaded containing the new results in
table format. You cannot view this report in a chart.
Note: You can change the Period for which you are generating this report. To do so, use
the Period Selector to select a different period. You are prompted to refresh the contents
of the report. Click OK. The contents of the report are updated using the new period you
selected.
The following table lists the report columns and their descriptions.
Column Description
Target Service Level The minimum acceptable service level that a company feels they must achieve.
Specifies if the service level on the stocking point was calculated by SLO or is an input.
Input Mechanism
Valid values are either Input or Optimized.
The number of periods between the time an order is placed and the time it must be shipped
Service Time
before a stockout is considered to have occurred.
The cost associated with holding inventory at a stocking location. It is expressed as a

Holding Cost Percentage
percentage of unit cost.
Represents the dollar value of one unit of inventory (expressed in the specified unit of
Unit Cost measure) for a given time at a given stocking location. This cost may include partial
processing (for example, assembly or painting) cost on the raw material or components.
Unit Purchase Cost The inbound acquisition cost or transfer price for each item-location.
The price at which a stocking point sells a unit of a product to its downstream stocking point
Unit Transfer Price
(its customer).
All inventory that is physically available to fill demand, which is all types of stock except
On Hand Inventory pipeline. Specifically, on hand inventory includes cycle, safety, merchandising, and prebuild
(if applicable) stock.
Unusable On Hand Unusable On Hand inventory is the portion of On Hand inventory that should not be
Inventory considered when calculating inventory targets as it cannot be used to satisfy demand.
110
MIPO
The standard unit in which the quantity of an item is managed. Examples of units of
Unit of Measure
measure include inches, pounds, gallons, and pallets.
Periods Between Reviews Defines the frequency at which inventory position is reviewed and replenishment decisions
(PBR) are made for an item at a location. PBR is specified in number of periods.
Periods Since Last Review For a given item at a given location is the number of periods since placing a replenishment
(PSLR) order or determining (based on inventory) to not place an order.
A heuristic adjustment made to the safety stock computation based on the perceived
Pooling Factor
correlation of demand across customer-facing nodes.
The maximum number of periods an item can remain at a given node before it becomes
Maximum Ship Life
unusable.
The number of periods over which Weeks of Stock is averaged to determine the Average
Coverage Duration
Safety Stock Coverage.
Schedule Attainment The ratio of between the expected attained production and the scheduled production.
The coefficient of variation of the schedule attainment. For example, if the schedule
Schedule Attainment CV attainment is 0.9 and the coefficient of variation is 0.5, then actual production can expect to
be 90% +/- 45% of the scheduled production.
Storage Capacity Specifies the maximum storage capacity for each item-location.
An optional field used by the Service Level Optimization (SLO) module to define the lower
limit on the individual target fill rate at the associated customer-facing stocking point.
An optional field used by the Service Level Optimization (SLO) module to define the upper
An optional field used by the Service Level Optimization (SLO) module to define the
Lost Sales Percentage acceptable lost sales percentage to be applied at the minimum service level at the
associated customer-facing stocking point.
Inventory Allocation Policy Policy used for calculating TIP; either Priority or Divide.
Processing Cost The per unit cost of manufacturing and assembly for each item-location.
The cost of moving an item from an upstream node to an immediate downstream node for
Transportation Cost
a given inventory stocking location.
Order Administration Cost The per unit cost of administering an order for each item-location.
The cost of material movements within the warehouse, which may include unloading costs,
Handling Cost
breakdown costs, labor costs, and machinery costs
Other Cost Miscellaneous expenses, including taxes and insurance, related to keeping inventory.
Related Topics:
Stocking Point Time Varying Inputs Report
111
Printing Reports
Comparing Reports

The Stocking Point Time Varying Inputs report displays time varying inputs for stocking points. The report results are
interactive, but can be viewed only in table format.
sections of this report that are expressed in unit amounts.
Perform the following steps to create a Stocking Point Time Varying Inputs Report:
3. Click Reports > Input Reports > Stocking Points > Time Varying Data to open the Stocking Points Time
Varying Inputs Report (Single Period) window. By default, the window displays results for all customer facing
stocking points.
4. To select a different set of nodes for which to generate the report, click the Browse (...) button to open the
Node Selector. Select the nodes and click OK to close the Node Selector.
5. Click Refresh. The Stocking Point Time Varying Inputs Report (Single Period) window is reloaded
containing the new results in table format. Note that the node names and time-varying properties are hypertext
links.
6. The Stocking Point Time Varying Inputs report is an interactive report. You can view different facets of the
results in different formats by clicking hypertext in the first row and column of the results table. You can
customize the contents and organization of the Stocking Point Time Varying Inputs report, as follows:
• To view an individual property for all nodes for all periods, click the name of the desired property in the top
row of the report table. The results are displayed in the Stocking Point Time Varying Inputs Report
(Single Property) window for all periods. The property you selected is displayed in the Time Varying
Properties field. You can change the Stocking Points for Report, the Start and End period for the report,
and the Time Varying Properties for the report by clicking the Browse (...) button next to each field,
respectively.
• To view all properties for an individual node for all periods, click the name of the desired node in the first
column of the report table. The results are displayed in the Stocking Point Time Varying Inputs Report
(Single Node) window for all periods. The name of the node you selected is displayed in the Stocking
Points for Report field. You can change the Stocking Points for Report and Start and End period for the
report, by clicking the Browse (...) button next to each field, respectively.
Note: The default period on which this report is based is determined by the values of the
Base Period and Data Horizon for the scenario.
Column Description
Input Forecast
An estimate of the mean demand for the product at that stocking location during a given period.
Demand Mean
112
MIPO
Characterizes the difference between forecasted and actual demand. It is a statistical measure of
forecast accuracy and can be used to estimate the variability of the underlying demand.
Input Forecast
Demand Standard
Deviation
Note: This column does not appear for scenarios using DIM outputs as the data associated with
this field will not be used for optimization.
Minimum inventory kept in a retail or customer-facing location. It may be used for showroom or
Minimum Required demonstration purposes, but is typically included in inventory available to meet demand. In
Stock addition, this report displays information about any custom properties created for your supply
chain.
Related Topics:
Printing Reports
Comparing Reports
Supply Path Static Inputs Report

The Supply Path Static Inputs Report displays inputs for supply paths. The report results are non-interactive and can be
viewed only in a table.
Perform the following steps to create a Supply Path Static Inputs Report:
3. Click Reports > Input Reports > Supply Paths > Static Data to open the Supply Path Static Inputs Report
window. By default, the window displays results for all restricted paths.
4. Click the Browse (...) button next to the Supply Paths for Report field to open the Path Selector. Use the
Path Selector to select a different set of paths for which to generate the report, if desired.
6. Click Refresh. The Supply Path Static Inputs Report window is reloaded containing the new results in table
format. You cannot view this report in a chart.
selected.
113
Column Description
The time that it takes from when the upstream (supplier) location begins to fill that order until it is
received in the downstream location. Physical lead time may also be defined as the time during
Physical Lead Time which physical goods are being modified (assembled, transported) and actual material costs are
being incurred. This may include manufacturing time, transportation time and material handling
/warehousing) time.
Order Processing Lead The elapsed time from when the order is placed on an upstream location until that location
Time begins to fill that order. This can include order receipt time, processing time, and queuing time.
Other Lead Time The amount of time an order physically exists.
Total Lead Time Mean The mathematical average of lead time in a given period.
Total Lead Time Standard deviation of lead time is a statistical measure of uncertainty regarding the magnitude of
Standard Deviation expected lead time in a given period.
Periods Between PBS defines the frequency at which shipments are made for a path, independent of PBR. PBS is
Shipments specified in number of periods.
Lets you define the number of periods for which variability in incoming demand to a stocking
Frozen Window
point or process point should not be considered.
Service Time
The one-to-one relationship between upstream and downstream items in the distribution portion
Packaging BOM of a supply chain. It determines the quantity of the upstream item in each package of the
downstream item.
Yield The remaining proportion of a process’ output after yield loss.
Minimum Batch Size

The minimum amount needed, measured by quantity, before an initial order can be produced.
(Units)
Minimum Batch Size The minimum amount needed, measured by periods of coverage, before an initial order can be
(Periods) produced.
The order quantity that is agreed-upon between the upstream and downstream nodes. The
Batch Size
downstream node’s order quantities must be an integer multiple of the batch size.
The probability that an order delivery will be completed within the total lead time (cycle time). If
Reliability delivery cannot be completed within the lead time, then it is assumed to be completed within two
lead times.
Identifies the transportation mode used to convey supply chain items on the associated supply
Mode
path.
Related Topics:
Supply Path Time Varying Inputs Report
114
MIPO
Printing Reports
Comparing Reports

The Supply Path Time Varying Inputs report displays time-varying inputs for supply paths. The report results are
sections of this report that are expressed in unit amounts.
Perform the following steps to create a Supply Path Time Varying Inputs report:
3. Click Reports > Input Reports > Supply Paths > Time Varying Data to open the Supply Path Time Varying
Inputs Report (Single Period) window. By default, the window displays results for all restricted paths.
4. To select a different set of paths for which to generate the report, click the Browse (...) button to open the Path
Selector. Select the paths and click OK to close the Path Selector.
5. Click Refresh. The Supply Path Time Varying Inputs Report (Single Period) window is reloaded containing
the new results in table format. Note that the path names and time-varying properties are hypertext links.
6. The Supply Path Time Varying Inputs report is an interactive report. You can view different facets of the results
in different formats by clicking hypertext in the first row and column of the results table. You can customize the
contents and organization of the Supply Path Time Varying Inputs report, as follows:
• To view an individual property for all paths for all periods, click the name of the desired property in the top
row of the report table. The results are displayed in the Supply Path Time Varying Inputs Report (Single
Property) window for all periods. The property you selected is displayed in the Time Varying Properties
field. You can change the Supply Paths for Report, the Start and End period for the report, and the Time
Varying Properties for the report by clicking the Browse (...) button next to each field, respectively.
• To view all properties for an individual path for all periods, click the name of the desired path in the first
column of the report table. The results are displayed in the Supply Path Time Varying Inputs Report
(Single Path) window for all periods. The name of the path you selected is displayed in the Supply Paths
for Report field. You can change the Supply Paths for Report and the Start and End period for the report
by clicking the Browse (...) button next to each field, respectively.
Column Description
Maximum Process The maximum quantity of each item that can be ordered or produced in each time period for each
Capacity manufacturing/assembly process or supply path.
The minimum quantity of each item that must be produced in each time period (typically due to a
Minimum Process
manufacturer’s desire to avoid labor schedule/shift reductions, cutbacks, layoffs, etc.) for each
Quantity
manufacturing/assembly process.
115
If a stocking point has multiple sources from which it can order, the supply ratio is the proportion
Supply Ratio
of the orders that go to each supplier.
Planned receipts are shipment quantities on a path for a given period, that are expected at the
end stocking point in that period, assuming deterministic lead times and service times in
response to planned orders.
Planned Receipts Planned receipts computed for the first start periods after the first review period are not based
upon orders placed during the data horizon, but are computed based on the assumption of
steady-state initial conditions. In the absence of PBR greater than one or the service time, start
period is equal to lead time on the path. For example, if the lead time is five periods, then any
receipts due before the sixth period had to be ordered before the first period.
Related Topics:
Printing Reports
Comparing Reports
Demand Stream Inputs Report

The Demand Stream Inputs Report displays the inputs on the demand stream portion of the supply path. The report
results are non-interactive and can be viewed only in a table.
3. Click Reports > Input Reports > Supply Paths > Demand Stream Data to open the Demand Stream Inputs
Report window. By default, the window displays results for all restricted paths.
4. Click the Browse (...) button next to the Demand Streams for Report field to open the Demand Stream
Selector. Use the Demand Stream Selector to select a different set of paths for which to generate the report, if
desired.
6. Click Refresh. The Demand Streams Inputs Report window is reloaded containing the new results in table
selected.
Column Description
116
MIPO
The defined number of periods for which variability in incoming demand to a stocking point or
Frozen Window
process point should not be considered.
Service Time
Related Topics:
Printing Reports
Comparing Reports
Output Reports
Master Summary Report (MIPO)
The Master Summary Report is a read-only, non-interactive report that displays the overall revenue, supply chain cost,
and the inventory investment by attribute and by target inventory position (TIP) component. Results are generated for
customer facing stocking points and internal stocking points for the chosen supply chain and scenario for the specified
period.
privilege in the associated module. If you are not authorized to view dollar amounts, you
are not authorized to create a Master Summary Report.
Note: Results for the Master Summary Report can contain an entry called Unassigned.
This entry is displayed when one or more stocking points is not assigned an attribute
value. The sum of relevant data for all such stocking points is displayed under this
heading.
Perform the following steps to generate a Master Summary report:
Note: The scenario you select must be optimized before you can view the Master
Summary Report.
3. Click Reports > Output Reports > Master Summary to open the Master Summary Report window.
4. Select the desired Start and End periods.
5. Click Refresh. The Master Summary Report window opens containing the report results in a table. You
cannot view this report in a chart.
report. If you select starting and ending periods that are the same, the results of the report will be based on a
single period. The contents of the report are updated using the new period you selected.
117
Start Period and End Horizon for the scenario.
Revenue
In the Master Summary Report, the overall revenue results include information about the outputs listed in the following
table:
Column Description
Service level is a metric that refers to the probability that demand is met from stock. Average
Average Customer
customer target service level is determined by calculating the end-customer service level using
Target Service Level
the Forecast Mean weighted average of service levels for all customer-facing stocking points.
Average customer service time is determined by calculating the average (not weighted) service
Average Customer time for all customer-facing stocking points. Service time is the number of periods between the
Service Time time an order is placed and the time it must be shipped before a stockout is considered to have
occurred.
The unit sales per period is determined by calculating the sum of forecast mean for all customer
Unit Sales facing stocking points. The sum of unit sales is obtained and then averaged, resulting in a unit
sales average for all periods.
Average Unit Sales Average unit sales price is the average price at which a unit of inventory is sold at customer
Price facing stocking points. It is determined by dividing the total estimated revenue by unit sales.
Total Forecasted The total forecasted revenue is determined as the sum of revenue for each customer facing
Revenue stocking point by multiplying the forecast mean and the unit transfer price for all periods.
The total lost margin is determined as the sum of lost sales for each customer facing stocking
Total Lost Margin
point over all periods.
Supply Chain Cost
In the Master Summary Report, the supply chain cost results include information about the outputs listed in the following
table:
Column Description
Material cost is determined by multiplying the forecast mean and component cost for all stocking
Material Cost points. The sum of the results is obtained for each period, resulting in an average component
cost for all periods.
Material transportation cost is determined by multiplying the forecast mean and transportation
Transportation Cost cost for all stocking points. The sum of the results is obtained for each period, resulting in an
average component transport cost for all periods.
Processing cost is the per unit cost of manufacturing and assembly for each item-location. For
this report, it is determined by multiplying the forecast mean and processing cost for all stocking
Processing Cost
points. The sum of the results is obtained for each period, resulting in an average processing
Inventory holding cost is the cost associated with holding inventory at a stocking location. For this
report, inventory holding cost is determined by calculating the total chain inventory investment,
Inventory Holding Cost
which is the sum of average pipeline stock, average safety stock, average cycle stock, average
prebuild stock, and average merchandising stock. The total chain inventory investment, holding
cost percentage, and unit cost totals are then multiplied for each period for all stocking points.
118
MIPO
The sum of the results is obtained for each period, resulting in an average inventory holding cost
for all periods.
Order administration cost is the per unit cost of administering an order for each item-location. For
Order Administration this report, it is determined by multiplying the forecast mean and order administration cost for all
Cost stocking points. The sum of the results is obtained for each period, resulting in an average order
administration cost for all periods.
Handling cost is the cost of material movements within the warehouse, which may include
unloading costs, breakdown costs, labor costs, and machinery costs. For this report, handling
Handling Cost cost is determined by multiplying the forecast mean and handling cost for all stocking points. The
sum of the results is obtained for each period, resulting in an average handling cost for all
periods.
Other costs are miscellaneous expenses, including taxes and insurance, related to keeping
inventory. For this report, other costs are determined by multiplying the forecast mean and other
Other Cost
costs for all stocking points. The sum of the results is obtained for each period, resulting in an
other costs average for all periods.
Total Estimated Cost Sum of Supply Chain Costs.
Inventory Investment
In the Master Summary Report, the inventory investment by attribute and by TIP component includes information about
the outputs listed in the following table:
Column Description
Average safety stock is a buffer added to inventory to counteract stockouts when demand and
lead times are uncertain. The amount of safety stock is typically determined based on a specified
service level and the associated variability in demand and lead times. For this report, average
safety stock is determined by multiplying the safety stock and the unit cost for all stocking points.
The sum of the results is obtained for each period, resulting in an average safety stock average
for all periods.
Average cycle stock is a component of the average inventory position at a stocking location for a
specified item and a specified period. It corresponds to the portion of average on hand inventory
that exists to cover demand between shipments (replenishments). For this report, average cycle
Average Cycle Stock
stock is calculated by doubling the cycle stock, subtracting from it the forecast mean, dividing that
number in half, and multiplying it with the unit cost for all stocking points. The sum of the results
is obtained for each period, resulting in an average cycle stock average for all periods.
Prebuild stock is inventory built due to capacity constraints in anticipation of future demand. For
Average Prebuild this report, average prebuild stock is determined by multiplying the prebuild stock and the unit
Stock cost for all stocking points. The sum of the results is obtained for each period, resulting in an
average prebuild stock average for all periods.
Merchandising stock is the minimum inventory kept in a retail or customer-facing location. It may
be used for showroom or demonstration purposes, but is typically included in inventory available
to meet demand. It is also known as minimum stock, showroom inventory, or display stock. Note
Average that merchandising stock is different than safety stock. It is an additional component of inventory
Merchandising Stock over and above the safety stock needed to accommodate supply and demand uncertainties. For
this report, average merchandising stock is determined by multiplying the merchandising stock
and the unit cost for all stocking points. The sum of the results is obtained for each period,
resulting in an average merchandising stock average for all periods.
Average pipeline stock represents all inventory for which a replenishment order has been placed
Average Pipeline but not yet received. For this report, average pipeline stock is determined by multiplying the
Stock average physical pipeline stock and the unit cost for all stocking points. The sum of the results is
obtained for each period, resulting in an average pipeline stock average for all periods.
119
Total Chain Inventory

Sum of Inventory Investments.
Investment
Turns
In the Master Summary Report, the number of turns is determined by dividing the annualized cost of goods sold (COGS)
by the average on hand inventory. An inventory turn is the number of times that a company’s inventory cycles over per
year (or per a specified time period). Lower inventories result in higher inventory turns.
Column Description
Turns Annualized Cost of Goods Sold (COGS) / Average on hand inventory.
Related Topics:
Printing Reports
Comparing Reports
Inventory Summary Report

The Inventory Summary report is an interactive report that summarizes the TIP or average inventory and its components,
as a cost, averaged for the selected periods as totals by attribute. The results of the report can be based on all nodes in a
supply chain, or on a selected group of nodes, and can be viewed as a table or in a chart. For this report, average
inventory is determined by adding the average cycle stock, average prebuild stock, average safety stock, average pipeline
stock, and average merchandising stock. The average inventory position on-hand is determined by subtracting the
average pipeline stock from the average inventory total.
cannot view this report.
Note: Results for the Inventory Summary Report can contain a column named
Unassigned. This entry is displayed when one or more stocking points is not assigned an
attribute value. The sum of relevant data for all such stocking points is displayed under
this heading.
Perform the following steps to create an Inventory Summary Report:
Note: The scenario you select must be optimized before you can view the Inventory
Summary Report.
3. Click Reports > Output Reports > Inventory Summary to open the Inventory Summary Report window. By
default, the window displays results for all stocking points.
select a different set of stocking points, click the Browse (...) button next to the Stocking Points for Report
field to open the Node Selector. Use the Node Selector to select a different set of stocking points for which to
generate the report. Click OK to close the Node Selector.
120
MIPO
single period.
The default period on which this report is based is determined by the values of the Start
Period and End Horizon for the scenario.
6. Click Refresh. The Inventory Summary Report window is refreshed containing the report results in a table.
Note that the text entries displayed in the first row (stages, by default) are hypertext links.
7. The Inventory Summary report is an interactive report. You can view the results for the nodes in each stage by
clicking the hypertext link for the desired stage. For example, if a set of nodes in your supply chain are assigned
the attribute value "Supplier", the Inventory Summary report contains a stage named "Supplier" in the first row.
If you click this link, you see inventory summary results for all supplier nodes only.
8. To return to the Inventory Summary Report main window, click BACK.
9. Click SHOW CHART to view the results in a chart. The Inventory Summary report opens in a separate window,
in chart format.
Related Topics:
Printing Reports
Comparing Reports
Service Level to Cost Report

The Service Level to Cost Report compares how increasing the service level across all demand streams in your supply
chain affects the cost of safety stock.
Note: The data used in this report must be generated by the Service Level to Cost
processor.
privilege in MIPO. If you are not authorized to view monetary amounts, you can only view
the sections of this report that are expressed in unit amounts.
Perform the following steps to create a Service Level to Cost Report:
Note: The scenario you select must be optimized before you can view the Service Level
to Cost Report.
3. Click Reports > Output Reports > Service Level to Cost to open the Service Level to Cost Report window.
121
4. Click GENERATE. The Service Level to Cost Report window displays the results in both table and graph
formats.
Related Topics:
Printing Reports
Comparing Reports
Inventory Detail
Inventory Detail by Item Report
The Inventory Detail by Item Report is an interactive report that displays time-varying outputs aggregated by item. The
results can be viewed in a table or a chart.
Perform the following steps to create a Inventory Detail by Item Report:
Note: The scenario you select must be optimized before you can view the Inventory Detail
by Item Report.
3. Click Reports > Output Reports > Inventory Detail > By Item to open the Inventory Detail by Item Report
window. By default, the window displays results for all items.
4. If you want to select a different set of items, click the Browse (...) button next to the Items for Report field to
open the Item Selector. Use the Item Selector to select a different set of items for which to generate the report.
Click OK to close the Item Selector.
single period.
6. Click Refresh. The Inventory Detail by Item Report window is reloaded containing the new results in table
format. Note that the item names in the left column are hypertext links.
7. Click SHOW CHART to view the results in a chart. The report opens in a separate window, in chart format.
8. The Inventory Detail by Item Report is an interactive report. You can view the results in different formats by
clicking hypertext in the first column of the results table.
9. You can customize the contents and organization of the Inventory Item by Detail Report. For example, to view a
single property for an individual item at all relevant nodes for all periods, click the name of the desired item in
the first column of the report table. The results are displayed in the Stocking Point Time Varying Outputs
Report (Single Property)window for all periods. The name of the item you selected for all relevant nodes is
displayed in the Stocking Points for Report field. You can change the Stocking Points for Report, the Start
and End period for the report, and the Time Varying Properties for the report by clicking the Browse (...)
button next to each field, respectively.
122
MIPO
Column Description
Safety stock is a buffer added to inventory to counteract stockouts when demand and lead
times are uncertain. For this report, safety stock is aggregated for all customer facing
stocking points containing the Item, Location, or Attribute value displayed in this row of
Safety Stock
output for each period. If no Item, Location, or Attribute value exists at customer facing
locations for this row, a dash (-) is displayed. Then the safety stock for each period is
averaged for all periods.
Cycle stock is the inventory that exists to cover demand between shipments (or
replenishments). Cycle stock exists to accommodate an ordering policy that results in more
inventory than is strictly needed for immediate replenishment. For this report, cycle stock is
Cycle Stock aggregated for all customer facing stocking points containing the Item, Location, or
Attribute value displayed in this row of output for each period. If no Item, Location, or
Attribute value exists at customer facing locations for this row, a dash (-) is displayed. Then
the cycle stock for each period is averaged for all periods.
Prebuild stock is inventory built due to capacity constraints in anticipation of future demand.
For this report, prebuild stock is aggregated for all customer facing stocking points
containing the Item, Location or Attribute value displayed in this row of output for each
Prebuild Stock
period. If no Item, Location, or Attribute value exists at customer facing locations for this
row, a dash (-) is displayed. Then the prebuild stock for each period is averaged for all
periods.
Merchandising stock is the minimum inventory kept in a retail or customer-facing location. It

may be used for showroom or demonstration purposes, but is typically included in inventory
available to meet demand. For this report, merchandising stock is aggregated for all
Merchandising Stock customer facing stocking points containing the Item, Location, or Attribute value displayed
in this row of output for each period. If no Item, Location, or Attribute value exists at
customer facing locations for this row, a dash (-) is displayed. Then the merchandising
stock for each period is averaged for all periods.
On hand stock includes all inventory that is physically available to fill demand, which is all
types of stock except pipeline. Specifically, on hand inventory includes cycle, safety,
merchandising, and prebuild (if applicable) stock. For this report, on hand stock is
On Hand Stock aggregated for all customer facing stocking points containing the Item, Location, or
the on hand stock for each period is averaged for all periods.
Physical pipeline stock includes all inventory in the supply chain that is currently being
moved from one location to another. For this report, physical pipeline stock is aggregated
for all customer facing stocking points containing the Item, Location, or Attribute value
displayed in this row of output for each period. If no Item, Location, or Attribute value exists
at customer facing locations for this row, a dash (-) is displayed. Then the physical pipeline
Total pipeline stock is based on the total lead time and includes all orders from the time that
they are created until the time they are actually received by the location that has ordered
them. For this report, total pipeline stock is aggregated for all customer facing stocking
Total Pipeline Stock points containing the Item, Location, or Attribute value displayed in this row of output for
each period. If no Item, Location, or Attribute value exists at customer facing locations for
this row, a dash (-) is displayed. Then the total pipeline stock for each period is averaged
for all periods.
AIP is determined by adding the average cycle stock, average prebuild stock, average
safety stock, average pipeline stock, and average merchandising stock. The average
Average Inventory Position
inventory position on hand is determined by subtracting the average pipeline stock from the
average inventory position total.
123
Related Topics:
Printing Reports
Comparing Reports
Inventory Detail by Location Report
The Inventory Detail by Location Report is an interactive report that displays time-varying outputs aggregated by location.
The results can be viewed in a table or a chart.
Perform the following steps to create a Inventory Detail by Location Report:
by Location Report.
3. Click Reports > Output Reports > Inventory Detail > By Location to open the Inventory Detail by Location
Report window. By default, the window displays results for all locations.
4. If you want to select a different set of locations, click the Browse (...) button next to the Locations for Report
field to open the Location Selector. Use the Location Selector to select a different set of locations for which to
generate the report. Click OK to close the Location Selector.
single period.
6. Click Refresh. The Inventory Detail by Location Report window is reloaded containing the new results in
table format. Note that the Location Codes in the left column are hypertext links.
8. The Inventory Detail by Location Report is an interactive report. You can view the results in a different format by
clicking a Location Code in the first column of the results table.
9. You can customize the contents and organization of the Inventory Detail by Location Report. For example, to
view a single property for all nodes associated with a location for all periods, click the desired Location Code in
Report (Single Property) window for all periods. All nodes associated with the Location Code you selected is
124
MIPO
Column Description
Safety Stock
Prebuild Stock
periods.

for all periods.
Related Topics:
125
Printing Reports
Comparing Reports
Inventory Detail by Attribute Report
The Inventory Detail by Attribute Report is an interactive report that displays time-varying outputs aggregated by node
attribute. The results can be viewed in a table or a chart.
Note: Attributes are specific to your supply chain and the entities it contains. Attribute
Types, Attribute Names, and Attribute Values must be uploaded from a .zip file or
created using the MIPO interface and assigned to appropriate entities, such as locations,
items, nodes, or paths.
Perform the following steps to create a Inventory Detail by Attribute Report:
by Attribute Report.
3. Click Reports > Output Reports > Inventory Detail > By Attribute to open the Inventory Detail by Attribute
Report window. By default, the window displays results for the Stage node attribute.
4. If you want to select a different attribute, click the Browse (...) button next to the Attributes for Report field to
open the Attribute Selector. Use the Attribute Selector to select a different attribute for which to generate the
report. Click OK to close the Attribute Selector.
single period.
6. Click Refresh. The Inventory Detail by Attribute Report window is reloaded containing the new results in
table format. Note that the Attribute Values in the left column are hypertext links.
8. The Inventory Detail by Attribute Report is an interactive report. You can view the results in a different format by
clicking an Attribute Value in the first column of the results table.
9. You can customize the contents and organization of the Inventory Detail by Attribute Report. For example, to
view results for all nodes associated with a specific STAGE for all periods, click the desired Attribute Code in
Report (Single Property) window for all periods. All nodes associated with the Attribute Value you selected is
126
MIPO
Column Description
Safety Stock
Prebuild Stock
periods.

for all periods.
127
Related Topics:
Printing Reports
Comparing Reports
Stocking Points
Stocking Point Static Outputs Report (MIPO)
The Stocking Point Static Outputs Report displays static outputs for stocking points. The report results are non-interactive
and can be viewed only in a table.
Perform the following steps to create a Stocking Point Static Outputs Report:
Note: The scenario you select must be optimized before you can view the Stocking Point
Static Outputs Report.
3. Click Reports > Output Reports > Stocking Points > Static Data to open the Stocking Point Static Outputs
Report window.
5. Click Refresh. The Stocking Point Static Outputs Report window is reloaded containing the new results in
Column Description
Service level is a metric that refers to the probability that demand is met from stock.
Calculated Service Level
Calculated service level is the service level calculated by MIPO. MIPO determines optimal
service level for each inventory stocking location by using the maximum of the calculated
128
MIPO
service level and the user-specified service level.
Non-stockout Probability The probability that the item will be available at the customer-facing stocking point.
times are uncertain.
Coverage Average Safety Stock Coverage is determined by averaging Weeks of Stock over a
number of periods, called the Coverage Duration. Weeks of Stock is the number of periods
of forward expected demand that can be met by the current inventory.
Effective lead time represents the first initial periods during which no changes can be made
to the planned receipts for a given stocking point. These periods can be considered a
Effective Lead Time
“frozen” horizon. Effective lead time is calculated based on lead time, lead time standard
deviation, and reliability inputs for all the incoming supply paths of a stocking point.
The end horizon is the last period deemed as having reliable output data throughout the
End Horizon
supply chain.
Implied Initial On Hand The implied initial on hand value for each forecast period.
Modified Service Time is an output calculated on each supply path (and displayed on that
Modified Service Time path's upstream node) that shows the Customer Service Time input adjusted and
propagated upstream.
This value identifies which period is the first with valid safety stock for the associated
stocking point.
An optional field used by the Service Level Optimization (SLO) module to define an
Average Lost Demand average lost sales value for each customer-facing stocking point (averaged over good
periods).
Average Forecast Mean average forecast value for each customer-facing stocking point (averaged over good
periods).
Average Forecast CV average forecast error CV value for each customer facing stocking point (averaged over
good periods).
Average Safety Stock average safety stock value for each customer-facing stocking point (averaged over good
periods).
Effective Lost Sales Defines the acceptable lost sales percentage to be applied at the minimum service level at
Percentage the associated customer-facing stocking point.
Sequestration Flag Defines whether the sequestration flag is set for the stocking point.
Related Topics:
Printing Reports
Comparing Reports
129
Outputs for Nodes
The Stocking Point Time Varying Outputs Report is an interactive report that displays time-varying outputs for stocking
points. The results can be viewed only in table format.
can only view the sections of this report that are expressed in unit amounts.
Perform the following steps to create a Stocking Point Time Varying Outputs report for a single period:
Time Varying Outputs Report.
3. Click Reports > Output Reports > Stocking Points >Time Varying Data to open the Stocking Point Time
Varying Outputs Report (Single Period) window. By default, the window displays results for all stocking
points.
5. Click Refresh. The Stocking Point Time Varying Output Reports (Single Period) window is reloaded
containing the new results in table format. You cannot view this report in a chart. Note that the node names and
time-varying properties are hypertext links.
6. The Stocking Point Time Varying Output report is an interactive report. You can view different facets of the
customize the contents and organization of the Stocking Point Time Varying Output report, as follows:
• To view an individual property for all nodes for all periods, click the name of the desired property in the top
row of the report table. The results are displayed in the Stocking Point Time Varying Outputs Report
(Single Property) window for all periods. The property you selected is displayed in the Time Varying
Properties field. You can change the Stocking Points for Report, the Start and End period for the report,
and the Time Varying Properties for the report by clicking the Browse (...) button next to each field,
respectively.
• To view all properties for an individual node for all periods, click the name of the desired node in the first
column of the report table. The results are displayed in the Stocking Point Time Varying Outputs Report
(Single Node) window for all periods. The name of the node you selected is displayed in the Stocking
Points for Report field. You can change the Stocking Points for Report and the Start and End period for
the report by clicking the Browse (...) button next to each field, respectively. Click SHOW CHART to view
the results in a chart. The report opens in a separate window, in chart format.
130
MIPO
Column Description
Forecast Demand
Mean
Forecast Demand
The difference between forecasted and actual demand.
Standard Deviation
Safety Stock Buffer added to inventory to counteract stockouts when demand and lead times are uncertain.
One component of the average inventory position at a stocking location for a specified item and a
Cycle Stock specified period. It corresponds to the portion of average on hand inventory that exists to cover
demand between shipments (replenishments).
Prebuild Stock Inventory built due to capacity constraints in anticipation of future demand.
The minimum inventory kept in a retail or customer-facing location. It may be used for showroom
Merchandising Stock
or demonstration purposes, but is typically included in inventory available to meet demand.
Expected On Hand Expected inventory that is physically available to fill demand, which is all types of stock except
Stock pipeline.
Physical Pipeline A subset of total pipeline stock and includes all inventory in the supply chain that is currently
Stock being moved from one location to another.
Component of target inventory position and is based on the total lead time and includes all orders
Total Pipeline Stock from the time that they are created until the time they are actually received by the location that
has ordered them.
Target inventory position (TIP) is the calculated optimal replenishment policy parameter defined
Target Inventory for each stocking point for each review period. A TIP replenishment policy calls for a stocking
Position point to periodically (every PBR periods) compare its TIP to its inventory position and place
enough orders (in multiples of the batch size) to bring its inventory position up to or above its TIP.
On Hand Stock
The number of periods covered by the current on hand stock value.
(Periods)
Shipment quantities on a path for a given period, that are expected at the end stocking point in
Planned Receipts
that period, assuming deterministic lead times and service times in response to planned orders.
Safety Stock (Periods) The number of periods covered by the current safety stock value.
Unshifted Safety Stock The amount of unshifted safety stock units associated with specific stocking point data.

The number of periods covered by the current unshifted safety stock value.
in periods
Unshifted
The amount of unshifted merchandise stock units associated with specific stocking point data.
Merchandise Stock
Backlog Safety Stock Backlog safety stock associated with specific stocking point data.
Lost Sales Represents lost sales associated with a stocking point for each period of the data horizon.
131
Additional Supply For this report, additional supply capacity is aggregated for all incoming supply paths to all
Capacity selected stocking points.
Additional Storage Specifies whether any additional storage capacity is required for an item at a location during the
Capacity specified time period.
Production Quantity The amount of a given item to be produced over a specific time period.
A calculated threshold used in consumption-based production planning to trigger replenishment

Reorder Point of the associated item whenever the total amount of onhand stock and outstanding planned
receipts drops below the reorder point.
Represents the on hand inventory level at which manual intervention or monitoring will be needed
Priority Level for service class differentiation. When this level is reached, demand can no longer be served as
First-come, First-served.
Related Topics:
Outputs for Nodes
Printing Reports
Comparing Reports
Key Output Audit Report

The Key Output Audit Report provides managers and planners with the ability to review changes made to key outputs for
the selected scenario in order to determine which key outputs have been changed, who made the changes, when the
changes were made, the difference between the original key output and the changed value, and the cost associated with
the change. The following key outputs are tracked by the report:
• Safety Stock
• Reorder Point
132
MIPO
Perform the following steps to create the Key Output Audit Report :
Note: The scenario you select must be optimized before you can view the Key Output
Audit Report .
3. Click Reports > Output Reports > Key Output Audit Report to open the Key Output Audit Report window.
4. Set the following report filter categories:
• Items: Defaults to All Items. To select a different set of items, click the Browse (...) button next to the Items
field to open the Item Selector. Use the Item Selector to select a different set of items for which to generate the
report. Click OK to close the Item Selector.
• Locations: Defaults to All Locations. To select a different set of locations, click the Browse (...) button next to
the Locations field to open the Location Selector. Use the Location Selector to select a different set of
locations for which to generate the report. Click OK to close the Location Selector.
• Users: Defaults to All Users.
• Date: The default value is Today. You can select Last Five Days, Last Ten Days, Last Thirty Days or Select
a Date Range. You can also click the Calendar button to select a Date Range.
• Start: Selects the Start Period date. Defaults to the first period associated with the selected scenario. To select
a different period, click the Browse (...) button to open the Period Selector. Use the Period Selector to specify
a different Start Period for the scenario, if desired.
• End: Selects the End Period data.
5. Click Refresh to generate the Key Output Audit Report.
Reviewing specific Key Output Audit changes
The Key Output Audit Report lists the following information:
• Date when the change was made
• Item name associated with the stocking point whose key output was changed.
• Location name associated with the stocking point whose key output was changed.
• Key Output name
• Period
• Original Value
• Modified Value
• Percent Change
133
• Cost Change
• User who made the change
Adjusting Date periods for Key Output Audit changes
You can further filter information by adjusting the Start and End periods.
3. Click OK.
Related Topics:
Printing Reports
Comparing Reports
Replenishment Report
The Replenishment report is a read-only, non-interactive report that displays replenishment quantities and related inputs
and outputs. The quantities, inputs, and outputs are displayed for stocking points for each selected period.
report in units.
Perform the following steps to create a Replenishment report:
Note: The scenario you select must be optimized before you can view the Replenishment
Report.
3. Click Reports > Output Reports > Replenishment to open the Replenishment Report window. By default,
the window displays results for all stocking points.
single period.
134
MIPO
6. Click Refresh. The Replenishment Report window is reloaded containing the new results in table format.
7. Click SHOW CHART to view the results in a chart. The Replenishment report opens in a separate window, in
chart format.
Column Description
Beginning On Hand Stock includes inventory that is physically available at the beginning of
each period, namely, before the realization of the planned receipts and the demand of that
Beginning On Hand Stock
period. In particular, beginning on hand inventory includes cycle, safety, merchandising,
unusable on hand, and prebuild (if applicable) stock.
User-input planned receipts are user entered planned receipts aggregated for all incoming
User-Input Planned
supply paths to all selected stocking points. User-input planned receipts are taken into
Receipts
account when the initialization is user-specified .
Calculated Planned Calculated planned receipts are MIPO-generated planned receipts aggregated for all
Receipts incoming supply paths to all selected stocking points.
Total Supply Total supply is beginning on hand stock, plus planned receipts.
The minimum quantity of each item that must be produced in each time period (typically due
Minimum Process to a manufacturer’s desire to avoid labor schedule/shift reductions, cutbacks, layoffs, etc.) for
Quantity each manufacturing/assembly process. For this report, minimum process quantity is
aggregated for all incoming supply paths to all selected stocking points.
The maximum quantity of each item that can be ordered or produced in each time period for
Maximum Process
each manufacturing/assembly process or supply path. For this report, maximum process
Capacity
capacity is aggregated for all incoming supply paths to all selected stocking points.
For this report, planned receipts are aggregated for all incoming supply paths to all selected
Planned Receipts
stocking points.
An estimate of the mean demand for the product at that stocking location during a given
Forecast Demand Mean
period. For this report, forecast demand mean is aggregated for all selected stocking points.
Total Pipeline Stock (End
them. Since total lead time includes all components of lead-time, this implies that total
of Period)
pipeline stock includes both physical and non-physical inventory. For this report, total pipeline
stock is a component of TIP for all selected stocking points.
Reorder Point. A calculated threshold used in consumption-based production planning to

ROP trigger replenishment of the associated item whenever the total amount of on hand stock and
outstanding planned receipts drops below the reorder point.
TIP is the calculated optimal replenishment policy parameter defined for each stocking point
for each review period. A TIP replenishment policy calls for a stocking point to periodically
Target Inventory Position
(every PBR periods) compare its TIP to its inventory position and place enough orders (in
multiples of the batch size) to bring its inventory position up to or above its TIP.
135
End On Hand Stock includes inventory that is physically available at the end of each period,
namely, after the realization of the planned receipts and the demand of that period. In
End On Hand Stock
particular, end on hand inventory includes cycle, safety, merchandising, unusable on hand,
and prebuild (if applicable) stock.
For this report, the order (replenishment) quantity is aggregated for all incoming supply paths
Order Quantity
to all selected stocking points.
Related Topics:
Printing Reports
Comparing Reports
Inventory Components Report

The Inventory Components report is a read-only, non-interactive report that displays the inventory component quantities
for specified stocking points for each selected period. The results of the report can be based on all nodes in a supply
chain, or on a selected group of nodes.
Note: Viewing report contents that are expressed as monetary amounts (cost) is a user
report in units.
Perform the following steps to create an Inventory Components Report:
Summary Report.
3. Click Reports > Output Reports > Inventory Components to open the Inventory Components Report
window. By default, the window displays results for all stocking points.
Note: The Advanced Report Filtering for stocking points can also be used by clicking the
blue pushpin button.
single period.
136
MIPO
6. Click Refresh to generate the Inventory Components Report.
The Inventory Components Report results, which can be viewed as cost or in units, include information about the
properties listed in the following table:
Column Description
One component of the average inventory position at a stocking location for a specified item
Cycle Stock and a specified period. It corresponds to the portion of average on hand inventory that exists
to cover demand between shipments (replenishments).
The minimum inventory kept in a retail or customer-facing location. It may be used for
Merchandise Stock showroom or demonstration purposes, but is typically included in inventory available to meet
demand.
A subset of total pipeline stock and includes all inventory in the supply chain that is currently
being moved from one location to another.
Component of target inventory position and is based on the total lead time and includes all
Total Pipeline Stock orders from the time that they are created until the time they are actually received by the
location that has ordered them.
Related Topics:
Printing Reports
Comparing Reports
Processor Reports
Supply Processor Report
The Supply Processor report displays the scheduled and actual values that the Supply processor uses for calculations.
The report can be run for a single internal stocking point and a user-specified period. The report displays several
statistics calculated by the Supply processor, including Mean Loss Ratio, Standard Deviation of Loss, CV of Loss ratio,
and MAPE.
3. Select Reports > Processor Reports > Supply Processor.
137
4. Click the blue pushpin button to generate a report based on a previously saved filter selection. Otherwise, use
the Browse.. button next to the Stocking Points for Report field to choose an internal stocking point on which
to report.
Note: This report allows you to select internal stocking points only.
5. Use the Start and End selectors to set location and date parameters.
6. Click Refresh to run the report.
selection by clicking the black pushpin button..
Details:
• This report displays row totals for all periods in the Supply processor data set, not just those selected for the
report.
• All statistical values shown in this report are independent of the period selected and cover the entire data set.
Related Topics:
Printing Reports
Comparing Reports
Published Reports
Published Reports
The Reports menu allows you to select and export flat files containing different types of data. Grouped by Inputs or
Outputs, these text-based files are intended to be viewed, edited, and manually loaded into third-party reporting
applications, such as Microsoft Access or Excel.
Note: Generating published reports is a user privilege. You can only view and export files
if you have privileges to do so.
Generating Published Reports
Published reports rely on inputs and outputs related to a selected supply chain, including scenario-specific output data
validated and optimized. Unless you select an alternative supply chain and/or scenario, the Published Reports feature will
automatically select the default supply chain and associated base scenario. If the published report you export contains
outputs, the scenario you select must be validated and optimized.
When you export a published report, the application generates a text file containing the specific data which is copied to a
directory on the application server machine. The text file will have either a .txt extension or .csv (comma separated
values) extension.
Perform the following steps to generate a published report on the application server:
138
MIPO
1. Use the Supply Chain Selector to select the supply chain for which you want to generate the published report.
2. Use the Scenario Selector to select the base or user scenario for which you want to generate the published
report.
Note: If the published report you want to generate contains output data, the scenario you
select must be optimized for the file to be displayed in the Published Reports window. In
addition, you must have privileges to access it.
3. Click Reports > Published Reports > Published Reports to open the Published Reports window.
4. Identify the files containing the data that you want to export under the Choose Files to Export - Inputs or
Choose Files to Export - Outputs heading.
5. Ensure that the check boxes associated with the desired files are selected; deselect check boxes for files
containing data you do not want to export.
Note: Click the check box next to the column heading labeled All Files to select or
deselect all of the available published reports.
6. Note that the Destination Directory column contains the path name of the directory on the application server
machine into which the file will be exported. This directory is configured by specifying its path name in a
.properties file that is installed on the application server. The subfolders in this path denote the supply chain
name if the base scenario is selected, user scenario name if a user scenario is selected, and the name of the
file to be exported.
Note: Only a network administrator or IT personnel should modify the destination directory
path name. Changes to the destination directory apply to all users who have privileges to
export Model Data Files. For additional information, refer to the Installation and Upgrade
Guide.
7. Click OK. The published reports you selected are exported to the application server machine.
Note: It can take several seconds for the files you selected to be exported to the
application server machine. Clicking OK multiple times causes your request to be
submitted multiple times. This can result in increased processing time and the
accumulation of redundant files on the application server.
8. The Export History panel will display the following information for the selected scenario and each Model Data
File being processed:
• Name of the report you selected to publish
• File Name of the exported file, including the Name, a timestamp including the year, month, date,
hour, minute, and second the file is exported, and .csv or .txt file extension
Note: Multiple users can export files to same directory the application server. The
timestamp included in the File Name can help you identify which file you exported.
• Status of the export process
Note: A published report whose Status is In Progress cannot be selected or submitted

for exporting. You can only select and export a published report if it had not yet been
exported or when its Status is Finished.
• Start Time and End Time of the export process, in Greenwich Mean Time (GMT), by default
• User Name of the user who exported the file
• Comments that can be entered by your organization to provide additional information to users
139
9. Click REFRESH to update the contents of the Export History panel. The published reports have been exported
to the application server successfully when the Status is Finished. If the Status is Failed, click Alerts > View
Alerts to view and resolve errors that prevented the published reports from being exported.
The published report is now ready to be viewed and edited if necessary, then imported into another application.
Related Topics:
Published Reports Details
Viewing Privileges
Published Reports Details (MIPO)

The following Inputs-related reports are available through the Published Reports feature:
User Account Data
Stocking Point Time Varying Inputs
Data Loading Errors
Items Master Data
Locations Master Data
The following Outputs-related reports are available through the Published Reports feature:
Stocking Point Static Data
Stocking Point TIP
Comprehensive Stocking Point Output
Supply Chain Cost Details
Aggregated TIP
Supply Chain Total Estimated Cost
Demand Processor
Threshold Notification
User Account Data
This report lists users and their details, including the last time they logged in. No configuration is needed to run this report.
The User Account Data report contains the following information:
Column Description
140
MIPO
User Login ID Login ID of the user.
First Name User’s first name.
Last Name User’s last name.
Email Address Email address of the user.
Activation Date The date when the account was activated.
Last Logged In Date The time and date when the user last logged into the account.
Termination Date The date when the account was deactivated.
This report lists all of the stocking points in the selected supply chain for all periods in the data horizon. The Stocking
Point Time Varying Inputs report contains the following information:
Column Description
Stock Keeping Unit - A unique indicator that identifies an item at a particular geographic
SKU
location.
Item A unique material or finished good identified as part of your supply chain data.
Loc A unique area and/or building identified as part of your supply chain data.
Period A date value representing the specific timeframe for the stocking points input data.
RiskPoolFactor
The prediction, projection, or estimation of demand over the specified future data
DemandForecast
horizon.
The demand standard deviation by item-location-period at all customer facing stocking

points for periods in data horizon.
DemandError
Note: This column does not appear for scenarios using DIM outputs as the data
associated with this field will not be used for optimization.
Minimum inventory kept in a retail or customer-facing location. It may be used for

MinRequiredStock showroom or demonstration purposes, but is typically included in inventory available to
meet demand. It is also known as showroom inventory or display stock.
InventoryAllocationPolicy Policy used for calculating TIP; either Priority or Divide.
Data Loading Errors
This report provides a status log of errors encountered during data loading process. The Data Loading Errors report
contains the following information:
Column Description
141
Supply Chain Name The name given to the supply chain when it was created.
Scenario Name The name given to the scenario when it was created.
Queued Date/Time The date and time when the data loading process was initiated.
Data Loading Start

The date and time when the data loader started the data loading process.
Date/Time
Load Set Filename The name of the load set file.
Interface Name The name of the interface used to load the data set.
Rejection Reason The reason the application rejected the data set.
Date/Time The date and time the load set was rejected.
Rejection Information Additional information about the load set rejection.
Rejection The classification for the rejection, either error or warning. Errors halt the data loading process,
Classification while warnings identify issues with the data, but do not halt the loading process.
Package Name The name of the package on which validations are run.
Procedure Name The name of the procedure being validated.
Error Date/Time The date and time the error was recorded.
Error Reason Additional information about the error.
Items Master Data
This report consists of a complete list of all items in all scenarios. The Items Master Data report contains the following
information:
Column Description
Desc Description of the specific item.
UOM Unit of measure.
CreationDate The date when the specific item record was created.
LastModifiedDate The last time the specific item record was modified.
Item Type User-defined category that allows you to group specific items by type.
This report consists of a complete list of all locations in all scenarios. The Locations Master Data report contains the
following information:
142
MIPO
Column Description
Loc Location - a unique area and/or building identified as part of your supply chain data.
Desc Description of the specific location.
CreationDate The date when the specific location record was created.
ContainsStockingPoints Identifies whether the specific location contains stocking points.
ContainsProcessingPoints Identifies whether the specific location contains processing points.
Location Type User-defined category that allows you to group specific locations by type.
This report details the static inputs and outputs for each stocking point in the selected scenario. The Stocking Point Static
Data report contains the following information:
Column Description
SKU
location.
Location A unique area and/or building identified as part of your supply chain data.
MaxShipLife Identifies the maximum ship life
FrzDur Identifies the freeze duration of a specific SKU.
AvgSSCov Identifies the average safety stock coverage for a specific SKU.
IsCustFacing Identifies whether or not stocking point is a customer-facing node.
CreationDate Date record was created.
LastModifiedDate Date record was last modified.
StorageCapacity Specifies the maximum storage capacity for the item-location.
SSCovDur Safety stock coverage duration for a specific SKU.
HoldingCost Holding cost percentage associated with a specific SKU.
StdCost Standard unit cost associated with a specific SKU.
DesiredServiceLevel Desired service level assigned to a specific SKU.
ScheduleAttainment Schedule attainment mean for a specific SKU.
ScheduleAttainmentCV Schedule attainment coefficient of variation for a specific SKU.
143
MaxSS Maximum shifted safety stock.
MaxUSS Maximum unshifted safety stock.
MaxROP Maximum reorder point.
Size The size of the item, small, medium, or large.
Type The item type, such as component or finished goods.
Stocking Point TIP
This report contains outbound data relating to the selected scenario, including the following information:
Column Description
OBI Name of the outbound interface.
Stock Keeping Unit Code - A unique indicator that identifies an item at a

OBI_SKU_CODE
particular geographic location.
OBI_LOCATION A unique area and/or building identified as part of your supply chain data.
A date value representing the specific timeframe for the stocking points
OBI_PERIOD
input data.
Target inventory position - The calculated optimal replenishment policy

OBI_TIP
parameter defined for each stocking point for each review period.
The amount of safety stock units associated with specific stocking point.
OBI_SAFETY_STOCK Safety stock is a buffer added to inventory to counteract stockouts when
demand and lead times are uncertain.
The amount of cycle stock units associated with specific stocking point.
OBI_CYCLE_STOCK Cycle stock is the portion of average on hand inventory that exists to cover
The amount of merchandise stock units associated with specific stocking

point. Merchandise stock is the minimum inventory kept in a retail or
OBI_MERCHANDISE_STOCK
customer-facing location. It may be used for showroom or demonstration
purposes, but is typically included in inventory available to meet demand.
The amount of on hand stock units associated with specific stocking point.
OBI_ON_HAND_STOCK On hand stock is inventory that is physically available to fill demand, which
is all types of stock except pipeline.
The amount of physical pipeline stock units associated with specific

stocking point. Physical Pipeline stock is a subset of total pipeline stock
OBI_PHYSICAL_PIPELINE_STOCK
and includes all inventory in the supply chain that is currently being moved
from one location to another.
OBI_ON_HAND_STOCK_IN_PERIODS The number of periods covered by the current on hand stock value.
OBI_SAFETY_STOCK_IN_PERIODS The number of periods covered by the current safety stock value.
144
MIPO
OBI_DEMAND Demand.
OBI_BATCH_MULTIPLES Batch multiples.
This report includes an extensive set of stocking point outputs for each period. The report allows the addition of attributes,
inclusion/exclusion of cost/unit/period data, and time offsets. The Comprehensive Stocking Point Output report contains
the following information:
Column Description
StockingPoint Stocking point identifier.
ForecastPeriod The forecast period associated with specific stocking point.
The amount of TIP in units associated with specific stocking point. Target
inventory position (TIP) is the calculated optimal replenishment policy parameter
defined for each stocking point for each review period. A TIP replenishment policy
TIPUnits
calls for a stocking point to periodically (every PBR periods) compare its TIP to its
inventory position and place enough orders (in multiples of the batch size) to bring
its inventory position up to or above its TIP.
The amount of safety stock units associated with specific stocking point. Safety
SafetyStockUnits stock is a buffer added to inventory to counteract stockouts when demand and
lead times are uncertain.
The amount of cycle stock units associated with specific stocking point. Cycle
CycleStockUnits stock is the portion of average on hand inventory that exists to cover demand
between shipments (replenishments).
The amount of prebuild stock units associated with specific stocking point. Prebuilt
PrebuildStockUnits stock is inventory built due to capacity constraints in anticipation of future
demand.
The amount of merchandise stock units associated with specific stocking point.
Merchandise stock is the minimum inventory kept in a retail or customer-facing
MerchandiseStockUnits
location. It may be used for showroom or demonstration purposes, but is typically
included in inventory available to meet demand.
The amount of on hand stock units associated with specific stocking point. On
OnhandStockUnits hand stock is inventory that is physically available to fill demand, which is all types
of stock except pipeline.
The amount of physical pipeline stock units associated with specific stocking
point. Physical Pipeline stock is a subset of total pipeline stock and includes all
PhysicalPipelineStockUnits
inventory in the supply chain that is currently being moved from one location to
another.
TargetPipelineStockUnits The amount of target pipeline stock units associated with specific stocking point.
UnshiftedSafetyStockUnits The amount of unshifted safety stock units associated with specific stocking point.
ServiceTimeTipUnits The amount of service time TIP units associated with specific stocking point.
The forecast demand mean calculated for specific stocking point. Forecast
ForecastDemandMean demand mean is an estimate of the mean demand for the product at that stocking
location during a given period.
145
Forecast standard deviation associated with specific stocking point data. Forecast
ForecastStdDev
standard deviation is the difference between forecasted and actual demand.
Average Inventory Position in units associated with specific stocking point data.
AIP is an estimate of the average on-hand stock (which includes the sum of
average safety, average cycle, average merchandising, and average prebuild
AIPUnits
stock, if applicable), plus average physical pipeline stock at the specified stocking
point/period combination. AIP represents the average of the sum of these
components over a period.
AvgCycleStockUnits Average cycle stock units associated with specific stocking point data.
AvgOnhandStockUnits Average on hand stock units associated with specific stocking point data.
AvgPhysicalPipelineStockUnits Average physical pipeline stock units associated with specific stocking point data.
BacklogSafetyStockUnits Backlog safety stock associated with specific stocking point data.
A calculated threshold used in consumption-based production planning to trigger

ReorderPointUnits replenishment of the associated item whenever the total amount of on hand stock
and outstanding planned receipts drops below the reorder point.
ProductionQty The amount of a given item to be produced over a specific time period.
Additional supply capacity is aggregated for all incoming supply paths to all
AdditionalSupplyCapacity
selected stocking points.
Specifies whether any additional storage capacity is required for an item at a

AdditionalStorageCapacity
location during the specified period.
Represents lost sales associated with a stocking point for each period of the data
LostSales
horizon.
PlannedReceipts Planned receipts associated with specific stocking point data.
TimeAvgPipelineStock Time average pipeline stock associated with specific stocking point data.
Average Inventory Position costs associated with specific stocking point data. AIP
is an estimate of the average on-hand stock (which includes the sum of average
safety, average cycle, average merchandising, and average prebuild stock, if
AIPCosts
applicable), plus average physical pipeline stock at the specified stocking
SafetyStockCosts Safety stock costs associated with specific stocking point data.
AvgCycleStockCosts Average cycle stock costs associated with specific stocking point data.
PrebuildStockCosts Prebuild stock costs associated with specific stocking point data.
MerchandiseStockCosts Merchandise stock costs associated with specific stocking point data.
AvgOnhandStockCosts Average on hand stock costs associated with specific stocking point data.
AvgPhysicalPipelineStockCosts Average physical pipeline stock costs associated with specific stocking point data.
ForecastDemandMeanCosts Forecast demand mean costs associated with specific stocking point data.
BacklogSafetyStockCosts
The cost associated with the Backlog safety stock related to specific stocking
146
MIPO
point data.
Determined as the sum of lost sales for the customer facing stocking point over
LostMargin
specified period.
OnhandStockPeriods The number of periods covered by the current on hand stock value.
SafetyStockPeriods The number of periods covered by the current safety stock value.
UnshiftedSafetyStockPeriods The number of periods covered by the current unshifted safety stock value.
InventoryAllocationPolicy Policy value used to calculate TIP for the specific stocking point.
Represents the on hand inventory level at which manual intervention or

PriorityLevel monitoring will be needed for service class differentiation. When this level is
reached, demand can no longer be served as first-come, first-served.
This report displays the various aggregated cost information for each stocking point in the supply chain. It also allows for
the inclusion of attributes and time offsets. The Supply Chain Cost Details report contains the following information:
Column Description
Stocking Point Name The name of the stocking point.
Start Date The start date for the period.
End Date The end date for the period.
Processing Cost
Inventory Holding Cost prebuild stock, and average merchandising stock. The total chain inventory investment, holding
for all periods.
this report, it is determined by multiplying the forecast mean and order administration cost for all
Order Admin Cost
stocking points. The sum of the results is obtained for each period, resulting in an average order
Handling Cost unloading costs, breakdown costs, labor costs, and machinery costs. For this report, handling
cost is determined by multiplying the forecast mean and handling cost for all stocking points. The
147
periods.
Other Cost
Number of Orders Number of orders.
Cost of Orders Cost of orders.
Average Order
Average order quantity.
Quantity
Average Order Interval Average order interval.
Aggregated TIP
This Outputs-based report lists on hand, pipeline, TIP, and (optionally) safety stock per item-location-period, and
aggregated by dummy node. This report includes the following information:
Column Description
SKU
location.
LOCATION A unique area and/or building identified as part of your supply chain data.
PERIOD The length of time related to the data
ON_HAND_STOCK The amount of stock on hand at a given location during a specific period
Based on the total lead-time, the total pipeline stock includes all orders from the time that
TOTAL_PIPELINE_STOCK they are created until the time they are actually received by the stocking point that has
ordered them.
Target inventory position - The calculated optimal replenishment policy parameter defined
TIP
for each stocking point for each review period.
A buffer added to inventory to counteract stockouts when demand and supply are
SAFETY_STOCK
uncertain.
This report provides cost estimate overview of the supply chain for a selected period. The Supply Chain Total Estimated
Cost report contains the following information:
Column Description
148
MIPO
Processing Cost
points. The sum of the results is obtained for each period, resulting in an average processing cost
for all periods.
for all periods.
Order Admin Cost
periods.
Other Cost
Demand Processor
This output report provides the following demand information:
Column Description
SKU Stock Keeping Unit - A unique indicator that identifies an item at a particular geographic location.
The value used to apply bias adjustment to the stocking point forecast at the end of demand error
BiasRatio
processing.
MAPE The value used for MAPE CV computation.
CV represents the difference between forecasted and actual demand. A statistical measure of
CV
149
Represents the value used to make a heuristic adjustment to the safety stock computation based
RiskPoolFactor
on the perceived correlation of demand across customer-facing nodes.
Value determines the mechanism used to decide the default CV, with the choices being
Analysis Mechanism
minimum, maximum, or average.
Identifies if demand has been classified as one of the following: Frequent, Insufficient Data,
Demand Classification
Intermittent, or Seasonal.
This report displays information where on-hand inventory exceeds customer-specified capacity levels per period at
locations in the supply chain. The report uses standard MIPO attributes to designate threshold limits. The Threshold
Notification report contains the following information:
Column Description
LOCATION_NAME Name associated with the stocking point.
LOCATION_ATTRIBUTE_NAME User-defined Location attributes value.
LOCATION_THRESHOLD_VALUE The on-hand inventory threshold value for the location.
SUMMATION_VALUE Summation value.
A unique material or finished good identified as part of

ITEM
your supply chain data.
A date value representing the specific timeframe for the

PERIOD
stocking points input data.
ATTRIBUTE_UNITS Attribute units.
ON_HAND_VALUE On hand value.
CONSUMED_VALUE Consumed value.
ON_HAND_UOM On hand unit of measure.
Backlog safety stock associated with specific stocking

BACKLOG_SAFETY_STOCK
point data.
ON_HAND_LESS_BACKLOG_VALUE On hand less backlog value.
ON_HAND_LESS_BACKLOG_CONSUMED_VALUE On hand less backlog consumed value.
ON_HAND_LESS_BACKLOG_SUMMATION_VALUE On hand less backlog summation value.
Compare Scenarios Report

Through the Reports menu, you can access the Compare Scenario feature, which lets you select two or more optimized
scenarios for comparison. Use this feature to compare comprehensive stocking point data in a tabular format showing the
selected scenarios side-by side for easy reference.
150
MIPO
Note: The Compare Scenarios feature is a user privilege. You can only generate a
Compare Scenarios report if you have privileges to do so.
Generating a Compare Scenarios Report
The Compare Scenarios reports relies on data related to a selected supply chain, including scenario-specific output data
validated and optimized. This feature will only work with scenarios validated and optimized for which you have access
privileges.
When you generate a Compare Scenarios report, the application creates a text file containing the specific data which is
accessed through the Publishing Queue. The text file will have a .csv (comma separated values) extension.
Perform the following steps to generate a Compare Scenarios report:
1. Click Reports > Published Reports > Compare Scenarios to open the Compare Scenarios window.
2. Under the Data Store Scenarios Available for Comparison heading, click the associated check box for each
scenario you want to compare. Also, deselect check boxes for scenarios containing data you do not want to
include in your report.
Note: Click the check box next to the column heading labeled Compare to select or
deselect all of the available scenarios for comparison.
3. Under the Choose Scenario Comparison Files to Generate heading, click the associated entity you wish for
comparison.
Note: Click the check box next to the column heading labeled Main Entities to select or
deselect all of the scenario entities for comparison.
4. Type in a unique name for your report in the Label field. This label name will be used to distinguish your report
from other reports listed in the Publishing Queue.
5. Click OK. The scenarios you selected for comparison are submitted to the Publishing Queue.
Note: It can take several seconds for the scenarios you selected to be generated into the
Compare Scenarios report. Clicking OK multiple times causes your request to be
6. Go to the Publishing Queue to view your report.
Related Topics:
Publishing Queue
Viewing Privileges
Publishing Queue
The Reports menu lets you view reports sent by the application to the Publishing Queue. Use this feature to access all
published reports.
151
Note: The Publishing Queue feature is a user privilege. You can only access this feature if
you have privileges to do so.
Accessing Reports from the Publishing Queue
Perform the following steps to access a report from the Publishing Queue:
1. Click Reports > Published Reports > Publishing Queue to open the Publishing Queue window.
2. Identify the report you wish to view under the Report Name and Report Information headings.
3. Click the associated link in the File Name heading to access the report. You have the option to either open the
report or save it.
Cancelling or Removing Reports from the Publishing Queue
Perform the following steps to cancel or remove a report from the Publishing Queue:
2. Identify the report you wish to cancel or remove under the Report Name and Report Information headings by
clicking its associated check box.
Note: Click the check box next to the column heading labeled Report Name to select or
deselect all of the available reports in the Publishing Queue.
report or save it.
Related Topics:
Compare Scenarios Report

You can change your report preferences to specify how and what you want to view in the Report windows. Specifically,
you can choose to view report results in Units or Cost, and TIP or AIP.
Note: Depending on the report with which you are working and your user privileges, not
all user preferences are available for selection in the Report Preferences window. For
example, if you are creating a report that only generates results for AIP, the TIP and AIP
radio buttons are disabled. In addition, there are no preferences associated with some
reports, such as the Master Summary Report.
Perform the following steps to change your preferences for reports:
152
MIPO
1. Click PREFERENCES in the reports window to open the Report Preferences window.
2. Click the Cost or Units radio button to view report results as cost data or in units, respectively.
3. Click the TIP or AIP radio button to view report calculations as target inventory position or average inventory
position, respectively.
4. Click OK to save your changes and close the Report Preferences window.
Note: You can also change your report preferences by using the User Settings window.
Click Settings > User Settings to open the User Settings window. The ability to access
the User Settings window is a user privilege.
Related Topics:
Printing Reports
Comparing Reports
Comparing Reports
The button labeled POPUP appears in the upper right corner of all reports windows. You can use the POPUP button to
open the window you are currently viewing into another, separate window, allowing you to maximize your viewing area.
Opening a report in a separate window also allows you to compare the results of multiple reports side-by-side. For
example, the instructions below outline how to compare two reports.
Perform the following steps to compare two reports:

1. Click Reports to create the report whose results you want to view.
2. Click POPUP to open the report results in a new window. Note that the new window contains the name of the
supply chain and scenario for which the report was created.
3. Click on the main browser window or minimize the new window. If desired, choose a different supply chain,
scenario, period, or change inputs that affect the outcome of the report.
4. Click Reports and create the report whose results you want to compare with the original report. Note that you
may have to re-optimize the scenario to validate and update the outputs before you can generate a new report.
5. Maximize the original report results in the new window by clicking its name in the Windows toolbar. You can
now compare the results and differences based on the changes you made.
Related Topics:
Printing Reports
Printing Reports
You can print reports that you generate in any application. Printed reports include the name of the report, the name of the
supply chain and scenario you selected, information about when the scenario was last modified and by whom, the period
for which the report was generated, and the attributes or other parameters you selected, as appropriate.
Note: You can print reports results displayed in a table or a chart.
Perform the following steps to print a report:
153
1. Generate a report.
2. If you are viewing the results:

• In a table, click PRINT to open the report in a separate window. Click Print. The Print dialog opens.
• In a chart, simply click PRINT. The Print dialog opens.

3. Adjust your printer settings if desired, and click Print.
Related Topics:
Comparing Reports

Report results generated in any application can be exported in Microsoft Excel format to your local PC. Exported reports
include the name of the report, the name of the supply chain and scenario you selected, information about when the
scenario was last modified and by whom, the period for which the report was generated, and the attributes or other
parameters you selected, as appropriate.
Note: When you export to Excel, reports results are displayed in a table above the chart if
a chart exists for that report
Perform the following steps to export report results to Excel:

1. Generate a report and ensure that you are viewing the results in a table, the default format.
2. Click EXPORT located at the top of the Report window. The File Download dialog opens, prompting you to
Open or Save the file, Cancel the operation, or obtain More Info.
3. Click Save. The Save As dialog opens.
4. Choose a directory in which to save the exported report, enter a name the File Name field, and click Save. The
exported report is saved in the directory you specified. The Download complete dialog opens.
5. Click Close to close the Download complete dialog.
6. Your report results are saved in Microsoft Excel format, in the directory you specified.
Related Topics:
Printing Reports
Comparing Reports
Managing Alerts
Managing Business Alerts
Managing Business Alerts
The Business Alerts feature lets you define and implement global validation rules to be used during the exception
management process. When data validation occurs using these pre-defined customizable business rules, alerts will be
generated whenever data exceeds a specified trigger value.
154
MIPO
The Manage Business Alerts screen displays a table listing of available Business Alerts, along with information such as
validation settings, severity settings, whether or not the Business Alert is active, when the Business Alert was last
modified, and who made the changes.
Note: You can define Business Alert settings for a specific data set by editing the data
set’s BAS.DAT file. See the Installation and Upgrade Guide for more information.
Using the features of the Manage Business Alerts screen, you can perform the following global functions:
• Activate or deactivate a specific alert
• Set severity level for a specific alert
• Change trigger value parameter for a specific alert
• Define a new Business Alert
• Remove a Business Alert
Related Topics:
Activating or deactivating a Business Alert
Setting a Business Alert's severity level
Changing a Business Alert's trigger value
Defining a new Business Alert
Deleting a Business Alert
Editing Business Alerts
Editing Business Alerts
When managing Business Alerts for the exception management process, you can configure the following settings:
Using the Edit Business Alerts screen, you can also define your own Business Alerts, as well as remove any Business
Alerts.
Related Topics:
155
By default, the Business Alerts supplied with the application are deactivated. To activate or deactivate a Business Alert:
1. From the menu, click Alerts > Manage Business Alerts.
2. Scroll through the list to select the Business Alert by clicking its associated radio button.
3. Click Edit to access the Edit Business Alert Rule screen.
4. Click the Active dropdown list to select either Yes or No.
5. Click OK.
You will return to the Manage Business Alerts screen. The Business Alert Rules table will be updated to
reflect your changes. A message appears instructing you to click the Apply button to activate all pending
Business Alert rule changes.
6. Click Apply to implement the change.
Related Topics:
The severity level setting is used by the Exception Management tool to determine whether or not the application must stop
processing a data set when an exception occurs. The settings include the following:
• Informational - Informational alerts are generated upon request to provide a summary progress of processing
for informational purposes. The generation of informational alerts can be enabled or disabled, by default,
depending on context.
• Warning - Warning alerts inform the user when a condition has occurred that could cause the software to
behave differently from its normal mode. Warnings can include initializations of missing initial values, unsolicited
changes to user preferences, and exceeding suggested limits.
• Error - An alert with error severity denotes a condition that may or may not require user attention. An alert with
error severity is recoverable within the context of the software module in use, so that processing may proceed,
at least partially.
156
MIPO
• Fatal Error - Fatal errors cause the procedure or computation in progress to terminate and roll the persistent
state of the installation to a consistent state. In general, fatal errors do not cause the server software or the user
session to terminate, unless the error occurred in an infrastructural area necessitating such termination.
To set the severity level for a specific Business Alert:
1. From the MIPO menu, click Alerts > Manage Business Alerts.
4. Click the Severity dropdown list to select the desired level.
5. Click OK.
Related Topics:
A Business Alert's trigger value defines the threshold measurement related to the rule set for the Business Alert that must
be crossed in order for the application to generate an alert. For example if the trigger value for the Demand CV Business
Alert has been set to 1%, when the application detects a scenario data set record whose demand value is greater than
1% compared to the supply chain data set, an alert is generated.
To change the trigger value for a specific Business Alert:
4. Under the Input Parameters tab, change the Value field the desired trigger value.
5. Click OK.
You will return to the Manage Business Alerts screen. The Business Alert Rules table will be updated to reflect
your changes. A message appears instructing you to click the Apply button to activate all pending Business
Alert rule changes.
157
Related Topics:
MIPO provides the capability to define any new Business Alert. The process is as follows:
1. Define the new Business Alert through rules written in a stored procedure.
2. Place new stored procedure on the database server along with the Business Alert stored procedures supplied
with the application.
3. Use the Edit Business Alerts feature to implement the new Business Alert.
To create a new Business Alert:
2. If you are copying the configuration settings of an existing business alert, scroll through the list to select the
Business Alert by clicking its associated radio button, then click Duplicate. Otherwise, click Add.
3. Fill out or modify the following configuration settings:
• Business Alert name
• Validation step
• Alert message
• Stored Procedure name
• Activation setting
• Severity level
4. Fill out the Input Parameters; if necessary use the Add button to create a new parameter.
5. Fill out the Output Parameters; if necessary use the Add button to create a new parameter.
6. Click OK.
You will return to the Manage Business Alert Rule screen. The Business Alert Rules table will be updated to
Related Topics:
158
MIPO
If you wish to delete a Business Alert, do the following:
3. Click Delete
4. A Confirm dialog box appears. Click OK.
Related Topics:

Active Trigger
Setting Value

percentage.

159


specified criteria.


criteria.



criteria.

criteria.


specified criteria.

specified criteria.
160
MIPO

criteria.

criteria.

specified criteria.

criteria.

Related Topics:
Managing Alerts
Managing Scenario Business Alerts

Managing Scenario Business Alerts
The Scenario Business Alerts feature lets you view, define and implement scenario-specific validation rules to be used
during exception management process. When data validation occurs using these pre-defined customizable business
rules, alerts will be generated whenever data exceeds a specified trigger value.
The Manage Scenario Business Alerts screen displays a table listing of Business Alerts assigned to the selected scenario,
along with information such as validation settings, severity settings, and whether or not the Business Alert is active.
Using the features of the Manage Scenario Business Alerts screen, you can perform the following:
161
• Assign a new Business Alert to the selected scenario
• Remove a Business Alert from the selected scenario
Related Topics:
Viewing Business Alerts associated with a user scenario
Activating or deactivating a Scenario Business Alert
Setting a Scenario Business Alert's severity level
Changing a Scenario Business Alert's trigger value
Assigning a new Scenario Business Alert
Removing a Scenario Business Alert
Viewing Scenario Business Alerts

To see Business Alerts assigned to a specific scenario, along with their configuration settings, do the following:
2. Use the Scenario Selector to select the user scenario.
3. From the menu, click Alerts > Manage Scenario Business Alerts.
5. Click OK to access the Business Alerts Rules screen. This allows you to see the configuration settings for the
selected Business Alert.
6. Click Back to return to the Manage Scenario Business Alerts screen.
7. Click OK when you are finished reviewing the Business Alerts associated with the scenario.
Related Topics:
162
MIPO
Editing Scenario Business Alerts
Editing Scenario Business Alerts
When managing Scenario Business Alerts for the exception management process, you can configure the following
settings:
• Assign a new Business Alert to a selected user scenario
• Remove an assigned Business Alert from a selected user scenario
Related Topics:
Activating or deactivating Scenario Business Alert
To activate or deactivate a Scenario Business Alert:
6. Click the Active dropdown list to select either Yes or No.
7. Click OK.
Related Topics:
163
Setting a Scenario Business Alert's Severity Level
The severity level setting is used by the Exception Management tool to determine whether or not the application must stop
processing a data set when an exception occurs. The settings include the following:
• Informational - Informational alerts are generated upon request to provide a summary progress of processing
for informational purposes. The generation of informational alerts can be enabled or disabled, by default,
depending on context.
• Warning - Warning alerts inform the user when a condition has occurred that could cause the software to
behave differently from its normal mode. Warnings can include initializations of missing initial values, unsolicited
changes to user preferences, and exceeding suggested limits.
• Error - An alert with error severity denotes a condition that may or may not require user attention. An alert with
error severity is recoverable within the context of the software module in use, so that processing may proceed,
at least partially.
• Fatal Error - Fatal errors cause the procedure or computation in progress to terminate and roll the persistent
state of the installation to a consistent state. In general, fatal errors do not cause the server software or the user
session to terminate, unless the error occurred in an infrastructural area necessitating such termination.
To set the severity level for a specific Scenario Business Alert:
6. Click the Severity dropdown list to select the desired level.
7. Click OK.
You will return to the Manage Scenario Business Alerts screen. The Business Alert Rules table will be
updated to reflect your changes. A message appears instructing you to click the Apply button to activate all
pending Business Alert rule changes.
8. Click Apply to implement the change
Related Topics:
164
MIPO
A Business Alert's trigger value defines the threshold measurement related to the rule set for the Business Alert that must
be crossed in order for the application to generate an alert. For example if the trigger value for the Demand CV Business
Alert has been set to 1%, when the application detects a scenario data set record whose demand value is greater than
1% compared to the supply chain data set, an alert is generated.
To change the trigger value for a specific Business Alert:
6. Under the Input Parameters tab, change the Value field the desired trigger value.
7. Click OK.
Related Topics:
Assigning a New Scenario Business Alert
To assign a new Business Alert to the scenario:
4. If you are copying the configuration settings of an existing business alert, scroll through the list to select the
Business Alert by clicking its associated radio button, then click Duplicate. Otherwise, click Add.
5. Configure the following configuration settings:
• Business Alert name
• Activation setting
165
• Severity level
6. Fill out the Input Parameters; if necessary click the Is Default? checkbox to change the default parameter.
7. Click OK.
Related Topics:
Removing an assigned Scenario Business Alert
If you wish to remove a Business Alert assigned to a scenario, do the following:
3. Click Delete
4. A Confirm dialog box appears. Click OK.
Related Topics:
166
MIPO

Active Trigger
Setting Value

percentage.


specified criteria.


criteria.



criteria.

criteria.

167

specified criteria.

specified criteria.

criteria.

criteria.

specified criteria.

criteria.

Related Topics:
Managing Alerts
Managing Alerts
Managing Alerts
Depending on the current state of an alert, group of alerts, or page of alerts you have selected, you can choose to perform
one of the following actions:
168
MIPO
• DISMISS - causes an alert to be removed from the list of alerts
• SUPPRESS - causes an alert to be removed from the list of alerts; in addition, alerts of this type are not
generated in the future
• HIDE - causes an alert to not be displayed in the list of alerts; in addition, alerts of this type are not displayed in
the future
• LOCK - prevents any other action from being performed on an alert
Note: When you select multiple alerts or a page of alerts, and individual alerts each have
a different status, the actions you can perform are limited accordingly. For example, if you
select two alerts, one locked and one unlocked, the UNLOCK button is enabled.
Dismissing an Alert
Dismissing an alert causes it to be removed from the list of alerts. To view a list of dismissed alerts, select Inactive from
the Status drop-down menu and click REFRESH.
Note: Alerts with a status of Inactive are periodically purged from the application.
Suppressing an Alert
Suppressing an alert causes it to be removed from the list of alerts. In addition, when you suppress an alert, alerts of the
same type are not generated in the future. When you SUPPRESS an alert type, you can specify the time period for which
that action remains in effect. After the specified time period passes, the status of the suppressed alert returns to Pending
and is again displayed in the list of alerts on the Alert Summaries or Alert Short Entries tabs. You can also add
comments that document, why, for example, you suppressed an alert type. These comments appear in the Alert Details
window.
Note: The value of the Can suppress or hide? field in the Alert Details window must be
true to SUPPRESS an alert.
Hiding an Alert
Hiding an alert causes it to not be shown in the list of alerts. In addition, alerts of this type are not shown in the future.
When you HIDE an alert, you can specify the time period for which that action remains in effect. After the specified time
period passes, the status of the hidden alert returns to Pending and is again displayed in the list of alerts on the Alert
Summaries or Alert Short Entries tabs. You can also add comments that document, why, for example, you hid an alert.
These comments appear in the Alert Details window.
Note: The value of the Can suppress or hide? field in the Alert Details window must be
true to HIDE an alert. Also, when you hide an alert, the initial alert on which you
performed this action isn't listed when you filter by Hidden status. This alert is dismissed,
while subsequent alerts of this type do appear when you filter by Hidden status.
To view a list of hidden alerts, select Hidden from the Status drop-down menu and click REFRESH. When you select an
alert type that is hidden, the UNHIDE button is enabled.
Locking and Unlocking Alerts
169
Locking an alert prevents any other action from being performed on it. A small lock icon denotes alerts that are locked. To
view a list of locked alerts, select Locked from the Status drop-down menu and click REFRESH. If you select an alert
that is locked, the UNLOCK button is enabled.
Related Topics:
Alert Definitions
Viewing Alerts
Exporting Alerts
Viewing Alert Types
Note: You can access the Alert Types window only if you have the appropriate privileges.
Perform the following steps to view and manage alert types:
1. The severity of each alert type is listed in the Severity column. An alert type can have the one of following
severity levels:
• Fatal Error- stops processing if a Fatal Error alert is generated.
• Error- stops processing if an Error or Fatal Error alert is generated.
• Warning- stops processing if any alert except Informational alert is generated.
• Informational- stops processing if any alert is generated.
2. The status of each alert type is listed in the Status column. An alert type can have the one of following statuses:
• Active - denotes an alert type on which no action has been performed
• Hidden - denotes an alert types that is hidden
• Suppressed - denotes an alert type that is suppressed

2. To select an individual alert type or multiple alert types in the Alert Types window, click the check boxes in the
first column next to the alert types that you want to select. To select all of the alert types on a page, click the
check box in the first row of the first column. Selected alert types are highlighted in yellow.
Note: Click the check box next to the column heading labeled Source to select or
deselect all of the available alert type groups on the displayed page.
3. After you have selected an alert type or a page of alert types, you can SUPPRESS or HIDE them, depending
on the current status. For more information, see Managing Alerts.
Note: The value of the Can suppress or hide? field in the Alert Type Status History
window must be true to SUPPRESS or HIDE an alert type. If you attempt to SUPPRESS
or HIDE an alert type that cannot be suppressed or hidden, it's status remains Active.
4. Click BACK to return to the Alert Settings window or click the hypertext name of an alert type to open the Alert
Type Status History window.
170
MIPO
Related Topics:
Alert Definitions
Managing Alerts
Viewing Alert Type Groups
Viewing Alert Type Status History

The Alert Type Status History window displays the following information about an alert type:
• Type - the general name of the alert type
• Status - describes the current state of the alert. The status displayed in the Alert Type Status History window
can be one of the following:
o Active
o Inactive
o Suppressed
o Hidden
o Description - the full description of the alert Type. In addition, the Description field in the Alert Type Status
History window contains specific information about the context in which the alert occurred and in some cases,
the name of the entity related to the alert. For example, if you received the alert "Analysis Horizon Exceeds End
Horizon" the Description field displays the name of the scenario and period for which the alert was generated.
o Can be suppressed or hidden? - indicates whether or not the selected alert type can be suppressed or
hidden. Suppressing an alert removes it from the list of alerts; in addition, alerts of this type will not be
generated in the future. Hiding an alert causes it to not be displayed in the list of alerts. If the value of the Can
suppress or hide? field is true, the alert type can be suppressed or hidden; if the value of this field is false, it
cannot.
o Severity - describes the seriousness of the alert. Alert severity can be Informational, Debugging, Warning,
Error, or Fatal Error.
o Transition Time - specifies when the alert type will be unsuppressed or unhidden. The Transition Time field
appears only if you have specified a time frame for unsuppressing or unhiding the alert type.
o Alert Actions - displays the history of actions performed on an alert type, including Date, Action, and any
Comments that were entered when the action was performed. The Alert Actions list appears only for alerts on
which you have performed an action.
Note: You can access the Alert Type Status History window only if you have the
appropriate privileges.
Click BACK to return to the Alert Types window.
Related Topics:
Alert Definitions
Managing Alerts
Viewing Alert Types
171

You can view and manage alerts grouped strictly according to their Source and categorized according to Alert Type in
the Alert Settings window.
Note: You can access the Alert Settings window only if you have the appropriate
privileges.
Perform the following steps to view alert types categorized according to their source:
1. Click Settings > Alert Settings to open the Alert Settings window.
2. Click a category link from the list of displayed alert types. The associated alert type entries are displayed in a
table.
3. The status of each alert type is listed in the Status column. An alert type can have the one of following statuses:
• Active - denotes an alert type group on which no action has been performed
• Hidden - denotes an alert type group that is hidden
• Suppressed - denotes an alert type group that is suppressed
• Mixed - denotes an alert type group that contains individual alerts types that are in two or more different
states or when alerts in the alert type group contain different values in the Can suppress or hide? field.
4. To select Alert Types categorized according to Source in the Alerts Settings window, click the check boxes in
the first column next to the alert type categories that you want to select. To select all alert type categories for all
sources on a page, click the check box in the first row of the first column. Selected alert type groups are
highlighted in yellow.
5. After you have selected a group of alert types for a source or multiple sources, you can SUPPRESS or HIDE
them, depending on the current status. For more information, see Managing Alerts.
Note: The value of the Can suppress or hide? field in the Alert Type Status History
window must be true to SUPPRESS or HIDE an alert type group. If you attempt to
SUPPRESS or HIDE an alert type group that cannot be suppressed or hidden, it's status
remains Active. In addition, you cannot UNSUPPRESS or UNHIDE an alert type group
that has a status of Mixed. You must UNSUPPRESS or UNHIDE individual alert types in
the Alert Types window.
6. To view all of the alert types in a category, click the name of the source that is a hypertext link, to open the Alert
Types window.
Related Topics:
Alert Definitions
Managing Alerts
Viewing Alert Types
Viewing Alerts
Viewing Alerts
The Alerts window allows you to view, manage, and export alerts generated by the application and its components. You
can limit which alerts you view, manage, and export by filtering them based on their Source, Class, Severity, Data
Context, Status, Date, or any combination thereof. After you've filtered the alerts that you want to view, you can view
alerts sorted by Source, Class, Severity, Data Context, Status, or Date in Ascending or Descending order.
172
MIPO
Note: You can access the Alerts window only if you have the appropriate privileges.
Perform the following steps to view alerts:
1. Click Alerts > View Alerts to open the Alerts window.
2. Filter the alerts you want to view by selecting filtering criteria.
3. Click Refresh to update the list of alerts. The list contains the following information for each alert type:
• Date and time the alert was generated.
• Type - serves as the general name of the alert
• Description - provides more detailed information about the alert Type. Note that the entries in this column
are also hyperlinks.
• Status - describes the current state of the alert. The alert states are Pending, Locked, Hidden, and Inactive.
• Severity - describes the seriousness of the alert. Alert severity can be Informational, Debugging, Warning,
Error, or Fatal Error.
• Class - describes the category an alert falls into. For example, alerts can be categorized as System, Data
Output, Data Integrity, Result Integrity, Data Input, or Computation alerts.
• Source - indicates the part of the application that generated the alert. For example, alerts can be generated
by the Data Loader, Analyze Scenarios, Validation and Optimization, and User Settings areas.
4. You can sort the list of alerts according to criteria similar to that which you used to filter them: Class, Severity,
Source, and Date in Ascending or Descending order. To do so, click an entry in the Sort By drop-down
menu, click the Ascending or Descending radio button if desired, and click REFRESH.
Note: Select Date in the Sort By drop-down menu, click the Descending radio button,
then click REFRESH to view the most recent alerts on page one of the Alerts window.
5. If the Alerts list includes a large number of alerts, you can page through the list by clicking PREV and NEXT. To
go directly to a specific page in a multi-page list, type a page number in the Page field and press ENTER.
6. Click a hyperlink for an alert in the Description column to open the Alert Details window. The Alert Details
window provides additional information about the alert whose description you clicked.
7. Click BACK to return to the Alerts window.
8. To select an individual alert or multiple alerts in the Alerts window, click the check boxes in the first column next
to the alerts that you want to select.
Note: Click the check box next to the column heading labeled Date to select or deselect
all of the available alerts on the displayed page.
9. Alerts (or a page of alerts) that are selected are highlighted in yellow.
10. After you have selected alerts or a page of alerts, you can DISMISS, SUPPRESS, HIDE, or LOCK them,
depending on the current Status. For more information, see Managing Alerts.
Related Topics:
Alert Definitions
Filtering Alerts
173
Exporting Alerts
Managing Alerts

The Alert Details window provides additional information about any specific alert as selected from the Alerts window.
Perform the following steps to view details for an alert:
1. Click Alerts > View Alerts to open the Alerts window.
2. Identify an alert for which you want to obtain more information. Click its hypertext link in the Description column
to open the Alert Details window. For more information, see Alert Definitions.
3. The Alert Details window displays the following information:
by the Data Loader, Analyze Scenarios, Validation and Optimization, and User Settings area.
• Date and time the alert was generated - The timestamp is displayed for Greenwich Mean Time (GMT).
Error, Fatal Error.
• Can suppress or hide? - indicates whether or not the selected alert can be suppressed or hidden.
Suppressing an alert removes it from the list of alerts; in addition, alerts of this type will not be generated in
the future. Hiding an alert causes it to not be displayed in the list of alerts. If the value of the Can suppress
or hide? field is true, the alert type can be suppressed or hidden; if the value of this field is false, it cannot.
• Description - repeats the full description of the alert Type. In addition, the Description field in the Alert
Details window contains specific information about the context in which the alert occurred and in some
cases, the name of the entity related to the alert. For example, if you received the alert "Analysis Horizon
Exceeds End Horizon" the Description field displays the name of the scenario and period for which the alert
was generated.
• Alert Actions - displays the history of actions performed on an alert, including Date, Action, and any
Comments that were entered when the action was performed. The Alert Actions list appears only for alerts
on which a user has performed an action.
5. After you have viewed the alert details, you can choose to DISMISS, SUPPRESS, HIDE, or LOCK the alert,
depending on the current Status. For more information, see Managing Alerts.
Note: If the value displayed in the Can suppress or hide? field is false, you cannot suppress or hide the alert.
6. Click BACK to return to the Alerts window.
Related Topics:
Exporting Alerts
Alert Definitions
Managing Alerts
174
MIPO
Exporting Alerts to Excel

Alerts generated in the application can be exported into Microsoft Excel on your local PC. Exported alerts include the
filtering information used to generate the list, as well as a table depicting the following information for each alert entry:
• Date and time the alert was generated - The timestamp is displayed for Greenwich Mean Time (GMT).
• Description - the full description of the alert Type.
• Supply chain name - indicates the supply chain associated with the alert.
• Scenario name - indicates the scenario associated with the alert.
Error, Fatal Error.
by the Data Loader, Analyze Scenarios, Validation and Optimization, and User Settings area.
• Details - contains specific information about the context in which the alert occurred and in some cases, the
name of the entity related to the alert. For example, if you received the alert "Analysis Horizon Exceeds End
Horizon" the Details field displays the name of the scenario and period for which the alert was generated.
Perform the following steps to export report alerts to Excel:
1. Click EXPORT located at the top of the Alerts window. The File Download dialog opens, prompting you to
Open or Save the file, Cancel the operation, or obtain More Info.
2. Click Save. The Save As dialog opens.
3. Choose a directory in which to save the exported report, enter a name the File Name field, and click Save. The
exported report is saved in the directory you specified. The Download complete dialog opens.
4. Click Close to close the Download complete dialog.
5. Your report results are saved in Microsoft Excel format, in the directory you specified.
Related Topics:
Alert Definitions
Filtering Alert Short Entries
Managing Alerts
MIPO Alert Definitions

The tables below list definitions and troubleshooting strategies for the alerts MIPO generates in the following areas:
Analyze Scenario
175
Business Alerts
Customer Support
Data Loader
Export Data Set
Load Set Translator
Processor Management
Published Reports
User Settings
Multistage Inventory Planning and Optimization Alerts
Analyze Scenario Alerts

Click a link below to see the definition corresponding to the associated alert.
Optimization Completed
Checked Exception in Scenarios
Optimization Started
Validation Started
Validation Completed
Scenario State Changed
Scenario Created
Scenario Deleted
Processing Started
Processing Ended
Processing Failed
Business Alerts Validation on Inputs Started
Business Alerts Validation on Inputs Completed
Postprocessing Started
Postprocessing Completed
Business Alerts Validation on Outputs Started
Business Alerts Validation on Outputs Completed
Report Generation Started
Report Generation Completed
Scenario Transition Cancelled
Gateway Data Loader Waiting
176
MIPO
Gateway Data Loader Maximum Number of Retries Exceeded
Gateway Data Loader SQL*Loader Error
Processor Dependency Error
Processor Dependency Warning
New Item Processor Missing Historical Sales
New Item Processor Missing Historical Demand Forecast
New Item Processor Missing Future Demand Forecast
Business Alerts
Informational Business Alert
Warning Business Alert
Error Business Alert
Fatal Error Business Alert
Comparison Scenario Missing
Customer Support Alerts

License expiration warning Alert
Data Loader Alerts

Data Loading Started
Data Loading Complete
Data Set Rejected
Data Set Enqueued
Data Set Dequeued
Data Set Moves Forward
Data Set Formats Mismatched
Supply Chain or Scenario Renamed
Data Loader Rejects and Errors
Load Set Cancelled
Export Data Set Alerts

177
Scenario Export Started
Scenario Export Failed
Scenario Export Complete
Load Set Translator Alerts

Load Set Translator Setup Failure
Load Set Translator Resource Missing
Load Set Translation Failed
Translator Format Unrecognized
Processor Management Alerts

Insufficient Historical Periods
Schedule Attainment CV Capped
Schedule Attainment CV Default
User Not Found
User Already Associated
Profile Not Found
User Disabled
Processing Cancelled
Published Reports Alerts

Export Process Failed
Export Process Finished
Export Process Started
On Hand Exceeds Threshold
On Hand Minus Backlog Exceeds Threshold
User Settings Alerts

User Preferences Changed
178
MIPO
User Privileges Changed
User Preferences Conflict
User Information Changed
User Accounts Changed
Maximum Users Reached
User Profiles Changed
Checked Exception Notify Admin
Checked Exception Notify Support
User Account Locked Out
Multistage Inventory Planning and Optimization Alerts

Supply Paths Create Loop
Holding Cost Invalid
Analysis Horizon Exceeds End Horizon
Customer Node has Outgoing Path
Forecast Demand Mean and Std Dev Mismatch
Min Process Quantity Too High
Process Point Upstream Error
Process Point Downstream Error
Stocking Point Upstream Error
Stocking Point Downstream Error
Invalid Supply Ratio
Supplier Node has Incoming Path
Supplier Node Downstream Error
Service Time on Multiple Sourced Node
Coefficient of Variation Too High
Resource Shared
Replenishment Plan Infeasible
Path Contains Invalid Data
BOM Data Missing
Stocking Point Data Error
Forecast Demand Data Missing
Path Data Missing
179
Resource Missing Forecast Data
Invalid Start Period
Invalid Data on Customer Path
Process Point Resource Error
Holding Cost Zero
Unit Cost Zero
Process Point Missing Resource
Process Point Contains Multiple Resources
Process Point Missing Static Data
Process Point Missing Time Varying Data
Stocking Points Missing Packaging Info
Process Point has Identical Items Upstream
Yield Negative or Zero
PSLR Exceeds PBR
Empty Scenario
Maximum Ship Life Exceeded
On Hand Without Demand
Item-Location Duplicate
Missing On Hand
Stocking Point Missing
Process Point Missing
Customer Node Missing
Supplier Node Missing
Stocking Point Wrong Type
Process Point Wrong Type
Customer Node Wrong Type
Supplier Node Wrong Type
Stocking Point Missing Location
Invalid BOM Ratio
Invalid Processing Point
Path Should Not Have Resource
Invalid BOM
Same SKU on Both Sides of BOM
Invalid Service Level

180
MIPO
Customer-facing Stocking Point Inventory Unit Cost Out of Range
Invalid Customer-facing Stocking Point Unit Cost
Invalid BOM Conversion Factor
First Batch Size Invalid
Invalid Analysis Horizon
MIPO Progress update interval
First MIPO Progress Threshold
Second MIPO Progress Threshold
First good output period > Analysis Horizon
Priority Level Capped
Frozen Window Negative
Unusable On Hand Inventory Negative
Min Batch Size Negative
Negative Process Point Frozen Window
Negative Process Point Min Batch Size
On-hand stock level exceeds storage capacity - additional storage capacity required
PBS Exceeds Max (PBR, Batch Size Coverage)
Related Topics:
Filtering Alerts
Managing Alerts
Alerts
Managing User Accounts

For Users
Editing Personal Information
The User Settings window allows you to modify your user account. You can edit your personal information, change your
password, reset profiles, view privileges and set or change your preferences.
Note: Accessing the User Settings window is a privilege. If you do not have privileges to
access your user account, you cannot edit your personal information, change your
password, reset profiles, view privileges, or change your user preferences.
Perform the following steps to edit your personal information:
1. Click Settings > User Settings to open the User Settings window.
181
2. Change the text in the First Name, Last Name, Email Address, Office Phone Number, Cell Phone Number,
or Other Phone Number fields, and click OK. The status message indicates that your changes have been
save.
Note: You can add more than one Email Address by using a semi-colon (;), with no
spaces, to separate each address. This feature is useful for user accounts created
specifically to run batch processes.
3. Click OK to save your changes. The User Settings window is reloaded and displays a status message
indicating that your changes have been saved.
Related Topics:
Resetting a Profile
Viewing Privileges
Changing Your Preferences

Perform the following steps to change your password:
1. Click Settings > User Settings to open the User Settings window. The contents of the User Info tab contain
information about your user account, by default.
2. Click CHANGE next to the Password field. The Change Password window opens.
3. Enter your old password in the Old Password field.
4. Enter your new password in the New Password field.
5. Verify your new password by entering it in the Verify Password field.
6. Click OK. The User Settings window is reloaded and displays a status message indicating that your changes
have been saved.
Expired passwords:
In compliance with Sarbanes Oxley legislation and security best practices, user passwords can be configured to expire
after a period of time. When your password expires, a Password Reset login page will appear, prompting you to select
and confirm a new password before proceeding. The system will check to ensure that passwords are not reused.
Related Topics:
Resetting a Profile
182
MIPO
Viewing Privileges
Resetting a Profile
A profile is a group of privileges and preferences that can be assigned to you by an administrator. Three default profiles
exist (but are not assigned by default):
• Administrator - Assignees of the Administrator profile have privileges to perform administrative tasks, such as
creating and maintaining user accounts and access control levels, scenario management, and other tasks.
• Planner - Assignees of the Planner profile have privileges to perform tasks related to supply chain and scenario
management.
• Technical Support - Allows users to perform technical support tasks such as viewing alerts in every module,
creating and maintaining user accounts and handling user security settings.
You can override preferences set in a profile by changing your preferences individually. If you have overridden the
preferences set in a profile in this manner, there may be some instances when you want to RESET these preferences
back to their original state, as defined in the profile.
Perform the following steps to reset a profile:
2. Ensure that your User Name is selected in the Select User drop-down menu. The User Info tab contains
3. Click User Profiles to open the User Profiles tab. If an administrator has assigned a profile to your user
account it is listed in the Assigned Profiles list.
4. Click the name of the profile that you want to reset and click RESET.
Related Topics:
Viewing Privileges
Privileges, Profiles and Preferences
Viewing Privileges
183
Perform the following steps to view your user privileges:
3. Click User Privileges to open the User Privileges tab.
4. Select the module for which you want to view your privileges by choosing it from the Select Module drop-down
menu.
5. The User Privileges tab displays the privileges that are enabled for your user account for the module you
selected.
Note: The privileges displayed in the User Privileges tab are valid from the time you
signed in. If a user with administrative privileges modifies your privileges (directly or by
assigning a profile) while you are signed in, you cannot view these changes until you log
out and sign in again.
Related Topics:
Resetting a Profile

Perform the following steps to change your user preferences:
3. Click User Preferences to open the User Preferences tab.
4. Select the module for which you want to set your preferences by choosing it from the Select Module drop-down
menu.
5. Check or uncheck preferences you want to set or enter new values as appropriate, and click OK to save your
changes. The preferences are updated for your account.
184
MIPO
Related Topics:
Resetting a Profile
Viewing Privileges
For Administrators
Changing User Settings
Creating a User Account
Note: The ability to add, modify, disable, copy and delete user accounts, and assign user
preferences and privileges, is available only if you have administrative privileges, and
privileges to access the User Settings window.
To create a new user account:
1. Click Settings > User Settings to open the User Settings window. By default, the User Info tab opens and
contains information for the current user.
2. Click TASKS > Create. The User Info tab contains empty text fields.
3. Enter appropriate text in the User Name, New Password, Verify Password, First Name, Last Name, and
Email Address required fields.
Note: The following special characters are not supported in User Names: single quote (‘),
double quote (”), backslash (\), angle brackets (>,<), ampersand (&), and pipe (|). A User
Name can not be longer than 25 characters. Also, a User Name cannot be changed after
the user account has been created.
4. Enter the user's Office Phone Number, Cell Phone Number, and Other Phone Number information, if
desired.
5. Select the Language to be displayed by the application.
6. Select the Time Zone in which the user resides. Use the Expanded List checkbox if necessary.
7. If desired, select a Time Format and Date Format.
8. Select the appropriate Decimal Notation.
9. Select the Password Security Enabled checkbox to activate password security and expiration policies for this
user. If you leave this box unchecked, the user will be exempt from password security requirements configured
for the application at your site. For more information about password security provisions and settings, see the
Installation and Upgrade Guide.
Note: The Password Security Enabled checkbox appears only if the user who is
creating the account has privileges to "Enable/Disable password security for any user."
10. Select the Account Enabled checkbox to make this account active. If you de-select this checkbox, the account
information will be saved, but the account itself will not be enabled.
185
11. To force the user to change their password after initially logging on to the new account, click the Change
Password At Next Logon checkbox.
12. Click OK. The User Settings window is reloaded and displays a status message indicating that the new user
account has been created. The user name appears in the User Selector.
13. You can now set privileges and preferences for this user account, or assign a profile.
Related Topics:
Modifying a User Account
Duplicating a User Account
Disabling a User Account
Deleting a User Account
preferences and privileges, is available only if you have administrative privileges and
Perform the following steps to modify user account information or change the account password:
1. Click Settings > User Settings to open the User Settings window. By default, the User Info tab is selected
and contains information for the current user.
2. Select a user account to modify by clicking the Browse (...) button to open the User Selector:
User Selector.
3. The User Info tab is selected and contains the information for the user you selected.
4. If you want to change personal information for this user, edit the text in the First Name, Last Name, Email
Address, Office Phone Number, Cell Phone Number, and Other Phone Number fields.
Note: A User Name cannot be changed after it has been created.
6. To change the language displayed by the application, select the Language drop down menu.
7. To change the time zone, select the Time Zone drop down menu. Use the Expanded List checkbox if
necessary.
8. If you want to change the time and/or date formats displayed by the application, use the Time Format and Date
Format drop down menus.
9. To change how numeric information is displayed by the application, use the Decimal Notation drop down
menu.
186
MIPO
10. If you want to change the password for this user, click CHANGE next to the Password field. The Change
Password window opens.
11. Enter the new password in the New Password field.
12. Verify the new password by typing it in the Verify Password field.
13. Click OK. The User Settings window is reloaded and displays a status message indicating that your changes
have been saved.
14. Change privileges and preferences for this user account, or assign a profile.
Related Topics:
Adding a User Account
Note: The ability to add, modify, disable, copy, and delete user accounts, and assign user
Perform the following steps to duplicate a user account:
Selector.
3. The User Info tab contains the information for the user you selected.
4. Click TASKS > Duplicate. The User Info tab is selected and all fields contain text based on the user account
you copied, except for the User Name, Password, and Verify Password fields, by default. In addition profile,
privilege, and preference settings are copied.
5. Enter a text in the User Name, Password, and Verify Password fields, as appropriate. Edit the text in the First
Name, Last Name, Email Address, Office Phone Number, Cell Phone Number, and Other Phone Number
fields as desired.
Note: The following special characters are not supported in User Names: single quote (‘),
double quote (”), backslash (\), angle brackets (>,<), ampersand (&), and pipe (|). A User
Name can not be longer than 25 characters. Also, a User Name cannot be changed after
187
the user account has been created.
7. Click OK. The User Settings window is reloaded and displays a status message indicating that the user
account has been created. The new User Name appears in the User Selector.
8. Change privileges and preferences for this user account, or assign a profile.
Related Topics:
When a user account is disabled, the User Name associated with the account cannot be used to sign in, although all
information and data related to the account is stored. A user account can become disabled when:
• a user with administrative privileges purposely disables the account for security reasons
• someone attempts to sign in and fails to enter valid information - the user account is automatically disabled
Disabling a user account can be useful in ensuring security, for example, when a user goes on vacation and you want to
ensure that the account cannot be accessed by anyone else. The number of times sign in can be attempted and fail is 5,
by default. This limit can be modified by the site administrator.
To disable a user account:
User Selector.
4. Uncheck the Account Enabled check box.
account has been disabled. The User Name cannot be used to sign in to the application.
Note: To enable a user account that is currently disabled, follow steps 1-3 above, then
check the Account Enabled check box. Click OK. The User Settings window is reloaded
and displays a status message indicating that the user account has been enabled.
188
MIPO
Related Topics:
Perform the following steps to delete a user account:
2. Select a user account to delete by clicking the Browse (...) button to open the User Selector:
User Selector.
4. Click TASKS > Delete. The confirmation dialog box opens and prompts you to confirm the deletion.
Note: Deleting a user account is irreversible, although information and data pertaining to
the account may exist in the database for an indefinite period of time.
account has been deleted. The User Name no longer appears in the User Selector.
Note: When you delete the account of a user all of their alerts are deleted. Also, if that
user is the Owner of a scenario, ownership of the scenario is automatically assigned to a
special user account named smartops. A user with administrative privileges must then
reassign ownership of the scenario to an existing user and grant that user privileges to
access it.
Related Topics:
189
Assigning Privileges
If you have administrative privileges, you can assign privileges that enable or prevent users from performing certain tasks.
For example, the ability to view cost information or to upgrade scenarios are privileges.
Perform the following steps to assign privileges to a user account:
2. Click User Privileges to open the User Privileges tab.
User Selector.
4. Select the module associated with the privileges you want to modify by selecting an entry from the Select
Module drop-down menu.
created. If a user creates a scenario and wants other users to be able to access it, a user
with administrative privileges must grant access privileges for the scenario.
5. Check or uncheck the check boxes for each privilege, to grant or deny the privilege, respectively.
Note: Click the check box next to the column heading labeled Privilege to select or
deselect all of the available privileges for the selected module.
Note: Privileges are hierarchical. For example, a user must have the privilege to
View/Manage Alerts before any subsequent privileges you select, such as View Alerts
or View alerts according to status, take effect. The different levels of the hierarchy are
denoted by level of indentation. Also note that assigning a high level, or base, privilege
does not mean that subsequent privileges are automatically selected and assigned. Each
privilege must be assigned individually.
indicating that the changes to the user account were saved successfully.
Note: Although the changes you make to a user account are effective immediately, if the
user whose account you modified is signed in at the time you saved the changes, he or
she cannot view the privileges you added or removed in the User Privileges tab until he
or she logs out and signs in again.
Related Topics:
MIPO Privilege Definitions
Assigning Preferences
190
MIPO
Assigning a Profile
Unassigning a Profile
If you have administrative privileges, you can assign preferences that enable or prevent users from performing certain
tasks. However, if a user changes his or her preferences individually, the changes made override preferences and profiles
an administrator applies to a user account.
Perform the following steps to assign preferences to a user account:
2. Click User Preferences to open the User Preferences tab.
User Selector.
4. Select the module associated with the preferences you want to modify by selecting an entry from the Select
Module drop-down menu.
5. Check or uncheck preferences you want to set or enter new values as appropriate.
she cannot view the preferences you changed in the User Preferences tab until he or she
logs out and signs in again.
Related Topics:
Assigning a Profile
Assigning a Profile
A profile is a group of privileges and preferences. If you have administrative privileges, you can assign profiles that enable
or prevent users from performing certain tasks. Three default profiles exist (but are not assigned by default):
• Administrator - Assignees of the Administrator profile have privileges to perform administrative tasks, such as
creating and maintaining user accounts and access control levels, scenario management, and other tasks.
191
• Planner - Assignees of the Planner profile have privileges to perform tasks related to supply chain and scenario
management. They are likely to be:
o Logistics planners who are interested in optimum transportation options for inbound logistics
o Warehouse managers who make inventory placement decisions
o Sales and operations planners interested in inventory targets and service levels
Note: You can assign a profile to multiple users by clicking Settings > Profile Settings,
and clicking the Profile Users tab.
Perform the following steps to assign a profile to a user account:

2. Click User Profiles to open the User Profiles tab.
User Selector.
4. Click ADD to open the Profile Selector:
a. Select All or Name from the Search by: drop-down menu.
b. If you select All, a list of all profiles is displayed; click the desired profile name and click OK to close
the Profile Selector.
c. If you select Name, the Name field is displayed.
d. Enter the first few letters of the name and click Show. The Profiles list is populated with profile
names that start with the text you entered. If there are many profiles, you can page through the list
e. Click the desired profile name and click OK to close the Profile Selector.
she cannot view the changes you made until he or she logs out and signs in again.
Note: The RESET button in the User Profiles tab removes user-specific overrides for
privileges and preferences defined in the selected profile. For example, a user is
authorized to administer his own user account, and he overrides a preference that is set in
a profile assigned to him. Selecting the profile and clicking RESET removes the override,
and sets his preferences according as defined in the profile.
Related Topics:
192
MIPO
Note: The ability to add, modify, disable, copy and delete user accounts, and unassign
user preferences and privileges, is available only if you have administrative privileges, and
Note: You can unassign a profile for multiple users by clicking Settings > Profile
Settings, and clicking the Profile Users tab.
Perform the following steps to unassign a profile from a single user account:
2. Click User Profiles to open the User Profiles tab.
User Selector.
4. Click the name of the profile you want to remove in the Assigned Profiles list.
5. Click REMOVE.
Note: Although the changes you make to a user account by unassigning a profile are
effective immediately, if the user whose account you modified is signed in at the time you
saved the changes, he or she cannot view the profiles in the User Profiles tab until he or
she logs out and signs in again.
Note: The RESET button in the User Profiles tab removes user-specific overrides for
privileges and preferences defined in the selected profile. For example, a user is
authorized to administer his own user account, and he overrides a preference that is set in
a profile assigned to him. Selecting the profile and clicking RESET removes the override,
and sets his preferences according as defined in the profile.
Related Topics:
Assigning a Profile
193
Changing Profile Settings
Viewing and Editing Profile Settings
If you have administrative privileges, you can assign profiles that enable or prevent users from performing certain tasks. A
profile is a group of privileges and preferences. Three default profiles exist (but are not assigned by default):
• Administrator - Allows users to perform administrative tasks, such as creating and maintaining user accounts
and access control levels, scenario management, and other tasks.
• Planner - Allows users to perform tasks related to supply chain and scenario management. Users assigned
this profile are likely to be:
o Logistics planners who are interested in optimum transportation options for inbound logistics
o Warehouse managers who make inventory placement decisions
o Sales and operations planners interested in inventory targets and service levels
Perform the following steps to view profile information:

1. Click Settings > Profile Settings to open the Profile Settings window. The Profile Info tab is selected by
default.
2. Select a profile to view by clicking the Browse (...) button to open the Profile Selector:
3. The Profile Settings window is reloaded and the Profile Info tab contains the Name of the profile you selected
and Comments, if they exist.
4. If you want to change or add comments for this profile, enter them in the Comments field and click OK to save
your changes.
5. Click the Profile Users tab to change the users who are assignees of this profile. The Assigned Users field
lists of users who have been assigned the selected profile.
6. To assign the selected profile to an additional user, click ADD to open the User Selector:
User Selector.
that start with the text you entered. If there are many users, you can page through the list.
f. Click OK to assign the profile to the user you selected and to save your changes.
7. To unassign this profile for a user, select the user name in the Assigned Users list and click REMOVE. Click
OK to save your changes.
194
MIPO
8. Click the Profile Privileges tab to change the privileges specified in the selected profile:
a. Select the module associated with the privileges you want to modify by selecting an entry from the
b. Check or uncheck the check boxes for each privilege, to grant or deny the privilege, respectively.
Note: Click the checkbox next to the column heading labeled Privileges to select or
deselect all of the available privileges for the selected module.
Note: Privileges are hierarchical. For example, a user must have the privilege to
View/Manage Alerts before any subsequent privileges you select, such as View
Alerts or View alerts according to status, take effect. The different levels of the
hierarchy are denoted by level of indentation. Also note that assigning a high level, or
base, privilege does not mean that subsequent privileges are automatically selected
and assigned. Each privilege must be assigned individually.
d. Click OK to save your changes.

9. Click the Profile Preferences tab to change the preferences specified in the selected profile:
a. Select the module associated with the privileges you want to modify by selecting an entry from the
b. Check or uncheck the check boxes for each preference, to select or deselect the preference,
respectively.
Note: Although the changes you make to a user account by assigning a profile are
effective immediately, if the user whose account you modified is signed in at the time
you saved the changes, he or she cannot view the profiles you added or removed in the
User Profiles tab until he or she logs out and signs in again.
c. Click OK to save your changes.
Related Topics:
Creating a Profile
Duplicating a Profile
Deleting a Profile
Creating a Profile
Perform the following steps to create a profile:

1. Click Settings > Profile Settings to open the Profile Settings window. By default, the Profile Info tab opens.
2. Click TASKS > Create. The Profile Info tab contains empty text fields.
3. Enter appropriate text in the Name field.
4. Enter comments in the Comments field, if desired.
5. Click OK. The Profile Settings window is reloaded and displays a status message indicating that the profile
has been created. The profile name appears in the Profile Selector.
6. Specify the privileges and preferences for this profile and assign it to users, if desired.
Note: Although the changes you make to a user account by assigning a profile are effective
immediately, if the user whose account you modified is signed in at the time you saved the
changes, he or she cannot view the profiles you added or removed in the User Profiles tab
until he or she logs out and signs in again.
195
Related Topics:
Deleting a Profile
Note: When you duplicate a profile, all of the privilege and preference settings it contains
are copied to the new profile. However, when you duplicate a profile, it does not contain
information about the user accounts to which it was originally assigned. You must assign the
copied profile to users as appropriate.
Perform the following steps to duplicate a profile:

1. Click Settings > Profile Settings to open the Profile Settings window. By default, the Profile Info tab opens.
2. Select a profile to duplicate by clicking the Browse (...) button to open the Profile Selector:
4. Click TASKS > Duplicate. The Profile Settings window is reloaded and the Name field is now editable.
5. Enter a name for the new profile text in the Name field.
6. Enter comments in the Comments field, if desired.
7. Click OK. The Profile Settings window is reloaded and displays a status message indicating that the profile
has been created. The profile name appears in the Profile Selector.
8. Modify the privileges and preferences for this profile and assign it to users.
Note: Although the changes you make to a user account by assigning a profile are effective
immediately, if the user whose account you modified is signed in at the time you saved the
changes, he or she cannot view the profiles you added or removed in the User Profiles tab
until he or she logs out and signs in again.
Related Topics:
Creating a Profile
196
MIPO
Deleting a Profile
Deleting a Profile
Note: You cannot delete a profile that is currently assigned to users. You must first
unassign the profile from the user accounts.
Perform the following steps to delete a profile:
1. Click Settings > Profile Settings to open the Profile Settings window. The Profile Info tab is selected by
default.
2. Select a profile to delete by clicking the Browse (...) button to open the Profile Selector:
4. Click TASKS > Delete. A confirmation dialog prompts you to confirm this action.
5. Click OK to delete the profile. The Profile Settings window is reloaded and displays a status message
indicating that the profile has been deleted.
Related Topics:
Creating a Profile
Viewing Application Server Log Files

The Application Server Logs screen displays hyperlinks to log files stored on the application server. Use this screen to
download and view application server logs in a text editor on your local machine.
To view application server logs:
1. Select Settings > Application Server Logs. The Application Server Logs screen will appear, showing a list of
links to the most recent log files available on the application server.
197
2. If needed, click the Generate Thread Dump link to include additional server-related support information in the
log file.
3. Click on the log file you want to view. If you are prompted to select an application with which to open the file,
choose a text editor such as TextPad or NotePad.
Note: It's recommended that you delete application server log files on a weekly basis.
Managing MIPO Module Settings

Use the Manage Module Settings feature to define configuration parameters related to MIPO and other modules. The
following modules contain MIPO-specific settings:
• Alert Settings
• Analyze Scenarios
• Business Alerts
• Data Management
• Export Scenario
• Load Set Translator
• Multistage Inventory Planning and Optimization
• Network Visualization
• Processor Management
• Published Reports
• Publishing Queue
• Remote File Manager
• User Settings
Other modules that use Manage Module Settings feature for their configuration parameters include:
• Compare Scenario (Data Store)
• Analytics
• Data Store
• Demand Intelligence Module (DIM)
• Gateway Data Connector
• Gateway Data Loader
• Service Level Optimization (SLO)
• Supply Intelligence Module (SIM)
198
MIPO
Click on any of the links associated with the modules listed above to see specific setting details.
Viewing Processor Logs

The Processor Logs screen displays hyperlinks to log files stored on the MIPO application server. Use this screen to
download and view processor logs in a text editor on your local machine.
To view processor logs:
1. Select Settings > Processor Logs. The Processor Logs screen will appear, showing a list of links to the most
recent log files available on the MIPO application server.
2. Click on the log file you want to view. If you are prompted to select an application with which to open the file,
choose a text editor such as TextPad or NotePad.
Editing the smartops.properties file

The smartops.properties file controls several functions within the application. This Properties file is stored on the
application server. You can access the file via a hyperlink in the Manage Module Settings screen. When you click on the
smartops.properties link, the file will be downloaded from the server and opened in a text editor on your local machine.
You can then edit the file locally and upload it to the application server.
To edit the smartops.properties file:
1. Select Settings > Module Settings. The Manage Module Settings window will appear.
2. In the top right corner of the window, click on the smartops.properties link. If you are prompted to select an
application with which to open the file, choose a text editor such as TextPad or NotePad.
3. After editing the smartops.properties file, upload your changes to the appropriate directory on the application
server.
Note: In order to save changes to the smartops.properties file, you must have access to
the appropriate application server directory containing the original property file.
The application server must be restarted for your changes to take effect.
For details about the smartops.properties file and the behaviors it controls, refer to the Installation and Upgrade Guide.

Privileges, Profiles and Preferences control users' access to different modules and functionality.
Privileges are individual settings that enable or disable access to menu items and screens. They can be set for individual
users by an administrator, or by a user with privileges to administer accounts.
Profiles are standard groups of privileges that can be assigned to several users at once. Administrators create profiles,
assign privileges to the profile, and then assign the profile to multiple users. The application ships with three standard
profiles:
199
• Administrator -- Profile for administrator personnel. This profile allows a user to access and/or modify all
settings/data within the user interface.
• Planner -- Profile for planning personnel. This profile allows a user to access any supply chain/scenario that
they have permission to view and/or modify.
• Technical Support -- Profile for technical support personnel. This profile allows a user to view alerts, maintain
user accounts, view and maintain customer support settings, and view the log and property files. This profile
has no supply chain/scenario privileges.
Preferences allow users to customize settings related to Network Visualization, Data Management and delivery options
for different types of alerts. The applicationships with standard sets of preferences. Administrators (and users with the
privilege to administer their own accounts) can change these preferences.
How Privileges and Profiles interact

Privileges assigned to individual users override the profile settings assigned to that user. The table below shows what
would happen if Profile X was assigned to two users, A and B, and a specific privilege was then granted or denied to each
of the users.
Privilege Privilege Privilege

granted to granted to granted to
User A User B Profile X
Yes Yes Yes User A and B both have the privilege
Yes No Yes User A has the privilege, User B does not
No No Yes Neither user has the privilege
No Yes No User B has the privilege, User A does not
Note: Privileges in are hierarchical. A user must have the highest- level privileges, such
as View/Manage Alerts, before lower-level assignments such as View Alerts or View
Inactive Alerts can take effect.
• The hierarchy of privileges is shown in the level of indentation in the list below.
• Higher-level privileges don't automatically inherit privileges at lower levels.

Each privilege must be assigned individually.
• The diamond symbol ♦ denotes a parent privilege that must be selected to

enable all subsequent (indented) privileges in a given group. Note that some
parent privileges do nothing but enable lower-level privileges.
About Alert delivery and generation options:
You can think of alert delivery and generation as "push/pull" functions. Alerts can be pushed -- or delivered -- to a user in
two ways: via email or the Alerts screen. Alternatively, the record of an alert can be generated and saved in the database
but not delivered to the user. In the application, the two push options, "View Alerts" and "Email Alerts," are grouped under
the "Deliver Alerts" heading. The pull option, "Generate Alerts," can be enabled in addition to, or instead of, the delivery
options for any category of alert.
Users can set different delivery or generation preferences for each alert source (an alert source is a broad category of
functionality, like Data Loader or Scenario Analysis. All alerts use the following privilege settings:
200
MIPO
• Deliver Alerts privileges: This parent privilege enables lower-level delivery options for alerts. It has no effect
on the "Generate Alerts" privilege.
• View Alerts privileges: If this privilege is enabled, a user's View Alerts privileges will be activated. Users with
privileges to administer their own accounts can configure preferences for the alert sources and types that they
want to view in the Alerts screen. The application ships with some high-level screen-delivery preferences
enabled.
• Email Alerts privileges: If this privilege is enabled, the user's email alerts preferences will be activated. Note
that granting this privilege does not activate alert emails for a given alert source; instead, it actives email
preferences, all of which are turned off by default until a user enables them (this prevents users from receiving
dozens of alerts emails in all categories). Administrators (or users with privileges to administer accounts) must
use the preferences tab to choose email delivery options for selected alerts.
• Generate Alerts privileges: Select this option if you want to save a database record of alerts that have
occurred in this source group.
Related topics:
MIPO Preference Definitions
Assigning a Profile
Alert definitions

Click a link to see the list of privileges associated with the corresponding category:
Alert Settings
Analyze Scenarios
Business Alerts
Compare Scenario
Data Loader
Data Management
Export Scenario
Load Set Translator
Multistage Inventory Planning and Optimization
Network Visualization
201
Publishing Queue
Published Reports
Scenario Access Control
User Settings
Alert Settings privileges
Click a link below to see the definition corresponding to the associated privilege.
View / manage alerts
View alerts
View alerts according to status
View inactive alerts
Hide alerts
Suppress alerts
Analyze Scenarios privileges
Manage scenarios
Access review inventory targets
Access scenario-related alerts
Bulk delete any/all scenarios, regardless of user-scenario privilege
Optimize a scenario
View cost information
Delete a user scenario
Delete a user, base, or historical scenario
Create a new scenario
Access scenario access
Upgrade a scenario to a new supply chain
Upgrade a scenario into its parent supply chain
Validate a scenario
Business Alerts privileges
202
MIPO
Access Business Alerts module
Access Business Alerts
Modify Business Alerts
Compare Scenario privileges
Access Compare Scenario module
Data Loader privileges
Access the Import Data Set window
Access data loader alerts
Access SDLT installer
Data Management privileges
Access data management
Access data management alerts
Modify item, location, node, and path attributes
Modify attributes
Configure preference regarding display of base scenario message
Export Scenario privileges
Access to export module
Access to export alerts
Load Set Translator privileges
Access load set translator
Access load set translator alerts
203
Multistage Inventory Planning and Optimization privileges
Access validation and optimization
Access validation and optimization alerts
View BOM Data
View service level to cost report
Network Visualization privileges
View supply chain network diagrams
Processor Management privileges
Access processors
Access processor alerts
View processor logs
Publishing Queue privileges
Access Publishing Queue module
View other user publications
Cancel other user publishing submissions
Remove other user publications
Submit to Publishing Queue
Published Reports privileges
Access Published Reports window
Access publishing alerts
Publish reports
Access Published Reports
Access Aggregated TIP Report
204
MIPO
Access Data Loading Errors Report
Access Demand Processor Report
Access Items Master Data Report
Access Locations Master Data Report
Access Stocking Point Static Data Report
Access Stocking Point Time Varying Inputs Report
Access Comprehensive Stocking Point Output Report
Access Stocking Point TIP Report
Access Supply Chain Cost Details Report
Access Supply Chain Total Estimated Cost Report
Access Threshold Notification Report
Scenario Access Control privileges
Scenario Access Control privileges are dynamically generated when a scenario is created. For each scenario, two
privileges are possible: View scenario and Modify scenario. If a user creates a scenario and wants other users to access
it, a user with administrative privileges must grant access privileges for the scenario.
User Settings privileges
View / manage user and profile settings
Access user settings-related alerts
Manage user security settings
Enable/disable password security for any user
Enable or disable user accounts
Modify other user passwords
Administer own user account
Administer other user accounts
MIPO Preference Definitions

Click a link to see the list of preferences associated with the corresponding category:
Analyze Scenarios
Business Alerts
Data Loader
Data Management
Export Scenario
Load Set Translator
205
Multistage Inventory Planning and Optimization
Network Visualization
Published Reports
User Settings
Analyze Scenarios preferences
Click a link below to see the definition corresponding to the associated preference.
View Business Alerts Validation on Inputs Completed alerts
View Business Alerts Validation on Inputs Started alerts
View Business Alerts Validation on Outputs Started alerts
View Business Alerts Validation on Outputs Completed alerts
View Checked Exception in Scenarios alerts
View Optimization Completed alerts
View Optimization Started alerts
View Bias Adjustment alerts
View Gateway Data Loader Processor Maximum Number of Retries alerts
View Gateway Data Loader Processor SQL*Loader Error alerts
View Gateway Data Loader Processor Waiting to Process alerts
View Postprocessing Completed alerts
View Postprocessing Started alerts
View Processor Ended alerts
View Processor Failed alerts
View Processor Started alerts
View Report Generation Completed alerts
View Report Generation Started alerts
View Scenario Created alerts
View Scenario Deleted alerts
View Scenario Transition Cancelled alerts
View Scenario State Changed alerts
View Validation Completed alerts
View Validation Started alerts
Email Business Alerts Validation on Inputs Completed alerts
206
MIPO
Email Business Alerts Validation on Inputs Started alerts
Email Business Alerts Validation on Outputs Started alerts
Email Business Alerts Validation on Outputs Completed alerts
Email Checked Exception in Scenarios alerts
Email Optimization Completed alerts
Email Optimization Started alerts
Email Bias Adjustment alerts
Email Gateway Data Loader Processor Maximum Number of Retries alerts
Email Gateway Data Loader Processor SQL*Loader Error alerts
Email Gateway Data Loader Processor Waiting to Process alerts
Email Postprocessing Completed alerts
Email Postprocessing Started alerts
Email Processor Ended alerts
Email Processor Failed alerts
Email Processor Started alerts
Email Report Generation Completed alerts
Email Report Generation Started alerts
Email Scenario Created alerts
Email Scenario Deleted alerts
Email Scenario Transition Cancelled alerts
Email Scenario State Changed alerts
Email Validation Completed alerts
Email Validation Started alerts

Business Alerts preferences
View Comparison Scenario Missing Alerts
View Error Business Alerts
View Fatal Error Business Alerts
View Informational Business Alerts
View Warning Business Alerts
Email Comparison Scenario Missing Alerts
Email Error Business Alerts
Email Fatal Error Business Alerts
207
Email Informational Business Alerts
Email Warning Business Alerts

Data Loader preferences
View Data Loader Processor Ended alerts
View Data Loader Processor Failed alerts
View Data Loader Processor Info alerts
View Data Loader Processor Started alerts
View Data Loader Processor Warning alerts
View Data Set Dequeued alerts
View Data Set Enqueued alerts
View Data Set Moves Forward alerts
View Data Set Rejected alerts
View Data Set Formats Mismatched alerts
View Data Loading Complete alerts
View Data Set Rejected alerts
View Scenario Rename alerts
View Data Loading Started alerts
Email Data Loader Processor Ended alerts
Email Data Loader Processor Failed alerts
Email Data Loader Processor Info alerts
Email Data Loader Processor Started alerts
Email Data Loader Processor Warning alerts
Email Data Set Dequeued alerts
Email Data Set Enqueued alerts
Email Data Set Moves Forward alerts
Email Data Set Rejected alerts
Email Data Set Formats Mismatched alerts
Email Data Loading Complete alerts
Email Data Set Rejected alerts
Email Scenario Rename alerts
Email Data Loading Started alerts
208
MIPO
Management preferences
Display the message: You cannot edit the base scenario; you can only view the information.
Export Scenario preferences
View Scenario Export Failed alerts
View Scenario Export Started alerts
View Scenario Export Complete alerts
Email Scenario Export Failed alerts
Email Scenario Export Started alerts
Email Scenario Export Complete alerts

Load Set Translator preferences
View Translator Format Identified alerts
View Load Set Translator Setup Failure alerts
View Load Set Translator Resource Missing alerts
View Load Set Translation Failed alerts
View Translator Format Unrecognized alerts
Email Translator Format Identified alerts
Email Load Set Translator Setup Failure alerts
Email Load Set Translator Resource Missing alerts
Email Load Set Translation Failed alerts
Email Translator Format Unrecognized alerts

Multistage Inventory Planning and Optimization preferences
View First good output period > Analysis Horizon
View BOM Data Missing alerts
View BOM Mismatch alerts
View Undefined Customer Node alerts
View Customer Node Wrong Type alerts
209
View Customer Node has Outgoing Path alerts
View Invalid Data on Customer Path alerts
View Supply Paths Create Loop alerts
View Invalid Start Period alerts
View Missing Forecast Demand Data alerts
View Item-Location Duplicate alerts
View Stocking Point Missing Location alerts
View Empty Scenario alerts
View Holding Cost Zero alerts
View Inconsistent SKUs In BOM alerts
View Forecast Demand Mean and Std Dev Mismatch alerts
View Holding Cost Invalid alerts
View Invalid Service Level alerts
View Invalid Supply Ratio alerts
View Maximum Ship Life Exceeded alerts
View Minimum Process Quantity Too High alerts
View Missing On Hand alerts
View Yield Negative or Zero alerts
View On Hand Without Demand alerts
View Coefficient of Variation Too High alerts
View Stocking Points Missing Packaging Info alerts
View Path Missing Data alerts
View Path Has Resource alerts
View Replenishment Plan Infeasible alerts
View Undefined Process Point alerts
View Process Point Wrong Type alerts
View Process Point Downstream Error alerts
View Process Point Contains Multiple Resources alerts
View Process Point Upstream Error alerts
View Path Contains Invalid Data alerts
View Process Point Missing Resource alerts
View Process Point has Identical Items Upstream alerts
View Process Point Missing Static Data alerts
View Process Point Missing Time Varying Data alerts

210
MIPO
View Process Point Resource Error alerts
View PSLR Exceeds PBR alerts
View Resource Missing Forecast Data alerts
View Same SKUs In BOM alerts
View Service Time on Multiple Sourced Node alerts
View Resource Shared alerts
View Analysis Horizon Exceeds End Horizon alerts
View Undefined Stocking Point alerts
View Stocking Point Wrong Type alerts
View Stocking Point Downstream Error alerts
View Stocking Point Data Error alerts
View Stocking Point Upstream Error alerts
View Unit Cost Zero alerts
View Supplier Node Downstream Error alerts
View Supplier Node has Incoming Path alerts
View Undefined Supplier Node alerts
View Supplier Node Wrong Type alerts
View Invalid BOM Ratio alerts
Email BOM Data Missing alerts
Email BOM Mismatch alerts
Email Undefined Customer Node alerts
Email Customer Node Wrong Type alerts
Email Customer Node has Outgoing Path alerts
Email Invalid Data on Customer Path alerts
Email Supply Paths Create Loop alerts
Email Invalid Start Period alerts
Email Missing Forecast Demand Data alerts
Email Item-Location Duplicate alerts
Email Stocking Point Missing Location alerts
Email Empty Scenario alerts
Email Holding Cost Zero alerts
Email Inconsistent SKUs In BOM alerts
Email Forecast Demand Mean and Std Dev Mismatch alerts
Email Holding Cost Invalid alerts
211
Email Invalid Service Level alerts
Email Invalid Supply Ratio alerts
Email Maximum Ship Life Exceeded alerts
Email Minimum Process Quantity Too High alerts
Email Missing On Hand alerts
Email Yield Negative or Zero alerts
Email On Hand Without Demand alerts
Email Coefficient of Variation Too High alerts
Email Stocking Points Missing Packaging Info alerts
Email Path Missing Data alerts
Email Path Has Resource alerts
Email Replenishment Plan Infeasible alerts
Email Undefined Process Point alerts
Email Process Point Wrong Type alerts
Email Process Point Downstream Error alerts
Email Process Point Contains Multiple Resources alerts
Email Process Point Upstream Error alerts
Email Path Contains Invalid Data alerts
Email Process Point Missing Resource alerts
Email Process Point has Identical Items Upstream alerts
Email Process Point Missing Static Data alerts
Email Process Point Missing Time Varying Data alerts
Email Process Point Resource Error alerts
Email PSLR Exceeds PBR alerts
Email Resource Missing Forecast Data alerts
Email Same SKUs In BOM alerts
Email Service Time on Multiple Sourced Node alerts
Email Resource Shared alerts
Email Analysis Horizon Exceeds End Horizon alerts
Email Undefined Stocking Point alerts
Email Stocking Point Wrong Type alerts
Email Stocking Point Downstream Error alerts
Email Stocking Point Data Error alerts
Email Stocking Point Upstream Error alerts

212
MIPO
Email Unit Cost Zero alerts
Email Supplier Node Downstream Error alerts
Email Supplier Node has Incoming Path alerts
Email Undefined Supplier Node alerts
Email Supplier Node Wrong Type alerts
Email Invalid BOM Ratio alerts
Number of periods shown after the selected period
Number of periods shown before the selected period
Sort entries in selectors

Network Visualization preferences
Vertical distance between layers in a stage in the network diagram (in pixels)
Horizontal distance between nodes in a layer in the network diagram (in pixels)
Vertical distance between stages in the network diagram (in pixels)
Maximum number of nodes in a layer in the network diagram
Change horizontal and vertical orientation for the network diagram
Show customer nodes in the network diagram
Show node names in the network diagram
Show supplier nodes in the network diagram

Processor Management preferences
View Insufficient Historical Periods alerts
View Profile Not Found alerts
View User Already Associated alerts
View User Disabled alerts
View User Not Found alerts
View Schedule Attainment CV Capped alerts
View Schedule Attainment CV Default alerts
Email Insufficient Historical Periods alerts
Email Profile Not Found alerts
Email User Already Associated alerts
Email User Disabled alerts
213
Email User Not Found alerts
Email Schedule Attainment CV Capped alerts
Email Schedule Attainment CV Default alerts

Published Reports preferences
View Threshold Backlog Notification alerts
View Export Process Finished alerts
View Export Process Failed alerts
View Export Process Started alerts
View Threshold Notification alerts
Email Threshold Backlog Notification alerts
Email Export Process Finished alerts
Email Export Process Failed alerts
Email Export Process Started alerts
Email Threshold Notification alerts
Select Aggregated TIP file by default
Select Data Loading Error file by default
Select Demand Processor file by default
Select Items Master Data file by default
Select Locations Master Data file by default
Select Stocking Point Static Data file by default
Select Stocking Point Time Varying Inputs file by default
Select Comprehensive Stocking Point Output file by default
Select Stocking Point TIP file by default
Select Supply Chain Cost Details file by default
Select Supply Chain Total Estimated Cost file by default
Select Threshold Notification file by default
User Settings preferences
View Checked Exception Notify Admin alerts
View User Profiles Changed alerts
View Maximum Users Reached alerts

214
MIPO
View User Preferences Conflict alerts
View Checked Exception Notify Support alerts
View User Account Locked Out alerts
View User Preferences Changed alerts
View User Privileges Changed alerts
View User Accounts Changed alerts
View User Information Changed alerts
Email Checked Exception Notify Admin alerts
Email User Profiles Changed alerts
Email Maximum Users Reached alerts
Email User Preferences Conflict alerts
Email Checked Exception Notify Support alerts
Email User Account Locked Out alerts
Email User Preferences Changed alerts
Email User Privileges Changed alerts
Email User Accounts Changed alerts
Email User Information Changed alerts
Managing MIPO Settings

Module Settings
Managing MIPO Module Settings
Use the Manage Module Settings feature to define configuration parameters related to MIPO and other modules. The
following modules contain MIPO-specific settings:
• Alert Settings
• Analyze Scenarios
• Business Alerts
• Data Management
• Export Scenario
• Load Set Translator
• Network Visualization
• Processor Management
215
• Published Reports
• Publishing Queue
• Remote File Manager
• User Settings
Other modules that use Manage Module Settings feature for their configuration parameters include:
• Compare Scenario (Data Store)
• Analytics
• Data Store
• Demand Intelligence Module (DIM)
• Gateway Data Connector
• Gateway Data Loader
• Service Level Optimization (SLO)
• Supply Intelligence Module (SIM)
Click on any of the links associated with the modules listed above to see specific setting details.
Export module settings to Excel

The Manage Module Settings feature lets you export all module configurations to an Excel spreadsheet You can perform
this task by doing the following:
1. Log on to the application.
2. Select Module Settings under the Settings menu.
3. Click the EXPORT button.
4. A confirmation dialog box appears. Click OK.
The Excel application will start up and a spreadsheet will appear displaying the current module settings. Please note that
you may need to disable any pop-up blocking functionality associated with your browser in order to see the spreadsheet.
Alert Settings module settings

The Alert Settings module contains the configuration settings used by the application to connect to an email server for the
generation of email alerts. You can access this module by doing the following:
3. Select Alert Settings from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Alert Settings parameters.
5. When you are finished with your configuration, click OK.
216
MIPO
If you decide not to implement the changes you made, click Cancel.
A list of the parameters and their functions is provided below.
Parameter Description Require

Name Server
Restart?
SMTP Host The DNS name assigned to the alerts email server. No
Name
SMTP Password Administrative account password used to access the email server. No
SMTP User Administrative account user name used to access email server. No
Name
Related Topics:
Manage Module Settings feature
Export Module Settings to Excel
Analyze Scenario module settings

The Analyze Scenarios module contains the configuration settings used by the application to perform the Analyze
Scenario feature. You can access this module by doing the following:
3. Select Analyze Scenarios from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Analyze Scenarios parameters.
Parameter Description Require Server

Name Restart?
Automatically Automatically delete a historical scenario on upgrade to parent supply Yes

Delete Historical
Scenario on chain.
Upgrade
Related Topics:
217
Business Alerts module settings

The Business Alerts module contains the configuration settings used by the application to perform its Business Alerts
feature. You can access this module by doing the following:
3. Select Business Alerts from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Business Alert parameters.

Name Restart?
Consolidation Number of individual business alerts generated, per alert rule, after Yes
Threshold
which remaining alert instances are consolidated into a single alert.
Related Topics:
Data Loader module settings

The Data Loader module contains the configuration settings used by the Data Loader. You can access this module by
doing the following:
3. Select Data Loader from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Data Loader parameters.

Name Server
Restart?
Archive Directory Identifies the name of the archive directory on the application server Yes
218
MIPO
relative to the DataLoader directory.
Automatically Identifies whether to automatically rename existing scenario by appending No

Rename Existing the time-date stamp.
Scenario
Data Loader Defines the Data Loader translated format. Yes

Translated
Format
Entity File Defines the file extension of the Data Loader data files. Yes
Extensions
External Drop Identifies the name of the Oracle directory where the load set is Yes
Directory processed.
Listener Identifies the name of the Listener directory on the application server for Yes
Directory load sets.
Load Set Check Defines the sleep duration, in seconds, for the Data Loader service before Yes
Interval checking the DataLoader directory for load sets.
Reject Directory Identifies the name of the reject directory on the application server relative Yes
to the DataLoader directory.
SGLT Translated Defines the SGLT translated format. Yes

Format
Save Archived Identifies whether to save successful load sets on the application server. No
Load Sets
Save Rejected Identifies whether to save rejected load sets on the application server. NO
Load Sets
Related Topics:
Data Management module settings

The Data Management module contains the configuration settings used by the application to perform data management
functions. You can access this module by doing the following:
3. Select Data Management from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Data Management parameters.
219

Name Restart?
Audit Data Sets whether to audit data changes on editing of input values. Yes
Changes on
Inputs
Audit Data Sets whether to audit data changes on editing of output values. Yes
Changes on
Outputs
Currency Sets the currency code used to display currency values. Defaults to US No
Dollar.
Related Topics:
Export Scenario module settings

The Export Scenario module contains the configuration settings used by the application to perform the Export Scenario
function. You can access this module by doing the following:
3. Select Export Scenario from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Export Scenario parameters.

Name Restart?
Export Data Set Name of the ORACLE DIRECTORY that is associated with the instance. No
Oracle Directory
On the database, this directory must point to the location defined by the
Export Data Set Target Directory.
Export Data Set Directory where exported data sets are written. Yes
220
MIPO
Target Directory
Number of Number of threads to use when creating the exported .DAT files. Yes
Parallel Tasks
Related Topics:
Load Set Translator module settings

The Load Set Translator module contains the configuration settings used by the application to perform load set translation
3. Select Load Set Translator from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Load Set Translator parameters.

Name Server
Restart?
MIPO Default The default source format name for MIPO load sets. Yes
Source Load set
Format Name
MIPO Forced The forced source format name for MIPO load sets. If not defined, No
Source Load set
Format Name automatic format selection occurs.
MIPO Target The target format name for MIPO load sets. Yes
Load set Format
Name
MIPO Validate Whether to check that the incoming MIPO load set fits the default No
Source Load set
Format format. Do not use if all incoming load sets are GUARANTEED to be
formatted correctly.
MIPO Validate Whether to check that the translated MIPO load set equals the target Yes
Translated to
Target Format format.
SGLT Default The default source format name for SGLT load sets. Yes
Source Load set
221
Format Name
SGLT Forced The forced source format name for SGLT load sets. If not defined, Yes
Source Load set
Format Name automatic format selection occurs.
SGLT Target The target format name for SGLT load sets. Yes
Load set Format
Name
SGLT Validate Whether to check that the incoming SGLT load set fits the default Yes
Source Load set
Format format. Do not use if all incoming load sets are GUARANTEED to be
formatted correctly.
SGLT Validate Whether to check that the translated SGLT load set equals the target Yes
Translated to
Target Format format.
Related Topics:
Multistage Inventory Planning and Optimization module settings

The Multistage Inventory Planning and Optimization module contains the configuration settings used by the application to
perform validation and optimization functions. You can access this module by doing the following:
3. Select Multistage Inventory Planning and Optimization from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Remote File Manager parameters.
Certain parameters, as indicated, require you to stop and restart the application server for your changes to take effect.
Clients connected to the system must stop and restart the application for the changes to take effect.
Parameter Description Requires Server

Name Restart?
Alerts Limit Consolidate alerts of a specific type upon reaching this limit. No
Optimize Memory Use this property to reduce the memory footprint of the validation No
Space During phase. Consider that optimizing for space is going to have an impact
222
MIPO
Validation on the execution speed.
Number of Number of workers that will be computing networks. Typically it should No

Computational be set to the number of CPUs the computer is running on or twice as
Threads much if readers are not threaded. Leave empty for letting MIPO
decide.
Recycle Workers This value triggers when to start reusing echelon workers when a No
Threshold thread for computing a network dies because there are no more
networks to compute. Since this workers do a pure computational work
typically this value should be set to the number of CPUs. With values
of 1 or less it will avoid recycling workers. Leave empty for letting
MIPO decide.
Number of Number parallel networks that will be read concurrently. Empty for No
Parallel Network letting MIPO decide.
Readers.
Maximum Queue Maximum size of the queue that feeds the computation processes. No
Size between
Readers and
Computation
Processes
Database Number of records retrieved from the database at a time. No

Reading Fetch
Size
Maximum Queue Maximum size of the queue that feeds the persistence processes. No
Size between
Computation
Processes and
Writers
Persistence Size of the batches submitted to the database for persistence. No

Batch Size
Number of Number of parallel writers for each writing group. No

Writers
Database Commit Frequency of commits based on number of batches submitted. Leave No

Frequency empty for not committing until the end of computation.
Alert Demand CV Generate an alert if a demand has a coefficient of variation which is No

Level above this level.
Sum of Incoming The sum of supply ratios on incoming arcs to a stocking point must be No
Supply Ratios one. MIPO validates this but allows a tolerance for it.
Tolerance Limit
Internal Service Any internal service level above this limit gets capped to this value. No
Level Upper Limit
Fill Rate to Non- Service levels which are above this limit get capped to this value. No
stockout Service
Level Conversion
Upper Limit
223
Service Level Service levels which are below this limit get capped to this value. No
Lower Limit
Log Validation Set to yes in order to include Validation Events in the log file. No
Events
Echelon Workers With this parameter the application can be tuned to create this number No
Initial Count of threads per network worker. This is helpful for those configurations
where the number of networks is small because everything is
interrelated and if the networks are broad (many nodes per echelon). It
is still preferable to thread using Task Count because loading will get
threaded as well. Do not use this parameter in favor of letting the
application balance itself using Recycle Workers Threshold.
Batch Size The upper iteration limit that is done for batch sizes. No
Iteration Upper
Limit
Dead Inventory Threshold for the difference between consecutive TIPs for truncating No
Stochastic TIP stochastic orders upstream due to dead inventory.
Threshold
Assembly Service Assembly service level trigger. When the service level of an out-bin No
Level Trigger node is below this value the service level is artificially pulled up.
Assembly Service Amount by which the service level for an out-bin node is pulled up No
Level Pull Up whenever the service level exceeds the trigger value.
Service Level Service level lambda upper limit value. No

Lambda Upper
Limit
Service Level The maximum value between searched lambdas in a golden search. No
Golden Searched
Lambdas Upper
Limit
Service Level The maximum number of iterations to perform during a golden search. No
Golden Search
Upper Limit
Writing Strategy Strategy used for persisting output data. No
Strategy for How writers will be grouped together into a single session. No
Grouping Writers
Gamma CV CV threshold for customer-facing nodes to use gamma distribution. No

Threshold for
Customer-facing
Nodes
Gamma CV CV threshold for internal (non-customer-facing) nodes to use gamma No

Threshold for distribution.
Internal Nodes
224
MIPO
Loss-free Service For service levels equal to or greater than this value, lost sales No
Level percentage will be zero if Lost Sales Model is set to Proportional.
Depletion Model Model for computing depletion; can either be Continuous or Instant. No
Inventory Sets policy to be used for calculating TIP; either Priority or Divide. No
Allocation Policy Represents the default value for a stocking point that does not have a
value specified for its inventory allocation policy.
Include Lead Sets whether or not to include lead time variability in the shifting of No
Time Variability in safety stock.
Safety Stock
Shifting
Demand Defines the number of standard deviations used to determine if No

Initialization initialization demand is an outlier.
Outlier Multiplier
MIPO Progress Defines the time (in seconds) between recurring progress check No
Update Interval intervals.
First MIPO Sets the calculation factor used by the MIPO progress monitor to No
Progress indicate when the first alert would be generated.
Threshold
Second MIPO Sets the calculation factor used by the MIPO progress monitor to No
Progress indicate when the second alert would be generated.
Threshold
Service Levels for A read-only setting that identifies the service levels, as comma- No
Sensitivity separated values, used in cost calculations.
Priority Level Caps the priority level output in a period to a percentage of the on No
Percentage Cap hand inventory in that period. The default is 100 percent.
Maximum Nodes This is the maximum number of nodes that will be merged together Yes
per Cluster before starting the next network cluster. The default is 2,000 nodes.
Small Network This is the largest network size, in nodes, to be a candidate for Yes
Size merging with another network. The default is 500 nodes.
Calculate Specifies the approach used to calculate the holding cost ratio at a No
Inventory Holding node with multiple downstream nodes, either average (default),
Cost Ratio minimum, or maximum.
Related Topics:
Network Visualization module settings

The Network Visualization module contains the configuration settings used by the application to perform its network
visualization functions. You can access this module by doing the following:
225
3. Select Network Visualization from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Network Visualization parameters.

Name Restart?
Retrieve Data Controls retrieval of additional data for Network Visualization applet. Yes
Default = true
Related Topics:
Processor Management module settings

The Processor Management module contains the configuration settings used by the application to perform processor
management functions. You can access this module by doing the following:
3. Select Processor Management from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Processor Management parameters.

Name Restart?
Demand Node This is the demand node naming convention which is appended to Yes
Creation Naming created
Convention
nodes from the demand node creation processor.
Gateway Data The check interval in minutes between continuing execution of the Yes
Loader -
Continue Load Gateway Data Loader Processor while a load set is being processed in
set Check Gateway.
226
MIPO
Interval
Gateway Data Where the gateway database resides for the Gateway Data Loading Yes
Loader -
Gateway Processor.
Database
Gateway Data The gateway schema password for the Gateway Data Loading Yes
Loader - Processor.
Gateway
Schema -
Password
Gateway Data The gateway schema user name for the Gateway Data Loading Yes
Loader - Processor.
Gateway
Schema - User
name
Gateway Data The maximum number of checks to continue execution of the Gateway Yes
Loader - Data
Maximum Load
set Check Loading Processor of a load set before it is canceled.
Intervals
Gateway Data Gateway Data Loader SQL*Loader Application used for populating the Yes
Loader -
SQL*Loader staging tables prior to calling Gateway.
Application
Inherit Scenario Determines whether to inherit scenario user access for SLO and DIM. Yes
User Access Defaults to Yes.
Lead Time CV Maximum CV for lead time. Yes

Cap
Lead Time Whether to exclude outliers? Yes

Exclude Outliers
Lead Time Lead time historical data horizon to use for CV computation. If not Yes
Historical Data
Horizon found, it defaults to the scenario historical data horizon. Caps at the
scenario
historical data horizon.
Lead Time Min Minimum number of historical observations required to carry on CV Yes
Data Point Count
calculation.
Lead Time Order Maximum value for order processing time mean on a supply path. Infinity Yes
Processing Mean
Cap if not found.
Lead Time Number of standard deviations used to identify outliers. Yes

Outlier Multiplier
227
Lead Time Maximum value for physical lead time on a supply path. Infinity if not Yes
Physical Mean
Cap found.
Lead Time Raw Determine whether to generate the raw input log file. Set it to 'true' Yes
Data Log
to enable raw input log generation.
New Item - Determines whether aggregation of sales forecast data is enabled in the Yes
Aggregate Sales New Item processor. Defaults to No.
Forecast Data
New Item - Determines whether logging is available in the New Item processor. Yes
Logging
Node This is the type of node that should be marked for trimming. Yes
Identification
Input Node Type
Node This is the node naming convention based on which the nodes are Yes
Identification marked
Naming
Convention for trimming.
Node This is the type of node that the identified nodes should be converted Yes
Identification
Output Node to.
Type
Number of Days Number of Days of Processor Log Files to be left out, before deleting Yes
before Processor
Log Files Logs.
Deletion
Processor Log Directory where processor log files are stored. Yes
Directory
Review Inventory Key output minimum percent change to load during report generation. No
Targets - Percent
Change
Minimum
Supply CV Cap Maximum CV for supply time. Yes
Supply CV Default CV to use if there is not enough data to compute it. Yes
Default
Supply Exclude Whether to exclude outliers? Yes

Outliers
Supply Generate Whether to generate detailed log? Yes

Detail Log
Supply Loss Default loss value if there is not enough data to compute it. Yes
Default
228
MIPO
Supply MAPE MAPE to use if calculation gives an infinity value for MAPE (division Yes
Ceiling
by zero).
Supply Minimum Minimum samples to make a meaningful analysis, otherwise we use Yes
Number of
Samples Count defaults.
Supply Outlier Criteria for identifying outliers as a multiplier of the STD. Yes
Multiplier
Unit Cost Determines the type of BOM calculation which occurs in the unit cost Yes
Calculator - BOM
Calculation calculator processor.
Unit Cost Determines the cost function to be used by the Unit Cost Calculator Yes
Calculator - Cost processor.
Function
Unit Cost Determines whether logging is enabled in the unit cost calculator Yes
Calculator -
Logging processor.
Related Topics:
Published Reports module settings

The Published Reports module contains the configuration settings used by MIPO to perform published reporting functions.
You can access this module by doing the following:
1. Log on to the MIPO application.
3. Select Published Reports from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Published Reports parameters.

Name Server
Restart?
Aggregate Tip: Defines Aggregate Pattern value for the Aggregated TIP outputs report. Yes
Aggregate
Pattern
229
Aggregate Tip: Defines End Offset value for the Aggregated TIP outputs report. Yes
End Offset
Aggregated Tip: Indicates whether to include safety stock in the Aggregated TIP outputs Yes
Include Safety report. Values = Yes, No.
Stock
Aggregate Tip: Defines Offset Units value for the Aggregated TIP outputs report. Yes
Offset Units
Aggregate Tip: Defines Start Offset value for the Aggregated TIP outputs report. Yes
Start Offset
Compare Defines the target directory for the Compare Scenario report. Default value Yes
Scenario Target = publications.
Directory
Delete Scenario Indicates whether to delete scenario published reports? Default value = Yes
Published Yes.
Reports
Filename: User-defined file name for the Aggregated TIP report. Default value = Yes
Aggregated Tip AggregatedTIPOBI.
Filename: User-defined file name for the Data Loading Errors report. Default value = Yes
Dataload Error DataLoadErrorMDF.
Filename: User-defined file name for the Demand Processor report. Default value = Yes
Demand DemandProcessorMDF.
Processor
Filename: User-defined file name for the Generate OBI report. Default value = Yes
Generate OBI GenerateOBI.
Filename: Item User-defined file name for the Items Master Data report. Default value = Yes
Master ItemsMasterDataMDF.
Filename: User-defined file name for the Locations Master Data report. Default value Yes
Location Master = LocationsMasterDataMDF.
Filename: User-defined file name for the Inventory Movement report. Default value = Yes
Movement InventoryMovementMDF.
Filename: SKU User-defined file name for the Stocking Point Static Data report. Default Yes
Input Output value = SKUsStaticDataMDF.
Static
Filename: SKU User-defined file name for the Stocking Point Time Varying Inputs report. Yes
Input Time Default value = SKUsTimeVaryingInputsDataMDF.
Varying
Filename: User-defined file name for the Comprehensive Stocking Point Output Yes
Stocking Point report. Default value = StockingPointOutputMDF.
Output
230
MIPO
Filename: User-defined file name for the Stocking Point TIP report. Default value = Yes
Stocking Point StockingPointTipOBI.
Tip
Filename: Supply User-defined file name for the Supply Chain Cost Details report. Default Yes
Chain Cost value = SupplyChainCostDetailsMDF.
Details
Filename: Supply User-defined file name for the Supply Chain Total Estimated Cost report. Yes
Chain Total Default value = SupplyChainTotalEstimatedCostMDF.
Estimated Cost
Filename: User-defined file name for the Threshold Notification report. Default value Yes
Threshold = ThresholdNotificationOBI.
Notification
Generate OBI Generate OBI attribute. Yes

Attribute
Header Name: Header for stocking point base section publish type. Default value = Yes
Comprehensive StockingPoint, ForecastPeriod.
Stocking Point -
Base Section
Header Name: Header for stocking point cost section publish type. Default value = Yes
Comprehensive ,AIPCosts, Safety Stock Costs, Avg Cycle Stock Costs, Prebuild Stock
Stocking Point - Costs, Merchandise Stock Costs, Avg Onhand Stock Costs, Avg Physical
Cost Section Pipeline Stock Costs, Forecast Demand Mean Costs, Backlog Safety
Stock Costs.
Header Name: Header for stocking point period section publish type. Default value = Yes
Comprehensive Onhand Stock Periods, Safety Stock Periods.
Stocking Point -
Period Section
Header Name: Header for stocking point unit section publish type. Default value = TIP Yes
Comprehensive Units, Safety Stock Units, Cycle Stock Units, Prebuild Stock Units,
Stocking Point - Merchandise Stock Units, Onhand Stock Units, Physical Pipeline Stock
Unit Section Units, Target Pipeline Stock Units, Unshifted Safety Stock Units, Service
Time Tip Units, Forecast Demand Mean, Forecast Std Dev, AIP Units, Avg
Cycle Stock Units, Avg Onhand Stock Units, Avg Physical Pipeline Stock
Units, Backlog Safety Stock Units.
Header Name: Header for data loader error records publish type. Default value = Package Yes
Data Loader Name, Procedure Name, Error Date/Time, Error Reason.
Error Records
Header Name: Header for data loader reject records publish type. Default value = Yes
Data Loader Interface Name, Rejection Reason, Rejection Date/Time, Rejection
Reject Records Information.
Header Name: Header for demand processor publish type. Default value = SKU, Item, Yes
Demand Loc, Bias Ratio, MAPE, CV, Risk Pool Factor, Generated By.
Processor
Header Name: Header for Item Master publish type. Default value = Item, Desc, UOM, Yes
Item Master Creation Date, Last Modified Date.
231
Header Name: Header for Location Master publish type. Default value = Loc, Desc, Yes
Location Master Creation Date, Contains Stocking Points, Contains Plants.
Header Name: Header for Movement publish type. Default value = Item, Source, Dest, Yes
Movement Week, Qty, Src Fraction, Lead time, Lead time Error, Batch Multiple.
Header Name: Header for sku input output static publish type. Default value = SKU, Item, Yes
SKU Input Location, Week, Max Ship Life, Frz Dur, Avg SS Cov ,Is Cust Facing,
Output Static Creation Date, Last Modified Date, Max OH Capacity, SS Cov Dur,
Holding Cost, Std Cost, Desired Service Level, Sched Attain Mean, Sched
Attain Std Dev.
SKU Input Time Header for SKU Input Time Varying publish type. Default value = SKU, Yes
Varying Item, Loc, Week, Risk Pool Factor, Demand Forecast, Demand Error.
Preprocessor
Safety Stock Header for safety stock coverage publish type. Default value = OBI_SKU, Yes
Coverage OBI_LOCATION, OBI_SS_COVERAGE.
Publish Factory: Publish task factory. Default value = Yes

Task com.smartops.publisher.tasks.MasterPublishTaskFactory.
Publish Factory: Publish type factory. Default value = Yes

Type com.smartops.publisher.types.MasterPublishTypeFactory.
Publisher Target Publisher target directory. Default value = publications. Yes

Directory
Publisher Work Publisher work queue maximum size. Default value = 30. Yes
Queue Maximum
Size
Report Format: Format date format. Default value = MM/dd/yy. Yes

Date Format
Report Format: Format decimal precision. Default value = 2. Yes

Decimal
Precision
Report Format: Format end of set. Default value = END_OF_SET. Yes

End of Set Tag
Report Format: Format field separator. Default value = ,. Yes

Field Separator
Report Format: Format MDF file extension. Default value = csv. Yes
MDF File
Extension
Report Format: Format OBI file extension. Default value = txt. Yes
OBI File
Extension
Report Format: Format suffix format. Default value = yyyyMMddHHmmss. Yes
232
MIPO
Suffix Format
Report Format: Format suffix in GMT. Yes

Suffix in GMT
Report Format: Format timestamp format. Default value = MM/dd/yy HH:mm:ss. Yes
Timestamp
Format
Service Level Sets the decimal precision used for service level values in all Compare Yes
Decimal Scenario reports.
Precision
Stocking Point User-defined End offset value for the Comprehensive Stocking Point Yes
Output: End Output report.
Offset
Stocking Point User-defined Node attributes value for the Comprehensive Stocking Point Yes
Output: Node Output report.
Attributes
Stocking Point User-defined Offset units value for the Comprehensive Stocking Point Yes
Output: Offset Output report.
Units
Stocking Point User-defined Output type value for the Comprehensive Stocking Point Yes
Output: Output Output report.
Type
Stocking Point User-defined Start offset value for the Comprehensive Stocking Point Yes
Output: Start Output report.
Offset
Supply Chain User-defined End offset value for the Supply Chain Cost Details report. Yes
Cost Details: End
Offset
Supply Chain User-defined Node attributes value for the Supply Chain Cost Details Yes
Cost Details: report.
Node Attributes
Supply Chain User-defined Offset units value for the Supply Chain Cost Details report. Yes
Cost Details:
Offset Units
Supply Chain User-defined Start offset value for the Supply Chain Cost Details report. Yes
Cost Details:
Start Offset
Supply Chain User-defined End offset value for the Supply Chain Cost Details report. Yes
Total Estimated
Cost: End Offset
Supply Chain User-defined Node attributes value for the Supply Chain Cost Details Yes
Total Estimated report.
Cost: Node
233
Attributes
Supply Chain User-defined Offset units value for the Supply Chain Cost Details report. Yes
Total Estimated
Cost: Offset
Units
Supply Chain User-defined Start offset value for the Supply Chain Cosst Details report. Yes
Total Estimated
Cost: Start Offset
Threshold User-defined Location attributes value for the Threshold Notification report Yes
Notification:
Location
Attributes
Write MDF Sets whether or not to write MDF headers to the MDF reports. Default Yes
Headers value = Yes.
Write OBI Sets whether or not to write OBI headers to the OBI reports. Default value = Yes
Headers Yes.
Related Topics:
Publishing Queue module settings

The Publishing Queue module contains the configuration settings used by the application to perform publishing queue
3. Select Publishing Queue from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Publishing Queue parameters.

Name Restart?
Maximum Number of concurrent reports running. Yes

Number of
Concurrent
Reports
Maximum Maximum number of elements queued for execution. The queue will Yes
Number of block
Elements
234
MIPO
Queued until the queue is drained.
Related Topics:
Remote File Manager module settings

The Remote File Manager module contains the configuration settings used by the application to perform remote file
management functions. You can access this module by doing the following:
3. Select Remote File Manager from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Remote File Manager parameters.

Name Restart?
Import Server - Provider to handle connection protocol for the Import Server. Possible No
Basic
Configuration - Values: Local, SSH, FTP.
Protocol Provider
Import Server - Default directory to use for relative paths on the Import Server. No
Basic
Configuration -
Default Remote
Directory
Import Server - Remote SSH server to connect to for Import Server. No

SSH
Configuration -
Server Name
Import Server - SSH Server port to use for Import Server. The default SSH port is 22. No
SSH
Configuration -
Server Port
Import Server - Remote user name on SSH server for Import Server. No
SSH
Configuration -
Username
Import Server - Remote password to use for authenticating to Import Server using SSH. No
SSH
Configuration -
235
Password This password is not required if an identify file is used.
Import Server - SSH identity file to use for authenticating to the Import Server. The No
SSH
Configuration - default value is ~/.ssh/id_dsa. ~ gets expanded to the home directory of
Identity File the user
running this server.
Import Server - Passphrase for SSH identity file for authenticating to the Import Server. No
SSH
Configuration - It is not required if you are using password to connect or if the identity file
Passphrase for does
Identity File
not have a passphrase.
Import Server - Known hosts file that contains the signature for Import Server. The No
SSH
Configuration - default value is ~/.ssh/known_hosts. ~ gets expanded to the home
Known Hosts directory of the user
File
running this server.
Import Server - Remote FTP server to connect to for Import Server. No

FTP
Configuration -
Server Name
Import Server - FTP Server port to use for Import Server. The default FTP port is 21. No
FTP
Configuration -
Server Port
Import Server - Remote FTP server to connect to for Import Server. No

FTP
Configuration -
Username
Import Server - Remote password to use for authenticating to Import Server using FTP. No
FTP
Configuration -
Password
Import Server - FTP Transfer mode to Import Server. Possible Values: Passive, Active. No
FTP
Configuration -
Transfer mode
Export Server - Provider to handle connection protocol for the Export Server. Possible No
Basic
Configuration - Values: Local, SSH, FTP.
Protocol Provider
Export Server - Default directory to use for relative paths on the Export Server. No
Basic
Configuration -
Default Remote
Directory
236
MIPO
Export Server - Name of the remote SSH server used with Export Server connectivity. No
SSH
Configuration -
Server Name
Export Server - SSH Server port used with Export Server connectivity - the default SSH No
SSH port is 22.
Configuration -
Server Port
Export Server - Administrative account user name for remote SSH server used with No
SSH Export Server
Configuration -
Username connectivity.
Export Server - Administrative account password for remote SSH server used for No
SSH authenticating to
Configuration -
Password Export Server using SSH - this password is not required if an identify file
is used.
Export Server - SSH identity file to use for authenticating to the Export Server. The No
SSH default value is
Configuration -
Identity File ~/.ssh/id_dsa. ~ gets expanded to the home directory of the user running
this server.
Export Server - Passphrase for SSH identity file for authenticating to the Export Server. It No
SSH is not
Configuration -
Passphrase for required if you are using password to connect or if the identity file does
Identity File. not have a
passphrase.
Export Server - Known hosts file that contains the signature for Export Server. The No
SSH default value is
Configuration -
Known Hosts ~/.ssh/known_hosts. ~ gets expanded to the home directory of the user
File running this
server.
Export Server - Name of the remote FTP server used with Export Server connectivity. No
FTP
Configuration -
Server Name
Export Server - FTP Server port to use for Export Server. The default FTP port is 21. No
FTP
Configuration -
Server Port
Export Server - Administrative account user name for remote FTP server used with No
FTP Export Server
Configuration -
Export Server - Administrative account password for remote FTP server used with Export No
FTP
237
Configuration - Server
Password
connectivity.
Export Server - FTP Transfer mode to Export Server. Possible Values: Passive, Active. No
FTP
Configuration -
Transfer Mode
Gateway Server Provider to handle connection protocol for the Gateway Server. Possible No
- Basic
Configuration - Values: Local, SSH.
Protocol Provider
Gateway Server Default directory to use for relative paths on the Gateway Server. No
- Basic
Configuration -
Default Remote
Directory
Gateway Server Name of the remote SSH server used with Gateway Server connectivity. No
- SSH
Configuration -
Server Name
Gateway Server SSH Server port used with Gateway Server connectivity - the default No
- SSH SSH port is 22.
Configuration -
Server Port
Gateway Server Administrative account user name for remote SSH server used with No
- SSH Gateway Server
Configuration -
Gateway Server Administrative account password for remote SSH server used for No
- SSH authenticating to
Configuration -
Password Gateway Server using SSH - this password is not required if an identify
file is used.
Gateway Server SSH identity file to use for authenticating to the Gateway Server. The No
- SSH default value
Configuration -
Identity File is ~/.ssh/id_dsa. ~ gets expanded to the home directory of the user
running this
server.
Gateway Server Passphrase for SSH identity file for authenticating to the Gateway No
- SSH Server. It is not
Configuration -
Passphrase for required if you are using password to connect or if the identity file does
Identity File. not have a
passphrase.
Gateway Server Known hosts file that contains the signature for Gateway Server. The No
- SSH
238
MIPO
Configuration - default value is

Known Hosts
File ~/.ssh/known_hosts. ~ gets expanded to the home directory of the user
running this
server.
SSH- Default Sets the default permissions for database directories created by the No
Directory Remote File Manager. The default octal value is 755.
Permissions
SSH - Default Sets the default permissions for database files created by the Remote File No
File Permissions Manager. The default octal value is 644.
Related Topics:
User Settings module settings

The User Settings module lets you define the default security parameters associated with user accounts. You can access
this module by doing the following:
3. Select User Settings from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Alert Settings parameters.

Name Restart?
Account Lockout Number of consecutive login failures which will cause the user No
Threshold account to be locked. Set to zero to disable lockout. Defaults to zero
(0).
Default Date Date format that is initially selected when a new user is created. No
Format Defaults to MM/DD/YYYY.
Default Decimal Decimal format that is initially selected when a new user is created. No
Notation Defaults to 1,234.56.
Default Language that is initially selected when a new user is created. No

Language Defaults to English.
239
Default Time Time format that is initially selected when a new user is created. No
Format Defaults to HH:MM AM/PM Z.
Initial Password Indicates whether a user must reset their password upon first login. No
Reset Defaults to No.
Password Number of days before a user password expires. Set to zero to No

Expiration disable password expiration. Defaults to zero (0).
Password Number of previous passwords to track. Set to zero to disable No

History password history. Defaults to zero (0).
Security Audit Indicates whether alerts are generated for login and logout. Defaults No
to No.
User Session Number of seconds before a user session is terminated due to No

Timeout inactivity. Defaults to 3.600.
(Seconds)
Minimum Minimum character length of a user password. Defaults to five (5). No

Password
Length
Minimum Upper Minimum number of English upper case letters that must be used a No
Case Letters user password. Defaults to zero (0).
Minimum Lower Minimum number of English lower case letters that must be used a No
Case Letters user password. Defaults to zero (0).
Minimum Minimum number of Westernized Arabic numerals that must be used No

Numerals a user password. Defaults to zero (0).
Minimum Minimum number of non-Alphanumeric (special characters) that must No

Special be used a user password. Defaults to zero (0).
Characters
Related Topics:
Scenario Settings
Managing MIPO Scenario Settings
Use the Manage Scenario Settings feature to define default scenario parameters related to MIPO and other modules.
The following modules contain MIPO-specific settings:
Other modules that use the Manage Scenario Settings feature for their configuration parameters include:
• Data Store
240
MIPO
• Demand Intelligence
• Service Level Optimization
Click on any of the links associated with the modules listed above to see specific scenario setting details.
Export scenario settings to Excel

The Manage Scenario Settings feature lets you export all scenario configurations to an Excel spreadsheet You can
perform this task by doing the following:
2. Select Scenario Settings under the Settings menu.
3. Click the EXPORT button.
4. A confirmation dialog box appears. Click OK.
The Excel application will start up and a spreadsheet will appear displaying the current scenario settings. Please note that
you may need to disable any pop-up blocking functionality associated with your browser in order to see the spreadsheet.
Multistage Inventory Planning and Optimization scenario settings

The Multistage Inventory Planning and Optimization module contains the scenario settings used by the application as
default parameters for any setting not defined in the data set. You can access this module by doing the following:
3. Select Multistage Inventory Planning and Optimization from the dropdown list.
4. Scroll through the configuration list and update any parameter to change its default setting.
Parameter Name Description
Adjust for Bias Enables MIPO to apply DIM-calculated bias adjustment to either the scenario
safety stock, forecast, or not apply them at all .
Analysis Horizon Defines the number of periods beyond the start/base period (future data) required
for accurate MIPO results.
Business Alerts On Inputs Stop Sets the severity level needed to shut down the input validation process
Severity
Business Alerts On Outputs Sets the severity level needed to shut down the output validation process.
Stop Severity
Data Horizon Defines the number of periods of data available for optimization.
241
Demand Timing Uncertainty Select Consider when using DIM outputs for MIPO scenarios with intermittent
demand streams.
Distribution Type Select Gamma distribution to improve the accuracy of inventory target for items
with lumpy demand, items with intermittent demand, or slow-moving items.
Forecast Source Defines the source for first-period forecast data during non-stocking node handling.
Historical Data Horizon Defines the amount of historical data available for creating a timeline.
Initialization Determines whether the user specifies on hand inventory targets, or the application
automatically calculates those values.
Lead Time Error Multiplier Defines the weight the application gives to standard deviation of lead time during
computation.
Lost Sales Model Defines the model the application uses to compute lost sales: Proportional or
Constant.
Multisourced Trimming Rule Defines whether to enable the multisourced trimming rule: Enable (default) or
Disable.
Order Delivery with Lead Time Defines whether the application considers order crossover (default), ignores it (in
Uncertainty favor of the sequential model), or uses a less comprehensive model.
Service Level Defines how the application calculates the probability that demand is met from
stock: either Fill Rate or Non-stockout Probability.
Storage Capacity Constraints Defines how to use storage capacity limitations during optimization, based on the
Storage Penalty Option and Storage Penalty Cost: either Ignore or Consider.
Storage Penalty Cost The cost of adding a new storage location. If the field is blank, cost is assumed to
be very expensive.
Storage Penalty Option Defines what type of optimization approach to use: either Minimize Impact (new
fixed-cost storage location, like a storage tank) or Minimize Cost (new variable-cost
storage location, like warehouse space).
Transfer Demand Processor Select Yes to transfer scenario demand processor outputs to Data Store
Outputs
Transfer Forecast Select Yes to transfer scenario forecast data to Data Store.
Transfer Process Points Select Yes to transfer scenario process point data to Data Store.
Transfer Sales Select Yes to transfer scenario sales data to Data Store.
Transfer Stocking Points Enables transfer of scenario stocking point data to Data Store.
Transfer Supply Paths Enables transfer of MIPO scenario supply path data to Data Store.
Related Topics:
Manage Scenario Settings feature
Export Scenario Settings to Excel
242
Analytics
Welcome to Analytics
The purpose of Analytics is to provide enhanced analysis of solutions data, results and alerts. The content of Analytics
consists of
charts, reports.
For more information about Analytics, see the SAP Enterprise Inventory and Service-Level Optimization: Analytics User
Guide.
Administration
Analytics Privilege Definitions
Access the Analytics module
Configure Analytics
Analytics module settings

The Analytics module contains the configuration settings used by the Analytics utility to its functions. You can access this
module by doing the following:
1. Log on to the Dashboard application.
3. Select Analytics from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Analytics parameters.
Content Display Specifies whether Analytics content is displayed in the frame of the
main window or pop-up.
Link Link can point to a URL, a local HTML file, or a JavaScript file.
243
Link Type Link type is either HTML, URL, or JavaScript.
Related Topics:
244
Data Gateway
Welcome to Data Gateway
The Data Gateway allows you to easily integrate business data in your supply chain source systems with your SAP
Enterprise Inventory and Service-Level Optimization solution. The Data Gateway module consists of two utilities and a
database schema which allow you to extract a data set from your supply chain source database and import it into MIPO
for optimization and analysis. You can then export the optimized Output data from MIPO back into your supply chain
source database.
Related Topics
Managing the Data Gateway
Topology Overview
Creating an initial supply chain network
Topology Overview
A topology is defined as the physical or logical layout of the nodes in a network. A supply chain network has a standard
physical topology based on items and locations, along with the paths and processes involved. However, a data set taken
from a supply chain source, such as an ERP, comes from a variety of sources and may not be organized in a supply chain
network topology. The methodology for how MIPO handles data sets from ERPs is as follows:
1. Create an initial supply chain network

2. Create an optimized MIPO supply chain network
3. Perform output processing on optimized data
As an inventory optimization tool, MIPO depends on demand data. In order for MIPO to optimize supply chain data, a
specific logical layout must be followed based on demand streams. For data validation to occur, MIPO must be able to
logically trace the journey for each finished good back to the source of each component piece as it enters the supply
chain.
The nodes on this journey consist of stocking points, paths, and processes. Along with the physical network data, each
node includes demand data associated with the item, whether it is the finished good itself, or a sub-assembly or
component used to create the finished good.
In order for MIPO to work with data from a supply chain source, the source data must first be organized in a supply chain
network topology. Then some data manipulation must occur in order to convert supply chain data into the MIPO topology
needed for optimization.
245
The MIPO topology uses demand nodes to satisfy demand stream calculations. Demand nodes are different from physical
nodes and are created when more than one demand stream runs through one physical node. For example, when a node
has demand from both a downstream customer-facing node and an internal node, a demand node will be created to
separate the two demand streams. They are also used for customer-facing nodes that have demands from multiple
customers. By separating multiple demand streams at a single physical node, MIPO can more accurately calculate
demand on upstream nodes.
The supply chain owner has the option to use their own resources to prepare their data sets so their structure fits the
MIPO topology with demand node creation. Another solution is the Data Gateway module and the Demand Node Creation
processor, which will take data from the supply chain ERP and other sources and automatically build the MIPO topology
needed to perform optimization.
Although demand nodes are used to capture individual demand stream calculations for MIPO validation, they are not used
for optimization calculations. These nodes are removed from the validated data set prior to optimization so they do not
appear in associated output data reports. These nodes are still visually represented in MIPO’s graphic representations of
the supply chain
The tools and processes designed to optimize supply chain data using the MIPO topology are as follows:
1. The Gateway Connector extracts supply chain data from the ERP in its native format and loads the extracted
data into Gateway staging tables.
2. The Data Gateway’s Topology Creation function moves the data from the staging tables into the Gateway
schema tables (initial network topology format).
3. The Gateway Data Loader moves the data to MIPO tables (MIPO topology format).
4. The Demand Node Creation processor analyzes the data to identify where demand nodes are needed and
creates them, marking them as demand nodes.
5. MIPO validates the data set.
6. As part of MIPO optimization, the Topology Trimming function locates each marked demand node in order to
distribute the input data associated with the node to its upstream source and downstream target node before
trimming the node from the data set.
7. MIPO optimizes the trimmed data set based on input data and generates corresponding output data.
8. Depending on the licensing agreement, the optimized data set can be loaded into the Data Store for analysis.
9. The Gateway Connector extracts optimized output data from MIPO or the Data Store back into the supply chain
ERP.
Related Topics
Creating an initial supply chain network
Creating an Initial Supply Chain Network

There are four steps involved with creating an initial supply chain network:
1. Get the data set from the ERP (Data Gathering)

2. Reorganize the data into a supply chain network topology (Network Creation)
3. Populate the data set with additional information needed by MIPO (Data Augmentation)
4. Transfer the data set to MIPO (Data Loading)
246
Data Gateway
Step 1: Data Gathering

The Gateway Connector is designed to interact with the ERP to extract supply chain data and place it in the Data
Gateway. This step can also be performed using another ETL tool if preferred by the supply chain owner.
The Gateway writes the extracted data into a few basic tables in the Data Gateway, called staging tables. The following
data is extracted from the ERP:
• A list of all supply chain items (materials) and associated attributes

• A list of all supply chain locations (plants) and associated attributes
• Forecast data
• Sales history
• BOM information
• Sourcing information
Additional staging tables are provided in order to support data augmentation. This allows additional supply chain data not
extracted from the ERP to be included in the data set when the initial supply chain network topology is created.
Step 2: Network Creation

Once the extracted data resides in the Data Gateway staging tables, it can be built into an initial supply chain network.
The network consists of stocking points, process points, and supply paths used by MIPO to determine optimization
outputs.
The network is built logically by the Data Gateway’s Topology Creation function, starting at the downstream endpoints for
each item, referred to as the customer nodes. These nodes are created based on forecast data.
After customer nodes are determined, the Topology Creation function works backwards to identify each finished good
item associated with the customer, and the plant location where each finished good resides before the customer receives
it. These customer-facing nodes are logically connected to the customer nodes.
The Topology Creation function then runs an iterative process for each finished good item, based on sourcing data, to
determine the upstream stocking points and associated paths. When the sourcing data ends, the last node in the iterative
process is connected to a supplier node.
The Topology Creation function generates process point nodes for each finished good (FG) or sub-assembly (SA) based
on bill of material (BOM) information. Using BOM explosion data and appropriate sourcing data, the Topology Creation
function creates SA stocking points and Raw Material (RM) stocking points, along with the associated paths, back to their
respective supplier nodes.
Once the Data Gateway function is finished, the end result will be a data set organized in a standard supply chain network
topology.
Step 3: Data Augmentation

Before converting a data set from the initial supply chain network topology to the MIPO supply chain topology, certain
processes must be run. All non-stocking nodes that were created during the initial network topology process must be
marked.
247
Any data that was not provided by the ERP data set must also be added, either through a manual process specific to the
data set, or through predefined default settings.
Step 4: Data Loading

After the data set has been validated by the Data Gateway, it will be loaded into MIPO through the Gateway Data Loader
process.
Related Topics
Loading a new data set into the Data Gateway
Restart loading a data set into the Data Gateway
Deleting Data Gateway data set
Features
Managing Data Sets
Managing Data
Managing data sets using the Data Gateway
The Manage Data Gateway window allows you to:
• Load a new data set into the Data Gateway.
• Restart loading a data set that failed to load into the Data Gateway.
• Delete unused data sets from the Data Gateway.
To access the Manage Data Gateway window:

1. Log on to Data Gateway from the Portal window, or else click Portal > Data Gateway.
2. Click Data Set > Manage Data Gateway.
Related Topics
The Manage Data Gateway window lets you do the following:
• Extract data from a supply chain source
• Load the data set into the Data Gateway schema
248
Data Gateway
• Restart loading a data set that failed to load into the Data Gateway.
• Delete unused data sets from the Data Gateway.
• Run various processors to prepare the data set for MIPO optimization
• Import the processed data set into MIPO.
The Data Gateway uses its Gateway Connector utility to perform this function. This utility includes a configurable XML file
to map data elements from your supply chain source to corresponding data tables in the Data Gateway schema.
Note: For more information on the XML configuration file, refer to the section entitled
"Gateway Connector XML configuration settings" in the Installation Guide.
Perform the following steps to load a new data set:
1. From the Manage Data Gateway window, go to Create New Data Set and click the Configuration File Name
dropdown list to select the XML configuration file to be used for the extraction process.
2. Enter a Supply Chain Name in the appropriate field.
3. You can include a Scenario Name for your data set, if applicable.
4. If needed, you can type a Description of the data set.
5. Click the Service Level dropdown list to select the service level type used by the data set (either Non-stockout
Probability or Fill Rate).
6. If the data set includes a Master BOM, enter the name in the appropriate field.
7. The Initialization dropdown list allows you to specify how MIPO processes the data set for on hand inventory
order and planned receipts data. Select Automatic to let MIPO determine these values. Select User Specified if
your data set includes initial on hand inventory order and planned receipts data.
8. Click the Period Length dropdown list to identify whether period data is broken out by days, weeks, months or
quarters.
9. To set the Start Period, click the Browse [...] button to invoke the Period dialog box. Select the appropriate
start date and click OK.
10. Enter a value for the number of periods for the Analysis Horizon.
11. Enter a value for the number of periods for the Historical Horizon.
12. Enter a value for the number of periods for the Data Horizon.
13. Click the Entry Point dropdown list to select the entry point in the Gateway attended workflow (either Start
Inbound Connector, Create Topology, Augment Data, or Start Data Loader).
14. Click the checkbox for any appropriate break points needed for the data set.
15. Click SCHEDULE.
The Data Gateway initiates its Inbound Gateway Connector utility, which extracts data from the supply chain source and
loads the data set into the Data Gateway schema, based on the selected XML configuration file.
249
The Create Topology processor moves the extracted data from the staging tables into the appropriate Gateway tables.
The Data Augmentation processor adds additional data not supplied by the supply chain source that is needed to perform
MIPO optimization.
The data set finally gets transferred from the Data Gateway, via the Gateway Data Loader, and into MIPO, through the
Outbound Gateway Connector.
If you set one or more break points (see step 14), the Data Gateway attended workflow will stop at the appropriate break
point. You can then perform the necessary tasks to prepare the data set for the next step in the workflow process. Once
the data set is ready, click RESUME.
Note: If the data set fails to load into the Data Gateway, you can determine the reason for the failure by
reviewing the application server log. This can be done by viewing the application server logs in MIPO.
The Published Reports feature can also be used to generate a Data Loading Error report on the Gateway
data set inputs.
You can also load data sets into MIPO by placing .zip files into the Data Loader listener directory. The
listener directory is the value specified for the smartops.dataloader.service.listener.listen_
directory property in the smartops.properties file. The smartops.properties file is located in

C:\MIPO_install_dir\myserver\SmartOps on the application server, where MIPO_install_dir is the root
directory where MIPO is installed.
Related Topics
Monitoring a data set's loading progress
Monitoring a Data Set's Loading Progress
The Data Gateway Queue History table in the Manage Data Gateway window lets you monitor the progress of all data
sets currently loading or queued up to be loaded into the Data Gateway. The following information is available:
• Supply Chain Name

• Scenario Name
• Scenario Type
• Load Set Status
• Is Paused
• Qeued Time
• Extract Start Time
• Extract End Time
• Import Start Time
• Import End Time
• Export Start Time
250
Data Gateway
• Export End Time
Related Topics
Restart loading a failed data set into Data Gateway
The Manage Data Gateway window lets you reload a data set that failed during the initial load after resolving the reasons
for the failure.
Perform the following steps to restart a data set load:
1. From the Manage Data Gateway window, look in the in Data Gateway Queue History table to locate the data
set you wish to import.
2. Select the radio button corresponding to the data set.
3. Click RESTART.
The Data Gateway restarts loading the data set.
Related Topics
Cancel loading a Gateway data set
The Manage Data Gateway window lets you cancel a data set that is in, or queued up for, the loading process.
Perform the following steps to cancel a data set load:
1. From the Manage Data Gateway window, look in the in Data Gateway Queue History table to locate the data
set you wish to cancel.
2. Select the radio button corresponding to the data set.
3. Click CANCEL.
The Data Gateway cancels loading the data set.
Deleting data sets from Data Gateway
The Manage Data Gateway window lets you delete one or more data sets no longer being used. Perform the following
steps to delete a data set:
1. From the Manage Data Gateway window, look in the Data Gateway Queue History table to see the list of
available data sets.
2. Select the check box corresponding to each data set you wish to delete.
251
3. Click DELETE.
The Data Gateway deletes all selected data set from the Data Gateway schema.
When the procedure is complete the selected data sets are removed from the Data Gateway Queue History table.
Related Topics
Exporting Data
Exporting Data Sets (Data Gateway)
The Export Data Set screen allows you to export a selected module scenario to a .zip file on the application server
machine. The .zip file can then be downloaded to your PC and opened in Excel or another spreadsheet program.
Note: Exporting data sets is a user privilege. You must have privileges both to export data
sets and to view and modify the specific data sets you want to export.
To export a scenario to the application server:

1. Use the Product Module Selector to select the application associated with the data set you wish to export
2. Use the Supply Chain Selector to choose the supply chain containing the scenario.
3. Use the Scenario Selector to choose a base or user scenario.
4. Click Data Set > Gateway Export to open the Export Data Set screen.
5. For MIPO data sets only, use the Options selectors to specify demand variability, schedule attainment, and
lead time data sources. See below for more information about these MIPO options.
6. Click the appropriate check boxes to review the export history for all modules and/or all users.
7. Click Export. A .zip file containing the optimized scenario data will be created and saved to the MIPO
application server.
Note: You can cancel exporting a data set after the data loading process has started, or if
a data set is queued up to be exported. To cancel a data set, click the blue X next to the
data set record listed in the History table. A dialog box appears, requesting confirmation of
the cancellation. Click OK to initiate the cancellation process. The Data Gateway will stop
exporting the data set and remove any data that had been loaded prior to the cancellation.
8. Click Refresh. A link to the .zip file will appear in the lower panel of the Export Data Set window. Exported
scenario files are named for the scenario, followed by a number identifying their place in the sequence of other
exported files for the same scenario.
9. To open or save the .zip file containing the scenario data, click on its named link. A File Download dialog will
appear prompting you to open or save the .zip file.
10. To export a different scenario, select it from the list in the scenario selector, then click the Refresh button in the
Export Data Set window and repeat steps 4 through 8 above.
MIPO Export options
When exporting a MIPO data set, the following Forecast Error data source options are available:
252
Data Gateway
• Calculated Forecast Demand: Exports the MIPO scenario inputs for calculated forecast demand.
• Future Forecast & DIM Scenario: Exports future forecast demand only for entities with revision period equal to
the base period of the scenario. Also exports DIM Export processor settings as enabled. If the scenario did not
originally have processor settings, they are added at the end of the processing order.
• DIM Input Data (default): Exports the DIM forecast and sales input data. Also exports DIM Error processor
processing order.
When exporting a MIPO data set, the following Lead Time data source options are available:
• User Input or Calculated: Does not export purchase order data. If the original scenario included settings for the
Supply Lead Time processor and the Lead Time processor, those settings are disabled.
• SIM Input Data (default): Exports purchase order data. Also exports Supply Lead Time processor settings as
enabled. If the scenario did not originally have processor settings, they are added at the end of the processing
order.
When exporting a MIPO data set, the following Schedule Attainment data source options are available:
• User Input or Calculated: Exports historical production data. If the original scenario included settings for the
Supply processor and the Production Intelligence processor, those settings are disabled.
• PIM Input Data (default): Exports historical production data. Also exports Production Intelligence processor
processing order.
Creating Reports
Published Reports (Data Gateway)
The Data Gateway Reports menu allows you to select and export flat files containing different types of data. Grouped by
Inputs or Outputs, these text-based files are intended to be viewed, edited, and manually loaded into third-party reporting
validated and optimized in one of the modules. Unless you select an alternative supply chain and/or scenario, the
Published Reports feature will automatically select the default supply chain and associated base scenario. If the published
report you export contains outputs, the scenario you select must be validated and optimized in the associated product
module.
When you export a published report, Data Gateway generates a text file containing the specific data which is copied to a
directory on the application server machine. The text file will have either a .txt extension or .csv (comma separated
values) extension.
253
1. Use the Module Selector to select the module associated with the data set.
report.
path name. Changes to the destination directory apply to all Data Gateway users who
have privileges to export Model Data Files. For additional information, refer to the
Installation and Upgrade Guide.
o Name of the report you selected to publish

o File Name of the exported file, including the Name, a timestamp including the year, month, date,
o Status of the export process

o Start Time and End Time of the export process, in Greenwich Mean Time (GMT), by default
o User Name of the Data Gateway user who exported the file
o Comments that can be entered by your organization to provide additional information to users
254
Data Gateway
Related Topics:
Viewing Privileges
Publishing Queue (Data Gateway)

The Reports menu lets you view reports sent by the Data Gateway to the Publishing Queue. Use this feature to access
all published reports.
report or save it.
report or save it.
Related Topics:
255
Published Reports Details (Data Gateway)

Data Loading Errors
Items Master Data
Stocking Point TIP
Aggregated TIP
Demand Processor
This Inputs-based report lists all stocking points in selected supply chain for all periods in the data horizon. No
configuration is needed to run this report. The table below contains the data fields associated with this report:
Column Description
SKU
location.
RiskPoolFactor
DemandForecast
horizon.

DemandError
256
Data Gateway

Data Loading Errors
This Inputs-based report produces a status log of errors encountered during data loading process. No configuration is
needed to run this report. The table below contains the data fields associated with this report:
Column Description
Data Loading Start

Date/Time
Items Master Data
This Inputs-based report produces a complete list of all items in all scenarios. No configuration is needed to run this
report. The table below contains the data fields associated with this report:
Column Description
257
This Inputs-based report produces a complete list of all locations in all scenarios. No configuration is needed to run this
Column Description
This Outputs-based report lists static inputs and outputs for each stocking point in the selected scenario. No configuration
is needed to run this report. The table below contains the data fields associated with this report:
Column Description
SKU
location.
258
Data Gateway
Stocking Point TIP
This Outputs-based report generates Stocking Point TIP information. No configuration is needed to run this report. The
table below contains the data fields associated with this report:
Column Description

OBI_SKU_CODE
OBI_PERIOD
input data.

OBI_TIP

259

OBI_DEMAND Demand.
This Outputs-based report lists an extensive set of stocking point outputs for each period; report allows addition of
attributes, inclusion/exclusion of cost/unit/period data, and time offsets.
Configuration settings for this report can be found in the Stocking Point Output fields of the Published Reports module.
This module can be accessed through the Manage Module Settings feature. The table below contains the data fields
associated with this report:
Column Description
TIPUnits
demand.
260
Data Gateway
another.
ForecastStdDev
AIPUnits


LostSales
horizon.
AIPCosts
261
point data.
LostMargin
specified period.

This Outputs-based report lists various aggregated cost information for each stocking point in the supply chain.
Configuration settings allow the inclusion of attributes and time offsets.
Configuration settings for this report can be found in the Supply Chain Cost Details fields of the Published Reports
module. This module can be accessed through the Manage Module Settings feature.
The table below contains the data fields associated with this report:
Column Description
Processing Cost
for all periods.
262
Data Gateway
for all periods.
Order Admin Cost
periods.
Other Cost
Average Order
Quantity
Aggregated TIP
aggregated by dummy node.
Configuration settings for this report can be found in the Aggregated TIP fields of the Published Reports module. This
module can be accessed through the Manage Module Settings feature.
The table below contains the data fields associated with this report:
Column Description
SKU
location.
ordered them.
TIP
263
SAFETY_STOCK
uncertain.
This Outputs-based report summarizes cost information for the supply chain, based on several categories. Configuration
settings allow the inclusion of attributes and time offsets.
Configuration settings for this report can be found in the Supply Chain Total Estimated Cost fields of the Published
Reports module. This module can be accessed through the Manage Module Settings feature.
The table below contains the data fields associated with this report
Column Description
Processing Cost
for all periods.
for all periods.
Order Admin Cost
periods.
Other Cost
264
Data Gateway
Demand Processor
No configuration is needed to run this Outputs-based report. The table below contains the data fields associated with this
report:
Column Description
BiasRatio
processing.
CV
RiskPoolFactor
Analysis Mechanism
This Outputs-based report lists information where on hand inventory exceeds customer-specified capacity levels per
period at locations in the supply chain. You configure the report using standard MIPO attributes to designate threshold
limits.
To set up the Threshold Notification feature in order to generate a report through the user interface, you must do the
following:
First verify that threshold location attribute name has been defined in the Published Reports Module.
1. Click Settings > Module Settings to open the Manage Module Settings window.
2. Select Published Reports from the Select Module dropdown list.
3. Scroll through the module parameters to verify that the Threshold Location Attribute exists.
If there is no name defined for the threshold attribute in the properties field, you must update the field to include a
threshold attribute name. See Published Reports module settings for more information.
Note: You can define multiple threshold attribute names in the Threshold Location Attribute data field using comma
separators between names.
You can now create the threshold attribute values to be used as threshold limits when the feature is activated.
1. Click Portal > MIPO to switch to the MIPO portal.
3. Click the Browse (...) button to view Attribute Selector dialog box.
4. Select Location from Attribute Type dropdown list.
5. Select threshold attribute name listed in the .properties file from the Attribute Name dropdown list. If the
Attribute you wish to use as a threshold is not available, you can use the Create Attribute feature by clicking
Create.
265
6. Click OK.
7. On the Edit Master Data - Attributes window, add one or more threshold limits and multipliers in the Attribute
Value field.
8. Click OK.
You can now add the threshold attribute to one or more locations that you wish to monitor.
1. Click Edit > Input Data > Master Data > Locations to view the Edit Master Data - Locations window.
2. Click the Browse (...) button to view Location Selector dialog box.
3. Select the location from the dropdown list, and then click OK.
4. From the Edit Master Data - Locations window, click ADD to open the Attribute Selector.
5. Select the threshold attribute from the dropdown list, and then click OK.
6. Repeat steps 2 through 5 for other locations in the selected scenario you wish to monitor against your threshold
settings.
7. Click OK to save your edits.
After you added the threshold attribute to one or more scenario locations, you can assign a specific threshold multiplier
the stocking point node at the location.
1. Click Edit > Input Data > Network Structure > Nodes to view the Edit Network Structure - Node window.
2. Click the Browse (...) button to view Node Selector dialog box.
3. Select the stocking point node from the dropdown list, and then click OK.
4. From the Edit Network Structure - Node window, click ADD to open the Attribute Selector.
5. Select the threshold attribute from the dropdown list, and then click OK.
6. Set the threshold value for the added attribute.
7. Click OK to save your edits.
After you finish making changes to your scenario relating to the threshold notification feature, you will need to optimize it.
You can now run the Threshold Notification Report through the Published Reports feature in order to compare your
scenario data to the defined threshold limitations you’ve set up:
Column Description

ITEM

PERIOD
266
Data Gateway
point data.
Publishing Queue
Administration
Data Gateway Privilege Definitions
For information on how to set privileges, see Assigning Privileges.
Gateway Connector privileges

Access Gateway Connector module
Access Gateway Connector alerts
Delete data set from the Data Gateway
Extract data set from the external system
Gateway Data Loader privileges

Access Gateway Data Loader module
Access Gateway Data Loader alerts
Gateway Export privileges

Access Gateway Export Module
Access Gateway Export Module alerts
Data Gateway Preference Definitions

For information on how to set preferences, see Assigning Privileges.
Gateway Connector preferences

View Load Set Cancelled alerts
View Load Set Deleted alerts
267
View Load Set Failure alerts
View Load Set Scheduled alerts
View Load Set Started alerts
View Load Set Successful alerts
Email Load Set Cancelled alerts
Email Load Set Deleted alerts
Email Load Set Failure alerts
Email Load Set Scheduled alerts
Email Load Set Started alerts
Email Load Set Successful alerts
Gateway Data Loader preferences

View Load Set processing cancelled alerts
View Load Set processing failure alerts
View Scenario Renamed alerts
View Load Set Scheduled alerts
View Load Set processing started alerts
View Load Set processing successful alerts
Email Load Set processing cancelled alerts
Email Load Set processing failure alerts
Email Scenario Renamed alerts
Email Load Set Scheduled alerts
Email Load Set processing started alerts
Email Load Set processing successful alerts
Gateway Export preferences

View Demand Multiple Lags alerts
View Data Set Export Completed alerts
View Data Set Export Failed alerts
View Data Set Export Started alerts
View Inconsistent BOM alerts
View Invalid In-bin Location alerts
View Invalid Out-bin Location alerts
View Missing DIM Scenario alerts
View Non-unique Stocking Point Item Location alerts
268
Data Gateway
View Non-unique Supply Path alerts
View Packaging BOM Not Supported alerts
Email Demand Multiple Lags alerts
Email Data Set Export Completed alerts
Email Data Set Export Failed alerts
Email Data Set Export Started alerts
Email Inconsistent BOM alerts
Email Invalid In-bin Location alerts
Email Invalid Out-bin Location alerts
Email Missing DIM Scenario alerts
Email Non-unique Stocking Point Item Location alerts
Email Non-unique Supply Path alerts
Email Packaging BOM Not Supported alerts
Gateway Data Connector module settings

The Gateway Data Connector module contains the configuration settings used by the Data Gateway utility to connectivity
1. Log on to the Data Gateway application.
3. Select Gateway Data Connector from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Gateway Data Connector parameters.
Auto Default Configuration File Configuration file to be used in case of automatic transfers when the data
set does not have an associated configuration file.
Auto Export of Scenario to Tells the Data Gateway whether to automatically export a scenario to the
Connector
external system.
Connector Application JVM Defines the initial heap size for the JVM that starts the connector
Initial Heap Size
application.
Connector Application JVM The maximum heap size for the JVM that starts the connector application.
269
Maximum Heap Size
Connector Application Library Defines the Java library path for connector native libraries. When providing the
Path Connector, use this path to the JCO native libraries that corresponds to this
system.
Connector Application Name Name of the connector java application. When providing the
Connector, use smartops.jar as the value.
Connector Starting Application Name of the application that starts the connector.
Name
Data Augmentation Type The type of process used by the Data Gateway to perform data augmentation.
Data Set Check Interval Sets the check interval in minutes before the Gateway Connector utility
checks to see if there is a load set.
Export Process Schema Defines whether the Export process is based off the MIPO or Data Store schema.
The property ensures that if the export is based off of the MIPO schema, then the
scenario is locked for the duration of the export.
Related Topics:
Gateway Data Loader module settings

The Gateway Data Loader module contains the configuration settings used by the Data Gateway utility to perform data
loader functions. You can access this module by doing the following:
3. Select Gateway Data Loader from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Gateway Data Loader parameters.
Auto Delete Existing Scenario Controls whether a scenario is deleted from the Data Gateway schema when it is
deleted from the MIPO schema.
Auto Rename or Delete Provides the option to automatically rename the existing scenario by appending a
Existing Scenario timestamp to the file name, or delete the existing scenario.
Data Loading Number of Defines the number of threads to start for data loading from gateway schema
Threads
to MIPO schema.
270
Data Gateway
Data Set Check Interval Sets the check interval in minutes before the Gateway Data Loader utility
checks to see if there is a loadset.
Related Topics:
Gateway Export module settings

The Gateway Export module contains the configuration settings used by the Data Gateway utility to perform export data
set functions. You can access this module by doing the following:
3. Select Gateway Export from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Gateway Export parameters.
Alerts Limit Consolidates Gateway Export alerts upon reaching the defined limit value.
Export Directory Defines the directory path under the home directory where the exported .zip files
are stored.
Related Topics:
Alerts
Gateway Connector Alerts
Gateway Load Set Deleted
Gateway Connector Failed
Load Set Scheduled for Connector
Load Set Processing Started by Connector
Load Set Processed Successfully by Connector
271
Gateway Data Loader Alerts

Load Set Data Loading Failed
Load Set Scheduled for Data Loading
Load Set Processing by Data Loader started
Load Set Processed Successfully by Data Loader
Scenario Renamed
Load Set Cancelled Successfully by Data Loader
Gateway Data Loader Rejects and Errors
Gateway Export Alerts

Data Set Export Started
Data Set Export Completed
Data Set Export Failed
Non-unique Stocking Point Item Location
Non-unique Supply Path
Inconsistent BOM
Packaging BOM Not Supported
Invalid In-bin Location
Invalid Out-bin Location
Missing DIM Scenario
Demand Multiple Lags
Related Topics:
Filtering Alerts
Managing Alerts
Alerts
272
Data Store
Welcome to Data Store
The Data Store allows you to easily extract data from SAP Enterprise Inventory and Service-Level Optimization
applications for analysis with third-party tools. You can also use Data Store to generate Compare Scenarios reports.
Features
Data Store Management
Through the Data Store menu, you can manage the scenario data placed in the Data Store module. With the Manage
Data Store feature, you can do the following tasks:
• Transfer scenario data into the Data Store
• Delete scenario data from the Data Store
Transferring a scenario into the Data Store
Note: The Data Store Management feature is a user privilege in the Portal. You can only
transfer scenarios into the Data Store if you have privileges to do so.
Perform the following steps to transfer a scenario into the Data Store:
1. If necessary, click Portal > Data Store to activate the Data Store module.
2. Click Data Set > Manage Data Store to open the Manage Data Store window.
3. Use the Product Module Selector to select the application associated with the scenario.
4. Use the product-specific data set selector (e.g., Supply Chain or Model) to select the data set associated with
the scenario.
5. Use the Scenario Selector to select the scenario you wish to transfer.
6. Click Transfer. the data associated with the scenario you selected is written into the Data Store.
The scenario you transferred can now be used in the Compare Scenarios - Data Store feature.
Deleting a scenario from the Data Store
Note: The Data Store Management feature is a user privilege in the Portal. You can only
delete scenarios from the Data Store if you have privileges to do so.
Perform the following steps to delete a scenario from the Data Store:
1. Click Data Set > Manage Data Store to open the Manage Data Store window.
3. Under the Data Store Scenarios Available for Deletion heading, click the checkbox associated with the
scenario you wish to remove from the Data Store.
4. Click Delete. The selected scenario is removed from the Data Store.
273
Related Topics:
Compare Scenarios - Data Store
Published Reports
Compare Scenarios - Data Store
Through the Data Store Reports menu, you can access the Compare Scenario feature, which lets you select two or more
data store scenarios for comparison. Use this feature to compare comprehensive data in a tabular format showing the
selected scenarios side-by side for easy reference. You can select the following scenario items for comparison:
• Stocking points
• Process points
• Supply paths
• Cost components
• Planned forecast vs. actual sales
• Purchase orders
Generating a Compare Scenarios Report
The Compare Scenarios report feature relies on scenarios available in the Data Store module. If a scenario you wish to
compare is not in the Data Store, you can transfer it using the Data Store Management feature.
Note: Compare Scenarios feature is a user privilege in the Portal. You can only generate
a Compare Scenarios report if you have privileges to do so.
When you generate a Compare Scenarios report, the Data Store creates a text file containing the specific data which is
accessed through the Publishing Queue. The text file will have a .csv (comma separated values) extension.
Perform the following steps to generate a Compare Scenarios report:
1. If necessary, click Portal > Data Store to open the Data Store module.
2. Click Reports > Published Reports > Compare Scenarios to open the Compare Scenarios window.
4. Under the Data Store Scenarios Available for Comparison heading, click the associated check box for each
scenario you want to compare. Also, deselect check boxes for scenarios containing data you do not want to
include in your report.
Note: Click the check box next to the column heading labeled Main Entities to select or
deselect all of the available scenario comparison files.
5. Under Choose Scenario Comparison Files to Generate heading, click the associated entity you wish for
comparison. Click check box labeled All Entities if you wish to generate reports for every available entity.
6. Type in a unique name for your report in the Label field. This label name will be used to distinguish your report
from other reports listed in the Publishing Queue.
274
Data Store
7. Click OK. The scenarios you selected for comparison are submitted to the Publishing Queue.
Note: It can take several seconds for the scenarios you selected to be generated into the
Compare Scenarios report. Clicking OK multiple times causes your request to be
8. Go to the Publishing Queue to view your report.
Related Topics:
Publishing Queue
Manage Data Store
Publishing Queue (Data Store)

The Reports menu lets you view reports sent by the Data Store to the Publishing Queue. Use this feature to access all
published reports.
report or save it.
3. If the Data Store has not finished generating the selected published report, click Cancel to halt the process.
Click Remove to drop the selected published report from the Publishing Queue.
275
Administration
Configuring Scenario Comparison - Data Store Privileges
To change Scenario Comparison privileges to a user account:
1. Click Settings > User Settings to open the User Settings window. By default, the User Info tab is selected and
contains information for the current user.
2. Click User Privileges to open the User Privileges tab, shown in Figure 1-3.
3. Select a user account to modify by clicking the Browse (...) button to open the User Selector.
a. Select All or User Name from the Search by drop-down menu.

b. If you select All, a list of all users is displayed. Click the desired user name and click OK to close the
User Selector.
that start with the text you entered. If there are many users, you can page through the list.
4. Select Compare Scenario from the Select Module drop-down menu.

5. Check or uncheck the check box to grant or deny the access privilege, respectively.
6. Click OK to save your changes. The User Settings window is reloaded and displays a status message indicating
that the changes to the user account were saved successfully.
user whose account you modified is signed in to MIPO at the time you saved the changes,
he or she cannot view the privileges you changed in the User Privileges tab until he or she
logs out and signs in again.
Compare Scenario privilege definition
Data Store Privilege Definitions

Access Data Store Management module
Access Data Store alerts
Delete scenarios from the Data Store
Transfer scenarios to the Data Store
Data Store Preference Definitions

View Scenario Transfer Deleted alerts
276
Data Store
View Scenario Transfer Failed alerts
View Scenario Transfer Queued alerts
View Scenario Transfer Started alerts
View Scenario Transfer Complete alerts
Email Scenario Transfer Deleted alerts
Email Scenario Transfer Failed alerts
Email Scenario Transfer Queued alerts
Email Scenario Transfer Started alerts
Email Scenario Transfer Complete alerts
Compare Scenario module settings

The Compare Scenario module contains the configuration settings used by the Data Store utility to perform its Compare
Scenario feature. You can access this module by doing the following:
1. Log on to the Data Store application.
3. Select Compare Scenario from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Compare Scenario parameters.
Cost Component Report Header for Compare Scenario Cost Component Report.
Header
Date Format Date formatting for all Compare Scenario reports.
Decimal Precision Decimal precision for real number values in all Compare Scenario
reports.
Field Separator Field separator for all Compare Scenario reports.
Output File Target Directory Directory where output files are stored.
Planned vs Actual Report Header for Compare Scenario Planned vs Actual Report.
Header
Process Point Report Header Header for Compare Scenario Process Point Report.
277
Purchase Order Report Header Header for Compare Scenario Purchase Order Report.
Service Level Decimal Decimal precision for service level values in all Compare Scenario reports.
Precision
Stocking Point Report Header Header for Compare Scenario Stocking Point Report.
Supply Path Report Header Header for Compare Scenario Supply Path Report.
Related Topics:
Data Store module settings

The Data Store module contains the configuration settings used by the Data Store to perform its functions. You can
access this module by doing the following:
1. Log on to the Data Store application.
3. Select Data Store from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Data Store parameters.
Allow Data Store Transfer Parent setting to allow scenarios to be transferred from MIPO to the
Data Store.
Auto Delete from Data Store Controls whether a scenario is deleted from the Data Store schema when
it is deleted from the MIPO schema.
Parallel Task Count Defines the number of concurrent tasks started for Data Store processing.
Related Topics:
278
Data Store
Data Store scenario settings

The Data Store module contains the scenario settings used by MIPO as default parameters for any setting not defined in
the data set. You can access this module by doing the following:
1. Log on to the MIPO application.
3. Select Data Store from the dropdown list.
Auto Transferable Select Yes to automatically transfer scenario to Data Store after optimization.
Related Topics:
Alerts
Data Store Alerts
Scenario Transfer Started
Scenario Transfer Failed
Transfer Complete
Scenario Transfer Queued
Data Store Scenario Deleted
Related Topics:
Filtering Alerts
279
Managing Alerts
Alerts
280
DIM
Welcome to Demand Intelligence Module
The DIM application consists of the Demand Intelligence processor and a user interface accessible through the portal.
The Demand Intelligence processor calculates the standard deviation of the demand forecast provided as input for MIPO,
based on historical demand forecasts and corresponding actual sales or shipment figures. These calculations are
designed to detect bias in the historical forecasts in order to adjust the demand forecast mean provided as input. In
addition, the processor generates a number of diagnostic outputs (e.g., estimated forecast bias) available as reports.
The Demand Intelligence processor runs during the preprocessing phase of MIPO optimization. This process requires
RFS (historical and future forecasts) and TDD (historical sales) data in order to run correctly.
The Demand Intelligence processor determines and populates per period demand standard deviation by item-location-
period at all customer facing stocking points (including those that contain insufficient demand data or no data at all) for
periods in the MIPO data horizon.
Features
DIM Features Overview
The DIM application User Interface lets you calculate forecast errors and forecast biases from a selected MIPO scenario,
based on past sales data, and both past and future forecast data. These calculations can then be exported back to MIPO
to provide more accurate optimization results The following features are available in DIM:
• Managing DIM Data Sets
• Analyzing DIM Data
• Creating DIM Reports
Managing Data Sets

Importing Data
Importing a MIPO Scenario into DIM
The Import Scenario window allows you to load a MIPO user scenario into DIM. If you wish to export the DIM-generated
outputs back to MIPO, you must import a MIPO user scenario rather than the base scenario, as any MIPO base scenario
cannot be edited once it has been loaded into MIPO.
1. Click Data Set > Import Data Set to open the Import Scenario window.
281
2. From the list of MIPO scenarios, click the radio button associated with the scenario you wish to import into DIM.
3. Click OK. You will be required to confirm your request.
4. From the Confirmation dialog box, click OK. The Manage Scenarios window appears.
5. Use the Manage Scenarios window to name the DIM scenario and set configuration parameters used by the
DIM Import Processor.
6. Click OK. The scenario will be loaded into the DIM module. When completed, you will see a message stating
"Imported Scenario successfully."
The Scenario Import History table is updated to include information based on the selected MIPO scenario, including the
status of the import process.
Once the selected MIPO scenario is successfully imported into DIM, you will see the status change to “Completed” in the
Data Set Import History table. Additionally, the Model and Scenario Selectors will include the names of the DIM data
model specified in the file you imported.

At the bottom of the Import Scenario window, there is a list of Import transactions as logged by DIM. The Import history
list includes the following information:
• MIPO Scenario Name
• DIM Scenario Name
• Loading Start and End date/time
• Status
The Import History is not limited to manual imports, but includes all unattended loads as well.
Note: If you have trouble importing the data set, use the View Alerts feature to determine
if any alerts were generated during the Import process. You can find more information on
DIM alerts here.
Related Links:
Exporting DIM Scenario to MIPO
Editing Demand Stream Static Inputs
Exporting Data
The Export Scenario screen allows you to export an optimized DIM scenario to the associated MIPO user scenario in
order to re-optimize the MIPO scenario with the DIM target demand outputs.
Note: Exporting scenarios is a user privilege in DIM. You must have privileges both to
export scenarios and to view and modify the specific scenarios you want to export.
To export a DIM scenario to the associated MIPO user scenario:

282
DIM
1. Use the Supply Chain Selector to choose the supply chain containing the DIM scenario you want to export.
2. Click Data Set > Export Data Set to open the Export Scenario window.
3. Click the Browse (...) button to open the MIPO Scenario Selector.
4. Select the associated MIPO user scenario by clicking its radio button.
5. Click OK to close the Scenario Selector.
6. Click OK to confirm the export.
The scenario’s demand output data will be exported back to the MIPO user scenario.
The Scenario Export History table is updated to include information based on the selected MIPO scenario, including the
status of the export process.
Once the selected DIM scenario is successfully exported to MIPO, you will see the status change to “Finished” in the
Scenario Export History table. You can now open the MIPO application and re-optimize the user scenario so it includes
the DIM target demand outputs.
Related Links:
Importing a MIPO Scenario (DIM)
Editing Data
The demand stream is the supply path between the customer-facing stocking point and the customer. The static input
data associated with the demand stream in DIM include the demand interval and the recency factor. You can edit these
static inputs for one or multiple demand streams in DIM.
To edit static input data for demand streams:
1. Ensure that you have selected the correct data model and user scenario selected in the Model and Scenario
Selectors; you cannot edit the base scenario.
2. Click Edit > Input Data > Demand Stream to open the Edit Demand Stream Data - Static window.
choose demand streams that you want to edit.
selected on the left and all of the editable properties on the right. By default, no data exists for the Demand
Interval or Recency Factor fields for a Demand Stream. This data can be added to a load set, but it is optional.
If no data has been provided in the load set, the values in the edit screen are blank. They may still be edited.
window, or by entering a number in the Page field and pressing enter.
7. If there are multiple paths, select the paths that you want to edit:
8. Click an individual radio button to edit an individual path.
9. Click the All Paths on all pages radio button to edit all paths.
283
10. Choose the method you want to use to specify your changes by clicking the one of the following radio buttons:
• Click =x to assign a new value.
• Click +x or -x to increase or decrease by a specific value.
• Click +x% or -x% to increase or decrease a value by percentage.
Note: When editing values that have a pre-defined valid range (such as, 0-1 for Yield
or Reliability) and you attempt to enter an absolute value (=x) outside of that range, a
status message indicates that the value you entered is invalid and you are prompted
to enter a different value.
However, if you specify a relative change (+x or -x) or a percentage change (+x% or
-x%) that results in a value outside the valid range, the value is automatically rounded
up or down to the closest valid value. For example, if the valid range is 0-1, the
current value is .75, and you increase it by 200%, the resultant value exceeds the
valid range. In this case, the new value that is saved for this property and displayed in
the user interface is one (1).
If the value is restricted to integers, any decimal value is rounded to the nearest
integer.
• For Demand Interval, the value must be an integer and no greater than the historical horizon. A
value of zero is treated as null.
• For Recency Factor, the value must be greater than zero, but less than or equal to one.
you made.
Related Links:
Analyzing DIM Data

In DIM, each data set is associated with a user scenario. You can use the Manage Scenarios screen to set specific
configuration parameters before computing the DIM data set outputs. After computation, the user scenario can be
analyzed. Its output data can be updated if necessary, then exported back into the MIPO user scenario from which the
data set was originally derived.
When you apply changes to any DIM scenario, validate, compute it, and view the new results (or outputs), you are
analyzing a scenario. You manage scenarios by duplicating and deleting them in DIM .
284
DIM
Note: The ability to analyze and manage scenarios is a user privilege in DIM. If you are
not authorized to analyze or manage scenarios, the Analyze > Manage Scenarios menu
Manage Scenario Access feature to add users.
Preparing a DIM scenario for Computation
If you select a DIM data set and its associated base scenario, you can edit a limited amount of related information, such
as Model Name, Description, and Owner in the Manage Scenarios window. You can also change default information in
the following fields:
• Scenario Name - the name of the scenario.
• Period Length - the length of time for which time varying data is provided to MIPO. For example, if a forecast is
given in weekly time buckets, the period length is one week.
• Start Period - the period from which calculation must begin for the selected scenario. All horizons are
• Historical Data Horizon - the amount of historical data available for creating a timeline in MIPO.
The Main Settings section of the DIM Manage Scenarios screen contains the following fields:
• CV Computation Method - Determines the type of CV Computation to use, either MAD (default) or MAPE.
• Minimum Data Point Count - Minimum number of historical observations required to calculate CV.
• Default Demand CV - Defines the CV default. This is used when CV cannot be calculated.
• Identify Period of First Sale - Determines if the period of first sale needed for DIM computation.
• Forecast Lag Method - Determines the method to be used for calculation of the CV.
• Enable Intermittency Classification - Indicates whether DIM should run Intermittency Classification
calculations on the data set.
• Enable Exclusion of Outliers Indicates whether DIM should exclude outliers during computation.
• CV Filtering - Determines which CV Filtering approach to use, either CapCV (default) or DiscardHighCV.
• Adjust CV for Bias - Indicates the type of sales bias adjustment to be used on the stocking point forecast at
the end of the DIM processor computation.
The Intermittency tab of the DIM Manage Scenarios screen contains the following fields:
• Intermittent CV Default Decider - Sets the mechanism to decide the default CV.
• Intermittent Demand Interval - Sets minimum value for the ratio of length of horizon to number of periods with
positive sales below which the demand is classified as non-intermittent.
• Minimum Number of Sales - Sets the minimum number of historical sales data required for CV calculation
when stocking point has been classified as intermittent based on the Intermittent Demand Interval.
285
• Small Sales Threshold Percentage - Defines the percentage of the average sales volume below which sales
are treated as zero volume as part of demand intermittency computations.
• Advanced Classification - If the user has chosen to classify intermittent demand, the further choice to use the
advanced intermittent demand classification algorithms that check for seasonality and good forecast timing
accuracy (yes) or not (no) can be made.
• Forecast Timing Accuracy - Determines the minimum value for forecast timing accuracy above which demand
that is candidate for intermittent demand is classified as intermittent.
• Average Number of Switches - Determines whether demand that is candidate for intermittent demand is
instead seasonal, based on how many times historical sales switch from zero to non zero (or back). The higher
the value the less likely demand will be classified as seasonal.
The Exception Handling tab of the DIM Manage Scenarios screen contains the following fields:
• Outlier Multiplier - Number of standard deviations used to identify outliers.
• Cap APE Outliers - Determines whether to cap APE outliers (if set to Yes, outliers are capped).
• APE Cap - Default Average Percent Error Cap for zero forecast.
• APE Default - Default Average Percent Error default for zero forecast.
• APE Outlier Multiplier - Number of standard deviations used to identify APE outliers.
• CV Cap - Determines the Maximum CV for forecast errors.
• CV Percentage - Determines the percentage of the higher CV that will be discarded.
• Positive Bias Cap - Specifies the upper bound limit for the bias.
• Negative Bias Cap - Specifies the lower bound limit for the bias.
The Data Adjustment tab of the DIM Manage Scenarios screen contains the following fields:
• Insert Zero for Null in Historical Forecast - Sets whether to convert null future forecast values to zero.
• Insert Zero for Null in Historical Sales - Identifies whether to convert null historical forecast sales values to
zero.
• Risk Pooling Factor - Risk pooling factor to be applied to the CV.
• Bias Confidence Interval - Determines level of confidence required in estimating bias.
• Recency Factor - Specifies the recency factor for all demand streams. The recency factor allows recent
forecast bias and forecast error CV to have more weight in DIM calculations. Enter a value greater than zero,
but less than or equal to one. The lower the value of the recency factor, data in recent periods has more impact
in the forecast bias and forecast error CV calculations.
The Forecast Lag Handling tab of the DIM Manage Scenarios screen contains the following fields:
• Lag - Determines the lag for which the CV is calculated.
• Maximum Lag - The number of additional forecast revision periods to be considered to account for lag.
286
DIM
• Lag Interval - Determines the Lag Interval increments used by DIM to calculate the CV for all lags from 0 to
Maximum Lag.
Other fields on the Manage Scenario screen are read-only:
• Base scenario modified- indicates whether or not changes have been made to the base scenario
• Last Modified - the date and time that the data model was last changed
• Modified By - the user name of the person who last modified the data model
• Base Period - the latest recognized date in the database when historical data transitions to forecast data
• Audit History Exists - identifies if input data had been updated in the scenario via a check box indicator.
Perform the following steps to edit DIM scenario information:
1. Use the Model Selector to select a data model. The base scenario is automatically selected in the Scenario
Selector.
3. Change the name of the data model by entering a new name in the Model Name field, if desired.
pipe (|).
User Selector.
6. Update any of the DIM configuration parameters from the default settings, if necessary.
8. You can now compute the scenario by using the Tasks menu.
Related Topics:
Duplicating a User Scenario
Validating a Scenario
Computing a Scenario
Postprocessing a Scenario
287
Managing Scenario Access (DIM)
Deleting a Model or a Scenario
Deleting Multiple Scenarios (DIM)
Creating a DIM User Scenario

You can create a DIM user scenario if you wish to run the DIM computation on a variation of the Base Scenario.
To create a User Scenario:
1. Use the Model Selector to select a data model. The base scenario is automatically selected in the Scenario
Selector.
3. Click TASKS>Create User Scenario.
4. Enter a name for the User Scenario in the Scenario Name field.
User Selector.
7. Change any of the DIM configuration parameters from the default settings.

The Scenario Selector is updated with the new User Scenario.
9. You can now compute the user scenario by using the Tasks menu.
During this time, you can continue using the DIM application. To determine the status of a
Related Topics:
Analyzing and Managing Scenarios (DIM)

288
DIM

If there is an existing DIM user scenario to which you want to make small changes, duplicating it and making changes to
the copy can save time and decrease the likelihood that you will introduce errors.
To duplicate a DIM scenario:

2. Use the Scenario Selector to select the DIM user scenario you want to duplicate (you cannot duplicate a base
scenario).
3. Click TASKS > Duplicate Scenario. A dialog box opens and prompts you to enter a name for the copy of the
scenario.
4. Enter a name in the Scenario Name field and click OK.
5. Update any of the DIM configuration parameters from the default settings, if necessary.
The Manage Scenarios window is reloaded and displays a status message indicating that scenario copy was
created successfully. The name you entered for the copy of the scenario is displayed in the Scenario Selector.
The Manage Scenarios window is refreshed, and contains a status message indicating whether the user scenario was
saved successfully. If the scenario was saved successfully, and you are the owner, the Scenario Selector displays the
name of the user scenario you created. In addition, the following fields contain updated information:
• Scenario Status – indicates the status of the scenario; if the user scenario was created successfully, this field
reads “Created, not validated.”
• Base scenario modified – indicates whether or not changes have been made to the base scenario
• Last Modified – the date and time that the supply chain was last changed
• Modified By – the user name of the person who last modified the supply chain
• Base Period – the latest recognized date in the database when historical data transitions to forecast data
• Audit History Exists – identifies if input or output data had been updated in the scenario via a check box
indicator. You can review the specific data changes for the scenario by clicking Edit > Audit Data Changes.
The Scenario Audit Information panel is displayed in the Manage Scenarios window. It displays information about tasks
performed on the selected scenario, including when the scenario was created, the Scenario Status of validation and
computation, and the Date and Time that the tasks occurred.
Related Topics:
289
Validation ensures that data added to the system is compatible with the algorithms used to calculate (or optimize) outputs.

1. Use the Model Selector to select the supply chain containing the scenario you want to validate.
2. Use the Scenario Selector to select the user scenario that you want to validate.
• If the scenario was validated successfully, you can now compute it.
• If the scenario contains validation errors, you must correct them before continuing. To determine the
Related Topics:

290
DIM
Before you can view the results (or outputs) of the changes you make to a DIM scenario, it must be validated and
computed. Validation ensures that the scenario is structurally and logically consistent with the algorithms used to calculate
outputs in DIM. When you compute a scenario, the data it contains is used by the algorithms to calculate new results
based on the changes you made.
Note: The ability to compute a user scenario is a user privilege. If you are not authorized
to compute a scenario, the TASKS > Compute Scenario menu item is disabled in the
Perform the following steps to compute a scenario:
1. Use the Model Selector to select the DIM scenario you want to compute.
Note: If you select a scenario for computation that has not yet been validated, it will be validated automatically
before the optimization process begins.
3. Click TASKS > Compute Scenario. The Manage Scenarios window is refreshed and displays a status
message indicating that the scenario is being computed. In addition, the Scenario Audit Information is updated
to reflect the status of the computation process.
Note: The amount of time it takes to compute a scenario depends on the quantity of data it contains. While a
scenario is being computed, the Manage Scenarios window is periodically reloaded. To annually reload the
Manage Scenarios window during computation, click REFRESH. To cancel computation, click TASKS >
Cancel Computation.
4. When computation of the scenario is complete, the Manage Scenarios window displays a status message
indicating that computation is complete. In addition, the Scenario Audit Information indicates that computation
is complete, and whether or not the scenario was computed successfully:
Note: If the scenario contains validation errors that prevent it from being computed successfully, you must
correct them before continuing. To determine the origin of errors, click Alerts > View Alerts to view the alerts
associated with the scenario. For specific information about the incorrect data, identify the specific alert and
view the alert details.
Related Topics:
After a scenario has been computed, you can run processors designed to perform specific postprocessing tasks on the
291
Note: If you select a scenario for postprocessing that has not yet been computed, it will be
computed automatically before the postprocessing process begins.
Related Topics:



compute (DIM).
292
DIM
Managing DIM Scenario Access

This feature lets the owners of specific user scenarios to provide access privileges to other application user accounts.
Perform the following steps to provide scenario access to another user account:
1. Use the Model Selector to select the model containing the base, historical, or user scenario for which you
want to provide access.
scenario owner.
Related Topics:
Note: The ability to delete models and user scenarios are user privileges. If you are not
authorized to delete supply chains and scenarios, the TASKS > Delete menu items are
disabled.

1. Use the Model Selector to select the model containing the base or user scenario you want to delete.

• If you have selected a base scenario, click TASKS > Delete Model.
• If you have selected a user scenario, click TASKS > Delete Scenario.
293
file settings" section in the Installation and Upgrade Guide.
Note: Processes invoked when you delete a model or scenario can take some time to
execute. During this time, you can continue using the application. To determine the status
of a scenario-related process, click Analyze > Analyze/Manage Scenarios to open the
6. Click OK to delete the model or scenario. The Scenario Management window is reloaded and it displays a
status message indicating that the supply chain or scenario has been deleted.
Note: All published reports associated with the deleted model or scenario will also be
deleted by default. You can change the default through the Published Reports module
configuration settings, found under Settings > Manage Module Settings.
Related Topics:
Related Topics:
Deleting Multiple DIM Scenarios
Note: The ability to delete models and user scenarios are user privileges. If you are not
authorized to delete models and scenarios, the Analyze > Delete Scenarios menu item
is disabled.
To delete multiple DIM scenarios at the same time:
application..
3. Click Delete.
Note: Processes invoked when you delete a model or scenario can take some time to
execute. During this time, you can continue using the application. To determine the
294
DIM
Note: All published reports associated with the deleted model or scenario will also be
deleted by default. You can change the default through the
Related Topics:
Analyzing and Managing DIM Scenarios
Creating DIM Reports

Demand Processor Report
The Demand Processor report displays the forecast and actual data values the Demand processor uses to calculate
forecast error. The report also displays several forecast statistics calculated by the processor, including mean error,
standard deviation, mean absolute deviation, MAPE, CV, and bias.
To run the Demand Processor report:
3. Select Reports > Processor Reports > Demand Processor.
4. Use the Browse... button next to the Stocking Points for Report field to choose a single stocking point on
which to report.
Note: Although the report selector allows you to choose any stocking point, this report
displays results for customer facing stocking points only. The system will not prevent you
from selecting other stocking points, but no data will be displayed for non-customer-facing
stocking points.
5. Use the Start and End selectors to set location and date parameters.
Notes:
295
• This report displays column totals for all rows of data returned in the report, not just for those rows visible on
any given screen.
• The report displays row totals for all periods in the Demand processor data set, not just those selected for the
report.
• The statistical values shown in this report are independent of the period selected; they cover the entire data set.
Related Topics:
Printing Reports
Comparing Reports
Raw Forecasts Report

The Raw Forecasts report displays the raw forecast data streams provided to the Demand processor. The report can be
run for a single stocking point over a given period.
To run the Raw Forecasts report:
3. Select Reports > Processor Reports > Raw Forecasts.
4. Use the Browse... button next to the Stocking Points for Report field to choose an internal stocking point on
which to report.
Note: Although the system allows you to select any stocking point, this report displays
results for customer facing stocking points only. If you run the report for non-customer-
facing stocking points, no data will be displayed.
5. Use the Revision Start and Revision End selectors to set revision date parameters (displayed as columns in
the report).
6. Use the Forecast Start and Forecast End selectors to set forecast date parameters (displayed as rows in the
report).
Related Topics:
Printing Reports
Comparing Reports
296
DIM
Published Reports
Published Reports (DIM)
The DIM Reports menu allows you to select and export flat files containing different types of data. Grouped by Inputs or

Published reports rely on inputs and outputs related to a selected data model, including scenario-specific output data
validated and computed in DIM. Unless you select an alternative data model and/or scenario, the Published Reports
feature will automatically select the default data model and associated base scenario. If the published report you export
contains outputs, the scenario you select must be validated and computed in DIM.
When you export a published report, DIM generates a text file containing the specific data which is copied to a directory
on the application server machine. The text file will have either a .txt extension or .csv (comma separated values)
extension.
1. Use the Model Selector to select the data model for which you want to generate the published report.
report.
path name. Changes to the destination directory apply to all DIM users who have
privileges to export Model Data Files. For additional information, refer to the Installation
and Upgrade Guide.
297


• User Name of the DIM user who exported the file
Related Topics:
Published Reports Details (DIM)
Publishing Queue (DIM)
Data Loading Errors
Items Master Data

Demand Processor
Data Loading Errors

This Inputs-based report produces a status log of errors encountered during data loading process. No configuration is
needed to run this report. The table below contains the data fields associated with this report:
Column Description
Supply Chain Name The name given to the supply chain when it was created in MIPO.
Scenario Name The name given to the scenario when it was created in MIPO.
298
DIM
Data Loading Start

The date and time when the MIPO data loader started the data loading process.
Date/Time
Rejection Reason The reason MIPO rejected the data set.
Rejection Date/Time The date and time the load set was rejected.
Items Master Data

This Inputs-based report produces a complete list of all items in all scenarios. No configuration is needed to run this
Column Description
Item A unique material or finished good identified in MIPO as part of your supply chain data.

This Inputs-based report produces a complete list of all locations in all scenarios. No configuration is needed to run this
Column Description
Location – a unique area and/or building identified in MIPO as part of your supply chain
Loc
data.
Demand Processor
No configuration is needed to run this Outputs-based report. The table below contains the data fields associated with this
report:
299
Column Description
Stock Keeping Unit – A unique indicator that identifies an item at a particular geographic
SKU
location.
Item A unique material or finished good identified in MIPO as part of your supply chain data.
Loc Location – a unique area and/or building identified in MIPO as part of your supply chain data.
The value used to apply bias adjustment to the stocking point forecast at the end of demand
BiasRatio
error processing.
CV
Represents the value used to make a heuristic adjustment to the safety stock computation
RiskPoolFactor
based on the perceived correlation of demand across customer-facing nodes.
Analysis Mechanism
Optional static input that specifies the recency factor for the demand stream. The recency
Recency Factor factor allows recent data to have greater weight in the forecast bias and forecast error CV
calculations. The value must be greater than zero and less than or equal to one.
Related Topics:
Generating Published Reports (DIM)
The Reports menu lets you view reports sent by DIM to the Publishing Queue. Use this feature to access all published
reports.
report or save it.
300
DIM
report or save it.
Related Topics:
Generating Published Reports (DIM)
Administration
Demand Intelligence Privilege Definitions
Access Demand Intelligence Module
Access Demand Intelligence Module alerts
Access DIM Reports
Access Demand Error Report>
Access Raw Forecasts Report
Demand Intelligence Preference Definitions

View Bias adjustment alerts
Email Bias adjustment alerts
View Stocking point wrong type alerts
Email Stocking point wrong type alerts
301
DIM module settings

The Demand Intelligence module contains the configuration settings used by the DIM utility to perform its functions. You
can access this module by doing the following:
1. Log on to the DIM application.
3. Select Demand Intelligence from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Demand Intelligence parameters.

Parameter Description Notes
Name
Alerts Limit Identifies the alert threshold limit used by DIM before consolidating Defaults to “300.”
alerts of a specific type.
Adjust Future Determines whether or not DIM applies the bias adjustment to the Defaults to “No.”
Forecasts for demand stream forecast at the end of DIM processing.
Bias Requires application
server restart.
Default Export Defines the Export CV value to use if none is provided with the data Defaults to “0.5.”
CV set.
Demand STD Determines whether to convert null future forecast values to zero. Does not require
Future Forecast application server
Insert Zero restart.
Demand STD Determines whether to generate the raw inputs log file. Does not require
Raw Data Log application server
restart.
Demand STD Defines the DIM target scenario name pattern when created. Read-only parameter.
Target Scenario
Name Pattern
Parallel Task Defines the number of concurrent tasks started for DIM processing. Does not require
Count application server
restart.
Related Topics:
302
DIM
DIM scenario settings

The Demand Intelligence Module contains the scenario settings used by DIM as default parameters for any setting not
defined in the data set. You can access this scenario module by doing the following:
1. Log on to the DIM application.
3. Select Demand Intelligence from the dropdown list.
APE Cap Sets the default Average Percent Error Cap value to be used for zero forecast.
APE Default Sets the Average Percent Error default value to be used for zero forecast.
APE Outlier Multiplier Determines the number of standard deviations used to identify APE outliers.
Adjust CV for Bias Determines the types of forecast bias adjustment: Adjust None, Adjust Postive,
Adjust Negative, Adjust All.
Advanced Classification Select Yes to use advanced intermittent demand classification algorithms that
check for seasonality and good forecast timing accuracy.
Average Number of Switches Determines whether demand is intermittent or seasonal, based on how many times
historical sales switch from zero to non zero (or back). A higher value indicates
demand less likely will be classified as seasonal.
Bias Confidence Interval Percentage value determines level of confidence required in estimating bias.
Business Alerts On Inputs Stop Sets the severity level needed to shut down the DIM input validation process.
Severity
Business Alerts On Outputs Sets the severity level needed to shut down the DIM output validation process.
Stop Severity
CV Cap Determines the maximum CV for forecast errors.
CV Computation Method Determines the type of CV Computation to use: MAD or MAPE.
CV Filtering Determines which CV Filtering approach to use: Cap CV or Discard High CV.
CV Percentage Determines the percentage of the higher CV that will be discarded.
Cap APE Outliers Select Yes to cap APE outliers in DIM calculations.
Data Horizon Defines the number of periods of data available for DIM calculations.
Default Demand CV Defines the default CV used for intermittent stocking points when CV cannot be
calculated.
Enable Exclusion of Outliers Select Yes to exclude outliers from DIM calculations.
303
Enable Intermittency Select Yes to classify demand as Intermittent.

Classification
Forecast Lag Method Determines the method used to calculate the CV.
Forecast Timing Accuracy Defines the minimum value for forecast timing accuracy as a percentage ratio used
for intermittent classification.
Historical Data Horizon Defines the amount of historical data available for DIM to use for CV computation.
Identify Period of First Sale Select Yes to have DIM find the first sale period in the data set.
Insert Zero for Null in Historical Determines whether to convert null historical forecasts to 0.
Forecast
Insert Zero for Null in Historical Determines whether to convert null historical sales to 0.
Sales
Intermittent CV Default Decider Determines the mechanism to decide the default CV: Minimum, Maximum, or
Average.
Intermittent Demand Interval Sets minimum value for the ratio of length of horizon to number of periods with
positive sales below which the demand is classified as non-intermittent.
Lag Specifies the number of periods between the forecast creation date and the
forecast planning date.
Lag Interval Determines the Lag Interval increments used by DIM to calculate the CV for all lags
from 0 to Maximum Lag.
Maximum Lag The number of additional forecast revision periods to be considered to account for
lag.
Minimum Data Point Count Sets the minimum number of historical observations required for CV.
Minimum Number of Sales Sets the minimum number of historical sales data required for CV calculation when
stocking point has been classified as intermittent based on the Intermittent Demand
Interval.
Negative Bias Cap Specifies the lower bound limit for the bias.
Outlier Multiplier Determines the number of standard deviations used to identify outliers.
Positive Bias Cap Specifies the upper bound limit for the bias.
Recency Factor Specifies the recency factor for the demand stream. The recency factor allows
recent forecast bias and forecast error CV to have more weight in DIM calculations.
Enter a value greater than zero, but less than or equal to one. The lower the value
of the recency factor, data in recent periods has more impact in the forecast bias
and forecast error CV calculations.
Risk Pooling Factor Defines a percentage value for the Risk Pooling Factor applied to the CV.
Small Sales Threshold Defines the percentage of the average sales volume below which sales are treated
Percentage as zero volume as part of demand intermittency computations.
Transfer Demand Processor Select Yes to transfer DIM scenario demand processor outputs to Data Store.
Outputs
Transfer Forecast Select Yes to transfer DIM scenario forecast data to Data Store.
Transfer Sales Select Yes to transfer DIM scenario sales data to Data Store.
Transfer Supply Paths Enables transfer of DIM scenario supply path data to Data Store.
304
DIM
Related Topics:
Alerts
Demand Intelligence Alerts
Sale Bias Adjusted
Stocking Point Wrong Type
Invalid Positive Bias Cap
Invalid Negative Bias Cap
Demand Interval is greater than Historical Data Horizon
Invalid DIM Lag
Small Sales Threshold Percentage Invalid
Related Topics:
Filtering Alerts
Managing Alerts
Alerts
305
SIM
Welcome to Supply Intelligence Module
The Supply Intelligence Module includes the Supply Intelligence processor, which runs during the preprocessing phase of
MIPO optimization. This process requires POF data in order to run correctly.
The Supply Intelligence processor calculates the mean order processing lead time, the mean physical lead time, and the
total lead time standard deviation for all supply paths with sufficient historical transactional data. The processor then
overwrites the values originally provided in the loadset with its newly calculated values.
Features
Viewing SIM Data
Supply Path Static Inputs Report (SIM)
The Supply Path Static Inputs Report displays inputs for supply paths. The report results are non-interactive and can be
viewed only in a table.
the sections of this report that are expressed in units.
3. Click Reports > Input Reports > Supply Paths > Static Data to open the Supply Path Static Inputs Report
window. By default, the window displays results for all restricted paths.
4. Click the Browse (...) button next to the Supply Paths for Report field to open the Path Selector. Use the
Path Selector to select a different set of paths for which to generate the report, if desired.
6. Click Refresh. The Supply Path Static Inputs Report window is reloaded containing the new results in table
selected.
Column Description
The time that it takes from when the upstream (supplier) location begins to fill that order until it is
Physical Lead Time received in the downstream location. Physical lead time may also be defined as the time during
which physical goods are being modified (assembled, transported) and actual material costs are
being incurred. This may include manufacturing time, transportation time and material handling
307
/warehousing) time.
Order Processing Lead The elapsed time from when the order is placed on an upstream location until that location
Time begins to fill that order. This can include order receipt time, processing time, and queuing time.
Other Lead Time The amount of time an order physically exists.
Total Lead Time Mean The mathematical average of lead time in a given period.
Total Lead Time Standard deviation of lead time is a statistical measure of uncertainty regarding the magnitude
Standard Deviation of expected lead time in a given period.
Periods Between PBS defines the frequency at which shipments are made for a path, independent of PBR. PBS
Shipments is specified in number of periods.
Lets you define the number of periods for which variability in incoming demand to a stocking
Frozen Window
point or process point should not be considered.
Service Time
The one-to-one relationship between upstream and downstream items in the distribution portion
Packaging BOM of a supply chain. It determines the quantity of the upstream item in each package of the
downstream item.
Yield The remaining proportion of a process’ output after yield loss.
Minimum Batch Size

The minimum amount needed, measured by quantity, before an initial order can be produced.
(Units)
Minimum Batch Size The minimum amount needed, measured by periods of coverage, before an initial order can be
(Periods) produced.
The order quantity that is agreed-upon between the upstream and downstream nodes. The
Batch Size
downstream node’s order quantities must be an integer multiple of the batch size.
The probability that an order delivery will be completed within the total lead time (cycle time). If
Reliability delivery cannot be completed within the lead time, then it is assumed to be completed within two
lead times.
Identifies the transportation mode used to convey supply chain items on the associated supply
Mode
path.
Related Topics:
Printing Reports
Comparing Reports
308
SIM
Creating SIM Reports

Published Reports (SIM)
Published Reports (SIM)
The SIM Reports menu allows you to select and export flat files containing different types of data. Grouped by Inputs or

validated and optimized in MIPO. Unless you select an alternative supply chain and/or scenario, the Published Reports
feature will automatically select the default supply chain and associated base scenario. If the published report you export
contains outputs, the scenario you select must be validated and optimized in MIPO.
When you export a published report, SIM generates a text file containing the specific data which is copied to a directory
extension.
report.
path name. Changes to the destination directory apply to all SIM users who have
and Upgrade Guide.
309

• User Name of the SIM user who exported the file
Related Topics:
Viewing Privileges
Publishing Reports Details (SIM)
Data Loading Errors
Items Master Data

Stocking Point TIP

310
SIM
Aggregated TIP
Demand Processor

Column Description
SKU
location.
RiskPoolFactor
DemandForecast
horizon.

DemandError

Data Loading Errors

Column Description
Data Loading Start

Date/Time
311
Items Master Data

information:
Column Description

Column Description
312
SIM

Column Description
SKU
location.
Stocking Point TIP

This report contains outbound data relating to the selected scenario, including the following information:
313
Column Description

OBI_SKU_CODE
OBI_PERIOD
input data.

OBI_TIP


OBI_DEMAND Demand.

Column Description
TIPUnits
314
SIM
demand.
another.
ForecastStdDev
AIPUnits

315

LostSales
horizon.
AIPCosts
point data.
LostMargin
specified period.


316
SIM
Column Description
Material Cost The material cost incurred.
Transportation Cost The transportation cost incurred.
Processing Cost The processing cost incurred.
Inventory Holding Cost Inventory holding cost.
Order Admin Cost Order administration cost.
Handling Cost Handling cost.
Other Cost Other cost.
Total Estimated Cost Total estimated cost.
Average Order
Quantity
Aggregated TIP
This report includes the following information:
Column Description
SKU
location.
ordered them.
TIP
SAFETY_STOCK
uncertain.
317

Column Description
Stocking Point Name Stocking Point Name.
Start Date Start date.
End Date End date.
Material Cost Material cost.
Transportation Cost Transportation cost.
Processing Cost Processing cost.
Inventory Holding Cost Inventory holding cost.
Order Admin Cost Order administration cost.
Handling Cost Handling cost.
Other Cost Other cost.
Total Estimated Cost Total estimated cost.
Demand Processor
This out-put report provides the following demand information:
Column Description
BiasRatio
processing.
CV
RiskPoolFactor
Analysis Mechanism
318
SIM
Column Description
LOCATION_NAME Location name.
LOCATION_ATTRIBUTE_NAME Location attribute name.
LOCATION_THRESHOLD_VALUE Location threshold value.

ITEM

PERIOD

point data.
Publishing Queue (SIM)
The Reports menu lets you view reports sent by SIM to the Publishing Queue. Use this feature to access all published
reports.

report or save it.

319
report or save it.
Related Topics:
Administration
Supply Intelligence Privilege Definitions
Access Supply Intelligence Module
SIM module settings

The Supply Intelligence module contains the configuration settings used by the SIM utility to perform its functions. You
can access this module by doing the following:
1. Log on to the SIM application.
3. Select Supply Intelligence from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate Supply Intelligence parameters.
Lead Time CV Cap Maximum CV for lead time.
Lead Time Exclude Outliers Whether to exclude outliers?
Lead Time Historical Data Lead time historical data horizon to use for CV computation. If not
Horizon
found, it defaults to the scenario historical data horizon. Caps at the scenario
historical data horizon. If not found, it defaults to the scenario historical data
horizon. Caps at the scenario historical data horizon.
Lead Time Min Data Point Minimum number of historical observations required to carry on CV
320
SIM
Count calculation.
Lead Time Order Processing Maximum value for order processing time mean on a supply path. Infinity
Mean Cap
if not found. Infinity if not found.
Lead Time Outlier Multiplier Number of standard deviations used to identify outliers.
Lead Time Physical Mean Cap Maximum value for physical lead time on a supply path. Infinity if not
found.
Lead Time Raw Data Log Determine whether to generate the raw input log file. Set it to 'true'
to enable raw input log generation. Infinity if not found.
Related Topics:
321
SLO
Welcome to Service Level Optimization (SLO)
The Service Level Optimization (SLO) module provides a means by which a company can determine its most cost-
efficient set of service levels across all items with external demand, given an overall service level target.
The MIPO application calculates an overall inventory cost for a given product line. If a company has a target service level,
in terms of fill rate, and wishes to minimize the total inventory cost, it will run SLO to optimize the individual service levels
at each customer facing stocking point such that the global service level is maintained but the overall inventory cost is
minimized.
Sample business problem addressed

A company has a diverse portfolio of over 300 products that sell through various channels to a large set of customers. In
order to maintain its position in the market and the satisfaction of its customers, the company needs to achieve a 98.5%
overall service level across all orders. To set inventory targets, the planners need to identify the specific service level
objective for each item, location, and customer combination. Should the planners set all the combinations to 98.5%, use
some type of ABC stratification, or is there a better way?
SLO's approach
The Service Level Optimization (SLO) module is the ideal tool for the difficult problem of finding the right balance between
service and cost. SLO provides optimal service levels for each demand point while respecting targets global service levels
or service cost-revenue tradeoffs.
SLO identifies the optimal service target for each demand point while achieving an aggregate 98.5% service level as well
as maintaining a minimum service level of 90% for each item. Many of the demand points have optimal service levels
below 98.5% and other require service levels above the global objective. It is not surprising that items with higher gross
margins will typically dictate higher service levels. Many other factors also impact the optimal service levels including lead
times, batch sizes, and forecast error. SLO tends to set higher service levels at demand points with lower forecast error,
leveraging these items to achieve the global objective.
Traditional Service Decision Approach Service Level Optimization (SLO)
Sets specific service levels for each item-location in the Optimizes specific service levels for each item-location in
supply chain to meet global service level target, but fails to the supply chain to ensure global service level target by
recognize differences between service-cost relationships in including calculations to minimize inventory and lost
calculations revenues
Models all relevant drivers of inventory requirements such

as:
Classifies items into ABC but can only do so through simple • Lead time and lead time variability
relationships between demand volumes and margins
• Replenishment frequency
• Forecast and forecast error
• Frozen window
Embeds sophisticated search algorithms within enterprise

Utilizes simple search mechanisms
inventory optimization
323
Fit within the SAP Enterprise Inventory and Service-Level Optimization

solution
Service Level Optimization (SLO) is a key component of the SAP Enterprise Inventory and Service-Level Optimization
solution. SLO runs in conjunction with Multistage Inventory Planning & Optimization (MIPO) to optimize item-specific
service levels given the optimal inventory placement generated by MIPO. SLO only requires a few additional data
elements in addition to supply chain data required for inventory optimization:
SLO Inputs SLO Outputs
• Global target service level per item groups

• Optimal service levels for each SKU-location
(optional)
• Lost sales percentage (when applicable)
• Inventory requirements
• Desired service level range (min/max)

• Expected lost revenues
• Margins (when incorporating lost revenues)

• Product availability statistics
Global target service level and lost sales percentage are optional inputs. When the objective is to minimize the total
inventory cost, a global target is needed to ensure reasonable service. If the desired objective is to minimize inventory
costs plus revenue loss, the impact of lost sales plays the role of the global target service level, and SLO can find the best
mix of service levels that minimize the total cost.
A company using the SLO module was able to determine the optimal global service level target by analyzing the tradeoffs
between inventory cost and lost revenues. In this case, targeting a global service level of 98% was the right mix between
cost and service for this company.
Benefits
Based on analysis of customer data, utilizing SLO will provide a 5%-7% additional reduction in inventory compared to
setting uniform service level targets across all items or even ABC type stratification schemes. Additionally SLO provides a
quantitative, systematic, and integrated method to establish and manage service level targets.
Features
SLO Features Overview
The SLO application lets you optimize your supply chain target service level for each stocking-point with external demand
forecast so as to guarantee the overall global target service level. The following features are available in SLO:
• Managing SLO Data Sets
• Editing SLO Data
• Analyzing SLO Data
• Creating SLO Reports
324
SLO
Managing Data Sets

Importing Data
Importing a MIPO Scenario (SLO)
The Import Scenario window allows you to load a MIPO user scenario into SLO. If you wish to export the SLO-generated
service levels back to MIPO, you must import a MIPO user scenario rather than the base scenario, as any MIPO base
scenario cannot be edited once it has been loaded into MIPO.
To import a MIPO scenario

1. Click Data Set > Import Data Set to open the Import Scenario window.
2. From the list of MIPO scenarios, click the radio button associated with the scenario you wish to import into SLO.
3. Click OK. You will be required to confirm your request.
4. From the Confirmation dialog box, click OK. The Manage Scenarios window appears.
5. Use the Manage Scenarios window to name the SLO scenario and set configuration parameters used by the
SLO Import Processor.
6. Click OK. The scenario will be loaded into the SLO module. When completed, you will see a message stating
"Imported Scenario successfully."
The Scenario Import History table is updated to include information based on the selected MIPO scenario, including the
status of the import process.
Once the selected file is successfully imported into SLO, you will see the status change to "Finished" in the Scenario
Import History table.
Additionally, the Supply Chain and Scenario Selectors will include the names of the SLO data model specified in the file
you imported.

At the bottom of the Import Scenario window, there is a list of Import transactions as logged by SLO. The Import history
list includes the following information:
• MIPO Scenario Name
• SLO Scenario Name
• Start Time (GMT)
• End Time (GMT)
• Status
Note: If you have trouble importing the data set, use the View Alerts feature to determine
if any alerts were generated during the Import process. You can find more information on
SLO alerts here.
Related Topics:
Exporting SLO Scenario to MIPO
Exporting Data
Exporting SLO Scenario to MIPO
The Export Scenario screen allows you to export an optimized SLO scenario to the MIPO source user scenario in order
to re-optimize the MIPO scenario with the SLO target service levels.
325
Note: Exporting scenarios is a user privilege in SLO. You must have privileges both to
export scenarios and to view and modify the specific scenarios you want to export.
To export a SLO scenario to the associated MIPO user scenario:

1. Use the Supply Chain Selector to choose the supply chain containing the SLO scenario you want to export.
2. Use the Scenario Selector to choose the SLO user scenario. Note: The scenario you select must be optimized
before you can export it.
3. Click Data Set > Export Data Set to open the Export Scenario window.
4. Click the Bowse (...) button to open the Select Scenario window.
5. Select the associated MIPO user scenario by clicking its radio button.
6. Click OK.
Note: You can monitor the process of the scenario export using the Scenario Export
History panel at the bottom of the window.
Related Topics:
Importing a MIPO Scenario
Editing SLO Data

Input Data
Editing Stocking Point Static Input Data (SLO)

service level, holding cost percent, and inventory unit cost. You can edit static inputs for one or multiple stocking points in
MIPO.
2. Click Edit > Input Data > Stocking Point Data > Static to open the Edit Stocking Point Data - Static window.

326
SLO
radio button.
Service Level, 0-1 for Holding Cost Percentage) and you attempt to enter an absolute
one (1).
property.
10. Click OK to save your changes. The Edit Stocking Point Input Data - Static window is reloaded and displays
a status message indicating that the data was updated successfully. The columns on the right reflect the
changes you made.
Related Topics:
Inputs for Nodes
Editing Stocking Point Time Varying Input Data (Single Period) (SLO)
327
6. The Edit Stocking Point Input Data - Time Varying (Single Period) window is reloaded and contains the

radio button.
11. Click OK to save your changes. The Edit Stocking Point Input Data - Static (Single Period) window is
Related Topics:
Inputs for Nodes
Editing Stocking Point Time Varying Input Data (Single Node) (SLO)
328
SLO
4. Click the Browse (...) button to open the Node Selector. Use the Node Selector to choose stocking points to
edit.
6. The Edit Stocking Point Data - Time Varying (Single Period) window is reloaded. It contains the stocking
9. The Edit Stocking Point Input Data - Time Varying (Single Node) window opens. It contains the time-varying
properties on the left and each of the periods in the display horizon on the right. Note that the name of the node
you are editing is listed in the Choose Nodes to Edit field near the top of the window.
radio button.
13. Click OK to save your changes. The Edit Stocking Point Input Data - Time Varying (Single Node) window is
reloaded and displays a status message indicating that the data was updated successfully. The window reflects
the change you made for the nodes and all properties and periods you specified.
Related Topics:
Inputs for Nodes
Editing Stocking Point Time Varying Input Data (Single Property) (SLO)
329
6. The Edit Stocking Point Input Data - Time Varying (Single Period) window is reloaded. It contains the
8. The Edit Stocking Point Input Data - Time Varying (Single Property) window opens. It contains the nodes

radio button.
12. Click OK to save your changes. The Edit Stocking Point Input Data - Time Varying (Single Property)
Related Topics:
Inputs for Nodes
Editing Supply Path Data
Editing Demand Stream Data - Static (SLO)
330
SLO
The demand stream is the supply path between the customer-facing stocking point and the customer. The static data
associated with the demand stream includes the desired service level, frozen window, and service time. You can edit
static inputs for one or multiple demand streams in SLO.
To edit static data for demand streams:

2. Click Edit > Input Data > Supply Path Data > Demand Stream to open the Edit Demand Stream Data -
Static window.
selected on the left and all of the editable properties on the right.
radio button.
different value.
one (1).
you made.
Output Data
Editing Stocking Point Static Output Data (SLO)

331
service level, holding cost percent, and inventory unit cost. You can edit static outputs for one or multiple stocking points
in MIPO.
2. Click Edit > Output Data > Stocking Point Data > Static to open the Edit Stocking Point Data - Static
window.
radio button.
one (1).
property.
10. Click OK to save your changes. The Edit Stocking Point Output Data - Static window is reloaded and
Related Topics:
Outputs for Nodes
332
SLO
Editing Stocking Point Time Varying Output Data (Single Period) (SLO)
6. The Edit Stocking Point Output Data - Time Varying (Single Period) window is reloaded and contains the

radio button.
11. Click OK to save your changes. The Edit Stocking Point Output Data - Static (Single Period) window is
Related Topics:
Outputs for Nodes
333
Editing Stocking Point Time Varying Output Data (Single Node) (SLO)
6. The Edit Stocking Point OutData - Time Varying (Single Period) window is reloaded. It contains the stocking
9. The Edit Stocking Point Output Data - Time Varying (Single Node) window opens. It contains the time-
varying properties on the left and each of the periods in the display horizon on the right. Note that the name of
the node you are editing is listed in the Choose Nodes to Edit field near the top of the window.
radio button.
13. Click OK to save your changes. The Edit Stocking Point Output Data - Time Varying (Single Node) window
is reloaded and displays a status message indicating that the data was updated successfully. The window
reflects the change you made for the nodes and all properties and periods you specified.
334
SLO
Related Topics:
Outputs for Nodes
Editing Stocking Point Time Varying Output Data (Single Property) (SLO)
6. The Edit Stocking Point Output Data - Time Varying (Single Period) window is reloaded. It contains the
8. The Edit Stocking Point Output Data - Time Varying (Single Property) window opens. It contains the nodes

radio button.
335
12. Click OK to save your changes. The Edit Stocking Point Output Data - Time Varying (Single Property)
Related Topics:
Outputs for Nodes
Auditing Data Changes (SLO)

The Audit Data Changes feature lets you see what changes were made to specific scenario data, who made specific
changes, and when these changes were made. The Audit Data Changes window can display all changes to Input and
Output data for specific scenarios. You can also filter the display to narrow the list of audit information.
To view the Audit history, click Edit > Audit Data Changes. You will see the Audit Data Changes window, which defaults
to the last audit transaction, if any exists.
From the Audit Data Changes window, you can do the following:
1. Set filters
2. Select a specific audit transaction, including associated component if necessary
3. Compare original data record to modified data record
Filtering Audit records
When setting filters to display Audit data, You can use the following categories:
• Data Type: Defaults to All data. You can select Input data or Output data.
• Audit Date: The default value is Today. You can select Last Five Days, Last Ten Days, Last Thirty Days.
You can also use the Calendar button to select a Date Range.
• Screen: Use dropdown list to view data changes associated with a specific MIPO screen.
• User: Use dropdown list to view data changes associated with a specific MIPO account.
Click any dropdown list to change the filter, and then click Refresh.
Selecting a specific Audit transaction
The Audit Data Changes window lists transaction information, including:
• Date and time when the change was made
• Account name of user who made the change
336
SLO
• Type of change that was made
• Specific MIPO screen used to make the change

To select a specific audit transaction, click its associated radio button.
Note: Certain audit transaction may involve multiple components. This is indicated by an
activated Component dropdown list. Click the Component dropdown list to select
specific component.
The associated records involved with the change appear at the bottom of the screen. You will see two sets of records, the
original and the modified record (yellow background). You can identify the change by comparing the data in the original
record to the modified record.
Adjusting Date periods for specific Audit transaction
You can further filter out unnecessary information by adjusting the Start and End periods.
3. Click OK.
Analyzing SLO Data

Analyzing and Managing Scenarios (SLO)
In SLO, each data set is associated with a user scenario. You can use the Manage Scenarios screen to set specific
configuration parameters before optimizing the SLO data set. After optimization, the user scenario can be analyzed. Its
output data can be updated if necessary, then exported back into the MIPO user scenario from which the data set was
originally derived.
When you apply changes to any SLO scenario, validate, optimize it, and view the new results (or outputs), you are
analyzing a scenario. You manage scenarios by duplicating and deleting them in SLO.
Note: The ability to analyze and manage scenarios is a user privilege in SLO. If you are
not authorized to analyze or manage scenarios, the Analyze > Manage Scenarios menu
Manage Scenario Access feature to add users.
Preparing a SLO scenario for Optimization
If you select a SLO data set and its associated base scenario, you can edit a limited amount of related information, such
as Supply Chain Name, Description, and Owner in the Manage Scenarios window. You can also change default
information in the following fields:
• Scenario Name - Sets the name of the scenario.
• Initialization - Determines if the user specifies values for On Hand (User-specified) or if the value is inferred by
the application (Automatic).
• Minimization Objective - Determines how SLO calculates cost minimizing as part of the objective of achieving
the defined global service level, either “Sum of Safety Stock Holding Costs and Lost Margin” or “Total Safety
Stock Holding Cost”.
• Global Service Objective - Identifies whether or not SLO enforces the global target service level constraint
during optimization.
337
• Global Service Level - Defines the global target used by SLO during optimization.
• Global Service Scope - Specifies whether or not only demand streams with optimized service levels contribute
to the global service level constraint (either Optimized Service Levels or All).
• Service Level Measure - Identifies whether to calculate service level as a function of cost or inventory quantity
(either Dollars or Units).
• Storage Capacity Constraints – Defines whether to use storage capacity limitations during optimization,
based on the Storage Penalty Option and Storage Penalty Cost.
• Storage Penalty Option – When Storage Capacity Constraints are considered, defines what type of
optimization approach to use: either Minimize Impact (new fixed-cost storage location, like a storage tank) or
Minimize Cost (new variable-cost storage location, like warehouse space).
• Storage Penalty Cost – The cost of adding a new storage location.
• Start Period - The period from which calculation must begin for the selected scenario. All horizons are
• Analysis Horizon - The number of periods beyond the start period (in other words, in the future) for which
accurate results are desired.
• Data Horizon - The number of periods of data available for computation (optimization) in SLO.
• Historical Data Horizon - The amount of historical data available for creating a timeline in SLO.
• Distribution Type - Indicates whether SLO uses a normal distribution algorithm or a gamma distribution
algorithm when calculating inventory targets.
• Lost Sales Model - Defines the model SLO uses to compute lost sales: Proportional or Constant.
• Adjust for Bias - Indicates whether SLO will adjust safety stock or forecast requirements as determined by
DIM.
• Demand Timing Uncertainty - Determines whether DIM module outputs are used during optimization
calculations.
• Business Alerts Inputs Stop Severity - Signals SLO to halt the validation process whenever an Input
business alert of the selected severity is generated.
• Business Alerts Outputs Stop Severity - Signals SLO to halt the validation process whenever an Output
business alert of the selected severity is generated.
• Order Delivery with Lead Time Uncertainty – Indicates whether SLO should consider order crossover when
calculating safety stock, ignore order crossover, or use a less comprehensive method of order crossover when
calculating safety stock.
Other fields on the Manage Scenario screen are read-only:
• Scenario Status - Indicates the status of the scenario
• Base scenario modified?- Indicates whether or not changes have been made to the base scenario
• Last Modified - The date and time that the data model was last changed
• Modified By - The user name of the person who last modified the data model
• Base Period - The latest recognized date in the database when historical data transitions to forecast data
338
SLO
• Audit History Exists? - Identifies if input data had been updated in the scenario via a check box indicator.
Perform the following steps to edit information about the base scenario:
1. Use the Supply Chain Selector to select a supply chain. The base scenario is automatically selected in the
Scenario Selector.
3. Change the name of the scenario l by entering a new name in the Scenario Name field, if desired.
pipe (|).
User Selector.
6. Update any of the SLO configuration parameters from the default settings, if necessary.
8. You can now optimize the scenario by using the Tasks menu.
Related Topics:
Creating an SLO User Scenario
Duplicating an SLO User Scenario
Validating an SLO Scenario
Optimizing an SLO Scenario
Upgrading an SLO Scenario
Postprocessing Scenarios
Managing Scenario Access (SLO)
Deleting a Supply Chain or a Scenario in SLO
Deleting Multiple Scenarios (SLO)
339

You can create an SLO user scenario if you wish to run the SLO optimization on a variation of the Base Scenario.
To create a User Scenario:
1. Use the Scenario Selector to select a Supply Chain. The base scenario is automatically selected in the
Scenario Selector.
3. Click TASKS>Create User Scenario.
4. Enter a name for the User Scenario in the Scenario Name field.
User Selector.
7. Change any of the SLO configuration parameters from the default settings.

The Scenario Selector is updated with the new User Scenario.
9. You can now optimize the user scenario by using the Tasks menu.
During this time, you can continue using the SLO application. To determine the status of a
Related Topics:

340
SLO

If there is an existing SLO user scenario to which you want to make small changes, duplicating it and making changes to
the copy can save time and decrease the likelihood that you will introduce errors.
To duplicate a SLO scenario:

2. Use the Scenario Selector to select the SLO user scenario you want to duplicate (you cannot duplicate a base
scenario).
3. Click TASKS > Duplicate Scenario. A dialog box opens and prompts you to enter a name for the copy of the
scenario.
4. Enter a name in the Scenario Name field and click OK.
5. Update any of the SLO configuration parameters from the default settings, if necessary.
The Manage Scenarios window is reloaded and displays a status message indicating that scenario copy was
created successfully. The name you entered for the copy of the scenario is displayed in the Scenario Selector.
The Manage Scenarios window is refreshed, and contains a status message indicating whether the user scenario was
saved successfully. If the scenario was saved successfully, and you are the owner, the Scenario Selector displays the
name of the user scenario you created. In addition, the following fields contain updated information:
• Scenario Status – indicates the status of the scenario; if the user scenario was created successfully, this field
reads “Created, not validated.”
• Base scenario modified – indicates whether or not changes have been made to the base scenario
• Last Modified – the date and time that the supply chain was last changed
• Modified By – the user name of the person who last modified the supply chain
• Base Period – the latest recognized date in the database when historical data transitions to forecast data
• Audit History Exists – identifies if input or output data had been updated in the scenario via a check box
indicator. You can review the specific data changes for the scenario by clicking Edit > Audit Data Changes.
The Scenario Audit Information panel is displayed in the Manage Scenarios window. It displays information about tasks
performed on the selected scenario, including when the scenario was created, the Scenario Status of validation and
computation, and the Date and Time that the tasks occurred.
Related Topics:
341
Validation ensures that data added to the system is compatible with the algorithms used to calculate (or optimize) outputs.

1. Use the Supply Chain Selector to select the supply chain containing the scenario you want to validate.
2. Use the Scenario Selector to select the user scenario that you want to validate.
o If the scenario was validated successfully, you can now optimize it.
o If the scenario contains validation errors, you must correct them before continuing. To determine the
Related Topics:
342
SLO
Before you can view the results (or outputs) of the changes you make to a user scenario, it must be validated and
optimized. Validation ensures that the scenario is structurally and logically consistent with the algorithms used to calculate
outputs. When you optimize a scenario, the data it contains is used by the algorithms to calculate new results based on
Note: The ability to optimize a user scenario is a user privilege. If you are not authorized
to optimize a scenario, the TASKS > Optimize Scenario menu item is disabled in the
Perform the following steps to optimize a scenario:

4. Click TASKS > Optimize Scenario. The Manage Scenarios window is refreshed and displays a status
message indicating that the scenario is being optimized. In addition, the Scenario Audit Information is
updated to reflect the status of the optimization process.
Note: The amount of time it takes to optimize a scenario depends on the quantity of data
it contains. While a scenario is being optimized, the Manage Scenarios window is
optimization, click REFRESH. To cancel optimization, click TASKS > Cancel
Optimization.
5. When optimization of the scenario is complete, the Manage Scenarios window displays a status message
indicating that optimization is complete. In addition, the Scenario Audit Information indicates that optimization
is complete, and whether or not the scenario was optimized successfully:
o If the scenario was optimized successfully, you can now upgrade it.
o If the scenario contains validation errors that prevent it from being optimized successfully, you must
correct them before continuing. To determine the origin of errors, click Alerts > View Alerts to view
the alerts associated with the scenario. For specific information about the incorrect data, identify the
specific alert and view the alert details.
Related Topics:
343
Upgrading Scenarios
After you've created a scenario and it has been validated and optimized, you can upgrade the changes that it contains to
the parent supply chain or to a new supply chain:
• If you upgrade a scenario to the parent supply chain, the parent supply chain is overwritten.
• If you upgrade a scenario to a new supply chain, you create a new supply chain that contains your changes and
has no associated user scenarios.
You can also optimize and upgrade a scenario at the same time, as well as optimize, upgrade and generate reports on
data inputs and outputs.
Note: The ability to create, edit, validate, optimize, upgrade and delete scenarios is a user
privilege. If you are not authorized to analyze or manage scenarios, the Analyze >
Analyze/Manage Scenarios menu item is disabled. In addition, you cannot view any
scenario-related alerts.
Upgrading a Scenario to the Parent Supply Chain
Perform the following steps to upgrade a scenario to the parent supply chain:
5. Click TASKS > Upgrade to Parent Supply Chain. A confirmation dialog opens, prompting you to confirm the
action.
indicating that the scenario was upgraded successfully. Also, the Scenario Audit Information panel contains a
message "Upgraded to Parent Supply Chain" and the name of the scenario you upgraded is no longer
displayed in the Scenario Selector.
Upgrading a Scenario to a New Supply Chain
Perform the following steps to upgrade a scenario to a new supply chain:

344
SLO
5. Click TASKS > Upgrade to New Supply Chain. A confirmation dialog opens, prompting you to confirm the
action.
Note: Upgrading a scenario to a new supply chain is irreversible.
indicating that the scenario was upgraded successfully. In addition, the following fields and selectors are
updated:
o the Scenario Audit Information panel contains a message "Upgraded to New Supply Chain"
o the name of the scenario you upgraded is no longer displayed in the Scenario Selector
o the name of the scenario you upgraded is displayed in the Supply Chain Selector and the base
scenario is automatically selected in the Scenario Selector
o no user scenarios are listed for the new supply chain in the Scenario Selector
Optimizing and upgrading a scenario
You can optimize and upgrade a scenario at the same time after you have validated changes made to the scenario inputs
and/or outputs. The changes made will be upgraded to the parent supply chain, overwriting the previous data.
To optimize and upgrade a scenario to the parent supply chain:
4. Click TASKS > Optimize and Upgrade. A confirmation dialog opens, prompting you to confirm the action.
6. Click OK to optimize and upgrade the scenario. The Manage Scenarios window is reloaded and contains a
status message indicating that the scenario was optimized and upgraded successfully. Also, the Scenario
Audit Information panel contains a message "Upgraded to Parent Supply Chain" and the name of the scenario
you upgraded is no longer displayed in the Scenario Selector.
Optimizing, upgrading, and generating reports
You can optimize and upgrade a scenario at the same time, as well as generate input and output reports, after you have
validated changes made to the scenario inputs and/or outputs. The changes made will be upgraded to the parent supply
chain, overwriting the previous data.
To optimize and upgrade a scenario to the parent supply chain, and generate reports:
345
4. Click TASKS > Optimize, Upgrade and Generate Reports. A confirmation dialog opens, prompting you to
confirm the action.
6. Click OK to optimize and upgrade the scenario, and generate reports. The Manage Scenarios window is
reloaded and contains a status message indicating that the scenario was optimized and upgraded successfully.
Also, the Scenario Audit Information panel contains a message "Upgraded to Parent Supply Chain" and the
name of the scenario you upgraded is no longer displayed in the Scenario Selector.
Note: You can view the input and output reports generated by the application under the
Reports menu.
Related Topics:
Postprocessing SLO Scenarios

After a scenario has been optimized, you can run processors designed to perform specific postprocessing tasks on the
Note: If you select a scenario for postprocessing that has not yet been optimized, it will be
optimized automatically before the optimization process begins.
346
SLO



compute (DIM).
Managing SLO Scenario Access

This feature lets the owners of specific user scenarios to provide access privileges to other application user accounts.
Perform the following steps to provide scenario access to another user account:
1. Use the Supply Chain Selector to select the supply chain containing the base, historical, or user scenario for
which you want to provide access.
scenario owner.
Related Links:
347
Deleting a Supply Chain or a Scenario
scenarios are user privileges. If you are not authorized to delete supply chains and
scenarios, the TASKS > Delete menu items are disabled.

1. Use the Supply Chain Selector to select the supply chain containing the base, historical, or user scenario you
want to delete.

o If you have selected a base scenario, click TASKS > Delete Supply Chain or TASKS > Delete
Historical Scenario.
Note: By default, the application will create a historical scenario whenever a base
scenario is updated. This feature can be turned off clicking Settings > Manage
Module to open the Manage Module Settings window. Then select Analyze
Scenario from the Module dropdown list.
Refer to the “Manage module settings” section in the Installation and Upgrade Guide.
o If you have selected a user scenario, click TASKS > Delete Scenario.
file settings" section in the Installation and Upgrade Guide.
status of a scenario-related process, click Analyze > Analyze/Manage Scenarios to
open the Scenario Management window. Then click REFRESH to view the Scenario
Status.
6. Click OK to delete the supply chain or scenario. The Scenario Management window is reloaded and it displays
a status message indicating that the supply chain or scenario has been deleted.
348
SLO
be deleted by default. You can change the default through the Published Reports
module configuration settings, found under Settings > Manage Module Settings.
Related Topics:
Note: The ability to delete supply chains (base scenarios) and user scenarios are user
privileges. If you are not authorized to delete supply chains and scenarios, the Analyze >
Delete Scenarios menu item is disabled.
To delete multiple scenarios at the same time:

application..
3. Click Delete.
be deleted by default. You can change the default through the
Related Topics:
349
Creating SLO Reports

Input Reports
Stocking Point Static Inputs Report (SLO)
The Stocking Point Static Inputs Report displays inputs for stocking points. The report results are non-interactive and can
be viewed only in a table.
can only view the sections of this report that are expressed in units.
Perform the following steps to create a Stocking Point Static Inputs Report:
3. Click Reports > Input Reports > Stocking Points > Static Data to open the Stocking Point Static Inputs
Report window. By default, the window displays results for all customer facing stocking points.
the Browse (...) button to open the Node Selector. Use the Node Selector to select a different set of nodes for
which to generate the report, if desired.
6. Click Refresh. The Stocking Point Static Inputs Report window is reloaded containing the new results in
selected.
Column Description
350
SLO
Specifies if the service level on the stocking point was calculated by SLO or is an input.
Input Mechanism
Valid values are either Input or Optimized.
Service Time
The cost associated with holding inventory at a stocking location. It is expressed as a

Holding Cost Percentage
percentage of unit cost.
Represents the dollar value of one unit of inventory (expressed in the specified unit of
Unit Cost measure) for a given time at a given stocking location. This cost may include partial
processing (for example, assembly or painting) cost on the raw material or components.
Unit Purchase Cost The inbound acquisition cost or transfer price for each item-location.
The price at which a stocking point sells a unit of a product to its downstream stocking point
Unit Transfer Price
(its customer).
All inventory that is physically available to fill demand, which is all types of stock except
On Hand Inventory pipeline. Specifically, on hand inventory includes cycle, safety, merchandising, and prebuild
(if applicable) stock.
Unusable On Hand Unusable On Hand inventory is the portion of On Hand inventory that should not be
Inventory considered when calculating inventory targets as it cannot be used to satisfy demand.
The standard unit in which the quantity of an item is managed. Examples of units of
Unit of Measure
measure include inches, pounds, gallons, and pallets.
Periods Between Reviews Defines the frequency at which inventory position is reviewed and replenishment decisions
(PBR) are made for an item at a location. PBR is specified in number of periods.
Periods Since Last Review For a given item at a given location is the number of periods since placing a replenishment
(PSLR) order or determining (based on inventory) to not place an order.
Pooling Factor
The maximum number of periods an item can remain at a given node before it becomes
Maximum Ship Life
unusable.
The number of periods over which Weeks of Stock is averaged to determine the Average
Coverage Duration
Safety Stock Coverage.
Schedule Attainment The ratio of between the expected attained production and the scheduled production.
The coefficient of variation of the schedule attainment. For example, if the schedule
Schedule Attainment CV attainment is 0.9 and the coefficient of variation is 0.5, then actual production can expect to
be 90% +/- 45% of the scheduled production.
Storage Capacity Specifies the maximum storage capacity for each item-location.
An optional field used by the Service Level Optimization (SLO) module to define the lower
An optional field used by the Service Level Optimization (SLO) module to define the upper
An optional field used by the Service Level Optimization (SLO) module to define the
Lost Sales Percentage acceptable lost sales percentage to be applied at the minimum service level at the
associated customer-facing stocking point.
351
Inventory Allocation Policy Policy used for calculating TIP; either Priority or Divide.
Processing Cost The per unit cost of manufacturing and assembly for each item-location.
The cost of moving an item from an upstream node to an immediate downstream node for
Transportation Cost
a given inventory stocking location.
Order Administration Cost The per unit cost of administering an order for each item-location.
The cost of material movements within the warehouse, which may include unloading costs,
Handling Cost
breakdown costs, labor costs, and machinery costs
Other Cost Miscellaneous expenses, including taxes and insurance, related to keeping inventory.
Related Topics:
Printing Reports
Comparing Reports
Stocking Point Time Varying Inputs Report (SLO)
The Stocking Point Time Varying Inputs report displays time-varying inputs for stocking points. The report results are
Perform the following steps to create a Stocking Point Time Varying Inputs report:
3. Click Reports > Input Reports > Stocking Points > Time Varying Data to open the Stocking Points Time
Varying Inputs Report (Single Period) window. By default, the window displays results for all customer facing
stocking points.
4. Click the blue pushpin button to generate a report based on a previously saved filter selection. To select a
different set of nodes for which to generate the report, click the Browse (...) button to open the Node Selector.
Select the nodes and click OK to close the Node Selector.
5. Click Refresh. The Stocking Point Time Varying Inputs Report (Single Period) window is reloaded
containing the new results in table format. Note that the node names and time-varying properties are hypertext
links.
6. The Stocking Point Time Varying Inputs report is an interactive report. You can view different facets of the
customize the contents and organization of the Stocking Point Time Varying Inputs report, as follows:
352
SLO
• To view an individual property for all nodes for all periods, click the name of the desired property in
the top row of the report table. The results are displayed in the Stocking Point Time Varying Inputs
Report (Single Property) window for all periods. The property you selected is displayed in the Time
Varying Properties field. You can change the Stocking Points for Report, the Start and End
period for the report, and the Time Varying Properties for the report by clicking the Browse (...)
• To view all properties for an individual node for all periods, click the name of the desired node in the
first column of the report table. The results are displayed in the Stocking Point Time Varying Inputs
Report (Single Node) window for all periods. The name of the node you selected is displayed in the
Stocking Points for Report field. You can change the Stocking Points for Report and Start and
End period for the report, by clicking the Browse (...) button next to each field, respectively.
Note: The default period on which this report is based is determined by the values of
the Base Period and Data Horizon for the scenario.
Column Description
Input Forecast
Demand Mean
Characterizes the difference between forecasted and actual demand. It is a statistical measure of
Input Forecast
Demand Standard
Deviation
Note: This column does not appear for scenarios using DIM outputs as the data associated with
this field will not be used for optimization.
Minimum inventory kept in a retail or customer-facing location. It may be used for showroom or
Minimum Required demonstration purposes, but is typically included in inventory available to meet demand. In
Stock addition, this report displays information about any custom properties created for your supply
chain.
Related Topics:
Printing Reports
Comparing Reports
Output Reports
Master Summary Report (SLO)
The Master Summary Report is a read-only, non-interactive report that displays the overall revenue, supply chain cost,
and the inventory investment by attribute and by target inventory position (TIP) component. Results are generated for
customer facing stocking points and internal stocking points for the chosen supply chain and scenario for the specified
period.
353
are not authorized to create a Master Summary Report.
Note: Results for the Master Summary Report can contain an entry called Unassigned.
This entry is displayed when one or more stocking points is not assigned an attribute
value. The sum of relevant data for all such stocking points is displayed under this
heading.
Perform the following steps to generate a Master Summary report:

Note: The scenario you select must be optimized before you can view the Master
Summary Report.
3. Click Reports > Output Reports > Master Summary to open the Master Summary Report window.
4. Select the desired Start and End periods.
5. Click Refresh. The Master Summary Report window opens containing the report results in a table. You
cannot view this report in a chart.
single period. The contents of the report are updated using the new period you selected.
Revenue
In the Master Summary Report, the overall revenue results include information about the outputs listed in the following
table:
Column Description
Service level is a metric that refers to the probability that demand is met from stock. Average
Average Customer
customer target service level is determined by calculating the end-customer service level using
Target Service Level
the Forecast Mean weighted average of service levels for all customer-facing stocking points.
Average customer service time is determined by calculating the average (not weighted) service
Average Customer time for all customer-facing stocking points. Service time is the number of periods between the
Service Time time an order is placed and the time it must be shipped before a stockout is considered to have
occurred.
The unit sales per period is determined by calculating the sum of forecast mean for all customer
Unit Sales facing stocking points. The sum of unit sales is obtained and then averaged, resulting in a unit
sales average for all periods.
Average Unit Sales Average unit sales price is the average price at which a unit of inventory is sold at customer
Price facing stocking points. It is determined by dividing the total estimated revenue by unit sales.
Total Forecasted The total forecasted revenue is determined as the sum of revenue for each customer facing
Revenue stocking point by multiplying the forecast mean and the unit transfer price for all periods.
The total lost margin is determined as the sum of lost sales for each customer facing stocking
Total Lost Margin
point over all periods.
354
SLO
Supply Chain Cost
In the Master Summary Report, the supply chain cost results include information about the outputs listed in the following
table:
Column Description
Processing Cost
for all periods.
Order Administration this report, it is determined by multiplying the forecast mean and order administration cost for all
Cost stocking points. The sum of the results is obtained for each period, resulting in an average order
periods.
Other Cost
Inventory Investment
In the Master Summary Report, the inventory investment by attribute and by TIP component includes information about
the outputs listed in the following table:
Column Description
Average safety stock is a buffer added to inventory to counteract stockouts when demand and
lead times are uncertain. The amount of safety stock is typically determined based on a specified
service level and the associated variability in demand and lead times. For this report, average
355
safety stock is determined by multiplying the safety stock and the unit cost for all stocking points.
The sum of the results is obtained for each period, resulting in an average safety stock average
for all periods.
Average cycle stock is a component of the average inventory position at a stocking location for a
specified item and a specified period. It corresponds to the portion of average on hand inventory
that exists to cover demand between shipments (replenishments). For this report, average cycle
Average Cycle Stock
stock is calculated by doubling the cycle stock, subtracting from it the forecast mean, dividing that
number in half, and multiplying it with the unit cost for all stocking points. The sum of the results
is obtained for each period, resulting in an average cycle stock average for all periods.
Prebuild stock is inventory built due to capacity constraints in anticipation of future demand. For
Average Prebuild this report, average prebuild stock is determined by multiplying the prebuild stock and the unit
Stock cost for all stocking points. The sum of the results is obtained for each period, resulting in an
average prebuild stock average for all periods.
Merchandising stock is the minimum inventory kept in a retail or customer-facing location. It may
be used for showroom or demonstration purposes, but is typically included in inventory available
to meet demand. It is also known as minimum stock, showroom inventory, or display stock. Note
Average that merchandising stock is different than safety stock. It is an additional component of inventory
Merchandising Stock over and above the safety stock needed to accommodate supply and demand uncertainties. For
this report, average merchandising stock is determined by multiplying the merchandising stock
and the unit cost for all stocking points. The sum of the results is obtained for each period,
resulting in an average merchandising stock average for all periods.
Average pipeline stock represents all inventory for which a replenishment order has been placed
Average Pipeline but not yet received. For this report, average pipeline stock is determined by multiplying the
Stock average physical pipeline stock and the unit cost for all stocking points. The sum of the results is
obtained for each period, resulting in an average pipeline stock average for all periods.
Total Chain Inventory

Sum of Inventory Investments.
Investment
Turns
In the Master Summary Report, the number of turns is determined by dividing the annualized cost of goods sold (COGS)
by the average on hand inventory. An inventory turn is the number of times that a company’s inventory cycles over per
year (or per a specified time period). Lower inventories result in higher inventory turns.
Column Description
Turns Annualized Cost of Goods Sold (COGS) / Average on hand inventory.
Related Topics:
Printing Reports
Comparing Reports
356
SLO
Inventory Summary Report (SLO)
The Inventory Summary report is an interactive report that summarizes the TIP or average inventory and its components,
as a cost, averaged for the selected periods as totals by attribute. The results of the report can be based on all nodes in a
supply chain, or on a selected group of nodes, and can be viewed as a table or in a chart. For this report, average
inventory is determined by adding the average cycle stock, average prebuild stock, average safety stock, average pipeline
stock, and average merchandising stock. The average inventory position on-hand is determined by subtracting the
average pipeline stock from the average inventory total.
Note: Results for the Inventory Summary Report can contain a column named
Unassigned. This entry is displayed when one or more stocking points is not assigned an
attribute value. The sum of relevant data for all such stocking points is displayed under
this heading.
Perform the following steps to create an Inventory Summary Report:

Summary Report.
3. Click Reports > Output Reports > Inventory Summary to open the Inventory Summary Report window. By
default, the window displays results for all stocking points.
single period.
6. Click Refresh. The Inventory Summary Report window is refreshed containing the report results in a table.
Note that the text entries displayed in the first row (stages, by default) are hypertext links.
7. The Inventory Summary report is an interactive report. You can view the results for the nodes in each stage by
clicking the hypertext link for the desired stage. For example, if a set of nodes in your supply chain are assigned
the attribute value "Supplier", the Inventory Summary report contains a stage named "Supplier" in the first row.
If you click this link, you see inventory summary results for all supplier nodes only.
8. To return to the Inventory Summary Report main window, click BACK.
9. Click SHOW CHART to view the results in a chart. The Inventory Summary report opens in a separate window,
in chart format.
Related Topics:
357
Printing Reports
Comparing Reports
Stocking Point Static Outputs Report (SLO)
The Stocking Point Static Outputs Report displays static outputs for stocking points. The report results are non-interactive
and can be viewed only in a table.
Perform the following steps to create a Stocking Point Static Outputs Report:
Static Outputs Report.
3. Click Reports > Output Reports > Stocking Points > Static Data to open the Stocking Point Static Outputs
Report window.
5. Click Refresh. The Stocking Point Static Outputs Report window is reloaded containing the new results in
Column Description
Service level is a metric that refers to the probability that demand is met from stock.
Calculated service level is the service level calculated by MIPO. MIPO determines optimal
Calculated Service Level
service level for each inventory stocking location by using the maximum of the calculated
service level and the user-specified service level.
Non-stockout Probability The probability that the item will be available at the customer-facing stocking point.
times are uncertain.
Coverage Average Safety Stock Coverage is determined by averaging Weeks of Stock over a number
of periods, called the Coverage Duration. Weeks of Stock is the number of periods of
forward expected demand that can be met by the current inventory.
Effective lead time represents the first initial periods during which no changes can be made
Effective Lead Time
to the planned receipts for a given stocking point. These periods can be considered a
“frozen” horizon. Effective lead time is calculated based on lead time, lead time standard
358
SLO
deviation, and reliability inputs for all the incoming supply paths of a stocking point.
The end horizon is the last period deemed as having reliable output data throughout the
End Horizon
supply chain.
Implied Initial On Hand The implied initial on hand value for each forecast period.
Modified Service Time is an output calculated on each supply path (and displayed on that
Modified Service Time path's upstream node) that shows the Customer Service Time input adjusted and
propagated upstream.
This value identifies which period is the first with valid safety stock for the associated
stocking point.
Average Lost Demand average lost sales value for each customer-facing stocking point (averaged over good
periods).
Average Forecast Mean average forecast value for each customer-facing stocking point (averaged over good
periods).
Average Forecast CV average forecast error CV value for each customer facing stocking point (averaged over
good periods).
Average Safety Stock average safety stock value for each customer-facing stocking point (averaged over good
periods).
Effective Lost Sales Defines the acceptable lost sales percentage to be applied at the minimum service level at
Percentage the associated customer-facing stocking point.
Sequestration Flag Defines whether the sequestration flag is set for the stocking point.
Related Topics:
Printing Reports
Comparing Reports
Outputs for Nodes
Stocking Point Time Varying Outputs Report (SLO)
The Stocking Point Time Varying Outputs Report is an interactive report that displays time-varying outputs for stocking
points. The results can be viewed only in table format.
359
Perform the following steps to create a Stocking Point Time Varying Outputs report for a single period:
Time Varying Outputs Report.
3. Click Reports > Output Reports > Stocking Points >Time Varying Data to open the Stocking Point Time
Varying Outputs Report (Single Period) window. By default, the window displays results for all stocking
points.
5. Click Refresh. The Stocking Point Time Varying Output Reports (Single Period) window is reloaded
containing the new results in table format. You cannot view this report in a chart. Note that the node names and
time-varying properties are hypertext links.
6. The Stocking Point Time Varying Output report is an interactive report. You can view different facets of the
customize the contents and organization of the Stocking Point Time Varying Output report, as follows:
• To view an individual property for all nodes for all periods, click the name of the desired property in
the top row of the report table. The results are displayed in the Stocking Point Time Varying
Outputs Report (Single Property) window for all periods. The property you selected is displayed in
the Time Varying Properties field. You can change the Stocking Points for Report, the Start and
End period for the report, and the Time Varying Properties for the report by clicking the Browse (...)
• To view all properties for an individual node for all periods, click the name of the desired node in the
first column of the report table. The results are displayed in the Stocking Point Time Varying
Outputs Report (Single Node) window for all periods. The name of the node you selected is
displayed in the Stocking Points for Report field. You can change the Stocking Points for Report
and the Start and End period for the report by clicking the Browse (...) button next to each field,
respectively.
Note: The default period on which this report is based is determined by the values of
the Start Period and End Horizon for the scenario.
Column Description
Forecast Demand
Mean
Forecast Demand
The difference between forecasted and actual demand.
Standard Deviation
Safety Stock Buffer added to inventory to counteract stockouts when demand and lead times are uncertain.
360
SLO
One component of the average inventory position at a stocking location for a specified item and a
Cycle Stock specified period. It corresponds to the portion of average on hand inventory that exists to cover
The minimum inventory kept in a retail or customer-facing location. It may be used for showroom
Merchandising Stock
or demonstration purposes, but is typically included in inventory available to meet demand.
Expected On Hand Expected inventory that is physically available to fill demand, which is all types of stock except
Stock pipeline.
Physical Pipeline A subset of total pipeline stock and includes all inventory in the supply chain that is currently
Stock being moved from one location to another.
Component of target inventory position and is based on the total lead time and includes all orders
Total Pipeline Stock from the time that they are created until the time they are actually received by the location that
has ordered them.
Target inventory position (TIP) is the calculated optimal replenishment policy parameter defined
Target Inventory for each stocking point for each review period. A TIP replenishment policy calls for a stocking
Position point to periodically (every PBR periods) compare its TIP to its inventory position and place
enough orders (in multiples of the batch size) to bring its inventory position up to or above its TIP.
On Hand Stock
The number of periods covered by the current on hand stock value.
(Periods)
Shipment quantities on a path for a given period, that are expected at the end stocking point in
Planned Receipts
that period, assuming deterministic lead times and service times in response to planned orders.
Safety Stock (Periods) The number of periods covered by the current safety stock value.
Unshifted Safety Stock The amount of unshifted safety stock units associated with specific stocking point data.

The number of periods covered by the current unshifted safety stock value.
in periods
Unshifted
The amount of unshifted merchandise stock units associated with specific stocking point data.
Merchandise Stock
Backlog Safety Stock Backlog safety stock associated with specific stocking point data.
Lost Sales Represents lost sales associated with a stocking point for each period of the data horizon.
Additional Storage Specifies whether any additional storage capacity is required for an item at a location during the
Capacity specified time period.
Production Quantity The amount of a given item to be produced over a specific time period.
A calculated threshold used in consumption-based production planning to trigger replenishment

Reorder Point of the associated item whenever the total amount of onhand stock and outstanding planned
receipts drops below the reorder point.
Represents the on hand inventory level at which manual intervention or monitoring will be needed
Priority Level for service class differentiation. When this level is reached, demand can no longer be served as
First-come, First-served.
361
Related Topics:
Outputs for Nodes
Printing Reports
Comparing Reports
Demand Stream Static Outputs Report (SLO)
The Demand Streams Static Outputs Report displays the outputs calculated by the SLO module associated with the
selected scenario's demand streams.
Perform the following steps to create the Demand Streams Static Outputs Report:
Note: The scenario you select must be optimized before you can view the Key Output
Audit Report .
3. Click Reports > Output Reports > Demand Streams to open the Demand Streams Static Outputs Report
window.
4. The Demand Streams for Report filter defaults to All Restricted Demand Streams. Click the associated [...]
button to use the Demand Stream Selector to select a specific demand stream.
5. Click REFRESH.
The Demand Streams Static Output Report displays the results in a tabular format. The following information is included in
the report:
Column Description
Service level is a metric that refers to the probability that demand is met from stock. Calculated
Calculated Service service level is the service level calculated by MIPO. MIPO determines optimal service level for
Level each inventory stocking location by using the maximum of the calculated service level and the user-
specified service level.
Calculation A demand stream specific output that specifies how the service level on the demand stream was
Mechanism calculated. Valid values are either Input or Optimized.
Non-stockout
The probability that the item will be available at the customer-facing stocking point.
Probability
Average Lost An optional field used by the Service Level Optimization (SLO) module to define an average lost
Demand sales value for each customer-facing stocking point (averaged over good periods).
Average Forecast An optional field used by the Service Level Optimization (SLO) module to define an average
Mean forecast value for each customer-facing stocking point (averaged over good periods).
An optional field used by the Service Level Optimization (SLO) module to define an average
Average Forecast CV
forecast error CV value for each customer facing stocking point (averaged over good periods).
Effective Lost Sales Defines the acceptable lost sales percentage to be applied at the minimum service level at the
Percentage associated customer-facing stocking point.
362
SLO
Related Topics:
Printing Reports
Comparing Reports
Published Reports (SLO)
Published Reports (SLO)
The SLO Reports menu allows you to select and export flat files containing different types of data. Grouped by Inputs or

validated and optimized in SLO. Unless you select an alternative supply chain and/or scenario, the Published Reports
feature will automatically select the default supply chain and associated base scenario. If the published report you export
contains outputs, the scenario you select must be validated and optimized in SLO.
When you export a published report, SLO generates a text file containing the specific data which is copied to a directory
extension.
report.
path name. Changes to the destination directory apply to all SLO users who have
and Upgrade Guide.
363
Note: A published report whose Status is In Progress cannot be selected or

submitted for exporting. You can only select and export a published report if it had not
yet been exported or when its Status is Finished.
• User Name of the SLO user who exported the file
Related Topics:
Viewing Privileges
Published Reports Details (SLO)
Data Loading Errors
Items Master Data

Aggregated TIP
364
SLO
Demand Processor

Column Description
SKU
location.
RiskPoolFactor
DemandForecast
horizon.

DemandError

Data Loading Errors

Column Description
Data Loading Start

Date/Time
365
Items Master Data

information:
Column Description

Column Description

366
SLO
Column Description
SKU
location.

Column Description
367
TIPUnits
demand.
another.
ForecastStdDev
AIPUnits
368
SLO


LostSales
horizon.
AIPCosts
point data.
LostMargin
specified period.

369

Column Description
Processing Cost
for all periods.
Order Admin Cost
periods.
Other Cost
Average Order
Quantity
Aggregated TIP
370
SLO
aggregated by dummy node. This report includes the following information:
Column Description
SKU
location.
ordered them.
TIP
SAFETY_STOCK
uncertain.

Column Description
Processing Cost
for all periods.
for all periods.
371
Order Admin Cost
periods.
Other Cost
Demand Processor
This output report provides the following demand information:
Column Description
BiasRatio
processing.
CV
RiskPoolFactor
Analysis Mechanism
Column Description
372
SLO

ITEM

PERIOD

point data.
Publishing Queue (SLO)
The Reports menu lets you view reports sent by SLO to the Publishing Queue. Use this feature to access all published
reports.

report or save it.

report or save it.
Related Topics:
373
Administration
SLO Privilege Definitions
Access to the SLO Module
Access SLO Module alerts
SLO Preference Definitions

View Global Service Objective Out of Range alerts
View Stocking Point Lost Sales Percentage Null or Negative alerts
View Invalid Customer-facing Stocking Point Unit Cost alerts
View Customer-facing Stocking Point Inventory Unit Cost Out of Range alerts
View Max Service Level < Global Service Objective alerts
View Min Service Level > Global Service Objective alerts
View Customer-facing Stocking Point is Non-stocking Node alerts
Email Global Service Objective Out of Range alerts
Email Stocking Point Lost Sales Percentage Null or Negative alerts
Email Invalid Customer-facing Stocking Point Unit Cost alerts
Email Customer-facing Stocking Point Inventory Unit Cost Out of Range alerts
Email Max Service Level < Global Service Objective alerts
Email Min Service Level > Global Service Objective alerts
Email Customer-facing Stocking Point is Non-stocking Node alerts
SLO module settings

The SLO module contains the configuration settings used by SLO to perform its functions. You can access this module by
doing the following:
1. Log on to the SLO application.
3. Select Service Level Optimization from the dropdown list.
4. Scroll through the configuration list and fill out the appropriate SLO parameters.
374
SLO

Delta threshold The percentage change on the value of the global target objective between two
consecutive iterations is evaluated by SLO in each iteration. If the corresponding
value is smaller than the predefined threshold, the default being 1e-6, the SLO
computation will stop. Default: 1e-6
Gamma Delta Service Level When gamma distribution is used to model demand for the MIPO scenario, SLO
performs a service level conversion based on the value defined in this parameter.
Default: 0.00001
Initial Omega IThe initial value of the predefined threshold used by SLO to determine the its
searching step sizes. Value must be > 0. Default: 1024
Initial Solution Search Factor The scale factor used to determine the step size in search of the first feasible
solution. The default value is 0.5.
Initial Solution Search Iterations The number of iterations for which to apply the initial solution search scale factor to
determine step size in search of the first feasible solution. Once this limit is
reached, a scale factor of 1 is applied. The default value is 4.
Maximum Alerts Consolidate alerts of a specific type upon reaching this limit. Value must be > 0.
Default: 500
Maximum Iterations Maximum MIPO iterations to compute. Value must be > 0 and <= 200. Default: 200
Note: If a SLO scenario contains less than 20 customer facing nodes, the SLO
module will automatically run 5.000 iterations regardless of this setting value.
Normal Delta Service Level The small perturbation on the fill rate. Value must be > 0. Default: 0.0001
Omega Scale Factor The scale factor used by SLO to reduce searching step sizes. Value must be > 1.
Default: 2
Omega threshold The threshold that is used to determine the SLO searching step sizes. Value must
be > 0 and < 0.01. Default: 1e-6
Percentage Change Percentage change - Value must be > 0 and < 0.01. Default: 1e-8
Validation Threads Number of threads that will be doing validations. Typically it should be set to the
number of CPUs the database computer is running. If empty it will use as many
threads as CPUs are available on the application server.
Related Topics:
SLO scenario settings

The SLO scenario module contains the scenario settings used by SLO as default parameters for any setting not defined in
the data set. You can access this scenario module by doing the following:
1. Log on to the SLO application.
3. Select Service Level Optimization from the dropdown list.
375

Parameter Name Description Notes
Adjust for Bias Enables SLO to apply DIM-calculated bias adjustment to Options: Forecast, None,
either the scenario safety stock, forecast, or not apply them at Safety Stock
all.
Default = None
Analysis Horizon Defines the number of periods beyond the start/base period Default: 52
(future data) requred for accurate SLO results.
Business Alerts On Sets the severity level needed to shut down the SLO input Options: Disabled, Error,
Inputs Stop Severity validation process. Fatal Error,
Informational, None,
Warning
Default: Error
Business Alerts On Sets the severity level needed to shut down the SLO output Options: Disabled, Error,
Outputs Stop Severity validation process. Fatal Error,
Informational, None,
Warning
Default: Error
Data Horizon Defines the number of periods of data available for Default: 52
optimization in SLO.
Demand Timing Select Consider when using DIM outputs for SLO scenarios Options: Consider,
Uncertainty with intermittent demand streams. Ignore
Default: Ignore
Distribution Type Select Gamma distribution to improve the accuracy of Options: Gamma,
inventory targets for items with lumpy demand, items with Normal
intermittent demand, or slow-moving items.
Default: Normal
Forecast Source Defines the source for first-period forecast data during non- Options: Net
stocking node handling. Requirements, Planned
Independent
Requirements
Default = Planned
Independent
Requirements
Global Service Level Defines the global target used by SLO to generate service Default: 0.985
level inputs that determine appropriate safety stock for each
inventory item when re-optimized by MIPO.
Global Service Select Yes to have SLO enforce the global target service Options: No, Yes
Objective level constraint during SLO optimization.
Default: Yes
376
SLO
Global Service Scope Determines whether or not demand streams with unoptimized Options: All, Optimized
service levels can contribute to the global service level Service Levels
constraint.
Default: All
Historical Data Horizon Defines the amount of historical data available for creating a Default: 130
timeline in SLO.
Initialization Determines whether the user specifies on hand inventory Options: Automatic,
targets, or SLO automatically calculates those values. User-specified
Default: Automatic
Lead Time Error Determines the weight SLO gives to standard deviation of Default: 1
Multiplier lead time during computation.
Lost Sales Model Defines the model SLO uses to compute lost sales; either Options: Constant,
Proportional or Constant. Proportional
Default: Constant
Multisourced Trimming Defines whether to enable the multisourced trimming rule; Options: Enable, Disable
Rule either Enable or Disable.
Default: Enable
Minimization Objective Determines how SLO calculates cost minimizing as part of Options: Sum of
the objective of achieving the defined global service level. Inventory Holding Cost
and Lost Margin, Total
Inventory Holding Cost,
Total Safety Stock
Holding Cost
Default = Sum of
Inventory Holding Cost
and Lost Margin
Order Delivery with Defines whether SLO considers order crossover, ignores it (in Options: Sequential,
Lead Time Uncertainty favor of the sequential model), or uses a less comprehensive Crossover, Simplistic
model. Crossover.
Default = Crossover
Service Level Defines the global target used by SLO during optimization. Options: Fill Rate, Non-
stockout Probability
Default: Fill Rate
Storage Capacity Determines whether to use storage capacity limitations during Options: Ignore,
Constraints optimization, based on the Storage Penalty Option and Consider
Storage Penalty Cost.
Default = Ignore
Storage Penalty Cost The cost of adding new storage space. If the field is blank, Default = blank (very
cost is assumed to be very expensive. expensive)
Storage Penalty Option When Storage Capacity Constraints are considered, defines Options: Minimize
what type of optimization approach to use: either Minimize Impact, Minimize Cost
Impact (new fixed-cost storage location, like a storage tank)
or Minimize Cost (new variable-cost storage location, like Default = Minimize
377
warehouse space). Impact
Transfer Demand Determines whether or not SLO scenario data processor Options: No, Yes
Processor Outputs outputs get transferred to Data Store.
Default = Yes
Transfer Forecast Determines whether or not SLO scenario forecast data gets Options: No, Yes
transferred to Data Store.
Default = Yes
Transfer Process Points Determines whether or not SLO scenario process point data Options: No, Yes
gets transferred to Data Store.
Default = Yes
Transfer Sales Determines whether or not SLO scenario sales data gets Options: No, Yes
Default = Yes
Transfer Stocking Determines what SLO scenario stocking point data gets Options: All, Inputs,
Points transferred to Data Store. Outputs
Default = All
Transfer Supply Paths Determines what SLO scenario supply path data gets Options: All, Inputs, No
Default = Inputs
Related Topics:
Alerts
SLO Alert Definitions
Max Service Level Less Than Global Service Objective
Min Service Level Greater Than Global Service Objective
Customer-facing Stocking Point is Non-stocking Node
Stocking Point Lost Sales Percentage Null or Negative
Global Service Objective Out of Range
Initial Feasible Solution Not Found
Related Topics:
Filtering Alerts
378
SLO
Managing Alerts
Alerts
379
Data Protection and Privacy

Introduction
Data protection is associated with numerous legal requirements and privacy concerns. In addition
to compliance with general data privacy regulation, it is necessary to consider compliance with
industry-specific legislation in different countries. SAP provides specific features and functions to
support compliance with regards to relevant legal requirements, including data protection. SAP
does not give any advice on whether these features and functions are the best method to support
company, industry, regional, or country-specific requirements. Furthermore, this information
should not be taken as advice or a recommendation in regard to additional features that would be
required in specific IT environments; decisions related to data protection must be made on a
case-by-case basis, taken into consideration the given system landscape and the applicable legal
requirements.
Notification
Note: SAP does not provide legal advice in any form. SAP software supports data protection
compliance by providing security features and specific data protection relevant functions, such as
simplified blocking and deletion of personal data. In many cases, compliance with applicable data
protection and privacy laws will not be covered by a product feature. Definitions and other terms
used in this document are not taken from a particular legal source.
Glossary
Term Definition
Blocking A method of restricting access to data for which the primary business
purpose has ended.
Consent The action of the data subject confirming that the usage of his or her
personal data shall be allowed for a given purpose. A consent functionality
allows the storage of a consent record in relation to a specific purpose and
shows if a data subject has granted, withdrawn, or denied consent.
Deletion The irreversible destruction of personal data.
End of purpose A method of identifying the point in time for a data set when the processing
(EoP) of personal data is no longer required for the primary business purpose.
After the EoP has been reached, the data is blocked and can only be
accessed by users with special authorization (for example tax auditors).
Personal Data Any information relating to an identified or identifiable natural person ("data
subject"). An identifiable natural person is one who can be identified, directly
or indirectly, in particular by reference to an identifier such as a name, an
identification number, location data, an online identifier or to one or more
factors specific to the physical, physiological, genetic, mental, economic,
cultural, or social identity of that natural person.
Purpose A legal, contractual, or in other form justified reason for the processing of
personal data. The assumption is that any purpose has an end that is
usually already defined when the purpose starts.
Residence period The period of time between the end of business and the end of purpose
(EoP) for a data set during which the data remains in the database and can
be used in case of subsequent processes related to the original purpose. At
the end of the longest configured residence period, the data is blocked or
381
deleted. The residence period is part of the overall retention period.

Retention Period The period of time between the end of the last business activity involving a
specific object (for example, a business partner) and the deletion of the
corresponding data, subject to applicable laws. The retention period is a
combination of the residence period and the blocking period.
Sensitive A category of personal data that usually includes the following type of
personal data information:
• Special categories of personal data such as data revealing racial or
ethnic origin, political opinions, religious or philosophical beliefs, or
trade union membership and the processing of genetic data,
biometric data, data concerning health, sex life or sexual orientation
or personal data concerning bank and credit accounts
• Personal data subject to professional secrecy
• Personal data relating to criminal or administrative offenses
• Personal data concerning insurances and bank or credit card
accounts
Where-used A process designed to ensure data integrity in the case of potential blocking
check (WUC) of business partner data. An application's where-used check (WUC)
determines if there is any dependent data for a certain business partner in
the database. If dependent data exists, this means the data is still required
for business activities. Therefore, the blocking of business partners
referenced in the data is prevented.
Read Access Logging

Read Access Logging (RAL) is used to monitor and log read access to sensitive data. Data may
be categorized as sensitive by law, by external company policy, or by internal company policy.
Read Access Logging enables you to answer questions about who accessed particular data
within a specified time frame. Such questions could be:
• Who accessed the data of a given business entity, for example a bank account?
• Who accessed personal data, for example of a business partner?
• Which employee accessed personal information, for example religion?
• Which accounts or business partners were accessed by which users?
From a technical point of view, this means that all remote API an UI structures (that access the
data) must be enabled for logging.
Information Report
Each person has the right to obtain confirmation as to whether or not personal data concerning
him or her are being processed. In SAP Enterprise Inventory and Service-Level Optimization it is
possible to display all information stored about a certain data subject.
382
Index
Erasure of personal data

Simplified Blocking and Deletion
When considering compliance with data protection regulations, it is also necessary to consider
compliance with industry-specific legislation in different countries. A typical potential scenario in
certain countries is that personal data shall be deleted after the specified, explicit, and legitimate
purpose for the processing of personal data has ended, but only as long as no other retention
periods are defined in legislation, for example, retention periods for financial documents. Legal
requirements in certain scenarios or countries also often require blocking of data in cases where
the specified, explicit, and legitimate purposes for the processing of this data have ended,
however, the data still has to be retained in the database due to other legally mandated retention
periods. In some scenarios, personal data also includes referenced data. Therefore, the
challenge for deletion and blocking is first to handle referenced data and finally other data, such
as business partner data.
Deletion of personal data

The processing of personal data is subject to applicable laws related to the deletion of this data
when the specified, explicit, and legitimate purpose for processing this personal data has expired.
If there is no longer a legitimate purpose that requires the retention and use of personal data, it
must be deleted. When deleting data in a data set, all referenced objects related to that data set
must be deleted as well. Industry-specific legislation in different countries also needs to be taken
into consideration in addition to general data protection laws. After the expiration of the longest
retention period, the data must be deleted.
Change Log
Personal data is subject to frequent changes. Therefore, for revision purposes or as a result of
legal regulations, it may be necessary to track the changes made to this data. When these
changes are logged, you should be able to check which employee made which change, the date
and time, the previous value, and the current value. It is also possible to analyze errors in this
way.
383
Index
384
A Attribute Type............................. 11, 13, 15, 19, 26, 191

Attribute value ................ 11, 13, 15, 19, 26, 86, 89, 191
accessing ................................................ 6, 7, 257, 261
Alert .................................................................... 260 Attribute Values list ............................ 11, 13, 15, 19, 26
Alert Type Status History window ........................ 258 Audit History
Alert Types window ............................................. 257 Auditing Data Changes ....................................... 105
Alerts window ...................................................... 261
Import .................................................................... 30 authentication.............................................................. 6
Input ........................................................................ 7 average ........................................................ 1, 182, 232
account .... 6, 7, 274, 276, 277, 278, 279, 280, 282, 283, average cycle stock ................................................. 182
285, 286, 288, 289, 291, 292, 295, 296, 297
data pertaining .................................................... 285 average pipeline stock............................................. 182
action................ 108, 135, 255, 257, 258, 260, 263, 297 average prebuild stock ............................................ 182
Active .............................................................. 257, 260 average safety stock ............................................... 182
address........................................ 6, 274, 279, 280, 282 B

Administrator profile ................................. 276, 289, 292 Base ........................................................ 164, 168, 173
Administrator - Assignees.................... 276, 289, 292 values .................................................. 164, 168, 173
aggregated ......................... 1, 37, 40, 44, 184, 188, 191 base scenario.............................................................. 9
AIP .......................................................................... 232 Base Scenarios 9, 36, 95, 109, 115, 121, 127, 135, 151,
Alert ............................................. 7, 255, 258, 260, 263 210
access ................................................................. 260 batch size .................................................................. 59
Dismissing........................................................... 255
Exporting Alerts ................................................... 264 Before Selected Period ........................................... 108
Hiding .................................................................. 255 Bitmap..................................................................42, 46
Managing ............................................................ 255
open ........................................................ 7, 260, 263 Bmp .......................................................................... 46
SmartOps Alerts ...................................................... 2 BOM ............................................ 44, 77, 91, 93, 95, 96
Suppressing ........................................................ 255
Viewing ............................................................... 263 Business Alerts
Business Alert (activate) ..................................... 237
Alert Definitions ....................................................... 266 Business Alert (define new) ................................ 240
Alert Details window ................................ 255, 261, 263 Business Alert (delete) ........................................ 242
Business Alert (security level) ............................. 238
Alert Settings window....................................... 257, 260 Business Alert (trigger value) .............................. 239
Alert Short Entries.................................... 255, 261, 263 Business Alerts - Defaults .................... 161, 242, 252
Viewing ............................................................... 261 Business Alerts - Editing ..................................... 236
Business Alerts - Managing ................................ 235
Alert Summaries .............................................. 255, 263 Validating Business Alerts (Inputs and Outputs) 140,
Alert Summaries window ......................................... 263 436, 518
Alert Type ........................................ 255, 257, 258, 260 By Item.................................................................... 184
Viewing ....................................................... 257, 260
Alert Type Status History ......................................... 258 C
Viewing ............................................................... 258 Cancel Validation .................................................... 132
Alert Types window .......................................... 257, 258 capacity......... 1, 61, 63, 65, 81, 108, 109, 115, 121, 127
access ................................................................. 257
Case-insensitive ........................................................ 41
Alerts window .................................................. 261, 263
Cell Phone Number .......................... 274, 279, 280, 282
access ................................................................. 261
center ............................................................. 29, 85, 88
analysis ................ 86, 89, 109, 115, 121, 127, 258, 263
CF Stocking Point .............................. 15, 51, 53, 55, 57
Analytics
Analytics.............................................................. 363 chain ........................................................ 7, 9, 115, 151
Analytics Privilege Definitions .............................. 363 CHANGE ......................................................... 274, 280
Analyze............. 109, 115, 121, 127, 132, 134, 135, 151 Change Password window ............................... 274, 280
Analyze Scenarios ........................................... 261, 263 Characteristics .....................................................86, 89
Analyze/Manage109, 115, 121, 127, 132, 134, 135, 151 item .................................................................86, 89
location ............................................................86, 89
application server..................................................... 298
node ................................................................86, 89
assembly ................................................... 1, 37, 93, 95 path .................................................................86, 89
Assigned........................... 276, 286, 288, 289, 291, 292 check box............................... 37, 40, 43, 257, 260, 261
Assigned Users ....................................................... 292 Choose ................................ 37, 55, 57, 63, 77, 81, 263
Assignees ................................................ 276, 289, 292 Destination ........................................................... 81
DISMISS............................................................. 263
Attribute Code.......................................................... 191 Incoming Item ....................................................... 77
385
Outgoing Item........................................................ 77 Customer Facing Stocking Point ............................. 164

Source................................................................... 81 Report ................................................................ 164
Choose File window................................................... 30 Customer Support ....................................................... 7
open ...................................................................... 30
Choose Time Varying Properties ......................... 57, 65 D
Class ............................................................... 261, 263 data 1, 7, 8, 9, 10, 15, 30, 36, 37, 40, 44, 46, 47, 51, 53,
55, 57, 59, 61, 63, 65, 73, 75, 80, 85, 86, 87, 88, 89,
Class, Severity......................................................... 261 93, 95, 108, 109, 115, 121, 127, 132, 134, 164, 165,
Click View/Edit ............................................................. 7 168, 171, 173, 177, 182, 195, 197, 210, 232, 261,
263, 283, 285, 286, 288
Clicking .. 6, 7, 8, 19, 55, 57, 63, 93, 168, 173, 184, 188,
191, 197, 210, 261, 280, 282, 283, 285, 286, 288, Data according .......................................................... 37
289, 291, 292, 296, 297 Data Context ........................................................... 261
Browse ...... 55, 57, 63, 168, 173, 184, 188, 191, 197,
280, 282, 283, 285, 286, 288, 289, 291, 292, 296, Data File ................................................................. 210
297 Data Files................................................................ 210
Incoming ............................................................... 19 application .......................................................... 210
LOGOUT ................................................................. 6 export ................................................................. 210
OK....................................................................... 210
POPUP ................................................................... 8 Data Gateway
PREV .................................................................. 261 Data Gateway Alerts ........................................... 405
REMOVE .............................................................. 93 Data Gateway Preference Definitions ................. 400
RESET ........................................................ 289, 291 Data Gateway Privilege Definitions ..................... 399
View/Edit ................................................................. 7 Delete Gateway .................................................. 374
Extracting a Data Set .......................................... 370
Close ................................................................. 43, 235 Gateway Import .................................................. 373
Display .................................................................. 43 Manage Data Gateway ....................................... 369
Code ........................................................................ 188 Data Input ........................................................ 261, 263
Comments ........................ 258, 263, 292, 295, 296, 297 Data Integrity.................................................... 261, 263
Compare Scenarios ................................................. 229 Data Loader ................95, 115, 132, 261, 263, 286, 288
Compare Scenarios - Data Store ......................... 408
Compare Scenarios - MIPO................................. 229 Data Loading Template ............................................. 30
component ............ 1, 11, 93, 95, 96, 177, 182, 207, 261 Data Output...................................................... 261, 263
Computation .................................................... 261, 263 Data pertaining........................................................ 285

account ............................................................... 285
control......................... 30, 109, 121, 276, 286, 289, 292
Data starting.............................................................. 10
Copyrights ................................................................. 29
Data Static ................................................................ 44
cost.... 1, 51, 73, 75, 164, 165, 168, 171, 173, 177, 182,
184, 188, 191, 197, 204, 207, 232, 286 Data Store
Data Store .......................................................... 407
Create Master ...................................................... 88, 89 Data Store Alerts ................................................ 416
Create Master Data ................................................... 87 Data Store Management ..................................... 407
Data Store Preference Definitions ....................... 412
Create Network Structure .................. 73, 75, 77, 79, 81 Data Store Privilege Definitions .......................... 412
Creating .. 73, 79, 87, 115, 121, 127, 177, 204, 279, 295 Date ................................................. 121, 258, 261, 263
Internal .................................................................. 73 including ...................................................... 258, 263
Items ..................................................................... 87
Master Summary ................................................. 177 Date in Ascending ................................................... 261
Replenishment .................................................... 204 Dealer ....................................................................... 37
Supplier ................................................................. 79
Debugging ....................................................... 261, 263
Csv .......................................................................... 210
DELETE ........................................... 107, 108, 285, 297
Current Attribute ........................................................ 86
delete scenario........................................................ 151
Current Attribute Values............................................. 89
Deleting................................................................... 151
Custom ................................................................ 73, 75 Supply ................................................................ 151
values ............................................................. 73, 75
demand ......... 1, 53, 55, 57, 61, 63, 65, 75, 81, 108, 164
Custom Properties ..................................................... 47
demand mean ........................................ 53, 55, 57, 164
customer.... 7, 43, 44, 51, 53, 55, 57, 73, 75, 77, 79, 80,
86, 89, 107, 108, 164 demand standard deviation ............................ 53, 55, 57
Customer defined ................................................ 86, 89 Descending ............................................................. 261
Customer facing........................................... 75, 80, 107 Description ..... 9, 11, 13, 85, 87, 88, 109, 115, 121, 127,
258, 261, 263
Customer facing locations .......................................... 75
Deselect .................................................................. 292
Customer facing stocking............44, 51, 53, 55, 57, 164 preference .......................................................... 292
386
Index
Deselect checkboxes ............................................... 210 Ending ..... 164, 168, 173, 177, 182, 184, 188, 191, 195,
Destination......................................................... 81, 210 197, 204, 207, 210
Changes.............................................................. 210 Ensure ...................................................................... 37
choose .................................................................. 81 View ..................................................................... 37
modify ................................................................. 210 ENTER... 6, 9, 11, 13, 15, 19, 26, 41, 51, 53, 55, 59, 61,
Destination Node ....................................................... 83 63, 121, 127, 261
details ............................... 184, 188, 191, 255, 261, 263 pressing ................................... 51, 53, 55, 59, 61, 63
Start.................................................................... 121
Diagram ..................................................................... 42
Entered ............................................................ 109, 115
dialog ... 42, 46, 108, 109, 127, 135, 151, 234, 235, 285, Start............................................................. 109, 115
297
Entire ........................................................................ 37
dialog box ........................................................ 108, 285 Viewing ................................................................. 37
DIM error ............................29, 127, 132, 134, 210, 261, 263
Demand Intelligence Alerts .................................. 456
Excel .......................................................... 30, 210, 235
Demand Intelligence Module ............................... 419
Demand Intelligence Preference Definitions ........ 451 Exception Management
Demand Intelligence Privilege Definitions ............ 450 What is Exception Management?........................ 153
DISMISS.................................................. 255, 261, 263 Ex Mgmt Step 1.............................................. 154
choose ................................................................ 263 Ex Mgmt Step 10............................................ 159
Ex Mgmt Step 11............................................ 160
Dismissing ............................................................... 255 Ex Mgmt Step 2.............................................. 155
Alert .................................................................... 255 Ex Mgmt Step 3.............................................. 155
Display................................................................. 40, 43 Ex Mgmt Step 4.............................................. 155
close ..................................................................... 43 Ex Mgmt Step 5.............................................. 156
open ...................................................................... 43 Ex Mgmt Step 6.............................................. 157
Ex Mgmt Step 7.............................................. 157
distribution ..................................... 1, 85, 86, 88, 89, 95 Ex Mgmt Step 8.............................................. 158
distribution center ................................................ 86, 89 Ex Mgmt Step 9a............................................ 158
Ex Mgmt Step 9b............................................ 159
Distribution portion ..................................................... 95
expired password .................................................... 274
dollars ...... 164, 165, 168, 171, 173, 177, 182, 184, 188,
191, 197, 204, 207 export ........................................... 42, 46, 109, 210, 235
Data Files ........................................................... 210
Download ................................................................ 235 Exporting a Network Diagram ............................... 42
downstream ... 51, 53, 55, 57, 59, 61, 63, 65, 73, 77, 79, Exporting Alerts .................................................. 264
80, 95, 164 Published Reports .............................................. 210
Downstream PG-item................................................. 95 Export files .............................................................. 210
Downstream PG-items ............................................... 95 Export History ......................................................... 210
Duplicate ................................................. 127, 282, 296 Export Interface/Model Data Files ........................... 210
Duplicate Scenario................................................... 127 Export Interface/Model Data Files window ............... 210
Exporting Interface Files.......................................... 210
E
edit1, 7, 8, 15, 30, 36, 41, 42, 43, 44, 47, 51, 53, 55, 57, F
59, 61, 63, 65, 73, 75, 77, 79, 80, 81, 83, 85, 86, 87, facing ........................................................................ 75
88, 89, 93, 95, 107, 108, 109, 115, 121, 127, 135,
210, 232, 274, 276, 277, 278, 280, 282, 292 factor......................................................................... 10
stocking points .......................................... 51, 55, 57 Failed ...................................................................... 210
Edit Master Data ............................................ 85, 86, 87 Fatal Error ........................................................ 261, 263
Editing Manufacturing BOM ....................................... 93 FG............................................................................. 11
Editing Manufacturing BOMs ..................................... 93 File Download dialog ............................................... 235
Editing Master.......................................... 85, 86, 88, 89 File Name ............................................ 30, 46, 210, 235
Editing Personal Information .................................... 274 FINISH ........................................................... 73, 75, 81
Editing Supply.......................................... 59, 61, 63, 65 finished good........................................................93, 95
Editing time-varying ........................... 15, 47, 55, 57, 63 First Name ............................................... 279, 280, 282
Editing Your Display Preferences............................... 43 forecast ..... 10, 53, 55, 57, 108, 109, 115, 121, 127, 164
Email ....................................................................... 279 Forecast Demand Standard Deviation ....................... 47
Email address .......................................... 274, 280, 282 Forecast preprocessor ............................................ 442
Enabled checkbox ................................................... 283
Uncheck .............................................................. 283 G
Generate ................................................................. 177
387
Master Summary ................................................. 177 change ........................................ 109, 115, 121, 127
GMT ......................... 109, 115, 121, 127, 210, 261, 263 Input............................. 7, 164, 165, 168, 171, 173, 210
Go To Sign In .............................................................. 6 access .................................................................... 7
INPUT DATA............................................................. 44
Greenwich ....................................................... 261, 263
INPUT DATA menu ................................................... 44
group . 11, 13, 15, 19, 36, 37, 40, 44, 55, 57, 63, 86, 89,
182, 207, 255, 260, 276, 289, 292 Input Data Static ....................................................... 44
uncheck................................................................. 37 Installation............................................................... 210
Group sets ........................................................... 86, 89 Interface File ........................................................... 210
Grouped according .................................................... 37 Interface Files ......................................................... 210
in ........................................................................... 37 application .......................................................... 210
location.................................................................. 37 export ................................................................. 210
H Internal .................................................................73, 81
Creating ................................................................ 73
help ..................................................................... 6, 210
Internal Stocking Point ....................... 15, 51, 53, 55, 57
Hidden ............................................. 255, 258, 261, 263
inventory ...... 1, 29, 40, 51, 73, 75, 85, 87, 88, 177, 182,
HIDE .........................................255, 257, 260, 261, 263 184, 188, 191, 207, 232, 289, 292
Hiding ...................................................................... 255 Inventory Item ......................................................... 184
Alert .................................................................... 255
Inventory planning ................................................. 1, 29
hierarchy.......................................................... 286, 292
inventory position ............................................. 182, 232
History ....................................................................... 28
Inventory Summary ................................................. 182
holding cost ............................................................... 51
Inventory Summary Report .............................. 182, 207
Homepage ................................................................... 7
Inventory Summary Report window ......................... 182
horizon10, 55, 57, 63, 65, 108, 109, 115, 121, 127, 164,
168, 173, 177, 182, 184, 188, 191, 195, 197, 204, IT 210
207, 258, 263 Item Attribute............................................................. 11
Horizon Exceeds End ...................................... 258, 263 Item Code ................................................................. 11
Hyperlink ................................................................. 261 Item Report ............................................................. 184
Hyperlinks .................................... 7, 55, 57, 63, 65, 261 Item Report window ................................................ 184
Item Selector . 11, 15, 19, 37, 73, 75, 77, 80, 85, 93, 184
I
Items .. 11, 15, 19, 37, 40, 73, 75, 77, 80, 85, 86, 87, 89,
icon........................... 61, 63, 65, 73, 75, 77, 79, 81, 255
93, 184
IE 6 characteristics..................................................86, 89
Import ........................................................................ 30 Creating ................................................................ 87
Access .................................................................. 30 open ..................................................................... 93
use ........................................................................ 30 Report ................................................................ 184
Use ............................ 11, 73, 75, 77, 80, 85, 93, 184
Import - Click Import .................................................... 7 Viewing ................................................................. 37
Import Data Set ......................................................... 30 Items list......................................................... 11, 15, 19
Import Data Set window ......................................... 7, 30 Items window .......................................................85, 87
In Ascending ............................................................ 261
L
In contrast ........................................................ 109, 121
Last Modified.................................... 109, 115, 121, 127
In Microsoft Excel .................................................... 235
Last Name ............................................... 279, 280, 282
In progress............................................................... 210
Layout ..................................................................41, 43
Inactive .................................................... 255, 261, 263
lead ....................................................................... 1, 59
Including .......................................................... 258, 263
Date ............................................................ 258, 263 lead time ................................................................... 59
Incoming .............................................................. 19, 93 length ......................................... 6, 10, 55, 63, 108, 109
clicking .................................................................. 19 level ..................................... 1, 132, 276, 286, 289, 292
PG-item ................................................................. 93
PG-items ............................................................... 93 list 9, 10, 11, 13, 15, 19, 26, 37, 55, 57, 65, 86, 108,
109, 115, 121, 127, 135, 210, 255, 257, 258, 260,
Incoming Items .................................................... 77, 80 261, 263, 276, 280, 282, 283, 285, 286, 288, 289,
checkbox ............................................................... 80 291, 292, 296, 297
choose .................................................................. 77
List contains ............................................................ 261
Informational .................................................... 261, 263
loadset ...................................................................... 30
Initialization ..................... 51, 73, 75, 109, 115, 121, 127
388
Index
location 1, 13, 15, 19, 36, 37, 40, 41, 44, 73, 75, 77, 79, Microsoft Corporation ................................................ 29
80, 85, 86, 88, 89, 115, 164, 188, 191 Microsoft Excel........................................................ 235
characteristics ................................................. 86, 89
grouped according................................................. 37 Microsoft Internet Explorer .......................................... 6
location attribute ........................................................ 13 Microsoft Paint .......................................................... 42
Location Codes .................................................. 13, 188 Microsoft Windows ...................................................... 6
location selector .. 13, 15, 19, 73, 75, 77, 79, 80, 85, 188 minimize........................................................... 1, 9, 233
lock .......................................................... 255, 261, 263 MIPO 1, 6, 7, 8, 9, 10, 11, 13, 15, 19, 30, 36, 37, 40, 43,
47, 51, 53, 55, 57, 59, 61, 63, 65, 73, 75, 77, 79, 80,
log6, 7, 30, 115, 277, 286, 288, 289, 291, 292, 295, 296 81, 83, 86, 87, 88, 89, 93, 95, 108, 109, 115, 121,
log files .................................................................... 298 127, 132, 134, 135, 151, 164, 165, 168, 171, 173,
log out 6, 7, 30, 115, 277, 286, 288, 289, 291, 292, 295, 177, 182, 184, 188, 191, 197, 204, 207, 210, 232,
234, 235, 261, 263, 274, 276, 277, 278, 283, 286,
296
288, 289, 291, 292, 295, 296
logging ......................................................................... 6
MIPO Alerts............................................................. 266
login............................................................................. 6
MIPO application ....................................................... 95
logistics............................................................ 289, 292 new values ........................................................... 95
logout .......................................................................... 6 MIPO application in ..................................................... 6
clicking .................................................................... 6 URL ........................................................................ 6
Missing On Hand.................. 73, 75, 109, 115, 121, 127
M
Mixed ...................................................................... 260
management 7, 51, 73, 75, 81, 108, 109, 115, 121, 127,
132, 134, 135, 151, 276, 289, 292 model ........................51, 53, 55, 57, 73, 77, 79, 80, 210
Managing................................................................. 255 Modified By ...................................... 109, 115, 121, 127
Alerts ................................................................... 255 Modify ........................................................ 41, 210, 280
Managing Scenarios ................................................ 109 Destination ......................................................... 210
user .................................................................... 280
Manufacturing ...................................................... 37, 93
Module Settings ............................................... 299, 323
Manufacturing BOM ....................................... 44, 94, 96 Settings-Analyze Scenarios ................................ 325
Manufacturing Out STAGE ........................................ 37 Settings-Business Alerts ..................................... 326
Settings-Compare Scenario ................................ 413
Manufacturing window ............................................... 93
Settings-Dashboard ............................................ 363
Master ............................................. 85, 86, 88, 89, 177 Settings-Data Management ................................ 328
Master Summary ..................................................... 177 Settings-Data Store ............................................ 414
create .................................................................. 177 Settings-DIM ....................................................... 451
generate .............................................................. 177 Settings-Export Scenario .................................... 329
view..................................................................... 177 Settings-Gateway Data Connector ...................... 402
Settings-Gateway Data Loader ........................... 403
Master Summary Report .................................. 177, 232 Settings-Load Set Translator .............................. 330
Master Summary Report window ............................. 177 Settings-Network Visualization............................ 338
Settings-Processor Management ........................ 338
materials ........................... 59, 61, 63, 65, 81, 83, 93, 95 Settings-Published Reports ................................ 343
maximize ............................................... 1, 8, 9, 10, 233 Settings-Publishing Queue ................................. 350
Settings-Remote File Manager ........................... 351
Maximizing Your Work Area......................................... 8
Settings-SIM ....................................................... 477
Maximum ................................................. 61, 63, 65, 81
month ......................................................... 10, 115, 210
value ................................................... 61, 63, 65, 81
More Info................................................................. 235
MDF ........................................................................ 210
Mulitstage Inventory Planning ..................................... 1
mean . 29, 109, 115, 121, 127, 164, 210, 261, 263, 286,
292 multistage ............................................................. 1, 29
mean demand .......................................................... 164
N
measure .......................................... 85, 87, 93, 95, 109
Unit ..................................................... 85, 87, 93, 95 name 6, 9, 11, 13, 15, 19, 26, 30, 37, 41, 42, 43, 46, 55,
57, 63, 65, 73, 75, 77, 79, 80, 81, 83, 87, 88, 89,
menu 7, 9, 30, 40, 44, 47, 51, 53, 55, 57, 59, 61, 63, 65, 109, 115, 121, 127, 135, 151, 168, 173, 182, 184,
73, 75, 77, 79, 87, 89, 109, 115, 121, 127, 132, 134, 191, 197, 210, 233, 234, 235, 257, 258, 260, 261,
135, 151, 210, 255, 260, 261, 276, 277, 278, 280, 263, 276, 277, 278, 279, 280, 282, 283, 285,
282, 283, 285, 286, 288, 289, 291, 292, 296, 297
286,鳈288, 289, 291, 292, 295, 296, 297
Menu Selection .......................................................... 47 reports include ..................................... 109, 234, 235
merchandising stock ................................................ 182 Scenario Selector displays ........................... 121, 127
Selector displays ................................................ 115
Microsoft .................................................................... 29
Named smartops ..................................................... 285
Microsoft Access...................................................... 210
Named Unassigned................................................. 182
389
Names beginning ....................................................... 41 on-hand inventory ................................................... 182

navigate ....................................................................... 7 online .................................................................... 7, 29
navigating ...................................................... 7, 30, 263 online help ............................................................ 7, 29
network .... 1, 7, 8, 36, 37, 40, 41, 42, 43, 44, 46, 51, 53, Open .................................. 7, 30, 43, 93, 235, 260, 263
55, 57, 73, 75, 77, 79, 80, 81, 83, 89, 107, 108, 109, Alert ......................................................... 7, 260, 263
121, 127, 210, 286, 288 Alert Manager ......................................................... 7
Network Diagram ................................................. 42, 46 Choose File window.............................................. 30
Display ................................................................. 43
Network Diagram Load ........................................ 36, 37 Item ...................................................................... 93
Network Display ......................................................... 43 operations ................................................ 235, 289, 292
network selector......................................................... 40 optimization .... 1, 9, 10, 29, 40, 109, 115, 121, 127, 134,
Network Structure .... 73, 75, 77, 79, 80, 81, 83, 89, 107, 261, 263, 286, 288
108 Optimize................................... 115, 121, 127, 134, 135
Network View............................................................. 37 Optimize Scenario ................................................... 134
Network View selector ............................................... 37 Orientation ................................................................ 43
Network Visualization....................................... 286, 288 Other Phone Number ....................... 274, 279, 280, 282
Network Window ........................................................ 44 Outbound Interface ................................................. 210
new scenario ..................................................... 30, 127 Outgoing ..............................................................19, 93
New values ................................................................ 95 PG-item ................................................................ 93
MIPO application ................................................... 95 Outgoing Item ......................................................77, 80
NEXT ..................................................... 73, 75, 81, 261 choose.................................................................. 77
node .. 1, 7, 8, 15, 19, 36, 37, 40, 41, 42, 43, 44, 46, 47, Output ............... 182, 184, 188, 191, 195, 197, 207, 210
51, 53, 55, 57, 59, 61, 63, 65, 73, 75, 77, 79, 80, 81, OUTPUT DATA ......................................................... 44
83, 86, 89, 93, 107, 108, 115, 132, 164, 165, 168,
OUTPUT DATA menus ............................................. 44
182, 184, 188, 191, 195, 197, 204, 207
characteristics ................................................. 86, 89 Output Reports............................. 7, 177, 195, 197, 204
Static Inputs .......................................................... 47 Owner ...................................... 109, 115, 121, 127, 285
Time Varying Inputs .............................................. 47 scenario ....................................................... 109, 285
Values ................................................................... 47
Select .................................................. 115, 121, 127
Node Code ........................................ 15, 51, 53, 55, 57
Node Properties ......................................................... 47 P
Node represents ............... 51, 53, 55, 57, 73, 77, 79, 80 Packaging ................................................................. 95
Viewing ................................................................. 95
Node Type .................. 15, 73, 75, 77, 79, 80, 83, 86, 89
Selector according................................................. 15 Page ... 9, 11, 13, 15, 19, 26, 51, 53, 55, 59, 61, 63, 261
Node Type menu ..................................... 51, 53, 55, 57 parameter ............................................ 36, 40, 234, 235
Nodes according ........................................................ 37 Parent ..................................................................... 135
Upgrade.............................................................. 135
Non-interactive ........................................ 165, 171, 195
password .............. 6, 274, 276, 277, 278, 279, 280, 282
Non-interactive report ...................... 164, 177, 204, 207
path 7, 19, 30, 36, 37, 40, 41, 44, 46, 47, 51, 53, 55, 57,
North Shore Center.................................................... 29 59, 61, 63, 65, 73, 75, 77, 79, 80, 81, 83, 86, 89,
107, 108, 109, 115, 121, 127, 171, 173, 191, 210
O characteristics..................................................86, 89
OBI .......................................................................... 210 Static Inputs .......................................................... 47
Time Varying Inputs .............................................. 47
Office Phone Number ...................... 274, 279, 280, 282
Path Code ................................................................. 19
OK 11, 13, 15, 19, 30, 43, 51, 53, 55, 57, 59, 61, 63, 65,
73, 75, 77, 79, 80, 81, 83, 85, 86, 87, 88, 89, 93, Path connecting ........................................................ 75
107, 108, 109, 115, 121, 127, 135, 151, 164, 165, Path denote ............................................................ 210
168, 171, 173, 182, 184, 188, 191, 195, 197, 204,
Path Properties ......................................................... 47
207, 210, 232, 274, 278, 279, 280, 282, 283, 285,
286, 288, 289, 291, 292, 295, 296, 297 Path Static .........................................................59, 171
Clicking ............................................................... 210 Path Static Data ........................................................ 59
save .... 43, 51, 53, 55, 57, 59, 61, 63, 65, 80, 83, 85,
86, 93, 109, 115, 121, 127, 232, 274, 278, 286, 288, Path Static Inputs Report ........................................ 171
289, 291, 292 Path Static Inputs Report window ............................ 171
Old Password .......................................................... 274 Paths attaching .............................................. 73, 77, 79
On Hand ......................... 51, 73, 75, 109, 115, 121, 127 Paths represent ............................ 59, 61, 63, 65, 81, 83
value .......................... 51, 73, 75, 109, 115, 121, 127 physical ................................... 59, 61, 63, 65, 81, 83
On Hand Inventory............................................... 73, 75
390
Index
Paths show ................................................................ 40 process ...... 15, 44, 61, 63, 65, 77, 80, 81, 93, 115, 121,
Pending ................................................... 255, 261, 263 127, 132, 134, 135, 151, 210
returns ................................................................. 255 Process Point ............................................................ 15
period6, 8, 10, 36, 40, 44, 46, 53, 55, 57, 61, 63, 65, 81, Processor Logs
108, 109, 115, 121, 127, 164, 165, 168, 171, 173, Viewing Processor Logs ..................................... 300
177, 182, 184, 188, 191, 195, 197, 204, 207, 233, Processor reports ..................................... 209, 441, 442
234, 235, 258, 261, 263, 285
Product Family .....................................................85, 87
Period From ......................................................... 55, 63
Specify ................................................................. 87
period length .............................................. 10, 109, 115
profile ... 7, 274, 276, 277, 278, 282, 288, 289, 291, 292,
period selector ...................... 10, 36, 109, 115, 121, 127 295, 296, 297
Period To ............................................................. 55, 63 unassign ............................................................. 291
Unassigning........................................................ 291
PG-item ..................................................................... 93
incoming................................................................ 93 Profile Info........................................ 292, 295, 296, 297
outgoing ................................................................ 93 Privileges, Profiles and Preferences ................... 301
profit............................................................................ 1
PG-items ................................................................... 93
incoming................................................................ 93 Properties ..........................................................47, 300
physical ... 15, 19, 37, 59, 61, 63, 65, 73, 75, 77, 79, 80, Published Reports ................................................... 210
81, 83, 85, 88 Published Reports Definition ............................... 213
Paths represent ....................... 59, 61, 63, 65, 81, 83 Publishing Queue
Planned Receipts............................. 109, 115, 121, 127 Publishing Queue ............................................... 231
planner .................................................... 276, 289, 292
Q
planner profile .......................................... 276, 289, 292
Quantity .................................................................... 93
planning scenario......................................................... 9
Quarters .............................................................10, 115
Point Static Inputs Report ........................................ 165
Quick Links ............................................................... 27
Point Static Inputs Report window............................ 165
Point Static Outputs Report...................................... 195 R
Point Static Outputs Report window ......................... 195 radio 19, 37, 51, 53, 55, 57, 59, 61, 63, 65, 93, 232, 261
Point Time Varying Inputs report .............................. 168 radio button .. 37, 51, 53, 55, 57, 59, 61, 63, 65, 93, 232,
Point Time Varying Outputs ..................................... 197 261
rate ......................................................................... 233
Point Time Varying Outputs Report .......................... 197
Raw Forecast Report .............................................. 442
Points ............................... 109, 168, 184, 188, 191, 197
Report ..................................168, 184, 188, 191, 197 REFRESH...... 9, 44, 115, 121, 127, 132, 134, 135, 151,
POPUP ................................................................ 8, 233 210, 255, 260, 261
Clicking ................................................................... 8 Refresh Rates ......................................................... 233
use ...................................................................... 233 Related Topics ... 6, 9, 10, 11, 13, 15, 19, 26, 30, 36, 37,
position ........................................................................ 1 40, 41, 42, 43, 44, 46, 51, 53, 55, 57, 59, 61, 63, 65,
Postprocessing 73, 75, 77, 79, 80, 81, 83, 85, 86, 87, 88, 89, 93,
107, 108, 109, 115, 121, 127, 132, 134, 135, 151,
Postprocessing Scenarios ........................... 139, 517
164, 165, 168, 171, 173, 177, 182, 184, 188, 191,
preferences.. 41, 43, 108, 232, 274, 276, 277, 278, 279, 195, 197, 204, 207, 232, 233, 234, 235, 255, 257,
280, 282, 283, 285, 286, 288, 289, 291, 292, 296 258, 260, 261, 263, 274, 276, 277, 278, 279, 280,
deselect............................................................... 292 282, 283, 285, 286, 288, 289, 291, 292, 295, 296,
MIPO Preference Definitions ............................... 309 297
Privileges, Profiles and Preferences .................... 301
REMOVE ..................... 80, 83, 85, 86, 89, 93, 291, 292
Pressing ...................................... 51, 53, 55, 59, 61, 63 component ............................................................ 93
ENTER .................................... 51, 53, 55, 59, 61, 63
Replenishment ........................................................ 204
PREV ...................................................................... 261 create ................................................................. 204
PRINT........................................................ 42, 109, 234 view .................................................................... 204
Print dialog................................................. 42, 109, 234 Replenishment Report............................................. 204
privileges ... 7, 9, 30, 43, 51, 73, 75, 109, 115, 121, 132, report ............................................................... 173, 184
134, 135, 151, 164, 165, 168, 171, 173, 177, 182, Items .................................................................. 184
184, 188, 191, 197, 204, 207, 210, 232, 257, 258, Stocking Points ................................................... 184
260, 261, 274, 276, 277, 278, 279, 280, 282, 283, Time Varying Properties ..... 168, 173, 184, 188, 191,
285, 286, 288, 289, 291, 292, 296 197
MIPO Privilege Definitions ................................... 304 reports 8, 44, 86, 89, 109, 121, 127, 164, 165, 168, 171,
Privileges, Profiles and Preferences .................... 301 173, 177, 182, 188, 191, 195, 197, 204, 207, 209,
Supply Intelligence Privilege Definitions .............. 477 210, 232, 233, 234, 235, 442
Customer Facing Stocking Points ....................... 164
391
Stocking Points ... 168, 182, 188, 191, 195, 197, 204, Search 11, 13, 15, 19, 41, 51, 53, 55, 57, 59, 61, 63, 65,
207 109, 115, 121, 127, 280, 282, 283, 285, 286, 288,
Reports include ........................................ 109, 234, 235 289, 291, 292, 296, 297
required ................................ 1, 7, 9, 36, 73, 75, 93, 279 SEARCH tool ............................................................ 41
Requires Adobe Acrobat Reader ................................. 1 Search-by ................................................................. 19
Requires Java............................................................ 36 security ........................................................ 6, 279, 283
reset ................................. 274, 276, 277, 278, 289, 291 Select ................................................. 15, 115, 121, 127
clicking ........................................................ 289, 291 Owner.................................................. 115, 121, 127
Sort....................................................................... 15
Result Integrity................................................. 261, 263
Select All .. 109, 115, 121, 127, 280, 282, 283, 285, 286,
results 1, 9, 37, 41, 51, 73, 75, 109, 115, 121, 127, 134, 288, 289, 291, 292, 296, 297
164, 165, 168, 171, 173, 177, 182, 184, 188, 191,
Select Date ............................................................. 261
195, 197, 204, 207, 210, 232, 233, 234, 235, 261,
263 Select Days ............................................................. 115
review ........................................................................ 15 Select Internal ........................................................... 73
Select Item ..................................................... 15, 19, 93
S
Select Module .................... 30, 277, 278, 286, 288, 292
sales .......................................................... 10, 289, 292
Select Refresh ........................................................ 207
Sarbanes-Oxley ....................................................... 274
Select Supplier Node ................................................ 79
save1, 42, 43, 46, 51, 53, 55, 57, 59, 61, 63, 65, 80, 83,
85, 86, 93, 109, 115, 121, 127, 232, 235, 274, 278, Select User .............................................. 276, 277, 278
280, 286, 288, 289, 291, 292, 295, 296 selector .. 7, 9, 10, 11, 13, 15, 19, 26, 36, 37, 40, 44, 51,
save as .............................................................. 46, 235 53, 55, 57, 59, 61, 63, 65, 73, 75, 77, 79, 80, 81, 83,
85, 86, 87, 88, 93, 107, 108, 109, 115, 121, 127,
Save Picture dialog .................................................... 46 135, 164, 165, 168, 171, 173, 182, 184, 191, 195,
scenario ... 1, 7, 9, 10, 30, 36, 37, 40, 42, 44, 46, 51, 73, 197, 204, 207, 210, 279, 280, 282, 283, 285,
75, 80, 81, 83, 87, 88, 89, 95, 109, 115, 121, 127, 286,鳈288, 289, 291, 292, 295, 296, 297
132, 134, 135, 151, 164, 165, 168, 171, 173, 177,
182, 184, 188, 191, 195, 197, 204, 207, 210, 233, Selector according .................................................... 15
234, 235, 258, 261, 263, 276, 285, 286, 288, 289, Node Type ............................................................ 15
292 Selector displays .......................................... 15, 19, 115
Owner ......................................................... 109, 285 name .................................................................. 115
supply chain containing ............................... 132, 135
user creates ........................................ 109, 121, 286 service ................................................... 1, 40, 289, 292
Scenario Access ...................................... 109, 121, 286 service level .......................................................... 1, 40
Scenario Access Control.................................... 30, 286 Set ........................................................... 30, 51, 73, 75
Automatic ............................................................. 51
Scenario Audit Information ............... 121, 132, 134, 135 User-specified..................................................73, 75
Scenario Business Alerts Set window ............................................................... 30
Scenario Business Alert (activate) ....................... 247
Scenario Business Alert (assign) ......................... 251 settings .... 7, 30, 43, 109, 115, 232, 234, 257, 260, 261,
Scenario Business Alert (remove) ....................... 252 263, 274, 276, 277, 278, 279, 280, 282, 283, 285,
Scenario Business Alert (security level) ............... 248 286, 288, 289, 291, 292, 295, 296, 297
Scenario Business Alert (trigger value) ................ 250 Severity ............................................................ 261, 263
Scenario containing ......................................... 1, 73, 75 Short Entries ........................................................... 261
scenario selector 7, 9, 36, 109, 115, 121, 127, 135, 151, Short Entries list ...................................................... 261
210
Show.... 11, 13, 15, 19, 37, 43, 109, 115, 121, 127, 280,
Scenario Selector contains .................................. 9, 115 282, 283, 285, 286, 288, 289, 291, 292, 296, 297
Scenario Selector displays ............................... 121, 127 SHOW CHART ................ 164, 182, 184, 188, 191, 204
Scenario Settings..................................................... 359 SHOW DATA ............................................................ 44
Data Store scenario settings................................ 415
SHOW DATA buttons ................................................ 44
DIM scenario settings .......................................... 452
MIPO scenario settings ....................................... 360 Sign In ........................................................................ 6
SLO scenario settings ......................................... 563 Sign In window ............................................................ 6
Scenario Status ........ 109, 115, 121, 127, 132, 135, 151 SIM
Scenario-related .............................................. 109, 135 Supply Intelligence Module ................................. 457
Supply Intelligence Privilege Definitions .............. 477
Scenario-related process .. 115, 121, 127, 132, 135, 151
Single Property ..... 57, 65, 168, 173, 184, 188, 191, 197
Scenarios ........................................................ 134, 229
Deleting Multiple Scenarios ................................. 152 size ......................................................................8, 115
SKU .......................................................................... 11
392
Index
SKU attribute ............................................................. 11 supply chain1, 7, 8, 9, 30, 36, 37, 40, 41, 42, 43, 44, 46,
SKU code .................................................................. 11 51, 53, 55, 57, 59, 61, 63, 65, 73, 75, 77, 79, 80, 81,
83, 85, 86, 87, 88, 89, 93, 95, 107, 108, 109, 115,
Sort...................................................................... 15, 91 121, 127, 132, 134, 135, 151, 164, 165, 168, 171,
select .................................................................... 15 173, 177, 182, 184, 188, 191, 195, 197, 204,
Sort By..................................................................... 261 207,鳈210, 233, 234, 235, 276, 289, 292
Sorting Manufacturing BOMs ..................................... 91 Supply Preprocessor ............................................... 209
Source ............................................... 81, 260, 261, 263 SUPPRESS ............................. 255, 257, 260, 261, 263
Source Node.............................................................. 83 Suppressing ............................................................ 255
SOX......................................................................... 279 Alert .................................................................... 255
Stage ................................................................. 89, 191 System ............................................................. 261, 263
STAGES .................................................................... 37 T
Starting .... 109, 115, 121, 164, 168, 173, 177, 182, 184,
tabset .......................................................................... 7
188, 191, 195, 197, 204, 207
enter............................................................ 109, 121 target ............................... 1, 44, 51, 177, 232, 289, 292
entered ................................................................ 115 target inventory position ................................... 177, 232
values .. 177, 182, 184, 188, 191, 195, 197, 204, 207
target service level .................................................... 51
Static .......................... 47, 51, 53, 59, 61, 165, 171, 195
TASKS ..... 115, 121, 127, 132, 134, 135, 151, 279, 282,
Static Inputs ............................................................... 47 285, 295, 296, 297
Nodes ................................................................... 47
Paths ..................................................................... 47 TASKS menu .......................................................... 109
Static window................................................. 44, 51, 59 technical support profile ........................... 276, 289, 292
Status ....................... 134, 210, 255, 257, 260, 261, 263 text6, 9, 11, 13, 15, 19, 37, 41, 73, 75, 77, 79, 107, 108,
109, 115, 121, 127, 135, 182, 210, 274, 279, 280,
Status History .......................................................... 258 282, 283, 285, 286, 288, 289, 291, 292, 295, 296,
Status window ............................................................. 6 297
Step ............................................................... 73, 75, 81 text box .................................................. 6, 9, 11, 13, 41
stock keeping unit ...................................................... 11 Text string .................................... 11, 13, 15, 19, 37, 41
stocking location .......................................... 93, 95, 164 time .... 1, 6, 9, 10, 15, 36, 40, 44, 47, 51, 53, 55, 57, 59,
61, 63, 65, 73, 75, 81, 109, 115, 121, 127, 132, 134,
Stocking Point Data ................................. 44, 47, 51, 53
135, 151, 164, 168, 173, 184, 188, 191, 197, 210,
Stocking Point Static .................................. 51, 165, 195 255, 258, 261, 263, 277, 283, 285, 286, 288, 289,
Stocking Point Static Data ......................................... 51 291, 292, 295, 296
Stocking Point Static Inputs Report .......................... 165 time period ............................... 1, 9, 10, 73, 75, 81, 255
Stocking Point Static Inputs Report window ............. 165 Time Varying ...... 15, 44, 47, 53, 55, 57, 61, 63, 65, 132,
168, 173, 197
Stocking Point Static Outputs Report ....................... 195
Time varying data........... 10, 53, 55, 57, 61, 63, 65, 109
Stocking Point Static Outputs Report window .......... 195
Time Varying Inputs .................................................. 47
Stocking Point Time Varying Data.................. 53, 55, 57 Nodes ................................................................... 47
Stocking Point Time Varying Inputs Report .............. 168 Paths .................................................................... 47
Stocking Point Time Varying Outputs Report .. 184, 188, Time Varying Inputs Report ..................................... 173
191, 197 Time Varying Output
Stocking Points .... 15, 47, 51, 53, 55, 57, 109, 115, 121, Time Varying Output Data (Single Node) ............ 101
127, 164, 165, 168, 182, 184, 188, 191, 195, 197, Time Varying Output Data (Single Property) ....... 103
204, 207 Time Varying Properties ... 168, 173, 184, 188, 191, 197
edit ...................................................... 51, 53, 55, 57 report ........................... 168, 173, 184, 188, 191, 197
Report .. 168, 182, 184, 188, 191, 195, 197, 204, 207
Timestamp .............................................................. 210
Summaries .............................................................. 255
TIP ........................................................... 108, 177, 232
Summary Report.............................................. 182, 207
toolbar .............................................................. 6, 7, 233
Sun’s Web site........................................................... 36
total ......................................................................... 182
Supplier ....................................................... 79, 81, 182
Trademarks ............................................................... 29
Supplier > Manufacturing In ....................................... 37
Transition Time ....................................................... 258
Supplier Node ...................................................... 15, 79
Txt file ..................................................................... 210
Supply ............................................. 109, 151, 171, 173
Deleting ............................................................... 151 Type......................................... 257, 258, 260, 261, 263
U
Unassign .......................................................... 291, 292
393
profile .................................................................. 291 Validate Scenario .................................................... 132

Unassigned.............................................................. 177 Validation ................................................. 134, 261, 263
Unassigning ............................................................. 291 Value 47, 51, 61, 63, 65, 73, 75, 81, 109, 115, 121, 127,
Profile.................................................................. 291 164, 168, 173, 177, 182, 184, 188, 191, 195, 197,
Uncheck ............................................ 37, 283, 286, 292 204, 207, 255, 257, 258, 260, 263
Enabled checkbox ............................................... 283 Base .................................................... 164, 168, 173
Grouped ................................................................ 37 Custom ............................................................73, 75
Maximum ............................................. 61, 63, 65, 81
Uncheck preferences ....................................... 278, 288 Node..................................................................... 47
Unconstrained ......................................... 61, 63, 65, 81 On Hand .................... 51, 73, 75, 109, 115, 121, 127
Start...... 177, 182, 184, 188, 191, 195, 197, 204, 207
Unhidden ................................................................. 258
Verify Password ............................... 274, 279, 280, 282
UNHIDE........................................................... 255, 260
View Alerts ... 7, 132, 134, 210, 257, 258, 260, 261, 263,
Unhiding .................................................................. 258 286, 292
unit ...29, 51, 61, 63, 65, 73, 75, 81, 85, 87, 93, 95, 164, View Network ..................................... 73, 75, 77, 79, 81
165, 168, 171, 173, 184, 188, 191, 197, 204, 207,
232 View/Edit .... 7, 15, 36, 44, 47, 51, 53, 55, 57, 59, 61, 63,
Measure .............................................. 85, 87, 93, 95 65, 73, 75, 77, 79, 80, 81, 83, 85, 86, 87, 88, 89, 93,
107, 108, 109, 132, 134, 210, 261, 263
unit of measure ........................................ 85, 87, 93, 95
View/Edit menu .................................. 44, 109, 121, 127
United States ............................................................. 29
View/Manage Alerts ......................................... 286, 292
UNLOCK button....................................................... 255
Viewing ...... 36, 37, 40, 44, 95, 177, 204, 257, 258, 260,
Unlocking Alerts ....................................................... 255 261, 263, 286, 292
UNSUPPRESS ........................................................ 260 Alert Details ........................................................ 263
Alert Type ........................................................... 260
Unsuppressing......................................................... 258 Alert Type Status History .................................... 258
Upgrade................................................................... 135 Alert Types ......................................................... 257
Parent ................................................................. 135 Alerts .................................................................. 261
Entire .................................................................... 37
upstream .................... 51, 53, 55, 57, 73, 77, 79, 80, 95
Item ...................................................................... 37
Upstream PG-item in ................................................. 95 Master Summary ................................................ 177
URL ............................................................................. 6 Packaging............................................................. 95
MIPO application in ................................................. 6 Replenishment.................................................... 204
Use ............. 11, 30, 37, 73, 75, 77, 80, 85, 93, 184, 233 Viewing Alert Short Entries ...................................... 261
Import .................................................................... 30
Item ............................ 11, 73, 75, 77, 80, 85, 93, 184 W
POPUP ............................................................... 233 Warning ........................................................... 261, 263
View ...................................................................... 37
Web ............................................................................ 6
user 1, 6, 7, 9, 30, 42, 43, 44, 51, 73, 75, 80, 83, 87, 88,
89, 108, 109, 115, 121, 127, 132, 134, 135, 151, week .......................................................... 10, 109, 115
164, 165, 168, 171, 173, 177, 182, 184, 188, 191, Welcome ..................................................................... 1
195, 197, 204, 207, 210, 232, 261, 263, 274, 276,
Where Used .............................................................. 93
277, 278, 279, 280, 282, 283, 285, 286, 288, 289,
291, 292, 295, 296, 297 Windows ............................................................29, 263
User creates ............................................ 109, 121, 286 Windows toolbar ..................................................... 233
User Info ... 274, 276, 277, 278, 279, 280, 282, 283, 285
Y
username .................................................................... 6
year....................................................................10, 210
User-specified....................... 73, 75, 109, 115, 121, 127
Automatic .................................... 109, 115, 121, 127 yield .....................................................................37, 59
set ................................................................... 73, 75
Z
V Zoom ........................................................................ 41
Validate ....................................115, 121, 127, 132, 134
394

EIS 610 User Guide en v2

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

EIS 610 User Guide en v2

Загружено:

Авторское право:

Доступные форматы

SAP Enterprise Inventory and

Service-Level Optimization User

Exception Management Workflow 101

3. Analytics _________________________________________________________________________________ 243

4. Data Gateway _____________________________________________________________________________ 245

5. Data Store ________________________________________________________________________________ 273

Published Reports 274

6. DIM ______________________________________________________________________________________ 281

7. SIM ______________________________________________________________________________________ 307

8. SLO _____________________________________________________________________________________ 323

9. Data Protection and Privacy _________________________________________________________________ 381

10. Index ____________________________________________________________________________________ 384

For help on a specific module, click the associated link:

Other Help links:

Copyrights and Trademarks

Click on a link below to view privilege definitions for a specific application:

DIM - Demand Intelligence Module

MIPO - Multistage Inventory Planning & Optimization

SIM - Supply Intelligence Module

Click on a link below to view preference definitions for a specific application:

DIM - Demand Intelligence Module

MIPO - Multistage Inventory Planning & Optimization

Click on a link below to view alert definitions for a specific application:

DIM - Demand Intelligence Module

MIPO - Multistage Inventory Planning & Optimization

The general approach to achieving these goals involves three steps:

• Create a graphical representation of the supply chain.

Copyrights and Trademarks

To launch the application:

Monitor resolution and browser version requirements

Changing Your Password

• Alerts - Lets you manage and view generated alerts.

• Home - Lets you return to the main window.

• History - Invokes the History feature.

• Log Off - Click to log off of the system.

• Clock - Displays the current date and time.

• Supply Chain Selector

• Demand Stream Selector

Maximizing Your Work Area

• Viewing a large supply chain network or comparing two networks

• Editing data for a significant number of nodes or periods

• Comparing two or more reports

Supply Chain Selector

Supply Chain Selector

Searching by Item Code

Select all items in the Items list or a single item, as follows:

Displaying All Items

Select all items in the Items list or a single item, as follows:

Filtering by Item Attribute

To filter items by item attribute:

1. Select Attribute from the Search by drop-down menu.

Note: The contents of the drop-down menus in the Attribute

5. Select an attribute value and click OK to close the Attribute Selector.

7. Select all items in the Items list or a single item, as follows:

Searching by Location Code

Select all locations in the Locations list or a single location, as follows:

Displaying All Locations

Select all locations in the Locations list or a single location, as follows:

Filtering by Location Attribute

To filter by location attribute:

1. Select Attribute from the Search by drop-down menu.

5. Select an attribute value and click OK to close the Attribute Selector.

7. Select all locations in the Locations list or a single location, as follows:

Filtering by Node Type