SAP-Xi --configuration: purpose is to receive Idoc in XI from SAPR3

Hi all,
Please provide information how to configure SAPR3 and XI systems to post an Idoc and receive and Idoc.
sender: Receiver
SAPR/3--->posts Idoc -
> XI receives Idoc
Please provide the configuration steps in detail. As i am new to Xi, Please help me to configure the same.
Thanx A Ton In Advance.
Bye all....

Hi Ajay,
Requirements in R3 system:
1. Create RFC destination pointing to XI in SM59
2. Create port for XI using we21
3. create Outbound Entry in partner Profile for XI in we20.
Requirements in XI system:
1. Create Technical System pointing to the R3 system.
2. create Business System pointing to the R3 system.
If you want to send IIDOC out of XI,
1. SM59 - Create RFC destination
2. IDX1 - Create port
3. IDX2 - Import Metadata.
Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
Check dis link for more info:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Cheers,
Prasanthi.

Similar Messages

Receiving IDocs in XI from a system with Queue Processing option

I am trying to use the Queue Processing option that can be set in a partner profile for IDoc sending, so that qRFC is used.
I have set up the Rule Name as one of the defaults that come with the system, but when I execute the sending of the IDoc, it gets stuck with status 30 (ready for dispatch). I have configured the Output Mode of the IDoc as "Transfer IDoc Immediately".
SAP Documentation states that:
"When you send by qRFC, the IDocs are first put in an outbound queue in the sending system, and then in an inbound queue in the recipient system. You can assign IDocs to various queues and specify queue name rules. "
Is there something I also have to do in the XI system that is receiving the IDoc?
Kind Regards,
Tony.

Hi Anthony,
Now I have the same problem in between ECC6.0 and PI7.11.
If you solving the problem,
Please let us know how you did.
Best Regards,

Send/receive IDOCs to SOLMAN system using AS2 protocol!

Hi All,
I want to send/receive IDOC file to/from web based SOLMAN system. Currently I'm using FTP server to send/receive IDOC file.
As of now the current process is to send the IDOCs from ECC to FTP server and from FTP to third party and vice-versa. But due to some constraints, I'm bound to use web based SOLMAN system. Please, can you let me know how to send/receive IDOC files to SOLMAN. Is there standrad FM/method to connect to SOLMAN from ECC as in case of FTP we have FM 'FTP_CONNECT'. Heard that same functionality in case of SOLMAN can be achieved through AS2 protocol.
Kindly help.
Thanks.
Regards,
Mukesh

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

Can we go with ALE configuration instead of receiver idoc adapter at target

Hi Experts,
Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI to Target system instead of configuring receiver IDOC adapter at target side.

Hi Raj
Point 1:
When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
Point 2:
When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
Regards,
Raj

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

Configuration Of Receiver Idoc Adapter

Hi Experts,
for an interface,I need to desighn a receiver idoc adapter.Plese guide Me
regarding following matters:
1. how to configure receiver idoc adapter ?
2. how to get the control record for the receiving idoc?
3. what are the configuration we have to make?
4. receiving idoc's data i want to update in my SAP database,How to achieve that?(Any program I have to write?what i need to mention in there?)
Eagerly looking for valuable suggestions.
Regards,
Rasmiraj
Edited by: rasmiraj tripathy on Aug 29, 2011 1:32 PM

Hi RashmiRaj,
Configuration Scenario
1. Create the RFC Destination in SM59.
2.Create Port in IDX1.
3.Create Logical System in BD54
4.Create A Scenario
5. Select a Business System in Service with out Party
6.Create a Receiver Communication Channel.
7. Create a new Business Service
8. Create a new Communication Channel
9. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.
10. create sender agreement
11. Create Receiver Determination
12. Create Interface Determination
13. Create Receiver Agreement
Also check the link [File to IDOC|http://www.****************/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm]
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660?quicklink=index&overridelayout=true
Thanks and Regards,
Naveen
Edited by: chichilin on Aug 29, 2011 5:40 PM

Configurations to receive IDocs in XI

Hi experts,
I'm using PI7.0 SPS10.
I have a scenario IDOC -> XI -> File.
From what I've read in the numerous threads posted before me, the configurations required on XI for such scenario is:
1. SM59
2. IDX1
3. IDX2
For the above scenario, my understanding is I do not need an iDoc Sender adapter, because the IDOC resides on the ABAP stack.
I am able to import the IDOC structure into IR, and create message mappings for the message types.
I have created 2 business systems
BS_NHGDDBS01 : The business system for the corresponding R/3 sender system. This has a TS of type WebAS ABAP - NHGDDBS01.
BS_DEV1_NAUTICUS_OOTS: The business system I created, simply to house the various projects/mappings that I will need. The mappings are housed in a SWCV which i defined.
I created my mappings for IDOC->File, under BS_DEV1_NAUTICUS_OOTS.
I activated the mapping in Integration Directory.
My questions:
1. Am I doing this correctly? I'm puzzled because I did not use the business system BS_NHGDDBS01 at all.
2. With this current setup, can XI receive IDoc from NHGDDBS01? I do not see a configuration mapping the IDoc to the message Interface which I want.
Please help to clear my doubt.
Thanks.
Ron

Hi,
>>>>I created my mappings for IDOC->File, under BS_DEV1_NAUTICUS_OOTS.
you cannot do that- you create it under software component not busines system
>>>>I activated the mapping in Integration Directory.
you activate them in repository not directory
for all scenarios with IDOCs and XI:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Configuration Of Receiver Idoc AdapterRe

Hi Experts,
for a interface,I need to desighn a receiver idoc adapter.Plese guide Me.
1. how top configure receiver idoc adapter ?
2. how to get the control record for the receiving idoc?
3. what are the configuration we have to make?
4. receiving idoc's data i want to update in my SAP database,How to achieve that?(Any program I have to write??)
Eagerly looking for valuable suggestions.
Regards,
Rasmiraj

Hi,
please go through this blog, i hope you will get all answers
http://www.****************/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm
regards,
ganesh.

Is it possible to receive IDOCs from a non-SAP system?

Hi,
I'm facing a problem where I have to configure SAP MII (12.0) to receive IDOCs from a non-SAP client. Is it possible? I'm dealing with a system named Hydra (developed by MPDV) and I'd like to know what I should configure in Hydra systems in fields like: PROGID, GWHOST, GWSERV, SYSNR, CLIENT etc.
Anyone can help me?
Thanks a lot in advance

Unless Hydra emulates ECC sending IDOCS, then you just might want to use the WSMessageListener (http://help.sap.com/saphelp_xmii120/helpdata/en/45/6a86ac88130dece10000000a11466f/frameset.htm) and configure your message processing rules accordingly.

Warnings while receiving IDOC from SAP

Hi All,
I am running BTS 2010. I configured recieve location to recieve ORDERS05 Idocs. But I am receiving below mentioned warning.
1) In SAP the Idoc shows as successfully sent
2) On the BizTalk side we cannot find the Idoc anywhere
3) In the EventLog of our BTS we get the following errors (the errors are raised exactly at the same time when the Idoc which “disappears” is sent from SAP to BizTalk )
Error 1:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "Microsoft.ServiceModel.Channels.Common.XmlReaderGenerationException: The segment or group definition E1234 was not found in the IDoc metadata. The UniqueId
of the IDoc type is: IDOCTYP/3/ORDERS05//700. For Receive operations, the SAP adapter does not support unreleased segments.
   at Microsoft.Adapters.SAP.TypedIdocBodyWriter.OnWriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.BodyWriter.WriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.BodyWriterMessage.OnWriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.Message.WriteBodyContents(XmlDictionaryWriter writer)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessageStream(Message wcfMessage, IAdapterConfigInboundMessageMarshalling config)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkMessage(IBaseMessageFactory messageFactory, IAdapterConfigInboundMessageMarshalling marshallingConfig, Message wcfMessage)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfMarshaller.CreateBizTalkSubmitMessage(IBaseMessageFactory factory, String inboundTransportLocation, String inboundTransportType, RLConfig config, Message wcfMessage,
String ssoToken)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkSubmitBase..ctor(Message message, BizTalkEndpointContext endpointContext, ControlledTermination control, AsyncCallback realCallback, String ssoToken)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkSubmit..ctor(Message message, AsyncCallback callback, Object state, BizTalkEndpointContext endpointContext, String ssoToken, ControlledTermination control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkOperation.Create(Message message, AsyncCallback callback, Object state, String ssoToken, Boolean bizTalkOneWay, BizTalkEndpointContext endpointContext, ControlledTermination
control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.BeginOperation(Message message, AsyncCallback callback, Object state, Boolean bizTalkOneWay)".
Error 2:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_INVALID_HANDLE. AdapterErrorMessage=An exception has occurred on the listener while executing
RfcWaitForRequest..
   at Microsoft.ServiceModel.Channels.Common.Design.AdapterAsyncResult.End()
   at Microsoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& requestContext)
   at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1.System.ServiceModel.Channels.IReplyChannel.EndTryReceiveRequest(IAsyncResult result, RequestContext& context)
   at System.ServiceModel.Dispatcher.ReplyChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)".
Error 3:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "The WCF service host at address sap://CLIENT=100;LANG=;@a/SAPD.corp.int/10?ListenerDest=BIZTALKD&ListenerGwServ=sapgw10&ListenerGwHost=SAPD.corp.int&ListenerProgramId=BIZTALKD&RfcSdkTrace=False&AbapDebug=False
has faulted and as a result no more messages can be received on the corresponding receive location. To fix the issue, BizTalk Server will automatically attempt to restart the service host.".
Error 4:
Event Type: Warning
Event Source: BizTalk Server 2010
Event Category: (1)
Event ID: 5740
Date: 1/10/2014
Time: 12:38:59
User: N/A
The adapter "WCF-Custom" raised an error message. Details "System.ServiceModel.CommunicationObjectFaultedException: The communication object, Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1[System.ServiceModel.Channels.IReplyChannel],
cannot be used for communication because it is in the Faulted state.
   at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Close()
at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.Close()".
http://social.msdn.microsoft.com/Forums/en-US/57a18e78-d902-4a39-a99f-95ef732792f7/adapter-pack-20-sap-adapter-problem
As per the replies in the above link i made the changes but still warning continues.
Please suggest
Thanks,

The IDOC has not arrived in BizTalk, that's why you do not see it. The problem is that the IDOC fails at adapter level, when the SAP RFC Library is called.
The actual problem is that the IDOC you are receiving is containing unreleased segments and that's not supported, you should contact your SAP administrator to get this problem resolved.
If I'm not mistaken it's transaction WE30 in SAP, there you have to select the IDOC type (ORDERS05 in your case) and then you can set the release. But your SAP administrator will probably know better how to do this
Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

How to process the Received Idoc in SAP R/3 ? What to be done ?

Hi All
I am working for file to Idoc scenario.....
Idoc received into SAP R/3 but how to process the Idoc data ?
Such it will store in SAP R/3 DB.....
Clearly
How to Process the received idoc data into SAP R/3 ? (this is for inbound idoc)
I hope any one can help me on the processing steps ?
Waiting for valuable inputs form experts
Regards
Rakesh

rakesh
chec <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc</a>
normally, based on the idoc types it will get processed. if it is an idoc with master record it will create appropriate master records or if it based for a transaction it will create one.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098</a>

Does SAP HANA supports JCo to call BAPI RFC's and to receive IDocs?

Hi,
We are using a WSO2 ESB to integrate our SAP 4.7 version system with SalesForce.com and as part of this integration we use JCo libraries to receive IDoc's and to execute RFC's from ESB.
This year we are planning to migrate our SAP environment to SAP HANA and wondering if SAP HANA supports the JCo libraries? or is there any changes in the implementation how we use JCo libraries?
Thanks in advance.
Regards,
Venkat

BAPI_TRANSACTION_COMMIT doesn't have two import parameter, please check

Receive idocs from SAP in XML format

Hi everyone.
Currently, to receive idocs, what we're doing is, we create an external RFC server, and listen to invocations of the RFC IDOC_INBOUND_ASYNCHRONOUS and IDOC_PROCESS_INBOUND. However, this leads us to receive idocs in EDI_DD/EDI_DD40 and EDI_DC/EDI_DC40 formats.
Is it possible to receive idocs in XML format via the RFC Server interface?
Thanks,
Mustansir

hi shreya,
function Module            Short text for function mod
HR_BE_DMFA_XML_DOWNLOAD    Register XML conversionca
    HR_PT_TAX_XML_DOWNLOAD
SDOK_LOIO_XML_DOWNLOAD_PUBLISH
SPRX_XML_DOWNLOAD              Displaying the Payload
DMEE_DOWNLOAD_XML_TREE
DMEE_DOWNLOAD_XML_TREE_ABA     DMEE: Download format tree
JITOUT10_DOWNLOAD_XML
GLOS_DOWNLOAD_XML
this function module you can use.
regards,
sandeep
Edited by: Sandeep patel on Jul 7, 2008 6:36 PM

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

SAP-Xi --configuration: purpose is to receive Idoc in XI from SAPR3

Similar Messages

Maybe you are looking for