Complexities handled
Complexities handled
|
Particulars |
Details |
|
Question |
Upto what service pack of Baan , ERPJewels is tested . |
|
Answer |
Tested upto SP23 specifically. Changes to the program due to changes in repgen program are minimal and very easy to do (may be 1 hour of debugging is sufficient ) |
|
Particulars |
Details |
|
Question |
How can I print all the fields of a layout report layout with minimum effort |
|
Answer |
|
|
Particulars |
Details |
|
Question |
Can I have more than 1 analysis on same report |
|
Answer |
Yes definitely. All analyses will run in the same program run. |
|
Particulars |
Details |
|
Question |
Can I run only 1 analysis out of more than 1 analysis linked to Baan report under job management. |
|
Answer |
Yes. Please make allowed yes only for 1 analysis. And
further link only that analysis when run under job management in se |
|
Particulars |
Details |
|
Question |
Can I add report input variable which may not be an output variable on the layout |
|
Answer |
It's not required as it may be meaningless information for after.field section .In normal circumstances this is not the requirement. However sometimes user may wish an input field which may not be output variable on the report. This may be a particular case in detail layout. In other layouts, it may not be meaningful to have an input field (not an output field) as an analyses field. Further user can zoom to report input variables with use of CTRL + E command on the report field input. |
|
Particulars |
Details |
|
Question |
Can I see report layout output field / input field and report layouts just before creating analyses. |
|
Answer |
Yes , with the use of Easy analysis creator for Baan report |
|
Particulars |
Details |
|
Question |
Can I use a variable declared in report script for analyses purpose. |
|
Answer |
If it is used as an output variable on the layout on which analyses is being made, then yes. In case it’s not required in the output then such variable may be included in the layout with 0 print condition and then included in the analyses. In normal cases, there will not be such a requirement. |
|
Particulars |
Details |
|
Question |
Will ERPJewels work on Windows NT |
|
Answer |
ERPJewels will run on any platform on which Baan runs. Because it’s written in Baan 4GL. Client programs will run only if client PC uses MS Office 1997 onwards. |
|
Particulars |
Details |
|
Question |
Does ERPJewels extract the values from report even if print condition is false |
|
Answer |
Definitely not. It's not required. |
|
Particulars |
Details |
|
Question |
Does my performance affect when printing report with ERPJewels. |
|
Answer |
Not at all. As ERPJewels does something extra (Extract, Transform and Load), the performance may be affected a bit for users authorized to see the analyses for that report. There will be no impact on performance for users not authorized to run analyses. Analyses on detail layout will take little more than analyses on after field section due to very architecture. |
|
Particulars |
Details |
|
Question |
Can I authorize the analyses user wise. |
|
Answer |
Definitely yes |
|
Particulars |
Details |
|
Question |
Can I add fields which are not printed in the layout. |
|
Answer |
By default all report output fields (including derived
aggregate fields and variables declared in the report script) are available
for choice. For detail layouts, all sort fields are available for selection
(be it printed in the layout or not). For after fields, all sort fields of
higher order are present (be it printed in the layout or not). Further if any
field is not printed in the layout and is present as an input field, user can
select such field for analyses. This will be meaningful only for detail layouts. |
|
Particulars |
Details |
|
Question |
Can I add fields from other layouts. |
|
Answer |
No. This is mainly required for sort fields. These sort
fields are available by default as per the layout. |
|
Particulars |
Details |
|
Summary Problem |
After report single column /row graph giving fatal error |
|
Description |
After report single record analysis did not the show the graph correctly. |
|
Frequency |
For any analysis on after report section |
|
Program Modified |
Yes |
|
Workaround |
Not required |
|
How do I Know |
Create an analysis on an after report section (e.g. aging analyses report for customer/supplier) |
|
Particulars |
Details |
|
Summary Problem |
Intervening empty detail layouts creating problem |
|
Description |
In reports with 1 or more detail report layout without output fields and just with labels (herein after called empty layouts), data is not extracted properly. Normally detail layouts contain at least 1 output field . However in rarest of rare situation when you have detail layout without output field and there is a detail layout after this layout from which data is to be extracted , the data is not extracted properly. |
|
Frequency |
Rarest of rare |
|
Program Modified |
No |
|
Workaround |
Specify at least 1 output field on a detail layout. If absolutely not required then have the print condition as 0 for that particular variable. |
|
How do I Know |
Create a blank empty detail layout and add 1 detail layout after that layout and have the analyses set on this detail layout. |
|
Particulars |
Details |
|
Summary Problem |
Forms without dictionary information |
|
Description |
Only form dump without form dictionary in tools will make selection
criteria for analysis inacce |
|
Frequency |
Rarest of rare. |
|
Program Modified |
No |
|
Workaround |
If standard, a form dump may be asked from Baan CS&S. In other cases recreate the form either manually or import it from backup or customization partner. |
|
How do I Know |
When the selection criteria do not come for analyses based
on Baan report, the se |
|
Particulars |
Details |
|
Summary Problem |
Improper Data extracted |
|
Description |
When the first field on the analysis layout was suppre |
|
Frequency |
Rare |
|
Program Modified |
Yes |
|
Workaround |
Not required |
|
How do I Know |
In an analysis keep the suppre |
|
Particulars |
Details |
|
Summary Problem |
Average aggregate function not working |
|
Description |
Average values were not extracted properly in the analysis layout. The reason is average in Baan report is a calculated field (just the way in MS OLAP ). |
|
Frequency |
Whenever Average is used |
|
Program Modified |
Yes |
|
Workaround |
Not required |
|
How do I Know |
Include a value in the analysis for the function average. |
|
Particulars |
Details |
|
Summary Problem |
Data from detail layout with intermittent sequence |
|
Description |
Data from Detail layout (with report sequence not in ascending orders) were not extracted perfectly. |
|
Frequency |
Sometimes in the situations specified |
|
Program Modified |
Yes |
|
Workaround |
Not required |
|
How do I Know |
Earlier logic a |
FastTrack to ERPJEWELS :
Latest Trend | Hot Links | Jewels of ERPJewels | Jewels of Baan | Jewels of Excel