SAP Business One is a good ERP for a mid-sized company. The problems I have seen around it almost always come from the order in which it gets implemented. Teams start with screens and reports, which is what people see, and leave for later what holds everything up: the catalogs and the rules.
This is the order I recommend, especially when the ERP will live alongside other systems: a CRM, a sales app, a point of sale or an online store.
1. Decide which system owns each piece of data
Before entering the first item, write down who owns the customer, the price, the inventory and the payment. If the CRM creates customers and the ERP does too, you will have duplicates in the first week.
At J. García López we made a decision like this about preneed plan prices. The rule was split between the CRM and each manager's judgment, and we moved it into the ERP: SAP Business One now sets the final price and the CRM only checks the down payment and the discount cap. I told the whole story in before you automate, ask which system owns each piece of data.
2. Build catalogs with their consumers in mind
Items, groups, price lists, warehouses, business partners. Every catalog you create in SAP will be read by something else: an integration, a report, an app. It pays to design codes and groups with that consumer at the table.
We have seen what happens when that does not happen. In a CRM connected to SAP, new special price lists were created in the ERP, and the interface catalog that translated them for the CRM did not know about them. The CRM had no way to quote with them. The fix was to map each new list to a mirror list the interface did understand, and to write down that every new list goes through that map before anyone uses it.
3. Put business rules inside the system
Maximum discounts, approvals, credit terms, user-defined fields for what SAP does not ship with. Everything that lives today in an email or in someone's memory has to end up in the ERP or in the layer around it.
User-defined fields are useful and also dangerous. Name them so they still make sense two years from now, document what each one means and avoid creating two fields that say almost the same thing, because integrations will read the wrong one.
4. Design the integration to fail loudly
Integration is where the pain is, and the costliest errors are the ones that stay quiet.
A real case: a child document in SAP was not being created when the gift included in a contract was worth $0.00. SAP rejected the document, but the integration stored the result against a record that did not exist and the error was lost. Nobody knew until someone looked for that document and it was not there.
Since then we check three things in any SAP Business One integration: that every call to the Service Layer or the DI API stores its response, that an error triggers an alert someone actually reads, and that zero amounts have an explicit rule, because they are almost always a special case.
5. Reports and dashboards come last
With owners, catalogs, rules and integration in order, reports come out almost on their own and, more importantly, they match finance. Build them earlier and you end up rebuilding them every time one of the layers underneath changes.
About the timeline
I will not give you a number of weeks, because it depends on the size of the operation and how many systems sit around the ERP. What I will tell you is that the phase most often cut from budgets, deciding owners and designing catalogs, is the one that saves the most time later.
If you are about to implement SAP Business One, or already have it and the integration is giving you trouble, our SAP Business One integration page covers what we do. And tell me which of these five steps your company skipped; it is almost always the first one.