Skip to Content

As you probably know, a new legal requirement apply in Spain, with this blog we want to give you an FAQ space regarding this legal change as well as some guidelines about the implementation of it.

MODEL 340

What is Model 340?

Is a new file for  Electronic VAT books (Llibro registro de facturas recibidas -IVA soportado- , facturas emitidas -IVA repercutido- en formato electrónico)

 

Are all Spanish Customers obliged to report model 340 to the Tax Authorities?

 

Not all in 2009. But customers that want to benefit from the new monthly devolution practice from the Spanish Tax Authorities, must use Model 340.(The legal text is “Real Decree 1065/2007 as of July 27th 2007 published the 5th of  September 2007”)

 

More details regarding this law can be found in the following link :

http://www.agenciatributaria.es/AEAT/Contenidos_Comunes/La_Agencia_Tributaria/Normativas/Ficheros_Asociados_a_Las_Normativas/IVA/REAL_DECRETO/Real%20Decreto%201065-2007.pdf

Which is first due date to present first model 340?

20.02.2009.

 

Is it technically necessary to use VAT DATE in order to be able to obtain model 340?

No. If you do not use VATDATE function, you have to apply note 1303567.

In that case, the file VATDATE will be filled with zeroes.

 

What to do to obtain model 340?

New report RFIDESM340 has been developed to obtain model 340.

 

Relevant notes to apply :

 

-Note  1292521 “Legal change on Modelo 340: Electronic VAT books”

Please make sure you performed all the manual activities of the note,

before implementing the correction instruction attached in note 1292521

and read carefully all documents attached to this note.

To  avoid  problems with some objects caused by wrong transport layer, it is very important to do as indicated in  Pag. 2, section “Create package” of document “User Manual Modelo-340V4.doc”

 

-Note 1302260  “Modelo-340 Legal Change Additional Correction”

Perform the manual activities described in this note.

Implement the correction instructions by support package or SNOTE  activities described in this note.

 

-Note 1304247 “Transaction Code for the report RFIDESM340”

Perform the manual activities described in this note.

 

-Note  1303567 “Addition of field “VATDATE” to structure”

Only if customers do not use VATDATE  function yet , they should to apply note 1303567: in this case, the file VATDATE will be filled with zeroes.

 

Further functional information and a very useful guidelines can be found in the SAP Note 1304756

VAT DATE

 

What is VAT DATE?

 

A new field VAT DATE has been added to the fi-document header

table BKPF, and additionally to BBKPF, VBKPF, RBKP, ACCIT, to fill new legal requirements in some countries, to have a specific tax due date

(In Spanish it is “Fecha de operación”)

 

Are Spanish Customers obliged to use VAT DATE?

Yes.

This is a legal requirement, mandatory as of 01.01.2009

(the legal text  is “REAL DECRETO 1466/2007 FECHA REALIZACIÓN DE LAS OPERACIONES Y LOS LIBROS REGISTROS”)

 

What to do to use VAT DATE?

Notes relevant for Spanish customers to use the VAT DATE function

 

-Note 1023317 “Legal Change: Vat Due date” (Note valid for releases Releases ERP 2005 y ERP 2004)

 

Important remark: You cannot implement this note by SNOTE.

The functionality can only be implemented by applying the support package because many DDIC-changes, 2 new BADIs, screen changes,    logical database changes (BRF), many text elements of reports,  DDIC-objects, messages and many program changes, and so on, are    involved.”

What to do with Note 1023317?:

You  have to upgrade to the relevant support for the current release ( the  note is properly updated with a list of support package-release)

 

Note 1235415: This note constitutes the downport of note 1023317 to release 4.6C and  4.70.

 

Note 1232484 “How to use the VAT due date, tax reporting”

What to do with Note 1232484?: This is a describing note.

Read carefully the PDF document attached to this note

Follow the points for a step by step instructions

 

Note 1038448  VAT due date: Country specific Reporting

This note changes some reports, and provides a migration tool for

documents that were posted before activation of the  VAT DATE  function.

What to do with note 1038448?:

First: note 1023317 has to be implemented (by support package).

Second: the manual activity described in the note

Third: Implement the correction instructions by support package or SNOTE.

 

Note 1281852 “Legal change on VAT”

This note modifies reports RFUSVS14, RFASLD11B, RFKORDES to use the VAT DATE

What to do with Note 1281852?

perform the manual activities described in this note.

Implement the correction instructions by support package or SNOTE  activities described in this note.

To report this post you need to login first.

63 Comments

You must be Logged on to comment or reply to a post.

  1. Felipe Yagüe Nodal
    I think I have implemented the main two notes for modelo 340 (1292521,1302260 ) but I am having serious problems to get the report runing:

    1 – The selection parameters in program RFIDESM340, in the include RFIDESM340_SELECTION are commented. As you can see in it the begining of the selection screen is:
    *&———————————————————————*
    *&  Include           RFIDESM340_SELECTION
    *&———————————————————————*

    SELECTION-SCREEN BEGIN OF BLOCK 6 WITH FRAME TITLE text-106. “#EC *
    *PARAMETERS:
    *  BR_BUKRS TYPE BKPF-BUKRS OBLIGATORY.
    *SELECT-OPTIONS:
    *  BR_BELNR FOR BKPF-BELNR,
    *  BR_GJAHR FOR BKPF-GJAHR OBLIGATORY,
    *  BR_BUDAT FOR BKPF-BUDAT OBLIGATORY,
    *  BR_XBLNR FOR BKPF-XBLNR.

    By this code there is no option to select the company, the year, the posting date….

    2 – In the badi: RFIDES_TAX_BADI_016 (end of selection) with the modifications introduced by the note 1292521 there is a call function to ES_REMOVE_SPECIAL_CHARACTER. That function is not implemented in my system (4.6c), where is its implementation?

    3 – In the same badi there is a condition which says: IF header-model_340 = ‘X’.
    this condition starts the processing of model_340 but this field header-model_340 is always initial, i need to modify it manually in order to go into the implemented processing of model340.

    I have another problems but they are minor. Hope this can help anybody or anybody can help me. Thanks in advance.

    Felipe Yagüe.
    S.A. MIRAT
    SALAMANCA
    felipe@mirat.net

    (0) 
    1. Rafael Fernandez
      Hello Felipe,

      about your first problem, we have the same one and we have solved it with the logical data base BRF wich have to be filled in the attributes of the program RFIDESM340. With this action, the program takes the selection criteria defined into the logical database. We wrote to SAP and they explain to us this action and it works.

      Hope it can help you.

      best regards,
      Toni

      (0) 
  2. DEL PINO VALDERRAMA
    After reading this blog, I continue still having a doubt.
    If I do not want to work with the date VATDATE, because with my case the date of invoice and expedition they coincide.

    I can execute the program, without need to apply the note 1023317. Because at this moment to apply this note implies raising the suppor package with everything what it implies.

    I have executed the program RFIDESM340 and at the moment it has not given me mistake, but it  does not select records in the file of exit.

    Thank yout

    (0) 
    1. Felipe Yagüe Nodal
      Maybe the problem is the same than the one of the order person over you. The program is not going into the concrete executing of model_340. Debug the badi and be sure that after importing structure HEADER, the field header-model_340 is ‘X’ as it should. In my 4.6c, it isn´t and I need to check it manually. I am going to explain my problem in another post to see if it is what also you suffer. Good luck!
      (0) 
  3. Bernadette GL
    After implementing this OSS note, we are able to execute the report RFIDESM340, and it displays several line items.  But after executing report RFASLDPC the downloaded file is empty.

    What do you think is wrong with the report?

    (0) 
    1. Felipe Yagüe Nodal
      Hello, you should try to have a look at the file prior to download to your pc, have a look in the server to know if it is empty or not. If it is empty maybe the problem is that you are not executing the changes for model 340 in badi. I need to check the field header-model_340 in the badi manually in debugging mode to get the program running througth the new requirements. Maybe you are seeing in the screen the vat books but not the 340 model.
      (0) 
  4. Teresa Lorite Post author
    After you apply corrections instructions of note 1292521, you might find some discrepancies between changes made in your system, and the manual “Manual Modelo-340V4.doc”, regarding:
    -Messages numbers created
    -The character length of OPRKEY

    Changes made by correction instruction from note 1292521 are the right ones.

    I have been informed that attachment “Manual Modelo-340V4.doc” in note 1292521 will be modified accordingly in short.

    (0) 
  5. Felipe Yagüe Nodal
    Hello! I am having another problem in model 340, i hope and i think this is the last one. The structure header is defined in RFIDESM340_DATA and exported to memory in order to be used by BADI_016 in RFIDEMS340_MAIN. In the definition the field CLRF is 4 characters long:
    clrf(4) type x value ‘0D0A’.

    Later when processing the BADI the structure is defined not in the same way because the field CLRF is defined with 2 bytes:

    clrf(2) type x.

    When importing the structure in the BADI the two fields in the structure after clrf which are model_340 and file_name are bad imported:
    – model_340 is initial instead of ‘X’ as it was when exported to memory.
    – file_name is the name I entered in the selection screen but before the name it has two characters: ## . Example: ##file.txt

    Modifying the definition of structure in the badi solves the problem but i think SAP should show a correction about this problem. After this modify the report and the file are ok.

    FElipe Yagüe.
    SALAMANCA
    ESPAÑA

    (0) 
  6. DEL PINO VALDERRAMA
    Hello all.

    I hope that someone could help me.

    I am not going to work with the date VATDATE.  Can I then obtain the file 340 without applies the note 1023317?

    The note applies 1023317 it forces me upgrade the new suppor package ,so I need to validate all my processes and do not have time in this moment.

    thank you

    (0) 
    1. Felipe Yagüe Nodal
      Yes you can obtain model 340 without using VATDATE. I am working in that way. No need to install note 102337 (at least I haven´t). I think if you apply note 1302260 you are able to obatin model 340 but in the file you will need to put some date in the correspondinf field of “fecha de la operación”. I have modified the report in order to copy budat into vatdate.
      Hope helps.
      (0) 
      1. DEL PINO VALDERRAMA
        thank you Felipe.

        Your explanation is very useful.
        I have executed the program RFIDESM340, it generates the file but only with the record of head (type 1).

        I don’t know , why not select  any invoice’s record.

        Can it be for the parametrización of the table ES34_PRKEY?

        are you modifying the report RFIDESM340 to complete this VATDATE field?.

        Have you created a new program ZRRFIDESM340?

        (0) 
        1. Bernadette GL
          We have the same problem.  We got an error on VATDATE.  We were given the instruction to implement OSS 1302260.  and after this, we got an error on “BR_BUKRS”.  We are again instructed to set “Logical Database” as “BRF”.  After these correction, we are now able to execute program RFIDESM340.  However, just like you, it generates the file but only with the record of head (type 1).  Its not selecting any invoice’s record.

          I am still awaiting SAP’s reply to my OSS message.  But has anyone here encountered the same problem?  Thanks.

          (0) 
        2. Felipe Yagüe Nodal
          Hello again! Asking your question:

          1 – Although you haven´t introduced anything in table ES340_PRKEY you should get your file with type 2 records.
          2 – I am modifying the program to complete the VATADATE field instead of with VATDATE field with BUDAT field and it goes OK.
          3 – I thought about it but finally I didn´t, the modifies are very little so I made them in the original.

          I think you should debug the RFIDES_TAX_BADI_016 to verify that when checking field HEADER-MODEL_340, the value of the field is ‘X’. Because is the entry for the model 340 processing. This if condition is in line 220 more or less and it is:

          IF header-model_340 = ‘X’.

          Have a look at this.

          Hope helps.

          (0) 
          1. DEL PINO VALDERRAMA
            hello Felipe.

            I have verified the rfides_tax_badi_016 badi again. The package-name = ‘ID-FI’ , and the manual says than package-name must be ‘ID-FI-ES’.
            So I have deleted the rfides_tax_badi implementation  and  I have created it again.

            !!! and surprise !!!!

            ALREADY  IT ME WORKS.

            Although the package-name still is ‘ID-FI’, because it’s the default value and I don’t know how change it.

            (0) 
  7. Vicente Esteras Esteban
    Hello,

    We are in 4.6C.
    RFIDESM340 call the report RFUMSV00, that shows many lines to include in the file.
    But this report (RFUMSV00) doesn’t export to the correct place and no information is recovered.
    The file created has only the header information, without any value.

    (0) 
    1. Wolfgang Wauer
      Hello Vicente,
      did You found the error of Your Problem?

      I found it Yesterday: In RFIDESM340 and in the BADI RFIDES_TAX_BADI_016 the Structure “HEADER” is different. This is used for EXPORT/IMPORT of Header Data.
                crlf(4)     TYPE x VALUE ‘0D0A’,
      and
                crlf(2)     TYPE x VALUE ‘0D0A’,

      is the Problem. May be only in 4.6C. And there is no Note about this.

      Regards, Wolfgang

      (0) 
  8. Vicente Esteras Esteban
    Hello,

    We are in 4.6C.
    RFIDESM340 call the report RFUMSV00, that shows many lines to include in the file.
    But this report (RFUMSV00) doesn’t export to the correct place and no information is recovered.
    The file created has only the header information, without any value.

    (0) 
  9. Teresa Lorite Post author
    Right package for  RFIDES_TAX_BADI_016 is ID-FI.                                   

    No need to change it to ID-FI-ES

    I have been informed that attachment “Manual Modelo-340V4.doc” in note 1292521 will be modified accordingly in short.

    (0) 
  10. Luis Serra Batlles
    Tenemos parametrizado el Recargo de equivalencia en la tabla “es340_oprkey”, indicandole “eqvtxc” = “YES” y “ktosl” = “ESA”.  ¿POR QUÉ NO NOS GENERA EL RECARGO DE EQUIVALENCIA EN EL MISMO REGISTRO DEL FICHERO, SINO QUE NOS GENERA OTRO REGISTRO ADICIONAL? 

    Gracias anticipadas,

    Joana,

    (0) 
  11. Luis Serra Batlles
    Tenemos parametrizado el Recargo de equivalencia en la tabla “es340_oprkey”, indicandole “eqvtxc” = “YES” y “ktosl” = “ESA”.  ¿POR QUÉ NO NOS GENERA EL RECARGO DE EQUIVALENCIA EN EL MISMO REGISTRO DEL FICHERO, SINO QUE NOS GENERA OTRO REGISTRO ADICIONAL? 
    (0) 
  12. Teresa Lorite Post author
    Introducing a value for Electronic  Code for VAT Return  (E_SEAL) in the general selection criteria for report RFIDESM340 might not lead to the desired result of filling this value in the output from report execution.

    A new note will be released regarding “Electronic  Code for VAT Return” and RFIDESM340.

    Meanwhile, you can do as follows:
    1. Go to transaction SE38
    2. Enter RFIDESM340
    3. Press the “Change” button
    4.Search for the following line  in the  include “RFIDESM340_MAIN”

         header-file_name = par_file.
      header-model_340 = ‘X’.

    5.Add the following line after  header-model_340 = ‘X’.

    header-eseal = E_SEAL.  “Changed By SAP

    6.After making the changes,it will look like following :

      header-file_name = par_file.
      header-model_340 = ‘X’.
      header-eseal = E_SEAL.  “Changed By SAP

    7.Activate the report RFIDESM340.

    (0) 
  13. Alex Ponsa
    Hi there,

    Sap says that for intracommunitarian operations and for the book of investments you have to do develop it, but I am not able to found any note or information talking about it.

    Does anyone know ho to develope it? Do you have to develope it in one of the BADIs, or where?

    If you can tell me something about it, I will be very pleased.

    Thank’s in advance,
    Alex.

    (0) 
  14. Teresa Lorite Post author
    File from RFIDESM340 might be rejected by the AEAT validation program if it includes special characteres such as ‘.

    ES_REMOVE_SPECIAL_CHARACTER will be modified.

    Mehanwhile, you can do the following:

    1.Execute SE37
    Select ES_REMOVE_SPECIAL_CHARACTER

    2.Press the “Change” button.

    3.Search for the following lines of codes:

    DATA : chk_str(30) TYPE c VALUE ‘*+!$&#128;#%()=?¿¡}><[]{ºª\”_@&•’, “#EC *
    chk_stra(8) TYPE c VALUE ‘ÄäÀàÂâÃã’, “#EC *
    chk_stre(6) TYPE c VALUE ‘ËëÈèÊê’, “#EC *
    chk_stri(6) TYPE c VALUE ‘ÏïÌìÎî’, “#EC *
    chk_stro(10) TYPE c VALUE ‘ÖöÒòÔôÕõóÓ’, “#EC *
    chk_stru(6) TYPE c VALUE ‘ÜüÙùÛû’, “#EC *
    chk_strn(2) TYPE c VALUE ‘Ññ’, “#EC *
    idx TYPE i.

    4.Replace the above line with the following line :

    DATA : chk_str(30) TYPE c VALUE ‘*-+”!$&#128;#%()=?¿¡}><[]{ºª\”_@&•’,”#EC *
    chk_stra(8) TYPE c VALUE ‘ÄäÀàÂâÃã’, “#EC *
    chk_strc(2) TYPE c VALUE ‘Çç’, “#EC *
    chk_stre(6) TYPE c VALUE ‘ËëÈèÊê’, “#EC *
    chk_stri(6) TYPE c VALUE ‘ÏïÌìÎî’, “#EC *
    chk_stro(10) TYPE c VALUE ‘ÖöÒòÔôÕõóÓ’, “#EC *
    chk_stru(6) TYPE c VALUE ‘ÜüÙùÛû’, “#EC *
    chk_strn(2) TYPE c VALUE ‘Ññ’, “#EC *
    idx TYPE i.

    5. Search for the following lines of codes

    DATA: str1(100) TYPE C,
    lnth TYPE I.

    str1 = TEXT1.
    lnth = STRLEN( STR1 ).
    DO lnth TIMES.
    IF lnth EQ sy-index.
    EXIT.
    ENDIF.
    idx = sy-index – 1.
    IF str1+idx(1) CA chk_stra.
    str1+idx(1) = ‘A’.
    ELSEIF str1+idx(1) CA chk_stre.
    str1+idx(1) = ‘E’.

    6.Replace the above lines of codes with the following lines of codes :

    DATA: str1(100) TYPE C,
    lnth TYPE I,
    lnth1 TYPE I.

    str1 = TEXT1.
    lnth = STRLEN( STR1 ).
    lnth1 = lnth + 1.
    DO lnth TIMES.
    IF lnth1 EQ sy-index.
    EXIT.
    ENDIF.
    idx = sy-index – 1.
    IF str1+idx(1) CA chk_stra.
    str1+idx(1) = ‘A’.
    ELSEIF str1+idx(1) CA chk_strc.
    str1+idx(1) = ‘C’.
    ELSEIF str1+idx(1) CA chk_stre.
    str1+idx(1) = ‘E’.

    7.Please activate the same.

    (0) 
  15. Teresa Lorite Post author
    Please refer to just released SAP notes:

    Note 1309426  “Corrections for the report RFIDESM340”

    Note 1306433 “Deferred Taxes Handling in the report RFIDESM340”

    (0) 
  16. MARIVI DEZA
    Buenos dias!!

    Tenemos un error en la generacion del modelo 340, ya que tenemos un iva al 7,5 %. El error viene porque en la generacion del modelo en vez de poner 750, pone 705; con lo cual hacienda nos dice que el iva 7,05% no existe.

    Gracias de antemano.

    Marivi

    (0) 
  17. Aridane Durán
    We have apply the note 1292521 and the related notes. The report is working properly, somehow there is problem.
    The header (Registro 1) is filled with the NIF A58379629 (SAP ESPAÑA) instead of the company NIF. The positions (Registro 2) are filled correctly with the company NIF.

    Does anybody know how I can solve this problem?

    (0) 
      1. Aridane Durán
        I have done this task. The Tax Number of the Company was already set before I run the report. (IMG->Customizing->Financial accounting-> Financial accounting global settings-> Company code ->Enter Global Parameters)

        The file which is generated by the report is wrong. (Strangley wrong)
        Register type 1 is like:
        13402009A58379629……..
        Every Register type 2 is like:
        23402009 Tax Number of the company code. (The Tax Number set in the Customizing.

        In brief, the register type 1 is wrong, it does not have the Tax Number of the Company. The registers type 2 are right, they have the Tax Number of the Company.

        (0) 
  18. ANA POLO LOPEZ
    We´ve notice some errors in the programme RFIDESM340, maybe it’s due to our support package version (SP SAPKH47022).

    First thing is, for “autorrepercutido” VAT indicators on the output chart the programme looks up the name and the Tax ID of the vendor on the table KNA1 instead of looking it up on LFA1 table. That’s why for the same document number the name and TaxID is not the same on the output and on the input box, and the programme must show us the same.

    The second problem is for CDP vendors and customers.The  input and output for this kind of
    customers/vendors it’s wrong. It does not appear the name neither the tax ID. That information is contained
    in the document (BSEC and BSEG), not in the tables LFA1 or KNA1, it doesn’t exist master data for this kind of vendors/customers.

    Thanks in advance.

    Ana Polo

    (0) 
  19. Matthias Kruse
    Hello,

    maybe someone can help us with this report. We are required to use this report but unfortunately we do not have this report in our system at all. We are running with ERP 6.0. When we try to open the report in SE38 we can not find it. Is there are note with the report included? Any help would be appreciated.

    Thank you …

    (0) 
  20. Rafael Manco Leon
    We have implemented report RFIDESM340 succesfully (including lastest notes), but we have problems with some customers that are registered in master data with this information: COUNTRY=’ES’ NIF=” NIF.COM.=”. We understand this program should report them in text file as ‘ES6’ (country+id.code) but we get blank spaces for these customers.

    Thanks for your answers.

    (0) 
  21. Julio J. Vicente
    Good Moorning,

    We are working in SAP ECC 6.0 where we have implemented the next sap notes:
    1292521, 1302260, 1309426, 1316299, 1304247 and 1023317.
    And we have followed the instructions in the atached document “MODELO_340_2009.zip” in note 1304756.
    When we execute the program “RFIDESM340” or use the transaction “TCODE_RFIDESM340” the System edit a dump because the modul function “ES_REMOVE_SPECIAL_CHARACTER” is not found.

    Thanks in advance for hour help.

    (0) 
  22. David Diaz
    Hi, my user has reported a ticket because of the VAT dates within the 340 files, the symptom is:

    Actually when you post a self invoice the 340 after executing RFKORDES report, the file VAT dates should be updated like this:

    Vendor’s invoice: for example 12/01/2009
    Self invoice(incoming vat): 23/02/2009

    Actually the system behaviour is to put the same VAT date in the both lines, ie 12/01/2009, wich it seems to be wrong…

    Anyone with the same problem??

    (0) 
  23. Teresa Lorite Post author
    Since note 1292521 was released on 30.01.2009, some errors were detected, so make sure you also implemneted following notes:        
                                                                   
    1302260 Modelo-340 Legal Change Additional Correction          
    1309426 Corrections for the report RFIDESM340                  
    1306433 Deferred Taxes Handling in the report RFIDESM340       
    1316299 RFIDESM340: Electronic VAT Books (SPAIN)               
    1318503 RFIDESM340: Electronic VAT Books(Spain)                
    1321369 RFIDESM340: Electronic VAT Books (Spain)               
    (0) 
  24. Monica Perez Puerta
    Hi Teresa,

    Thanks for your guidance with this new report.

    I wonder if there is any SAP standard transaction code for report RFIDESM340, so that we can assign it through SE93.

    Thanks a lot.
    Mónica

    (0) 
    1. Teresa Lorite Post author
      Hello Mónica,

      Note 1304247 “Transaction Code for the report RFIDESM340”, provides
      a transaction to execute report REFIDESM340                       

      Best Regards,

      Teresa

      (0) 
  25. Monica Perez Puerta
    Hi Teresa,

    After applying note 1321369 following syntax error appears in Include RFIDESM340_MAIN, line 208:

    The field “SEL_TMDT” is unknown, but there is a field with the similar name “SEL_VTDT”.

    Could you please advise on how to correct it?

    Thanks in advance.

    Mónica

    (0) 
  26. Apolonia Garcias
    I have solved the error with BR_BUKRS in the RFIDESM340 setting BFR in “logical database” in program “Attributes”.
    But now I have a new error: “ Field “COUNT” is unknown. It is neither in one of the specified tables”.
    Has anyone had the same problem?
    I don´t found OSS notes or entries in this blog.

    Regards

    (0) 
  27. Rafael Manco Leon
    Hello:

    We have some problems with code operations J, because actually if the program RFIDES340 find a customer info with country = “ES” and there is no any Fiscal ID then the program shows nothing in these two columns, this must be an error because operations J (ticekts) shouldnt ask for a Fiscal ID, the program should mark these rows as country = “ES” and ID Country = 6.

    (0) 
  28. Stijn Stevens
    Hi,

    I get the following error when implementing note 1321369:

    The field “SEL_TMDT” is unknown, but there is a field with the similar name…

    Can you please help

    Tx a lot,

    Stijn Stevens

    (0) 
    1. Shwetha Thimmappa
      Hi,

      our R3 system is in ECC6.0 EHP4(701).
      and have implemented following SAP notes already which are not included in EHP4, to implement Model 340 and VAT date functionality to Spain;

      1). 1292521 “Legal change on Modelo 340: Electronic VAT books”
      2). 1302260 “Modelo-340 Legal Change Additional Correction”
      3). 1304247 “Transaction Code for the report RFIDESM340”
      4). 1303567 “Addition of field “VATDATE” to structure” – this Snote is not required because Spain using VAT date function.
      5). Note 1023317 “Legal Change: Vat Due date”
      6). Note 1232484 “How to use the VAT due date, tax reporting” (This is a describing note).
      7). Note 1038448 VAT due date :Country specific Reporting (manual activity n implement correction instructions)
      8). Note 1281852 “Legal change on VAT” (manual activity n implement correction instructions).
      9). 1302260 Modelo-340 Legal Change Additional Correction
      10). 1309426 Corrections for the report RFIDESM340
      11). 1306433 Deferred Taxes Handling in the report RFIDESM340
      12). 1316299 RFIDESM340: Electronic VAT Books (SPAIN)
      14). 1318503 RFIDESM340: Electronic VAT Books(Spain)
      15). 1321369 RFIDESM340: Electronic VAT Books (Spain)

      After doing the prevalidation, we are getting follwoing error codes;
      Type of Registration     error code     error message
      2               1302          Date of issuance, Inappropriate content in
      2               1003          N.I.F. in the country of residence, Lack content
      2               703          Name and first name, business name or name of the declared, Lack content
      1               301          Exercise ,Content Incorrect
      2               701          Name and first name, business name or name of the declared, Content Incorrect
      2               503          N.I.F. of Declared , Lack content
      1               801          Number identifying the statement, Content Incorrect
      2               1202          cloves of operation , Inappropriate content
      2               901          Key identification number in the country of residence , Content Incorrect

      Please let us know how to resolve these error codes.
      Appreciate your quick response,

      Thanks you,
      Shwetha

      (0) 
  29. Shwetha Thimmappa
    Hi,

    our R3 system is in ECC6.0 EHP4
    and have implemented following SAP notes already those are not included in EHP4, to implement Model 340 and VAT date functionality for Spain;

    1). 1292521 “Legal change on Modelo 340: Electronic VAT books”
    2). 1302260 “Modelo-340 Legal Change Additional Correction”
    3). 1304247 “Transaction Code for the report RFIDESM340”
    4). 1303567 “Addition of field “VATDATE” to structure” – this Snote is not required because Spain using VAT date function.
    5). Note 1023317 “Legal Change: Vat Due date”
    6). Note 1232484 “How to use the VAT due date, tax reporting” (This is a describing note).
    7). Note 1038448 VAT due date :Country specific Reporting (manual activity n implement correction instructions)
    8). Note 1281852 “Legal change on VAT” (manual activity n implement correction instructions).
    9). 1302260 Modelo-340 Legal Change Additional Correction
    10). 1309426 Corrections for the report RFIDESM340
    11). 1306433 Deferred Taxes Handling in the report RFIDESM340
    12). 1316299 RFIDESM340: Electronic VAT Books (SPAIN)
    14). 1318503 RFIDESM340: Electronic VAT Books(Spain)
    15). 1321369 RFIDESM340: Electronic VAT Books (Spain)

    After doing the prevalidation, we are getting follwoing error codes;
    Type of Registration – error code – error message
    2 1302 Date of issuance, Inappropriate content in
    2 1003 N.I.F. in the country of residence, Lack content
    2 703 Name and first name, business name or name of the declared, Lack content
    1 301 Exercise ,Content Incorrect
    2 701 Name and first name, business name or name of the declared, Content Incorrect
    2 503 N.I.F. of Declared , Lack content
    1 801 Number identifying the statement, Content Incorrect
    2 1202 cloves of operation , Inappropriate content
    2 901 Key identification number in the country of residence , Content Incorrect

    Please let us know how to resolve these error codes.
    Appreciate your quick response,

    Thanks you,
    Shwetha

    (0) 
  30. Teresa Lorite Post author
    As of june 2009 following notes have been released:

    1335806 RFIDESM340 : Electronic VAT Books (Spain)            
    1365022 RFIDESM340: Electronic VAT Books (SPAIN)             
    1382672 RFIDESM340:Issue with tax base amt & field-78        
    1406392 RFIDESM340:Vendor/Customer info. missing in Deferred 

    (0) 
  31. Paul Doherty
    Hi Teresa,
              I’m implementing note 1309426 and getting an issue with a code update to the ES_REMOVE_SPECIAL_CHARACTER FM which does not exist on our system. Can you advise on the creation of this FM? I’ve checked the documentation on note 1292521 and cannot see a reference to this object.

    regards,

    Paul

    (0) 
  32. Maximino Suárez Arboleya
    Hola,

    Tenemos facturas registradas con IVA diferido. Se realiza el traslado al indicador de IVA definitivo, una vez pagadas las facturas, a través del report RFUMSV25.
    Al ejecutar el modelo 340, no selecciona los datos del acreedor (nombre, NIF) para estas facturas. Hemos visto que hay varias notas de SAP sobre este tema. La nota 1428256 es la última. Si se aplica esta nota, junto con las notas relacionadas que tenga, ¿se solucionará este problema?

    Gracias y un saludo,
    Olga Suárez

    (0) 
    1. Valentina Vicario
      Hi,
      I have just uploaded from release 4.7 to release ECC 6.0 and the program output change.

      Customer Example:
      – Land Code: IT
      – NIF: ESXXXXXXXXX

      In 4.7 the output showed the customer in category ES1, while now is in category IT2.

      I found out that in release 4.7 Note 1382672 wasn’t applied. Could it be the reason?

      Furthermore customer refers to manual in Note 1292521 to fill declaration, maybe that there is a new version?

      Thanks for your help.

      (0) 
  33. Spyros Stamou
    Hi Teresa,

    we have an issue with the report Model 340 for Spain. My FI colleagues say that the only way to make the report work is bundle VAT and Recargo in the same tax code.
    Currently we have 2 different tax codes for VAT and Recargo.
    I could see in your example above that you dont use Recargo in your VAT tax code.
    Please advise.
    PS: I accidentally added the same in “How to deal with spanish new tax rates 2010.” YOu can reply to both  🙂

    (0) 
  34. Monica Martinez Castellote

    Hi.

    In VF11, I need BKPF-BUDAT = BKPF-BUDAT from the new reverse document, to get this I use NOTE 339928. But this note cancels the bady VATDATE_VALUES.

    I need also the VATDATE equal to the BKPF-BUDAT from the new reverse document.

    (0) 

Leave a Reply