$120 tested Claude codes · real before/after data · Full tier $15 one-timebuy --sheet=15 →
$Free 40-page Claude guide — setup, 120 prompt codes, MCP servers, AI agents. download --free →
clskills.sh — terminal v2.4 — 2,347 skills indexed● online
[CL]Skills_
SAPbeginnerNew

SAP SD Customer Master

Share

Create and maintain customer master data with sales areas

Works with OpenClaude

You are an SAP SD (Sales and Distribution) consultant. The user wants to create and maintain customer master data with sales areas in SAP.

What to check first

  • Access transaction code VA01 (Create Customer) or VD01 (Create Customer - alternative) in your SAP system
  • Verify you have authorization object M_CUST_GRP (Customer Master) with create/change activity levels
  • Check that your user has access to the relevant sales organization and distribution channel

Steps

  1. Open transaction VD01 in the SAP command palette (type /nvd01 in any SAP field) to create a new customer master record
  2. Enter the Account Group (Kontotype) — e.g., CUST for regular customers or DEB for customers who are also vendors
  3. Fill General Data tab: Customer Name, Address (Street, City, Postal Code, Country), and Communication fields (Phone, Email)
  4. Navigate to Sales Area tab and click New Entry to add a sales area; select Sales Organization, Distribution Channel, and Division from dropdown
  5. In the Sales Area section, populate key fields: Customer pricing procedure (VKORG), Customer group, Sales district, and tax classification
  6. Set payment terms (Zahlungsbedingungen) in the Payment Terms tab — define baseline date and net payment days
  7. Configure Shipping conditions (Versandbedingungen) and Incoterms for logistics planning
  8. Enter partner functions (Soldto party, Bill-to party, Ship-to party, Payer) — link related customer numbers if applicable
  9. Save the customer master record using Ctrl+S; SAP generates a customer number (manually assigned or auto-assigned based Customizing)

Code

REPORT zsd_create_customer_master.

DATA: lv_kunnr TYPE kna1-kunnr,
      lv_name1 TYPE kna1-name1,
      lv_ort01 TYPE kna1-ort01,
      ls_kna1  TYPE kna1,
      ls_knvv  TYPE knvv,
      lv_vkorg TYPE knvv-vkorg,
      lv_vtweg TYPE knvv-vtweg,
      lv_spart TYPE knvv-spart.

* Define customer master data
ls_kna1-name1 = 'ACME Corporation'.
ls_kna1-ort01 = 'New York'.
ls_kna1-land1 = 'US'.
ls_kna1-pstlz = '10001'.
ls_kna1-stras = '123 Main Street'.
ls_kna1-kunnr = '0000001000'.
ls_kna1-ktokd = 'CUST'.

* Populate sales area data
lv_vkorg = '1000'.
lv_vtweg = '10'.
lv_spart = '00'.

ls_knvv-v

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

Quick Info

CategorySAP
Difficultybeginner
Version1.0.0
AuthorClaude Skills Hub
sapsdcustomer

Install command:

curl -o ~/.claude/skills/sap-sd-customer-master.md https://clskills.in/skills/sap/sap-sd-customer-master.md

Related SAP Skills

Other Claude Code skills in the same category — free to download.

Want a SAP skill personalized to YOUR project?

This is a generic skill that works for everyone. Our AI can generate one tailored to your exact tech stack, naming conventions, folder structure, and coding patterns — with 3x more detail.