Debug Update routine for LIS infostructure S942

[Former Member]

Hey Experts,

I am new to LIS and probably this could be a naive question for you, but I did not get any satisfactory thread on debugging the update rules for LIS.

I have modified a routine (FMCV2942) which supposedly updates Info structure S942. Ideally as per its update rule, it should be triggered while creating the Invoice document for a Outbound Delivery.

I have put break-point there, started update debugging but the control does not stop here. I am even clueless if the routine is called or not.

I did check at few places and all I got was the customizing to generate info structures, field catalogs, update rules etc (tcodes:  MC18, MC21, MC24, OMO1).

I could not find anything relevant here.

Now I am stuck at a place that I am not able to debug and not even find out if the routine is called or not or how should i check it.

Any pointers on debugging the update routines are highly appreciated.

Thanks so much in advance!

Warm Regards,

Shreya

[FredericGirod]

Hi,

maybe you have to generate your routine like those in VOFM using a program like RV80HGEN ?

regards

Fred

[Former Member]

Hi Frederic,

My mistake, i should have mentioned that I have tried this option as well but did not work.

The routine is already active.

Warm Regards,

Shreya

[FredericGirod]

Did you try :

/hs (system debug)

check  update debugging

Save

F8

if a new window open

check update debugging (again) and system debuging (again)

save

F8

sometimes, the update debugging is multi level

regards

Fred

[Former Member]

Dynamic breakpoints help me out when I am not sure whether a routine is getting called or not.

Enter debugging mode and goto Menu > Breakpoints > Breakpoint at > Breakpoint at subroutine.

Include name would be FMCV2942, and subroutine name can be selected from F4 help.

You would have to set dynamic breakpoint twice, once in debug mode, one in update mode.

Another way that can be used, just to be sure, is to write a select query on custom table, and check in ST05 trace whether that table was actually accessed.

[Former Member]

Hi Manish,

Sorry, may be in a haste I forgot to mention. I did try the mentioned steps of putting dynamic break-points but it does not stop there only (though break point is set).

I am not sure what am I missing or if I am checking on the right track only :S.

Best Regards,

Shreya

[Former Member]

Hi Shreya,

Had the same problem - the processing of the routine is done in an update task, so you have to activate update debugging.

Hope this helps.

Mark

[Former Member]

Hi

I had the same issue, and I found a way to 'simulate' the change using DEBUG.  It is a customizing function.

Put a breakpoint in your routine - FMCV2942.  Then execute transaction MCVR.  In my case I enter in the Sales Order and this simulates the update.

Give that a try.

Linda