Master Data in SAP SD: Customer, Material, and Pricing Records Made Simple

SAP SD Masterdata: Simple customer, material and pricing records

Master data is at the core of every sales transaction in SAP, from quotation to invoice. The sales order is processed with limited manual effort through delivery, billing and accounting, provided that the master data is correct. If it is wrong, there are errors at every step. This article describes the main SAP SD master data objects in SAP Sales and Distribution (SD), their relationships and how to keep them clean.

What is Master Data in SAP SD and Why is it Important?

Master data is the fairly static core information that SAP uses again and again in business processes. Master data is created once and used many times. It is not like transactional data such as a sales order or an invoice created for one event and created once. When a customer is created, their address, payment terms, and shipping conditions are automatically copied to every order for that customer.

In SAP SD most of the sales processes are driven by three master data objects:

• Customer master: who you sell to, where you deliver, who pays and on what terms
• Material master: what you sell, its units, weights, plants, sales-specific settings.
• Pricing condition records: what you charge including prices, discounts, surcharges, goods and taxes.

Master data matters for 4 reasons:

• Automation. If a user enters a customer number and a material number in a sales order, SAP will fill in dozens of fields like payment terms, incoterms, delivery plant, tax data, price, etc.
• Consistency. One central record means that every order, delivery and invoice treats the same customer or product the same.
• Integration. Master data in SD is available in Material Management (MM), Finance (FI), Production Planning (PP) and Controlling (CO). A mistake in one spot often shows up somewhere else.
• Accuracy of Reporting. Sales reports, revenue analysis, and credit exposure are impacted by duplicate or incomplete records.

Know the Data Types in SAP Sales and Distribution

SAP SD master data is divided into several groups. The core objects are customer master, material master and pricing condition records. Supporting objects are customer material information record, partner functions, and account groups. The following sections cover each, and together they form the foundation of the SAP order-to-cash process.

Customer Master Data (XD01, VD01, and Business Partner in S/4HANA)

The customer master data in SAP SD holds everything SAP needs to do business with a customer. It is organized into three data levels, and understanding them is the key to understanding customer maintenance.

1. General data (client level). This applies across the whole company and includes:

• Name, address, communication details, and language
• Country, region, and tax-related identifiers (for example, GST registration data in India)
• Bank details and, where relevant, contact persons

2. Company code data. This is used mainly by Finance and includes:

• The reconciliation account (the G/L account that collects the customer's receivables)
• Payment terms and payment methods
• Dunning information and interest settings

3. Sales area data. A sales area is a combination of sales organization, distribution channel, and division. This level contains the data SD uses most:

• Customer pricing procedure, price group, and price list type
• Currency and exchange rate type
• Shipping conditions, delivery priority, and delivering plant
• Incoterms and terms of payment for the sales area
• Partial delivery rules and order combination settings
• Partner functions
• Tax classification and account assignment group

Key transaction codes (ECC and classic SAP):

Transaction	Purpose
XD01 / XD02 / XD03	Create / change / display a customer centrally (all three levels)
VD01 / VD02 / VD03	Create / change / display customer with sales area data
FD01 / FD02 / FD03	Create / change / display customer with company code data
XD05 / XD06 / XD07	Block / mark for deletion / change account group

S/4HANA Business Partner. In SAP S/4HANA, the Business Partner (transaction BP) gives you a single entry point to create and maintain your customers and vendors. The older transactions XD01 and VD01 are not the recommended way to work anymore. Instead, a business partner is created in the customer role (e.g. FLCU00 for the FI customer view and FLCU01 for the sales customer view). We will have a synchronisation layer called Customer-Vendor Integration (CVI) to create the matching customer record behind the scenes. Downstream SD processes will continue to work with customer numbers as before.

A practical advantage of the Business Partner approach is that one entity can have many roles. Instead of two unrelated records, you can have one business partner who is both your customer and your supplier.

What can go wrong: The types of customer master problems you see most often are: Incomplete sales area (which means orders cannot be created), missing or incorrect account assignment group (which means revenue posts to the wrong account), incorrect payment terms or tax settings.

Material Master Data (MM01 and Sales Org Views)

The material master in SAP describes a product and is shared across many departments. Each department looks at the same material from a different perspective. The most important views for SD are the ones related to sales.

Important SD-relevant views:

• Basic data 1 and 2: Description of material, base unit of measure, material group, gross and net weight, division.
• Sales Organization Data 1: supplying plant, sales unit, tax classification, and material group assignments used for pricing and statistics.
• Sales Organ. Data 2: Item category group (determines how a line item behaves in a sales document), Material pricing group and Product hierarchy.
• General/Plant Data: Availability check group, Transportation group, Loading group, Batch management indicator.
• Plant Data / Stock: The MRP and stock data that determine whether the product is available to promise.

Key transaction codes:

Transaction	Purpose
MM01	Create material
MM02	Change material
MM03	Display material
MMBE	Stock overview

Material type is important. Depending on the type e.g. FERT (finished product), HAWA (trading goods) or DIEN (service) materials have different views and behave differently in SD. A finished good is manufactured and sold. A trading good is bought and sold.

Material Distribution to a selling organization. A frequent task is to roll out an existing material to a new sales organization or distribution channel. This is done via MM01 or MM02 by choosing the Sales views, entering the target sales organization and distribution channel, with the ability to copy data from a reference sales area. If you do not perform this step, users will receive errors like 'Material is not defined for sales organization and distribution channel'.

What could go wrong. Common material master problems are a missing delivering plant, a missing or wrong tax classification, a wrong item category group (so the order line behaves incorrectly) and no sales unit or unit conversion defined.

Price Condition Records (VK11 and Condition Types)

Pricing in SAP SD is what SAP uses to determine what a customer pays. It is based on a structured set of building blocks. Condition records are the actual price data that you maintain.

The Building Blocks of Pricing:

• Condition type: A code that represents one pricing element, such as a base price, a discount, a surcharge, goods, or tax.
• Condition table: Defines the combination of fields (the key) in which a record is stored, e.g. Customer/Material or Material alone.
• Access sequence: The ordered search strategy that SAP uses to find a valid record. It first looks at the most specific condition table and then progresses to more general ones.
• Pricing procedure: full calculation schema with all condition types in sequence, with subtotals, requirements and account keys. Sales area, customer pricing procedure and document pricing procedure are determined.
• Condition record: the value stored, including amount, currency, unit and validity dates.

Commonly used condition types:

Condition type	Typical meaning
PR00	Base price
K004	Material discount
K005	Customer/material discount
K007	Customer discount
KA00	Sales promotion discount
HA00	Header percentage discount
MWST	Output tax (may differ by country; India uses JOIG, JOCG, JOSG for GST)

Key transaction codes:

Transaction	Purpose
VK11	Create condition record
VK12	Change condition record
VK13	Display condition record
V/03, V/05, V/07	Define condition tables / access sequences / condition types (configuration)
VOK0	Maintain pricing procedure

Pricing in a sales order: When you save a line item, SAP executes the pricing procedure, starting from the top and going to the bottom. For each condition type, it uses the access sequence to find a valid record. If it finds one, it applies the value and displays it in the order. If it doesn't, the condition is not there and often appears as a zero price or an incompleteness error.

Scales and validity: Each condition record has a valid-from date and a valid-to date. SAP uses the order's pricing date to get the matching record so it will not pick up an expired price. Records can also have scales e.g. a lower price if a customer orders more than 100 units.

What can go wrong: Prices not found, generally because the record does not exist, has expired or is stored under a key that the access sequence does not search, or because the customer pricing procedure or material pricing group is not set up correctly.

Customer Material Info Record (VD51)

The customer-material information record has the data which is specific to a customer and a material. Useful for when a customer might have their own part numbers or special delivery rules.

What it may contain:

• The customer's own material number and description, so that the customer's number can be entered in a sales order and SAP can find your material
• Customer delivery plant
• Delivery tolerances (under/over delivery limits)
• Minimum order quantity and partial delivery rules
• Text for sales orders (e.g. special packing instructions)

Key transaction codes:

Transaction	Purpose
VD51	Create customer-material info record
VD52	Change customer-material info record
VD53	Display customer-material info record

Why it matters: If not, a customer ordering by their part number means your team's got to translate every order by hand. This enables SAP to automatically locate the right material, which minimises errors and saves time. It also allows you to override standard material or customer settings for one particular combination without having to change the master record.

Partner Functions and Accounts

Partner functions describe the function of business partners in a sales transaction. A single customer often entails several different parties:

Partner function	Meaning
SP (Sold-to party)	The customer who places the order
SH (Ship-to party)	Where the goods are delivered
BP (Bill-to party)	Who receives the invoice
PY (Payer)	Who actually pays the invoice

These four are the standard set and are covered in most sales documents. Partner functions are stored in the customer master sales area data, so that one sold-to party can be linked to several ship-to parties and different players. When you create an order, SAP proposes these partners from the master record automatically.

Partner functions are assigned to partner determination procedures. Partner determination procedures determine what functions are mandatory or optional for each document type.

Account groups classify customers and control the creation of their master records. Examples are sold-to-party, ship-to-party, payer, and one-time customer; An account group specifies:

• The number range (internal or external numbering) to use for new customers;
• The field status for each field (required, optional, display only or hidden)
• Allowed partner functions for customers in that group
• CPD (One-off account) for the occasional buyer who doesn't want a permanent record

Good account group planning at the beginning of an implementation is important, as it is difficult to change a customer's account group at a later date and this can lead to data inconsistencies.

Common Master Data Errors and How to Fix Them

Here are the most common SAP SD master data errors SD users encounter, their typical causes and how to resolve them.

1. Sales area xxxx/xx/xx is not defined for the customer.
Cause: Customer master is not extended to the sales area.
Solution: Add the sales area data for the customer with VD02 or XD02 or create it with VD01.

2. Material sales organization and distribution channel not maintained.
Cause: The material was not extended to the sales views for this sales organization and distribution channel.
Fix: Change the material to the correct sales organization and distribution channel by using MM02.

3. Price is zero / "No condition record found."
Cause: The condition record is not valid, the validity date has expired, the record is created with a key that is not searched by the access sequence or the pricing procedure does not contain the condition type.
Correction: Look at the pricing analysis in the order (the analysis button in the item conditions screen) and then create or correct the record with VK11 or VK12. Verify the customer pricing process and record the pricing process.

4. Mistakes in tax or tax determination.
Cause: No tax classification for customer or material, or no tax condition records.
Fix: Keep tax classification in customer master (Sales area data) and material master (Sales organization data 1) and check tax condition records.

5. The delivery of the plant couldn't be determined.
Cause: The delivering plant is not available in the material master, customer master or customer-material record.
Fix: Keep the delivering plant in at least one of these records - SAP will look at the customer-material info record, then the customer master, then the material master.

6. Order blocked due to credit or customer block.
Cause: Customer has a block in the central or sales area, or credit limit checks failed.
Solution: Check block in XD02 and credit data in the credit management transaction and correct or release as appropriate.

7. Wrong partner or no partner in the order.
Cause: Partner functions not maintained or partner determination procedure not defined for document type.
Fix: Keep partner functions in customer sales area data and check partner determination procedure.

8. Wrong G/L account identified (revenue posted to the wrong G/L account).
Cause: Wrong account assignment group on customer or material.
Solution: Check the revenue account determination records (VKOA) and correct the account assignment groups in the customer and material master data.

Maintaining Clean Master Data

Fixing one error at a time is costly. A better approach to SAP master data management is to avoid them through disciplined processes.

• Ownership, define. Clearly define who owns each master data object. Rather than anyone having access, a small group of trained people should make and change records.
• Follow a normal creation process. Have an approval workflow and standard request form so that all mandatory data is included from start for every new customer or material.
• Do not duplicate. Verify existing records before creating new ones. Consistent naming conventions, duplicate checks (SAP has duplicate-check functions for business partners).
• Set required fields. Prevent skipping critical fields like tax classification, payment terms and shipping conditions by using account groups and field status settings.
• See records. When extending to new sales areas or creating similar customers or materials you can copy from a reference record to maintain settings.
• Check prices regularly. Check for expired condition records, overlapping validity periods and unused records. See upcoming price changes before they happen.
• Perform data quality checks regularly. Report on customers without sales areas, materials without delivering plants, blocked records still in use and inactive records. Don't delete data with history. Archive or block what's not needed anymore.
• Mass changes of control. If you plan to use tools such as LSMW, Data Migration Cockpit in S/4HANA, or mass-change transactions, be careful. Test always in a non-production system first and document each change.
• Write down the rules. Have a short master data guide defining mandatory fields, naming rules and ownership of decisions by team. New users learn more quickly and make fewer mistakes.
• User training. Many mistakes are due to a user not understanding how a field impacts downstream processes. A quick tour of the customer-to-cash process can help people appreciate the importance of accuracy.

Conclusion: Key Takeaways

Master data is the backbone of SAP SD. When you create a sales order, the customer, material and pricing records work together. So, the quality of these records directly impacts how smoothly sales, delivery, billing and finance processes run.

Important things to note:

• The customer master has three levels (general, company code and sales area). Most SD behaviour is driven by the sales area data. Customers are created in S/4HANA using the Business Partner (BP) transaction.
• The material master should be extended to the right sales organization and distribution channel with correct delivering plant, tax classification, and item category group.
• The condition type, condition table, access sequence and pricing procedure all work together to form the pricing condition records (VK11). The most common cause of pricing problems is missing or expired records.
• Customer material information record (VD51) deals with customer specific part numbers and delivery rules.
• Partner functions determine the role each partner plays in a transaction, and account groups determine the creation of customer records and what fields are required.
• Most SD errors come from incomplete or inconsistent master data. The best way to fix most SD errors is prevention: clear ownership, controlled creation processes, mandatory fields and regular data quality checks.

Investing time in clean master data pays dividends in terms of fewer errors, faster order processing and more reliable reporting across the entire business.