SD 考试常见陷阱与易错点

发表于 更新于 分类于 ， ， 阅读次数： 本文字数： 1.1k 阅读时长 ≈ 4 分钟

Exam Traps (考试陷阱)

⚠️Common Pitfalls
This page lists common mistakes and traps in SD exams. Each trap links to the relevant concept note.

Organizational Structure Traps

⛔Trap: Sales Area Assignments
Question: Can a sales organization be assigned to multiple company codes?

Wrong Answer: Yes
Correct Answer: No - A sales organization can only be assigned to ONE company code. However, multiple sales organizations can be assigned to one company code.

→ [[01-Enterprise-Structure/Org-Units-Overview]]

⛔Trap: Shipping Point Assignment
Question: How are shipping points assigned?

Wrong Answer: Shipping points are assigned directly to sales organizations.
Correct Answer: Shipping points are assigned to plants, not directly to sales organizations.

→ [[01-Enterprise-Structure/Shipping-Structure]]

⛔Trap: Multiple Distribution Channels
Question: Can one distribution channel be assigned to multiple sales organizations?

Correct Answer: Yes - A distribution channel can be assigned to multiple sales organizations.

→ [[01-Enterprise-Structure/Sales-Area-Structure]]

Master Data Traps

⛔Trap: Customer Master Number Assignment
Question: How are customer numbers assigned?

Key Points:

  • Account Group controls whether number assignment is internal or external
  • Internal: System automatically assigns the next available number
  • External: User must enter a unique number
  • This is set at the account group level, not globally

→ [[03-Master-Data/Customer-Master]]

⛔Trap: One-Time Customers
Question: What is special about one-time customers?

Key Points:

  • One-time customers have a single master record
  • Actual customer data (name, address) is entered at document level
  • Used when you don’t want to maintain full master records for occasional customers

→ [[03-Master-Data/Customer-Master]]

⛔Trap: Material Master Views
Question: Who maintains which material master views?

Key Points:

  • Basic Data View: All departments (central maintenance)
  • Sales View: Sales department (pricing, sales unit)
  • Shipping View: Shipping/Plant departments (shipping data, loading grp)
  • Not all views are required for all materials

→ [[03-Master-Data/Material-Master]]

Document Processing Traps

⛔Trap: Sales Area Assignment
Question: Can you change the sales area of a sales document after creation?

Correct Answer: No - Once a sales document is created, its sales area assignment cannot be changed. This is because pricing, master data access, and many other controls are based on sales area.

→ [[04-Data-Determination/Sales-Document-Types]]

⛔Trap: Document Flow
Question: Which documents can follow a sales order?

Key Points:

  • Standard flow: Sales Order → Delivery → Billing
  • Not all documents are mandatory - depends on document type and configuration
  • You can have multiple deliveries from one order (partial deliveries)
  • You can have multiple billing documents from one delivery

→ [[02-Process-Overview/SD-Process-Chain]]

⛔Trap: Delivery Type Determination
Question: How is the delivery type determined?

Key Points:

  • Delivery type is determined based on sales document type + item category
  • Not directly selectable by the user in most cases
  • Configuration in delivery type determination table

→ [[04-Data-Determination/Sales-Document-Types]]

Shipping and Delivery Traps

⛔Trap: Shipping Point Determination
Question: When is shipping point determined?

Key Points:

  • Shipping point is determined at sales order time (not at delivery creation)
  • Based on: Plant + Shipping Conditions (from customer master) + Loading Group (from material master)
  • If multiple shipping points are found, system may require manual selection

→ [[04-Data-Determination/Plant-Shipping-Route]]

⛔Trap: Route Determination
Question: What factors determine the route?

Key Points:

  • Departure Zone (from shipping point master)
  • Transportation Zone (from customer master)
  • Shipping Conditions (from customer master)
  • Transportation Group (from material master)
  • Weight Group (from weight of items)
  • Route is determined at sales order time

→ [[04-Data-Determination/Plant-Shipping-Route]]

⛔Trap: Picking and Shipping
Question: What is the sequence of shipping activities?

Correct Sequence:

  1. Create Delivery (VL01N)
  2. Post Goods Issue (VL02N)
  3. Pick (VL02N) - can be before GI
  4. Pack (VL02N) - optional
  5. Ship (VL02N) - create shipment document

→ [[04-Data-Determination/Shipping-Planning]]

Availability Check Traps

⛔Trap: ATP Logic
Question: What is included in ATP calculation?

Key Points:

  • Warehouse Stock: Physical stock in plant
  • Planned Issues: Outgoing movements (orders, deliveries)
  • Planned Receipts: Incoming movements (purchase orders, production orders)
  • ATP = Warehouse Stock + Planned Receipts - Planned Issues
  • Different checking rules control what’s included

→ [[05-Availability-Check/ATP-Basics]]

⛔Trap: Checking Group vs Checking Rule
Question: What’s the difference?

Key Points:

  • Checking Group: Material-specific (defined in material master)
  • Checking Rule: Transaction-specific (defined in sales order type, etc.)
  • Together they control the availability check scope
  • Example: Different rules for sales order vs delivery

→ [[05-Availability-Check/ATP-Basics]]

Complaint Processing Traps

⛔Trap: Credit Memo vs Returns
Question: What’s the difference between credit memo and returns?

Key Points:

  • Credit Memo Request: No goods movement, only financial credit
  • Returns: Goods are returned from customer, requires delivery and goods receipt
  • Credit memo is faster for financial-only adjustments
  • Returns must track physical goods

→ [[07-Complaints/Credit-Memo]]

⛔Trap: Invoice Correction Request
Question: When should you use invoice correction?

Key Points:

  • Used for correcting billing amount errors
  • Contains both debit and credit items
  • Creates an invoice with corrected amounts
  • Not for returning goods (use Returns instead)

→ [[07-Complaints/Invoice-Correction]]

Pricing and Condition Traps

⛔Trap: Condition Exclusion
Question: How do condition exclusions work?

Key Points:

  • Multiple condition records can exist for same condition type
  • Exclusion indicator prevents certain conditions from being combined
  • Best Condition principle: Most favorable condition is selected
  • Configuration controls which conditions can be combined

→ [[03-Master-Data/Condition-Records]]

⛔Trap: Access Sequence
Question: What is an access sequence?

Key Points:

  • Access Sequence defines the search order for condition records
  • System searches in sequence until it finds a valid record
  • Example: Customer/Material → Customer → Material → All
  • First match wins!

→ [[03-Master-Data/Condition-Records]]

General Exam Tips

💡Memory Aids
  • Sales Area = Sales Org + Dist Channel + Division (remember: S+D+D = Sad)
  • Shipping Point = Plant + Shipping Cond + Loading Grp (remember: P+S+L = PSL)
  • Document Flow: Always remember: Order → Delivery → Billing
  • ATP: Stock + In - Out
💡Question Keywords
  • “Always” or “Never” → These answers are often wrong
  • “Multiple” → Check if it’s N:1 or 1:N relationship
  • “Automatic” → Usually involves configuration/master data
  • “Manual” → Requires user intervention during processing
⚠️Read Carefully
  • Pay attention to: “Sales Organization” vs “Sales Area”
  • “Shipping Point” vs “Plant”
  • “Customer Master” vs “Customer Material Info Record”
  • “Condition Type” vs “Condition Record”
  • [[00-Dashboard/00-Quick-Reference]] → Quick reference for all concepts
  • [[00-Dashboard/00-MOC]] → Complete topic map