XI content in AII

Hi experts,
Iam new to AII. How to make use of XI content in AII in order to communicate with XI.How can we configure this in XI.
Reyaz Hussain

Refer to the flexible delivery config guides in www.service.sap.com/scm
Go under rfid section to download the latest flexible delivery scenario guide. This will give you detail step by step configurations that needs to be maintained for XI and AII communication.
Hope this helps.
Regards,
Ashish

Similar Messages

Version to be downloaded

Hi
I gave to download contents for AII and OER from marketplace. I am using PI 7.1 EHP and AII is SAP EHP 2.
So when I download which content should I consider? Should it be based on my PI version or the AII version? The scenario involves proxies, so do I need to download the Proxy code to ECC as well?
Regards

Hi,
>>>So when I download which content should I consider? Should it be based on my PI version or the AII version? The
XI content should be for AII version - but I don't believe there are any changes for this
>>>so do I need to download the Proxy code to ECC as well?
no, stadnard proxies are already there in AII& ECC systems - you just need to connect PI to AII and to ECC
Regards,
Michal Krawczyk

Com.sap.aii.utilxi.misc.api.BaseRuntimeException:An invalid XML character (Unicode: 0x1f) was found in the element content of the document

Hi,
I'm getting the below runtime exception during IDOC- SOAP message mapping in Integration engine.
"Runtime exception occurred during application mapping com/sap/xi/tf/<<<\\Message mapping object name\\>>>; com.sap.aii.utilxi.misc.api.BaseRuntimeException:An invalid XML character (Unicode: 0x1f) was found in the element content of the document"
I have no clue why this exception occurs. Could anyone say the reason of the exception?
Thanks!
Regards,
Gopi

Hi Gopinath
Check this thread
An invalid XML character (Unicode: 0x1d) was found in the element
Kind regards
Javi

How to resolve Content not allowed in prolog with PDF files

We are using PI 7.1 to read a file and using ASMA get the file name and pass it to a target mapping and call a web service with the file name.
We have a scenario that reads a PDF file as Binary form a folder. Our mapper uses ASMA to get the file name and folder of the
file to map to the target.
Testing in mapper works fine except for the ASMA does not function (known issue).
At runtime we drop a file and it is picked up as expected BUT from SXMB_MONI we see the following:
Runtime exception occurred during application mapping com/sap/xi/tf/_MM_FileNotification_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog.
This error does not happen all the time either. When it appears it is typically only the first time a file is mapped and on subsequent retries it processes normally. In dev we have shown that PI seems to get stuck on a few initial files u2013 process properly on the first retry and then at some point has no issues and will process files very fast.
u201CContent not allowed in prologu201D at least from an XML perspective is related to characters appearing before the xml file declaration:
<?xml version="1.0".encoding="UTF-8"?>
If chars appear before this you get this error in Java parsers. This could be related but we do not have control over how PI parsed the file content and puts into XML messages inside the mapper as we do nothing with the file content.
The same file will go through randomly with this exception on multiple drops. Sometimes it gets processed properly and sometime it doesnu2019t u2013 but in dev it u201Calwaysu201D gets processed properly on the automatic retry. It does not seem to matter what PDF we drop in there either.
Our tyoes look something like this:
Source:
DT_FILE - xsd:hexBinary
Target:
FilePath - xsd:String
I have tried with DT_FILE as xsd:base64Binary with the same results...
We use a UDF to get the file name from ASMA as follows:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
DynamicConfigurationKey key2 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","Directory");
String ourSourceFileName = conf.get(key1);
String ourSourceDirName = conf.get(key2);
//conf.put(key1, ourSourceDirName + "/" + ourSourceFileName);
return ourSourceDirName + "
ToProcess
" + ourSourceFileName;
Edited by: Carey Bingham on May 26, 2010 12:24 AM

> Is using a custom adapter module the standard way to handle files when we do not want the content?
I would rather say this is a feasible solution
> If so does anyone have generic code that we can use for the purposes of simply monitoring a file and passing the file name/folder out implemented as modules already?
The questio is. What do you want to do with this information?
Here is a sample code written for a specific purpose, you can adapt this to your needs:
http://wiki.sdn.sap.com/wiki/display/XI/AdapterModulePI7.0SetAttachmentName
> Is this a known workaround to get around the "content not allowed in prolog" issue?
At least it is known by me

Problem with file content conversion in receiver file adapter

Hi All
I have a problem with file content conversion in receiver file adapter.
This is my recordset structure: Header_Record,1,Claim_Record,*,Check_Rec,1
These are the content conversion parameters:
Header_Record.fieldSeparator = ,
Header_Record.endSeparator = 'nl'
Claim_Record.fieldSeparator = ,
Claim_Record.endSeparator = 'nl'
Check_Rec.fieldSeparator = ,
Check_Rec.endSeparator = 'nl'
In SXMB_MONI, i can see that the data is correctly extracted from proxy, and correctly mapped to receiver message, and i see a checkered flag (success).
But, Adapter status is RED with the following error message:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
In communication channel monitoring, i get the following error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages
What is going wrong here? Can anyone please tell me?
Thanks
Chandra

Posted in Incorrect forum.
Posted again in Process Integration forum

Email Integration Scenario - Issue with email body content

Hi All,
We have an Email to File Scenario. PI is connected to Outlook server using Sender Mail Channel using POP3. We are able to fetch and display emails correctly for most of the received emails.
However we notice that for Email sent from few Mail server like Yahoo mail, Gmail, Hotmail, we are not getting the Email content correctly.
Issue is happening with Emails sent in HTML/Rich text format (containing Formatting and without any attachments). In the receiver system we see the email is converted to Plain text format. If the same email is sent with some attachment / Embedded Image, we get all the Formatting correctly in Receiver System.
A closer look at Pimon we found the following:
1. When Email is sent with Formatting (without any attachment/ image) in Pimon we see that it creates 2 Payloads (screenshot attached)
2. The First Payload - MainDocument contains the Email content in XML format, but is missing the Email formatting data in it.
3. The other Payload - ([email protected]) contains the actual Formatted Email Content.
Not sure why the formatting data is missing from MainDocument. Instead its coming in other payload. Due to this we are not able to display correct data at receiver end as we parse the MainDocument as our Input Payload Stream
Note: We cannot use payload swap bean, as it will swap the data for all the incoming emails which we don't want.
Anyone faced similar issue? Steps to get proper formatting data in MainDocument..
Suggestions / Inputs will be highly appreciated.
Thanks,
Azhar

Azhar,
We cann't influence the behavior of Gmail, Hotmail. But have to get HTML as main payload, so we have to swap payload (not always, in some cases based on a condition). Please try below Java mapping. In Operational Mapping set "Read Attachments".
package javaapplication1;
import java.io.*;
import com.sap.aii.mapping.api.*;
import java.util.Collection;
public class NewClass6 extends AbstractTransformation {
 @Override
 public void transform(TransformationInput transformationInput, TransformationOutput transformationOutput) throws StreamTransformationException {
 try {
 InputStream inputstream = transformationInput.getInputPayload().getInputStream();
 OutputStream outputstream = transformationOutput.getOutputPayload().getOutputStream();
 byte[] b = new byte[inputstream.available()];
 inputstream.read(b);
 //Loop over attachments and if attachment name starts with 'payload-' swap it with main payload. Edit below logic as needed.
 Collection<String> listAtt = transformationInput.getInputAttachments().getAllContentIds(true);
 for (String att : listAtt) {
 if (att.startsWith("payload-")) {
 b = transformationInput.getInputAttachments().getAttachment(att).getContent();
 outputstream.write(b);
 } catch (Exception exception) {
 getTrace().addDebugMessage(exception.getMessage());
 throw new StreamTransformationException(exception.toString());

Email content line feeds using receiver mail adapter - HELP!

Hi all,
I have read the threads on how to download the XSD from SAP for creating a mail message type with dynamic To and From addresses and this is working fine. However, I am unable to create multiple lines in my mail message. I have the following parameters in my config:
XML2Plain - Transform.Class - com.sap.aii.messaging.adapter.Conversion
XML2Plain - Tansform.ContentType - text/plain;charset=utf-8
XML2Plain - xml.conversionType - SimpleXML2Plain
XML2Plain - xml.addHeaderLine - 0
XML2Plain - xml.fieldFixedLengths - 12,150
XML2Plain - xml.fixedLengthTooShortHandling - Cut
XML2Plain - xml.fieldSeparator - '0x0D''0x0A'
I have not changed the message type in the Design so the mapped Content field currently just contains one long line of 162 characters (as does the resulting email). I want 12 characters on the first line and 150 characters on the second line. Do I need to concatenate something between by 12-character and 150-character strings to achieve this? Do I need a line.Separator parameter in my module configuration?
Many thanks,
Stuart Richards

Hi Sreeramulu,
As mentioned by Lucas, you can use the UDF. Inn addition to that, you need to define the Variable Headers under Variable transport binding after enabling the Adapter Specific Message Attributes.
For the Enabling ASMA, follow the below steps and check for the variable attributes.
Select the Advanced tab page.
   To save adapter-specific attributes in the message header of the XI message, select Use Adapter-Specific Message Attributes and Variable Transport Binding.
The following attributes in the message header are then available for processing:
○       User: (technical name: TServerLocation)
○       Authentication key: (technical name: TAuthKey)
The following mail header fields are available for processing:
○       From: (technical name: THeaderFROM)
○       To: (technical name: THeaderTO)
○       Cc: (technical name: THeaderCC)
○       Bcc: (technical name: THeaderBCC)
○       Subject: (technical name: THeaderSUBJECT)
○       Reference to the mail that is to be replied to: (technical name: THeaderIN-REPLY-TO)
○       Reply to: (technical name: THeaderREPLY-TO)
○       Mail client program: (technical name: THeaderX-MAILER)
○       Send confirmation of receipt: (technical name: THeaderDISPOSITION-NOTIFICATION-TO)
○       Priority: (technical name: THeaderPRIORITY)
○       Importance of message: (technical name: THeaderIMPORTANCE)
   To transfer further header fields, set the relevant indicator for Variable Header. The technical names for the fields are XHeaderName1, XHeaderName2, and XHeaderName3.
The parameters are included in the mail header under the names specified here.
The attribute namespace for the adapter is http://sap.com/xi/XI/System/Mail.
Thanks,

How to change the HTTP Response as XML (Content Type "text\xml") ?

Hi Friends ,
                 I have created one RFC Destination TYPE H . When i am trying to post some XML Message to that particular HTTP Service using POST method . It succesfully accepted the XML File but , it is returning the String as " OK" . In the connection test trace i have seen the Content Type as "text/html" but * I need to get as "text\xml" .*
                 I need to get response back as XML not plain text .
        1 Any Configuration setting do we need to do on Service (SICF ) ?
         2. Or any other place we need to modify to get the HTTP Response as XML not plain text
              Can you please help to solve the problem . Any clue ?
Thanks & Regards.,
V.Rangarajan
Edited by: ranga rajan on Jan 2, 2008 2:07 PM

Dear users,
we have requirement sending SMS to the customers mobiles. I am successfully sending the messages to the customers mobiles by using the above method. Facing issues with response message. The response messages is in plain text fromat in single line like...Sent
Using HTTP_AAE Receiver adapter.
The response message was failed while excution of the message mapping with the error
Mapping failed in runtimeRuntime Exception when executing application mapping program com/sap/xi/tf/_MM_SMS_CUST_RES_; Details: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Content is not allowed in prolog.
please share the comments how to pass the Status of the message to SAP ECC from SAP HTTP adapter
Regards,
Sudir.

How to change the HTTP Response as XML (Content Type "text\xml") When Post

Hi Friends ,
I have created one RFC Destination TYPE H . When i am trying to post some XML Message to that particular HTTP Service using POST method . It succesfully accepted the XML File but , it is returning the String as " OK" . In the connection test trace i have seen the Content Type as "text/html" but * I need to get as XML format no Srting ( Type "text\xml" . ) *
I need to get response back as XML not plain text .
1 Any Configuration setting do we need to do on Service (SICF ) ?
2. Or any other place we need to modify to get the HTTP Response as XML not plain text
Can you please help to solve the problem . Any clue ?
Thanks & Regards.,
V.Rangarajan

Dear users,
we have requirement sending SMS to the customers mobiles. I am successfully sending the messages to the customers mobiles by using the above method. Facing issues with response message. The response messages is in plain text fromat in single line like...Sent
Using HTTP_AAE Receiver adapter.
The response message was failed while excution of the message mapping with the error
Mapping failed in runtimeRuntime Exception when executing application mapping program com/sap/xi/tf/_MM_SMS_CUST_RES_; Details: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Content is not allowed in prolog.
please share the comments how to pass the Status of the message to SAP ECC from SAP HTTP adapter
Regards,
Sudir.

Content conversion in Sender JMS Adapter

Hi,
Scenario is file to IDoc
My source file is   ' ; ' separated file coming from MQ via JMS adapter. now I need to convert this to XI.
Source DT looks like
Root
HEADER (Occurance 1)
     Field 1
     ISOCURCD
     TRANKODE
     IDENTIFIER
     DATO
     TIME
DETAIL(Occurance 1 to unbounded)
     ISOCURCD
     TRANKODE
     EFFDATE
     COMMDATE
     DKKVAL1
     USDVAL1
TRAILER(Occurance 1)
     ISOCURCD
     TRANKODE
      TRANCOUNT
According to How to use content conversion in JMS guide from SDN i have configured the content conversion parameters in the module of JMS sender adapter.
In the processing sequence given the module name as localejbs/AF_Modules/MessageTransformBean and module Key as Plain2XML.
And in module configuration
Parameter Name                      Parameter Value
Transform.Class                          com.sap.aii.messaging.adapter.Conversion
Transform.ContentType                     text/xml;charset=utf-8
xml.keyFieldName                          TRANKODE
xml.keyFieldType                          CaseSensitiveString
xml.recordsetName                          Root
xml.documentName                                   MT_ROOT
xml.documentNamespace                          http://XXX.XXX.XX/xi/XXXXX
xml.processFieldNames          fromConfiguration
xml.conversionType                                   StructPlain2XML
xml.recordsetStructure          HEADER,1,DETAIL,*,TRAILER,1
xml.HEADER.fieldNames           Field1,ISOCURCD,TRANKODE,IDENTIFIER,DATO,TIME
xml.HEADER.fieldSeparator                     ";"
xml.HEADER.keyFieldValue                     H
xml.fieldSeparator                                      ";"(if i don't use this then the file is not being picked and getting an error in the CC monitoring of RWB saying xml.field separator missing.)
Similarily for Detail and Trailer records as well.
But when I run the scenario, the file is being picked up but I am not getting any payload into the inbound message.
Can you please help me where I have configured wrongly. And one more thing will this configuration help for ; separated file .
Thanks & Regards,
Kumar
Edited by: Kumar on Dec 19, 2007 11:11 AM
Edited by: Kumar on Dec 19, 2007 11:15 AM

HI,
Have you gone through the below pdf i think it will help to find ur mistake.
How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Thnx
Chiarg

J2SE XML to Flat File Content Conversion

Hi
I've currently got a scenario which sends a flat file to the integration server, it gets mapped and sent to a receiver adapter on a deployed j2se engine.
I'm now trying to convert the xi-xml structured file to a flat file again on the j2se side (the same flat file format it originally had).
My original flat file looks like this -
477
477=AA1
My xml file looks like this -
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ResultMessage xmlns:ns0="urn:xxxx-com:a_test_j2se_filetofile">
<Item>
 <field1>477</field1>
</Item>
<Item>
 <field1>477</field1>
 <field2>AA1</field2>
</Item>
</ns0:ResultMessage>
I am using these content conversion parameters:
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
I get this error on the integration engine (sxmb_moni):
Error while sending by HTTP (error code: 500, error text: Internal Server Error:java.lang.NullPointerException) (See attachment HTMLError for details)
and the j2se adpater log says this:
17:16:32 (4120): Message "13b9d644-54c9-4ffb-0c40-db4c14458d77" of type "application/xml", kind "B" received
17:16:32 (4124): Parsing XML message
17:16:32 (4131): ERROR: Message processing failed with "java.lang.NullPointerException"
What am i missing?

So, now... I did a test configuration in XI and sent your test-payload...it worked.
The J2SE adapter configuration:
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
version=30
mode=XMB2FILEWITHCONVERSION
#Adress for XMB endpoint -
XI.httpPort=8111
XI.httpService=/file/receiver
#File Adapter specific parameters -
file.createDir=1
file.targetDir=c:/transfer/inbound
file.targetFilename=xmboutput.txt
#file.writeMode=append
#file.writeMode=overwrite
file.writeMode=addCounter
file.counterMode=immediately
#file.counterMode=afterFirst
file.counterSeparator=_
file.counterFormat=00000
file.counterStep=1
#File Content Conversion specific parameters -
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
And here the configuration of the receiver communication channel in the integration directory:
Adapter Type: XI
Receiver
Transport-Protocol: HTTP 1.0
Message-Protocol: XI 3.0
Adapter-Engine: Integration Server
Adressing-Type: URL Address
Target Host: <yourJ2SEip>
Service Number: 8111
Path Prefix:http://<yourJ2SEip>:8111/file/receiver
Authentication Data
Logon data for non-SAP systems
User
Password
That's it... sent your payload and got the wished result:
477
477=AA1
Regards,
Heinrich

Invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

Hi,
I have this error on a SOAP Receiver Channel: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
I've found several threads on SDN Forums about similar errors, but I did not find a solution for my problem yet.
I checked this blog: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009 Pt.6 applies to my situation, but the proposed solution doesn't solve the problem.
TRACE Messaging System
u2026
2011-06-06 10:59:41.822 Success Delivering to channel: CC_SOAP_RCV_XXX
2011-06-06 10:59:41.823 Success MP: entering1
2011-06-06 10:59:41.825 Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2011-06-06 10:59:41.828 Success SOAP: request message entering the adapter with user J2EE_GUEST
2011-06-06 10:59:42.012 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error
2011-06-06 10:59:42.014 Success SOAP: sending a delivery error ack ...
2011-06-06 10:59:42.014 Success SOAP: sent a delivery error ack
u2026
Message Details
Address   http://aaa.bbb.be:54000/MessagingSystem/receive/AFW/XI
Credential   PasswordCredential(PIISUSER):password=********
Transport Headers   accept-encoding=gzip sap-xi-messageid=4DEA11FE90003094E10000000AE908B4 content-length=7520 http=POST host= aaa.bbb.be:54000 user-agent=SAP NetWeaver Application Server (1.0;711) content-type=multipart/related;boundary=SAP_4DEA47CEAD3A5138E10000000AE908B4_END;type="text/xml";start="" soapaction="http://sap.com/xi/XI/Message/30"
Configuration Details SOAP Communication Channel
SOAP Receiver Channel
No modules configured
Do not use SOAP Envelope -> NOT checked
If I type the target URL in browser it opens (no login required) and I see the available web services.
Anyone any idea what's the reason for this error?
Thanks in advance
Kind Regards
Edmond Paulussen

Hi Edmond,
We faced similar problem & found alternative.
Try out, if it works for u as well.
1) Use HTTP Adapter instead of SOAP.
Transport Protocol : HTTP 1.0
Message Protocol : XI Payload in HTTP Body
Adapter Engine : Integration Server
Addressing type : URL Address.
Target Host:
Service Number :
Path Prefix:
Authentication type : we hv used Ananymus login, as our login details in payload header.
Content Type : application/soap+xml;charset=UTF-8( this is IMP).
Header Fields.
Name         value
Host           target host
XI Payload Manipulation
XML Code : UTF-8
Hope, this helps...
-santosh.

Error regarding File content conversion

Hello all,
I am getting the below mentioned error,
com.sap.aii.af.ra.ms.api.MessagingException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '')', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '')', probably configuration error in file adapter (XML parser error)'
My scenario is rfc -> file.In receiving adaptor it is giving me this error. I am not able to understand whats going wrong with it.I have checked the parameters specified for file content conversion i think they are fine.
Please can anyone help me to get out of this..
ZZSP.addHeaderLine      0
ZZSP.fieldFixedLengths     6,8,2,6,8,2,148
ZZSP.fixedLengthTooShortHandling     Cut
ZZSP.endSeparator     'nl'
ZZRP.addHeaderLine      0
ZZRP.fieldFixedLengths     3,1,2,4,2,6,1,2,2,7,9,2,7,8,5,5,6,12,8,4,6,6,3,2,67
ZZRP.fixedLengthTooShortHandling     Cut
ZZRP.endSeparator     'nl'
ZZTOT.addHeaderLine     0
ZZTOT.fieldFixedLengths     3,1,2,2,2,10,35,2,2,10,35,12,12,12,12,12,12,1,14
ZZTOT.fixedLengthTooShortHandling     Cut
ZZTOT.endSeparator     'nl'
ZZSUB.addHeaderLine      0
ZZSUB.fieldFixedLengths     3,1,2,10,3,2,2,3,3,6,3,25,25,6,1,12,12,12,12,12,25
ZZSUB.fixedLengthTooShortHandling     Cut
ZZSUB.endSeparator     'nl'
ZZLIN.addHeaderLine      0
ZZLIN.fieldFixedLengths     3,1,2,5,2,12,23,2,8,3,6,2,9,3,5,3,3,4,4,1,9,12,12,10,10,12,3,10,1
ZZLIN.fixedLengthTooShortHandling     Cut
Edited by: Siddhesh Pathak on Nov 3, 2008 2:19 PM
Edited by: Siddhesh Pathak on Nov 3, 2008 2:19 PM
Edited by: Siddhesh Pathak on Nov 3, 2008 2:20 PM

ur FCC is not configured correctly, I can not see fieldNames in the FCC.
wat is the strucutre of ur file?
r u having any key field in ur file?
refer sample example:
Content Conversion (Pattern/Random content in input file)
How to send a flat file with various field lengths and variable substructures to XI 3.0
chirag
Edited by: Chirag Gohil on Nov 3, 2008 7:34 PM

File Content Conversion Error

Hello,
I have Async. File receiver scenario in which the following is the XML message structure. This is received by the file adpater.
<ns1:MT_Info_File xmlns:ns1="urn:http://freemanco.com/xi/info_list">
 <TYPE>
 <FileItem>
 <FileName>DD11022007</FileName>
 </FileItem>
</TYPE>
<DATA>
 <LineItem> <LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
 </LineItem>
 <LineItem>
<LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
 </LineItem>
<DATA>
<LineItem</ns1:MT_Info_File>
I want to write only folowiing DATA structure to file. I do not want to wite contents of TYPE structure
<DATA>
 <LineItem> <LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
 </LineItem>
 <LineItem>
<LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
 </LineItem>
<DATA>
In the receiver file adpater I have follwoing File content conversion parameters.
RecordSetStructure: DATA,LineItem,*
*.addHeaderLine 0
*.fieldFixedLengths 301
*.fixedLengthTooShortHandling Error
*.endSeparator nl
LineItem.fieldSeparator nl
DATA.fieldSeparator nl
While testing I got following error. Looks like it is expecting some values for FileItem element in the XML.
Error Attempt to process file failed with java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
Error MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
Error Exception caught by adapter framework: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'
Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'FileItem' found in document', probably configuration error in file adapter (XML parser error)'.
How to resolve this issue? I appreciate your help.
Thank you,
Balaji

Balaji,
I would suggest to remove FileItem and LineItem in your receiver datatype. They are increasing the hierarchy of your content conversion. If you do that then you will have
<ns1:MT_Info_File xmlns:ns1="urn:http://freemanco.com/xi/info_list">
<TYPE>
<FileName>DD11022007</FileName>
</TYPE>
<DATA><LineEntry>234567891234567890123456789012345678901234567890</LineEntry>
<LineEntry>95473523647586969587265245437586979798376524253586</LineEntry>
<DATA>
</ns1:MT_Info_File>
Then in content converstion give this parameters:
Record structure : TYPE,FileName,DATA,LineEntry
TYPE.fieldfixedlengths : 0
FileName.fieldfixedlenghts:0
DATA.fieldfixedlenghts:0
LineEntry.fieldfixedlengths:301
LineEntry.endSeparator:'nl'
Then it should work. Also you can use FileName in your variable substituition. Also please see this weblog on how to use FileName in variable substitution:
/people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
If you dont want to remove FileItem and LineItem then add these also in your content conversion. Then the parameters would be:
Recordset: TYPE,FileItem,FileName,DATA,LineItem,LineEntry
TYPE.fieldfixedlengths : 0
FileItem.fieldfixedlengths:0
FileName.fieldfixedlenghts:0
DATA.fieldfixedlenghts:0
LineItem.fieldfixedlengths : 0
LineEntry.fieldfixedlengths:301
LineEntry.endSeparator:'nl'
Regards,
---Satish

** File Content Conversion Error in Receiver CC - How to solve this?

Hi friends,
My target structure looks like below.
EmployeeJobDetails --> Message Type
 JobCode --> Node
 EmployeeNumber xsd:string
 Domain xsd:string
 JobTrack --> Node
 Department xsd: string
 Position xsd: string
I use the FCC parameters in the receiver CC as below:
Recordset Structure: JobCode,JobTrack
JobCode.fieldSeparator = |
JobCode.endSeparator = 'nl'
JobTrack.fieldSeparator = |
JobTrack.endSepartor = 'nl'.
Because, we want the output like below
1099|Raja
Accts|JuniorAccountant
1100|Ram
HR|Recruiter
like this.
In this scenario Source is XML and target is txt file.
I am using XSLT Mapping. The FCC works fine, if my source input file contains some records. But, when we send empty source XML file as below
<?xml version="1.0" encoding="UTF-8"?>
<EMPLOYEE_DATA/>
Mapping works fine. Message is processed successfully in SXMB_MONI. The payload in response also comes with Message Type name like below
<EmployeeJobDetails namespace >
</EmployeeJobDetails>
While convert this, the system throws below error.
Error Message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)'
Friend, how to convert this when source XML is empty.
But, if we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the same empty XML file FCC is working fine and we get the target text file 0 KB. (Amazing !!)
But, in the first case, how to solve the issue?
Kind Regards,
Jegathees P.

Hi friends,
If we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the same empty XML file FCC is working fine and we get the target text file 0 KB. (Amazing !!)
But, if we give parameters like JobCode,JobTrack then send pass the same empty file, we face the problem 'File Content Conversion' Error.
Searching solution for this problem ...

XI content in AII

Similar Messages

Maybe you are looking for