Every SAP Business One user eventually hits a problem that forums and colleagues cannot fix. Maybe a report throws an unexpected error. Maybe an add on stops syncing. Maybe month end closing starts acting strange right after an update.
When that happens, open an official support case. SAP and support teams call this an incident. It is the fastest way to get real help from SAP or your local partner. This guide walks you through the process step by step. You will learn what information to gather first, and how to write a case that gets resolved faster.
Why a Proper Support Case Matters
Many users treat support tickets as an afterthought. They type “system is broken” and hope someone else figures out the rest. This approach almost always backfires.
Support engineers handle dozens of incidents at once. The clearer your case, the sooner it gets picked up. Think of a support case like a doctor visit. The more accurately you describe your symptoms, the faster the diagnosis. SAP Business One incidents work the same way.
Who Can Open a Support Case
Your access depends on how your company purchased and manages SAP Business One.
If you run the on premise version with a direct SAP agreement, your authorized contacts can log into the SAP Support Portal. If you bought through a Value Added Reseller or local partner, which is common for small and mid sized businesses, you raise cases through their help desk instead. Your partner escalates to SAP only when the issue truly requires it.
Check with your IT administrator or partner account manager first. Submitting through the wrong channel adds unnecessary delays.
Before You Open the Case
Rushing straight into the ticket form feels tempting. But a few minutes of prep saves hours later.
Gather Your System Information
Collect these details before you start typing:
- Your SAP Business One version and patch level. Find this under Help then About in the client.
- Your database type, either SAP HANA or Microsoft SQL Server, plus its version.
- The exact module or window where the issue happens. Examples include Sales Order entry, Inventory Valuation, or the Payment Wizard.
- Any add ons or third party integrations involved. These often cause the real problem.
Reproduce the Issue
Try to recreate the problem at least once before logging the ticket. If you can reproduce it reliably, write down the exact clicks and fields you used.
If it happens randomly, note any pattern you notice. Maybe it only happens with invoices over ten thousand dollars. Maybe it started right after the last patch. Random bugs are harder to fix, but even a partial pattern gives engineers a head start.
Capture Screenshots and Error Messages
Never paraphrase an error message. SAP error codes are specific. A screenshot showing the exact wording, including any internal error numbers, is one of the most valuable things you can attach.
If a report or document looks wrong, export or screenshot the actual output. Let the support team see exactly what you see.
Step by Step: Creating the Support Case
Step 1: Log Into the Correct Support System
If you work directly with SAP, go to the SAP Support Portal or SAP for Me. This has become the unified entry point for support, licensing, and system information. Log in with your S user ID.
If you go through a partner, use their help desk portal or the contact method they gave you. This might be a web form, an email address, or a support line.
Step 2: Start a New Incident
Look for an option like Report an Incident, Create Case, or New Message. The exact wording depends on your interface version.
Select SAP Business One as the product area. If prompted, choose the correct installation or system ID. Larger companies often manage multiple SAP Business One databases, so this matters.
Step 3: Select the Correct Component
This step matters more than most users realize. SAP routes tickets automatically based on the component you select. Choose the wrong one, and your case lands in the wrong queue. That adds days of delay.
Common Business One components include:
- Financials
- Sales and Purchasing
- Inventory and Warehouse Management
- Production
- Service and Administration
Not sure which one fits? Ask your partner, or search the SAP knowledge base. When in doubt, name the module clearly in your subject line so the team can redirect quickly.
Step 4: Write a Clear, Specific Subject Line
Skip vague subjects like “Error in system” or “Help needed urgently.” Get specific instead.
A subject like “Error 131 96 when adding AR Invoice with Withholding Tax” tells the reader exactly what to expect. A strong subject line also helps later, when you search your own ticket history.
Step 5: Describe the Issue in Detail
This is where your prep pays off. Cover what you were trying to do, what actually happened, the exact error message, and how to reproduce it.
Here is an example: “User was creating a new AR Invoice for customer C001. After entering three line items and clicking Add, the system displayed error 131 96 Amount Invalid. This started after the latest patch was applied on the tenth of the month. It happens consistently with this customer but not with others.”
Notice how this example answers who, what, when, and how in just a few sentences.
Step 6: Attach Supporting Files
Upload screenshots, error logs, and any sample document or transaction number. Include reference numbers for the affected business partner, item, or document. This saves the engineer an extra question.
For database issues, your partner may also request a backup or log file. Keep those ready in case they ask.
Step 7: Set the Priority Correctly
Most portals ask you to classify urgency, often as Low, Medium, High, or Very High. Be honest here.
If your company cannot process invoices and revenue stalls, that is genuinely high priority. If a report looks slightly misaligned but does not block daily work, that is lower priority. Marking every ticket as urgent does not speed things up. It actually trains the system to deprioritize your future high priority cases, since your history shows inflated severity.
Step 8: Submit and Save Your Case Number
Once you submit, you will receive a case or incident number. Save it somewhere accessible. You will need it for follow up calls, emails, or status checks.
Working through a partner? Ask them for the official SAP incident number too. This gives you full visibility, especially on issues that take several days to resolve.
What Happens After You Submit
Your case moves through a few stages after you submit it.
First, the system triages and assigns it to an engineer based on component and priority. The engineer then reviews your description and attachments. They may ask for more information, or request remote access to your system. For deeper issues, they might connect through a remote session tool to see the problem firsthand.
Once they identify the cause, you get a workaround, a configuration change, a patch recommendation, or a note explaining that the behavior works as designed. Confirmed bugs get logged for a future patch, and SAP notifies you when that patch becomes available.
Tips to Get Faster Resolutions
- Respond quickly when the engineer asks follow up questions. Slow replies reset the queue priority and stall the case.
- Keep communication inside the ticket. Side channels like phone calls do not create an official record, and that record matters for accountability.
- Avoid bundling unrelated issues into one case. Open separate tickets instead. Combining issues confuses root cause analysis and slows down every fix.
- Check the SAP knowledge base before submitting. Many common Business One errors already have documented fixes, and you might solve it yourself in minutes.
Common Mistakes to Avoid
Skipping the version and patch level is the most frequent oversight. The engineer will almost always ask for it before doing anything else.
Describing the symptom instead of the actual behavior causes problems too. Saying “the system is slow” tells the engineer nothing. Name the screen, the action, and how slow compares to normal.
Finally, test after applying a fix before you close the case. Users who skip this step often reopen the same ticket days later, when the issue resurfaces under slightly different conditions.
Working With Your Partner Versus Direct SAP Support
A certified partner usually serves as your first line of support. They escalate to SAP directly only when the issue needs deeper backend investigation, or when it looks like a genuine product defect rather than a configuration issue.
This layered model exists because your partner understands your specific business processes and customizations. SAP’s general support team does not have that visibility. Keep your partner in the loop, even for issues you think you can raise directly. It usually leads to faster, more context aware support.
Final Thoughts
Creating a support case for SAP Business One does not need to feel intimidating once you understand the structure.
Preparation makes the difference. Know your version, reproduce the issue, capture the exact error, and describe the situation clearly. This habit gets your current issue resolved faster. It also builds a track record that support teams trust, and that pays off the next time something unexpected happens in your system.
