Ansicht
Dokumentation

/AFS/SIMGARUN_GRP - Define Rules for Requirements Grouping

BAL Application Log Documentation   CPI1466 during Backup  
This documentation is copyright by SAP AG.

In this IMG section you define conditions under which certain requirements that fulfill the same criteria can be grouped during an allocation run. You can handle requirements of this group separately during the allocation. For example, you can apply a special release procedure to the group.

You want to group all the requirements of a sold-to party with identical purchase order numbers in an allocation group so that you can use an individual release rule. To do this, define allocation groups and assign the corresponding group its own release rule, which is different than the rule in the allocation type.

Forming allocation groups is the prerequisite for using allocation logics other than the FIFO logic (first in first out).

You define allocation groups using grouping rules. You assign fields to each of these rules, according to which the requirements should be grouped. Using grouping rules you can control, for example, that all the requirements will be grouped according to the sold-to party in an allocation run. You can then carry out the allocation for each allocation group according to the equal distribution principle, for instance (see Allocation Logic).

1. Define your grouping rule by assigning an alphanumeric key with a maximum of four characters as well as an explanatory text.
2. Assign fields to your rule, according to which the requirements should be grouped.
3. Assign constants to your grouping fields if necessary.

If individual release rules should be used for this allocation group, enter an external group number as well. To do this, enter a numeric key with a maximum of five digits in the corresponding field. You can also use a self-defined function module, which can then fill the group number.

1. If you want to carry out a special release procedure for the requirements of this allocation group, first enter the external group number, which you assigned to your grouping rule in the previous step. Then enter the relevant grouping rule.

• You can make settings for the individual release levels as well as for the final action without entering a separately defined release rule. These entries are then only valid for the underlying allocation group.

• You can also select an already existing release rule. In this case, default values will be superimposed, which you can individually change. If the Reference indicator is set, the original data of the selected release rule will always be used. Without the indicator, the visible (changeable) settings will always be valid during the allocation run.

Store the grouping rule in the allocation type.

You want to group all of the requirements from customer A that were created with the sales document type TA (standard order). To do this you define a corresponding grouping rule. You could then use, for example, a special release rule for the requirements of this group 1. You can combine the customer's requirements that were created in another sales document type, according to a different grouping rule. You can then in turn carry out a release procedure for the requirements of this group 2, which is different than the release procedure for group 1.

General Material Data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 3607 Date: 20240425 Time: 194214     sap01-206 ( 86 ms )