Transport Demo Data

This companion module builds a complete Arabic transport scenario on top of the transport module so it can be demonstrated or tested without typing data. It creates master data, dispatch orders and trips, treasury and driver advances, broker bills and settlements, using the real business logic of the transport module. It is for test databases only and must never be installed in production. It helps trainers and testers see the whole cycle from loading to settlement in minutes.

1. 1

   Install on a test database

   The tester installs the demo module after the transport module, and only on a test database. Installation runs a hook that builds everything. The module depends on Accounting, Fleet and the chatter.

   • Test databases only
   • Runs after installation
   • Needs transport, accounting, fleet
2. 2

   Master data is built

   The builder creates locations, routes, goods categories, vehicles, contractors, brokers, drivers and customers with Arabic names. It also sets tariffs so pricing works out of the box. Names are demo values.

   • Arabic demo names
   • Tariffs configured
   • Ready for pricing
3. 3

   Operations are created

   The operations builder creates dispatch orders and trips and moves them through loading, transit, delivery and review. It uses the module's own actions so the numbers are real. Trips with shortage and different vehicle ownerships are included.

   • Dispatch orders and trips
   • Uses real module actions
   • Includes shortage cases
4. 4

   Money flows are posted

   The money builder creates treasury moves, driver advances, broker bills and settlements and posts the accounting entries. The dashboards and reports therefore show real figures. A savepoint protects the run so a failure does not leave half-built data.

   • Treasury, advances, broker bills
   • Accounting entries posted
   • Savepoint protects the run
5. 5

   Explore and remove

   The trainer walks through menus, statements and the dashboard with the demo data. When finished the module is uninstalled on the test database. It must not be installed on production.

   • Use for training
   • Uninstall after testing
   • Never on production

Back to version applications