Improve Your Company's Revenues with ATP in Sales Using SAP SD

  • by Gaetano Altavilla, Senior SAP Practice Manager
  • December 30, 2017
Learn about the processes involved in sales using Available-to-Promise (ATP) functionality. Read details about the main master data to be maintained in the system along with the main customizing settings available for this solution.
Learning Objectives

Reading this article, you’ll learn:

  • About the processes involved in Availability to Promise (ATP) in SAP sales and distribution (SD) and get details about the main customizing settings to be done in the system.
  • How to prepare master data for a product, characteristics and classes, and condition records.
Key Concept
The Available-to-Promise (ATP) quantity is calculated from the warehouse stock, the planned inward movements of stock (production orders, purchase orders, planned orders), and the planned outward movements of stock (sales orders, deliveries, reservations).

An Available-to-Promise (ATP) check is performed dynamically for each transaction (i.e., warehouse stock, inward and outward movement of stocks), taking into account the relevant stock and planned goods movements with or without replenishment lead time. Planned independent requirements are not taken into account here.

The ATP can be done at the following organizational levels:

  • Plant: The requirement of 1200 each (EA) can be completely covered by receipt 1 and plant stock. The plant stock can provide an ATP quantity of 300 pieces for future requirements.
  • Storage location: Only 300 pieces are confirmed for requirement 2 of 500 EA.
  • In case only one batch is entered, the check is carried out on two levels — first against the batch and then against the plant stock.
  • If a batch and a storage location are entered, the check is carried out on four levels — first against the batch storage location, then against the batch, then against the storage location, and then against the plant stock. Just as with the check on storage location level, the organization level with the lowest ATP quantity determines the result of the check.

This article can be used as a guideline during the realization phase of the project and during the pre-cutover to check that all the settings have been transported correctly.

I discuss the following topics:

  • Implement ATP processes in SAP SD
  • Master data preparation
    • Material’s Views
    • Condition Records
  • Transactional Data
    • Sales Order
      • Perform the ATP check
      • Outbound Delivery
        • Perform the ATP check
      • Good Issues
      • Post Billing
      • Verify the sales flow
  • Customizing
    • Configuration about ATP in Sales & Distribution

In Table 1, you can find an example about the ATP logic using the plant or storage location as organizational levels.


Gaetano Altavilla

Dr. Gaetano Altavilla is a senior SAP practice manager. His focus is on pre-sales, delivery of SAP application solutions for large international corporations, and SAP knowledge management in Europe, the Middle East, and Africa (EMEA).

In his 18 years of SAP application experience working for many multinational companies, such as Procter & Gamble and Hewlett-Packard, he has covered a wide range of ERP logistic areas, focusing on the MM, WM, SD, LES, PP, PP-PI, PLM (QM, PM, PS) modules, as welll as CRM (TFM), SRM (EBP), SCM (SAP APO), and MES (ME) components.

Dr. Altavilla holds a degree with first-class honors in mathematics from the University of Naples and is certified in many SAP modules: SAP Logistics Bootcamp, SAP MM, SD, LE (SHP/WM/LE), PP, PLM (PM, QM, PS), SRM, CRM, SCM (APO), SCM (TM), FI, CO, and Solution Manager. He also has experience in ABAP/4 and application link enabling (ALE) and IDocs. He has participated in numerous industry conferences, such as the SAP Skills Conference in Walldorf at SAP SE.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.