Backward & Forward Integration
Many a times, users need to update their transactional data based on analysis results. This can be a case when budgets, estimates and plans are revised based on the actual data. Further it is possible that user desires to use ERPJewels as DTS (Data Transformation Service) and wish to have his/her client applications to load the analyses results. This can be a case in following cases.
1. Customer’s
live production server database is also OLAP services provider (like
SQL server /Oracle 9i )
2. Customer already has separate OLAP server and wishes
to use DTS
(Data Transformation Services) of ERPJewels.
In such a case there is a need for updating such estimates/budget automatically. The tool provides for running a 4GL or 3GL program after the analysis is done. After analysis program can be maintained in the following sessions for each separate data source in Baan.
1. Analysis based on Baan report
2. Analysis Based on Baan Table
For this purpose, a new program should be written to update transactional data base.
The tool will activate the 3GL or 4GL program with following arguments in the following order.
1. Analysis serial number - This is long type of variable. This is a unique number which identifies an analysis definition in unique manner in analysis definition masters. Even in analysis runtime data this number is stored.
2. Analysis based on- This is Enum field with domain tubase. This tells whether analysis is based on Baan report or Baan table or ASCII file.
3. Analysis History number – This is long type of variable. This indicates the number of analysis within an analysis.
This arguments can be accessed with the help of argv$ function.
With the help of these arguments and pre-defined variable logname$, user can access analysis runtime data and update the transactional database. Analysis runtime data are contained in following tables.
1. tudll980 - Analysis runtime data.
2. tudll981 - Analysis runtime column data.
3. tudll982 - Analysis runtime Row data
4. tudll974 - Analysis runtime Drill down data.
When the analysis are run from Baan job management, the after analysis program will not be invoked. The after analysis program has to be scheduled immediately after job running the analysis is finished. In such a case the after analysis program has to be a 4GL program which can be included in Baan jobs.
Further when after
analysis action is delete, analysis runtime data are deleted. So to run an
after analysis program the after analysis action has to be ‘save’.
In cases where customer has separate OLAP server, the user has to use Analysis type as “OLAP Interface” and have his / her client application which can use the analyses results and upload the same to OLAP Server.
FastTrack to ERPJEWELS :
Latest Trend | Hot Links | Jewels of ERPJewels | Jewels of Baan | Jewels of Excel