Lockbox File Format in Europe

Hi,
We are in planning to implement Lockbox functionality for auto cash application in our European company codes. I have few questions:
1)What file formats can SAP read other than BAI2  format.We are using standard SAP program  RFEBLB00 (Transaction FLB2) to read a BAI2 file for our US company codes and they work fine.
2)Ours is Bank of America and they are unable to provide BAI2 format? Has anybody faced this kind  of situation where Bank can't provide BAI2 format for Europe transactions? What are the alternatives?
Thanks in Advance.
Rakesh

Currently, only BAI and BAI2 file formats are supported by SAP.  It includes
the following:
BAI Record Format:  Specify the length of the document numbers (10 in
the standard SAP System) and the number of document numbers in record types 6
and 4 of the BAI file. Your bank must agree on this format information.
BAI2 Record Format: It is not necessary to specify the length of the
document or the number of document numbers in record types 6 and 4. This is
because BAI2 file is designed that each document number is on a different record
type 4 with its corresponding payment and deduction amounts.  Your bank must
agree on this format information.
NOTE:  while the BAI and BAI2 formats are supposedly standard, experience
has shown that they can vary by bank and many SAP clients have contracted for a
customized format.  The format received will need to be mapped to reconcile with
the SAP delivered data dictionary layout (Tables FLB01, FLB05, FLB06, etc.) to
ensure proper processing.  If the format does not reconcile and the user does
not want to have the bank change the format, SAP recommends that a user-written
ABAP be used to reformat the file or alternatively the SAP data dictionary can
be modified (this is a repair that will need to be re-applied in future
releases).
Batch Input Sessions [Posting Functions]:  Specify which postings the
system creates (general ledger cash postings and/or customer cash
application).  It is recommended that both choices are selected if you are using
the general ledger and accounts receivable modules.  For the general ledger you
can decide whether to post one aggregate amount to the incoming cash account or
one line per check. This depends on your reconciliation with the bank.  In
addition, you can choose to create and name a batch input session to insert any
missing or new customer bank details into the customer master records  (this can
only be done if the system identifies a valid document number).
Important Note: The lockbox  program first attempts to identify the customer
with unique bank information in the customer master record matching to MICR
information on the check, so maintenance of unique customer MICR information is
important to ensure success.  If there is more that one customer with the same
MICR bank and account, then the program cannot apply the check to an
account.  This situation usually means that either the same customer has been
set up twice, or maybe what should have been only Ship-to or Sold-to customers
for the same Payer have actually been set up as separate Payers. Alternatively,
it may be necessary to set up a relationship where one customer is identified as
the main Payer and has MICR info, and the related customers do not have MICR
info but instead have the main Payers customer number in the Alternate Payer
field of the customer master record.
The payment information provided in the bank data file will create a payment
advice per check.  This payment advice will be used by the lockbox procedure to
clear subledger open items.  For more information on payment advices, please
read accounts receivable/accounts payable Payment Advice Notes in the IMG or
On-Line Help

Similar Messages

  • Lockbox Process, Configuration, Lockbox File format

    Hi everybody,
    I need a help on lockbox documents. Pls send.
    Regards,
    JC

    hi
    Lockbox is a process provided by a bank where the customer remits his payment to a PO Box at your bank, the bank deposits the check in your account and enters the remittance data from the customer. Then the bank sends the data to you electronically for you to import and apply in SAP-AR.
    The structure that the bank uses is usually one of two formats. BAI will provide you the customer information and the check amount but no invoice remittance data. Usually cheaper and works well for a business where customers are paying only one invoice at a time.
    BAI-2 offers remittance data but the bank charges more for the service because they have to enter more info.
    Look at structures FLB** to see the transfer data. 
    When the bank sends the customer payment data you use Treasury function FLB2 to import and then process the payments. This process attempts to determine where to apply the payment and will post directly against an invoice, an account to a customer or if it can't even determine the customer it posts into a clearing account (configured) to be resolved.
    Purpose
    Lockbox is a service offered by American banks in which banks collect and process customer payments to reduce processing time. The system can handle both lockbox file formats offered by banks, namely, BAI and BAI2.
    Process Flow
    A company can create accounts called ‘lockbox’ accounts at its bank (or banks) that act as payment collection accounts for customer payments.  The company then informs their customers that all open item payments for their accounts must be submitted to one of the established bank lockbox accounts.  The bank collects these payments along with the customers’ remittance information that indicates what open items the customer payments intend to clear.  Data entry clerks at the bank manually enter the information into an electronic file for transmission to the company to which the lockbox account belongs. These files are typically transferred nightly to the various lockbox owners (companies).  The files adhere to one of two standard banking industry transmission formats (BAI and BAI2), both of which are supported in the system.
    BAI and BAI2 formats differ in their level of information detail.  BAI does not separate out the incoming check line items by invoice subtotal reference.  Conversely, BAI2 splits the check total into separate invoice references and associated payment amounts. As a result, your ‘hit rate’ percentage of payment-invoice matching from each transmission is likely to be higher when using BAI2 rather than BAI formats.
    for furthur notes
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/4e/888d24ccb811d3bffd0000e8a4a484/frameset.htm
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/57/f1fc3768b56d00e10000009b38f842/frameset.htm
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/7a/af0eba9ffa11d295d900a0c9426c73/frameset.htm
    http://help.sap.com/search/search_overview.jsp
    nagesh

  • Payment file formats supported by SAP in Europe-France, Belgium, Italy, Spa

    Hi Friends,
    Any information on payment file formats preferably DME formats supported by SAP would be great, specially following Europe countries:
    France
    Belgium
    Italy
    Spain.
    If anyone has imeplemented following formats in SAP for the following countries, can you pl. share your experience as well as implementation effort for this?
    UCV          - Belgium
    CFONB160 - France
    Norma 34  - Spain
    CDI/Bonfica - Italy
    Thanks and regards,
    Pinky

    hi
    check this Note 395679 - PMW: Overview of available formats

  • Lockbox Transmission Formats and Sample Data File

    Hi All,
    We are going to implement. For that we are going to use one of the standard transmission formats.
    As per the oracle manuals we can use Convert (arconv.ctl) tranmission format for transferring payment information from other systems.However it does not containt the lockbox name and many other fields.
    Please tell me whats the best standard format I can use and give me any sample data file formats if you have.
    Regards,
    MPH

    Hi Thanks a lot for your reply,
    Can you tell me if you have any data files created based on the BAI transmission format.
    Thanks and Regards,
    MPH

  • I'm trying to e-mail music scores and audios, but I receive an error message saying Preview doesn't recognize the file format, regardless whether I use .mus, .pdf, or .mp3.  I haven't come across Preview or this problem before.  Any suggestions?

    I'm trying to send music, scores and audio, as e-mail attachments, with a copy to my e-mail address.  Whether I use .mus, .pdf, or .mp3, the error message says Preview doesn't recognize the file format.  I haven't seen Preview, or had any problems, before now.  Thanks for any suggestions.

    Hi,
    Firstly, your country is detemined by several factors, including your phone's regional settings, your SIM card and your NokiaAccount settings, if you used this phone whilst abroad then you may need to check that your regional and account settings are up to date since you have arrived in Canada.
    For services like Gigs, you should also ensure that the MixRadio app has access to your phone's GPS location as well as the main location being on in the phone settings. To check this, as well as Location being turned on in the phone settings, in MixRadio itself go to Settings>Location>On:
    The concern with favourites may also be related to location, if the music from certain artists is available in Canada but not where the service might think you are, availability of content may vary from region to region.
    If all settings in both the phone, your Nokia Account and the MixRadio app are correct, we may have to investigate deeper.
    It is impossible to comment on your camera without seeing it, you cold have the phone checked by Nokia Care locally, but of course if it was supplied in Europe it will be covered by the European Limited Warranty which is not valid in Canada.
    If this or any post answers your question, please remember to help others by pressing the 'Accept as solution' button.

  • Lock Box file format

    Hi All,
    I need help on lock box upload file format.I created a test file using bank layout & FLB* structure tables and put a test data for a customer.and tried to process it in FLB2 using pc upload but system didnt select the customer open items.
    The file contains details for Record type 1,2,4,5,6,7,8,9.and I dont  know what else need to do ,could anyone please provide any guidance on file format?.Thanks
    100YPCCDESTINYPCCORIGIN1106221714          
    2YPCCDESTINYPCCORIGIN000000000040008000801
    50010001234567110622YPCCDESTINYPCCORIGIN     
    6001001000012614407100001300091524660000055555     
    400100160195590023784     
    700100012345671106220010000126144     
    8000000123456711062200010000126144     
    9000000                              
    thats the file I created but not working.
    Regards
    Shaun

    Hi,
    Please refer this links:
    how to create Lockbox test file?
    http://wiki.sdn.sap.com/wiki/display/ERPFI/ConceptofLockbox
    Regards,
    Pramitha.

  • How to Reprocess Lockbox file

    Hi Gurus,
    We upload one lockbox file ( BIA2 file format ). But it wast posted correctly So I need to Clear ( means reverse that lockbox file in SAP System ) and process same file one more time.
    Que
    1. how can i reverse that lockbox file from SAP System ? ( Could you please provide steps with T-code and necessary intructions )
    Thanks
    P B Patel

    Hi pbpatel ,
    Whenever you upload lock box file ( BIA2 file format )through FLB2 system generate the fallowing document numbers Automatically in output screen.
    AR Document number
    GL Document number
    Payment Advice document number
    If we reverse the above document numbers we can able to simulate same issue.
    Post process Lock box you can check in FBL1
    Rds,
    Anil

  • BAI2 file format- 4 record

    Hello SAP Guru's-
    In testing the lockbox functionality, I have a client who has a customer that remits with over several hundred line items in one check.  In the 4 record, the bank sent me a file with the following format
    Record Type  4
    Batch Number  001
    Item Number  001
    Overflow Type  4
    Overflow Seq Nbr  01 to 99 then start 01 again
    Last Ovfl Flag  9 (on last record)
    On the Overflow Sequence number, when they got to 99 they started over to 01 on the next line item.  Is this correct?  I understood that they should change the overflow type from a 4 to a 6 and restart with a new 4 record?
    Please help!
    I will AWARD POINTS.
    Many thanks!

    Hi,
    Please go through the following regarding Record 4 for BAI2 file format:
    <i>Record 4: Table FLB24
    4002003401716000002 00000100000000000000
    4002004402918000018 00001000000000000000gh
    • The item in blue is the Record Type indicator. Record Type 4 can appear numerous times in the Lockbox file. Record 4 is the “Item Record” and it is used to hold one invoice each. (Field name OR001)
    • The item in green is the Batch Number for the Lockbox. This item will have 3 characters. (Field name OR002)
    • The item in red is the Batch Item Number for the Lockbox. This item will have 3 characters/spaces. (Field name OR003)
    • The item in purple Type of Overflow record (1 space). In this case, it is a ‘4 record’ because it contains only its own item, not an item overflowed from a preceding 6 Record. (Field name OR004)
    • Bright green is the Sequence Number for the record (2 spaces). (Field name OR005)
    • The item in yellow is the End Indicator for the Lockbox. A ‘9’ indicates the last record of a Lockbox (1 space). (Field name OR006)
    • The next items in black are the Invoice Numbers (16 characters/spaces each). Only 1 invoice is placed into each 4 Record. (Field name IVCNR) The best field format convention would be to use left-justification, blank-padding right for the invoice number(as shown in the Record 4 above).
    • The items in dark yellow are the Payment Amounts per invoice (10 characters/spaces). (FiT)
    • The items in gray are the Deduction Amounts per invoice (10 characters/spaces). MT)
    • Dark Blue is the External Reason Code for the payment. (Field name RESTG)
    • Up to the next 30 character spaces are available for short text. They may be left blank if desired. (Field name OR011)</i>
    In BAI2 overflow type is not changed, 4 is correct. Only in BAI format it is changed.
    Thanks
    Murali.

  • BAI2 file format- 6 record / Check DDA Account

    SAP Guru's
    Can any one confirm for me what the position and characters should be for check DDA Account.  In my last assignment, I used the following:
    Position 27-39  Field Size 13 Right justify and zero filler
    The BAI/ BAI2 file format white paper for SAP I believe is out of date because it says that the check DDA account should be 10 characters. 
    Can any one confirm for me which is right and if I am right which I assume I am since my last lockbox implementation was successful, why is the white paper say 10?  Is there a latest version?
    Thanks!
    POINTS PROMISED

    no response

  • Reg DMEE file format

    Dear experts,
    My requirement is that i have to change the DMEE file format for format tree GB_BACS according to user requirement. I have copied to ZGB_BACS and trying to change it according to user requirement. But when the functional trying to attach ZGB_BACS to configuration, it is throwing an error stating it is not updated in table. Can anyone help me in achieving this.
    tks in advance

    Stephen,
    I'm sure you're trying various alternatives with your mentioned transaction, but in the documentation, I find reference to DME, and here's what it says.
    DME
    Data medium exchange in this case involves the creation of a file which corresponds to the rules of the credit institution in question for automatic payment transactions and which contains all the necessary payment information.
    The information relevant for the payment medium (file format, creation data, payment amount in local currency, payment documents involved etc.) are stored in the system and can be called up via the DME manager.
    Other functions of the DME manager are:
    - Downloading the file into your local (PC) file system
    - Displaying and printing the file contents
    - Generating a payment summary for the data medium
    I would strongly suggest putting as many parameters as you know while trying to extract an output from this program.
    If things still don't work, have a look at T.Code PC00_M99_FPAYM. The Easy Access path is HR --> Payroll --> Europe --> Great Britain --> Payroll --> Bank Transfer
    Just in case you haven't looked here, there are a bunch of other programs here that might turn out to be useful to you.
    If you have, and tried & discarded all of these, I guess a custom development is your only way out.
    Regards
    Gulshan

  • Bank File and File Formats

    When sending ach file to bank after it gets placed on application server (what is application server transaction code) a direct interface or not? If not what is a direct interface?
    What is flat file and xml file. Please tell the difference with example??
    What are various file formats sap supports for importing ebs in sap? What information should be requested from bank?

    Hi Sheena,
    1. Outbound files - You can create a ACH file in any format you want. SAP support text file, IDOC.
    After you run your payment program - F110 - the last step is to create the payment medium. When you run this payment medium program it creates the file in a specific format as per your configuration. This file can be stored in your hard drive (C:) or in the SAP server based on the path given by you in the variant.
    You can use T-code FDTA to view the file.
    If it gets stored in C: you can just go to the directory and double click the file.
    If it is stored in SAP server you can use transaction AL11 to view the file.
    2. Inbound file  - The electronic bank statements come in various formats. The most common formats are BAI in US, Multicash in Germany, MT940 in Europe. Each format has been defined separately, you can go to Googe and search for details about these format.
    SAP has standard program which read these formats and post them to your General Ledger.
    If you have more questions, please post them and I would try to answer.

  • File Format options not appearing in the Save As dialog box - InDesign CC

    So i was working with a legacy file (an .eps from illustrator4) that i placed into InDesign CC, and when i went to export as a jpg, the option to choose a different file format from the bottom of the dialog box was gone. Did i hit some crazy shortcut to remove the options, or is this a bug that occurs when working with certain legacy files? I've restarted InDesign, rebooted my laptop, deleted my Adobe preferences, reset my adobe warning dialogs, and I still cant export or save as any other file format because the option doesnt appear. And it doesnt matter if i create a new file or open an existing one. Please help. See the pic below. No option for file format on the bottom of the dialog box.

    Thank you very much!
    Reinstalling worked, but i'd still kinda like to know what caused this problem & if this will continue to happen. To me, reinstalling is pretty much like having to reboot anytime you go to IT -- they dont know what the problem is, they just know how to fix/stop it.

  • Duplicate File Format options in Save As Dialog

    I am getting duplicate file format options in my save as dialog. I am running photoshop 12.0.1 on mac os x 10.6.4.

    Thanks for the answer, I have the same problem, happened after I uninstalled CS4, (using cs5 now) however I can't seem to find where the duplicates are located. Any tips as to where I should look?
    Thanks in advance!

  • How to export table contents in xml file format through SQL queries

    hi,
    i need to export the table data in to xml file format. i got it through the GUI what they given.
    i'm using Oracle 10g XE.
    but i need to send the table name from Java programs. so, how to call the export commands from programming languages through. is there any sql commands to export the table contents in xml format.
    and one more problem is i created each transaction in two tables. for example if we have a transaction 'sales' , that will be saved in db as
    sales1 table and sales2 table. here i maintained and ID field in sales1 as PK. and id as FK in sales2.
    i get the combined data with this query,
    select * from sales1 s1, sales2 s2 where s1.id=s2.id order by s1.id;
    it given all the records, but i'm getting two ID fields (one from each table). how to avoid this. here i dont know how many fields will be there in each table. that will be known at runtime only.
    the static information is sales1 have one ID field with PK and sales2 will have one ID filed with FK.
    i need ur valuable suggestions.
    regards
    pavan.

    You can use DBMS_XMLGEN.getXML('your Query') for generating data in tables to XML format and you can use DBMS_XMLGEN.SETROWSETTAG to change the parent element name other wise it will give rowset as well as DBMS_XMLGEN.SETROWTAG for row name.
    Check this otherwise XMLELEMENT and XMLFOREST function are also there to convert data in XML format.

  • ABAP to XML file - Formatting problem and UTF-8 requirement

    Hi Everyone,
    Could you please guide us on the ABAP coding required to get the proper XML file format. We have prepared the code for downloading SAP transaction data into an XML file format. However, we are stuck with an improper format as per Example 1.
    The file format we get is this:
    Example 1:
    <?xml version="1.0"?><FDXLMDOrd><FXNHdrLp><CrtDtTm>20070613094517</CrtDtTm><MsgID>319304155</MsgID><MsgTyp>850</MsgTyp><MsgSubTyp>SALES_A</MsgSubTyp><Pr
    <RcvTP>FSCS</RcvTP><SndSrc>FXN</SndSrc><RcvSrc>EIB</RcvSrc><UsrID>VAR</UsrID></FXNHdrLp><OrdHdrLp><OrdNbr>319304155</OrdNbr><OrdActnCD>9</OrdActnCD><Ord
    teCarrReq>FDE</RteCarrReq><RteTptSvcReq>FEIP</RteTptSvcReq></DprtRteLp><SpecInstrLp><SpecInstrTyp>SHIP</SpecInstrTyp><SpecInstr>Example Packing Instruct
    les Order</RefDesc></RefLp><RefLp><RefIDQual>CPO</RefIDQual><RefID>test 1 line 1 pc - s</RefID><RefDesc>Customers Customer Purchase Order</RefDesc></Ref
    Typ><EntIDQual>91</EntIDQual><EntID>H00092</EntID><EntNm>VLAD BOBES</EntNm><Cty>MONTREAL</Cty><PstlCD>H3X 2N5</PstlCD><RgnalCD>QC</RgnalCD><CtryISOCD>CA
    ></AdrLnLp><ConLp><ConTypCD>IC</ConTypCD><ConNm>VLAD BOBES</ConNm><CommLp><CommNbrQual>TE</CommNbrQual><CommNbr>514-731-8361</CommNbr></CommLp></ConLp><
    <Cty>MONTREAL</Cty><PstlCD>H3X 2N5</PstlCD><RgnalCD>QC</RgnalCD><CtryISOCD>CA</CtryISOCD><AddlNmLp><AddlNm1>VLAD BOBES</AddlNm1></AddlNmLp><AdrLnLp><Str
    However, the format need to look like this as in Example 2 below.
    We also need help in how to get  " encoding="UTF-8"?> " as part of the file format.
    Example 2:
    <?xml version="1.0" encoding="UTF-8"?>                
    <FDXLMDProdRcpt>                                      
        <FXNHdrLp>                                        
            <CrtDtTm>20070612151817</CrtDtTm>             
            <SessID>26796</SessID>                        
            <MsgTyp>861</MsgTyp>                          
            <MsgSubTyp>WRE_A</MsgSubTyp>                  
            <PrcsingPrty>5</PrcsingPrty>                  
            <SndTPQualCD>ZZ</SndTPQualCD>                 
            <SndTP>FSCS</SndTP>                           
            <RcvTPQualCD>ZZ</RcvTPQualCD>                 
            <RcvTP>EIB</RcvTP>                            
            <SndSrc>YANTRA</SndSrc>                       
            <RcvSrc>EIB</RcvSrc>                          
            <UsrID>VAR</UsrID>                            
        </FXNHdrLp>                                       
        <ProdRcptHdrLp>                                   
            <ShpID>VAR20070612NCHIC1</ShpID>              
            <ShpTyp> </ShpTyp>                            
            <ShpActnCD>00</ShpActnCD>                     
            <InTransMrgTyp> </InTransMrgTyp>              
            <ShpVolUOM>CI</ShpVolUOM>                     
            <ShpWgtUOM>LB</ShpWgtUOM>                     
            <ShpTotVol>310022.00</ShpTotVol>              
            <ShpTotWgt>861.00</ShpTotWgt>                 
            <DtTmLp>                                      
                <DtTyp>050</DtTyp>                        
                <DtTmQual>501</DtTmQual>                  
                <DtTm>2007-06-12T15:07:41-04:00</DtTm>    
            </DtTmLp>                                     
            <AdrLp>                                       
                <EntTyp>RC</EntTyp>                       
                <EntIDQual>93</EntIDQual>                 
                <EntID>NCHIC</EntID>                      
                <EntNm>NCHIC</EntNm>                      
                <AutoCrtTrdPar>0</AutoCrtTrdPar>          
                <AutoCrtTrdParRole>0</AutoCrtTrdParRole>  
                <AutoUpdtTrdPar>0</AutoUpdtTrdPar>        
            </AdrLp>                                      
            <ProdRcptTptLp>                               
                <TptIDQual>BOL</TptIDQual>                
                <TptSCAC> </TptSCAC>                      
                <TptID> </TptID>   
    Thanks and Best Regards
    Sitaraman

    You could try to use the following coding:
    *& Report  ZUS_SDN_UC_XML_TO_UTF8_TRANSF
    REPORT  zus_sdn_uc_xml_to_utf8_transf.
    define local data
    CONSTANTS:
      gc_encoding           TYPE string VALUE 'UTF-8'.
    DATA:
      gd_result             type string,
      go_ixml               TYPE REF TO if_ixml,
      go_stream_factory     TYPE REF TO if_ixml_stream_factory,
      go_encoding           TYPE REF TO if_ixml_encoding,
      go_resstream          TYPE REF TO if_ixml_ostream.
    DATA:
      gt_knb1    TYPE STANDARD TABLE OF knb1,
    gd_xml     TYPE string,
      gt_xml     TYPE TABLE OF string.
    START-OF-SELECTION.
      SELECT * FROM knb1 INTO TABLE gt_knb1 UP TO 10 ROWS
          WHERE bukrs = '1000'.
      go_ixml = cl_ixml=>create( ).
      go_stream_factory = go_ixml->create_stream_factory( ).
      go_encoding = go_ixml->create_encoding( character_set = gc_encoding
                                            byte_order = 0 ).
      go_resstream =
                  go_stream_factory->create_ostream_cstring( gd_result ).
      CALL METHOD go_resstream->set_encoding
        EXPORTING
          encoding = go_encoding.
    XML Transformieren
      CALL TRANSFORMATION id_indent
        SOURCE     itab = gt_knb1
        RESULT XML go_resstream.
      APPEND gd_result TO gt_xml.
      CALL METHOD cl_gui_frontend_services=>gui_download
        EXPORTING
         BIN_FILESIZE              =
          filename                  = 'C:\temp\xml_to_utf8.txt'
         FILETYPE                  = 'ASC'
         APPEND                    = SPACE
         WRITE_FIELD_SEPARATOR     = SPACE
         HEADER                    = '00'
         TRUNC_TRAILING_BLANKS     = SPACE
         WRITE_LF                  = 'X'
         COL_SELECT                = SPACE
         COL_SELECT_MASK           = SPACE
         DAT_MODE                  = SPACE
         CONFIRM_OVERWRITE         = SPACE
         NO_AUTH_CHECK             = SPACE
         CODEPAGE                  = SPACE
         IGNORE_CERR               = ABAP_TRUE
         REPLACEMENT               = '#'
         WRITE_BOM                 = SPACE
         TRUNC_TRAILING_BLANKS_EOL = 'X'
       IMPORTING
         FILELENGTH                =
        CHANGING
          data_tab                  = gt_xml
        EXCEPTIONS
          file_write_error          = 1
          no_batch                  = 2
          gui_refuse_filetransfer   = 3
          invalid_type              = 4
          no_authority              = 5
          unknown_error             = 6
          header_not_allowed        = 7
          separator_not_allowed     = 8
          filesize_not_allowed      = 9
          header_too_long           = 10
          dp_error_create           = 11
          dp_error_send             = 12
          dp_error_write            = 13
          unknown_dp_error          = 14
          access_denied             = 15
          dp_out_of_memory          = 16
          disk_full                 = 17
          dp_timeout                = 18
          file_not_found            = 19
          dataprovider_exception    = 20
          control_flush_error       = 21
          not_supported_by_gui      = 22
          error_no_gui              = 23
          OTHERS                    = 24.
      IF sy-subrc <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    END-OF-SELECTION.
    However, I like to mention that the file created from out ECC 5.0 (6.40, non-Unicode) contains a special character between the XML header and the data part (when displayed using NotePad Editor):
    ...xml version="1.0" encoding="utf-8"?>[special character]<asx:abap xmlns:asx="http://www.sap.com/a...
    Using a HexEditor the special character (0x0A) is displayed as a dot.
    Also Check with FM - TREX_TEXT_TO_UTF8
    Reward Points if it is helpful
    Thanks
    Seshu

Maybe you are looking for