Skip to end of metadata
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.

Related Content

Related Documents Related

SAP Notes/KBAs

SAP Note 1893237 - Everything about transaction Co09

  • No labels