One Client copy English Company copy) is the duplication of a SAP Business One database – including master and transaction data, evidence, users, UDTs and UDOs — to another client. It is the central tool for supplying test systems, running upgrade samples, preparing migrations, or providing a demo system for training.
Context
Technically, a tenant copy is created by backing up and then restoring the DatabaseOn HANA HANA Cockpit → Backup → Data Recovery into a new tenant, on MS SQL via SQL Management Studio (Backup → Restore asinto a new Company DB. Subsequently, the new tenant must be registered in the SLD (for HANA) or in the Site User mode (for SQL); user passwords and license assignments will be reset. For test systems, an additional Anonymisation Sensible data: pseudonymise customer data, blank bank details, rename logins, deactivate email dispatch. Add-ons such as the Versino Financial Suite or Coresuite products often create registration entries per tenant, which also need to be adjusted after copying. For pure accounting tests, the tenant is sufficient – for complete scenarios including B1if integration and external web shops, interface endpoints must also be redirected so that test runs do not hit productive systems.
Demarcation
A client copy is not a backup in the sense of a disaster recovery strategy – it is a working duplicate. It also differs from a Test database by Site User → New, which creates an empty client; for meaningful tests, you need the actual data structures from production. And it does not replace a migration run from an old system: there, mapping, cleansing, and data loading are essential; a pure copy, on the other hand, takes over the existing data unchanged.
Why companies are hesitant about AI in ERP
Predictive maintenance: how to turn SMEs into smart factories
RPA in the ERP environment: increasing efficiency through digital process assistants
Generative AI in ERP: How LLMs are changing the role of ERP systems
Preparing the ERP future with APIs and microservices
