Sample Interview QA FOR PRACTICE

SAP SD L2 Support Interview Guide

25 Real-Life Scenario-Based Questions with Detailed Solutions

This comprehensive guide contains 25 real-life scenario-based SAP SD questions commonly asked in L2
Support and Functional Consultant interviews at MNCs. Each question includes detailed troubleshooting
steps, configuration guidance, and practical tips based on actual support scenarios.

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
Technical Troubleshooting Scenarios

1. A user reports that a delivery document is not getting created from the sales order. How do you
troubleshoot?

Systematic Troubleshooting Approach:

• Check Sales Order Status: VA03 - Verify order is not blocked or incomplete

• Verify Delivery Block: Check delivery block at header/item level

• Availability Check: Ensure stock is available and not reserved elsewhere

• Incomplete Log: VA02 → Environment → Incompletion Log

• Copy Control Settings: VTLA - Check sales order to delivery copy control

• Item Category Configuration: Verify item category allows delivery creation

• Plant/Storage Location: Confirm proper plant assignment in sales order

Pro Tip:

Always check the document flow (VA03 → Environment → Document Flow) to see if delivery creation
was attempted and failed with specific error messages.

2. An invoice is failing to post to accounting (FI). What steps would you take to find and fix the issue?

Root Cause Analysis Steps:

• Check Billing Document: VF03 - Review document status and error messages

• Account Determination: VKA1/VKA2 - Verify G/L account assignment

• Customer Master Data: XD03 - Check reconciliation account

• Tax Configuration: Verify tax codes and account assignments

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
• Pricing Procedure: Check condition types have proper G/L accounts

• Company Code Settings: Ensure proper FI integration settings

• Document Splitting: Check if document splitting is causing issues

Common Solutions:

Most issues are due to missing G/L account assignments in account determination or incorrect customer
reconciliation accounts. Always test with VF01 to see real-time error messages.

3. The tax is not being calculated correctly in the billing document. What could be the possible
reasons?

Tax Calculation Troubleshooting:

• Customer Tax Classification: XD03 - Check tax classification 1 field

• Material Tax Classification: MM03 - Verify tax classification in sales view

• Tax Procedure: FTXP - Check country-specific tax procedure

• Tax Codes: VK03 - Verify tax condition records

• Pricing Procedure: Ensure tax condition types are properly sequenced

• Plant Configuration: Check tax jurisdiction codes

• Condition Technique: Verify access sequence for tax conditions

Quick Check:

Use VA03 → Conditions to see if tax conditions are being picked up. Most tax issues stem from incorrect
customer/material tax classifications.

4. Pricing is missing in the sales order. How would you resolve it?

Pricing Troubleshooting Matrix:

• Condition Records: VK03/VK13 - Check if pricing records exist

• Pricing Procedure: V/08 - Verify customer/document pricing procedure

• Access Sequence: Check field combinations in access sequence

• Validity Dates: Ensure condition records are valid for order date

• Scale Basis: Verify minimum quantity requirements

• Customer Hierarchy: Check if using customer hierarchy pricing

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
• Material Pricing Group: Verify material master pricing reference

Debug Technique:

Use VA02 → Conditions → Analysis to see exactly why pricing conditions are not being determined. This
shows the system's search strategy.

5. A customer is asking for a special discount. How do you configure this without affecting other
customers?

Customer-Specific Discount Configuration:

• Create Condition Record: VK01 - Use customer-specific condition type (e.g., K004, K005)

• Validity Period: Set specific start and end dates for the discount

• Scale Types: Configure quantity or value-based scales if needed

• Exclusion Groups: Use exclusion to prevent stacking with other discounts

• Customer Hierarchy: If applicable, set at appropriate hierarchy level

• Material Group: Restrict to specific material groups if required

• Sales Area: Limit to specific sales organization/distribution channel

Best Practice:

Always use customer-material or customer-specific condition types to ensure isolation. Document the
business justification and set appropriate validity periods.

Process & Workflow Issues

6. You notice that a delivery is blocked due to credit check. What are your steps to investigate and
resolve it?

Credit Management Resolution Process:

• Check Credit Exposure: FD32 - Review customer credit limit and exposure

• Credit Management Overview: VKM1 - Analyze blocked documents

• Customer Credit Master: FD03 - Check credit limit and risk category

• Release Blocked Documents: VKM2 - Release if approved by credit team

• Credit Control Area: Verify proper assignment and settings

• Automatic Credit Control: OB45 - Check configuration

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
• Document Updates: Coordinate with finance team for credit limit adjustments

Coordination Point:

Always involve the credit/finance team before releasing credit-blocked documents. Document the
business justification for any manual releases.

7. A sales order is incomplete. How do you identify and fix the incomplete data?

Incompletion Analysis & Resolution:

• Incompletion Log: VA02 → Environment → Incompletion Log

• Incompletion Procedure: OVA2 - Check which fields are mandatory

• Status Profile: Verify document type configuration for incompletion

• Field Dependencies: Check if certain field combinations trigger incompletion

• Master Data Issues: Verify customer/material master completeness

• User Authorization: Ensure user has access to complete missing fields

• Workflow Integration: Check if incompletion triggers workflow notifications

Resolution Strategy:

Address incomplete data systematically by priority. Some fields may require master data updates, while
others need immediate order amendments.

8. A business user wants to automate PDF invoices via email. What output type configuration would
you use?

Output Type Configuration for Automated Email:

• Output Type: NACE - Configure billing output type (e.g., RD00)

• Processing Routine: Set to external send (e.g., RSNAST00)

• Print Program: Use appropriate invoice print program

• Form/Layout: Configure PDF form (Smart Forms/Adobe Forms)

• Transmission Medium: Set to 5 (External Send) for email

• Email Settings: Configure SCOT (SAPconnect) for email delivery

• Condition Records: VV21 - Create output condition records

• Customer Master: Ensure email addresses are maintained

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
Technical Requirements:

Coordinate with BASIS team for SCOT configuration and email server setup. Test with sample customers
before rolling out to production.

Configuration & Business Requirements

9. The business wants different pricing for the same product in two distribution channels. How do you
set it up?

Distribution Channel-Specific Pricing Setup:

• Condition Tables: Create/use tables with distribution channel field

• Access Sequence: Configure sequence to check distribution channel

• Condition Type: Modify or create condition type with distribution channel dependency

• Pricing Procedure: Ensure procedure accommodates distribution channel pricing

• Condition Records: VK01 - Create separate records for each distribution channel

• Material Master: Verify material is extended to both distribution channels

• Customer Master: Check customer assignment to distribution channels

Configuration Tip:

Use condition table 005 (Material + Distribution Channel) or create custom table if needed. This ensures
clean separation of pricing by channel.

10. A client needs a return order process. How would you map this in SAP SD?

Return Order Process Configuration:

• Sales Document Type: VOV8 - Configure return order type (e.g., RE)

• Item Categories: Set up return item categories with proper controls

• Copy Control: VTAA - Configure copy control from standard order to return

• Pricing: Set up return pricing procedure (usually negative pricing)

• Account Determination: Configure revenue account determination for returns

• Movement Types: Set up goods receipt movement types (e.g., 161)

• Return Reasons: Configure reason codes for returns tracking

• Workflow: Set up approval workflow if required

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
Process Flow:

Typical flow: Return Order → Return Delivery → Goods Receipt → Return Credit Memo. Ensure proper
integration with QM module for quality inspection if needed.

Data Correction & Support Scenarios

11. A delivery is already posted but the quantity was incorrect. What are your options to fix it?

Post-Delivery Quantity Correction Options:

• Reversal Options: Check if goods issue can be reversed (VL09)

• Additional Delivery: Create subsequent delivery for remaining quantity

• Return Process: If over-delivered, create return delivery

• Inventory Adjustments: Coordinate with warehouse for physical adjustments

• Billing Implications: Check if billing document needs adjustment

• Stock Transport: Use stock transport if goods need relocation

• Documentation: Maintain proper audit trail for all corrections

Best Practice:

If goods issue is not posted, you can still change delivery quantity. If posted, reversal followed by new
delivery is cleanest approach.

12. The client wants to track order acknowledgment. How would you handle it?

Order Acknowledgment Configuration:

• Output Type: NACE - Configure order acknowledgment output (BA00)

• Processing Time: Set to immediate or periodic processing

• Form Assignment: Configure acknowledgment form/template

• Condition Records: VV01 - Set up automatic output determination

• Status Tracking: Use user status or system status for tracking

• Email Integration: Set up automatic email acknowledgments

• Customer Requirements: Include specific fields as per business needs

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE

Tracking Method:

Integration & Cross-Functional Issues

13. An intercompany invoice isn't generating. Where do you start debugging?

Intercompany Invoice Troubleshooting:

• Intercompany Setup: VK01 - Check intercompany customer/vendor setup

• Document Flow: VA03 - Verify intercompany sales order creation

• Billing Due List: VF04 - Check if intercompany billing is due

• Copy Control: Verify delivery to billing copy control settings

• Account Assignment: Check intercompany account determination

• Company Code Settings: Verify cross-company code configuration

• Pricing: Ensure intercompany pricing procedure is correctly assigned

Common Issue:

Most problems are in customer/vendor intercompany relationships (XD03/XK03) or missing

intercompany billing type configuration.

14. Sales orders are getting duplicated due to system lag. How do you prevent this?

Duplicate Order Prevention Strategy:

• Number Range Settings: VN01 - Ensure proper number range buffer settings

• User Training: Educate users not to click multiple times during processing

• Performance Analysis: Work with BASIS to identify system performance issues

• Background Processing: Consider batch processing for bulk orders

• Duplicate Check: Implement custom validation or user exit

• Session Management: Configure proper session timeouts

• Monitoring: Set up monitoring for duplicate document detection

Technical Solution:

Implement user exit in sales order creation to check for recent duplicates based on customer, material,
and timestamp within a defined window.

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
Advanced Configuration Scenarios

15. You're asked to configure a new sales document type for sample products. What factors will you
consider?

Sample Order Document Type Configuration:

• Document Category: Set to 'C' for standard sales order

• Pricing: Usually no pricing for sample orders

• Credit Management: Typically exclude from credit checks

• Billing Relevance: May not be billing relevant

• Item Categories: Configure special item categories for samples

• Copy Control: Set up copy control for delivery creation

• Number Range: Assign specific number range for samples

• Incompletion: Define mandatory fields specific to samples

• Status Profile: Configure appropriate status management

Business Consideration:

Consider approval workflow for sample orders, quantity limitations, and integration with inventory
management for sample stock tracking.

16. The delivery team says products are not reserved. What could be wrong in the availability check
settings?

Availability Check Configuration Review:

• Checking Group: OVZ9 - Verify material checking group assignment

• Checking Rule: OVZ2 - Review availability checking rule configuration

• Scope of Check: Ensure proper scope (stock, inward/outward movements)

• Requirements Class: Check item category requirements class for availability

• ATP Logic: OMI1 - Review ATP (Available to Promise) settings

• Plant Settings: Verify plant-specific availability settings

• Storage Location: Check if specific storage locations are configured

Quick Check:

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
Use MD04 to check stock overview and CO09 to see ATP quantities. Verify if requirements are being
transferred to MM.

17. A rebate agreement is not calculating correctly. What areas will you check in pricing configuration?

Rebate Configuration Troubleshooting:

• Rebate Agreement: VBO1/VBO2 - Check agreement validity and conditions

• Condition Type: Verify rebate condition type configuration (scale, calculation)

• Accrual/Settlement: Check if accruals are being posted correctly

• Material Rebate Group: Verify material master rebate group assignment

• Customer Rebate Group: Check customer master rebate classification

• Pricing Procedure: Ensure rebate condition types are in correct sequence

• Account Determination: Verify G/L account assignment for rebate accruals

• Settlement Process: VF42 - Check rebate settlement configuration

Validation:

Use VBO6 to simulate rebate calculations and VB(7 to check rebate index for transaction data
verification.

Master Data & System Integration

18. A customer master was updated, but the changes aren't reflecting in the order. Why?

Customer Master Data Propagation Issues:

• Buffer Refresh: Customer master changes may need buffer refresh

• Sales Area Extension: Check if customer is extended to proper sales areas

• Field-Specific Propagation: Some fields only update in new documents

• Change Documents: XD04 - Verify changes were actually saved

• Authorization Issues: Check if user had proper authorization for changes

• Lock Objects: Customer master might have been locked during update

• Workflow Dependencies: Some changes might require approval workflow

Resolution:

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
For existing orders, you may need to manually update relevant fields. New orders should automatically
pick up the changes after buffer refresh.

19. Client complains of wrong G/L account during billing. How do you trace account determination?

Account Determination Analysis:

• Account Assignment: VKA1 - Check revenue account determination

• Condition Type Settings: V/06 - Verify G/L account assignment to condition types

• Account Keys: VKOA - Check account key assignments

• Material Account Assignment: MM03 - Check account assignment group in material master

• Customer Account Assignment: XD03 - Verify customer account assignment group

• Account Determination Trace: Use debug mode in billing to trace account determination

• Plant-Specific Settings: Check if plant has specific account assignments

• Valuation Class: Verify material valuation class impacts account determination

Tracing Method:

Use VF01 in debug mode or check table VKOA for the combination of account assignment groups to
identify which G/L account should be picked.

Support Operations & Communication

20. How do you support users during month-end closing where billing volume is high and issues are
frequent?

Month-End Support Strategy:

• Proactive Monitoring: Set up monitoring for billing due list and error documents

• Issue Categorization: Classify issues by priority (P1-Critical, P2-High, P3-Medium)

• War Room Setup: Establish dedicated communication channels for month-end

• Batch Processing: VF04 - Use collective billing for efficiency

• Error Resolution: VF05 - Monitor and resolve billing errors promptly

• Extended Support Hours: Provide coverage during critical processing windows

• Documentation: Maintain real-time issue tracking and resolution log

• Escalation Matrix: Clear escalation path for complex issues

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
Best Practice:

Prepare standard resolution documents for common month-end issues. Coordinate with BASIS team for
system performance monitoring during high-volume processing.

21. What would you do if the goods issue was posted accidentally for the wrong quantity?

Goods Issue Correction Process:

• Impact Assessment: Check if billing document is already created

• Reversal Option: VL09 - Attempt to reverse goods issue if possible

• Material Document: MB03 - Check material document for reversal possibility

• Stock Verification: MMBE - Verify current stock levels

• Billing Impact: If billed, coordinate billing document correction

• Physical Inventory: May require physical stock adjustment

• Documentation: Maintain proper audit trail for all corrections

• Process Improvement: Analyze root cause to prevent recurrence

Resolution Path:

If reversal is not possible, use movement type 102 (goods receipt for sales order) to correct the stock,
then process correctly. Always involve warehouse team.

22. How would you configure and test third-party sales where delivery is done by a vendor?

Third-Party Sales Configuration:

• Item Category: Configure TAS (Third-party sales) item category

• Schedule Line Category: Set up schedule line for third-party procurement

• Copy Control: Configure sales order to purchase requisition copy control

• Account Assignment: Set up special G/L account determination

• Vendor Master: Ensure vendor is set up for direct delivery

• Purchase Info Records: Maintain purchase info records for materials

• Delivery Address: Configure customer address transfer to PO

• Invoice Verification: Set up three-way match (PO, goods receipt, invoice)

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
Testing Scenario:

Create sales order → Check purchase requisition creation → Convert to PO → Goods receipt at customer
→ Invoice verification → Customer billing. Verify document flow at each step.

23. How do you communicate a complex configuration change to a non-technical stakeholder?

Technical Communication Strategy:

• Business Impact Focus: Explain what the change means for their daily operations

• Before/After Scenarios: Show clear examples of current vs. future state

• Visual Documentation: Use screenshots, flowcharts, and process diagrams

• User Story Format: "As a [user], I will be able to [function] so that [benefit]"

• Risk Mitigation: Address potential concerns and mitigation strategies

• Training Requirements: Outline any user training or process changes needed

• Implementation Timeline: Provide clear timeline with key milestones

• Success Metrics: Define how success will be measured

Communication Best Practice:

Always follow up written communication with a discussion session. Use analogies from their business
domain to explain technical concepts.

Reporting & Analysis

24. A business wants a report showing all open sales orders by division. What steps would you take?

Report Development Approach:

• Requirement Analysis: Define "open" (not delivered, not billed, or specific status)

• Data Source: Identify tables (VBAK, VBAP, VBUK, VBUP)

• Standard Reports: VA05 - Check if standard reports meet requirements

• SAP Query: SQ01 - Create functional area query if needed

• Custom Report: Develop ABAP report if complex logic required

• Authorization: Ensure proper data access controls

• Performance: Consider database performance for large datasets

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE
• Distribution: Set up automated report distribution if needed

Quick Solution:

Start with VA05N (Sales Order List) with division selection. If more complex, use SE16 to analyze data
structure before building custom solution.

25. How do you coordinate with the MM or FI team when you know the issue is cross-functional?

Cross-Functional Issue Management:

• Issue Documentation: Create detailed problem statement with evidence

• Data Collection: Gather relevant documents, error messages, and screenshots

• Impact Analysis: Clearly define business impact and urgency

• Joint Analysis Session: Schedule collaborative troubleshooting session

• Responsibility Matrix: Define clear ownership for different aspects

• Communication Plan: Establish regular update schedule with stakeholders

• Testing Coordination: Plan joint testing of solutions

• Knowledge Transfer: Document resolution for future reference

Collaboration Success:

Use shared documentation tools and maintain transparent communication. Always involve business
users in solution validation to ensure all requirements are met.

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com

 Sample Interview QA FOR PRACTICE

Interview Preparation Tips

Additional Interview Success Tips

Technical Preparation:

• Hands-on Practice: Practice these scenarios in a sandbox system

• T-Code Mastery: Memorize key transaction codes and their purposes

• Integration Knowledge: Understand SD integration with MM, FI, PP, and WM

• Configuration vs. Customization: Know when to configure vs. when to develop

Behavioral Aspects:

• Problem-Solving Approach: Always explain your systematic troubleshooting methodology

• Communication Skills: Demonstrate ability to explain technical concepts simply

• User Focus: Show understanding of business impact in technical decisions

• Continuous Learning: Discuss how you stay updated with SAP developments

Common Follow-up Questions:

• "How would you handle this if you couldn't resolve it immediately?"

• "What would you do if the business user disagreed with your technical solution?"

• "How do you prioritize multiple critical issues during peak business hours?"

• "Describe a challenging SD issue you resolved and what you learned from it."

https://www.linkedin.com/in/pawan-kumar001 Contact no: 9693439957 Email Id: krish.pwnkmr0001@gmail.com