cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

XML Messages Monitoring error

Former Member

on ‎02-05-2009 7:29 AM

0 Kudos

Hi Experts,

I have created a scenario in SAP XI in which an XML file is picked from an FTP server & then this file data is sent to SAP ECC system via IDOC, but the problem is that in SXMB_MONI (on XI server) i am getting this message status as Checkered flag (succesful) but its Outbound status is showing red flag, i have also cleared the message queue in the XI system but still the error persists, According to you what should be the problem.

Thanks & Regards,

Amit

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
‎02-05-2009 11:39 AM
0 Kudos

Hi Rajeev/Rajesh,

I checked IDX5, there is no error for the message, also i checked SMQ2, here also there is no entry for queue, I had one doubt, i have created a Basic Type Z_HRMD_A07 in system ECC system & Linked it to the message type HRMD_A & then imported this IDOC in XI, but there is no Message type HRMD_A in the XI system & because of this, in WE20, i am not able to maintain Message Type 'HRMD_A' in the Outbound parameters column, so is this a reason for the problem, if so then what should be done???

Thanks & Regards,

Amit

Show replies
Show replies
Former Member
‎02-05-2009 12:18 PM
0 Kudos

Hi,

in XI in WE20 you do not need to configure anything for this IDOC...........log into r/3 and run transaction WE05 and see whether your IDOC is seen there..........then if your IDOC is seen in some scheduled status, then in r/3 in WE20 check for the logical system and in Inbound parameters you will need to add this IDOC for inbound processing of this IDOC.

Regards,

Rajeev Gupta

Former Member
‎04-20-2009 7:03 AM
0 Kudos

Heelo Experts,

This problem has been resolved, in SXMB_ADM under Integration Engine Configuration, i changed the Role of Business system to Integration server, it was Application server.

Thanks & Regards,

Amit Naik

Former Member
‎02-05-2009 10:22 AM
0 Kudos

Hi Rajesh/Rajeev,

I checked the RFC connection, everything seems to be fine, connection is working, also through IDX5 i checked the Trace content, i am a bit confused over this, i will share this content with you, can you pin point the exact problem & let me know what action needs to be taken :-

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

- <!-- Response

-->

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

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external =</Trace>

<Trace level="1" type="T">Receiver agency external =</Trace>

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

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

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

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

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>

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

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

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

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

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

<Trace level="1" type="Timestamp">2009-02-05T10:02:57Z CET</Trace>

</Trace>

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

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

-->

<Trace level="1" type="T">Message-GUID = 7A45CD6CDFF84B0B26AFCED0B12E31CA</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</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">Queue name : XBTI0001</Trace>

<Trace level="1" type="T">Generated prefixed queue name =</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>

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

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

-->

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

<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>

<Trace level="1" type="T">Continue single processing</Trace>

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

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

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

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

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

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

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

<Trace level="1" type="Timestamp">2009-02-05T10:02:57Z CET</Trace>

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

</Trace>

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

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>

- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">

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

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

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

<Trace level="1" type="T">Reading sender agreement</Trace>

<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

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

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

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

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

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

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

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

<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />

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

-->

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

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

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

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

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO0___0001</Trace>

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

</Trace>

<Trace level="1" type="T">Persisting single message for post-split handling</Trace>

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

<Trace level="1" type="T">Going to persist message + call qRFC now...</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">Async barrier reached. Bye-bye !</Trace>

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

</Trace>

<Trace level="1" type="T">Generated prefixed queue name =</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="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

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

-->

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

<Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace>

<Trace level="1" type="T">Continue single processing</Trace>

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

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

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

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

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

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

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

<Trace level="1" type="Timestamp">2009-02-05T10:02:57Z CET</Trace>

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

</Trace>

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

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

-->

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">

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

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

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

<Trace level="1" type="T">Interface Mapping http://clarityPOC OM_Resource</Trace>

<Trace level="1" type="T">ContentType application/xml</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">

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

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

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

</Trace>

</Trace>

</Trace>

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

- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_OUT">

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

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

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

<Trace level="1" type="T">Reading receiver agreement</Trace>

<Trace level="1" type="T">Outbound validation does not take place</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">

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

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

-->

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

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

-->

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

</Trace>

<Trace level="1" type="T">---- Outbound IDoc-Adapter -

</Trace>

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

</Trace>

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

<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>

<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>

<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>

<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>

<Trace level="1" type="T">Sender service pcspsun</Trace>

<Trace level="1" type="T">Receiver service SAPECC6</Trace>

<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>

- <Trace level="1" type="B" name="IDX_XML_TO_IDOC">

<Trace level="1" type="T">Parse XML-BODY</Trace>

<Trace level="1" type="T">Get the Metadata for port SAPEC6</Trace>

<Trace level="1" type="T">Convert one IDoc</Trace>

<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>

<Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>

</Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>

<Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>

- <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">

<Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= EC6clnt100</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

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

</Trace>

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

</Trace>

<Trace level="1" type="T">Async processing completed OK.</Trace>

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

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

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

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

<Trace level="1" type="Timestamp">2009-02-05T10:02:57Z CET</Trace>

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

</Trace>

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

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

-->

</SAP:Trace>

Thanks & Regards,

Amit Naik

Show replies
Show replies
Former Member
‎02-05-2009 10:41 AM
0 Kudos

Hello Amit Naik,

Is any error showed in idx5 .It usually shows lthe list of idocs and their status

Double click on your outbound idoc and check is there any error messges showing.

Rajesh

Former Member
‎02-05-2009 10:42 AM
0 Kudos

Hi,

just to check...........go to SMQ2 and execute it.....are there any entries in any queue....if there is, then process that entry and clear the queue........see if your IDOC reached XI........if there is nothing in the queue, then rerun your scenario with a new file...........see if something gets stuck in SMQ2.......check in R/3 whether the IDOC reached R/3........

if your IDOC structure in r/3 has changed, then update your IDOC in IR and update mapping also......go to IDX2 transaction and update the metadata of your IDOC.

Regards,

Rajeev Gupta

Former Member
‎02-05-2009 7:43 AM
0 Kudos

Hi Rajesh/Madan,

Thanks a lot for your quick reply, the thing is that, when i double click on the message, there i find no error, just the 'Outbound Status' column shows the Red Flag & when i keep the cursor on this flag it shows 'Message has error Status on outbd. side'

Thanks & Regards,

Amit

Show replies
Show replies
Former Member
‎02-05-2009 7:46 AM
0 Kudos

Hello Amit,

I do faced the similar error .waht can you do is here check the idoc data generated and check idx5 it lists you if there is any error in idoc config.

Go to pipeline steps and select trace and check there it will provide the error info.

Rajesh

Former Member
‎02-05-2009 8:16 AM
0 Kudos

Hi Amit,

ask your basis guys to check the type 3 connection from your XI system to R/3 system is working or not in SM59 transaction in your XI system.......i think this connection is not working so your IDOCs are erroring in XI on outbound side and so are not able to reach R/3 system....just make this connection working and re-run your scenario.........then your IDOC will reach r/3 sytem.

Regards,

Rajeev Gupta

madanmohan_agrawal
Contributor
‎02-05-2009 7:36 AM
0 Kudos

Hi Amit,

What is the error message you are getting?

Br,

Madan Agrawal

Show replies
Show replies
Former Member
‎02-05-2009 7:35 AM
0 Kudos

IDoc has not been sent to ECC.

For this check the messag e mapping is fine and able to produce idoc data.

If idoc data has been created check the control record structure and configurations required for idoc is in place.

if you have any specific error then post that

Rajesh

Show replies
Show replies
Ask a Question