Kontakt

Ansicht
Dokumentation

FSH_GROU_C - Maintain Rules for Grouping

FSH_GROU_C - Maintain Rules for Grouping

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define conditions for grouping requirements that fulfill the same criteria during an order allocation run (ARun).You can handle requirements for each group separately during the allocation.

Forming allocation groups is the prerequisite when the spread allocation logic is used.

You use grouping rules to define allocation groups. You assign fields to each of these rules and the requirements are grouped based on these rules. For example, you can specify that all requirements are grouped by sold-to party in an order allocation run. You can then execute order allocation run for each allocation group based on the Spread distribution logic (see Allocation Logic).

  1. Enter an alphanumeric key with a maximum of four characters and a description for your grouping rule.
  2. Assign fields to the rule, indicating how the requirements need to be grouped.
  3. If required, assign constants to the grouping fields. If individual release rules are to be used for this allocation group, enter an external group number as well (numeric value with a maximum of five digits) in the corresponding field.
  4. If you want to carry out a release procedure for the requirements of this allocation group, assign the release rule for the external group number that you assigned to the grouping rule in the previous step.
  5. Save the grouping rule in the allocation type.

External group can be applied to specific customers (any grouping field) by providing constants.

Consider the following example:

Grouping
Rule Grouping
Field   Ext.
Group   Constant Release Rule
0001 KUNNR   C1   Customer_1 REL_1
0001 KUNNR   C2   Customer_2 REL_2

Here, among all the requirements selected by ARun, the release rule REL1 will be applied to only those requirements which are created by the Customer_1. Similarly, REL2 will be applied to only those requirements which are created by the Customer_2.







ABAP Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 3448 Date: 20240523 Time: 202511     sap01-206 ( 45 ms )