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!!

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..

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

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

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.

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

Hi! I need steps for HTTP Receiver adapter

My scenario is like this:
HTTP(HTTP Sender adapter)->XI->File(File adapter).
For this Iam sending the data as payload in the body of HTTP. Now What am i going to do is the opposite of above scenario:
File(FileAdapter)->XI->(HTTP Receiver Adapter)HTTP.
I would like to know what are the steps to transfer a file(xml) from File adapter to XI and from there to Http.
How to send the data using File adapter. Please suggest me some steps.
Hoping a quick response!!!
Thanks in advance!

Hi Datta,
For a HHTP -> XI -> FILE Scenario:
DESIGN:
1. Create DataTypes for source and Destinations. Create elements for all the text fields of your HTTP Client so that they can all be mapped into the destination file
2. Create MessageTypes for the two datatypes.
3. Create Message Interfaces. The One for HTTP is the sender, Asynchronous ( as no response is expected) and one for File is receiver, asynchronous.
4. Do the mapping. It will be mostly a one to one mapping of the fields.
5. Create the Interface Mapping.
Configuration:
1. Import your Business System under your Configuration Scenario.
2. Create 2 communication channels. One for Http as a sender and one for File as a receiver.
Check these links for the configuration part.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
3. Do the Receiver Agreement for file. HTTP doesnt need a sender agreement.
4. DO the Receiver Determination and Interface Determination.
Weblog which talk about the same scenario:-
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
(use case) and explained it...
Check this SDN tv demo, it has detail of HTTP adapter setup.
https://media.sdn.sap.com/SDNTV/main.asp?mediaId=107
Refer to this link for adapter settings.
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
You should also have a HTTP client to send message to XI. In the connecting parameters to XI u have to use the URL in the pattern mentioned by Alex. U have to give all the configuration details in the URL.
Regards,
Abhy
Message was edited by: Abhy Thomas

Adapter-specific message attributes for the JMS Receiver adapter

Dear SAP Community,
We are trying to activate some parameters at message level when SAP XI sent an interface (XML data) to IBM Websphere MQ. Programmaticaly, this is done the following way:
       TextMessage outMessage = session.createTextMessage();
       MQQueue replyToQ = new MQQueue("TESTQM01","SYSTEM.ADMIN.ACTIVITY.QUEUE");
       Destination replyTo = (Destination) replyToQ;
       outMessage.setJMSReplyTo(replyTo);
       outMessage.setIntProperty("JMS_IBM_Report_Exception", MQC.MQRO_EXCEPTION);
       outMessage.setIntProperty("JMS_IBM_Report_Expiration", MQC.MQRO_EXPIRATION);;
       outMessage.setIntProperty("JMS_IBM_Report_COA", MQC.MQRO_COA);
       outMessage.setIntProperty("JMS_IBM_Report_COD", MQC.MQRO_COD);
       outMessage.setIntProperty("JMS_IBM_Report_Discard_Msg", MQC.MQRO_DISCARD_MSG);
This code is working fine.
Since the documentation about this feature (Adapter-specific message attributes) is very light, We am not sure about the interpretation we made.
First, we defined the following attributes: MS_IBM_Report_Exception, JMS_IBM_Report_Expiration, JMS_IBM_Report_COA, JMS_IBM_Report_COD, JMS_IBM_Report_Discard_Msg. All of them are with type int.
Then we changed the mapping (XSL) to pass the value to the dynamic configuration, using the technical names (DCJMSMessageProperty0, ..., DCJMSMessageProperty4) and the value of the constants. We also specified a value in the Reply To Queue parameter of the adapter. As a test, We also change another parameter via the mapping (the correlation ID, to use the idoc number) and according to the log of the processed message, every thing is finde. According to the trace of the JMS adapter, everything is fine to. However, this has no impact on the message, only the correlation ID is changed.
The JMS server is IBM Websphere MQ (v6.0.2.1). It is already in production and working fine. This is a change we have been asked to implement.
Has anyone experience with the JMS receiver adapter-specific message attrbitutes ? What have we done wrong ?
Any help is greatly appreciated.
Regards,
Gregory PFISTER
SAP XI Analyst - Holcim

Hi Neha,
pls do chk the below links for SOAP adapter message attributes
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
Regards
Sampath

Configuring a Seeburger FTP Receiver Adapter

Hello,
I am trying to build a scenario where SAP ECC 6 sends an invoice to a customer via EDI.
We are using ECC 6.0 and PI 7.0 and the Generic Seeburger EDI Adapters. The VAN is a GEIS EDISWITCH VAN (Eircom in Ireland).
I am able to successfully send an IDoc from ECC 6 and into PI where a Seeburger map converts the message to EDI-XML format. I can use a file adapter to create a file in normal EDI format. But I can't get the Seeburger FTP adapter to work with the VAN.
I have configured the correct IP, port, username and password but I keep getting the following message when the communication channel tries to send the message:
<h6>Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 501-Syntax errors in parameter. usage: %[recipient id]%[APRF] where either [recipient] or [APRF] can be omitted. (to change your current default SEND relationship). %% (places you in your 'HOME' TR). &['s'|'single'] ('get' command gets single file). &['m'|'multiple'] ('get' command gets multiple files). >> </h6>
The FTP session is expecting a PUT command with the recipient id and APRF as parameters but these are not getting passed. I suspect this is because I am not passing the correct variables to the receiver adapter but I don't know what variables it expects and where they should be specified. And I can't find the answers in the documentation.
Can anyone shed some light on what I need to do?
Thanks,
Ben

Hi Prateek,
Thanks for your comments. The channel is set to GEIS(GeMarkIII). There is nowhere to specify a directory or filename. The settings I have used are as follows:
Adapter Type: FTP (http://seeburger.com/xi)
Receiver
Transport Protocol: FTP
Message Protocol: GEIS/GeMarkIII
Adapter Engine: Integration Server
Host name: <IP address of VAN server>
port: 21
User Id: <Our mailbox number>
Password: <Correct password>
Host path/VAN Partner ID: <blank>
Script file: <blank>
Transfer type: ASCII
Connection mode: Passive
Use keep alive: <Not checked>
Security Mode: None
Proxy Mode: none
Resource ID: <blank>
Deliver transmission report: <not checked>
Payload mode: Attachment
Attachment ID: SeeburgerMain
Channel status: Active
Use dynamic attributes: <Checked>
Use non-empty attributes: <Checked>
Request displayed report: <Not checked>
Request dispatched report: <Not checked>
Report timeout (minutes): 720
Handle received reports: Refer reports to XI system
There is nowhere in the communication channel configuration that allows me to specify the receiver ID or the APRF. The documentation say this is read from the EDI data and the relevant fields are populated.
Any ideas?
Thanks,
Ben

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

Dynamic URL in SOAP Receiver adapter

Hi all,
I have a scenario where I am using a SOAP receiver adapter to send a cXML document to some vendors. I need to change the URL based on the vendor number (passed by sender SRM system). So I have created a user-defined function and used in message mapping to assign the right URL to the variable TServerLocation. But the communication channel still prompts for a static URL which appears to be a mandatory field. Even though the DynamicConfiguration tab in Message Monitoring shows that the TServerLocation was correctly assigned, the scenario does not work when I put some dummy in the static URL field like 'dummy' or '*'. Any ideas on how to make the communication channel go for the dynamic URL field and ignore the static URL field? I have already selected the'Use Adapter Specific Message attributes' and 'Variable Transport Binding' check boxes. Am I referring to the correct variable that references the target URL? Also other than the two checkboxes that I mentioned, I am not displayed anything else under "Adapter Specific Message Attributes" section in the comm. channel.
Thanks

James,
I ve just been digging into SAP help, and have tried it too ... Looks like it doesnt work the way it is supposed to.
Anotheer point i found was, in the FILE ADAPTER, when we say ADAPTER SPECIFI ATTRIBUTES , we can select the attirbutes.. This is not possible in a SOAP adapter...
Maybe, we can only access the ADAPTER SPECIIFC ATTIRIBUTES of a SOAP adapter, but cannot set them dynamically.
Let me know if you find something on this issue.
Regards,
Bhavesh

JDBC Sender/Receiver Adapter Configuration with key fields in SAP XI

Hi All,
Good evening.
Please let me know, what are the settings required for key fields when configuring both sender and receiver Adapter?
In My IDOC-XI-File Scenario, when i am sending an IDOC from R/3, I got Mapping Runtime exception error? So, How to send the same IDOC after correcting the error?
Thanks to all in advance.
Regards,
Nagarjuna.

HI Nagarjuna,
If my understanding is correct, When you trigger the Idoc from R/3 it thrown the error in XI.
If you want to send the same Idoc then go to WE19 in R/3 system enter the same Idoc number and execute the scenaio. It send the Idoc to XI system, but the message number will change.
Regards
Goli Sridhar

Steps to define correctly IDoc receiver adapter

Similar Messages

Maybe you are looking for