Professional Documents
Culture Documents
43D Set-Up EN XX
43D Set-Up EN XX
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Required Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Add Certificate to Certificate Trust List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Create Technical Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 Create Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 Create Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Interaction with the SAP Cloud Service Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Note
This scope item establishes the communication with external systems using SAP Cloud Integration.
See the latest set-up instruction at SAP API Business Hub with this link: https://api.sap.com/package/
SAPS4HANAIntegrationwithExternalTaxCalculationEngines/overview .
This document describes the additional configuration steps that have to be carried out by customers in order to
activate the integration of SAP S/4HANA Cloud with External Tax Calculation Engines.
To integrate SAP S/4HANA Cloud with the external engines using SAP Cloud Integration, complete the steps
described in the Setting-up SAP Cloud Integration with External Tax Calculation Engines (SAP S/4HANA Cloud)
document, in the API Business Hub , under the SAP S/4HANA Integration with External Tax Calculation Engines
integration package.
To integrate SAP S/4HANA Cloud with the engines using SAP Localization Hub, Tax Service, complete the steps
that follow in this document.
As these configuration steps are customer-specific, they must be carried out by customer instead of being
delivered by SAP.
During the activities described in this guide, you are required to enter or provide system-specific information. To
ensure a smooth and efficient integration to SAP S/4HANA, we recommend that you have the information listed in
the table below at hand before starting the integration process.
Information Required
SAP Localization Hub, tax service endpoint Recommendation: Copy your Tax Service consumer endpoint.
SAP Localization Hub, tax service authentication You need your oAuth2.0 client credentials, as well as Tax Serv-
ice oAuth2.0 authorization and token endpoints.
2.2 Prerequisites
You have configured your SAP Localization Hub, tax service consumer account. For more information, please refer
to https://help.sap.com/viewer/product/SLH_tax_service/Cloud/en-US.
The communication arrangement SAP_COM_0249 must be activated in SAP S/4HANA for communication with
SAP Localization Hub, tax service.
Prerequisite
In order to carry out the following activity, a business user with a business role must exist. The business role
must contain the business catalog SAP_CORE_BC_SEC (Security). For example, you can use the business role
SAP_BR_ADMINISTRATOR (Administrator).
Procedure
below:
(.CER).
4. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
5. Choose Maintain Certificate Trust List.
6. Choose Add (+) to upload new certificates.
7. Browse the file for the exported certificates.
8. Choose Upload.
Prerequisite
In order to carry out the following activity, a business user with a business role must exist. The business role must
contain the business catalog SAP_CORE_BC_COM (Communication Management). For example, you can use the
business role SAP_BR_ADMINISTRATOR (Administrator).
Procedure
1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Select the Maintain Communication Users tile.
3. Choose New to create a user.
4. Enter a description for the user.
5. Assign a password for the user.
6. Choose Create.
7. Make a note of user data, which is required when you create the communication arrangement.
Procedure
1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Select the Communication Systems tile.
3. Choose New to create a new system.
4. Enter a system ID and a system name as the example below:
System ID: Tax_Service
5. System Name: choose Create.
6. Enter a host name. If a host name is not required for your scenario, enter the system ID. You get the host name
endpoint from url field in Your CF subaccount in SAP BTP Service Instance Tax Service instance Service
Keys .
7. In the OAuth 2.0 Settings section, enter the authorization endpoint of your SAP Localization Hub, tax service in
the Authorization Endpoint field, as described in the example below. You get the authorization endpoint of your
Note
Example: Authorization endpoint of SAP Localization Hub, tax service: <sap btp account
Subdomain>.authentication.sap.hana.ondemand.com/oauth/token
8. In the OAuth 2.0 Settings section, enter the token endpoint of your SAP Localization Hub, tax service as
described in the token endpoint field, as described in the example below. You get the token endpoint of your
SAP Localization Hub, tax service from UAA url field in Your CF subaccount in SAP BTP Service Instance
Tax Service instance Service Keys .
Example
9. Add a new authentication method in the User for Outbound Communication section.
1. Select OAuth 2.0 as the authentication method.
2. Enter your SAP Localization Hub, tax service OAuth2.0 client ID and client secret.
3. Close the dialog box.
10. Choose Save.
Procedure
1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Select the Communication Arrangements tile.
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0249 (SAP Localization Hub - Tax Service Integration).
5. Adjust the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System from the input help that was created in the
Create Communication System section.
8. The OAuth 2.0 Client ID that was created on Create Communication System section is automatically added to
the Outbound Communication section.
9. In the Outbound Services section and SAP Localization Hub - Tax Service Integration sub-section,
enter /tax/v0/quote in the Path field.
10. Choose Save.
FI-LOC-TXS
Use
Create a ticket.
Procedure
1. In case of problems with Tax Service integration, create a ticket for the component listed on Ticket Component
[page 11] with the SAP Support Launchpad.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.
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. All
other product and service names mentioned are the trademarks of their
respective companies.