SAP Note 3141469

eDocument – EU eInvoicing: External Files

Configuration and Customizing

Manual Activities _

© 2022 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.
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. Please
see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. 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 SE or its affiliated companies shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP SE 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein.
This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may
be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality.
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.

Copyright/Trademark
1. Logical path definition
1.1. Go to the FILE transaction.
1.2. Press the New entries button.
1.3. Enter the values as below (replace <XX> for the country code you are implementing):
Logical file path Name
EDOC_<XX>_EXT_FILE_UPLOAD_PATH eDocument <XX>: External File Upload
EDOC_<XX>_EXT_FILE_ARCHIVE_PATH eDocument <XX>: External File Archive
Example:
Logical file path Name
EDOC_DE_EXT_FILE_UPLOAD_PATH eDocument DE: External File Upload
EDOC_DE_EXT_FILE_ARCHIVE_PATH eDocument DE: External File Archive
1.4. Select the newly created line and press Assignment of Physical Paths to Logical Path from the
menu on the left side.
1.5. Press the New entries button.
1.6. Enter UNIX for the Syntax group field.
1.7. In the Physical path enter the application server path where the XML files from the external
systems will be uploaded.
Example: /usr/sap/<SYSID>/SYS/src/<FILENAME>
Note: Use different physical paths for upload and archive.
1.8. Save your entries.
1.9. Select the Logical File Name Definition, Cross-Client from the menu on the left.
1.9.1. Press New entries.
1.9.2. Enter the following values (replace <XX> for the country code you are implementing):
Log. file EDOC_<XX>_EXT_FILE_UPLOAD_PATH
Name eDocument <XX>: External File Upload
Physical file
Data format DIR
Applicat. Area BC
Logical path EDOC_<XX>_EXT_FILE_UPLOAD_PATH

Log. file EDOC_<XX>_EXT_FILE_ARCHIVE_PATH

Name eDocument <XX>: External File Archive
Physical file
Data format DIR
Applicat. Area BC
Logical path EDOC_<XX>_EXT_FILE_ARCHIVE_PATH
1.9.3. Save your entries.

Copyright/Trademark
2. Activate Source Document Types per Company Code
2.1. In Customizing for Cross-Application Components, choose General Application Functions->
eDocument-> General Settings-> Activate Source Type Documents for Company Code
(EDOCOMPANYACTIV).
2.2. Choose the New Entries pushbutton.
2.3. Make an entry for each company code and source document combination that you want to
activate:
Company Code Source Type Active
<Company_Code> SRC_FILE X
2.4. Save your entries.

3. Define Interface Type per eDocument Type

This configuration step is used to define the interface type that is used for an eDocument. You
must define the interface type per company and eDocument type.
3.1. In Customizing for Cross-Application Components, choose General Application Functions
->eDocument-> General Settings-> Define Interface Type for eDocument (EDOINTTYPEV).
3.2. Choose the New Entries pushbutton.
Make an entry for each company code and eDocument type combination that you want to
activate.
Company Code eDoc Type Type Description Interface Type
<Company_Code> <XX>_CREEX <Country> External Credit Note (see point 3.3)
<Company_Code> <XX>_INVEX <Country> External eInvoice (see point 3.3)
Note: eDocument Types start with “<Country_Code>_” + “CREEX” or “INVEX”. For special cases and
exceptions please refer to point 12. of this document.
3.3. In the Interface Type column, select the interface type according to the solution that you are
implementing:
· Full solution in SAP_APPL: Select AIF_PROXY - AIF proxy (for web services).
· Full solution in S4CORE: Select STANDARD - Standard implementation using AIF.
Example:
Company Code eDoc Type Type Description Interface Type
DE01 DE_CREEX Germany External Credit Note STANDARD
3.4. Save your entries.

4. Maintain Process Step Interface Determination

4.1. Go to transaction SM30
4.2. Enter EDOPROCSPINTDETV in the Table/View field.
4.3. Choose the Edit/Maintain push button.
4.4. Choose the New Entries push button.
4.5. Enter the values as below (replace <XX> for the country code you are implementing):

Copyright/Trademark
 eDoc. Vers Proc. Step eDoc Type Source Proc.Step Interface ID
Process Type Variant
EUINV 1 REQ_SEND <XX>_INVEX UBL_SEND_GENERIC_REQUEST
EUINV 1 REQ_SEND <XX>_CREEX UBL_SEND_GENERIC_REQUEST
EUINV 1 SENDEDOC <XX>_INVEX UBL_SEND_GENERIC_REQUEST
EUINV 1 SENDEDOC <XX>_CREEX UBL_SEND_GENERIC_REQUEST

Note: eDocument Types start with “<Country_Code>_” + “CREEX” or “INVEX”. For special cases
and exceptions please refer to point 12. of this document.
Example:
eDoc. Vers Proc. Step eDoc Type Source Proc.Step Interface ID
Process Type Variant
EUINV 1 REQ_SEND DE_INVEX UBL_SEND_GENERIC_REQUEST
4.6. Save your entries.

5. Maintain Process Step Determination: Interface shall execute this step

5.1. Go to transaction SM30
5.2. Enter EDOPROCSTEPDETV in the Table/View field.
5.3. Choose the Edit/Maintain push button.
5.4. Choose the New Entries push button.
5.5. Enter the values as below (replace <XX> for the country code you are implementing):
eDoc. Vers Interface ID eDoc Type Source Proc. Step
Process Type
EUINV 1 UBL_SEND_GENERIC_REQUEST <XX>_INVEX SENDEDOC
EUINV 1 UBL_SEND_GENERIC_REQUEST <XX>_CREEX SENDEDOC
EUINV 1 UBL_SEND_GENERIC_RESPONSE <XX>_INVEX PROC_RESP
EUINV 1 UBL_SEND_GENERIC_RESPONSE <XX>_CREEX PROC_RESP
Note: eDocument Types start with “<Country_Code>_” + “CREEX” or “INVEX”. For special cases and
exceptions please refer to point 12. of this document.
Example:

eDoc. Vers Interface ID eDoc Type Source Proc. Step

Process Type
EUINV 1 UBL_SEND_GENERIC_REQUEST DE_INVEX SENDEDOC
5.6. Save your entries.

6. Maintain Mapping Class Determination

6.1. Go to transaction SM30
6.2. Enter EDOMAPCLASSDETV in the Table/View field.
6.3. Choose the Edit/Maintain push button.
6.4. Choose the New Entries push button.
6.5. Enter the values as below (replace <XX> for the country code you are implementing):

Copyright/Trademark
 eDoc. Vers Interface ID eDoc Type Source Mapping Class
Process Type
EUINV 1 UBL_SEND_GENERIC_REQUEST <XX>_INVEX CL_EDOC_MAP_UBL_FILE
EUINV 1 UBL_SEND_GENERIC_REQUEST <XX>_CREEX CL_EDOC_MAP_UBL_FILE
EUINV 1 UBL_SEND_GENERIC_RESPONSE <XX>_INVEX CL_EDOC_MAP_UBL_FILE
EUINV 1 UBL_SEND_GENERIC_RESPONSE <XX>_CREEX CL_EDOC_MAP_UBL_FILE
Example:
eDoc. Vers Interface ID eDoc Type Source Mapping Class
Process Type
EUINV 1 UBL_SEND_GENERIC_REQUEST DE_INVEX CL_EDOC_MAP_UBL_FILE
6.6. Save your entries.

7. Maintain eDocument Interface Version

Note: This step is only valid for all SAP_APPL releases and S4CORE releases 100 to 104.
7.1. Go to transaction SM30
7.2. Enter EDOINTVERSIONV in the Table/View field.
7.3. Choose the Edit/Maintain push button.
7.4. Choose the New Entries push button.
7.5. Enter the values as below:
Interface ID Vers Version Description Active From
UBL_SEND_GENERIC_REQUEST 1 Original version <date>
UBL_SEND_GENERIC_RESPONSE 1 Original version <date>
7.6. Save your entries.

8. Assign AIF Interface and Version to ERP Interface

8.1. Go to transaction SM30
8.2. Enter EDOINTAIFV in the Table/View field.
8.3. Choose the Edit/Maintain push button.
8.4. Choose the New Entries push button.
8.5. Enter the values as below:
Interface ID Vers AIF Namespace AIF Interface AIF Version
UBL_SEND_GENERIC_REQUEST 1 /EDUBL GENPRX 1
UBL_SEND_GENERIC_RESPONSE 1 /EDUBL GENPRXR 1
8.6. Save your entries.

9. Assign SOA Service Name to Logical Port

Note: You may choose your own names for the SOA Service and Logical Port, as long as you ensure they
match in EDOINTV and SOAMANAGER respectively.
9.1. Go to transaction SM30
9.2. Enter EDOSOASERV in the Table/View field.
9.3. Choose the Edit/Maintain push button.
9.4. Choose the New Entries push button.
9.5. Enter the values as below:
SOA Service Name CoCd Logical Port
<EU_GENERIC_WEBSERV> <Company_Code> <EDO_EU_GENERIC_WEBSERV>

Copyright/Trademark
 9.6. Save your entries.

10. Assign Interface to SOA Service

10.1. Go to transaction SM30
10.2. Enter EDOINTV in the Table/View field.
10.3. Choose the Edit/Maintain push button.
10.4. Choose the New Entries push button.
10.5. Enter the values as below:
Interface ID SOA Service Name 10.6. Save your entries.
UBL_SEND_GENERIC_REQUEST <EU_GENERIC_WEBSERV>
11. Create logical port in
SOAMANAGER
11.1. In your ERP or SAP S/4HANA system, go to transaction SOAMANAGER and select Web
Service Configuration.

11.2. Search for the consumer proxy CO_DCS_DCP_GENERIC_WEBSERVICE

11.3. In the result list, select the proxy and choose Create > Manual Configuration.

Copyright/Trademark
11.4. Enter the Logical Port Name and a Description:

Note: The Logical Port name must be the same one that was assigned to the SOA Service in point 9
of this document.
11.5. The Consumer Security tab page configuration depends on the security being used for the
SAP ERP or SAP S/4HANA - SAP CLOUD PLATFORM INTEGRATION communication:
 If you use basic authentication, select the User ID / Password radio button and enter
the username and password.
 If you use certificate-based authentication, select the X.509 SSL client certificate radio
button and ensure that the required certificates are available in transaction STRUST.
Example:

Copyright/Trademark
11.6. On the HTTP Settings tab page, make the following entries:
Note: The screenshots may look slightly different in your system depending on the release,
but all the required fields should be available.

Enter the appropriate values in the fields above according to the information below:
 Host:
Environment Host
Test l100468-hcioem.hcisbp.eu1.hana.ondemand.com
Productive l90003-hcioem.hcisbp.eu1.hana.ondemand.com
Test (EU only)* s2202-hcioem.hcisbt.eu2.hana.ondemand.com
Productive (EU only)* y2321-hcioem.hcisbp.eu2.hana.ondemand.com
 Port: 443 is the standard port for the HTTPS protocol.
 Path: /cxf/PeppolSendGenericRequest
Example:

Copyright/Trademark
 11.7. In the Messaging tab page, set Message ID Protocol to Suppress ID Transfer.

11.8. No settings required in the tabs Identifiable Business Context and Operation Settings. Just
select Next and then Finish.

12. eDocument Types: Special Cases and exceptions:

12.1. eDoc Types for France:
 FR_EUINVEX: France External eInvoice
 FR_EUCREEX: France External Credit Note
12.2. eDoc Types for Poland:
 PL_INVEX: Poland External eInvoice
 PL_INV_COREX: Poland External Credit Note
12.3. Additional eDoc Types for countries with self-billing:
 <XX>_INVSBEX: <Country> External Self-Billing eInvoice
 <XX>_CRESBEX: <Country> External Self-Billing Credit Note
Example: NZ_INVSBEX: New Zealand External Self-Billing eInvoice

Copyright/Trademark