CUSTOMER

Digital compliance service for India

Installation and Configuration Guide

TABLE OF CONTENTS
1 INTRODUCTION ............................................................................................................................... 3
1.1 How to use this document .............................................................................................................. 3
1.2 DCS Software Versions ................................................................................................................... 3
1.3 Support ............................................................................................................................................. 7
2 INSTALLATION ................................................................................................................................ 7
2.1 Prerequisite Checks ........................................................................................................................ 7
2.1.1 Account on the SAP Business Technology Platform .................................................................. 7
2.2 Setting up the Database .................................................................................................................. 8
2.2.1 Create DB Users/Schemas.............................................................................................................. 8
2.2.2 Change Initial Passwords ............................................................................................................... 9
2.2.3 Define Lifetime Validity for DB Users ............................................................................................ 9
2.2.4 Give Authorization/Roles for DB Users ......................................................................................... 9
2.3 Download the Software Components .......................................................................................... 11
2.4 Installation and Configuration of the Software Components ................................................... 12
2.4.1 Hana Delivery Unit (DU) Import (file type: tgz)............................................................................ 12
2.4.2 Java Deployment (file type: zip) ................................................................................................... 12
2.4.3 Fiori Content/ UI Deployment (file type: mtar) ............................................................................ 13
2.5 Data Source Binding ..................................................................................................................... 14
2.6 Enable Oauth Authentication and Register Clients ................................................................... 15
2.6.1 Enable Oauth Authentication: ...................................................................................................... 15
2.6.2 Register Oauth Clients: ................................................................................................................. 15
2.7 Configuring Destinations .............................................................................................................. 16
2.7.1 Getting DB host name .......................................................................................................................... 16
2.7.2 Updating Destinations ......................................................................................................................... 16
2.8 Assign Users to Authorization Groups ....................................................................................... 22
2.9 Configuring the XS scheduler jobs .............................................................................................. 24
2.10 Post Installation Steps ......................................................................................................................... 24
2.10.1 ITC Expiry Date Update ...................................................................................................................... 24
2.10.2 Integration flow Update ...................................................................................................................... 25
2.10.3 Annexures ........................................................................................................................................... 21

2
Digital compliance service for India, hereafter referred to as DCS, enables taxpayers to upload and download
data, process and reconcile invoice data that is to be reported to the GST Network (GSTN) using a GST
Suvidha Provider (GSP).
Any business system (SAP ERP and non-SAP ERP) can use DCS to send invoice details to the GSTN.

1 INTRODUCTION
This document is an installation and configuration guide for the components of the solution to be installed
and configured on the SAP Business Technology Platform (Neo environment), hereafter referred to as BTP,
and SAP Cloud Integration, hereafter referred to as SCI.

1.1 How to use this document

This document can be used for both initial installation for a new customer, and for an upgrade to the latest
DCS version.

For initial installation, please go through all the sections.

For an upgrade to latest version, please use all intermediate Release Tag of the Versions table below (e.g.
#DCS181) to get to the all the steps required for that release.

Important note on upgrades:

The solution
• should always be upgraded to the latest released version. The latest software components to be
downloaded are mentioned in Section 2.3
• can be upgraded to the latest version directly without going through intermediate versions. For
example, solution can be upgraded from DCS 1.3.0 to DCS 1.9.0 without installing DCS 1.4.0, DCS
1.5.0, DCS 1.6.0, DCS 1.7.0, or DCS 1.8.2.
However, there may be additional configuration steps which may have been introduced
during the intermediate versions. These steps are mandatory. These steps can be searched in
this document using the “Release Tags” below. For example, to upgrade from DCS 1.3.0 to DCS
1.9.0 please search for #DCS140, #DCS151, #DCS160, #DCS171, #DCS180, #DCS181, #DCS182.

For upgrades, Section 2.3 and Section 2.4 would always be mandatory.

1.2 DCS Software Versions

DCS versions follow the pattern “DCS x.x.x”. for example, DCS 1.6.0 or DCS 1.7.1. The first two numbers for
example ‘1.7’, represents a major feature whereas the third number ‘1.7.1’ indicates a patch/correction/minor
release on top of 1.7.0.

DCS Release Release Tag Comments

Version Date
Initial July 2017 #Initial

DCS 1.3.0 Jan 2019 #DCS130

DCS 1.4.0 July 2019 #DCS140

DCS 1.5.1 Jan 2020 #DCS151 For Configuration XS Jobs, Please refer to document
XS_JOB_Configuration.pdf attached to Note

3
DCS Release Release Tag Comments
Version Date
2460667.

SDCS 1.6.0 Feb 2020 #DCS160

DCS 1.7.1 May 2020 #DCS171 For updating Configuration XS Jobs, Please refer to
document XS_JOB_Configuration.pdf attached to
Note 2460667.

DCS 1.8.1 June 2020 #DCS181 For updating Configuration XS Jobs, Please refer to
document XS_JOB_Configuration.pdf attached to
Note 2460667.

DCS 1.8.2* August 2020 #DCS182 *IMPORTANT NOTE: GSTN has introduced a new
version of APIs called v2.0.

The below two Notes are mandatory to be

installed in ECC/S4H for this DCS version:

2824737 - eDocument India:CDN delinking

changes API version V2.0

2837257-eDocument India:Prerequisite note for

2824737

DCS 1.9.0 Jan 2021 #DCS190 The below SAP Notes are mandatory for DCS 1.9.0

3017261 - eDocument India: Prerequisite note for

3013196

3013196 - eDocument India: IRN mapping for

Sales/outward invoices

3017400 - eDocument India: IRN mapping for

Purchase/Inward invoices

Important: Please read the “Important_Metering

of Electronic Documents_Framework_25.pdf”
document attached to the DCS Master Note:
2460667

DCS 1.9.1 Feb 2021 #DCS191 The below SAP Notes are mandatory for DCS
1.9.1.

3025251 - eDocument India: Unable to cancel

outward invoice document when the
eDocument status is cancellation requested

4
DCS Release Release Tag Comments
Version Date
DCS 1.9.2 Mar 2021 #DCS192 Changes for upgrade from HANA 1.0 to HANA 2.0.
This patch will work for both Hana 1.0 and Hana
2.0. The patch can be installed before or after the
Hana DB version upgrade

DCS 1.9.3 April 2021 #DCS193 Bug Fix ‘Financial Period not visible for current
financial year”

DCS 1.10.0 May 2021 #DCS1100 The below SAP Notes are optional for DCS 1.10.0

3032721- eDocument India: Reconciliation subtype

mapping in EDOC_COCKPIT

Please refer to Annexure 1 for GSTR1 version 2.2

DCS 1.10.2 June 2021 #DCS1102 Mandatory Note To be Applied as part of DCS
1.10.2

3068914 - eDocument India: UQC and Invoice date

mapping

Please refer to the important information

mentioned in #DCS1102 Annexure 2: before
proceeding with installation steps

DCS 1.10.3 July 2021 #DCS1103 This is an Optional patch.

List of issues fixed in this Patch

DCS 1.10.4 August 2021 #DCS1104 This is an Optional patch.

List of issues fixed in this Patch

DCS 1.10.5 October 2021 #DCS1105 This is an Optional patch.

List of issues fixed in this Patch

DCS 1.11.0 December #DCS1110 What's New for Digital Compliance Service for India -
2021 SAP Help Portal

DCS 1.11.1 December #DCS1111 Please refer to SAP Security Note: 3132177
2021

DCS 1.11.2 January 2022 #DCS1112 What's New for Digital Compliance Service for India -
SAP Help Portal 1.11.2

DCS 1.11.3 March 2022 #DCS1113 What's New for Digital Compliance Service for India -
SAP Help Portal 1.11.3

5
DCS Release Release Tag Comments
Version Date
DCS 1.11.4 April 2022 #DCS1114 Deploy latest iFlow received on or after 30th April
from GSP provider . This integration flow upgrade
is mandatory for DCS 1.11.4 , without which GSTR1
filing would not work.

Please refer to the important information

mentioned in #DCS1114 Annexure 6 before
proceeding with installation steps

What's New for Digital Compliance Service for India -

SAP Help Portal 1.11.4

DCS 1.12.0 June 2022 #DCS1120 Deploy latest iFlow received on or after
21st June from GSP provider . This integration flow
upgrade is mandatory for DCS 1.12.0.

What's New for Digital Compliance Service for India -

SAP Help Portal 1.12.0

DCS 1.12.1 July 2022 #DCS1121 Deploy latest iFlow received on or after
28th July from GSP provider .

What's New for Digital Compliance Service for India -

SAP Help Portal 1.12.1

DCS 1.12.2 September #DCS1122 What's New for Digital Compliance Service for India -
2022 SAP Help Portal 1.12.2

DCS 1.13.0 October 2022 #DCS1130 What's New for Digital Compliance Service for India -
SAP Help Portal 1.13.0

To enable GSTR6 (ISD) in ECC or S/4HANA,

implement SAP Notes 3230666 and 3260125

Deploy latest iFlow received on or after

27th September from GSP provider .

DCS 1.13.1 December #DCS1131 What's New for Digital Compliance Service for India -
2022 SAP Help Portal 1.13.1

Deploy latest iFlow received on or after

9th December from GSP provider .

DCS 1.13.2 February #DCS1132 What's New for Digital Compliance Service for India -
2023 SAP Help Portal 1.13.2

For updating Configuration XS Jobs, Please refer to

document XS_JOB_Configuration.pdf attached to
Note 2460667.

Follow GSP provider instructions received on or after

28th Februar

DCS 1.13.3 March 2023 #DCS1133 What's New for Digital Compliance Service for India -
SAP Help Portal 1.13.3

6
 DCS Release Release Tag Comments
Version Date
DCS 1.14.0 June 2023 #DCS1140 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.0

DCS 1.14.1 June 2023 #DCS1141 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.1

DCS 1.14.2 August 2023 #DCS1142 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.2

DCS 1.14.4 November #DCS1144 What's New for Digital Compliance Service for India -
2023 SAP Help Portal 1.14.4

DCS 1.14.5 March 2024 #DCS1145 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.5

DCS 1.14.6 June 2024 #DCS1146 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.6

DCS 1.14.7 Nov 2024 #DCS1147 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.7

Mandatory Note To be Applied as part of DCS

1.14.7
Deploy latest iFlow received on or after
07th November from GSP provider .

DCS 1.14.8 Nov 2024 #DCS1148 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.8

DCS 1.14.9 Nov 2024 #DCS1149 What's New for Digital Compliance Service for India -
SAP Help Portal 1.14.9

DCS Dec 2024 #DCS11410 What's New for Digital Compliance Service for India -
1.14.10 SAP Help Portal 1.14.10

1.3 Support

If you face any issues while installing this solution, create an OSS incident under the CA-GTF-CSC-EDO-IN-
DC component.

2 INSTALLATION

Release Tag - #Initial

2.1 Prerequisite Checks

2.1.1 Account on the SAP Business Technology Platform

7
Please logon to the SAP Business Technology Platform (henceforth, BTP) Neo environment account cockpit
using the URL and User Id provided in the Welcome mail.
Welcome Mail sample:

SAP Business Technology Platform Cockpit:

Note: For initial setup of Subaccount please refer to Initial_Setup_Subaccount.pdf attached to Note 2460667

2.2 Setting up the Database

2.2.1 Create DB Users/Schemas

Create the following five Database Users/Schemas using the guidelines mentioned here.

The first step “Create a Database Administrator User” mentioned in above link would create an SAP HANA
DB Administrator.

8
 DB User/Schema Use Release Tag
GSTR1DB Database schema for the DCS GSTR1 Application #Initial

COMMDB Database schema for the DCS Communications Application #Initial

GSTR2DB Database schema for the DCS GSTR2 Application #Initial

GSTRMDCDB Database schema for the DCS Master Data and Configuration #DCS130
Application

ITC04DB Database schema for the DCS ITC-04 Application #DCS140

At the end of this step, there would be six DB users (Administrator, plus five application DB users listed in the
table above).

2.2.2 Change Initial Passwords

For each of the newly created DB users, change the initial password:
In the SAP Business Technology Platform account cockpit, choose SAP HANA / SAP ASE -> Databases &
Schemas.
Click on the DB/Schema ID column, Click on SAP HANA Web-based Development Workbench.
Login with the 5 database user credentials, one-by-one, and change the initial password.

Note on DB user passwords:

Please make a note of the DB user passwords. These are used to make data source bindings.

2.2.3 Define Lifetime Validity for DB Users

In the SAP Business Technology Platform cockpit, choose SAP HANA / SAP ASE -> Databases & Schemas.
Click on the DB/Schema ID column, Click on SAP HANA Web-based Development Workbench.
Use the SAP HANA DB administrator user credentials to log in.
Choose the Catalog tab.
Click the Open SQL Console icon.
Run the following SQL statements:
ALTER USER COMMDB disable password lifetime;
ALTER USER GSTR1DB disable password lifetime;
ALTER USER GSTR2DB disable password lifetime;
ALTER USER GSTRMDCDB disable password lifetime;
ALTER USER ITC04DB disable password lifetime;

2.2.4 Give Authorization/Roles for DB Users

In the SAP Business Technology Platform cockpit, choose SAP HANA / SAP ASE -> Databases & Schemas.
Click on the DB/Schema ID column, Click on SAP HANA Web-based Development Workbench.

1. #Initial Giving Access to GSTR1DB

Login as SYSTEM user. Choose the Catalog tab. Click the Open SQL Console icon.

9
Run the following SQL statements:
call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Administrator','GSTR1DB');
call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Developer','GSTR1DB');

GRANT SELECT,UPDATE,EXECUTE ON SCHEMA _SYS_REPO TO "GSTR1DB";

GRANT MODELING TO GSTR1DB;

GRANT SELECT,UPDATE,EXECUTE ON SCHEMA _SYS_BIC TO "GSTR1DB" WITH GRANT OPTION;

GRANT EXECUTE ON REPOSITORY_REST TO GSTR1DB WITH GRANT OPTION;

2. #Initial Giving Access to GSTR2DB

Login as SYSTEM user. Choose the Catalog tab. Click the Open SQL Console icon.
Run the following SQL statements:
call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Administrator','GSTR2DB');
call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Developer','GSTR2DB');

GRANT SELECT,UPDATE,EXECUTE ON SCHEMA _SYS_REPO TO "GSTR2DB";

GRANT MODELING TO GSTR2DB;
GRANT SELECT,UPDATE,EXECUTE ON SCHEMA _SYS_BIC TO "GSTR2DB" WITH GRANT OPTION;
GRANT EXECUTE ON REPOSITORY_REST TO GSTR2DB WITH GRANT OPTION;

3. #DCS130 : Data migration from ACRSCOREDB to GSTRMDCDB.

Important Note on data migration from ACRSCOREDB to GSTRMDCDB:

Master data before DCS 1.3.0 resided in ACRSCOREDB. This has been migrated to GSTRMDCDB. So only
customers upgrading from version 1.2.* should do this.
New Customers can ignore this step.

Login as ACRSCOREDB.
Choose the Catalog tab. Click the Open SQL Console icon.
Run the following SQL statements:

GRANT EXECUTE ON REPOSITORY_REST TO GSTRMDCDB WITH GRANT OPTION;

GRANT EXECUTE ON REPOSITORY_REST TO GSTR1DB WITH GRANT OPTION;
GRANT "EXECUTE","SELECT","UPDATE","INSERT" ON SCHEMA ACRSCOREDB TO GSTRMDCDB
WITH GRANT OPTION;
GRANT "EXECUTE" ,"SELECT","UPDATE","INSERT" ON SCHEMA ACRSCOREDB TO GSTR1DB WITH
GRANT OPTION;
GRANT SELECT ON SCHEMA _SYS_BIC TO "GSTRMDCDB";
GRANT UPDATE ON SCHEMA _SYS_BIC TO "GSTRMDCDB";
GRANT "EXECUTE" ,"SELECT","UPDATE","INSERT","SELECT METADATA","SELECT CDS METADATA"
ON SCHEMA ACRSCOREDB TO GSTR1DB WITH GRANT OPTION;

4. #DCS130 - Assigning Roles to GSTRMDCDB

10
Login as SYSTEM user.
Choose the Catalog tab. Click the Open SQL Console icon.
Run the following SQL statements:

call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Administrator','GSTRMDCDB');

call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Developer','GSTRMDCDB');
GRANT MODELING TO GSTRMDCDB;
GRANT SELECT, UPDATE, EXECUTE ON SCHEMA _SYS_BIC TO "GSTRMDCDB";
GRANT EXECUTE ON REPOSITORY_REST TO GSTRMDCDB WITH GRANT OPTION;
Logout from SYSTEM.

Login as GSTRMDCDB.
Choose the Catalog tab. Click the Open SQL Console icon.
Run the following SQL statements:
GRANT SELECT, UPDATE ON SCHEMA GSTRMDCDB TO _SYS_REPO WITH GRANT OPTION;

5. #DCS140 Assigning Roles to ITC04DB:

Important Note on ITC04DB:

ITC-04 Return support was introduced in DCS 1.4.0. So for customers upgrading from DCS 1.3.0 or below
versions, these steps are mandatory.

Login as SYSTEM user . Choose the Catalog tab. Click the Open SQL Console icon.

Run the following SQL statements:

call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Administrator','ITC04DB');
call _SYS_REPO.GRANT_ACTIVATED_ROLE ('[Link]::Developer','ITC04DB');
GRANT MODELING TO ITC04DB;
GRANT SELECT, UPDATE, EXECUTE ON SCHEMA _SYS_BIC TO "ITC04DB";
Logout SYSTEM user.

Login as ITC04DB.
Choose the Catalog tab. Click the Open SQL Console icon.
Run the following SQL statements:
GRANT "EXECUTE", "SELECT","UPDATE","INSERT","SELECT METADATA","SELECT CDS METADATA"
ON SCHEMA ITC04DB TO GSTRMDCDB WITH GRANT OPTION;
GRANT "EXECUTE" ,"SELECT","UPDATE","INSERT","SELECT METADATA","SELECT CDS METADATA"
ON SCHEMA ITC04DB TO GSTR1DB WITH GRANT OPTION;
GRANT SELECT, UPDATE, EXECUTE ON SCHEMA ITC04DB TO _SYS_REPO WITH GRANT OPTION;

2.3 Download the Software Components

#DCS11410

11
For every release, below three Software Components have to be downloaded from the Software center .

Software Components Download Page link Support Package Version

SLHGSTR1DU 100 Link (#DCS11410) SP 14 Patch 8

SLHDCSAPPL 100 Link (#DCS11410) SP 14 Patch 10

SLHDCSUI 100 Link (#DCS11410) SP 14 Patch 7

Please download all three software components in a local folder in your desktop/laptop.
Note: Please download the proper Support Package Version as mentioned in the above table.
Read again: Important Note on Upgrades.

2.4 Installation and Configuration of the Software Components

2.4.1 Hana Delivery Unit (DU) Import (file type: tgz)

In the SAP Business Technology Platform cockpit, choose SAP HANA / SAP ASE -> Databases & Schemas.
Click on the DB/Schema ID column, Click on SAP HANA Web-based Development Workbench.
Login as GSTR1DB
Import the SLHGSTR1DU delivery unit following the steps mentioned here.

2.4.2 Java Deployment (file type: zip)

Extract the SLHDCSAPPL archive in to a folder on your laptop/desktop.

Download and install the latest Java SE.
Download and extract Java Web Tomcat 9 SDK from [Link]
For more information, see Installing the SDK for Java Development.

Using the Console Client, run the following Neo command tool to deploy the Java application into the BTP
account
neo deploy --host <<landscape host>> --account <<account number>> --application gstrapp --source
<<location of the extracted folder>> --user <<P/S BTP account user with Administrative Role>>

Example: neo deploy --host [Link] --account a9ef421ca --application gstrapp --source
“C:\Users\john\Desktop\slhdcsappl” --user S111223344
After successful deployment, you should see the gstrapp Java application in your BTP cockpit in stopped
status.

12
Click on gstrapp link. In the resulting screen, Click on the button Update.

Enter the following value under JVM Arguments and click on Update.
-[Link].dcsgstr2db.max_active=32

2.4.3 Fiori Content/ UI Deployment (file type: mtar)

Deploy the Multi-target Application (MTA) archives following the steps mentioned here.

13
After the deployment of the MTA is complete, Install the Fiori Site following the below steps:
• Go to the Services panel and search for portal services.
• Select the portal and click the Go to Service link. This opens the home page in a new window.
• Click Site Directory and choose Edit for the Digital Compliance Services - GST India site.
• Choose the dropdown icon (V) choose Edit.
• This opens “Fiori Configuration Cockpit - Digital Compliance Services - GST India” and click on
publish site (Globe icon) in top right corner.
• Select check box for Clear HTML5 application cache and choose Publish.
• Once Successfully published then no need to clear browser cache by individual users to get the
latest changes.

Note on the Fiori Launchpad URL:

Share the Fiori Launchpad URL with your business users as this is the URL for the application.

2.5 Data Source Binding

This step binds the Java application to the DB Users created in Step 2.2.1.
In the SAP Business Technology Platform cockpit, choose Java Applications -> gstrapp -> Configuration ->
Data Source Bindings -> New Binding.
Create 5 Data Sources as given below. Use the DB user password set in Step 2.2.2 for the corresponding
DB Users

Data Source Custom Logon (DB User) Release Tag

jdbc/dcscommdb COMMDB #Initial

jdbc/dcsgstr1db GSTR1DB #Initial

jdbc/dcsgstr2db GSTR2DB #Initial

jdbc/gstrmdcdb GSTRMDCDB #DCS130

jdbc/dcsitc04db ITC04DB #DCS140

After binding the data sources, start the gstrapp application.

After 7-8 minutes, you should see the application in Started status as shown in the screenshot below.

Important Note on DB User Password change:

Every time when you reset/change the password, follow the below mandatory steps:
• stop the Java gstrapp application
• delete the corresponding data source binding
• Create new data source binding with the new password.

14
 • Start the Java application.

2.6 Enable Oauth Authentication and Register Clients

#Initial

2.6.1 Enable Oauth Authentication:

In the SAP Business Technology Platform cockpit, choose Java Applications -> gstrapp -> Authentication
Configuration.
Click on Activate Custom Configuration.
For Form type, add oAuth 2.0 from the drop-down.

2.6.2 Register Oauth Clients:

In the SAP Business Technology Platform cockpit, choose security -> oauth , go to the Clients tab.
Choose Register New Client.
• Enter gstrapp as the name.
• In the Subscription field, choose <account name>/gstrapp.
• In the ID field, enter the default ID generated by the system.
• Choose Client Credentials in the Authorization Grant field.
• The Confidential checkbox is automatically selected and is greyed out.
• In the Secret field, enter your password.
• In the Token Lifetime field, enter 60 minutes.
• Save your entries.

Note: Please note down the Secret, which will be used in many places during the setup.

15
2.7 Configuring Destinations

2.7.1 Getting DB host name

In the SAP Business Technology Platform cockpit, choose SAP HANA / SAP ASE -> Databases &
Schemas.
Click on the DB/Schema ID column, Click on SAP HANA Web-based Development Workbench.
You will get the DB hostname from the screenshot below

2.7.2 Updating Destinations

In the SAP Business Technology Platform cockpit, choose Connectivity -> Destinations, update the
configuration of below destinations.

16
#Initial

1. BG_DCS_COMM_DEST
• Choose the Edit button
• Change the authentication type to Basic Authentication.
• Enter the username (client ID) and password (secret) as created for gstrapp application in Register
Oauth Clients section
• Choose the Save button. The changes will take effect in a few minutes.

2. HCI_GSP

After you have configured the integration flow in your SAP Cloud Integration system(SCI), edit this
destination by entering the Integration flow URL details and parameters required for authentication.

#DCS1100
From DCS 1.10.0 version onwards, DCS application supports Basic authentication as well as X509
Certificate based authentication.
We recommend certificate-based authentication which is more secure than the basic authentication.
In case of Basic authentication enter the username and password as in the cloud integration tenant.

• URL: <SCI Integration flow URL>

• User: <SCI user>
• Password: <SCI user password> Save your entries.

17
To setup client certificate-based authentication for connectivity from SAP Business Technology Platform,
Neo environment DCS application to SAP Cloud Integration, please refer to Section 1 of
Client_Certificate_Authentication.pdf attached to Note 2460667

Note: For GSP Integration Flow (Integration flow), search for Integration from Digital Compliance Service to
GST Suvidha Provider and eSign Application Service Provider content catalog in the Integration Content Hub
of the SCI. This content provides a template Integration flow which you can adapt to connect to any GSP.

3. HCI_PING

After you have configured the integration flow in your SAP Cloud Integration system (SCI), edit this
destination by entering the Integration flow URL details and parameters required for authentication.

#DCS1100
From DCS 1.10.0 version onwards DCS application supports Basic authentication as well as X509 Certificate
based authentication.
We recommend certificate-based authentication which is more secure than the basic authentication.
In case of Basic authentication enter the username and password as in the cloud integration tenant.

• URL: <SCI Integration flow URL>

• User: <SCI user>
• Password: <SCI user Password>
Save your entries.

To setup client certificate-based authentication for connectivity from SAP Business Technology Platform,
Neo environment DCS application to SAP Cloud Integration, please refer to Section 1 of
Client_Certificate_Authentication.pdf attached to Note 2460667

Note: For Ping DCS Integration Flow, search for Integration from Digital Compliance Service to GST
Suvidha Provider and eSign Application Service Provider content catalog in the Integration Content Hub of
the CPI. This content provides an Integration flow which you can deploy in your test/productive Cloud
Platform Integration tenant.

4. GSTR_APP_SERVICE:
First get the DB hostname as mentioned in Getting DB host name. Update the DB host name and Set the
GSTR1DB user and password.

18
#DCS130

4. GSTR2_XS_SERVICE_DEST
First get the DB hostname as mentioned in Getting DB host name
Update Hostname in the URL and Set the GSTR2DB user and password.

5. PLATFORM_USERS_DEST - Update Hostname.

Get the Hostname from Subaccount URL (url highlighted in red - below screenshot) and update that
Hostname in the Destination URL appended with the prefix "api" in 2 places (highlighted in green - below
screenshot) .

Example:
If the Subaccount URL host : [Link]
URL should be : [Link]
In the Additional Properties, tokenURL should be: [Link]

6. PLATFORM_USERS_DEST
Update User and Password
First, create Platform API credentials as shown in the below screenshot (click on save).

19
 Then, Update Platform API credentials in the Destination as shown in below screenshot
Note: Please do not forget to Note down this ID and secret for future use.

#DCS1142

7. HCI_GSP_BASE – update URL and Credentials

A) Update URL.

After successful UI import you will see the destination with default values as shown in figure i.

20
Figure – i

Step1: Get the base URL.

Get the tmn base URL from HCI (figure ii/iii)

Figure – ii (If SAP Cloud Integration is ‘Neo’)

Figure – ii (If SAP Cloud Integration is ‘CF -Cloud Foundry)

21
 Step2: Append the sub-URL “api/v1/” (figure iv)

Figure – iii

Example:
If the tmn URL is: [Link]
URL must be: [Link]

B) Update Credentials
Step1: Update the credentials (userId and Password) provided in HCI_GSP destination.
(Or) Any other credentials to access SAP Cloud Integration.

2.8 Assign Users to Authorization Groups

#Initial

• [Link]
The admin role contains authorizations to perform configurations, GSTN authentications, and GSTR
report scheduling.
• [Link]
The tax admin role contains authorization for performing GSTIN filing status and GSTIN details.
• [Link]
The tax accountant role contains authorizations to save GSTR forms.
• [Link]
The source admin will be able to upload invoices and track invoices in the DCS application.

22
To enable easy assignment of roles to users, authorization groups are delivered. The below-mentioned table
mentions the assignment of each role to the corresponding authorization group:

Role Authorization Group

[Link] Administrators

[Link] Tax Adminstrators

[Link] Tax Accountants

[Link] Source Administrator

Assign the portal roles and Java application roles to the above-mentioned authorization groups using the
following steps:
In the cockpit, choose Security -> Authorizations. Choose the Groups tab.
Select a group and assign the roles as mentioned below:

Authorization Group Role

Administrators Subaccount: Portal

Application: nwc
Role: [Link]

Subaccount: <subaccount name>

Application: gstrapp
Role: [Link]

Tax Administrators Account: Portal

Application: nwc
Role: [Link]

Subaccount: <subaccount name>

Application: gstrapp
Role: dcs. taxAdmin

Tax Accountants Subaccount: Portal

Application: nwc
Role: [Link]

Subaccount: <subaccount name>

Application: gstrapp
Role: [Link]

Source Administrator Subaccount: Portal

Application: nwc
Role: [Link]

23
 Authorization Group Role

Subaccount: <subaccount name>

Application: gstrapp
Role: [Link]

Save the changes. Now you can assign users to the respective roles.
(If the user has access to see the invoices of all plants, please assign the user to GST_ALL role)
Add the OAuth client generated in Register Oauth Clients for the Source Administrator , Administrator, Tax
Accountants group. Add the OAuth client in the following format: oauth_client_<client ID>

Please refer to the below sample screenshot for roles Assignment and Client id Assignment, similarly other
Roles needs to be added based on the above table.

If you are integrating your ERP system with the DCS solution, you must maintain the client ID in your ERP
system. For more information, refer to the document “Integrate_to_DCS.pdf” attached to SAP Note 2465014.

2.9 Update Java application JVM Arguments

In the BTP Cockpit, select the option Java applications under Applications.

2.10 Configuring the XS scheduler jobs

Release Tag; #DCS151, #DCS171, #DCS181, #DCS190

This is a Mandatory Step. For Configuration XS Jobs, Please refer to document

XS_JOB_Configuration.pdf attached to Note 2460667.

2.10 Post Installation Steps

2.10.1 ITC Expiry Date Update

This is an OPTIONAL STEP- Do check with your TaxAccountant)

#DCS181 :
In #DCS181 and above the DCS application handles the Cut-off/Expiry date for ITC claim. This FY Expiry
date is typically, 30-Sep-xx+1.

24
Invoices uploaded by supplier after this cutoff date would not be reconciled. They would be in the Missing in
source and Missing in GSTN categories. Sub-category of such invoices would be "ITC_Expired".
If you want to check & update the invoices for this ITC_Expired scenario for the GSTIN’s and FYYEAR which
are already reconciled, you can execute the below procedure with right input.
Ensure below points before executing the procedure, because wrong way of executing this procedure might
impact the financial data in the database.
#PLEASE DO CHECK WITH YOUR TAX ACCOUNTANT
#CONFIRM YOU GIVE RIGHT INPUTS TO THE PROCEDURE
#CHECK NO GSTR2 ACTIVITIES GETS EXECUTED (LIKE ECC-to-DCS, GSTR2A PULL,
RECONCILIATION) BY ANY USER WHILE EXECUTING THE PROCEDURE for that taxpayer / Fiscal Year

In the SAP Business Technology Platform cockpit, choose SAP HANA / SAP ASE -> Databases &
Schemas.
Click on the DB/Schema ID column, Click on SAP HANA Web-based Development Workbench.
Login as GSTR2DB.
Choose the Catalog tab. Click the Open SQL Console icon.
Run the following SQL statements:

CALL "GSTR2DB"."[Link]::ItcExpiryDateReconUpdateProcedure"(
' <Replace with fisical year; For Ex: for 2019-20, the value will be 2019> ',
' <Replace with Itc ExpiryMonth; For Ex: For financial Year 2019-20 and the itcExpiryDate is on September
2020 then the value will be - 09 > ',
' <Replace with Itc ExpiryYear; For Ex: For financial Year 2019-20 and the itcExpiryDate is on September
2020 then the value will be - 2020> ',
' <Replace with taxpayer GSTIN ; For Ex: 34GSPTN0741G1ZZ; in case of all taxperGSTINs give - * > ',
? );
Example – For fy year – 2019-2020 and ItcExpiryDate – 31-Sep-2020, if you want to update for all Taxpayer
GSTN, then the query will be
CALL "GSTR2DB"."[Link]::ItcExpiryDateReconUpdateProcedure" ('2019','09','2020','*',? );

2.10.2 Integration flow Update

#DCS190
This is a MANDATORY step. In DCS Release 1.9.0, we have made Integration flow changes with support of
new API methods. Customers upgrading to 1.9.0 release should get the latest Integration flows from the
GSPs and update the latest Integration flow to reflect the feature changes.

#DCS1110
This is a MANDATORY step. In DCS Release 1.11.0, we have added a new mail adapter Integration flow to
support sending email notifications to taxpayer users and suppliers for any purchase invoice reconciliation
issues. Customers upgrading to 1.11.0 release should get the latest Mail Adapter Integration flow from the
GSPs and follow the steps as detailed in the Mail Adapter Integration Configuration_v1.0 document attached
to master note 2460667.
There is no change to the existing GSP Integration flow and need not be upgraded. However, it is
mandatory to update version for GSTR1 returns to 2.2 in the externalized parameter ‘gstr1_ret_ver’.

25
This change is required for the eInvoice pull and GSTR1 submit functionality to work correctly based on
latest GSTN API changes.

2.10.3 Annexures

#DCS1100 Annexure 1: GSTR1 version 2.2

Configuration:
GSTR1 version 2.2 has been enable at GSTN on 20th May 2021. DCS 1.10.0 is already pre-configured to
support version 2.2. (Attribute SupportRateWiseHSNSummary = Y)

#DCS1102 Annexure 2:
After deployment of this Hotfix once the java application started, a automatic migration query will run in the
GSTR2 tables to populate the financial year field for old invoices.
This automatic migration query is expected to take about 3 hours.
During these 3 hours, please do not upload/modify and Purchase invoices via eDocument cockpit or Excel
files.

#DCS1103 Annexure 3:
List of issues addressed in this patch:
• Allow Credit/Debit Notes for GSTR1 with tax rate as 0 (this was not allowed earlier).
• Minor UI navigation and UI validation issues in Inward Invoices and Reconciliation App.
• Enhanced validations for IMPG invoices for goods received via courier for Port Code and BOE
number; Please also install SAP Note 3079413 for this change.
• For Exports or sales to SEZ without payment of taxes, now it is allowed to pass a GST rate but no
amount (this was not allowed earlier).
• Minor UI issues in ITC-04 App.
• Simplified Delete/Cancel of invoices, either outward or inward, via Excel files. The list of mandatory
fields required to delete/cancel invoices in DCS is now only Financial Year, Invoice number, and
Invoice Type.
• Browser Cache clearing not required to be done by all users anymore. Please check additional one
step to performed during installation here.
• Other minor stability and usability issues identified.

#DCS1104 Annexure 4:
List of issues addressed in this patch:

• GSTR1/GSTR3B Filing Status, Filing Dates, and Supplier Name been added to the "Supplier
Invoices" and "Reconciliation" UI and Excel downloads.

• Filing status of IMPG received from Customs department will now be set automatically as "Filed".
Now IMPG invoices can now be reconciled.

• Minor bug fixes in ITC-04

• Other UI bug fixes in Inward Invoices reconciliation.

26
#DCS1105 Annexure 5:
List of issues addressed in this patch:

• Issue with scheduled pull of GSTR2A data : Due to an implementation change in GSTR2A
delta pull from GSTN, there was a issue of supplier invoices getting refreshed in DCS, if a
scheduler was configured. This is now fixed.
• Automated scheduler for GSTR2B Pull : GSTR2B Scheduler will run 13th of every month for
all GSTINs where GSTR2 is configured. There is no additional configuration required.
• Counterparty Filing status, date, and name in Multi-GSTIN Reconciliation Excel downloads.

#DCS1114 Annexure 6:

Deploy latest iFlow received on or after 30th April from GSP provider . This integration flow upgrade is
mandatory for DCS 1.11.4 , without which GSTR1 filing would not work.

The integration flow contains changes to support the following changes:

1. New API process flow introduced by GSTN for GSTR1 APIs.
2. Support for multiple versions for ledger APIs such as ‘Get Cash ITC Balance’ and ‘Get Liability
Ledger Details’.

As part of the new integration flow, new externalized parameter <gsp name>_gstn_gstrptf is
introduced where the base URL needs to be updated with the actual GSP url for
sandbox/production(For this please follow GSP provider implementation steps)

27
[Link]/contactsap

© 2020 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.

The information contained herein may be changed without prior notice. 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 or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP 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, and they should not be relied upon in making purchasing decisions.

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. See [Link]/copyright for additional trademark information and notices.