File conversion in a file adapter

Hi
I am using a FTP file adapter to place the file in the ftp servers.
The structure of the file is
<?xml version="1.0" encoding="UTF-8" ?>
- <p2:MT_Cust xmlns:p2="http://RashidaBPM">
<Cust_no>KRTEST2</Cust_no>
<Cust_Name>XI CUSTOMER 2</Cust_Name>
<Cust_Address>GB</Cust_Address>
</p2:MT_Cust>
I want the resulta to come in as cust_no , cust_name, cust_address
Can someone please help me to get the centent conversion parameters correct to get the desired result
Thanks
Nikhil

Hi Nikhil,
To convert a XML file into a flat file you need to have a Stucture of the XML file like this one mentioned below:
<root>
<substructure>
<data>
</data>
</substructure>
<root>
By XML I mean the input data, that will be routed from XI server to FTP servers.
now the parameters to be given in Content Conversion Tab and which are of utmost importance are:
substructure.fieldSeparator
root.fieldSeparator
substructure.endSeparator
you can also use the methods such as fieldFixedLengths etc.
Include these methods and test your scenario again.
I hope it helps,
Thanks & Regards,
Varun Joshi

Similar Messages

File Content Conversion in Sender File Adapter

Hi,
I am implementing a scenario, where I need to do Content conversion in My file Adapter.My input file is as follows
BGN00S-A200711281003ET4
REF38381012
DTP007D820071128
N1P5P5MicrosoftFI58-0612397
INSY18030XNAN
REFZZZZ666666666
DTP336D819970331
NM1ILIL1AdamsMarkE34666666666
PERIPIPHP770555-5555
N31470 Georgia Club Drive
N4StathamGA30666
DMGD819571022MM7
HD030HLTAE1D
My data type is as below.
<header>
     <BGN>
          <A></A>
          <B></B>
          <C></C>
          <D></D>
     </BGN>
     <REF>
          <A1></A1>
          <B1></B1>
          <C1></C1>
          <D1></D1>
     </REF>
     <DTP>
          <A2></A2>
          <B2></B2>
          <C2></C2>
          <D2></D2>
     </DTP>
</header>
<Content>
     <N1>
          <A></A>
          <B></B>
          <C></C>
          <D></D>
     </N1>
     <REFAR>
          <A1></A1>
          <B1></B1>
          <C1></C1>
          <D1></D1>
     </REFAR>
     <DMP>
          <A2></A2>
          <B2></B2>
          <C2></C2>
          <D2></D2>
     </DMP>
</Content>
My issue is, How do I set my parameter in Sender Comm channel for content conversion especially at record structure.
I have provided the value as Header,1,Content,*
But its not working.
If I do provide like
BGN_REC,,REF_REC,,DTP_REC,,N1_REC,,INS_REC,,NM1_REC,,PER_REC,,N3_REC,,N4_REC,,DMG_REC,,HD_REC,* then ,I am not getting above XML format. Please suggest or How can I modify my Data type which competes to configure in Channel
Thanks
Manmadha

Hi All,
I am sorry for the Jumbled Content. I dont know what happened.
I should get the XML output as below.
header>
     <BGN>
          <A></A>
          <B></B>
          <C></C>
          <D></D>
     </BGN>
     <REF>
          <A1></A1>
          <B1></B1>
          <C1></C1>
          <D1></D1>
     </REF>
     <DTP>
          <A2></A2>
          <B2></B2>
          <C2></C2>
          <D2></D2>
     </DTP>
</header>
<Content>
     <N1>
          <A></A>
          <B></B>
          <C></C>
          <D></D>
     </N1>
     <REFAR>
          <A1></A1>
          <B1></B1>
          <C1></C1>
          <D1></D1>
     </REFAR>
     <DMP>
          <A2></A2>
          <B2></B2>
          <C2></C2>
          <D2></D2>
     </DMP>
</Content>

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

Receiver File adapter content conversion using StrictXml2PlainBean

Hi All,
For receiver file adapter i am using the module StrictXml2PlainBean, and also i mentioned the module configuration like this
parameter name                              parameter value
recordTypes                                  Header,TransactionHeader,TransactionDetail,TransactionTrailer,FileTrailer
FileTrailer.endSeparator                |\n
FileTrailer.fieldSeparator               |
Header.endSeparator                   |\n
Header.fieldSeparator                  |
TransactionDetail.endSeparator   |\n
TransactionDetail.fieldSeparator |
TransactionHeader.endSeparator |\n
TransactionHeader.fieldSeparator |
TransactionTrailer.endSeparator |\n
TransactionTrailer.fieldSeparator |
But when i send the idoc, The receiver CC is throwing an error
Message processing failed. Cause: com.sap.aii.af.modules.conversion.xml2plain.ConversionException: Invalid structure name encountered during conversion: Transaction at XML element MT_DeliveryOrder,Transaction
My actual structure is
MT_DelvOrder
   Header 0...1
   Transaction 0....Unbounded
      TransactionHeader 1..1
       TransactionDetail     0...unbounded
        TransactionTrailer 1...1
   FileTrailer 0...1
The module is checking for the Transaction node,but i require the rest 3.
Same configuration i have done successfully with FCC without using the module....
So can any one suggest me where i am missing... why the module is pointint towards, the Transaction cant i ignore this node . and continue with the rest???
Regards,
Sridhar
Edited by: sridhar reddy kondam on Aug 10, 2009 12:35 AM

Hi Rajesh,
The same FCC configuration was working fine with FCC and when i am using this module configuration i am getting the prob...
In the file i need the Header,TransactionHeader,TransactionDetail,TransactionTail,Filetrailer
my sample output file is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_DeliveryOrder>
<Header>
</Header>0...1
<Transaction>0...Unbounded
    <TransactionHeader> 1..1
     </TransactionHeader>
     <TransactionDetail> 0...Unbounded
     </TransactionDetail>
      <TransactionTrailer>1...1
       </TransactionTrailer>
</Transaction>
<FileTrailer> 0...1
</FileTrailer>
Any suggestions will be great help...
I think i need to go with other options without using this module....
Regards,
Sridhar
Edited by: sridhar reddy kondam on Aug 10, 2009 6:03 AM

Error in Receiver File adapter using File content Conversion

Hi,
I am getting the following error in the receiver file adapter.
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'statement.fieldFixedLengths' or 'statement.fieldSeparator' is missing
I am using the below parameters for FCC:
Recordset Structure - statement
statement.endSeparator - 'nl'
statement.fieldSeparator - '0X09'
statement.fieldNames -xblnr,wrbtr,newbs,kostl,newko,prctr,xref1,rke_wwfud,rke_wwst3,blart,bukrs,bldate,budat,gjahr,monat,ctype,waers,bktxt,posnr,wbs_element,mwxkz,businessplace,businessplace,c_waers,c_wrbtr,g_ctype,g_waers,g_wrbtr,h_ctype,h_waers,h_wrbtr,trade_id,lob,sgtxt,zuonr,reason_rev,ldgrp,tcode,lifnr
ignoreRecordsetName - true
Please let me know where i am going wrong.
Thanks,
Aparna

Hi Aparna,
I feel the problem in your content conversion parameters is with
statement.fieldNames and ignoreRecordsetName
When you are confirguring receiver file adapter for file content conversion the above one is not required. Please refer below link for details on configuring content conversion in file adapter
[http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm]
Hope this helps !!
Regards,
Amit

Receiver File Adapter Content Conversion Problem.

Hi All,
I am getting in receiver file adapter due to content conversion setting. Problem is that all the fields coming in file adapter are optional. In content conversion , i have specified fieldfixedlengths. So whenever any optional field is not present , it fails . How should we handle it? is there any option to declare fields as optional, I know that is the there for sender adapter. But no. of fields is also very large, so putting each and every field as optional is very time consuming.
What should i do?
Ranjeet Singh.

Hi Daniele,
Instead of using the standard funciton , i created a UDF for handling this situation.
My logic is UDF is like
   //write your code here
int Size = Integer.parseInt(Truncate_Size);
String Return_Value = "";
     if (!("".equals(Input)) )
          if (Input.length() > Size )
               Return_Value = Input.substring(0,Size);
          else
               Return_Value = Input.substring(0, Input.length());
     else
          for(int i = 0; i< Size ; i++)
          Return_Value = Return_Value + " " ;
return Return_Value;
SO in this case also , it should be able to handle empy source element. But it is not working.

Receiver File Adapter - Content Conversion

Hi,
I don't quite get this:
I have a structure
<?xml version="1.0" encoding="UTF-8"?>
<AnElement1>
   <AnElement2>
      Bla bla bla
   </AnElement2>
</AnElement1>
I want to convert this to a flat file with a line containing
Bla bla bla
In te receiver file adapter I define the following:
In the 'Content Conversion Parameters'
Recordset Structure : AnElement2
Name                         Value
AnElement2.addHeaderLine         0
AnElement2.fieldSeparator        'nl'
AnElement2.endSeparator          'nl'
This results in an Empty file each time indicating some error somewhere.
What am I missing?
Thanks
Andre

Hi Andre,
Just check the link <a href="http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm">File content conversion</a>
Also check out this web log <a href="/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2 to TXT</a>
Is there any error log shown in File adapter ?
Regards,
Keith
Message was edited by: keith thompson

File Content Conversion Parameters in FIle Adapter

Hi
I am doing a scenario - XML file to Text file using File content conversion parameters in Receiver File Adapter Channel.
I given FCC Parameters like:
DATA.addHeaderLine - '0'
DATA.fieldSeparator - ,
DATA.endSeparator - 'nl'
But im getting error in Receiver File Adapter as - fieldSeparator not specified.
i would be greatful if any one help me.
Regards
Rajesh

Hi Rajesh,
There are lot of blogs which explain File Content Conversion in different scenarios:-
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
I hope this helps.
Regards.
Praveen

File Conversion in Rec File Adapter with subnodes

Hi
My XML Structure is like this -->
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_Test xmlns:ns0="urn:TESTconversion">
<MstName>Hello</MstName>
- <Header>
<TableName>1tst</TableName>
<PayDate>0102</PayDate>
<TotalAmt>24.00</TotalAmt>
<Total>000002</Total>
<PaySource>CHK</PaySource>
- <Subheader>
<TableName>1tst</TableName>
<SelectCatgry>test</SelectCatgry>
<CustID>200</CustID>
<PayAmount>11.00</PayAmount>
</Subheader>
- <Subheader>
<TableName>1tst</TableName>
<SelectCatgry>test</SelectCatgry>
<CustID>400</CustID>
<PayAmount>13.00</PayAmount>
</Subheader>
</Header>
- <Header>
<TableName>1tst</TableName>
<PayDate>0103</PayDate>
<TotalAmt>10.00</TotalAmt>
<Total>000001</Total>
<PaySource>ONE</PaySource>
- <Subheader>
<TableName>1tst</TableName>
<SelectCatgry>test</SelectCatgry>
<CustID>100</CustID>
<PayAmount>10.00</PayAmount>
</Subheader>
</Header>
</ns0:MT_Test>
which means
MT_Test is root 1..1
Header is the sub-node of MT_test as 1...*
Subheader is sub-node of Header which is also 1...*
rest of the fields are elements as 1..1
Now I need to convert this into Flat file using Receiver File Adapter, I gave this in my content conversion logic
recordset Structure -
MstHeader,BFKKZK,BFKKZP
MstName.addHeaderLine     0
MstName.fieldFixedLengths     8
MstName.endSeparator     'nl'
Header.addHeaderLine     0
Header.fieldFixedLengths     30,10,15,6,6
Header.endSeparator     'nl'
Subheader.addHeaderLine     0
Subheader.fieldFixedLengths     34,10,35,16
Subheader.endSeparator     'nl'
But with this I am getting exception as -->
Could not process due to error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:MT_Test' found in document', probably configuration error in file adapter (XML parser error)'
I know that http://help.sap.com/saphelp_nwpi711/helpdata/en/44/686e687f2a6d12e10000000a1553f6/content.htm says following -->
The expected XML structure contains the structure as nodes filled with any number of elements without additional subnodes.
But does that mean Structure with sub-nodes cannot be converted in flat format.
Pls. suggest the solution for this.
- lalit -

Shab
I resolved the issue & able to convert the hierarchical XML file into flat file with the desired format I wanted.
Rather then FCC, I use MessageTransformBean module and I have to insert more dummy contexts & dummy fields in the target structure in order to achieve the flat file format.
I am getting file ( not actual file below just template is shown below) like this now
Header1 ....details....
SubHeader1.1
SubHeader1.2
SubHeader1.x
Header2 ....details....
SubHeader2.1
SubHeader2.2
SubHeader2.x
Headerx ....details....
SubHeaderx.1
SubHeaderx.2
SubHeaderx.x
Once the total development is over on my side I will create the blog for this. So this following statement is only correct when you use protocol as FCC but not with module.
"The expected XML structure contains the structure as nodes filled with any number of elements without additional subnodes."
Thanks
Lalit

Sender file adapter conversion Error!!

Hello every one....
I am stuck with a problem...in my scenario,, there are possiblities that file may contain more than required paramters... in such case,,, paramters defined in conversion should go ahead and others should be ignored...
for this very purpose i added the paramter:
row.fieldSeparator                 ,
row.fieldNames                     orderno,authcode,status
row.endSeparator                  'nl'
row.additionalLastFields      ignore
the scenario works fine if the file contains thrree comma separated values but it raises an error if no of paramters increase as :
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting
document line no. 1 according to structure 'row':java.lang.Exception: ERROR in configuration: more
elements in file csv structure than field names specified!
we are using PI 7.... does it require some more configuration in additoin to paramter row.additionalLastFields
any help in this regard would be highly appreciated...
thanx

this parameter is already set, and this is the exact behavior i want from adapter engine... but the problem
here is different... the exception is raised at communication channel's conversion routine level,,, the retry
interval is not the one defined in visual admin but infact the interval (polling) time defined in communication
channel.... the system does'nt stop after 3 attempts,, but infact keep on trying to read it....
one peice of information i have found is in sap note:821267 , which states:
*Q35:*
Q: I have configured a File Sender channel with File Content
Conversion or a custom-developed module, which may throw an
exception. When the File Adapter encounters an invalid file, which
triggers a conversion error or an exception in a module, the
adapter will enter a retry interval and upon each following
processing attempt try to process the faulty file. This basically
prevents the File Adapter from picking up files that are located
after the fauilty file according to the configured sort order. How
can I change this behavior?
o A: This is by design. When the File Adapter encounters an invalid
file, manually remove this file from the configured source
directory. You can configure an alerting rule to get notified each
time this occurs.
We are currently evaluating possible solutions that could be used
to skip this manual interaction.
now can there be a way around to make communication channel read the file only 3 times (value defined in adapter engine profile in visual admin)
I have thaught of writing of module.... but the error is raised even before calling module !!
any further clue ???

Sender File Adapter - Content Conversion

HI Friends,
I got a scenario where I need to convert the File to XML document through Sender file adapter..
My file looks like below.
BATCH1234........
12DASER123142JMM
237DSAFDLKC839890
45SDFLASJ90011
BATCH3455...
132FGAR
SD21352525
BATCH998898...
123145DSRTW
12FSTS
So there is a Header and Body for each record set..
My XML Structure is as follows.
<TimeStructure>
<TimeRecord>
     <ControlRec>
         <Field1>BATCH </Field1>
         <Field2> ...</Field2>
     </ControlRec>
     <DataRec>
         <F1> ...... </F1>
         <F2> ...... </F2>
     </DataRec>
</TimeRecord>
<TimeRecord>
     <ControlRec>
         <Field1> BATCH </Field1>
         <Field2> ADFAS </Field2>
     </ControlRec>
     <DataRec>
         <F1> ...... </F1>
         <F2> ...... </F2>
     </DataRec>
   </TimeRecord>
</TimeStructure>
The blog <a href="/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem:///people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
is somewhat relevant to my requirement.
But the problem is I have the keyfield "BATCH" for my header file but don't have any <b>key field in the data record</b> of the input file.
Please help me out how to mention the configuration parameters.
Regards,
Kumar

Hi,
If you don't have constant key value for your detail records, then you can not directly get the required xml.
So in this case, you can read all the records in a common Row model, i.e each record will be considered as a one row with all the values, and then split this row with Substring or java functions in the mapping.
Even you can do this in the Adapter module .
If you have key value for each record to identify then you can try with content conversion.
Regards,
Moorthy

File Adapter: Initialization error: Conversion initialization failed

Hi all,
I'm trying to establish a file adapter (FTP, File Content Conversion).
In the adapter monitor I' ve got the following error:
Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
Configured at 14:49:34 2005-08-29
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
My content conversion parameters are:
BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
20,50,50,1,10,50,10,50,5,20,20,15,15
BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
HouseNo,PhoneNumber,Fax,BankId,BankAccount
BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
trim
BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
ignore
What could be the error or where I have to look for it?
Thanks,
Fabian

Yes,
Recordset name: BP_BusinessPartnerMasterData_IncomingData
Recordset structure: BP_BusinessPartnerMasterData_IncomingData
The corresponding Message Type:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
     <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
     <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               f323a4b018a911da9fd9000bcd69ce64
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Number">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8500fe111da89f2d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Id from Sender for BP
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name2">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8510fe111dacfd7d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Last name or Company name
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name1">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8520fe111da94bad1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         First name or Company name 2
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Gender">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8530fe111da99add1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         m or f or blank
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="1" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Birthdate">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8540fe111dab156d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="City">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8550fe111daa58cd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Postcode">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8560fe111dac0c2d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Street">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8570fe111dabbd3d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="HouseNo">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8580fe111dab63fd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="5" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PhoneNumber">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8590fe111dac782d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Fax">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85a0fe111daa9ebd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankId">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85b0fe111dace1ed1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankAccount">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85c0fe111da8801d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

Sender File Adapter with file conversion

Hi guys,
Im using a Sender File adapter with file conversion. The message to be processed has a structure with fixed lengths and in your content are some values that needs to be ignored.
An example:
value1 <b>value2</b> value3
I want to ignore <b>value 2</b> but I cant find a parameter for that! Do I need to define dummy fields on my data type and ignore those fields during mapping? Or there is a specific parameter for that?
Thanks in advance,
Ricardo.

hi,
there always is another way:)
you can import the whole line to one field
and cut it inside the adapter module
(then you can define start and stop of the substring that you need to use)
but of course it's not standard even though it's quite easy to achieve in java
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

File adapter content conversion

Hi all,
We are having File to File Scenario
We are facing problem in Content conversion in File
Adapter(Sender)
The source file is in text format and fields are
seperated by '|' character
The source file structure is :
Header|No. of Records
Data Record1
Data Record2
Data Recordn
Trailer|No. of Records
     where Data Recordn is of type Field1|Field2|Field3|Field4
     and the number of data records is variable
     e.g.
     Header|5
     2|144012|20050801|20050801
     212|012|20050801|20050801
     244012|2|20050801|20050801
     2144|144012|20050801|20050801
     212|012|20050801|20050801
     Trailer|5
Now , we need to ignore the contents of Header and Trailer Records
     For Header , we are setting the property Document Offset to 1
     Hence the Header record is ignored
     However , we are facing problems in ignoring the Trailer record
     We want to know :
     1. Is there a direct way ( or some propety ) wherein we can ignore the last record of the file ,
        which in this case is Trailer record
     2. We also tried the following :
          a. We set the Recordset Structure to : row,*,trailer,1
          b. However in this case , the keyField is required for row ;
             but since the number of data records is variable ,
             the keyFieldValue cannot be specified
       How should we go about in this case
Please guide us on this
Regards
Shikha

Hi all
Thanks for replies
Actually , we are able to ignore header and that is not an issue
Now if we need to discard the trailer record , we believe that RecordSet Structure should be <b>row,,trailer,1</b> or <b>header,1,row,,trailer,1</b>
However , since structure is <b>row,*</b> ; we need to specify the <b>keyField</b> column for row ( data records )
Since <u>number of data records</u> is variable , we are not able to set the <b>keyFieldValue</b> for <u>row ( data record )</u>
Can you'all please guide us on this as we are stuck on this .
Regards
Shikha
Message was edited by: Shikha Jain

REG: File content conversion in Receiver file adapter

HI Gurus,
I have the scenario like proxy to file with content conversion
my message type for the source like this
MT_SOURCE
-----||
       |---ROW
------------||
                |---LINE
target strucuture also same
MT_TARGET
-----||
       |---ROW
------------||
                |---LINE
i am using the following FCC parameters in receiver file adapter
LINE.fieldSeparator = '                       '
LINE.fixedLineWidth = 90
LINE.lineSeparator = 'nl'
LINE.fieldFixedLengths = 200
LINE.endSeparator        = 'nl'
the output file show the data differently in note pad when compare to word
word output
dgepvs                       023456987
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
kgdd0016155710                SS Smw Ne 01
notepad out put
dgepvs           023456987   kgdd0016155710                SS Smw Ne 01       kgdd0016155710                SS Smw Ne 01          kgdd0016155710                SS Smw Ne 01            kgdd0016155710                SS Smw Ne 01    kgdd0016155710                SS Smw Ne 01
word output is the correct output wat i am expect but same out put i want in note pad can any help me out for this how can i resolve this
Thanks in advance

There is nothing wrong in your content conversion parameters. This is pure editors interpretation for the next line character.
I would do in java program to fix this issue using '\r\n'   You might want to try and see how that helps for notepad editor.

File conversion in a file adapter

Similar Messages

Maybe you are looking for