mrinmoygupta
13th April 2010, 11:36
We use the below code to generate outbound (tdilc4201m000) using stpapi
...
...
stpapi.put.field( "tdilc4201m000", "print.recom", str$(tcyesno.yes) )
stpapi.put.field( "tdilc4201m000", "prnt.shortage", str$(tcyesno.yes) )
stpapi.set.report( "tdilc4201m000","rtdilc420101000",p.disp, error )
stpapi.continue.process("tdilc4201m000",error)
rets=stpapi.get.mess.code("tdilc4201m000", error)
stpapi.end.session("tdilc4201m000")
...
...
It has stopped working after upgrading from SP21 to SP27. It seems it does generate the outbound but always comes back with a message that "Report Name not Filled". AFSLOG does not say more. We have also installed the latest stpapi solutions. It only works if we replace tdilc4201m000 with SP21 object. One more thing, everytime we run this session the reports
rtdilc420101000 and rtdilc420102000 are loaded in the background and keeps running. Any help will be appreciated.
manish_patel
13th April 2010, 13:50
In previous thread Andy has same problem; you can check with him.
http://www.baanboard.com/baanboard/showthread.php?t=35898
mark_h
13th April 2010, 15:00
Don't know if this helps or not.
| The next 4 lines generate both the advice and shortages, if you want
| just one report then set the flags correctly, but always point the report
| to the advice report - This is the only way to get it to work.
| Advice Report
if run.advice = tgyenox.yes then
stpapi.put.field( "tdilc4201m000", "print.recom", str$(tcyesno.yes) )
else
stpapi.put.field( "tdilc4201m000", "print.recom", str$(tcyesno.no) )
endif
stpapi.put.field( "tdilc4201m000", "prnt.error.report", str$(tcyesno.yes) ) |20060804
stpapi.put.field( "tdilc4201m000", "prnt.shortage", str$(tcyesno.no) )
stpapi.put.field( "tdilc4201m000", "pr.peg.shortage", str$(tcyesno.no) )
stpapi.set.report( "tdilc4201m000","rtdilc420101000",spool.device, msg )
stpapi.continue.process("tdilc4201m000",msg)
stpapi.end.session("tdilc4201m000")
We are only on Sp23 or 24. Just like with the other post I would report to baan and check the session out also.
mrinmoygupta
14th April 2010, 11:48
Thanks for your inputs Mark. Both the posts originated from the same source.
Along with SP-27 we’ve also installed latest tools and stpapi patches. I’ve tried going back to older stpapi, it does not help. It is only when I go back to older outbound session object it starts working again. In all the cases it does generate the outbound and print the outbound but comes back with this message and also has both the reports running in the process list.
This is what Infor support says
“...customizations are not part of the Scope of Operations for Standard Support.
The session in the AFS script is using a customized form which can not be supported...direct you to PSO department....
mark_h
14th April 2010, 14:47
Yep - that sounds like them. Have you asked pointedly for the lastest version of the outbound program? We also have customized the form - using qkey. I think we are going to SP27 later this year. Do you all own source where you might be able to see what the code is doing?
Andy..
20th April 2010, 21:21
Hi Mark, what does field 'pr.peg.shortage' refer to...?
Don't know if this helps or not.
| The next 4 lines generate both the advice and shortages, if you want
| just one report then set the flags correctly, but always point the report
| to the advice report - This is the only way to get it to work.
| Advice Report
if run.advice = tgyenox.yes then
stpapi.put.field( "tdilc4201m000", "print.recom", str$(tcyesno.yes) )
else
stpapi.put.field( "tdilc4201m000", "print.recom", str$(tcyesno.no) )
endif
stpapi.put.field( "tdilc4201m000", "prnt.error.report", str$(tcyesno.yes) ) |20060804
stpapi.put.field( "tdilc4201m000", "prnt.shortage", str$(tcyesno.no) )
***stpapi.put.field( "tdilc4201m000", "pr.peg.shortage", str$(tcyesno.no) )***
stpapi.set.report( "tdilc4201m000","rtdilc420101000",spool.device, msg )
stpapi.continue.process("tdilc4201m000",msg)
stpapi.end.session("tdilc4201m000")
We are only on Sp23 or 24. Just like with the other post I would report to baan and check the session out also.
Thanks
mark_h
20th April 2010, 22:24
We run the A&D version of the session and this would print the peg(or project) shortages on the order.
Andy..
21st April 2010, 16:46
in further news it seems the SP26 version does work, so watch out if you gen outbound and upgrade to SP27.
There even seems to be a specific solution that could be causing the problem:
Solution: 239302
SITUATION IDENTIFIED IN:
"Generate Outbound Advice" (tdilc4201m000)
SITUATION DESCRIPTION:
If a customized report is added to the "Generate Outbound Advice" (tdilc4201m000) session, then
the box to select the report is displayed multiple times. The user chooses the required report and
after pressing the continue button, the box comes up again.
When running the session for a new outbound run, without closing the session, the box comes up
three times.
SOLUTION DESCRIPTION:
Adaptations are made to ensure that a report menu box only appears once per print range.
mark_h
21st April 2010, 22:06
I think we go to 27 later this year.
mrinmoygupta
26th May 2010, 13:05
To update you on this Infor support has accepted this as a product issue in SP-27 and has promised us a fix soon.
mark_h
29th January 2011, 01:02
Does infor have a fix for this yet? We were just testing SP25 to Sp28 and my outbound code has stopped working.
mrinmoygupta
31st January 2011, 15:34
I've been provided this fix sol# 249269 which I've not installed yet. Let me know if it works for you.
Does infor have a fix for this yet? We were just testing SP25 to Sp28 and my outbound code has stopped working.
mark_h
31st January 2011, 16:30
I will look into trying to use this solution.
Thanks
mark_h
31st January 2011, 18:32
It worked on our system. :D No more report name not filled and we get our reports. What I did not test is trying to get all the reports at once - I only tested the ones we use.
Thanks
mrinmoygupta
1st February 2011, 11:06
Thats good news. We are currently continuing using SP26 obejct. Will upgrade in future.
It worked on our system. :D No more report name not filled and we get our reports. What I did not test is trying to get all the reports at once - I only tested the ones we use.
Thanks
mark_h
1st February 2011, 15:20
More detail is that what we did before - was we ran the session twice to get all the reports. One run got the advice and the error report. The second run would get only the peg shortages. I did not try to re-write the code to get all three reports at once. Before this patch those routines would error out with report name not filled. And now with the patch the old code works, so I left it alone. Thanks again for the solution!