Enabling Automatic Creation of eDocument in Source Applications

For eDocuments to be created upon creation of source documents, ensure that you have set up the following in your system:

For Finance Accounting (FI) Source Documents

You register function modules for the EDOC application as well as events 1025 and 1030.

For Sales and Distribution (SD) Source Documents

Maintaining XML Destination in Customer Master Data

For customers that have to be invoiced electronically, maintain in their master data the field Tax Number Field 5 (STCD5) the following destinations in the (use XD03 transaction and go to Control Data tab):

If multiple destinations apply for an eDocument, the information you enter in the Tax Number Field 5 (STCD5) is concatenated to a key. For examples and hints on how to enter the destinations, refer to the SAP Note 2028454.

Maintaining Customers’ Web Service Address

If the customer has a web service available for receiving electronic documents, ensure that you enter this value in the communication method ‘SSF’ of that customer.

Example: SSF-ID: <"webservice address">

Notes: ‘ES_INV_WS’ (this value is used to identify that address as a Webservice for eInvoices for Spain). If this field is not maintained, then the systems uses the manual process for that customer (manual download/upload of eDocuments).

Enabling eDocument Status Processing

You can enhance your Basic solution for Spain by implementing theTRIGGER method of the EDOC_INTERFACE_CONNECTOR BAdI defined in the ES_EDOCUMENT enhancement spot to enable the use of actions in the Create and Submit eDocument report (EDOC_COCKPIT transaction).

The table below summarizes the process steps that are triggered by the system when you perform the respective actions in the report.

Refer to the BAdI implementation and methods documentation available direct in the system for more information. For tips and hints on how to implement the BAdIs for enhancing the Basic solution for Spain, see SAP Note 2080683.