What Is Availability Check in SAP SD
Availability check in SAP SD (Sales and Distribution) is a critical component that ensures requested materials are available to fulfill customer orders on time. It works behind the scenes during sales order processing, ensuring customers get accurate delivery dates based on real-time stock, planned receipts, and outgoing requirements. Think of it as checking your fridge before promising someone dinner—you need to know what’s actually there.

The Core Concept: What is Availability Check in SAP?

At its heart, an availability check determines if enough stock is available to fulfill a customer's requested delivery date. This check factors in current inventory, incoming stock (such as from purchase orders or production), and outgoing commitments (such as existing sales orders or reservations). The availability check is not just about what you have right now—it’s about whether you’ll have enough at the right time.

When and Where Does Availability Check Trigger in SAP SD?

Availability check is automatically triggered during:
  • Sales order creation
  • Delivery creation
  • Scheduling agreement processing
  • Returns and backorder processing
It calculates the material availability date based on delivery scheduling, ensuring the material can be delivered on or before the customer's requested date.

Key Master Data Involved in Availability Checks

Several master data elements play a role in availability check:
  • Material Master: MRP 3 view contains the availability check settings.
  • Customer Master: Controls complete/partial delivery indicators.
  • Customer-Material Info Record: Can override settings for specific customer-material combinations.

Configuration Touchpoints for Availability Checks

Availability check depends heavily on the configuration done in the system. Important transaction codes and customizing points include:
  • OVZ2: Controls cumulation of requirement and confirmed quantities during sales order creation or change.
  • OVZ9: Used to set the scope of check and influence whether certain requirements (sales, reservations) are considered.

What’s Considered During an Availability Check?

Availability checks can include:
  • Current stock levels
  • Planned inward movements (purchase orders, production orders)
  • Planned outward movements (sales orders, deliveries, reservations)
The combination of what’s physically available and what’s expected to come in or go out forms the basis of the ATP (Available to Promise) logic.

Types of Availability Checks in SAP

SAP supports different types of availability checks:
  • ATP Check (Available to Promise): Most commonly used; checks real-time availability.
  • Check Against Planning: Compares against planned independent requirements.
  • Check Against Product Allocation: Used in industries with limited quantities for specific markets or customers.

How ATP Logic Works in Real-Time

ATP logic dynamically assesses availability by considering the scope of check, which includes defined elements such as:
  • Stock on hand
  • Incoming purchase orders
  • Scheduled receipts from production
  • Outbound sales orders and reservations
The checking group (from the material master) and checking rule (defined in transaction OVZ9) work together to control this logic.

Influence of Customer Agreements and Delivery Promises

Customer agreements can significantly affect availability check outcomes. For example:
  • Complete Delivery Required: The system will confirm only if the entire order quantity is available.
  • Partial Delivery Allowed: Allows confirmation of partial quantities if full is not available.
These are defaulted from the customer master and customer-material info record but can be overridden at sales order level.

The Role of Transfer of Requirements

Transfer of requirements enables communication between SD and MM/PP. When a sales order is saved, a requirement is transferred to MRP, allowing the system to plan procurement or production accordingly.Different requirement types (linked to requirement classes) influence how and when materials are planned. Configuration in transaction OVZG helps control this process.

Real-World Problem: Sales Order Not Triggering Availability Check

Sometimes, availability checks don’t behave as expected. One common issue is when a material appears to be available, but the system doesn’t confirm it in a new sales order. This can happen if:
  • The material is already reserved for another sales order
  • Data inconsistencies exist in requirement tables (e.g., VBBE)

Quick Fix: Using SDRQCR21 to Rebuild Inconsistencies

Program SDRQCR21 is often used to fix inconsistencies between SD and MRP requirements. Executed via T-code SE38, this program rebuilds requirement data by cleaning and recreating entries. It is a safe and SAP-recommended fix, but always test it in a non-production environment first.

Configuration-Based Long-Term Solution

To avoid repeated inconsistencies, you can tweak your availability check configuration:
  • Go to T-code OVZ9
  • Select the checking group and checking rule (typically A for Sales Orders)
  • Under the Inward/Outward Movements tab, uncheck 'Include Sales Requirements' and/or 'Include Reservations' to prevent double reservation
This setting helps prevent the same material from being over-confirmed across multiple sales orders.

SAP Best Practices and Recommendations

SAP recommends using:
  • Cumulation of requirement quantities when creating sales orders
  • Cumulation of confirmed quantities when changing orders
This ensures a balanced and performance-efficient availability check process.

Pro Tips for Functional Consultants and Power Users

  • Monitor ATP inconsistencies using transaction CO09
  • Use transaction MD04 to view detailed material planning
  • Refer to SAP Notes for known issues (e.g., Note 25444 on ATP check logic)
  • Always align business rules with system logic to avoid surprises

Conclusion: Why a Clean Availability Check Process is Crucial

Availability check isn’t just a background feature—it’s the backbone of timely deliveries, customer satisfaction, and operational efficiency. Ensuring a robust configuration, following SAP best practices, and proactively managing issues like inconsistencies can go a long way in making your order-to-cash process seamless.

Frequently Asked Questions (FAQs)

1. What is ATP check vs availability check in SAP?

ATP is a type of availability check that considers real-time stock, incoming and outgoing movements to determine available quantities.

2. Can availability check be bypassed?

Yes, but it's not recommended. You can configure sales document types or item categories to skip availability check, often used in special scenarios.

3. What happens if stock is reserved in another order?

That quantity is considered unavailable for new orders unless the existing order is changed or the requirement is deleted.

4. How does SAP handle partial deliveries during ATP?

SAP uses delivery rules from customer master or order level. If partial deliveries are allowed, the system will confirm what’s available.

5. Is SDRQCR21 safe for production environments?

Yes, but with caution. Always run in test mode first and use in production only when necessary and after backups.

Read also:
Checking Rule In Availability Check

SAP SD Books :-
SAP Sales and Distribution, Interview Questions, Certification and Configuration Books

Goto:
SAP SD Pricing

Back to :-
SAP SD (Sales and Distribution) Configuration Hints and Tips

Return to :-
SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips

(c) www.gotothings.com All material on this site is Copyright.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
All product names are trademarks of their respective companies.  The site www.gotothings.com is in no way affiliated with SAP AG.
Any unauthorised copying or mirroring is prohibited.