Preparing an SAP question: 20 examples and a checklist

A short template for a useful SAP question

This resource is not a human consulting service or a list of verified fixes. Adapt questions to your version and role. The examples use no actual customer data.

Goal:
SAP product / version / module (say if unknown):
Transaction or application:
Expected result:
Observed result:
Redacted error text:
Reproduction steps:
Safe checks already attempted:
Requested output: explanation / questions / investigation steps
Ask for missing details first. Separate steps requiring verification before any change.

20 starter questions

These are copyable test scenario questions, not Digital SAP Consultant answers or customer success stories.

1. I know my SAP version and module. What context should I provide before investigating a question?
2. I only have redacted error text. What missing details should you ask for without making assumptions?
3. How can I turn expected versus observed behaviour into a concise SAP support ticket?
4. Which parts of your proposed solution are verified information and which are assumptions? Separate them.
5. Explain document date versus posting date in SAP FI and identify version-dependent points.
6. Which organisational and date details matter in an FI period-close question? Avoid requesting sensitive data.
7. Prepare non-mutating investigation questions for a user reviewing an FI document.
8. Explain the relationship between a purchase order and goods receipt in SAP MM without assuming company configuration.
9. What information should I collect to investigate quantity differences across order, goods receipt and invoice?
10. Write an MM error-report template using placeholders instead of real document numbers.
11. Explain the conceptual document flow between sales order, delivery and invoice in SAP SD.
12. What context matters for an SD pricing question? Do not request actual customer or pricing data.
13. How can I describe a delivery question separately to a business user and a technical team?
14. Prepare an ABAP investigation template for version, redacted error text and reproduction steps.
15. Write a checklist for reviewing an ABAP code suggestion for security and version compatibility.
16. How should I check whether a suggested SAP Note exists and applies to my situation?
17. Suggest five questions to clarify requirements before a consulting meeting, without jumping to solutions.
18. What information should I collect before escalating to the internal SAP team?
19. What should a test, authorisation and rollback plan include before a proposed production change?
20. List circumstances where this answer might be incomplete and steps to verify it against reliable sources.

Answer verification checklist

• Are SAP version, module and process assumptions explicit?
• Does the answer address the error text and observed behaviour?
• Does a suggested SAP Note or source exist and apply to your version?
• Is a check read-only or a change? Do you have the required authorisation?
• Does the material contain sensitive data, credentials or unnecessary client information?
• For a change, are testing, approval and rollback steps ready?
• Is uncertainty clear, and has the issue been escalated to an authorised expert when needed?

Next step

Digital SAP Consultant scope and access terms. No registration is needed for this resource. Product applications are accepted only while the campaign is open and require a work email address.