Control Profile 

A control profile contains settings that define the type of display and the layout of the data as well as the locking properties of the system. You can maintain the following data:

  • Presentation: You use the presentation to define how data is displayed in capacity leveling. You can choose between the planning table, planning table (tabular form) and the list display.
  • Layout type : Here you specify whether the data for capacity requirements and available capacity are displayed per period or continuously. Data can be displayed per period in the planning table (tabular form) or in the planning table. Data is displayed continuously in the capacity planning table.
  • Change mode : If this indicator is set, capacity leveling is called up in change mode and you can change the objects. If you have not set the indicator then capacity leveling is called up in display mode. With Locking properties you control when orders are locked.

If you are not authorized to change capacity leveling parameters, then you automatically go to display mode even if the indicator is set.

  • GUI status for display mode: You can use this GUI status to define how the menu is set up for the planning tables for display mode. If you do not maintain the GUI status for display mode, then the system uses the GUI status predefined by SAP.
  • GUI status for change mode: You can use this GUI status to define how the menu is set up for the planning tables for display mode. If you do not maintain the GUI status for display mode, then the system uses the GUI status predefined by SAP.
  • Restrict. plan.: If you set this indicator then the capacity planning table is called up in a session in which you can temporarily save the results of your planning without leaving the planning table.

You can carry on working in the planning table during the saving process. The system saves changes made since the last time the saving process was started; it saves them in the next saving process.

In this planning table session orders are only locked during the saving process; they are not locked while the capacity planning table is being called up or during processing. The locking properties in the control profile are not taken into account.

Planning functions are limited in this planning table session:

    • You cannot dispatch operations to individual capacities
    • You cannot change or display orders.
    • You cannot change sequence numbers of orders
    • You cannot change capacities
    • You cannot display operations. You can make limited changes to operations in orders. You can change their standard values.
    • When leaving the planning table you cannot start another action automatically using the trigger CY_PLANNING_TABLE_END.
  • Locking properties: This indicator determines when orders are locked if you call up the planning table in Change mode. Other users cannot change the orders that you have locked. You can:
    • Only lock orders on changing them

The orders are only locked when you change them, for example, when you dispatch an operation.

    • Only lock orders in pool

The orders in the pool are locked when they are read in. The dispatched orders, on the other hand, are only locked when you change them. Special case: If one operation belonging to an order is in the pool and another has been dispatched then the order is not locked.

    • Lock all orders

All orders are already locked when the system reads them in.

In the order view only those orders are locked on being read in that you selected in the initial screen of capacity leveling. However, any other orders that the system reads in to determine the relevant available capacities and displays on the planning table are not locked.

  • Always sort: You use this indicator to specify that the lines in the capacity planning table are to be sorted after every change (for example, after deallocating a requirement). If the indicator is not set then new lines are added to existing ones on the planning table.
  • Set event and parameters: You use this setting to determine that on leaving the planning table other actions are automatically triggered, such as mass dispatching. You use the indicator Set event to set the trigger CY_PLANNING_TABLE_END. On leaving the planning table the job is automatically triggered that you have defined for this event and the parameter.