How user exits attached to SAP programs ?

[Former Member]

How are user exits attached tp SAP programs ?

Is it through CALL FUNcTION 'Some-EXIT-NAME'

Now I know that in my case a user exit EXIT_SAPLCOIH_009 is implemented for transaction IW32. I am turning debugger on by using /H and then clicking on save event in IW32 when the user exit gets triggered.

Then I set break-point for CALL Function inside the debugger.

But I can't see CALL FUNCTION 'EXIT_SAPLCOIH_009' in the debugger of transaction program....

So I am just wondering is it this way the user exit is hanged to program. Please throw some light on this....

[Former Member]

How are user exits attached tp SAP programs ?

Is it through CALL FUNcTION 'Some-EXIT-NAME'

Now I know that in my case a user exit EXIT_SAPLCOIH_009 is implemented for transaction IW32. I am turning debugger on by using /H and then clicking on save event in IW32 when the user exit gets triggered.

Then I set break-point for CALL Function inside the debugger.

But I can't see CALL FUNCTION 'EXIT_SAPLCOIH_009' in the debugger of transaction program....

So I am just wondering is it this way the user exit is hanged to program. Please throw some light on this....

[RichHeilman]

I would say that most are implemented as function modules which are usually called by something like this.

CALL CUSTOMER-FUNCTION 'WHATEVER'

Some are implemented as includes, like the ones for Sales Document Processing.

In your case, it is a function module, EXIT_SAPLCOIH_009 which is probably called by CALL CUSTOMER-FUNCTION '009', or something to that effect, somehow it translates to EXIT_SAPLCOIH_009. Also there must be a "Z" include in the function module EXIT_SAPLCOIH_009. Double click the include, system will ask you if you want to create it. Say yes. Now put a break-point in the include. Make sure to activte the enhancement in SMOD/CMOD. Run your main program, It should stop at your break point.

Regards,

Rich Heilman

[Former Member]

Thanks Rich , you advice have been helpful always.