Use this option to export all register content, for example - all Invoices, by typing technical name of it " IVVc" in if Register export
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.
Save file under the technical name of register.
Note : Each register has to be exported and saved in file separately.
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. |
* to create corresponding Data Cube correctly
** you have to choose which Object or Classification types must be imported in HansaWorld Source Application
| |
| |
Have a question ? Contact us | |
| |
| |
| |
| |
| |
| |
| |
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. |
|
| |
| |
| |
|
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. |
For HansaWorld Books 6.3 to export registers you have to go to the System module and for:
|
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 :
Keep in mind that HansaWorld Module = Data cube in Flex.bi language. |
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. Then move to Source application section below.
If some of register files are missing, not recognized or empty, please go to - Automated export setup with flex.bi provided HAL package.
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 :
|
You can setup application in Source Data > Source Applications tab by selecting "Add new Source Application" button.
For more information about the cubes and dimensions visit the page on: What properties and measures are available for HansaWorld cubes?
If you want to import Extra dimensions (Object types, Customer classes, Item classes, Location classes, Item Varieties), click on section Extra Dimensions and select, which Extra Dimensions you need.
If your file is not recognized as a HansaWorld file then:
|
Go back to Source Application tab and press Import.
|
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. |
(this should be done by the administrator or the programmer)
(Sample - halrulesvc.txt). After adding Hal rules make sure to restart your StandardERP (HansaWorld) client.
Add the funcition burti_TimedEvents to background tasks and 90 seconds to run:
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.
Fill in the standard fields as needed (Select Maintenance as routine type)
In the matrix add three lines
AccStr - "Register Code"
ObjStr - "Destination"
Media - 2
Use this export for bigger files which could affect your systems workload
Fill in the standard fields as needed (Select Maintenance as routine type)
In the matrix add 6 (or less) lines
flags[0]:
0 - filename.extension
1 - filename_register_datetime.extension
2 - filename_monthyear.extension
3 - filename_month_year.extension (Recommended)
ArtMode - 0 to 15
0 - NL Transactions, 1 - Sales Invoices etc., 13 - Quotations, 14 - Item History, 15 - POS Invoices
ObjStr - "Destination"
sStartDate - "Starting date" - can be used with hal language date functions (CurMonthStart , Date etc.)
sEndDate - "Ending date" - can be used with hal language date functions
Media - 2
This will export your files to requested destination path.
flags[0]:
0 - filename.extension
1 - filename_register_datetime.extension
2 - filename_month_year.extension
3 - filename_monthyear.extension (Recommended)
ArtMode - 0 to 15
0 - NL Transactions, 1 - Sales Invoices etc., 13 - Quotations, 14 - Item History, 15 - POS Invoices
ObjStr - "Destination"
sStartDate - AdjMonthStart - Start of the adjacent month
sEndDate - AdjMonthEnd - End of the adjacent month
Media - 2