Solved: IDOC Receiver determines no receiving service

Hi,

I have send an R/3 IDOC successfully to XI and find the messag with status OK in the monitor, even the receiving service and the receiving interface is empty.

I have configured a message interface and the receiver has an appropriate communication channel using SOAP. In the repository there is a defined receiver and even in the SXI_cache I can see the receiver.

Has anyone an idea?

Thanks

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Volker,

the cache is OK, here is the data form the monitor:

Date Time sender Namespace sender Sender Interface Receiver Rceiver Interface

17.03.2006 05:42:53 SAPR3 urn:sap-com:document:sap:idoc:messages REQOTE.PORDCR04.YFUTURA

and here is the SOAP header of the message:

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

<Trace level="1" type="T">Language: D</Trace>

<Trace level="1" type="T">XML-Conversion for all IDocs </Trace>

<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling </Trace>

<Trace level="1" type="T">IDoc-Inbound-Handling </Trace>

<Trace level="1" type="T">Syntax-Check-Flag X</Trace>

<Trace level="1" type="T">IDoc-Tunnel-Flag </Trace>

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

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

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

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

</Trace>

<Trace level="1" type="T">Set Receiver Routing-object </Trace>

<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB </Trace>

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

</Trace>

</Trace>

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

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

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

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

<Trace level="1" type="T">Message-GUID = 3B4CA10CF867924D9F60B752E345F378</Trace>

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

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

</Trace>

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

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

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

</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-776FED7FF7A6634D8BEB10F4A04B3B50@sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>

I dont know how to increase the trace level, so ists still 1.

Thanks

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Jürgen!

As you can see again, no receiver service and no rceiver interface can be found.

To increase the trace level select a message in SXMB_MONI and press button "Restart". You will then be asked whether you want to increase the trace level.

Unfortunately the SOAP Header you've sent is not helpful. It just covers the inbound message and nothing else ... the next steps would be the exciting ones ...

Once more the question:

At wich point does your message processing chain end (see my last post).

Maybe it is the best if you make some screenshots of the message and send it to my via email to volker.kolberg@btconsult.de

If I then cannot help you you should open an OSS Call, because for me the next step would be to login into your system and to have a look at the situation. Because this is not possible for me but for SAP, this would be my suggestion.

Regards,

Volker

... and additionally some screenshots of your Integration Directory settings:

Receiver Determination

Interface Determination

Receiver Agreement

SOAP Receiver Comm. Channel

Regards,

Volker

Answers (9)

Hi,

there are two products, the most important is from the vendor Tobit.

Regards

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi all,

thanks for the help. In the end only the qRFC inbound queue was not working properly. Now I only have the problem with the content type in the SOAP Outbound interface.

Beste Regards

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Jürgen!

As you wrote me all your problems are fixed now.

Thanx for the points.

Regards,

Volker

Hi,

in the monitor I have a green flag, not a black white one. In the adapter monitor I find no message!

In the integration engine monitor I find this:

Attribut Value

Status zu senden

Wiederholbar Ja

Beendbar Ja

Start 17.03.2006 09:52:15

Ende 17.03.2006 09:52:15

Sender-Partner

Sender-Service SAPR3

Sender-Interface urn:sap-com:document:sap:idoc:messages

REQOTE.PORDCR04.YFUTURA

Empfänger-Partner

Empfänger-Service

Empfänger-Interface

Quality-of-Service Exactly Once

Message 932978FC2B01F5459ED6FCD1DB8A1AC9

Referenz

Eingang IDOC

Ausgang

Queue XBTI0007

Pipeline CENTRAL

Acknowledgment-Status 000

Vater-Message

Fehlerkategorie

Fehlercode

Message-Typ A

Ausgangsstatus 000

Anzahl Kinder 000

Mandant 100

Benutzer RUGE

Anz. Wiederh. 000

Restart-Version 000

Request-Message

Thanks

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi!

As you can see here ...

Empfänger-Service

Empfänger-Interface

No receiver service and no receiver interface is found for this message. Please check again that you have defined and activated a:

- receiver determination

- interface determination (unconditional or with conditions that come true)

- receiver agreement

Are all these objects activated and visible in the SXI_CACHE.

In the SXMB_MONI detail view for that message, what do you see on the left side? Is there?

1. Incoming Message with a green flag

2. Receiver Determination

3. Interface Determination

4. Receiver Grouping

5. Mapping

6. Technical Routing

7. Adapter Call

and so on ...

Where is this chain broken on your site. Please send the SOAP Header Main part of the last visible step. The best is if you use the "download" option in the context menu of such a message. This will download the whole message to your PC and then you can paste it into this thread.

But before doing that please try to restart the message and increase the trace level and then use that message.

Regards,

Volker

Hi,

the scenario is as follows:

- A own written IDOC from R/3 is send to XI

- There is a mapping in XI which is transparent

- The IDOC should be send to a 3rd party system using the SOAP adapter

The SOAP system is defined as business system and in SLD there is a technical and a business system and in the Directory the I have configured the whole interface determination

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Okay.

And I've understood correctly that in the SXMB_MONI all messages have a black-white flag?

Please try the following: Use the RWB and click on Message Monitoring. First try to find the message in the Integration Engine and have a look at the final status. Then try to find the Message in the Adapter Engine and have a look at the final status.

Copy and Paste these infos into this thread.

Additionally one question:

Did you configure and activate a receiver agreement for the SOAP receiver?

When a Adapter is grey then normally no receiver/receiver agrement is defined for that adapter.

Regards,

Volker

Hi,

I am not using BPM and of course I have in the monitor only one row. I know that I will get the second row onl if a receiving party will be invoked but this is not filled yet.

Thanks

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

the SM58 queue is empty. The receiving Adapter is grey, so no error but also no message.

Any ideas?

Thanks

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Jürgen!

Sorry, but now I have a problem. Could please once more describe in short words your scenario and where exactly the message hangs?

Who and what is the sender and who and what is the receiver?

Thanx!

Regards,

Volker

Hi,

in sxmb_moni there is no error, just no receiver found.

Also the IDOC type in IDX5 and in the interface determination is spelled totally equal.

How can I see in RWB if the receiving communication channel is working?

Thanks

Juergen

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Juergen!

To start the Adapter Monitor within the RWB use Component Monitoring and then select the Adapter Framework. On bottom part of the screen at the right side a button "Adapter Monitor" appears. Click on it.

To further investigate your problem also have a look at the message monitoring in the RWB, because the SXMB_MONI only covers the ABAP part of the lifetime of a message while the RWB also covers the J2EE part.

Also have a look at transaction SM58 whether any tRFC entries are hanging.

Hope this helps!

Regards,

Volker

Hi,

>>How can I see in RWB if the receiving communication channel is working?

Go to runtime workbench->Message monitoring->Integration engine.

Check your receiver determination. How many rows can you see in the moni? Are you using any BPM?

Regards

Suraj

Juergen,

Can you please check one more time, what is the IDOC type you are sending and for what IDOC type you have configured the recievers?

Some times it may happen that you have configured for MATMAS04 and the incoming IDOC type is actually MATMAS01.

Regards,

Ravi

Note : Please reward the helpful posts.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

just check in the sxmb_moni for any error message.when u double click on ur message in the sxmb_moni a screen will appear where u can trace out the error.

i think there will some issues with ur receiver determination else goto runtime work bench and see whether the receiver communication channel is working or active.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count

IDOC Receiver determines no receiving service

Accepted Solutions (1)

Accepted Solutions (1)

Answers (9)

Answers (9)

SAP Analytics Cloud for planning - Set Advanced Fi...

Problem with Select-Options

Re: I am using exit_saplkedrcopa_001 for enhanceme...

SAP build action - 403 error for POST API call wit...

Re: Table DDNTF is not active in the dictionary er...