Translating SD and MM document control, pricing, and trade flows

How SAP's three-level sales document control (document types, item categories, schedule line categories) and the condition technique for pricing map to D365 trade agreements, order management, and charges; and how SAP purchasing document types, release strategies, and scheduling agreements translate to D365 purchase orders, purchase agreements, and procurement workflows.

What you will be able to do

• Describe the three-level SAP sales document control model and identify which level controls account determination, delivery relevance, and billing relevance
• Explain how the condition technique works and why it has no direct D365 equivalent
• Map SAP pricing condition types and procedures to D365 trade agreement journals, unified pricing management and the charges framework
• Translate SAP purchasing info records, scheduling agreements, and release strategies to D365 purchase agreements and procurement workflows
• State the correct approach for intercompany and direct-delivery scenarios in D365

Introduction

SAP Sales and Distribution is a three-layer control system. The sales document type sets header defaults and number ranges. The item category controls what happens at the line level: whether the line is delivered, billed, priced, and MRP-relevant.

The three-level SD document control

Sales document types (VBAK-VBTYP) control the header behaviour of a sales transaction. Standard document types include OR (standard order), QT (quotation), RE (returns), CR (credit memo request), and DR (debit memo request).

The condition technique: SAP pricing's centrepiece

The SAP condition technique is a rules engine. Understanding it requires understanding its four components:

The purchasing document landscape and release strategies

SAP purchasing documents follow the same view-based extension model as sales documents. Purchase orders (EKKO header + EKPO items) carry the purchasing organisation, vendor, document type, and currency at header level; the material, plant, quantity, price, delivery date, and account assignment at item level.

D365 trade agreements and pricing

D365 trade agreements are maintained via trade agreement journals in the Trade agreements form (Sales and marketing > Prices and discounts or Procurement and sourcing > Prices and discounts). Each journal type covers a specific combination:

Intercompany, direct delivery, and cross-border trade

SAP intercompany processing uses paired document types: a standard sales order (OR) in the selling company triggers an intercompany purchase order (NB) in the delivering company, which processes the shipment.

Knowledge check

Summary

SAP's SD document architecture is deeply layered; D365's is flatter but sufficient for most trade scenarios. The condition technique is the major gap — a full rules engine that requires redesign, not migration.