Create a New Demo in Seed
( Just starting to collect ideas here. )
Over the years, a static seed database is proving to be problematic. The dates of transactions are a decade old, the calendar periods are closed and the data does not represent all the functionality of the application. To fix this, the database requires a seed that can be updated to the current year and modified to suit the changes to the application. It is proposed that this seed be created in testing the application automatically. Essentially, GardenWorld will be built from scratch at each release by the test process.
- Tables of seed data will be created to drive test software that will perform the setup, create opening documents and a series of transactions similar to creating a new client. This will generate an illustrative history with a number of documents in various stages of completion with reasonable date ranges. In creating this data, most major functions will be thoroughly tested.
- The database will be left in a state where workflows can be completed as part of tutorials for new users.
- 1 Setup Data
- 2 Document Data
The setup data is created to test and demonstrate the feature set of ADempiere.
- Multiple accounting schema (?)
- Multiple currencies
- USD, EUR
- Multiple languages
- English, Spanish
- Subordinate Organizations - a tree with summary organizations to show roll-ups of financial data
- Retail Division (summary)
- Bank accounts
- Cash Journals
- A larger list of Business Partners with groups within customers, vendors, employees/users, contractors. Included inactive entries.
- A variety of payment terms and credit limits
- A variety of contacts for each BP where the BP is a company. Use e-mail addresses, phone numbers
- A variety of locations. Some customers and vendors should have multiple locations, some just one.
- Multiple levels of tax, no tax, exempt tax, regional differences, etc
- Complex logistics with main warehouse and in-store warehouses, including in-transit
- Realistic locations within each warehouse
- Demo default/clearing locations within each
- Include parent categories. I.e. Seeds as parent of Vegetables, Flowers-Annual, Flowers-Perennial etc. for use in search and in reports
- Multiple product attributes (suggest seeds (sun, water, season, soil, nutrients, flower colour, etc...)
- Multiple instance attributes (fertilizer (lot and date))
- Multiple types of lots
- Product attributes (non-instance) (assign to seed products)
- Instance attributes (mandatory and not)
- A large selection of products
- Use attributes - both product and instances
- Include multi-level BOMs, summary products
- Make use of UPS and SKU codes
- Demonstrate different pricing schemes
- Demonstrate gift cards and promotions
Price List Schema
==Requisition to Invoice
... and so on.
It may be possible to use the Adaxa "Generate Test Data" process. This process lets you create as many orders as you want. If yyou create a set of 'on credit' orders it will generate orders, shipments and invoices. 'warehouse orders' will generate sales orders and customer shipments. A mixture of order types will create a variety of documents at all stages of completion that orders can have.