I need to make a change to the report for session tfacp1438m000. But when I compile the Baan standard session, I already get the following error and I am unable to find what causes it. Has anybody seen this before:

rtfacp1438150002:
repgen6.1 -c 'tfB40Cb4AlpG' '2tfB40Cb4AlpGacp143815000' -o /baan_tmp/users/tmp0
53378136 -q /baan_tmp/users/tmp053378137
bic6.1 /baan_tmp/users/tmp053378136 -d otfglddll0061 -u -o rtfacp1438150002 -f
/baan_tmp/users/tmp053378135 -q /baan_tmp/users/tmp053378137
tmp053378136( 229): Error: 'r.todayl$' not declared
tmp053378136( 231): Error: Dimensions in array assignment differs: -1:0
tmp053378136( 232): Error: Operations with arrays not allowed.

Did you lately update your portingset? As far as I can remember this has to do that the include files don't match with your portingset.
Please make sure that the used include files belong to your portingset.

Regards,
Han

This is what gets to me, this report does not utilize any includes. And the library it does use, does not seem to be the cause of this problem. This is definitely not a variable that is used anywhere in the report.

I am not sure how to proceed.

Can you compile any reports or is this the only report with the problem?

There are 6 reports linked to this session and I am not able to compile any of them. But I am able to compile reports linked to sessions tfacp1436m000 and tfacp1435m000 without any errors.

Have any tools patches or porting set updates been applied? On our system I can put a report in debug mode and see r.today$, but no r.todayl$.

Normally variables/tables fields ending in l is a localized one (like BGL0). Just
From the error it looks like a valid error, may be you got a script with bug in it

No tools updates or updates to the porting set has been made. Yes, we do use Global Localization (BGLO). The problem is that I am not able to find this variable anywhere in the script for the report or any of the report fields. Thus I am not sure how to solve this problems. Any ideas of where to start will be appreciated. I have thought to redo the report field by field and line by line and then see if I still get the error. Perhaps if you can debug the report, and you can see the variable, then you can let me know what the domain should be and I can start working from there.

Thanks for your help so far.

One scenario to look for is, field is used in the layout, but nt defind in the report script nor in the input fields
In this case you may end up with the error

This was my thought also at first, but I physically went through every field that is used in the layout of this report and this variable is nowhere to be found. It is nowhere in the layout, not any of the input fields and not anywhere in the report script. There are no include files used by the report script where this field could possibly show up. The report uses 1 library, but even after removing this library and all traces of it, I still get the error.

I am still pretty sure that it has to do with the include files since the error sound so familiar with me. Perpaps you should log an inquiry with ssa and see what they turn up with.

Regards,
Han

Will ssa assist me if this is a customization I am working on? As far as I know they just ignore customization cases.

Try copying a standard report and compiling that. This will show if it is your problem or standard Baan. If the standard report will not compile, Baan Support should help. If the standard one works, start from there to see what is wrong with yours.

Edited: I see that you can compile the standards. Can you use a standard report that compiles, just to get your headings, then replace the layouts with your own...? If you do that one by one you can see which layout has an issue (if any).

It is the standard that will not compile. I will get Baan Support to help me to solve this.

Thanks for all the help.

It is the standard that will not compile. I will get Baan Support to help me to solve this.

Thanks for all the help.

Hello,

4 Years ago i've had this problem too.

It was a bug in bic_repgen.
I've changed the bic_repgen an my r.todayl$ goes away.

!!! First talk to your BaaN Support !!!

Regards