user exit

[Former Member]

Hi Friends,

I have a function exit and Include file in it. I want to make some changes in the include file and debug it. How should I do it. If I set a break point in the include and run the function exit, it is not stopping in the include. Please help me how to do it.

Thanks

Veni.

[sridhar_k1]

Create a project in Tx:CMOD and assign the enhancement of the function exit and activate the project.

Regards

Sridhar

[Former Member]

Vani,

If you have already activated the project then put a break point at the statement the function exit is called...then you will whether the control is going there atleast or getting skipped.

Thanks,

[Former Member]

hi,

After placing the break point, u need to executre the transaction assoiated to this exit. Then it will stop when the corresponding event is triggered.

Sreedhar

[Former Member]

Hi,

First go to CMOD and crate the Project and then Assign the Enhancement to it . adn then implement the exit by double clicking the Function module, there you have to add the code inside the ZX*****include . and write the code. and activate the FM,and Project. and now keep a break point in the include code. and now run the Corresponding transaction.

Regards

vijay

[Former Member]

Hi Veni,

put tis code into ur INCLUDE program.

If sy-uname = <give ur user name>.

break-point.

endif.

- Selvapandian Arunachalam

[Former Member]

The information you provided is not sufficient to give you any reason why it is not stopping at the breakpoint. In all probability, your user exit is called in an update task and so it is not stopping at your breakpoint. Another reason could be that your user exit is an output related one like IDOC. Please let us know the user exit and the include so that we can give you a way to debug.

[Former Member]

Hi Srinivas,

It is related to IDOC. EXIT_SAPLVMDE_003 is the exit and ZXLIDU17 is the Include. Please help me how to debug.

Thanks

Veni.

[Former Member]

Vani,

The main program which is calling EXIT_SAPLVMDE_003, put a breakpoint at a statement before calling this exit. I dont know whether it is looking for some condition before calling this exit or not. So try a breakpoint before the exit and check whether the control is going till there. If the control goes inside, the it will surely pass through the include.

Thanks,

[Former Member]

IDoc processing happens in a separate background process, so the processing won't stop for you to see it.

I've found that the best way to debug is to use the IDoc test environment (WE19), copy an existing IDoc (enter its number on the selection screen in the field "Existing IDoc"), and process your copy via "Inbound function module", in foreground. This should work, i.e. the processing will stop at your breakpoint, if I remember well (it's been some time since I've worked in this area).

[Former Member]

Since this is an inbound IDOC, you have to use WE19 test tool to get into debugging. If it is outbound, then you can execute RSNAST00 for the specified output type and stop at the break point. Of course the output in this case should not be set up for immediate processing or repeat output should be allowed.

[Former Member]

Hi Veni,

Put a breakpoint somewhere in FM SD_IDOC_INPUT_PICKING, jst before routine 'perform sdpiid01_verarbeiten using idoc_nummer'. This routine call the user exit. In case of return <> 0, this routine will be skipped.

Also check if the user exit is activated(Just a thought)

Cheers,

Vikram

Pls reward for helpful replies!!