You are on page 1of 9

www.sap.

com

eDocument: Invoice transmission for Colombia


ERP SOAMANAGER and SAP Cloud Platform Integration
Set-Up

© 2014 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.
TABLE OF CONTENTS
1 PREREQUISITES .............................................................................................................................. 3
2 SECURE CONNECTION................................................................................................................... 3
3 GENERAL INFORMATION ............................................................................................................... 3
4 SETUP STEPS .................................................................................................................................. 4
4.1 Deploy the certificate and the credentials to the SAP CLOUD PLATFORM INTEGRATION
tenants 4
4.2 Copy integration flows .................................................................................................................... 4
4.3 Deploy integration flows on test/productive tenants ................................................................... 5
4.4 Create the logical ports in SAP ERP or SAP S/4HANA SOAMANAGER .................................... 5
5 TESTING ........................................................................................................................................... 8
The communication part of the eDocument Full Solution for processing electronic transport registrations in Colombia is
taken care of by SAP Cloud Platform Integration. In order to get SAP Cloud Platform Integration working, there are some
required steps on both the ERP system and the SAP Cloud Platform Integration tenant.
These steps are typically taken care by an SAP Cloud Platform Integration consulting team, who is responsible for
configuring the ERP-SAP Cloud Platform Integration connection and maintaining the integration content and
certificates/credentials on the SAP Cloud Platform Integration tenant.

1 PREREQUISITES

Before you start with the activities described in this document, ensure that the following prerequisites are met.
1) eDocument Colombia Full Solution: All relevant notes are installed in the test and/or productive systems (see note
2330040 for an overview of which notes are required for the Full Solution).
2) Registration at DIAN is completed and the following data is available:
a. Certificate used for digital signature (Private Key + Password).
For more information, go to DIAN’s web page, section “Factura electrónica”-> “Información técnica” and
look for document “Anexo Técnico 002. Política de Firma de los Documentos XML de Facturación
Electrónica"
b. Range number approved.
c. User ID and password to connect to DIAN.
The authentication data needed from DIAN is described in page 6 of the document provided by
goverment: go to DIAN’s web page, section “Factura electrónica”-> “Información técnica” and look for
document “Anexo Técnico 005. Servicio de Recepción de Facturas Electrónicas”
Follow the steps to generate the registration in DIAN: go to DIAN’s web page, section “Factura electrónica”->
“Información técnica” and look for document “Guía de Usuario Externo Facturador Electrónico”.
3) SAP Cloud Platform Integration test/productive tenants are live.
4) You have configured the connection from ERP to SAP Cloud Platform Integration. Please refer to the following
document: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4037b5a5-47a5-3110-e891-
f3d9dbafbe86.

2 SECURE CONNECTION

You have configured the secure connection between SAP ERP OR SAP S/4HANA and SAP CLOUD PLATFORM
INTEGRATION. More reference information can be found in Application Help for SAP Cloud Platform Integration.

Note: The above listed link is maintained by the SAP Cloud Platform Integration team. If you encounter any issue in the
linked documentation, please open a support ticket against the component LOD-HCI-PI-OPS.

3 GENERAL INFORMATION

The package eDocument: Electronic Invoice for Colombia contains the following iFlow:
iFlow Name in WebUI Project Names / Artifact Names
Send Invoice com.sap.GS.Colombia.GenericInvoice
4 SETUP STEPS

Perform the following steps to set up the iFlows.

4.1 Deploy the certificate and the credentials to the SAP CLOUD PLATFORM INTEGRATION
tenants

1. Deploy the certificate (as private key with alias) in the tenants JAVA_KEYSTORE.
To allow the iFlows to be updated with minimal adaptation effort, the alias used for the private key should be as
follows:
• Private Key alias: colombiasignaturekey
Note: If you deploy the private key with another alias, you need to configure the alias name in the iFlow
parameters. Please refer to section 4.2 for how to configure the alias name.
2. Deploy the public certificate which is generated in the point a of PREREQUISITE step into the tenants
JAVA_KEYSTORE.
3. Add User ID and password to connect to DIAN the Security Material with the alias “colombiawscredentials”.
Add -> User Credentials

Complete the information related to your credentials provided by DIAN

4.2 Copy integration flows

Copy all iFlows in the package eDocument: Electronic Invoicing for Colombia to the target tenant as follows:
1. In your browser, go to the WebUI of the tenant (URL: <Tenant URL>/itspaces/#shell/catalog).

2. From the menu in the upper left corner, choose Discover.

3. Go to tab page ALL.


4. In the search field, enter eDocument: Electronic Invoicing for Colombia package and press ENTER.

5. Select the package and in the upper right corner, choose Copy.

4.3 Deploy integration flows on test/productive tenants

To deploy an iFlow in the WebUI, select it and choose Deploy. After all the iFlows are deployed, you note down the URLs
of the endpoints for each service.

4.4 Create the logical ports in SAP ERP or SAP S/4HANA SOAMANAGER

The proxy must be connected to the SAP CLOUD PLATFORM INTEGRATION tenant via logical port. In the SAP ERP or
SAP S/4HANA test system, the logical ports are configured to connect to the test tenant. In the productive SAP ERP or
SAP S/4HANA system, the logical ports are configured to connect to the productive SAP CLOUD PLATFORM
INTEGRATION tenant.
1. In your SAP ERP or SAP S/4HANA system, go to transaction SOAMANAGER and select Web Service
Configuration.

2. Search for the proxies for Colombia with the search term CO_EDO_CO_*.

The following table lists the proxies and the logical port name, description and path for each proxy.
Note: The proxy names have been changed with Integration Package 1.1.0.
Proxy Name Logical Port Name Description Path
CO_EDO_CO_INVOICE_V1_0 EDO_CO_INVOICE_TRANSM_SERV_PORT Colombia /cxf/ColombiaGenericInvoice
eDocument -
Invoice
Transmission
Service

CO_EDO_CO_DEBIT_NOTE_V1_0 EDO_CO_DEBIT_NOTE_TRANSM_SERV_PORT Colombia /cxf/ColombiaGenericInvoice


eDocument –
Debit Note
Transmission
Service

CO_EDO_CO_CREDIT_NOTE_V1_0 EDO_CO_CREDIT_NOTE_TRANSM_SERV_PORT Colombia /cxf/ColombiaGenericInvoice


eDocument –
Credit Note
Transmission
Service

3. In the result list, select a proxy and create logical port(s) for each proxy. Choose Create > Manual Configuration.

4. Enter the Logical Port Name and a Description.

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.
a. If you use basic authentication, select the User ID / Password radio button and enter the User Name and
Password.
b. 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.
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:
• Port 443 is the standard port for the HTTPS protocol.

• To find the Host, go to Cloud Platform Integration Web UI, choose Operations View and under

Managed Integration Content go to All. Use the search to find your iFlow as in the screen shot below:
• The entries for the Proxy fields depend on your company’s network settings. The proxy server
is needed to enable the connection to the internet through the firewall.
7. In the Messaging tab page, set Message ID Protocol to Suppress ID Transfer.

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

5 TESTING

To test the communication, the best way is to create and send an eDocument from SAP ERP or SAP S/4HANA. How you
can achieve this depends on how the system is configured to generate and send eDocuments. Follow these steps:
1) Check if all relevant notes for the eDocument Full Solution for Colombia are installed and all the manual
configuration steps were performed (see section 1).
2) Create a relevant document for eDocument for Colombia (for example an invoice).
Note: If the system is configured to generate an eDocument for the selected document type, an instance of the
eDocument will be created as soon as the document is posted (for example when you save an SD Billing
document).
3) Go to the eDocument Cockpit by running the transaction EDOC_COCKPIT.
4) Select from the Result Overview the process for the eDocument for Colombia and run the report.
5) Select the eDocument and choose Submit to trigger the communication with SAP Cloud Platform Integration.
The system displays on the right side of the Cockpit the eDocuments that match the search.
Note: You should see a list of eDocuments based on your selection. Find the one that you just created and check
the following:
• You can double-check if the message went through on the SAP Cloud Platform Integration tenant; or
you can use a trace from transaction SRT_UTIL to look at the XMLs transmitted via web services from
SAP ERP or SAP S/4HANA.
• You can double-click on the Interface Message GUID field to navigate to AIF and look at the log.
Communication errors will be displayed there.