Ansicht
Dokumentation

/AFS/SIMGARUN_ALLRUL - Allocation Rule

ROGBILLS - Synchronize billing plans   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

The allocation rule defines how the system allocates stock to a requirement requirement. The allocation rule is assigned to the ARun type.

The following fields form the basis of the allocation rule:

• Requirements Date

This is the reference date of the sales document for allocation purposes. This is important because the requirement stock mapping is based on reference dates. You can select from the following the reference dates:

• Confirmed delivery date

• Order cancellation date

• Requested delivery date

• GR Date

This is the reference date of the future receipt that is to be considered for the allocation process. You can select from the following reference dates:

• Schedule line date

• Receipt/requirements date

• Delivery Scheduling

You can enable this check box to ensure on-time delivery to the customer. The system checks factors that influence the delivery time, such as picking time, packing time, loading time, and goods receipt processing time.

• Batch Horizon ( Dynamic Stock Prioritization)

This is defined as the number of days between today and the requirement date needed for allocation of a batch to a requirement. The batch horizon is maintained in the From Days in 'Dynamic Stock Validity'.

Important points are:

• Batches are allocated only if the requirement date minus the current date is less than the batch horizon.

• Only the absolute value of the batch horizon is considered.

• It is not possible to set a horizon for a sales order date in the past. In other words, a batch can be allocated to all sales orders with a past date.

• Priority of Stock ( Dynamic Stock Prioritization)

This indicates the priority of batch stock. When multiple stock types need to be allocated to a requirement, the system checks this parameter to determine the priority of the batch stock..

• Purchase Orders ( Dynamic Stock Prioritization)

• From: Number of days to be added to the reference requirement date. This new date is calculated as the start limit of the reference date of the purchase order that needs to be allocated to a requirement

• To: Number of days to be added to the reference requirement date. This new date is the end limit of the reference date.

• Priority of Stock: Enter the priority for purchase order stock. .

• Confirmations ( Dynamic Stock Prioritization)

This is similar to the data needed for purchase orders (see above).

• Production Orders ( Dynamic Stock Prioritization)

This is similar to the data needed for purchase orders (see above).

• Field Checks

During the allocation process, the system carries out these checks on the fields in the sales document. You can choose from the following checks:

• Batch Number: Ensures that only the batch number entered in the sales document is considered for allocation.

• Storage Location: Ensures that only those stock elements in this storage location are considered for allocation.

• Category Check: Ensures that the stock category of the stock element is mapped to the requirement category of requirement as maintained in the coverage strategy.

• Category Sort: Ensures that, in addition to the category mapping, valid stock elements with different stock categories are prioritized according to the sort parameter in the coverage strategy before being allocated.

• Season End: Ensures that allocation occurs only when the stock availability date is not after the season end date.

• Cancel Date: Ensures that allocation occurs only when the stock availability date is before the cancel date in the sales document.

• Stock Prioritization:There are two ways of prioritizing stock elements for allocation:

• Use Stock Sort Rule: Requires a stock sort rule (which must have already been maintained in Customizing) for prioritizing stock.

• Dynamic Stock Prioritization: You can prioritize different stock types so that the one with the highest priority is allocated first. For allocation against goods receipts, the system looks for each stock type, matching stock from the 'From days' maintained to the 'To Days'. If the 'From Days' Maintained for a stock element is greater than the 'To Days', then the stock search is backwards, else it is forward, as indicated by the arrows in the screen for 'Dynamic Stock Validity'.

Batch Horizon: Assume that the batch horizon is 5, the sales order date is May 20, and today is May 13. In this case, the batch is not allocated to the sales order. Only sales orders with a date up to May 18 are allocated to stock.

If the batch horizon is changed to 8, then allocation would take place. Now all sales orders up to May 21 will be allocated to batch stock.

Dynamic Stock Prioritization: Assume that there is a sales order with delivery date 20th of July and the dynamic stock validity for the purchase order is maintained with 'From Days' as -5 and 'To Days' as 5. In such a scenario, a Purchase Order would be searched for the Sales order from 15th of july to 25th of july (Forwards).

If the dynamic stock validity for the purchase order was maintained with 'From Days' as 5 and 'To Days' as -5, then a Purchase Order would be searched for the Sales order from 25th of july to 15th of july (Backwards).

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 7870 Date: 20240425 Time: 062448     sap01-206 ( 104 ms )