acc

 

GENERAL VENDOR MASTER DARA PROCESS

Q1: End-to-End Process of Vendor Creation in SAP:

 

ü  Receiving Request on Email for Creation of Vendor

ü  Check Documentation & Approval

ü  Check the Duplicity of the Vendor

ü  Creation of Vendor in SAP using T-Code XK01

Process of Creating Vendor in SAP

1.     Receiving Request on Email for Creation of Vendor

1.     First we receive the request from the concerned department (procurement department) via email for creating the vendor along with the VMD Form (Vendor Master Data Form).

2.     Check Documentation & Approval

1.     Vendor Master Data form should be correctly filled.

2.     Proper documentation like PAN No, VAT No, GST No, Bank Details, etc. should be attached.

3.     Approval from the Finance Manager or Director should be obtained.

4.     If the Finance Manager or Director is on leave, additional approval is required.

3.     Check the Duplicity of the Vendor T-Code XK03

1.     If all the documents are correct, check whether the vendor is already created in the system using T-Code XK03.

2.     If the vendor exists, no need to create it.

4.     Creation of Vendor in SAP using T-Code XK01

a.     Vendor is created at three levels:

1.     Global Data: Vendor Name, Address, Contact Details, PAN No, VAT No, GST No, Bank Details, etc.

2.     Company Code Data: Reconciliation Account, Cash Management Group, Payment Terms, etc.

3.     Purchase Organization Data: Order Currency, Terms of Payment, etc.

==============================================================================

Q2: Key Fields Required While Creating a Vendor Master Record:

• Vendor is created at three levels:

1. Global Data: Vendor Name, Address, Contact Details, PAN No, VAT No, GST No, Bank Details, etc.
2. Company Code Data: Reconciliation Account, Cash Management Group, Payment Terms, etc.
3. Purchase Organization Data: Order Currency, Terms of Payment, etc.

Q3: Difference Between a One-Time Vendor and a Regular Vendor:

• One-Time Vendor (CPD – "Common Payee Data"): Used for infrequent transactions; master data is not permanently stored.
• Regular Vendor: Has a dedicated master record and is used for repeated transactions.

Q4: Handling Duplicate Vendor Records in SAP:

• Use Transaction Code S_ALR_87012089 to check for duplicate vendors.
• Regular audits and cleansing activities.
• Activate duplicate check settings in SAP.

Q5: Different Account Groups in Vendor Master & Their Importance:

• Account groups control number ranges and field statuses. Examples:
• LIFA (Financial Vendors) – for financial transactions.
• LIEFER (Regular Vendors) – for material/service procurement.
• CPD (One-time Vendor) – for one-time purchases.
• Helps in classification and reporting.

---

VENDOR CREATION, EXTENSION & DELETION

Q6: Extending an Existing Vendor to Another Company Code or Purchasing Org:

Use XK99 (Mass Maintenance) or XK02 (Change Vendor).

Add the vendor to a new company code or purchasing org while keeping existing details intact.

Q7: Process for Blocking or Deleting a Vendor:

Blocking: Use XK05 to block a vendor at company code or purchasing level.

Deletion Flag: Use XK06 to mark for deletion (does not remove from the system).

Q8: Managing Changes to Vendor Master Data & Controls in Place:

Changes should be restricted to authorized personnel.

Maintain change logs using T-code XK04.

Use approval workflows for major changes (like bank details).

Q9: Impact of Vendor Deletion on Historical Transactions & Reports:

Deleting a vendor affects historical records, making reconciliation difficult.

Reports may show missing vendors in past transactions.

Instead of deletion, vendors are usually marked for deletion (XK06).

Q10: Ensuring Vendor Data Accuracy & Compliance:

Implement approval processes for vendor creation/changes.

Conduct periodic data audits.

Enable duplicate checks and validation rules.

---

SAP T-Codes & System Knowledge

Q11: Key SAP T-Codes for Vendor Master Data:

Creation: XK01, MK01, FK01

Change: XK02, MK02, FK02

Display: XK03, MK03, FK03

Block/Delete: XK05 (Block), XK06 (Delete Flag)

Mass Changes: XK99

Q12: Difference Between XK01, MK01, and FK01:

XK01: Creates vendor centrally (for both purchasing and finance).

MK01: Creates vendor for purchasing organization only.

FK01: Creates vendor for finance (company code) only.

Q13: Displaying Vendor Master Data:

Use XK03 (Centrally), MK03 (Purchasing), FK03 (Finance).

Q14: Reports to Check Vendor Details & Transactions:

Vendor List: S_ALR_87012086

Vendor Open Items: FBL1N

Vendor Payment History: S_ALR_87012093

Q15: Handling Errors/Missing Mandatory Fields in Vendor Creation:

Ensure all required fields are filled based on field status configuration.

Use F4 (Search Help) for valid entries.

Check error messages in SAP Message Log (T-code: SLG1).

---

Share it Please

Tweet

Tom Stokes

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation.