Skip to Content

Hello Guys,

We’ve released the SAP Note 2238556 with the changes needed to comply with NT 003.2015.

Some background information about the change:

The legal change NT 2015.003 for NFe is delivered with note 2238556.

Since the government changed the WebServices the note will re-generate ABAP-Proxies (needed for the mapping from ABAP structures to XML).

This note requires (amongst other) to implement the notes 2114276 and 2206471 because these also changed the ABAP-Proxies.

There was a general problem in the NetWeaver stack which occured during the implementation of notes which contain changes to ABAP-Proxies (especially deletions). This problem was solved with note 2252522.

Implementing the note 2114276 before note 2252522 leads to inconsistent ABAP-Proxies so the issuing of NF-e does not work anymore.

How to proceed

SP19 or lower

A.The best solution is to implement the latest SP23 available in on December 8th.

Since the problem was not inside the NFE software, the problem does not occur when implementing the Support Package.

B.If you did not implement any of the notes 2114276 and 2206471 yet and you cannot implement SP23, please proceed as follows:

1.implement all notes that are listen in note 1397878. This includes the note 2252522 and will solve all (known) problems related to the transport of ABAP Proxies via notes

2.Make sure all these notes are implemented completely and successfully!

3.Afterwards you can implement the note 2238556 (together with all the required the notes)

4.Check the successful implementation of the notes in the section “How to check if the ABAP proxies are consistent” below.

C.If you did implement note 2114276 or 2206471 and you cannot implement SP23, please proceed as follows:

1.implement all notes that are listen in note 1397878. This includes the note 2252522 and will solve all (known) problems related to the transport of ABAP Proxies via notes

2.Make sure all these notes are implemented completely and successfully!

3.De-implement note 2114276 (and 2206471) and all other notes based on these

4.Re-implement the note 2114276 (and 2206471)

5.Afterwards you can implement the note 2238556 (together with all the required the notes)

6.Check the successful implementation of the notes in the section “How to check if the ABAP proxies are consistent” below.

SP 20 to 22

A.The best solution is to implement the latest SP23 available in on December 8th.

Since the problem was not inside the NFE software, the problem does not occur when implementing the Support Package.

B.If you cannot implement SP23, please proceed as follows:

1.implement all notes that are listen in note 1397878. This includes the note 2252522 and will solve all (known) problems related to the transport of ABAP Proxies via notes

2.Make sure all these notes are implemented completely and successfully!

3.Afterwards you can implement the note 2238556 (together with all the required the notes)

4.Check the successful implementation of the notes in the section “How to check if the ABAP proxies are consistent” below.

How to check if the ABAP proxies are consistent

A.Use transaction se80 and navigate to the Enterprise Service Consumer (fancy name for the ABAP Proxy) /XNFE/CO_008_BATCH_NFE_AUTORIZ. Depending on your Support Package, the Proxy is either in package /XNFE/IXI or /XNFE/IXINFE.

B.Double-click on the Proxy and make sure that there is no warning displayed in the bottom of the screen. Moreover, the menu ‘Goto’à’Show Log’ should be disabled (since there should be no log)

C.Choose the tab ‘External View’ which will show you the complete XML structure in a tree. Navigate to NfeAutorizacaoLote->nfeDadosMsg->enviNFe->NFe->infNFe->det->imposto->ICMSUFDest and check if all new fields introduced with NT 2015.003 are available. You can also check the field CEST in det->prod

D.Use transaction se16 to display the content of table SPROXDAT. Make sure you have the following entries (and not more!):

1.For OBJ_NAME ‘/XNFE/008_BATCH_NFE_AUTORIZ272’

Picture1.png

2.For OBJ_NAME ‘/XNFE/008_BATCH_NFE_AUTORIZ313’

Picture2.png

3.For OBJ_NAME ‘/XNFE/008_BATCH_NFE_AUTORIZ178’

Picture3.png

IMPORTANT INFO: The SAP Note 2255516 must be applied for those who implemented SP23 (or SAP Note 2238556) and have ICMS non-contributer interstate scenarios.


Regards,

Renan Correa

To report this post you need to login first.

8 Comments

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

    1. Diego Gabriel

      Hello,

      It was released few minutes ago but now it’s locked again.

      Here the problem is the step 13 (SP18). The structure /XNFE/WD_NFE_ICMSTOT does not exist.

      (0) 
      1. Renan Correa Post author

        Hi Diego,

        You’re right. The structure was only created in SP19. I notified the development team to adjust it.

        Regards,

        Renan Correa

        (0) 
          1. Diego Gabriel

            Hello Renan,

            Thanks for the info.

            All related notes/manual steps of notes 1397878, 2238556 and 2255516 were successfully implemented. ABAP proxies are consistent as well.

            We are going to start the tests tomorrow morning.

            I will let you know whether we face any problem or not.

            PS: We follow “SP19 or lower” > option B.

            Regards,

            Diego

            (0) 
  1. Vinicius Da Silva Sales

    Hello Renan,

             Since the government changed the WebServices the note will re-generate ABAP-Proxies (needed for the mapping from ABAP structures to XML) this will also affect Companies that did not have implemented NT003/2015. Considering they do not have ICMS ST buy/sell goods.

    Thanks and Best Regards,

    Vinicius Sales

    (0) 
  2. Diego Gabriel

    Hello Renan,

    It seems there is a problem…

    SM30 for table /xnfe/proxy_map.

    According to the document we should not assign any “Display Structure” for component ICMSUFDEST.

    However the NFe monitor needs a structure to display the new data.

    When I access the NFE monitor <server>/sap/bc/webdynpro/xnfe/nfe_outb_monitor and I click on the NFe Key to see the details I get an ABAP DUMP:

    Erro tmp.exec.         ASSIGN_TYPE_CONFLICT

    Programa ABAP          /XNFE/SAPLGROUPING

    Please take a look at include /XNFE/LGROUPINGF03 line 109.

    Is this a really problem or I missed some step?

    Regards,

    Diego

    Just a remark:

    Even the include is checking whether the structure should be displayed or not, we get the dump.

    I forced via debug an ‘X’ to be displayed and tried to use the same structure /XNFE/WD_IMPOSTO_ICMS_T but it didn’t work as well 🙁

    Thanks again.

    Diego

    (0) 

Leave a Reply