Do I need XI to use IDOC adapter

Hi Guys;
I have scenario like that nonSAP application sends IDOC-XML to directly SAP but I dont want to use XI , because already nonSAP system send it in IDOC-XML format.
Is it possible for this scenario without XI?
I need to do small test , I will make http Post a IDOC to SAP and want to see in we19,
but Which service in sicf I post it to?
Thanks

hi,
you don´t need XI for that scenario.
u can use the ABAP Service in SICF called "xml_idoc".
You send idoc-xml with http/s. The service converts the data into IDoc and you can see it in WE05/BD87 or WE19.

Similar Messages

Sender agreement & communication channel not needed in case of IDOC adapter

Hello everyone ,
I am new to xi , as far as i know a communication channel cannot be created in ID when using IDOC adapter , the answer for this question is like , the idoc adapter resides on the integration server & not part of j2ee AF .
Can some one explain me in the terms of a laymen , its not clear to me.
Thanks & Regards,
Reena.

Hi ! Reena
IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML, hence there is no need for sender Adapter .Also since its residing on Integration server you can directly post the message in the Integration engine.
well lemme explain a little bit,the main reason for sender agreement is to associate namespace with the sender adapter,now when we shoot IDOC from R/3 it already contains its standard SAP namespace so no need of sender agreement.
now comes the sender CC,main use of sender CC is to identify the sending system and the adapter.the IDOC header contains details of all the this,so again there is no need for sender CC
loook at this thread discuss the same
Re: Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sende
Re: why HTTP & IDOC adapter do not require sender communication channel?
Thanks!!
Questions are welcome here!!
Also mark helpful answers by rewarding points
Regards
Abhishek Agrahari

How to implement IDOC Serialization(EOIO) using IDOC Adapter

I am sending IDOC from 4.6c to XI to ECC6.0 using IDOC Adapter. I want to ensure that IDOCs are processed serially(EOIO) on the receiver side. I tried setting up the SE16-->IDXQUEUE on XI for the Receiver system and enabled the Queue processing flag on the Receiver communication channel, but the IDOCs are not serialized.
I see that XI is using XBTO_007(EO) Queue. It should be using the queue that I specified in SE16.Please let me know what else needs to be done to implement EOIO for the IDOC adapter.
Please note Sender is 4.6c System while the receiver is ECC 6.0 on WAS>=6.2
Thanks in advance.
Rajeev Gupta

Rajeev,
From http://help.sap.com/saphelp_nw70/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
<b>The receiver or sender system must be based on SAP Web Application Server 6.40 or higher.</b>
The blog listed above is when you need to sends Idoc from R3 to XI in EOIO. It does not work with SAP R3 4.6C for the reason above.
For sending Idoc's from XI to R3 ( to ECC in your case ) in EOIO, you need to seelct Queue Processing in the Receiver Idoc adapter and the rest I think is handled implicitly by XI.
Regards
Bhavesh
PS: Have not tried this practically though!
Message was edited by:
Bhavesh Kantilal

Best Scenarios when to use IDOC Adapter, RFC Adapter and Proxy

Please provide me links/weblogs which demonstrate the full scenario that when to use IDOC Adapter, RFC Adapter and Proxy when working with sender R/3 system.
Regards
Rachit

Hi abhinash,
Check these links for java proxy
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
for ABAP Proxy ...
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
for RFC .....
RFC-xi-SOAP Scenario
How to send RFC response message back to XI File/FTP adapter?
https://weblogs.sdn.sap.com/pub/wlg/3865//Troubleshooting [original link is broken] [original link is broken] [original link is broken] [original link is broken]
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
Hope you will find them useful ..
Regards
Abhi

Why we use IDOC adapter for IDOC as reciever?

hello,
Why we use IDOC adapter while using IDOC as receiver, whereas we don't use IDOC adapter while IDOC is sender?
I am clear about why we don't use adapter for sender IDOCs.
Thank you.
Sarika

Hi Sarika,
>>>>Why we use IDOC adapter while using IDOC as receiver,
maybe the easiest answer would be that we use
IDOC adapter as receiver to tell the XI where he should
send the data - there are many systems to which we can
connect our XI and somewhere there has to be an object
which will tell thx XI "where to" -> which RFC destination should it use
BTW
I believe IDOC apdater is also used as sender
although you don't configure it in AF:
"Once the IDoc has left the application through the RFC interface and has reached the <b>IDoc adapter</b> at the Integration Server inbound channel, the system converts it from IDoc format to IDoc XML format"
from:
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
Regards,
michal

Error using IDOC adapter

Hi All,
I'am trying to run the following scenario:
FILE --> XI --> IDOC (r/3).
Data is read and mapped towards an internal format. Then a mapping from the internal format to MATMAS_BAPI01 is done.
I disabled EDI_DC40 and did the needed mappings.
When I execute the scenario I get the following error.
<?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="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: MSGGUID CA9DC2E01F1211DA9EED000D56B9D8A6: Control record must start with tag EDI_DC40, not E1BPMATHEAD</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I expected that the XI system would automaticly fill in the needed info in EDI_DC40.
Does anyone has an idea what is going wrong?
Kind regards
Message was edited by: Geert Wouters

hi,
most probably your idoc message
has a wrong format
when you import your new idoc to integration repository
does it have EDI_DC40 at the beggining?
BTW
try without disabling the edi_dc40
you cna also have a look at my weblog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Regards,
michal
Message was edited by: Michal Krawczyk

IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

Hello SDN Gurus,
The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
The IDOCS produced in Appl system may be in the following order
PAYEXT
PAYEXT
EUPEXR
PAYEXT
PAYEXT
PAYEXT
EUPEXR
I need them to be processed in the same order into flat file.
The scenario is working good except for the serialization. So I did the following
Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types. I used the following link to create the above two steps.
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
The SAP system in based on WAS 6.4.
I can see the queue name & EOIO in the inbound message header.
I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
Does anybody had this problem earlier? Please advice.
Thanks
Srini Vaidyam

I found an OSS note to resolve my issue. The note number is 1057573.
Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
This forum Rocks.
Thanks.
Srini Vaidyam

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.

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

Need help in idoc adapter

Hi ,
this is Surya.
can we use idoc adapter at receiver side (i.e receiver- sap Ecc6.0 ) like that normal sap system (4.7)
with regrads,
surya

Hi,
File to IDOC (Creating PO)
/people/ravikumar.allampallam/blog/2005/03/03/creating-purchase-order-idoc-through-xi
File-to-Idoc
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
File To IDOC - Part1 (SLD and Design)
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
Troubleshooting File-to-IDOC Scenario in XI
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
File to IDOC, trouble shooting
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
No message in found in XI in IDOC to FILE scenario
Regards,
Phani

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

Doubt about IDOC Adapter

Hi all,
i'm using idoc adapter for generating IDOCS from R/3, and my scenario is: IDOC->XI->File. this is working fine, in R/3 i've got partner profiles for diferent vendors(suppliers) and they are configured for create idoc message in R/3 and all this message are caught by XI from my scenario and generate the corresponding text file.
but now suppose that I need another scenario because i need to send purchase orders by mail instead file to some of my vendors in R/3. the scenario would be IDOC->XI->Mail.
for both cases i would use ORDERS05.
i can't undertand how XI knows wich scenario have to use, if there's nothing from R/3 that tells XI which scenario should be used.
thanks, Fabian.

Thanks for responses, I know what should i use to do what i wanted. but i've tried to make a condition in the receiver determination and it's giving me an error saying that 'No receiver could be determined'.
i've searched in other threads and i have seen that utilizes xpath to make conditions
what i have done is add a condition in Configured Receivers as '/p1:ZORDERS2/IDOC/EDI_DC40/RCVPRN = 0000010598'
because depending on the partner, i want to use either one or other adapter (file or mail)
do i have misedd something?

Reciever idoc adapter Determination error

Hi,
I have scenario File-XI-R/3.I am using Idoc adapter to send data to R/3.
I am getting Reciever determination error.I have done all the steps according to the below weblog.
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
When I test my steps in configuration with test tool it is succesfull but give me error at runtime.
Below is error description.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Plz help me out if any one has some idea abt it.
Thanx
Rekha

Hi Rekha,
The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
The most common reason for this error is:
1. An error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.
2. An error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!
Hope this helps.
Regards
Suraj

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.

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.

Do I need XI to use IDOC adapter

Similar Messages

Maybe you are looking for