SAP Note 2054892
eDocument Chile - Configuration and Customizing
Consulting
© 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.
Basic Customizing and Configuration for Electronic Documents
These settings are relevant for the basic solution and for the full solution.
1. Activate Interfaces for Applications
This table is used to decide if eDocuments must be created for the company. Per company the interfaces
must be activated using SM30 for table EDOCOMPANYACTIV. It is possible to only activate the interface for
FI or SD documents or for SD Goods Issue. For the ledgers separate entries must be made: LEDGER and
EDOC_LIST.
2. Define Solution Type per Country
This table is used to decide which eDocuments solution (basic solution or full solution) is used for every
country. Per country the table must be maintained as follows:
1.1. Execute transaction SM30.
1.2. Enter EDOCOUNTRYSOLV 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 country code and solution type combination that you want to set.
1.6. Save your entries.
Example: Use the value ‘BS’ for basic solution and ‘FS’ for full solution.
Note: If the field ‘Solution Type’ is empty or do you do not create any entry for the country it will be
considered basic solution by default.
3. Define DTE types
DTE types as defined by tax agency need to be maintained
Transaction SM30, Table/View is EDOCLDTETYPEV.
Type eDocument Type
33 Electronic Invoice
34 Electronic Tax Exempt Invoice
39 Electronic Boleta
41 Electronic Tax Exempt Boleta
43 Electronic Payment Detail Invoice
46 Electronic Purchase Invoice
52 Electronic Delivery Note
56 Electronic Debit Note
61 Electronic Credit Note
110 Export Invoice
111 Export Debit Note
112 Export Credit Note
Copyright/Trademark
4. Relevant Document Types for DTE
Accounting document types that are relevant for the electronic DTE process must be maintained. The
accounting document types are used to identify the relevant FI and SD documents for document Type
CL_DTE and country CL.
Transaction SM30, Table/View is T003EDOC.
Example:
Country Type eDocument Type
CL DR CL_DTE
CL DG CL_DTE
Delivery note (waybill) document types that are relevant for the electronic DTE process must be maintained
for document Type CL_DTE and country CL.
Transaction SM30, Table/View is TVLKEDOC.
Example:
Country Type eDocument Type
CL LB CL_DTE
CL LF CL_DTE
5. Relevant Document Types for Ticket Receipt (Boleta)
Accounting document types that are relevant for the electronic ticket receipt process must be maintained in a
table. The accounting document types are used to identify the relevant FI and SD documents for document
Type CL_BOLETA and country CL.
Transaction SM30, Table/View is T003EDOC.
Example:
Country Type eDocument Type
CL DR CL_BOLETA
CL DG CL_BOLETA
Delivery note (waybill) document types that are relevant for the electronic ticket receipt process must be
maintained in a table for document Type CL_BOLETA and country CL.
Transaction SM30, Table/View is TVLKEDOC. Example: Transaction SM30, Table/View is TVLKEDOC.
Example:
Country Type eDocument Type
CL LB CL_BOLETA
CL LF CL_BOLETA
Copyright/Trademark
6. Assign DTE Type to Standard FI Document Types (Relevant for SD Billing)
DTE type must be defined for the FI document types that are DTE relevant. This is done in SM30 using View
EDOCLDTEACCV.
Example:
Type Description DTE Type Description eDocument Type
DR Customer Invoice 33 Electronic Invoice CL_DTE
DG Customer Invoice 39 Electronic Boleta CL_BOLETA
7. Assign DTE Type to Standard SD Delivery Note Document Types
DTE type must be defined for the Delivery types that are DTE relevant. This is done in SM30 using View
EDOCLDTEDLNV.
Example:
Type Description DTE Type Description eDocument Type
LF Outbound Delivery 52 Electronic Delivery Notes CL_DTE
LB Outbound Delivery 52 Electronic Delivery Notes CL_DTE
8. 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.
1.1. Execute transaction SM30.
1.2. Enter EDOINTTYPEV 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 eDocument type combination that you want to activate.
1.5..1. Note: All eDocument types for Chile start with CL_*.
1.6. In the Interface Type column, select the interface type according to the solution that you are
implementing:
Basic solution: Select CUSTOM - Customer-specific
Full solution: Select AIF_PROXY - AIF proxy (for web services)
1.7. Save your entries.
Copyright/Trademark
9. Number Ranges for DTE Types
The number range XML and number range must be maintained using the transaction code
‘EDOC_CL_NRXML’.
Per Company code / DTE type, number range applications have to be made for at SII. The range is received
as part of an XML called CAF. Run the transaction ‘EDOC_CL_NRXML’ with company code, number range
number and CAF XML to create the number range for DTE types and to save the number range XML in
database.
You also have to maintain the number range that is actually being used for the DTE type. This is maintained
in a separate Table that can be maintained using transaction SM30 and view EDOCLDTENUMBERV.
Example:
CoCd DTE Type Description No
CL01 33 Electronic Invoice 05
CL01 52 Electronic Delivery Notes 01
Copyright/Trademark
10. Additional Company Data
A number of additional fields must be added for the country Chile. This information is required in the files that
are sent to SII.
To add these fields to the additional fields for Chilean companies enter transaction SM30 and fill V_T001I as
Table/View. Add the following parameters:
Par.Type Description Length ISO code
RDDNL Resolution Date Daily Number Ledger 10 CL
RNDNL Resolution Number Daily Number Ledger 6 CL
RDWBL Resolution Date Delivery Note Ledger 10 CL
RNWBL Resolution Number Delivery Note Ledger 6 CL
RDBOL Resolution Date Monthly Boleta Ledger 10 CL
RNBOL Resolution Number Monthly Boleta Ledger 6 CL
RDSAL Resolution Date Monthly Sales Ledger 10 CL
RNSAL Resolution Number Monthly Sales Ledger 6 CL
TAXIDS Sender’s Taxpayer ID 10 CL
RESDAT Resolution Date 10 CL
RESNUM Resolution Number 5 CL
TAXIDC Tax Id of Commissioner 10 CL
CMPLOB Line of business of the Issuer 48 CL
ACTECO Economic Activity Code 6 CL
To maintain these fields, enter transaction SPRO. In IMG go to Financial Accounting (New) Financial
Accounting Global Settings (New) Global Parameters for Company Code Enter Global Parameters.
Select the relevant Chilean companies, press Additional Data and maintain following parameters (maybe you
have to click on Next page (Page down) to be able to see the fields:
Name Description for possible values
Resolution Date Daily Number Date when resolution number was issued for the user that is
Ledger authorized by SII to issue daily ledgers
Resolution Number Daily Resolution number issued for the user that is authorized by SII to
Number Ledger issue daily ledgers
Resolution Date Delivery Note Date when resolution number was issued for the user that is
Ledger authorized by SII to issue delivery note ledgers
Resolution Number Delivery Resolution number issued for the user that is authorized by SII to
Note Ledger issue delivery note ledgers
Resolution Date Monthly Boleta Date when resolution number was issued for the user that is
Ledger authorized by SII to issue monthly boleta ledgers
Resolution Number Monthly Resolution number issued for the user that is authorized by SII to
Copyright/Trademark
Boleta Ledger issue monthly boleta ledgers
Resolution Date Monthly Sales Date when resolution number was issued for the user that is
Ledger authorized by SII to issue sales ledgers
Resolution Number Monthly Resolution number issued for the user that is authorized by SII to
Sales Ledger issue sales ledgers
Sender’s Taxpayer ID The tax payer ID number of the authorized user that is authorized
by SII to issue DTE and Boleta
Resolution Date Date when the resolution number was issued for the user that is
authorized by SII to send DTE and Boleta
Resolution Number Resolution number issued for the user that is authorized by SII to
issue DTE and Boleta
Tax Id of Commissioner Tax ID of the commissioner
Line of business of the Issuer Issuer’s line of business
Economic Activity Code Economic activity code of the issuer
11. Document Filter
The following filtering of the documents is part of the delivery:
1. FI Document type (also for SD)
Only those FI document types that are relevant for DTE must be selected. SD Document types are
filtered through their FI document types
2. SD Delivery Document Type
Only those SD Delivery Note document types that are relevant for DTE must be selected.
3. The BAdI name is EDOC_ADAPTOR. Per country additional filtering can be implemented for the
‘IS_RELEVANT’ method.
12. Authorization
12.1. Two additional authorization objects have been created for Report
EDOC_RESUBMIT_EDOCUMENT. The users that have to work with the report have these objects
added to their User authorizations.
12.1.1. Company – EDO_BUK
This object verifies if you are authorized to view the eDocuments for the company.
12.1.2. Process Step – EDO_PROC
This object verifies that you are authorized to perform the process step.
12.2. Authorization object have been created for Report EDOC_CL_NR_XML_UPLOAD. The
users that have to work with the report have these objects added to their User authorizations.
12.2.1. Number range maintenance - EDO_CL_NR
This object verifies if you are authorized to create or delete number range and number range
XML.
Copyright/Trademark
Copyright/Trademark
