PUBLIC

2018-03-16

eDocument for Italy

Content

1 eDocument for Italy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

1.1 Customizing for eDocument - Italy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Implementation Considerations for eDocument - Italy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Archiving eDocument Data with EDOCUMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Data Destruction in SAP eDocument. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Deletion and Blocking of Customer and Vendor Data in SAP eDocument. . . . . . . . . . . . . . . . . . . . . 10
1.3 Implementation Considerations for eDocument in AIF - Italy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.4 Business Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
eDocument Status and Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Creating and Submitting an eDocument. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Deleting an eDocument. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Resubmitting an eDocument. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Cancelling an eDocument. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Displaying eDocument Status History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Downloading an eDocument. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

eDocument for Italy

2 PUBLIC Content
1 eDocument for Italy

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.

The following eDocument solution variant is available for Italy:

Prerequisites

For the creation of eDocuments for Italy using any of the two above-mentioned eDocument solution, ensure that
the following has been done in your system:

1. You made the customizing in as described in Customizing for eDocument - Italy [page 3].
2. You made the settings as described in Implementation Considerations for eDocument - Italy [page 5].

The following is relevant for eDocument solution using customer-specific communication capabilities system:

● You made the settings as described in Implementation Considerations for eDocument in AIF - Italy [page 11]

1.1 Customizing for eDocument - Italy

General Settings

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 transaction FIBF in the SAP Menu.

Customizing

You make the following settings in Customizing for eDocuments under Cross-Application Components General
Application Functions eDocument General Settings :

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).

eDocument for Italy

eDocument for Italy PUBLIC 3
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 Blling Document Type (TVFKEDOCV)
4. For an eDocument Type, you define which process statuses are assigned to which eDocument status. You do
this in Assign eDocument Status to Process Status (EDOMETASTATDETV).

Business Add-Ins

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 Business Add-Ins :

● Enhancements for eDocument BAdI (EDOC_ADAPTOR): You use this BAdI to define customer-specific 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 the transferring of eDocuments over to external or to the tax
authorities’ systems. The implementation of this BAdI varies depending on which eDocument solution variant
you are using.

Refer to the BAdI implementation documentation as well as the corresponding BAdI Methods documentation for
more detailed information.

Integration with Solution Industry for Utilities (IS-U)

To enable the integration with the SAP Industry solution for Utilities (IS-U), you make settings in Customizing in
the IS-U system under Customizing for SAP Utilities under Invoicing E-Invoicing Country-Specific Functions
E-Invoicing – Italy

Italy-Specific Settings

In addition to the general settings mentioned above, you make settings which are specific for Italy in Customizing
for eDocuments under Cross-Application Components General Application Functions eDocument Country-
Specific Settings Italy :

You define the number range for the numbering of eDocuments for Italy in Maintain Number Ranges for
eDocument Numbering.

eDocument for Italy

4 PUBLIC eDocument for Italy
1.2 Implementation Considerations for eDocument - Italy

Integration with other SAP solutions

● Utilities Industry Solution (IS-U)

Note
Supported only for eDocument Basic solution.

1. Function Module for printing:

For IS-U invoices, in transaction FQEVENTS assign the function module EDOC_ISU_R394 to the R394
event. For more information, see the SAP Note 2058588 .
2. Add eDocument field in Contract Account Level:
Add the IPA Code and IPA Start date fields in Contract Account and maintain them in master data for your
contract accounts. For more information, see SAP Note 2031033 .
For more information about IS-U invoices, in www.help.sap.com search for SAP ERP Central Component and
then for Industries in SAP ERP SAP Utilities Invoicing .
● Health Care Industry solution (IS-H)
The system automatically creates eDocuments once for IS-H documents are created.

Making Settings in Master data

For the customers for which you create eDocuments, make the following settings in their master data:

1. Ensure that the customer for which you create eDocuments is an Italian customer and the value in the Tax
Number 4 (STCD4) field in customer's master data (XD03 transaction, Control Data tab) is not initial.
2. Ensure that the Tax Number 4 for this customer has IPA code.

Follow the instructions described in the attachment of the SAP Note 2005415 if the field Tax Number 4 is not
displayed in your system.

Including Additional Fields Required by the Tax Authorities to the XML File

Some additional fields for Company Global Parameters are required for the eDocument for Italy. You add these
fields to the V001I table using the SM30 transaction.

eDocument for Italy

eDocument for Italy PUBLIC 5
● For the FatturaPA 1.0 version, the following fields are required:

Table 1:

Par. Type Description Length ISO Code

INRBOL Fattura Duty Stamp Nr. 14 IT

IBOLFI Fattura GL account for Bollo 10 IT

IBOLSD Fattura cond. type for Bollo 4 IT

INRREA Fattura Companies Register 20 IT

Nr.

IREGFI Fattura Tax System 4 IT

ISTLIQ Fattura Liquidation Indicator 2 IT

IUFFIC Fattura Province Reg. Office 2 IT

Refer to the attachment of the SAP Note 2005415 for more information.

● For the FatturaPA 1.1 version, additionally to the fields you required to the FatturaPA 1.0, you add new ones.

Table 2:

Par. Type Description Length ISO Code

ICASOC Fattura Company Share Cap­ 15 IT

ital.

ISOCUN Fattura Companies Share­ 2 IT

holders

Refer to the attachment of the SAP Note 2142250 for more information.

After you add the above mentioned fields, you maintain them in Customizing for Financial Accounting under
Financial Accounting Global Settings Global Parameters for Company Code Enter Global Parameters .
Alternatively, you can use the OBY6 transaction:

1. Select the Company Code for which you want to customize this function.

2. Click on Additional Data and click on until you find the field you want to maintain. See the table below for
details about each field:

Table 3:

Field Name Information about possible values

Fattura Duty Stamp Nr. Details of the relevant authorization issued by the tax author­
ity electronic payments

eDocument for Italy

6 PUBLIC eDocument for Italy
 Field Name Information about possible values

Fattura GL account for Bollo General Ledger account used for Duty Stamp movements.

You can define for a company code that the system collects in
only one payment the amounts due for the duty stamp (Bollo)
posted in single invoices during a period of time. For that, en­
ter Always in this field. The system sets the Bollo
Virtualle field of the XML to SI.

Fattura cond. type for Bollo Condition type used for the pricing of billing documents for
Duty Stamp movements

Fattura Companies Register Nr. Registration number that has to be filled in if the company is
listed on the Companies Register pursuant to Art. 2250 of the
civil code.

Fattura Tax System Tax status of the seller/provider, possible values: RF01 to RF18

Fattura Liquidation Indicator LS : in liquidation; LN : not in liquidation

Fattura Province Reg. Office Acronym of the province where the Companies' Registry Office
at which the company is registered is located (T005S-REGIO).

Fattura Company Share Capital. Only in the case of a company (SpA, SApA, SRL), the field
must be filled in with the share capital. Numeric format; deci­
mals must be separated from the integer with the '.' character
(point)

Fattura Companies Shareholders Only in the case of a joint-stock company or limited liability
company, the field must be filled in to indicate the sharehold­
ers. Allowed values: [SU] : sole shareholder, [SM] : several
shareholders

Rules for Tax and Price Conditions for Items in Billing Documents

In case there are no tax or price conditions active for the item of a billing document, the following apply:

● If the line item of the billing document does not have a valid tax condition or this is inactive, the tax rate is set
to 0.00 and the Natura code is set to N4.
● If the line item of the billing document does not have a valid price condition or this is inactive the unit price is
set to 0.00. If the line item has more than 1 active price conditions, they will be summed up.

You maintain tax and prices conditions in Customizing for Sales and Distribution under Basic Functions
Pricing .

eDocument for Italy

eDocument for Italy PUBLIC 7
Maintaining Number Range for Progressive number

The progressive number is used for the generation of a part of the names of the files send to SdI. You maintain the
interval for the EDOITPROGR number range in the SNRO transaction. The number of the range is 01. The From
Number is 000000001, the To Number is 999999999.

Invoice Splitting

Invoice splitting means that your customer pays the VAT directly to the tax authorities instead of paying it to you. If
you issue an eDocument to a public entity, this entity is responsible for paying the VAT amount due and this, in
turn, should be deducted from the total amount of the invoice. For information on how to customize your system
to use the invoice splitting feature, see the attachment of the SAP Note 2117870 .

For the eDocument using Customer-specific Comunication Capabilities solution, an extra mapping in AIF is
necessary. For more information, see Implementation Considerations for eDocument in AIF - Italy [page 11].

1.2.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:

Table 4:

Object Name Description Authorization Fields Relevant for Programs

EDO_BUK eDocument: Authorization for BUKRS ● eDocument Cockpit

Company code (EDOC_COCKPIT)
● Create and Submit
eDocument
(EDOC_RESUBMIT_EDOC
UMENT)

EDO_PROC eDocument: Authorization for EDO_PROC ● eDocument Cockpit

Process & Process Step (EDOC_COCKPIT)
EDO_PRSTEP
● Create and Submit
eDocument
(EDOC_RESUBMIT_EDOC
UMENT)

EDO_MSGTY eDocument: Authorization for EDO_MSGTY Upload Tool for Incoming

Inbound Message Type Messages
(EDOC_INBOUND_UPLOAD)

eDocument for Italy

8 PUBLIC eDocument for Italy
1.2.2 Archiving eDocument Data with EDOCUMENT

Archiving object for eDocument

You can archive and delete eDocuments using the EDOCUMENT archiving object.

Data archiving is used to remove mass data from the database that is no longer required in the system but must be
kept in a format that can be analyzed. For all archiving objects of documents, the data archiving concept is based
on the Archive Development Kit (ADK).

For more information, see the SAP NetWeaver Library on SAP Help Portal at http://help.sap.com/nw. Choose the
relevant SAP NetWeaver Platform and under Application Help, select SAP NetWeaver Library: Function-Oriented
View. Navigate to Life Cycle Management Data Archiving .

For information about the EDOCUMENT archiving object, enter the archiving object in transaction SARA, and
check the system documentation available under the Help pushbutton.

1.2.3 Data Destruction in SAP eDocument

The archiving object describes which database objects must be handled together as a single business object. You
need the archiving object name to carry out the archiving programs in archive administration (transaction SARA).

You use the EDOCUMENT archiving object to destroy eDocuments. This archiving object destroys records from the
following database tables and views:

Table 5: Database tables and views

Tables Description

EDOCUMENT eDocument

EDOCUMENTHISTORY eDocument: History

EDOCUMENTFILE eDocument: File

EDOSRCFILE eDocument: File

EDOMSGCONTROL eDocument Message Control Attributes

EDOMSGDATA eDocument Message Content Data

EDOMSGHISTORY eDocument Message History

The system also considers country-specific tables defined in the EDOTYPEV (eDocument: Type) and
EDOTYPETABV (Document: Additional eDocument Type-Specific Tables).

The EDOCUMENT archiving object supports the Information Lifecycle Management (ILM) functions for data
destruction. You can use the Information Retention Manager (IRM) to define the rules for retaining data. When
running the write program of the archiving object, the system performs checks to evaluate these rules and
determines which of the selected data can be destroyed. The data is temporarily written to an archive file. After the
write phase, the associated delete program deletes the data from the database and the archive.

eDocument for Italy

eDocument for Italy PUBLIC 9
The following programs are available for EDOCUMENT:

Table 6: Programs

Program Function

EDOCUMENT_WRI Write program of the archiving process

EDOCUMENT_DEL Delete program of the archiving process

EDOCUMENT_REL Reload program of the archiving process

Prerequisites

You are familiar with the basics of the destruction of data and have made the following settings in particular:

● You have activated Information Lifecycle Management (ILM).

● You are familiar with the functions for ILM policies and rules and have defined the retention rules for the
archiving object.

1.2.4 Deletion and Blocking of Customer and Vendor Data in

SAP eDocument

SAP eDocument supports the simplified blocking and deletion of customer or vendor master based on SAP
Information Lifecycle Management (ILM) and using the EDOCUMENT archiving object.

SAP eDocument supports the simplified blocking and deletion of customer or vendor master based on SAP
Information Lifecycle Management (ILM) and using the EDOCUMENT archiving object. For more information, see
SAP Note 2007926.

Prerequisite

The existence of business partner information in the eDocument is a prerequisite for the archiving of the
eDocuments. To keep your data ready for the archiving, SAP recommends to run the Update eDocument Business
Partner Table (EDOC_UPDATE_EDOBUPA) program regularly in your system. This program assigns the eDocuments
to the business partners, customer or vendor, that are involved in the business transaction that generated the
eDocument.

eDocument for Italy

10 PUBLIC eDocument for Italy
Handling of blocked customer or vendor in SAP eDocument

If a customer or a vendor is blocked, the eDocument specific data is masked in the eDocument Cockpit and it is
not possible to execute any action on the respective eDocuments. The system peroforms this function if the
following is met:

● eDocument has the status completed (green icon in the eDocument Cockpit).
● For the eDocument the customer or vendor data is stored in the eDocument database table, or
● An eDocument file created by the Application Interface Framework exists.

For more information, see the SAP Note 2594642 .

1.3 Implementation Considerations for eDocument in AIF -

Italy

Definition

You use the SAP Application Interface Framework (AIF) to map the transactional data into the legally required XML
for each country. This is relevant if you have implemented one of the solutions: eDocument Full solution or the
eDocument using Customer-Specific Comunication Capabilities.

Note
For information about implementation and upgrade steps for AIF, see SAP Note 2071823

To integrate both SAP system and SAP AIF, you perform some steps which are generic for all countries:

● 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
with the SAP Note 2010697 doing the following:
1. Use the SCPR3 transaction to upload the BC sets.
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.

● Make Italy-specific AIF settings

You create and activate BAdI implementations and customizing entries that are specific for Italy. For more
information, refer to the SAP Note 2026905 :
● Install Italy-specific BC sets
You upload and activate the Italy-specific BC sets delivered with SAP Note 2018361 relevant for the
FatturaPA 1.0 version and additionally the SAP Note 2118196 relevant for the FatturaPA 1.1 version. These
BC sets automatically install in your system interfaces that contain the namespace /EDOIT, as well as all

eDocument for Italy

eDocument for Italy PUBLIC 11
 customizing and structure mappings necessary for this country. You create mapping value tables using the
transaction /AIF/VMAP.

Note
The eDocument solution for Italy supports multiple versions of the FatturaPA XML. If you implement the
eDocument Basic solution, ensure that your customer-specific implementation handles the different
versions of the FatturaPA XML.

The SAP Note 2005415 provides you with technical information about setting up the system.
● Maintain value mappings
After you have activated the BC sets in your system, in the /AIF/V MAP transaction, for the namespace /
EDOIT maintain the following value mappings:
○ For FatturaPA 1.0
○ Map Fattura-specific values to the document types to GET_DOCUMENT_TYPE.
○ Map tax codes used in your system to GET_NATURA_CODE
○ Map payment methods used in your system to GET_PAYM_TERMS
○ Map document types to information necessary for the reverse chargeGET_REVERSE_CHARGE
See the SAP Note 2018361 for details on how to maintain the mapping.
○ For FatturaPA 1.1:
Additionally to the mapping above described, you need for FatturaPA1.1 the following mapping:
○ Map Fattura-specific values to the document types to GET_DOCUMENT_TYPE.
○ Map tax codes used in your system to GET_NATURA_CODE
See the SAP Note 2118196 for details on how to maintain the mapping.

Invoice splitting

Invoice splitting means that your customer pays the VAT directly to the tax authorities instead of paying it to you.
In this case, the VAT is deducted from the amount due by your customer. If you want to use this feature, you map in
AIF that the VAT chargeability XML field (EsigibilitaIVA) is defined as invoicing splitting. See SAP Note 2137074
for more details on how to do the mapping.

Note
This feature is only valid for FatturaPA 1.1 version.

1.4 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.

Note
The eDocument Cockpit replaces the Create and Submit eDocument report (EDOC_RESUBMIT_EDOCUMENT
transaction). While the latter is still available for you in the system, enhancements will be made available only in

eDocument for Italy

12 PUBLIC eDocument for Italy
 the Cockpit. Therefore, SAP recommends you to migrate your current country implementations to the Cockpit.
For information on the migration, see the SAP Note 2293306 .

Most actions you perform on eDocuments are done in the same way in both above mentioned programs.

1.4.1 eDocument Status and Actions

During its processing, the eDocument statuses changes many times. You can see the current process status of the
eDocument in the eDocument Cockpit. Some statuses require that you take actions, while others are only
technical and temporary. The table below summarizes the existing statuses and the required actions for
eDocument.

Table 7:

Status Description Action

CREA eDocument created This is the initial status of an eDocument

once it has been created in the system.
The following actions are possible:

● Cancel the eDocument. You can ei­

ther manually reverse/cancel the
source document in the source ap­
plication or create a new eDocument
for it later. See Cancelling an eDocu­
ment [page 16]
● Submit the eDocument to SDI. See
Creating and Submitting an eDocu­
ment [page 14]

SNRQ Sending requested This status informs you that the eDocu­
ment has not reached the interface.

You can resubmit the eDocument in the

eDocument Cockpit.

eDocument for Italy

eDocument for Italy PUBLIC 13
Status Description Action

SEND Sent to interface This is the status after you have re­
quested the submitting of the eDocu­
ment. The eDocument has been sent to
SDI but the response from the tax author­
ities could not be successfully processed
in the system. You can do the following:

● Restart the AIF response interface to

synchronize the systems and reproc­
ess the response. For an eDocument,
double-click on Interface Message
GUID column to be directed to the
AIF Error Monitor.
● Cancel the eDocument. You can ei­
ther manually cancel the source
document in the source application
or create a new eDocument for it
later. See Cancelling an eDocument
[page 16]

CANC Cancelled The eDocument is cancelled and no user

actions can be performed anymore.

Note
The source document is not automati­
cally cancelled. To keep the consis­
tency in your system, cancel the
source document manually in its
source application.

1.4.2 Creating and Submitting an eDocument

Use

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

eDocument for Italy

14 PUBLIC eDocument for Italy
Procedure

1. Run the eDocument Cockpit to display eDocuments according to your selection.

To access the Cockpit, on the SAP Easy Access screen, choose Cross-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 Components
General Application Functions eDocument General Settings

2. Select the document and choose Submit.

The subsequent processes performed by the system or by you vary depending on the eDocument solution that
you have implemented in your system. Refer to the documentation direct in the Cockpit for more information on
the available actions.

1.4.3 Deleting an eDocument

Context

You use the eDocument Cockpit report to delete eDocuments that have not yet been submitted to the tax
authorities. The source document is not deleted in this action. You can create a new eDocument for this source
document at a later time. If you want to cancel the source document too, you have to 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.

eDocument for Italy

eDocument for Italy PUBLIC 15
Results

The system deletes only the eDocument record from the database.

1.4.4 Resubmitting an eDocument

Use

You can resubmit eDocuments if it they have not reached the interface yet (SNRQ process status).

For more information about the possible status an eDocument may have and the respective actions you can
perform, see eDocument Status and Actions. [page 13]

Procedure

1. Select an eDocument in the output screen of the Create and Submit eDocument report (EDOC_COCKPIT).
2. Go to eDocument Resubmit .

The system submits the eDocument once more to the tax authorities.

More Information

Refer to the application help documentation directly in the report for more information.

1.4.5 Cancelling an eDocument

Use

You can cancel eDocuments in the following circumstances:

● You have created the eDocument but not yet submitted it to the tax authorities (CREA process status).
● The system has requested the sending of the eDocument to the interface but this action failed (SNRQ process
status).
● The system has sent the eDocument to the interface but there is no acknowledgment from the tax authorities
yet (SEND process status).

For more information about the possible status an eDocument may have an the respective actions you can
perform, see eDocument Status and Actions. [page 13]

eDocument for Italy

16 PUBLIC eDocument for Italy
Procedure

1. Select an eDocument in one of the programs and proceed as follows:

○ In the eDocument Cockpit (EDOC_COCKPIT): Go to More... Cancel eDocument
report.
2. In the Create and Submit eDocument (EDOC_RESUBMIT_EDOCUMENT):
Go to eDocument Cancel/Void eDocument
3.

The system cancels the eDocument.

Recommendation
To keep the data consistent in your system, ensure that you revert/cancel the corresponding source document
manually. You can access the source document by double clicking on the value in the eDocument Source Key
column. You can check in the Src.Canc. (Source Document Cancelled) column if a source document has already
been cancelled or not.

More Information

Refer to the documentation directly in the report for more information.

1.4.6 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 XML
that was sent out from the system to the tax authorities' systems, or it can be the XML 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.

1.4.7 Downloading an eDocument

Definition

Once you have created your eDocuments, you can download the XML 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

eDocument for Italy

eDocument for Italy PUBLIC 17
documents you want to download to your file system. Choose Export File. The files are exported in XML 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 XML format
required by the tax authorities of a given country. You still need to map the fields to the legally-required XML.

More Information

For more information, see the Application Help documentation directly in the report.

eDocument for Italy

18 PUBLIC eDocument for Italy
Important Disclaimers and Legal Information

Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.

Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a
binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not
apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see:
http://help.sap.com/disclaimer).

eDocument for Italy

Important Disclaimers and Legal Information PUBLIC 19
go.sap.com/registration/
contact.html

© 2017 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 http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.