Procurement Process Fundamentals

Understanding the Core Elements of the Procurement Process

The procurement process is the backbone of any organization that purchases goods or services. Mastering its fundamentals—such as the vendor master, plant structure, storage locations, and key purchasing data—enables businesses to reduce costs, improve compliance, and accelerate the flow of materials. This course breaks down each concept, explains its role within SAP (or similar ERP systems), and provides practical examples to reinforce learning.

1. The Vendor Master: Controlling Entry of Accounting Data

In SAP, the vendor master stores all essential information about a supplier. It is divided into three views:

• General data – address, communication details, and tax information.
• Company code data – accounting details such as payment terms, reconciliation account, and bank information.
• Purchasing organization data – purchasing-specific data like order currency and incoterms.

The company code view is the element that controls the entry of accounting data. When a vendor is created, the system requires a company code assignment to ensure that financial postings (e.g., invoices) are posted to the correct ledger.

Key takeaway: Always assign the appropriate company code when maintaining the vendor master to guarantee accurate accounting entries.

2. Plant and Storage Location: Defining Where Materials Reside

What Is a Plant?

A plant is a central organizational unit in logistics. It represents a physical location where production, procurement, and inventory management occur. Common misconceptions include the belief that a plant can belong to multiple company codes. In reality, a plant is assigned to a single company code, but a company code can have multiple plants.

Key characteristics of a plant:

• Acts as a key element in purchasing and inventory management.
• Determines the valuation area for material stocks.
• Links to a specific set of storage locations.

Understanding Storage Locations

A storage location is a sub‑unit of a plant where materials are physically stored. It is best described as the place within a plant where materials are kept until they are needed. This definition distinguishes it from other logistics areas such as staging zones or finished‑goods warehouses.

Typical uses of storage locations include:

• Segregating raw materials from semi‑finished goods.
• Managing inventory for different production lines.
• Facilitating location‑specific stock counts.

Practical tip: When setting up a new plant, define storage locations that reflect real‑world material flow to simplify picking, shipping, and inventory reconciliation.

3. Purchase Requisition: Required Organizational Data

A purchase requisition (PR) is an internal request to procure goods or services. To create a PR, the system must know three pieces of organizational data:

• Company code – the legal entity that will be financially responsible.
• Purchasing organization – the unit that negotiates with vendors and issues purchase orders.
• Purchasing group – the buyer or team responsible for the specific requisition.

These three fields ensure that the requisition is routed correctly, priced according to the right conditions, and posted to the appropriate ledger.

Common mistake: Selecting a storage location instead of a purchasing group. Remember, the storage location belongs to the plant, not the purchasing hierarchy.

4. Data Types Relevant to Purchasing

Effective procurement relies on accurate master data. Four primary data types are directly linked to the purchasing process:

• Vendor master – contains supplier details and accounting information.
• Material master – stores material specifications, valuation, and purchasing data.
• Purchasing info records – link a vendor to a material, defining price, terms, and delivery schedules.
• Sales master – not relevant for purchasing; it pertains to the sales side of the business.

By focusing on the first three, organizations can streamline source‑to‑pay cycles and avoid data inconsistencies.

5. Material Master – Purchasing View

The purchasing view of the material master holds key data that influences how the system processes purchase orders. The correct set of key data includes:

• Purchasing group – the buyer responsible for the material.
• Goods receipt processing time – the expected time between receipt and posting.
• Delivery tolerances – permissible deviations in quantity and date.

These fields enable the system to calculate lead times, trigger alerts for late deliveries, and assign the appropriate buyer automatically.

Why the purchasing organization is not a key field here: The purchasing organization is defined at the transaction level (e.g., in the purchase order) and can vary per order, whereas the purchasing group is a material‑specific responsibility.

6. Item Categories: Matching Business Scenarios

Item categories determine the processing logic for each line item in a purchase order. Selecting the correct category is crucial for accurate inventory and financial postings.

Third‑Party Item Category

Use the Third‑party item category when a vendor ships goods directly to the customer, bypassing the buyer’s inventory. This scenario is common in drop‑shipping models where the supplier fulfills the order on behalf of the buyer.

Other Common Item Categories

• Consignment – goods remain vendor‑owned until consumption.
• Stock Transfer – movement of stock between plants or storage locations.
• Standard – regular procurement that updates inventory on receipt.

Tip: Always verify the business process before assigning an item category; an incorrect choice can lead to wrong inventory valuation or tax treatment.

7. Account Assignment Categories: Linking Purchases to Cost Objects

When a purchase order is posted, the system must know where to allocate the cost. The account assignment category (KNTTP) defines this link.

• Asset – used when acquiring a fixed asset (e.g., machinery, computers). The cost is posted to the asset master and later depreciated.
• Cost center – allocates costs to a department or internal unit.
• Order – ties the expense to a production or maintenance order.
• Project – assigns costs to a specific project or internal order.

Choosing Asset ensures that the purchase is capitalized rather than expensed, complying with accounting standards and enabling proper depreciation schedules.

8. Integrating the Concepts: A Sample End‑to‑End Scenario

To illustrate how these elements interact, consider the following example:

1. Vendor master creation: A new supplier is added with company code 1000 (controlling accounting data) and purchasing organization 2000.
2. Material master setup: Material MAT‑001 is defined with a purchasing view that includes purchasing group PG‑01, goods receipt processing time of 2 days, and delivery tolerances of ±5%.
3. Plant and storage location: Plant Plant‑A (assigned to company code 1000) contains storage location SL‑01 where raw materials are kept.
4. Purchase requisition: The production planner creates a PR for MAT‑001, entering company code 1000, purchasing organization 2000, and purchasing group PG‑01.
5. Purchase order: The buyer converts the PR to a PO, selects the Third‑party item category because the vendor will ship directly to the customer, and chooses the Asset account assignment category to capitalize the purchase of a new production line.
6. Goods receipt: Since the item is third‑party, no physical receipt is posted; instead, the system records a service entry and triggers invoice verification.

This flow demonstrates how each data element—vendor master, plant, storage location, purchasing view, item category, and account assignment—must be correctly configured for a seamless procurement process.

9. Best Practices for Maintaining Procurement Master Data

• Regular audits: Conduct quarterly reviews of vendor master records to remove duplicates and update banking details.
• Consistent naming conventions: Use clear, descriptive codes for plants, storage locations, and purchasing groups to avoid confusion.
• Leverage SAP’s data governance tools: Implement change‑request workflows for material master updates to ensure that purchasing views remain accurate.
• Train end‑users: Provide hands‑on workshops for buyers on selecting the correct item and account assignment categories.
• Integrate with finance: Align the company code assignments in the vendor master with the finance team’s chart of accounts to prevent posting errors.

Adopting these practices reduces errors, improves compliance, and accelerates the procure‑to‑pay cycle.

10. Quick Reference Cheat Sheet

• Vendor master accounting control: Company code
• Storage location definition: Place within a plant where materials are kept until needed.
• Plant assignment rule: One plant → one company code; a company code can have many plants.
• Purchase requisition required data: Company code, Purchasing organization, Purchasing group.
• Non‑relevant data type for purchasing: Sales master.
• Purchasing view key data: Purchasing group, Goods receipt processing time, Delivery tolerances.
• Item category for direct‑ship: Third‑party.
• Account assignment for fixed assets: Asset.

Keep this cheat sheet handy when configuring or troubleshooting procurement processes.

Conclusion

Mastering the fundamentals of the procurement process—understanding the vendor master, plant and storage location hierarchy, requisition requirements, and the correct use of item and account assignment categories—creates a solid foundation for efficient, compliant, and cost‑effective purchasing. By applying the concepts and best practices outlined in this course, professionals can optimize their organization’s source‑to‑pay workflow, reduce manual errors, and support strategic decision‑making.