Back

Adding a Routing Status Filter or Previous Routing Status Filter

Overview: Operation Lines
Video 6/14
Play
Close
  • Helpful
  • Not helpful
  • Needs update
  • Technical error
This video includes functionality from the app "Shop Floor Mobile" which is available at Microsoft AppSource. Click to visit AppSource. Shop Floor Mobile

Playlists  Manage

Log in to create a playlist or see your existing playlists.

Presenter: Sune Lohse, Chief Strategy Officer

In the production scheduling header, you can use two fields called routing status filter and previous routing status filter to control which operations you see before they are calculated. Set the routing status filter to a value like In Progress to load only the operations that match, instead of pulling in everything and filtering afterwards.

This matters most when you calculate capacities. Limiting the data up front keeps the number of operations down and the calculation manageable.

You can add more than one value to a filter. For example, you can include both Planned and In Progress in the same filter.

A common setup is to filter for operations where the routing status is Not Started (only planned or blank) and the previous routing status is Finished or In Progress. That way you see the work that is coming to your station next.

Where to find the routing status filters

The two fields, routing status filter and previous routing status filter, sit in the filter functionality in the header. You use them to decide which operations are pulled into the view, based on their current routing status and the routing status of the previous operation.

Filtering before you calculate operations

When you update or maximise the view, you see all your operations listed at the bottom. If you only want to see operations that are in progress, you could apply a filter afterwards on the list itself.

For larger data sets, it is better to set the filter before you calculate the operations. By setting the routing status filter to In Progress before recalculating, the view loads only those operations and shows the ones that are started.

Why filtering matters for capacity calculations

The main reason to use the routing status filter and previous routing status filter is to avoid loading too many operations. This is especially important when you calculate capacities. Cutting down the volume of operations up front keeps the calculation fast and the data relevant.

Combining routing status and previous routing status

You can also filter on the previous routing status, and you can add more than one value to each filter. For example, you can set the filter to include both Planned and In Progress.

When you update the operation, or simply click it, the lines at the bottom update to match your filters.

A typical configuration is to set the routing status to Not Started, which means only planned or blank, and the previous routing status to Finished or In Progress. This shows you what is heading towards your station so you can plan around the work that is coming next.

Q&A

Q&A

What do the routing status filter and previous routing status filter do?

They let you filter operations in the production scheduling header based on their own routing status and the routing status of the previous operation. You use them to control which operations are loaded into the view.

Why should I set the filter before calculating operations?

Setting the filter first loads only the operations you need, instead of pulling in everything and filtering afterwards. This keeps the number of operations down, which matters most when you calculate capacities.

Can I filter on more than one routing status at a time?

Yes. You can add more than one value to a filter. For example, you can include both Planned and In Progress, and the view will show operations matching either.

What is a common filter setup for seeing upcoming work?

Set the routing status to Not Started (only planned or blank) and the previous routing status to Finished or In Progress. This shows you the operations that are coming to your station next.

671848170-Ib4vBzVvSiY-ENG21081017