Allocation Against Future Receipts 

Use

...

This AFS process allocates future receipts to sales orders. This enables you to reserve stock from a future receipt (for example, a couple of months in advance) to be sure you will have the stock ready to fill the sales orders once the goods are received. This way, stock you have purchased on behalf of a specific customer is reserved for exactly that customer, even before you receive the stock. You are thus able to make commitments to your customers based on stock reservations.

The following types of future receipts are supported for mode 1 (normal) future allocation:

·        Purchase orders

·        Shipping notifications

·        Production orders

Integration

All functions and features in ARun treat future receipts as if it were unrestricted stock, with the following exception: future receipt allocations can only be given the reserved status (MRP Status R). This status cannot be changed to fixed (MRP Status F).

In addition to the normal MRP status, there is a special “future MRP status” used for allocation against future receipts. This future MRP status treats future receipts as if they were freely available physical stock. The future status indicates in advance what the MRP status would be when all future goods receipts are posted.

See also the following:

·        Consequences of Changing Sales Orders

·        Consequences of Changing Purchase Orders

·        Consequences of Changing Confirmations

·        Consequences of Changing Goods Receipts Dates

Features

·        The system uses a “best match” strategy (dynamic stock prioritization) for pairing purchase orders and requirements. During the allocation process, the system runs a date validity check. This ensures that incoming stock from purchase orders will fit within the time constraints for its assigned sales order. For example, if Customer A has ordered 100 pieces of SKU 123 and you have created a purchase order for that SKU to cover the order, then the purchase order should have a goods receipt date that is prior to the confirmed delivery date for the sales order. The system performs this check before allocation of a single requirement. Future receipts that fail the check are ignored for the current requirement being checked; they may, however, be considered for other requirements which fit the date constraints.

·        The release rule calculates the release to fixed status (MRP F) only on the basis of unrestricted stock.

For example, suppose you have an order for 100 pieces with an 80% release rule.

·         If an assignment achieves 80% fulfillment from a purchase order (future receipt) and 20% from unrestricted stock, all assignments will be given reserved status (MRP R).

·         Conversely, if you have 80% fulfillment from unrestricted stock and 20% from a purchase order, the assignment using physical stock will be set to fixed status (MRP F) because the release percentage is over 80%. However, the second assignment using the purchase order will retain MRP status R.

·        A second release check calculates the release on the basis of all assigned stock.

Using the above example, you have an order for 100 pieces with an 80% release rule. If an assignment achieves 80% fulfillment from a purchase order (future receipt) and 20% from unrestricted stock, all assignments will be given future fixed (MRP F).

·        Business Add-Ins (BAdIs) are available for the following:

¡        Deallocation when changing purchase orders and shipping notifications

¡        Deallocation when changing sales orders

¡        Deallocation during goods receipt

¡        Sorting for deallocations

¡        Deallocation during ARun Optimizer and ARun reorganization

¡        Preallocation of “best matching stock”

Restrictions

·        Secondary requirements are not supported for ARun mode 1 (normal). This includes components of production and subcontracting orders.

·        Purchase requisitions and planned orders are not supported for mode 1 allocations (normal). However, future allocation for these orders is possible in preview and simulation modes.

·        MM contracts cannot be allocated.

·        Allocation against future receipts cannot support spread logic over future receipts because of the different delivery dates in the sales orders.

·        Stock transfer orders are only linked as stock in the receiving plant, not in the supplying plant