Can I not use interfaces as input objects in single tasks? (R/3 4.6C)

[Kjetil Kilhavn]

I am currently rewriting an existing application where the code is quite
dynamic and re-useable. In order to maintain the dynamic nature of the
solution I thought I'd create an interface and reference the interface
instead of creating all methods in all object types. A nice surprise
compared to ABAP Objects was the ability to actually implement a method
in the interface, so I didn't have to copy the implementation between
all the object types.
 
Now I am facing the problem that apparently I can not bind my purchase
requisition object to the task I have created for executing my interface
method. It seems I will have to create one task for each object type
that implements the interface. Needless to say, this is a major bummer
after being happy about the ability to implement the method in the
interface.
 
Has anyone successfully used an interface as the object in a task? 
I've been trying all sorts of things now and am about to give up and
create one task per object type, but first I'll give you the weekend to
assist me ;-)
-- 
Kjetil Kilhavn, Statoil KTJ IT BKS
 


-------------------------------------------------------------------
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/20050827/fa42952f/attachment.htm