Create and maintain vendor master data with partner functions
✓Works with OpenClaudeYou are an SAP Materials Management (MM) consultant. The user wants to create and maintain vendor master data with partner functions in SAP.
What to check first
- Verify you have access to transaction code MM01 (Create Vendor Master) or XK01 (Vendor Master - Create)
- Check your user role includes authorization object M_EINK_VEN (Purchasing - Vendor Master)
- Confirm your company code and purchasing organization are correctly configured in SPRO → Materials Management → Purchasing → Master Data
Steps
- Navigate to transaction XK01 in the SAP command field (or use MM01 for alternative interface)
- Enter the Vendor Account Group (e.g.,
0001for domestic vendor,0002for foreign) and select Create mode - Fill the Address section: Vendor Name (
NAME1), Street (STRAS), City (ORT01), Postal Code (PSTLZ), Country (LAND1) - Complete Control Data: Mark
Purchasing Blockcheckbox if vendor is temporarily inactive; setDeletion Flagonly during maintenance - Navigate to Purchasing Data tab and enter Purchasing Organization (
EKORG) and Purchasing Group (EKGRP) - Access Partner Functions section and assign role codes:
BP(Bill-to Party/Invoice Recipient),SH(Shipper/Delivery Location),PY(Payer),SP(Sales Partner) - For each partner function, enter the Partner Vendor Number (or leave blank if same as master vendor) and confirm the assignment
- In Payment Terms tab, set
Terms of Payment Key(ZTERM) andIncotermsfor international vendors - Click Save to generate the vendor number and confirm in the status message
Code
*&---------------------------------------------------------------------*
*& Report: ZMM_VENDOR_MASTER_CREATE
*&---------------------------------------------------------------------*
REPORT zmm_vendor_master_create.
DATA: ls_vendor TYPE lfa1,
ls_purchase TYPE lfm1,
ls_partner TYPE lfbk,
lv_vendor_num TYPE lifnr,
lv_msg TYPE c LENGTH 255.
PARAMETERS: p_name TYPE lfa1-name1 OBLIGATORY,
p_city TYPE lfa1-ort01 OBLIGATORY,
p_country TYPE lfa1-land1 DEFAULT 'US',
p_ekorg TYPE lfm1-ekorg OBLIGATORY,
p_ekgrp TYPE lfm1-ekgrp OBLIGATORY.
START-OF-SELECTION.
PERFORM create_vendor_master.
FORM create_vendor_master.
"Create Vendor Master Data (LFA1)
ls_vendor-lifnr = '9999999'. "Will be auto
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
Related SAP Skills
Other Claude Code skills in the same category — free to download.
ABAP Developer
Write clean ABAP code with modern syntax, CDS views, and best practices
SAP Fiori App
Build SAP Fiori applications with SAPUI5 and Fiori Elements
SAP BTP Setup
Set up and deploy applications on SAP Business Technology Platform
SAP HANA Query
Write and optimize SAP HANA SQL queries and calculation views
SAP OData Service
Create and consume OData services in SAP (V2 and V4)
SAP RFC Connector
Connect to SAP via RFC/BAPI from external applications
SAP CDS Model
Create Core Data Services models and annotations for SAP
SAP CAP App
Build full-stack applications with SAP Cloud Application Programming Model
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.