'No import Transferred' Error URGENT

Hill, Anna anna.hill at sap.com
Fri Oct 7 05:52:34 EDT 2005


Hi Adnan
 
When you are operating at method level, you already have the obeject
instance - any method parameters are OPTIONAL extras, so you do not need
to bind the object instance into the method, only into the task. Some
methods have no parameters at all and no bindings are available at
method level. 
 
However it is handy to know that method bindings are implicit - this
means that you do not usually need to specify them. When you add the
method to a task, if there are method parameters available, you will be
asked whether to 'transfer the missing elements from the object method'
- if you say yes to this (which you should), this will automatically
enter container elements into the task container of the same name and
reference of the method parameters. The bindings will automatically
transfer data from containers elements in the task which are identical
to container elements in the method without you needing to specify them.
 
Best thing to do test the task in SWUS and just bind the object instance
in, and no additional paramters. You should then find that it works OK
and can try calling it from your workflow. 
 
Regards


Anna Hill
SAP Netweaver Technology 

SAP (UK) Ltd
Clockhouse Place, Bedfont Road,
Feltham, Middlesex TW14 8HD 

T   +44 (0)20 8917 6125
F   +44 (0)20 8917 6461
M  +44 (0)7966 975125
E  anna.hill at sap.com <mailto:anna.hill at sap.com>  

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Adnan Hashim
Sent: 06 October 2005 13:34
To: SAP Workflow Users' Group
Subject: RE: 'No import Transferred' Error URGENT


Anna, 
   I do agree with you and that is what I expected. But I cannot bind
the object instance to bound in the method. Beacaue when I try to bind
it, I don't find a match on METHOD level. 
Refer to the pic attached. The method has only 1 PARAMETER
'ReleaseIgnore' . 
 
In my tracing I found out that the method is invoking
FIPP.FlagReleaseSet which fails to 
read the Object-key and raised the Exception  (FP065, subrc = 1)  'No
import transferred'.
 
Any clue ? am I missing something important here ? !!

Regards
Adnan

"Hill, Anna" <anna.hill at sap.com> wrote:

	Hi Adnan
	 
	All tasks must have the object instance bound in to be able ot
execute at runtime, which si what you're missing here. The import
parameter you describe below is an ADDITIONAL import parameter (and will
default to X if nothing is bound in). Check you are binding the FIPP
object into your task in the workflow. Test the task in SWUS as ensure
you provide an instance of the parked invoice when you test it. If this
works OK, then you know there's a problem in your bindings. 
	 
	Good luck!
	Anna
	SAP UK

________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Adnan Hashim
	Sent: Wednesday, October 05, 2005 7:31 AM
	To: SAP Workflow Users' Group
	Subject: 'No import Transferred' Error URGENT
	
	

	Hi Experts,

	    Am using TS50000048 (FIPP_CHAPOST) which has only 1 IMPORT
parameter 'ReleaseIgnore'  and has 2 Terminated Events FIPP.POSTED &
FIPP.DELETED and the binding is there for those T.E

	 

	Know when I ever execute the workitem I get the below Error and
exit the W.F I could not

	find more help on this. Can you help pls ?

	 

	 

	 

	 



	Adnan Hashim
	ABAP & WorkFlow
	Batelco, Bahrain. 

	
________________________________

	Yahoo! for Good
	Click here to donate <http://store.yahoo.com/redcross-donate3/>
to the Hurricane Katrina relief effort.
_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	

________________________________

Yahoo! for Good
Click here to donate <http://store.yahoo.com/redcross-donate3/>  to the
Hurricane Katrina relief effort. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051007/bb56cbc7/attachment.htm


More information about the SAP-WUG mailing list