cancel
Showing results for 
Search instead for 
Did you mean: 

Urgent

Former Member
0 Kudos

I developed a scenario

for exchanging data from sap to sap with proxiex.

When Iam sending message it is giving success message .

When I check SXI_MONITOR in R/3 system*The flag is green*

In trace I am getting a message as given below.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Inbound Message

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">COMMIT is expected by application !</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = ED1</Trace>

<Trace level="1" type="T">client = 100</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = IBMABAP1</Trace>

<Trace level="1" type="Timestamp">2008-01-14T05:17:04Z CET</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 478AF11CE6B71394E10000000A8439E5</Trace>

<Trace level="1" type="T">PLNAME = SENDER</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>

<Trace level="1" type="T">Queue name : XBTS0001</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTS0001</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="T">--start sender interface action determination</Trace>

<Trace level="1" type="T">select interface MI_S1*</Trace>

<Trace level="1" type="T">select interface namespace urn:godrej-com:Test1</Trace>

<Trace level="1" type="T">no interface found</Trace>

</SAP:Trace>

My sample code is

&----


*& Report ZPT

*&

&----


*&

*&

&----


REPORT ZPT.

Data : Begin of itab occurs 0,

s1(5) type c,

s2(5) type c,

s3(5) type c,

s4(5) type c,

s5(5) type c,

end of itab.

itab-s1 = 11110.

itab-s2 = 11110.

itab-s3 = 11110.

itab-s4 = 11110.

itab-s5 = 11110.

Append itab.

clear itab.

itab-s1 = 11111.

itab-s2 = 11111.

itab-s3 = 11111.

itab-s4 = 11111.

itab-s5 = 11111.

Append itab.

clear itab.

itab-s1 = 11112.

itab-s2 = 11112.

itab-s3 = 11112.

itab-s4 = 11112.

itab-s5 = 11112.

Append itab.

clear itab.

itab-s1 = 11113.

itab-s2 = 11113.

itab-s3 = 11113.

itab-s4 = 11113.

itab-s5 = 11113.

Append itab.

clear itab.

Data : WA_TEST TYPE ZPT_DT_S1_ROOT,

IT_TEST TYPE ZPT_DT_S1_ROOT_TAB,

IT_OUT TYPE ZPT_MT_S1,

Client_Proxy TYPE REF TO ZPT_CO_MI_S1,

SYS_EXCEPTION TYPE REF TO CX_AI_SYSTEM_FAULT,

APPL_EXCEPTION TYPE REF TO CX_AI_APPLICATION_FAULT.

Loop at itab.

WA_TEST-S1 = ITAB-S1.

WA_TEST-S2 = ITAB-S2.

WA_TEST-S3 = ITAB-S3.

WA_TEST-S4 = ITAB-S4.

WA_TEST-S5 = ITAB-S5.

APPEND WA_TEST TO IT_TEST.

CLEAR WA_TEST.

endloop.

IT_OUT-MT_S1-ROOT = IT_TEST.

CREATE OBJECT CLIENT_PROXY .

TRY.

CALL METHOD CLIENT_PROXY->EXECUTE_ASYNCHRONOUS

EXPORTING

OUTPUT = IT_OUT.

If sy-subrc = 0.

Write : / 'Method called successfully'.

else.

Write : / 'Method calling failed'.

endif.

CATCH CX_AI_SYSTEM_FAULT INTO SYS_EXCEPTION.

WRITE : / 'System Exception Encountered'.

RETURN.

CATCH CX_AI_APPLICATION_FAULT INTO APPL_EXCEPTION.

WRITE : / 'Application Exception Encountered'.

RETURN.

endtry.

COMMIT WORK.

But unable to see the message in XI system.

In SXI_MONITOR I was unable to see the message sent.

Please help .

Thanks in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

nikhil_bose
Active Contributor
0 Kudos

hi swapna!!

if the status is in green, there might be chance of queue been locked. go to the queue for the particular message( you can see it by scrolling to right in the SXMB_MONI for the same message and under Queue id), open the queue, see the message there. just discard the queue.

hope this may solve your problem

regards

nikhil

Former Member
0 Kudos

I have checked it .

Not struck in queue.

nikhil_bose
Active Contributor
0 Kudos

hi swapna!

your ABAP part looks fine. but i am not sure about the XI part.

check both the Receiver and Sender SOAP adapters are invoked in the Adapter Monitoring (communication channels).

else,

1. check your receiver channel

2. sender channel which is exposed as SOAP channel

3. Defined the web service in XI

let me know more about XI perspective.

regards

nikhil

Former Member
0 Kudos

Hi swapna

can u tell me wat exactly that u want i mean wat is ur exact problem.

rgrds

venu