Ale settings when receiving idoc from xi

Hi friends,
I wan o confirm that the settings I had done in my R/3 system for receiving idoc from Xi are correct.
Third party is goin to send message to my Xi system, from there I have to send that message to my R/3 system.
In R/3 I had created 2 logical system,one for r/3 itself and other for my XI system.
I assigned client to this systems.
I created RFC and port for XI.
Then created distribution model, with sender as xi logical name ,receiver as R/3 logical name.
Is this configuration correct?or I need to create the thirdparty logical system also in my R/3 system?

Hi,
Your steps looks fine to me. I think distribution model is not required for inbound case.
just check the below configuration once again.
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Also look at the step by step process.
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)&
chirag
Edited by: Chirag Gohil on Nov 24, 2008 1:23 PM

Similar Messages

Settings in XI side to receive IDOC from application server

Could somebody verify the following stmt regarding
Settings in XI side to receive IDOC from application server
The metadata for the idoc should be in place before sending idoc from the application system

Hi Vasanthakumar,
have a look at those settings by Shravan:
Re: Steps to define correctly IDoc sender adapter
you don't have to do point 4
Regards,
michal

Hello I send imessages to a phone number I receive delivery notice but sms does not show on receiving phone. Otherwise when receive imessage from other phone I reply and receiver sees SMS !!! Any explanation ?

Hello I send imessages to a phone number I receive delivery notice but sms does not show on receiving phone. Otherwise when receive imessage from other phone I reply and receiver sees SMS !!! Any explanation ?

To my knowledge, I've only seen this for imessage only and not SMS.
The other users would need to have send read receipts enabled on their phone.

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

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

Hi guys
i have problem when i run my windows application exe in windows server 2003
it give me this exception error :
I using sql server 2005
visual studio 2008
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Sales.SalesClass.ShowSalesData(String ConnectionString)
at Sales.Form1.timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
Sales
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/administrator.ALTAWIREADYMIX.000/Desktop/Sales.exe
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Why this error show and how to solve it
if possible help me
Why this exception show and how to solve it.
Notes this exception not close my application and not affect in result show but i don't know why it show

The problem can be caused by certain issues of long-running queries, which are reported improperly. Try increasing the timeout:
http://support.microsoft.com/en-us/kb/555938

Error when generating IDoc from MC document - workitem to all the SAP users

A workflow item with the subject of Error when generating IDoc from MC document is sent to all the SAP users' inbox. Is it possible to stop the generation of this work item? If that is not possible, can we limit sending the work item to a specific user/agent instead of all the users in the system?
It appears that these work item or error message are generated when one of the developers reopen the POs and add line items. Moreover, during that time the procurement team blocked the IDOCs from going out to the vendors when changing and resaving the POs. Therefore, we need stop the generation of error message/work item when the IDOCs generation blocked.

Please check Rule 70000141which is the default rule for this task. Inside this rule a FM is attcahed which is reading table EDO13 and EDPP1 where agent is retrieved Probably this table entries are not maintained. This Workflow is getting triggered from Message cOntrol I think.
Please check this link for
http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4aec8453d11d189430000e829fbbd/frameset.htm
<b>Reward points if useful and close thread if resolved</b>

Error when generating IDoc from MC document

Hi,
Our Workflow administrator is getting the following error in his inbox daily for a particular IDOC type.
Error when generating IDoc from MC document
Please let me know how to disable this message.
Regards
Elini.P

Hi experts,
i got the error msg when generating idoc from mc document
this error msg goes to all sap users inbox,how to resolve this problem
pl give me solutions
regards
kumar

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.

Send idoc when bp created and receive idoc from external

I am sap abap developer and am new to CRM technical side.
*****my requirement is : when we create business partner and save it then i need to send that as an idoc to 3rd party theru ESP system.
I planned to create BP using BAPI BUPAFS_FS_CREATE_FRM_DATA01 and generate idoc in CRM and should send to ESP. They will send to 3rd party and collect some data from tham and they have to generate idoc using BAPI which i specify (I dont know which bapi) and send to us. But i dont know what bapi i have to used at ESP to generate and send idoc from ESP to CRM. Is am not sure how to use bapi exactly.
Please help me out as soon as you can. I was struct in project.Urgent

Hi Mehar,
SAP CRM supports this functionality in the standard. All you need is some customizing to get changes in CRM mapped to an outbound IDOC and send it out to an external system.
Inbound is also covered. You can post IDOCs to the CRM system using an inbound port. No need to call a BAPI, you can create the IDOC externally and simply post it as a file to the CRM system.
Alternatively, you can use XML to achieve the same.
I've sent a configuration document to your email address. In it you will find all you need to perform the customizing for a working XIF scenario.
Get back to me when you get stuck.
Regards,
Michael.

Problem when pushing IDOC from SAP to XI

Hi,
I am trying to push an IDOC from SAP R/3 system to XI. When I processed the IDOC using test tool(WE19), it's showing message that IDOC sent succesfully to R/3 or External system. But in SM58 Transaction it gave error message that in Trabsaction IDX1: some RFC connection error. Then I opened the Transaction IDX1 on XI server, in that IDOC Adapter configuration I gave RFC destination, Logical system name of R/3 and saved it. Now When I tried again to push IDOC from R/3 to it's not giving any error message(in SM58), but I am not able to see any thing in SXMB_MONI. Can anybody guess what's happening? And also I am using fresh newly installed XI server. DO I need to configure something else? All RFC connections are well defined and working fine.

Hi,
It is not required to create Sender Agreement for the Idoc to XI scenario. Because it is implicitly exists.
Can u check Receiver Determination created in the XI once again. And also check for RFC destinations created in the R/3.
Hope it helps ..
-Moorthy

ALE Settings For File-IDOC Scenario

Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
Bopanna

HI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
We need to do the following settings in XI
1)   Create an RFC Destination to the Receiving System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select Create New button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in XI towards R/3
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Inbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Message Type and Process Code.
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
                                                                                [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM

Receiving idoc from R/3 and receiving aleaudit idoc back to senderr

Hi,
I'm trying to post a idoc from R/3 to a FTP server using file adapter. I have configured a RFC destination, port on R/3 to the XI server and a partner profile on R/3. Also created a RFC destination and port on the XI to the R/3 system.
When I try to test the idoc using TA we19, mention the sender and reciever port , the idoc is sent with a msg 'IDoc sent to R/3 System or external program'. In TA we05 the idoc is shown with status 3.
But when monitoring the idoc in XI it doesn't appear in the moni
Would appreciate ur replies.

HI,
Please try to run program RBDMOIND with ta code se38.
Also see the below links for ALE AUDIT.
Check these docs...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
https://websmp210.sap-ag.de/~sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Regards
Chilla..

Problem when sending IDOC from ECC to MII 12.0

Hi all,
   I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
   But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
   - 53 IDOCS were successfully outbounded (list in WE02).
   - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
   - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
   I'm wonder why some IDOCs were successful while some others were error. If the bean IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
   I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
   If some have the same problem and know how to resolve it, could you please help me?
Thank a lot in advance,
Vinh Vo

Hi Vinh,
Please read the following document:
[IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.
In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it.
I suggest that you follow the document completely and do nothing else to set up a new listener.
If you are not using ECC 6.0, you may find the paths are different, but the transactions codes are generally the same. However, you may want to check with some of the older installation instructions regarding specific modifications. Look in the Wiki for MII under Connectivity.
Good luck,
Mike

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

Error when exporting IDOC from one XI system to another

Hi all,
When I do an export for an IDOC from my one XI server to be able to import it into another I get the error below. The funny thing is that it works perfectly for my COND_A idoc but not at all for DEBMAS and MATMAS idoc.
Any ideas?
<b>Error during export. Internal error during pvc call: SAP DBTech JDBC: Result set is positioned after last row.</b>
Regards,
Liesel

Hey,
I guess you are using MAXDB,
please read note number 1055246
(Inconsistent XI content caused by bug in MAX DB)
Good luck!

Ale settings when receiving idoc from xi

Similar Messages

Maybe you are looking for