IDoc Adapter 151 - Transaction aborted

Hi fellows,
after patching our XI-System to SP19 we try to do a new IDoc2File Szenario. We have one from the old XI-Level which runs really good. It's going from external R/3 to our XI server into the file system.
the new scenario has some selfmade IDoc and i already checked EVERYTHING (we20, we21, sm58, sm59, idx1, idx2, idx5, sm21) Following i give some hints what kind of problems i see. perhaps u can help me?!
in the sender-system:
sm58: IDOC_INBOUND_ASYNCHRONOUS, some mistake in IDX1 saying RFC-Destination is corrupt. But i can successfully use the remote login and the connection test.
in the receiver system:
idx5: nothing displayed concerning the new szenario
sm21:Transaction aborted IDOC_ADAPTER 151
I have no clue what it can be, has someone had same experiences?!
thx best regards, Jens

Thx!
> From SE91 the error message IDOC_ADAPTER 151 means:
>
> Short Text
> Transaction IDX1: Port &1, client &2, RFC destination
> &3 contain error
>
> Diagnosis
> Transaction IDX1: Port &1, client &2, RFC destination
> &3 contain errors
>
> System response
> You tried to fetch the metadata for the current IDoc
> from the reference system, using RFC.
>
> In doing so, an error occurred that was caused by one
> of the following:
>
> 1. You have not yet assigned a port/client to the RFC
> destination.
>
> 2. You have not yet created the RFC destination or it
> contains errors.
>
> 3. The target system is unable to receive.
>
> Procedure
> 1. Check your RFC destination in transaction SM58.
>
Yes, SM58 in the sender system says an error concerning IDX1. RFC destination is wrong - BUT it's all working fine. in case of reading the metadata i also configured IDX2 in XI System to get the metadata in advance. RFC remote login and Connection test runs fine!!
I have no clue again because when i use WE19 with the old IDoc-Scenario and the SAME parameters of sending the IDoc it's working, with the new one it doesn't.
some ideas
null

Similar Messages

Connecting of an external system by IDOC adapter

Hello everybody,
we want to connect an external (storage) system to XI by IDOC-Adapter.
In a scenario without XI the R/3 backend triggers the external system by RFC-Call (TCPIP-conncetion) and an program on the external system is called. This program executes an RFC-call on the R/3 to get the IDOC-informations.
IN the new scenario (with XI) the R/3 Backend sends the IDOC information to XI. The XI routes this to external system. An TCPIP-Connection is needed which calls the program from the external system.
But how should this work? The program can not (or should not) call the R/3 Backend directly but the XI.
What has to be done now? Has the program of the external system changed so that it can understand IDOC-structure directly?
Or do I have to implement a business process scenario to guarantee that the external system reads the IDOC data in XI (similar to "old" scenario?
Thanks a lot!

HI everybody,
thank you very much for your help. Now it es possible to send an IDOC from R/3 Backend and IDOC-Adapter via XI to an external system using the IDOC-Adapter.
But now the external system wants to send IDOCs back. So the communication is realised by using the IDOC-Adapter again. In this case we do not get the messages in XI. The conncection is ok (we see this in the Gateway), but the system gets an error in IDOC adapter (sys-log):
Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )LFS = external system (AS400).
In the RFC-Trace we find following information:
 **** Tra
Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )ce file opened at 20060223 111414 W. Europe Stand, SAP-REL 640,0,109 RFC
======> Der Funktionsbaustein "EDI_FILL_SYIDOC01_FOR_RFC" ist nicht vorhanden
ABAP Programm: SAPLIDX1 (Transaction: )
Called function module: EDI_FILL_SYIDOC01_FOR_RFC
User: RFC_USER (Client: 910)
Destination: C01 (handle: 3, , {C322581B-EB47-43E7-87D7-4607C2873828})
SERVER> RFC Server Session (handle: 1, 95896538, {43FD899F-8993-0202-E100-00000A
SERVER> Caller host: LHMAS40A.INTRANET.SYS
SERVER> Caller transaction code: (Caller Program: SAPCPIC)
SERVER> Called function module: ARFC_DEST_SHIP
Can anybody help us?
Thanks a lot!
Florian

XI 3.0 IDoc Adapter Problem

Hello,
I have a problem to establish an Idoc communication between SAP R/3 4.70 and SAP XI 3.0.
Following systems I have defined in XI SLD:
Sending R/3: HS3CLNT100
Receiving XI: X30CLNT100
In the Idoc (type orders) the sending port is "SAPHS3".
I have configured the XI 3.0 IDoc Adapter as follows.
- IDoc Port "SAPHS3"
- I have loaded the IDoc Metadata
- ALE Distribution model in sending R/3 is defined
- In the Integration Directory I have defined a "service"
This was done by upload an existing business system
"HS3CLNT100" including the automatic generation of
communication channels.
This should "normally" be all, what I have to define.
PROBLEM
========
When SAP R/3 tries to send an IDoc into SAP XI it will fail. In SAP R/3 transaction SM58 I can see following message:
"No service for system SAPHS3 client 100 in Integration Directory"
I don't think, it's normal to configure XI business systems with the same name as the IDoc port!?
Thanks in advance
Klaus

Hi James,
yes in the IB (Configuration) I have generated a service under "services without partner". Service name is "HS3CLNT100" and he includes the generated receiver channels. Or do you mean something different?
Klaus

IDOC adapter question

I am trying to set up a simple file to IDOC transaction ( as a poc ), and I think that I havent configured my IDOC reciever channel properly. I used IDX1 to get the port, and RFC destination information. When I used the wizard, it said that the channel configuration was not complete, so I tried creating it manually. I am able to create and activate it without getting any errors. However, when I send my Idoc message, I get the following error in my message:
<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
I am guessing that my channel is what is screwed up. Any ideas or tips ? I noticed that in the adapter monitor of Runtime workbench, there is no entry for an IDOC adapter monitoring. Where else can I look to find specific errors ?
Thanks
Osman

Thanks Chris,
I got into bd54, and the LS are already configured. So I tried to set up the Business system with the "Adapter-Specific Identifier". But the Logical system box is greyed out, so I cant enter anything. The only box that is editable is the Marketplace Adapter entry.
Any idea what Im doing wrong...
Thanks
Osman

Error in call of IDOC adapter

Hi!
I am facing with very strange IDOC error in adapter call.
Can some one help me to solve this problem please?
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thank you very much!
regards
Thom

I hope you have loaded the IDOC Metadata in IDX2?
Please check the SAP Note 940313 the problem C in this Note (Below are content)
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
 Activities in sender system ABC:
 Transaction SM21 contains entries for failed logons.
 Activities in the central XI system:
 Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
 In Transaction SM21, you will find entries relating to authorization problems and more exact details.
 Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
 In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
 The most common errors are:
 - IDoc type or segments not released
 - Segments that no longer exist are listed in the IDoc type
 - Data elements that do not exist in the DDIC are assigned to fields
 in the segment.
 Contact your system administrator and correct these errors in the IDoc type.

Issue about IDoc Adapter Receiver Channel's Performance

Hi Everyone,
Currently, I am working on a scenario of File -Integration Process - IDoc in XI 3.0 with patch level 16. The scenario works fine when it process one/two/three files in parallel, and the IDocs arrive R/3 system quite fast. But when I try four files in parallel, the whole XI server blocks, I can not do anything even logon Integration Builder, and the IDocs arrive R/3 brokenly, sometime with the invterval to 10 minutes. When the XI comes back, I found all the four integration processes finish successfully and each transaction works fine and fast. What's more, after I change the IDoc Adapter receiver channel to a File Adapter receiver channel, it works fine for even 20 files in parallel. So I think it is some issue about IDoc Adapter receiver channel. Does anyone have the same experience as me? Any comments will be appreciate.
Regards,
Nick

Hi Nick,
Can you check this Blog-
/people/sreekanth.babu2/blog/2005/01/05/delayed-xi-message-processing
May be useful.
How are you picking the files .. You can try with EOIO options while picking the file.
But if you use BPM, it is not applicable. It will act as a EO only.
Check this SAP Note- 833740
Thanks,
Moorthy

IDoc-Adapter Monitoring

Hi,
I know the transaction "IDX5". There are sender-information and receiver-information from the xml-message. In this monitoring the settings are correct but when I look in R/3 for example the sender-information of the message are different in comparison to the sender-information from the transaction "IDX5".
Is there a IDoc-Adapter Monitoring that shows the sender- and receiver-information which arrived to the R/3-System??
Thanks.
Regards.
Stefan

Hi,
For IDocs, to trace Idoc error the transaction you can use is IDX5, SM58 in the XI systema nd SM58, We02 in the R/3 system.
If you see the outbound Idoc in the IDX5 and not in R/3 that means either the RFC destination is wrong or the Control record data is wrong.
You can check for error in SM58. If no error then there is something wrong with control record data
Regards
Vijaya

Configuration Problem on IDOC Adapter

Hi,
I am trying to configure the IDOC Adapter and am badly stuck.
On the sender system: I have configured
-RFC destination, ports and partner profile.
- I have also configured the SLD as per documentation
On the Integration Server:
-RFC Destination, Port maintanence(IDX1.
- Imported Metadata (IDX2)
My IDOC is getting created and is being sent properly, I can see that in WE02
But I cannot see it in Integration Server using transaction IDX5.
Please help.
Regards
Ramesh

Ramesh,
Try to refresh the cache
in Xi using transaction SXI_CACHE > delta Cache refresh.
Then go to Integration Server and Environment Cache Notifications.
Status should be green once you refresh the cache.
This may look a bit silly, but it worked for us.
(We used to get errors with SXI_CACHE in XI3 Service pack 9. Then we followed the steps of Checking Instalaltion part 1 as in XI3 install guide. Once we repeated these steps . SXI_CACHE worked and everything was fine).
To find what exacly is happening, try to send the IDoc from one R/3 to anotehr thro Xi.
The other R/3 will tell you the errors even if it does not show up in SXMB_MONI.
Hope this helps.
Thanks,
BG
Message was edited by: Bhaskar Ghandikota

IDoc Adapter steps??

Hi
I want to use IDoc adapters in the scenario IDoc to File.
I went through the SAP Help IDoc adapter installation.
The steps to be follwed are:
creating Port - IDX1
Loading Metadata - IDX2
and creating the normal configuration for XI.
Please can anyone tell me if we need to do anything more then this?
Regards
Vijaya

Hi Vijaya,
I am not clear where the error occurs, but I am assuming that you have downloaded the metadata in IR, and now you try to download it using transaction IDX2 on XI server, and the error occurs here.
Normally you do not need to manually download the metadata in IDX2. You can leave it now, and finish all your dev and config on this scenario. When you execute it, in runtime, the metadata will be loaded and you will see it in IDX2.
But still the error is strange. Can you please make sure in IDX1, you have config the port name as SAPPDC, and client number is 300, and its RFC destination is a R/3 destination defined in SM59 pointing to client 300?
Regards,
Hart

IDoc adapter inbound channel: Error Error when reading Exchange Profile

Hello Experts,
Currently i am working on an IDOC to file scenario, in which Data will be sent from ECC server (IDOC) to an FTP server via SAP PI, but when i try to send IDOC to PI, i am getting the following error
in Transaction SM58:-
'IDoc adapter inbound channel: Error Error when reading Exchange Profile for system XID and
client 401 occurred in the IS pipeline' .
Can anyone please help me on this.
Thanks & Regards,
Amit Naik

Hello Experts,
Let me explain to you the whole scenario, We have two servers of PI, 7.1 & 7.0. Now the Java Stack of 7.0 is not working & Cache update of 7.1 is not happening.
Thats why we have linked ABAP stack of 7.0 with Java stack of 7.1. Now we can see the objects created under Java 7.1 in ABAP stack of 7.0 (SXI_CACHE).
Now we have done all the settings to create an IDOC to file scenario. All the RFCs are working fine, but when we send an IDOC from the ECC system to ABAP 7.0, we are getting the following error 'Error while reading exchange profile for system NW' in SM58 .
Now can anyone tell me what exact settings i have to change in the Exchange profile (Java stack of 7.1), so that the Java 7.1 & ABAP 7.0 connection is setup or do i need to change anything else.
Thanks & Regards,
Amit Naik

IDOC ADAPTER Issue, some meta data loads, some doesn't

Hey all,
I just started trying to setup the IDOC adapter connection between our R/3 system and our XI system. I decided to try and pull in some meta data via IDX2 to start. The weird thing is that I get some IDOC structures successfully, but not others. I think it has to do with some requirnments that I am missing on the R/3 side. For instance, outside of setting up the RFC connection, creating the tRFC port and the partner profile for the Logical system what else is needed. Do I have to assign the basic type to the outbound partner profile to access it? Do I have to actually create IDOCS for the basic type? Just curious. Here are the details of what I have done so far. A lot of this I pulled from other peoples postings here on the forum, I think I am just missing a few steps!
Our current configuration is as follows:
SAP R/3 Enterprise to post IDOCs to XI .
- R/3 Configuration:
logical system created: DXICLNT200
we20 : Partner Type LS: partner number: DXICLNT200.
we21 : IDOC Ports: Transactional RFC: Port name: DXICLNT200. IDOC record type SAP Release 4.x. RFC Destination : DXICLNT200
sm59 : create RFC destination : DXICLNT200. Target host: the XI box. Logon security: Client 200. XIAPPLUSER. PASSWORD (for XIAPPLUSER). Testing the connection works.
- XIHOST Configuration:
sm59 : created RFC destination to DDSCLNT210. Gateway options used, NO Client or User specified, are these needed, if so, is there a particular user to use.
Test connection works.
IDX1 : Created Port - DDSCLNT210. client 210. RFC destination DDSCLNT210.
IDX2 : Able to load metadata for IDoc Type CHRMAS01, of port DDSCLNT210. NOT ABLE TO IMPORT CREMAS03 or MATMAS03!
Any help is greatly apprciated!
Thanks,
Chris

There was a problem in the RFC connection, the target host was not populated correctly. All meta data can now be pulled.
However, I am curious about where the meta data for CHRMAS and CLSMAS came from. the RFC connection was NOT working, so where could it have pulled this information from????

Error when Loading Metadata for IDOC Adapter

Everybody,
I know this should be pretty straight forward and that there are a few posts about it. But following the Demo 3.0 guide and the posts I can't seem to load the data into the IDOC Adapter. I did every step in the guide and when I try to execute IDX2 for the source port I previously created I get the error "No RFC Destination is maintained for the port".
Following the guide I have my XI host
ID:ABC
Instance:01
Client:700
Executed IDX1 and got port SAPABC_107 with RFC Dest-ABC_107, which I defined previously with transaction sm59 and the test came back ok.
When I try to execute IDX2 I get the error message...
What am I missing ?????
Thanks!
Diego

Everything was setup before (by following the XI 3.0 Demo guide) here are the steps I did:
1. Setup an RFC R/3 Destination on my client 107 (American Airlines) to client 700 (my XI): ABC_700
2. Setup an RFC R/3 Destination on my client 700 to client 107: ABC_107
3. Setup the IDOC processing port "SAPABC" on client 107 with RFC Destination ABC_700.
4. Define partner type LS for logical system ABCCLNT105 (Airline Lufthansa)
5. Define partner type LS for logical system ABCCLNT700 (XI)
6. Specified the ALE distribution model in client 107.
7. Execute IDX1, I input the SAPABC port created in step 3, input the client number 107 and the RFC destination ABC_107 created in step 2 and save. The result is port SAPABC_107.
AND..!! where the error occurs:
8. Execute IDX2 input port SAPABC_107 and idoc type and get the error message "No RFC Destination is maintain for SAPABC_107"
Any ideas !?
Thanks
D
The client 107 represents the Airline American Airlines and has a R/3 RFC Destination to client 700, my XI. The same way my XI has an R/3 RFC Destination to client 107.

Acknowledment issue with idoc Adapter

Hello all,
I've an interface process that send a specific idoc from SAP R/3 4.7 to SAP XI 3.0.
This Idoc is known at XI side in IDX2 transaction.
Each time XI receives this kind of idoc, it processes an acknowledgment (sends back an ALEAUD idoc to my SAP R/3)
with followings data in E1ADHDR / E1STATE segment :
DOCNUM     0000000002401038
STATUS     51
STAMQU     SAP
STAMID     IDOC_ADPAPTER
STAMNO     000
I don't want this ack idoc to be sent but I don't manage to find where customize Idoc adapter to send it.
Can you help me ?

HI,
Make an entry in the table IDXNOALE in XI system by providing the details for the port, IDOC etc for which the Acknowledgements need to be turned off. You ca check this port etc from IDX1 entry in XI server
Or
Go to IDXNOALE report in XI There, click on request acknowledgement button, and in exceptions section, provide the message type for which you donot want acknowledgements.
Regards,
Moorthy

How to install IDOC adapter

Hello friends
I need help installing IDOC adapter.... I installed XI connectivity and I am able to view RFC, SOAP, JMS and File adapters. Our team says they need IDOC adapter. I could not find any installation document to install IDOC adapter. I checked Adapter and online documentation. Appreciate any help.
Thank You
Raghu

Hi!
> I am with the impression that I need to run
> "install_idocadapter" under tech_adapter and then I will
> be able to see it under the list of adapters in the
> adapter engine screen
No, the IDoc adapter is not configured in the adapter engine but in the transactions IDX1 and IDX2.
-> http://help.sap.com/saphelp_xi20sr1/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Regards, Tanja

Difference between Idoc Adapter and Proxies..

HI XI Guru's,
I am new to XI, I wanted to know what is the difference between Idoc adpater and proxies. When and what should be preffered ?
Warm Regards,
- Priya R

idocs which mean - (intermediate documents) are standard document formats which sap systems use to store as well send data from one system to another. If this is the format in which data has to received by R/3 then you will use idoc adapter in XI. idoc adapter can be used to communicate between systems is with SAP release higher than 3.1.X. Communication using idoc adapter is always asynchronous.
proxies are available for communication between SAP systems with version WAS 6.20 and above. They support both synchronous as well as asynchronous modes of communication. Generally when you are looking at developing new application using WAS 6.20 and above then you can design the interfaces for this new applications in SAP XI and generate the required code for these interfaces automatically in SAP systems using transaction code - SPROXY in the case of ABAP Proxy and in the case of Java proxies the code is generated by SAP XI system itself. You only have to implement these interfaces in your new application. So, basically you have to only worry about building the application and the interface part is taken care by XI itself. you can also look at using proxies when data has to be inserted or fetched from custom/standard tables in R/3 using XI.
,idoc adapter can be used for commuincation between ABAP stacks only but Proxy can be used for both ABAP as well JAVA stack.

IDoc Adapter 151 - Transaction aborted

Similar Messages

Maybe you are looking for