Note1743455 NFEonAEX
Note1743455 NFEonAEX
Note1743455 NFEonAEX
Copyright/Trademark
Approach
With the release of SAP Process Integration 7.31 it is possible to run the system as an AEX (Advanced
Adapter Engine Extended /Java-only / single stack) installation. In the current release of the PI content of
SAP NFE, ccBPM processes are used for government communication. These ccBPM processes are not
supported on a Java installation since they are based on ABAP.
To enable the NFE scenarios to run on a Java-only PI installation, new adapter modules replicating the
ccBPM logic in combination with the existing RequestResponseBean and ResponseOnewayBean are used.
The new adapter modules read and store, add, and remove values from the payload. Furthermore,
acknowledgement handling is achieved by using specific adapter modules. In the remainder of this note, it is
described how to configure the SEFAZ communication in PI.
Copyright/Trademark
Configuration Steps
The configuration of AEX PI contains of several steps:
1. Configure NWA Destination
2. Configure integration scenarios
3. Manual post processing
4. Complete configuration
For AEX PI configuration integration scenarios with the infix AEX have to be used. In this case, the
integration scenario NFESC_AEX_WebAS_Outbound_NFeStatusCheck is configured.
First, create the Configuration Scenario and select the relevant Process Integration Scenario. Then, open the
Model Configurator and ensure the Configuration for Advanced Adapter Engine flag is checked.
Select the Web AS Template swim lane and choose your SAP NFE backend. Use Without Header Mapping
option for the second group of colons.
Copyright/Trademark
Select Government System swim lane and add all required SEFAZ systems to the swim lane.
Select the (first) connection from Web AS to government system and maintain the Communication Channel.
Please create communication channels with template using the New button.
The sender channel AEX_WAS_XI_SND can be reused across all scenarios; the receiver channel is
scenario specific.
When you create AEX_WAS_XI_SND channel check the tab Acknowledgement Handling tab.
It contains a name of an NWA HTTP Destination pointing to the SAP NFE backend for delivering XI
acknowledgements (see previous step).
Select the second connection and complete the channel configuration. Use templates to generate
communication channels. You can reuse both sender and receiver channel across all scenarios.
Save the model and perform the generation using Integrated Configuration scope.
Close the generator wizard and switch to the Objects tab in the configuration scenario. For every SEFAZ
system there will be a separate integrated configuration. In addition there will be one integrated configuration
with the SAP NFE backend as the sender.
3. Manual post-processing
3.1. Copy response Integrated Configurations
Generated integrated configuration objects in request-response scenarios need to be post processed.
List of affected scenarios:
Copyright/Trademark
http://sap.com/xi/NFE/006
BATCH_AEX_WebAS_Outbound_Batch
BATSR_AEX_WebAS_Outbound_BatchStatusRequest
EVENT_AEX_WebAS_Outbound_EventReceipt
EVENT_CANCR_AEX_WebAS_Outbound_EventCancellationRequest
EVENT_OPPRG_AEX_WebAS_Outbound_EventOperationProgressRequest
NFEDL_AEX_WebAS_Outbound_NFeDownloadRequest
NFESC_AEX_WebAS_Outbound_NFeStatusCheck
SKIPR_AEX_WebAS_Outbound_SkippingRequest
http://sap.com/xi/NFE/008
BATCH_AEX_WebAS_Outbound_Batch
BATCH_AEX_WebAS_Outbound_BatchZip
BATSR_AEX_WebAS_Outbound_BatchStatusRequest
EVENT_AEX_WebAS_Outbound_EventReceipt
NFESC_AEX_WebAS_Outbound_NFeStatusCheck
SKIPR_AEX_WebAS_Outbound_SkippingRequest
http://sap.com/xi/CTE/104
CTESC_AEX_WebAS_Outbound_CTeStatusCheck
http://sap.com/xi/CTE/200
CTESC_AEX_WebAS_Outbound_CTeStatusCheck
http://sap.com/xi/MDFE/100
MDFESC_AEX_WebAS_Outbound_MDFeStatusCheck
Open the response integrated configuration having SEFAZ as sender party/service. Click on Copy Object
toolbar button and provide the NFE Backend system as virtual receiver.
Assign the resulting integrated configuration to the configuration scenario. Delete original integrated
configuration.
Copyright/Trademark
ETB2B_AEX_WebAS_Outbound_B2B_Event
NTB2B_AEX_WebAS_Outbound_B2B_NFe
http://sap.com/xi/CTE/104
CancCTB2B_AEX_WebAS_Outbound_B2B_Cancellation
CTB2B_AEX_WebAS_Outbound_B2B_CTe
http://sap.com/xi/CTE/200
CTB2B_AEX_WebAS_Outbound_B2B_CTe
Open the integrated configuration. Click on Copy Object toolbar button. Select Sender uses Virtual
Receiver checkbox. Enter * (asterix) as value of virutual party and service. Assign the resulting integrated
configuration to the configuration scenario. Delete original integrated configuration.
Copyright/Trademark
The proxy connection for the other interfaces would then remain the standard ABAP to ABAP connection.
Copyright/Trademark