Meet-The-Expert sessions about Nota Fiscal Eletronica (NF-e) 3.10

In order to help you to identify solution pre-requisites, implement the correct notes and customize the system to use the new NF-e layout 3.10 we, from Product Support, will host two Meet-the-Experts sessions, one in English and another in Portuguese. We will talk about the two KBAS that we have already created (2056762 and 2057942) and any new topics that might come up. In the end, we will do a quick Q&A session.

Both sessions will be held in September 17th. Below you can find the times for each of them:

English at 10:00 – 11:00 (UTC-3)

Portuguese at 14:00 – 15:00 (UTC-3)

The registration for the session requires an S-User and can be done with the following link ( short URL ).

If you already have questions, please write them in the comments below and we will try to accomodate them in the sessions.

1 Comment

Our company is participating in the MTE session tomorrow. We wanted to submit in advance the followin questions:

1. Exportacao Indireita: Nota Técnica point 3.11

SEFAZ is asking for Numero de Registro de Exportacao, Chave de Acceso a Nota Fiscal recebeida para Exportacao. SAP has responded accordinlgy generating such fields underneath BADI Export. We however have the doubt on how can a company possibly provide a Registro de Exportacao number in the NF-e where the NF-e is a required document to submit Registro de Exportacao-RE?

2. autXML: we tought of developing a customer master header text field to flow all the way to billing document and from there transport via BAdI to CNPJ and CPF tags up to 10 ID’s. However, we saw the object J_1BNFE_T_AUTXML beign created with the .SAR files from main SAP note. How does this Data Type works? Does SAP already developed a best-practice for this development?

3. For releases 604 and below no DDics for Master Data, Master Data Screen nor Tax Determination DDics are being delivered by SAP, although layout is being updated. How does SAP recommeds implementing requirements for example for tag indIEDest that relays on view J_1BTICMSTAXPAY

So far we have been told “develop a Z logic” however this involves logic coming from three notes that are all 605 and that SAP already knows exaclty what to do for releases 605 and above (notes 1873294, 1869555, 1856625): this meaning creating master data fields for Customer, vendor and branch master, LSMW or MDM IDOC changes, logic for tax determination, value determination in NF-e programs, and finally BAdI method to fill XML.

If we were 605, this would only mean apply note, and BAdI method. Can SAP provided a more detailed instruction for lower releases to ease the pain in these sort of developments for 604 and lower?