Error in FCC

Hey guys
i m doing a very simple File content conversion scenario and getting this error when i test the mappin using the payload generated in SXMB_MONI.
    Cannot produce target element /ns:MT_FILEOUTPUT/Record/Row. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
where might the problem be?
thanx
ahmad

hey
tha payload i m getting in moni is
<?xml version="1.0" encoding="utf-8"?>
<ns:FILEINPUT xmlns:ns="http://Thoughtbyte.com">
<Record>
     <Row>
          <Name>Mark</Name>
          <Address>sue</Address>
     </Row>
</Record>
</ns:FILEINPUT>
and the one i m getting in Message mappin is
<?xml version="1.0" encoding="UTF-8"?>
<ns:MT_FILEINPUT xmlns:ns="http://Thoughtbyte.com">
  <Record>
    <Row>
      <Name>Mark</Name>
      <Address>Sue</Address>
    </Row>
  </Record>
</ns:MT_FILEINPUT>
The second line of these XML are different ,in MONI i m gettin <ns:FILEINPUT xmlns:ns="http://Thoughtbyte.com"> where as in mapping i m gettin  <ns:MT_FILEINPUT xmlns:ns="http://Thoughtbyte.com">
one thing which i noticed is that if i copy the payload from moni and jst change the second line as per the payload of message mappin,it works fine(i.e just change <ns:FILEINPUT xmlns:.....> with <ns:MT_FILEINPUT xmlns:....> )
MT is my message types and FILEINPUT is my data type.
hope this makes it more clear
thanx
ahmad

Similar Messages

  • Error in FCC in sender JMS adapter

    Dear all,
    We have IDoc flat file which is fixed field length but it has no field separators. It also doesnt have a carriage return(enter) after every segment ( say edi_dc40).
    In this case ,the FCC is giving error  " Missing Structure in Last recordset ".
    But if we try adding a CARRIAGE RETURN ( ENTER ) after every segment 
    the fcc is working.
    Regards,
    Madhu

    Hi !  Madhu
    take some idea from this
    http://help.sap.com/saphelp_nw70/helpdata/en/0d/00453c91f37151e10000000a11402f/frameset.htm
    <b>Converting File Content in a Sender Adapter</b>
    http://help.sap.com/saphelp_nw70/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    Thanks !!
    Regards
    Abhishek Agrahari

  • Error in fcc to db scenario

    hi experts.
    i got  a problem in fcc to db scenario.
    everything is working.
    in the runtime workbench also no error regarding adapter monitoring.
    still it could not pick up the file from input directory.
    why this is happened and where it went wrong.

    Hi,
    >>in the runtime workbench also no error regarding adapter monitoring.
    still it could not pick up the file from input directory.
    You have to to do Monitoring in Communication Channel Monitoring not in Adapter monitorin!!!!
    Click on RWBCompo MoniAdapter Engine--CC Monitoring
    Just select your CC from the list and say Filter, now you will be able to see the Messge
    Regards
    Seshagiri

  • Error in FCC-Sender Channel.

    Hi Experts,
    I have configured the following FCC in Sender communication Channel.
    DT_HEADER.keyFieldValue     =1
    DT_HEADER.fieldNames =     KEY,FILENAME
    DT_RECORDS.keyFieldValue=     2
    DT_HEADER.fieldNames=     KEY,AMOUNT
    DT_TRAILER.keyFieldValue     =3
    DT_TRAILER.fieldNames=     KEY,SUM
    DT_HEADER.fieldSeparator =     ,
    DT_RECORDS.fieldSeparator=     ,
    DT_TRAILER.fieldSeparator =     ,
    DT_TRAILER.endSeparator =     'nl'
    DT_RECORDS.endSeparator=     'nl'
    DT_HEADER.endSeparator =     'nl'
    My sender text file is
    1,RDFILE
    2,100
    3,100
    In RWB i am getting the following error message,
    Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'DT_HEADER.fieldFixedLengths' or 'DT_HEADER.fieldSeparator' is missing Consistency check: no. of arguments in 'DT_HEADER.fieldFixedLength' does not match 'DT_HEADER.fieldNames' (0 <> 2)
    i need to get  Sender XML structure as follows
    <DT_HEADER>
          <KEY/>
          <FILENAME/>
       </DT_HEADER>
       <DT_RECORDS>
          <KEY/>
          <AMOUNT/>
       </DT_RECORDS>
       <DT_TALER>
          <KEY/>
          <SUM/>
       </DT_TALER>
    i dont know where i did the mistake can any one help me to solve this issue.
    Regard's
    Preethi.

    Hi
    You need alter Data type structure first then do file content conversion
    DT_Record
        <Header>
              <Key>
              <FileName>
       </Header>
       <Trailer>
    </trailer?
    then add
    HEADER.keyFieldValue =1
    HEADER.fieldNames = KEY,FILENAME
    RECORDS.keyFieldValue= 2
    It works
    Regards,
    Raj

  • Mapping error in FCC to XML conversion

    hiii friends,
    im donig a simple fcc to xml conversion
    my Sender msg type is like
    TXT_mt
          records                             1.1   
                row                             1.n
                    id                             1
                    Name                       1
                    address                   1
    My receiver msg type like
    Xml_mt
          records                             1.1   
                row                             1.n
                    id                             1
                    Name                       1
                    address                   1
    msg mapping like
    records--->records
    id--->id
    Name-->Name
    address-->address
    **Im getting a mapping error like**
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_pepsi_fcc_file_mm_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>During the application mapping com/sap/xi/tf/_pepsi_fcc_file_mm_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I ve checked my adapeters they r green.
    Could u tell me the problem here and how to solve it???
    Regards
    Balaji

    Hii Volker,
    I have tried to understand the trace msg,. i got one interesting error message i hope it will tell the exact problem im facing,,,
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_pepsi_fcc_file_mm_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns:xml_mt/record/row. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram
    My Sender CC  contains the following FCC parameters
    Document Name -
    > txt_mt
    Recordset Name -
    > records
    recordset Structure -
    >  row, *
    row.fieldNames -
    > id, Names,address
    row.fieldSeparator -
    > , (comma)
    row.endSeparator--- >  'nl'
    row.processConfiguration  -
    > FromConfiguration
    my TXT_in.txt contain
    100,balaji,chennai
    200,raj,orissa
    300,charakrat,bangalore
    Regards,
    Balaji
    Edited by: Balaji Pichaimuthu on Jul 1, 2009 3:44 PM

  • Parsing an empty source. Root element expected! error in fcc using MTB

    Hi experts,
    While converting a flat file to xml using MTB , i'm facing this error in mapping.
    " com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping  .....
    Parsing an empty source. Root element expected!   "
    Whereas the audit log in file channel - Communication channel monitoring shows that , the payload transformed but i'm unable to view the source message.
    Please let me know the resolution if anyone has faced the same issue..
    thanks,
    younus

    hi,
    you want to convert yor receivee structure or sender??
    see these links about FCC to see how they do it.
    File Receiver with Content Conversion
    /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/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
    Type of separatos
    http://help.sap.com/saphelp_nw04/helpdata/en/05/7fdf3d0eb8af5ee10000000a114084/frameset.htm
    Troubleshooting the File Adapter
    /people/shabarish.vijayakumar/blog/2007/07/26/troubleshooting-the-file-adapter-last-updated-on-02-july10
    Converting File Content in a Sender Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    Converting File Content in the Receiver Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
    Thanks
    Rodrigo
    PD: Reward points if useful
    Edited by: Rodrigo Pertierra on May 14, 2008 12:11 PM

  • Error in Receiver File adapter - FCC

    Got error message as "File Adapter Receiver Channel CC_OB_REQ: Not initialized - cannot proceed: null"
    My requirement is to send IDOC to file which consists of 4 fields, My target message interface is
    MT_REQ
      FILE_STRUC
        FILE_OP
           AAA (Field1)
            BBB(Field2)
           CCC(Field3)
           DDD(Field4)
    Output file should contain the above 4 fields with fixed lengths 20,1,1,2
    So I declared FCC in File Adapter  as
    I tried many options
    RecordSet Structure: MT_REQ,FILE_STRUC,FILE_OP
    FILE_STRUC.fieldSeparator - 'nl'
    FILE_OP.fixedFieldLengths - 20,1,1,2
    FILE_OP.fieldSeparator - 'nl'
    FILE_OP.endSeparator - 'nl'.
    Please let me know where is the problem?
    Thanks in advance,
    Krishna

    Hi Ramakrishana,
    In FCC fixed length file format when your XML payload is goes to Adaptor engine, it should contain all fields in XML. Otherwise its throw error in FCC channel. Please check receiver payload at SXMB_MONI or message monitoring of Run time work bench. In that payload you will find that some of the fields is not generated in target payload.
    Field in receiver payload is not generated means from sender payload corresponding field is not coming. As per my past experience this generally happens in IDOC sender.
    solution:- In message mapping in every field from IDOC to file use mapWithDefault node function with null value. Due to this though if any field do not generates in IDOC, corresponding field will generate in File Payload and it will not throw error in FCC.
    Regards,
    Prashant

  • Archive Source Files with Errors

    Hi All,
    I need to archive my sending file in repective directory, if it has errors..
    It is mentioned in library that A permanent error occurs either during the conversion of the file content, or in a module in the module processor.
    What is permanent error?
    For example if my input file name is abc.txt which containg 3 fields id,name,address.
    i have configured sending file adapter with FCC .
    now i have given some faulty entries in abc.txt like for example 4 fields separated by comma,
    but this is a error.Asper FCC i have given only 3 fields..
    so this error file has to archive in so and so folder.
    If i check <b>Archive Source Files with Errors</b> parameter in sending file adapter.
    and specified the specified directory.
    but its not working for me. file is not picking but its not coming in the archive folder.
    In library it is mentioned to see message transfer bean link.
    there i found <b>Transform.PermanentErrors: True/False</b>.
    If we have not used message transfer bean then, in that case will this parameter <b>archive source files with errors</b> will work for FCC?
    Please suggest me .
    I would really appreciate if anyone could send a complete blog for this how to archive source files with errors in FCC?
    Thanks in Advance..
    Regards,
    Reehan

    Reehan,
    I am not sure if you are still stuck with your issue of archiving faulty source files but I came across the same issue. Please check your mode of processing. The faulty source files archiving feature will work good in ARCHIVE mode but not in test or delete mode. I haven't check for set for read-only mode.
    Good luck!

  • Reciever channel  FCC problem

    I am getting this error in FCC  in reciever  channel
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Channel has not been correctly initialized and cannot process messages
    Please help on this ..
    Regards
    Ninad

    Hi Sameer /abhishek
    This is recv  file content conversion
    My FCC parameters are
    Recordset Structure  ::     SAPLinkdata
    SAPLinkdata.fieldSeparator : ,
    SAPLinkdata.endSeparator  :  'nl'
    Let me know now ?

  • Sender FTP Adapter - Archive faulty files not working

    Hello,
    We are on SAP PI 7.11 SP 06
    We have a scenario where we are reading CSV files from a FTP location.
    File Sender Adapter is polling the FTP location for CSV files, if there
    is any error during FCC we need to move the faulty file under a
    particular directory on FTP server.
    Archive faulty files tick is click under the communication channel and
    also the required directory is specified, but the functionality is not
    working.
    If there is a faulty file it is just adding a rejected prefix to the
    file and keeping the file in the polling directory. It is not moving
    the file in the rejected directory specified in the communication
    channel.
    Thanks & Regards,
    Rahul Nawale

    Are you trying to archive the file on the same FTP server or a different FTP server? Archiving the faulty file on the FTP server might not have expected results. And if you are trying to archive the file on a separate FTP server, it wouldn't probably be achieved using the simple file adapter functionalities.
    The best way would be to archive the faulty files to an NFS location on your PI server (this will certainly work, even if it's FTP mode) and then use a separate script or PI interface (file tunneling) to move these files from PI server File System to FTP archive location.
    Regards,
    Suddhasatta

  • Error in Receiver Communication Channel in FCC

    I have a simple scenario of Proxy to File. I have to just one field in complete row. So my structure is as below : MT_RecordIB -> Records.  So my XSD looks like this :
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://XXXl.com/INF31018/SAPSerOrd_DaysIn" targetNamespace="http://hnwl.com/INF31018/SAPSerOrd_DaysIn">
       <xsd:element name="MT_RecordIB" type="DT_RecordIB" />
       <xsd:complexType name="DT_RecordIB">
          <xsd:sequence>
             <xsd:element name="Records" type="xsd:string" />
          </xsd:sequence>
       </xsd:complexType>
    </xsd:schema>
    I have used FCC and the parameters are :
    Recordset Structure                                  Records
    Records.fieldSeparator             'nl'
    But I am getting following error in Receiver Communication Channel :
    Failed to process message content. Reason: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:MT_RecordIB' found in document', probably configuration error in file adapter (XML parser error)' (Software version: 3.0.21)
    Thanks,
    Pankaj Singh

    Hey Pankaj,
    Your content conversion parameter might be configured improperly.
    Refer this blogs
    /people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    Refer the following threads for your problem
    [ Unknown structure 'ns0:MT_dbglgtr_FileName' found in document'|Unknown structure 'ns0:MT_dbglgtr_FileName' found in document']
    Rgds
    Ramesh

  • 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>

  • RECEIVER FILE ADAPTER FCC ERROR

    Hi team
    My scenario is a text file has to be picked up by PI, has to processe it and the receiver is Proxy and it has to get updated and sent back to FTP location.
    i am using Sender File Adapter with FCC and Also receiver File Adapter with FCC.
    Both the sender and receiver structures are same; i am using the same FCC parameters for both the sides.
    in Receiver File Adapter i am getting the following errors
    1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
    2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
    please help me out
    thank you
    Edited by: vemugantivn on Aug 16, 2010 12:19 PM

    Hi,
    > 1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    >  Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
    > 2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    > Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
    It is saying that you are not using the fieldSeparator parqameter.
    have you provided the field separator parameter? if not then give like below
    order_row.fieldSeparator : ,  (give what ever the separater you are using)
    or 
    order_row.fieldSeparator : 10,5,...  (if you are using fixed length)
    Regards
    Ramesh

  • FCC Error in RWB

    Hi All,
    My scenario is Idoc to File scenario in which i am using FCC at the target end,
    My data type structure was
    RootNode
    Level -
    1
    5 Fields
    Level  -
    2
    5 Fields
    Level -
    3
    5 Fields
    and my FCC parameters was ..
    Level1.fieldFixedLengths  --- 0,0, (As i dont want all these fields i marked as 0,0,....)
    Level1.fixedLengthTooShortHandling  -- Cut
    Level1.endSeparator                           -- 'nl'
    Level2.fieldFixedLengths                    --- 10,15,10,12,15
    Level2.fixedLengthTooShortHandling  -- Cut
    Level2.endSeparator                           -- 'nl'
    Level3.fieldFixedLengths  --- 10,15,10,12,15
    Level3.fixedLengthTooShortHandling  -- Cut
    Level3.endSeparator                           -- 'nl'
    but, unable to find where actaully the error is..
    This is the folllowing error which i am getting in Receiver comm channel monitoring in RWB.. I think the error is with FCC
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error occurred while connecting to the FTP server "rps37ykf.rim.net:21": java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:RootNode' found in document', probably configuration error in file adapter (XML parser error)'
    request your inputs to solve this issue..
    regards,
    sai

    Hi..
    RootNode ..is it the name of your Message type?
    Yes Root Node is my message Type
    Also are Level1,Level2,Level1 on same level?
    Yes all the levels are in same level ..
    If i need to suppress any one level at the output end how can i suppress it..
    If i alter the Data type structure i can do it but the values which is populated at that level will be used by the other levels
    Eg: i want to suppress level 1 but some functionality of that level will be used by the other 2 levels. so in the structure it is essential but at the target end i need to suppress those values..
    can i suppress it using any other fixedlength funcitonality
    regards,
    sai

  • Error in sending file using FCC

    Hi all,
    i am doing the file content conversion scenario from saptechnicalcom
    my message type is as follows:
    MT_File_Cont_Conv
         Record
            Emp_Header
              Key
              Emp_Id
              Emp_Name
    File is not picked up by the sender file adapter and in RWB communication channel monitoring i am getting the following error:
    Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'Emp_Header.keyFieldValue': no value found
    anybody plz provide me some input to rectify this error
    regards
    sandeep sharma

    >
    sandeep sharma wrote:
    > hi
    > FCC parameters are as follows
    >
    > Document Name:                    MT_File_Cont_Conv
    > Recordset Name:                      Record
    > Recordset Structure:                   Emp_Header,1
    > Recordset sequence:                    Ascending
    > Recordset per message:                 1
    > Key Field Name:                         Key
    >
    >
    >
    >
    > Emp_Header.fieldFixedLengths                   1,6,10
    > Emp_Header.endSeparator          'nl'
    > Emp_Header.fieldNames          Key,Emp_Id,Emp_Name
    > Emp_Header.keyFieldValue                      1
    > Emp_Header.keyFieldInStructure                 ignore
    make sure there is no white space before or after
    Emp_Header.keyFieldValue and also the value 1
    Even a single whitespace can cause an issue

Maybe you are looking for