Availability Check in ERP

Requirements, receipts and stocks are managed in SAP R/3 on different levels.These are:

 Plant
 Storage location
 Batch
 Batch / storage location

Every requirement, stock, receipt that exist on a certain level also exits on all superior levels. So for example a
requirement which exists on storage location level also exits on plant level.

Attention: When the indicator ‘SLoc MRP indicator’ in the material master (MRP View 4, for the relevant storage
location) is maintained and this storage location is maintained in the sales document then the sales requirement exists
only on the storage location level. A sales requirement does not exists on plant level either if you are working with mrp
areas. So ATP check will be carried out only on storage location level.

Since the availability check can be carried out for example only on plant level or on plant and storage location level, the
availability check has to consider all levels until up to the plant level before a requirement can be confirmed.

Let us have a look at an example. As you already know transaction Co09 is the relevant transaction where you can
check the availability situation.
The starting situation is that we have 170 on stock. The stock is distributed to three storage locations (WS1, WS2 and
WS3). Furthermore the stock is distributed to the batches 0000000483, 0000000484, 0000000795, 0000000796. The
blue lines always represent an own level. Stock = plant level StLcSt = storage location level BtchSt = batch level BStLoc
= batch/storage location level.

Now we create a sales order 16749 with quantity 50 and we maintain storage location WS2 and batch 00000000483.
You can see that the sales order appeared under the different levels. You can see it under the plant level, storage
location level WS2, batch level 0000000483 and batch/storage location level 0000000483/WS2. When you compare this
screen shot with the previous one then you can also see that the cumulated ATP quantity has been reduced by the
confirmed quantity.

Now we create a second sales order 16751 with quantity 120 where only the plant is maintained.
You can see that sales order 16751 only appears under the plant level. This is the case because no storage location
and/or batch has been maintained in the document. The documents/orders are displayed in transaction Co09 on the
levels which are maintained in the document. In this case the ATP check has been carried out on the plant level only.
The cumulated ATP quantity has been also reduced on plant level only.

Now we create a further sales order 16752 with quantity 1 where storage location WS3 is maintained.
 In the column ‘Confirmed’ you can see that the sales order has not been confirmed despite of having enough stock on
storage location level. On storage location WS3 you have a stock of 100. The ATP check always checks all involved
levels. This means the system checked the situation on storage location level where the quantity can be confirmed but it
also checked the plant level and there nothing is available. The confirmed quantity of a document is always the
minimum quantity of all checks on the levels that are involved. If you have batches then also the batch level will be
checked.

Backorder Processing
Skip to end of metadata

 Created by Former Member, last modified by Agnes Sziladi on Apr 19, 2018
Go to start of metadata

Purpose
The purpose of this page is to explain which different possibilities of backorder processing exist and how they work.

Overview
Backorder Processing can be carried out for SD and PP documents. There are mass processing possibilities and also
backorder possibilities for single records.

 Transaction V_V2 / report SDV03V02

 Transaction Co06

Transaction V_V2 / report SDV03V02

1. Report SDV03V02 / Transaction V_V2 is used for the rescheduling of sales documents like e.g. quotations, sales
orders, scheduling agreements and stock transport purchase requisitions / stock transport purchase orders.
2. The rescheduling for sales documents is always carried out for the whole item. It is not possible to carry out the
rescheduling for a special schedule line. This means that when rescheduling is carried out for a scheduling agreement
item then the whole item with all schedule lines will be rescheduled. It is not possible to carry out rescheduling only for a
specific schedule line.
3. Regarding the setting 'Unconfirmed documents required' please check SAP note 1588423 - V_V2 / SDV03V02 -
Unconfirmed documents required .
4. The selection criteria or the sorting criteria cannot be enhanced in the SAP standard. You have the possibility to use the
report as template and to modify it according to your business needs. Please consider SAP note 549064 - FAQ:
Rescheduling/backorder updating in R/3 question 2 and SAP note 1897242 - Missing BAdI for XTAB_SORT in
rescheduling V_V2 .
5. Report SDV03V02 selects all open sales documents independent of whether transfer of requirements and/or ATP check
is activated or not. If you would like to exclude e.g. quotations from the selection then you have to modify the report.
6. The report selects all relevant documents according to the selection criteria and sorts them according to the sorting
criterias. The confirmed quantities of the documents will be released and after that the sorted documents will be atp
checked one after the other.
7. The sorting of the result is NOT the same as the sorting of the documents for the ATP check. The sorting of the result
list happens in the subroutine AUSGABE of include LV03RF0A: SORT output STABLE BY
matnr werks kunnr vbeln posnr. So the sorting is according to material number (matnr), plant (werks), customer
number (kunnr), document number (vbeln) and item number (posnr). The result list is stored in the clustered table INDX.
The result of the rescheduling run will be also stored on the database when it is run in simulation. SAP note 1037547 -
Modification: Rescheduling simulation writes to cluster provides a modifcation in order to prevent the saving of the
result in case of a simulation run.
8. Sales document items that use product allocation have to be excluded from rescheduling. Product allocation and
rescheduling cannot be used together.
 Troubleshooting Guide for report SDV03V02 / transaction V_V2

1. In the result list you can see materials that have not been specified in the initial screen of transaction V_V2 or
report SDV03V02:
Please check SAP note 1491650 - V_V2 / SDV03V02 - non-selected materials in the result list
2. Rescheduling does not confirm partial quantities these means the sales document or purchase document does not get
any confirmation when only a partial quantity is available:
The setting 'Avail.check rule' in transaction OVZJ controls which result (e.g. full delivery, delivery proposal, etc.) the
system takes over during the rescheduling run. If the system does not confirm partial quantities then please check this
setting. When setting the value 'E' then partial quantities will be accepted. Please check SAP note 33084 - Confirmation
during rescheduling . This is valid for sales documents. For purchase documents please check the setting in:
Customizing (transaction SPRO) -> Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport
Order -> Assign Delivery Type and Checking Rule -> field: 'Av.Ch.Rule' (V_161V-REVFE).
3. Some sales documents will not be selected and thus not rescheduled: Sales document items with assembly process
(dynamic or static assembly process) or 'Fixed date and Quantity' set will be not selected. Regarding product selection
please consider SAP note 549064 - FAQ: Rescheduling/backorder updating in R/3 question 6. For contracts please
consider SAP note 1768866 - Rescheduling (transaction V_V2 / report SDV03V02) ignores contract document types .
4. Dates of partially delivered shcedule lines are changed / delivered schedule lines are swapped / the confirmed quantity
of the requested schedule line is changed after the rescheduling run leaving the requested date unchanged. Please
consider that this behavior is not wrong from requirements perspective because the schedule line is already referenced
and it is the follow-up document that holds the requirement making the sales order schedule lines' dates irrelevant. If the
sales order has more confirmed schedule lines that are partially delivered only the dates of the requested schedule line
are important.

Backorder Processing with transaction Co06

Transaction Co06 can be used for manually distributing available quantities. It is an expert tool! Please check SAP
Note 1906338 - Everything about transaction Co06 for further information.

How to check the ATP situation

Skip to end of metadata

 Created by Former Member, last modified on Jan 22, 2016

Go to start of metadata

Purpose
The purpose of this page is to explain how to cehck the ATP situation for a material.

Overview
 Transaction Co09

Availability Overview - Transaction Co09

Transaction Co09 is the only suitable transaction to check the availability situation. In transaction MD04 and MMBE the
scope of check is not considered, so it does not provide you the information on what stocks, receipts and issues will be
considered during the ATP check.
The initial screen:

On the initial screen you define the material and plant / MRP area. The checking rule is very important as it defines
together with the checking group (material master, MRP3 view) the scope of check (transaction OVZ9). In the scope of
check it is defined which stocks, receipts and issue elements should be considered during an availability check.
Therefore different checking rules can lead to different scope of checks and by that, to different availability situations
displayed in transaction Co09. The checking rule for sales orders and deliveries is hard coded. For PP, MM, etc.
documents you can define your own checking rules. Please consider the corresponding WIKI pages. Furthermore when
you are using special stocks then you have to extend the checking rule with the special stock indicator. This part we will
cover in a later section. The flag for ’With reqmts quants’ is relevant when you are using accumulation ’3’. In this case
you can check the availability situation in case of creating a new document.
Now have a deeper look at transaction Co09.
In the section ‘Totals display’ you have a summary about all receipts, issues and confirmed quantities. Here you can
easily see whether you have some available quantity left or even a situation with over confirmation. Every blue line
represents a specific level. ‘Stock’ is the plant level, StLcST is the storage location level, BtchSt is the batch level and
BStLoc is the batch/storage location level. Please also check the WIKI how the ERP ATP check works. The plant stock
is usually the sum of the storage location stocks. If a storage location is planned separately then the quantity of that
storage location is not added to the plant stock. In the column ‘Rec./reqd qty’ you can see the different stocks on the
different levels (blue lines) and (when existing) the quantities of the receipts and issues. In the column ‘Confirmed’ you
see the confirmed quantities of the different issue elements. The cumulated ATP quantity represents the available
quantity. How the cumulated ATP quantity is calculated will be explained later on. Now we will create a sales order with
quantity of 80 for storage location WS1 and batch WS3.
The sales order appears on all levels which have been maintained in the order and you can see that the cumulated ATP
quantity has been reduced also on all levels. For batch WS3 only 70 are available and therefore the whole requested
quantity cannot be confirmed. Currently you see totals record in Co09. So actually you do not know whether the
requested quantity of 80 is distributed to several sales orders or not. If you are using single requirements records (that
means the requirements will be stored in table VBBE) then you can display some more detailed information by pressing
the button ‘Totals records’. For summarized requirements (table VBBS) this is not possible.
Now you can see which document(s) is (are) causing the totals records.
In addition to the requirement we now create a receipt element.
In the purchase order only the plant and storage location has been maintained. Therefore the purchase order is only
visible on these levels. For receipt documents the same applies as for issue documents. The documents are considered
on the levels which are maintained in the documents. The cumulated ATP quantity will be increased on that date where
the receipt will come in.

Now let us have a look how the cumulated ATP quantity is calculated. We have the following situation:
First the theory and after that we will take a look at the example. The example will cover the plant level that is
highlighted. It works the same on all other levels. Prerequisite is that you use accumulation which can be activated in
the customizing of the checking group (transaction OVZ2) and is strongly recommended by SAP.

1. The cum. ATP qty. will always show the maximum qty. that could be confirmed on this date if a simulated requirement
was entered on this line.

2. The cum. ATP qty. will be increased on the date of a receipt if the receipt is greater than the issues below it (until the
next receipt element, of course).

3. The cumulative ATP quantity cannot be greater than the figure for Total receipts - Total Confirmed Issues. Otherwise
you can get any over confirmation.

The calculation (plant level):

We have a stock of 115 and an issue of 70 on 15.01.2016. 115 – 70 = 45. 45 cannot be taken over as there are further
issues that reduce the cumulated ATP quantity. The issues are bigger than the next receipt so the cumulated ATP
quantity will be reduced further. There is a purchase order with quantity 30 and two sales orders with quantity 20 and
15. So the calculation will be as follows: 45 + 30 – 20 – 15 = 40. Therefore the cumulative available quantity till
13.07.2016 is 40. In other words this means that from 13.01.2016 to 12.07.2016 you can confirm a further quantity of
40. On 13.07.2016 a further receipt is considered with a quantity of 90 and there are no further issues. Therefore the
cumulated quantity will be increased to 130 (40 + 90 = 130). Another example and many other information you will find
in SAP Knowledge Base Article 1893237 - Everything about transaction Co09.

Let’s have another look at transaction Co09 when the Replenishment Lead Time is activated in the scope of
check.
In screen shot above you can see that the situation has changed when using the Replenishment Lead Time. Please
have a look at SAP Knowledge Base Article 2135782 which explains the calculation of the Replenishment Lead Time. In
the screen shot you can see that the cumulated ATP quantity is not calculated after the End of Replenishment Lead
Time. The last purchase order is not considered any more. After the End of Replenishment Lead Time neither issue nor
receipt elements have any effect on the available quantity as everything can be confirmed after the End of
Replenishment Lead Time.

In the next step we create a sales order for a Make-to-Order scenario. In the MTO scenario you are working
with special stocks. The special stock indicator is ‘E’ and you can find it in the customizing of the requirements class
(transaction OVZG) or in the customizing of the item category (transaction VOV7).

In transaction MD04 you will find a separate section for the sales document.

The blue line is your special stock segment and under the blue line you can see the corresponding sales document. The
MRP element data of the blue line show always the first document that you have created with a special stock indicator.
This means when you first have created a quotation then you will see the quotation number in the blue line even when
you have already created the sales order with reference to that quotation. All documents that you create with the
account assignment to a special sales document will be displayed under the blue line of that special sales document in
MD04. Now let us check transaction Co09 for this sales document. We call transaction Co09 with following data.
You will see the following situation:
You can see that sales order 16832 is not displayed in transaction Co09. In order have the correct available situation for
such a MTO order you have to call transaction Co09 in a different way. First the checking rule is not ‘A’ in this case. The
checking rule in case of using special stocks is (in case of sales documents) ‘A’ + ‘special stock indicator’, which means
‘A’ + ‘E’ = ‘AE’. If you would have project stock you would use ‘AQ’. Please also have a look at the F4 Help of the
checking rule in Co09.
Just changing the checking rule to ‘A’ is not sufficient. In case of using special stocks you also have to maintain the
special stock element e.g. sales order and item number, WBS element, etc.. So in our example the following data have
to be maintained on the selection screen of Co09 in order to get the correct availability situation.
And we can see the availability situation that has been considered during the ATP check.
Here you can also see the special stock segment. We have nothing on stock and there is no receipt element. Therefore
the sales order could not be confirmed. By checking the situation with checking rule ‘A’ you cannot see any reason why
the sales order could not be confirmed. It is very important to check the availability situation in transaction Co09 with the
correct data.

Negative cumulated ATP quantity.

In many cases you cannot confirm a requirement because of a negative cumulated ATP quantity. Sometimes the
negative cumulated ATP quantity is not visible at first (when you enter the transaction).
So please scroll to the right in order to the fully display the cumulated ATP quantity field.
And so you can see the negative prefix.

The negative cumulated ATP quantity prevents the further confirmation of documents. Also when you carry out a new
ATP check in a confirmed document then the document might be unconfirmed totally as the whole confirmed quantity of
the document is used to cover the negative cumulated ATP quantity. The negative cumulated ATP quantity has the
highest priority.

Storage location excluded from MRP or planned separately.

In the material master on MRP view 4 you can maintain that a specific storage location should be excluded from MRP or
planned separately.
This setting has also an effect on the availability check. Let us have a look on how the availability situation in transaction
Co09 has changed.
All documents that are assigned to that storage location cannot be seen any more on plant level and so they are also
not considered in the calculation of the cumulated ATP quantities.
You can also see that the stock on storage location WS1 is not included on plant level. This means when you have a
document where such a storage location is assigned to then the ATP check is only carried out on that storage location
level. On plant level the system will not carry out an ATP check.