Skip to Content

Hi Guys,

After having implemented the Nfe 3.10 pre-requisites and notes ( I hope that you have used the KBA “2056762 – Guidelines for NF-e layout 3.10 SAP Notes installation” ) you’ll be challenged by the changes required to use the new layout version. To ease this work we have created the KBA “2057942 Guideline for NF-e layout 3.10 implementation in ERP and SAP NFE“.

We hope that this information can help you to avoid issues and identify the changes quickly.

Regards,


On behalf of Renan Correa

To report this post you need to login first.

20 Comments

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

  1. Nishikant Nibandhe

    Hi Tiago & Team,

    Thanking you very much for all the informative blogs on NFe 3.10 upgrade.You people are doing great help to the people working in Brazil specific (niche) NFe area.

    We are trying to upgrade NFe 3.10 for one of our client and I have few questions related to the same. It would be of great help if you can clarify my below doubts :

    1. For KBA :  2056762, you mentioned that in step 2 (SAP ECC Side) implementation option B, we need to implement all the relevant SAP Notes given in the Table & also the Notes in Step 3. My question is if we have already implemented SAP Note 1933985 (and the related pre & post activities ) in our system, Do we need to still implement ALL the Notes which you mentioned under Step2, section 2.1.1?

    2. Under KBA : 2057942, for section 1.2 Danfe format determination, you mentioned,If you use the option 3, you’ll need to schedule a job for program  J_BNFECALLRFC, can you please provide some more details on this part ?. Can you please explain the need of this configuration in greater detail for a better understanding. Currently in our system, we are getting an expected result with this field as BLANK.

    Your help / response on these questions are much appreciated.

    Regards,

    Nishikant Nibandhe

    (0) 
    1. Tiago Correa Post author

      Hi Nishikant,

      Thank you for the feedback! We are glad to hear that.

      Anyway, please find my answers below:

      1. If you have already implemented SAP Note 1933985, it means that you already have all the notes in step 2, as they are all pre-requisites to SAP Note 1933985 itself. Depending on your release, there are a few notes that won’t be necessary to implement. Bottom line is that you won’t be needing to implement them as you already have them implemented.

      2. As of November 1st RFC Execution blank will not be supported as per SAP Note 2050786. You can find all information about job J_BNFECALLRFC in SAP Note 1265172.

      Cheers,

      Tiago.

      (0) 
  2. Nishikant Nibandhe

    Hi Tiago,

    We are done with the initial implementation of SAP Note : 1933985 and its pre & post activities. Now while creating test cases in Development environment, we are getting the below error :

    Validation error: field PARTNER-EMIT[1]-IE: Referenced Rural Producer: Issuer IE. Content not allowed (407.262.644.11)

    Message no. J1B_NFE_ERP_GRC215

    Can you please guide us in getting this resolved.

    Thanks in advance…

    Regards,

    Nishikant

    (0) 
    1. Renan Correa

      Hi Nishikant,

      The error is happening because you have “.” in the value of field IE. You have 407.262.644.11 and the correct would be 40726264411.

      Regards,

      Renan Correa

      (0) 
      1. Nishikant Nibandhe

        Hi Renan,

        Thank you very much for your prompt response. The issue is solved now.

        Really appreciate your (SAP NFe) team’s efforts for taking the 3.10 Upgrade initiative forward.

        Thanking you.

        Nishikant Nibandhe

        (0) 
  3. Nishikant Nibandhe

    Hi Team,

    We are upgrading the NF – layout and 2.00 for the 3.10, however while testing, we are getting the following error from SEFAZ Homologation environment :

    598 – Rejection : NF- issued environmental approval with Company name other than ‘ NF-E EMITIDA EM AMBIENTE DE HOMOLOGACAO – SEM VALOR FISCAL ‘ .

    For NF – layout and 2.00, we have the BADI ( @ GRC ) / XNFE / 006_SIGN_NFE_OUT in which we can implement to meet the need of modifying the recipient’s name to the name required by SEFAZ , however, to the layout 3.10, we find that this BADI is not called and hence we are getting the above error.

    This BADI was passing the below values to the Homologation Environment :

    CNPJ: 99.999.999/0001-91

    XNOME: NF-E EMITIDA EM AMBIENTE DE HOMOLOGACAO – SEM VALOR FISCAL

    Can you please help us in resolving this error or suggest a better approach to handle this.

    Regards,

    Nishikant

    (0) 
    1. Renan Correa

      Hi Nishikant,

      The BADI in GRC does not exist for layout 3.10.

      The options you have are:

      1- Changing customer master data in ERP.

      2- Changing the values of CNPJ and XNOME using a “dirty assign” inside CL_NFE_PRINT.

      Regards,

      Renan Correa

      (0) 
  4. Nishikant Nibandhe

    Hi Team,

    Issue Header:

    Importing parameters IN_VBFA and IN_VBELN of BADI CL_NFE_PRINT Method FILL_ITEM are blank after NFe Decoupling(Note# 2057942)

    Issue Details:

    After implementing NFe Decoupling as per Note# 2057942, BADI CL_NFE_PRINT Method FILL_ITEM importing parameters IN_VBFA and IN_VBELN are always blank.

    Prior to Decoupling Parameters IN_VBFA and IN_VBELN used to have VBFA document flow and Document Number data respective.

    Can you please suggest/ guide us in knowing why these parameters are blank. Is there any OSS NOTE which we are missing.

    Regards,

    Nishikant

    (0) 
    1. Renan Correa

      HI Nishikant,

      I’ve not seen this issue before. The best way to check it is opening function J_1B_NF_MAP_TO_XML, looking for PERFORM fill_vbfa and checking why it’s not being called.

      Regards,

      Renan Correa

      (0) 
  5. Renato Barbosa dos Santos

    Hi Tiago!

    We are implementing the note SAP 2052491 for the treatment of new fields Vicmsdeson e Moticmsdeson in Z. Franca scenarios, but after implementing the fields didn`t appear in the documents. So they weren´t transferred to the XML.

    We are using the BADI  CL_NFE_PRINT. This note is relevant for this BADI?

    Regards,

    Renato Santos

    (0) 
    1. Renan Correa

      Hello Renato,

      For the fields to appear in the documents you must have them assigned to a NF type with screen control that they are enabled.

      The note enables the fields on the J1B*N screens.

      If you want to use the BAdI to fill them it was already delivered in the past, together with the NF-e layout 3.10 note

      REgards,

      Renan 

      (0) 
  6. Nishikant Nibandhe

    Hi Renan,

    Thanks for your reply, to add further to my query raised on Sep 30, 2014 2:32 AM

    Subroutine : fill_vbfa triggers only when wk_header-cnpj_bupla is INITIAL. As per our business process the value of this field will always be the CNPJ number (say value X) of Issuer which won’t be INITIAL in any case.

    As per function module “J_1B_NF_MAP_TO_XML”

    We started the bove issue only after implementing the De Coupling solution provided by SAP via Note# 2057942, we further found out that program “J_BNFECALLRFC” calls function module “J_1B_NF_MAP_TO_XML” without passing data for parameters I_VBELN & IT_VBFA.

    Prior to De-Coupling the above parameters were having values while calling function module “J_1B_NF_MAP_TO_XML”

    Request your help to guide us further.

    Regards,

    Nishikant

    (0) 
    1. Renan Correa

      Hi Nishikant,

      I have not tested this scenario, if you have all the details to reproduce the error please open a message to SAP providing them and the access to the system and we’ll investigate it further.

      Regards,

      Renan Correa

      (0) 
  7. Nishikant Nibandhe

    Hi Renan & Team,

    Thanks for your prompt reply, we have raised this issue to SAP and they have provided Pilot note  number : 2054197, which we will be implementing and testing soon.

    Apart from this I need your advice for below 2 things in Return Scenarios :

    1. IPIDevol & VIPI Devol Fields Calculations

    We have already implemented the Note 1993209 & its pre & post requsites, but still the values for these fields are not coming.

    We have checked that the FM “J_1B_NFE_CALC_IPI_RETURN” where IPI calculations are done is invoked only during manual change of tax values (via J1B1N/J1B2N) but not during automatic creation of NFe via VF01 or VF04 batch.

    2. ICMS Total Errors (Rejection Error 531, 533 etc)

    We have implemented the Note : 2004264 as per our SP but still getting the errors 531 & 533.

    Requesting your kind advice.

    Thanks & Regards,

    Nishikant Nibandhe

    (0) 
    1. Tiago Correa Post author

      Hi Nishikant,

      About point 1., are you talking about issues in return IPI? If that is the case, this scenario is only for returns via MM and manually via J1B1N/J1B2N/J1B3N/. If that is not the case, maybe you can create an incident with the problem and we can take a look at the example.

      On point 2 I don’t see how to help you without checking the issue. It might be due to incorrect tax calculation and/or rounding issues.

      BR,

      Tiago.

      (0) 
  8. Nishikant Nibandhe

    Hi Tiago,

    Greetings !!!

    Thanks for your reply.

    About point 2, indeed it was tax calculation issue. we resolved it by changing appropriate IPI tax text at country tab level in sales order and the issue got resolved.

    Regarding point number 1, I have a doubt about  the IPI Devol & VIPI Devol fields. Are these relevant for only MM flows (Inbound NFe flows) and will the calculation of the VIPI Devol field on NFe screen take place only in case of manual creation via J1B1N/J1B2N/J1B3N/. Are these fields not relevant for Customer returns scenarios (Nfe type N4/N5).

    I am bit confuse about their applicability and was not able to find any concrete blog/ information regarding this, hence requesting your help.

    Kindly suggest/ guide. Really appreciate.

    Regards,

    Nishikant Nibandhe

    (0) 
    1. Tiago Correa Post author

      Hi, sorry for the delay.

      No, ipi devol is not relevant for customer return scenarios (when the company issues incoming notas fiscais).

      BR,

      Tiago.

      (0) 
  9. Renato Barbosa dos Santos

    Hi Tiago,

    I´m creating a exportation process and  is occurring the error below:

    527: Rejeição: Operação de Exportação com informação de ICMS incompatível

    Our process is using the ICMS tax situation 41, but the include LJ_1B_NFEF23  in line 60 changes the Situation to 40.

    The result is that SEFAZ rejects the nota fiscal.

    Why SAP changes this situation in this include?

    Thanks,

    Renato

    (0) 
    1. Tiago Correa Post author

      Hi Renato,

      Are you using ICMS with the statistic flag? Do you need to have that? Otherwise I think it maintains 41.

      But this is something that we should check via incident.

      Cheers,

      Tiago.

      (0) 

Leave a Reply