FB60 transaction call works with method, not with task

Kjetil Kilhavn KJETILK at statoil.com
Thu Jul 28 03:45:01 EDT 2005


If you are certain that the bindings are OK and the container in the
task contains the company code, then you have to take the long road.
Test it with tracing on and examine the trace to see what happens when
the transfer of container elements takes place.
-- 
Kjetil Kilhavn, Statoil KTJ IT BKS
 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of mikko.maki-rahkola at accenture.com
Sent: 28. juli 2005 08:22
To: sap-wug at mit.edu
Subject: FB60 transaction call works with method, not with task


Hello wug:ers,
 
I tried to fine-tune our non-PO invoice entry workflow step because it's
currently launching an SAP standard company code popup when entering
FB60 but ran into some difficulties, I hope you can help me out. We're
on 4.6c.
 
I have an instance-independent document parking method for the subtype
of object BKPF having company code and transaction code as import
parameters. The method basically just calls FB60 with the company code
(the company code is entered into the user buffer and afterwards FB60 is
called). Testing it and putting in the two required params, transaction
FB60 is launched with the proper company code without any popups for
entering a company code. Method is ok, everything fine so far.
 
But. When I start a task wrapping the above method with proper input
values, the popup suddenly reappears. I don't know what's wrong because
I have the company code and transaction code as task container elements
(import) and the bindings between the task and method container are ok.
When looking at the runtime task container, the company code is
populated there as well. For some reason it just doesn't reach the
method container because the popup is launched. 
 
Do you know why this happens?
 
Any ideas appreciated,
-Mikko


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050728/64d76db5/attachment.htm


More information about the SAP-WUG mailing list