USER GUIDE | PUBLIC
2020-05-29
Document Compliance for Greece
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
Product Assistance
THE BEST RUN
This is a preview of the documentation that will be available on SAP Help Portal when the Support Packages
specified in SAP notes listed in the SAP Note 2930400 are released for customers.The information in the
preview of an upcoming release is not subject to your license agreement or any other service or subscription
agreement with SAP. SAP has no obligation to pursue any course of business outlined in a preview or any
related presentation, or to develop or release any functionality mentioned therein. Previews or any related
presentation and SAP's strategy and possible future developments, products, platforms, directions, and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice.
The preview information is not a commitment, promise or legal obligation to deliver any material, code, or
functionality. This information is provided without a warranty of any kind, either express or implied, including
but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or noninfringement. This information is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in preview sections, except if such damages were caused by
SAP´s willful misconduct or gross negligence. All forward-looking statements are subject to various risks and
uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not
to place undue reliance on these forward-looking statements, which speak only as of their dates, and they
should not be relied upon in making purchasing decisions.
Content
1
Document Compliance for Greece. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2
eDocument Processing with SAP Document Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3
Customizing for Document Compliance for Greece. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
3.1
Customizing for Full Solution - Greece. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2
Configurations for SAP Application Interface Framework - Greece. . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3
Configurations for SAP Cloud Platform Integration - Greece. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4
Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5
Business Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.1
Processes for Greece. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Uploading Invoices in XML Format as Sellers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Uploading Invoices in XML Format as Buyers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Downloading Invoices in XML Format as Buyers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2
eDocument Statuses and Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Statuses for eDocument for Greece eBooks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Statuses for eDocument for Greece eBooks Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Statuses for eDocument for Greece myDATA eBooks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Statuses for eDocument for Greece myDATA eBooks List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Statuses for eDocument for Greece Incoming eBooks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Statuses for eDocument for Greece eBooks Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3
Processing eDocuments in the Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Document Compliance for Greece
Content
PUBLIC
3
1
Document Compliance for Greece
Use
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.
To comply with the legal requirement that companies are generally obliged to transmit data via electronic
transmission, on 1 August 2019, the Greek Independent Authority of Public Revenue (IAPR) published the
framework for the operation of the digital platform, My Digital Accounting and Tax Application (myDATA). The
platform enables companies to maintain electronic books (eBooks) and record invoice and tax receipt data, as
well as certain other data. Thus, eBooks must be available and transmitted electronically to the myDATA. With
Document Compliance for Greece, you can submit the following types of invoices to myDATA:
● Sales and Distribution (SD) invoices
● Financial accounting (FI) invoices
● Credit notes
● Material Movement Invoices
Prerequisites
For the creation of SAP Document Compliance for Greece, ensure that you have made the settings described in
Customizing for Document Compliance for Greece [page 10].
Features
eDocument Creation
You can set up the system to create eDocuments for different document types as shown in the table below:
Document Type
eDocument Creation
Customer SD invoices
You can create eDocuments for SD invoices via transaction
VF01 for customers.
Customer FI invoices
You can create eDocuments for FI invoices via transaction
FB70/FB01/FB75 for customers.
4
PUBLIC
Document Compliance for Greece
Document Compliance for Greece
Document Type
eDocument Creation
Vendor FI invoices
You can create eDocuments for FI invoices via transaction
FB60/FB01/FB65 for vendors.
Customer credit notes
You can create eDocuments for credit notes via transaction
FB70/FB01/FB75 for customers.
Vendor credit notes
You can create eDocuments for credit notes via transaction
FB60/FB65/FB01 for vendors.
Vendor material movement documents
You can create eDocuments for material movement docu­
ments via transaction MIRO for vendors.
Summary lists
You can create eDocument summary lists for the eDocu­
ments which are already created using the eDocument
Greece: Create Consolidated eDocuments
(EDOC_GR_SUMMARY_REPORT) report by selecting the
Create Greece eBooks Summary List radio button.
For more information, see the application help directly in the
report.
Classification lists
You can create expense classification lists for the eDocu­
ments that are matched with myDATA eBooks using the
eDocument Greece: Create Consolidated eDocuments
(EDOC_GR_SUMMARY_REPORT) report by selecting the
Create Greece eBooks Classification List radio button.
For more information, see the application help directly in the
report.
Processes for eDocuments
The Document Compliance for Greece provides processes in the eDocument Cockpit (transaction
EDOC_COCKPIT) that support the business scenarios shown below.
Business Scenario
Description
Process
Uploading documents as sellers (Seller
In this process, sellers can upload indi­
Uploading Invoices in XML Format as
Outgoing Process)
vidual electronic documents or the lists
Sellers [page 18]
of electronic documents to myDATA.
Uploading documents as buyers (Buyer In this process, buyers can upload the
Outgoing Process)
individual foreign electronic documents
Uploading Invoices in XML Format as
Buyers [page 20]
to myDATA.
Document Compliance for Greece
Document Compliance for Greece
PUBLIC
5
Business Scenario
Description
Process
Downloading documents as buyers
In this process, buyers can download
Downloading Invoices in XML Format as
Buyers [page 22]
(Buyer Incoming Process)
the domestic invoices from myDATA
which are submitted by their sellers and
expense classification can be submit­
ted for the matched invoices to my­
DATA.
6
PUBLIC
Document Compliance for Greece
Document Compliance for Greece
2
eDocument Processing with SAP
Document Compliance
Use
SAP Document Compliance is an integrated end-to-end solution that allows you to create electronic
documents in XML format and transmit them to external systems, such as to tax authorities or business
partners.
SAP Document Compliance comprises the following:
● eDocument Framework
The functionality required to create the eDocuments is part of this product. It contains generic programs
(for example, the eDocument Cockpit) and also specific functions that enables you to use the most
common business scenarios for electronic document.
● SAP Application Interface Framework.
This application is used to map the transactional data to the required XML format.
● SAP Cloud Platform Integration
An integration package in SAP Cloud Platform Integration is available to handle the communication with
external systems as well as notification messaging.
Prerequisites
1. You have made the required Customizing settings.
2. You have made the settings required for SAP Application Interface Framework.
3. You have made the settings required for SAP Cloud Platform Integration.
Process
The figure below depicts an example of eDocument processing when using the Document Compliance end-toend solution.
Document Compliance for Greece
eDocument Processing with SAP Document Compliance
PUBLIC
7
1. You create the source document (for example, invoice) using an SAP application. Once you post 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.
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).
4. This BAdI calls the interface type that enables the system to connect to SAP Application Interface
Framework.
5. SAP Application Interface Framework triggers the mapping of transactional data into the required XML
format and saves the XML files.
6. The system calls SAP Cloud Platform Integration via an ABAP Proxy and establishes communication with
the tax authorities’ or business partners’ systems.
7. If the call is successful, the outgoing XML is saved. After successfully receiving the response, the response
XML is saved.
8. SAP Cloud Platform Integration processes the XML to comply with the official communication
requirements and triggers the corresponding Web services for sending the XML file over to the external
system.
9. SAP Cloud Platform Integration receives information regarding the status of the request back from the
external systems, transforms it into a consumable format (by decoding and mapping the result) and
forwards that together with the signed eDocument (if applicable) to SAP Application Interface Framework
and to the SAP system.
10. The system updates the eDocument in the database with information received from the external systems.
Related Information
SAP Application Interface Framework
8
PUBLIC
Document Compliance for Greece
eDocument Processing with SAP Document Compliance
SAP Cloud Platform Integration
Document Compliance for Greece
eDocument Processing with SAP Document Compliance
PUBLIC
9
3
Customizing for Document Compliance
for Greece
General Settings
Customizing
You make the following settings in Customizing for Cross-Application Components under
Functions
eDocument
General Application
General Settings :
1. For a company code, you activate the types of source documents for which you want eDocuments to be
created in the Activate Source Type Documents for Company Code (EDOCOMPANYACTIV) Customizing
activity. In the Document Compliance for Greece, the source document type can be configured as the
following types:
Greece: Source Document Type for Company Code
Company Code
Source Type
Active
<Customer-specific>
EDOC_LIST

Note
This column should be checked.
<Customer-specific>
FI_INVOICE

Note
This column should be checked.
<Customer-specific>
INV_VERIF

Note
This column should be checked.
<Customer-specific>
SD_INVOICE

Note
This column should be checked.
<Customer-specific>
SRC_FILE

Note
This column should be checked.
2. You select the interface type that you want to use for the generation of eDocuments in the Define Interface
Type for eDocument (EDOINTTYPEV) Customizing activity. You can configurate this Customizing activity as
the table shown below.
10
PUBLIC
Document Compliance for Greece
Customizing for Document Compliance for Greece
Interface Type for Document Compliance for Greece
eDocument Type
eDocument Type Description
Interface Type
GR_EXPENSE
Greece eBooks ExClassification
Standard Implementation using AIF
GR_INV
Greece eBooks
Standard Implementation using AIF
GR_INVI_IM
Greece Incoming eBooks Import
Standard Implementation using AIF
GR_INV_CR
Greece Credit Note
Standard Implementation using AIF
GR_INV_IN
Greece Incoming eBooks
Standard Implementation using AIF
GR_INV_MD
Greece myDATA eBooks
Standard Implementation using AIF
GR_INV_SUM
Greece eBooks Summary
Standard Implementation using AIF
GR_MD_SUM
Greece myDATA eBooks Summary
Standard Implementation using AIF
LE_INV
Localization Extension Invoice
Standard Implementation using AIF
3. You can assign the eDocument type to the Accounting Document Type in theAssign eDocument Type to
Accounting Document Type (T003EDOCV) Customizing activity. You can configurate this Customizing
activity as the table shown below:
Greece: Assign eDocument Type to Accounting Document Type
Deviating
Deviating
eDocument De­
eDoc. Type for
eDoc. Type De­
Rev.
scription
Type
Description
eDocument Type
scription
D7
Debit Note CO
GR_INV
Greece eBooks
DG
Customer Credit
GR_INV_CR
Greece Credit
Memo
DH
Customer Debit
Note
GR_INV
Greece eBooks
Memo
DR
Customer Invoice
GR_INV
Greece eBooks
KR
Vendor Invoice
GR_INV_IN
Greece Incoming
eBooks
RV
Billing doc.trans­
GR_INV
Greece eBooks
fer
4. In addition to these general customizing settings, you also need to make configurations for the Full
solution. See Customizing for Full Solution - Greece [page 14].
Document Compliance for Greece
Customizing for Document Compliance for Greece
PUBLIC
11
Greece Specific Settings
In addition to the generic settings mentioned above, you make settings that are specific for Greece.
Before you make configurations, there are some important requirements that need to be fulfilled as follows:
Type
Requirement
Invoice Type
Invoice types are determined on the following two determi­
nation conditions:
Classification Category/Type
●
Print Task Code (PTC)
●
General Ledger (G/L) Account
Classification categories are determined based on G/L Ac­
count and Company code.
VAT Category
VAT categories are determined based on TAX codes only. A
domain is created for master data with the values provided
in the invoice-mapping excel.
Withhold Tax Category
Withhold Tax categories are determined based on withhold
tax codes only. A domain is created for master data with the
values provided in the invoice-mapping excel.
Stamp Category
These values are determined based on tax codes or G/L Ac­
count and Company code. Domains are created for master
data with the values provided in the invoice-mapping excel.
Fees Percentage Category
These values are determined based on tax codes or G/L Ac­
count and Company code. Domains are created for master
data with the values provided in the invoice-mapping excel.
Other Tax Category
These values are determined based on tax codes or G/L Ac­
count and Company code. Domains are created for master
data with the values provided in the invoice-mapping excel.
Deduction Amount
Deduction Amount is determined based on G/L Account and
Company Code.
● You can maintain the Invoice Type and its descriptions in this eDocument Greece: Define myDATA Invoice
Type view (EDOGRINVTYPE) through transaction SM30.
● You can maintain the Document Type, Print Task Code, Country Type, and Invoice Type ineDocument
Greece: Customize Invoice Type from Print Task Code view (EDOGRINVTYPEPTC) through transaction
SM30.
● You can maintain Document type, Company Code, Region, From G/L Account, To G/L Account, Invoice
Type in eDocument Greece: Customize Invoice Type from Accounting Info view (EDOGRINVTYPEACC)
through transaction SM30.
● You can maintain Classification category and its Description in eDocument Greece: Classification Category
Master Data view (EDOGRCLASSCATEG) through transaction SM30.
12
PUBLIC
Document Compliance for Greece
Customizing for Document Compliance for Greece
● You can maintain Income / Expense Classification Type and Classification Type Description in eDocument
Greece: Income/Expense Classification Type view (EDOGRCLASSTYPE) through transaction SM30.
● You can maintain Company code, Country Type, From G/L Account, To G/L Account, Classification
Category and Income/Expense Classification Type in eDocument Greece: Customize Classification Type
with G/L Acc view (EDOGRCLASSTYPEGL) through transaction SM30.
● You can maintain Withholding Tax Code, Tax Type, Withhold Tax Category, Stamp Duty Percentage, Fee
Percentage Category, Other Tax Percentage Category in eDocument Greece: Withhold Tax Category view
(EDOGRWTCATE) through transaction SM30.
 Note
When maintaing the view, you should keep in mind the following restrictions:
○ If TAX TYPE is Withholding Tax, only Withhold Tax Category is allowed.
○ If TAX TYPE is Fees, only Fee Percentage Category is allowed.
○ If TAX TYPE is Other Taxes, only Other Tax Percentage Category is allowed.
○ If TAX TYPE is Stamp Duty, only Stamp Duty Percentage Category is allowed.
○ Excluded or Deductions or VAT isn’t allowed for TAX TYPE.
● You can maintain Tax on Sales/Purchases Code, Tax Type, Withhold Tax Category, Stamp Duty Percentage,
VAT Category, Fee Percentage Category, Other Tax Percentage Category in this eDocument Greece: Define
Categories for Tax Codes view (EDOGRCATEMWSKZ).
 Note
The following restrictions are to be followed for maintaining the view:
○ If TAX TYPE is VAT, only VAT Category is Allowed.
○ If TAX TYPE is Withholding Tax, only Withhold Tax Category is allowed.
○ If TAX TYPE is Fees, only Fee Percentage Category is allowed.
○ If TAX TYPE is Other Taxes, only Other Tax Percentage Category is allowed.
○ If TAX TYPE is Stamp Duty, only Stamp Duty Percentage Category is allowed.
○ Excluded or Deductions isn’t allowed for TAX TYPE.
● You can maintain Tax on Company Code, From G/L Account, To G/L Account, Tax Type, Withhold Tax
Category, Stamp Duty Percentage, Fee Percentage Category, Other Tax Percentage Category in eDocument
Greece: Define Categories for G/L Accounts view (EDOGRCATEHKONT).
 Note
The following restrictions are to be followed for maintaining the view:
○ If TAX TYPE is Withholding Tax, only Withhold Tax Category is allowed.
○ If TAX TYPE is Fees, only Fee Percentage Category is allowed.
○ If TAX TYPE is Other Taxes, only Other Tax Percentage Category is allowed.
○ If TAX TYPE is Stamp Duty, only Stamp Duty Percentage Category is allowed.
○ Excluded or Deductions, no category is allowed.
○ VAT isn’t allowed for TAX TYPE.
Document Compliance for Greece
Customizing for Document Compliance for Greece
PUBLIC
13
3.1
Customizing for Full Solution - Greece
In addition to the general Customizing activities, for the Full solution, maintain the following activities in
Customizing for eDocuments under
eDocument
Cross-Application Components
General Application Functions
General Settings :
1. You activate specific fields in the eDocument Cockpit in the Activate Solution Specific Fields
(EDOCOUNTRYSOLV) Customizing activity. By default, only the fields for the Basic solution are activated.
2. You define SOA Services to logical ports in the Define SOA Services for Communication (EDOSOASERV)
Customizing activity. For Document Compliance for Greece, you can configurate this Customizing activity
as the table shown below:
Greece: Define SOA Services for Communication
SOA Service Name
Company Code
Logical Port
SOA Service Description
GR_CANCEL_INVOICE
<Customer-specific>
EDO_GR_CANCEL
Greece - Cancel Invoice
GR_EXCLASSIF_INVOICE
<Customer-specific>
EDO_GR_EXPENSE_CLS
Greece - Expense Classification Invoice
GR_INCOMING_INVOICE
<Customer-specific>
EDO_GR_INVOICE
Greece - Incoming Invoice
GR_MDSUM_INVOICE
<Customer-specific>
EDO_GR_REQUEST_DOC
Greece - myDATA eBooks
Summary
GR_SEND_INVOICE
<Customer-specific>
EDO_GR_INVOICE
Greece - Send Invoice
GR_SUMMARY_INVOICE
<Customer-specific>
EDO_GR_INVOICE
Greece - Summary Invoice
3. You assign SOA Services to eDocument interfaces in the Assign SOA Services to eDocument Interfaces
(EDOINTV) Customizing activity. For Document Compliance for Greece, you can configure this
Customizing activity as the table shown below.
Greece: Assign SOA Services to eDocument Interfaces
Interface ID
SOA Service Name
Direction
Interface Description
GR_CANCEL_REQUEST
GR_CANCEL_INVOICE
Outbound
Cancel Request
GR_CANCEL_RESPONSE
GR_CANCEL_INVOICE
Inbound
Cancel Response
GR_CLASSIFICATION_RE­
GR_CLASSIFI_INVOICE
Outbound
Classification Request
GR_CLASSIFI_INVOICE
Inbound
Classification Response
GR_EXCLASSIF_INVOICE
Outbound
QUEST
GR_CLASSIFICATION_RE­
SPONSE
GR_EXCLASSIFICA­
TION_REQUEST
14
PUBLIC
Expense Classification Re­
quest
Document Compliance for Greece
Customizing for Document Compliance for Greece
Interface ID
SOA Service Name
Direction
GR_EXCLASSIFICA­
GR_EXCLASSIF_INVOICE
Inbound
TION_RESPONSE
GR_INCOMING_REQUEST
Interface Description
Expense Classification Re­
sponse
GR_INCOMING_INVOICE
Outbound
Incoming Request
GR_INV_MDSUM_REQUEST GR_MDSUM_INVOICE
Outbound
myDATA Summary Request
GR_INV_MDSUM_RE­
Inbound
myDATA Summary Re­
GR_MDSUM_INVOICE
SPONSE
sponse
GR_SEND_REQUEST
GR_SEND_INVOICE
Outbound
Send Request
GR_SEND_RESPONSE
GR_SEND_INVOICE
Inbound
Send Request
GR_SUMMARY_REQUEST
GR_SUMMARY_INVOICE
Outbound
Summary Request
In addition to these Customizing settings, you make configurations for SAP Application Interface Framework
(AIF) (see Configurations for SAP Application Interface Framework - Greece [page 15]) and SAP Cloud
Platform Integration (see Configurations for SAP Cloud Platform Integration - Greece [page 16]).
3.2
Configurations for SAP Application Interface
Framework - Greece
Definition
You use SAP Application Interface Framework to map the transactional data into the legally required XML for
each country. This is relevant if you have implemented the eDocument Full solution.
 Note
For information about implementation and upgrade steps for SAP Application Interface Framework, see
SAP Note 2071823 .
To integrate both SAP system and SAP AIF, you perform the following steps:
● Make global AIF settings
You create and activate database tables and BAdI implementations in a customer namespace as described
in SAP Note 2027186 . These objects are generic and valid for all countries.
● Install global BC sets
AIF is fully compliant with the eDocument solution as of version 701.SP 06. You install the BC sets delivered
doing the following:
with the SAP Note 2010697
1. Use the SCPR3 transaction to upload the BC sets.
Document Compliance for Greece
Customizing for Document Compliance for Greece
PUBLIC
15
2. Use the SCPR20 transaction to activate the BC sets.
The available BC sets contain all necessary generic customizing entries for the eDocument solution. By
activating the BC sets, some generic entries are automatically made in your system, such as the global
namespace /EDO is created as well as all other relevant objects needed for the creation of a generic
eDocument.
You do Greece-specific configurations for SAP Application Interface FrameworkF, see SAP Note2930400
3.3
.
Configurations for SAP Cloud Platform Integration Greece
Definition
Document Compliance uses the SAP Cloud Platform Integration to communicate with external systems via
web services. For that, you do the following:
● Connect your back-end system and Application Interface Framework with SAP Cloud Platform Integration.
● Set up of SAP Cloud Platform Integration for connecting to the external systems.
The prerequisite to access the SAP Cloud Platform Integration implementation for a given local version is to
have an SDN account that enables you to access SAP Cloud Platform Integration. To find the Integration
package, do the following.
1. Access the SAP Cloud Platform Integration page using this link: http://api.sap.com
.
2. Choose Integration.
3. Choose All.
4. Search for the integration package you’re looking for. If you don’t know the exact name of the integration
package, search for eDocument and a list of integration packages for eDocument is displayed and you can
choose the one you’re interested in.
5. Go to Documents and open the integration documentation. The document guides you through the settings
you do in SAP Cloud Platform Integration to enable eDocuments for your local version.
Once you access the SAP Cloud Platform Integration catalog page, you find the SAP Document Compliance:
Electronic Tax Register Books for Greece(e-Books) package. By clicking on this package, you are directed to the
page specific for Document Compliance for Greece. On this page, click on the Documents icon to find the
Greece Electronic Tax Register Books (e-Books): Setting Up SAP Cloud Platform Integration. This
document guides you through all the necessary settings you need to make in SAP Cloud Platform Integration
to enable the Full eDocument solution for Greece.
16
PUBLIC
Document Compliance for Greece
Customizing for Document Compliance for Greece
4
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 in the following
reports:
Authorization Object
Authorization Fields
Actions
EDO_BUK
BUKRS
View eDocuments for a company code
in the eDocument Cockpit report
(transaction code EDOC_COCKPIT)
EDO_PROC
EDO_PROC
EDO_PRSTEP
Document Compliance for Greece
Authorization Objects
Perform process steps in the eDocu­
ment Cockpit report (transaction code
EDOC_COCKPIT)
PUBLIC
17
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
eDocument Cockpit
5.1
Cross-Application Functions
eDocument
or call the EDOC_COCKPIT transaction.
Processes for Greece
The Document Compliance for Greece supports the following business processes and the tracking of
eDocument statuses to these processes:
● Uploading Invoices in XML Format as Sellers [page 18]
● Uploading Invoices in XML Format as Buyers [page 20]
● Downloading Invoices in XML Format as Buyers [page 22]
5.1.1 Uploading Invoices in XML Format as Sellers
To perform actions on the SD and FI invoices for this scenario, you use the Greece eBooks process and Greece
eBooks Summary process in the eDocument Cockpit report. For information about the actions supported for
this process, choose the
Help pushbutton on the top of the process-specific screen.
An example of the generic process for Uploading Invoices in XML Format as Sellers is depicted in the figure
below, and is followed by an explanation:
18
PUBLIC
Document Compliance for Greece
Business Transactions
Uploading Invoices in XML Format as Sellers
Proceed as follows:
1. Post a source document in the source applications. See eDocument Creation in the Feature section in
Document Compliance for Greece [page 4].
Once you post the source document, the system creates an eDocument instance automatically for that in
the database.
2. You can submit the eDocument instance individually or submit the eDocument summary as follows:
1. In the Greece eBooks process in the eDocument Cockpit, you submit the eDocument instance
individually.
2. Submit an eDocument summary as follows:
1. Create a summary for the eDocument instance you created by running eDocument Greece: Create
Consolidated eDocuments (EDOC_GR_SUMMARY_REPORT) report.
Make sure you run the report with the option Create Greece eBooks Summary List selected.
Once you run this report successfully, the system creates a summary list eDocument consisted of
one or multiple eDocument instances you selected and displays it in eDocument Cockpit.
2. Go to Greece eBooks Summary process in the eDocument Cockpit and submit the eDocument
summary you created.
The system forwards it to the SAP Application Interface Framework for mapping the XML file in the format
required by the tax authorities. This application forwards the XML to the SAP Cloud Platform Integration.
3. SAP Cloud Platform Integration processes the XML and sends it to the tax authority.
4. Tax authority processes invoices, stores it and sends back legal data, including the UID and MARK number
which is processed and forward it until it reaches the eDocument Cockpit.
 Note
UID is a unique document ID. And MARK is a unique registration number. They’re given by myDATA
upon document’s first successful transmission for the eDocument. When you try resubmitting the
same document, UID remains unchanged, while MARK is changed upon every resubmission.
Document Compliance for Greece
Business Transactions
PUBLIC
19
5. In the Cockpit, the system updates the response from myDATA for summaries and individual eDocuments
and store myDATA legal data.
6. The system updates the process statuses as follows:
○ If the electronic invoice has been accepted by myDATA, the status is changed to Accepted and Income
Classified.
○ If the electronic invoice has been rejected by myDATA, the status is changed to Rejected by myDATA.
You can check error messages in the Application Log, fix the errors and resubmit the electroinc invoice.
○ If the eDocument summary has been accepted by myDATA, the staus is changed to Accepted by
myDATA.
○ If the eDocument summary has been rejected by myDATA, the status is changed to Rejected by
myDATA.
 Note
eDocument summaries can not be resubmitted.
7. You can cancel the individual electronic invoices or eDocument summary. In the eDocument Cockpit, go to
More Cancel eDocument . For detailed steps, choose the
process-specific screen.
The cancellation request is sent to myDATA.
Help pushbutton on the top of the
 Note
When you cancel an eDocument summary, the cancellation request of the eDocument summary is not
sent to myDATA. The cancellation request of individual eDocuments contained in the eDocument
summary are sent to myDATA.
8. SAP Cloud Platform Integration validates the request and sends it to the tax authority.
9. Tax authority processes the cancellation request and sends the response to SAP Cloud Platform
Integration.
10. You can check its status in the eDocument Cockpit, there are two cases occur:
• When the request for cancellation is rejected by myDATA, the status is remained unchanged. You can
check error messages in the Application Log.
• When the request for cancellation is accepted by myDATA, the myDATA cancellation ID is updated for the
electronic invoice in the Cancel Mark column, and the status is changed to Cancellation Accepted.
5.1.2 Uploading Invoices in XML Format as Buyers
To perform actions on the foreign vendor invoices for this scenario, you use the Greece Incoming eBooks
process in the eDocument Cockpit. For information about the actions supported for this process, choose the
Help pushbutton on the top of the process-specific screen.
An example of the generic process for Uploading Invoices in XML Format as Buyers is depicted in the figure
below, and is followed by an explanation:
20
PUBLIC
Document Compliance for Greece
Business Transactions
Uploading Invoices in XML Format as Buyers
Proceed as follows:
1. Post a source document in the source applications. See eDocument Creation in the Feature section in
Document Compliance for Greece [page 4].
Once you post the source document, the system creates an eDocument instance automatically for that in
the database.
2. Submit the eDocument instance.
The system forwards it to the SAP Application Interface Framework for mapping the XML file in the format
required by the tax authority. This application forwards the XML to the SAP Cloud Platform Integration.
3. SAP Cloud Platform Integration processes the XML and sends it to the tax authority.
4. Tax authority processes invoices, stores it and sends back legal data, including the UID and MARK number
which is processed and forward it until it reaches the eDocument Cockpit.
 Note
UID is a unique document ID. And MARK is a unique registration number. They’re given by myDATA
upon document’s first successful transmission for the eDocument. When you try resubmitting the
same document, UID remains unchanged, while MARK is changed upon every resubmission.
5. In the Cockpit, the system updates the response from myDATA for the eDocument and store myDATA legal
data.
6. If the electronic invoice has been accepted by myDATA, the status is changed toAccepted and Expense
Classified.
If the electronic invoice has been rejected by myDATA, the status is changed toRejected by myDATA. You
can check error messages in the Application Log.
7. You can cancel the individual electronic invoices. For detailed steps, choose the
top of the process-specific screen.
The cancellation requests of individual electronic invoices are sent to myDATA.
Help pushbutton on the
8. SAP Cloud Platform Integration validates the request and sends it to the tax authority.
Document Compliance for Greece
Business Transactions
PUBLIC
21
9. Tax authority processes the cancellation request and sends the response to SAP Cloud Platform
Integration.
10. You can check its status in the eDocument Cockpit, there are two cases occur as follows:
• When the request for cancellation is rejected by myDATA, the status is remained unchanged. You can
check error messages in the Application Log.
• When the request for cancellation is accepted by myDATA, the myDATA cancellation ID is updated for the
electronic invoice in theCancel Mark column, and the status is changed to Cancellation Accepted.
5.1.3 Downloading Invoices in XML Format as Buyers
To perform actions on the electronic invoices for this scenario, you use the following processes in the
eDocument Cockpit:
● Greece myDATA eBooks
● Greece myDATA eBooks List
● Greece Incoming eBooks
● Greece eBooks Classification
For information about the actions supported for this process, choose the
process-specific screen.
Help pushbutton on the top of the
An example of the generic process for Downloading Invoices in XML Format as Buyers is depicted in the figure
below, and is followed by an explanation:
Downloading Invoices in XML Format as Buyers
Proceed as follows:
1. You use eDocument Inbound Message Handler (EDOC_MESSAGE_HANDLING) report to process incoming
electronic invoices, that is to download the incoming invoices to your system which are submitted by
sellers to myDATA.
22
PUBLIC
Document Compliance for Greece
Business Transactions
The system pulls the incoming invoices that match your selection.
 Note
Once you run the report, the system creates an eDocument summary for electronic invoices pulled
from myDATA.
To access this report, on the SAP Easy Access screen, choose
eDocument
Cross-Application Components
eDocument Inbound Message Handler .
For more information, see the documentation directly in the report.
2. The system forwards the pull request to the SAP Application Interface Framework for mapping the XML file
in the format required by the tax authority. This application forwards the XML to the SAP Cloud Platform
Integration.
3. Tax authority sends the requested electronic invoices back.
4. A match process is automatically performed between the electronic invoices pulled from myDATA and the
electronic invoices posted by buyers. There are two cases occur:
○ If the eDocuments are matched with invoices pulled from myDATA successfully, the system updates
the status of Matched with Buyer Invoice in the Greece Incoming eBooks process.
○ If the eDocuments aren’t matched with invoices pulled from myDATA, the system creates one
eDocument instance for each invoice in the Greece myDATA eBooks process.
And upon every time you pull incoming invoices from myDATA, one eDocument list consisted of
electronic invoices pulled from myDATA is automatically created in the Greece myDATA eBooks List
process.
○ If the eDocuments are matched with multiple invoices pulled from myDATA, the statuses are changed
to Matching Failed.
 Note
If the match isn’t automatically done, you can also manually perform the match process by clicking
the Match Documents button in the Greece Incoming eBooks process in the eDocument Cockpit.
5. Run eDocument Greece: Create Consolidated eDocuments (EDOC_GR_SUMMARY_REPORT) report to
create classification eDcoument List.
Make sure you run the report with the option Create Greece eBooks Classification List selected. After you
run this report, the system creates a classification eDocument list automatically for that in the database.
6. Go to Greece eBooks Classification process and submit the classification eDocument list you created.
The system forwards it to the SAP Application Interface Framework for mapping the XML file in the format
required by the tax authorities. This application forwards the XML to the SAP Cloud Platform Integration.
7. SAP Cloud Platform Integration processes the XML and sends it to the tax authority.
8. Tax authority processes electronic invoices, stores it and sends responses back.
9. In the Cockpit, the system updates the responses from tax authority for the eDocument.
10. You can check the statuses for classification eDocument lists. There are three cases occur:
○ If the classification eDocument lists are rejected by myDATA, the statuses are changed to Rejected by
myDATA. You can check error messages in theApplication Log.
○ If the classification eDocument lists are accepted by myDATA, the statuses are changed to Accepted
by myDATA.
○ If some classification electronic invoices of a classification eDocument list are accepted, the statuses
are changed to Partially Accepted by myDATA , you can check the statuses of individual electronic
invoices.
Document Compliance for Greece
Business Transactions
PUBLIC
23
 Note
The classification eDocument lists can't be resubmitted.
5.2
eDocument Statuses and Actions
5.2.1 Statuses for eDocument for Greece eBooks
The following table lists all the possible process statuses of the eDocument for Greece eBooks process in the
order that they take place:
Process Status
Meaning
User Action
eDocument Created (CREA )
An eDocument has been created.
Create a summary list and submit the
summary list.
Submit the eDocument to myDATA with
the Submit button.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Accepted and Income Classified
myDATA has accepted the sales invoice. Resubmit the eDocument to myDATA.
(ACP_INCOME )
And the income has been classified by
myDATA.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Added to Summary (ADD_TO_SUM)
A summary list has been created for
No further action is not possible on the
one or multiple eDocuments by running eDocument.
eDocument Summary
(EDOC_GR_SUMMARY_REPORT) re­
port.

Note
Further action can be done only in
Greece eBooks Summary process.
24
PUBLIC
Document Compliance for Greece
Business Transactions
Process Status
Meaning
User Action
Cancellation Accepted (CANA )
The request of cancellation for already
No further action is possible on the
accepted eDocument has been ac­
eDocument.
cepted by myDATA.
To keep data consistency, you should
ensure the source document is also
canceled in the source application.
Cancelled (CANC )
An eDocument has been canceled.
No further action is possible on the
eDocument.
To keep data consistency, you should
ensure the source document is also
canceled in the source application.
Rejected by myDATA (REJE )
myDATA has rejected the invoice.
Create summary list and resubmit sum­
mary list.
Re-Submit the eDocument to myDATA
with the Submit button.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Sent to Interface (SEND )
An invoice XML file has been created
Try resubmitting the eDocument. If this
and is pending transfer to myDATA.
status still lasts, it means that technical
error has occurred during transfer.
Check the Error column for trouble­
shooting. Resubmit the eDocument
when the error is fixed.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Sending Requested (SEND_REQ)
The system has requested that an eDo­
Try resubmitting the XML file when the
cument should be sent.
error is fixed.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Document Compliance for Greece
Business Transactions
PUBLIC
25
5.2.2 Statuses for eDocument for Greece eBooks
Classification
The following table lists all the possible process statuses of the eDocument for Greece eBooks Classification
process in the order that they take place:
Process Status
Meaning
eDocument Created (CREA )
An eDocument has been created.
User Action
Submit the classification eDocument to
myDATA with the Submit button.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Accepted by myDATA (ACEP )
The myDATA has accepted the classification eDocument list.
Cancelled (CANC )
A process has been completed. No fur­
ther action is required.
The classification eDocument list has
No further action is possible on the
been cancelled. The status of individual
eDocument.
invoice is changed to its previous sta­
tus.
Partially Accepted by myDATA (PACP )
Some classification electronic invoices
Check the statuses of individual elec­
of a classification list eDocument are
tronic invoices.
accepted.
Note: The classification list eDocument
can’t be resubmitted.
Rejected by myDATA (REJE )
myDATA has rejected the classification
No further action is possible on the
list eDocument.
eDocument.
Note: The classification list eDocument
can’t be resubmitted.
Cancellation Accepted (CANA )
The request of cancellation for already
No further action is possible on the
accepted eDocument has been ac­
eDocument.
cepted by myDATA.
To keep data consistency, you should
ensure the source document is also
canceled in the source application.
Sent to Interface (SEND )
An invoice XML file has been created
Try resubmitting the eDocument. If this
and is pending transfer to myDATA.
status still lasts, it means technical er­
ror has occurred during transfer. Check
the Error column for troubleshooting.
Resubmit the eDocument when the er­
ror is fixed.
Cancel the eDocument.
26
PUBLIC
Document Compliance for Greece
Business Transactions
Process Status
Meaning
User Action
Sending Requested (SEND_REQ)
The system has requested that an eDo­
Resubmit the eDocument when the er­
cument should be sent.
ror is fixed.
Cancel the eDocument.
5.2.3 Statuses for eDocument for Greece myDATA eBooks
The following table lists all the possible process statuses of the eDocument for Greece myDATA eBooks process
in the order that they take place:
Process Status
Meaning
User Action
eDocument Created (CREA )
An eDocument has been created.
No further action is possible on the
eDocument.
Cancelled (CANC )
An eDocument has been cancelled.
No further action is possible on the
eDocument.
Matched with Buyer Document
The electronic invoice received by sell­
(MATCH )
ers match the invoice from buyers.
Display the electronic invoice, which
contains MARK and UID received from
myDATA.
Matching Failed (MATCH_ERR )
The electronic invoices pulled from my­
No further action is possible on the
DATA aren’t matched with electronic in­ eDocument.
voices received by sellers from vendors.
5.2.4 Statuses for eDocument for Greece myDATA eBooks
List
The following table lists all the possible process statuses of the eDocument for Greece myDATA eBooks List
process in the order that they take place:
Process Status
Meaning
User Action
eDocument Created (CREA )
An eDocument has been created.
No further action is possible on the
eDocument.
Document Compliance for Greece
Business Transactions
PUBLIC
27
Process Status
Meaning
User Action
myDATA Summary Processed (PROC )
The eDocument list has been proc­
No further action is possible on the
essed by myDATA to check if the invoi­
eDocument.
ces from mydata match the invoices
which sellers have received from ven­
dors.
5.2.5 Statuses for eDocument for Greece Incoming eBooks
The following table lists all the possible process statuses of the eDocument for Greece Incoming eBooks
process in the order that they take place:
Process Status
Meaning
User Action
eDocument Created (CREA )
An eDocument has been created.
Submit the eDocument to myDATA with
the Submit button.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Accepted and Expense Classif.
myDATA has accepted the purchasing
Cancel the eDocument. To keep data
(ACP_EXPEN )
invoices and updated the expense with
consistency, you should also cancel the
classifications.
source document in the source applica­

Note
tion.
This status is only applicable to for­
eign purchasing invoices and FI in­
voices for vendors.
Added for Classification
(ADD_TO_CLA )
A classification list has been created for Submit the electronic classification list
one or multiple eDocuments by running to myDATA with the Submit button.
eDocument Summary
(EDOC_GR_SUMMARY_REPORT) re­
port.

Note
This is only for domestic vendor in­
voices.
28
PUBLIC
Document Compliance for Greece
Business Transactions
Process Status
Meaning
User Action
Cancellation Accepted (CANA )
The request of cancellation for already
No further action is possible on the
accepted eDocument has been ac­
eDocument.
cepted by myDATA.
To keep data consistency, you should
ensure the source document is also
canceled in the source application.
Cancelled (CANC )
An eDocument has been cancelled.
No further action is possible on the
eDocument.
To keep data consistency, you should
ensure the source document is also
canceled in the source application.
Cancelled by Seller (CANI )
The eDocument has been cancelled by
No further action is possible on the
seller.
eDocument.

Note
This is applicable to domestic ven­
dors’ invoices. The cancelled status
is pulled from mydata when seller
cancels electronic invoices that
have been marked as Matched with
myDATA eBook or Expense
Classified.
Expense Classified (EXPENSE)
myDATA has accepted the expense
Submit the classification data of invoi­
classification data.
ces from domestic vendors by creating
and submitting classification list.
Cancel the eDocument.
Rejected by myDATA (REJE )
myDATA has rejected the invoice.
Resubmit the XML file when the error is
fixed.
Matched with myDATA eBook (MATCH )
The incoming invoice from myDATA
Create the classification eDocument
matches the invoice from buyers.
list.

Note
Note: This is only possible for do­
mestic invoices.
Matching Failed (MATCH_ERR )

Note
Submit the classification eDocu­
ment list in the Greece eBooks
Classifications process.
The incoming invoice from myDATA
Fix the error in the invoice, and then
doesn’t match the invoice from buyers.
create a classification list and Submit
the eDocument to myDATA with the
Submit button.
Document Compliance for Greece
Business Transactions
PUBLIC
29
Process Status
Meaning
User Action
Sent to Interface (SEND )
An invoice XML file has been created
Try resubmitting the eDocument. If this
and is pending transfer to myDATA.
status still lasts, it means that technical
errors have occurred during transfer.
Check the Error column for trouble­
shooting. Resubmit the eDocument
when the error is fixed.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Sending Requested (SEND_REQ)
The system has requested that an eDo­
Try resubmitting the XML file when the
cument should be sent.
error is fixed.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
5.2.6 Statuses for eDocument for Greece eBooks Summary
The following table lists all the possible process statuses of the eDocument for Greece eBooks Summary
process in the order that they take place:
Process Status
Meaning
User Action
eDocument Created (CREA )
A summary list eDocument has been
Submit the eDocument to myDATA with
created.
the Submit button.
Cancel the eDocument. To keep data
consistency, you should also cancel the
source document in the source applica­
tion.
Accepted by myDATA (ACEP )
Cancellation Accepted (CANA )
myDATA has accepted the list eDocu­
A process has been completed. No fur­
ment.
ther action is required.
The request of cancellation for already
No further action is possible on the
accepted eDocument has been ac­
eDocument.
cepted by myDATA.
30
PUBLIC
Document Compliance for Greece
Business Transactions
Process Status
Meaning
User Action
Cancelled (CANC )
An summary list eDocument has been
The status of individual invoice eDocu­
canceled.
ment will be changed to its previous
status and can be included in a new
summary list eDocument.
Partially Accepted by myDATA (PACP )
Some electronic invoices of a summary
Check the statuses of individual invoi­
list are accepted.
ces in the Greece eBooks process.

Note
Summary list can’t be resubmitted.
Rejected by myDATA (REJE )
myDATA has rejected the invoice.
No further action is possible on the
eDocument.

Note
Summary list can’t be resubmitted.
Sent to Interface (SEND )
An invoice XML file has been created
Try resubmitting the eDocument. If this
and is pending transfer to myDATA.
status still lasts, it means technical er­
ror has occurred during transfer. Check
the Error column for troubleshooting.
Resubmit the eDocument when the er­
ror is fixed.
Cancel the summary list eDocument.
Then, the individual eDocument will be
changed to its previous status and can
be included in a new summary list eDo­
cument..
Sending Requested (SEND_REQ)
The system has requested that an eDo­
Try resubmiting the XML file when the
cument should be sent.
error is fixed.
Cancel the eDocument. Then, the indi­
vidual eDocument will be changed to its
previous status and can be included in a
new summary list eDocument.
5.3
Processing eDocuments in the Background
You use the eDocument: Processing in Background report to create automatic jobs to run specific process
actions on selected eDocuments.
Document Compliance for Greece
Business Transactions
PUBLIC
31
To find the eDocument: Processing in Background, on the SAP Easy Access screen, choose
Functions
eDocument
eDocument: Processing in Background
or call the EDOC_BACKGROUND transaction.
For information about the actions you can do in the report, choose the
screen.
32
PUBLIC
Cross-Application
Help pushbutton on the selection
Document Compliance for Greece
Business Transactions
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.
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.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
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.
Document Compliance for Greece
Important Disclaimers and Legal Information
PUBLIC
33
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
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