Sap layout 4.0 nota fiscal eletronica how to#
Sap layout 4.0 nota fiscal eletronica upgrade#
Sap layout 4.0 nota fiscal eletronica code#

Here you need to maintain all the validations for which you want to ensure that ADAPT_CHAR_SET validation is performed.

SPRO -> Nota Fiscal Eletrônica -> Outbound -> NF-e → NF-e: Maintain Validation Rules To ensure the consistent behavior now projects need to maintain below stated SPRO configuration. It’s note worthy that table data /XNFE/XMLVALID is provided by SAP and should only be changed on recommendation on SAP or NFE consultant.

Encontre abaixo o snippet de código em que a alteração foi implementada pela SAP. A SAP introduziu uma nova configuração que oferece aos usuários a flexibilidade de manter a estrutura e os campos para os quais queremos que a validação seja realizada. Mas, iniciando o SP30, ele não utilizará / XNFE / XMLVALID-DEF_CHAR_SET. Portanto, tivemos que depurar e descobrir por nós mesmos o que mudou e o que precisa ser mantido para garantir que todas as validações funcionem como antes.īasicamente, antes do NFE 10.0 SP30, a SAP tinha a lógica escrita em torno da tabela / XNFE / XMLVALID campo DEF_CHAR_SET, isto é, se o valor for definido como X, o sistema executará a validação ADOPT_CHAR_SET, que costumava “#”. Infelizmente, esse link não lança muita luz sobre o que mudou e como afeta a validação atual. Essa alteração foi feita como parte da versão NFE 10.0 SP30, como documento neste link.

Sap layout 4.0 nota fiscal eletronica code#

Find below the code snippet where the change was implemented by SAP.Īo comparar e analisar o código uma e outra vez, percebemos que a SAP mudou a maneira como fundamentalmente realiza validações. SAP has introduced a new configuration that gives users the flexibility to maintain the structure and fields for which we want the validation to be performed. But starting SP30 it will not be using /XNFE/XMLVALID-DEF_CHAR_SET. if the value is set to X then system will perform ADOPT_CHAR_SET validation which used to take care of “#”. Thus, we had to debug and find out for ourselves what changed and going forward what needs to be maintained to ensure that all validations work as they were working before.īasically, before NFE 10.0 SP30 SAP had logic written around table /XNFE/XMLVALID field DEF_CHAR_SET i.e. This change was made as part of Version NFE 10.0 SP30 as document in this link.īut unfortunately this link does not throw much light on what has changed and how it impacts the current validation. On comparing and analyzing the code time and again we realized that SAP has changed the way it fundamentally performs validations. IF_STRUC – IT_NFE_DET with IF_FIELD INF_AD_PROD IF_STRUC – IS_NFE_INFADIC with IF_FIELD INF_AD_FISCO and

Sap layout 4.0 nota fiscal eletronica how to#

Thus we referred to Knowledge Management 2613668 to see how to handle special characters but no luck.īased on the KBB 2613668 there is a difference in version 3.1 and 4 layout.(In our case we were already on version 4 of layout)įor the new 4.0 layout if you have a special character like ‘#’, you should inform in table /XNFE/XMLVALID > NO_SPEC_CHAR > the character ‘#’ directly or the value ‘DEFAULT’, which will remove a predefined set of characters tried this but it was still failing with same error.Īfter comparing the XML generated in upgraded vs Non-upgraded environments we were able to drill down to two structures where the special character “#” was still being passed to SEFAZ. Assim, sempre que enviamos dados à SEFAZ, ele retornava o Código de Status 225 – Rejeição: Falha no Esquema XML do lote de NFe. Português – Durante nossa atualização do NFE 10.0 SP28 para uma versão superior, ou seja, NFE 10.0 SP30 +, observamos que o SAP mudou a maneira como as validações são realizadas, especialmente para caracteres especiais “#”.

Thus when ever we sent out data to SEFAZ it was returning Status Code 225 – Rejeição: Falha no Schema XML do lote de NFe. NFE 10.0 SP30 + we noticed that SAP has changed the way the validations are carried out especially for special characters “#”.

Sap layout 4.0 nota fiscal eletronica upgrade#

Note: Tradução para português usando o Google Translatorĭuring our upgrade from NFE 10.0 SP28 to a higher version i.e.