We need to add tdltc001.lsup to our Print Outbound reports (tdilc440101000-tdilc440105000). When I use the Baan sessions to add the field below the tdilc401.clot field that is already on the report and complile, the report just returns a blank. I know that was because the field wasn't declared in the script because we had to add the same field to the Replenishment Pick List report last week. I had a script for the Replenishment Pick List report so Baan support helped me declare the table and I was able to get the field to print on that report. Now I have to do the same on Print Outbound but there is no script. What do I do now?

4c4
Windows

Just create an empty script. Then add declarations into. Not really sure if that is what you are asking or not. Not all baan reports have a script and you just need to add one.

We need to add tdltc001.lsup to our Print Outbound reports (tdilc440101000-tdilc440105000). When I use the Baan sessions to add the field below the tdilc401.clot field that is already on the report and complile, the report just returns a blank. I know that was because the field wasn't declared in the script because we had to add the same field to the Replenishment Pick List report last week. I had a script for the Replenishment Pick List report so Baan support helped me declare the table and I was able to get the field to print on that report. Now I have to do the same on Print Outbound but there is no script. What do I do now?

4c4
Windows

Hello,

add a reportscript.

then code:

declaration:

table ttdltc001

in report section with field tdilc401.clot :

select tdltc001.*
from tdltc001
where <your condition>
...............

Regards

As Mark has observed in his post above, report script is not mandatory for all reports. You use report scripts only if you want some complex manipulation in the report which is not possible in layouts or in program script.

I guess you have to declare table tdltc001 if it is not declared already in the program script. And then add a select (or join tdltc001 to the select on tdilc401). If table tdltc001 is already declared and selected, confirm that field tdltc001.lsup is selected.

You can debug the program script, placing a trace on tdltc001.lsup, to see if it is getting any value before the data is sent to the report.

NVP

As Mark has observed in his post above, report script is not mandatory for all reports. You use report scripts only if you want some complex manipulation in the report which is not possible in layouts or in program script.

I guess you have to declare table tdltc001 if it is not declared already in the program script. And then add a select (or join tdltc001 to the select on tdilc401). If table tdltc001 is already declared and selected, confirm that field tdltc001.lsup is selected.

You can debug the program script, placing a trace on tdltc001.lsup, to see if it is getting any value before the data is sent to the report.

NVP

Hello,

in BaaN original sessionsript by Wim van Lemmen, table tdltc001 is not declared.
So the field tdltc001.lsup is not accessible.

If session source is not available, it's the best way to declare and read the field in reportscript.

Regards

Hello,

in BaaN original sessionsript by Wim van Lemmen, table tdltc001 is not declared.
So the field tdltc001.lsup is not accessible.

If session source is not available, it's the best way to declare and read the field in reportscript.

Regards

Agreed...if source code is not available, it would be easier to do it in reportscript.

That worked. I assumed you had to have a script to start with. Thanks again.