Bypassing a node in Content Conversion

Searched to no avail.
I have a node in my Idoc that I do not want to be passed to the outputfile in the output file. 
Does anyone know how to do this?

Hi Mark,
Take a look at this thread..
File Adapter - Content conversion parameters at Receiver
Hope it helps you!
cheers,
Prashanth
P.S Please mark helpful answers

Similar Messages

  • Remove Header Node in File Content Conversion

    Hi Guys,
         In our scenario receiver payload is
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:MarketInventoryResponse  xmlns:ns1="PRINCIPALS/MarketInventory">
         <Header>
                <CurrentDate>200809</CurrentDate>
         </Header>
         <MarketInventory>
                <Local_ProductCode>121</Local_ProductCode>
                <WH_QTY>20</WH_QTY>
                <WH_Cost>3000</WH_Cost>
                <Store_QTY>40</Store_QTY>
                <Store_Cost>5000</Store_Cost>
          </MarketInventory>
    </ns1:MarketInventoryResponse>
    We are using File content conversion method. Now we got the output is
    200809
    121#20#3000#40#5000
    But We need below mentioned format.
    121#20#3000#40#5000
    we don't need CurrentDate which is in Header node. So, how to ignore Header node in FCC method. Please any one help me.
    Note :  Now we using following parameters in FCC
    Recordset Structure  : MarketInventory
    MarketInventory.addHeaderLine   :  0
    MarketInventory.fieldSeparator     :  #
    MarketInventory.endSeparator      :  'nl'
    Thanks & Regards
    Vijay

    Hi Vijaya,
    You have two options:
    1.-  Sãnthosh Kûmãr V   Solution:
    Recordset Structure : Header,MarketInventory
    Header.fieldFixedLengths = 0
    Header.fixedLengthTooShortHandling = Cut
    Header.endSeparator = '0'
    2.- Use Adapter-Specific Message Attributes in your File adapter.
    In the last one you would have to set the name of your file in FileName atributte.
    Carlos

  • File content conversion: nodes have multiple occurence and is jumbled

    Hi,
    Here is one structure used in file content conversion.
    Header
    Dataline1
    Dataline1
    Dataline1
    Dataline2
    Dataline2
    Dataline2
    Header, Dataline1 and Dataline2 are nodes containing more than one fileds.
    We have mentioned 'fieldSeparator', 'EndSeparator' and 'keyFieldValue' for each of the nodes Header, Dataline1 and Dataline2 .
    Now the requirement has changed and the source file structure is as given below.
    Header
    Dataline1
    Dataline2
    Dataline1
    Dataline2
    Dataline1
    Dataline2
    Now with the same communication channel, the content conversion picks up only the first occurence of Dataline1, Dataline2 ie only this much
    (Header
    Dataline1
    Dataline2)
    is being picked or read.
    The other occurences are lost, even though logically it should pick all of them, since 'keyFieldValue' is specified for each node..
    Should I give any extra parameters in the communication channel for file content conversion.? or else what is the best way to proceed

    Hi John !
    Have you checked the recordset structure in the file content conversion parameters?? like "Header,1,Dataline1,,Dataline2, " to specifiy that it should be 1 header structure, N dataline1 and N dataline2 ??
    Regards,
    Matias.

  • Content Conversion for Item node under Header node

    Hi,
    Below is the file sample:
    0LBS00000000082011090707:30:13~0000000009
    4GBP55.67SB300005VISTADocNO1100DistChanPaymentDays
    5001QuanUoMNetPriceGrossPricePubDiv9781444724585201109071001.1
    5002QuanUoMNetPriceGrossPricePubDiv9781444724585201109071001.1
    4GBP55.67SB300005VISTADocNO1100DistChanPaymentDays
    5001QuanUoMNetPriceGrossPricePubDiv9781444724585201109071001.1
    1~7
    Record Type:Header Record(Always = 0),Min Occurrence:1,Max Occurrence:1
    Record Type:Sales Invoice Header Record (Always = 4),Min Occurrence:0,Max Occurrence:unlimited
    Record Type:Sales Invoice Item Record (Always = 5) ,Min Occurrence:1(per Sales Invoice Header Record)
    ,Max Occurrence:999999 (per Sales Invoice Header Record)
    Record Type:Trailer Record(Always = 1),Min Occurrence:1,Max Occurrence:1
    In content conversion:
    Record set structure:Header,1,SalesInvoiceHeader,(Star),SalesInvoiceItem,(Star),Trailer,1
    Key field name:RecordType
    Header.fieldSeparator ~
    Header.fieldNames RecordType,SendingSystem,FileNumber,CreationDate,CreationTime,NextFileNumber
    Header.keyFieldValue 0
    SalesInvoiceHeader.fieldSeparator ~
    SalesInvoiceHeader.fieldNames cordType,Currency,ExchangeRate,DocumentType,Customer,VistaDocNumber,PubDiv,DistChan,PaymentDays
    SalesInvoiceHeader.keyFieldValue 4
    SalesInvoiceItem.fieldSeparator ~
    SalesInvoiceItem.fieldNames RecordType,ItemNumber,Quantity,UoM,NetPrice,GrossPrice,PubDiv,Material,BillDate,VATAmount,VATRate
    SalesInvoiceItem.keyFieldValue 5
    Trailer.fieldSeparator ~
    Trailer.fieldNames RecordType,RecordCount
    Trailer.keyFieldValue 1
    ignoreRecordsetName true
    The Src str in ESR is
    1. Header
    2. SalesInvoiceHeader
    SalesIncoiveItem(Chlid node of SalesInvoiceHeader)......
    3. Trailer
    Provide some inputs
    Thnkx

    VJ,
    You are absolutely right it is not possible to get multiple hierarchy using file content conversion.
    Splitbyvalue function would not work in my scenario as I need to group FED records based on first few characters in the first column of FED records. I wrote a UDF to insert context change based on the column value.
    Thanks again for your help.
    Regards
    Haseeb

  • FIle Content Conversion Problem in IDOC-XI-File Scenario

    Dear All,
    I am doing IDOC-XI-FILE scenario.
    I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like <b>%store_code%_%current_date%_sitemaster.xml</b> , I have completed the dynamic generation successfully .
    Now there is slight change in the requirement ,<b>we have to suppress the current_date node of the xml content</b> . i have tried to suppress the current_date using these <b>DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut</b> , But I am unable to suppress it Can some body provide me the details on this .
    The output xml version generated by Reciever file adapter is as below :
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    </ns0:MT_SITE_MASTER>
    Plz provide me the code I have to write in the file content conversion .
    Thanks in advance
    Regards
    Prabhat

    If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
    My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier.  Then use the Suppress Logic for the Current Date.
    So it will look like this-
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
    - <SITE_DATA>
    <STORE_CODE>N002</STORE_CODE>
    <TITLE_MEDI>Company</TITLE_MEDI>
    <STORE_NAME>Mount Road</STORE_NAME>
    <STREET>Chennai</STREET>
    <COUNTRY>IN</COUNTRY>
    <SALES_TAX_NO>12345678910</SALES_TAX_NO>
    </SITE_DATA>
    <CURR_DATE>
       <CURRENT_DATE>20051105</CURRENT_DATE>
    </CURR_DATE>
    </ns0:MT_SITE_MASTER>
    So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
    CURR_DATE.fieldFixedLengths - 0
    CURR_DATE.fixedLengthTooShortHanling - Cut
    And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
    Hope this solves ur problem.
    Regards,
    Moorthy

  • File Content Conversion Problem

    Hi
    I have a flat file having 10 fileds with fixed length of field 7 characters
    abc  bcd  dce  cef  ecf  fgi
    123  234  343  233 434 343
    322  222  222  222 222 222
    +++++++++++++++++++++++++++++++
    XML CODE FOLLOWS
    +++++++++++++++++++++++++++++++
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_send xmlns:ns0="http://OTO-Continue.com">
      -<SEND>
       <abc>343</abc>
       <bcd>343</bcd>
       <dce>434</dce>
       <cef>3434</cef>
       <ecf>343</ecf>
       <fgi>434</fgi>
      </SEND>
      </ns0:MT_send
    As per the client req I'm going with FCC. The file is picking fine with the FILE. But not picking with the FCC.
    The parameters which I gave are as follows.
    SOURCE I feel it is fine since file is picking fine and keeping the same for FCC also.
    PROCESSING
    QOS -- Exactly Once
    Poll Interval -- 10
    Processing Mode -- Delete
    Empty-File Handling -- Process empty files
    CONTENT CONVERSION Parameters
    Document Name -- (am giving sender data type name) DT_send
    Document NSpace -- http://OTO-Continue.com
    Recordset Name -- SEND
    Recordset Structure -- SEND,*
    Recordset Sequence -- Ascending
    Recordset per Message -- 0
    And in the table the parameters am settings are
    SEND.fieldNames                 abc,bcd,cde,def,efg,ghk
    SEND.fieldFixedLengths      7,7,7,7,7,7       (because each and every field has 7 characters)
    SEND.keepIncompleteFields       No
    SEND.fieldFixedLengthType      char
    SEND.fieldContentFormatting     trim
    SEND.fieldEndSeparator            'nl'
    This was the configuration. But this is not working I monitored the Communication Channel and file is not reading and not getting deleting.
    What actually went wrong in above configuration. Why it is not working.
    Thanks.

    Hi Swarna,
    CONTENT CONVERSION Parameters
    Document Name -- ?
    DocumentNSpace -- ?
    Recordset Name -- ?
    Recordset Structure -- ?
    Recordset Sequence -- Ascending
    Recordset per Message -- ?
    Document Name - <Message Type> eg:- (MT_ABC)
    DocumentNSpace - Name space of your MT
    Recordset Name - The root node( Which has one occurence)
    Recordset Structure - The parent node of the fields(can have multiple occurences)
    Recordset Sequence -- Ascending
    Recordset per Message -- 1/* (No.of records per each record set)
    In your structure
    +++++++++++++++++++++++++++++++
    XML CODE FOLLOWS
    +++++++++++++++++++++++++++++++
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_send xmlns:ns0="http://OTO-Continue.com">
    -<SEND>
    <abc>343</abc>
    <bcd>343</bcd>
    <dce>434</dce>
    <cef>3434</cef>
    <ecf>343</ecf>
    <fgi>434</fgi>
    </SEND>
    </ns0:MT_send
    There is no root node,  so in your FCC you need to mention your RecordsetName and you can ignoreRecordSetName in result structure. Check the following blog simulates your requirement.
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    Regards,
    Prasanna

  • Content Conversion in receiver channel

    Hi all,
    I have a proxy to FTP scenario with no mapping involved.Over proxy communication PI is receiving the data, I am creating the CSV file using content conversion in receiver channel and placing the file at FTP.
    The file name is coming in one of the field of the input xml,I am using variable substitution and setting the file name from that particular field value.But as I don't want that node and file name element in my output file content, please guide me what parameters can I set in my content conversion to remove the FileNode from o/p csv file.
    The sample input xml is
    <MT>
    <Record>
    <Field1>1</Filed1>
    <Field2>2</Filed2>
    </Record>
    <Record>
    <Field1>3</Filed1>
    <Field2>4</Filed2>
    </Record>
    <FileNode>
    <FileName>InutFile</FileName>
    </FileNode>
    </MT>
    I want output xml to be like
    1,2
    3,4
    I have followed this blog /people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12 to cut the FileNode, but it gives an error in cc parameters.
    In my actual i/p payload,the Record is 0..unbounded and there are 50 sub elements inside Record element.
    Please provide your inputs.
    Thanks,
    Ruchi

    Hi Ruchi,
    Change your structure like this.
    MT>
    <Record>
    <Field1>1</Filed1>
    <Field2>2</Filed2>
    </Record>
    <Record>
    <Field1>3</Filed1>
    <Field2>4</Filed2>
    </Record>
    <FileNode>
    <FileName>InutFile</FileName>
    </FileNode>
    </MT>
    Dont put the filenode under Record.
    Also Add the below parameters.
    FileNode.fieldSeparator     '0'
    FileNode.endSeparator     '0'
    FileNode.fieldFixedLengths     0
    FileNode.fixedLengthTooShortHandling     Cut
    FileNode.fieldNames     FileName
    Now use the same parameter mentioned in the blog .Your problem will be resolved.

  • Receiver File Adapter - File Content Conversion

    My XML is like this in XI:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Target xmlns:ns0="http://test.com">
    - <Target>
    - <Directory>
      <Comment_1>#</Comment_1>
      <Directory_Rec>testfile.csv</Directory_Rec>
      </Directory>
    - <File>
      <Comment_2>#</Comment_2>
      <File_Rec>testfile.csv</File_Rec>
      </File>
      <Target_Rec>Record 1</Target_Rec>
      <Target_Rec>Record 2</Target_Rec>
      <Target_Rec>Record 3</Target_Rec>
      </Target>
      </ns0:Target>
    and my CSV file should looklike
    #testfile.csv
    #testfile.csv
    Record 1
    Record 2
    Record 3
    How can I do that. Would someone help he. If I put fieldseparator as 'nl' its writing as follows
    Record 1
    Record 2
    Record 3

    Hi Ram,
    with the structure you have given we can not achieve your target csv structure. at the max you can achieve the output as the following
    #testfile.csv
    #testfile.csv
    Record 1Record 2Record 3
    using the below specified config
    Recordset Structure: Target,Directory,File
    Target.fieldSeparator as 'nl'
    Directory.fieldSeparator as '0'
    Directory.endSeparator as 'nl'
    File.fieldSeparator as '0'
    File.endSeparator as 'nl'
    in teh output the last line Record 1... comes like that because the File.fieldSeparator's value overrides the parents fieldSeparator i.e of Targets. '0' stands for no separator.
    if you want to achieve your target output Target_Rec should be inside one more node say TargetRecords
    and XML should be like this in XI:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Target xmlns:ns0="http://test.com">
    - <Target>
    - <Directory>
    <Comment_1>#</Comment_1>
    <Directory_Rec>testfile.csv</Directory_Rec>
    </Directory>
    - <File>
    <Comment_2>#</Comment_2>
    <File_Rec>testfile.csv</File_Rec>
    </File>
    <TargetRecords>
    <Target_Rec>Record 1</Target_Rec>
    <Target_Rec>Record 2</Target_Rec>
    <Target_Rec>Record 3</Target_Rec>
    </TargetRecords>
    </Target>
    </ns0:Target>
    and the content conversion configuration should be
    Recordset Structure: Target,Directory,File,TargetRecords
    Target.fieldSeparator as 'nl'
    Directory.fieldSeparator as '0'
    Directory.endSeparator as 'nl'
    File.fieldSeparator as '0'
    File.endSeparator as 'nl'
    TargetRecords.fieldSeparator as 'nl'
    Regards,
    Sundar

  • DT for File Content Conversion scenario

    Hi Guys,
    I am working on IDOC to file scenario in which I want to know which type of DT should I go for?
    DT_Type
    ....Row
    ......Filed1
    ......Filed2
    ......Field3
    ...Row
    DT_Type
    Or
    DT_Type
    ..Details
    ....Row
    ......Filed1
    ......Filed2
    ......Field3
    ...Row
    ..Details
    DT_Type
    I am going for Receiver Content conversion as I need to produce Flat like, I have about 30 filed names and I am wondering is it possible not ot mention field names in Content conversion?
    What is the parameter to place to get a new line after each record? I am using row.endSeparator as 'nl' I am getting some special character instead of starting a new record in next line.
    Thanks
    Rajeev

    HI,
    The SOURCE IDOC strcuture is:
    IDOCNAME----
    1..1
    >IDOC--
    1..1
    >BEGIN--
    required
    >EDI_DC40--
    1..1 (it has sub nodes but not required)
    >E1KNAM1--
    1..1
    >SEGMENT----
    Required
    >Werks----
    0..1
    >Z1KNU2----
    0..1 (SUB SEGMENT OF E1KNAM1)
    >ZNUM----
    0..1
    >Z1ADD----
    0..7 (SUB SEGMENT OF E1KNAM1)
    >PostCode----
    0..1
    >E1KAVVM----
    0..999(SUB SEGMENT OF E1KNAM1)
    >VTWEG----
    0..1
    >LOVEM----
    0..1
    >E1KAVPM----
    0..999(SUB SEGMENT OF E1KNAM1)
    >KUNN2----
    0..1
    >Z1KAN--0..1 (SUB SEGMENT OF E1KAVPM---(SUB SEGMENT OF E1KNAM1))
    >NAME1----
    0..1
    Target File structure is:
    MT_Type----
    1..1
    Row--
    0..Unbound
    Filed1----
    0..Unbound
    Filed2----
    0..Unbound
    Filed3----
    0..Unbound
    Filed4----
    0..Unbound
    Filed5----
    0..Unbound
    Filed6----
    0..Unbound
    if IDOC contains one IDOC data then it has to generate one file .. If IDOC contains more than one IDOC information then it has to generate one file with multiple IDOC informaiton in it.
    how this can be achieved?
    Thanks
    Rajeev

  • File Content Conversion

    Hi All...
    I am facing a Problem with File Content Conversion in sender File Adapter .
    In my scenario file contains 3 rows (nodes ) of Data but actually the structure of the source is with 4 nodes ,if i do the File Content conversion for 4 nodes i am getting an error
    stating 3 rd row is missing...
    Hear i have mentioned Keyfiled value for Each row ...for Each row like ROU,HDR,KLP,CTR
    In the File KLP row is missing ...how can i handel that .. ?
    thanks in Advance
    shakif

    if ur file will have only those 3 key field values Y do u add the 4th key field (i mean the extra row) in the FCC. if u skip that in content conversion what happens?
    in teh source structure for this extra node change the occurance to 0...

  • File sender adapter: Content conversion for very deep nested structure

    Hi all
    I have a file which looks like this
    HDOCKET    9800000660980000061911062009AA123456bbWM100012349800000619
    DDOCKET_TEST001 4012YAG1 
    WZOA00000000010000000001
    WZOA00000000020000000002
    WZOB00000000030000000003
    IAAXX000001
    IAAXX000002
    C0000000000000000000100000000000000000001000000000000000000020000000000000000000300000000000000000004
    T2
    and my structure is
    Header  - 1
    Detail     - 0....Unbounded
            Bag     - 0.....Unbounded   (sub node of detail)
            Track  - 0.....Unbounded    (sub node of detail)
            Customer - 0.....Unbounded    (sub node of detail)
    Trailer    - 1
    and in the file sender adapter i mentioned the following content conversion setting
    HEADER,1,DETAIL,*,Bag,*,Track,*,Customer,*,TRAILER,*
    But when i go and see in the monitoring i received the following conversion
    <?xml version="1.0" encoding="utf-8" ?>
    <ns:MT_REQ xmlns:ns="http://royalmail.com/dd_c">
    <HEADER>
      <ID>H</ID>
      <INT>DD</INT>
      <CAR>9899999660</CAR>
      <CUS>9899999619</CUS>
      <POST>11062009</POST>
      <NUMBER>AA123456bbWM10001234</NUMBER>
      <ACC>9899999619</ACC>
      </HEADER>
    <DETAIL>
      <ID>D</ID>
      <Bag>DOCKET_TEST001</Bag>
      <S>4012</S>
      <Code>YAG</Code>
      <mat>1</mat>
      <count/>
      <Mixed />
      </DETAIL>
    <Bag>
      <ID>W</ID>
      <Zone>ZOA</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
    <Bag>
      <ID>W</ID>
      <Zone>ZOA</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
    <Bag>
      <ID>W</ID>
      <Zone>ZOA</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
      </Bag>
    <Track>
      <ID>I</ID>
      <Item>AAXX000001</Item>
      </Track>
    <Track>
      <ID>I</ID>
      <Item>AAXX000001</Item>
      </Tracked>
    <Customer>
      <ID>C</ID>
      <OrigCustomer>00000000000000000001</OrigCustomer>
      <Field1>00000000000000000001</Field1>
      <Field2>00000000000000000002</Field2>
      <Field3>00000000000000000003</Field3>
      <Field4>00000000000000000004</Field4>
      </Customer>
    <TRAILER>
      <ID>T</ID>
      <Count>2</Count>
      </TRAILER>
      </ns:MT_REQ>
    whereas i wanted it like:
    <?xml version="1.0" encoding="utf-8" ?>
    <ns:MT_REQ xmlns:ns="http://royalmail.com/dd_c">
    <HEADER>
      <ID>H</ID>
      <INT>DD</INT>
      <CAR>9899999660</CAR>
      <CUS>9899999619</CUS>
      <POST>11062009</POST>
      <NUMBER>AA123456bbWM10001234</NUMBER>
      <ACC>9899999619</ACC>
      </HEADER>
    <DETAIL>
      <ID>D</ID>
      <Bag>DD_TEST001</Bag>
      <S>4012</S>
      <Code>egg</Code>
      <mat>1</mat>
      <count/>
      <Mixed />
    <Bag>
      <ID>W</ID>
      <Zone>zzz</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
    <Bag>
      <ID>W</ID>
      <Zone>zzz</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
    <Bag>
      <ID>W</ID>
      <Zone>zzz</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
      </Bag>
    <Track>
      <ID>I</ID>
      <Item>AAXX000001</Item>
      </Track>
    <Track>
      <ID>I</ID>
      <Item>AAXX000001</Item>
      </Tracked>
    <Customer>
      <ID>C</ID>
      <OrigCustomer>00000000000000000001</OrigCustomer>
      <Field1>00000000000000000001</Field1>
      <Field2>00000000000000000002</Field2>
      <Field3>00000000000000000003</Field3>
      <Field4>00000000000000000004</Field4>
      </Customer>
    </DETAIL>
    <DETAIL>
      <ID>D</ID>
      <Bag>DD_TEST002</Bag>
      <S>4012</S>
      <Code>egg</Code>
      <mat>1</mat>
      <count/>
      <Mixed />
    <Bag>
      <ID>W</ID>
      <Zone>zzzzzz</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
    <Bag>
      <ID>W</ID>
      <Zone>ZOA</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
    <Bag>
      <ID>W</ID>
      <Zone>zzz</Zone>
      <Item>0000000001</Item>
      <Number>0000000001</Number>
      </Bag>
      </Bag>
    <Track>
      <ID>I</ID>
      <Item>AAXX000001</Item>
      </Track>
    <Track>
      <ID>I</ID>
      <Item>AAXX000001</Item>
      </Tracked>
    <Customer>
      <ID>C</ID>
      <OrigCustomer>00000000000000000001</OrigCustomer>
      <Field1>00000000000000000001</Field1>
      <Field2>00000000000000000002</Field2>
      <Field3>00000000000000000003</Field3>
      <Field4>00000000000000000004</Field4>
      </Customer>
    </DETAIL>
    <TRAILER>
      <ID>T</ID>
      <Count>2</Count>
      </TRAILER>
      </ns:MT_REQ>
    i.e. i need all Bag ,Track and Customer inside detail tag.
    could anyone help me in this..i've already searched SDN and got some link as useful but none of them were totally related.
    Regards
    Naina

    Naina
    Pls. check my forum link, i had the single level hierarchy XML file which I converted into nested structure & then into flat file.
    File Conversion in Rec File Adapter with subnodes
    This can give you an idea how to go ahead. Let me know in case you need any more info about this.

  • File Content Conversion on the Sender Adapter in PI 7.1

    Hi Experts
    I am working on a file to Proxy scenario where my file is fixed format length which will have only one Structures (Details Records) that would be coming from the text file but in the message type I have delcared Header, Detail , Trailer,
    However I would be receiving the only Detail part (No header and Trailer) in some instances  what value should I give for the header and trailer in the Content conversion part,
    Thanks
    PR

    Since you are going to get values only some instances  for header and trailer node, you can create
    Header  structure   &  Trailer structure  - make the occurence 0 to 1
    Note: if your Header and Trailer values are empty for some instances then no worries. You declare FCC fields for header and trailer similar to Details.
    Refer SAP FCC help link.

  • Content conversion in Reciever File  Adapter

    Hi Frens,
    Iam doing A FCC in Reciever file adapter. My input structure is
    DT_structure
    ->Record
      ->Row
           Field1
           Field2
           Field3
    I have donr the configuration as
    Recordset Structure : Record,Row
    Row.fieldSeparator : ,
    Row.endSeparator : 'nl'
    Record.fieldSeparator : 'nl'.
    With this configuration  Iam able to display only one record but I need to display multiple records in the file. Please do suggest me wha need to be done to achieve this.
    Radhika.

    First check whether your datatype has the occurrence of records unbounded or not. Then goto content conversion. If both your Record and Row tags can occur multiple times, then use
    Recordset Structure : Record,*,Row,*
    Or if Record occurs only once and multiple Row nodes are required, then use
    Recordset Structure : Record,1,Row,*
    Regards,
    Prateek

  • Mapping issue after Content Conversion in PI 7.1

    Hi Experts
    I am working on a File (Fixed format) to proxy , Data is getting converted in the File Content and conversion and passing to mapping as xml data , But the when the mapping happens no values are being returned on the  target side
    When I load the data (xml ) file from sxmb_moni on the sender side all nodes  shows in red color though file content happened without issues
    please provide the inputs how to map with the values
    Thanks
    PR

    A couple of checkpoints for you:
    1. When you load the XML from SXMB_MONI in the test tab of message mapping it turns red..this means the constructed XML (from CC content conversion) doesnt match the one (XSD) defined in your ESR/IR. In this case you have to check again thoroughly the file content conversion fields values/field length in the sender Communication chaneel.
    2. Once you rectify the error above then you can test the mapping in ESR message mapping.

  • File Content Conversion issue in PI 7.1

    Hi Experts
    I am working on a file to Proxy scenario, I am getting a flat file with , separated but my file will have multiple nodes and I need to do the content conversion and map it to the following structure
    Interface Header
      InterfaceName
      UserID
      Date
      Time
    Journal Entries (1 - Unbounded)
        DocumentHeader
           DocumentDate
           DocHeadetext
           postingDate
        DocumentLineItems
          lineItemno
          lineitemText
          postingkey
    InterfaceTrailer
      Noofrecords.
    Here the problem :I have declared the InterfaceHeader, DocumentHeade,DocumentLineItems and Interface trailer but for Journal entries node what are all the parameters to declare in the content conversion
    please let me know if there are any solutions for this coples structure (content conversion)
    Thanks
    PR

    <?xml version="1.0" encoding="UTF-8"?>
    <!-- New document created with EditiX at Thu May 12 18:57:06 EDT 2011 -->
    <xsd:schema targetNamespace="http://pi.dvn.com/fa/app/ecc/journalEntries/10" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pi.dvn.com/fa/app/ecc/journalEntries/10">
         <xsd:element name="MT_JournalEntryVouchers" type="DT_JournalEntryVouchers"/>
         <xsd:complexType name="DT_JEHeader">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Header structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="documentDate">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="docHeaderText" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="25"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="postingDate">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="companyCode">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="currency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="documentType">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionCode">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="referenceNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="16"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accrualReasonForReversal" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accrualReversalDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="taxCalculationFlag" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JELineItems">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Line Items structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="lineItemNumber">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="lineItemText" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="postingKey">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="companyCodeLineitem">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accountNumber">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="17"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionAmount">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="costCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accountType">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="wbsElement" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="8"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="quantity" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="unitOfMeasure" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="productionDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="tradingPartner" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="6"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="materialNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="18"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentKeyTerms" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentBlockKey" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentMethod" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentMethodSupplement" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="baselineDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="witholdingTaxCode" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="payer_payeeNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="jointVenture" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="6"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="equityGroup" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="partnerAcctNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="recoveryIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="billingIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="orderNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="profitCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="partnerProfitCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="assignment" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="18"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="referenceKey" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionType" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="amountInLocalCurrency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="amountInGroupCurrency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="taxCode" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="splGLIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="assetTransactionType" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="xref2" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JournalEntryRecord">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Record Set for Journal Entry</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="InterfaceHeader" type="DT_InterfaceHeader"/>
                   <xsd:element name="journalEntries" type="DT_JEDocument" maxOccurs="unbounded"/>
                   <xsd:element name="InterfaceTrailer" type="DT_InterfaceTrailer"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JEDocument">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Document Data Type</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="documentHeader" type="DT_JEHeader"/>
                   <xsd:element name="documentLineItems" type="DT_JELineItems" maxOccurs="unbounded"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_InterfaceTrailer">
              <xsd:sequence>
                   <xsd:element name="numberOfRecords" type="xsd:string" minOccurs="0"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JournalEntryVouchers">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Voucher Interface structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="JournalEntryRecordSet" type="DT_JournalEntryRecord"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_InterfaceHeader">
              <xsd:sequence>
                   <xsd:element name="interfaceName" type="xsd:string"/>
                   <xsd:element name="userID" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="runDate" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="runTime" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="testRun" type="xsd:string" minOccurs="0"/>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

Maybe you are looking for