The ABAP class that uses this communication is /EDGE/CL_CS_CON_AEAT_DIRECTO.
The transaction /EDGE/SII_ENDPNT will have to be customised with the configuration of the logical ports per company (from the SOAMANAGER).
If the proxies offered from the product are used for this type of communication, the parameterization corresponding to each book is the following one:
Book | Tax Agency | Proxy class |
---|---|---|
Issue invoices | AEAT | /EDGE/CO_SII_DSII_SOAP2 |
Received invoices | AEAT | /EDGE/CO_SII_DSII_SOAP3 |
Issue invoices | Álava | /EDGE/CO_SII_DSII_SOAP4 |
Received invoices | Álava | /EDGE/CO_SII_DSII_SOAP5 |
Issue invoices | Guipúzcoa | /EDGE/CO_SII_DSII_SOAP6 |
Received invoices | Guipúzcoa | /EDGE/CO_SII_DSII_SOAP7 |
Issue invoices | Vizcaya | /EDGE/CO_SII_DSII_SOAP8 |
Received invoices | Vizcaya | /EDGE/CO_SII_DSII_SOAP9 |
Issue invoices | ATC(Canarias) | /EDGE/CO_SII_CA_SII_SOAP |
Received invoices | ATC(Canarias) | /EDGE/CO_SII_CA_SII_SOAP1 |
If a company sends to AEAT and ATC(Canarias), for the entry corresponding to the ATC proxy class, the flag "ATC conciliation" must be marked.
Finally, the endpoint will have to be created.
In the SOAMANAGER, you must enter the PSE certificate for each logical port for the company code:
In the messaging tab, select the corresponding data. For AEAT and Navarra the transfer protocol corresponds to HTTP Header.
While for the rest of the provinces, it corresponds to SOAP Header.
In the Transport setting tab enter the Path, host name and corresponding port for each endpoint.