Communication by PI
For this type of communication there are no changes.
Asynchronous Cloud Communication
For this type of communication, class /EDGE/CL_SII_COM_AEAT_CLOUD_AS is provided by default, with this communication it is necessary to configure the Proxy to consume the Web Services as we have done for version 1.0 in the "Asynchronous Cloud Communication" section of section 2.1.8. Middleware customizing . This configuration will be carried out by the FUSE and ABAP implanter where the client will have to report the endPoint and the port.
For asynchronous Fuse version 1.1 the service to be selected is: /EDGE/CO_SII_CLAPROCESAR_LOTE1
Important: In the asysnchronous service we must change the configuration of the "Transport Settings" tab. In the access URL we have to put: / entrada_fuse/services/ProcesarLoteSII
