SAP SD Mastery

From Zero to Consultant

Target: 80%+ Score

Complete SAP SD Reference Guide

Prepare for your Certification and Job Interviews. This page contains detailed configuration steps, 100+ Transaction Codes, 50+ Database Tables, and deep-dive explanations of logic like Pricing and Determinations.

"Study hard, practice in the system, and success will surely come."

Enterprise Structure

You must memorize the definition and assignment of these units.

  • Sales Organization Highest level in SD. Responsible for legal liability and sales.
  • Distribution Channel How goods reach customers (e.g., Wholesale, Retail, Online).
  • Division Grouping of materials. Useful for profit center analysis.
  • Sales Area Combination of Sales Org + Dist. Channel + Division.

Master Data

  • Customer Master (BP) General Data (Client level), Company Code Data (FI), Sales Area Data (SD).
  • Material Master Views: Basic Data, Sales Org 1/2, Sales General/Plant.
  • Customer-Material Info Record Maps customer's material number to our material number. High priority in search.

Determination Rules

1. Plant Determination

Priority Order:

  1. Customer-Material Info Record
  2. Customer Master (Shipping Tab)
  3. Material Master (Sales Org 1)
2. Shipping Point Determination

Shipping Condition (Cust Master) + Loading Group (Mat Master) + Delivering Plant

3. Route Determination

Departure Zone (Plant) + Destination Zone (Ship-to) + Shipping Condition + Transportation Group

4. Storage Location

Plant + Shipping Point + Storage Condition

Document Controls

Level T-Code Key Controls
Sales Doc Type VOV8 Number range, Item increment, Delivery block, Billing block.
Item Category VOV7 Billing relevance, Pricing relevance, Schedule line allowed.
Schedule Line VOV6 Movement Type (601), Transfer of Requirements, Availability Check.

Pricing Procedure (16 Steps)

You cannot pass the interview without explaining the 16 fields of the pricing procedure.

1
Step: Sequence number.
2
Counter: Sub-step for multiple conditions.
3
Condition Type: (PR00, K007) The actual price element.
4
Description: Name of condition.
5
From: Base value calculation start step.
6
To: Base value calculation end step.
7
Manual: Can be entered manually.
8
Required: Mandatory condition.
9
Statistical: Not posted to accounting (e.g., VPRS cost).
10
Print: Print on output document.
11
Subtotal: Stores value in KOMP structure (e.g., Net Value).
12
Requirement: (Routine) Check if condition should apply.
13
Alt. Calc Type: Formula to calculate value.
14
Alt. CBV: Formula for Condition Base Value.
15
Account Key: Links to G/L account (e.g., ERL for Revenue).
16
Accruals: Provisions (e.g., Rebates).

Partner Determination

Determines who is involved in the transaction (Sold-to, Ship-to, etc.).

  • Partner Function: Role of the partner (SP, SH, BP, PY).
  • Partner Procedure: Assigned to Account Group (Master Data) or Doc Type (Sales).
  • Account Group: Controls field status and number ranges for customer.

Text Determination

Flows text from Master Data -> SO -> Delivery -> Invoice.

Access Sequence -> Text Object (VBBK/VBBP) -> Text ID

Output Determination

Sends documents via Print, Email, EDI, or Fax. Uses Condition Technique.

  • T-Code: NACE
  • Application: V1 (Sales), V2 (Shipping), V3 (Billing)
  • Program: RSNAST00 (Standard Print Program)

Incompletion Log

Defined in status groups. If mandatory fields are missing:

Block Saving
Block Delivery
Block Billing
Warning Only

Material Determination

Automatic substitution of materials (e.g., Old -> New, or Promo Packaging).

Technique: Condition Technique (A001).
T-Code: VB11 (Create), OVRQ (Config).

Listing & Exclusion

  • Listing: Customer can ONLY buy these materials.
  • Exclusion: Customer can buy anything EXCEPT these.

Cross Selling

Suggests related accessories. Triggers a popup in VA01.
Profile: Assign to Sales Area/Doc Type/Customer.

Bill of Materials (BOM)

Explodes main material into sub-items in Sales Order.

Header Pricing (LUMF) Main item priced, sub-items free.
Item Pricing (ERLA) Main item free, sub-items priced.

Customer Hierarchy

Maintains complex customer structures (e.g., HQ -> Regional -> Local). Used for pricing conditions applying to entire groups.