FM not triggering????????

[Former Member]

Hi Everybody,

I'm new to ALE/ IDocs and trying to trigger a ZFM from a delivery. An IDoc is generated when an o/p type is created. When I do that it is generating the IDoc but if I put a break point to chk my code in FM where IDoc is getting generated it's not stopping. Any idea??????????

Thanks in advance....

chesat

[christian_wohlfahrt]

Hi Chesat!

Your ZFM is called in update task. You did not activate update debugging, so any break point does not stop, even when the function is called.

This is a setting in the properties of the debugger, activate this before ( / in the beginning of) saving the delivery.

Regards,

Christian

[Former Member]

Hi,

It seems the FM is under an IF condition or would be executed only if certain condition is satisfied. Since the condition is not satisfied your FM is not triggered.

If you want that the FM should alwyz be executed, then please check whether you have specified in condition for its execution.

I hope this would solve the problem. If it still doesnt solve the prblm, then pls. paste the code.

Best regards,

Prashant

[andrea_galluccio2]

Hi,

use the inbound/outbound idoc function to test your idoc inbound/inbound.

Create and idoc like the other and try execute it. There u will able to put the break point to the function module that save the idoc on the database.

Now i don't have a system near here. Run WEDI trx and then select an idoc already created , copy and test it.

Before "run", u shoul be albe to select the which FM use to save it. Watch what is the FM and put a break-point in it.

Hope it helps

Bye

Andrea

Pls reward if it helps

[Former Member]

Hi Chesat,

There might be 2 possibilities for that :

1. Your fm is being called in Update task. To check that you see the where-used-list for this fm. There you can check if it has been called in update task. If this holds true, activate update debugging.

2. You are not authorised to debug this fm. To check whether you are actually triggering this function, write some message type 'x' inside this function. It will generate a short dump. Now you can check list of short dumps generated in transaction ST22. There you can see the user name. If its not user then you need authorization to debug this code.

Most important don't forget to delete your short dump code from fm...

[Former Member]

Hi everybody,

Thank u all for ur replies. But,inspite of activating the update task I'm not able to trigger the FM when I save o/p type after a repeat. But I was able to trigger it through VL71 trnx. Problem is sloved but still not cleat not thru VL02N???????????

Thanking u alllllllll