2.1.8.4. FTP communication (FUSE)

Communication with FUSE via FTP consists of 2 steps:

• Output XML file to SAP server path.

       Using the /EDGE/CL_SII_COM_AEAT_FTP class, the output communication of the file will be performed. To do this, in "Middleware Parameters" we must indicate this class as value of            the parameter CLASS_COMUNICACION and additionally indicate a new parameter called RUTA_FTP that will take as value the route of the SAP server where the generated XML file            will be deposited when sending a lot.

       With these settings, the XML files generated when sending batches will be stored in the indicated path waiting to be collected by FUSE for shipment and processing by the AEAT.

• Response XML reception from SAP server path.

       The reception of response XML files from FUSE is done by the program /EDGE/SII_RESPUESTA_FTP, which must be programmed as background job for the periodic reading of the path         where the response files will be left. This path will be indicated in "Middleware Settings" with the parameter RESPONSES_FTP.

       Once the answer XML file has been read, the indicated program treats it and makes the relevant modification of the batch in the Cockpit using the RFC /EDGE/SII_RESPUESTA_AEAT           and  /EDGE/SII_ESTADO_LOTE_MW functions that are the same as those used in the pass through processing ( Whether updating the status of the batch, an AEAT error message, etc).

       Finally, if in "Parameters Middleware" we have completed the parameter PROCESSED_FTP, processed XML files will be moved to the indicated path. If this parameter is not specified,            the  XML files will be deleted.