Reciever Comm. Channel Content conversion parameter for deep level

I am doing a scenario from SAP to Legacy sytem ( Proxy to File Scenario).Target File to be generated is of for fixed length.
__My source strucure is as follows:__
DT_Source
--->Root_IS .......................................0.to..1
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
Here DT_source is Data type name,
Root_IS is structure under this we have one field DC,
Root_VT is second field of Root_IS but act a a Stucture for fields POY and PON,
Root_VR is a field of Root_VT but act as a structure for Fields POL and SF.
__My targert strucure is as follows:__
DT_Target
>Root_IS.......................................0.to..1
Key..............................................0..to..1.............................xsd:string
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
>Root_ZS............................0..to..1
Key..............................................0..to..1.............................xsd:string
Count...........................................0..to..1.............................xsd:string
Here DT_Target is data type for file reciever.In which i need to configure reciever communication channel with file content conversion parameters.File needs to be generated is of fixed length.Root_IS,Root_VT,Root_ZS are sructure on same level and Root_VR sructure is under Root_VT.
I tried to Configure File Content Conversion Parameters on reciever Comm Channel but getting comm channel error as follows:
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: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', 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 'VR')', probably configuration error in file adapter (XML parser error)'
Could not process due to 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 'VR')', probably configuration error in file adapter (XML parser error)'
File content parameters i used as follows:
Root_IS.fieldNames                                      : Key,DC
Root_IS.fieldFixedLengths                           :(as per length mentioned)
Root_IS.endSeparator                                 :'nl'
Root_VT.fieldNames                                   :Key,POY,PON
Root_VT.fieldFixedLengths                        :(as per length mentioned)
Root_VT.endSeparator                              :'nl'
Root_VR.fieldNames                                  :Key,POL,SF
Root_VR.fieldFixedLengths                       :(as per length mentioned)
Root_VR.endSeparator                             :'nl'
Root_ZS.fieldNames                                 :Key,Count
Root_ZS.fieldFixedLengths                      :(as per length mentioned)
Root_ZS.endSeparator                            :'nl'

Please consider this one as new: i tried to explain it more as on privew everything gets shaked
I am doing a scenario from SAP to Legacy sytem ( Proxy to File Scenario).Target File to be generated is of for fixed length.
__My source strucure is as follows:__
DT_Source
--->Root_IS .......................................0.to..1
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
Here DT_source is Data type name,
Root_IS is structure under this we have one field DC as a child,
Root_VT(structure) is second field of Root_IS but act a a Parent Stucture for fields POY and PON,
Root_VR(structure) is a field of Root_VT but act as a Parent structure for Fields POL and SF.Means we have three structres Root_IS and under this we have Root_VT and under this we have Root_VR
__My targert strucure is as follows:__
DT_Target
>Root_IS.......................................0.to..1
Key..............................................0..to..1.............................xsd:string
DC..............................................0..to..1.............................xsd:string
>Root_VT....................................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POY....................................0..to..1.............................xsd:string
PON....................................0..to..1.............................xsd:string
>Root_VR............................0..to..unbounded
Key..............................................0..to..1.............................xsd:string
POL.............................0..to..1.............................xsd:string
SF----
0..to..1.............................xsd:string
>Root_ZS............................0..to..1
Key..............................................0..to..1.............................xsd:string
Count...........................................0..to..1.............................xsd:string
Here DT_Target is data type for file reciever.In which i need to configure reciever communication channel with file content conversion parameters.File needs to be generated is of fixed length.Root_IS,Root_VT,Root_ZS are sructure on same level as a first level subelements of DT_Target and Root_VR sructure is under Root_VT.
Root_IS have fileds: key,DC: Root_VT have Fields :Key,POY,PON:Root_VR have fields:Key,POL,SF and Root_ZS have Fields:Key and Counts.
I tried to Configure File Content Conversion Parameters on reciever Comm Channel but getting comm channel error as follows:----
>
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: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value 'VR')', 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 'VR')', probably configuration error in file adapter (XML parser error)'
Could not process due to 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 'VR')', probably configuration error in file adapter (XML parser error)'
File content parameters i used as follows:
Root_IS.fieldNames                                      : Key,DC
Root_IS.fieldFixedLengths                           :(as per length mentioned)
Root_IS.endSeparator                                 :'nl'
Root_VT.fieldNames                                   :Key,POY,PON
Root_VT.fieldFixedLengths                        :(as per length mentioned)
Root_VT.endSeparator                              :'nl'
Root_VR.fieldNames                                  :Key,POL,SF
Root_VR.fieldFixedLengths                       :(as per length mentioned)
Root_VR.endSeparator                             :'nl'
Root_ZS.fieldNames                                 :Key,Count
Root_ZS.fieldFixedLengths                      :(as per length mentioned)
Root_ZS.endSeparator                            :'nl'

Similar Messages

  • Comm Channel content conversion

    Hi everyone,
    I have an existing interface IDOC to File scenario, in which I want to drop one field from the final output file.
    But I can't remove that field from the interface as it is is required for business logic till the very end.
    Can I acheive this in Ciontent conversion in Communication channel ?
    Any ideas will be appreciated.
    Cheers,

    Hi,
    While configuring FCC parameteres, for 'fieldFixedLengths' keep the width of that corresponding field as '0'.
    It will work.
    Regards,
    Supriya.

  • How to escape newline character(nl) in file content conversion parameter?

    Hi Experts,
    How to escape newline character(nl) in file content conversion parameter?
    For example:
    field1field2field3
    field4field5field6
    Means Item is splitted in two lines.
    I want to SKIP new line character
    and to collect all SIX fields.
    What will be the file content conversion parameter?
    Thanks in Advance..........

    Hi,
    as far as i know there is nothing in the standard. But the question is why dont you combine at mapping the fields into only structure?
    Regards,
    Udo

  • What are the right content conversion parameter in this receiver ?

    Hi experts,
    Can someone help me with setting right Content conversion parameter in the Receiver of File adpater(FCC).The output file must be fixed length text file.
    Here is the receiver structure:
    <Recordset>
        <Header>
           <f1>01</f1>
           <f2> </f2>
           <f3> </f3>
        </Header>
         <Body>
            <SubBody1>
                  <field1 />
                  <field2 />
                  <field3 />
                  <field4 />
                  <field5 />
            </SubBody1>
             <SubBody2>
                  <field6 />
                  <field7 />
                  <field8 />
                  <field9 />
                  <field10/>
            </SubBody2>
         </Body>
        <Trailer>
            <f1>03</f1>
            <f2> </f2>
            <f3> </f3>
       </Trailer>
    </Recordset>
    Also Body can occure multiple times in the file but still will have this structure...Header and Trailer can occure only once in file.
    What are the right content conversion perameters in this case?
    Appreciate your help asap!T
    Thanks
    Jon

    <Recordset>
        <Header>
           <f1>01</f1>
           <f2> </f2>
           <f3> </f3>
        </Header>
         <Body>
             <SubBody>
                  <field1 />
                  <field2 />
              </SubBody>
              <SubBody>
                  <field1 />
                  <field2 />
              </SubBody>
              <SubBody>
                  <field1 />
                  <field2 />
              </SubBody>
            </Body>
        <Trailer>
            <f1>03</f1>
            <f2> </f2>
            <f3> </f3>
       </Trailer>
    </Recordset>
    if this is the input structure then FCC goes like this ....
    Recordset:Header,Body,SubBody,Trailer
    Header.fieldFixedLengths – 10,20,30.. (based on you are structure fixed lengths)
    Header.endSeparator - 'nl'
    SubBody.fieldFixedLengths – 10,20,20  (based on you are structure fixed lengths)
    Body.endSeparator - 'nl'
    Trailer.fieldFixedLengths – 10,20,30….(based on you are structure fixed lengths)
    Trailer.endSeparator - 'nl'
    We might have to try out SubBody.endSeparator - 'nl' if Body.endSeparator - 'nl' does not insert a new line after each body record.
    Cheer's

  • Content Conversion issue for header record

    Hi,
    We have a very urgent question on an issue here with one of our XI objects. 
    This is an inbound interface from an external system into R/3 & BW.  The inbound file has a header record (with about 8 fields) and detail records (about 900 fields per detail record). Data going into R/3 & BW don't have header records and everything goes in as detail records. One field from the header of this source file should be passed to the target structure at the detail level. Also, we are NOT using BPM.
    Can someone help us how we could define the file content conversion parameters for File adapter.
    Thanks in advance ......
    Prashant

    I'm so sorry, I wasn't subscribed to this thread and I didn't realize there were responses.
    If you have a message type made up of a Header with 1 occurence and Detail with 1 to unbounded occurunces, you'd want to do the following in content conversion:
    Document Name - your message type
    Document Namespac - your message type namespace
    Recordset Structure - Header,1,Detail,*
    Recordset Structure - Ascending
    Then you'll need to set some of the parameters, depending on the layout of your incoming file. 
    As for the problem of having hundreds of fields, I'm less sure about that.
    Would it be possible to break your detail data type down into smaller data types.  Each with fewer fields.  You'd still have to maintain every field in content conversion, but at least they'd be in seperate parameters, instead of all 900 in one tiny box.
    Here's a very rough example of what I mean:
    If you have 900 fields, instead of making 1 data type of detail, you could make 9 data types, Detail1, Detail2, Detail3, Detail4, Detail5, Detail6, Detail7,Detail8, Detail 9, each with 100 fields in them (or more with even less fields).
    Setting things up the file content conversion would be more complex in this scenario, so it might be a toss up if it's worth it to break it up this way or not if it meant configuring quite a few more parameters.
    For example,
    You'd have to declare your recordset structure like Header,1,Detail1,,Detail2,,Detail3,* etc, and you'd have to make sure to set the .endSeparator to '0' for all of the first 8 details, so it would recognize that they were all on one line.
    I hope this helps a little bit.

  • Reciever comm channel configuration  for ftp

    Hi
    all
    I have configured the comm ch in reciever nfs
    content conversion parameters
    Name.fieldNames                 FIRSTNAME,LASTNAME,SALARY
    Name.fieldSeparator         ,
    Name.processConfiguraion    FromConfiguration
    Name.endSeparator        'nl'
    sender comm ch nfs
    content conversion parameters
    Recordset name              Record
    Recordstructure             Name,*
    Name.fieldNames                 FIRSTNAME,LASTNAME,SALARY
    Name.fieldSeparator         ,
    Name.processConfiguration   FromConfiguration
    Name.endSeparator         'nl'
    Receiver Adapter v2405 for Party '', Service 'BS_VIJ_RECV':
    Configured at 2006-08-18 21:45:51 EDT
    History:
    - 2006-08-18 21:45:51 EDT: Error: Conversion initialization failed: Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Parameter 'NAME.fieldFixedLengths' or 'NAME.fieldSeparator' is missing
    please suggest me if i am doing anything wrong
    thanks all in advance

    Hi,
    I think there is some problem with record strcuture. Because error shows something with NAME as a segment. But not able to see that in your sturtcure. check the structure
    Have a look into these blogs-
    /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
    Regards,
    Moorthy

  • Need Content Conversion parameter help

    Hi,
        I need help regarding the Content conversion parameters.I have sent a IDOC and i could receive it as an XML file in my receiver end.
    My XML files looks like this
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_IDoc2FILE xmlns:ns0="http://ffvendor">
    <NAME>....</NAME>
    <EMAIL>....</EMAIL>
    <MOBILE>.....</MOBILE>
    </ns0:MT_IDoc2FILE>
    Please let me know how to convert this to a comma separated flat file
    Regards,
    Karthik

    HI
    FCC Paremeters:
    nameA.fieldSeparator =~
    nameA.endSeparator ='nl'
    nameA.fieldNames =text1,text2,text3,text4
    nameA.processFieldNames fromConfiguration
    nameA.lastFieldsOptional Yes
    nameA.missingLastFields Add
    nameA.additionalLastFields ignore
    ignoreRecordsetName: true
    if endSeparator = newline, then
    nameA.endSeparator = 'nl'
    nameA.fieldSeparator =~
    nameA.fieldNames = field1,field2,field3,field4
    if endSeparator = #, then
    nameA.endSeparator = #
    nameA.fieldSeparator =~
    nameA.fieldNames = field1,field2,field3,field4
    1.     NameA.missingLastfields
    If the inbound structure has less fields than specified in the configuration then the XML outbound structure is created as follows:
    ○ ignore
    Outbound structure only contains the fields in the inbound structure
    ○ add
    Outbound structure contains all fields from the configuration; the fields missing in the inbound structure are empty.
    ○ error
    Conversion is terminated due to the incomplete inbound structure. An error message is displayed.
    2. NameA.additionalLastFields
    If the inbound structure has more fields than specified in the configuration then the XML outbound structure is created as follows:
    ○ ignore
    Outbound structure only contains the fields in the inbound structure
    ○ error
    Conversion is terminated due to the incomplete inbound structure. An error message is displayed.
    The default value is ignore. If you have defined the NameA.fieldFixedLengths parameter, the default value is error.
    If you have defined the NameA.fieldFixedLengths parameter and do not set either of the parameters described above, apart from the default values, the conversion routine works the same as described under Handling Structure Deviations.
    Only once you set one of the two parameters will the other parameter be evaluated with its default value.
    To ensure a well-defined runtime behavior for variable inbound structures, we recommend that you always set both parameters.
    File Content prameters for the Receiver Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
    File Content prameters for the Sender Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    Refer
    File Receiver with Content Conversion
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    Configuring the Receiver File/FTP Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/95/bb623c6369f454e10000000a114084/frameset.htm
    File content conversion sites
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Please see the below links for file content conversion..
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter - FCC
    File Content Conversion for Unequal Number of Columns
    /people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns - FCC
    Content Conversion (Pattern/Random content in input file)
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file - FCC
    /people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario - FCC - MDM
    XI in the role of a FTP
    /people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp - FCC
    File to R/3 via ABAP Proxy
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - FCC
    /people/mickael.huchet/blog/2006/09/18/xipi-how-to-exclude-files-in-a-sender-file-adapter - EOIO - File
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/c9f0b4925af54cb17c454788d8e466/frameset.htm - cc
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/95/bb623c6369f454e10000000a114084/content.htm - fcc cOUNTER
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/da1e7c16-0c01-0010-278a-eaed5eae5a5f - conversion agent
    cheers

  • Receiver File Adapter: Problem with NewLine Content Conversion Parameter

    Hello Everybody
    On our SAP-XI (SAP NetWeaver 2004s, sp14) I have the scenario to send a price catalogue (IDoc PRICECATALOGUE.PRICECATALOGUE02) from SAP R/3 as csv PRICAT file to a file share.
    In the receiver communication channel I have defined
    Message Protocol = File Content Conversion
    using the following RecordSet:
    RecordSet = HeaderRow,MainBody
    One header row is followed by one or more main body rows. The csv PRICAT message format demands that there is an empty row (i.e. one carriage return) between header and main body and another carriage return after the last main body row:
    <Header Row>
    carriage return
    <MainBody 1>
    <MainBody 2>
    carriage return
    As content conversion parameters I tried to use NewLine ('nl') to create the carriage returns in the file:
    HeaderRow.fieldSeparator = ,
    HeaderRow.endSeparator = 'nl'     " new line
    MainBody.fieldSeparator = ,
    MainBody.endSeparator = 'nl'
    Using the settings I have been able to created the carriage return at the end of the file but not the one between header and main body.
    As workaround I have used the following approach:
    " Add the following XSLT mapping between header and body:
                <SeparatorLine>
                    <value>
                        <xsl:value-of select=" '' "/>
                    </value>
                </SeparatorLine>
    RecordSet and parameters have been changed accordingly:
    RecordSet = HeaderRow,SeparatorLine,MainBody
    HeaderRow.fieldSeparator = ,
    HeaderRow.endSeparator = 'nl'  
    SeparatorLine.fieldFixedLength = 0,0   " sic! 
    MainBody.fieldSeparator = ,
    MainBody.endSeparator = 'nl'
    Has anybody an idea why I failed to receive the first carriage return and has somebody a more elegant solution?
    Kind Regards
       Uwe

    Hi,
    Thanks for reply. I have already used 'nl'.
    When i open into the notepad it is showing [] boxes rather then new line.
    e.g. 1 [] 2 []
    but when we open into wordpad it opens properly.
    Customer wants when he opens in notepad it should show line by line.
    e.g.
    1
    2
    How should i convince to customer ?

  • JMS sender communication channel content conversion

    Hi,
    I struck with the content conversion in the JMS Sender communication channel.
    I have configured the communication channel with the filed fixed lengths. (Simple type)
    The field fixed lengths i have given are 10,2,3,11
    The contents in the file 1000000072  230 111
    but, in the input xml after conversion iam getting 100000007 in the first field and 2 in the second field 23 in the third field.
    I have configured the sender communication channel as in the document in SDN.
    Even, i configured several communication channels. I didn't get this strange error any time.
    I have gone through SDN to fix this issue, but i didn't get solution.
    If anyone got rectified this kind of error, please answer your solution to me
    Thanking you,
    Regards,
    Krishnaraju.

    Hi,
    Thanks for all your support. The issue got resolved.
    The issue is due to the file, In the file the special characters are appearing. We are not able to see these characters in the notepad, wordpad, text editor.
    But, these characters are appearing in th syn text editor. So, we removed those characters and processessed the file. Now, it is successfull.
    Regards,
    Krishnaraju.

  • File/FTP adapter, outbound channel, content conversion, UTF-8 (Unicode)?

    We would like to send "delimited" files to another application (tab-delimited, CSV, ... - the other application does not support XML-based interfaces). Obviously we will have an outbound channel that uses the file/FTP adapter and the data will be subjected to "content conversion".
    The data contains names in many languages; not all of this can be represented in ISO Latin-1, much less in US-ASCII. I suppose UTF-8 would work. The question is: how is this handled by the FTP protocol? (considering that the FTP client is part of the SAP PI file/FTP adapter and the FTP server is something on the "other" machine)

    Hi Peter,
    you can maintain the file encoding in the outbound adapter. See [Configuring the Receiver File/FTP Adapter|http://help.sap.com/saphelp_nw2004s/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm]
    For your requirements "utf-8" sounds pretty fitting.
    Regards,
    Udo

  • Content Conversion Parameter- Help

    Dear Friends,
    I have a quick question regarding content conversion paramter.
    My structure is as follows
    <MT_Root>
    <Statement_response>
    <row>
    <Value1>ABC</Value1>
    <Value2>CDE</Value2>
    <Value3/>
    </row>
    <row>
    <Value1>DATA</Value1>
    <Value2>TEST</Value2>
    <Value3/>
    </row>
    <row>
    <Value1>CHECK</Value1>
    <Value2>OUT</Value2>
    <Value3/>
    </row>
    </Statement_response>
    </MT_Root>
    In the receiver adapter i'm using
    Record Structure :MT_Root,Statement_response,row
    row.fieldSeparator ,
    Statement_response.endSeparator 'nl'
    Statement_response.fieldSeparator 'nl'
    Everything is fine , if you see the o/p file there are lot of spaces appened between each fields. I don't want the spaces.
    If you guys help me out, I'll really appreciate it!!
    Thanks,
    raj.

    hi,
    possibly you could use small lengths while passing the data to file in FCC parameters.
    i.e fixedfieldlengths.
    also use the TooShortHandlingfield parameter with value "cut". it will ignore the large length of the fields and cut it down as per the values.
    Plesae refer below link for usage of these parameters,
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
    thnaks
    Swarup

  • What are the content conversion parameters for this structure

    Hi All,
    The below file is the text file. what are the content conversion parameters are required and what is the structure to create in the IR to convert into xml.
    Schedule D - District/Port List (by District Code) [Produced13APR11]
    District |    Port      |    Name
    Code     |    Code      |
    01       |              |    PORTLAND, ME
             |    0101      |    PORTLAND, ME
             |    0102      |    BANGOR, ME
             |    0103      |    EASTPORT, ME
             |    0104      |    JACKMAN, ME
             |    0105      |    VANCEBORO, ME
             |    0106      |    HOULTON, ME
             |    0107      |    FORT FAIRFIELD, ME
             |    0108      |    VAN BUREN, ME
             |    0109      |    MADAWASKA, ME
             |    0110      |    FORT KENT, ME
             |    0111      |    BATH, ME
             |    0112      |    BAR HARBOR, ME
             |    0115      |    CALAIS, ME
             |    0118      |    LIMESTONE, ME
             |    0121      |    ROCKLAND, ME
             |    0122      |    JONESPORT, ME
             |    0127      |    BRIDGEWATER, ME
             |    0131      |    PORTSMOUTH, NH
             |    0132      |    BELFAST, ME
             |    0152      |    SEARSPORT, ME
             |    0181      |    LEBANON AIRPORT
             |    0182      |    MANCHESTER USER FEE AIRPORT, NH
    02       |              |    ST. ALBANS, VT
             |    0201      |    ST. ALBANS, VT
             |    0203      |    RICHFORD, VT
             |    0206      |    BEECHER FALLS, VT
             |    0207      |    BURLINGTON, VT
             |    0209      |    DERBY LINE, VT
             |    0211      |    NORTON, VT
             |    0212      |    HIGHGATE SPRINGS/ALBURG

    since in this case you dont seem to have a key value to figure out what your header is, it is better to go for a two level mapping. i.e first read all the data - each line as an xml tag. and in the first mapping group it as required and then use it for your original mapping.
    Regards,
    Ninu

  • Content Conversion Parameter in File Receiver Adapter

    Hi all,
    I have created one File Receiver Adapter with Message Protocol 'File Content Conversion' and with the following configuration:
    Recordset Structure: Message
    Message.fieldFixedLengths: 1000
    My Message Type is:
    LogErro_MT
      Message (Type: String) (Occurrence: 0..Unbounded) (Details: Min,Max Length: 1000)
    But the file created by it has no data inside it. If I change the Message Protocol to 'File', the content of the file is the XML generated by the Outbound Proxy.
    Would someone can help me?
    Thanks in advance
    Leo

    Hi,
    Please create a data type with
    Records
    Message ---0..unbounded
    and hten MT for the same.
    In the receiver file adapter:
    Recordset Structure: Message
    Message.fieldFixedLengths: 1000
    Please check this weblog for the same:
    /people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp
    IS this what you are trying to do.
    Regards
    Vijaya

  • Regarding content conversion parameter

    Hi
    I am doing content conversion in sender file adapter.I want to remove " " in target file.
    I used  row.enclosureSignEsc ""
    but its not working.
    can any one tell me how to use enclosure sign parameter.
    Source Flat file looks like:
    "A00",417,"SC9",20050101,100617,3229
    "B01","EA",20041231,39.4,"ACT","F","D"
    "B01","EA",20041231,38.7,"ACT","F","W"
    "B01","EA",20050101,39.4,"TOD","F","D"
    "B01","EM",20041231,39.3,"ACT","F","D"
    "B01","EM",20041231,38.7,"ACT","F","W"
    "Z99",50
    In the target i want like this:
    A00,417,SC9,20050101,100617,3229
    B01,EA,20041231,39.4,ACT,F,D
    B01,EA,20041231,38.7,ACT,F,W
    B01,EA,20050101,39.4,TOD,F,D
    B01,EM,20041231,39.3,ACT,F,D
    B01,EM,20041231,38.7,ACT,F,W
    Z99,50
    Thanks&Regards
    venkat.

    >
    venky adireddy wrote:
    > Hi
    > I am doing content conversion in sender file adapter.I want to remove " " in target file.
    > I used  row.enclosureSignEsc ""
    > but its not working.
    > can any one tell me how to use enclosure sign parameter.
    >
    > Source Flat file looks like:
    >
    > "A00",417,"SC9",20050101,100617,3229
    > "B01","EA",20041231,39.4,"ACT","F","D"
    > "B01","EA",20041231,38.7,"ACT","F","W"
    > "B01","EA",20050101,39.4,"TOD","F","D"
    > "B01","EM",20041231,39.3,"ACT","F","D"
    > "B01","EM",20041231,38.7,"ACT","F","W"
    > "Z99",50
    >
    > In the target i want like this:
    >
    > A00,417,SC9,20050101,100617,3229
    > B01,EA,20041231,39.4,ACT,F,D
    > B01,EA,20041231,38.7,ACT,F,W
    > B01,EA,20050101,39.4,TOD,F,D
    > B01,EM,20041231,39.3,ACT,F,D
    > B01,EM,20041231,38.7,ACT,F,W
    > Z99,50
    >
    >
    >
    > Thanks&Regards
    > venkat.
    THERE
    there is no parameter to achieve what you want in FCC.
    as mentioned earlier you will have to use a function to remove the "
    you dont have to create a UDF you can use the standard text function available in XI - replaceString

  • Content conversion parameters for fixed length file

    Hi,
    Hey i have a small doubt.My input is like this
    99443  123213  232234  12312    127544  23423
    Here i have four recorsetnames namely HEADER1,HEADER2,HEADER3,HEADER4,HEADER5,HEADER6 all the recordsets are of same size but the lengths of the fields in it vary so i specified the following parameters
    HEADER1.fieldFixedLengths=1,3,1
    HEADER1.fieldNames=value1,value2,value3
    HEADER1.endseperator=" "
    HEADER2.fieldFixedLengths=1,3,2
    HEADER2.fieldNames=value1,value2,value3
    HEADER2.endseperator=" "
    MY OUPUT XML STRUCTURE SHOULD BE like this
    <header1>
    <value1>9<\value1>
    <value2>944<\value2>
    <value3>3<\value3>
    <\header1>
    <header2>
    <value1>1<\value1>
    <value2>232<\value2>
    <value3>13<\value3>
    <\header2>
    Is the content conversion parameters i specified enough for that. I wanted to know how would it know the begin of the next recordset(ie the seperation between the two recordsets) .Please help me its vey urgent
    Thanks in advance
    Sriandh

    Are header 1 fields always going to occur first , then header 2 and so on?
    By default file adapters do not support Nested Strcutures and so if the sequence is going to be the same and all of these have an occurence of 1..1 then things will work.
    But if there is going to be an occurnece of *  then you will need to use KeyFields.
    Regards
    Bhavesh

Maybe you are looking for

  • Windows 8.1 will not download iTunes setup file

    Windows 8.1 will not download iTunes setup file. It asks if I want to save the file. I click yes but it doesn't download. Tried numerous times on my new Toshiba Qosmio computer.

  • Has anyone returned an iPod for a gift card

    Hi everyone. Apple was kind enough to return my 3 week old refurbished iPod video so I could get a new one. Now I am iPodless! I was planning on getting a new iPod right away when I got my Gift Card. Seel, I bought the iPod using a gift card. Now the

  • Export destination picker: allow entering of path

    In the Export->Export Location->Choose->Browse for Folder, there is no option to paste a path directly. With most other programs, I find this the most efficient method. I have a folder open in another window, and all I have to do is copy and paste th

  • File icons in Finder shows random app icons

    My image files all have an iTunes icon. I don't know how it got like this, but how can I fix it so it shows the generic Image or Preview (which is the app selected to open all JPGs) icon? I tried selecting a file and choosing to open all files of thi

  • Missing adobe application support file

    I had to purchase a new machine. Mac Book Pro - version 10.6.5 2.4 Ghz intell core 2 duo I was running Photoshop CS 8.0 I dragged my app to the new machine and now see this message: Now at first this was just fine. But I cannot get my pics to open. I