File Conversion to File Conversion Scenario..

Hi,
I am doing a File Conversion to File Conversion scenario. Hope its clear..
Well in this scenario my structure is
<File2File_Conversion_Sender_MT>
<Employee>
<id>aa</id>
</name>sas</name>
<Employee>
<File2File_Conversion_Sender_MT>
In sender:-
Wat will be the document name?
Recordset name?
Recordset structure?
In receiver:-
Recordset structure?
Let me know if any more clarification is needed.
thanks
Anju

Hi Anju,
Use this :
Document Name : File2File_Conversion_Sender_MT (this is Outbound Message Type)
Document Namespace : NAmespace of outbount Message Type.
Recordset Structure : Employee,*
Name----
Value
Employee.fieldSeparator -
>   ,
Employee.endSeparator -
>  'nl'
Employee.fieldNames    -
>  id,name
ignoreRecordsetName   -
> true
Go through this :
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
Thanks,
Maheshwari.
Message was edited by:
        Maheshwari Morbale

Similar Messages

  • XML File to Flat File scenario: Reciver file adaptor content conversion

    Hello Friends,
    Currently I am working on XML File to Flat File Scenario.
    I used receiver side File adaptor with content conversion.
    My receiver side adaptor is giving error. Error is given below.
    Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
    My content conversion parameters are as:
    row.fieldNames                           Customer_ID,Name,Address,Phone
    row.fieldSeparator                      ,
    row.processConfiguration          FromConfiguration
    row.endSeparator                       'nl'
    Can you please suggest me what kind of error is this?
    Regards,
    Narendra

    Still I am facing below given issue.
    2010-06-08 15:34:25     Error     File adapter receiver channel CC_Customer_FlatFile_Distination is not initialized. Unable to proceed: null
    2010-06-08 15:34:25     Error     Exception caught by adapter framework: Channel has not been correctly initialized and cannot process messages

  • Problem in content conversion in file - xi - file scenario

    Hi there,
    could you please give some help? I am getting stuck.
    here, my problem (last response): Error in Adapter monitor
    Besta regards,
    david

    Hi david
    Please use the following parameter at the sendeer side to convert an text file into xml file
    RECORD.fieldSeparator :,
    RECORD.fieldNames :KEY,FNAME,LNAME,AGE
    RECORD.keyFieldValue :1
    DETAIL.fieldSeparatr :,
    DETAIL.fieldNames :KEY,SALARY,EMPID
    DETAIL.fieldNames :2
    Note:these parameters are accoding to the structure given below.
    suppose you have a structure like as below
    data (0..unbounded)
    record (0..unbounded)
    key (1..1)
    fname (1..1)
    lname (1..1)
    age (1..1)
    detail (0..unbounded)
    key (1..1)
    salary (1..1)
    empid (1..1)
    and the input file will look like as below
    1,aaa,bbb,23
    2,12000,10838
    1,ccc,ddd,23
    2,13000,10830
    if you still have the problem please reply me back so that i can solve your problem.
    Thanks
    Rinku

  • ERROR :Conversion of file content to XML failed at position 0

    Hi Frnds,
    I have a File to File scenario, while testing I am getting the following error:
    Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 1 according to structure 'TA_830':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
    Can any one please tell me why Iam getting this error even I have provided the following informantion in channel configuration. Here TA_830 is the record name.
    TA_830.processFieldNames     fromConfiguration
    TA_830.fieldNames     SEG_NUM,PROCESS_DATE,PAYEE_BCODE,ISSUE_SEQ_NUM,CR_DATE,PAYER_BCODE,PAYER_ID,ENTRY_SEQ_NUM,TRAN_TYPE,PAYMENT_TYPE,PROCESS_FLAG,REF_NUM,PAYER_ACC,VAL_DATE,ISO_CURRENCY,AMOUNT,RESV_11,SEG_NUM,EXCHG_RATE,ADDR1,ADDR2,ADDR3,ADDR4,RESV_18,SEG_NUM,BANK_ID,BANK_CODE,ADDR1,ADDR2,ADDR3,ADDR4,RESV_5,SEG_NUM,ACCOUNT,ADDR1,ADDR2,ADDR3,ADDR4,RESV_6,SEG_NUM,MESSAGE1,MESSAGE2,MESSAGE3,MESSAGE4,RESV_6,SEG_NUM,MESSAGE1,MESSAGE2,MESSAGE3,MESSAGE4,RESV_6,SEG_NUM,PROCESS_DATE,PAYEE_BCODE,ISSUE_SEQ_NUM,CR_DATE,PAYER_BCODE,PAYER_ID,ENTRY_SEQ_NUM,TRAN_TYPE,PAYMENT_TYPE,PROCESS_FLAG,TOTAL_AMOUNT,RESV_59
    TA_830.fieldFixedLengths     2,6,12,5,6,7,5,5,3,1,1,16,24,6,3,15,11,2,12,24,24,24,24,18,2,1,24,24,24,24,24,5,2,24,24,24,24,24,6,2,30,30,30,30,6,2,30,30,30,30,6,2,6,12,5,6,7,5,5,3,1,1,16,59
    TA_830.fieldContentFormatting     nothing
    Regards,
    Shiva.

    Hi,
    As you are using Fixed Length File...use below specified parameters:
    TA_830.fieldName:          Names of Fields in teh File
    TA_830.fieldFixedLegths: Lenghts as per your file
    TA_830.keyFieldValue:    If you use any value as key
    TA_830.lastFieldsOptional: YES
    TA_830.endSeparator :        'nl'
    This will help you out..
    Thanks,
    Kishore.

  • File sender with content conversion and ignoreRecordsetName

    Him,
    I have an scenario with a compressed file sender with content conversion.
    In my sender cc i have:
    1     AF_Modules/PayloadZipBean     Local Enterprise Bean     unzip
    2     AF_Modules/MessageTransformBean     Local Enterprise Bean     transform
    3     CallSapAdapter     Local Enterprise Bean     2
    In module configuration, I have also added:
    xml.ignoreRecordsetName  --> true
    But RecordsetName is not removed from XML
    Why?
    thanks, in advance
    Carme

    Hi,
    No need to enter anything in module configuration. Just specify following Name-Value pair in the table provided on the Content Conversion tab of your file adapter.
    Add a row with Name = ignoreRecordsetName and Value = true (Both case-sensitive)
    For details, see [this link|http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm].
    [some more here|http://www.riyaz.net/blog/index.php/2008/02/20/xipi-file-content-conversion-for-complex-structures/]
    Regards,
    Riyaz

  • File content conversion:move files to a new directory

    hi all,
              I have a file content conversion sender and receiver scenario.Now my doubt is: XI is running on sap27 server.Input file is being created by an ABAP program in r/3 and file being put in sap29 server.
    In source directory if i am giving the sap29 path it is not working.Is there any way that i can write a OS command to move files from 29 to 27 before message processing ??
    Any other option available??
    thanks,
    Nisheeta

    hi,
          Yes the basis people have shared the folder and they have mapped the sap29 folder into sap27 using I:\ drive
    But the files are not getting picked....am i giving the source directory wrong??
    I am giving I:\Folder_Name
    suggestions needed
    thanks,
    Nisheeta

  • Blogs for File content conversion in File Adapter

    hi all,
    Can some one give me the links for File Content Conversion for File to File Scenario. please.
    Thanks in advance.

    Hi
    For Sender
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /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/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    SAP Help for sender
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    For Receiver:
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    SAP Help for receiver
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm

  • Character conversion in File Adapter leads to Mapping Error

    Hello experts,
    I have a problem with file encoding on the file sender adapter. The scenario I'm using just reads a flat file and maps each line of this file to an Idoc field. Normally this works perfect but from time to time we get files contaning the character "'" (dec. 39 or hex 27) which then end up in a mapping exception. In the adapter configuration we use file content conversion, File Type is set to "text" and we haven't set any encoding.
    When I look at the generated XML then I can see that it created a UTF-8 encoding (default) and the "'" has been replaced by "&apos;".
    I tried to load this XML into the mapping in test mode and it faild as well. Only if I change the XML encoding to "ISO-8859-1" it goes through. If I set "ISO-8859-1" as encoding on the sender adapter, it doesn't make any difference.
    What am I doing wrong here and why is character dec 39 affected at all? From my understanding this is in the normal ASCII table between 1 and 128 and should not cause any problem! In the same file I can also see the "&" (dec 38 or hex 26) which is converted in the XML to "&amp;" and works perfect.
    I'd appreciate any helpful statements...
    Thanks in advance
    /Michael

    From your description I would guess that not the apostrophe causes the trouble, but there is any European letter in your source which is not part of ASCII like an German umlaut. Otherwise it should not make any difference whether you use UTF-8 or latin-1 for encoding.
    Could you send me the file that makes the trouble to my email address stefan dot sdn at gmail dot com?
    Regards
    Stefan

  • Error Message: Conversion of file content to XML failed at position 0: sun.

    Hi Experts,
    i strugle with a File 2 IDOC Scenario.
    In the sender communication channel monitoring I get the error message:
    Conversion of file content to XML failed at position 0: sun.io.MalformedInputException
    Unfortunately I am not getting any further information and I do not know where the file-adapters problem is.
    Tthe .fieldSeparator = # . Can this be the problem, that the file-adapter-engine can not handle # within file conversion? I also tried it with .fieldSeparator = '#' . But the error message is the same.
    I am glad for any hints.
    Thank you for your help in advance.
    Regards,
    Udo

    Hi Udo,
    The error is due to wrong intput.
    putting # might be a reson.
    You Can try (,) or a space as a field separater.
    Can you test this once.
    Have to defined the field separated?
    Regards,
    Sumit 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

  • Content Conversion in File Receiver Adapter

    Hi,
    I am doing a Content Conversion in File Receiver Adapter.
    Input to the Adapter is:
    <ns1:FileResponse_MT xmlns:ns1="http://www.bpmtest.com/bpm">
         <OrderID>123</OrderID>
         <Quantity>98</Quantity>
        <Price>76.23</Price>
    </ns1:FileResponse_MT>
    Desired output is:  <b>OrderID# Quantity# Price (123#98#76.23)</b>
    I tried to accomplish this with different settings in ‘Recordset Structure’ and ‘Conversion Parameters’ but could not achieve it, every time an empty file is produced.
    Would appreciate any help on this.
    Best Regards,

    Hi,
    Enclose your structure with a parent element like this.
    <ns1:FileResponse_MT xmlns:ns1="http://www.bpmtest.com/bpm">
    <parent>
      <OrderID>123</OrderID>
      <Quantity>98</Quantity>
      <Price>76.23</Price>
    </parent>
    </ns1:FileResponse_MT>
    Then give the parameters, it will work.
    parent.fieldSeparator = '#'
    parent.endSeparator = 'nl'
    Regards,
    P.Venkat

  • File Content Conversion i.e Flat file 2 Flat file

    Hi guys,
       I am new 2 SAP XI
    and i am trying 2 do "Flat File To Flat File".
    Input File contains following data:
    Name:varun
    Surname:rajaraman
    Address:B-2
    Employee no:8204
    i.e Each Data is in separate Row.
    Output File Should contain the following data:
    I am varun rajaraman staying at B-2 bearing employee no. 8204.
           (name,surname)               (address)                        (Employee No.)
    i.e data should be in a single row.
    So, i have a problem of reading the data from input file i.e data from each row and transfering it into output file along with which i need 2 insert  "i am " ,"staying at", etc.
    pls tell me the procedure in detail.
    Thanks and regards
    santhosh rajaraman

    Hi,
    Check this links for file content convertion.
    File content conversion sites
    /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

  • Attachment of original message in file sender adapter content conversion

    Hi,
    does anybody know how I can configure a file sender communication channel (with content conversion) so that the original file is added to the XI SOAP message as attachment? Maybe this is just a parameter in "Advanced" tab. (The content conversion itself is not an issue.)
    The result should be the "Main Document" (XML-message) and the "original document" as two attachments in the SOAP payload.
    The reason for this is that the original file should be archived with the XML message as it was before the XML content conversion of the file sender adapter took place.
    Thanks,
    Philipp

    original file is added to the XI SOAP message as attachment?
    The "Advanced" tab -> additional files added in file adapter should act as the attachment to soap receiver adapter if u select the "Keep Attachments" option in soap receiver communication channel.
    What do u want to do in FCC is a bit unclear?
    Regards,
    Prateek

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

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

Maybe you are looking for

  • Error in document splitting

    Hi experts, I am posting vendor invoice, while saving system is giving the following error: Doc.Type : KR ( Vendor Invoice ) Normal document Doc. Number                     Company Code    6000         Fiscal Year     2010 Doc. Date      23.09.2010  

  • My hp photosmart c4680 wont print on network

    i set up the printer on one computer (it prints fine from there) i then shared it over the local network. when i try to print from one of the other computers it says printing, the computer it is connected to says printing and so does the printer. but

  • Package declaration problems.

    CREATE TYPE avg_rwnd_shift_t AS OBJECT (c2 NUMBER(10,0) ,rwnd NUMBER(10,0) CREATE TYPE avg_rwnd_shift_set_t IS TABLE OF avg_rwnd_shift_t; CREATE OR REPLACE PACKAGE intrabase IS FUNCTION rwnd_limit(in_cid IN NUMBER, in_direction IN NUMBER, in_window I

  • Pass bean property name across JSP pages

    First, the sample code: <%-- ================ some.jsp =============== --%> <%-- bunch of code [...] --%> <tr> <td><bean:message key="prompt.desc" /></td> <td><html:textarea property="desc" /></td> </tr> <tr> <td> <bean:message key="prompt.notes" />

  • Reopen period in MM

    Hallo everybody, i have this issue in MM opening/closing periods. I opened the 3th period (MMPV).But i just realised that i have to do some postings in the 12th period .How can i open again December and do my postings? Is there a way to do this? Rega