FB60 transaction call works with method, not with task

Tiwari, Rammanohar rammanohar.tiwari at logicacmg.com
Thu Jul 28 02:52:04 EDT 2005


Did you write the code to set the parameter BUK before calling the transaction in your method?
 
Inside your method use the code like given below:
SET PARAMETER ID 'BUK' FIELD lv_bukrs.

CALL TRANSACTION 'FB60'.

 
Cheers,
Ram

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of mikko.maki-rahkola at accenture.com
Sent: Thursday, July 28, 2005 11:52 AM
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



This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050728/090c85e3/attachment.htm


More information about the SAP-WUG mailing list