IDOC not to be converted to XML-IDOC

Hi
there is a setting you can make in XI so that IDOCS sent to XI from R/3 are not converted to XML-IDOC.
That parameter is XML_CONVERSION.
I found out from SAP today that this will only work if you are sending from R/3 to R/3 via XI.
But I want this to work for R/3 to ThirdParty via XI.
So SAP are saying this will not work.
OK - so does anybody have a simple XSLT I can use that will strip out the XML tags so I have a plain old IDOC ?

Hi,
1.if, so then ask him to provide SAP at target (in this case its possible)...there is no other option.(as of now SAP does't provide these kind of functionality)
2.otherwise if he required the same structure at target then go with IDoc...PI...File scenario
Please explain to your end user clearly about IDoc functionality..hope he will understand..
Rgds,
MFH

Similar Messages

Converting ISO20022 XML Payment file to PAYEXT iDoc using PI 7.1

Hi All,
As per my requirement : R/3 generates ISO20022 XML Payment file . PI will pick the file and converts into PAYEXT Idoc and send back to the same R/3.
I have some doubts regarding this...
1)Is ISO20022 XML Payment file also like normal xml file in R/3 OR different.
2) Can we use file adapter to pick the file.
3)Any modules required in CC.
4)Can I go with normal file to Idoc scenario.
Thanks
Drumi

solved

Display XML Idoc for people who do not understand XML

Hi,
does anybody know an easy way to make an Idoc XML readable for people who do not have any knowledge about XML?
This request comes from our sales department. We store incoming ORDERS.ORDERS05 Idocs from customers in XML format on a file server before mapping and sending them into an R/3 system to create the sales orders. For some reason, the sales people in our company sometimes have to have a look at the original incoming file.
Our intension is to give them an easy tool to open the Idoc XML and get it displayed in a more or less clearly arranged way, maybe as HTML table or something similar. Unfortunately I am not too familiar with XSLT.
Any ideas?
Thanks,
Philipp

Hi Philipp,
you need to do some kind of transformation. XSLT would be my first idea, but if you are not familiar with it, it might be worth a try to have a look at graphical report generators. They will take the hassle of doing manual coding from you.
Or there are XSLT mapping tools available which allow you to transform from XML to HTML, doing basically the same thing.
I do not know if I am allowed to supply some product names here, but I guess a google query for "report generator" or "xslt mapping tool" will yield some results.
Cheers!
Stefan

Receiving binary IDOC via Queue and convert it to XML-IDOC

Hello,
we are focusing the following scenario:
We receive an plain, binary IDOC in a MQSeries Queue. We want to pick it, transform it and place it into R/3 (of course using XI 3.0). Afterwards the other way around.
I know the Howto for the ABAP mapping from XML-Idoc to plain IDOC. This may also work for our scenario. Do you agree?
The other way around is more difficult. I assume that - since the IDOC adapter resides in the ABAP stack - we cannot re-use an existant adapter module in the JMS adapter. Right?
I heared about JCO capabilities of "xmlizing" Idocs - but did not find hints within the javadoc. Anyway, would this really be the preferred way - writing an user exit for the adapter using JCO - to handle this? There must be a way to do it better, must it not?
How did you guys face this problem - I think its a common one...
Any starting points for a discussion are appreciated....
Greets,
helge

Hi Helge,
For the conversion of the incoming flat message, one could imagine a similar ABAP mapping as the one described for the XML->flat message conversion. The function module IDX_IDOC_TO_XML could be a good starting point for your search.
To perform conversions in the Java stack (e.g. in an adapter module) might be a quite complex task since you first have to get the IDoc metadata. And there you cannot reuse existing function modules.
Best regards
Joachim

Idoc be converted into XML format

Hi,
Can idoc be converted into XML format? If yes guide me the path , how to do?
Thanks
Avi

<b>Hi,
we can .
Follow the link
http://www.erpgenie.com/sap/sapedi/Conversion%20of%20IDOCs%20to%20XML%20format.pdf</b>
Thanks
Manju
<u><b>Don't repeat the Questions</b></u>

XML IDOC data (hosted on a web server) & handling multiple WSDLs

Hi ALL,
1)how to design an Interface for picking up an XML IDOC data (hosted on a web server) which will be uploaded to SAP or converted to a file
this is what the customer has given me ..can any one explain me this and help me how to more forward
2).This Interface must use UDDI concept because we are going to use multiple BAPIs /RFCs as WSDLs
what is this mean can any send me some document on this
3).Use web-service navigator concept as we will be handling multiple WSDLs
i worked on 1. to define a place holder in WebAS for holding the
wsdls.
2. publish the wsdls in WebAS UDDI Repostory
but i have never used web-service navigator concept as we will be handling multiple WSDLs what is the difference ..send me some step by step docs ..
thanks very much
RK..

1.I am not clear with the requirement too. THere is no big deal in sending XML to IDOC or File. Based on your requirement you have to import IDOC structure or ify ou are using file, create a structure for the file.
If u are asking about sendin the XML directly without mapping, even you can do that without MM and even IM.
Please be more elaborate and if you are not clear with what client said, paraphrase them or ask again. Its not good to start work unless we are very clear with the requirement.
you can say to my understanding i feel this, now pI will send data like this. Is it correct?
2. More information on UDDI
http://en.wikipedia.org/wiki/UDDI
I dont think you need to worry much about this now with many features provided in ESR especially
3. http://<Host>:<port>/wsnavigator/
The webservices going out of PI are published here.
provide host and port are host and port details of ext system.
Once you enter link in your browser, it shows the available webservices hosted there.
All you need is to click on the required wsdl and test it.
It is as good as sending your data from PI to other system.
It is similar to Altova XML spy but the difference here is you enter the values directly here but in XML spy we send XML .

Automate flat IDOC to XML IDOC using one interface

Hello all,
We are currently going through a migration process where XI will be replacing a legacy system. As part of our testing procedure, we are using historical data pairings from the legacy system and using an automated tool to compare if the interfaces we develop in XI match. The catch is we need the data that we are comparing in XML format for the automated tool to be able to do the comparison, and unfortunately the legacy data is a flat format. So now I would like to automate a way to convert this data to XML format.
Specifically for IDOCs, I would like to have an interface which picks up the flat files, transforms them to XML, and then drops them back into another file directory in the XML format. It would need to be able to pick up any kind of IDOC (given that XI has the metadata already imported), recognize what message type it is, then do the conversion.
I have been reading on SDN and found that there is a standard tool to do the conversion, but it appears it can only handle one kind of IDOC at a time, and it appears it only picks up one specifically named file at a time.
Has anybody tried to implement a scenario like this? Any help is appreciated (A walkthrough would be the best!).
Thanks in advance,
Mike

Mike,
What version of PI will you be using? PI 7.11 can now auto-convert Flat File IDocs to XML IDoc and vice versa.
Here is the documentation:
http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm (flat to XML)
http://help.sap.com/saphelp_nwpi711/helpdata/en/74/a45bc07e2043fb9b63295229178903/frameset.htm (XML to flat)
I have not tried this personally, but seems like you might be able to use a "File to File" scenario with no mapping, and use the "IDOCFlatToXmlConvertor" Module in your File Adapter Comms Channel and it may just work, giving you files that are the IDoc XML version of the flat file it is reading. It looks like it does an RFC call to the back-end SAP system where the IDocs are originally from (or could be any system as long as you know the IDocs in there are identical), and reads the IDoc metadata (which has always included flat file field offsets for each IDoc Segment Field), and applies that either to convert from flat file IDoc to XML IDoc, or XML IDoc to flat file IDoc.
It does mention that there is a limitation that there can only be one IDoc in the source flat file - could be a problem if you have many in one file, which is pretty typical.
Regards,
Brendan

Conversion of multiple xml idocs to flat file

Hi,
I did ABAP mapping to convert xml idoc to flat file by using the reference how to do abap mapping in xi3.0.pdf
It is working for only one idoc at a time.
If I have multiple idocs in a single xml file, the above code is not working.
Please let me know what cchange to be done to work out for this.
Hope am clear.
Regards,
Anil.

Look For the Occurances of target Field node...It should be 1 to unbounded

What is best way to connect a non-sap sys sending xml idocs to SAP system

Hi Can some one please guide as to what will be the best approach in connecting a NON SAP system to a SAP system.
The non sap system should not be connected to access real time data,it does not support RFC,it can send data in IDOC xml format and i think in teaxt files also.Also I dont think there is any EDI subsystem in place.
There has to be a periodic upload of material data from SAP /stock status/
then there will be incoming data into SAP for sales order/purchase order etc
What would be the best way to connect the two systems,IDOCs with partial EDI looks the best way ,but I am confused as to how will the XML IDOC be converted to normal IDOC and viceversa,how to handle the event triggering mechanism.
If someone has experience in such a scenario ,please help.
There is a option to update the database of the application through SQL also...

Hi,
Check this link.
Web Services from Function Module
it might help u.
Thanks.

IDOCType PORDCR101 : XML IDoc conversion: No known segments identified

Hello all,
I'm strugling with the mapping to the IDOC create puchase order PORDCR1.PORDCR101.
The source structure for the moment is exactly the same as the target strcuture i.e. our IDOC.
So I would not expect to much problems with this one.
However, when sending the message we get the following error in SXI_MONITOR:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I also augmented the trace lvl to 3 and got the following in the Trace-part of TC SXI_MONITOR and
suspect it starts to get wrong already in the beginning
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
Trace level="1" type="T">Convert one IDoc</Trace> .
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore segment field: COMP_CODE</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADERX</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADERX</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOADDRVENDOR</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOADDRVENDOR
I already found the four or so other threads on the SDN website about this error and in the mean-time tried them (delete and reload the structure with IDX2, set the begin and segment-attribute to 1, make sure that the segments-names self are also mappend) but to no avail.
We just implemented two other IDOC's (DELVRY03 and WMMBID02) and they arrive at SAP without problmens.
Hope you have form ideas to get me out of this one.
Tnx and best regards.
Bart.

Hi Bart,
We had a similar problem.... It took us 2 days to find out what the problem was... Nothing on SDN was helpfull so far... First we incremented the trace level of XI to see the debug messages... Then we saw that certain segments could not be identified and are ignored, others not...
So further investigation in IDX2 to the specific IDoc with problems showed us a list with all used segments and their versions. Some segments had only 1, others had more versions....
So we could identify the problem as a segment version problem. It seemed that our IDoc Communication Channel took not the most recent version. So we changed the "Segment Version" to the most recent one and the problem was solved!
Please reward points if this was usefull to you...
cheers!
Pedro

Importing an idoc with namespace extension gives strange XML tagnames in PI

Hello All,
We have created an extension to the ORDERS05 idoc in a namespace. The extension is called "/cclcl/zorders05", "/cclcl/" is the ABAP namespace. We want to use this Idoc in SAP PI and send the Idoc in XML format to a external party. The XML format of the Idoc is generated in SAP PI, when we import the idoc in the Enterprise Service Repository. The root element of the XML is being generated as <_-CCLCL_-ZORDERS05> (see idoc xml example below). The "/" characters are converted to "_-" and therefore the XML rootelement looks very strange. How can we use idoc extensions under a ABAP namespace and have normal rootelements in the idoc xml of SAP PI (without the "_-" characters)?
<?xml version="1.0" encoding="UTF-8"?>
<_-CCLCL_-ZORDERS05>
<IDOC BEGIN="">
<EDI_DC40 SEGMENT="">
<TABNAM/>
<MANDT/>
<DOCNUM/>
<DOCREL/>
<STATUS/>
<DIRECT/>
<OUTMOD/>
<SUNIT/>
<WAERQ/>
</E1EDS01>
</IDOC>
</_-CCLCL_-ZORDERS05>
Kind regards,
Mark

Hi, Mark van Dooren
I think i could not put the statement in proper manner in previous post ,i feel,
when u import a Idoc from an R/3 system,u will get the XML structure in which u will be haveing the '/' character
replaced by '_-'.
And when u use this XML structure(of Idoc) and export it to the external system,then the structure will be automatically converted into the normal XML structure in destination system.
This part u need not to take care externally.....
I hope i made my statement clear..

Convert custom outbound idoc to CSV file

Hi
I need to send generate a flat file that will be sent to a non SAP partner. A requirement is that the messages go via the IDOC system. This makes it possible to resend them if necessary.
So there are 2 stages
1) create IDOC. I have done this
2) read IDOC and convert to flat file
stage 1
=====
I have defined a custom IDOC, partner profile etc and developed a Function Module to create the outbound IDOCs The FM is triggered by a message in the NAST table. . This works OK.
So I now have custom outbound IDOCs in the DB with status 30 (ready for dispatch) (WE05).
Stage 2
======
Now I want to convert these custom IDOCs into simple flat files (CSV like).
How do I go about making this happen? I guess I need to develop another Function Module. But I dont know how to tie this FM into the system. My questions are:
How will the FM be triggered
what is the interface of the FM
will I need to configure a 2nd partner profile for stage 2 (which is fine)
Peter
Note1 - there is no EDI converter available so must solve this in ABAP
Note2 - I do not want to create the flat file at the same time as I create the IDOC. This would defeat the purpose of going via IDOCs

No, EDI is only one method of transferring data. There's no need for an EDI subsystem in this case.
To the OP, since it seems the you have decided that you must use IDOC processing in this case, I would go ahead and use a file port (or an XML port). You will drop an IDOC formatted flat file into the specified location (for each IDOC, based on your logical file definition). For you, this will merely be a temporary holding location. You can then use a simple program to read the file, re-format it, send it, then move the original file to a 'processed' location. Of course, you could also just throw away the generated files and read the IDOCs directly with the standard functions available and (re)generate/send the files as required.
It's often done this way with 3rd party EDI providers, where the company in question is required to use EDI by their customers but do not have the required systems in place.

Issues with creating and sending BOM XML IDOC to SAP using 2010 WCF-SAP Adapter (without using Biztalk Server)

I'm trying to replace an existing Biztalk 2006 Send BOM IDOC process, and completely remove Biztalk server from the equation. The existing Bizatalk 2006 server receives an input BOM (Bill of Materials) flat file, and using a Biztalk Map (BM08),
and Orchestration, generates an Idoc and sends it to SAP.
In my replacement C# program, I'm using the 2010 WCF-SAP Adapter, and am trying to generate the BOMMAT03 XML IDOC it to SAP.
I generated the BOMMAT03 schema from SAP using the Add Adapter Service in VS 2010. I was able to generate a BM08 XSLT from the existing BMO8 map in the current Biztalk 2006 process. I am able to run a XSLT transform on the input BOM flat
file, and generate an XML file from that.
However, I've run into a few issues. First of which, is that the XML file that is generated from the XSLT transform is NOT the same schema as the BOMMAT03 schema expects. It's somewhat similar, but different enough that I have to manually
translate between the two in my code. I've verified that both the original Bitztalk 2006 process and my replacement program use BOMMAT V3 from SAP. Question--Is Biztalk 2006 server doing some other magic to turn that transormed XML into the BOMMAT03
schema?
I ended writing code which translates the transformed XML into the BOMMAT03 schema (which is a strong typed XML IDOC at this point).
However, when I try to send the BOMMAT03 XML IDOC, I get an exception "Object reference not set to an instance of an object."
idocClient.Send(idocData, ref sadapterTxGuid);
idocData is of type BOMMAT03, and I've verified that the various fields are populated.
Any help is appreciated.

Well, putting in a MSDN subscription support ticket for Biztalk server actually helped with the issue. They didn't find, or fix the issue directly. But one of the examples (https://randypaulo.wordpress.com/tag/idoc/) they sent over, jogged my
memory, and I realized in the code snippet below, I had accidentally deleted the 1st line. Such a simple mistake, yet was easy to overlook. The URL example is almost EXACTLY like my code, but without the transform and translation code to convert
from input XML file to IDOC XML. If someone is interested in that, let me know.
//Forgot the 1st line.
idocClient = new IdocBOMMAT03SIEIS_WED_BOMMAT03V3R700Client(binding, endpointAddress);
idocClient.Send(idocData, ref sadapterTxGuid);
For anyone else interested in knowing, you CAN send a strongly typed IDOC to SAP using C#.NET and the WCF SAP 2010 Adapter, using the IDOC Binding Client class you generated using the Add Adapter Service Reference in VS2010.
The one difference, which no one, not even the tech support from MS could tell me, was why the XSLT which I generated from the original map, did not transform the input BOM XML into the BOMMAT03 XML. Instead, it transformed it into an intermediate
XML, which resembled the BOMMAT03 IDOC XML, but still needed to be translated to the BOMMAT03 IDOC format.
The tech support person swore up and down that it should. But I believe that something happens in Biztalk server, after the Mapping occurs, maybe in the Pipeline, which converts that
intermediate XML into the final BOMMAT03 IDOC XML format.
I do think that the examples are severely lacking in showing how to send a strong typed IDOC using C# and the WCF-SAP Adapter. Even worse, the examples are completely lacking in how to actually generate a weakly typed IDOC. They show how to send
that weakly typed IDOC, but show me, or give me a class to be able to generate it.
I realize that this is not quite the "recommended way" to do it, but in reality, not everyone wants or even needs a full Biztalk installation. For some simple stuff like this, a C#.NET program and WCF-SAP adapter do the trick.

IDOC not displayed in WE05

Hi Experts,
I have successfully run my scenario CSV-pi-Idoc yesterday. IN MOni XML file is Ok. In R/3side (WE05) Idoc generated successfully. But Yesterday night Basis people change R/3 password. Now my problem is in R/3 IDOC not displayed in WE02.
Iam also change password in SM59. But no result. Where can I do changes. can any one help me.
Thanks
Hari

Hi Hari,
Make sure in SXMB_MONI in your PI system the message is showing successful flag in outbound side (ie.. drag the scroll bar to ur right had side and see if you can see checkered flag). If you see any error then go to tcode sm58 (trfc queue) and filter based on dates and u will find error logs in detail and take appropriate action.
Mostly it might be authetication problem so better to check in ur R/3 destination in Sm59 in PI system if your rfc test and authentication test is successfully showing green or not.
Thanks,
Prasanthi.

XML IDOC post to R/3 Via WAS - want to see error content with JavaScript

Hi,
I am posting XML IDOCs to our R/3 system via a webpage that I have built with JavaScript. I am posting to the WAS, which is configured to read the XML IDOC with SAP's standard class handler CL_HTTP_IDOC_XML_REQUEST. We are on basis 620 support pack SAPKB62041.
In my webpage, I have the JavaScript code set to read the status and statusText so I can see the response from WAS when I post my XML IDOC. However, I am getting back very generic information when I encounter a 409 error. THe statusText is always "input_not_found". So I debugged the class handler code and found that SAP is returning back the more descriptive error info in HTML format.
I ran a packet sniffer to see what WAS returns and the info looks like this:
<html><head><title>IDoc-XML-inbound not ok</title><h1>IDoc-XML-inbound not ok</h1></head><body>
E:Table Lookup Error:300 Cannot map value for field MESCOD in table ZFI_IF_IDOCORG using values
SNDSAD = |TE| and RCVLAD = |GL| and MESTYP = |ACC_DOCUMENT|</body></html>
I want to know how I can get my webpage to read this HTML info and store that into an alert so I can read this text that I'm returning back to the HTTP post.
This is how my script looks. I'm using IE6.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
     <title>Test XML</title>
<SCRIPT ID=clientEventHandlersJS LANGUAGE=javascript>

</SCRIPT>
</head>
<body>
<BR>
This page posts to
<BR>
http://some_server:1089/sap/bc/zxml_idoc?sap-client=200&sap-language=EN
<FORM name=xmlform method=post >
<P><TEXTAREA style="WIDTH: 623px; HEIGHT: 369px" name=xmlData rows=23 cols=77>
</TEXTAREA>
<P>
<INPUT type="button" value="Submit XMLHTTP" id=XMLHTTPButton name=XMLHTTPButton
LANGUAGE=javascript onclick="return XMLHTTPButton_onclick(document.xmlform.xmlData.value)">
</form>
Previously with this class handler, SAP returned the detailed info back to the "alert(xmlhttp.statusText)" and I had no problem seeing the return info. But now they have decided to format it in HTML and I don't know how to view this text since it has no ID on it to pull this into an alert box.
If anyone has any ideas, please let me know.
Thanks,
Andrea

Ok!
I have solve the problem. So, I was trying to connect via SSO within an user that was not registered in R/3 and I forgot it.
Sorry for the inconvenience.

IDOC not to be converted to XML-IDOC

Similar Messages

Maybe you are looking for