Sender File Adapter with file conversion

Hi guys,
I’m using a Sender File adapter with file conversion. The message to be processed has a structure with fixed lengths and in your content are some values that needs to be ignored.
An example:
value1  <b>value2</b>  value3…
I want to ignore <b>value 2</b> but I can’t find a parameter for that! Do I need to define dummy fields on my data type and ignore those fields during mapping? Or there is a specific parameter for that?
Thanks in advance,
Ricardo.

hi,
there always is another way:)
you can import the whole line to one field
and cut it inside the adapter module
(then you can define start and stop of the substring that you need to use)
but of course it's not standard even though it's quite easy to achieve in java
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

  • File Adapter with Content Conversion

    Hi -
    I am trying to convert a Flat file which has data as
    firstnamelastnamecompanyName
    Now i have created a message type which has a root name as Contact and its children are FirstName,LastName,Company.
    And in the configurator i have created a file adapter with the content conversion, but being very new to XI i have never used a file adapter with content conversion.  This is what i have in my Content Conversion Parameters.Please correct my code.
    Document Name      ::   MT_Contact
    Document Namespace ::   http://venkat
    Document Offset    :: <i>i did not enter anything here</i>
    Recordset Name     ::   RootNode(i gave this name just like that,,, Should it be something from the IR??
    Recordset NameSpace:: <i>i did not enter anything here</i>
    Recordset Structure::   Contact (this is the name in my IR
    Recordset Sequence ::  Ascending
    Recordsets per Message :: Contact,* (Can someone explain what should be given here)
    Then in the bottom in the name value pairs i have given
    Contact.fieldNames   =   FirstName,LastName,Company
    Contact.fieldSeparator = #
    When i am using the above configuration the error i am getting in RWB is Error: Conversion initialization failed: Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Format error in 'xml.recordset' argument: incomplete structure (name,number) pairInvalid 'xml.recordsetsPerMessage' value 'Contact,*' found
    I am very new to XI and i am unable to understand what exactly each field means in the file adapter when the content coversion is used. Can someone take the pain of explaining them.
    Thank you
    Venkat

    Hi,
    Use the following to create an XML strucutre like this,
    <MT_CONTACT>
    <CONTACT>
    <FirstName> </FirstName>
    <LastName> </LastName>
    <CompanyName> </CompanyName>
    </CONTACT>
    <MT_CONTACT>
    DocumentName : MT_TEST
    DocumentNamespace : Yournamespace
    RecordserName : record
    RecordsetStructure : CONTACT,1
    In the table,
    ignoreRecordsetName  : true
    CONTACT.fieldNames : FirstName,LastName,CompanyName
    CONTACT.fieldSeparator : #
    Go through the links suggested by moorthy and also these blogs to understand content conversion better,
    /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
    /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/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
    Regards,
    Bhavesh

  • Sender file adapter with content conversion  Simple XML

    Hi experts,
    I'm trying to parametrize my sender file adapter content conversion.
    I'm receiving a text file with one single line like:
    AA1;AA2; AA3;
    and I want to convert it to an XML like
    <MT_A1>
    <field1>AA1</field1>
    <field2>AA2</field2>
    <field3>AA3</field3>
    </MT_A1>
    Actually I know how to do somenthing like
    <MT_A1>
        <LINE>
              <field1>AA1</field1>
              <field2>AA2</field2>
              <field3>AA3</field3>
         <LINE>
    </MT_A1>
    What I want is remove the <LINE> tag from my XML.
    Regards
    Gonzalo
    Edited by: Gonzalo del Castillo on Nov 28, 2008 2:18 PM

    Hi
    Use this help document for receiver FCC
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Content Conversion (Pattern/Random content in input file)
    File conversion text to xml (Few Last Post)

  • Sender File Adapter with file conversion  Multimapping

    Hello all,
    i have to use multimapping with the file sender adapter
    XML for multimapping ist like this
    ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>
          <ns1:KVNR_Senden_MT xmlns:ns1="urn:lsv.de/SENDER">
             <Inhalt>
                <KE/>
                <VF/>
                <BBNRAB/>
                <BBNREP/>
                <VERNR/>
                <ED/>
                <FEKZ/>
    in File adapter
    DocumentName Messages
    RecordsetName  Inhalt
    Recorset Struc Inhalt,20
    Inhalt.fieldFixedLength 4,5,6.....
    Inhalt.fieldNames        KE,VF,.....
    but were can I generate Message1?????
    any Hints?
    regards
    ralf

    sorry but the message tags will not be add dynamically
    i have change an existing message mapping 1:1 with file content conversion
    into a multimapping.
    by changing into multimapping the message was surrounded with
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>.......
    no changing in File Adapter an in the IE there was an error
    com.sap.aii.utilxi.misc.api.BaseRuntimeException geworfen: RuntimeException in Message-Mapping transformatio~.
    if i added the stuct
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>.......
    by hand and it works???
    so i think i had to add
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>.......
    to the file content conversion but i don't know how to do it???
    Ralf

  • Receiver File Adapter with File content Conversion

    I have a requirement to send 2 different files to the target directory. Source is the same and different mapping for the 2 files.
    This I can achieve through multi-mapping but there is a problem. How can I use the File content for receiver File adapter which is using Multimapping.
    The structure of the 2 files also different.

    Why would you need FCC on receiver file adapter? If you need different files to be generated from the source, you could create two receiver channels with different mappings and just add them to the same Receiver Detemination. Isn't feasible?

  • Sender Mail Adapter with SAP Conversion agent

    have some1 used SAP conversion agent on attchment from XI Sender Mail adapter?
    it seems to ignore the attchment of the e-mail
    the sender configuration module tab is as follows :
    1.localejbs/AF_Modules/PayloadSwapBean transform
    2.localejbs/sap.com/com.sap.nw.cm.xi/CMTransformBean CM
    3.sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean mail
    The paramters are
    transform swap.keyName Content-Disposition
    transform swap.keyName Content-Description
    transform swap.keyValue attachment
    transform swap.keyValue codeco
    CM TransformationName ZIM_CODECO_VALIDATIONS
    The Convesion Agnet runs prefectly when using the Conversion Agent engine
    thx,Shai Rosenzweig

    check with tis may helpful for you
    http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
    Regds
    Abhishek

  • File Sender adapter with File content conversion

    Hi
    I'm having problems picking up a flat file that has some junk characters in the file.
    I'm usign a file sender adapter with file content conversion. The adapters shows the following error-
    Conversion of complete file content of  to XML format failed around position 0: sun.io.MalformedInputException
    this is the sample data with junk char's -
    A20099201009999009999060815160505051700130008151vÿÿÿÿ³  r 0OK0476                     31N016227241915840IV  00840 ÿÿÿ ÿ ÿÿÿÿÿÿÿÿ ÿ ÿÿÿ             
    There is not much in the file content conversion. This is a fixed length file, I'm just pickign it up & passing it to an inbound proxy. All my processing is in the proxy.
    I'd appreciate any suggestions.
    Thanks
    Rachana

    Hi Rachana,
    Do you use a specific "encoding" like UTF-8 or ISO-8859-1 in your Sender CC?
    To be simple, Encoding is linked to country, you can find all "iso-nnnn" via google or some of them in sap help.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    Moreover, with your source file opened thanks to Notepad (for instance), use option "save UNDER", you will the encoding use by your file
    Mickael

  • File Adapter with Conversion - XML with Hierarchy?

    XI 3.0 (SP9)
    We are using the inbound file adapter with conversion to convert a flat file that has header and line items.  I would have thought that the data type should have been setup something like this:
    <data type>
    <header>
      <item>1</item>
      <item>2</item>
    </header>
    </data type>
    Our flat file looks like this:
    H12345
    I12345
    We have only been able to configure the file adapter to bring in the data like this:
    <data type>
    <header></header>
    <item>1</item>
    <item>2</item>
    </data type>
    What is the proper way to inbound data through a file adapter that has structure conversion like this?
    Do all of the elements get put under the root node, or is there a way to build structure?
    Do we need to build the data type to correspond with the exact way that the data will come in from the file adapter?
    Thanks
    Peter

    Not quite sure what you want to get, as the flatfile and xml structure does not contain the same values.
    However, I will try to give you an example:
    Your flat file looks like this:
    H12345
    I12345
    If the first row is header and the next is a line, then you need to specify the fila adapter with the following:
    Document name = datatype
    Recordset name = recordset
    Recordset structure = header,1,item,*
    Recordsets per message = *
    Recordset sequence = Ascending (need SP10 for this, but you do not need it for this)
    Keyfieldname = id
    header.fieldFixedLengths = 1,5
    header.fieldNames = id,number
    header.keyFieldValue = H
    header.lastFieldsOptional = Yes
    item.fieldFixedLengths = 1,5
    item.fieldNames = id,number
    item.keyFieldValue = H
    item.lastFieldsOptional = Yes
    This will create something like this:
    <datatype>
    <recordset>
    <header>
    <id>H</id>
    <number>12345</number>
    </header>
    <item>
    <id>I</id>
    <number>12345</number>
    </item>
    </recordset>
    </datatype>
    Hoever, if both rows are "item" rows , then you need to specify the file adapter with the following:
    Document name = datatype
    Recordset name = header
    Recordset structure = item,*
    Recordsets per message = *
    Recordset sequence = Ascending (need SP10 for this, but you do not need it for this)
    item.fieldFixedLengths = 1,5
    item.fieldNames = id,number
    item.lastFieldsOptional = Yes
    This will create something like this:
    <datatype>
    <header>
    <item>
    <id>H</id>
    <number>12345</number>
    </item>
    <item>
    <id>I</id>
    <number>12345</number>
    </item>
    </header>
    </datatype>
    Q: Do we need to build the data type to correspond with the exact way that the data will come in from the file adapter?
    A: Yes!
    Good luck!

  • File Adapter: Initialization error: Conversion initialization failed

    Hi all,
    I'm trying to establish a file adapter (FTP, File Content Conversion).
    In the adapter monitor I' ve got the following error:
    Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
    Configured at 14:49:34 2005-08-29
    Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
    My content conversion parameters are:
    BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
    20,50,50,1,10,50,10,50,5,20,20,15,15
    BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
    HouseNo,PhoneNumber,Fax,BankId,BankAccount
    BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
    trim
    BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
    ignore
    What could be the error or where I have to look for it?
    Thanks,
    Fabian

    Yes,
    Recordset name: BP_BusinessPartnerMasterData_IncomingData
    Recordset structure: BP_BusinessPartnerMasterData_IncomingData
    The corresponding Message Type:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
         <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
         <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   f323a4b018a911da9fd9000bcd69ce64
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="Number">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8500fe111da89f2d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Id from Sender for BP
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name2">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8510fe111dacfd7d1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Last name or Company name
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Name1">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8520fe111da94bad1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             First name or Company name 2
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Gender">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8530fe111da99add1210a87220d
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             m or f or blank
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Birthdate">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8540fe111dab156d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="City">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8550fe111daa58cd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Postcode">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8560fe111dac0c2d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Street">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8570fe111dabbd3d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="HouseNo">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8580fe111dab63fd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PhoneNumber">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e8590fe111dac782d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="Fax">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85a0fe111daa9ebd1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankId">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85b0fe111dace1ed1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="BankAccount">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7679e85c0fe111da8801d1210a87220d
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="15" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

  • Get additional file attachements with file adapter

    Hello,
    Has anyone ever had the following situation:
    A Sender interface sends a little bit of data to XI.
    This data contains the filenames of some files on a FTP server.
    Based on these filename the file needs to be retreived from a FTP server and further handled as an attachement of the XI message?
    Is it possible to trigger a sender file adapter with a variable directory and filename from XI, in a BPM or Mapping?
    Warm Regards,
    Leon Boeijen

    hi,
    >>>>Is it possible to trigger a sender file adapter with a variable directory and filename from XI, in a BPM or Mapping?
    no it's not possible to start a file adapter from BPM
    you can use a java proxy that will do the trick
    we've used a solution like this many times with no big issues
    remember that it's better to use an async java proxy
    (with correlation) then a sync one...
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • 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

  • File adapter:  Receiver File Content Conversion problem.. XML to CSV..!!

    Hi,
    I am facing some problem in FCC for Receiver adapter. It has to convert from XML to CSV File.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:PaymentFull_Target xmlns:ns0="http://sdn.com/Payment">
    - <RECORDSET>
    - <Header>
      <LineItem>1</LineItem>
      <SaleNumber>102</SaleNumber>
      <TransNumber>105</TransNumber>
      <Store>1326</Store>
      <variant>Z6</variant>
      <TransType>NEW</TransType>
      <Adjustm_Type />
    </Header>
    - <Header>
      <LineItem>2</LineItem>
      <SaleNumber>102</SaleNumber>
      <TransNumber>105</TransNumber>
      <Store>1326</Store>
      <variant>Z6</variant>
      <TransType>NEW</TransType>
      <Adjustm_Type />
    </Header>
    - <Header>
      <LineItem>3</LineItem>
      <SaleNumber>102</SaleNumber>
      <TransNumber>105</TransNumber>
      <Store>1326</Store>
      <variant>Z6</variant>
      <TransType>NEW</TransType>
      <Adjustm_Type />
    </Header>
    </RECORDSET>
    </ns0:PaymentFull_Target>
    Output File is coming only with lineitem values , remaining fields are not coming.
    *1,2,3*
    FCC Used...
    RecordSet Structure -- Header
    Header.fieldNames -
    LineItem,SaleNumber,TransNumber,Store,variant,TransType,Adjustm_Type
    Header.fieldSeparator-----   ,
    Header.endSeparator-----    'nl'
    Did I miss anything.. any idea whats going wrong?
    Thanks
    Deepthi

    Hi Deepthi,
    Mention the occurrence of header in Recordset
    You specify like this:
    Recordset: Header, *
    Header.fieldSeparator : u2018Field Separatoru2019
    -->For FCC on Receiver side you donu2019t have to mention the field names.
    -->The u2018endSeparatoru2019 parameter needs to given for substructure only
    Check this links:
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    /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
    Rgds,
    Akhila

  • XI 2.0 File Adapter with XI3.0

    I am send a file from my pc to XI3.0,using an XI2.0 file adapter on my pc.
    My problem is that I cannot get it to correctly generate the name spaces
    <ns1:SALES_ORDER xmls:ns1="http://SALES_NS">
    instead it generates:
    <ns1:SALES_ORDER xmls="http://SALES_NS">
    Am I missing a paramter in my file adapter properties file?
    Thanks
    Patrick

    Hello,
       We are also having similar type of problems. In our installation the log is at/usr/sap/<INSTANCE>/DVEBMGS00/j2ee/cluster/server0/log/services/com.sap.aii.adapter.file.svc
    In the log file, I see
    2004:11:11 10:12:12 : File Adapter Administration Intialized
    No file adapter configured
    Not sure why it says that no adapter is configured even though we have couple File adapters configured with Adapter status active and all the objects have been activated.
    I would really appreciate if anyone can point out, if I am missing something that I am supposed do to other than J2EE File adapter service being run and Activating a Fileadapter in the Integration Directory.
    Thanks

  • How to use File Adapter with hierarchial Structure?

    Hi,
    How to use File Adapter with hierarchial Structure like..
    Data:
    --Header Details:
    Line Item Details:
    Data
    Bcoz I am getting a Flatfile in a hierarchial way as shown below.
    Header Details :1
    Line Item a
    Line Item b
    Header Details :2
    Line Item c
    Line Item d
    Kishore

    Hey Kishore,
    In order to create a structure you need to use the file with convertion mode on the sending communication channel of the file adapter.
    check the link for the needed configuration paramters.
    If the structure is more complexed you can use the Contetnt master(CM) from itemfield which allows to ceate XML file from complex flat files and more.
    <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm">File sender adapter</a>
    If you have any question i'll be more than happy to assist.
    Nimrod Gisis

  • Acknowledgement from receiver file Adapter with out BPM

    Hi Gurus,
    I am trying to get Acknowledgement from Receiver file Adapter with out Using BPM.
    Here is the scenario. I am sending files from different Sender Adapters. There is only one target that is File Adapter. After each successfull and failure transaction I need an Acknowledgement that needs to trigger another receiver adapter and send the the file name and timestamp to that file.
    Hope this is a complicated scenario. Please help me.
    Thanks,
    Kevin

    from sap note 821267
    6. Acknowledgements
        * Q: Does the File Adapter support acknowledgements?
        * A: You need to distinguish system acknowledgements (indicating that a message has been received by the target system) and application acknowledgements (indicating that the message has been successfully processed by the application on the receiver side).
               The receiver of an XI message will only send an acknowledgement back to the sender if the sender has requested one. However, the File Adapter has no functionality that relies on the receipt of an acknowledgement, so it never requests one.
               On the other hand, if a File Adapter Receiver receives a request to send an acknowledgement, it will do so for a system acknowledgement request. Application acknowledgements are not supported at all as the File Receiver has no way to determine if the written file has been correctly processed by the back-end application, which is what a positive application acknowledgement would imply.
    this means that your requirement is ideally not possible without a BPM

Maybe you are looking for