Need to debug a bapi by putting external break point

[Former Member]

Hello ABAP gurus

One of our applications is interfaced with SAP using .Net Connector and it calls a standard BAPI.

Since all the data that are sent from our application is not getting updated in SAP tables I want to debut the BAPI.

The ERP server on which this BAPI resides has 4.7. My client SAP Logon PAD is 6.4. When I tried to connect from my SAP Client Log Pad and opened the bapi using SE37, I just see a Stop button that says Internal Breakpoint. When I put a break point using this button and make our application call this BAPI, it is not stopping at the break point.

As a test, I connected to another test ERP server which has the latest version (ECC), I can see 2 stop buttons (one says internal break point and another one says external break point).

However, since the client is using the older version (4.7) how can I put the external break point to debug and findout if the data is reaching the server properly.

Any feedback or suggestion will be highly appreciated.

Thanks

|Ram

Edited by: Ram Prasad on Dec 11, 2008 5:30 PM

[Former Member]

Try with

SE38-> From the top menu > utilities> settings> debugging tab>put your id and check "session break point active immed"

a®

[former_member194669]

Try with

SE38-> From the top menu > utilities> settings> debugging tab>put your id and check "session break point active immed"

a®

[Former Member]

Hi Ram Prasad

Just check if you can use this technique to debug to your RFC call in 4.7 version.

Although this is method if used for debug R/3 while calling the BAPI from XI.

and check this link for the explanation of this technique:

Neha

Edited by: Neha Shukla on Dec 11, 2008 10:33 PM

[Sm1tje]

Before trying to debug, answer a few questions:

1. Data is not being updated, did you get an error message in the return parameter which is provided by 'all' BAPI's and has structure BAPIRET2?

2. Did you check the dump logs in transaction St22?

3. Did you also call BAPI_TRANSACTION_COMMIT?