---
pdfexport: true
alias: tutorials-settingupflows
description: "This documentation outlines the process for configuring and managing system flows and their associated data elements"
---
# Setting Up Flows
To set up **Flows**, begin by utilizing the **Master Data** to establish the necessary **Facilities**, **Areas**, and **Reasons** as well as the required Lookup Table entries. Then, you can create as many **Steps** as required by the different **Flows**. If a **Flow** consists of **Child Flows** or involves Rework **Flows**, those **Flows** must be created first.
A more detailed explanation is shown in the sub-sections below.
## Create the Necessary Master Data
The necessary **Master Data** for setting up **Flows** is described in the table below:
| Master Data Item | Item Type | Description |
|-------------|-------------|--------------------------|
| **Units** | Lookup Table | This lookup table contains the different possible units of measure that can be defined as Primary or Secondary units of a Step. |
| **StepType** | Lookup Table | This lookup table defines the different Step types. |
| **FlowType** | Lookup Table | This lookup table defines the different Flow types. |
| **Services** | Object | The Services are required to specify the Storage Services as well as the Service Context that defines the Service required for Material at that Step. |
| **Reasons** | Object | There are four different types of Reasons that may be referenced by the Step:
• Loss
• Bonus
• Hold
• Rework|
| **Facilities** | Object | A Facility is required because a Step must be always associated with at least one Facility via the Area object. |
| **Areas** | Object | A Step must be associated with at least one Area. A Step can be associated with multiple Facilities but always through different Areas. |
Table: Master Data preparation
## Create the Necessary Steps
A **Step** is a regular system object that can be created and edited just as any other system object. For more information, see [[tutorials-howto-createstep]].

## Create the Necessary Flows
A **Flow** is a versioned object and it is subject to change control. For more information, see [[tutorials-howto-createflow]].

!!! info
When setting a new version of a **Flow** effective, the system will check that the new **Flow** version maintains the system integrity (e.g., by checking that if in a certain **Flow** version some **Steps** are removed, that there are no **Materials** currently in those **Steps** that have been removed).