Before any transaction can happen in the procure-to-pay cycle, the system needs a detailed, organized set of records. This is your master data. Think of it as a digital filing cabinet where every item your company buys and every supplier you buy from has its own meticulously labeled folder. Getting this data right from the start is what enables the entire automated process to run smoothly. We'll focus on the three core components: the material master, the business partner (or vendor), and the record that links them together.

Every item a company procures, produces, or sells is represented by a unique record called the Material Master. You can create or change this using transaction code $MM01$. This isn't just a simple item description; it's a collection of data organized into different 'views,' each relevant to a specific business function. For procurement, a few views are essential.

The Purchasing view is where you define how the material is bought. You'll set the base unit of measure (e.g., pieces, kilograms), the purchasing group responsible for procuring it, and flags for things like automatic purchase order creation. This data is maintained at the plant level, meaning a material can be purchased differently for your manufacturing plant in Texas versus your warehouse in California.

The MRP views (Material Requirements Planning) control how the system plans for this material. Here you set the MRP type, which tells the system whether to plan automatically based on consumption or future demand. You also define lot-sizing procedures and safety stock levels to ensure you never run out unexpectedly.

Perhaps the most critical view for financial integration is Accounting 1. This is where the material is linked to the company's financial books.

Choosing the correct Valuation Class is non-negotiable for automatic account determination. When you receive a material, the system checks its Valuation Class to know which inventory account to debit and which clearing account (like the GR/IR account) to credit. An incorrect setting here will cause financial postings to fail.

In modern SAP S/4HANA systems, you no longer create separate customer and vendor masters. Instead, you create a single Business Partner (BP) using transaction code $BP$. This BP can then be extended to different roles. A single company record could be a customer (it buys from you), a supplier (you buy from it), or both.

For the P2P cycle, you'll create a BP and extend it to two key roles:

1. General Role (BP General): This contains basic data like the company's name, address, and communication details. This information is universal, regardless of the business relationship.
2. Supplier Financials Role (FI Vendor): This role holds company-code-specific financial data. You'll define reconciliation accounts (the G/L account that represents this vendor in your sub-ledger), payment terms, and dunning procedures.
3. Supplier Role: This contains the purchasing-specific data. This information is tied to the Purchasing Organization and includes the order currency, Incoterms, and a crucial checkbox: GR-Based Invoice Verification. When checked, this setting forces the system to require a goods receipt before an invoice can be paid, creating a vital three-way match between the purchase order, goods receipt, and invoice.

What happens when you have a special price or a fixed supplier for a specific material? Storing this information directly in the material or vendor master would be inefficient. This is where the Purchasing Info Record (PIR) comes in. Created with transaction code $ME11$, the PIR is a master data record that connects a specific material with a specific vendor.

When you create a purchase order, the system searches for a valid PIR for the material-vendor combination. If found, it automatically pulls in the price, lead time, and other conditions, saving time and preventing manual entry errors. This master record is the final piece of the puzzle, creating a strong, data-driven link between what you buy and who you buy it from.

With the master data foundation correctly configured, you're ready to start the actual procurement process. These records will now drive every subsequent transaction in the cycle.