SAP Localization Hub, Digital Compliance Service for India for the Neo Environment

SAP SE

SAP Localization Hub, Digital Compliance Service for India for ...

Guide performed during installation. New. 2021-0. 7-30. SAP Lo caliza tion. Hub,. Digital. Compli ance. Service. India. Globali zation. Neo.

This document is not included as part of the Installation Guides, Configuration Guides, ... Quick Link on SAP Service Marketplace or SCN.

User Administration and Authentication. ... Manual upload: shows ERP Request Details ... User Management in the SAP HANA Security Guide.

Browser built in viewer
PDF Viewer
Universal Document Viewer
Google Docs View
Google Drive View
Download Document [pdf]

File Info : application/pdf, 124 Pages, 1.58MB

Document

loio607db81e4ced4933a83034927a5bd708

PUBLIC 2021-09-29
SAP Localization Hub, Digital Compliance Service for India for the Neo Environment
THE BEST RUN

Content

What Is Digital Compliance Service for India?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

What's New for Digital Compliance Service for India . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Digital Compliance Service for India Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Digital Compliance Service for India Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Implementation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Security Guide for Digital Compliance Service for India. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7.2 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

7.3 Security Aspects of Data, Data Flow and Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

7.4 User Administration and Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

7.5 Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7.6 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7.7 Data Storage Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7.8 Security-Relevant Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

7.9 Services for Security Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Digital Compliance Service for India Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

8.1 eDocument Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

eDocument Basic Enablement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Reporting Goods and Services Tax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Customizing for eDocument - India. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Implementation Considerations for eDocument - India. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Business Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

eDocument Individual Invoice Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

8.2 Setup Digital Compliance Service for India. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Digital Compliance Service for India Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.1 Integrate Digital Compliance Service for India with a GSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.2 Integrate Digital Compliance Service for India with eSign Application Service Provider . . . . . . . . . . . 47

eSign ASP Integration content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Integration Content Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

eSign ASP SAPUI5 Application Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Digital Signature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Content

10 Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 10.1 Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Manage Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Manage Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 10.2 Returns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 View GSTR9 Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 View GSTR3B Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 File or Save ITC-04 Returns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Reconcile ISD Invoices (GSTR6). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 File a GSTR1 Return. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Reconcile Inward Invoices (GSTR2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 10.3 Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Manage Inward Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Manage Outward Invoices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 GSP Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Digital Compliance Service Health Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Counterparty Filing Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 GSTIN Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 GSTN Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

FAQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

11.1 eDocument Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

11.2 DCS: Installation and Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

11.3 Users, Roles and Authorization Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

11.4 DCS: Connecting to GSP via SAP Cloud Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118

11.5 GSTR1: Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

11.6 GSTR: Submit and File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Content

PUBLIC

1 What Is Digital Compliance Service for India?

Manage your compliance reporting requirements of Goods and Services Tax (GST) for India
SAP Localization Hub, digital compliance service for India offers the capability to comply to various GST returns to GSTN in the format prescribed by GSTN

Environment
This service runs in the Neo environment.

Features

Details of Outward Supplies All outward (sales)supplies invoices uploaded from various source systems can be viewed using this feature

Details of Inward Supplies

The tax computation content is pre-delivered, and has in-built rules to compute applicable taxes

Input Credit Reconciliation Inward (purchase) invoices can be reconciled between source copy of invoices and the supplier copy of invoices (retrieved from GSTN)

Monthly GSTR3B Return

A view of the outward and inward invoices can be taken as input to file GSTR3B in the GSTN

Annual Return

A view of some of the sections of GSTR9, of data taken from GSTR3B data and inward/outward invoices, can be taken as input to file GSTR9 in the GSTN

Data Transfer Monitor at ECC/S4Hana Level

Feature to check the status of various documents that have been transferred to DCS

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What Is Digital Compliance Service for India?

DCS Components
Next: What's New for Digital Compliance Service for India [page 6]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What Is Digital Compliance Service for India?

PUBLIC

2 What's New for Digital Compliance Service for India

The following table includes information about new features and changes introduced during each releases. It does not provide information about changes released with patches.

Techni cal Com ponent

Capa bility

Envi ron ment

Title

Description

Type

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.10.5

The following GST Simplification features and enhancements are New released:
Resolved issue with scheduled pull of GSTR2A data: Be cause of an implementation change in GSTR2A delta pull from GSTN, there was an issue of supplier invoices getting re freshed in digital compliance service for India, in case a scheduler is configured.
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.
Added counterparty filing status, date, and name in MultiGSTIN Reconciliation Excel downloads.

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.10.4

The following GST Simplification features and enhancements are New released:
Added GSTR1/GSTR3B filing status, filing dates, and supplier name to the Supplier Invoices and Reconciliation UI and Excel downloads.
Filing status of IMPG received from customs department will now be set automatically to Filed. Also, IMPG invoices can be reconciled now.

Availa ble as of 2021-0 9-30
2021-0 8-31

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What's New for Digital Compliance Service for India

Techni cal Com ponent

Capa bility

Envi ron ment

Title

Description

Type

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.10.3

The following GST Simplification features and enhancements are New released:
Allowed Credit/Debit notes for GSTR1 with zero tax rate. Allowed to pass a GST rate with no amount for exports or
sales to SEZ without payment of taxes.
Simplified Delete/Cancel of invoices, either by outward/ inward or, via Excel files. The list of mandatory fields required to delete/cancel invoices in digital compliance service for In dia are Financial Year, Invoice number, and Invoice Type.
No requirement to clear browser cache now: Check addi tional step in the section 2.4.3 Fiori Content/ UI Deploy ment (file type: mtar) of the Installation and Configuration Guide performed during installation.

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.10.2

The following GST Simplification features and enhancements are New released:
Supporting GSTR1 ver 2, UQC issue for service lines: UQC is sent as NA and quantity as zero. Install SAP Note 3068914 in your ERP system to support this change.
Usability improvements for Inward Invoices: Supporting up load of purchase invoices to digital compliance service for In dia with different FY invoice date but same period. Issue oc curs when supplier invoice gets posted in the next FY (invoice date is previous FY) in ERP, and supplier has generated an other invoice with the same number in current FY.

Availa ble as of 2021-0 7-30
2021-0 6-29

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What's New for Digital Compliance Service for India

PUBLIC

Techni cal Com ponent

Capa bility

Envi ron ment

Title

Description

Type

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.10.0

The following GST Simplification features and enhancements are New released:
Scheduler for eInvoice Pull from GSTN: Now, eInvoice data pull from GSTN can be scheduled/automated. For more infor mation, see Configure Scheduler [page 75].
New App GSTN Reports: A new app GSTN Reports has been introduced. The reports provide comparison between differ ent returns for Tax liability and ITC. For more information, see GSTN Reports [page 105].
New Reconciliation sub category RCM Flag Mismatch: A new subcategory RCM flag mismatch under Probable Match category has been introduced. For more information, see Reconciliation [page 95].
Usability improvements for existing screens. Performance improvements to the Inward Invoice
Reconciliation.
Hotspots and help introduced for user assistance. Check out the Question mark available on the top-right corner of the application.
Support for the new GSTR1 version 2.2: GSTR1 version 2.2 was enabled at GSTN on 20th May 2021. DCS 1.10.0 is pre configured to support version 2.2. For more information, refer to Annexure 1: GSTR1 version 2.2 in the Installation_Config uration_Guide.pdf attached to the SAP Note 2460667 .
Reconciliation Category, Status, and Subcategory (new) can be accessed in the eDocument cockpit in your backend ECC/ S4Hana system. For more information, see SAP Note 2875002 and SAP Note 3032721 .
You can now enable client certificatebased authentication for connectivity from SAP Business Technology Platform, Neo environment DCS application to SAP Cloud Integration (SCI). Refer to SCI_Client_Certificate_Authentication.pdf at tached to the SAP Note 2460667 .

Availa ble as of
2021-0 5-21

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What's New for Digital Compliance Service for India

Techni cal Com ponent

Capa bility

Envi ron ment

Title

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.9.0

Description

Type

The following GST Simplification features and enhancements are New released:
GSTR1: Implementation of e-Invoice API, which pulls the e-In voice from GSTN. Reconciliation of e-Invoice and DCS data.
Additional IRN fields in Excel Upload and ERP.
Credit/Debit notes to accept quantity field via Excel/ERP (using BADI).
UQC and HSN validation for CDN de-linked invoice (in voices without any reference).
GSTR2: Implementation of GSTR2B API, which pulls the autodrafted ITC statement. Reconciliation of GSTR2B with GSTR2 data. Proposed GSTR3B based on action taken using Reconci liation. New Tax payer Mismatch Report under Reconciliation Reports. Probable Report to support more volume with asynchro nous download. Enhancement of smart link feature to pick Reconciliation category instead of 'CM Manual Match'. Reconciliation Upload to support huge volume using CSV upload. CSV can be generated using Generate CSV but ton present in the Reconciliation Invoice Download. Counterparty Summary for Purchase Register Invoices.
Addition of User Remarks field to update the Reconcilia tion Remarks for each invoice.
Read-only Access - To restrict users to have only reading access for Reconciliation.
GSTN Utilities: Combined GSTN Utilities (older) and Counterparty Filing Status tiles into a single functional tile to support both features. Supporting Filing Status for any ad-hoc Counterparty GSTINs. The ad-hoc Counterparty GSTINs can also be pasted directly into the UI.
GSTR3B: Legal Change - Provisional ITC can be availed up to 5%.
User Web Assistance: Enabled Web assistant or in-app help.

Availa ble as of
2021-0 1-29

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What's New for Digital Compliance Service for India

PUBLIC

Techni cal Com ponent

Capa bility

Envi ron ment

Title

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.8.0

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.7.0

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.6.0

Description

Type

The following GST Simplification features are released:
GSTR1: Additional Tax Validations: Source system to DCS sys tem
GSTR2: Automated scheduled pull of GSTR2A invoices from GSTN Probable Match as a report Additional filters in Manage Inward and Purchase Regis ter ITC Expiry setting for Expired invoices Run Reconciliation for Multiple GSTIN Additional Tax Validations: Source system to DCS sys tem Amendment details in Manage Inward process Smart Linking for 'Missing in Source' and 'Missing in GSTIN'

New

The following GST Simplification features are released:
ANX-1: Upload to GSTN Pull ANX-1 from GSTN and compare with DCS Upload invoices from Excel/REST API
ANX-2: Smart Linking for 'Missing in Source' and 'Missing in GSTIN' ANX-2 Upload (Buyer Action) to GST Upload invoices from Excel/ REST API Upload to GSTN

New

Reconciliation views as per GSTR2/ PR Financial period Additional filters in Reconciliation/ PR screens Comprehensive report: Removed few restrictions in number
of GSTINs/Financial Periods Enhancements to Excel Upload

New

Availa ble as of 2020-0 6-12
2020-0 4-08
2019-0 2-20

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What's New for Digital Compliance Service for India

Techni cal Com ponent

Capa bility

Envi ron ment

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Title Re lease 1.5.0
Re lease 1.4.0

Description

Type

GSTR3B: Get ALL ledgers from GSTN

New

Show ledger values in GSTR3B app

GSTR2:

GSTR2A pulls based on changes in GSTN API

Delta Pull: Pull the GSTR2A invoices based on FROM date (from_date)

SAP ERP system:

Display of Purchase Invoice Reconciliation Action Sta tuses (Reconciliation Accepted/ Reconciliation Pending/ Reconciliation Rejected / To Be Reconciled) in the eDo cument Cockpit

Display of Purchase Invoice Reconciliation Category Sta tuses (Probable Match, Partial Match, Missing In GSTN, Complete Match) in the eDocument Cockpit

GSTIN Utility:

Getting the Counterparty Filing Status and Store the Data in DCS

Searching for Counterparty Details and Store the Data in DCS

ITC04:

Changes to JW2M table and added additional fields

GSTR2: New UI for GSTR2, GSTR2A and Reconciliation, with graphs and tables to aid visual analytics. Enhanced Reconciliation Process Reconciliation summary Information GSTIN Validation using GSTN Taxpayer API GSTN filing status, filing date for a given Period
GSTR6: New GST Return for ISD invoices: Pull GSTR6A invoices from GSTN to DCS Upload GSTR6 invoices to DCS Reconcile GSTR6 invoices from DCS and GSTN
ITC04: New GST Return for Job works Uploading of Challans: Manufacturer to Job Worker to DCS through eDocuments Uploading of Challans: Job Worker to Manufacturer to DCS from SAP Standard subcontracting Pushing the Challans from DCS to GSTN Summary level Comparison between DCS and GSTN

New

Availa ble as of 2019-1 2-18
2019-0 7-22

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What's New for Digital Compliance Service for India

PUBLIC

Techni cal Com ponent

Capa bility

Envi ron ment

Title

SAP Lo Globali Neo caliza zation tion Hub, Digital Compli ance Service India

Re lease 1.3.0

Description

Type

GSTR1 Submit and File Summary level Comparison Counter Party level Comparison State Code level Comparison Invoice Level Comparison Pull invoices from GSTN: Section Level Pull invoices from GSTN: Counter Party Level (B2B, CDNR) Pull invoices from GSTN: State Code Level (B2CL) Download Summary Download pulled Invoices
Manage Configuration User Assignment New design for configure business places
Reconciliation Features Multiple Reconciliation Category Multiple Counter Party selection Reconciliation runs for the year Retain the accepted status if re-pull invoices again Change of Taxpayer Export with filter: multiple reconciliation category
Manage Inward Invoices Manual upload: shows ERP Request Details Show amendment details along with invoice details

New

You can see a video explaining all the above features here . Also, for more information on previous release see the SAP Note 2460667

Availa ble as of
2019-0 2-27

Previous: What Is Digital Compliance Service for India? [page 4] Next: Digital Compliance Service for India Overview [page 13]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment What's New for Digital Compliance Service for India

3 Digital Compliance Service for India Overview
SAP Localization Hub, digital compliance service for India, hereby referred to as digital compliance service for India, provides you with solutions that enable you to fulfill your compliance reporting requirements of Goods and Services Tax (GST) for India.
The digital compliance service for India comprises of the following applications:
Manage Configuration SAP provides you with report categories that help you fulfill the GST compliance reporting requirements in India. In this app, you make the connection between the reporting entities for which you should submit the compliance reports and the content provided by SAP. Using this app, you can perform the following: Define reporting entities for compliance reporting Assign reporting levels, such as, company code, GST number, and so on to the reporting entities Set periodicity and validity of reporting entities Specify parameters specific to the reporting entity and reporting category
Manage Authentication You can use this app to maintain and authenticate your Goods and Services Tax Network (GSTN) user corresponding to a Goods and Services Taxpayer Identification Number (GSTIN). You also receive a token from the GST Suvidha Provider (GSP), that should be used in all further communications with the GSP.
Manage GST Returns You can use this app to get an optimized overview of your compliance reporting tasks and to keep you ahead of your submission deadlines. The app provides a smooth process for creating and sending compliance reports to the government on time and acts as a constant monitor of submission statuses. This app provides the following features: Easy access to the list of all compliance reports that you are responsible for Notification of due dates Possibility to analyze individual report runs and their results Possibility to generate report documents in the legally required format, to view the documents, or to download them Direct contact to the government, allowing you to verify and submit report documents easily to the government and to receive a direct response
Previous: What's New for Digital Compliance Service for India [page 6]
Next: Digital Compliance Service for India Components [page 14]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Overview

PUBLIC

4 Digital Compliance Service for India Components
The digital compliance service for India solution requires the installation and integration of the following components: SAP Enterprise Resource Planning (ERP) Document Compliance Framework in SAP ERP or in SAP S/4HANA SAP Business Technology Platform (SAP BTP) SAP Cloud Integration SAP Certified GSP Government tax portal GSTN
Previous: Digital Compliance Service for India Overview [page 13] Next: Important SAP Notes [page 15]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Components

5 Important SAP Notes

The following SAP Notes contain the updated information about the installation, as well as enhancements to the installation. Read the following SAP Notes before you start the installation.

Document Compliance

Document Compliance framework notes

SAP Note SAP Note 2134248

Description Document Compliance Framework - Installation Overview

eDocument enablement notes

SAP Note SAP Note 2439151 SAP Note 2439094 SAP Note 2439143

Description eDocument India: Installation Overview eDocument India: Pre-requisite note for 2439143 (GST) eDocument India: GST

After installing the above notes, you can test the eDocument creation for relevant documents in the monitor (txn: edoc_cockpit). However, to be able to send the eDocument to the digital compliance service for India solution, install the following eDocument to digital compliance service for India integration notes.

eDocument to digital compliance service for India integration

SAP Note SAP Note 2518222 SAP Note 2508793 SAP Note 2458714 SAP Note 2443144 SAP Note 2465014

Description eDocument India: Pre-requisite note for 2508793 (GST II) eDocument India: GST (II) eDocument India: Pre-requisites for Note 2443144 eDocument India: GST mapping eDocument India: Implementation of Interface Connector

Additional Notes

SAP Note

Description

Authorization Feature in eDocument Cockpit

SAP Note 2668293

India eDocument Plant Level Authorization - Prerequisite Note for 2672373

SAP Note 2672373

India eDocument Plant Level Authorization in eDocument Cockpit

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Important SAP Notes

PUBLIC

SAP Note SAP Note 2695558 SAP Note 2689219 Additional GSTR2 Notes SAP Note 2688755 SAP Note 2688688 Recommended Notes SAP Note 2621128 SAP Note 2609467 SAP Note 2590525 SAP Note 2631931 SAP Note 2638685 SAP Note 2638134 SAP Note 2714105 SAP Note 2636967
SAP Note 2889709

Description eDocument India: Prerequisite note for 2689219 eDocument India: Plant Authorization
eDocument India: Pre-requisite note for 2688688 eDocument India: GSTR2 validations error messages enhancements
eDocument India: Prerequisite note for 2609467 eDocument India: Issues in the DCS mapping for GSTR1 GST India: Data Readiness Check Cockpit/Report GST INDIA S4HANA: Data Readiness Check Cockpit/Report eDocument India: Prerequisite note for 2638134 eDocument India: eInvoice error log report eDocument India: Tax base amount could not be determined for Rebate document SAP solution for e-Way Bill India - Restricting DCS duplicate eDocument creation for eWayBill (Applicable for SAP eWay Bill Solution customers only) List of GSPs working with SAP for platform "SAP Digital Compliance Service for India" integration certification

Digital Compliance Service for India

SAP Note SAP Note 2460667

Description SAP Localization Hub, digital compliance service for India

Previous: Digital Compliance Service for India Components [page 14] Next: Implementation Sequence [page 17]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Important SAP Notes

6 Implementation Sequence

#unique_9/unique_9_Connect_42_subsection-im1 [page 17] #unique_9/unique_9_Connect_42_subsection-im3 [page 18] #unique_9/unique_9_Connect_42_subsection-im2 [page 17]

Hover over each component for a description. Click the tile for more information.

Implementing eDocument Framework
The eDocument framework is the solution that allows you to manage electronic documents that have legal compliance aspects. To implement the eDocument framework, see the section Important SAP Notes [page 15].
Also, you need to implement the eDocument interface connector to enable the communication between eDocument and DCS India solution. For more information, see the SAP note 2465014

Customizing eDocument
After installing the eDocument framework, you can customize eDocuments using the following customizable views:

View EDOINTXCODEMAPV

Description
eDocument India Tax Code Mapping for GST: To identify the line item as NR, NG and EX, Tax code should be mapped against one of the nil type.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Implementation Sequence

PUBLIC

View EDOINITCRULEMAPV EDOINUQCV J_1ISTATECDM

Description
eDocument India JV Rule Type for GS: This view provides provision to maintain Reason for reversal and Rule type
eDocument India- Unit Quantity Code: This view provides provision to maintain/map internal UQC to GST UQC.
State Code Mapping; e-Filing India Localization: This view provides provision to main tain/map internal state code to GST state code

For more information on the eDocument application, see eDocument Setup for India

Implementing DCS
To implement the DCS India solution, see the SAP note 2460667 . After implementing the SAP Note and installing the software components, the DCS application needs to be integrated with a GSP (GST Suvidha Provider) and the eSign application service provider. For more information, see Integrate Digital Compliance Service with a GSP and Integrate Digital Compliance Service with eSign Application Service Provider.

Previous: Important SAP Notes [page 15] Next: Security Guide for Digital Compliance Service for India [page 19]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Implementation Sequence

7 Security Guide for Digital Compliance Service for India
This security guide provides an overview of the security-relevant information that applies to SAP Localization Hub, digital compliance service for India, which is a service in the Neo environment on SAP BTP. This document is not included as part of the Installation Guides, Configuration Guides, Technical Operation Manuals, or Upgrade Guides. Such guides are only relevant for a certain phase of the software life cycle, whereas this security guides provides information that is relevant for all life cycle phases.
Target Audience
Technology consultants Security consultants System administrators
Why Is Security Necessary?
With the increasing use of distributed systems and the Internet for managing business data, the demands on security are also on the rise. When using a distributed system, you need to be sure that your data and processes support your business needs without allowing unauthorized access to critical information. User errors, negligence, or attempted manipulation of your system should not result in loss of information or processing time. These demands on security apply likewise to the SAP Localization Hub, digital compliance service for India.
Previous: Implementation Sequence [page 17]
Next: Digital Compliance Service for India Implementation [page 29]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

PUBLIC

7.1 Prerequisites

Fundamental Security Guides
The SAP Localization Hub, Digital Compliance Services for India is built on SAP BTP and SAP NetWeaver ABAP. Therefore, the following Security Guides also apply to SAP Localization Hub, Digital Compliance Services for India: SAP NetWeaver Security Guide SAP BTP Security Guide SAP Cloud Integration Security Guide S/4 HANA Security Guide SAP ERP Central Component Security Guide

Important SAP Notes

The important SAP Notes that apply to the security of SAP Localization Hub, Digital Compliance Services for India are shown in the table below.

Title
Setting up SSL on Application Server ABAP

SAP Note SAP Note 510007

Comment
Relevant sections in the note are: 1+2 -> installing and enabling the library in SAP NetWeaver to set up SSL 4+5 -> creating SSL client PSEs for SAP Web AS through transaction STRUST 7 -> how to enable TLSv1.2

For a complete list of the available SAP Security Guides, see SAP Service Marketplacehttps:// websmp202.sap-ag.de/~sapidb/012002523100000000111997E.

Configuration
You can find a summary of the configuration steps for implementing security for the SAP Localization Hub, Digital Compliance Services for India in the Installation and Configuration Guide attached to the master note 2460667 .

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

Additional Information

For more information about specific topics, see the links in the table below.

Content Security Security Guides Related SAP Notes
Released platforms Network security SAP Solution Manager SAP NetWeaver

Quick Link on SAP Service Marketplace or SCN http://scn.sap.com/community/security http://service.sap.com/securityguide http://service.sap.com/notes http://service.sap.com/securitynotes http://service.sap.com/pam http://service.sap.com/securityguide http://service.sap.com/solutionmanager http://scn.sap.com/community/netweaver

7.2 Technical System Landscape
The figure below shows an overview of the technical system landscape for the SAP Localization Hub, Digital Compliance Services for India.

SAP Localization Hub, Digital Compliance Services for India is a consumer managed JAVA application built on SAP BTP, Neo environment that allows you to transmit outward and inward supplies electronic data from backend system to GSTN system.
The GST relevant data is pushed in the form of eDocuments from backend system (SAP ECC or SAP S/4HANA) to the ASP application in SAP BTP. The ASP application makes use of SAP HANA's in memory capabilities to

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

PUBLIC

then consolidate and prepare GSTR data in the format as mandated by GSTN and sent to GSTN through SAP Cloud Integration via approved GST service Provider (GSP). The ASP application exposes its services in the form of REST APIs protected with OAuth 2.0 so that any backend system can be integrated to it irrespective of SAP ECC or SAP S/4 HANA.
7.3 Security Aspects of Data, Data Flow and Processes
The figure below shows an overview of the data flow for the SAP Localization Hub, Digital Compliance Services for India.

Since SAP Localization Hub, Digital Compliance Services for India is provided as Platform as a Service offering, all SAP BTP resources are dedicated to single customer and hence multi-tenant concept doesn't apply.
The table below lists the security measures to be considered for each of the process step:

Step 1 2
3

Description User triggers invoice submission Through API the eDocument is pushed to the ASP
ASP validates the API format and sends re sponse status back to ECC

Security Measure
NA
Plant level authorization for eDocuments is supported in addition to authorization at Company and eDocu ment Process & Process Steps.
The Rest API is protected with OAuth2.0
The asynchronous request is returned with acknowl edgement number which the source system would use further to get the latest status. No asynchronous call back from cloud ASP application to backend is allowed.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

Step 4
5
6 7 8

Description

Security Measure

On Successful validation, ASP stores the invoice Virus Scanning is in place before storing any file/

data & unstructured data in HANA and Docu ment Service

request data in SAP BTP Document Service.

JSON format validation and data validation done before

storing the data in SAP HANA database

Business user reviews and selects the reporting entity for which the users wants to submit re turns

SAP ID service is used as the trusted identity provider to ensure proper authentication.
SAP BTP role-based authorization is provided.

In addition, activity-based authorization for each GSTR form and Reporting entity/ business place is supported.

ASP pulls the data from HANA and prepares JSON compliant with GSTN

Base-64 encoded data is transferred from ASP applica tion to Cloud Integration.

JSON is encrypted as per GSTN security stand JSON is encrypted based on GSTN API requirements ards and pushed to GSP

GSP sends the data to GSTN for tax filing

7.4 User Administration and Authentication
SAP Localization Hub, Digital Compliance Services for India uses the user management and authentication mechanisms provided with the SAP BTP and SAP NetWeaver Application Server. Therefore, the security recommendations and guidelines for user administration and authentication as described in the Security section of SAP BTP Help Document and SAP NetWeaver Security Guide also apply to the SAP Localization Hub, Digital Compliance Services for India.
In SAP BTP, SAP ID service is used as the default trusted identity provider to ensure proper authentication of user. With SAP Localization Hub, Digital Compliance Services for India, one SAP BTP Administrator user (Suser) would be provisioned in the customer tenant. It is the responsibility of this customer specific platform Administrator (S-user) user to create other users who would access the application or perform SAP BTP specific activities. Only an administrator can create or delete other users.
Multi-factor authentication is not supported by default SAP ID service. It is recommended to configure identity federation with existing external identity provider or SAP Identity Authentication Service (IAS) to enable multifactor authentication. Multi-factor Authentication can be enabled based on user groups (mapped to application specific role such as Administrator) or other criteria as defined in the security policy of your organization.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

PUBLIC

7.5 Authorizations

Authorization in SAP NetWeaver ABAP
SAP Localization Hub, Digital Compliance Services for India supports eDocument authorization based on Company Code eDocument Process and Process Steps Plant within business place

Authorization in SAP BTP

The SAP Localization Hub, Digital Compliance Services for India uses role-based authorization supported by SAP BTP.
Predefined Authorization Groups are delivered as part of the application SAP Localization Hub, Digital Compliance Services for India to ease role assignment.
Refer the below table for Role to Authorization Group mapping.

Role dcs.admin

Authorization Group Administrator

dcs.taxAccountant Tax Accountant

dcs.sourceAdmin

Source Administrator

Description
Users assigned to this group can perform configuration re lated activities in the system such as business place / reporting entity creation and user assignment to each GSTR form activity. They can manage GSP communication, per form health check and GSTN authentication.
Users assigned to this group can perform SAVE activity for all GST Returns
Users assigned to this group can upload and manage Out ward and Inward Invoices

In addition to predefined roles support, SAP Localization Hub, Digital Compliance Services for India supports fine grained access control based on:
Reporting entity or Business place GSTR Form specific activity such as Save, Summary Save, Submit, File Invoice level authorization based on authorization object passed from backend source system
In backed ABAP source system, plant level authorization restriction for India e-Invoices is supported in addition to standard eDocument authorizations based on Company Code and eDocument Process & Process steps.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

7.6 Network and Communication Security
This section describes the network security and communication channels that the SAP Localization Hub, Digital Compliance Services for India uses.
There are two major network interfaces in the SAP Localization Hub, Digital Compliance Services for India:
Backend Source System to ASP application hosted in SAP BTP in Cloud SAP Cloud Integration within SAP BTP to GST Suvidha Provider (GSP)
SAP Localization Hub, Digital Compliance Services for India supports only asynchronous communication where the source system sends the data to the target and receives just an acknowledgement id unique for each transaction without waiting for the target system to complete processing of data. It is the responsibility of the source system to request for status update from the target system as and when required based on the acknowledgement id received previously and update the information back. No callback from target system to source system is supported.
This means ASP application hosted in SAP BTP doesn't initiate any update back to the backend source system and hence there is no need to open any inbound traffic in the On-Premise network. Similarly, GSP system can't initiate any update back to ASP application hosted in SAP BTP. Further, ASP application communicates with external network (GSP) through SAP Cloud Integration. Certificate based authentication is supported from ASP application to SAP Cloud Integration.

Communication Channel Security

The table below shows the communication channels used by the SAP Localization Hub, Digital Compliance Services for India, the protocol used for the connection, and the type of data transferred.

Communication Path

Protocol Used

Backend Source System to application in SAP BTP

HTTPS

Application in SAP BTP to SAP Cloud Integration HTTPS

SAP Cloud Integration to GST Suvidha Provider (GSP)

HTTPS

GST Suvidha Provider (GSP) to GSTN

HTTPS

Type of Data Transferred JSON
JSON JSON
JSON

HTTP connections are protected using the Secure Sockets Layer (SSL) protocol throughout all communication paths starting from backend source system to GSTN.

7.7 Data Storage Security
SAP Localization Hub, Digital Compliance Services for India stores data in:
SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

PUBLIC

Customer ABAP system as eDocuments SAP BTP Document Service SAP HANA Database
Data stored in ABAP system is protected by standard SAP NetWeaver functions. Data stored in SAP BTP Document service is encrypted during transport (HTTPS) and at rest with industry standard AES encryption. The data stored in SAP HANA is encrypted at rest. Data encryption in SAP HANA Neo is automatic with the process and keys managed by SAP. Access to data in the SAP HANA database is limited to only database users created by customer with the appropriate role and permission. For more details, refer the section SAP HANA User Management in the SAP HANA Security Guide.
Data Protection
SAP Localization Hub, Digital Compliance Services for India doesn't store any personal information about users other than the user id created specifically to access the application. This user id is a standalone attribute and doesn't have any corelation with any of the user details in other SAP or non-SAP applications.
As part of SAP Localization Hub, Digital Compliance Services for India, SAP BTP tenant specific to an individual customer is provisioned and platform administrator user (S-User) is shared with the customer. It is this S-user who creates further users who can access the application. Only the user with platform administrator role can create/delete applicationspecific business users.
User management and role authorization within the application can be performed only by the user with applicationspecific role Administrator. Only the application specific administrator can view another user's id. Also, once a user id is created, it isn't possible to edit the user id in the application.
User id in the application is stored only for standard logging. SAP Localization Hub, Digital Compliance Services for India uses standard logging features of SAP BTP. The logs in SAP BTP are deleted as per the details furnished in section 'Deletion of data' in the SAP BTP Security document .

7.8 Security-Relevant Logging and Tracing
SAP Localization Hub, Digital Compliance Services for India uses the security relevant logging and tracing supported by SAP NetWeaver Application Server and SAP BTP.

7.9 Services for Security Lifecycle Management

The following services are available from Active Global Support to assist you in maintaining security in your SAP systems on an ongoing basis.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

Security Chapter in the EarlyWatch Alert (EWA) Report
This service regularly monitors the Security chapter in the EarlyWatch Alert report of your system. It tells you:
Whether SAP Security Notes have been identified as missing on your system. In this case, analyze and implement the identified SAP Notes if possible. If you cannot implement the SAP Notes, the report should be able to help you decide on how to handle the individual cases.
Whether an accumulation of critical basis authorizations has been identified. In this case, verify whether the accumulation of critical basis authorizations is okay for your system. If not, correct the situation. If you consider the situation okay, you should still check for any significant changes compared to former EWA reports.
Whether standard users with default passwords have been identified on your system. In this case, change the corresponding passwords to non-default values.

Security Optimization Service (SOS)
The Security Optimization Service can be used for a more thorough security analysis of your system, including: Critical authorizations in detail Security-relevant configuration parameters Critical users Missing security patches This service is available as a self-service within SAP Solution Manager, as a remote service, or as an on-site service. We recommend you use it regularly (for example, once a year) and in particular after significant system changes or in preparation for a system audit.

Security Configuration Validation
The Security Configuration Validation can be used to continuously monitor a system landscape for compliance with predefined settings, for example, from your companyspecific SAP Security Policy. This primarily covers configuration parameters, but it also covers critical security properties like the existence of a non-trivial Gateway configuration or making sure standard users do not have default passwords.

Security in the RunSAP Methodology / Secure Operations Standard
With the E2E Solution Operations Standard Security service, a best practice recommendation is available on how to operate SAP systems and landscapes in a secure manner. It guides you through the most important security operation areas and links to detailed security information from SAP's knowledge base wherever appropriate.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

PUBLIC

More Information
For more information about these services, see: EarlyWatch Alert: http://service.sap.com/ewa Security Optimization Service/ Security Notes Report: http://service.sap.com/sos Comprehensive list of Security Notes: http://service.sap.com/securitynotes Configuration Validation: http://service.sap.com/changecontrol RunSAP Roadmap, including the Security and the Secure Operations Standard: http://
service.sap.com/runsap (See the RunSAP chapters 2.6.3, 3.6.3 and 5.6.3)

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Security Guide for Digital Compliance Service for India

8 Digital Compliance Service for India Implementation

eDocument Implementation [page 29] You use this solution to create eDocuments, that is, to transform documents created in various SAP applications into predefined exchange formats and transfer them electronically to external systems, such as to the systems of legal or tax authorities.
Setup Digital Compliance Service for India [page 44] SAP Localization Hub, digital compliance service for India, from now on referred to as digital compliance service for India, enables customers 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).
Previous: Security Guide for Digital Compliance Service for India [page 19]
Next: Digital Compliance Service for India Integration [page 46]

8.1 eDocument Implementation
You use this solution to create eDocuments, that is, to transform documents created in various SAP applications into predefined exchange formats and transfer them electronically to external systems, such as to the systems of legal or tax authorities.
For India, you can use the eDocument Basic solution to create electronic for documents created in source applications, such as Sales and Distribution (SD) or Financial Accounting (FI). The system makes eDocument data available for further processing by your own custom solution for creating the JSON and submitting it to the Indian tax authority. For more information, see here [page 30].

Prerequisites
For the creation of eDocuments in India, ensure that you have done the following: You made the settings as described in Customizing for eDocument - India [page 32] You made the settings as described in Implementation Considerations for eDocument - India [page 33]

Features
Reporting Goods and Services Tax
SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

It is a legal requirement in India that GST invoices are registered in the tax authorities' systems. You use the eDocument basic solution to create eDocuments for GST invoices transaction create in source applications. The eDocument data is made available for your custom solution that is responsible for creating and signing the JSON file and communicating with the tax authorities' system to request authorization for the transaction. For more information, see Reporting Goods and Services Tax [page 31]
Parent topic: Digital Compliance Service for India Implementation [page 29]

Related Information
Setup Digital Compliance Service for India [page 44]

8.1.1 eDocument Basic Enablement
The eDocument Basic Enablement allows you to extract the data of source documents previously created in other SAP applications, such as Financial Accounting (FI) or Sales and Distribution (SD), and make it available in the database as an eDocument instance for further processing. Using this solution, you can do the following: Map the data to the legally required JSON format Submit the JSON to the SAP Localization Hub, digital compliance service for India solution

Prerequisites
You have made the following settings: You have implemented the SAP Note 2439151 . You have made the Customizing settings required for the country you are implementing. For more
information, see the countryspecific Customizing.

Process
The processing of the eDocument when using the eDocument Basic Enablement is depicted in the following figure:
1. You create the source document using an SAP application, such as in FI or in SD. Once you save the source document, the system creates an instance of the eDocument in the database.
2. You submit the eDocument by running the eDocument Cockpit (EDOC_COCKPIT transaction). For more information, see the application help documentation directly in the report.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

3. The system retrieves the eDocument from the database and calls the interface connector to deploy the eDocument Interface Connector (EDOC_INTERFACE_CONNECTOR) Business Add-In (BAdI). This BAdI contains the implementation that connects to the SAP Localization Hub, digital compliance service for India solution.
4. Your solution retrieves the eDocument from the BAdI interface, converts it into the required JSON format, and establishes communication with the SAP Localization Hub, digital compliance service for India solution to send the JSON files.

eDocument Basic Solution
The Basic Enablement contains additional functions and it is called eDocument Basic Solution. The following is available: You can save the submitted JSON file in the eDocuments database. You can update the eDocument status implementing BAdIs to connect to your customerspecific
development. For more information, see SAP Note 2002415 .
8.1.2 Reporting Goods and Services Tax
Under the Goods and Services Tax (GST) regime, tax is levied on every supply of goods and services.

Prerequisites
You have done the customizing settings for the cash invoice registration scenario as described in here [page 32].

Context
The Centre levies and collects Central Goods and Services Tax (CGST), while the states levy and collect State Goods and Services Tax (SGST) on all transactions within a state. Every registered taxable person must file returns (monthly and yearly) with the Indian tax authorities. You use the eDocument basic solution to assemble the data of the GST invoices in form of eDocuments. You use your custom solution to transform the eDocuments in JSON files and transmit them to the tax authorities for reporting purpose.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

The process of creating an eDocument for reporting GST for India is as follows:

Procedure
1. You create GST invoices in source applications. 2. The system does the following:
Checks the settings you have done in customizing for the country-version, picks the GST invoice issued and adds them to the eDocument.
Calls the eDocument Interface connector (EDOC_INTERFACE_CONNECTOR) BAdI that triggers the SAP Localization Hub, digital compliance service for India solution.
3. Depending on the processing status from the f solution, you receive a response (for example, in the form of an acknowledgement ID).
4. After the SAP Localization Hub, digital compliance service for India solution processes the document, you will receive the following statuses: Transaction ID received (TIDR). The GST eDocument registration is successful. Rejected by DCS application (REJECTED). You can cancel the GST eDocument or correct and resubmit it in the Create and Submit eDocument (EDOC_COCKPIT) report. For more information, see here [page 39] Filed to GSTN. The eDocument has been filed in the tax authorities' system. This is the final status.
8.1.3 Customizing for eDocument - India
Regardless of which eDocument solution variant you are implementing in your system, you make the following settings:

Business Transaction Events (BTE)
You activate the BTE for the EDOC SAP application using the FIBF transaction in the SAP Menu.

Customizing
You make the following settings in Customizing for eDocuments under Cross-Application Components General Application Functions eDocument : 1. For a company code, you activate the types of source documents for which you want eDocuments to be
created in Activate Source Type Documents for Company Code (EDOCOMPANYACTIV). 2. You select the interface type that calls the eDocument solution variant that you want to use for the
generation of eDocuments in the Define Interface Type for eDocument (EDOINTTYPEV).

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

3. You assign eDocument types to the relevant source document types in the following Customizing activities: Assign eDocument Type to Accounting Document Type (T003EDOCV) Assign eDocument Type to Billing Document Type (TVFKEDOCV)
Business and Add-Ins (BAdIs) The Business Add-Ins (BAdIs) relevant for all eDocument solution variants are contained in the ES_EDOCUMENT enhancement spot.
You implement the following BAdIs in Customizing for eDocuments under Cross-Application Components General Application Functions eDocument General Settings Business Add-Ins : Enhancements for eDocument BAdI (EDOC_ADAPTOR): You use this BAdI to define customerspecific
rules for the generation of eDocuments. Define Interface Connector for eDocument BAdI (EDOC_INTERFACE_CONNECTOR): You use this BAdI to
define the communication process you want to use for transferring eDocuments over to the SAP Localization Hub, digital compliance service solution. The implementation of this BAdI varies depending on which eDocument solution variant you are using. For more information, refer SAP Note 2465014 .
Country-Specific Settings
For the Reporting Goods and Services Tax scenario, you make the following settings in Customizing for eDocuments under Cross-Application Components General Application Functions eDocument Country-Specific Settings India : Map tax codes to fields specific to GST reporting in Map Tax Codes to GSTRSpecific Fields
(EDOINTXCODEMAPV). Maintain this via SM30 transaction. Assign unit quantity codes to standard SAP unit of measurement in Map Unit Quantity Codes to SAP
specific Unit of Measurement (EDOINUQCV). Maintain this via SM30 transaction. Map eDocument details to the relevant sections (such as B2B, B2C) in the GSTR-1 return. Implement the
DETERMINE_SD_PROCESS_GSTR1 and DETERMINE_FI_PROCESS_GSTR1 methods of the BAdI: Map eDocument Details to GSTR-1 Sections (EDOC_IN_MAP). Maintain this via SE19 transaction.
8.1.4 Implementation Considerations for eDocument - India

Enabling eDocument Status Processing
You can enhance your Basic solution by implementing BAdIs that enable user actions and status maintenance in the eDocument Cockpit report (EDOC_COCKPIT transaction).
By implementing the TRIGGER method of the EDOC_INTERFACE_CONNECTOR BAdI defined in the ES_EDOCUMENT enhancement spot, you can enable actions in the report that allows you to perform the following processing steps.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

Processing step you want to trigger Send the eDocument to the interface

Action you perform in the eDocument Cockpit Submit

8.1.4.1 Authorization Objects

The system checks the users' authorizations before they can perform certain actions.
The following authorization objects are needed in the AAAB authorization class for performing actions it the programs listed below:

Object Name EDO_BUK
EDO_PROC

Description

Authorization Fields

eDocument: Authorization for Company code

BUKRS

eDocument: Authorization for Process & Process Step

EDO_PROC EDO_PRSTEP

Relevant for Programs
eDocument Cockpit (EDOC_COCKPIT)
Create and Submit eDocument (EDOC_RE SUBMIT_EDOCUMENT)
eDocument Cockpit (EDOC_COCKPIT)
Create and Submit eDocument (EDOC_RE SUBMIT_EDOCUMENT)

SAP does not deliver any value in the AuthObject field in the JSON request. If a customerspecific field (such as business place or plan) is to be mapped to the JSON request, make the mapping in the EDOC_ADAPTOR Business Add-In.

8.1.5 Business Transactions
You use the eDocument Cockpit report to display eDocuments as well as to perform most activities on eDocuments. To find the Cockpit, on the SAP Easy Access screen, choose Cross-Application Functions eDocument eDocument Cockpit or call the EDOC_COCKPIT transaction.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

8.1.5.1 eDocument Status and Actions
During its processing, the eDocument statuses change many times. Some statuses require that you take actions, while others are only technical and temporary.

Related Information
Statuses for Individual Invoice Processing [page 35] Statuses for eDocument Summary Processing [page 38]

8.1.5.1.1 Statuses for Individual Invoice Processing

The table below summarizes the existing statuses and the required actions for an individual invoice.

Status CREA
SNRQ

Description eDocument created
Sending requested

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

Status SENT
TIDR REJECTED
UPLOAD_DCS

PUBLIC

Description Sent to DCS application
Transaction ID received Rejected by DCS application
Uploaded to DCS application

Action
This is the status after you have re quested the submitting of the eDocu ment. The eDocument has been sent to tax authorities but the response from the tax authorities could not be suc cessfully processed in the system. You can do the following:
Cancel the eDocument. You can ei ther manually cancel the source document in the source applica tion or create a new eDocument for it later. See Cancelling an eDocu ment.
This is a technical status that informs you that the tax authority has provided the transaction ID (such as an acknowl edgement ID) to the transaction and the registration is therefore successful. This ID is then forwarded back to the custom solution.
The eDocument has been rejected by the tax authorities. You can do the fol lowing:
Cancel the eDocument. You can ei ther manually cancel the source document in the source applica tion or create a new eDocument for it later. See Cancelling an eDocu ment.
You can resubmit the eDocument.
The eDocument has been uploaded to the DCS application. You can do the fol lowing:
check the eDocument modify the eDocument cancel the eDocument
You can either manually cancel the source document in the source ap plication or create a new eDocu ment for it later.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

Status FAILED SAVED FILED CANCEL_REQ CANCELLED
ADD_TO_SUM

Description Save failed Saved to GSTN Filed to GSTN Cancellation Requested Cancelled
Added to eDocument summary

Action
The eDocument has not been saved in the DCS application. You can do the fol lowing: resubmit the eDocument cancel the eDocument
The eDocument has been saved in tax authorities' system. You can now do the following: Get eDocument status Modify eDocument Cancel eDocument
The eDocument has been filed in the tax authorities' system. You can do the following: Modify eDocument Cancel eDocument
This is the final step. No user actions on eDocuments are possible.
This is the status after you have trig gered the eDocument cancellation re quest to the DCS application.
The eDocument is cancelled and no user actions can be performed any more.
If you want to create a new eDocument for the same invoice, first delete the cancelled eDocument and then create a new one.
Note
The source document is not auto matically cancelled. To keep the consistency in your system, cancel the source document manually in its source application.
The eDocument has been included in eDocument summary.
No further actions are possible.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

8.1.5.1.2 Statuses for eDocument Summary Processing

The table below summarizes the existing statuses and the required actions for eDocument.

Status CREATED
SNRQ SENT
TIDR

Description eDocument Summary created
Sending requested Sent to DCS application
Transaction ID received

Action
This is the initial status of an eDocu ment once it has been created in the system. The following actions are possi ble:
Cancel the eDocument. You can ei ther manually cancel the source document in the source applica tion or create a new eDocument for it later. See Cancelling an eDocu ment.
If there is an error and the eDocu ment was not automatically sent to the tax authorities, you can submit it manually in the Cockpit.
This is the status that informs you that the eDocument Summary has not reached the interface yet.
You can resubmit the eDocument.
This is the status after you have re quested the submitting of the eDocu ment. The eDocument has been sent to tax authorities but the response from the tax authorities could not be suc cessfully processed in the system. You can do the following:
Cancel the eDocument. You can ei ther manually cancel the source document in the source applica tion or create a new eDocument for it later.
This is a technical status that informs you that the tax authority has provided the transaction ID (such as an acknowl edgement ID) to the transaction and the registration is therefore successful. This ID is then forwarded back to the custom solution.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

Status REJECTED
UPLOAD_DCS PART_UPLDD FAILED CANCELLED

Description Rejected by DCS application
Uploaded to DCS application Partly uploaded to DCS application Failed to upload to DCS eDocument Summary cancelled

Action
The eDocument has been rejected by the tax authorities. You can do the fol lowing:
Cancel the eDocument. You can ei ther manually cancel the source document in the source applica tion or create a new eDocument for it later.
You can resubmit the eDocument.
The eDocument has been uploaded to the DCS application
This is the final status of eDocument Summary.
Only a portion of the eDocuments are uploaded to the DCS application.
This is the final status of eDocument Summary
eDocument Summary not saved in the DCS application.
The eDocument summary is cancelled. The individual statuses of the invoices are reset to CREA. You can create a new eDocument Summary.

8.1.5.2 Creating and Submitting an eDocument
You can set up your system to create eDocuments automatically when the corresponding source documents have been created in the source application.
Context
If, for any reason, the eDocument was not created automatically, you can still create it manually in the eDocument Cockpit report (EDOC_COCKPIT transaction).

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

Procedure
1. Run the eDocument Cockpit report to display eDocuments according to your selection. To access the Cockpit, on the SAP Easy Access screen, choose Cross-Application Functions General Application Functions eDocument eDocument Cockpit or call the EDOC_COCKPIT transaction. The Status column shows you at a glance if the eDocument is on a process status that require you to perform any activity.
Note
To better meet your business needs, for each eDocument type, you can define in Customizing which process status is assigned to which eDocument status. Refer to the documentation of Activate Source Type Documents for Company Code in Customizing for eDocument under Cross-Application Functions General Application Functions eDocument General Settings . 2. Select the document and choose Submit.
8.1.5.3 Cancelling an eDocument
You use the eDocument Cockpit (EDOC_COCKPIT transaction) to cancel eDocuments. For each country, there are specific requirements regarding the type of documents that can be cancelled as well as in which situations they can be cancelled. In some countries, you can cancel documents that have been already approved by the tax authorities by voiding them. In other countries, you can cancel rejected documents that contained errors.
More Information
Refer to the application help documentation directly in the report for countryspecific information to find more information regarding the cancellation of eDocuments for the country you are interested in.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

8.1.5.4 Deleting an eDocument
You use the eDocument Cockpit report to delete eDocuments that have not yet been submitted to the tax authorities.

Context
The source document is not deleted in this action. You can create a new eDocument for this source document later. If you want to cancel the source document too, you must do it in the source application where you have created it.

Procedure
1. Run the eDocument Cockpit report.
To access the report, on the SAP Easy Access screen, choose Cross-Application Functions eDocument eDocument Cockpit or call the EDOC_COCKPIT transaction.
2. In the eDocument Cockpit, select one or more eDocuments that have not been submitted to the tax authorities yet and click More Delete eDocument .
3. Confirm the deletion.

Results
The system deletes only the eDocument record from the database.

8.1.5.5 Displaying eDocument Status History
After creation in the system, the eDocument status changes many times during its processing, depending on which process step it goes through, until it reaches its final status in the system.
In the eDocument Cockpit report (EDOC_COCKPIT transaction), you can select one or more files and click Goto... History to display a list of all the statuses that an eDocument had in the past, including the last
status. The Sequence No. field shows the order in which the status has changed.
Depending on which status the eDocument is currently in, a related file may exist. This file can be the original JSON that was sent out from the system to the tax authorities' systems, or it can be the JSON file you received back from the tax authority as an acknowledgment. It can also have other formats and purposes, depending on the scenario you have implemented in your system. If the related files have the File GUID field filled, you can select and download them to your file system by choosing Export File.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

8.1.5.6 Create eDocument Summary
You use this report create a summary of eDocuments created for one company code. In India, you create a summary of all Goods and Services Tax (GST) invoices and submit them all at once to the SAP Localization Hub, digital compliance service for India solution. The system creates the summary as an eDocument. Once the summary eDocument is created, you submit it to the tax authorities using the Create and Submit eDocument / eDocument Cockpit (EDOC_COCKPIT) report.
Selection
In the selection screen of this report you can do the following: Select the eDocuments you want to include in the summary. You can either select all created documents
for a given date, or you can select the eDocuments by its GUID, status or source type. If you check the Automatically create Summary for selected eDocuments checkbox, all valid documents created in the specified date are inserted to the summary. Display the eDocuments that have been already included in a summary. You can search for the summary creation date, summary eDocument type, or summary eDocument GUID. You can select the layout with the list format to display the data in the output screen.
Output
The report displays the collected eDocuments in accordance with your selection screen settings. The ALV list displays the result in lines using different shadings with different meanings: Blue shading: eDocument has been already included in a summary Yellow shading: eDocument has not been included in a summary yet Green shading: eDocument has been included in the summary that you created in this report session Red shading: eDocument has errors and has not been included in a summary yet
Activities
To create a new summary, in the output screen, select the eDocuments that you want to include in a summary and click on Create Summary. The system creates an eDocument summary with a corresponding ID. This ID is displayed in the Summary ID column of each of the eDocuments belonging to this summary. By double-clicking on this cell, you are directed to the respective eDocument summary (source type EDOC_LIST) in the Create and Submit eDocument report.
Note
You can create multiple summaries for eDocuments created in the same day. The system assigns each summary an ID.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

Subsequent activities in the Create and Submit eDocument Report Once you have created the summary, you can submit it to the tax authorities for approval. In the Create and Submit eDocument report, select the eDocument summary and click on Submit. To check the current status of the approval request, click the Tax Authority button in this report. By doubleclicking the eDocument Status Overview, you see the status that the eDocument has already been through.
8.1.5.7 Downloading an eDocument
Once you have created your eDocuments, you can download the JSON files to your file system using the eDocument Cockpit report (EDOC_COCKPIT transaction). To do so, select the relevant process in the Cockpit and select the documents you want to download to your file system. Choose Export File. The files are exported in JSON format from the SAP system to your file system.
Note
If you are using the eDocument Basic solution, your eDocuments will not be mapped to the JSON format required by the tax authorities of a given country. You still need to map the fields to the legally-required JSON.

More Information
For more information, see the Application Help documentation directly in the report.
8.1.6 eDocument Individual Invoice Processing
Suppliers of goods or services to public companies are required by law to issue invoices, credit or debit memos, or other financial documents electronically. You use eDocument Basic Solution to assemble the data of the invoices in form of eDocuments. You integrate your custom solution to transform the eDocuments in JSON files and transmit them to the GSTN.

Prerequisites
You have done the customizing settings for the reporting goods and services tax scenario as described here [page 32].

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

Process
The process to create an eDocument using the normal processing for India as follows:
Submit eDocuments to Tax Authorities 1. You create documents in source applications. 2. The system automatically creates an eDocument for the respective source document in the Create and
Submit eDocument report (EDOC_COCKPIT). 3. You submit the eDocument to the SAP Localization Hub, digital compliance service for India solution by
clicking Submit in the Create and Submit eDocument report (EDOC_COCKPIT). 4. The system calls the eDocument Interface connector (EDOC_INTERFACE_CONNECTOR) BAdI that
triggers the solution required for the assembling of the JSON in the predefined format.
Update Status in eDocument Cockpit 1. You request the update the status of the eDocument by clicking the Status button. 2. The system updates the latest status after retrieving from the SAP Localization Hub, digital compliance
service for India solution, and displays the status in the Create and Submit eDocument report.
More Information
For more information about eDocument status and the permitted actions you can do in the system, see here [page 35].

8.2 Setup Digital Compliance Service for India
SAP Localization Hub, digital compliance service for India, from now on referred to as digital compliance service for India, enables customers 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 digital compliance service for India to send invoice details to the GSTN. Digital Compliance Service for India has the following features: Authenticates with GSTN Processes and uploads invoices from multiple source systems Uploads invoices containing outward supply data (GSTR1) An intuitive user interface for managing all GST returns For installing and configuring all the components of the solution on the SAP Cloud Integration, refer SAP note 2460667 and follow the Installation and Configuration Guide attached for detailed information.
Parent topic: Digital Compliance Service for India Implementation [page 29]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

Related Information
eDocument Implementation [page 29]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Implementation

PUBLIC

9 Digital Compliance Service for India Integration

Integrate Digital Compliance Service for India with a GSP [page 46] The communication part of the SAP Localization Hub, digital compliance service for India solution for integration with the GST Suvidha Provider (GSP) is taken care of by the SAP Cloud Integration Service.
Integrate Digital Compliance Service for India with eSign Application Service Provider [page 47] You integrate SAP Localization Hub, digital compliance service for India with the eSign application service provider (eSign ASP) to digitally sign filing document content before filing returns.
Previous: Digital Compliance Service for India Implementation [page 29]
Next: Applications [page 67]

9.1 Integrate Digital Compliance Service for India with a GSP

The communication part of the SAP Localization Hub, digital compliance service for India solution for integration with the GST Suvidha Provider (GSP) is taken care of by the SAP Cloud Integration Service.
SAP is partnered with several certified and non certified GSPs. The following table lists the reference links to be followed for detailed information on deploying SAP integration flow to establish communication between digital compliance service and GSPs.

GSP Partners SAP Certified NonCertified

Integration Reference
SAP Note 2889709 Integration from Digital Compliance Service to GST Suvidha Provider and eSign Application Service Provider

Parent topic: Digital Compliance Service for India Integration [page 46]

Related Information
Integrate Digital Compliance Service for India with eSign Application Service Provider [page 47]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

9.2 Integrate Digital Compliance Service for India with eSign Application Service Provider
You integrate SAP Localization Hub, digital compliance service for India with the eSign application service provider (eSign ASP) to digitally sign filing document content before filing returns.
The SAP Cloud Integration Service integrates the SAP Localization Hub, digital compliance service for India with the eSign application service provider (eSign ASP). This document provides steps to establish communication between these two applications
Note
This documentation and configuration would be required only if you want to digitally sign the document content via the online process as mentioned in <>. Alternately, you can use the offline process using Digital Signature Certificate(DSC) USB device to digitally sign the filing content.
Note
eSign Service Provider (ESP), also known as certificate authority or Certifying Authorities (CA), is an entity that issues digital signature certificates for electronic authentication of users.
eSign Application Service Provider (eSign ASP) is an entity that signs the contract with the ESP to provide electronic signature Service. eSign ASP uses eSign service as part of their application to digitally sign the content. eSign ASP provides the interface software platform for users to sign documents using Aadhaar + OTP or using Digital Signature Certificate (DSC) USB device.
The below diagram provides an overview of the integration between SAP Localization Hub, digital compliance service for India and eSign ASP.

Prerequisites
Before you start with the activities, ensure that the following prerequisites are met:
Installed the SAP Localization Hub, digital compliance service for India solution in your SAP BTP, Neo test and/or productive landscape. For detailed information, refer SAP note 2460667 .
Obtained the digital compliance service for India USB device. Have a registered PAN, as recommended by the GSTN, at the time of filing digitally signed content. Provisioned live SAP Cloud Integration Service test and/or productive tenants. Chosen eSign ASP or eSign gateway service providers and completed the registration process. You have received the following information or documents after on boarding with eSign ASP:
eSign ASP integration or setup manual guide JavaScript SDK

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Certificate required for establishing SSL handshake with eSign ASP.
Note
After you complete integration with the eSign ASP mentioned in this guide, you should develop and configure digital compliance service for India eSign ASP SAPUI5 application which acts as interface between the digital compliance service for India application screen and the eSign ASP/ Web service screen, by exchanging data between the screens or the application. For more details, see <>.
Parent topic: Digital Compliance Service for India Integration [page 46]

Related Information
Integrate Digital Compliance Service for India with a GSP [page 46]

9.2.1 eSign ASP Integration content

The content catalog package Integration between Digital Compliance Service to GST Suvidha Provider and eSign Application Service Provider contains the following integration flows:

Integration Flow Name in WebUI GSP Integration Template eSign ASP Integration Template

Project Names/Artifact Names com.sap.slh.dcs.gsp.template com.sap.slh.dcs.esp.template

eSign ASP integration flow is a generic integration template and should be modified or enhanced for integration with eSign ASP. This template contains process calls to set up communication with the DCS application. The process call for communication with eSign ASP must be added based on the details received after registering with eSign ASP.

Procedure
To find the integration flow in the content catalog, perform the following steps:
1. In your browser, go to the WebUI of the SAP Cloud Integration tenant using the url: <SAP Cloud Integration Tenant URL>/itspaces.
2. To logon, enter your P user or S user. If you get the HTTP Status 403 error, contact your tenant administrator.
3. After successful login, from the menu in the upper left corner, choose Discover. 4. In the subsequent screen, search for Integration between Digital Compliance Service to GST Suvidha
Provider and eSign Application Service Provider, and select the package.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

9.2.1.1 RESTful API for eSign Integration
The SAP Localization Hub, digital compliance service for India exposes two RESTful APIs to setup eSign Integration with an external application.
The two RESTful APIs are the following: dcsdownload
Provides plan or unsigned filing document content in base64 encoded format. dcsupload
Accepts signed filing document content along with type of signature and signatory ID.
Note
eSign ASP integration flow template has built-in communication setup for digital compliance service RESTful API and digital compliance service oAuth service. You should configure digital compliance service application URL and oAuth token endpoint URL while deploying the Integration flow.

9.2.1.1.1 RESTful API: dcsdownload

This RESTful API accepts query parameters to select filing document in database and provide the same in response with base64 encoded format along with the response status code.

Parameter URL
Method Headers

Value
<dcsmain application baseURL>/gstr/esignservice/api/v1/ dcsdownload GET Content-Type: application/json

The following table provides a list of query parameters:

Parameter name gstin repCatId fp

Data type String String String

repActivityId

String

Description

Example

GST Identification number

GST Return type

IN_GSTR1

Reporting period

022017
where 02 indicates reporting month and 2017 indicates re porting year

Activity for which filing is done.

GSTR1FILE

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Response

{ "code": <status>, "content": <filing document content in base64 format> } The following table details the Response JSON attributes:

Attribute code Content

Data Type String String

Description

Example

Status code

SUCCESS or FAILED

Selected filing document content for requested query parameters

9.2.1.1.2 RESTful API: dcsupload

This RESTful API accepts signed filing document content, type of signature and signatory ID as part of the request body, and header or query parameters to update the request content to the respective GSTR in the database.
The API returns the response content status and the document reference ID for content stored. The API also converts the received request content to JSON format as prescribed by the GSTN for filing returns.

Parameter URL
Method Headers

Value
<dcsmain application baseURL>/gstr/esignservice/api/v1/ dcsupload POST Content-Type: application/json

The following table provides a list of query parameters:

Parameter name gstin repCatId

Data type String String

Description

Example

GST Identification number

GST Return type

IN_GSTR1

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

Parameter name fp

Data type String

repActivityId

String

Description Reporting period
Activity for which filing is done.

Example
022017 where 02 indicates reporting month and 2017 indicates re porting year
GSTR1FILE

Request Body Payload

"sign": <signed filing document content in pkcs7 format>, "st": "<DSC>", "sid": "<PAN Number>" } The following table details the Request Body JSON attributes:

Attribute sign st sid

Data Type String String String

Description SStores signed content Signature Type Signer ID

Example
Either DSC or ESIGN If st is DSC, then sid will be PAN. If st is ESIGN, then sid will be Aadhaar number.

Response
{ "code": SUCCESS or FAILED "content": <Document Id if SUCCESS> }

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

The following table details the Response JSON attributes:

Attribute code content

Data Type String String

Description

Example

Status code

Either SUCCESS or FAILED

Content that is returned from Contains Document ID of dig

digital compliance service ital compliance service appli

application

cation

9.2.2 Integration Content Setup
SAP Cloud Integration for process integration facilitates the integration of business processes spanning different companies, organizations, or departments within an organization.
Recommendation
Perform the below mentioned steps in your TEST and PRODUCTION SAP Cloud Integration cockpit accounts.

9.2.2.1 Import SSL Certificates to SAP Cloud Integration Tenant
To set up an SSL connection between the SAP Cloud Integration tenant and eSign ASP, you must import the required security certificates into the SAP Cloud Integration tenant JAVA keystore. For more details, see Tenant Client Keystore.
Procedure
1. Create a new Keystore and import the eSign ASP trusted certificates into the keystore.
Note
You can use tools like Keystore Explorer to create a new keystore. 2. Add keystore entries to the JAVA keystore of the SAP Cloud Integration tenant by following the process
mentioned here. To perform the above operation, you need to be a tenant administrator with role AuthGroup.Administrator.
Recommendation
To check the connectivity with eSign ASP, run connectivity test using Monitor Manage Security Connectivity Tests .

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

9.2.2.2 Adapt eSign ASP Integration Content Template
An integration flow is a graphical representation of how the integration content can be configured to enable the flow of messages between two or more participants using SAP Cloud Integration, and thus ensure successful communication.

Context
The Integration between Digital Compliance Service to GST Suvidha Provider and eSign Application Service Provider content catalog contains pre-delivered integration template for eSign ASP. You can use integration flow eSign ASP Integration Template to build the specific eSign ASP integration flow. To find the integration flow in the content catalog, perform the following steps:

Procedure
1. In your browser, go to the WebUI of the SAP Cloud Integration tenant using the url: <SAP Cloud Integration Tenant URL>/itspaces.
2. To logon, enter your P user or S user.
If you get the HTTP Status 403 error, contact your tenant administrator. 3. After successful login, from the menu in the upper left corner, choose Discover. 4. In the subsequent screen, search for Integration between Digital Compliance Service to GST Suvidha
Provider and eSign Application Service Provider, and select the package. 5. Click on the entry and in the subsequent screen, choose Copy. 6. From the menu in the upper left corner, choose Design. 7. Click on Integration between Digital Compliance Service to GST Suvidha Provider and eSign Application
Service Provider catalog and in the subsequent screen, choose ARTIFACTS. 8. Select integration flow eSign ASP Integration Template. 9. Choose Actions Download .
The system downloads the integration content as a *.zip file. 10. Import the downloaded zip file to eclipse and modify the content to adapt eSign ASP integration. For more
details, seeManaging Integration Content .
Note
You need to adapt the eSign ASP communication and authentication for highlighted process call as shown in the above picture.
11. Configure the integration flow parameters as defined below: Receiver: DCS_server_get_Auth_token Parameter name: oauthasservices_url

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Description: SAP BTP account oAuth Token Endpoint Value: In your web browser, log on to the cockpit, and select an account.
Go to Security OAuth Branding section oAuth URL's Select and copy Token Endpoint value. Maintain the value without prefixing https
Sample value to be entered: <oauthasservices-example.com/oauth2/api/v1/token> Parameter name: Credential Name/dcsoAuthtokencredentials Description: user credential for client ID and client secret key for oAuth authentication. Value: get the ID and secret key for the registered oAuth client gstrapp in SAP BTP cockpit.
Use this ID and secret key as name and password while creating user credentials as mentioned in step 12 below. User credentials act as alias or reference to client ID and secret key maintained in security materials.
Enter the <user credential> created. Receiver: DCS_server_download/DCS_server_upload
Parameter: dcsapplurl Description: DCS main application URL Value: In your web browser, log on to the cockpit, and select an account.
Go to Connectivity Destinations and select ACRS_CORE_DEST. Under Destination Configuration, copy URL value.
For example, https://gstrappxxxxx.example.com/acrscore. Maintain the value without prefixing https.
For example, <gstrappxxxxx.example.com/acrscore>. Receiver: eSign_ASP_server_upload
Parameter: eSignASPGatewayUploadURL Description: eSign ASP gateway URL to upload raw content Value: Enter received eSign ASP gateway URL to upload raw content.
For example, https://esigngatewayurlupload.com. Maintain the value without prefixing https.
For example, <esigngatewayurlupload.com>. Parameter name: Credential Name/ eSignASPcredentials Description: user credential for eSign ASP client ID and client secret key Value: You would have received eSign ASP client ID and client secret key after eSign registration.
Use this ID and secret key as name and password while creating user credentials as mentioned in step 12 below. User credentials act as alias or reference to client ID and secret key maintained in security materials.
Enter the <user credential> created. Receiver: eSign_ASP_server_download
Parameter: eSignASPGatewaydownloadURL Description: eSign ASP gateway URL to download signed filing document content Value: Enter received eSign ASP gateway URL to download signed filing document content.
For example, https://esigngatewayurldownload.com. Maintain the value without prefixing https.
For example, <esigngatewayurldownload.com>.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

12. Create user credentials in Web UI of the SAP Cloud Integration tenant by performing the following steps:
In the SAP Cloud Integration Web UI, from the menu, choose Menu Monitor . Click Security Material. Choose the Add button, and select User Credentials. In the Add User Credentials screen, enter the following details:

Field name Name Description User Password Repeat password SuccessFactors

User action and values Enter Credential Name Free text Enter username/client_id Secret key Secret key Do not select

Choose OK to save the credentials.
13. Deploy the modified integration flow After the deployment, check if the integration flow is in Started state. You can check this by choosing Monitor Manage Integration Content . After successful deployment, the endpoint URL is https://<SAP Cloud Integration Tenant URL>>/http/dcs/ esign.

9.2.3 eSign ASP SAPUI5 Application Setup
The DCS eSign ASP SAPUI5 application acts as an interface between the DCS application screen and eSign ASP or Web service screen by exchanging data between the screens.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

9.2.3.1 Create Destination for eSign ASP SAP Cloud Integration flow
To access eSign ASP Integration flow, create a destination which will be accessed by the DCS eSign ASP user interface application.

Procedure
1. Create a new destination in the SAP BTP cockpit following the steps mentioned in Create HTTP Destinations.
2. Maintain the following values: Name: <destination name> Type: HTTP Description: <Description of the destination> URL: <eSign ASP Integration flow endpoint URL https://<SAP Cloud Integration Tenant URL>>/ http/dcs/esign> Proxy Type: Internet Authentication: Basic Authentication User: < enter your P user or S user with access to SAP Cloud Integration tenant where eSign ASP Integration flow is deployed> Password: <user password>
9.2.3.2 Create SAPUI5 application
Create a custom SAPUI5 application to capture the relevant information as per the requirements of the eSign ASP.

Context
To create an SAPUI5 application in SAP BTP Web IDE, refer Developing.

Procedure
1. Open SAP BTP cockpit in browser and select Service. 2. Search and select SAP Web IDE. 3. In the subsequent screen, select Go to Service.
The system redirects you to the SAP BTP Web IDE screen.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

4. To create a new SAPUI5 application, select new Project from Template . For more information, refer Create Projects from Templates.
5. Select SAPUI5 application from the template selection and follow the wizard to create the project. 6. From the created project, open the neo-app.json file and maintain the destination details that you have
already created in Create Destination for eSign ASP SAP Integration Flow. { "path": "/destinationaccess", "target": { "type": "destination", "name": "< destination name>", "entryPath": "/" }, "description": "<Description of the destination>" } 7. From the created project, open the view and make changes as per your business requirements to capture the relevant information required to be exchanged with eSign ASP APIs and DCS APIs. For example, the below code can be used in view (view type: XML) to create: For example, the below code can be used in view (view type: XML) to create: button to trigger eSign If you use the following code snippet, also ensure that you add the xmlns:f="sap.ui.layout.form" library to the view mvc.
Sample Code
<content> <f:SimpleForm editable="true" layout="ResponsiveGridLayout" maxContainerCols="2" labelSpanL="4" labelSpanM="4" labelSpanS="6"> <f:content> <Label text="{i18n>email}" required="true"/> <Input type="Email" id="email" width="60%" /> <Label text="{i18n>PanDetails}" required="true"/> <Input id="panDetId" width="60%" maxLength="10" />
</f:content> </f:SimpleForm> </content> <footer> <Toolbar> <ToolbarSpacer/> <Button text="{i18n>Esign}" press="onPress"/> </Toolbar> </footer>
8. Open the controller file linked to the view created above, and create a function that the system calls on choosing the eSign button.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Note
The digital compliance service application will pass below mentioned parameters/values to DCS eSign UI application during cross-application navigation. Provided information should be used to retrieve the document that is to be signed.
The following table details the information passed from DCS application UI to DCS eSign UI:

Parameter Name GSTNumber ReportCategoryID ReportingPeriod

Type String String String

ReportingActivityID

String

Description

Example

GST Identification number

GST Return type

IN_GSTR1

Reporting period

022017
where 02 indicates report ing month and 2017 indi cates reporting year

Activity for which filing is done

GSTR1FILE

9. When you choose the eSign button, the system initiates the first call to eSign ASP integration flow to download the file content to be signed from DCS application API, and then upload the same to eSign ASP API. Next, navigate to the eSign ASP user interface to complete the signing process.
Use the below code snippet in the eSign button function:
Sample Code

onPress: function(oEvent)

{

var oURLParsing = new sap.ushell.services.URLParsing();

var url = oURLParsing.getHash(location.href);

var oShellHash = oURLParsing.parseShellHash(url);

var data = {

//request payload to be filled and passed to eSign ASP Integration flow

"request": {

"gstin": oShellHash.params.GSTNumber[0],

"reportingcategory": oShellHash.params.ReportCategoryID[0],

"period": oShellHash.params.ReportingPeriod[0],

"repactivityid": oShellHash.params.ReportingActivityID[0],

"action": "dcs_download",

email": this.getView().byId("email ").getValue(),

"docid": "",

"placeholder1": "",

"placeholder2": "",

"stype":"<Type of signature>",

"sid":

this.getView().byId("panDetId").getValue()

}

};

var destinationaccessURL = "/destinationaccess"; var that = this; jQuery.ajax({

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

url: destinationaccessURL, contentType:'application/json', method:"POST", data: JSON.stringify(data), success: function(oResp) { // Integrate JavaScript SDK provided by eSign ASP }, error: function(oError) { sap.m.MessageBox.error(oError.responseText.split("</h1>") [1].split("</body>")[0]); } }); }

Note
In Success function of AJAX call, integrate JavaScript SDK provided by eSign ASP to call eSign ASP user interface. Using JavaScript SDK, you can navigate to eSign ASP user interface.
The following table details the request payload:

Parameter name gstin reportingcategory period

Data Type String String String

repactivityid action

String String

String

Description

Example

GST Identification number

GST Return type

IN_GSTR1

Reporting period

022017
where 02 indicates report ing month and 2017 indi cates reporting year

Activity for which filing is done

GSTR1FILE

Indicator to decide action required on integration flow
Possible default value: dcs_download dcs_upload

dcs_download:
To download the file content to be signed from DCS ap plication API and upload the same to eSign ASP API.

dcs_upload:

To download the signed content from eSign ASP API and upload the same to DCS application API

eSign requestor email

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Parameter name docid

Data Type String

placeholder1 placeholder2 stype sid

String String String String

Description

Example

eSign ASP Acknowledg ment ID

Acknowledgement ID re ceived for uploading file content to be signed to eSign ASP API

Field to pass any additional value, if required.

sType of signature

DSC or ESIGN

PAN of authorized represen tative if stype = DSC or AADHAR number of author ized representative if stype=ESIGN

Use the below code snippet to call eSign ASP integration flow and download the signed content, and the upload the same to the DCS API. Note that the below-mentioned code snippet should be called in Success function.
Sample Code

var oURLParsing = new sap.ushell.services.URLParsing();

var url = oURLParsing.getHash(location.href);

var oShellHash = oURLParsing.parseShellHash(url);

var data = {

//request payload to be filled and passed to eSign ASP Integration flow

"request": {

"gstin": oShellHash.params.GSTNumber[0],

"reportingcategory": oShellHash.params.ReportCategoryID[0],

"period": oShellHash.params.ReportingPeriod[0],

"repactivityid": oShellHash.params.ReportingActivityID[0],

"action": "dcs_upload",

email": this.getView().byId("email").getValue(),

"docid": "<acknowledgement ID received for eSign ASP>",

"placeholder1": "",

"placeholder2": "",

"stype":"<Type of signature>",

"sid":

this.getView().byId("panDetId").getValue()

}

};

var destinationaccessURL = "/destinationaccess"; var that = this; jQuery.ajax({
url: destinationaccessURL, contentType:'application/json', method:"POST", data: JSON.stringify(data), success: function(oResp) {

window.history.back(1);

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

}, error: function(oError) { sap.m.MessageBox.error(oError.responseText.split("</h1>") [1].split("</body>")[0]); }});

9.2.3.3 Deploy SAPUI5 application on SAP BTP
Once the SAPUI5 application development is completed and is executable, deploy SAPUI5 project from SAP Web IDE to SAP BTP as a new application or update to a previously deployed application in SAP BTP accounts.

Related Information
https://help.sap.com/viewer/825270ffffe74d9f988a0f0066ad59f0/Cloud/enUS/ 463b52bd34de4549ad05f6282ada02d6.html?q=Deploy%20Applications%20to%20SAP%20Cloud %20Platform
9.2.3.4 Register SAPUI5 Applications to SAP Fiori Launchpad
You can register an SAPUI5 application to SAP Fiori Launchpad directly from SAP Web IDE.

Context
Once registration is complete, a new tile is created in the launchpad which is assigned to a site, a catalog, and a group. You can navigate to the SAPUI5 application from the digital compliance service application using a semantic object and action.
Prior to registering an application, ensure you have made the following settings: Make sure you are assigned to the TENANT_ADMIN role in the SAP BTP cockpit. For more information,
seeUsing Services in the Neo Environment You have obtained the Fiori site details after installing the SAP Localization Hub, digital compliance service
for India solution in your SAP BTP.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Procedure
1. Register the SAPUI5 application created to the SAP Fiori Launchpad site created for SAP Localization Hub, digital compliance service for India.
For detailed information, see here 2. Enter the following values:
Semantic Object: Reporting Action: ESign Tile type: Static Site: Digital Compliance Services - GST India Catalog: DCS - Manage GSTR Returns Groups: Returns
Note
You can hide the tile by selecting tile type as No Tile. For more information, seehere .

9.2.4 Digital Signature
The GST Network (GSTN) has made digital or electronic signature mandatory for filing document content before filing returns.
This documentation will provide an overview of the digital signature methods recommended by GSTN and digital signature adoption options available in the SAP Localization Hub, digital compliance service solution. You can choose a different signing mechanism as per your need and convenience.
GSTN supports two ways of digital or electronic signature for electronic document content as given below:
Digital Signature Certificate (DSC) Digital Signature Certificates are the digital equivalent (that is, electronic format) of physical or paper certificates. A digital certificate can be presented electronically to prove one's identity, to access information or services on the Internet, or to sign certain documents digitally. In India, DSC are issued by authorized certifying authorities. Using a DSC is mandatory for authorized signatories of the following: Public Limited Company Private Limited Company Unlimited Company Foreign Company Limited Liability Partnership (LLP) Firm Foreign LLP Public Sector Undertaking Using a DSC is optional for individual tax payers and proprietary. Alternatively, Aadhaar + OTP based signing can be used via eSign gateway of digital or electronic signature. The GSTN accepts only PAN based Class II and III DSCs. To obtain a DSC, please contact one of the authorized DSC-issuing certifying authorities. After obtaining the DSC, register it with the GST portal before using it for signing the document. For more information, refer the government's official website.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

Note
An existing and a valid DSC obtained from certifying authorities can also be used for GST returns filing. Electronic Signature (Aadhaar + OTP based signing)
Electronic Signature is an online electronic signature service in India to generate an Aadhaar+ OTP (One Time Password) based digital signature for a document. A one-time password (OTP) is sent to a mobile phone number registered with Aadhaar at the time of digitally signing the document.
Overview
SAP Localization Hub, digital compliance service supports both DSC (Digital Signature Certificate) and Aadhaar + OTP-based digital signature. The following diagram illustrates the digital signature process overview.

SAP Localization Hub, digital compliance service supports DSC based signing using online and offline processes.
You should obtain a valid DSC USB dongle from one of the authorized DSC-issuing certifying authorities. If you are an individual tax payer or proprietary. choose the Aadhaar + OTP based signing.
Note
Aadhaar + OTP based digital signing will also be possible through the online process. However, Aadhaar + OTP based digital signing will not be discussed in detail as it would be required only for individual tax payers and proprietary

9.2.4.1 Offline Process
The following content explains how to generate digital or electronic signature for electronic document content using the digital signature certificate via a manual approach in SAP Localization Hub, digital compliance service for India. Note that for the offline process, you would not require integration with eSign ASP RESTful API or Web Scripts. The digital signature generation process should be performed manually by the user.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Prerequisites
You have performed the following: Obtained the DSC USB device and the DSC Interface software. Installed the DSC Interface software on your local client system where the digital or electronic signature
will be generated. Have a registered PAN, as recommended by the GSTN, at the time of filing digitally signed content.
Note
The DSC USB device is specially built to store digital signature certificates. The DSC Interface software acts an interface between filing document and DSC USB dongle attached to client system, and helps in generating digital signature to the selected filing document. DSC Interface should be obtained either from third-party entities (eSign ASP) or from certified authorities.
Ensure that the DSC USB device is attached to the client system at the time of digital signature generation.
Process
The DCS application allows you to download filing document to your local client system in JSON format. To do this, run the Manage GST Returns app and for a selected report run, choose the DSC Offline Service in the Select eSign Method dialog box. The digital signature certificate and the digital interface software installed on local client system should be used to sign the filing document content downloaded. After signing, the digitally signed document should be uploaded to the digital compliance service application either in TXT or JSON format.
Note
Filing document downloaded from the digital compliance service application will be in plain JSON format as provided by GSTN. Any formatting or encoding of filing document content before signing using DSC should be performed by the user manually as per the DSC Interface software requirement.
The digitally signed document content should be in the PKCS#7 format, as mentioned on the GSTN portal. The digital compliance service application accepts digitally signed document (either TXT or JSON) with below mentioned format: The TXT file should only contain signed content in PKCS#7 format with no other information or key value
pair. The JSON file should contain at least one root attribute with name pkcs7.
For example: { "pkcs7": "<signed content in PKCS#7 format>" }

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

9.2.4.2 Online Process
The following content explains how to generate digital or electronic signature for electronic document content using the digital signature certificate through an automated approach using the digital compliance service solution.
For the online process, you would require integration with the eSign ASP RESTful APIs or Web Scripts. The digital signature generation process is automated with minimum user interaction.
Develop the DCS eSign custom user interface application and integration flow to achieve seamless online digital signature process. The DSC USB device should be attached to client system to generate the digital signature.

Prerequisites
You have performed the following settings: Obtained the DSC USB device. Provisioned live SAP Cloud Integration Service test and/or productive tenants. Chosen eSign ASP or eSign gateway service providers and completed the registration process. Have a registered PAN, as recommended by the GSTN, at the time of filing digitally signed content. eSign Application Service Provider (eSign ASP) is an entity that signs the contract with the ESP to provide eSign Service. eSign ASP uses eSign service as part of their application to digitally sign the content. eSign ASP provides the interface software platform for users to sign documents using Aadhaar eSign or Digital Signature Certificate (DSC) USB device. eSign Service Provider (ESP), also known as certificate authority or Certifying Authorities (CA), is an entity that issues digital signature certificates for electronic authentication of users. SAP Localization Hub, digital compliance service provides documentation and SAP Integration flow template to develop DCS eSign custom user interface application and eSign ASP specific integration flow.
9.2.4.3 eSign ASP Integration Flow
eSign ASP integration flow is a generic integration template and should be modified or enhanced for integration with eSign ASP.

Context
This template contains process calls to set up communication with the DCS application. The process call for communication with eSign ASP must be added based on the details received after registering with eSign ASP. The content catalog package Integration between Digital Compliance Service to GST Suvidha Provider and eSign Application Service Provider contains the following integration flows:

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

PUBLIC

Integration Flow Name in WebUI GSP Integration Template eSign ASP Integration Template

Project Names/Artifact Names com.sap.slh.dcs.gsp.template com.sap.slh.dcs.esp.template

To find the integration flow in the content catalog, perform the following steps:

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Digital Compliance Service for India Integration

10 Applications
Configurations [page 67] Returns [page 76] Utilities [page 98] Previous: Digital Compliance Service for India Integration [page 46] Next: FAQ [page 107]
10.1 Configurations
Manage Authentication [page 68] You create a reporting entity and assign a unique GSTIN to this entity. Once the master data is updated, you need to authenticate the GSTIN with the GSTN before reporting the data. Note that you can report data only when the authentication is successful.
Manage Configuration [page 69] You can use this app to define and configure the business place for which you want to submit the compliance reports.
Parent topic: Applications [page 67]
Related Information
Returns [page 76] Utilities [page 98]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

10.1.1 Manage Authentication
You create a reporting entity and assign a unique GSTIN to this entity. Once the master data is updated, you need to authenticate the GSTIN with the GSTN before reporting the data. Note that you can report data only when the authentication is successful. The Manage Authentication app allows you to authenticate or validate your GSTIN and subsequently post the relevant data to the GSTN for processing.
Parent topic: Configurations [page 67]
Related Information
Manage Configuration [page 69]
10.1.1.1 Getting Started with Manage Authentication
Procedure
1. From your Fiori Launchpad, log on to the Manage Authentication app. You can see your entry for the GSTIN assigned to the reporting entity in the Manage Configuration app. Status of the GSTIN entry is EXPIRED.
2. Choose the Edit icon. You can see the Edit GSTN screen.
3. Enter your GST user name, and choose Save. 4. Choose Authenticate.
You can see the Enter OTP/Authentication dialog box. 5. Enter the one-time password you receive on the registered mobile number. 6. Choose OK.
The status of your entry is now ACTIVE. 7. Choose the Refresh Token button if you do not want to perform manual authentication.
This ensures that your token, received from the GSTN, is kept active beyond its initial active period of 120 minutes.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

10.1.2 Manage Configuration
You can use this app to define and configure the business place for which you want to submit the compliance reports.
The Manage Configuration app consists of the following features:
Define business places for GST compliance reporting. You can define new business places for your compliance reporting requirements. A business place is the legal entity that is obliged to submit certain compliance reports.
Assign forms to a business place. You can assign forms to your business place. A form corresponds to the kind of compliance reporting you should do, such as, GSTR-1 returns.
Note
Forms are pre-delivered by SAP. You can only assign forms predelivered by SAP.
Set periodicity of forms. You can tell the system when you should start working on each of the compliance reports for a business place, determine your company's due date for submission, and when the business users should be notified that the due date is approaching.
Assign GST Identification Number (GSTIN) to the business place. Authorization at business place or form level.
You can assign users to the business place, to be able to submit the compliance reports via the Outward Supply Returns app. Only the users assigned to an activity is authorized to perform relevant activity at form level. Configuration of scheduler for pulling the GSTR2A invoices and perform reconciliation. Define activity at form level. You can assign activities such a Save, Submit, File to the user. Assign relevant activities to the users so that they can perform the activities. Configuration of scheduler for pulling the eInvoice data before saving GSTR1 return.
Getting Started with Manage Configurations [page 69]
Parent topic: Configurations [page 67]

Related Information
Manage Authentication [page 68]

10.1.2.1 Getting Started with Manage Configurations
Use the Manage Configuration application to: Create a New Business Place [page 70]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

Copy a new business place [page 71] Update a business place [page 72] Activate or Deactivate a business place [page 73] Copy user assignment [page 73] Update user assignment [page 74] Configure Scheduler [page 75]
The Scheduler tab under the Manage Configuration application helps you in pulling the GSTR2A invoices and eInvoice data.
Parent topic: Manage Configuration [page 69]
10.1.2.1.1 Create a New Business Place

Procedure
1. From your SAP Fiori launchpad, log on to the Manage Configuration app. 2. Choose the Add icon on the screen.
The system displays the Configure Business Place screen.
3. Maintain Business Place configuration. In the Business Place Configuration section, enter business place and GSTIN data.
4. Assign Form to Business place. In the Available Reporting Form section, select the relevant form and click on Move to Selected button.
The system displays the selected form in the Selected Reporting Form section. 5. Assign users to the business place. In the Available Users section, select the relevant user and click on
Move to Selected button.
The system displays the selected user in the Selected User section.
Note
You can choose to allow or restrict the actions that each user can perform within the application by assigning appropriate user access under Assigned Users tab. For example: A user with Read Only access cannot adjust the reconciliation settings or perform manual upload whereas a user with All Actions access is able to perform all the operations in the application.
6. Choose Next . The system displays the Configure Business Place screen based your inputs in previous steps.
7. Maintain reminder settings such as Notify by, Notify unit. 8. Assign activity to the users at form level. In the Assigned Users section, select the relevant activity such as
Save, Submit, File to the user as follows:

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

a. Select the relevant form in the GSTR Forms dropdown. b. Set the relevant activity and save.
In case, you select form GSTR1 or GSTR2, the default scheduler configuration is set. You have an option to make further changes before saving the configuration.
Task overview: Getting Started with Manage Configurations [page 69]
Related Information
Copy a new business place [page 71] Update a business place [page 72] Activate or Deactivate a business place [page 73] Copy user assignment [page 73] Update user assignment [page 74] Configure Scheduler [page 75]
10.1.2.1.2 Copy a new business place

Context

Procedure
1. From your Fiori launchpad, logon to the Manage Configuration app. 2. Choose the Copy icon on the screen.
The system displays the Copy Business Place screen. 3. Maintain the following:
a. New GSTIN ID b. Existing GSTIN ID c. Business Place d. Click OK
Task overview: Getting Started with Manage Configurations [page 69]
SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

Related Information
Create a New Business Place [page 70] Update a business place [page 72] Activate or Deactivate a business place [page 73] Copy user assignment [page 73] Update user assignment [page 74] Configure Scheduler [page 75]
10.1.2.1.3 Update a business place

Procedure
1. From your Fiori launchpad, logon to the Manage Configuration app. The system displays the Configure Business Place screen.
2. Choose the relevant business place record. The system displays the relevant business place record in display mode.
3. Select the Edit button to make relevant changes 4. Click the Next button, maintain relevant data and save 5. Click the Republish button to update master data changes in the database 6. Click the Information button to view the change log
Task overview: Getting Started with Manage Configurations [page 69]

Related Information
Create a New Business Place [page 70] Copy a new business place [page 71] Activate or Deactivate a business place [page 73] Copy user assignment [page 73] Update user assignment [page 74] Configure Scheduler [page 75]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

10.1.2.1.4 Activate or Deactivate a business place

Context

Procedure
1. From your Fiori launchpad, logon to the Manage Configuration app. The system displays the Configure Business Place screen.
2. Change the Is active value for the relevant business place record Note that you can report GSTN data only for active business place
Task overview: Getting Started with Manage Configurations [page 69]
Related Information
Create a New Business Place [page 70] Copy a new business place [page 71] Update a business place [page 72] Copy user assignment [page 73] Update user assignment [page 74] Configure Scheduler [page 75]
10.1.2.1.5 Copy user assignment

PUBLIC

3. Select the relevant user record. 4. Select the Copy button. 5. Maintain relevant data and save.
Task overview: Getting Started with Manage Configurations [page 69]
Related Information
Create a New Business Place [page 70] Copy a new business place [page 71] Update a business place [page 72] Activate or Deactivate a business place [page 73] Update user assignment [page 74] Configure Scheduler [page 75]
10.1.2.1.6 Update user assignment

Procedure
1. From your Fiori launchpad, logon to the Manage Configuration app. The system displays the Configure Business Place screen.
2. Choose the User Assignment section. The system displays the user records.
3. Click the relevant user record The system displays the user records in display mode.
4. Choose Edit 5. Maintain relevant data such as update business place assignment, activity assignment 6. Click Save
You can also export the user details to an excel by clicking the icon on your right-hand corner.
Task overview: Getting Started with Manage Configurations [page 69]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

Related Information
Create a New Business Place [page 70] Copy a new business place [page 71] Update a business place [page 72] Activate or Deactivate a business place [page 73] Copy user assignment [page 73] Configure Scheduler [page 75]
10.1.2.1.7 Configure Scheduler
The Scheduler tab under the Manage Configuration application helps you in pulling the GSTR2A invoices and eInvoice data.

Procedure
1. Select an existing GSTIN from the Business place configuration screen. 2. Choose Edit and then choose Next. 3. Select a relevant form under the GSTR Forms drop-down to configure scheduler.
GSTR2 form for pulling GSTR2A invoices. GSTR1 form for pulling eInvoice data. 4. Set the Periodicity as either Daily, Weekly, or Bi-monthly where: Daily: Specifies to run the scheduler for a specific GSTIN daily. Weekly: Specifies the day of the week during which you want to run the scheduler for a specific GSTIN. Bi-monthly: Specifies the 2 days of a month during which you want to run the scheduler. 5. Set the Months to Pull for GSTR forms. For GSTR2 form, the default value is 2 months. You can set up to a maximum of 18 months. For GSTR1 form, the default value is 1 month. You can't reset this value. Months to Pull: Refers to the months to pull from the current month. 6. Choose Activate and Save.

Next Steps
Choose Scheduler under the Manage Configuration app to see the list of GSTINs on which the scheduler is activated. You can also view the scheduler for each GSTIN from the same screen.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

Note
You can copy the scheduler configuration of a GSTIN to another GSTIN by using the Copy Scheduler Configuration function available next to the search field. You can also turn On/ Off the scheduler.
Task overview: Getting Started with Manage Configurations [page 69]
Related Information
Create a New Business Place [page 70] Copy a new business place [page 71] Update a business place [page 72] Activate or Deactivate a business place [page 73] Copy user assignment [page 73] Update user assignment [page 74]

10.2 Returns

View GSTR9 Details [page 77] GSTR 9 is an annual return to be filed by the taxpayers registered under GST in India. It consists of details regarding outward and inward supplies made/received during the relevant financial year. It's a consolidation of all the returns (GSTR-1, GSTR-2A, GSTR-3B) filed in that year.
View GSTR3B Details [page 78] GSTR-3B is a monthly return to be filed by a registered GST tax payer in India. It's a simplified return that consolidates the details of outward & inward supplies.
File or Save ITC-04 Returns [page 80] ITC-04 Returns under GST form are filed by a manufacturer quarterly in India. It shows the details of inputs/capital goods dispatched or received from a job worker, Inputs/Capital goods sent from one job worker to another job workers in the quarter, and Inputs/Capital goods supplied from the premises of job workers in the quarter.
Reconcile ISD Invoices (GSTR6) [page 81] GSTR 6 is a monthly return that has to be filed by an Input Service Distributor in India. It contains details of Input Tax Credit received by an Input Service Distributor and distribution of Input Tax Credit. The input service distributors must file these returns by the 13th of the subsequent month.
File a GSTR1 Return [page 84] GSTR-1 is a sales return that is required to be filed by every GST registered Tax payer in India. GSTR1 can be filed on a monthly or quarterly basis based on the Tax payer's turnover.
Reconcile Inward Invoices (GSTR2) [page 90] You can use this application to monitor the inward supply invoices uploaded to the digital compliance service application, upload new purchase invoices via Microsoft Excel, get supplier invoices in the

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

GSTR2A/GSTR2B format, and reconcile inward invoices. For a selected period, the application proposes the Input Tax Credit available for the tax payer, after the inward invoices are reconciled.
Parent topic: Applications [page 67]

Related Information
Configurations [page 67] Utilities [page 98]

10.2.1 View GSTR9 Details
GSTR 9 is an annual return to be filed by the taxpayers registered under GST in India. It consists of details regarding outward and inward supplies made/received during the relevant financial year. It's a consolidation of all the returns (GSTR-1, GSTR-2A, GSTR-3B) filed in that year.

Context
Steps to view and authenticate the GSTR9 details.

Procedure
1. From your SAP Fiori launchpad, log on to the View GSTR9 app.
System displays the Selection Criteria for GSTR9 screen. 2. Enter the GSTNID and the time period.
Note that you enter the GSTNID that you've registered in the tax portal. 3. Choose OK.
The system displays the GSTR9 Details screen.
Note that you need to authenticate the GSTIN ID with the GSTN to view the reporting data. If status of the GSTIN ID entry is EXPIRED, then the system displays the error message that the GSTIN is currently not authenticated. 4. Use the following steps to authenticate the GSTIN: a. Choose Click here to authenticate link. The system displays the authentication screen. b. Enter the one-time password you receive on the registered mobile number. c. Choose OK.
The status of your entry is now ACTIVE.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

d. Choose the Refresh Token button if you don't want to perform manual authentication. This ensures that your token, received from the GSTN, is kept active beyond its initial active period of 120 minutes.
5. View the GSTR9 data. The system displays 4, 5, 6, 7 and 9 section of GSTR 9. 6. Choose the Download button to download section details.
a. Save the data in your local location. b. Open it to view it. 7. Choose the Get GSTR3B button to get the GSTR3B data from GSTN
The system displays the message that the GSTR3B Pull is initiated. Check the get Request Status for detailed information.
Note that if you previously pulled the GSTR3B data, the system displays the following message.
GSTR3B data is successfully pulled. Do you want to pull the data again.
Select yes to pull the data again.
The system displays the following message GSTR3B Pull is initiated. Please check the get Request Status for detailed information. 8. Choose the Request Status button to view the status of the GSTR3B data being pulled from GSTN.
The system displays the GSTR3B data on the Request Status screen.
Task overview: Returns [page 76]

Related Information
View GSTR3B Details [page 78] File or Save ITC-04 Returns [page 80] Reconcile ISD Invoices (GSTR6) [page 81] File a GSTR1 Return [page 84] Reconcile Inward Invoices (GSTR2) [page 90]
10.2.2 View GSTR3B Details
GSTR-3B is a monthly return to be filed by a registered GST tax payer in India. It's a simplified return that consolidates the details of outward & inward supplies.

Procedure
Steps to view and authenticate GSTR3B details. 1. From your SAP Fiori launchpad, log on to the View for GSTR3B app.
System displays the selection criteria for GSTR3B screen.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

2. Enter the GSTIN and the reporting period.
Note
Enter the GSTIN that you've registered in the tax portal.
3. Choose OK. The system displays the GSTR3B Details screen.
Note
You need to authenticate the GSTIN ID with the GSTN to view the reporting data. If the status of GSTIN ID entry is EXPIRED, then the system displays the error message that the GSTIN is currently not authenticated.
4. Use the following steps to authenticate the GSTIN: 1. Choose Click here to authenticate link. The system displays the Authentication screen. 2. Enter the one-time password you receive on the registered mobile number. 3. Choose OK. 4. The status of your entry is now ACTIVE. 5. Choose the Refresh Token button if you do not want to perform manual authentication. This ensures that your token, received from the GSTN, is kept active beyond its initial active period of 120 minutes.
5. View the GSTR3B data. The system displays the 3.1, 3.2, 4, and 5 sections of GSTR3B. 6. Choose Download to download the section details
1. Save the data in your local location. 2. Open it to view it

GSTIN Ledger Balances
You can also see the GSTIN ledger balances from the GSTR3B details screen. To view the ledger balances, choose GSTN Ledger. The system fetches and displays the ledger summary from GSTN for the GSTIN and reporting period selected in the GSTR3B details screen. The ledger summary includes details on Liability ledger, ITC ledger, and Cash ledger. The total eligible ITC is displayed under the ITC ledger tab.
Parent topic: Returns [page 76]

Related Information
View GSTR9 Details [page 77] File or Save ITC-04 Returns [page 80] Reconcile ISD Invoices (GSTR6) [page 81] File a GSTR1 Return [page 84] Reconcile Inward Invoices (GSTR2) [page 90]
SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

10.2.3 File or Save ITC-04 Returns
ITC-04 Returns under GST form are filed by a manufacturer quarterly in India. It shows the details of inputs/ capital goods dispatched or received from a job worker, Inputs/Capital goods sent from one job worker to another job workers in the quarter, and Inputs/Capital goods supplied from the premises of job workers in the quarter.

Procedure

1. From the SAP Fiori launchpad, log on to the ITC-04 Returns app. 2. Enter the Tax Payer GSTIN and select a Financial Year and choose Go.
The system displays the ITC-04 reports status over the four different quarters of the chosen financial year. Against each quarter, you can see whether the status of the report is in Filed or Save. Save is to upload the challans in DCS application to GSTIN. File is to file the ITC-04 for that specific quarter. 3. Choose Save. The system displays the ITC-04 screen with the challan status overview and lists the challans based on the Tax Payer GSTIN and the Financial Year chosen in step 2. 4. You can perform the following four actions in the ITC-04 screen: 1. Manage Manual Uploads: To upload M2JW or JW2M challans to DCS. The M2JW or JW2M challans
have the following status in the DCS application: Uploaded: The challans are uploaded to DCS successfully. Not Uploaded: The challans are not uploaded to DCS due to incorrect data. Invalid File: The challans are not uploaded due to incorrect format 2. Upload to GSTN: To upload the challans to GSTN, which is uploaded either from DCS or ECC. 3. GSTN Upload History: To check the status of those challans that are uploaded to GSTN. 4. View Summary: To pull the data from GSTN and to view the data of the M2JW or JW2M challans uploaded to GSTN. 5. Choose Manage Manual Uploads. The screen displays the list of uploaded files, which you can filter based on the Created At, Created By, and Acknowledgement ID. You can also perform further actions in this screen using the following action buttons: Download Template: To download the template for M2JW and JW2M. Upload Challan: To upload the challans in DCS. Remove Invalid Files: To delete challans with the status as Invalid File. 6. Choose Upload Challan to upload a M2JW or JW2M challan. 7. Choose Refresh to check if the status of the challan is Uploaded. 8. Go to the ITC-04 screen and choose Upload to GSTN. The system displays all the M2JW and JW2M challans with taxable amount, which are ready to upload to GSTN. These challans are of the following statuses: New: Challans that are ready to be uploaded to GSTN. In process: Challans that are in the process to be uploaded to GSTN. Uploaded: Challans that are uploaded to GSTN.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

Uploaded (Modified): Challans that are uploaded to GSTN with some modification, these challans are uploaded again in DCS with M that is, modified flag and the uploaded to GSTN.
Filed: Challans that are filed for a quarter. Error: Challans that are not uploaded to GSTN due to incorrect data. Deleted: Challans that are uploaded in DCS and then deleted from DCS using the D that is, Deleted flag
in excel. Uploaded (deleted): Challans that were first uploaded to GSTN but later deleted from GSTN.
Note
Only those challans with the status as New, Uploaded (Modified) and Uploaded (Deleted) can be uploaded to GSTN.
9. Choose Proceed to Upload and the message Successfully created transaction is displayed. 10. Choose GSTN Upload History to check the status of the challans, which are uploaded to GSTN.
The status of the uploaded challans are of the following type: Successfully uploaded to GSTN (Green) Challans are not uploaded to GSTN as they contain some errors (Red) Challans are in progress (Yellow) Not yet started 11. Choose Re-Trigger Transaction to restart the transaction for those challans that are in the Not yet started status.
Parent topic: Returns [page 76]
Related Information
View GSTR9 Details [page 77] View GSTR3B Details [page 78] Reconcile ISD Invoices (GSTR6) [page 81] File a GSTR1 Return [page 84] Reconcile Inward Invoices (GSTR2) [page 90]
10.2.4 Reconcile ISD Invoices (GSTR6)
GSTR 6 is a monthly return that has to be filed by an Input Service Distributor in India. It contains details of Input Tax Credit received by an Input Service Distributor and distribution of Input Tax Credit. The input service distributors must file these returns by the 13th of the subsequent month.
Prerequisite: You have been assigned to the Source Administrator authorization group.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

Note
Currently, SAP Digital Compliance Service for India, supports the following features under GSTR6:
Download of supplier invoices via GSTR6A. Upload of purchase invoices from source system. Reconciliation between purchase invoices and GSTR6A invoices.

Procedure
1. From the SAP Fiori launchpad, log on to the GSTR6 app. 2. Enter the GSTIN, Financial Year, Financial Periods, and choose the Invoice type and click Go.
You can see the graphical representation of the invoices in Reconciliation status, and the ITC Trend and Missing GSTN trend. 3. Choose Purchase Register (PR) and select the Financial Period, Invoice Date, Invoice Type. The system displays a list of invoices uploaded to the digital compliance service application under the Reconcilable Invoices tab.
Note
The Reconcilable Invoices tab contains only the B2B and CDN invoice since only these invoice types can be reconciled.
1. To view the details, select an invoice. The system displays the invoice details in the subsequent screen.
2. In the Invoice History/Details tab, you can view the entire history of the invoice like the time of invoice upload from source system, invoice upload to GSTN and so on.
3. Choose the Manage Manual Uploads button to upload new invoices via Microsoft Excel. The system displays the list of uploads already completed. For uploads with status Uploaded with Errors, you can view the error log by clicking on the respective upload entry. The system displays the log on the right-side pane.
4. Start a new upload by clicking on the Add button. 5. In the Upload File dialog, click Browse to locate the file and then choose Upload.
The system creates a new entry under Uploads, with status New, on the Manage Manual Uploads screen. 6. Choose Refresh. The system changes the status once the file is processed. 7. SAP delivers a total of 6 additional fields that you can name as per your business requirements. To utilize these fields, choose the Maintain Custom Fields button. 8. In the Maintain Custom Field Label dialog box, choose against the field key and enter the description. 9. Save your changes. The system enables one or more fields across all the invoices. 4. Choose Supplier Invoices and select the Financial Period, Invoice Date, Invoice Type. The system displays the list of invoices under the Invoice Details and Counter party Wise Summary tabs. You can click on an invoice to see its details. 5. Choose Reconciliation.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

The screen displays the invoice data for the GSTIN and financial period you have chosen in step 2. You can filter the invoices based on the Invoice Period, Reconciliation Type, Invoice Type, Reconcile status, Counter Party GSTIN/ PAN, and Invoice Date. The reconcile inward invoices screen lists the invoices under the Summary Details, Reconciled Invoice Details and Amended Original Invoice Details tab. The table below details the reconciliation types and sub-types:

Reconciliation Type Complete Match (CM) Partial Match (PM) Probable Match (PRBM)
Missing in GSTN (MIG) Missing in Source (MIS)

Reconciliation Subtype
Complete Match (CM) Within Tolerance (ITC <)(ITC_LESS_WT) Within Tolerance (ITC >)(ITC_MORE_WT)
Item Mismatch (ITEM_MISMATCH) Exceeds Tolerance (ITC <)(ITC_LESS_WOT) Exceeds Tolerance (ITC >)(ITC_MORE_WOT)
PAN match (PAN_MATCH_POS_MATCH) - Within Tolerance POS /CP GSTIN Mismatch (PAN_MATCH_POS_MISMATCH) - Within
Tolerance Reverse Charge Mismatch (REVERSE_CHARGE_MISMATCH) - Within
Tolerance POS /CP GSTIN match (POS_NOTMATCH) - Within Tolerance Invoice Number Mismatch (Inv_num_mismatch) - Within Tolerance
Only in Source System
Only in GSTN System

6. Choose Reports to view the reconciled reports. You can filter the reconciled reports based on the following: Tax Payer/ Counter Party Report Tax Payer PAN Report Counter Party PAN Report Comprehensive Report

Parent topic: Returns [page 76]

Related Information
View GSTR9 Details [page 77] View GSTR3B Details [page 78] File or Save ITC-04 Returns [page 80] File a GSTR1 Return [page 84] Reconcile Inward Invoices (GSTR2) [page 90]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

10.2.5 File a GSTR1 Return
GSTR-1 is a sales return that is required to be filed by every GST registered Tax payer in India. GSTR1 can be filed on a monthly or quarterly basis based on the Tax payer's turnover. You can use the GSTR1 Return app to save all the inward and outward supply details to the GSTN.
Procedure
1. From your SAP Fiori launchpad, log on to the GSTR1 Return app. Based on the Tax Payer GSTIN, Financial Year, and Reporting Period, you can see the list of relevant reports. You can further filter the reports based on the Document Type and GSTN Communication Status.
2. Choose any form type on the left-hand side, under Overview to narrow down the search results for a specific form type.
3. Choose a reporting task that is due for submission. Based on the authorizations, you can see the list of activities that are assigned to the report. However, you can only perform those activities for which you have the necessary authorization.
4. For a GSTR-1 report, you should perform the following activities in the sequence given below:
1. Preview Outward Supply Details [page 85] You have a preview of the eInvoice data fetched from GSTN on this screen where you can do a comparison with the invoices in DCS.
2. Save Outward Supply Details [page 86] You create and save the outward supply invoices.
3. Submit Outward Supply Details [page 88] You submit the saved outward supply invoices.
4. File Outward Supply Details [page 89] You file the submitted outward supply invoices.
Parent topic: Returns [page 76]
Related Information
View GSTR9 Details [page 77] View GSTR3B Details [page 78] File or Save ITC-04 Returns [page 80] Reconcile ISD Invoices (GSTR6) [page 81] Reconcile Inward Invoices (GSTR2) [page 90]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

10.2.5.1 Preview Outward Supply Details
You have a preview of the eInvoice data fetched from GSTN on this screen where you can do a comparison with the invoices in DCS.
Context
GSTN auto-populates certain sections of the GSTR1 based on the eInvoice data that has been sent by the taxpayer earlier. In the preview screen, you can fetch the auto-populated invoice data from GSTN and do a comparison with the invoices in DCS. The DCS application reconciles the data and shows a preview of the invoice file that is created when the next invoice file is created. GSTN recommends sending only the invoices changed after eInvoice generation in GSTR1. A preview helps you to achieve this recommendation.
Note
You cannot save any data in the preview screen. It is just a summary of data auto-populated.
Note
We have two additional functionalities Logs (checks the process while the system is fetching the data from the GSTN) and Manual Upload (used to manually upload the invoices, in case the integration of the DCS system with the GSTN is not working).
Note
Preview screen is not applicable if, the tax payer is registered as a SEZ supplier.

Procedure
1. From your SAP Fiori launchpad, log on to the GSTR1 Return app. 2. Select the activity you want to save with status In Progress.
A preview screen appears with complete details of the selected activity under three different sections, GSTR1 Summary Data, E-Invoice Auto Population, and Preview Invoice File. 3. Choose Generate Summary button on the top-right corner of the screen under the GSTR1 Summary Data section.
This step fetches the summary of the GSTR1 data as per the information available in the GSTN. This table also gives you a comparison between the data in the DCS system and the data fetched from the GSTN. 4. Choose Get E-invoices button under the E-Invoice Auto Population section.
This fetches all E-invoice data from the GSTN system and auto populates the table for the four sections, B2B Invoices, Credit/Debit Notes (Registered), Credit/Debit Notes (Unregistered), and Export.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

Note
From DCS 1.10.0 onwards, pulling of eInvoice data can be scheduled/automated. Check Scheduler Configuration under Manage Configuration. 5. Choose Preview Invoice File button once the data is available in the previous two sections. Based on the data pulled in the previous two steps, the Preview Invoice File provides you the differences in the data. You can preview any discrepancy in the pulled data and send it to the GSTN by proceeding to the save functionality.
Task overview: File a GSTR1 Return [page 84]
Next task: Save Outward Supply Details [page 86]
10.2.5.2 Save Outward Supply Details
You create and save the outward supply invoices.

Context
Before you start this activity, ensure that the Save activity is in Not Started or In Progress status. If the Save activity is in On hold status, click on the Unblock Save button to change the status to In Progress.

Procedure
1. From your SAP Fiori launchpad, log on to the GSTR1 Return app. 2. Choose Save. The system takes you to the preview screen first to verify the details before saving. After
previewing, click on Save GSTR1, which redirects you to the GSTR-1 Save Overview screen.
The screen displays the status overview of all outward supply invoices. Additionally, you can also view the overview of GSTR-1 file uploads under the following categories: IN-PROCESS
Displays all GSTR-1 files, which are prepared and pending upload to the GST Network (GSTN). The files can have any one of the following statuses: Created
Indicates that the file is ready to be uploaded to GSTN. Cancelled
Indicates that the file has been cancelled before upload to GSTN. No further processing is allowed. SENT

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

Displays all GSTR-1 file that has already been reported to the GSTN. The files can have any one of the following statuses: Sent to GSTN
Indicates that the file has been reported to GSTN and a GSTN reference ID has been received. However, the file is yet to be processed by GSTN. Accepted by GSTN Indicates that the file has been processed by GSTN without any errors. Accepted with errors by GSTN Indicates that the file has been processed by GSTN with errors in some or all invoices. Invalid File Indicates that the GSTN was unable to process the file due to an invalid format.
The request and response JSON for each of the above-mentioned files can be downloaded by clicking on the respective View links. 3. Choose Create. You can create the following GSTR-1 files:
Invoice file Creates a GSTR-1 file containing sections that the system reports to GSTN at an invoice level. For example, B2B invoices, B2C large invoices, Credit/Debit notes, and export invoices.
Note
If the status of the invoice file is No Data and the description is No invoices pending to be sent to GSTN, you can proceed to summary file creation.
Summary file Creates a GSTR-1 file containing sections that the system reports to GSTN at a state-wise consolidated level. For example, B2C small invoices, nil-rated invoices, advance received and advance adjusted details, HSN summary, and document issued details.
Note
SAP recommends that you create one summary file every month. Ensure that the summary file is the last to be uploaded to the GSTN before saving.
Delete file Creates a GSTR-1 delete file. 1. Choose the Add new invoices to the section button. 2. In the Add pop-up, select the invoices, and choose Add. The system adds the selected invoices to the delete file. 3. Choose Upload to GSTN to report the deleted invoices to the GSTN.
4. Select Invoice File. 5. In the Create Invoice File pop-up, choose Save.
The system creates a GSTR-1 invoice file.
Choose the newly created file to view the details on the right-side pane. This pane provides an overview of the sections included in the file. Also, you can view the summarized tax amounts for each section. 6. Choose the newly created invoice file to view the details in the right-hand pane. These details include the consolidate taxable amount and the various taxes for each GSTR-1 section. 7. To view the individual section details, click on the relevant section. The system displays the list of all invoices under that section.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

You can also remove individual invoices by selecting them and choosing the Remove Invoices button. In the Remove Invoices pop-up, choose Remove. 8. Choose the Upload to GSTN button to upload the GSTR-1 file to GSTN. 9. In the Upload File pop-up, choose Yes. The system changes the file status to Sent to GSTN and the file is moved under SENT on the Outward Supply Returns - Save screen. 10. Select the file by clicking on the radio button and choose the Get Status button. The system fetches the file processing status from GSTN, if available and the status changes to Accepted by GSTN. In case the status is Accepted with errors by GSTN, you can view the error log by selecting the file and choosing the View Errors button. 11. Go to Outward Supply Returns screen. 12. Choose Update Status to update the Action and select On-Hold. The save activity is now on-hold and you can continue with the submit/file activity.
Task overview: File a GSTR1 Return [page 84]
Previous task: Preview Outward Supply Details [page 85]
Next task: Submit Outward Supply Details [page 88]
10.2.5.3 Submit Outward Supply Details
You submit the saved outward supply invoices.
Context

Procedure
1. From your SAP Fiori launchpad, log on to the Form GSTR1 app. 2. Choose Save to GSTN to navigate to the next screen. 3. Choose Generate Summary.
The system fetches the GSTR1 Summary from the GSTN and sets the status of the run to Generated Successfully.
Note
If for some reason, the system is unable to generate a successful run, the reason is displayed in the Log section of the Run Details screen. To regenerate the run, choose the Regenerate summary button.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

4. You can view the summary data. Additionally, you can: Get specific sections from GSTN. To do so choose the Pull section button. Export summary details to CSV. To do so choose the Export to CSV button.
5. Choose Submit button to submit the GSTR1 return to GSTN. The system changes the status of the report run to Sent to GSTN.
6. Choose Get Status button to get the status of GSTR1 return. The system uses reference ID to get the status from the GSTN. The system changes the status of the report run changes to Accepted by GSTN
7. Choose Download button to download the summary file.
Task overview: File a GSTR1 Return [page 84]
Previous task: Save Outward Supply Details [page 86]
Next task: File Outward Supply Details [page 89]
10.2.5.4 File Outward Supply Details
You file the submitted outward supply invoices.
Context
Before you start this activity, ensure that the Submit activity is completed.
Procedure
1. From your SAP Fiori launchpad, log on to the GSTR1 Return app. System displays the list of relevant compliance records. Based on the Tax Payer GSTIN, Financial Year, and Reporting Period, you can see the list of relevant reports. You can further filter the reports based Document Type and GSTN Communication Status.
2. Choose Save to GSTN activity to navigate to the next screen. 3. Choose File button. 4. Choose Generate Summary
The system fetches the summary file from the GSTN and sets the status of the run to Generated Successfully.
Note
If for some reason, the system is unable to generate a successful run, the reason is displayed in the Log section of the Run Details screen. To regenerate the run, choose the Regenerate summary button.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

5. Choose eSign button to digitally sign the document.
The system displays the Select eSign Method dialog box. 6. Choose DCS Offline Service radio button or the eSign Gateway Service radio button.
If you choose DCS Offline Service, the system gives you an option to download the summary file. After downloading the file, sign the file using the USB DCS dongle. The eSign provider gives you a signed file in a format specific to that provider. You can upload the signed content either in TXT or in JSON format. If you choose the TXT format, copy the signed content from the file provided by the eSign provider and paste it in to the TXT file that you have created. If you choose the JSON format, copy the signed content from the file provided by the eSign provider and create a file structure in your JSON file using the following format: { "pkcs7": "<signed content>" }
Upload the file to the SAP Localization Hub, digital compliance service for India solution by choosing the Upload button.
If you choose eSign Gateway Service, the system takes you to an external user interface. For more information, refer <eSign Guides>.
7. Choose File button to submit the signed document to GSTN.
The system changes the status of the report run to Sent to Government. 8. Choose report run, links for Response are available. 9. Choose Get Status button to get the status from GSTN. The system uses this reference ID while updating
the status to the GSTN. If successful, the status of the report run changes to File Accepted by GSTN. The system also changes the status of Submit/File to File Accepted by GSTN.
Task overview: File a GSTR1 Return [page 84]
Previous task: Submit Outward Supply Details [page 88]
10.2.6 Reconcile Inward Invoices (GSTR2)
You can use this application to monitor the inward supply invoices uploaded to the digital compliance service application, upload new purchase invoices via Microsoft Excel, get supplier invoices in the GSTR2A/GSTR2B format, and reconcile inward invoices. For a selected period, the application proposes the Input Tax Credit available for the tax payer, after the inward invoices are reconciled.
Prerequisite: You have been assigned to the Source Administrator authorization group.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

Procedure
1. From the SAP Fiori launchpad, log on to the GSTR2 application. 2. Enter the Tax Payer GSTIN, Financial Year, Financial Period. 3. Select Invoice Type. 4. Choose Go.
You can see the graphical representation of the invoices under the Matching Suggestion, Reconciliation Status, ITC Trend, and Missing in GSTN Trend tabs. 5. Now, select the appropriate option to execute the next steps according to the process flow. You have the following 4 process flow tiles available: Purchase Register (PR) [page 92]
Purchase Register provides the information of reconcilable and non-reconcilable inward invoices under GSTR2. Supplier Invoices [page 94] Supplier invoices provide the information of GSTR2B and GSTR2A. You can also pull the latest data with the pull functionality under GSTR2A and GSTR2B tabs. Reconciliation [page 95] Reconciliation provides detailed information on the reconciled invoices. You can reconcile the purchase register and the invoices uploaded by the supplier. Reports [page 97] You can generate the given reports based on the specific filters applied.
Parent topic: Returns [page 76]
Related Information
View GSTR9 Details [page 77] View GSTR3B Details [page 78] File or Save ITC-04 Returns [page 80] Reconcile ISD Invoices (GSTR6) [page 81] File a GSTR1 Return [page 84]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

10.2.6.1 Purchase Register (PR)
Purchase Register provides the information of reconcilable and non-reconcilable inward invoices under GSTR2.

Procedure
1. Choose Purchase Register (PR) in the GSTR2 application. 2. Select the Financial Period, Invoice Date, Invoice Type, Counter Party GSTIN, and Invoice Number. The
Invoice Number field supports multiple selections of invoice numbers. The system displays a list of invoices uploaded to the digital compliance service application under the Reconcilable Invoices and Non-Reconcilable Invoices tab.

Reconcilable Invoices

The Reconcilable Invoices tab contains details about all the registered invoices such as B2B, Credit and Debit Memo, Import of Goods, and Import of Goods from SEZ. Only registered invoices such as these are eligible for reconciliation.
1. To view the details, select an invoice. The system displays the invoice details in the subsequent screen. You have two kinds of data available here: Invoice Details and Counter Party Wise Summary
2. In the Invoice Details tab, you can view the entire history of the invoice, like the time of invoice upload from source system. Choose the Manage Manual Uploads button to upload new purchase invoices via Microsoft Excel. The system displays the list of uploads already completed. For uploads with status Uploaded with Errors, you can view the error log by clicking on the respective upload entry. The system displays the log on the right-side pane.
Start a new upload by choosing . In the Upload File dialog, select Browse to locate the file and then choose Upload.
The system creates a new entry under Uploads, with status New, on the Manage Manual Uploads screen. Choose Refresh. The system changes the status once the file is processed.
Note
To perform the Manual Upload action, the file size should not exceed 50 MB. The Generate CSV button inside the Excel file generates a .CSV file in the same location as the source .XLSM file thereby reducing the file size and you can upload the generated .CSV file for reconciliation.
SAP delivers a total of 6 additional fields that you can name as per your business requirements. To utilize these fields, choose the Maintain Custom Fields button.

In the Maintain Custom Field Label dialog box, choose description.

against the field key and enter the

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

Save your changes. 3. In the Counter Party Wise Summary tab, you can view the summary of the counter party, like invoice count
and taxable amount.

Non-Reconcilable Invoices

The Non-Reconcilable Invoices tab contains details about all the un-registered invoices such as B2B, Credit and Debit Memo, Refund Voucher, Import of Services, Advance Payment, ITC Reversal, and Advance Clearing.
1. To view the details, select an invoice. The system displays the invoice details in the subsequent screen.
2. In the Invoices tab, you can view the entire history of the invoice, like the time of invoice upload from source system. Choose the Manage Manual Uploads button to upload new purchase invoices via Microsoft Excel. The system displays the list of uploads already completed. For uploads with status Uploaded with Errors, you can view the error log by clicking on the respective upload entry. The system displays the log on the right-side pane.
Start a new upload by clicking on the icon. In the Upload File dialog, click Browse to locate the file and then choose Upload.
The system creates a new entry under Uploads, with status New, on the Manage Manual Uploads screen. Choose Refresh. The system changes the status once the file is processed.
Note
To perform the Manual Upload action, the file size should not exceed 50 MB. The Generate CSV button inside the Excel file generates a .CSV file in the same location as the source .XLSM file thereby reducing the file size and you can upload the generated .CSV file for reconciliation.
SAP delivers a total of 6 additional fields that you can name as per your business requirements. To utilize these fields, choose the Maintain Custom Fields button.

In the Maintain Custom Field Label dialog box, choose description.
Save your changes.

against the field key and enter the

Parent topic: Reconcile Inward Invoices (GSTR2) [page 90]

Related Information
Supplier Invoices [page 94] Reconciliation [page 95] Reports [page 97]
SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

10.2.6.2 Supplier Invoices
Supplier invoices provide the information of GSTR2B and GSTR2A. You can also pull the latest data with the pull functionality under GSTR2A and GSTR2B tabs.

Procedure
1. Choose Supplier Invoices in the GSTR2 application. 2. Select the Tax Payer GSTIN and Financial Year. Click Go.
You have 2 tabs available here: GSTR2B and GSTR2A.

GSTR2B
Note
There is a GSTR2B Pull option available at the bottom right of the application page, which helps you to fetch complete 2B statement based on 2 criteria: Tax Payer GSTIN - For a selected GSTIN, across all period, data is pulled. GSTR2B Statement Period - For all GSTIN, the selected period data is pulled.
GSTR2B provides eligible and ineligible Input Tax Credit for each month, similar to GSTR2A but remains constant for a period. GSTR2B is available to all the regular taxpayers. Every recipient can generate it on the basis of the GSTR-1 furnished by their suppliers. 1. Choose GSTR2B and select the GSTR2B Statement Period in addition to the previous selections.
The system displays the list of invoices, ITC summary and counter party summary under the Invoice Details, ITC Summary, and Counter Party Wise Summary tabs respectively. You can click on an invoice to see its details.

GSTR2A
Note
There is a GSTR2A Pull option available at the bottom right of the application page, which helps you to fetch complete 2A statement based on the following 2 criteria: Tax Payer GSTIN - For a selected GSTIN, across all period, data is pulled. Financial Period - For all GSTIN, the selected period data is pulled. You have additional filters available to refine your search like from date, counter party GSTIN, invoice types and so on.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

GSTR2A is a purchase-related tax return, that is, automatically generated for each business by the GST portal. When a seller files GSTR-1, the information is captured in GSTR2A. It takes information of goods and/or services, which have been purchased in a given month from the seller's GSTR-1. 1. Choose GSTR2A and select the Financial Period and Invoice Date in addition to the previous selections.
There are several other filters available like Invoice Type, Invoice Number and so on. The Invoice Number field supports multiple selections of invoices. The system displays the list of invoices and counter party summary under the Invoice Details, and Counter Party Wise Summary tabs respectively. You can choose any invoice to see its details.
Note
The Counter Party Filing Status button redirects you to the Counter Party Filing Status application, where you can view the filing status for relevant return types and financial periods.
Parent topic: Reconcile Inward Invoices (GSTR2) [page 90]

Related Information
Purchase Register (PR) [page 92] Reconciliation [page 95] Reports [page 97]
10.2.6.3 Reconciliation
Reconciliation provides detailed information on the reconciled invoices. You can reconcile the purchase register and the invoices uploaded by the supplier.

Procedure
1. Choose Reconciliation in the GSTR2 application. 2. The screen displays the invoice data for Tax Payer GSTIN and Tax period chosen earlier in the GSTR2 home
page. You can filter the invoices based onReconciliation Type, Invoice Type, Reconciliation Status, Counter Party GSTIN, Financial Year, Invoice Number, and Source.
Note
You can use the Source field to select GSTR2B, GSTR2A, or GSTR2 data as the source.
The reconcile inward invoices screen lists the invoices under the Reconciliation Type Summary, Reconciled Invoice Details and Amended Original Invoice Details tab.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

Note
You can use the Recon Settings option at the bottom left-hand corner to perform actions such as the reconciliation action settings and tolerance level settings for the taxable amount and tax value.
Also, you can use the Run Reconciliation button to check the details of the reconciliation ran for any particular GSTIN, Financial Year, and the Invoice Type. In order to perform reconciliation, choose the appropriate filter and select RUN on the Run Reconciliation screen. Choose refresh to see the request status and the last create date of the latest entry.

The following table details the reconciliation types and subtypes:

Reconciliation Type Complete Match (CM) Partial Match (PM) Probable Match (PRBM)
Missing in GSTN System (MIG) Missing in Source System (MIS)

3. Choose Go. The system displays all the details of the list of selected invoices under the GSTR2B, GSTR2A, and Proposed GSTR3B tabs.

GSTR2B
GSTR2B is an auto-drafted ITC statement, which is generated for every registered GSTIN on the basis of their respective GSTR-1 filing. It is a static information, generated on the 12th of every month. The system displays the information pulled under GSTR2B statement in the following three tabs: Reconciliation Type Summary Reconciled Invoice Details Amended Original Invoice Details Since 2B captures the information, the source filter tab can be used to select the source type for the information displayed in the consequent screen.

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

GSTR2A
GSTR2A is a purchase-related tax return, that is, automatically generated for each business by the GST portal. When a seller files GSTR-1, the information is captured in GSTR2A. It takes information of goods and/or services, which have been purchased in a given month from the seller's GSTR-1. The system displays the information pulled under GSTR2B statement in the following three tabs: Reconciliation Type Summary Reconciled Invoice Details Amended Original Invoice Details

Proposed GSTR3B
Proposed GSTR3B is used to give an overview of the information to be filed under the GSTR3B form for the Reporting Period selected in the filters. There are four parts of the data overview: 1. ITC Available (whether in full or part) 2. ITC Reversed 3. Net ITC Available(A-B) 4. Ineligible ITC The leading section depicts the provisional credit.
Parent topic: Reconcile Inward Invoices (GSTR2) [page 90]

Related Information
Purchase Register (PR) [page 92] Supplier Invoices [page 94] Reports [page 97]

10.2.6.4 Reports
You can generate the given reports based on the specific filters applied. You can generate the following types of reports: Tax Payer/Counter Party Report: You can filter the reports based on the Tax Payer GSTIN, Counter Party
GSTIN, Reconciliation Type, Financial Year, and Tax Period. Tax Payer PAN Report: You can filter the reports based on the Tax Payer PAN, Counter Party GSTIN,
Reconciliation Type, Financial Year, and Tax Period.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

Counter Party PAN Report: You can filter the reports based on the Tax Payer GSTIN, Counter Party PAN, Reconciliation Type, Financial Year, and Tax Period.
Tax Payer Mismatch: You can filter the reports based on the Tax Payer GSTIN, Counter Party GSTIN, Financial Year, Tax Period, and Invoice Type.
Comprehensive Report: You can filter the reports based on the Tax Payer GSTIN, Counter Party PAN and GSTIN, Invoice Type, Financial Year, Tax Period, and Request ID.
Parent topic: Reconcile Inward Invoices (GSTR2) [page 90]
Related Information
Purchase Register (PR) [page 92] Supplier Invoices [page 94] Reconciliation [page 95]

10.3 Utilities

Manage Inward Invoices [page 99] You can use this app to keep track of the inward supply invoices uploaded to the digital compliance service application, upload new invoices via Microsoft Excel, and reconcile invoices.
Manage Outward Invoices [page 100] You can use this app to monitor the outward supply invoices uploaded to the digital compliance service application, and upload new invoices via Microsoft Excel.
GSP Communications [page 101] The GSP Communications app allows you to manage different GST Suvidha Providers (GSPs), set the priority of a GSP, keep track of the application programming interface (API) usage for the respective GSP, and generate reports on the API usage.
Digital Compliance Service Health Check [page 102] You can use the Health Check app before you proceed with the digital compliance service applications. The app ensures that all the configurations have been made properly, so that the digital compliance service applications function correctly.
Counterparty Filing Status [page 103] The Counterparty Filing Status application is now obsolete. You can use GSTIN Utilities application to view the filing status of the GSTIN for the taxpayer as well as the counterparty.
GSTIN Utilities [page 104] GSTIN is a Goods and Services Tax Identification Number, which is assigned to each person registered under GST in India. This application helps you fetch the GSTIN details from the GSTN portal. You can see the filing status of the GSTIN for the taxpayer as well as the counterparty.
GSTN Reports [page 105]

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

GSTN reports provide you the information on Tax liability and ITC comparison. GSTN auto calculates the tax payer liability based on the tax payers filed GSTR1 and tax payer eligible ITC based on suppliers filed GSTR1. The Excel report provides comparison between the data auto calculated by GSTN and the data filed by Tax payer as part of GSTR3B.
Parent topic: Applications [page 67]

Related Information
Configurations [page 67] Returns [page 76]

10.3.1 Manage Inward Invoices
You can use this app to keep track of the inward supply invoices uploaded to the digital compliance service application, upload new invoices via Microsoft Excel, and reconcile invoices.

Context
You have been assigned to the Source Administrator authorization group.

Procedure
1. From the Fiori Launchpad, log on to the Manage Inward Invoices app.
The system displays a list of invoices uploaded to the digital compliance service application. 2. To view the details, select an invoice.
The system displays the invoice details in the subsequent screen. 3. In the Invoice History/Details tab, you can view the entire history of the invoice like the time of invoice
upload from source system, invoice upload to GSTN and so on. 4. Choose the Manage Manual Uploads button to upload new invoices via Microsoft Excel.
The system displays the list of uploads already completed. For uploads with status Uploaded with Errors, you can view the error log by clicking on the respective upload entry. The system displays the log on the right-side pane. 5. Start a new upload by clicking on the button. 6. In the Upload File dialog, click Browse to locate the file and then choose Upload.
The system creates a new entry under Uploads, with status New, on the Manage Manual Uploads screen.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

7. Choose Refresh. The system changes the status once the file is processed. 8. SAP delivers a total of 6 additional fields that you can name as per your business requirements. To utilize
these fields, choose the Maintain Custom Fields button. 9. In the Maintain Custom Field Label dialog box, choose against the field key and enter the description. 10. Save your changes.
The system enables the field(s) across all the invoices.
Task overview: Utilities [page 98]
Related Information
Manage Outward Invoices [page 100] GSP Communications [page 101] Digital Compliance Service Health Check [page 102] Counterparty Filing Status [page 103] GSTIN Utilities [page 104] GSTN Reports [page 105]
10.3.2 Manage Outward Invoices
You can use this app to monitor the outward supply invoices uploaded to the digital compliance service application, and upload new invoices via Microsoft Excel.
Context
You have been assigned to the Source Administrator authorization group.
Note
GSTR1 Summary includes section wise summary and rate wise summary for a relevant GSTIN and financial period.

Procedure
1. From the SAP Fiori Launchpad, log on to the Manage Outward Invoices app. The system displays a list of invoices uploaded to the digital compliance service application.

100

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

2. To view the details and history, select an invoice. The system displays these details on the right-side pane.
3. In the Invoice History tab, you can view the entire history of the invoice like the time of invoice upload from source system, invoice upload to GSTN and so on.
4. Choose Manage Manual Uploads button to upload new invoices via Microsoft Excel. The system displays the list of uploads already completed. For uploads with status Uploaded with Errors, you can view the error log by clicking on the respective upload entry. The system displays the log on the right-side pane.
5. Start a new upload by clicking on the button. 6. In the Upload File dialog, choose Browse to locate the file and then choose Upload.
The system creates a new entry under Uploads, with status New, on the Manage Manual Uploads screen. 7. Choose Refresh.
The system changes the status once the file is processed.
Task overview: Utilities [page 98]
Related Information
Manage Inward Invoices [page 99] GSP Communications [page 101] Digital Compliance Service Health Check [page 102] Counterparty Filing Status [page 103] GSTIN Utilities [page 104] GSTN Reports [page 105]
10.3.3 GSP Communications
The GSP Communications app allows you to manage different GST Suvidha Providers (GSPs), set the priority of a GSP, keep track of the application programming interface (API) usage for the respective GSP, and generate reports on the API usage.
Prerequisites
You have performed the following settings: Adapted/installed the integration flow of the respective GSP Created a destination for the integration flow deployed in the SAP BTP cockpit

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

101

Parent topic: Utilities [page 98]
Related Information
Manage Inward Invoices [page 99] Manage Outward Invoices [page 100] Digital Compliance Service Health Check [page 102] Counterparty Filing Status [page 103] GSTIN Utilities [page 104] GSTN Reports [page 105]
10.3.4 Digital Compliance Service Health Check
You can use the Health Check app before you proceed with the digital compliance service applications. The app ensures that all the configurations have been made properly, so that the digital compliance service applications function correctly. You must run the app for each digital compliance service application, and the health check status for each application must be Connection was established successfully.
Prerequisites
You have made the following settings: Configured the database for each digital compliance service application. All the digital compliance service applications are in Started state. Maintained all destinations as per the Installation and Configuration Guide attached to the SAP Note
2460667 .
Features
The app makes various checks for the following applications: ACRS Core DCS Communication GSTR-1 GSTR-2 MDC ITC-04

102

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

Parent topic: Utilities [page 98]
Related Information
Manage Inward Invoices [page 99] Manage Outward Invoices [page 100] GSP Communications [page 101] Counterparty Filing Status [page 103] GSTIN Utilities [page 104] GSTN Reports [page 105]
10.3.5 Counterparty Filing Status
The Counterparty Filing Status application is now obsolete. You can use GSTIN Utilities application to view the filing status of the GSTIN for the taxpayer as well as the counterparty.
Parent topic: Utilities [page 98]
Related Information
Manage Inward Invoices [page 99] Manage Outward Invoices [page 100] GSP Communications [page 101] Digital Compliance Service Health Check [page 102] GSTIN Utilities [page 104] GSTN Reports [page 105] GSTIN Utilities [page 104]

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

103

10.3.6 GSTIN Utilities
GSTIN is a Goods and Services Tax Identification Number, which is assigned to each person registered under GST in India. This application helps you fetch the GSTIN details from the GSTN portal. You can see the filing status of the GSTIN for the taxpayer as well as the counterparty.
Tax Payer
The details you see under Taxpayer GSTIN, belongs to your company. Follow the steps below: 1. Select the Taxpayer GSTIN and Financial year. 2. Choose Go to view its filing status on a monthly basis. Under the tab Filing Status, you can see the corresponding details for return type GSTR1 and GSTR3B. The details visible are of the last pull from GSTN. To get the latest status, select Get Filing Status at the bottom right-hand corner of the screen. To know when the last pull was initiated, hover the cursor on the Taxpayer GSTIN.
Note
When you choose Go, the data is fetched from within the DCS application and when you choose Get Filing Status, the data is pulled from the GSTN portal and refreshed in the DCS application.

Counterparty
Similar to the Tax Payer tab, the Counterparty tab provides the details on filing status along with the GSTIN details. You only need to select either the Counterparty GSTIN or the Taxpayer GSTIN along with the Financial Year as the details displayed corresponds to both. If you do not select either the Counterparty GSTIN or the Taxpayer GSTIN, then the table lists the details of all the GSTINs. Under the GSTIN Details tab, Vendor Region and Vendor Code are based on your source ERP system and is populated when purchase invoices are sent from the source ERP system.
The Counterparty filing status is based on the below sources: 1. GSTR2A data pull 2. GSTR2B data pull 3. GSTIN return filing tracking API (Get Filing Status)
Note
To pull the GSTINs return filing status of all the suppliers associated with a particular Tax Payer GSTIN, select the Tax Payer GSTIN and choose Get Filing Status. This will initiate the filing status pull of all supplier GSTINs associated to the selected tax payer.
Note
You can manually enter up to 50 ad-hoc counterparty GSTINs under the Counterparty GSTIN field to fetch its details from the GSTIN even though you do not see the GSTIN in the list of available options.

104

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

Parent topic: Utilities [page 98]

Related Information
Manage Inward Invoices [page 99] Manage Outward Invoices [page 100] GSP Communications [page 101] Digital Compliance Service Health Check [page 102] Counterparty Filing Status [page 103] GSTN Reports [page 105]
10.3.7 GSTN Reports
GSTN reports provide you the information on Tax liability and ITC comparison. GSTN auto calculates the tax payer liability based on the tax payers filed GSTR1 and tax payer eligible ITC based on suppliers filed GSTR1. The Excel report provides comparison between the data auto calculated by GSTN and the data filed by Tax payer as part of GSTR3B.

Procedure
Follow the steps to generate GSTN reports:
1. From the SAP Fiori Launchpad, log on to the GSTN Reports app under Utilities. 2. Select a relevant time period from the Financial Year drop down menu to display a list of Tax Payer GSTIN
entries created. You can also search specific entries for report generation in the search bar provided at the top right-hand corner of the screen. 3. Choose Go. The system displays all relevant Tax Payer GSTIN entries with the Status and Report column.
Note
All new Tax Payer GSTIN entries, where the Pull from GSTN has not been performed is in the Not Initiated status.
4. Select the check box available for Tax Payer GSTIN column header to check the complete list. You also have an option to do selective pulls by checking the check box available beside each entry.
5. Choose Pull from GSTN at the bottom right-hand corner of the screen. You see a message on the screen GSTN report generation initiated successfully. This pulls the data from GSTN and calculates the following 2 values: Tax payer liability based on the GSTR1 filed by tax payers. Tax payer eligible ITC based GSTR1 filed by suppliers.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

PUBLIC

105

Note
A report can be generated only on the data available from July 2020 onwards.
6. After initiating the pull, select any Tax Payer GSTIN entry from the list to check the Month-wise status pulled from GSTN. A panel slides from the right side displaying Month, Section, Status, Last Pulled Time, and Error Description for each month of the selected financial period. The status changes from New to either Success or Error in the process. You have 5 types of status displayed in the left panel or the initial screen: Not Initiated: Initial state, when the pull is not initiated. Failed: After the pull, if all 24 entries fail . Partial: After the pull, if few entries are successfully initiated and others fail. In Process: When the pull is in process. Completed: After the pull, if all 24 entries are successful.
7. For all Partial and Completed pulls, an Excel report is generated which includes, the comparison result of the data auto calculated by GSTN, and the data filed by tax payer as part of GSTR3B. Choose the highlighted download icon in the Report column to download the comparison report generated.
The Excel report includes 7 sheets, mainly Overview, Comparison Summary, Tax liability, Reverse charge, Export and SEZ, ITC(Other than IMPG), and ITC(IMPG).
Parent topic: Utilities [page 98]
Related Information
Manage Inward Invoices [page 99] Manage Outward Invoices [page 100] GSP Communications [page 101] Digital Compliance Service Health Check [page 102] Counterparty Filing Status [page 103] GSTIN Utilities [page 104]

106

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment Applications

11 FAQ

Use this guide to get answers to some frequently asked questions on the various phases of SAP Localization Hub, Digital Compliance Services for India. The questions are grouped together under the following topics: eDocument Framework [page 107] DCS: Installation and Usage [page 114] Users, Roles and Authorization Management [page 116] DCS: Connecting to GSP via SAP Cloud Integration [page 118] GSTR1: Save [page 119] GSTR: Submit and File [page 121]
Previous: Applications [page 67]
11.1 eDocument Framework

Installation and Implementation issues
1. How to create eDocuments for documents posted before implementing the eDocument framework? Solution: Use the Change button in the edoc_cockpit. Enter the company code, source document number(s) and check the Not yet Created check box in the dialog screen. Execute and create the selected documents. eDocument would be created.
Note
If the volume of the document is huge, then see this document .
Generate section after section i.e. first billing documents, then Accounting documents etc. Also mention the date in the upper section instead of mentioning in the Restriction on the eDocument Criteria tab. 2. How to create eDocuments for Invoices created before Go-Live See the document eDocument creation for Invoices in Background.docx and follow the steps mentioned in it. 3. To display the eDocuments in cockpit which are in CREATED/FAILED/SENT state. You can filter documents with eDoc status 0002: In process 0003: Action Required 4. How to send a batch of eDocuments from ECC to DCS

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

107

You can create a summary of the documents using the transaction edoc_in_summary. The limit is 999 eDocuments per summary.
5. The error Class CL_ASP_CONNECTOR_HELPER_IN does not exist is thrown . Solution: Check if the following notes are implemented successfully:
2458714 : eDocument India: Pre-requisites for Note 2443144
2443144 : eDocument India: GST mapping
6. Unable to create eDocuments. Error says Implement the Interface Connector. Solution: Create an implementation of BAdI EDOC_INTERFACE_CONNECTOR for the following filter values:
Interface Type: CUSTOM
Country: IN
GENERIC_FILTER: IN_INV Create an implementation of BAdI EDOC_ADAPTOR for filter value country: IN.
7. Document posted using standard FI transactions but unable to see eDocument in edoc_cockpit. Solution: Run the FIBF tcode, under the Setting menu, select Identification -> SAP Application. the check box should be selected for application 'EDOC'.
8. Skipping table 'EDO*' because of delivery class or Table 'EDO*' does not exist. Solution: Check if you have implemented all the framework notes and their manual steps correctly. Such errors could be avoided if TCI implementation was used. This error would only arise if the framework tables are not created correctly. Check if the report NOTE_2293306_POST_IMPL has been executed successfully.
9. The status of the Note 2465014 says cannot be implemented. Solution: The note 2465014 is a consulting note which has certain manual steps to be followed. It does not have any correction instructions to be implemented.
10. In the edoc_cockpit transaction, the status column is blank. Solution: Check if the BC sets, EDOC_IN_METASTATUS and EDOC_IN_SUMM_METASTATUS are activated. If not, activate using the t-code SCPR20.

RFC Connection related errors
1. Connection refused or host Unknown error. Solution: If you are using any proxy, then maintain proxy details in RFC connection for all the RFC destinations. Add the Baltimore, Verizon, AP1 or Hana certificates in STRUST. Select the same SSL certificate in logon & security tab while creating RFC. In addition to this, install the regionspecific certificate if required. For more information, see this video .
2. SSL Handshake Error. Solution: Verify if the Baltimore, Verizon, AP1 and Hana certificates are added in STRUST. These certificates should not be tampered.

108

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

3. 403 - Unauthorized error when submitting an eDocument. Solution: Verify if you have generated the OAuth Client ID in the DCS application following the Configuration guide attached to note 2460667 . S-user or P-user ID should not be used for RFC destinations. The oauth_client_<client ID> should be assigned with the Source Admin role in DCS application. The same Client ID should be maintained in the RFC token destinations. This would enable you to send documents to DCS. For more information, see this video .
4. Token error when using a different account (Dev to Qualtiy/Production). Solution: Generate a new client ID for this account and maintain the Source Admin role in DCS application. The same Client ID should be maintained in the RFC token destinations. This would enable you to send documents to DCS.
5. GSTR1/GSTR2 token error but the connection test was successful. Solution: The error is an indication of Oauth token not being generated. Verify your client ID and secret. One of the common issues faced by customer is when copy-pasting the password, there are additional spaces saved and an error is thrown. Press Enter Key after entering the user ID and password.
6. Unknown Host (NIE_HOST_UNKNOWN) error while doing a connection test in SM59. Ensure to maintain the IP address (Host name) of the SAP CP Account in the host file to resolve this error.

Sending eDocuments from ECC to DCS
1. How to check Application log? Solution: If the eDocument is created and submitted. System shows Transaction ID Received. Select the eDocument and click Status to get the status. The system shows Failed to Upload to DCS. Steps to open the error through application log 1. Goto transaction /edoc_cockpit. Select the eDocument which has error. 2. Click Goto and select Display Application Log Further, you can see the Error Log report once installing the following Notes: 2638685 - eDocument India: Prerequisite note for 2638134 2638134 - eDocument India:eInvoice error log report Transaction : /nEDOC_IN_LOG_REPORT
2. How to export request and response files from edoc_cockpit? Solution: If you want to check the request or response received from DCS, follow the below steps: 1. Click History. 2. Select the entry with the File Name with extension .json and .xml which you want to download. Click on export file.
Note
For GSTR1 Validation list refer to the excel
For GSTR2 Validation list refer to the excel

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

109

3. The document status is "Sending Requested" and the error says "GSTIN is initial". Solution: The tax number 3 field is for CTIN not for GSTIN. You must maintain the GSTIN number to your business place. Correct the STCD3 field data in view J_1BBRANCV for the respective business place.
4. The document status is "Sending Requested" and we get the error "TAXBASE Amount could not be determined". Solution: TAXPS is a mandatory field, which has to be maintained at line item level. Check if you have implemented the below notes and followed all the manual steps mentioned.
2448045 - GST India: Taxes should be <Line Item Wise>
2517220 - GST India: TAXPS/TXGRP Not Updated for Revenue Line
5. The document status is " eDocument has errors" and we get the error "Place of Supply is Initial". Solution: This error is returned by DCS application if the data mapped is incorrect and basic validation failed. Verify if the State Codes maintained in view 'J_1ISTATECDM' are numeric codes and not character.
6. The document status is " eDocument has errors " and we get the error message "CTIN Invalid/ Required field". Solution: The CTIN field is filled from the data maintained in STCD3 field of the customer master. This has to be in the format of GSTIN number.
7. The document status is "eDocument has errors" and we get the error message "Unit Quantity Measure(UQC) is not filled for line item". Solution: Maintain the entries in view 'EDOINUQCV' for the unit quantity measure.
8. The document status is "eDocument has errors" and getting the error message "HSN_SAC is Initial". Solution: Verify if the Material Master/ Service master data for the line item has been maintained.
9. The document status is " DCS Integration Error " and the error reads "Token is not generated". Solution: Verify if the Client ID and secret generated for the application is correct. For more information, refer the section RFC Connection related errors.
10. The document status is "Failed to Upload to DCS" and the error is "Invalid Tax Combination error". Solution: An invoice document cannot be created with both CGST and IGST. It could be either CGST and SGST or IGST.
11. Error while submitting a credit note or debit note created using FB75. Submit the original Invoice first to DCS and then submit the Credit/Debit Note.
12. After creating the manual FI postings and while submitting the eDocument, get the error "Unit of Measure (UQC) and Quantity is initial". Solution: When you are posting manual FI invoice, you should enable the fields Quantity (BSEG-MENGE) and Unit of Measure (BSEG-MEINS) to enter data. These two fields are mandatory if the HSN_SAC code is of type 'Goods'. If the documents are already posted in your system, use the BAdI methods in EDOC_IN_MAP to fill the data as the item level. The methods are different for GSTR1 (SD, FI) and GSTR2 (MM, FI). Please maintain the implementations accordingly.
13. Getting the error "Export type is initial" while submitting the eDocument.

110

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

Solution: In standard mapping, system uses the tax category JOIG from customer tax classification to identify whether the customer belongs to "Deemed Export" or "SEZ Developer". In standard recommendation, value '2' of JOIG is for SEZ and '3' of JOIG is for Deemed export. If you are not using the tax category JOIG or even if you are using JOIG and are not using the above values to determine the SEZ and Deemed export then you should do the enhancement using the BAdI EDOC_IN_MAP methods FILL_SD_HEADER_GSTR1(for SD billing document), FILL_FI_HEADER_GSTR1(for Manual FI Customer invoice) to fill the field "EXPTYPE" accordingly. The following are the values that you can pass to EXPTYPE field:
R: Regular or normal invoices
DE: Deemed export
SEWP: SEZ with taxes greater than zero
SEWOP: SEZ without taxes(where tax amounts are zero)
14. We are not using the ODN solution of India localization. We are getting the error "Invnum is Invalid/ Required field". Solution: If the Reference field is initial (XBLNR), we use the document number for ODN. If the reference field is filled with some invalid data, you have to use the implementation of EDOCUMENT_IN BAdI's FILL_ADDITIONAL_DATA method to modify the value of invnum field in the cs_add_info structure. The same BAdI method should be used to store and display additional fields in the eDocument cockpit.
15. How to restrict creation of eDocuments for a source document. Solution: The IS_RELEVANT method of the EDOC_ADAPTOR BAdI has to be implemented to restrict creation of eDocuments. For GSTR2, there are mandatory restrictions. So, call the INCLUDE EDOC_IN_RESTRICT_EDOC_GSTR2 in this method. Similar logic can be implemented to restrict creation of eDocuments according to their scenarios.
16. We are getting the error 'Process could not be determined'. Solution: This error message is raised when the system is unable to identify any of the section (example B2B, B2C, export etc.). The issue is caused when you are not maintaining Vendor GSTN (field STCD3) or no reverse charge tax conditions are available. Based on your requirement maintain either of one.
17. How Vendor Classification is used in GSTR2? Solution: Vendor classification are used in three scenarios:
To identify whether the invoice belongs to B2B Unregistered vendor (Process could not be determined error): In standard mapping if ven_class is `0', it will be considered as unregistered vendor. If you are using a different value, the process should be modified in the BAdI method DETERMINE_FI_PROCESS_GSTR2 for FI invoice and DETERMINE_MM_ PROCESS_GSTR2 for MM invoice in EDOC_IN_MAP BAdI as 1.
To identify SEZ (Special Economic Zone) vendor: In standard mapping if ven_class is 2, then the vendor will be considered as SEZ vendor. If you are using a different value, then two sections will be affected which should be filled using the BAdI method `FILL_MM_HEADER_GSTR2' for MM invoices and `FILL_FI_HEADER_GSTR2' for FI invoices. For B2B section, IMPTYPE field should be filled as the following:
R: Regular or normal invoices
SEWP: SEZ with taxes greater than zero
SEWOP: SEZ without taxes (where tax amounts are zero) For IMPG section, ISSEZ field should be filled as:

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

111

Y: SEZ
N: Other scenarios
Used in the restriction of eDocument creation when vendor classification is SEZ and Import conditions are maintained.
18. How Bill of entry number and Port Code will be filled for Import of Goods (IMPG) section? Solution: For imports customs invoice, first 6 characters of the XBLNR field will be filled as Port Code and the remaining number be considered as Bill of Entry number. If you are not capturing in the same format, you must use BAdI EDOCUMENT_IN's FILL_ADDITIONAL_INFO method to fill the bill of entry number and update the invoice number. EDOC_IN_MAP item level methods should be used to fill the Port Code. Standard mapping sample: If XBLNR: 3210936104234, PORTCODE: 321093 and BOENUM: 6104234. Invoice number field in edoc_cockpit will have 6104 and same will the invoice number in DCS application.
19. What data to be sent for Import of Goods Scenario and how to restrict eDocument creation for other import scenarios? Solution: eDocument will be created if the GST partner (bseg-gst_part or rbkp-gst_part) is outside India or SEZ vendor. We check the import related condition type (condition type should be assigned to import related condition name in the table J_1igexcdefn) in the document. In Customs invoice, for field GST_PART if you are maintaining customs vendor (In standard it will be defaulted with vendor from whom you are importing goods), then you need to restrict the eDocument creation for main vendor invoice and create the eDocument only for customs invoice since you need to report only customs invoice (Bill of entry) to GSTN. If you capture the customs invoice details and vendor invoice details separately in the both SEZ and normal imports scenarios, then eDocument will be created for only customs invoice and this will be reported to GSTN. But if you are capturing the customs and vendor invoice details in the same invoice in case of SEZ scenario, eDocument will be created, but during mapping from edoc to DCS you should make sure that you are sending only customs invoice details like bill of entry number, port code, invoice amount, taxable amount, tax amount for this eDocument, not the whole details of invoice since GSTN asked only for customs invoice details in case of imports. You need to adjust the mentioned fields and other relevant fields for this scenario using the BAdI EDOC_IN_MAP.

Mapping, ODN, Other Business/Functional Related questions
1. For UOM configuration, we have updated in material master then why again we are mapping here in table EDOINUQC. Solution: UOM used internally and for purpose of GSTR reporting can be different. We can't make it mandatory to use same code in material master as specified by GSTN. Hence a separate mapping table is delivered. If the same code is used, just maintain 1:1 mapping in this table.
2. While doing a vendor credit memo, customer should pay taxes to vendor so in that case the Accounting doc type RE which will comes under GSTR1 or GSTR2. Should it be assigned for IN_INV / IN_PINV or for both. Solution: Vendor Credit/debit memo are supposed to add/reduce your input tax credit in GSTR2. They come under GSTR2 clearly mentioned in formats. It should be assigned to IN_PINV

112

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

3. In eDocument India Tax code Mapping for GST in case of Import and Domestic, how to do the configuration in SM30 EDOINTXCODEMAPV and should it be assigned to the output tax code. Solution: The table is used for mapping. To identify a transaction if it is `nil rated' or `exempted' or `non-GST' supply/ purchase etc. This is relevant for both output as well as input tax codes. You can specify the combination of procedure and tax code to identify these scenarios in mapping. If done properly, standard mappings will work to identify these sections as per requirement to be reported in GSTRs.
4. 4. In case of Delivery doc type mapping to eDocument, only Proforma Inv case to be considered and what is the impact. Also to confirm if Sub-Contracting delivery type to be assigned or not. Solution: So far, only invoices (with accounting) are required to be reported in GSTR forms. Subcontracting challans (created as proforma) or delivery documents are not required to be reported in GSTR forms. There is only number range requirement for few such documents which has to be filled in manually and will be editable in GSTR1. No eDocument process is required for such documents.
5. For Self-Invoice, does it come under GSTR1 or GSTR2? Solution: Self invoices (purchase from unregistered vendors) are realized in MIRO itself in ECC. They are part of GSTR2 and should be mapped to GSTR2 for e-Document purpose.
6. Import Goods /Services, tax code should be same or different? Solution: They must be different and should be configured in the configuration table as explained in question 3. Otherwise, standard mappings will not work and BAdIs will have to be implemented to override standard mapping.
Sending Old Invoices from ECC to DCS without mandatory fields
1. Mandatory fields in the documents such as TAXPS, Tax Base field have not been filled for Old Invoices Issue: Mandatory Compliance Notes/Customizations recommended by SAP have not been installed earlier. Option 1: You can use Excel to upload such documents to DCS and manage subsequent process in DCS. The status of such documents will not be available in ECC. Option 2: You should use the methods of BAdI EDOC_IN_MAP to fill missing fields like TAXPS. For more information on TAXPS field, see here .
The BAdI EDOC_IN_MAP has specific methods for GSTR1 (SD, FI) and GSTR2 (MM, FI). The corresponding methods should be used to fill all item related data which is missing in the standard tables. When using these methods, tax base and tax amount details should be filledin correctly to avoid inconsistency in the data.
This approach is suggested for documents which have been posted already. For new documents, follow the steps in the document "EdocMappingConfig.pdf" attached to Note 2465014 .

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

113

11.2 DCS: Installation and Usage

General
Note
The recommended browser for DCS is Google Chrome. Also ensure to disable the popup blocker.
1. Where can I get more information about REST API and Excel Upload features? To download the excel templates, go to Manage Outward Supply/ Manage Inward Supply and click Manage Manual Uploads button. Here click on Download Template. For general instructions on uploading the excel using manual upload, see the question 6 below. For information on REST API Documentation, see here .
2. Where can I get more information about GSPs who are working with SAP for their integration certification? For the list of GSPs working with SAP for integration certificate, see the Note 2512413 .
3. Can we connect multiple ECC tenants to single DCS instance? Yes. RFC connections must be maintained in multiple ECC instances to point to the same DCS instance.
4. Can we connect a non-SAP source system and SAP ECC to single DCS instance? Yes
5. What is the range of dynamic IP addresses used by the Cloud platform accounts? For information on the range of dynamic IP addresses, see SAP Note 2418879 . You can add this the range of dynamic IP addresses to your firewalls.
6. General Instructions for Uploading the Excel using manual upload.
Note
Add/Edit data only in the excel template provided by DCS.
Create new rows by copying the existing sample row in each section. This is a protected workbook. Do not change any settings. Drop-downs are provided where ever possible for ease of use. Refer the table for required fields and definition of each field. Data must be filled only in the required sections and the rest of the sections must be blank. GSTIN of supplier/E-commerce should be a valid one. State code of supplier GSTIN and E-Commerce
GSTIN should be the same. Amount should be only up to 2 decimal digits Ensure the filling of excel is strictly as per sample data to avoid errors. Master data sheet provides the inputs allowed in the mentioned data field. Inputs in the master data
sheet is used for the drop-down lists in the worksheets. For invoices containing multiple line items, invoice level details like GSTIN/UIN, Invoice Number,
Invoice Date and Place of Supply should be repeated for all the line items All date fields should be specified in dd-mm-yyyy format. The worksheets have some data as example. Delete the sample data from all the worksheets before
using.

114

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

Ensure that there are no stray entries in any cell of the sheets other than return related declaration under the indicated column headers.
This excel workbook template works best with Microsoft Excel 2007 and above. For GSTR1 Validation list, refer to the excel . For GSTR2 Validation list, refer to the excel . .

Installation
1. neo deploy --host ..... command gives the error "Multiple properties files found [?-user, Snnnnnnnnn]. Provide only one properties file" This happens because of a <space> in the --source parameter. Specify the --source parameter within double quotes (").
2. Which Java Tomcat SDK to be used for deployment? Java Web Tomcat 8 from https://tools.hana.ondemand.com/
3. While create a DB user (example GSTR1DB), getting the error "Cannot use duplicate schema name". A detailed explanation on resolving this issue can be found here .

Using DCS Application
1. While opening any of the Fiori App, getting an "Error - Http status 404" This issue arises when the Java application is not started or is an older version. Verify the following: Java application should be deployed using Tomcat 8 SDK only. If the deployment was done using any other SDK, then redo the deployment using Tomcat 8 SDK and restart the application. Check if the latest java application is deployed. You can see the version details in the release notes of the latest DCS version here . Clear your browser cache or open the app in the Incognito mode.
2. GSTN throws following error while Filing - "Data used for signing is different from uploaded summary data" This is an issue from GSTN side. This message is wrongly sent by GSTN even if the request for filing is correct. It is communicated by GSTN that the filing of GSTR1 via APIs is not working in production. To be sure, you can refer to the 'sign data validator' provided by GSTN here . As a fall back option, you can always FILE from the tax payer Portal (GSTN portal) under the Returns Dashboard after you have logged in. If you FILE via the Tax payer portal, you can come back to the DCS app and update the status of the FILE activity for that period manually to 'Content Accepted by Government'.
3. We get status code = "ER" from GSTN. It shows "error_cd":"RET191106". It indicates schema validation error. How to do JSON Schema Validation? 1. Download the GSTN JSON schema from the GST website. 2. Download the Request JSON from the DCS application. (Use Google Chrome; in other browsers the JSON file may not get downloaded; Disable popup blocker). 3. Use a Jason schema validator to do a JSON format validation.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

115

11.3 Users, Roles and Authorization Management

1. Which S user ID do we need to login to SAP BTP? Solution: The default S user ID is based on IT contact person mentioned in the order form. The details of which are mentioned in the welcome e-mail. In case if the default IT contact person is not available, then refer to this Wiki for assigning another user as Admin.
Note
Use S user ID to login to cockpit rather than e-mail as your mail might be linked to multiple S user and that would cause an issue.
2. How to request a new S-user ID for SAP Support Portal /SAP Service Marketplace/ SAP DCS application? Solution: Contact your organization User/ System administrator and ask them to create a S user for you. Admins can create user by going to this link www. service. sap.com/user-admin and then go to Data Administration tab -> Request New Users.
3. What If there is an issue with login and access either for user or User/ System administrator? Solution: To reset the password, follow this link . If your user is locked or if you can't access the cockpit despite resetting the password, then send an e-mail from your official ID to service@sap.com for further assistance. You can also use the helpline on https://service.sap.com/call1sap and choose option 1 for getting support on S user ID.
Note
Due to security reasons, the on-call support team do not perform password reset procedures instead you'll be guided on how you can reset the password yourself.
4. How to assign Cloud platform roles to members? You can assign users to respective cloud platform roles like for development, deployment and accessing portal. For more information on managing members and assigning authorizations, follow the links below: Managing Members in the Neo Environment Managing Member Authorizations
5. What are the available Application Roles and what do they mean? The following are the roles: Administrators: The users assigned to this authorization group can access the following applications: Manage Configuration Digital Compliance Service Health Check If you get a "403 Forbidden Access Error" --> the user needs to be assigned to all the authorization objects to perform the Health Check. Manage Authentication GSP Communications Usage Details GSP Communications Scheduler Tax Administrators: The users assigned to this authorization group can perform the SUBMIT and FILE activity for any GST Returns by accessing the following application:

116

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

Manage GST Returns GSTR SUBMIT/FILE Tax Accountants:The users assigned to this authorization group can perform the SAVE activity for any
GST Returns by accessing the following applications: Manage GST Returns GSTR SAVE Reconcile Inward Invoices Source Administrators: The users assigned to this authorization group can upload and manage Outward/ Inward Invoices by accessing the following applications: Manage Outward Invoices
If you get a "403 Forbidden Access Error" --> Give the user "Source Administrator" + "Tax Accountant" Authorizations. If user is not able to open the tile --> Give the user the Cloud Platform "Developer" Role (see Q.4 Above) Manage Inward Invoices 6. How do I assign Application Roles to selected users? In your cloud platform account cockpit, navigate to your subaccount --> Security (left menu) --> Authorizations (left menu); Select each of the above Application Roles and Assign Users. 7. How to restrict access of specific users at invoice/document level? At the API level, a new field is introduced named as `authobject' which can be filled when you send documents from the source system. If you are using ECC as your source invoicing system, in BAdI EDOC_ADAPTOR, method SET_OUTPUT_DATA the authobject can be set as per the custom implementation. If you set the authobject as IN01 and want a certain user to have access only to the invoices with authobject IN01, then create a new Authorization Group in the SAP BTP cockpit. The Authorization Group name must start with the prefix GST_. Assign the users to this group. For example: For IN01 as the authobject, create a new Authorization Group as GST_IN01 If you want a user to access all the invoices irrespective of the authobject, then assign the users to the GST_ALL Authorization Group. 8. How to manage authorizations at the Reporting Entity Level/ GST Registrations Level? After assigning users to the predefined authorization groups, you can manage authorization via the Manage Configurations application at the following two levels: Reporting Entity level: You can assign users at the Reporting Entity Level (this is typically GSTIN) - If you assign the users at the Reporting Entity level then the users can perform all the activity (SAVE, SUBMIT, FILE etc.) for all reporting categories (any GST Returns). Reporting Category/Activity level: You can assign users at the Reporting Category and Activity level Choose the reporting category and the activity and then assign the user. For the SAVE activity for any GSTR reporting category, there is also a "Summary" checkbox. This must be checked for the users who can create summary documents for GSTR form.
Note
This is provided so that the authobject is not considered at the time of summary preparation. As the summary is reported at the GST registration level rather than the authobject (or invoice/document) level.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

117

11.4 DCS: Connecting to GSP via SAP Cloud Integration

As a prerequisite, ensure that you have installed and configured the integration flow in DCS. For more information, see here .
1. Unable to Authenticate using the "Manage Authentication" App in the DCS. It is possible that you have not yet created the SAP Cloud Integration Flow for GSP connectivity. Once you configure your integration flow, you will have to configure the HCI_GSP Destination in your SAP BTP account. The URL should point to the SAP Cloud Integration URL and not dummyurl.com. For more information on this, see Page 10 of the "Installation and Configuration Guide" attached to Note 2460667 .
2. How to construct the URL for SAP Integration Flow once the integration flow to integrate with the GSP is deployed? Once you deploy the integration flow the end-point address of the newly deployed integration flow would be https://<Runtime URL>/http/<Address> Runtime URL: This is the URL received in the email from SAP Cloud Integration. Note this URL must be the URL of the tenant in which you have developed/deployed the integration flow Example: https://IXXXX-tmn.hci.euX.hana.ondemand.com/http/sapdcs/dcs2gsp
3. When integration flow is developed from Eclipse and deployed, deployment is failing with the error "Component 1.* is not supported in the Product Profile". Cause: If you had installed the latest SAP Cloud Integration Tooling from https://tools.hana.ondemand.com/neon and your tenant runtime version is not compatible version to that version, you may get this error. Solution: If your tenant is on older version than expected ( e.g: 2.30.* or 2.29.* ), create a ticket on LOD-HCI-PI-OPS with a screenshot of the tenant version taken from web UI.
4. 1. Worker Node (IFLMAP) is in stopped state
2. When in integration Flow is deployed for the first time, it is failing with the error "No runtime nodes have been started for this tenant ". Cause: This is a new feature introduced from 2.30.* release onwards . The worker nodes are automatically shut down if there are no integration flows deployed. Solution: Deploy an integration flow on to the tenant and wait for 30 minutes. This should create a worker node automatically and the integration flow should execute successfully. For more information, see SAP Notes 2520573 .
5. While accessing the tenant URL (example: https://xxxxx-tmn.hci.eu1.hana.ondemand.com/itspaces), I am getting, HTTP Status 403 - Access to the requested resource has been denied. Cause: You do not have the necessary Authorization to access the tenant. Solution: If you are an Integration Developer, your user should have the AuthGroup.IntegrationDeveloper role assigned. For Tenant administrator, the AuthGroup.Administrator role should be assigned. For more information, see the More details are available on on-boarding guide https://cloudplatform.sap.com/ onboarding After the role(s) is assigned, open a new session of a browser (preferably in the incognito mode) and login. For more information, see User Management for Cloud Integration.

118

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

6. I am getting Access Denied Error while posting message from GST application to SAP Cloud Integration tenant. Cause: The user that is configured under HTTP Destination is not assigned to the necessary authorization role Solution: Assign the role ESBMessaging.send to the user in the iflmap application.
7. On my SAP Cloud Integration tenant, I noticed that the application ifl is in stopped state, whereas iflmap,tmn are is started state. Do I need to worry about ifl? For GST customers ifl application is not relevant. It is meant for FSN ( Financial Services Network) customers. So, you need not worry about it for GST case.
8. What is the "Ping DCS Integration Flow"? The Ping DCS integration flow is delivered as part of the Standard Integration Content Catalog. This integration flow is provided to do a connection test between your SAP BTP (SAP Business Technology Platform) and Cloud Integration system. This integration flow is used in the DCS Communication Health Check application to do a communication check as part of the DCSCOMM application.
9. What is "GSP Specific integration flow(s)"? If the GSP is certified with SAP ICC, then you may have received two Integration flows. One for authentication and communication to GSTN and the other to check the server status/health status of GSP. You need to deploy both the integration flows in the TEST & PRODUCTIVE CPI tenants. After you deploy the integration flows, create a new destination in the Main TEST/PRODUCTIVE account and maintain the CPI Runtime URL(<RuntimeURL>/http) with the user and password who has access to the CPI tenant with ESBMessaging.send role. Once the above steps are performed, maintain the GSP with the respective endpoint address in the GSP Communication Usage Details --> Manage GSP application.
10. What is the AUTH4037 error? We are getting the AUTH4037 error from Authenticate GSTN Screen. Follow the steps detailed here .

11.5 GSTR1: Save
1. Pushing invoice to DCS Failed: Due to Invalid Taxbase calculation Error 'VAL_SUMMARY_INVALID_TAX_AMOUNT_TAXBASE'. Cause: DCS calculates the TaxAmount based on Taxbase and rate (round off for to 2 decimal places). DCS gives a tolerance of -0.99 to +0.99 to this value. Formula: (Taxbase * rate)/ 100 Example: If igstrate = 28% & Taxbase = 200.88, then igstamt must be equal to 56.2464 (Round off value: 56.25). Tolerance range: 55.26 to 57.24. DCS will accept any value between this range. Solution Upgrade to DCS Release 1.2.14 version to enable the tolerance range. Correct the Tax Amount, so that the validation passes.. If you require a higher tolerance range, then raise a ticket under the component 'XX-CSC-IN-ST'.
2. Summary File Failed at GSTN with the error description 'The UQC entered is not valid' Cause: The request payload for the HSN summary contains UQC which is not accepted by GSTN. Solution: Ensure that the UQC mapped/maintained at ECC is one among the below which is provided by GSTN

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

119

BAG-BAGS BAL-BALE BDL-BUNDLES BKL-BUCKLES BOU-BILLION OF UNITS BOX-BOX BTL-BOTTLES BUN-BUNCHES CAN-CANS CBM-CUBIC METERS CCM-CUBIC CENTIMETERS

CMS-CENTIMETERS CTN-CARTONS DOZ-DOZENS DRM-DRUMS GGK-GREAT GROSS GMS-GRAMMES GRS-GROSS GYD-GROSS YARDS KGS-KILOGRAMS KLR-KILOLITRE KME-KILOMETRE

MLT-MILILITRE MTR-METERS MTS-METRIC TON NOS-NUMBERS PAC-PACKS PCS-PIECES PRS-PAIRS QTL-QUINTAL ROL-ROLLS SET-SETS SQF-SQUARE FEET

SQM-SQUARE METERS SQY-SQUARE YARDS TBS-TABLETS TGM-TEN GROSS THD-THOUSANDS TON-TONNES TUB-TUBES UGS-US GALLONS UNT-UNITS YDS-YARDS OTH-OTHERS

3. Uploaded invoices to GSTN portal not showing up in the GSTN portal. GSTN portal may be having some problem while refreshing the data. Try checking after for some time and if the invoices do not appear for a considerable time, then do the following:
1. In the DCS application, go to Manage Returns and choose the affected GSTIN and Financial Period.
2. Go to Sent tab and see the transactions (Invoice File/Summary File) which are in the Sent To GSTN status.
3. Copy the GSTN Reference ID field.
4. Send the issue to your GSP with this GSTN Reference ID.
4. What are the scenarios for using Invoice Cancellation (ECC/Excel/ Delete) file? Scenario 1 Delete the invoice which is present in DCS but not yet uploaded to GSTN
Mode: Mark invoices as 'D' flag in the Excel. Result: DCS will do a hard delete from the database, you will not see invoice in Manage Outward Invoice
page.
Impact: You will be able to re-upload the invoice with same invoice number (taxpayer_gstin, FinancialPeriod, InvoiceType)
Usage: When you do not wish to see or completely delete the invoice in DCS. Scenario 2 Delete the invoice which is present in DCS and is also uploaded to GSTN
Mode: Mark invoices as 'D' flag in the Excel. Result: DCS will mark the Invoice as `Cancel Initiated' by resetting all the amount to zero. Next time
when you create the Invoice transaction file, deleted invoices will be picked and will be sent to GSTN (To delete the Invoice copy at GSTN server). You will see the invoice in manage outward invoice with status as deleted.
Impact: You will NOT be able to upload/ modify the same invoice number again with the key fields (taxpayer_gstin, FinancialPeriod, InvoiceType) combination.
Usage: When you want to delete the invoice in DCS and also in GSTN without having to upload the same Invoice number again to DCS.
Scenario 3 "Delete File" feature available in Manage GST Returns
Mode: By clicking "Delete File" available under Create dropdown menu Invoice is in NEW status

120

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

Result/Impact: No impact as user is given option to hand pick the invoice which already uploaded to GSTN. Invoice is in UPLOADED status (Sent to GSTN) Result: DCS displays only the Invoices which are already uploaded to GSTN so that you can pick and include it as part of deleted file. When a deleted file (invoices picked by user for deletion) is uploaded to GSTN, invoice copies are deleted from GSTN. On successful response, the status of the invoices is reset back to NEW (As good as a new Invoice uploaded from excel). Impact: You will be able to modify/delete (like scenario 1) the invoice as it is reset back to the NEW status Usage: When you want to delete the Invoice copy form GSTN without initiating a cancel/modify from ECC/Excel.
Note
This feature must be used with utmost caution as the invoice status between your source system and GSTN will be out of sync.
5. How to report Nil supplies from a GSTIN? This business scenario arises when there are no outward supplies from a particular GSTIN for a financial period. In this case, there is no Invoice File to be created. Only Summary File needs to be created. Please see the document here .

11.6 GSTR: Submit and File

In the SUBMIT or FILE activity you might encounter errors while performing actions such as `Fetch Summary' or `Submit' or `File'. To troubleshoot these issues, check the latest log messages.
Following are some of the commonly encountered issues and their troubleshooting steps:
1. `No invoice found for return period and Section' while fetching summary. Fetching summary from GSTN will be successful only when the invoice is successfully saved to GSTN and is reflected at GSTN portal. At times, saved data might not show up immediately on the GSTN portal. Incase if you receive mentioned error, check GSTN and confirm saved invoice is visible in the portal and retry `Fetch summary'.
2. `GSTR1SAVE cannot be blocked; GSTR1 Summary not created or saved' error while changing SAVE activity status to `On hold'. Ensure that summary is created in the SAVE application and is upload successfully and accepted by GSTN.
3. `Cannot initiate GSTR1SUB activity, GSTR1SAVE activity is in process' Error while doing `Fetch Summary' in Submit activity. Change the status of Save activity to `on Hold' and then try to fetch summary in Submit activity.
4. Report submission failed with status EXTERNALEXCEPTION to pass government gateway - Invalid Return period; recommended format is MMYYYY. error while submitting. GSTN only accepts submission for return period July 2017 onward both in Sandbox and Production system.
5. Failure to get data from GSTN with code: REQ-INVALID-0029, status: EXTERNALEXCEPTION and description: Authentication to GSTN expired for GSTIN XXXXXXXXXXXXXXX You need to authenticate for the concerned GSTIN from `Manage Authentication' app.

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

PUBLIC

121

Note
Even if the GSTN authentication status is active in the Manage Authentication application, trigger it again.
6. Failure to get data from GSTN with code: RTN_26, status: EXTERNALEXCEPTION and description: You already have Submitted/Filed for Current Return Period. This suggests that the submit for the concerned return period is done. Check the submit status from the tax payer portal, if it is `SUBMITTED', then change the status of the run by clicking on "Update Submission Status".
Note
The manual update status is an irreversible operation to keep the application in sync with GSTN. Confirm the submission/filing status in GSTN portal before using this option.
7. Code: GEN5002, `Unable to process your request'. Note the transaction ID for the action from the GSP communication application and report the issue to your GSP with transaction ID.
8. I tried to SUBMIT through DCS app but submission failed then I manually updated the status to Content Accepted by Government. Does this mean the report is submitted to GSTN? No, before manually updating the status to Content Accepted by Government, check in the GSTN portal whether the report for a period is submitted or not. If not, then rectify the issue and re-submit. If you have already submitted and status is reflected in GSTN portal, then you can use `Update status' to change the status in DCS application.
Note
The manual update status is an irreversible operation to keep the application in sync with GSTN. Confirm the submission/filing status in GSTN portal before using this option.
9. When to use refresh data button? In the Submit/File activity, if you have already fetched Summary and you wish to fetch latest Summary again, for whatever reasons, you can click on the `Refresh Data' button.
10. Can delete existing summary and fetch new summary again? Yes, either use refresh data or delete the existing run and use `Fetch summary' to get summary again.

122

PUBLIC

SAP Localization Hub, Digital Compliance Service for India for the Neo Environment FAQ

Important Disclaimers and Legal Information
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 a 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.
Videos Hosted on External Platforms
Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
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 Localization Hub, Digital Compliance Service for India for the Neo Environment Important Disclaimers and Legal Information

PUBLIC

123

www.sap.com/contactsap
© 2021 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. 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. Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.
THE BEST RUN

AH XSL Formatter V6.3 MR5 for Windows (x64) : 6.3.6.26216 (2016/10/17 11:37JST) Antenna House PDF Output Library 6.3.855 (Windows (x64))