IDoc-Tunnel - IDoc is rejected

Hi guys,
well i have an internal EDIserver which will send IDoc native via XI (IDoc-Tunnel) to a R/3 target System. Therefore for EDIserver a RFC-Destination of type TCP/IP exists where a registered Serverprogram is applied, also with given gateway values from the XI-System.
After configuring an IDoc-Channel in the Integration Directory the testing of the SM59 RFC-Destination works fine. Well because of Michal's Blog for IDoc-Tunneling i already did the configuration of the integration engine (XML CONVERSION).
Ok i imported the IDocs in IR, announced them in IDX2 and did the ID-Part with Sender-Agreement and so on.
But when we try to send an IDoc from EDI to XI we get following error:
rfc_error_info.message="No service for system SNDPOR, client 100 in Integration Directory"
The EDI-Consult thinks that he needs the Header-data from the IDoc like RCVPOR, RCVPRT, RCVPRN but i think we don't.
So where could be the problem?! perhaps at the registered server program of the EDIServer?!
br

Hi Udo, thx for ur reply.
Well that might be the problem. I have applied an EDI_Test in SLD for EDIServer but the EDI-Consultant might not have used this field so that there is a standard value in it (SNDPOR) which indicates what kind of info is needed there.
So he should enter EDI_Test for let XI accept the IDoc when it is posted!
br

Similar Messages

Tunnelling in IDOC To IDOC and payload size

Hi XI Experts,
We runned in a PI 7.0 SP13 an IDOC To IDOc scenario with non conversion XML (Tunnelling with IDOC/XML_CONVERSION parameter set). Refer to Michal Krawczyk blog : /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
All seems good : payload in message monitoring is flagged as 'application/x-sap.idoc.bin' et scenario works fine.
But we have 2 questions :
Q1 : in monitoring, payload document is displaied in right bottom window like XML representation....like an XML-converted document.
Q2 : value parameter 'SIZE_PAYLOAD' in message with non conversion XML is greater than....in conversion XML ?!?....
Thanks for yours responses.
Etienne

Hi
Please find here with you the clarification,
*Q1 : in monitoring, payload document is displaied in right bottom window like XML representation....like an XML-converted document.
the value is set to XML_CONVERSION parameter to value 2
a) 0 - Every IDoc is saved as a table; no IDoc-XML conversion
b) 1 - Every IDoc is converted to IDoc-XML
c) 2 - An IDoc is converted to IDoc-XML if requested by the service
Here the IDOC is internally be treated as IDOC-XML as you would be using the Business systems with SAP. And it depends upon the services.
Q2 : value parameter 'SIZE_PAYLOAD' in message with non conversion XML is greater than....in conversion XML ?!?....
The SIZE_PAYLOAD will be always more with non-conversion XML includes the header details also..(I am not sure with it).
Its better that you copy the XML Payload and save on local PC. Then check with its size.
thanks
Swarup

Idoc to idoc scenario with idoc tunneling

IN idoc to idoc scenario with idoc tunneling the XML_CONVERSION parameter to value 2 is set whish means An IDoc is converted to IDoc-XML if requested by the service
I want to know where we specify this and how we specify?

1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
ref these weblogs.
It is given under;
TCODE - SXMB_ADM
- Integration Engine configuration
- set the XML_CONVERSION parameter to value 2

IDoc tunneling (Parameter XML_CONVERSION)

The parameter in the SXMB_ADM transaction defines whether the IDoc is transported as a table and is not converted to IDoc-XML in the IDoc adapter. This is only recommended if IDocs are received and sent as IDocs in the Integration Server. If none of the services in the Integration Engine use IDoc-XML, you can avoid unnecessary conversion from and to XML, thereby improving system performance.
Possible Values
'0' Every IDoc is saved as a table; no IDoc-XML conversion.
'1' Every IDoc is converted to IDoc-XML.
'2' An IDoc is converted to IDoc-XML only if requested by the service.
The question is: does anybody know what "if requested by the service" exaclty means ?
Regards,
Sandro

Think about a scenario SAP-XI -JMS (or Flat file) vice versa . I will do the transformation with ABAP-Mapping in both direction and theres no need for receiveing an XML-Stream from IDOC-Adpater or send an XML-stream to IDOC-Adpater.
We would receive a better performance if we could avoid the expensive XML-Transformation.
There is a check of an existing Mapping for Sender-Message in the Table SMPPREL3 .
There could be an special XML-flag in this Table and in the Receiver-Determination you could set this flag or not .
XI uses CL_IDX_IDOC_RESOURCE for the IDOC-Tunnel. In this class EDIDC and EDIDD are serialized in an XSTRING . In my ABAP-Mapping first i would check Content_Type via PARAM->GET. For transforming the binary Content into EDIDC and EDIDD a static method should be implemented by SAP in CL_IDX_IDOC_RESOURCE . I think I could implement such a method myself, but its risky if SAP changes their ITAB_TO_BINARY-method in an incompatible way.
In the XI-SAP -direction I would like to set the content_type in ABAP-Mapping to bin and convert the EDIDC and EDIDD in X-string (like in CL_IDX_IDOC_RESOURCE ->ITAB_TO_BINARY ).
Regards Josef

IDoc-Tunneling -- No Receiver Agreement

Hi, i am trying to do the IDoc-Tunneling scenario from Michal.
Well everything looks fine so far except that i get following error:
+<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
<SAP:P1>-Q01CLNT010</SAP:P1>
<SAP:P2>0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Es konnte keine Empfängervereinbarung für den Sender -Q01CLNT010 zum Empfänger 0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01 gefunden werden</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>+
Well i have Receiver Agreement that looks like:
Sender Service: Q01CLNT010
Receiver Service: EDI
Interface: DELFOR.DELFOR02
Namespace: urn:sap-com:document:sap:idoc:messages
CC: IDOC_RECEIVER_EDI
In this Receiver-CC i also activated
- Apply Control Record Values
- Take sender from payload
However, i have no clue what is wrong.
Can somebody help? br Jens

Hi Jens
(6) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
The problem is in Technical routing.
Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
Please refer the follwoing blog for details
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Thanks
AbhishekMahajan
*****Please reward points if helpful*********

IDOC "Tunneling"

Hello all,
We are currently implementing a IDOC->XI->JMS scenario.
We would like to use the IDOC Tunneling option:
SXMB_ADM -> Integration Engine Configuration
IDoc -> XML Conversion = 2 or 0
2 questions:
When setting the XML_Conversion parameter to 0 XI seems to be ignoring our request and the IDOC is still being converted to XML.
Does anybody have any idea why this happens?
When setting the XML_Conversion parameter to 2 how do we get the service NOT to request the IDOC conversion?
Thanks in advance.
Claus

Hi Holger,
Thank You for Your answer.
We have tried the IDOC->XI->IDOC scenario.
However the payload shows that the IDOC is converted to XML.
Can we expect to see a non-converted IDOC in the payload if we use the XML_CONVERSION parameter value 0 or 2?
Regards
Claus Borre Nielsen

IDoc Tunneling and XML_CONVERSION

Hi,
I'm developing a File 2 IDoc / IDoc 2 File Scenario.
The Partner who receives and send files wants to use the idoc flat table structure.
I noticed that wasn't so easy to convert IDoc XML to flat file, till i found IDoc Tunelling which perfectly fits my scenario!
The research i've done, explains that we just have to set the IDOC / XML_CONVERSION parameter:
Possible Values
'0' Every IDoc is saved as a table; no IDoc-XML conversion
'1' Every IDoc is converted to IDoc-XML
'2' An IDoc is converted to IDoc-XML if requested by the service
But, setting value to '2', how can i control if i want or not Xml conversion to occur? Is a setting made in R/3 or XI?
I have scenarios where i really need XML (to use mapping features). Value 2 looks perfect, but where is this controlled?

Hi Jose,
Sounds good idea and approach..
Check out this blog by Michal..you will get all your answer on idoc tunelling..
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Hope this will help.
Let me know if you need more details.
Nilesh

IDoc Tunnelling

All,
   I was going through the Michals Blog for IDoc tunnelling and I'm little confiused here. As per the blog,
setting the "XML_CONVERSION parameter to value 2" enables the IDoc tunnelling.
1) Does all the IDocs coming out of R3 will be in the flat file format.
2) Also the blog says as per SAP help "2 - An IDoc is converted to IDoc-XML if requested by the service" - Can someone tell me what service request that we need to use for IDoc - XML conversion with a value of 2?
Thanks.

My question is
1) if we set the XML_Conversion parameter to 2, are all the IDocs coming out of ECC will be in the flatfile
   format?
2) If all the IDocs coming into XI are flatfile's, what service do we need to request for the IDoc to be in IDoc XML format with the XML_Conversion parameter set to "2"
Thanks.

Sender Namespace and Sender Interface in the IDOC to IDOC scenario

My question maybe very basic...
It is SAP IDOC to SAP IDOC scenario.
Lets assume that I have done config in XI for:
 Sender = A,
 Interface = B,
 Namespace = C.
My question is:
Is there a place in the source system or somewhere to point that
when an IDOC e.g. DEBMAS is triggered in the source system,
then the Interface should be B and Namespace should be C in the xml file ?
Cheers
Agnie

Hi Agnieszka,
 Check these threads/blogs from you may get some help:
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Idoc-to-idoc scenario
IDoc to IDoc scenario necessary configuration steps
For A-Z help on IDOC, you can refer Michal's book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
Regards,
Subhasha Ranjan

IDOC to IDOC queue blockek status shows green flag

Hi i' m doin an iDOcto idoc scenario.. in sxmb_moni the status flag is green...queue is blocked.. i tried activating the queue
it still shows sysfail...
this is the trace message... any problem with my design or the message passed.. or is it a queue problem if so how to handle
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: PI_RM_USER</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEC</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = DIN</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PI_RM_USER</Trace>
<Trace level="1" type="Timestamp">2009-08-07T09:08:38Z CST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 80144FDD6C661DEEA0E63CA33DA20911</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC">
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface COELEM.COELEM01</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
</SAP:Trace>
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:23 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:24 AM

HI,
Correctly said by Abhishek, click on Queue Id and then further selct the Queue and Click on details to see all the messages in that Queue. Select the First Message in SYS FAIL and try to restat that. If that again Fails. Don't delete the whole Queue but delete the selected message from Queue in Error. Then go Back and Unlock the Queue and refresh. All messages behind this message will re-process automatically.
SMQ1 and SMQ2 are tcodes foe Queues.
REgards,
Anurag

Idoc to idoc in bpm

hi experts,
i am getting problem in idoc to idoc scenarios in confriguration part,how many businees system i have to used in this scenarios.if any examples are there please help me.

Hi
u can go for IDOC tunneling and packaging
see the below link
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Check this blog by Michal,
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Tunneling
Re: Need help please......:IDOC TO IDOC
Re: configuration steps for receiving idoc in xi from r/3

Need help please......:IDOC TO IDOC

Hi frends,
As Iam a fresher to SAP XI, I would be very thankful if someone can answer this question.
Need to send a Delivery IDOC from a sap system to other to create sales order idoc on the receiver side if the sold to party is already present.
If the sold to party not present, one has to be created using an DEBMAS idoc and then create the Sales order idoc.
I am very much confused how to configure this BPM scenario.
As per the specification i need to create two interface mappings one for Delivery to Salesorder and the other for Delivery to Customer.
But I don't understand how two interface mappings can be created and used in a BPM scenario.
Please help me resolve this issue.
Thanks in Advance.

Hi Kinthali,
Check these blogs/help file realted to IDOC scenario for ur help:
<a href="/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get: IDOC to IDOC tunneling - how fast (and easy) can you get?</a>
Go through Michal's book, this is a one stop for all issues related to IDOC:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi: New book: Mastering IDoc Business Scenarios with SAP XI</a>
Also check these files:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a</a>
Regards,
Subhasha Ranjan

Idoc-XI-Idoc Scenario

Dear All,
I am working on Idoc-XI-Idoc scenario in which I am getting ORDRSP Idoc in input. In one of its segment I am getting value as either A or B. If value is coming as A in input then in the output we want PORDCR101 Idoc but if we have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for each line item there will be different idocs.
Please guide me on how we can implement BPM in this scenario as required two MM i have created and they are working fine.
Regards,
NJ

Hi,
If value is coming as A in input then in the output we want PORDCR101 Idoc but if we
have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for
each line item there will be different idocs.
For Source = A:
SourceField----
-----equalS ----ifwithoutElse ----then Constant(blank) ---> PORDCR101
Constant(A)---
Assuming that A in input then in the output we want PORDCR101 Idoc means that you need only one occurence of the IDOC
For Source = B:
SourceField----
-----equalS ----ifwithoutElse ----then LineItem ---> PORDCR102
Constant(B)---
Regards,
ABhishek.

IDOC-Xi-IDOC: CRM - XI -R/3 (No service for system SAPOCC, client ** in ID)

Hi all
I am doing a scenario IDOC - Xi - IDOC where CRM sends an IDOC to R/3 via PI.
I have configured everything in OCC (CRM system), PI and BSC (R/3 system) but when I test it with the transaction WE19 in OCC nothing happens in PI or BSC.
All i can see if a message in SM58 transaction in OCC.
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - XI.
Status Text - No service for system SAPOCC, client *** in Integration Directory.
Could anyone tell me what is the problem.
Your help will be very much appreciated
Regards
Naina

Error message: No service for system SAPCRD client 201 in the integration directory
Cause: There is no service without party in PI server that represents OCC server with client details.
Solution:
We send IDocs from system OCC to PI. In the control record (Segment EDIDC40) of the IDoc, the SNDPOR (SenderPort) field contains the value "SAPCRD". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service)
In System Landscape Directory (SLD) create a technical system for OCC system and assign a client for the same. Don't forget to assign an "ALE logical system" to the technical system created. Create a business system for this technical system. Then Business System can be imported under service without party/update the details existing in PI.
Edited by: Rodrigo Alejandro Pertierra on Jun 23, 2010 10:28 AM

Issue in IDOC-XI-IDOC scenario

Hi,
We are facing a strange issue in an IDOC-XI-IDOC scenario. We are using a SAX parser to parse the code here.
The error we are getting in 'sxmb_moni' is
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS</SAP:P1>
<SAP:P2>java.lang.RuntimeException</SAP:P2>
<SAP:P3>For input string: ""</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS a java.lang.RuntimeException was thrown: For input string: ""</SAP:Stack>
The strange thing is, when I restart the message, it gets processed successfully. Also, when I copy the payload, and test the same on a different environment, it gets processed successfully.
Would really appreciate some pointers here!
cheers,
Prashanth

Hi,
This related to mapping error check it once again.Check in Interface mapping Test tab.see the result.check the sxmb_moni and get the source of mapping come back to interfcae mapping and test .
See the below links
Hi I got EXCEPTION_DURING_EXECUTE in RWB->Message Monitoring
I am getting MAPPING EXCEPTION_DURING_EXECUTE
EXCEPTION_DURING_EXECUTE- Error in Mapping. Doubt about IE and AE
EXCEPTION_DURING_EXECUTE
Mapping problem - EXCEPTION_DURING_EXECUTE
ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION
Regards
Chilla..

IDoc-Tunnel - IDoc is rejected

Similar Messages

Maybe you are looking for