Ansicht
Dokumentation

SIMG_CFMENUOLPKOPDF - Define grouping requirememts

ROGBILLS - Synchronize billing plans   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this step you define the following for capacity leveling and the extended evaluation:

• requirements grouping

A requirements grouping defines which objects appear with their capacity requirements in the planning table in capacity leveling or in the extended evaluation. Examples of objects are work centers or orders. You specify a requirements grouping in the selection profile.

• requirements groups

A requirements grouping can comprise several requirements groups. Every requirements group groups together certain objects and their capacity requirements and displays them line by line in a chart in the planning table, for example all dispatched capacity requirements for the work centers, that you have selected when accessing capacity leveling.

Requirements groups are defined using multidimension sets. The individual requirements groups in the requirements grouping that you specify in the selection profile are assigned under Define layout to the various charts in the planning table.

In the definition of the requirements group you also specify which material stock curves (if any) - for example, available quantity - can be displayed in the capacity planning table in capacity leveling.

The following examples display step by step how you use a requirements grouping and its requirements groups to display objects and assigned capacity requirements in a planning table with two charts.

The requirements grouping should contain two requirements groups. One requirements group is to group capacity requirements for all capacity categories in work centers, another requirements group the capacity requirements for orders:

Requirements group   Object

1                    all capacity categories for the work centers

2                    orders

You assign the requirements groups of the requirements grouping to the charts in layout L1 under Define layout:

Chart    requirements group  object

1           1                all capacity categories of work centers

2           2                orders

In the first chart in the planning table the capacity requirements for all the capacity categories at the work centers are displayed, in the second chart the capacity requirements for the orders.

The requirements group defines which objects and assigned requirements are in the lines in the planning table screen.

It is defined using a multidimension set that selects the objects and the assigned capacity requirements accordingly. A multidimension can comprise several basic sets each of which refers to a selection criterion.

In the example the capacity requirements for all the capacity categories at the work centers are displayed in the lines for chart 1 to which the requirements group 1 is assigned.

Basic set    Object            Field        Value

BS1          work center       ARBPL        R1

BS2          capacity category KAPAR

The basic set BS1 refers to the field ARBPL (work center). The value R1 is assigned to this field. Thus the work center R1 is selected. The basic set BS2 refers to the field KAPAR (capacity category). No value is assigned to this.

With the requirements group 1 defined in this way the capacity requirements for all the capacity categories at work center R1 are displayed line by line in chart 1, thus

Work center    capacity category

R1             person

R1             machine

R1             energy

etc.

If you do not specify a value in the basic set BS1 for the field ARBPL the capacity categories for all work centers that you specify when accessing capacity leveling are selected using the requirements group 1. They are displayed line by line in the first chart of the planning table with the capacity requirements that belong to them.

If you only want to display the dispatched capacity requirements in chart 1 for all the capacity categories for the work centers you need an additional basic set with a selection criterion that contains the status information. Define the requirements group 1 and assign it to chart 1 with a multidimension set containing the following basic sets: BS1, BS2 and BS3:

Basic set   object                           field     value

BS1         work center                      ARBPL     R1

BS2         capacity category                KAPAR

BS3         status of capacity requirements  KBEDSELAV SAP001

The basic set BS3 refers to the field KBEDSELAV, that is the status stored in the capacity requirements record. The value SAP001 is assigned to the field. It concerns a selection profile. A status profile allows the assignment of one or more statuses. The basic set BS3 has the effect that only those capacity requirements are selected whose status corresponds to the selection profile SAP001. With the status profile SAP001 defined by SAP only the dispatched capacity requirements are selected.

• Every requirements group (multidimension set) should contain a basic set to which not value is assigned.

A basic set without a value has the effect that all the objects are selected to which the field belongs. The field ARBPL belongs to the object work center, so all the work centers are selected. The field name is not of significance. (The assignment of fields to objects is stored in the table TCY36).

• All the basic sets that follow the last basic set without a value (in the example the set BS2) only serve to select capacity requirements.

• The capacity planning table can only display two charts. In the capacity planning table load sums are assigned to the lines instead of bars. So the capacity requirements assigned to a line are aggregated. The logic is as described above.

• If possible restrict yourself to the requirements groups provided by SAP; the definition of new requirements groupings is time-consuming and problematic.

If necessary define new requirements groupings.

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 8777 Date: 20240523 Time: 201420     sap01-206 ( 125 ms )