Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

External debugging from Informatica

Former Member
0 Likes
635

Hi Experts,

We have an RFC being called from Informatica workflow using SAP user 'INFAUSR'. How do I perform external debugging for this RFC, I mean other than setting External breakpoint in RFC, is there something I need to do? I want to debug the RFC code when the Informatica workflow is run.

Thanks,

Leena

1 ACCEPTED SOLUTION
Read only

Clemenss
Active Contributor
0 Likes
533

Hi Leena,

you can put an endless loop in the called function, i.e.

data x.
while x is initial.
endwhile.

When workflow gets called, it will hang in this enless loop. SM50 you can see the process eating time. Debug process from here, set x tp 'X', exit the loop and debug step by step.

A better way that will not stop any process is the creation of a checkpoint group (transaction SAAB). In the function module code you can use statement

LOG-POINT ID group
          [SUBKEY sub]
          [FIELDS val1 val2 ...].

to log values for certain fields of interest. It is helpful to use a timestamp as subkey because otherwise the logs get overwritten by subsequent calls.

The advantage is you can activate/deactivate log-points for individual users and servers.

In SAAB you can check the results logged - quite easy to use.

Only SAP system parameter default for size of log entries is usually by far too small if you want log internal tables and structures. If you will notice a scissors icon in the log display, ask system admin to set size to 16k or so.

Regards

Clemens

2 REPLIES 2
Read only

ChandrashekharMahajan
Active Contributor
0 Likes
533

Hi,

I guess if the user has same user id in both informatica and SAP then just setting external breakpoint will work. the control will stop in your RFC.

Thanks,

Chandra

Read only

Clemenss
Active Contributor
0 Likes
534

Hi Leena,

you can put an endless loop in the called function, i.e.

data x.
while x is initial.
endwhile.

When workflow gets called, it will hang in this enless loop. SM50 you can see the process eating time. Debug process from here, set x tp 'X', exit the loop and debug step by step.

A better way that will not stop any process is the creation of a checkpoint group (transaction SAAB). In the function module code you can use statement

LOG-POINT ID group
          [SUBKEY sub]
          [FIELDS val1 val2 ...].

to log values for certain fields of interest. It is helpful to use a timestamp as subkey because otherwise the logs get overwritten by subsequent calls.

The advantage is you can activate/deactivate log-points for individual users and servers.

In SAAB you can check the results logged - quite easy to use.

Only SAP system parameter default for size of log entries is usually by far too small if you want log internal tables and structures. If you will notice a scissors icon in the log display, ask system admin to set size to 16k or so.

Regards

Clemens