Requirements in Status F and R 

Use

If stock has been assigned in the full quantity to a sales order requirement during the allocation, the requirement receives the MRP status F (fixed) or R (Reserved). After that, this stock/requirements assignment can only be dissolved manually (via the ARun Optimizer).

Depending on the manner in which the release rule and action rule are customized, a requirement could only be partially allocated. Incase of a contract requirement (the latter is only possible starting with AFS release 2.5B), it can receive the MRP status R (reserved) if the appropriate setting of the allocation type has been made. After that, this stock / requirements assignment can also only be dissolved manually (via the ARun Optimizer).

 

In case customizing is as mentioned above, if a stock amounting to 80 pieces is assigned to a requirement of 100 pieces, 80 pieces would be reserved against the requirement. The remaining 20 pieces of the requirement would either be in the MRP status B or T depending on the stock situation.

During allocation, based on the stock selection rule and allocation rule various stock elements are considered. Batch stock, purchase orders, confirmations and production orders are the considered stock elements during an allocation run. However, a requirement could only get an F (Fixed) status in case it is assigned to batch stock. In case of future receipts like purchase orders, production orders and confirmations, the stock forecasted to come could be reserved by a certain sales orders.

A delivery can be created for requirements with fixed assignments (MRP status F) only. However, which requirements are selected for the worklist for delivery depends on the material availability date - that is, the date that resulted from the availability check as the delivery date for a schedule line.

By using rescheduling, you can control that allocated schedule lines are confirmed again for the original requested delivery date. You are then able to deliver on time, prevent keeping stock unnecessarily long in your warehouse, and prevent your customer from having to wait unnecessarily long for the delivery.

Features

A stock / requirements assignment met by ARun basically remains during rescheduling. The sort sequence you choose for rescheduling is irrelevant.

If the schedule line is already completely allocated (status F) or completely reserved (status R), it receives the original requested delivery date as the confirmed delivery date.

If there are two requirements records for the schedule line, you control how the system proceeds using your settings for the availability check run.

Requirement Completely in F/R

If you use rescheduling in this case, a result of the availability check achieved during the order entry is adjusted to a different result of the allocation.

Your customer has ordered 100 blouses in size S. The requested delivery date was January 1, 2001. During the order entry, the result of the availability check was that no stock can be assigned for this date. The end of the requested delivery time (February 1, 2001) has been determined and confirmed as the earliest possible delivery date.

The allocation run did, however, assign warehouse stock in the full requirement quantity (100 pieces) to this requirement. The requirement is therefore completely in MRP status F.

If you execute rescheduling for your material blouse at this point, the system recognizes that there is already a fixed stock assignment for this requirement. The stock quantity is also immediately available because it is warehouse stock. The original requested delivery date can therefore be kept and is confirmed as the delivery date for this requirement.

This also applies if a requirement in the full requirement quantity has the MRP status R. In this case, warehouse stock has been reserved for a requirement during the allocation. This assignment is just as binding as a fixed assignment of stock to a requirement. One possible reason why stock has in this case not been immediately fixed for a requirement could be a special setting of the release rule of the allocation type used during the allocation. Even during rescheduling, the availability check cannot use stock to meet a requirement that has already been reserved for another requirement.

Requirement Proportionally in F / R

A single schedule line of requirement could constitute some of its quantities having an F (Fixed) status, some an R (Reserved) status and some unassigned. This is due to the various options open to you when configuring the allocation run, which allow you to decide for each allocation run when an assignment of warehouse stock to a requirement is released.

See also Logics in the ARun Release Rule

During the order entry, you confirmed for your customer 500 pieces in one size for the requested delivery date, which is March 30, 2001. In case you are not able to deliver the full quantity, your customer will also accept a delivery of only 80% of the original purchase order quantity per schedule line. At the time of the allocation there is indeed not enough stock available. Only 400 pieces of stock (80%) can be assigned to the requirement (500). According to the release rule Min. Quota = 80% of SL, this allocation is successful.

There are now two requirements records for the schedule line in the stock / requirements list: one for 400 pieces in status F, and one for 100 pieces in status Bor T, depending on the stock situation.

In the sales order the schedule line remains unchanged with all 500 pieces.

During rescheduling, how the schedule line with several requirements records is handled depends on the settings you have made for the availability check run in the background for each sales document category per sales area (in AFS Customizing under Sales and Distribution ® Sales ® Sales Document Header ® Maintain order types per sales area).

See also: Presettings for the Availability Check

·        If you choose Proposal ATP values, the schedule line is split in the same manner as the requirements records that exist for it. The schedule line with status F or Rreceives the original requested delivery date as the confirmed delivery date. The rest of the schedule lines are checked by the availability check as usual. That means that they are either confirmed or rejected for the date of the next incoming stock.

For the schedule line in the above example: You receive two schedule lines, one for 400 pieces and completely in MRP status F, and one for 100 pieces and in MRP status T or B. The schedule line in status F receives the requested delivery date as the confirmed delivery date, and the system checks for which other date the second schedule line can be confirmed. If this fails, it is rejected.

·        If you choose Full quantity with latest delivery date, the availability check runs for the part of the schedule line whose requirements record is not F or R. The date that the availability check can confirm as the delivery date is then valid for the complete schedule line.

·        If you choose One time with order requested delivery date, the requirement quantity of the schedule line is reduced by the amount for which there is no requirements record in F or R. The requested delivery date is then confirmed as the delivery date for the schedule line. The remaining requirement quantity is rejected.

For the schedule line in the example above, this means that the 100 pieces of the requirement quantity in MRP status T or B are rejected. The 400 pieces in Fremain and the requested delivery date of the customer is confirmed as the delivery date for the schedule line.