SAP Note 2591325

eDocument Spain: SII External Documents Cash

Payments

AIF Setup and other Settings

Manual Activities

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please
see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products
and services, if any. Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein.
This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may
be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on
these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
1. Logical path definition for upload folder
1.1. Go to FILE transaction
1.2. Press New entries button
1.3. In the table enter the values as below:

Logical file path Name

EDOC_ES_SII_EX_CASH_PAY_FILE_PATH eDocument Spain: SII External Docs Cash
Payments

1.4. Select the newly created line and press Assignment of Physical Paths to Logical Path from the
menu on the left side (under Logical File Path Definition).
1.5. Press New entries button
1.6. Enter UNIX for Syntax group field
1.7. In the Physical path enter the application server path where the XML files from the external
systems will be uploaded.
An example: /usr/sap/<SYSID>/SYS/src/<FILENAME>
1.8. Save
1.9. Select the Logical File Name Definition, Cross-Client from the menu on the left.
1.10. Press New entries button
1.11. In the displayed screen enter the values:
Log. file EDOC_ES_SII_EX_CASH_PAY_FILE_NAME
Name Document Spain: SII External Docs Cash
Payments
Physical file
Data format DIR
Applicat. area SD
Logical path EDOC_ES_SII_EX_CASH_PAY_FILE_PATH

1.12. Save

2. Logical path definition for Archive folder

2.1. Go to FILE transaction
2.2. Press New entries button
2.3. In the table enter the values as below:

Logical file path Name

EDOC_ES_SII_EX_CASH_PAY_ARCH_FILE_PATH eDocument Spain: SII External Docs Cash
Payments Archive

2.4. Select the newly created line and press Assignment of Physical Paths to Logical Path from the
menu on the left side (under Logical File Path Definition).
2.5. Press New entries button
2.6. Enter UNIX for Syntax group field
2.7. In the Physical path enter the application server path where the XML files from the external
systems will be uploaded.
An example: /usr/sap/<SYSID>/SYS/src/<FILENAME>

Please note that the physical path defined at point 2.7 MUST be different from the
physical path used for uploaded files, defined at point 1.7 in this document.

2.8. Save

Copyright/Trademark
 2.9. Select the Logical File Name Definition, Cross-Client from the menu on the left.
2.10. Press New entries button
2.11. In the displayed screen enter the values:
Log. file EDOC_ES_SII_EX_CASH_PAY_ARCHIVE_FILE_NAME
Name eDocument Spain: SII External Docs Cash Payments
Archive
Physical file
Data format DIR
Applicat. area SD
Logical path EDOC_ES_SII_EX_CASH_PAY_ARCH_FILE_PATH

2.12. Save

3. External system identification

As already used for Outgoing eDocument types, the external systems where the XML are created
for Incoming and Payments must be also maintained as described below.
3.1. Go to SM30 transaction
3.2. In the Table/View field enter EDOESSII_EXSYSV
3.3. Press Maintain button
3.4. Press New Entries button
3.5. In the displayed table enter the external system IDs for the systems you will get the XML from.
The name of the system will also be specified in the beginning of the uploaded XML files name.
Example:
External system ID External system
description
SYSID1 External system 1

3.6. Press Enter

3.7. Save

4. Response folders customizing

Please make sure you have defined the Logical path for each eDocument type used for each
Company Code.
4.1. Go to SM30 transaction
4.2. In the Table/View field enter EDOESSIIRESFOLV
4.3. Press Maintain button
4.4. Press New Entries button
4.5. In the displayed table enter the response logical paths corresponding to company code and
eDocument types.
An example:
Company Company eDoc Type Type Logical file
Code Name Description
ES01 Company ES_SII_XCD SII External EDOC_ES_SII_EX_CASH_PAY_FILE_NAME_RESP
description Cash Pay
Deregist
ES01 Company ES_SII_XCR SII External EDOC_ES_SII_EX_CASH_PAY_FILE_NAME_RESP
description Cash Pay
Register

Copyright/Trademark
 To assign a physical path to the logical path maintained in the table above please follow the example for
EDOC_ES_SII_EX_CASH_PAY_RESP_FILE_PATH:

(Note: steps 4.6-4.17 must be done for each logical path maintained above)

4.6. Go to FILE transaction

4.7. Press New entries button
4.8. In the table enter the values as below:

Logical file path Name

EDOC_ES_SII_EX_CASH_PAY_RESP_FILE_PATH eDocument Spain SII External Documents
Cash Payments: response folder

4.9. Select the newly created line and press Assignment of Physical Paths to Logical Path from the
menu on the left side (under Logical File Path Definition)
4.10. Press New entries button
4.11. Enter UNIX for Syntax group field
4.12. In the Physical path enter the application server path where the response XML files
received from the Tax Authority will be saved.
An example: /usr/sap/<SYSID>/SYS/src/<FILENAME>
4.13. Save
4.14. Select the Logical File Name Definition, Cross-Client from the menu on the left
4.15. Press New entries button
4.16. In the displayed screen enter the values:

Log. file EDOC_ES_SII_EX_CASH_PAY_FILE_NAME_RESP

Name eDocument Spain SII External Documents Cash
Payments: response files
Physical file
Data format DIR
Applicat. area SD
Logical path EDOC_ES_SII_EX_CASH_PAY_RESP_FILE_PATH

4.17. Save

5. Define eSOA Service Names

5.1. Execute transaction SM30.
5.2. Enter EDOSOASERV in the Table/View field.
5.3. Choose the Edit/Maintain push button.
5.4. Choose the New Entries push button
5.5. Insert the following entries incl. the description (by scrolling to the right):
In case you are configuring for several company codes, the SOA service name should not be multiplied,
i.e. each company code uses the same SOA service name but different logical ports. The logical port is
the one you will configure at point 8
SOA Service Name Company Logical Port SOA Service
Code Description
ES_SII_XEX_DER_CASH ES01 EDO_ES_SII_EXTERNAL_FILES_ES01 Cash Payments
Deregistration (Extenal
files)
ES_SII_XEX_DER_CASH ES02 EDO_ES_SII_EXTERNAL_FILES_ES02 Cash Payments
Deregistration (Extenal
files)
ES_SII_XEX_REG_CASH ES01 EDO_ES_SII_EXTERNAL_FILES_ES01 Cash Payments
Registration (Extenal
files)

Copyright/Trademark
ES_SII_XEX_REG_CASH ES02 EDO_ES_SII_EXTERNAL_FILES_ES02 Cash Payments
Registration (Extenal
files)

6. Define eDocument Interfaces

6.1. Execute transaction SM30
6.2. Enter EDOINTV in the Table/View field
6.3. Choose the Edit/Maintain push button.
6.4. Choose the New Entries push button
6.5. Maintain SOA Service Name entries as described below and save:
Interface ID SOA Service Name I/O Interface Description

ES_SII_DE_IN_CASH_PAY_EXT_REQ ES_SII_XEX_DER_CASH O Deregister external incoming cash

payments (request)
ES_SII_DE_IN_CASH_PAY_EXT_RES ES_SII_XEX_DER_CASH I Deregister external incoming cash
payments (response)
ES_SII_RE_IN_CASH_PAY_EXT_REQ ES_SII_XEX_REG_CASH O Register external incoming cash
payments (request)
ES_SII_RE_IN_CASH_PAY_EXT_RES ES_SII_XEX_REG_CASH I Register external incoming cash
payments (response)

7. Define eDocument interface types

7.1. Execute transaction SM30.
7.2. Enter EDOINTTYPEV in the Table/View field.
7.3. Choose the Edit/Maintain push button.
7.4. Choose the New Entries push button
7.5. Maintain company codes and assign eDocument type for Registration and Deregistration as in
example below (where ABCD is the company code):
Company eDocument type Type Description Interface type
code
ABCD ES_SII_XCD SII External Cash Pay Deregist AIF proxy

ABCD ES_SII_XCR SII External Cash Pay Register AIF proxy

8. Create the logical port in SOAMANAGER

8.1. In your ERP or SAP S/4HANA system, go to transaction SOAMANAGER and select Web Service
Configuration.

Copyright/Trademark
 8.2. Search for the proxy for Spain SII External Documents Incoming and Payments with the search
term CO_EDO_ESSII_EX_*

From the list select the proxy relevant for Cash Payments

CO_EDO_ESSII_EX_IN_CASH_PAYMEN

8.3. In the result list, select the proxy and create logical port(s). Choose Create > Manual Configuration.

The number of logical ports that you need to configure for the proxy depends on the number of AEAT
certificates / integration flows that you are configuring. For example, if you’re configuring for two
company codes (ES01 and ES02):

Proxy Name Logical Ports Description Path

CO_EDO_ESSII_EX_IN_CASH_PAYMEN EDO_ES_SII_EXTERNAL_FILES_ES01 Spain SII cxf/SpainSIICommunicateES01
eDocument -
Logical Port for

Copyright/Trademark
 External
Documents
ES01

CO_EDO_ESSII_EX_IN_CASH_PAYMEN EDO_ES_SII_EXTERNAL_FILES_ES02 Spain SII cxf/SpainSIICommunicateES02

eDocument -
Logical Port for
External
Documents
ES02

8.4. Enter the Logical Port Name and a Description:

8.5. The Consumer Security tab page configuration depends on the security being used for the SAP ERP or
SAP S/4HANA - SAP CLOUD PLATFORM INTEGRATION communication

a. If you use basic authentication, select the User ID / Password radio button and enter the User Name
and Password.
b. If you use certificate-based authentication, select the X.509 SSL client certificate radio button and
ensure that the required certificates are available in transaction STRUST.

8.6. On the HTTP Settings tab page, make the following entries
Note: The screenshots may look slightly different in your system depending on the release, but all the
required fields should be available.

Copyright/Trademark
Enter the appropriate values in the fields above according to the information below:
• Port 443 is the standard port for the HTTPS protocol.

• To find the Host, go to Cloud Platform Integration Web UI, choose Operations View and under

Managed Integration Content go to All. Use the search to find your iFlow as in the screen shot below:

• The entries for the Proxy fields depend on your company’s network settings. The proxy server
is needed to enable the connection to the internet through the firewall.

Copyright/Trademark
8.7. In the Messaging tab page, set Message ID Protocol to Suppress ID Transfer

8.8. No settings required in the tabs Identifiable Business Context and Operation Settings.
Just select Next and then Finish

Copyright/Trademark