Documentation

Transaction EDOC_RESUBMIT

© 2014 by SAP AG. All rights reserved.

SAP and the SAP logo are registered trademarks of SAP AG in Germany and other countries. Business
Objects and the Business Objects logo are trademarks or registered trademarks of Business Objects
Software Ltd. Business Objects is an SAP company.
Sybase and the Sybase logo are registered trademarks of Sybase Inc. Sybase is an
SAP company.
Short text
Create and Submit eDocument

Purpose
You use this report to generate eDocuments for the source documents created in Financial Accounting (FI) and
Sales and Distribution (SD) and submit them in the required XML format to the tax authorities or to your business
partners.

The process for eDocument generation and transmission of XML file to external systems varies depending on the
country and the eDocument solution you have implemented in your system. For more information about features
and country availability of each solution, see the application help for eDocuments at www.help.sap.com under SAP
ERP -> (select release of SAP ERP) > Application Help (select English) -> SAP ERP Central Component ->
Accounting or Logistics-> Country Versions -> (select country)>Cross Application Functions -> eDocument.

Report Processing Steps

Once you made your settings in the selection screen and run the report, the system performs the following actions:

1. Checks if the source documents you specified in the selection screen are valid source documents for
the generation of eDocuments for the country in question.
2. Checks which interface you have defined in the customizing activity Define Interface Type
3. When you trigger the creation of an eDocument, the system creates an instance for this eDocument in
the database.
4. Once you submit the eDocument to the external systems (tax authorities' or business partners'
systems) the report calls the interface connector through the implementation of the eDocument Interface
connector BAdI (EDOC_INTERFACE_CONNECTOR). The BAdI deploys the process variant depending
on the interface you have defined for your system:

 Process variant 1: Interface that connects to customer-specific implementation

a) The interface connects to the customer-specific solution you have implemented to map the
source document fields to the legally required XML format and to communicate with external
systems for the transmission of the XML files over to the external systems of tax authorities or
business partners.
b) The system stores the generated XML and updates the eDocument status in the database.

 Process variant 2: AIF_XML Connector interface

a) The system maps the source document fields to the legally required XML format.
b) You can export the eDocuments from SAP ERP to your file system. You implement your own
solution for the further processing of the eDocuments, like the communication and the sending of
the XML files over to the external system.
c) The system stores the generated XML and updates the eDocument status in the database.

 Process variant 3: AIF_PROXY Connector interface

a) The system maps the source document fields to the legally required XML format.
b) The system stores the generated XML and updates the eDocument status in the database.
c) The system establishes communication with external systems for the transmission of the XML
files using web services.

Prerequisites
You have done the general customizing for eDocuments in the SAP Customizing Implementation Guide under
Cross-Application Components -> General Application Functions -> eDocument.

Copyright/Trademark
Because each country has different legal requirements, ensure that you have implemented all necessary support
packages and/or all relevant SAP Notes for each country in your system. For more information, see the application
help for eDocuments at www.help.sap.com under SAP ERP -> SAP ERP Central Component -> (Select release of
SAP ERP) ->SAP ERP Cross-Application Functions->Cross Application Components -> eDocument.

Selection
You can select eDocuments for one company code at a time. To narrow down your selection, use one or more
selection parameters, as described below:

 eDocuments data: You specify if you want to select an existing eDocument by GUID, by date, or by user
that created the document.

 eDocuments created from billing documents: You specify the number of the billing document and/or its
creation date.

 eDocuments created from accounting documents: You specify the number of the accounting document,
its fiscal year, or its posting date.

 Other options: You can filter the documents by their status, that is, documents which have been either
successfully processed, or which have errors, or which have not been created, or which have not been
sent to the interface yet. Multiple selections are allowed.

If you check the Automatically send pending eDocuments to the interface checkbox, the system ignores any other
selection you have done before and only selects eDocuments that are still to be submitted to the tax authorities.
Once you run the report, the interface connector is automatically triggered for each eDocument. You can use this
option when you schedule the program as a periodic job.

Output
The report displays the collected eDocuments in accordance with your selection screen settings as follows.

The ALV list displays the result in lines using different colors. The combination of the value in the eDocument
GUID column and the color of the cell has different meanings:

N/A + green shading: The source document is not relevant for the eDocument solution. You cannot create an
eDocument for this source document.

<INITIAL> + yellow shading: No eDocument was found for the source document. You can create an eDocument
for this document.

<INITIAL> + red shading: No eDocument was found for the source document, but you cannot create an
eDocument for it because there are errors.

eDocument GUID + green shading: The eDocument has been created and the interface connector has been
triggered successfully.

eDocument GUID + yellow shading: The eDocument has been created but the interface connector has not been
triggered yet. You can resubmit the eDocument to the tax authorities.

eDocument GUID + red shading: The eDocument has been created with an error or there was an error while
triggering the interface connector. You can resubmit the eDocument to the tax authorities.

Activities
In the output screen, you can perform the following activities, depending on the result of your search:

Copyright/Trademark
  Create an eDocument: Select one or more yellow lines with value <INITIAL> in the eDocument GUID
column and click Create.

 Submit an eDocument that has no yet t been submitted to the tax authorities or resubmit a document that
has had problems during the triggering the interface connector: Select one more yellow or red lines that
have an eDocument GUID value and click Submit.

 Resubmit a document to the tax authorities: You can resubmit a eDocument has been rejected by the tax
authorities due to inconsistencies in its master data, for instance. You correct the issues in the master
data and save the source document. After that, in the report, you select the eDocument in question and
go to eDocument menu and click Resubmit. Important note: If you resubmitt an eDocument, the system
overwrites the old XML file by a new one.

 Delete an eDocument: Select one or more eDocument that has not yet been submitted to the tax
authorities and click Delete. Note: Only the eDocument record is deleted from the database. To delete the
corresponding source document do it in the source application where this document has been created.

 Display the errors that occurred during the eDocuments generation: Select Display Log.

 Display the errors that occurred during the triggering of the interface connector: Select Display Interface
Log.

 Export the XML files to your file system: Select one or more green lines that have an eDocument GUID
value and click Export File.

Country-Specific Activities
Some activities are only available for certain countries, provided the prerequisites are met.

Chile

 Get status of eDocument from the authorities: By clicking Tax Authorities button, the system calls the
implementation you have done in the TRIGGER method of the eDocument Interface Connector BAdI to
update the eDocument with the current status provided by the tax authorities. The status is displayed in
the eDoc Status column of the output screen of the report.

 Update status of eDocument from customers: By clicking Customer, the system calls the
implementation you have done in the TRIGGER method of the eDocument Partner Connector BAdI
(EDOC_PARTN ER_CONNECTOR) BAdI to update the eDocument with the current status provided by
the customers. The status is displayed in the eDoc Status column of the output screen of the report.

Chile and Peru

 Send eDocument to Customer: By clicking the Send to Customer button the system calls the
implementation you have done in the TRIGGER method of the eDocument Partner Connector BAdI
(EDOC_PARTNER_CONNECTOR) to send the eDocument to customers.

Copyright/Trademark