I have upgraded from BaanIV (old timer) to SSA LN6 recently.

In LN6 at Session (ttadv2500m000), I can add a report by clicking Specific>Reports (ttadv3530m000),Then click Specfic>Link Report to Session.
There I specific the Group and No. to which I want to place the report. (something equivalent to BaanIV).
I do not seems to have problem with other reports in LN6.

Except for (so far) tdpur4401m000 (print purchase order) & tdsls4401m000 (print order acknowledgement).
By debugging & reading script, I discovered that both the above reports doesn't really use/utilize whatever existing "standard" report or "to be customized report" that you have place in the Group and No. in ttadv3530m000 mentioned above. In fact, both reports utilized the function script tdpurdll4401 and tdsls.dll4401 respectively which inside its script referred "hard coded" its existing "standard" report. Thus, I can say that it is "controlled" by script and not by the "Group and No." in ttadv3530m000.

Anybody out there who can please help solve this problem.
Or teach how to made the above mentioned function scripts to utilize the "Group and No." in the ttadv3530m000.

Hi ,

As u mentioned u r able to read & debug ...means u hv the source code so y not carry out source code customization to suite yr requirement.
:-)

regards,

Thank for the reply.
The reason I did not want to customize it because I just want to copy & MINOR editing to layout to suit different users. So there is no point to customize it. I can read source but fair in simple programming only.

sorry,should be "no point to use source, just use layout in ttadv3530m000".
I just use ttadv3530m000 (not program source) to create many report layouts to suit many users in LN6 with no problem except in the tdpur4401m000 & tdsls4401m00 (so far, I discovered these two in LN6 after upgrading from BaanIV).

Some background info
In LN users have the possibility to automate steps that are present in the order type. When an order is approved automatic processing starts. If the order step for printing the order is automated the order will be printed automatically. A dll was needed to make printing the order available for automatic processing from all kinds of applications. So, reports are not strictly linked to a session anymore, but are related to print DLL's.

Defect
However, users want to customize the reports linked to the print session. I did not realize myself that during development of the automatic processing functionality. Just this week a defect was coming in. We are now making a solution for it in sessions tdpur4401m000 and tdsls4401m000, so that users can customize in the way as they are used to in previous versions:
- The print reports are linked to the print sessions again.
- If a user wants to customize, the options are:
1. Copy the report to the customization vrc and simply change the report
2. Copy the report to a new one in the customization vrc, link the new report also to the print session (in the same report group). When pressing the print button, a menu pops up which report must be printed: the new customized report or the standard report.

You can expect the solution within a few weeks.
When you have more hints, please post them!

Dear Evert-Jan Bosch,
It is indeed a welcoming answer from the guru himself.
If the solution can come out within a few weeks, it can really make all the LN users jumping up in joy.

Can please you let me know once the solution is out?

Can please you let me know once the solution is out?
I will post it here once the solution is available.

I know that SSA will need few weeks for the defects.
However I am really in urgent need to customize layout for few of my users.
For the print sales order (order acknowledgment) and purchase order mentioned previously, I have only the function script (tdslsdllsls4401 and tdpurdllpur4401) respectively. Is there any way I can temporarily utilize the function script so that I can customize in such a way users can pick their choice of reports ? I have a few idea:_

1. I try but not workable. In the DFE, i inserted a new field to the existing Form so that my user can select it. Then I write a few statements in the function script to get the new field that user selected. However its fail because as you know the new field will appeared as error message due not recognised and therefore the new field is not "passed" to the function script.
If I have the program script , I can add the new field to the before.layout but problem is I do not have program script (only function script). Am I correct? Is there any way for the new field to be 'recognized/passed" to the function script.

2. Is there any where in the function script whereby the statement before the "standard" report, I can make a subroutine to pop-up selection "window" prompting user to chose reports?

Example (see may remark statement brad997 below):
(in the function script)
function long print.report(...)
.......

for nr.copy = 0 to (i.preview ? 0 : g.copies)
orco = strip$(tdsls400.ofbp) &
strip$(tdsls400.orno) &
str$(nr.copy)
|| brad997-if i can make a pop-up here for user to select it.
|| then I can write something i like this
if report select = 1 then|say for "standard" report
RETIFNOK(tdsls.dll4206.print.report("rtdsls440101000",device,tccom110.clan,o.process.stopped))
if report select = 2 then|say for "user A" report "99"
RETIFNOK(tdsls.dll4206.print.report("rtdsls440101099",device,tccom110.clan,o.process.stopped))
if report select = 2 then|say for "user B" report "98"
RETIFNOK(tdsls.dll4206.print.report("rtdsls440101000",device,tccom110.clan,o.process.stopped))
| and so on....
o.order.printed = true
endfor

return(0)
}

You need to change following components to get a workable solution:

1. Session tdsls/pur4401m000
- enable choice print.data in the std. commands and remove the choice cont.process in the form commands
- link the standard and the customized report to the session
2. UI script tdsls/pur4401
move logic from choice cont.process to choice print.data. As a result tools variable spool.report will be filled when user presses the print button.
3. DLL tdpur/slsdll4401.
Pick up the tools variable spool.report in the dll and sent that one to dll 4206.RETIFNOK(tdpur.dll4206.print.report(
spool.report,
device,
tdpur.dll0402.get.buy.from.language(
tdpur400.otbp),
o.process.stopped))
This is the way the official solution will be made (more or less).

For sales the solution is already published: 202679.
For warehousing the solution is: 202800.

For purchase the solution is: 202670.