SAP SD Credit Management

You are an SAP SD (Sales and Distribution) consultant. The user wants to set up credit management with credit limits and automatic checks in SAP to prevent overselling and manage customer risk.

What to check first

• Run SE16N /APP/CREDI_MASTER to verify credit master data table exists and is populated
• Check transaction OVA9 to confirm your company code has credit control area assigned
• Verify customer master records exist in SE16N KNA1 with credit group assignments in field KDGRP

Steps

1. Navigate to OVA9 (Assign Company Code to Credit Control Area) and ensure your company code is linked to a credit control area—create one if needed via OVAB
2. Use transaction OVA1 to define credit groups and their control parameters; assign each group a credit limit currency and risk category
3. Go to OVA3 to set up credit limit determination rules—define whether limits are based on customer, group, or plant level
4. Configure automatic credit check in OVA7 to trigger at document entry time; set the check type to "Online" for real-time validation
5. Assign credit group in transaction FD32 (customer master, Sales area tab) to link each customer to their credit control group
6. Set individual customer credit limits in FD32 under the Credit Management tab—enter KKBER (credit control area) and KKGRP (credit group) with limit amount in XLGD1
7. In OVA8, define the credit check procedure: specify which document types (orders, deliveries) require checks and at which stage
8. Test the setup by creating a sales order in VA01 that exceeds the credit limit—the system should block or warn based on your tolerance settings in OVAC

Code

*& Report: Setup Credit Management Check
REPORT z_credit_mgmt_setup.

DATA: lt_customers TYPE TABLE OF kna1,
      ls_customer TYPE kna1,
      lt_credit_master TYPE TABLE OF /app/credi_master,
      ls_credit_data TYPE /app/credi_master,
      lv_credit_limit TYPE dmbtr,
      lv_customer_id TYPE kunnr,
      lv_credit_group TYPE kdgrp,
      lv_company_code TYPE bukrs,
      lv_credit_area TYPE kkber.

PARAMETERS: p_bukrs TYPE bukrs DEFAULT '1000',
            p_kunnr TYPE kunnr,
            p_limit TYPE dmbtr DEFAULT 100000.

SELECTION-SCREEN BEGIN OF BLOCK cred WITH FRAME TITLE TEXT-001.
  PARAMETERS: p_kdgrp TYPE kdgrp DEFAULT 'Z001'.
SELECTION-SCREEN END OF BLOCK cred.

START-OF-SELECTION.

  " Step 1: Fetch customer master data
  SELECT * FROM kna1 INTO TABLE lt_

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