Tax Service - How to Access Tax Service Request and Response Payloads for a Document in your SAP S/4HANA (Cloud or OP)

[rodrigo_lumertz]

Note: This blog post, originally published in 2020, contains information related to an older version of this product. For information about the latest version, please see Integration with External Tax Calculation Engines – New Integration for SAP S/4HANA Cloud and SAP S/...

 

Note: The content of this blog post applies to the version of tax service that runs in the Neo environment.

 

If you are using the tax service connected to your SAP S/4HANA (cloud or on-premise) and you want to check how tax service built the JSON request and response payloads for a specific document, perform the following steps.

Access Tax Service Trace from Your SAP S/4HANA Cloud Fiori Launchpad

NOTE: To access this feature in SAP S/4HANA on-premise edition, use the TXS_TRACE transaction

See the steps below on how to access it through the Fiori Launchpad:

1. Login to your SAP S/4HANA Cloud Fiori Launchpad with the TAX_SPECIALIST role.


2. Go to the SLH, Tax Service tab.


3. Choose the Tax Service Trace Transaction tile.

Note: Every document and document item (where taxes were calculated by the tax service) contains a unique reference ID, also named Trace GUID, which will be used to access the specific request and response JSON payloads logged on Tax Service Audit Logger solution. See the Audit Logger official documentation for more information.

4. On the Tax Service Trace, you can search for the Trace GUID using other information about the document. See the example below:

Example:

Company Code: 1410

Application: V (Sales and Distribution)

Document Category: C (for Orders)

Document Number: 145 (Sales Order Number)

Fiscal Year: 2019

5. Choose the Execute button.


6. Copy the GUID from the result to use in the Tax Service Audit Logger solution in the next steps.

Ensure You Have the Right Authorization to Access Tax Service Audit Logger

In order to access the Tax Service Audit Logger data, you need to ensure you have the right authorization.

Create a new OAuth client on your SAP Cloud Platform account.

1. On your SAP Cloud Platform account, under Security > OAuth > Client, choose the Register New Client button.


2. Fill in the Name, ID, and Secret fields.


3. For the Subscription field, choose the taxservice application.


4. For the Authorization Grant, choose Client Credentials.

Ensure your client id is assigned to your Administrator role.

1. In your SAP Cloud Platform account, under the taxservice subscription application, access the Roles section.


2. Choose the Administrator role and ensure that under Individual Users there is an OAuth client with the following naming-convention: oauth_client_<client id>. Use the Client ID created on previous step. Example: oauth_client_taxuser_sapsupport.

Get a new bearer token.

1. On your SAP Cloud Platform account, under Security > OAuth > Branding, get the Token Endpoint.


2. Using a REST API client tool, get a new bearer token using the Token Endpoint, Client ID, and Secret from the previous steps. See the following screenshot of an example where I used the Postman tool to get a bearer token.

Reprinted with permission © Postdot Technologies Inc. All rights reserved.

Access Tax Service Request and Response Payloads from Audit Logger Using Document ID (GUID)

Now that the proper authorization is in place, you can use a REST API client tool to access the Tax Service Audit Logger endpoint to retrieve the request and response payloads for a given document ID (GUID).

1. On your SAP Cloud Platform account, under Applications > subscriptions, choose the taxservice application and copy the Application URL.


2. Concatenate the copied URL with /tenantAccessLogs


3. Add the documentId parameter with the GUID (copied in previous step) as the value.


4. For authorization, use the generated bearer token from previous step.

See the following screenshot of an example where I used the Postman tool to get the request and response and payloads.



Reprinted with permission © Postdot Technologies Inc. All rights reserved.

Result: You will see the JSON request payload on requestPayload field and the JSON response payload on systemId field.