Creating and Using Views
You can use views to define easy options for selection on the Labor Demand Planning (LDP) user interface (UI), so that you can make quick selections without having to enter many selection values. A view can aggregate the workload of a certain area or team in your warehouse. A view represents a workload selection for activity areas and external process steps. You maintain views in Customizing for Extended Warehouse Management under .
A view has the following attributes:
-
View ID
The view ID is a 4-character-long key value which must be unique within the warehouse. The views on the UI are sorted by the view ID. You can enter an activity area and external process step as a single value or as a range. You can also include and exclude specific activity areas and external process steps.
-
Description
The description can only be maintained in the logon language. If you run the UI in other languages, you must first log on in the other languages and enter the descriptions in Customizing.
-
Accuracy level
The accuracy level describes which type of workload is shown on the UI. There are three different levels, as follows:
-
The most accurate workload is based on warehouse orders (WOs) and warehouse tasks (WTs).
-
The second most accurate workload is based on outbound delivery items (ODOs).
-
The least accurate workload is based on a forecast. For more information, see Forecasting Workload.
-
If you do not define any views in Customizing, the following default views are displayed:
-
One view for the complete warehouse, containing all activity areas and all external process steps
-
One view for each activity area, containing all external process steps
The view ID in this case is either the warehouse number or the activity area. The view description is either the warehouse description or the activity area description. If there is an activity area equal to the warehouse number, the view ID for the complete warehouse is set to $.
In these default views, accuracy levels based on WOs/WTs and on ODOs are switched on.
You can use the authorization object /SCWM/LDPV to control which users can see and process which views on the UI. This authorization object is not checked in the Customizing activity itself.

