Scribd Logo
Upload

Welcome to Scribd!

  • 8 views

    Sapnote 0000123500

    Uploaded by

    José Armando Sisconeto
    This document discusses why the results of an availability check may differ from stock levels shown in other transactions. It explains that transaction CO09 must be used to understand availability check results, as it shows quantities as interpreted by ATP logic, unlike other transactions. The solution also notes that flag settings and checking rules must match between the availability check and CO09 for direct comparison.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Sapnote 0000123500

    Uploaded by

    José Armando Sisconeto
    8 views3 pages
    This document discusses why the results of an availability check may differ from stock levels shown in other transactions. It explains that transaction CO09 must be used to understand availability check results, as it shows quantities as interpreted by ATP logic, unlike other transactions. The solution also notes that flag settings and checking rules must match between the availability check and CO09 for direct comparison.

    Original Title

    sapnote_0000123500

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses why the results of an availability check may differ from stock levels shown in other transactions. It explains that transaction CO09 must be used to understand availability check results, as it shows quantities as interpreted by ATP logic, unlike other transactions. The solution also notes that flag settings and checking rules must match between the availability check and CO09 for direct comparison.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    8 views3 pages

    Sapnote 0000123500

    Uploaded by

    José Armando Sisconeto
    This document discusses why the results of an availability check may differ from stock levels shown in other transactions. It explains that transaction CO09 must be used to understand availability check results, as it shows quantities as interpreted by ATP logic, unlike other transactions. The solution also notes that flag settings and checking rules must match between the availability check and CO09 for direct comparison.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 3

    SAP Note 123500 - Controlling the results of the

    availability check
    Note Language: English Version: 2 Validity: Valid Since 11.02.1999

    Summary

    Symptom
    The results of an availability check (according to ATP logic) in
    production, process, maintenance order or in the Project System seem to be
    incorrect (that is, too large or too small confirmed quantities for the
    components checked) if you compare them with the output of the stock
    overview (Transaction MMBE) or the current stock/requirements list
    (Transaction MD04). This case can also occur for the results of processes
    which use the material availability check internally (for example, the
    batch determination).

    Additional key words


    ATP, CO01, CO02, COR1, COR2, CO28, COID, MD04, MMBE, CO09, VA01, VA02,
    VL01, VL02, collective availability check

    Cause and prerequisites


    In general, this is not a program error!

    Solution
    The values displayed in the two transactions stated (MD04, MMBE) cannot be
    used for understanding and for controlling the results of an availability
    check.
    Instead, you must use Transaction CO09 (Availability Overview). This
    transaction shows the development of the available quantities exactly the
    same way as it is taken into account in the availability check, that is,
    according to the ATP logic. In contrast to this, Transaction MD04
    interprets the data found according to the MRP logic and Transaction MMBE
    displays only the currently available stocks. In general, both can and will
    cause (depending on the settings in the scope of inspection) differing
    values.
    So that the information in Transaction CO09 also corresponds to the
    information during a check, you must enter the exact checking rule which is
    also used within the availability check on the selection screen of the
    transaction. It is relatively simple to determine the availibility check at
    least in the production order by selecting the respective component on the
    component overview and call in the menu entry 'Settings -> Availibility'.
    In the dialog box generated, in addition to the scope of inspection set
    also the checking rule is displayed in the header. Alternatively, a check
    can only be initiated (also in the other order types named) for the
    component considered. In this case, the system displays a dialog box 'Date
    overview' from which you can display, among other things, the scope of
    inspection.
    In addition, flag 'With reqmts qtys' is available on the selection screen
    as of Release 3.1H. You must only set this flag if you work with cumulation
    type '3' (you set it in the checking group, Transaction OVZ2) and want to
    have the values which are calculated by an availability check during the
    creation.
    Note also the information in Note 89362 which, in addition, explains
    something about the technical background.

    Header Data
    Release Status: Released for Customer

    13.03.2013 Page 1 of 3
    SAP Note 123500 - Controlling the results of the
    availability check
    Released on: 10.02.1999 23:00:00
    Master Language: German
    Priority: Recommendations/additional info
    Category: Consulting
    Primary Component: PP-SFC-PLN-CPT Components

    Secondary Components:
    PM-WOC-MO-MAT Stock material, bills of
    material, availability check
    PP-PI-POR Process Order
    PS-MAT Material
    SD-BF-AC Availability Check

    Valid Releases
    Software Component Release From To and
    Release Release Subsequent
    SAP_APPL 30 30D 31I X
    SAP_APPL 40 40A 40B X
    SAP_APPL 45 45A 45B X
    SAP_APPL 46 46A 46B X
    SAP_APPL 46C 46C 46C
    SAP_APPL 470 470 470
    SAP_APPL 500 500 500
    SAP_APPL 600 600 600
    SAP_APPL 602 602 602
    SAP_APPL 603 603 603
    SAP_APPL 604 604 604
    SAP_APPL 605 605 605
    SAP_BASIS 46 46D 46D

    Related Notes
    Number Short Text
    597233 ATP Server: Co-products are taken into account twice
    547118 FAQ: Result of ATP calculation
    457787 Collective SAP note: Advice notes ATP check
    326320 Component ovw.: incorrect call availability check
    321803 Explanatory notes on the ATP Customizing
    125848 Internal documentation collective availability check
    114100 Confirmed qty/date returned by availability check
    89362 No confirmation despite available quantity/stock

    Attributes

    13.03.2013 Page 2 of 3
    SAP Note 123500 - Controlling the results of the
    availability check
    Attribute Value
    Transaction codes CO01
    Transaction codes CO02
    Transaction codes CO09
    Transaction codes CO28
    Transaction codes COID
    Transaction codes COR1
    Transaction codes COR2
    Transaction codes MD04
    Transaction codes MMBE
    Transaction codes OVZ2
    Transaction codes VA01
    Transaction codes VA02
    Transaction codes VL01
    Transaction codes VL02
    old release 00146C SR1 R3STD
    0123500

    13.03.2013 Page 3 of 3

    You might also like