SAP Note 2352299

eDocument Colombia: Configuration and

Customizing
Consulting

© 2016 by SAP SE. All rights reserved.

SAP and the SAP logo are registered trademarks of SAP SE 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.

1. Activate Source Document Types per Company Code

This table is used to decide if eDocuments must be created for the company. Per company and source
document type, the interfaces must be activated as follows:
1.1. Execute transaction SM30.
1.2. Enter EDOCOMPANYACTIV in the Table/View field.
1.3. Choose the Edit/Maintain push button.
1.4. Choose the New Entries push button
1.5. Make an entry for each company code and source document combination that you want to activate.
If you will use Colombia’s incoming process implementation, add the following source type:
Company code Source Type Active
<comp_code> SRC_FILE X

1.6. Select the Activate check box for each entry to activate it.
1.7. Save your entries.

2. Define Interface Type per eDocument Type

This table is used to define the interface type that is used for an eDocument. Per company and eDocument
type, the interface type must be defined.
2.1. Execute transaction SM30.
2.2. Enter EDOINTTYPEV in the Table/View field.
2.3. Choose the Edit/Maintain push button.
2.4. Choose the New Entries push button
2.5. Make an entry for each company code and eDocument type combination that you want to activate.

Note: All eDocument types for Colombia start with CO_*.

2.6. In the Interface Type column, select the interface type according to the solution that you are
implementing:
Basic Enablement: Select CUSTOM - Customer-specific
Full solution: Select AIF_PROXY - AIF proxy (for web services)
2.7. Save your entries.

3. Assign eDocument Type to Accounting Document Type

The accounting document types that are relevant for the electronic invoicing process in Colombia must be
maintained in a view. Every accounting document type maintained here will trigger the creation of an
eDocument with the type that is assigned to it.
3.1. Enter T003EDOCV in the Table/View field.
3.2. Choose the Edit/Maintain push button.
3.3. Enter CO in the Country column.
3.4. Choose the New Entries push button
Note:
Maintain the entries only for eDocument types: CO_INV, CO_CRE, CO_DEB
All eDocument types for Colombia start with CO_*.
3.5. Select the eDocument type mentioned above and assign the Document Type of the accounting
document.

Copyright/Trademark
3.6. Save your entries.

Note: You can use method CHANGE_EDOCUMENT_TYPE of BAdI EDOC_ADAPTOR to change the
eDocument determination settings you have done in this table. You can implement this method to define that
the combination of country and accounting document type is valid for two eDocument types, instead of for
only one eDocument type. In your implementation, you define how the system differentiates both
eDocuments types.

4. Define Number Ranges Intervals

4.1. Execute transaction SNRO.

4.2. Enter Object EDOC_CO and press Display.
4.3. Press Interval Editing push button
4.4. Put your Company Code here.
4.5. Press Intervals push button.
4.6. Define Intervals here filling out following columns: No, From No, To Number, Nr Status, Ext.
4.7. Save your entries.

5. Define Number Ranges

5.1. Execute transaction SM30.

5.2. Enter EDOCONUMBERV in the Table/View field.
5.3. Choose the Edit/Maintain push button.
5.4. Choose the New Entries push button.
5.5. Define range number according to the one No used in previous step.
5.5.1. Select: Company Code, VarKey, eDocument Type, Valid From, Valid To, No (No which you defined in
range intervals)
5.6. Save your entries.

Note: If a different number range should be used for different organizational entities, it is also possible to
implement the BAdI method GET_VARIABLE_KEY of BAdI EDOC_ADAPTOR. The return value of the BAdI
method is used in the variable key field VarKey of table EDOCONUMBER to determine the prefix and
number range for different organizational entities.

6. Assign the Approved Number Ranges

6.1. Execute transaction SM30.

6.2. Enter EDOCORANGESV in the Table/View field.
6.3. Choose the Edit/Maintain push button.
6.4. Choose the New Entries push button
6.5. Assign Company Code, No (No which you defined in range intervals), Prefix.
After you got approval from government that range was approved, fill rest of fields: Technical Key, Resolution
Number, Valid From, Valid To, Not Approved.

Note: For some document types, like Credit Memo or Debit Memo there are no approvals needed, therefore
the flag in field Not Approved can be set to X.

6.6. Save your entries.

7. Document filter

The following filtering of the documents is part of the delivery:

Copyright/Trademark
7.1. Document types
7.2. BAdI for additional filtering The BAdI name is EDOC_ADAPTOR. Per country, additional filtering can be
implemented within the IS_RELEVANT method. For instance, in case you want to prevent the creation of
eDocuments for Billing or Accounting Documents that were posted before the eDocument functionality was
implemented, you can set the changing parameter CX_RELEVANT equal to ABAP_FALSE and the
eDocument will not be created (you could check for example the field Invoice Date or Creation Date).

The data of the Billing or Accounting Document can be retrieved from the importing object IO_SOURCE
using the method IO_SOURCE->GET_DATA(). This method will return a structure of type
EDOC_SRC_DATA_SD_INVOICE or EDOC_SRC_DATA_FI_INVOICE, depending on the Source type (if
IO_SOURCE->MV_SOURCE_TYPE is equal to ‘SD_INVOICE’ or equal to ‘FI_INVOICE’”).

8. Authorization

Two additional authorization objects have been created for Report EDOC_COCKPIT. The users that have to
work with the report have these objects added to their user authorizations.
8.1. Company – EDO_BUK This verifies if you are authorized to view the eDocuments for the company.
8.2. Process Step – EDO_PROC This object verifies that you are authorized to perform the process step.

9. Logical path definition

9.1 Go to FILE transaction

9.2 Press New entries button
9.3 In the table enter the values as below:

Logical file path Name

EDOC_CO_INVOICE_UPLOAD_PATH eDocument Colombia Invoice Upload Path

9.4 Select the newly created line and press Assignment of Physical Paths to Logical Path from the menu on
the left side (under Logical File Path Definition).
9.5 Press New entries button
9.6 Enter UNIX for Syntax group field
9.7 In the Physical path enter the application server path where the XML files from the external systems will
be uploaded.
An example: /usr/sap/<SYSID>/SYS/src/<FILENAME>
9.8 Save
9.9 Select the Logical File Name Definition, Cross-Client from the menu on the left.
9.10 Press New entries button
9.11 In the displayed screen enter the values:
Log. file EDOC_CO_INVOICE_UPLOAD_FILE
Name eDocument Colombia Invoice Upload File
Physical file
Data format DIR
Applicat. area
Logical path EDOC_CO_INVOICE_UPLOAD_PATH

9.12 Save
9.13 Go to FILE transaction
9.14 Press New entries button
9.15 In the table enter the values as below:

Logical file path Name

Copyright/Trademark
 EDOC_CO_INVOICE_ARCHIVE_PATH eDocument Colombia Invoice Archive Path

9.16 Select the newly created line and press Assignment of Physical Paths to Logical Path from the menu
on the left side (under Logical File Path Definition).
9.17 Press New entries button
9.18 Enter UNIX for Syntax group field
9.19 In the Physical path enter the application server path where the response XML files received from
the Tax Authority will be saved.
An example: /usr/sap/<SYSID>/SYS/arch/<FILENAME>
9.20 Save
9.21 Select the Logical File Name Definition, Cross-Client from the menu on the left.
9.22 Press New entries button
9.23 In the displayed screen enter the values:
Log. file EDOC_CO_INVOICE_ARCHIVE_FILE
Name eDocument Colombia Invoice Archive File
Physical file
Data format DIR
Applicat. area
Logical path EDOC_CO_INVOICE_ARCHIVE_PATH

9.24 Save

Copyright/Trademark