FCC undefined structure

Hi all,
I am doing FCC to FCC scenario.
My message is picking up from source...and in moni it is showing inbound message. But while giving output it is showing structure is not correct...
My input is as follows......
3936A20070501122019393600INOAC  
3936D.................
3936Z.....................
Sender parameters are as follows :::::::
Header.fieldFixedLengths     4,1,8,6,6,6,369
Header.fieldNames     InformationTypeCode,RecordTypeCode,.....
Header.keyFieldValue       A
Header.endSeparator     'nl'
Items.fieldNames     InformationTypeCode,RecordTypeCode,.....
Items.fieldFixedLengths     4,1,8,6,7,.................
Items.keyFieldValue     D
Items.endSeparator     'nl'
Tail.fieldNames     InformationTypeCode,RecordTypeCode............
Tail.fieldFixedLengths     4,1,8,6,7,11,363
Tail.keyFieldValue     Z
ignoreRecordsetName     true
Tail.endSeparator       'nl'        
can any one help me???????

Hi,
Make following changes
  recordsetstructure ->  Header,,Items,,Tail,*
Header.fieldFixedLengths->4,1,8,6,6,6,369
Header.fieldNames-> KZ,InformationTypeCode,RecordTypeCode,.....
Header.keyFieldValue 1
Header.keyFieldlnStructure->ignore
Header.endSeparator 'nl'
Items.fieldNames->KZ,InformationTypeCode,RecordTypeCode,.....
Items.fieldFixedLengths-> 4,1,8,6,7,.................
Items.keyFieldValue->2
Items.endSeparator ->'nl'
Items.keyFieldlnStructure->ignore
Tail.fieldNames->KZ, InformationTypeCode,RecordTypeCode............
Tail.fieldFixedLengths 4,1,8,6,7,11,363
Tail.keyFieldValue->3
Tail.keyFieldlnStructure->ignore
Tail.endSeparator 'nl'
   Here KZ  is key field. Also check character after dot should be small letter.
like.  ( Items.keyFieldValue)
Regards,
S.RamNarender

Similar Messages

  • Generic function displaying alv grid for undefined structure

    Hi experts,
    I'm doing my first steps on abap development (Totally noob).
    I'm writing some little reports based on simple selections (1 or 2 tables).
    In every report, I've defined a structure (internal table) that i'm displaying with an ALV Grid.
    In every report, I need to create a catalog for my structure in order to make the alv grid working.
    What I would like to do is :
    Create a function that receives a undefined structure (for all my reports) as a parameter.
    This function sould create the catalog for the coresponding structure and call the alv grid function to display the data's contained in this structure.
    The goal is : In every report, I would like to use this function to show the selected data's without taking care of catalogs, alv grid, etc...
    Is it possible ?
    I really don't see how I can do that... Does anybody already tried something like that ?
    Thank you for your help
    Regards
    Quentin

    Hi,
    In this method Pass the structure name-
    CALL METHOD gh_grid->set_table_for_first_display
    EXPORTING
    I_BUFFER_ACTIVE =
    I_BYPASSING_BUFFER =
    I_CONSISTENCY_CHECK =
    I_STRUCTURE_NAME = "<- here pass the structure
    IS_VARIANT =
    I_SAVE =
    I_DEFAULT = 'X'
    IS_LAYOUT = "<-Layout variable if using layout
    IS_PRINT =
    IT_SPECIAL_GROUPS =
    IT_TOOLBAR_EXCLUDING =
    IT_HYPERLINK =
    IT_ALV_GRAPHICS =
    IT_EXCEPT_QINFO =
    CHANGING
    it_outtab = gt_line[]
    it_fieldcatalog = gt_fieldcat
    IT_SORT =
    IT_FILTER =
    EXCEPTIONS
    invalid_parameter_combination = 1
    program_error = 2
    too_many_lines = 3
    OTHERS = 4

  • Error in Receiver FCC: Unknown structure ... found in document

    Hi Experts,
    I have a problem with the Receiver File Adapter. I want to use Content Conversion to generate a plain file.
    Input to receiver file adapter:
    <?xml version="1.0" encoding="utf-8" ?>
    <PlainFile>
      <filename>filename.txt</filename>
      <line>Line 1</line>
      <line>Line 2</line>
    </PlainFile>
    Wanted result: a file filename.txt with this content:
    Line 1
    Line 2
    FCC settings:
    RecordSet Structure: line, filename
    line.fieldSeparator:'nl'
    filename.fieldFixedLengths:0
    filename.fixedLengthTooShortHandling:Cut
    Problem is: the adapter throws error "Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'PlainFile' found in document'"
    If I use:
    RecordSet Structure: PlainFile, line, filename
    and add:
    PlainFile.fieldSeparator:'nl'
    ... the lines are printed, but also the unwanted filename. The XML input results from an 1:n mapping, therefore I want to set different filenames by variable substitution from the payload.
    Many thanks for your help,
    Ralf

    Since you want to the filename to be sent in the payload, check out the below Variable Substitution Method. This information is available in help.sap.com.
    Advanced Tab Page
    Variable Substitution (Target Directory/File Name Scheme)
    If you set the Enable indicator, you can enter variables for the Target Directory and File Name Scheme. Enter the names of the variables and references in the table.
    &#9679;      Enter each variable that you reference in the Target Directory and File Name Scheme fields without the surrounding percentage sign under Name of Variables in the table.
    The variables can refer to attributes of the message header or elements of the message payload.
    &#9675;       If the variables are to refer to an attribute of the message header, add the prefix message: to the name of the variable under Reference. You can specify the following attributes of the message header:
    sender_party, sender_service, receiver_party, receiver_service, interface_name, interface_namespace,
    message_id (message ID with hyphens, for example 9fbe1ff1-9a0d-11d9-8665-cbf10a126331)
    message_id_hex (message ID in hexadecimal format, for example 9fbe1ff19a0d11d98665cbf10a126331)
    For example, if you want to specify the interface name from the message header in the target directory or in the file name scheme, enter message:interface_name as the reference.
    Note
    If one of the message attributes contains characters that are not permitted in a file name, for example \, /, :, *, ?, ", <, >, |, then these characters are replaced by an underscore ("_").
    &#9675;       If the variable refers to an element in XML schema, add the prefix payload: to the information under Reference. The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
    namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
    The description begins at the root of the document and ends at the respective element.
    Example
    To reference the element that is in bold in the example, the following expression is used: payload:root,1,e1,1,e2,2
    The parser searches for the first occurrence of the root element at the first level. It then searches for the first occurrence of e1 at the second level and for the second occurrence of e2 at the third level. The content of the last element (“Example Value”) is set as the value for a specified variable.
    <?xml version="1.0" encoding="UTF-8" ?>
    <root>
      <dummy>
         <e1>
            <e2>Data_1</e2>
            <f/>
            <g attr="abc">text</g>
            <e2>Data_2</e2>
         </e1>
      </dummy>
      <e1>
         <e2>illegal/value</e2>
         <f/>
         <g attr="abc">text</g>
         <e2 attr="fghij">Example Value</e2>
      </e1>
    </root>

  • Reg:working without Keyfield in FCC node structures

    Hi All,
    I have a scenerio of FCC to RFC , where i need to read a Text file and want to post it to R/3 through RFC
    Recordset Structure : Header,1,Item,*,Trailer,1
    Is it possible to read the file without Keyfield vale ?
    Please give your valuable suggestions.
    Thanks & Regards,
    S.K.Karthikeyan.

    Thanks for the inputs folks....
    According to our requirement, we have different no. of line items for each node viz. Header, Item and Trailer out of which Item occurs n number of times.
    In this case, we have done the FCC using a keyField value itself.
    Cheers,
    Karthi

  • FCC  Recordset structure question.

    Hi,
    I have completed the config for scenarion File>XI>IDOC(R/3)
    After activating the File comm channel, the message coming out of XI (in sxmb_moni) has the following error
    'Parsing an empty source. Root element expected'
    I want to know:
    1> Does the Recordset-structure field names (defined in .fieldNames) need to match exactly with the Data_type structure defined in IR. Currently my Data_type in IR does not have a key field, which I have introduced in the FCC keyField parameter.
    2>I have generated all my ID config by importing 'Integration Scenario' from IR and this has resulted in Automatic Creation of HTTP, RFC, IDOC,XI Receiver channels. ( GeneratedReceiverChannel_HTTP, GeneratedReceiverChannel_RFC, GeneratedReceiverChannel_IDOC, GeneratedReceiverChannel_XI ). Do I require all of these to be active?
    Thanks and Regards
    Shirin

    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.
    cheers

  • Unknown structure 'ns0:MT_dbglgtr_FileName' found in document'

    I have other problem.
    The receiver channel communication gives the next error:
    Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:MT_dbglgtr_FileName' found in document', probably configuration error in file adapter (XML parser error)'.
    I haven't empty node and any condition.
    Thank you.

    Hi,
    Same problem solved here: (infact many threads with the same problem and solution)
    Error in Receiver FCC: Unknown structure ... found in document
    Re: Receiver File content conversion - NO Output
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Apr 14, 2009 7:42 PM

  • RFC 2 FLAT "Conversion configuration error: Unknown structure" MessageTrans

    Hello all,
    I want to use MessageTransformBean to map an RFC Call to a FlatFile in Receiver Adapter. As it is not FTP I can't use FCC.
    Everytime I start the processing I get the error:
    com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Z_FUNCTION' found in document', probably configuration error in file adapter (XML parser error)''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Z_FUNCTION' found in document', probably configuration error in file adapter (XML parser error)'
    I implemented everything according to [this|http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm] guide (complex conversion for receiver cc).
    I also tried to map the RFC to another XML structure, but the error was the same?
    Any ideas?
    Best regards,
    David

    You can probably find answers in these threads:
    Error in Receiver FCC: Unknown structure ... found in document
    Unknown structure 'ns0:MT_dbglgtr_FileName' found in document'
    Error in reciever file content conversion
    Regards,
    Ravi

  • Idoc to flatfile FCC issue

    Hello everybody,
    i am implementing an idoc-flatfile scenario (PI 7.1). It works to write an xml file into directory, as soon as I use FCC in order to generate txt-file, no file is written, and sxmb_moni shows an acknowledgement with system error. In both cases sxmb_moni shows the following acknowledgement:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Technisches Routing der Antwort
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
      <SAP:P1>,ZZ_CC_IBDLV</SAP:P1>
      <SAP:P2>,ZZ_CC_IBDLV,,</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Es konnte keine Empfängervereinbarung für den Sender ,ZZ_CC_IBDLV zum Empfänger ,ZZ_CC_IBDLV,, gefunden werden.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Inbound = idoc SHP_OBDLV_SAFE_REPLICA
    message type for outbound:
    ZZ_DT_OBDL     Complex Type          
    header     Element          1
    -test1     Element     xsd:string     1
    -test2     Element     xsd:string     1
    item     Element          0..unbounded
    -itemtest     Element     xsd:string     1
    -itemtest2     Element     xsd:string     1
    FCC:
    Recordset structure:                header,item,*
    header.addHeaderLine          1
    header.fieldNames               test1,test2
    header.fieldSeperator               ,
    header.processConfiguration          FromConfiguration
    header.endSeperator               'nl'
    item.addHeaderLine               1
    item.fieldNames               itemtest,itemtest2
    item.fieldSeperator               ,
    item.processConfiguration          FromConfiguration
    item.endSeperator               'nl'
    I also tried StrictXml2PlainBeanu2026 doesnu2019t work eitheru2026 thanks in advance,
    Lukas

    It works to write an xml file into directory, as soon as I use FCC in order to generate txt-file, no file is written
    --->
    use
    Recordset structure: header,item
    In receiver FCC, do not specify occurrences in recordset structure
    Also fieldNames parameter is also not required.
    RWB--> Message Monitoring, select Details of your message, you will find FCC errors here

  • Help with FCC on receiver side

    Hey guys
    i have an XML structure on the receiver side as follows
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Invoices xmlns:ns0="urn:NOVInvoiceToSCO">
       <Invoice>
          <InvoiceProperties>
             <InvoiceNumber>sdds</InvoiceNumber>
             <InvoiceDate>dsd</InvoiceDate>
             <VendorNumber>dsd</VendorNumber>
             <InvoiceTypeCode>rer</InvoiceTypeCode>
             <PrimaryCurrency>
                <CurrencyCode>dd</CurrencyCode>
                <ExchangeRate>dsd</ExchangeRate>
             </PrimaryCurrency>
             <PaymentTerms>sd</PaymentTerms>
          </InvoiceProperties>
          <InvoiceDetails>
             <InvoiceLineItem>
                <WorkOrdernumber>dsd</WorkOrdernumber>
                <LineItemNumber>dsd</LineItemNumber>
                <InvoiceQuantity>
                   <Quantity>ds</Quantity>
                   <UnitOfMeasureCode>ds</UnitOfMeasureCode>
                </InvoiceQuantity>
                <LineItemInformation>
                   <LineItemMaterialNumber>sds</LineItemMaterialNumber>
                   <LineItemDescription>dsd</LineItemDescription>
                </LineItemInformation>
                <Pricing>
                   <UnitPrice>
                      <MonetaryAmount>dsd</MonetaryAmount>
                      <UnitOfMeasureCode>dsd</UnitOfMeasureCode>
                      <CurrencyCode>sds</CurrencyCode>
                   </UnitPrice>
                </Pricing>
                <LineItemtotal>
                   <MonetaryAmount>sd</MonetaryAmount>
                   <CurrencyCode>ds</CurrencyCode>
                </LineItemtotal>
                <Requisition>
                   <Number>ds</Number>
                   <LineItemNumber>ds</LineItemNumber>
                </Requisition>
                <Status>sd</Status>
             </InvoiceLineItem>
          </InvoiceDetails>
          <InvoiceSummary>
             <TotalLineItems>ds</TotalLineItems>
             <InvoiceTotal>
                <MonetaryAmount>ds</MonetaryAmount>
                <CurrencyCode>ds</CurrencyCode>
             </InvoiceTotal>
             <Tax>
                <TaxTypeCode>sd</TaxTypeCode>
                <TaxAmount>
                   <MonetaryAmount>ds</MonetaryAmount>
                   <CurrencyCode>s</CurrencyCode>
                </TaxAmount>
                <TaxReference>ds</TaxReference>
             </Tax>
          </InvoiceSummary>
       </Invoice>
    </ns0:MT_Invoices>
    <InvoiceProperties> is the header
    <InvoiceDetails>is the data
    <InvoiceSummary>is the trailer
    i am using the following on the receiver side under FCC
    Recordset Structure: Invoices,Invoice,InvoiceProperties,PrimaryCurrency,InvoiceDetails,InvoiceLineItem,InvoiceQuantity,LIneItemInformation,Pricing,UnitPrice,LineItemTotal,Requisition,InvoiceSummary,InvoiceTotal,Tax,TaxAmount
    Invoices.fieldSeparator     'nl'
    Invoice.fieldSeparator     ,
    Invoice.endSeparator     'nl'
    InvoiceProperties.fieldSeparator     ,
    InvoiceProperties.endSeparator     'nl'
    PrimaryCurrency.fieldSeparator     ,
    PrimaryCurrency.endSeparator     ,
    InvoiceDetails.fieldSeparator     ,
    InvoiceDetails.endSeparator     'nl'
    InvoiceLineItem.fieldSeparator     ,
    InvoiceLineItem.endSeparator     'nl'
    InvoiceQuantity.fieldSeparator     ,
    InvoiceQuantity.endSeparator     ,
    LineItemInformation.fieldSeparator     ,
    LineItemInformation.endSeparator     ,
    Pricing.fieldSeparator     ,
    Pricing.endSeparator     ,
    UnitPrice.fieldSeparator     ,
    UnitPrice.endSeparator     ,
    LineItemTotal.fieldSeparator     ,
    LIneItemTotal.endSeparator     ,
    Requisition.fieldSeparator     ,
    Requisition.endSeparator     ,
    InvoiceSummary.fieldSeparator     ,
    InvoiceSummary.endSeparator     'nl'
    InvoiceTotal.fieldSeparator     ,
    InvoiceTotal.endSeparator     ,
    Tax.FieldSeparator     ,
    Tax.endSeparator     ,
    TaxAmount.fieldSeparator     ,
    TaxAmount.endSeparator     ,
    Now i want the output of the following form
    Header
    Data
    Trailer
    Note:Data has occurence 0--* and both header and trailer have occurence 1
    i m unable to get the CSV file on the receiver side,can anbody cross check my parameters and lemme know whr i m wrong?
    thanx
    ahmad

    Hi Ahmad,
    give recordsetstructure : InvoiceProperties,1,InvoiceDetails,*,InvoiceSummary,1
    and in key-value pair give:
    InvoiceProperties.fieldFixedLengths : length of fields of InvoiceNumber,InvoiceDate..etc similarly for InvoiceDetails and InvoiceSummary
    InvoiceProperties.fieldSeparator , similarly for InvoiceDetails and InvoiceSummary
    Then you will get your req CSV file.
    Thanks,
    Rajeev Gupta

  • Error in Receiver File adapter using File content Conversion

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

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

  • 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

  • To CSV conversion problem

    hi all,
    could you fix this problem in the File Adapter :-
    Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
    while trying to write XML to a CSV file.
    i've configured the FCC as:
    Structure = structs ( with 6 columns)
    struct.fieldFixedLengths 20,10,10,10,10,10
    struct.fieldSeparator ,
    struct.endSeparator 'nl'
      thanks in advance
    nikhil
    null

    I think the problem is a spelling error: you named your structure "structs" and then you refer to it as "struct".
    You have to choose one between the two (or a better one if you can find it).
    About File content conversion I suggest you to see the following links:
    Content Conversion (Pattern/Random content in input file)
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    File Content Conversion for Unequal Number of Columns
    /people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
    How to send a flat file with fixed lengths to XI 3.0 using a Central 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
    Content Conversion ( The Key Field Problem )
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    Solution to the problem encountered using Variable Substitution with XI-SP12
    /people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
    I hope this will be helpfull.
    Regards,
    Salvatore

  • Getting Problem in Flat File to IDoc Scenario.

    Hi,
    I am facing problem which is as follows.
    Test Flat File Contain Data As Follow
    Field1,Field2,Field3
    Field4,Field5,Field6
    Field1,Field2,Field3
    Field4,Field5,Field6
    Field1,Field2,Field3
    Field4,Field5,Field6
    Source structure has only one segment with all six fields and is repeating.
    What will be the file content conversion parameters so that it will pick first 2 lines and convert it into segment in this away.(I cant create two segments)
    Thanks in advance.

    Hi,
    I agree with Vijay.. so try to create the Data type like this..
    Recoredset 0...1
    -----Line1 0.... unbound
    --------Field1 0...1
    --------Field2 0...1
    --------Field3 0...1
    -----Line2 0.... unbound
    --------Field4 0...1
    --------Field5 0...1
    --------Field6 0...1
    Now do your FCC
    Recordset Structure ---- Line1,*,Line2,*
    Recordset per Message ---- 1
    Line1.fieldNames ----- Field1,Field2,Field3
    Line1.fieldSeparator ---- ,
    Line1.endSeparator ----- 'nl'
    Line2.fieldNames ----- Field4,Field5,Field6
    Line2.fieldSeparator ---- ,
    Line2.endSeparator ----- 'nl'
    now map the fields as per your requirement.
    Regards,
    Sarvesh

  • BootCKCL.etl files and CompCS events

    I have been trying to parse the BootCKCL.etl file with the event tracing apis to track cpu utilization of processes over start-up. However when i do this i do not get any thread switch events. I do get a bunch of CompCS events that have an undefined structure.
    When i export this file with xperf i get a bunch of CSwitchedCached events witch contain the thread switching information i need. So my question is how is these CSwitchedCached events related to the CompCS events and are these data structures documented anywhere?
    Thanks for any help,

    As far as I know, there is no publishing utility tool in Internet to view the ETL logs. If you want to find the root according to the ETL logs, you'd better create a Microsoft support ticket to get more help.
    Of course you can post the ETL content here and other partners who read the forums regularly can either share their knowledge with you. Please do remember that hide the sensitive/privacy information when you post the log.
    Feel free to post back. Thanks.
    Tony Chen
    TechNet Community Support
    A new Office has arrived, try it now.
    A beautiful Start. It begins here. Windows 8 and Windows RT.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • Event Tracing Events (BootCKCL.etl files and CompCS events)

    
    Not sure if this would be considered the correct place to post this request, however if anyone has any insight into this issue it would probably be someone who has experience with Kernel level event tracing and its data structures.
    I have been trying to parse the BootCKCL.etl file with the event tracing apis to track cpu utilization of processes over start-up. However when i do this i do not get any thread switch events. I do get a bunch of CompCS events that have an undefined structure.
    When i export this file with xperf i get a bunch of CSwitchedCached events witch contain the thread switching information i need. So my question is how is these CSwitchedCached events related to the CompCS events and are these data structures documented anywhere?
    Thanks for any help,

    Yes.  Create a smart album with the criteria Photo is RAW:
    Then you can select all of the photos in the smart album and use the Events ➙ Create Event menu option to move all of the RAW photos into a new event.
    OT

Maybe you are looking for