Tools : Initial Data Load

A set of automated data import processes to quickly load core ERP data into Openbravo, from a predefined spreadsheet.

Click here for information about buying commercial modules.

Benefits
Functionality
Specifications

Minimize time to migrate core ERP data

The Initial Data Load module provides a streamlined set of automated data import processes to quickly migrate core ERP data into a standard Openbravo ERP instance. It significantly eases the frustration of a notoriously difficult, mission-critical process—typically reducing the end-to-end data migration effort from weeks to days.

Enable end users to manage the process

All user interaction is through the browser, with no direct server access required—enabling the owners of the data to take direct ownership of the process, if desired. This allows Saas providers to empower customers to import their own data with minimal or no assistance.

Help ensure a trouble-free standard implementation

Using the Initial Data Load module results in a fully-integrated set of validated ERP data. This ensures that the system’s relational database will start with a “clean” dataset that is complete, and that will support all required transaction processing without errors due to missing or mis-aligned data.

Brought to you by:

Openbravo is the award-winning developer of Openbravo ERP—the leading web-based, commercial open source business management solution for SMBs worldwide.

To ensure data integrity and facilitate reporting and analysis, Openbravo ERP includes a robust relational database with referential integrity defined on the entities. Here are some of the core entities supported by the Initial Data Load module, and their relationships:

The Initial Data Load Module ensures that all relational constraints are met, and includes complete and detailed documentation to guide you through importing the entities, in the required sequence. Key Initial Data Load functionality includes:

Ability to establish a default value for any data element, minimizing front end “data cleaning” requirements
Ability to validate the external dataset prior to importing data
Clear, actionable error messages to tell you what is wrong with your dataset
A web service interface to enable automation of the processing
- for example, to support full "new-install-to-production-ready" test automation