SAP SD (Sales and Distribution) is a core module in SAP ERP that manages sales, customer orders, billing, and shipping processes. Learning SAP SD equips professionals with in-demand skills for configuring order-to-cash cycles in S/4HANA. SAP SD online training offers hands-on experience, boosting career growth and global job opportunities. Enroll in SAP SD training today!

Explain Partner Functions vs. Business Partner Approach?

• Partner Functions (ECC): Used to define roles like Sold-to, Ship-to, Bill-to, and Payer within the customer master. Managed via Customer Master tables (KNA1, KNVP).
• Business Partner (S/4HANA): Unified model combining customer, vendor, and contact into a single BP entity using transaction BP. Replaces traditional customer/vendor master.
  • Partner roles are assigned to a single BP (e.g., FLCU01 for customer, FLVN01 for vendor).
  • Reduces data redundancy and enables centralized master data maintenance.

Difference between Static and Dynamic Credit Checks?

• Static Check:
  • Based on total open items + current sales orders vs. credit limit.
  • Simple, quick validation.
• Dynamic Check:
  • Adds a time horizon (e.g., 15 days) to consider only imminent deliveries.
  • More accurate for real-time credit control.
  • Defined in credit management config (OVA8), requires FSCM in S/4HANA.

How Advanced ATP Works in S/4HANA

• Advanced ATP (aATP) is the S/4HANA innovation for real-time availability.
  • Replaces classic ATP logic with powerful tools:
    • Product Allocation (PAL)
    • Backorder Processing (BOP)
    • Alternative-based Confirmation (ABC)
    • Supply Assignment
  • Real-time, Fiori-enabled, integrated with live inventory and demand.
  • Uses the embedded PP/DS and advanced rule-based logic for substitutions.

Configuration and Use of Schedule-Line Category

• Determines delivery and MRP relevance in a sales order.
  • Controlled by Item Category + MRP type (VOV6).
  • Key fields:
    • Availability check (relevant or not)
    • Requirements type (integration with MRP)
    • Movement type for delivery
• Used to trigger stock checks and procurement processes.

 How Account Determination is Configured (Pricing, Revenue, Tax)?

• Involves mapping condition types to G/L accounts:
  • Pricing: via condition technique (V/08 → VKOA)
  • Tax: via tax condition types (e.g., MWST), linked to country, tax code, and account keys
• Key elements in VKOA:
  • Chart of accounts
  • Sales org / Customer / Material account assignment groups
  • Account keys (from pricing procedure)
• System uses this to post revenue, discounts, freight, taxes.

Setup and Use of Batch Determination and Integration with MM?

• Used when materials are managed in batches (e.g., pharmaceuticals, food).
• In SD, set up in:
  • Sales order (copy control, requirement type)
  • Delivery (Batch search strategy via VCH1, VCH2)
• Integration with MM:
  • MM handles batch classification (LOBM, expiry, shelf-life)
  • SD uses MM’s batch master for picking and post goods issue

Describe Shipping Point Determination Using Plant/Condition Logic?

• Shipping point is determined based on:
  • Shipping condition (from customer master)
  • Loading group (from material master)
  • Delivering plant
• Configuration via OVL2 table:
  • Combines the three values to propose a shipping point in sales/delivery documents.

Methods of Pricing Procedure, Condition Types, Access Sequences?

• Pricing Procedure defines structure of conditions in sales (V/08):
  • Subtotals, base prices, discounts, taxes
• Condition Types (e.g., PR00, K004) define how price/discount is calculated
• Access Sequence: Searches condition records using key fields (e.g., customer/material)
  • Linked to condition type (V/07), uses tables like 001, 004, etc.
• The procedure is assigned via document pricing procedure + customer pricing procedure.

Rebate Processing Workflow: Agreements, Accumulation, Settlement?

• Rebate Agreement is created (T-code: BO01) with customer and rebate conditions.
• During billing, system accrues the rebate amount automatically.
• At period end:
  • Create rebate settlement request
  • Generate credit memo to customer
• S/4HANA uses Settlement Management (replacing traditional SD rebate), integrated with Condition Contract Management.

 Handling Third-Party and Intercompany SD Scenarios?

Third-Party Order Process:

• Customer orders → vendor delivers → you bill customer.
• Flow:
  • Sales Order (item category TAS)
  • Auto PR → PO to vendor
  • Vendor ships → goods receipt → billing to customer
• No inventory maintained in your plant.

Intercompany Sales:

• Cross-company plant delivers goods; your company bills customer.
• Flow:
  • Sales Order (delivering plant in another company code)
  • Delivery + PGI by delivering company
  • Intercompany Billing (IV) between companies
  • Customer Billing (F2) to end customer
• Requires intercompany config in VOE2, VOE4, and pricing with condition type IV01.