IDoc XML Conversion Issue

Hi Exerts,
When IDoc sent from R/3 got successfully loaded with all segments in WE02 wihtout overlapping,
I find the data gets overlapped in XML only for a deep routed structure in sxi_monitor, while WE02 has no issue for it.
Analysis made:
1. IDoc details had been checked for the field which has 18 digits, but at XML it receives only 5 digits after which it loads to next element of that structure.
2. When i crosschecked with cache, it was fine and i even activated once with the updated metatdata from R/3.
Queries:
1. From R/3 end, everything looks fine by analyzing WE02, i also checked by running IDOC_XML_TRANSFORM, but this XML has generated the proper data as seen in WE02. Where did it get this issue for overlapping in Integration engine? Will R/3 use this standard function module to transform to XML message or any else that creates this unknown error?
2. I activated the complete objects in repository and also checked the cache status, but still it gets me the same overlapping at XML under the Inbound message. Could anyone kindly clarify why this happens?
Helpful answers will be rewarded.

Santhosh,
Thanks for the quick response.
I cross-checked already in IDX2 for the segment reflections as defined in R/3.
But unforgetedly i missed checking the outbound ports which had required this updations....
This works well...
Here is your granted points.
Thanks a lot for remainding me this resolution Santhosh...
Thanks!
Regards,
Dhayanandh .S

Similar Messages

Flat Idoc to Idoc XML conversion error.

Hi All,
We are using PI 7.1 EHP1, Where in we would like to see the capabilty of User-Module for Conversion of IDoc Messages Between Flat and XML Formats. Gone thru the below blog and maintained the necessary NWA configurations:
How to Use User-Module for Conversion of IDoc Messages Between Flat and XML Formats
While testing phase, The file is not been picked by the Sender File Adapter and the below error is been displayed in RWB:
"MP: exception caught with cause com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: Invalid character encountered in XML input data source: state=INITIAL, charPosition=0, lineNumber=1, columnNumber=1, invalidChar=U+0045, sourceSnippet=...EDI_DC40 510000000002889077846C 3012 SHPMNT05 ZSHPMNT9 S... ^"
Any Clues?
Thnx

Hi Stefan,
You are right i have maintained the mandatory parameters (SAPRelease, SourceJRA, TargetDestination) within the sender File adapter module key parameters.
Now getting another error within Comm Channel Monitoring:
MP: exception caught with cause java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Any Clues?
Thnx

IDoc xML character issue

Dear expert,
I meet a intractable issue in our SAP system.
The scenario as below:For our product shipping to china,the ship-to of Sales Order should be chinese.
when i give the response to customer using ALE IDoc which is std in sap,the EDI-Subsystem can't parse the xml file! So our customer can't receive the data.
After tracing the issue,i find it is the chinese charater to beget this.
Actually the idoc file is the ANSI coding.
Can anybody help me ?
Thank you very much.

Dear
I find the really reason is that the R/3 System is Non-Unicode System,the ECC 6.0 is Unicode System.
Is my viewpoint right?
Pls give me some advice.
TKS!

IDOC-- XML conversion

Hi all,
Could anyone let me know if there is any method of converting IDOC to XML with out using XI or any EAI tools?
Raghav

Raghavan,
If you want to convert an idoc to XML (write to XML file), then ALE has a simple mechanism to do it.
Please read the following post in SDN , wherein we can define a XML port (instead of a file port) to convert a idoc to XML
convert IDOC data to XML format.
Some post also list the required FM to achieve the same

XML conversion issues

Dear all,
I am using oracle8i. I would be pleased, if you could answer for this questions.
create table dept(deptno number,
dname varchar2(20),
loc varchar2(20));
alter table dept add primary key(deptno);
create table emp(empno number,
ename varchar2(20),
deptno number);
alter table emp add primary key(empno);
alter table emp add constraint fk_dept foreign key(deptno) references dept;
insert into dept values(10,'Account','Houston');
insert into dept values(20,'Finance','Austin');
insert into dept values(30,'Finance',NULL);
insert into emp values(101,'Krish',10);
insert into emp values(102,'Sam', 10);
insert into emp values(103,'Scott',20);
insert into emp values(104,'Brent',20);
I have a procedure to covert the data into XML.
CREATE OR REPLACE PROCEDURE STP_SAMPLE_XML AS
v_context DBMS_XMLQUERY.CTXTYPE;
v_document CLOB;
v_offset NUMBER := 1;
v_chunk VARCHAR2(4000);
v_chunk_size NUMBER := 4000;
l_file UTL_FILE.FILE_TYPE;
BEGIN
l_file := UTL_FILE.FOPEN('D:\Data\XMLFILES', 'sample.XML', 'w');
v_context:= DBMS_XMLQUERY.NEWCONTEXT('SELECT DEPTNO,DNAME,LOC,
CURSOR(SELECT EMPNO,ENAME,DEPTNO
FROM EMP EMP_DETAILS
WHERE EMP_DETAILS.DEPTNO = DEPT.DEPTNO) EMP_PAYEE
FROM DEPT');
DBMS_XMLQUERY.USENULLATTRIBUTEINDICATOR(v_context,TRUE);
DBMS_XMLQUERY.SETROWSETTAG(v_context,'EMP');
DBMS_XMLQUERY.SETROWTAG(v_context,'EMP');
v_document := DBMS_XMLQUERY.GETXML(v_context);
WHILE( v_offset < DBMS_LOB.GETLENGTH( v_document))
LOOP
v_chunk := DBMS_LOB.SUBSTR(v_document,v_chunk_size,v_offset );
UTL_FILE.PUT(l_file, v_chunk );
v_offset := v_offset + v_chunk_size;
END LOOP;
UTL_FILE.FCLOSE(l_file);
DBMS_XMLQUERY.CLOSECONTEXT(V_context);
END;
This procedure gives the below output.
<?xml version="1.0" ?>
- <EMP>
- <EMP num="1">
<DEPTNO>10</DEPTNO>
<DNAME>Account</DNAME>
<LOC>Houston</LOC>
- <EMP_PAYEE>
- <EMP_PAYEE_ROW num="1">
<EMPNO>101</EMPNO>
<ENAME>Krish</ENAME>
<DEPTNO>10</DEPTNO>
</EMP_PAYEE_ROW>
- <EMP_PAYEE_ROW num="2">
<EMPNO>102</EMPNO>
<ENAME>Sam</ENAME>
<DEPTNO>10</DEPTNO>
</EMP_PAYEE_ROW>
</EMP_PAYEE>
</EMP>
- <EMP num="2">
<DEPTNO>20</DEPTNO>
<DNAME>Finance</DNAME>
<LOC>Austin</LOC>
- <EMP_PAYEE>
- <EMP_PAYEE_ROW num="1">
<EMPNO>103</EMPNO>
<ENAME>Scott</ENAME>
<DEPTNO>20</DEPTNO>
</EMP_PAYEE_ROW>
- <EMP_PAYEE_ROW num="2">
<EMPNO>104</EMPNO>
<ENAME>Brent</ENAME>
<DEPTNO>20</DEPTNO>
</EMP_PAYEE_ROW>
</EMP_PAYEE>
</EMP>
</EMP>
But i want to achive the output as below. How can i do this ?.
I want to remove - <EMP_PAYEE_ROW num="1"> tags, and
i want to change the tag <EMP_PAYEE> to <EMP-PAYEE> tag,
<?xml version="1.0" ?>
- <EMPIMPORT>
- <EMP>
<DEPTNO>10</DEPTNO>
<DNAME>Account</DNAME>
<LOC>Houston</LOC>
- <EMP-PAYEE>
<EMPNO>101</EMPNO>
<ENAME>Krish</ENAME>
<DEPTNO>10</DEPTNO>
</EMP-PAYEE/>
- <EMP-PAYEE>
<EMPNO>102</EMPNO>
<ENAME>Sam</ENAME>
<DEPTNO>10</DEPTNO>
</EMP-PAYEE/>
</EMP>
- <EMP>
<DEPTNO>20</DEPTNO>
<DNAME>Finance</DNAME>
<LOC>Austin</LOC>
- <EMP-PAYEE>
<EMPNO>103</EMPNO>
<ENAME>Scott</ENAME>
<DEPTNO>20</DEPTNO>
</EMP-PAYEE/>
- <EMP-PAYEE>
<EMPNO>104</EMPNO>
<ENAME>Brent</ENAME>
<DEPTNO>20</DEPTNO>
</EMP-PAYEE/>
</EMP>
</EMPIMPORT>
Any webpages to read for solving this issues...
It is urgent. Thanks
Govind

Govind,
Create a view of the data the way you want it displayed with the column names to match. Then produce the XML from the view.

Issue in Excel to XML Conversion

Hi Gurus,
I am creating a custom java module in sap nwds 7.3 for Excel to XML Conversion. But I am getting following error
Classpath dependency validator message.
Classpath entry will not be exported or published. Runtime ClassNotFoundExceptions may result.
I imported the Jars from a different PI system and i am using NWDS in local PC with creating a separate folder with all JARs and also imported them using build path option.
This issue is occuring for all the jars imported.
I am using following code.
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.AbstractTrace;
import java.util.HashMap;
import jxl.Cell;
import jxl.Workbook;
public class JavaMappingExcelToXML implements StreamTransformation{
private Map map = null;
private AbstractTrace trace = null;
public void setParameter(Map arg0) {
map = arg0; // Store reference to the mapping parameters
if (map == null) {
this.map = new HashMap();
public static void main(String args[]) { //FOR EXTERNAL STANDALONE TESTING
try {
FileInputStream fin = new FileInputStream ("c:/ashu.xls"); //INPUT FILE (PAYLOAD)
FileOutputStream fout = new FileOutputStream ("C:/Users/ashutosh.a.upadhyay/My Documents/ashuXML2.xml"); //OUTPUT FILE (PAYLOAD)
JavaMappingXLStoXML mapping = new JavaMappingXLStoXML ();
mapping.execute(fin, fout);
catch (Exception e1) {
e1.printStackTrace();
public void execute(InputStream inputstream, OutputStream outputstream) {
String msgType = "Message Type name will come here";
String nameSpace = "Namespace Name will come here";
String xmldata = "";
try {
Workbook wb = Workbook.getWorkbook(inputstream);
xmldata ="<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"+ "<ns0:"+msgType+" "+"xmlns:ns0=\""+nameSpace+"\n">";
Cell[] cells ;
Cell[] cellNames ;
cellNames = wb.getSheet(0).getRow(0);
for(int j=1;j<wb.getSheet(0).getRows();j++){
xmldata = xmldata+"\n<Record>\n";
cells = wb.getSheet(0).getRow(j);
for(int i=0;i<wb.getSheet(0).getColumns();i++){
xmldata = xmldata+"\t<"+cellNames[i].getContents()+">"+cells[i].getContents()+"</"+cellNames[i].getContents()+">\n";
xmldata = xmldata+"</Record>";
xmldata = xmldata+"\n</ns0:"+msgType+">";
System.out.print(xmldata);
xmldata.getBytes();
wb.close();
byte by[] = xmldata.getBytes();
outputstream.write(by);
inputstream.close();
outputstream.close();
System.out.println("\n"+"File processed");
catch (Exception e) {
e.printStackTrace();
Request you to guide how to resolve this issue.
Thanks in advance

Thanks Anand,
PDF shared by you was extremely helpful. Now I have successfully developed and deployed the adapter. But while using it in Communication Channel I am getting following error.
Error: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name localejbs/ExcelToXML, cannot resolve object reference. [Root exception is javax.naming.NamingException: Error occurs while the EJB Object Factory trying to resolve JNDI reference Reference Class Name: Type: clientAppName Content: sap.com/SAP_Exel_To_XMLEAR Type: interfaceType Content: local Type: ejb-link Content: Excel_To_XML Type: jndi-name Content: ExcelToXML Type: local-home Content: sap.com.excelToXML.Excel_To_XMLLocalHome Type: local Content: sap.com.excelToXML.Excel_To_XMLLocal com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/SAP_Exel_To_XMLEAR; nested exception is: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/SAP_Exel_To_XMLEAR]. at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:398) at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:182) at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:144) at com.sap.engine.services.ejb3.runtime.impl.EJBObjectFactory.getObjectInstance(EJBObjectFactory.java:63) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:76) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33) at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:226) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283) at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:434) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:223) at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:242) at javax.naming.InitialContext.lookup(InitialContext.java:351) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:69) at com.sap.aii.af.lib.util.ejb.FastEjbFactory.createEjbInstance(FastEjbFactory.java:50) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.getModuleLocal(ModuleProcessorBean.java:419) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:287) at sun.reflect.GeneratedMethodAccessor946.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:74) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at com.sun.proxy.$Proxy3299.process(Unknown Source) at com.sap.aii.adapter.file.File2XI.send(File2XI.java:3605) at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1374) at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:669) at com.sap.aii.af.lib.scheduler.JobBroker$Worker.run(JobBroker.java:534) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:280) ]
pl
please help

Idoc flatfile to IDOC xml issue with new PI7.11 module SAP_XI_IDOC/IDOCFlat

Hi,
I am trying to develop a scenario as mentioned in the blog using the new module available in PI7.1,but I am getting this error
"Error: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS05" is unavailable."
I have made every configuration correct and IDOC meta data available in both SAP R3 and PI,but it is still complaning about the meta data does not exist.
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743%3Fpage%3Dlast%26x-order%3Ddate
did anybody face issue with the new module available "SAP_XI_IDOC/IDOCFlatToXmlConvertor",please help me or give me mre information why I am getting this meta data error.
Thank you,
Sri

Hi Sri,
To Convert IDOC Flat file into IDOC xml from the given blog, the IDOC flat file should be present in standard format like:
E2EDK01005                    0000047110815000000000001.........
E2EDKA1003                    0000047110815000000000002.........
E2EDKA1003                    0000047110815000000000003..........
E2EDKA1003                    0000047110815000000000004........
The Flat file have relationship as IDOC Number "000004711081500000" and segment sequence "0000001".
If your flat file is not in this formate so i don't think that module is able to convert into IDOC xml. and if your file is already in this format then it may be issue with destinations which are created in NWA.
Thanks
Harish

Error in Idoc to XML conversion

Hi,
I am doing Idoc to XML conversion using standard program RSEINB00. Can anyone plz tell me what are the pre-requisites to executing this program? I am getting an error message Port XXX segment defn YYYYY in IDoc type ZZZZZ CIM type do not exist.
Why am i getting this error? and what is the slution for it?
Regards,
Mateen.

Hi
Delete the metadata in IDX2 for the corresponding IDOC type in PI.
Also re-import the same in IDX2.
Reimport the IDOC type into Integration Repository under your SWCV.
Then check it..
Refresh the cache also.

SAP IDOC XML to Flat File Conversion

Hello,
I have downloaded SAP schema through the "Consume Adapter Service" with properties GenerateFlatFileCompatibleIdocSchema = "true" and FlatFileSegmentIndicator = "SegmentType". I am trying to convert IDOC XML into a IDOC Flat File.
Though the flat file gets created it has a "/" at the end of each blank field which I do not want in the flat file. I see the schema has <recordInfo structure="delimited"...> which I believe should be "positional". I tried
changing preserve_delimiter_for_empty_data="True" and suppress_trailing_delimiters="False" properties also but did not help.
I would appreciate any help on this.
Thanks,
Tarun

Hi Tarun....
please check this property set this property GenerateFlatFileCompatibleIDoc is set to false

CDATA issue in RFC XML conversion

Hi all,
I am trying to consume a webservice from ABAP. One of the webservice method responds with a data holding an xml fragment under the tags CDATA, like,
<!CDATA[[<?xml version="1.0" encoding=.....]]>
But the program throws exception during RFC XML conversion.
However i could find the correct response payload in the error log in ST11 transaction.
Pls advice.

Hi,
as this is not a proper CDATA
try:
<![CDATA[ cdata text ]]>
you can test it easily by opening with IExplorer
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Creating IDoc XML and sending to XI

There is a mechanism to create IDoc XML within SAP ERP through the use of
Change Pointers in concert with a port of type XML File (WE21). This is well
documented in this document.
http://www.erpgenie.com/sap/sapedi/Conversion%20of%20IDOCs%20to%20XML%20format.pdf
My question is whether the IDoc XML can be generated using Change Pointers and
the resulting IDoc XML be sent to XI through a RFC Adapter.
Please don't suggest using an IDoc Adapter. I already know how to do that.
Thanks
Vamsi

Hello Vamsi,
2) You need use Sender File Adapter for this.Not by RFC Adapter
1)yes, you can generate IDOC-XML using Change pointer
for better understanding...
Re: Change pointers trouble
CHANGE POINTER SAPAPO/C5
Re: Change pointer issue!!
If you want to know the basic concepts of Change pointers...Search SDN..you will find lot of info regardin this...
******************Reward points,if found useful

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

Send / Receive Idoc(XML) in SAP ECC 5.0

Hi Experts,
We are using SAP standard idocs to exchanges master data and Sales data between SAP and non SAP system. currently all the idocs are generated and posted as flat file structure.
There is possiblity to use idoc(XML) and HTTP service instead of standard process without XI?
All info related with this is welcome. is it possible? how?
all suggestion n helpful ans will be rewards with points.
regards: gaurave.

Hi Gaurave,
I have comae accross this type of issue once and hope the below link will give you an idea.
http://msdn2.microsoft.com/en-us/library/cc185479.aspx
thanks,
KIRAN

Adapter module in PI 7.1 EhP1 for Falt File Idoc to Idoc xml transformation

Hi Experts,
In PI 7.1 (EhP1) there is a java adapter module that can be added to the file adapter that automatically transforms Flat File representation of IDoc to IDoc XML. Can anyone provide the link to this particular module? Tried searching but could not get the specific module name or parameters.
The same conversion can be achieved using a standard SAP provided ABAP mapping but we need to use the module in this case.
Thanks and regards,
Shiladitya

/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
FYI~~~

Error: IDoc XML data record

Hi all,
 We have file->XI->idoc scenario and the problem we are facing is like, when the idoc structure is prepared using XSLT mapping, when the idoc is ready to get in thru the idoc adapter we are getting the following error.
Error: IDoc XML data record: In segment
Z1UKGAS_HEADR attribute occurred instead of SEGMENT 
Anyone faced the same issue....if so pls do throw some light into this issue....
We r in XI 3.0 SP13...
Thanks & regards,
Jayakrishnan

Hi,
In an IDOC structure segment attribute is requried. From the error you posted, it looks like seqment attribute is missing.
<Z>
 <IDOC BEGIN="">
 <ED SEGMENT="">
 </ED>
 </IDOC>
</Z>
Naveen

IDoc XML Conversion Issue

Similar Messages

Maybe you are looking for