The title "SAP SD consultant" appears in countless job ads, yet the scope of the role varies from company to company. In this article I summarise, from a field perspective, what an SAP SD consultant actually does, where the role overlaps with SAP analyst and ERP analyst roles, and what has changed with SAP S/4HANA.
The SAP SD module: the backbone of order-to-cash
SD (Sales and Distribution) manages the order-to-cash process, from customer demand to payment. The typical flow is: quotation, sales order, availability check, delivery, picking and goods issue, billing and transfer to accounting. Every step creates a document and the documents are linked; that link is the system's answer to "which order did this invoice come from?"
Responsibilities of an SAP SD consultant
- Requirements analysis: mapping processes with sales, logistics and finance teams and identifying where the standard needs to be extended
- Organisational design: sales organisation, distribution channel, division and shipping point
- Document types and copy control: which document is created from which, with what data
- Pricing: the pricing procedure, condition types and access sequences; discount, freight and tax logic
- Credit and output management: risk checks, blocks, invoice and delivery-note output
- Testing and training: writing test scenarios, running user acceptance tests, training key users
- Post-go-live support: fixing issues at the root cause and prioritising improvement requests
How it differs from an SAP analyst and an ERP analyst
An SAP analyst focuses on turning business needs into a technically feasible design: functional specification, data flow, test scenarios and a common language with the ABAP developer. An ERP analyst looks from a wider angle, analysing process efficiency, reports and bottlenecks across modules. In practice, these three roles are often combined in one person on a project. A good SAP SD consultant is also a good analyst.
Integration points: SD never works alone
- MM: stock, availability check and goods issue
- FI: accounting postings for invoices, customer receivables, tax
- CO-PA: transfer of revenue and cost elements to profitability analysis
- LE / WM / EWM: warehouse and shipping processes
A small configuration mistake in SD often surfaces in another module, such as an invoice posting to the wrong account or an empty value field in CO-PA. That is why an SD consultant needs to know the integration points well.
What changed with SAP S/4HANA?
- Business Partner (BP): customer and vendor master data were merged into a single business partner model.
- Credit management: classic SD credit management was replaced by FSCM-based credit management.
- Unified data model: accounting and profitability data were combined in the ACDOCA table; account-based profitability analysis came to the fore.
- Fiori: many transactions and reports moved to role-based Fiori apps.
- Simplified tables: some old aggregate and status tables were removed, so custom reports need to be adapted.
What to look for in a good SAP SD consultant
- Deep knowledge of standard SAP, treating custom development as a last resort
- The ability to explain pricing and document flow in business terms (margin, cycle time, errors), not just screens
- The ability to test FI and CO-PA integration end to end
- Enough technical literacy to speak the same language as the ABAP developer
- Documenting decisions and changes so whoever comes next can understand the system
SAP SD consulting is less about configuration screens and more about understanding how the sales process makes money for the company. Technical knowledge is essential, but what makes the difference is connecting business outcomes to system design.
To go deeper, read about the pricing procedure, copy control and SD–MM–FI integration, or see the scope on the SAP SD consulting page.
