Upgrade Guide Upgrade Guide to NFE Layout 3.

10
Target Audience Cx{ Consultants Cx{ Administrators

PUBLIC C a'DF[wS?d
Fe];7\O(\"ywJ\hGnGwFtc

Document History

The following table provides an overview of the most important document changes.
Version Date Description

1.0

2014-02-11

Required changes when upgrading to NFE SP16

2/10

PUBLIC

2014-02-11

Table of Contents

Chapter 1

Upgrade to Layout 3.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2014-02-11

PUBLIC

3/10

This page is left blank for documents that are printed on both sides.

Upgrade to Layout 3.10

1 Upgrade to Layout 3.10

As of SP16, SAP NFE supports the receiving and issuing of NF-es with the new Layout 3.10 and the contingency process SVC. For the new Layout, the government systems offer new Web Services with different structures. Therefore we have introduced a new function for integrating the ERP backend as well as new proxies for communicating to the Authority Web Services via PI. The process for issuing NF-es with the new Layout 3.1 was implemented as a process flow (which is similar to the inbound processing of NF-es). Therefore, the system offers a different set of monitors for NF-es, batches and service status results depending on which Layout is used.
Changes when Receiving NF-es with Layout 2.00 and Layout 3.10

The process of receiving NF-es did not change: the Fiscal Workplace shows all NF-es in both Layouts. The additional information available in the new Layout will be shown as additional fields or as separate tabs in the NF-e Details.
Changes when Issuing NF-es with Layout 2.00

1. 2.

3.

Customizing Nothing has changed as long as the contingency process SVC is not needed for these NF-e. Batch Jobs Nothing has changed, the same reports are scheduled as in earlier SPs:  /XNFE/PROCESS_REPORTS for sending batches and batch requests (the option Note Acknowledgements should be deactivated!!!)  /XNFE/EVENT_BATCH_SEND for sending Events (cancellation and correction letter)  /XNFE/GET_ACKNOWLEDGMENT for processing negative acknowledgements retrieved from PI  /XNFE/CHECK_SRV_STATUS for checking the Web Service availability of SEFAZ and SCAN (if you plan to use SVC, please read the respective section below)  /XNFE/UPDATE_ERP_STATUS for repeating the status update to ERP in case of technical problems Monitors Nothing has changed, the classic monitors for NF-es and NF-e batches have not changed; however only NF-es with Layout 2.00 are shown here. The Service Status Monitor has also not changed (unless you implement SVC).

2014-02-11

PUBLIC

5/10

Upgrade to Layout 3.10

Changes when issuing NF-e with Layout 3.10

The process for issuing NF-e with layout 3.10 differs from that of layout 2.00. It has been developed using new functions and new database tables. Therefore you need separate Customizing settings, batch Jobs and monitors: 1. Customizing For issuing NFE with layout 3.10 there are new customizing activities required:  NF-e: Maintain Connected Government Systems  NF-e: Maintain Version of Message Types (also for the issued events!)  NF-e: Define Query for Service Status for Authority (SEFAZ)  NF-e: Maintain Batch Parameters (also available as Current Settingsfor the system administrator) 2. Batch Jobs  New: /XNFE/NFE_BATCH_PROCESS for sending batches and batch requests  New: /XNFE/NFE_B2B_SEND for sending authorized NF-es to the Business Partners  New: /XNFE/NFE_SKIP_SEND for sending skip requests.  New: /XNFE/NFE_CONTINUE_PROCESS for repeating the status update to ERP in case of technical problems  New: /XNFE/NFE_CHECK_SRV_STATUS for checking the Web Service availability of SEFAZ, SCAN and SVC.  Nor changed: /XNFE/EVENT_BATCH_SEND for sending Events (cancellation and correction letter)  Not changed: /XNFE/GET_ACKNOWLEDGMENT for processing negative acknowledgements from PI 3. Monitors There are new monitors for NF-es with Layout 3.10:  New NF-e Monitor  New NF-e Batch Monitor  New Service Status Monitor (SEFAZ, SCAN and SVC) 4. BAdI The connected ERP system transfers the NF-e data using the new function module /XNFE/ OUTNFE_CREATE. This function provides two generic parameters IT_NFE_EXT1 & IT_NFE_EXT2 for transferring additional information (for example, data needed for the B2B communication) to the SAP NFE system. A new BAdI Saving of Extension Parameters from ERP Back-End System writes this data to the database. 5. PI Configuration The new WebServices require a new set of PI Configuration the corresponding integration scenarios are delivered with namespace http://sap.com/xi/NFE/008. Note that you also need to configure the Integration Scenarios for issuing events from the same namespace! The only

6/10

PUBLIC

2014-02-11

Upgrade to Layout 3.10

exception are the two integration scenarios needed for the XML Download which you can still access athttp://sap.com/xi/NFE/006.
Changes when using the new contingency system SVC

As of SP16, the service status check was extended to support the SVC contingency systems. In order to not disrupt the issuing of NF-es with Layout 2.00, the new capabilities were implemented in parallel (including the backend function, customizing and the monitor). The new Service Status Check is always used for NF-es with Layout 3.10, whereas the older version is used for Layout 2.00. Before you can switch to the new Service Status Check you need to change the SAP NFE system with SAP Note 1973306 and the ERP backend by implementing SAP Note 1965381.
CAUTION

Before you implement these notes, configure the new Service Status Check and make sure that the report for reading the information from the authority systems is being run regularly. 1. Customizing SW NF-e: Maintain Connected Government Systems SW NF-e: Maintain Version of Message Types SW NF-e: Define Query for Service Status for Authority (SEFAZ) Batch Jobs New: /XNFE/NFE_CHECK_SRV_STATUS for checking the Web Service availability of SEFAZ, SCAN and SVC Monitor New Service Status Monitor (SEFAZ, SCAN and SVC)

2.

3.

2014-02-11

PUBLIC

7/10

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

Copyright 2014 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Disclaimer

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

8/10

PUBLIC

2014-02-11

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

Copyright 2014 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.