File Content Conversion(SenderFileadapter) fields parameters

Hi all
           I am doing aFile to File scenario,
Using content Conversion at SENDER FILE adapter
my source message type is as :  
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Cnet_Source xmlns:ns0="http://abc.com/Cnet">
   <<b>HeaderPayment</b>>
      <First_Payt_Doc/>
      <Beneficiary_email_id/>
   <<b>/HeaderPayment</b>>
   <<b>AdviceFormat</b>>
       <Client_Code/>
      <Payment_Document_No/>
      <Document_Date/>
   <<b>/AdviceFormat</b>>
   <<b>LineItem</b>>
     <Title1/>
      <Title3/>
   <<b>/LineItem</b>>
   <<b>FILENAME</b>>
      <FNAME/>
   <<b>/FILENAME</b>>
</ns0:MT_Cnet_Source>
it has 3 structures :HeaderPayment(0,1),AdviceFormat(0,1),LineItem(0,unbounded)
in Recordsetstructure i gave= HeaderPayment,1,AdviceFormat,1,LineItem,1
in FCC parameters i used
HeaderPayment.fieldname... =First_Payt_Doc,Beneficiary_email_id
HeaderPayment.fieldseperator ='nl'
HeaderPayment.endseperator ='nl'
ignorerecordset = true
similarly for rest 2 structure also
my source text  file is type :
we0023
[email protected]
xyc
acd
21/05/2007
10034
acccd
payment
i tried alot of options,refering sdn..still on reading the file value are not coming in the designated fields...
Thanks &Regards,
ajay

You are Right i correct it but i sxmb_moni
i get as <HeaderPayment>
<First_Payt_Doc/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
</AdviceFormat>
<LineItem>
<Title1/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
the header payment should not repeat....
Regards
Ajay

Similar Messages

  • File Content Conversion - Key Field Value

    Hi Experts,
    I am using File to Idoc scenario for my mapping. In the receiver Communication channel, I am using File Content Conversion. My scenario is as follows :
    I have a recordset with Header and Line items with Key Field Indicator as 'H' and 'L'. In some cases, the value for this Key Field is coming in as something other than 'H' and 'L'. I need to throw an exception when this Key Field is not 'H' or 'L'.
    In the 'Content Conversion' tab, my attributes are as:
    Header_Structure.keyFieldValue = 'H' and Line_Structure.keyFieldValue = 'L'. Is there any more attributes that I need to add ?
    Please advise. Thanks a lot.
    Regards,
    Freddy.

    >>multiple key field values in FCC configuration i.e Line_Structure.keyFieldValue = H or L
    AFAIK it is not possible but lets wait for other experts to comment on this...
    >>Can keyFieldInStructure (add, ignore) parameter help me in this case ?
    No. this parameter is only used when you want to include key filed in ur XML structure(add) or not (ignore)...
    Chk this:
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

  • File Content Conversion ( avoid fields in conversion)

    Hi all
                        An IDoc to File scenario , I am doing file content conversion in receiver File adapter.
    my message type for file  2 HEADER each having its own substructure
    Like    1header
                       fieldA               
              2header
                       fieldC
                       fieldD
    I want the "<b>1header and its 1 subelement not be converted in file content conversion"  </b>   
    because  its used for dynamic file name configuration, so i do'nt want it to be written on file.
    Regards
    Ashutosh.r

    Rawat,
    Yes I know you will get that error. That is the reason why I have told you to add another parameter fixedLengthTooShortHandling as Cut. So add one more parameter in your file receiver communicaion channel: Also I hope ASFD0101 is your strcuture not the field in the strcuture.
    ASFD0101.fixedLengthTooShortHandling :  Cut
    Then I think it should work like a boom.
    ---Satish

  • File Content Conversion ignore fields

    HI ,
    I need to ignore some rows in the middle of the data in File content conversion for exaple
    H1,Field1,Field2,Field3
    A,GB07,MICHEL,1000
    H2,Field3,Field4,Field5
    B,GB08,andrew,2000
    The above is the sample text file from the source , I need to parse in the below
    RECORDset1
    <Field1>A</Field1>
    <Field2>MICHEL</Field2>
    <Field3>100</Field4>
    RecrodSet2
    <Field4>A</Field4>
    <Field5>andrew</Field5>
    <Field6>200</Field6>
    I need to omit or ignore the H1 and H2 rows from the File Content conversion.,
    Please guide me how to achive this using File Content conversion

    Hi Krishna,
    In case if H1 and H2 is your record type or line type then to ignore line for this type... just do not handle "keyFieldValue" in the content conversion for H1 and H2 record type.
    Thanks,
    Binod

  • File Content Conversion some fields are missing

    Hello Friends,
    I am trying to convert a fixed length flat file to XML.
    Here are my parameters
    CompanyCodeRecord.fieldNames = field1,field2,....field50
    CompanyCodeRecord.fieldFixedLengths = 1,4,15,20...,50 (for all 50 fields)
    CompanyCodeRecord.processFieldNames = fromConfiguration
    CompanyCodeRecord.lastFieldsOptional = YES
    CompanyCodeRecord.endSeparator = nl
    If I do not use lastFieldsOptional=YES then the adapter is throwing an exception Error: <b>Conversion of complete file content to XML format failed around position 0 with java.lang.Exception: ERROR converting document line no. 1 according to structure 'CompanyCodeRecord':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
    last retry interval started 19:31:08 2005-07-11</b>
    If I use lastFieldsOptional=YES then the message does not contain last 8 columns (That means each record is containing only 42 columns).
    Please help.
    Thanks
    SKM

    Hi SKM
    Go through this blog on sending fixed length flat file
    <b>/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    and
    >><i>lastFieldsOptional=YES then the message does not contain last 8 columns</i>
    <b>lastFieldOptioanl parameter specifies whether the last fields can be omitted (YES) or not (NO) in a CSV structure. If you do not make a specification, the default value is NO</b>.
    So i think u should use <b>NO</b> in this parameter.
    Hope it helps.
    Regards
    Arpit Seth

  • File content conversion without field separator

    Hi experts,
    in my scenario I'm sending a txt file to an external receiver.
    Each field of the file must be separated from the others with differents field separators according with the requirement of the receiver, for example:
    field1;field2:field3, field4; ecc....
    For this reason I've created in the source message many "FieldSeparator" fields. These fields will be populated by ABAP program.
    I thought that it was possible to omit parameter fieldSeparator in content conversion, but testing the interface I receive an error because fieldSeparator is missing.
    Is possible to omit fieldSeparator or to specify a fieldSeparator null?
    The fields in the target file must be of variable lenght, so I cannot use FieldFixedLenght.
    The only solution I found is to create in the target message structure a single string with each field concatenated, is the only possible solution?
    Thanks
    Fabio Boni
    Edited by: Fabio Boni on Oct 21, 2010 5:47 PM

    Sorry...posting error earlier..
    The seperator can be concatenated at the end of each field in mapping.So seperator will be part of field value.
    But with receiver FCC, you need to either mentione fieldfixedlenght or fieldseperator.Please check if space is going to to work for you as separator.
    Edited by: nagarjuna _s on Oct 21, 2010 6:36 PM

  • Flat file content conversion repeating fields

    Hello,
       I have a flat file where the first three fields are fixed; the rest of the file line is made up of 1 .. n analysis characteristic results. The name of the field (Result) is always the same, but I never know how many results I will have on one line. Could anyone tell me how I might define this in content conversion ? Thanks in advance.
    Peter DOUGHERTY.

    Sorry,
       Of course ... here it is
    10059514     22/09/08 8:29:02     20,2     0     0     0     0,30     0     133     0     0     0     0     0     0     0     0     0     0     0     
    The first field is the Id of the sample
    Second field Date
    Third field Time
    The 4th ... 21st fields a (varying) number of results (here there are 18, but there could be any number from 1 upwards)
    Hope it is clearer
    Thanks
    Peter

  • File content conversion: Target Field is optional

    I am using FCC in receiver file adapter.
    My file is getting generated.
    In target structure one field is optional and hence target xml element doesnt have value. hence that field is not there in txt file. with this what happens next subsequent field gets shifted to my optional field place and then i get error field length is not correct.
    I want to put 2 spaces if that optional field length is 2 char and then there should be field separator(space) and the subsequent column.
    I am already giving fixedfieldlegnth of all the fields.
    Pl can anyone suggest how to do this.
    thanks,
    sharada

    Hi Sharada,
    Do your normal mapping to the target field that is optional.
    Use a If function before mapping the field.
    Check if the node is created in usual mapping, else map a constant with 2 spaces.
    DO something like this:
    Mapping ---------------->
                               equalsS ----> if
    constant(empty Value)--->
                      constant(2 spaces)--> then -> tgtField
                       Mapping -----------> else   
    regards,
    P.Venkat

  • Skip field in file content conversion (file adapter)

    hy guys,
    I have a log file and want to convert it into xml. that works fine.
    the problem is: can I skip some fields that I do not need in the xml with file content conversion
    the fields I want to skip are the same in every record of the log file.
    thanks.

    Ralf,
    You can only ignore lines in the begiining of the file using Document Offset option.
    If you have the unwanted field in the end of the record and you are in SPS12 (PI 7.0), you can use the option additionalLasstFields in FCC parameters. have a look into the blog /people/sukumar.natarajan/blog/2007/06/12/content-conversion-in-sender-file-adapter--2-new-useful-parameters
    Easier, is to ignore those fields in mapping.
    Also, you can try to remove those fields using a shell script which can be called from the File adapter.
    Regards,
    Jai Shankar

  • File Content Conversion - Error in keyfield Value

    Hello experts,
    I am doing file content conversion for a file to file scenario. The input file is a csv file which is converted to xml using the file content conversion. The key field of input file is used for implementing conversion.
    While testing the FCC, I noticed that if the keyfield value is wrong for a record in the file, the record is ignored altogether without throwing any errors or warnings. Is there any way to notify if any records have been ignored as a result of incorrect keyfield value??
    Thanks in advance!
    RR

    There seems to be NO way to handle it in FCC.
    File Content Conversion - Key Field Value
    u can think of work arounds by handling it in mapping....
    -santosh.

  • 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

  • Problem with File content conversion and parameters

    Hi experts,
       What is the use of file content conversion that is available in file adapter? For what cases we can use it?
      What do the different content conversion parameters mean?
    Kindly help
    Thanks
    Gopal

    Hi,
    We use the file content convertion to conver the flat file that is text file into XML,
    File adapter cant understand the format the file is,so we have to declare the content convertion parameters.
    Check some links which will tell how the convertion is done.
    /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/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
    /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/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/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Regards,
    Phani
    Reward points if helpful

  • FILE CONTENT CONVERSION   PARAMETERS

    HI
       my source file is text format.. and  source struture is contain only two fields.. but the  data was getting from source  is  large string..  like in the  bellow format i'm getting the  source files..
    <b>FI 6E151/AN VT-IND
    DT BKK MAA 250445 M14A
    -  1001 OUTRP  0151/25 VOBG/VOCI .VT-IND</b>
    like this three  lines i'm getting for 2 fields.. i want to send  entire the first line to first field. and    the next two lines  i want to send to  next field..( the 2nd  and 3 rd  lines data both i want to send into a particular  field  only..
    so, in file content conversion what are the paramenters i need to pass.. plz suggest me..
    but if i use as normal parametrs   the first line was not going  completely to the  first field of the source
    insted of that where ever i'm getting space in the  first line..  from that  it was  going to second field  but the remaning 2 lines data it was not going to any fields...
    thanks
    babu

    hi babu,
    File Content Parameters
    Under Content Converstion Parameter:
    DocumentName: Here give your OutBound MessageType name
    Cocument NameSapace: give your namesapace
    RecordsetName: Recordset
    RecordsetStructure: Records1,*
    Records1.fieldNames:Field1,Field2,Field3
    Records1.endSeparator 'nl'
    regards
    Ramesh P
    Message was edited by:
            Ramesh P

  • Key field values for file content conversion at sender communicationchannel

    Hi all,
    I am working on  scenario File to Idoc.In this scenario at the sender side we configure the file content conversion for .CSV file.
    In the flat file i am having more than one orders, XI will pick the file and creates a separate Idoc for each sales order at r/3.
    We have similar fields "Order Item Number" both header and item.
    If we got '00000' on the Header item then it should create a new idoc at the r/3 side other wise it will create line item.
    Order item number will be 00000 for header but it will differ from order item to item.
    source structure
    Order Header
    Order type
    Sold-to-code
    PO number
    Order item number
    Order date
    AdresName1
    AdresName2
    Street and House number
    Postal Code
    City
    Country Code
    Filler
    Order Item
    Order type
    Sold-to-code
    PO  number
    Order item number
    Order date
    Product code
    Order quantity
    Item text
    Filler
    Now I have some questions....
    I don't have standard filed values to give the key fileds at source structure.
    I need to create the Idoc at r/3 system for each individual record.
    Is it possible to create new idoc with out using the Key filed value?
    If it is possible then how can i proceed with fcc?
    please give me your valuable suggestions
    Best Regards,
    satya
    Edited by: satyatanuku on Mar 3, 2010 1:41 PM
    Edited by: satyatanuku on Mar 3, 2010 1:42 PM
    Edited by: satyatanuku on Mar 3, 2010 1:44 PM

    Hi,
    Just check the Content Conversion Parameters-  Recordset Structure.
    If you have filled in this parameter with
    Header,1,Item,1
    then change it to
    Header,1,Item,3
    Regards
    Chandra

  • Upload flat file (Content Conversion Parameters)

    Hello,
    I am still trying to upload a flat text file to XI. Its a non separator file.
    Here the error message from the XI adaper engine:
    Sender Adapter v1508 for Party '', Service 'IXI_FileSystem_CSV':
    Configured at 15:36:12 2005-08-03
    Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: <b>
    Mandatory parameter 'CONTROL.keyFieldValue': no value found</b>
    Here all my settings:
    Message protocol: File Content Conversion
    Document name: CMA_FILEINPUT1
    Document namespace: http://www.xyz/ogsd
    Recordset name: RECORD
    Recordset structure: CONTROL,1,SEGMENT,*
    <b>Key Field Name: SEGMENT.DUMMYKEY</b>
    Key Field Type: String (cs) -> default
    Fields:
    CONTROL.fieldNames:TABNAM,MANDT,DOCNUM,DOCREL,....
    CONTROL.fieldFixedLengths:10,3,16,4,2,1,1,...
    SEGMENT.fieldNames:DUMMYKEY,DUMMY,LOCATIONID,...
    SEGMENT.fieldFixedLengths:12,51,10,18,4,10,
    SEGMENT.keyFieldValue:E2BPBULOCM03 (string that occurs in the first field DUMMYKEY of SEGMENT)
    The message type looks like this:
    CMA_MSGTYP1                1:1
      RECORD                   1:1
        CONTROL                1:1
          TABNAM
          MANDT...
        SEGMENT                0:unbounded
          DUMMYKEY
          DUMMY
          LOCATIONID...
    Why do i get that error message? How to fill Key field name correctly? In my opinion i dont need key fields for CONTROL because of the occurence of one.
    Any idea?

    Thanks to all. So "Key Field Name" is just symbolic?
    Here are my new settings:
    Message protocol: File Content Conversion
    Document name: CMA_FILEINPUT1
    Document namespace: http://www.xyz.de/ogsd
    Recordset name: RECORD
    Recordset structure: CONTROL,1,SEGMENT,*
    <b>Key Field Name: KF</b>
    Key Field Type: String (cs) -> default
    Fields:
    CONTROL.fieldNames:TABNAM,MANDT,DOCNUM,DOCREL,....
    CONTROL.fieldFixedLengths:10,3,16,4,2,1,1,...
    SEGMENT.fieldNames:DUMMYKEY,DUMMY,LOCATIONID,...
    SEGMENT.fieldFixedLengths:12,51,10,18,4,10,
    <b>SEGMENT.keyFieldValue:E2BPBULOCM03 (from DUMMYKEY)
    CONTROL.keyFieldValue: HRETZU (from TABNAM) </b>
    Both key fields are the first entries in the substructures.
    Now this error is coming up:
    Sender Adapter v1508 for Party '', Service 'IXI_FileSystem_CSV':
    Configured at 16:41:24 2005-08-03
    Last message processing started 16:41:24 2005-08-03, Error: Conversion of complete file content to XML format failed around position 0 with java.lang.Exception: ERROR converting document line no. 2 according to structure 'SEGMENT':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
    last retry interval started 16:41:24 2005-08-03
    length 30,000 secs
    What is that for a new parameter(lastFieldsOptional)?

Maybe you are looking for