SAP SD Availability Check

You are an SAP SD consultant specializing in ATP (Available-to-Promise) configuration. The user wants to configure availability checks and backorder processing for sales orders in SAP.

What to check first

• Run transaction SPRO and navigate to Sales and Distribution → Sales → Availability Check and Transfer of Requirements to verify current IMG settings
• Check transaction OVZG to review your plant-specific availability check groups and their assigned checking rules
• Run MD04 (Stock/Requirements List) for your material to see current stock and demand situation before configuring rules

Steps

1. Access SPRO → Sales and Distribution → Sales → Availability Check and Transfer of Requirements → Define Checking Rules
2. In transaction OVZC, maintain the availability check group assignment to your materials (assign group like "01" for ATP check)
3. Navigate to OVZB to configure the checking rule details—set required fields: Checking Rule (e.g., "ATP"), Description, Scope (whole plant or storage location), and ATP Logic (set to ATP for forward-looking availability)
4. Define backorder processing in VOV8 (Sales Document Types)—enable "Backorder Processing" checkbox and set the Backorder procedure (typically "1" for standard backorder)
5. Configure the ATP strategy in OVZG (Plant-specific settings)—select your plant and assign the checking rule created in step 3
6. Set up delivery-related availability in VSBP (Shipping Point Determination)—link materials to shipping points that will trigger ATP checks
7. Test the configuration by creating a sales order in VA01—enter material, quantity, and customer plant to trigger the ATP check algorithm
8. Review the ATP check result in the sales order item detail screen (field "ATP" shows available quantity); if insufficient stock, the system allows backorder entry based on your VOV8 configuration

Code

*&---------------------------------------------------------------------*
*& Report: Configure ATP Availability Check and Backorder Processing
*&---------------------------------------------------------------------*
REPORT z_atp_availability_check.

DATA: lt_mara TYPE TABLE OF mara,
      lt_marc TYPE TABLE OF marc,
      ls_marc TYPE marc,
      ls_tvgg TYPE tvgg,
      lt_tvgg TYPE TABLE OF tvgg,
      lv_material TYPE matnr,
      lv_plant TYPE werks_d,
      lv_check_rule TYPE atpkz,
      lv_atp_qty TYPE menge_d,
      lv_stock_qty TYPE labst.

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE TEXT-001.
  PARAMETERS: p_matnr TYPE matnr OBLIGATORY,
              p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.

START-OF-SELECTION.

  lv_material = p_matnr.
  lv_plant = p_plant.

  " Fetch material master data

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change