Monitoring IDoc Receiver Adapter

Dear experts,
in FILE -> XI -> IDoc scenarios erros are not shown correctly. Neither SXMB_MONI nor RWB shows errors for outbound status of the IDoc when I select for errors. If XI sends an IDoc to another System and the partner for the RFC connection is locked, I only see the error in SM58 or SXMB_MONI (but not in the first column... I have to scroll to the right to see the red flat in column "Outbound Status" and the flag in the first column shows me, that everything is ok).
Is it possible, to configure XI to change the overall status of the message or to show these errors in RWB? It's impractical to use different selections and tools to get all possible errors.
Thanks in advance,
David

Hi David,
Since your scenario is File to IDOC hence if XI has processed the message successfully then you will see the successful flag but as you said if you scroll to the right and there you see a red flag which is also correct behavior because the problem is at outbounding side. So check your configuration again in ID.
Few steps you can varify ....
Check the RFC password has not expired.
Make sure in your receiving system i.e R3, You have setup the partner profile correctly in WE20. Also the Port created in XI which contains the RFC (which connects to R3 system) is working fine.
Also make sure if you have uploaded the IDOC metadata using IDX2 transaction code.
if you are getting any specific error message please let us know.
Secondly it will be not possible to change the standard behvior of Moni to change the overall status of message.
Regards,
Sarvesh

Similar Messages

Overwrite MESTYP in IDoc Receiver Adapter PI 7.1 SP8

Hi all,
can anybody tell me, how i can overwrite the MESTYP field in Idoc Receiver Adapter in PI 7.1 SP 8
BR,
Martin

If you would have read the link you posted, you would have seen that "Apply Control Record Values from Payload indicator" in the receiver IDoc adapter, only overwrites the following fields:
MESCOD
MESCFT
TEST
EXPRSS
STD
STDVRS
STDMES
SNDSAD
SNDLAD
RCVSAD
RCVLAD
REFINT
REFGRP
REFMES
STATUS
DIRECT
OUTMOD
CREDAT
CRETIM
Sorry but it seems that this forum just get's spammed with answers based on superficial knowledge just in order to increase the count on your answers.
Hopefully SAP-Forum admins quickly implements a quality control for forum answers!

IDOC Receiver Adapter

Hi,
We have IDOC receiver adapter and data for control record is fed from mapping. For this we have checked the flags " apply control record" and sender receiver from payload.
Recently we copied our QA system from Dev and while testing the Control records are coming from Dev. We have mapping in place whcih looks at the value of receiver and if it does not match with QA, by default it assignment the dev system as receiver
When i am running the interface this mapping is failing and IDOC of QA is getting DEV Control record parameter.
How doe this receiver/sender value is determined in mapping. I checked the SLD and everything looks good.
I cannot test the mapping as while testings is giving 'Test_SenderService' etc which is expected.
Thanks!

We have mapping in place whcih looks at the value of receiver and if it does not match with QA, by default it assignment the dev system as receive
>>> Can you share the UDF?
Are you reading the system name(System.getProperty("SAPSYSTEMNAME")) to determine the environment of the XI system??
Make sure that updated the logical system names in SLD..

Steps to define correctly IDoc receiver adapter

Hi guys,
I try to set up the IDoc receiver adapter, but I still get error, that adapter is not deefined correctly...
Can you pls send me the info, which all steps I have to do, to have it defined correctly?
Thanx in advance, Peter
Message was edited by: Peter Jarsunek

Guys,
I'm in trouble.. I tried all the things you advised me, but nothing works... I still get the error: Communication channel is not defined correctly.
I have read all the links, but please, understand - I'm not a "SAP" man
Could you please write me step-by-step help, what to do??
e.g. 1, on XI box - SM59 (you have to define RFC connection to target system)
PLEASE!!!!!
10 PTS for YOU!!!
Thanx in advance!!

Monitoring HTTP receiver adapter ?

Hi Guys,
How to monitor the HTTP adapter ? How can we know when any errors in the HTTP adapter ? Do i need to look in the integration engine ?
Thanks,
srini

If there is an error in your reciever HTTP adapter you will find the red flag in XI itself in SXMB_MONI.
To monitor your Receiver HTTP adapter, you need to use the SXMb_MONI itself.
Regards
Bhavesh

Maximum size of XML files and number of IDocs for IDoc receiver adapter

Hi Guys,
We have an XML file to IDoc scenario where XI picks up an XML file with multiple Customer records in it, it does a simple mapping and creates one DEBMAS06 IDoc per record in the XML file. All IDocs are sent in a single file in XML-IDOC format to IDoc adapter which then posts the separate DEBMAS IDocs to R/3.
a) What is the maximum size of XML files that XI can handle with mapping involved ?
b) What is the maximum number of IDocs in a single file that the receiver IDoc adapter can handle ?
The first time this interface runs almost 200,000 Customer records will be exported in one XML file.
Thank you.

Hi,
Well it is difficult to find out the maximum Size of xml messgaes that can be processed by XI and also Maximum number idocs an recevier Idoc adapter can handle.
This totally depends on your production system loads and the limits can be set totally on trail & error basis..
In my heavy loaded production system, i found out that the maximum size of the successfull messages after processing by XI is around 75 MB (seen in transaction SXMB_MONI). Whereas messages with size around 100 MB went into error.
I havent encounter any such limits with respect to Idocs.
I would suggest that you divide your data into smaller chunks and sent it part by part instead of sending it all once since you data size is huge.
You can vary your batch size as per your system load.
Regards,
- Deepak.

IDOC Receiver Adapter, getting Lock Table Overflow to CRM System

Hello SDN!!!
This scenario is for PI to process a file and send to CRM via IDOC. The IDOCu2019s are only being created and not processed until later.
Problem: I am getting a Lock Table Overflow error in method IDOC_INBOUND_ASYNCHRONOUS via sm58 in PI which points to the CRM box.
I have been searching many forums and every solution seems to indicate increasing the lock table, the problem with that solution is we are currently trying to create (not process yet) 80000 IDOCu2019s. This would allocate too much for the lock table.
So my question is this, Shouldnu2019t the lock be released when the IDOC gets created or none the less when a packet of IDOCu2019s via content management (breaking up the file in 1000 increments) finish. The lock table in CRM keeps increasing until all rows from the file, sent via IDOC adapter in 80 messages with 1000 IDOCu2019s per messagein the table are complete (80 separate messages in sxmb_moni).
Background:
IDOC was imported, changed to include unbounded and reimported.
Content Management breaks the file into 80 different segments, thus creating 80 distinct mappings with distinct MessageIdu2019s.
80 IDOC packets are sent to CRM, via IDOC adapter and sm58.
TCODE sm12 in CRM shows the table to keep growing and locks not released until full message is complete.
Any help would be appreciated
Cheers
Devlin

The only way to process the IDOCs in this case is by increasing the "enque/table_size" parameter in order to create the required IDOCs. You can increase the value for this parameter up to 102400 (beyond that can cause performance issues). Since you need to handle 80000, this shouldn't be an issue.
Please refer to the notes below for more information about the lock queue overflow and management.
[Note 552289 - FAQ: R/3 Lock management|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=552289]
[Note 13907 - System error in the block handler, overflow lock table|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=13907]

IDOC Sender Adapter and Receiver Adapter

Hi,
Why we don't require IDOC Sender Adapter to communicate with PI and why IDOC Receiver Adapter is required to communicate with SAP ?
Regards,
J Augastine

Hi,
>>>Why we don't require IDOC Sender Adapter to communicate with PI
you're talking about sender and receiver agreements right ?
as this adapter is based on abap stack - with new functionalities of IDOC adapter
require sender agreement
>>>and why IDOC Receiver Adapter is required to communicate with SAP ?
as we need to put the RFC to the destination system somewhere...
Regards,
Michal Krawczyk

Send Idoc flat file message in JMS receiver adapter

Hello,
I am working on a scenario where we send Delvry 03 idoc from ECC to external system. To external system, we send the whole Idoc in flat file structure through JMS queue. I have used Idoc to flat file program in my interface mapping and have configured JMS receiver adapter with just default Module configs but, I am getting an error in communication channel monitoring for the messages.
Please note that Idoc xml to flat file structure conversion is already done in the mapping, I need to just pass this idoc flat structure in the jms adapter. Hence ther eis no content conversion i nthe adapter..
Please give some inputs..Here are the modules in my receiver adapter and nothing else..
SAP XI JMS Adapter/ConvertMessageToBinary
SAP XI JMS Adapter/SendBinarytoXIJMSService
The error I get is in audit log
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_R:ca336a6689f837da8bd3387140fc4447
in turn the message has this error if I open the message
Whitespace is not allowed at this location. Error processing resource 'http://host:port/mdt/messageconten...
and it shows one of the lines from idoc..flat file
Any idea is greatly appreciated..Thank you..Thanujja

The difference in what I suggest is that it is way simpler.
Maybe you did not understand this, so will try to explain it better. Its not the best thing to do, but if JMS adapter doesn't budge then you can give it a shot.
1. You continue to use the ABAP mapping in your interface mapping to map the Idoc xml to Idoc flat.
2. Write a Java Map that will take the output of the ABAP mapping ; and then create a XML output which would be something like,
<Root>
<Idoc_Flat>
<Data>ABAP Mapping Output<Data>
</Idoc_Flat>
</Root>
3. Now use the simple content conversion in the JMS adapter to convert this to flat file.
Regards
Bhavesh

Wrong port in FTP receiver adapter - no errors in message monitoring?

Hello all
We're on XI 3.0 SP16 and have created / configured a HTTP XML -> XI -> FTP Server scenario. In the receiver comm. channel (ftp) we had specified a wrong port number and always wondered, why we never got errors in message monitoring. Everything seemed to be processed correctly... but no file arrived on the FTP server (receiver) side!
After correcting the wrong FTP port number in the receiver FTP comm. channel everything went fine.
We now encountered a similar problem with a RFC receiver adapter. We're using it in another scenario HTTP XML -> XI -> RFC to SAP R/3 (4.7).
For some reason it died (red status in adapter monitor) and it was no more possible to do RFC calls from XI to SAP R/3 (normal RFC adapter, NO proxies).
In XI message monitor everything seemed to be ok but no message arrived till SAP R/3. Nothing in any queue...
After deactivating and reactivation the RFC receiver comm. channel it worked again BUT ALL PREVIOUSLY SENT messages seem to be lost.
Is it really the way it works? Does XI integration engine at runtime NOT catch whether or not a RFC or FTP receiver adapter died, thus is not able to tell somewhere in message monitor that a message could not be delivered at all?
I'm really confused here but hopefully I simply don't understand some easy principles to take into account...
Our SAP R/3 is on rel. 4.70 with Web AS 6.20. The XI 3.0 plugin is not installed. Do we need to go with server proxies there and use QOS = best effort?!?
Thanks for some suggestions.
Best regards,
Renaud

Hi Michal
Thanks... works great for normal XML based messages!
Now, what if I wanted to pass binary files from one ftp server via BPM to another ftp server in order to enable the transport acknowledgment?
The files polled from ftp server using the ftp sender adapter are all in binary format (ARJ). No xml data in there. How should the message format look like in BPM for the receiving step? Or: how to make sure not to loose the binary content when passing through BPMs?
I need this sort of scenario because of the tansport acknowledgment and because I need to have some sort of message splitting (send the binary file over to a second ftp server and additionally send some kind of info message to SAP R/3 regarding thin binary file).
BTW: in the MessagingSystem/monitor/monitor.jsp I do not see sender / receiver information. Is this normal? It's quite of a bad thing to look inside each message in order to find out what message I'm having in front of me...
Thanks a lot for your support and patience!
Kind regards,
Renaud

Monitoring problem in async SOAP receiver adapter

Hi!
I have a File to SOAP asynchronous scenario.
I want to see in monitoring (sxi_monitor) if problem occured when calling the webservice, for example when the connection is refused, or a timeout.
In Runtime Workbrench, I can see the errors in Communication Channel Monitoring and in Message Monitoring from Component Adapter Engine.
I have configured an alert rule for receiving alerts when an error occured, but <u>I don't receive any alert</u>. And when I go to the transaction SXI_MONITOR in my system XI, the status of the message is <u>"Processed successfully" instead of "System Error"</u>.
Any idee of how to solve this?
Thanks in advance,
Laurence

Hi,
In this link you will find the list of the container elements.
Declare these container elements in your Alert Category, and use them between & CONATINERELEMENT& in your alert text and these will be filled up in the run time.
the link to your message will be added by default in the Post Processing Steps. You need not do anything special for this.
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
Regards
Bhavesh

IDOC as a receiver adapter in XI to 3rd party scenario

Hi All,
I have an requirement to connect sap xi and 3rd party. the scenario as given below:
sap ecc 6.0 --> sap xi --> 3rd party
Here ecc is sending an idoc to the 3rd party. The 3rd party is SAP certified and intelligent enough to receive and send idocs. Here I'm using a idoc adapter as a receiver adapter. In the receiver adapter I have to give a rfc destination and a port name.
My question is how to create a rfc destination for the 3rd party. and which port name we'll use in this case. Is the port name will be the 3rd party port name is yes then how I can create a port in the 3rd party system.
Please help.
Regards,
Santosh

A communication channel with a receiver IDoc adapter can be created automatically for business systems that are defined in the System Landscape Directory. refer this link
[http://help.sap.com/saphelp_nw04/helpdata/en/42/d1a4d665c5574fa6e19784358ec948/frameset.htm]
You need to configure the receiver IDoc adapter to convert Integration Server contents from IDoc-XML to native IDoc format and to forward the IDocs to an SAP system .
you create a port and the rfc destination pointing to receiver in PI system
use tcode sm59 for creating rfc destination and IDX1 to create port and map it to rfc destination.

How to Monitor IDOC Adapter

Hi Frnds,
How to monitor IDOC adapter. Its resides in Integration Engine.
Regards,
Raj

hi,
Adding to above you can refer to this wiki.It has all in fo about Idoc.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/step%252bby%252bstep%252bprocedure%252bfor%252bcreation%252bof%252bidoc
regards,
ujjwal kumar

HTTP receiver Adapter configuration

Hi All,
I want to post an XML message using HTTP Receiver Adapter for my BPM scenario (Idoc to HTTP service)
The receiver has Oracle gateway and it expects message in following format.
HTTP Header
   HttpVersion: HTTP/1.1
   Authorization: Digest username=myusername,
                         realm=[email protected],
                         nonce=dcd98b7102dd2f0e8b11d0f600bfb0c093,
                         uri=/dir/index.html,
                         qop=auth,
                         nc=00000001,
                         cnonce=0a4f113b,
                         response=6629fae49393a05397450978507c4ef1,
                         opaque=5ccc069c403ebaf9f0171e9517f40e41
                         Contentlength: 12345
                         Contenttype: text/html
HTTP Body
   TRANSPORT_PROTOCOL=OXTA
   TRANSPORT_PROTOCOL_VERSION=1.0
   REQUEST_TYPE=SEND
   MESSAGE_ID=A1234567890ZZ0987654321
   MESSAGE_TYPE=XML
   MESSAGE_STANDARD=OAG
   TRANSACTION_TYPE=PO
   TRANSACTION_SUBTYPE=PROCESS
   DOCUMENT_NUMBER=12345
   PARTYID=9999
   PARTY_SITE_ID=8888
   PROTOCOL_TYPE=HTTPSOXTA
   PROTOCOL_ADDRESS=HTTPS://www.me.com/servlets/oracle.ecx.oxta.
   transportAgentServer
   USERNAME=myusername
   PASSWORD=myloginpassword
   ATTRIBUTE1=
   ATTRIBUTE2=
   ATTRIBUTE3=
   ATTRIBUTE4=
   ATTRIBUTE5=
   PAYLOAD=<xml ... ...>
I think this is not a typical HTTP URL type of format, is it?
And I am not sure how I can build the message. Where do I put the parameters like TRANSPORT_PROTOCOL, TRANSPORT_PROTOCOL_VERSION, REQUEST_TYPE etc in the HTTP adapter?
Also is there any place where I can see the final actual XI message that is sent to HTTP service?
Any help will be really appreciated.
Thanks and regards,
Rahul.

Hi Rajeev,
The receiver system should have the details about the content type it expects. I got that from the team who monitors our receiver system.
The HTTP Body of HTTP adapter is made up of PrologPayloadEpilog.
So I added the paramter list that receiver system expects as part of the Prolog. Refer to the HTTP body that I have posted in my earlier message. Out of that till ".....Payload=" is added to Prolog and XI then appends actual payload to it.
To be precise -
TRANSPORT_PROTOCOL=OXTA&TRANSPORT_PROTOCOL_VERSION=1.0&MESSAGE_TYPE=XML&MESSAGE_STANDARD=UNIVERSAL&TRANSACTION_TYPE=XXXE&TRANSACTION_SUBTYPE=ORDER_I&DOCUMENT_NUMBER=PO12345&PARTY_SITE_ID=ESAP_ORDER_I&USERNAME=***&PASSWORD=**&PAYLOAD=
So in the end it worked out well.
Cheers,
Rahul.

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

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">User: RUGE</Trace>
<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="B" name="IDX_IDOC_TO_XML">
<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 level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
</Trace>
<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 = TXI</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = D</Trace>
<Trace level="1" type="T">user = RUGE</Trace>
<Trace level="1" type="Timestamp">2006-03-17T04:42:53Z 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>
<Trace level="1" type="T">Message-GUID = 3B4CA10CF867924D9F60B752E345F378</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>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
</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>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></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:[email protected]"><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

Monitoring IDoc Receiver Adapter

Similar Messages

Maybe you are looking for