User cannot find all the SAP Notes related to the NF-e 4.0: NT 2018.005 solution and needs a list of them organized by component area:
This KBA also aims to solve known problems during the implementation of listed SAP Notes:
5. Known issues when applying the SAP Notes mentioned above:
5.1 SAP Note 2722239 cannot be implemented.
5.2 Field CEST is unknown.
5.3 Context TAX_RATE is not found for one or multiple tables.
5.4 During "test run", we are facing an error "Data Element or Structure J_1BNFE_CODE_DESCRIPTION does not exist".
5.5 Methods GET_EXP_JSON and CHECK_JSON does not exist in Class TC_J_1BNFE_CF_AUTHORIZE_310.
5.6 Object directories IDNFBRJ_1BNFEPAYMENT, IDNFBRJ_1BNFEPHARMA and IDNFBRJ_1BNFETRACE does not exist.
5.7 Fields PREDBCEFET, VBCEFET, PICMSEFET, VICMSEFET does not exist or are unkown in one or multiple tables.
5.8 Status TECRESP01 of the user interface SAPLJ1BB2 missing
5.9 Rejection 225 due to incorrect CEP format in DELIVERY or WITHDRAW group
5.10 Technical responsible is not mapped to XML even filling up the screen or mapping via BAdI
5.11 Rejection 225 due to incorrect FONE format in DELIVERY or WITHDRAW group
5.12 NF-e created via BAPI BAPI_J_1B_NF_CREATEFROMDATA is missing the CNPJ field on structure BAPI_J_1BNFE_TEC_RES
5.13 View J_1BNFE_PAR_MAPV(delivery and withdrawal) filled but not mapped to the NF-e XML.
5.14 Applying 2766957 - TABL J_1BNFE_S_ITEM400 was not activated. Same as J_1BNFE_S_RFC_PROD_MED_400 and J_1BNFE_S_RFC_TAX_ICMS_400.
5.15 Issues related to version 1.20 from NT2018.005 for SAP NFE (messaging system)
5.16 SAP recommendation regarding the Technical Responsible group
5.17 You received a XML with tag p_ST and the content does not show in WebDynpro monitor
5.18 Tag "IE" (Inscrição Estadual) with special characteres in groups "entrega" and "retirada" are not being removed
5.19 Parameter 'IS_NFE_INFRESPTEC' is not inserted in Function Module J_1BNFE_OUTNFE_CREATE_400
5.20 You are creating a MIRO and you go to NOTA FISCAL, inform a value in field VICMSSUBSTITUTO, go back to MIRO, then SAVE the value is cleared.
5.21 EU829 Object CINC CL_J_1BNFE_PARTNER_MAP========CCAU is inactive
5.22 BAdI CL_NFE_PRINT is not being called after apply the SAP Notes related to NT2018.005
5.23 Rejection 971 due to incorrect filling of IE tag
5.24 Tag CEP for export scenarios in delivery and withdraw groups
SAP ERP and S/4
NFe, localizacao, localization, cl_nfe_print, persistencia, persistency, badi, notatecnica, J_1BNFE_CODE_DESCRIPTION,TAX_RATE, 2622015, 2722589, 2608929, GET_EXP_JSON, CHECK_JSON, TC_J_1BNFE_CF_AUTHORIZE_310, CEST, PREDBCEFET, VBCEFET, PICMSEFET, J_1BNFE_OUTNFE_CREATE_400, VICMSEFET, IDNFBRJ_1BNFEPAYMENT, IDNFBRJ_1BNFEPHARMA, IDNFBRJ_1BNFETRACE, 225, delivery, withdraw, retirada, entrega, cep, format, Technical responsible, responsável técnico, fone, tag, telefone, FAQ, IS_NFE_INFRESPTEC BAdi CL_NFE_PRINT tec_resp IND_BADI_CTRL, 971, ie, delivery, withdraw, entrega, retirada, 2018.005, nt
, KBA , XX-CSC-BR-NFE , Nota Fiscal Electronica , XX-CSC-BR-SD , Sales and Distribution , SLL-NFE , Nota Fiscal Electronica (NFe) , XX-CSC-BR-NFEIN , Incoming Automation with SAP GRC NFe , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.