If you create a sales order in the OLTP system and carry out the availability check in APO, you branch to a delivery proposal screen. If you simulate an availability check in APO, you branch to a confirmation proposal screen.

On the APO: Availability Check: Delivery Proposal screen, you can select a delivery proposal.

The system checks here if the requested delivery date can be met. If stock for the desired product exists on the requested delivery date, the system proposes the stock quantity. If stock does not exist, a zero appears as the confirmed quantity.

The system checks here if enough stock for a full delivery exists on any later date. If enough stock to cover a request from the sales document exists on a later date, the system proposes the date. If a full delivery is not possible on any later date, the system displays no proposal.

In an availability check in which the checking horizon is taken into account, the system proposes the date on which the checking period expired, if the stock did not cover the incoming orders quantity before the end of the checking horizon.

In an availability check in which the checking horizon is not taken into account, the system is oriented towards stock and planned receipts.

To adopt this solution in the sales document, choose (Full delivery/confirmation).

The system checks here if, and on which dates, partial deliveries are possible. The system proposes partial deliveries on different dates based on the planned receipts and issues on the time axis.

In an availability check in which the checking horizon is taken into account, the system proposes the date that lies beyond the end of the checking horizon, if the stock cannot cover a partial delivery before the end of the checking horizon.

In an availability check in which the checking horizon is not taken into account, the system proposes dates on which partial deliveries are possible based on existing stock.

To accept this solution, choose (Delivery/confirmation proposal).

The system gives a warning in the form of a pushbutton if, for example, a date shift occurs during the combination of basic methods (product availability check as the first check method, product allocation as the second).

If you are working with product allocation it is possible that the product allocation that caused the confirmation is no longer valid. The availability check returns the late confirmation but also gives a warning. The warning is given regardless of whether the confirmation date lies outwith the validity of a product allocation.

If you receive such a warning in the confirmation proposal (simulation) or delivery proposal screen, you should check the detailed results of the individual basic methods.