The 2 main pre-requisites to the upgrade of NFe 4.00 layout on the GRC NFe (SLL-NFE 10.0) are:
- Support Package 27
- PI 7.10 or higher
- Security Protocol TLS 1.2
Even if you are not planning to issue NFe with the new layout until the final due date (April/2018), you have to be ready to receive NFe in the 4.00 layout from vendors and partners that are already moving to the 4.00 this October (NFe Inbound & B2B)
OSS Notes
While the ERP oss notes are not released, SAP released this week the GRC NFe SP27 (SLL-NFE 10.0):
2422760 – SAPK-90027INSLLNFE: Support Package 27 for SLL-NFE 10.0
Be aware that the maintenance for SAP NetWeaver Java 7.0x ends in December 2017. Moreover, support for TLS 1.2 which is required for the new NFe 4.00 Layout is only available for SAP NetWeaver Java Server 7.10 or higher
Review the OSS Note 2462623 – SAP Exchange Infrastructure (XI) 7.0x has to be upgraded for more details.
Landscape
The landscape options are the following:
1 – SAP NF-e with SAP PI AEX
2 – SAP NF-e with SAP PI Dual Usage
3 – SAP NF-e with SAP PI 7.4 Dual Stack
Since the SP 27 will allow to handle the 3.10 and 4.00 and due to the complexity of the changes, it is recommended to implement the SP27 and XI ahead of the ERP changes, test and validate it still with the 3.10 layout.
4 – SAP NF-e full landscape
5 – PI Step-by-Step flow
SAP NetWeaver PI serves as middle-ware that routes messages between
SAP NFE components, government authorities, and business partners.
SAP NetWeaver PI provides the following integration features for NFE:
● Tailoring XML messages to SEFAZ requirements.
● Secure SOAP communication using client and server certificates.
● Switching from synchronous message transfer – used between SAP NetWeaver PI and SEFAZ – to an asynchronous message transfer due to performance reasons (async-sync bridge).
- Send the message asynchronously from SAP NFE to PI
- Embed legal document into a SOAP envelope
- Invoke SEFAZ Web Service synchronously via HTTPS with certificate-based authentication from PI
- Extract legal response from SEFAZ Web Service
- Send the message asynchronously to SAP NFE (WebAS)
Features
Here are some extra features added to this SP27 besides the legal changes required to the layout 4.00 as per Technical Note 2016.002:
-
NF-e Inbound
-
Support Avulsa NF-e (CPF as Issuer)
Avulsa NF-es are displayed in the Fiscal Workplace and have a different business determination than normal NF-es.
-
-
General Improvements
-
Log read access to sensitive personal data for main documents added
An application log is written whenever someone looks at the details of an NF-e, CT-e or MDF-e, or downloads the XML of an NF-e, CT-e or MDF-e. This log is switched off by default and can be switched on in Customizing.
-
-
Changed Features
-
To issue or receive NF-e with layout 4.00, you have to configure new integration scenarios in SAP NetWeaver Process Integration. These scenarios – and all other related artifacts – can be found in the new namespace http://sap.com/xi/NFE/009.
After the PI configuration has been created for the new scenarios, the handling for NF-e events and the distribution webservice must be switched to the new namespace. Please see SAP notes 2498688 and 2498689 for more details.
-
For more details, check this post: NFe 4.00 – Date and other changes
SAP Blog, SAP BRAZIL, SAP S/4HANA and more... 
Thank you for the information, it’s very helpful. However, I’m a little bit confused with the diagrams, and where the ERP system sits within the landscape. Would you be able to clarify? Also, in figure 1 it seems to suggest that you can run a Java 7.5 system alongside an ABAP (PI?) stack of a lower version. Is this correct?
LikeLike
Mark, I added what would be the full landscape. I didn’t add before because this post was only covering the SLL-NFE 10.0, in regard the usage of Java 7.5, I recommend you checking this great blog (unfortunately it is in Portuguese) from our friend Renan Correa where he explain the options you have better: https://blogs.sap.com/2017/03/03/fim-da-manutencao-do-netweaver-as-java-7.0-e-possiveis-impactos-na-nfe/
LikeLike
Thank you again, especially for the quick reply. Firstly, apologies, I am not an application person, so am approaching this with little knowledge of the functional NFe side.
The confusion on our side was around the ABAP stack of the PI system. We are currently running an ERP system alongside a dual stack PI 7.02 system. I know that you have to split the dual stack system, but I wasn’t sure if the ABAP side was still required, or whether it was only the Java side required.
Initially we thought that we could just build a new Java 7.5 system, configure and connect to ERP, and totally remove our current dual stack PI environment.
I think (after looking at the other blog) that the PI ABAP is still required though (possibly for storing the xml documents?) and therefore we will need to keep ours and upgrade after splitting.
LikeLike