IDoc Adapter - ATTRIBUTE_BE_NOT_SUPP Async processing

Hello,
I'm trying to establish IDoc communication. Here is the scenario that I need:
<XML Data> --- <SOAP> --> PI Server ( Map XML to IDoc XML) --- <IDoc> --> SAP Retail System
I have the following components set up:
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
2. Sender Agreement
3. Map from InXML to OutIDoc. OutIDoc - Message Interface - Inbound Asynchronous
4. Receiver Determination
5. Interface Determination
6. Receiver Agreement
7. Receiver IDoc Communication Channel
8. Business Service for all this
No Integration Scenario.
If I replace item 7 to the FTP for example, everything works just perfect - I send XML it gets Mapped to IDoc and in my FTP I have the IDoc file.
Now, I've asked SAP support specialist to establish communication from PI Server to Retail using IDoc. He send me parameters, which I used for IDoc Communication Channel:
RFC Destination: NX7CLNT800
Port: A000000022
SAP Release: 3 - this is I put myself
But when I run the whole system again, I'm getting the error:
IDOC_ADAPTER ATTRIBUTE_BE_NOT_SUPP - "Only asynchronous processing supported for IDoc adapter outbound processg"
This is very confusing because both my message interfaces are Asynchronous.
Can anyone tell me what I'm doing wrong and why I'm getting this error.
Thanks.

8. Business Service for all this
Should it not be Business System for IDOC.....for SOAP it will be Business Service
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
Check what is the QoS that is specified in the SOAP Channel.....if it is Best Effort then it will be a cause of the error......change it to Exactly Once (EO).
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 4, 2009 10:29 AM

Similar Messages

Posting Purchase Orders (IDOC Adapter) according to Vendor using BPM's

Hi,
My requirement is to post purchase orders into SAP r/3 according to vendor wise using IDOC adapter using BPM's.
Input is a FLAT File which contains all the Purchase order items/records for various vendors.
We need to process these items/records according to vendor and post it into SAP r/3 using IDOC Adapter within 8hrs processing time(Time Bound).
What i mean is: the process should collect all respective vendor related items/records from the flat file and post respective purchase orders in SAP. That means if 5 items out of 20 are from one vendor, we shud create a PO in SAP with 5 items for that vendor and likewise for the rest of the items.
Please explain the procedure and detail Mapping in step by step procedure... how to send 'n' items for a PO.
Regards,
Ravi

for idoc configuration refer
https://wiki.sdn.sap.com/wiki/display/XI/SAP+R3+%28Idocs%29+To+XI+--+Steps+Summarized
Source WIKI. As far as BPM is concerned, set the correlation based on vendor number. this will ensure u collect the message according to vendor number.
there are two option set for ur for posting the PO WRT vendor number:
1. using BAPI
2. using idocs
The mapping for both the methods are straight forward except care need to be taken for mapping the data segment esp WRT the vendor number.

REG: Error in IDoc adapter outbound processing

Hi All,
      I had a couple of doubts regarding these IDoc's.
1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
"IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
Can any one help me to Solve my Problem
2) How to find out whether the IDoc is of synchronous or Asynchronous mode
    and how to handle the synchronous type of IDoc's
Thanks in advance.
with Regards,
Kalyan Dannapaneni.

Hi Kalyan,
IDOCs are only Aynchronous (EO or EOIO).
If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
Best regards,
Silvia

Process flow of IDoc adapter in SAP PI

Hi Experts,
can any one pls send me about IDoc adapter in SAP PI/XI, which covers a complete info of IDoc adapter.
i mean complete in and out about IDoc adapter.
with rgds,
MF

Hi
If you do a search, you will get lots of material.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd
IDOC Adapter
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/idoc%252badapter
These links should help you out
Thanks
Saiyog

Messages get lost between IE and AE (IDoc to SOAP - Async)

Dear Experts,
in a IDoc to SOAP (Async) scenario a message was not transferred. I could not see any error message in RWB or ABAP Monitoring. When I enter RWB, the column engine is "Integration Engine" and the status is "Successful". At the same time other message with the same message interface were transmitted and they have engine "All" and status "Successful".
Why was this message not passed on to Adapter Engine? How can I restart the processing, so that the message is transfered?
Best regards,
David

Thank you for your answers:
@ Divyesh:
I can't resend the message. It does not have an error status. It says "Successful", although it only can be seen in Integration Engine, not Adapter Engine. There are not SM58 errors.
@ Krish:
In ABAP Monitoring all steps were performed as expected. Before and after this message some other messages with the same message interface were transmitted and they are visible in ABAP Monitoring, Inegration Engine and Adpater Engine.
@Hareenkumar:
In SAP everything looks like expected.
The only difference between this message and other messages sent at the same time (which were transmitted correctly) is that in RWB Message Monitoring (Component: Integration Server) the Engine is "Integration Engine" instead of "All". And the message is not visible when you select for component "Adapter Engine".
Do you have another idea?
Thanks in advance,
David

IDoc Adapter throws error

We are trying to send data to SAPR/3 47 IDES using IDoc Adapter.
the data is sent to XI from SQL database thro JDBC adapter and then to R/3 thro IDoc adapter.
All this is in Asynchronous mode and at no point we chose synchronous (IDoc adapter does not suppost Asynchronous process right).
But we are getting the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>B7685EB2-42F1-554B-80CC-6ADFC86C7975</SAP:MessageId>
<SAP:RefToMessageId>35A42550-81F9-11D9-AFC7-00C09F450580</SAP:RefToMessageId>
<SAP:TimeSent>2005-02-18T22:05:33Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>S70_812</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS04</SAP:Interface>
</SAP:Sender>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processing</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
We are not sure where from this synchronous is being picked?
Please advise.
Thanks,
Bhaskar and Anil

In the Processing Parameters section of the JDBC adapter, make sure you have Exactly Once (Asynchronous) selected.

XI FILE(FTP) - XI- CRM(Idoc adapter) scenario - restart message

Hello All,
I have scenario as below.
FTP->XI->CRM
The sender adatper is File Adapter, FTP.
Recv. adapter : IDOC adapter.
In CRM, there were middleware settings for idoc processing.
For an interface, in XI, i had a problem in getting a file of 10 Mb in size, so the file is split and i have made the XI sender adapter 'Z_PRICE_NEW20061004*.txt', so it picks all files within 5 mins and i have almost 104 XML messages.
Now the problem is a quite no. of message are ended up with error status in outbouond process in XI.
How can i reporcess the message? As the file is deleted from FTP? i ahve to do anything with the failed message.
A quick help is highly appreciated.
Thanks in advance.
Best Regards,
Jilan Bhasha

Hi ,
This weblog will help you....
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
sekhar

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

Basic Idoc Adapter Error - XI 3.0

Hi,
I am new to XI so excuse me if this is a basic question.
The scenario we have is File -> XI -> IDOC
When the message is processed into the IDOC Adapter I am getting the following error :
Control record must start with tag EDI_DC40 not E1LFA1M
Don't really understand this one as in the message mapping this segment on the target IDOC is disabled. It was my understanding that this segment is automatically filled by the IDOC Adapter.
Is there something I need to change in the Idoc Adapter to get this to happen ?
Kind regards
colin.

It is not a basic question, but it seems to be a common problem.
Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.
Regards
Stefan

Why do we require Receiver IDoc Adapter wen Sender IDoc Adapter is not req?

Hi All,
We require Receiver IDoc Adapter( if the receiving System is R/3 and uses IDoc) but when sending BS uses IDoc, Sender IDoc Adapter is not required since it resides in ABAP Stack. So, can anyone explain me as why do we need to configure Receiver IDoc adapter?

Hi,
Both the sender and receiver IDoc transmission is done by the RFC communication channel.
In case of the sender IDoc, partner profile configuration in the sender system will tell for a particular IDoc type which port should be used. This port will have the details of the RFC channel to be used to deliver the IDoc.
However, in case of SAP XI/PI system we don't configure partner profile and hence we need a way to tell which port & RFC destination should be used to deliver the IDoc and hence we define a receiver aggrement and adapter. This is just used as a reference at rutime and unlike the other adapter, this receiver IDoc adapter doe's not process any message over Adapter engine.
Hope this helps...!!!!
~SaNv...

IDOC adapter Retry interval

Hi
I am doing File-IDOC scenario.
For each 5 min there will be new file coming to the FTP folder..sender File adapter needs to pick the file and send as IDOC to R/3.
Each file consist of multiple lines..so i am using IDOC bundling..so for each file i am sending aroung 50 IDOCs at a time toR/3..
I am using BPM for this scenario...( i know we can do this without BPM also...but i have to use BPM..)
if R/3 system is down...then i am waiting for 2 min..and through deadline branch i am canceling the process...assuming that receiver system is down..and throughing alert to support team to intimate the same...
Each adapter is having default Retry interwal...if that adapter fails to send to the receiver...by default it will try for 3 time..with time interwal gap of 5min(i think) between each retry..
For each 5 min i will get a new file...so i have mentioned 2 min for deadline branch...
what happens if the IDOC adapter succeded in seconed attemt.(i mean after 5min) to send to receiver (here R/3)..?
--> i am sending alert to support team...but IDOC has sent succefully..which should not happen..so either we have to decrease the IDOC retry interwal or need to increase the deadline branch inerwal...
Questions:
What's the default retry interwal for IDOC adapter??
Can we decrease IDOC retry interwal time as normal file adapter in Visual admin..??
if i increase the Deadline branch time interwal...it will keep on trying to send first file..so waiting status..if sencond file comes after 5 min...it will also wait status..will there be any problem...??
Thanks
Murali

>>What's the default retry interwal for IDOC adapter??
Can we decrease IDOC retry interwal time as normal file adapter in Visual admin..??
No. Idoc adapter is not part of Java stack and hence you cant alter any idoc adapter settings in VA.
When the Idoc adapter fails, the message fails in SXMB_MONI unlike other adapters which pass through SXMB_MONI.
So, incase of Idoc adapter the restart depends on the reprocessing the error messages in SXMB_MONI.
Usually the report to restart errror messages in SXMB_MONI is scheduled as a background job.
You need to check for that. But in most cases, the interval is a few hours rather than minutes.
Jai

IDOC adapter and number of tRFC records

We have idoc inbound scenario file -> XI -> idoc -> R/3.
For each file record an IDOC is created.
Can somebody explain, why only one tRFC record is created containing all IDOCs? Can you influence with interface config how many tRFC records are created? Does settings ' exactly once ' / ' exactly once in order ' have something to do with how many tRFC entries are created?
We faced a situation with our interface scenario that file unexpectedly contained huge number of records causing huge number of idocs generated in XI. However only one tRFC entry was created that contained all idocs. As consequence the receiving system had performance problems and the tRFC call had to be cancelled.
As workaround we splitted the source file in file adapter to interval of 1000recs, thus causing multiple tRFC records created and performance was ok in background system.
Is XI trying to keep IDOCs created out of each incoming message in one "LUW" and send them alltogether in one tRFC call to R/3? Or is there a config parameter that each created IDOC could be sent independent of other idocs still to be created?
br: Kimmo

Kimmo,
There will be one TRFC call per message from XI.
The whole input file is treated as a XI message.
The Receiver IDOC Adapter call the SAP system via ONE TRFC call and posts the message.
By mentioning Exactly Once in the Receiver Idoc Adapter Communication Channel, XI guarantees the delivery of that message.
One way is to split the file into multiple Messages.
You can do this via BPM. But this is not advisable for large files.
We had the same problem for very large files.
We used XI to just pass through the file from Source system and post as file in the Application Server of SAP.
We defined a LSMW project for Periodic Processing, which would take this file and post as Idocs in the SAP System.
Our Scenario
File -> XI -> File.
In the Receiver File Adapter, use the Execute Operating System Command to trigger event sapevt in the SAP system.
You can define events for Background jobs.
So when XI posts the file in the Application server of SAP, XI will trigger the background event defined in the Communication Channel.
The LSMW project which has been scheduled to listen to this background event will kick off.
Hope this helps.

RE:SENDER IDOC ADAPTER

Hi ,
why don't we crate a communication channel for idoc on sender side,but when we go for receiver side we create communication channel .
please let me know how an idoc converted in to idoc-xml while transfer to integartion engine from sender side.( with out idoc adapter on sender side)

hi prateek,
The communication at sender also passes through the Idoc adapter.
with our configuring idoc adapter on sender side, how can an idoc passes through idoc adapter, is this because idoc adapter resides in abap stack.
can u briefly describe how can an idoc convert in to idoc-xml before comming to integration engine.
if idoc adapter is on abap stack then
in case of file to idoc
why we go for idoc adapter . (con't the process same as reciver side) .
please give brief explain to each of my questions.

How to get rid of messages in idx5 idoc adapter

We are having a lot of messages in idx5 (327828 for a particular date). When I go to sxmb_moni "Monitor for processed xml Messages" I do not find these messages there.
We are running the archiving/deletion reports and I expected theese to take care of the Idoc Adapter messages as well. Is this not the case? Are there separate archiving/deletion jobs for the idoc adapter? How do I get rid of the messages in the idx5 xml messages in the idoc adapter?
When running the report RSXMB_SHOW_STATUS this is today (after archiving/deleting all messages older then one day) showing good 30.000 messages in the database - and do not show the huge number of messages in the idoc adapter.

The baseball is probably the symbol assigned to you in Address Book - take a look and see. It appears on all your sent mail in Mail, but not on the messages as they appear to recipients, so don't worry about it too much. If you don't like it, you can remove or replace it through Address Book.

IDOC ADAPTER as sender settings

Hi ,
We trying a basic scenario where R/3 is a sender system
R/3 >IDOC ADAPTER>XI-->(File/sap system)
S57CLNT800
Configuration done at Sender R/3 system
1) RFC DEST for XI
2) trfc Port for above rfc dest
3)Partner profile for Logical system EXICLNT100(this is ls for XI server)
   outbound parameters (Message type Orders)
Configuration done at XI
1)RFC dest for Sender R/3
2) port by idx1 for RFC dest created above
in Integratoion directory
Assign buusiness systm...for technical system Sender SAP system
Whats next?
Is there any settings to be done in XI to setup partner proile and inbound parameters as Orders.
When i am trying that then it is throwing error saying orders message type not present in table edmsg
Casn some one explain me what settings to be done in (WE20)Integration repository also?
Please help me in this matter coz i am stuck like dope with no hope....with this for many days.
Please let me know if any more details you need.
Thanks a lot
Deepti Patil

Hi Michal
I am amzed to see your so fast reply.
Ya i have read the weblog by Ravikumar Allampallam which had helped me to configure
My SAP system as receiver and which went successfully.
But now since i am trying the scenario where SAP system should send the idoc
and lets say receiver system can be FILE or Again some SAP system but through XI.
So as i told earlier
I have made a technical system as system as ABAP (S57)
business system assigned to it.
When i assign this business system to a configuration scenario in Integration directory,
in adapter specific identifiers i can see
logical system as my sender system
R/3 system ID S57
Client 800
Integration server is set as integration server in sxmb_adm
Now i have queries as
1) any data mapping necessary in Integration repository (by importing IDOC)
    IN Integration directory will there be only one communication channel as
    receiver for my receiving system?
2) In Sender system when i simulate the IDOC that time who will be my recipient(we19)
   I am very new to idoc also so if you can help me in this.
3) if now if i am posting IDoC from SAP system, where in XI we can check whether IDOC is arrived or not/
4) if you have any standard document for all this.
5) i am following SAP HELP IDOC processing with IDOC ADAPTER
Thanks a lot again!!
Deepti patil

IDoc Adapter - ATTRIBUTE_BE_NOT_SUPP Async processing

Similar Messages

Maybe you are looking for