🤖 What Is SAP Joule, and How Does It Help With SD Configuration?
Today we are discuss What is Joule and How Help With SD Configuration?. built-in AI assistant in SAP S/4HANA Cloud. For SAP SD configuration - which covers enterprise structure, sales document types, pricing procedures, output determination, and partner functions - Joule turns a multi-day SPRO task into a guided, conversational workflow. Instead of remembering hundreds of menu paths and field dependencies, you simply describe what you want in SIMPLE language and Joule navigates to the right screen, suggests values, checks assignments, and saves the configuration correctly. This is especially powerful for SD because the module has one of the most complex configuration chains in all of SAP - every sales area must be linked to the right combination of Sales Organisation, Distribution Channel, and Division before a single sales order can be created.This tutorial Breaks Down the process step by step using simple language and real-world examples to help you master the skill.
The old way. Navigate 150+ SPRO nodes for SD, know every path, every dependency, every field - with no guidance and no context. One missing assignment blocks all sales orders for an entire sales area.
The smart way. Describe your business need. Joule finds the SPRO path, suggests the right values for your context, sequences all assignments correctly, and prevents missing-link errors before you hit save.
Plain Language Input
No need to know SPRO paths. Say "Create a new sales organisation for Delhi" and Joule handles navigation, field filling, and assignment sequencing.
Sales Area Aware
Joule knows that a valid Sales Area = Sales Org + Distribution Channel + Division. It builds all three and their assignments in the correct order automatically.
Validates Before Save
Before saving any SD config, Joule checks that all prerequisite assignments exist - preventing the most common "no sales area found" errors in production.
🧠 How Does Joule Work for SAP SD Configuration? (Step-by-Step)
Before the real scenarios, here is exactly how Joule handles SD configuration tasks - what happens at each step when you ask it something.
business need
correct SPRO path
& suggests values
SD assignments
& validated ✓
Click the Joule icon (blue circle, top-right) on any S/4HANA screen. The Joule panel opens alongside your current screen - you can use it while in SPRO, VA01, VK11, or any SD transaction. Joule sees your current screen context and adjusts its responses accordingly. You do not leave your working screen.
🤖 Joule Panel → Top right in S/4HANA Cloud → Available on any screen → Context-awareYou do not need to know T-codes or SPRO menu paths. Describe the business need directly: "We are opening a new sales office in Chennai and need a sales area set up for retail customers." Joule understands both technical terms ("create a distribution channel") and business descriptions ("we sell direct to hospitals and through distributors - need separate channels"). It keeps full context across the conversation so follow-up questions are understood.
🤖 Example: "Create a sales area for our Chennai office - Sales Org IN01, channel retail, division home appliances"For a sales area setup, Joule knows the correct sequence: first create Sales Organisation (if new), then Distribution Channel, then Division, then assign Sales Org to Company Code, then assign Distribution Channel and Division to Sales Org. It navigates directly to each node - you never touch the SPRO menu tree. It explains what each step does and why it is needed before you confirm.
▶ SPRO: Enterprise Structure → Definition → SD → Maintain Sales Org (OVX5) → Distribution Channel (OVXI) → Division (OVXB)As you go through each screen, you can ask Joule about any field in plain language: "What does Currency in the Sales Organisation control?" - Joule explains that this is the default transaction currency for all sales documents created under this Sales Org, and recommends INR for an India-based organisation. For Indian implementations Joule also flags common requirements like GST relevance, tax classifications, and company code-plant assignments that are frequently missed.
🤖 Ask Joule: "What currency should I use for a Sales Org that sells in India to domestic customers?"The most powerful thing Joule does for SD is manage the complete assignment chain - Sales Org → Company Code, Sales Org → Distribution Channel, Sales Org → Division, Sales Org + DC + Div = Sales Area, Sales Area → Plant, Sales Area → Shipping Point. Missing any single link means sales orders cannot be created. Joule checks every link, warns about missing ones, and completes them in the correct order. This prevents the #1 cause of go-live delays in SD implementations.
▶ Key assignments: OVX3 (Org → CC) · OVXK (Org → DC) · OVXA (Org → Div) · OVX6 (DC → Div = Sales Area)Important: Everything Joule configures is saved to the same SAP Customising tables as manual SPRO work - TVKO (Sales Org), TVKOB (Sales Org assignments), TVTW (Distribution Channel), TSPA (Division). Joule is a smarter interface to the exact same system. Any config done via Joule is transported via standard transport requests in SE10 exactly like manually created config. There is no difference in the output - only in how quickly and safely you get there.
🏢 Real Scenario: Setting Up SAP SD Enterprise Structure Using Joule
The SD enterprise structure - Sales Organisation, Distribution Channel, Division, and their assignments - is the very foundation of all sales processing. Without it, no sales order can be created. It is also the most error-prone part of SD configuration because a single missing assignment breaks the entire chain. Joule makes this structured and safe.
Anand Consumer Products Ltd - New Mumbai Sales Office Setup via Joule
Anand Consumer Products Ltd is expanding into Mumbai. They need a complete SD enterprise structure for their new Mumbai sales office - Sales Org MU01, two distribution channels (Retail and Wholesale), two divisions (Electronics and Home Appliances), and a full sales area for each combination. The SAP admin needs to build this without navigating SPRO manually.
The admin opens Joule and describes the requirement. Joule navigates to SPRO → Enterprise Structure → Definition → SD → Maintain Sales Organisation (T-code OVX5), fills the fields - MU01, Mumbai Sales Organisation, currency INR, country IN - and asks whether to assign this to Company Code ACPL immediately. All fields are filled with context-aware defaults for India. The admin only needs to confirm, not type anything into the SPRO screen.
Pre-filled: Currency: INR, Country: IN, Calendar: IN (India), Sales Org Type: Standard.
Shall I also assign MU01 → Company Code ACPL immediately? This is required before any sales area can be used for sales orders.
Joule creates both distribution channels - RE (Retail) and WH (Wholesale) - in the Distribution Channel definition screen (OVXI) and then immediately assigns both to Sales Org MU01 (OVXK). It explains that the assignment is what activates the distribution channel for this Sales Org - merely defining the channel is not enough. Both channels are created and assigned in a single guided conversation, not in four separate SPRO visits.
✓ RE – Retail (direct sales to end customers)
✓ WH – Wholesale (sales through distributors)
Both are now assigned to MU01 via OVXK. Next I'll create your divisions - which product categories do you need?
Joule creates divisions EL (Electronics) and HA (Home Appliances), assigns them to MU01, then builds all four sales area combinations: MU01-RE-EL, MU01-RE-HA, MU01-WH-EL, MU01-WH-HA. In SPRO this would require visiting OVX6 four times minimum. Joule does all four in one step, then verifies that every combination is valid and asks whether to assign each sales area to a plant and shipping point - the next required step for delivery processing.
✓ MU01 / RE / EL – Mumbai Retail Electronics
✓ MU01 / RE / HA – Mumbai Retail Home Appliances
✓ MU01 / WH / EL – Mumbai Wholesale Electronics
✓ MU01 / WH / HA – Mumbai Wholesale Home Appliances
All assignments are complete. Shall I now assign these sales areas to Plant MU01 and set up the Shipping Point assignment?
What Joule Saved: Building a full SD enterprise structure with 2 distribution channels, 2 divisions, and 4 sales areas manually requires visiting at least 8 separate SPRO nodes in the correct sequence - miss one assignment and all sales orders fail. With Joule, the entire setup was completed in one conversation. Estimated saving: 4–5 hours of careful manual work reduced to 30 minutes.
📄 Real Scenario: Configuring Custom Sales Order Types and Number Ranges Using Joule
Sales Document Types in SAP SD control how a sales order behaves - which number range it uses, which delivery type it creates, which billing type follows, what the credit limit check does, and which partner functions are mandatory. Creating a custom sales order type with correct settings used to require deep SD knowledge. With Joule it becomes a conversation about business requirements.
Rajan Electronics Ltd - Custom Sales Order Types for Retail and Export Sales
Rajan Electronics Ltd in Pune sells both domestically (standard retail orders) and through exports. They need two custom sales order types: ZRET for domestic retail orders with credit limit check and three-level credit approval, and ZEXP for export orders with mandatory incoterms, LC reference field, and foreign trade data. Both need separate number ranges and specific delivery and billing type assignments.
The SD consultant describes the domestic retail order type to Joule. Joule navigates to SPRO → SD → Sales → Sales Documents → Sales Document Header → Define Sales Document Types (VOV8), copies standard type OR (Standard Order) as the base, and applies the ZRET-specific settings. It sets credit limit check to D (automatic check at order save), asks for the credit group, and configures the delivery type LF and billing type F2 as the follow-on documents. The consultant answers in plain language - Joule translates to configuration values.
✓ Credit Limit Check: D (automatic at order save - blocks if exceeded)
✓ Delivery Type: LF (standard outbound delivery)
✓ Billing Type: F2 (standard invoice)
✓ Immediate Transfer of Requirement: Active
✓ Shipping Conditions: from customer master
Shall I set up number range 01 (0000010000–0000099999) for ZRET, or do you want a different range?
For the export order type ZEXP, Joule applies different settings - it makes the Incoterms field mandatory (foreign trade requirement), activates the LC (Letter of Credit) reference field in the header, and links to export-specific billing type IV (Pro Forma Invoice) and external delivery type LF. Joule also flags that for export orders the Foreign Trade/Customs data view in the customer master must be maintained and the Export Control Profile activated in the sales area data - dependencies that many consultants miss.
✓ Incoterms: Mandatory (field required at order entry)
✓ Billing Type: F8 (Pro Forma Invoice)
✓ Number Range: 02 (0000200000–0000299999)
✓ LC Reference Field: Active in header
✓ Foreign Trade Data: Active
⚠️ Note: For ZEXP to work, customers must have the Foreign Trade view maintained in XD02 and export control classification set. Shall I flag these as open items?
After creating both document types, Joule assigns them to the correct sales areas (ZRET to all domestic sales areas, ZEXP only to export-designated sales areas). It then sets up Copy Control - the rules that govern how data flows from Sales Order to Delivery to Invoice. Joule explains that without Copy Control, creating a delivery from a ZRET order would fail. It uses standard routines (1, 101, G, etc.) and asks only about exceptions - items that need custom copy rules.
▶ Assign to Sales Area: VOV8 → Sales Area assignment · Copy Control: VTLA (Order→Delivery), VTFL (Delivery→Billing), VTFA (Order→Billing) 🤖 Joule prompt: "Set up copy control from ZRET sales order to LF delivery and from LF delivery to F2 invoice"Interview Question This Covers: "What is the difference between a Sales Document Type and a Copy Control in SAP SD?" - Sales Document Type (configured in VOV8) defines how a sales order behaves - its fields, credit check, number range, and follow-on document types. Copy Control (VTLA, VTFL, VTFA) defines how data flows from one document to the next - which fields are copied, which are re-determined, and which routines run during the copy. Both are required: the document type sets the rules; the copy control makes the document chain work. Joule handles both together in one guided workflow.
💰 Real Scenario: Building a Pricing Procedure for SD Using Joule
The SD Pricing Procedure is the most complex - and most business-critical - configuration in the entire module. It controls every price component on a sales order: the base price, discounts, surcharges, taxes (GST), freight, and the final net value the customer pays. Getting it wrong means every invoice is wrong. With Joule, you describe the pricing logic in business terms and Joule builds the correct schema.
Vikram FMCG Ltd - GST-Compliant Pricing Procedure for Indian Market
Vikram FMCG Ltd in Hyderabad needs an SD pricing procedure for the Indian market that handles: base selling price (PR00), trade discount (K004 percentage), customer-specific special discount (K005), freight surcharge (KF00), 18% GST (ZGST), and final invoice value. The price must auto-populate from the customer-material info record and GST must calculate from the net value after all discounts. Building this manually in SPRO (VK00/M/08) takes an experienced consultant half a day - Joule does it in a single guided conversation.
The SD consultant tells Joule the pricing components needed. Joule builds the complete pricing schema ZINFMCG - defining the step numbers, condition types, from/to references for subtotals, requirement routines, calculation types, and account keys. It places GST (ZGST) at the correct step so it calculates on the net value after discounts, not on the gross base price. It also sets the statistical flag on informational subtotals so they appear on the order but do not affect the total.
Step 10: PR00 – Base Selling Price (mandatory, from condition records)
Step 20: K004 – Trade Discount % (subtract from Step 10)
Step 30: K005 – Customer Special Discount % (subtract from Step 10)
Step 40: ZNET – Net Value Subtotal (statistical, from Steps 10–30)
Step 50: KF00 – Freight Surcharge (fixed amount, added)
Step 60: ZGST – GST 18% (calculated on Step 40 net value)
Step 70: ZINV – Final Invoice Value (total of Steps 40+50+60)
GST base is correctly set to Step 40 to calculate on net-of-discount value. Account key MWS assigned to ZGST for G/L posting. Shall I now set up the Access Sequence for PR00?
The Access Sequence defines where SAP looks for a price - first in the customer-material combination, then by customer group, then by material group, then a general price. Joule builds the access sequence PR02 for PR00 with three access steps in priority order: (1) Customer + Material (most specific), (2) Price List + Currency + Material, (3) Material alone (general fallback). This means a special price for a specific customer is found first; the standard list price is the fallback. Joule explains the exclusion indicator - once a more specific price is found, lower-priority steps are not checked.
▶ Access Sequence: SPRO → SD → Basic Functions → Pricing → Pricing Control → Define Access Sequences · T-Code: V/07 🤖 Joule prompt: "Set up access sequence for PR00: check customer+material first, then customer price list, then general material price"Joule assigns ZINFMCG to the correct sales areas via the Pricing Procedure Determination table (OVKK). It then guides the creation of the first actual price condition record in VK11 - the base price for material FMCG-SOAP-200G in sales org MU01: ₹45.00 per unit, valid from today to 31-March-2026. Joule confirms that when a sales order is created for this material in the MU01/RE/HA sales area, the price ₹45 will be automatically found via the PR02 access sequence.
▶ Pricing Determination Assignment: OVKK · Create Condition Record: VK11 · Display Condition: VK13 · Analyse Pricing: V/LDJoule and the Pricing Procedure Determination: One of the trickiest parts of SD pricing configuration is the Pricing Procedure Determination - which pricing procedure applies to which sales area + document pricing procedure + customer pricing procedure combination. Without Joule you must navigate OVKK and fill the three-way key manually. With Joule you simply say "Assign ZINFMCG to all domestic retail sales areas" and Joule creates the correct entries in the determination table, explaining the three-way key as it goes so you understand the logic for future troubleshooting.
👥 Real Scenario: Customer Master Configuration and Partner Functions via Joule
Pramod Automobiles Ltd - Customer Account Groups and Partner Schemas
Pramod Automobiles Ltd needs to configure customer account groups and partner function schemas for three types of customers: direct dealers (ZDLR), distributors (ZDST), and end consumers for warranty registration (ZCON). Each group needs different field selections (what is mandatory vs optional on XD01), different number ranges, and different partner functions. For dealers the "Ship-to Party" and "Bill-to Party" can be different companies; for consumers they are always the same person. Joule handles all of this in a single configured conversation.
Joule creates all three account groups - ZDLR (Dealer), ZDST (Distributor), ZCON (Consumer) - in the customer account group definition screen (OBD2/OVXB in SD context). For each group it sets the number range, the field selection reference (which fields are mandatory, optional, suppressed on the customer master screens), and whether the account group represents a one-time customer. For ZCON (consumers), Joule suppresses many B2B-specific fields like Payment Method, Dunning Area, and Credit Control Area since consumers are handled differently.
ZDLR – Dealer: Number range 1000–1999999, all B2B fields active, credit control area mandatory.
ZDST – Distributor: Number range 2000–2999999, same field selection as ZDLR.
ZCON – Consumer: Number range 3000–3999999, Dunning: suppressed, Credit Control: suppressed, Payment Method: optional.
Field selections applied. Shall I now create the partner function schemas for each group?
Partner functions define the "roles" in a business transaction - Sold-to Party (SP), Ship-to Party (SH), Bill-to Party (BP), Payer (PY). For dealers (ZDLR), all four can be different companies - a dealer orders (SP), goods ship to their warehouse (SH), invoice goes to their head office (BP), and payment comes from their bank account (PY). For consumers (ZCON), all four are the same person. Joule builds the partner schema ZPAS (for ZDLR/ZDST) with all four functions mandatory, and ZPAC (for ZCON) where SP, SH, BP, PY are all linked to the same customer.
▶ Partner Functions: VOPAN · Partner Schemas: VOPAS · Assign Schema to Acct Group: VOPAB · Table: TPARA 🤖 Joule prompt: "Create partner schema ZPAS for dealers - SP, SH, BP, PY all mandatory and can be different customer numbers"With account groups and partner schemas ready, Joule guides the creation of the first dealer customer. The admin describes the customer in plain language. Joule fills all required views - General Data (name, address, bank details), Company Code Data (reconciliation account, payment terms), Sales Area Data (sales district, pricing procedure, customer pricing procedure, account assignment group for revenue posting). It automatically assigns partner schema ZPAS and prompts for the four partner addresses. All required fields based on ZDLR field selection are prompted - optional fields can be skipped.
▶ T-Code: XD01 (Create Customer with all views) · FD01 (FI only) · VD01 (SD only) · Table: KNA1 (general) + KNB1 (FI) + KNVV (Sales)Why Partner Functions Matter: The most common SD go-live issue is incorrect partner determination - either missing partner functions on the customer master or incorrect partner schemas on the document type. If the Payer (PY) partner function is missing on a customer, the billing document cannot be created. If the Ship-to Party (SH) is missing, the delivery cannot be processed. Joule's guided customer master creation ensures all mandatory partner functions are present before the customer is saved - preventing the cascading errors that block entire sales cycles.
⚡ SAP SD Configuration: Before vs After Using Joule
- Navigate 150+ SD SPRO nodes - must know every path by heart
- Sales area setup: 8 separate SPRO visits minimum
- Pricing procedure: half a day for an experienced consultant
- Missing one assignment = all sales orders blocked for that sales area
- Copy control setup requires deep document flow knowledge
- Access sequence configuration is notoriously confusing
- Partner function schemas - easy to get wrong silently
- Output determination setup requires knowing 5 separate config steps
- New customer account group takes 2–3 hours with field selection
- Full new entity SD setup: 3–5 days for experienced consultant
- Describe business need in plain language - Joule navigates
- Full sales area with 4 combinations built in one conversation
- Pricing procedure: describe components, Joule builds the schema
- Joule warns about missing assignments before you save
- Copy control: "link ZRET order to LF delivery" - Joule sets it up
- Access sequence: describe search logic, Joule creates the steps
- Partner schemas: answer "who can be different?" - Joule configures
- Output: "send PDF invoice by email to billing party" - Joule sets it
- Account group + field selection done in 30 minutes with guidance
- Full new entity SD setup: 4–6 hours with Joule guidance
| SD Configuration Task | Manual SPRO (hours) | With Joule (hours) | Time Saved |
|---|---|---|---|
| New Sales Org + all assignments | 3–4 hours | 0.5–1 hour | ~80% faster |
| Complete Sales Area (4 combinations) | 4–5 hours | 30–45 min | ~85% faster |
| Custom Sales Document Type + Copy Control | 3–4 hours | 45–60 min | ~80% faster |
| Full Pricing Procedure (6 condition types) | 5–7 hours | 1–1.5 hours | ~78% faster |
| Access Sequence (3 access steps) | 2–3 hours | 30 min | ~82% faster |
| Customer Account Groups + Field Selection | 2–3 hours | 30 min | ~82% faster |
| Partner Function Schema + Assignment | 2 hours | 20 min | ~83% faster |
| Output Determination (Invoice + Order Conf) | 3–4 hours | 40 min | ~80% faster |
| Full new entity SD setup | 3–5 days | 4–6 hours | ~78% faster |
📝 Joule Prompt Library - Copy These for SAP SD Configuration
Enterprise Structure Prompts
// Create a new Sales Organisation "Create sales organisation [CODE] called [NAME] for company code [BUKRS]. Country India, currency INR." // Create Distribution Channels and assign to Sales Org "Create distribution channels [DC1] ([DESC1]) and [DC2] ([DESC2]) and assign both to sales organisation [SORG]." // Create Divisions and build all Sales Areas "Create divisions [DIV1] and [DIV2] for sales org [SORG] and build all sales area combinations." // Assign Sales Area to Plant and Shipping Point "Assign sales area [SORG]/[DC]/[DIV] to plant [PLANT] and shipping point [SHPT]."
Sales Document and Pricing Prompts
// Create custom sales order type "Create sales order type [ZTYPE] for [business purpose]. Credit check [yes/no], delivery type [LF/etc], billing type [F2/etc], number range [XX]." // Build pricing procedure "Build pricing procedure [ZPROC] with: base price PR00, discount [K004] %, customer discount [K005] %, freight [KF00] fixed, GST [18%] on net value." // Set up access sequence "Set up access sequence for [CTYPE]: check customer+material first, then price list + material, then material alone as fallback." // Assign pricing procedure to sales area "Assign pricing procedure [ZPROC] to sales area [SORG]/[DC]/[DIV] with document pricing procedure [A] and customer pricing procedure [1]." // Create first condition record "Create a price condition record for material [MATNO] in sales org [SORG]: price [AMOUNT] per [UOM], valid from today to [DATE]."
Customer Master and Partner Function Prompts
// Create customer account group "Create customer account group [ZGRP] called [NAME]. Number range [XXXX–YYYY]. Make GST number mandatory. Suppress dunning and credit control fields." // Create partner function schema "Create partner schema [ZSCHEMA]: SP mandatory, SH mandatory (can differ from SP), BP mandatory (can differ from SP), PY mandatory (can differ from SP)." // Create customer master "Create customer [CUSTNO] called [NAME], account group [ZGRP], sales area [SORG]/[DC]/[DIV]. Payment terms [NT30]. Reconciliation account [140000]." // Set up output determination for invoices "Set up output type RD00 to send PDF invoice by email to the billing party when a billing document is saved. Transmission medium: 5 (external send)."
Tips for Better Joule Prompts in SD: (1) Always mention the Sales Area (Sales Org / Distribution Channel / Division) - Joule needs all three to place configuration in the right context. (2) Use the actual document type or condition type codes when you know them - "PR00" is more precise than "base price". (3) If you are not sure of codes, describe the business purpose - "the price a customer pays before any discounts" - and Joule will suggest the right condition type. (4) After any pricing change ask Joule: "What else do I need to configure for this to work in a sales order?" - it will check for missing access sequences, determination tables, and condition records.
⚠️ Joule Limitations for SAP SD Configuration
| SD Area | What Joule CAN Do | What Joule CANNOT Do |
|---|---|---|
| Enterprise Structure | Create Sales Org, DC, Div; handle all standard assignments including Sales Area | Cross-company-code sales setup; multiple plant assignment edge cases |
| Sales Document Types | Create and configure standard and custom order types based on OR, RE, CR, DR | Highly custom item category determination logic; multi-level BOM order types |
| Pricing | Build complete pricing schemas; assign access sequences; create standard condition records | Custom ABAP pricing routines (VOFM); complex rebate agreement configurations |
| Copy Control | Set up standard copy control for order→delivery→billing with standard routines | Custom copy routines requiring ABAP; inter-company billing copy control |
| Customer Master | Create customers with all standard views; field selection; partner schemas | Mass customer creation from external files (use LSMW/BAPI for large volumes) |
| Output Determination | Set up standard output types (RD00, BA00) for email, print, and EDI | Custom Smart Forms; complex EDI output with ALE/IDOC mapping |
| Availability | Available in SAP S/4HANA Cloud public and private cloud | NOT available in SAP ECC on-premise; limited in S/4HANA on-premise |
Interview Answer on Joule for SD: "Joule is the AI copilot in SAP S/4HANA Cloud that helps automate SD configuration by translating business requirements into SPRO actions. For SD specifically, it is most valuable for the complex assignment chain (Sales Org → Company Code → Plant → Sales Area), pricing procedure setup, and ensuring copy control completeness - the three areas most prone to errors that block sales order processing. Joule does NOT replace the need to understand SD concepts like the Order-to-Cash process, how pricing determination works, or what partner functions do. It makes execution faster; business knowledge is still required to ask it the right questions."
📚 SAP SD Configuration via Joule - Complete Reference
| SD Config Task | T-Code | SPRO Path (Short) | Joule Prompt Starter |
|---|---|---|---|
| Create Sales Organisation | OVX5 | Enterprise Structure → Definition → SD → Sales Org | "Create sales org [CODE] for company code [BUKRS], currency INR" |
| Assign Sales Org → Company Code | OVX3 | Enterprise Structure → Assignment → SD → Sales Org to CC | "Assign sales organisation [CODE] to company code [BUKRS]" |
| Create Distribution Channel | OVXI | Enterprise Structure → Definition → SD → Distribution Channel | "Create distribution channel [CODE] called [NAME]" |
| Assign DC to Sales Org | OVXK | Enterprise Structure → Assignment → SD → DC to Sales Org | "Assign distribution channel [CODE] to sales org [SORG]" |
| Create Division | OVXB | Enterprise Structure → Definition → Logistics General → Division | "Create division [CODE] called [NAME] for sales org [SORG]" |
| Create Sales Area | OVX6 | Enterprise Structure → Assignment → SD → Set up Sales Area | "Create all sales areas for sales org [SORG] with all channel and division combinations" |
| Assign Plant to Sales Org | OVX6 | Enterprise Structure → Assignment → SD → Assign Sales Org to Plant | "Assign sales area [SORG/DC/DIV] to plant [PLANT]" |
| Sales Document Type | VOV8 | SD → Sales → Sales Documents → Define Sales Document Types | "Create sales order type [ZTYPE] for [purpose], delivery type LF, billing F2" |
| Number Ranges for Sales Docs | VN01 | SD → Sales → Sales Documents → Define Number Ranges | "Set number range [XX] for sales document type [ZTYPE]" |
| Pricing Procedure | SPRO/M/08 | SD → Basic Functions → Pricing → Define Pricing Procedures | "Build pricing procedure with base price, % discount, freight, and 18% GST" |
| Access Sequence | V/07 | SD → Basic Functions → Pricing → Define Access Sequences | "Set up access sequence: customer+material first, then price list, then material" |
| Condition Record (Price) | VK11 | Logistics → SD → Master Data → Conditions → Create | "Create price ₹[X] per [UOM] for material [MATNO] in sales org [SORG]" |
| Customer Account Group | OBD2 | SD → Master Data → Business Partners → Customers → Account Groups | "Create customer account group [ZGRP] with mandatory GST number, number range [XXXX]" |
| Partner Function Schema | VOPAN | SD → Basic Functions → Partner Determination → Set up Partner Determination | "Create partner schema for dealers: SP, SH, BP, PY all mandatory and can be different" |
| Create Customer Master | XD01 | Logistics → SD → Master Data → Business Partners → Customers → Create | "Create customer [NAME] account group [ZGRP] in sales area [SORG/DC/DIV]" |
| Copy Control Order→Delivery | VTLA | SD → Sales → Maintain Copy Control for Sales Documents | "Set up copy control from sales order type [ZTYPE] to delivery type LF" |
| Output Determination | NACE | SD → Basic Functions → Output Control → Output Types | "Set up output type RD00 to email PDF invoice to billing party on billing save" |
The One-Line Summary for SAP SD + Joule: SAP SD configuration involves the most complex inter-connected assignment chain in all of SAP - Sales Org, Company Code, Distribution Channel, Division, Sales Area, Plant, Shipping Point, Pricing Procedures, Output Types, and Partner Functions must all be linked correctly before a single sales order can flow to a delivery and invoice. Joule transforms this multi-day expert task into a series of guided plain-language conversations - you describe what your business needs, Joule builds the correct configuration, warns about missing links, and validates the chain before saving. The concepts remain yours to understand; Joule handles the execution.