issue with amodal secondary method call

[Hilsbos, Margaret A]

Vijay,

In development this is not likely to be your problem, but what happened to me in production with using a secondary method is that the user did not have all the necessary authorizations. Apparently calling a secondary method relies on an authorization that the user could be missing and not even notice otherwise.

If you haven't done so already, you should do SU53 to see if this is your problem.  

Margaret Hilsbos
Day & Zimmermann

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of vijay srikanth
Sent: Wednesday, October 26, 2005 12:48 AM
To: sap-wug at mit.edu
Subject: issue with amodal secondary method call


Hi,

I'm using an amodal secondary method call in my workflow step.
For some reason the secondary mehod is not called and not executed.
What could be the reason for this. I was first thinking there could be 
binding problems between
the workflow and the task container, but then I realized that for secondary 
methods, there's no binding definitions transfer between workflow and the 
task. Could there be any other reason for the secondary method not to be 
executed. Thanks for the help in advance.


Regards,
Vijay


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug