Skip to end of metadata
Go to start of metadata



NFE Inbound B2B - How To Use a Single Inbound Interface for NF-e and Cancellation for different NF-e versions.

1 - Interface Mapping

1.1 - NF-e 005a (v 1.10)

Go to the NFB2B_procNFe_TO_enhProcNFe interface mapping in the namespace http://sap.com/xi/NFE/005a in the Basis Objects node. Enter into Edit mode and click on Modify. In the Source Interface list, change the existing default namespace (http://sap.com/xi/NFE/005a) for the namespace http://sap.com/xi/NFE/006. You can leave the SWCV as the default one (which should be your custom SWCV). Save your interface mapping, click on Modify again and activate it. It should look something like this:

 

1.2 - Cancellation 005a (v 1.07)

Go to the CFB2B_enhProcCancNFe_TO_enhProcCancNFe interface mapping in the namespace http://sap.com/xi/NFE/005a in the Basis Objects node. Enter into Edit mode and click on Modify. In the Source Interface list, change the existing interface (CFB2B_procCancNFe_OB) for the NFB2B_procNFe_OB message interface of namespace http://sap.com/xi/NFE/006. Save your interface mapping, click on Modify again and activate it. It should look something like this:

 

 

1.3 - Cancellation 006 (v 2.00)

Go to the CFB2B_enhProcCancNFe_TO_enhProcCancNFe interface mapping in the namespace http://sap.com/xi/NFE/006 in the Basis Objects node. Enter into Edit mode and click on Modify. In the Source Interface list, change the existing interface (CFB2B_procCancNFe_OB) for the NFB2B_procNFe_OB message interface of namespace http://sap.com/xi/NFE/006. Save your interface mapping, click on Modify again and activate it. It should look something like this:


2 - Integration Directory

In the Integration Directory, transfer the NFB2B_WebAS_Inbound_B2B_NFe_006 Integration Scenario of the namespace http://sap.com/xi/NFE/006 into a Configuration Scenario, as you would do normally. This scenario doesn’t need to be changed anyhow. The Communication Channel may also be configured normally as it would be for a simple Incoming NFE interface.
After the configuration for the Incoming B2B NFE scenario is complete, it is just necessary to include the routing to the NF-e inbound interface (v 005a) and Cancellation inbound interface (v 005a and 006); we’ll be using the same configuration scenario for that, by just modifying some objects, as described below.

2.1 - Interface Determination

Open the Interface Determination object for the Incoming B2B NFE scenario. It should include one entry in the Configured Inbound Interfaces list: NFB2B_enhProcNFe_IB (with associated Interface Mapping NFB2B_procNFe_TO_enhProcNFe). Add other lines in the list and input the following content: 




Click on the Input Help button for the Interface Mapping data for this new line. It should bring the Interface Mapping that we had modified above:


 In the Condition column, insert the conditions:

(/p1:nfeProc EX AND /p1:nfeProc/@versao = 1.10)

(/p1:procCancNFe EX AND /p1:procCancNFe/@versao = 1.07)

(/p1:nfeProc EX AND /p1:nfeProc/@versao = 2.00)

(/p1:procCancNFe EX AND /p1:procCancNFe/@versao = 2.00)


After you’ve finished, save and activate the object. It should look like this:

 

2.2 - Receiver Agreement

After manually including a lot of new receiver interfaces to the Interface Determination, we need to manually create a lot of Receiver Agreements related to these interfaces:


 

 

 
  

Related Contents:

How to Use a Single E-mail for NF-e and Cancellation Messages in SAP GRC NFE Inbound B2B Interface