File Adapter to Proxy abap

[Former Member]

Hi all

I´m developing a file to proxy abap scenario. My XI is 3.0 sp 15 6.40 and the ABAP proxy is in an R3 system wich is in 6.20.

In the cc i have set the protocol parameter as XI 2.0

But is not working fine I can see this error in the SXMB_MONI in R3 system:

<SAP:Code p1="UNCAUGHT_EXCEPTION" p2="ZXICL_MI_EVENTOS_NO_DETONADOS" p3="EXECUTE_SYNCHRONOUS" p4="">APPLICATIONCALL.DYNAMIC_CALL_FAILURE</SAP:Code>

<SAP:Text language="EN">Unable to execute the dynamic application call (kernel error ID UNCAUGHT_EXCEPTION, class ZXICL_MI_EVENTOS_NO_DETONADOS, method EXECUTE_SYNCHRONOUS)</SAP:Text>

I was wondering if there is something with the version of 6.20 and 6.40

Many thanks

Regards and Happy new year to all!!!

Noelia

[Former Member]

The most important think is to know the Service Pack of the R/3 system 6.20.

Can you tell us ?

Did you also activated the proxy successfully (class ZXICL_MI_EVENTOS_NO_DETONADOS) ?

Regards,

Sandro

[Former Member]

Hi Sandro

+The most important think is to know the Service Pack of the R/3 system 6.20.

Can you tell us ?+

SAP_BASIS 620 0050 SAPKB62050

SAP_ABA 620 0050 SAPKA62050

SAP_APPL 470 0024 SAPKH47024

EA-GLTRADE 110 0006 SAPKGPGA06 SAP R/3 Enterprise Global Trade

EA-HR 110 0010 SAPKGPHA10 SAP R/3 Enterprise AddOn HR

EA-PS 110 0020 SAPKGPPA20 SAP R/3 Enterprise Public Services

EA-RETAIL 110 0006 SAPKGPRA06 SAP R/3 Enterprise Retail

APPINT 200_620 0006 SAPK-20006INAPPINT SAP Exchange Infrastructure 2.0

ST-A/PI 01G_R3_470 0000 - Application Servicetools for R/3 470

Sorry but I´m not a basis person I´m a developer.....

Did you also activated the proxy successfully (class ZXICL_MI_EVENTOS_NO_DETONADOS) ?

yes I did

Many thanks for your help

[Former Member]

Can you verify also the Kernel Patch (disp+work) level ?

You can ask to basis admin or check by yourself from SM51 in the backend.

Regards,

Sandro

[Former Member]

I have asked to my basis admin and he told me that the kernel of my R3 system is

Kernel 6.40 pach level 71.

Many thnaks!

Regards

Noelia

[Former Member]

Probably the basis admin refere to the XI system that is 6.20, but we are speaking about the back-end, that would be 6.20.

Please ask again.

Sandro

[Former Member]

hi sandro

I have checked by myself now in the SM51 in the button release info.

in my R3 system

The kernel is 6.40 and the pach level is 139.

and also I have checked it in my XI system and

The kernel level is 6.40 and pach level is 101

Regards

Noelia

[Former Member]

SAP ended the maintenance for the 6.20 Kernel as the 6.40 Kernel is fully downward compatible with the 30.06.2005. Since then no 6.20 patches are avaiable any more.

So we have the 6.40 also in the backend. The patch 139 is not very old, we can assume that the problem is not here.

My suggestion is to try to debug the ABAP proxy, as explained in the document

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3dfac358-0d01-0010-5598-d4900e81a30c">How To… debug XI applications</a>

Regads,

Sandro

[Former Member]

Ok many thnaks

I still working on it?

regards

Noelia

[Former Member]

I suggest to make a debugging of the ABAP proxy in the backend, in order to understand what makes the message fail.

Have you checked the transacitons SM21 and ST22 in the backend ?

Sandro

[Former Member]

Hi,

Please can you check on the following property of the XI adapter:

http://help.sap.com/saphelp_nw04/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/content.htm

You set up the HTTP destination in the SAP system by using transaction SM59. Use the following path prefixes in the Target System Settings.

/sap/xi/engine?type=entry

for SAP systems based on SAP BASIS 6.40 (XI 3.0 message protocol).

/sap/xi/engine?type=receiver

for SAP systems based on SAP BASIS 6.20 (XI 2.0 message protocol).

2. Please debug and see that the code is correct.

Regards

Vijaya

[Former Member]

hi vijaya

I have check it and is right

I have set /sap/xi/engine?type=receiver

for SAP systems based on SAP BASIS 6.20 (XI 2.0 message protocol).

many thanks

noelia

[Former Member]

Hi Sandro

I cannot see the link for the debug. I have check the ST22 and is nothing there. about the SM21 I have no access.

Regards

Noelia

[Former Member]

Noelia, the text in blue is a link to the document:

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3dfac358-0d01-0010-5598-d4900e81a30c">How To… debug XI applications</a>

here in clear text:

https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/d...

Sandro

[Former Member]

Sorry this was about my english, i meant that the link is not working.

But is working now!

Sorry for be so stupid

Regards

Noelia

[Former Member]

Hi,

please go through the configuration guide:

For business systems based on SAP Web AS 6.20:

You have installed the XI Add-On in each of these business systems as described in the Installation Guide – SAP Exchange Infrastructure 2.0.

• If you want to generate new ABAP proxies on your business systems based on SAP Web AS 6.20: Use SAP Web AS 6.20 kernel patch level 1253. See SAP Notes 675441 and 721160.

• The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).

Regards

Vijaya