Ansicht
Dokumentation

/AFS/SIMGARUN_SORT - Requirement Sorting

/AFS/SIMGARUN_SORT - Requirement Sorting

PERFORM Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

In this step you set the criteria for sorting requirements records during an allocation run.

By using requirements sorting, you can greatly influence which customers will receive the original requirements quantity and in what amount. It provides you with a tool for you to use your own criteria and priorities to restructure the original sequence in which the requirements records are posted in the system for the incoming order.

For example, you can specify that sales documents for very important customers should always be assigned first. This way you can make sure that you achieve the best possible allocation result for these requirements even if there is a stock shortage.

You must enter a rule for the requirements selection for each allocation type.

Hint
If you sort requirements according to fields at the schedule line level or item level before the fields at header level, orders and items might be split. This could happen, for instance, if you execute a release check at the next highest level. This could result in different MRP statuses within an order or an item. You should therefore set the final release check to 1 or 2 in the allocation type. In addition, you should be sure to first sort according to a field at header level and then according to a field at item or schedule line level in the sort rule.

If you have activated the availability check at the schedule line level in your system, keep the following in mind when defining the requirements sorting:

  • The availability check for a requirement use FIFO logic exclusively. The system determines the quantity available for a requirement by calculatulating the warehouse stock and planned incoming stock on the one hand, and all of the issues (posted sales orders, reservations, blocked stock, and so on) on the other hand. The availability check determines a delivery date for the requirement according to the given stock/ requirements situation.
  • The stock/requirements side is rechecked during every allocation. Your rule for the requirements sorting determines which logic will underlie the allocation of stock to requirements during the allocation. You can, for example, control requirements sorting based on logic that is different from, or even contrary to, the logic used by the availability check.
  • This affects the date on which a requirement can actually be delivered. The result of the allocation could be, for example, that the delivery dates of some requirements (such as those with low priority) can no longer be kept, but the delivery dates of other requirements (such as those with high priority) are given preference. The delivery dates of the requirements are not adjusted during the actual allocation. However, you can make sure they are adapted by implementing the AFS rescheduling.
  1. Define your rule by assigning an alphanumeric key with a maximum of four characters as well as a description.
  2. Assign sort fields to your rule. Enter the sequence in which these fields should be sorted.
  3. If necessary, assign constants to your sort fields.
Example
You choose KUNNR (customer number) as one of your sort fields for the requirements sorting. You can now explicitly enter customer numbers as constants in this field and you can prioritize the customer numbers using your own sorting sequence.

Alternatively, you can define and enter a function module to control sorting of the requirements, schedule lines, or stock during the allocation.






BAL Application Log Documentation   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 3930 Date: 20240328 Time: 194304     sap01-206 ( 91 ms )