Generation of DME file in FI_CO

Hi all,
I have a requirement to generate dme file for singapore with three record sturture namely - header record, detail record, trailer record. can anyone please tell me what is the standard program which generates such kind of file format.
Please help. Its urgent.
Edited by: srinivas kodukula on Aug 7, 2008 5:12 PM

Hello Rob,
thanks for your reply.
Yes I did a check of the OSS notes and I found that OSS 1365764 (Pls see below) describes exactly the problem I have but it is relevant only for payments and DME files created with this purpose.
Also the DCP parameter (that has to be specified at user level) is only relevant for RFFO* programs.
Note 1365764 - Codepage of DME file
https://service.sap.com/sap/support/notes/1365764
Also the two following notes
Note 911190 - PMW: Entering the code page when writing and downloading
https://service.sap.com/sap/support/notes/911190
Note 899205 - RFUMSV00: DMEE format tree with additional parameters
https://service.sap.com/sap/support/notes/899205
So to be honest I do not really know how to look at to solve the issue.
Thanks again for your reply & best regards
Tony
Edited by: Antonio Lanza on Nov 9, 2010 9:33 AM

Similar Messages

RFUMSV00 (Tax report) wrong generation of DME file in Unicode system

Hello gurus,
I've a problem running the program RFUMSV00 (Advance Return for Tax on Sales/Purchases) transaction S_ALR_87012357 when "Create DME file" check box is selected and a format tree and a file name are specified.
On 4.7 it was working properly but now on ECC6.0, that is unicode compliant, does not work correctly because each char of each field on the downloaded table into Unix directory has preceeded by an hash (#).
So 1234 becomes #1#2#3#4...
The problem seems to be related to codepages and I found in debug that the RFUMSV00 program calls from the include I_RFUMS_DME_FORMS the following routine at line 119: PERFORM write_file_to_system USING lt_dme_file.
This form contains a call to the following function:
    CALL FUNCTION 'FI_PAYM_FILE_OPEN'
              EXPORTING
              i_temse_name = par_tems
              i_file_name = l_file_name.
without specifying the codepage as further parameter so the function open the dataset for output in binary mode (and here the problem) because i_codepage is initial
Pls see below.
    IF i_codepage IS INITIAL.
      OPEN DATASET i_file_name FOR OUTPUT   "Open File to write
                               IN BINARY MODE.
    ELSEIF i_codepage = '4110' AND
           cl_abap_char_utilities=>charsize > 1. " UTF-8 and Unicode
      OPEN DATASET i_file_name IN TEXT MODE FOR OUTPUT
                                       ENCODING DEFAULT.
    ELSEIF i_codepage = '4102' OR i_codepage = '4103' OR i_codepage = '4110'.
      OPEN DATASET i_file_name FOR OUTPUT
                               IN BINARY MODE.
    ELSE.
      OPEN DATASET i_file_name FOR OUTPUT   "Open File to write
                               IN LEGACY BINARY MODE
                               CODE PAGE i_codepage
                               IGNORING CONVERSION ERRORS.
Putting '4110' on i_codepage all is working magically perfect.
Does anybody know where set the code page (4110) or how to solve this problem ?
Thanks a lot in advance & best regards
Tony

Hello Rob,
thanks for your reply.
Yes I did a check of the OSS notes and I found that OSS 1365764 (Pls see below) describes exactly the problem I have but it is relevant only for payments and DME files created with this purpose.
Also the DCP parameter (that has to be specified at user level) is only relevant for RFFO* programs.
Note 1365764 - Codepage of DME file
https://service.sap.com/sap/support/notes/1365764
Also the two following notes
Note 911190 - PMW: Entering the code page when writing and downloading
https://service.sap.com/sap/support/notes/911190
Note 899205 - RFUMSV00: DMEE format tree with additional parameters
https://service.sap.com/sap/support/notes/899205
So to be honest I do not really know how to look at to solve the issue.
Thanks again for your reply & best regards
Tony
Edited by: Antonio Lanza on Nov 9, 2010 9:33 AM

DME File generation

Hi Guru's
I am having a small problem in generation of DME file after F110 is done.
Once the F110 has been run successfully and the Payment has been carried out, we can generate a DME file from Environment-->Payment medium--->DME Administration, there is also T code (I don't remember the T code)
I could see the reference no. etc in REGUT table also , but I couldn't see or generate the DME File
I am getting the following error "There is no source for this data record" Error no :FZ205
Can any one help me out in generating the file
Regards
VSK

Dear
thanks for the quick response, One small doubt
I have recreated a Pmt medium thru the program"SAPFPAYM",... i have got a new window saying that posting orders generated , completed
My doubt is that should we delete the previous entry because the 1st window is showing me the generated lines...
I have not deleted, and am still getting the same error message...
Any pointers in this regard
Regards
VSK

Regarding problem with new line feed for DME file generation

Hello Experts,
I m facing a problem in the DME file generation.
we want each record in the DME file should be in new line. for that we have add the new line feed character in the each row end. So in the SAP output it looks ok, But if we download that file the carriage return field is coming in the end of every row.
can any one tell how to solve this issue.
Please refer the below line code which i m using for new line
DATA: GM_newline TYPE c VALUE cl_abap_char_utilities=>CR_LF
You reply is valuable..
Thanks,
Suresh

DATA: GM_newline TYPE c VALUE cl_abap_char_utilities=>newline.

Problem in DME file generation

Hi experts,
I am facing a problem in the generation DME file. Required file format for SPAIN is different to that of the standard file that is generated by executing the standard program RFFOES_T. So I copied that standard program into another and made changes for the new file format in the subroutine DTA_SPANIEN. The file is being generated but with systematically 7 white lines (i.e) blank lines between 2 real lines. Cannot find where the problem lies. Can any one help me in this? Thanks in advance.
Regards,
Asha

Hi Calsadillo,
The below code says how I have passed the different records to the file
types: begin of t_file,
         record(1000),
       end of t_file,
     begin of t_h1,
       rec(2),
       trans(2),
       field1(10),
       crtd(6),
     end of t_h1,
     begin of t_h2,
       rec(2),
       trans(2),
       paynm(6),
     end of t_h2,
     begin of t_h3,
       rec(2),
       trans(2),
       payadd(35),
       filler(2),
       field2(40),
     end of t_h3,
     begin of t_h4,
       rec(2),
       trans(2),
       matdat(6),
       deltype,
       contype(2),
       filler(7),
     end of t_h4.
data : lwa_h1 type t_h1,
       lwa_h2 type t_h2,
       lwa_h3 type t_h3,
       lwa_h4 type t_h4,
       lwa_file type t_file.
data : li_file type standard table of t_file.
*Start Filling Record 1
      l_count        = l_count + 1.
      lwa_h1-rec     = lc_03.
      lwa_h1-trans   = lc_56.
      lwa_h1-field1 = t001z-paval.
      lwa_h1-crtd = '0000000O02XR'.
      lwa_file       = lwa_h1.
      APPEND lwa_file TO li_file.
*Start Filling Record 2
      l_count       = l_count + 1.
      lwa_h2-rec    = lc_03.
      lwa_h2-trans = lc_56.
      lwa_h2-paynm = t001-butxt.
      lwa_file      = lwa_h2.
      APPEND lwa_file TO li_file.
*Start Filling Record 3
      l_count       = l_count + 1.
      lwa_h3-rec    = lc_03.
      lwa_h3-trans = lc_56.
      lwa_h3-payadd = adrc-city1.
    lwa_h3-filler    = lc_06.
      lwa_file      = lwa_h4.
      APPEND lwa_file TO li_file.
*Start Filling Record 4
      l_count       = l_count + 1.
       lwa_h4-rec    = lc_03.
      lwa_h4-trans = lc_56.
      lwa_h4-matdat = lc_030.
      lwa_h4-deltype    = lc_004.
      lwa_h4-contype    = lc_003.
      lwa_file      = lwa_h3.
      APPEND lwa_file TO li_file.
OPEN DATASET par_unix FOR OUTPUT IN LEGACY TEXT MODE
                                IGNORING CONVERSION ERRORS.
IF sy-subrc IS INITIAL.
    LOOP AT li_file INTO lwa_file.
      TRANSFER lwa_file TO par_unix.
    ENDLOOP.
    CLOSE DATASET par_unix.
ENDIF.
where par_unix is the file name entered on the selection screen.
Now where can i fit the two declarations of code which you have sent? Can you please explain.
Regards,
Asha

DME File Generation for Thailand

Hi Gurus,
I would like to know which DME File format is using for Thailand.
I need to generate DME file for the Thailand country format while running APP F110.
Thanks in Advance.
Pavan

Hi,
If you are using PMW for DME generation than please go to DMEE transaction code and in tree property node at File Data tab select radio button 'Allow Only These Charact.' and don't specify this characters in the field against Character Definition.
For blank space control it with Length and Conv. function in the segment definition.
Regards,
Anand Raichura

DME file generation in APP

Hi All,
Can you tell me, how i can generate DME file after APP run, what program should i use for this and are there any other specific settings required to generate

Hello,
Follow the below step,
1) Create a structure in the transaction code DMEE
2) Assign the DMME structure in the payment method by conuntry in FBZP
3) Create the payment medium Formats with the same name as given in the DMEE structure ( PATH : AP - Business transaction - outgoing payment - automatic outgoing payment - payment media - make settings for payment medium from payment medium workbench - create payment medium formats)
4) create a variant for the DMEE structure you created (Select the DMEE you created and create a new variant)
5) Then execute the F110
based on the above config and settings, DME file will be generated.
Hope this clarifies.
Raja.A

Query regarding the conversion of DME file in MT940 format.

Hello Experts,
I have a query regarding the generation of MT940 file after generating the payment file from other DME tree.
After completion of payment run, my payment file is generated in the DME format which is according to the DME tree.
I want to convert the DME file (which is generated via F110) from existing format to the standard MT940 format.
Is there any standard program which converts the DME file to MT940. If so, please inform me as early.
I have tried to upload the DME file in FF.5 transaction, but it is not allowing me to convert the file in MT940 structure.
Or please inform the steps how i can convert the file .
Awaiting for your inputs.
Thanks in advance

Hi Zareena.
I would like to suggest,
SX_OBJECT_CONVERT_RAW_TXT.
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

DME File not Generating

Hi Experts,
Is there any authorization required for the generation of the DME file after we run the automatic payment program?.
1. The open line items are cleared once the APP is run.
2. checked for the dme file using the AL11, But no files has been created.
Note I have used the payment method S - SWIFT payment
Regards
TSR

Hi,
I see that you are using PMW format and you have mentioned that you use program RFFOAVIS_FPAYM. Please note that this program creates payment advice notes for payments created using the Generic payment medium program SAPFPAYM.
Please use program SAPFPAYM to create payment medium file.
There are 2 types of output medium that can be used 1) File system 2) Temse
In se38: sapfpaym, use the correct variant, once the Payment medium format is entered, check the Output Control section, here you have an indicator "Output to File System", check the F1 help of this field. If you enable this indicator then File is created on application server path specified. Else file is created and stored with SAP
TemSe in the SAP System (file for storage of temporary sequential data).
Hope this helps. Let me know if this information was useful.
Kind Regards
Soumya

Automatic Payment using DME file in India

Hello Gurus,
May i know the configuration for DME file generation for Out going Payments to Vendors in India.
Cheers!
SK

Hello
When configuring the payment methods for the country (transaction OBVCU), choose the payment medium program as RFFOM100.
From se38, pls read the documentation for the program, which will give you the various options & the required config too.
You would also need to configure the instructions keys as required.
To generate the DME file, you have to run the automatic payment program with this payment method.
After the payments have been successfully posted, you can go to DME administration and with the help of dme manager download files on your PC.
SAP has determined that the standard print programs for automatic payments will no longer be supported, and will be replaced by transfer structures created by a tool called the DME Engine.
This tool enables the business to create DME output files without ABAP development, and can be attached to a print program and form for the creation of Payment Advices.
Outside of the DME Engine (DMEE), the majority of the configuration takes place within the following IMG menu path:
IMG Path: Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Payment Media -> Make Settings for Payment Media Formats from Payment Medium Workbench
Config
Assign Selection Variants
IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Payment Media -> Make Settings for Payment Medium Formats from Payment Medium Workbench -> Create / Assign Selection Variants or transaction
OBPM4..select your format that you are using
Check in FBZP config that all is linked!
Although this is bitty but you need to work through it!
Start with FBZP, create all there than go to DMEE either to create your own format or use the standard ones.. than go to the menu path above and work through from create to assign...
Reg
Suresh

DME file creation for APP

Hi all,
my client needs to do the payments for vendors in electronic format. for this i know only for electronic payments we use file DME.
How we create DME file in F110? and how this file fits for bank given specification? after payments made from bank (sending this file to bank and bank will pay) how the bank file we upload and post?
kindly send me any docs regarding config.of DMEE and upload also.
Thanks in advance,
i will assure points.
Soma

Dear Soma,
For DME file generation you need to first make the set up in SPRO and then while running the printout in F110, it will get generated. Then you can doenload the fle from FDTA and can upoad it to bank site.
The standard documentation on this from SAP is:-
http://help.sap.com/erp2005_ehp_03/helpdata/EN/cb/4104aadf2b11d3a550444553540000/frameset.htm
Regards,
Gaurav

DME file encryption

Hi experts,
We have DME developments for our project and right now we are using Payment Medium Workbench(PMW) method for generating DME files and in this method, the file is being generated and stored it in the Presentation server(User PC).
Our requirement is we need to encrypt the DME file while generation and it needs to be stored in the Presentation server. Please suggest us whether it is able to acheive it in the PMW.
Regds,
Uma

Hi,
1. File transport.
Anyway DME file in only Presentation server as a text file.
Use FM --> GUI_UPLOAD get the data to Internal table and
use FM --> DX_FILE_WRITE Pass the itab and app. file path create file to appication server.
OR
Run BDC for CG3Z
Like below code
data : t_bdcdata type table of bdcdata,
       w_bdcdata type bdcdata.
clear : w_bdcdata, t_bdcdata.
w_bdcdata-program = 'SAPLC13Z'.
w_bdcdata-dynpro = '1020'.
w_bdcdata-dynbegin = 'X'.
w_bdcdata-fnam = 'RCGFILETR-FTFRONT'.
w_bdcdata-fval = w_wrk_string.
append w_bdcdata to t_bdcdata.
w_bdcdata-program = 'SAPLC13Z'.
w_bdcdata-dynpro = '1020'.
w_bdcdata-dynbegin = 'X'.
w_bdcdata-fnam = 'RCGFILETR-FTAPPL'.
w_bdcdata-fval = w_g_efile_a.
w_addparam = w_g_efile_a.
append w_bdcdata to t_bdcdata.
w_bdcdata-program = 'SAPLC13Z'.
w_bdcdata-dynpro = '1020'.
w_bdcdata-dynbegin = 'X'.
w_bdcdata-fnam = 'RCGFILETR-IEFOW'.
w_bdcdata-fval = 'X'.
append w_bdcdata to t_bdcdata.
w_bdcdata-program = 'SAPLC13Z'.
w_bdcdata-dynpro = '1020'.
w_bdcdata-fnam = 'BDC_OKCODE'.
w_bdcdata-fval = '=EIMP'.
append w_bdcdata to t_bdcdata.
w_bdcdata-program = 'SAPLC13Z'.
w_bdcdata-dynpro = '1020'.
w_bdcdata-fnam = 'BDC_OKCODE'.
w_bdcdata-fval = '=ECAN'.
append w_bdcdata to t_bdcdata.
call transaction 'CG3Z' using t_bdcdata mode 'E'.
Same way for CG3Y.
2. Encryption Part.
data : l_encrtpt_ap type sxpgcolist-parameters.
data : l_econst(1) type c value 'E'.
data : w_addparam type sxpgcolist-parameters,
       w_finalencrpt type string,
       t_chkfile1 like btcxpm-message.
data : w_status like extcmdexex-status.
data : w_exitparam like extcmdexex-exitcode.
data : t_exec_protocol like btcxpm occurs 0 with header line.
*w_addparam = Appication server TXT file path Name. *F\PROJECT\text_file.txt
*w_finalencrpt = Appication server ENC file (Encrypted file path name)
* F\PROJECT\encrypted_file.txt
* t_chkfile1 = 32 digit key code (checksum code)
*              Example #978708gflkorluf96moldglfj0lhop9#
* w_status = space (No value).
* w_exitparam = space (No value).
* t_exec_protocol = space (No value).
w_addparam =    'F:\usr\sap\EED\DVEBMGS00\work\TESTDURAI123.txt'.
w_finalencrpt = 'F:\usr\sap\EED\DVEBMGS00\work\TESTDURAIENC.txt'.
t_chkfile1 = '978708gflkorluf96moldglfj0lhop9D'.
concatenate l_econst w_addparam w_finalencrpt t_chkfile1
                   into l_encrtpt_ap separated by space.
call function 'SXPG_COMMAND_EXECUTE' destination 'devr3_EED_00'
    exporting
      commandname                = 'XWIZSTOP'
      additional_parameters      = l_encrtpt_ap
    importing
      status                     = w_status
      exitcode                   = w_exitparam
    tables
      exec_protocol              = t_exec_protocol
    exceptions
      no_permission              = 1
      command_not_found          = 2
      parameters_too_long        = 3
      security_risk              = 4
      wrong_check_call_interface = 5
      program_start_error        = 6
      program_termination_error = 7
      x_error                    = 8
      parameter_expected         = 9
      too_many_parameters        = 10
      illegal_command            = 11
      others                     = 12.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*Here ZCRYPTOBJECT is commend name in SM49.
*Result : Encrypted file generated to application server in w_finalencrpt file name
*        I.e. F\PROJECT\encrypted_file.txt
*Here Without generated the checksum key we Encrypted the file
*we hard code the checksum key.
*if u want to genereted the checksum code defined on file.
*there we can use SXPG_CALL_SYSTEM function module
<REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
Thanks,
Durai.V
Edited by: Alvaro Tejada Galindo on Aug 21, 2008 3:19 PM

F110S runs for a long time to produce DME file

A batch job schduled for "daily payment run + creation of DME files" using F110S (SAP ECC 6.0) . The batch is running in production for more than 20 hours to process payment against just single invoice.
The job runs in following 2 steps
1. SAPF110S which processes the payment clears FBL5N.
2. SAPFPAYM_SCHEDULE.
The second step seems a non-ending process.
The job variant has only 15 customers, only one invoice is to be processed against one account.
However in quality system the same job with more than 10,000 customer account range with more than 10 invoices runs just in few minutes.
Any idea or suggestion why it's taking so long in production? Any missing configuration in production server?

It's not performance issue. When we run F110S or F110 in production with individual login id, program runs the way it should and finishes in reasonable time (for example the scenario I described in question finsihes in few seconds).
The problem occurs only when production batch job runs with job scheduler; program seems looping somewhere for infinite time - to be particular it keeps reading the table TPRI_DEF which has just few records (must be reading this table inside a loop).

DME file in XML format in SAP 4.6C

Hi Experts,
For a Belgium client, I have a requirement to generate DME file in XML format for payments made to foreign and domestic vendors. I want to know the following,
1. Can DME file be generated in XML format using classic payment medium programs RFFOBE_E and RFFOBE_I.
2. If not why and what are the other options.
3. I also came to know that there is an options of using Payment medium workbench - through XML format trees BE_BEPDTA and BE_PIBDTA. But since we are in 4.6C, i am not able to create a payment format. Is there any support package or patch that is required.
4. I tried for SEPA_CT - again a XML format tree but was not very successful as that too was not available in SAP 4.6C. Is there any way that I can get this done in 4.6C - any support packages or patches available?
Thanks

Hi Kaylan,
could you please share that documentation with me too.
Thanks, Regards,
Alex Cardona

F110 - How to prevent multiple creation of DME file?

Hello,
I need to prevent multiple creation of DME file for the same Payment Run (after it has been created once).
"Printout" bottom creates DME file and Payment Advice any time you trigger it.
I'm searching for some User Exit / BAdi / Function that will help me to add ABAP code that will check if DME file has already been created.
Thank You in Advance

Hello,
Please check if the flag "Create payment medium" is not flagged at the proposal and the payment run file.
If it is flagged the payment file will be generated. Also when you press the print out button, the print program will be called and the system will try to created a new payment file.
In order to avoid duplicated payments you should consider using the flag 'Payment Document Validation" in your print program.
If the 'Payment Document Validation' parameter is not set ON, documents already processed for payment can be selected and paid again in a subsequent payment run, when posting terminations have occurred.
Please refer to SAP Knowledge Base Article 1713825 in order to activate Payment Document Validation.
Another option is to suppress the"Create Payment Medium" flag at Proposal Run.
In this case you should check the following information:
Please restrict the activity 15 of object F_REGU_BUK in the user
profile/role
You may also refer to the available activities on this:
- 02 Edit parameters
- 03 Display parameters
- 11 Execute proposal
- 12 Edit proposal
- 13 Display proposal
- 14 Delete proposal
- 15 Create payment medium proposal
- 21 Execute payment run
- 23 Display payment run
- 24 Delete payment run payment data
- 25 Create payment media of payment run
- 26 Delete payment orders of payment run
- 31 Print payment medium manually
Kind Regards,
Fernando Evangelista

Generation of DME file in FI_CO

Similar Messages

Maybe you are looking for