Files that are exported from HansaWorld with standard routines can be used for flex.bi data import. This type of file import can be used as a supplementary import for REST API import or an alternative to REST API import in case REST API import is not available.

Files export and import to flex.bi is a manual work for each register and to automate this process with files it requires a specific HAL package setup and automatic file transfer setup to flex.bi server. Therefore it's always recommended to use REST API option for flex.bi data imports.

Export register files from HansaWorld

To export All Register content

Use this option to export all register content, for example - all Invoices, by typing technical name of it " IVVc" in if Register export

Go to Module Database maintenance
Open Routines > Exports > Register exports
Type in the Technical name of register, for example, try exporting Customers - CUVc . Press Ok. See the list below for Technical name s of registers.
Save file and use the technical name as a filename, to make it easier to recognise the content afterwards. Example: IVVc.txt , CUVc.txt

Important: Save files under the technical name of register and period. Each register has to be exported and saved in file separately.

To export register for period (Only Transaction registers)

Go to Module Integration.
Open Routines > Exports > Transaction registers (period)
Choose from the list of transaction registers ( choose one each time). Press Ok
Save file under the technical name of register.

Note : Each register has to be exported and saved in file separately.

How does it work?

You decide which HansaWorld Modules data you would like to see in flex.bi, export files in HansaWorld standard format (*txt), afterwards you go to flex.bi and upload them and setup Hansaworld Import application. flex.bi will create Data Cubes for Each Hansaworld module data automatically based on files you upload and Import.

Keep in mind that HansaWorld Module = Data cube in flex.bi language.

List of HansaWorld Files Supported

* ESSENTIAL to create corresponding Data Cube correctly
** DYNAMIC you have to choose which Object or Classification types must be imported in HansaWorld Source Application

HANSAWORLD INVOICES DATA CUBE Based on Sales Ledger module and Invoices data	Base currency setting - BaseCurBlock * Invoices - IVVc * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Persons - UserVc (Sales Person) * Item Groups - ITVc * Invoice Balances - ARVc / Measures Dimension Location - LocationVc Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc Location types - LocClTypeVc ** Location classes - LocCLVc Routes - DelRouteVc VAT codes - VATCodeBlock
HANSAWORLD FINANCIALS DATA CUBE Based on General Ledger module and Transactions data	Transactions - TRVc* Simulations - SMVc Accounts - AccVc* Object Class - OTVc (Object Types) ** Objects - ObjVc * VAT codes - VATCodeBlock Companies - CompaniesBlock
DO NOT FORGET TO PRESS IMPORT FOR FLEX.BI HANSAWORLD APPLICATION AFTER FILE UPLOAD Have a question ? Contact us
HANSAWORLD POS DATA CUBE Based on Point of Sales module and POS Invoices data	Base currency setting - BaseCurBlock * POS Invoices - IVCashVc * Local Machines - LocalMachineVc Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Persons - UserVc (Sales Person) * Item Groups - ITVc * Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc VAT codes - VATCodeBlock
HANSAWORLD QUOTATIONS DATA CUBE Based on Quotations module and Quotations data	Quotations - QtVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc Routes - DelRouteVc
HANSAWORLD CRM DATA CUBE Based on CRM module and Activities data	Activities - ActVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Accounts - AccVc Activity Types - ActTypeVc * Projects - PRVc * Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Classification types - CTypeVc Item Class - DIVc (Item Classifications) **
HANSAWORLD SALES ORDERS DATA CUBE Based on Sales Orders module and Sales Orders data	Sales Orders - ORVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Location - LocationVc Location types - LocClTypeVc Location classes - LocCLVc Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc ** Routes - DelRouteVc VAT codes - VATCodeBlock
HANSAWORLD PURCHASE ORDERS DATA CUBE Based on Purchase Orders module and Purchase Orders data	Purchase Orders - POVc * Base currency setting - BaseCurBlock * Projects - PRVc * Persons - UserVc * VAT codes - VATCodeBlock Object Class - OTVc (Object Types) ** Objects - ObjVc Classification types - CTypeVc Supplier categories - VGVc Customer categories - CCatVc * Customer Class - CCLassVc (Contact Classifications) ** Customers - CUVc (Contacts) * Item Class - DIVc (Item Classifications) ** Item Groups - ITVc * Item varieties - VARVc Item variety groups - VARGVc ** Items - INVc * Location types - LocClTypeVc ** Location classes - LocCLVc Location - LocationVc Units of measure - UnitVc
HANSAWORLD PURCHASE INVOICES DATA CUBE Based on Purchase Ledger module and Purchase Invoices data	Purchase Invoices - VIVc * Base currency setting - BaseCurBlock * Purchase Invoice Balances - APVc / Measures Dimension Persons - UserVc (Sales Person) * Projects - PRVc * VAT codes - VATCodeBlock Accounts - AccVc* Object Class - OTVc (Object Types) ** Objects - ObjVc Classification types - CTypeVc Supplier categories - VGVc Customer categories - CCatVc * Customer Class - CCLassVc (Contact Classifications) ** Customers - CUVc (Contacts) * Item Class - DIVc (Item Classifications) ** Item Groups - ITVc * Item varieties - VARVc Item variety groups - VARGVc ** Items - INVc * Units of measure - UnitVc
HANSAWORLD JOB COSTING DATA CUBE Based on Job Costing module and Project budget data	Project budget - TBBUVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Activity Types - ActTypeVc Projects - PRVc * Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Classification types - CTypeVc Item Class - DIVc (Item Classifications) **
HANSAWORLD STOCK DATA CUBE HANSAWORLD GOODS RECEIPTS DATA CUBE HANSAWORLD STOCK DEPRECIATION DATA CUBE HANSAWORLD STOCK MOVEMENTS DATA CUBE HANSAWORLD DELIVERIES DATA CUBE Stock module in HansaWorld has 5 transaction registers. flex.bi supports them all in a seperate data cubes. As we also have shared measures - data from Goods received will be available in also in Stock cube, and for example.	HANSAWORLD STOCK DATA CUBE Item Status - ItemStatusVc * Item History - ItemHistVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Location - LocationVc Location types - LocClTypeVc Location classes - LocCLVc Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc **
	HANSAWORLD GOODS RECEIPTS DATA CUBE Goods Receipts - PUVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Location - LocationVc Location types - LocClTypeVc Location classes - LocCLVc Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc ** VAT codes - VATCodeBlock Supplier categories - VGVc
	HANSAWORLD STOCK DEPRECIATION DATA CUBE Stock Depreciation - SDVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Location - LocationVc Location types - LocClTypeVc Location classes - LocCLVc Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc ** Standard Problems - StandProblemVc
	HANSAWORLD STOCK MOVEMENTS DATA CUBE Stock Movements - StockMovVc * Base currency setting - BaseCurBlock * Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Location - LocationVc Location types - LocClTypeVc Location classes - LocCLVc Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc ** Routes - DelRouteVc
	HANSAWORLD DELIVERIES DATA CUBE Deliveries - SHVc * Base currency setting - BaseCurBlock * Accounts - AccVc* Customers - CUVc (Contacts) * Customer categories - CCatVc * Items - INVc * Item Groups - ITVc * Persons - UserVc (Sales Person) * Location - LocationVc Location types - LocClTypeVc Location classes - LocCLVc Object Class - OTVc (Object Types) Objects - ObjVc Customer Class - CCLassVc (Contact Classifications) Item Class - DIVc (Item Classifications) Classification types - CTypeVc Item varieties - VARVc Item variety groups - VARGVc **

Standard ERP

If you do not see this module in the list of modules you have to add it to the user account in System > Settings > Access Groups.

To find which Access group you have access rights from, you have to look in System > Register > Persons by opening your personal record.

HansaWorld Books 6.3

For HansaWorld Books 6.3 to export registers you have to go to the System module and for:

AcVc - System data/Accounts
AccVc - Registers (period)
To export Objects - please contact your partner

EXAMPLE

To create report " Item Statistics By Customer And Object" you have to export data from Sales ledger module that builds Invoices Data cube in flex.bi and is based on Invoice data. According to list, you have to export :

Base currency setting ( BaseCurBlock)
Invoices, (IVVc)
Items (Invc)
Customers (CUVc)
Customer categories (CCatVc)
Contacts (UserVc),
Object types (OTVc)
Objects ( ObjVc).
You can also export Item Classifications (DIVc) if you think you might need them in reports somewhere. But you can add them also later.

Transactions - Trvc
Objects - OTVc
Object Types - ObjVc
Accounts - ActVc

Keep in mind that HansaWorld Module = Data cube in flex.bi language.

Upload register files to flex.bi

a) For automated exports / imports with HAL

If you are using automated exports / import where files are sent to server by HAL package timed events, you do not have to upload files - they will show in Source files section automatically, just check if they show up in Source files and are recognized as HansaWorld format.

b) For manual file export / import

In the flex.bi interface you have to find the tab Source Data > Source Files and upload the register files you prepared previously. If files after upload are recognized as HansaWorld files then you will see the HansaWorld logo appear under each file name. Result table should look like this or similar:

If your file is not recognized as a HansaWorld file then:

Make sure the file contains any data at all.
Try to re-export the data from HansaWorld again and allow some time for the new file to be populated with data, because exporting big files (several megabytes) can cause the files to appear as empty while they are being populated by data

Automate exports with HAL (Optional)

Requirements

HAL License
Customized halcust/hobcust files

For HAL license owners we provide HAL code package that configures automatic exports for chosen data and period. Please contact us or your local Hansaworld partner for more info.

The Process

Add the halcust/hobcust package to your server
(this should be done by the administrator or the programmer)
(Optional) - Create package keys
Add additional hal rules
After adding Hal rules make sure to restart your StandardERP (HansaWorld) client.
Go to Technics - Settings - Timed Operations
- Add the funcition burti_TimedEvents to background tasks and 90 seconds to run:
Go to System - Settings - Timed events and add the functionality you want to execute.
The provided timed events and export packaged can differ from the standard functionality provided from StandardERP (or HansaWorld) by letting you execute multiple events and defining automated export paths.
- (Optional) - Sample Timed Events register TimedEventVc.txt. Contact us or your local flex.bi consultants, if you need help with customising the register for your needs.
Editing Timed Events
There are two types of export events - "Full register export" and "Customized register export". The first should usually be used only daily/weekly/monthly preferably during off-times. The second (customized) - should be used for exports you need much more often, e.g. - exporting every 10 minutes any transactions made during current day.
1. ExportEverythingEn - full export
  1. Fill in the standard fields as needed (Select Maintenance as routine type)
  2. In the matrix add three lines
    1. AccStr - "Register Code"
    2. ObjStr - "Destination"
    3. Media - 2
    4. Use this export for bigger files which could affect your systems workload
2. ExportPartialEn - customized export
  1. Fill in the standard fields as needed (Select Maintenance as routine type)
  2. In the matrix add 6 (or less) lines
    1. flags[0]:
      0 - filename.extension
      1 - filename_register_datetime.extension
      2 - filename_monthyear.extension
      3 - filename_month_year.extension (Recommended)
    2. ArtMode - 0 to 15
      0 - NL Transactions, 1 - Sales Invoices etc., 13 - Quotations, 14 - Item History, 15 - POS Invoices
    3. ObjStr - "Destination"
    4. sStartDate - "Starting date" - can be used with hal language date functions (CurMonthStart , Date etc.)
    5. sEndDate - "Ending date" - can be used with hal language date functions
    6. Media - 2
    This will export your files to requested destination path.
3. Partial export for previous month (ExportPartialEn)
  If you want to replace data of previous month, you can do it with Timed Events as well. In this case you have to add 2 more lines.
  1. Fill in the standard fields as needed (Select Maintenance as routine type)
  2. In the matrix add 8 lines
    1. flags[0]:
      0 - filename.extension
      1 - filename_register_datetime.extension
      2 - filename_month_year.extension
      3 - filename_monthyear.extension (Recommended)
    2. ArtMode - 0 to 15
      0 - NL Transactions, 1 - Sales Invoices etc., 13 - Quotations, 14 - Item History, 15 - POS Invoices
    3. ObjStr - "Destination"
    4. $AdjMonth - set the month adjacent to current month (-1 for previous month, -2 for two month ago etc.)
    5. sStartDate - AdjMonthStart - Start of the adjacent month
    6. $AdjMonth - set the month adjacent to current month (-1 for previous month, -2 for two month ago etc.)
    7. sEndDate - AdjMonthEnd - End of the adjacent month
    8. Media - 2

Browser not supported