Problems with ABAP Proxy

[Former Member]

Hi all,

i am trying with scenarion to send the data from R/3 to File using ABAP Proxy's .

the report at r/3 side is working fine even the data is also being filled in the table.

i have not done any adapter specific settings (from the sender's side).

My message is not getting displayed in the SXMB_MONI.

what could be the problem , please tell me if i have to do any other configurations.

Thanks in Advance,

Kishore Kumar Yerra

[Former Member · Accepted solution]

Hi,

did you see the Messages in sxmb_moni from the sending R/3 System ?

Or you don`t see the Message in both Monitorings ? R/3 and XI ?

Did you test to execute the Outbound proxy manual from transaction sproxy?

Regards,

Robin

[Former Member]

Hi Kishore,

did you test the proxy out of SE80 testing function?

Regards Mario

[MichalKrawczyk]

hi,

1. did you generate the proxy class from SPROXY

on your R3?

2. do you see any exception when you're calling the send

method of the proxy?

3. did you register the queues on R3 ? via SXMB_ADM ?

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member]

Hi,

1.) i tried sxmb_moni in both R/3 and XI but both doesnt give me any results.

2.) in the report program i have removed catch exception then it is giving a runtime error.

runtime exception ( UNCAUGHT_EXCEPTION CX_AI_SYSTEM_FAULT)

Below is the report program that i was using.

-

---

-

---

REPORT ztkish_abap_proxy .

DATA prxy TYPE REF TO zco_mioa_file_input_proxy.

CREATE OBJECT prxy.

DATA it TYPE zmt_file_input_proxy.

TRY.

it-mt_file_input_proxy-detail-name = 'Sravya'.

it-mt_file_input_proxy-detail-lname = '80101'.

it-mt_file_input_proxy-detail-address = 'NetWeaver'.

CALL METHOD prxy->execute_asynchronous

EXPORTING

output = it.

commit work

.

• CATCH cx_ai_system_fault .

• DATA fault TYPE REF TO cx_ai_system_fault .

• CREATE OBJECT fault.

• WRITE 😕 fault->errortext.

*ENDTRY.

[MichalKrawczyk]

hi,

but did you generate the class via transaction SPROXY

on your R3?

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member]

Hi,

yes i have generated through sproxy only.

Regards,

Kishore Kumar Yerra.

[MichalKrawczyk]

hi,

then it has to either work or send an exception

are you sure you checked SXI_MONITOR on your <b>R3?</b>

Regards,

michal

[Former Member]

And it didn`t work when you test to execute it from sproxy direct?

Regards,

Robin

[Former Member]

Hi,

how do we test from sproxy,

Regards,

Kishore

[Former Member]

Use the Test Button or F8 !

Regards Mario

[Former Member]

hi ,

when i run the report and if i dont handle exception it is giving a run time error as i said earlier.

i checked the sxi_monitor in R/3 also but no messages.

Regards,

Kishore Kumar Yerra.

[Former Member]

Hi,

try in sproxy to execute the outbound interface. Not with your report.

Select the interface on the left tree menu and press f8 or use the button like mario said.

look as well in sxmb_adm of the R/3 System if the specific configuration for integration engine are set for monitoring.

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions a look at me!</a>

maybe there are messages but you don`t see them

Regards,

Robin

[Former Member]

Hi Kishore,

I also used this report.

Activate the catch block!

As you can see in the coding, the report gives a hint what went wrong in the catch block:

>>>WRITE 😕 fault->errortext.<<<

But if fault->errortext = BLANK, you will not see, that the report went into the catch-block.

Accomplish your coding:

WRITE 😕 fault->errortext.

WRITE 😕 'ERROR OCCURED'.

Regards Mario