🤖 What Is SAP Joule, and How Does It Help With MM Configuration?
Today we are discuss What is Joule and How Help With MM Configuration?.SAP Joule is the built-in AI assistant in SAP S/4HANA Cloud. Think of it as having a very knowledgeable SAP expert sitting next to you - one who knows every configuration path in SPRO, every field in every transaction, and can guide you, fill in values, explain why each setting matters, and even trigger configuration actions directly. Instead of going through many SPRO options one by one, you can just type or say what you want to do. Joule understands your request, suggests the correct steps, and helps you finish the task easily. For SAP MM configuration - which involves lots of inter-connected settings across enterprise structure, master data, and procurement processes - Joule can turn a multi-day task into a few hours of guided, AI-assisted work.This tutorial Breaks Down the process step by step using simple language and real-world examples to help you master the skill.
The traditional way. consultant open SPRO, navigate through hundreds of hierarchical menus, know every IMG path by heart, remember the sequence, and fill each field manually - with no guidance on what values to enter or why.
The intelligent way. You describe what you want in plain language. Joule identifies the correct configuration path, explains what each field means, suggests appropriate values for your business context, and helps you complete the task step by step.
Plain Language Input
You do not need to know SPRO paths. Just say what you want: "Set up a new purchasing organisation for Mumbai plant" - Joule handles the rest.
Dependency-Aware
Joule knows that a Purchasing Organisation must be assigned to a Company Code before it can be assigned to a Plant. It warns you and sequences the steps correctly.
Validates as You Go
Before you save any configuration, Joule checks consistency rules - preventing the most common MM config mistakes like missing plant-valuation area assignments.
🧠 How Does Joule Actually Work for MM Configuration? (Step-by-Step)
Before going into specific scenarios, it is important to understand exactly how you interact with Joule and what happens technical details when you ask it to do MM configuration tasks.
in plain language
your intent (NLP)
the right SPRO path
and explains fields
validated ✓
Joule is available in SAP S/4HANA Cloud (not on-premise ECC 6.0). You access it by clicking the Joule icon → a small blue circular icon → in the top-right corner of any S/4HANA screen. It opens as a side panel without leaving your current screen. You can also use it while you are in SPRO, ME21N, MM01, or any other transaction. It is always available, always context-aware of what screen you are on.
🤖 Joule Panel → Top right corner icon in S/4HANA Cloud → Available on any screenYou do not need to know T-codes or SPRO menu paths. You can simply describe what you want to achieve. also Joule understands both technical language ("create a purchasing organisation") and business language ("we need to set up procurement for our new Delhi office"). It also understands follow-up questions in the same conversation - if you ask "what should I put in the currency field?" after starting a purchasing org setup, Joule knows you are still talking about the same task.
🤖 Example prompt: "I need to create a new purchasing organisation called PO-DELHI for our Delhi plant in company code INCO"Based on your request, Joule maps your intent to the correct SPRO path and can open the relevant configuration screen directly. For "create a purchasing organisation", it navigates to: SPRO → Enterprise Structure → Definition → Materials Management → Maintain Purchasing Organisation. It does not just tell you where to go - it can take you there and pre-fill fields based on what you have told it. This eliminates the need to memorise any SPRO path.
▶ SPRO Path: Enterprise Structure → Definition → MM → Maintain Purchasing Organisation (T-code: OX08)As you fill the configuration screen, you can ask Joule about any field. "What does the Purchasing Organisation Schema Group control?" - Joule explains that this field determines which pricing procedure schema is used when purchasing documents are created for this org. It gives you context-specific suggestions: "Since you are setting up for India, the standard recommendation is schema group 'Z001' for domestic procurement." This is the guidance that used to require an experienced consultant.
🤖 Ask Joule: "What should I enter in the Schema Group field for an Indian purchasing org?"After creating the Purchasing Organisation, Joule reminds you that it needs to be assigned to both the Company Code and the Plant before it can be used for procurement. It checks whether the required prerequisite configurations already exist - if the plant does not yet have a valuation area assigned, Joule flags this and guides you to complete it first. This sequential dependency management is one of the most valuable things Joule does - it prevents the cascading errors that plague manual MM configuration.
▶ Assigns: POrg → Company Code (OX01) → POrg → Plant (OX17) - Joule guides this sequence automaticallyWhere Joule Stores Configuration: Everything Joule helps you configure still gets saved in the exact same SAP customising tables as manual SPRO work. Joule is a smart interface layer - not a different system. A Purchasing Organisation created via Joule is identical to one created manually. It appears in T005E (Purchasing Organisation), is transported via standard transport requests (SE10), and follows all the same rules as any other SAP configuration. Joule just makes the process faster and safer.
🏢 Real Scenario: Setting Up SAP MM Enterprise Structure Using Joule
The Enterprise structure is the very first thing you configure in SAP MM. Before anything else - before material masters, before purchase orders, before inventory management - you must define and link the organisational units. This used to be one of the most confusing parts of SAP implementation. With Joule, it becomes a guided, error-free process.
Pramod Steel Industries - Setting Up New Delhi Plant with Joule
Pramod Steel Industries is expanding operations and needs to add a new manufacturing plant in Delhi (Plant code: DL01) to their existing SAP S/4HANA Cloud system. The SAP admin must configure the full enterprise structure for this plant - company code assignment, purchasing organisation, storage locations, and valuation area - without manual SPRO navigation.
The admin opens Joule and types their requirement. Joule immediately identifies that this is a Plant Definition task, opens the correct configuration screen, and starts a guided setup wizard. It pre-fills the country (India), language (EN), factory calendar (IN for India), and suggests the valuation area matches the plant code (DL01) since this is an independent valuation scenario. The admin only needs to confirm or adjust the suggested values.
I've pre-filled: Country: IN, Currency: INR, Factory Calendar: IN (India), Language: EN. I recommend setting the Valuation Area to DL01 for plant-level valuation. Shall I also assign this plant to Company Code PSI1 immediately after saving?
After the plant is saved, Joule automatically moves to the next required step - assigning the plant to the company code. Without this assignment, the plant cannot post financial entries. Joule shows the existing company code PSI1 (Pramod Steel Industries Ltd) and completes the assignment in one click. It also checks whether the fiscal year variant and chart of accounts are correctly set for this company code before completing the assignment.
I also notice that Plant DL01 does not yet have any Storage Locations defined. Shall I help you create the storage locations for this plant next?
Storage locations define where within a plant physical inventory is stored - Raw Material Store, Finished Goods Store, Rejection Area, Quarantine Store. Joule suggests standard storage location codes based on Indian manufacturing norms and allows you to create all of them in one go. Each storage location is assigned to plant DL01 automatically. What used to be a repetitive manual entry for each location is now a single guided conversation.
RM01 – Raw Material Store
FG01 – Finished Goods Store
RJ01 – Rejection Area
QI01 – Quality Inspection Hold
All assigned to Plant DL01. Your enterprise structure for the Delhi plant is now complete!
What Joule Saved Here: The traditional manual approach to setting up a new plant in SAP MM requires navigating at least 6 separate SPRO nodes (plant definition, company code assignment, purchasing org assignment, storage location creation, valuation area, and factory calendar), each with its own menu path and dependencies. With Joule, the entire sequence took one conversation, with automatic dependency checking and no missed steps. Estimated time saving: 3–4 hours of manual SPRO work reduced to 20 minutes.
🏷️ Real Scenario: Configuring Material Types and Creating Material Masters Using Joule
Material Types in SAP MM define how a material behaves - which accounts it posts to, which fields are mandatory, whether it is valuated, and which procurement types apply. Configuring a custom material type and then creating materials under it is one of the most common MM configuration tasks. With Joule, even the field-level decisions become guided.
Vikram Pharmaceuticals Ltd - Custom Material Type for API Ingredients
Vikram Pharmaceuticals Ltd in Hyderabad needs a custom material type for their Active Pharmaceutical Ingredients (APIs) - raw materials that require stricter batch management, GMP documentation, and separate G/L accounts compared to regular raw materials. The existing SAP standard ROH (Raw Material) type does not have all the required settings. The admin needs to create a new material type ZAPI and then create the first material under it.
The admin asks Joule to create a custom material type. Joule understands that ZAPI should be based on ROH (Raw Material) but with specific differences. It opens the material type configuration screen, copies the ROH settings as a starting point, and then walks through each setting group - asking about quantity/value updating, account determination, special procurement, and batch management requirements. The admin can answer in plain language and Joule translates the answers into correct configuration values.
✓ Quantity updating: Active (stock tracked in quantity)
✓ Value updating: Active (stock tracked in value in FI)
✓ Batch Management: Mandatory (every GR must have a batch number)
✓ Procurement Type: F (external procurement only)
✓ Internal/External Purchase Orders: Both allowed
Do you want me to also set up separate valuation classes (like 3100 for API raw materials) in the account category reference so API materials use different G/L accounts than regular raw materials?
Joule explains that for separate G/L accounts to work for API materials, we need to set up a new Account Category Reference (ZAPI_REF) and link specific valuation classes to it. This is configuration that many junior consultants miss - leading to APIs posting to the same accounts as general raw materials. Joule walks through the configuration step by step, asking clear business questions and mapping the answers to the correct SPRO settings without the admin needing to know the path.
▶ SPRO → MM → Valuation → Account Determination → Account Determination Without Wizard → Define Valuation Classes · T-Code: OMSK 🤖 Joule prompt: "Set up valuation class 3100 for API raw materials linked to material type ZAPI"With ZAPI configured, Joule helps create the first API material: Paracetamol API (Material: API-PARA-500). Instead of the standard MM01 multi-screen navigation, the admin describes the material in plain language. Joule asks targeted questions for each view - Basic Data 1 (description, base unit, material group), Purchasing (purchasing group, planned delivery time, GR processing time), MRP (MRP type, lot size, safety stock), Quality Management (inspection type for GMP compliance, certificate type). Each answer maps to the correct field automatically.
I've filled: Material Type: ZAPI, Base Unit: KG, Plant: DL01, Planned Delivery Time: 30 days, Minimum Order Qty: 25 KG, Storage Conditions: Room temperature (02), Batch Management: Active (mandatory per ZAPI type).
For GMP compliance, I recommend enabling QM Inspection Type 0101 (goods receipt inspection) and Certificate Type B1 (Certificate of Analysis). Shall I configure these in the QM view?
Joule and Field Selection Profiles: One of the most powerful uses of Joule for MM configuration is managing Field Selection - controlling which fields are mandatory, optional, or hidden on MM01 screens for different material types. Without Joule you need to navigate SPRO → MM → Basic Functions → Material Master → Field Selection and understand the complex field selection logic. With Joule, you simply say: "Make the Hazardous Material Number field mandatory for all ZAPI materials" and Joule makes the correct field selection setting in the right reference field group.
📋 Real Scenario: Configuring Purchase Order Settings and Document Types Using Joule
Rajan Auto Components - Setting Up PO Document Types and Approval Workflow
Rajan Auto Components in Pune needs to configure two custom Purchase Order document types: one for domestic suppliers (ZDPО) with a three-level approval workflow, and one for import/overseas suppliers (ZIРО) with mandatory LC (Letter of Credit) field and customs duty handling. Both need number ranges, text schemas, and message schemas configured. This is complex MM configuration - Joule makes it a conversation.
The MM consultant types the business requirement to Joule. Joule navigates to the Document Types configuration in SPRO, copies the standard NB (Standard PO) document type as a starting point for both custom types, and applies the differences. For ZDPO it sets up three-level workflow approval. For ZIPO it makes the incoterms and LC reference fields mandatory. Joule explains that document types control which fields appear, which number ranges apply, and which workflow is triggered.
ZDPO – Domestic Purchase Order: Number range: 45 (4500000000–4599999999), Approval: 3-level workflow, Field selection: Standard domestic fields.
ZIPO – Import Purchase Order: Number range: 46 (4600000000–4699999999), Incoterms: Mandatory, Import indicator: Active, Header text for LC reference: Mandatory.
I've also assigned both types to Purchasing Organisation PO-IN01. Shall I now configure the 3-level approval workflow release strategy for ZDPO?
Release Strategy in SAP MM is notoriously complex to configure manually - it requires setting up Release Groups, Release Codes, Release Indicators, and Release Conditions in separate SPRO steps with correct sequence. Many consultants spend a full day on this. With Joule, the admin describes the business rule and Joule configures all the underlying settings. "POs up to ₹1 lakh: approved by Purchase Supervisor. Up to ₹10 lakh: also requires Finance Manager. Above ₹10 lakh: requires CFO approval." Joule translates this into the Release Strategy tables (T16FS, T16FC, T16FK) correctly.
L1 (Level 1) – Purchase Supervisor: Triggered for all ZDPO orders. Release code: 01
L2 (Level 2) – Finance Manager: Triggered when PO value > INR 100,000. Release code: 02
L3 (Level 3) – CFO: Triggered when PO value > INR 1,000,000. Release code: 03
Release conditions are set using characteristic GNETW (net order value). The workflow is ready - shall I assign user IDs to each release code?
The pricing procedure determines which price components (basic price, freight, GST, customs duty) appear on a purchase order and how they are calculated. For ZDPO (domestic), the pricing procedure needs basic price, freight, and GST components. For ZIPO (import), it additionally needs custom duty, CVD, and assessable value calculations. Joule helps build both pricing procedures by asking about each condition type in business terms - "Does your domestic PO price include freight or is it shown separately?" - and then building the correct schema in SPRO.
▶ SPRO → MM → Purchasing → Conditions → Define Price Determination Process → Define Calculation Schema · T-Code: M/08 🤖 Joule prompt: "Build a pricing procedure for domestic POs with basic price, freight, and 18% GST. Make freight changeable at PO level."Interview Question This Covers: "How does SAP MM Release Strategy work?" - Release Strategy is configured in SPRO and controls who needs to approve a Purchase Order before it can be processed. It uses Characteristics (like GNETW = net value, EKGRP = purchasing group) to evaluate conditions, and Release Codes to identify approvers. A PO in "blocked" status cannot be used for goods receipt. Joule makes configuring this approachable - but you still need to understand the underlying logic (Release Group → Release Code → Release Indicator → Workflow) for interviews and troubleshooting.
📊 Real Scenario: Setting Up Purchasing Info Records and Source Lists with Joule
Purchasing Info Records store the agreed price and conditions between a vendor and a material - they are the source of truth that populates purchase orders automatically. Source Lists define which vendors are approved for which materials and whether a vendor is mandatory, optional, or blocked. Together they automate and control the purchasing process. Joule makes creating and maintaining these records dramatically faster.
Suresh Metals Ltd - Bulk Info Record and Source List Setup via Joule
Suresh Metals Ltd in Surat has just negotiated annual rate contracts with 3 vendors for their top 20 raw materials. The procurement team needs to create Purchasing Info Records for all material-vendor combinations (60 records) and then set up Source Lists so MRP automatically proposes the right vendor for each material. Doing this manually in ME11 for 60 records would take most of a day. With Joule, it can be done in under an hour.
The procurement manager uploads the rate contract Excel file to the SAP S/4HANA document management area and then asks Joule to read it and create the info records. Joule reads the structured data - vendor code, material code, price, unit, validity period, minimum quantity - and creates the corresponding info records in ME11. It handles the Purchasing Organisation and Plant assignment for each record. For records where a vendor has negotiated a scale price (e.g., price drops at 100+ units), Joule adds the pricing conditions in the correct pricing procedure schema.
✓ Info Record Number: 5300012456 (auto-assigned)
✓ Net Price: ₹68.00 per KG
✓ Validity: 01-Apr-2025 to 31-Mar-2026
✓ Minimum Order Qty: 500 KG
✓ Purchasing Org: PO-IN01 · Plant: DL01
✓ Order Unit: KG · Info Category: Standard
Info record created. Do you want me to also add this vendor to the Source List for MS-ROD-12MM at plant DL01?
Joule follows up on the info record creation by immediately proposing to create the Source List entry. A Source List tells SAP's MRP engine which vendor(s) are approved for a material. The "Fixed" flag means MRP will always propose this vendor - no user decision needed. The "Blocked" flag means this vendor must not be used (useful for quality-hold situations). Joule sets up the source list for all 20 materials across the 3 vendors in a systematic guided conversation - asking about which vendor should be fixed/preferred and which are alternative suppliers.
✓ V-1034 (Joshi Steel) → Fixed vendor (MRP will always propose this vendor first)
✓ V-1087 (Mehta Metals) → Alternative vendor (purchaser can select manually)
Both valid: 01-Apr-2025 to 31-Mar-2026
I've also activated the Source List Requirement flag on the material master for MS-ROD-12MM - this means purchase orders can only be created to vendors on the approved source list. This prevents unauthorised vendor usage.
Joule helps verify the entire configuration chain by walking through a test purchase order creation. When the buyer opens ME21N and enters material MS-ROD-12MM and plant DL01, SAP should automatically: (1) propose vendor V-1034 from the source list, (2) pull the price ₹68/KG from the info record, (3) require a minimum of 500 KG. Joule walks through this test, checking each automatic fill, and confirms the configuration is working end-to-end before the procurement team begins using it for live transactions.
▶ T-Code: ME21N (Create PO) - Test that vendor is proposed, price is pulled from info record, minimum quantity is applied 🤖 Joule prompt: "Create a test purchase order for MS-ROD-12MM at plant DL01 for 500 KG and verify the price and vendor are automatically populated"The Power of Joule for Bulk Operations: Traditional SAP does not have a good native bulk creation tool for Info Records and Source Lists - most companies resort to LSMW (Legacy System Migration Workbench) or custom ABAP programs, both of which require technical resources. Joule's natural language interface and ability to create multiple records in a conversational flow effectively provides bulk creation capability without any technical development. For a company with 500+ material-vendor combinations, this alone can save weeks of implementation effort.
⚡ SAP MM Configuration: Before vs After Using Joule
Here is a clear picture of how Joule changes the MM configuration experience across the most common tasks.
- Navigate 200+ SPRO nodes manually - need to know every path
- No guidance on what to fill in each field - rely on documentation
- Dependency errors only discovered when something fails downstream
- Creating 60 info records = 60 separate ME11 transactions, one by one
- Release strategy setup takes 1–2 full days for an experienced consultant
- Custom material type configuration requires deep SPRO expertise
- Storage location creation: each one a separate manual entry
- No automatic validation - errors caught only during testing or go-live
- New consultants need months to learn the SPRO landscape
- Forgot one assignment (e.g., plant to company code) = procurement blocked
- Describe what you want in plain language - Joule finds the SPRO path
- Context-aware field guidance for every screen - explains WHY, not just what
- Joule warns about missing dependencies before you hit save
- Create 60 info records in a guided conversation in under an hour
- Release strategy: describe the business rule, Joule builds the strategy
- Material type: answer business questions, Joule sets technical values
- Create multiple storage locations in one conversational exchange
- Automatic consistency checks - validated at the point of configuration
- New team members productive from day one with Joule guidance
- Joule suggests the complete sequence for new plant setup automatically
| Configuration Task | Manual SPRO (hours) | With Joule (hours) | Time Saved |
|---|---|---|---|
| New Plant Setup (all assignments) | 4–6 hours | 0.5–1 hour | ~80% faster |
| Custom Material Type + Field Selection | 3–4 hours | 0.5–1 hour | ~75% faster |
| PO Document Type + Number Range | 2–3 hours | 30–45 minutes | ~75% faster |
| Release Strategy (3-level) | 6–8 hours | 1–2 hours | ~80% faster |
| 50 Purchasing Info Records | 4–5 hours | 45 minutes | ~85% faster |
| Source List for 20 materials × 3 vendors | 3–4 hours | 30 minutes | ~87% faster |
| Pricing Procedure Setup | 4–6 hours | 1–2 hours | ~70% faster |
| Full new entity MM setup (plant + all config) | 3–5 days | 4–8 hours | ~75% faster |
📝 Joule Prompt Library - Copy These for Your SAP MM Configuration
Here is a practical library of tested Joule prompts for the most common SAP MM configuration tasks. Copy and adapt these to your own system values.
Enterprise Structure Prompts
// Create a new plant "Create a new plant [PLANT_CODE] called [PLANT_NAME] in company code [BUKRS]. Country is India. Assign it to purchasing org [PORG_CODE]." // Create storage locations in bulk "Create 5 storage locations for plant [PLANT_CODE]: Raw Material Store (RM01), Finished Goods (FG01), WIP Store (WI01), Rejection Area (RJ01), and Quarantine (QH01)." // Create a new purchasing organisation "Set up a new purchasing organisation [PORG_CODE] called [PORG_NAME]. Assign it to company code [BUKRS]. Currency is INR." // Assign purchasing org to plant "Assign purchasing organisation [PORG_CODE] to plant [PLANT_CODE]."
Material Master and Material Type Prompts
// Create a material master "Create material master [MAT_CODE] for [DESCRIPTION], material type [MATTYPE], base unit [UOM], for plant [PLANT_CODE]. Lead time [X] days, minimum order [Y] [UOM]." // Create custom material type "Create a custom material type [ZTYPE] based on [ROH/HALB/FERT]. Enable batch management as mandatory. Set up separate G/L accounts using valuation class [XXXXX]." // Update MRP settings for a material "Update MRP settings for material [MAT_CODE] at plant [PLANT_CODE]: MRP type MQ (reorder point), reorder level [X] [UOM], reorder quantity [Y] [UOM]." // Extend material to a new plant "Extend material [MAT_CODE] to plant [NEW_PLANT]. Copy settings from plant [OLD_PLANT] but set a new storage location [SLOC_CODE]."
Purchasing and Info Record Prompts
// Create purchasing info record "Create a purchasing info record for vendor [VENDOR_CODE] and material [MAT_CODE] at plant [PLANT_CODE]. Price is [AMOUNT] per [UOM], valid until [DATE]. Minimum order [MIN_QTY] [UOM]." // Set up source list "Add vendor [VENDOR_CODE] to the source list for material [MAT_CODE] at plant [PLANT_CODE] as the fixed (mandatory) vendor. Valid from [DATE1] to [DATE2]." // Configure release strategy "Set up a PO release strategy for document type [DTYPE]: orders up to [AMOUNT1] need [APPROVER1] approval, up to [AMOUNT2] need [APPROVER1] and [APPROVER2], above [AMOUNT2] need all three levels including [APPROVER3]." // Create outline agreement (contract) "Create a quantity contract for vendor [VENDOR_CODE] for material [MAT_CODE], total quantity [QTY] [UOM], price [PRICE] per [UOM], valid until [DATE]. Plant [PLANT_CODE], purchasing org [PORG_CODE]."
Tips for Writing Better Joule Prompts: (1) Always include the specific codes - Joule works best when you give it exact plant codes, vendor numbers, and material numbers from your system. (2) Mention the validity dates - Joule asks for them anyway and including them upfront saves a round-trip. (3) If Joule's suggestion is not right, just say "not quite - I actually need..." and correct it in the same conversation. Joule remembers the full conversation context. (4) For complex tasks, break them into steps: "First do X, then we will do Y." (5) Ask "is there anything else I need to configure for this to work?" - Joule will check for missing dependencies proactively.
⚠️ Joule Limitations - What You Still Need to Know and Do Manually
Joule is powerful but not unlimited. Understanding what Joule cannot do is just as important as knowing what it can - especially for experienced consultants and for anyone preparing for SAP interviews.
| Area | What Joule CAN Do | What Joule CANNOT Do |
|---|---|---|
| Enterprise Structure | Create plants, storage locations, purchasing orgs; handle all standard assignments | Multi-language plant name setup; special characters in descriptions |
| Material Master | Create and extend material masters; guide field selection; suggest values | Mass material master changes (use LSMW or MM17); classification value upload |
| Pricing Procedures | Create standard pricing schemas, assign condition types, set calculation rules | Complex access sequence logic; highly custom condition formulas (VOFM routines) |
| Release Strategy | Build complete release strategies from business rules; assign release codes | Complex cross-document-type release strategies; retroactive release on existing POs |
| Info Records / Source Lists | Individual creation and guided bulk creation; validity dates; scale prices | Mass upload from external files (still needs LSMW/BAPI for large volumes) |
| Account Determination | Basic G/L account assignments for standard movement types | Complex account determination for special stock types, split valuation, consignment |
| Transports / Changes | Configuration is saved to the system; standard transport requests created | Cannot manage transport routes, import queues, or cross-system transports (use STMS) |
| Availability | Available in SAP S/4HANA Cloud (public cloud and private cloud) | NOT available in SAP ECC (on-premise); limited availability in S/4HANA on-premise |
Interview Answer on Joule: If an interviewer asks "What is SAP Joule and how does it help MM configuration?" - the correct answer covers three things: (1) Joule is the AI copilot built into SAP S/4HANA Cloud, powered by large language models trained on SAP documentation and processes. (2) For MM configuration, Joule reduces the time and expertise needed to navigate SPRO by translating business requirements into configuration actions, handling dependencies, and validating settings. (3) It does NOT replace the need to understand SAP MM concepts - a consultant still needs to know what a Release Strategy is, what the enterprise structure means, and how valuation classes work. Joule makes execution faster; it does not replace conceptual knowledge.
📚 SAP MM Configuration via Joule - Complete Reference
| MM Config Task | T-Code | SPRO Path (Short) | Joule Prompt Starter |
|---|---|---|---|
| Create Plant | OX10 | Enterprise Structure → Definition → Log General → Plant | "Create a new plant [code] called [name] in company code [BUKRS]" |
| Assign Plant → Company Code | OX18 | Enterprise Structure → Assignment → MM → Assign Plant to CC | "Assign plant [code] to company code [BUKRS]" |
| Create Purchasing Org | OX08 | Enterprise Structure → Definition → MM → Purchasing Org | "Create purchasing organisation [code] for company code [BUKRS]" |
| Assign POrg → Plant | OX17 | Enterprise Structure → Assignment → MM → Assign Purch Org to Plant | "Assign purchasing org [code] to plant [code]" |
| Create Storage Location | OX09 | Enterprise Structure → Definition → MM → Storage Location | "Create storage location [code] at plant [code]" |
| Material Type Attributes | OMS2 | MM → Basic Functions → Material Master → Define Material Types | "Create custom material type [ZTYPE] based on [ROH/FERT]" |
| Valuation Classes | OMSK | MM → Valuation → Account Determination → Define Valuation Classes | "Set up valuation class [XXXX] for material type [ZTYPE]" |
| Number Ranges for PO | OMH6 | MM → Purchasing → Purchase Order → Define Number Ranges | "Set number range [45] for PO document type [ZDPO]" |
| PO Document Types | OMEC | MM → Purchasing → Purchase Order → Define Document Types | "Create PO document type [ZDPO] for domestic purchases" |
| Release Procedure | OME9 / OMEN | MM → Purchasing → PO → Release Procedure | "Set up 3-level release strategy: [amount1] supervisor, [amount2] manager, [amount3] CFO" |
| Pricing Procedure (MM) | M/08 | MM → Purchasing → Conditions → Define Calculation Schema | "Build pricing procedure with basic price, freight, and 18% GST" |
| Purchasing Info Record | ME11 | Logistics → MM → Purchasing → Master Data → Info Record | "Create info record for vendor [V-code] material [M-code] price [X] per [UOM]" |
| Source List | ME01 | Logistics → MM → Purchasing → Master Data → Source List | "Add vendor [V-code] as fixed vendor in source list for material [M-code]" |
| Material Master - Create | MM01 | Logistics → MM → Material Master → Create Material | "Create material [code] for [description], material type [type], plant [code]" |
| Material Master - Extend | MM01 / MMAM | Logistics → MM → Material Master → Change Material | "Extend material [code] to plant [new plant], copy MRP settings from [old plant]" |
The One-Line Summary: SAP Joule transforms MM configuration from a menus-and-memorisation exercise into a guided, conversational experience. You describe what you want in business language, Joule maps it to the correct SPRO path, guides you through every field with context-aware advice, checks dependencies automatically, and saves configuration correctly - exactly the same as manual SPRO work, just dramatically faster and more guided. The key insight is that Joule is a smarter interface to the same SAP system - not a replacement for understanding SAP MM concepts.