Availability Check for Components 
Availability Check for Components
Use
There are two different logics, which you can use to carry out the availability check for components (both standard and AFS) in the AFS production order: the SAP standard logic and the logic that has been especially developed for the production planning and control in AFS.
You can use both logics to carry out the availability check of the components in the production order, but the AFS logic can only be used for the production planning and control (AFS Customizing). This logic was especially developed for customers who want to use the availability check for rush orders.
Features
SAP Standard Availability Check Logic
If you use the SAP standard availability check the requirements to be checked are considered according to the requested delivery date. Here, the availability check checks the requirements according to their creation sequence (see
Availability Check (ATP)).
According to the SAP standard logic, already existing orders are first checked and confirmed. Requirements with an earlier requirements date but which arrive later do not get preference. As a result, rush orders might be rejected, although there is enough stock on their requirements date and the requirements date of the already existing orders are later.
Availability Check Logic for Production Planning and Control in AFS
The availability check for production planning and control in AFS arranges the requirement to be checked in chronological order of the already existing requirements, according to its requirements date. That means that the requirements are checked and confirmed in the sequence of their requirements dates. Here the time of their creation is not taken into account.
By using this special logic for the production area in AFS rush orders might take already confirmed stock from orders with a later requirements date. This happens because the system prefers, checks and confirms orders with an earlier requirements date. The already confirmed order retains the same status, although the confirmed quantity no longer corresponds to the requirements quantity. This can lead to inconsistencies.
We therefore recommend that you carry out a collective availability check to correct the inconsistencies mentioned above.
Example for the Availability Check Logic for Production Planning and Control in AFS
Initial situation: Stock in warehouse: 100 pieces
|
Order |
Requirements date |
Requirement quantity in pieces |
Confirmed quantity in pieces |
|
Order 1 |
30.11.2002 |
50 |
50 |
|
Order 2 |
15.12.2002 |
20 |
20 |
|
Order 3 |
20.12.2002 |
30 |
30 |
If order 4 with requirements date 17.12.2002 and requirement quantity of 20 pieces is opened / released, the AFS availability check distributes the stock of 100 pieces as follows:
|
Order |
Requirements date |
Distributed stock in pieces |
|
Order 1 |
30.11.2002 |
50 |
|
Order 2 |
15.12.2002 |
20 |
|
Order 4 |
17.12.2002 |
20 |
|
Order 3 |
20.12.2002 |
10 |
As soon as the system checks the availability of the components for order 4, it confirms the order.
Order 3, which was already confirmed with 30 pieces, therefore has a material shortage of 20 pieces. The already confirmed quantity of 30 pieces is not automatically reset for this order. It is therefore necessary to carry out a collective availability check on a regular basis that checks and confirms all orders according to their requirements dates.
After a collective availability check, the following situation arises:
|
Order |
Requirements date |
Requirement quantity in pieces |
Confirmed quantity in pieces |
Missing parts in pieces |
|
Order 1 |
30.11.2002 |
50 |
50 |
|
|
Order 2 |
15.12.2002 |
20 |
20 |
|
|
Order 3 |
17.12.2002 |
20 |
20 |
|
|
Order 4 |
20.12.2002 |
30 |
10 |
20 |