HLD: High Level Design Document

ANDES Project
___________________________________________
ROLES AND APPROVALS

ROLE NAME/AREA SIGNATURE

IS Functional Lead Charles Santos
IS Project Manager Enock Alves
IS Integration Mgr Fabio Guizelini
Program Manager Rodrigo Pasqualetti
Requester
Controller
Division / Area IS manager
BPO (Business Process Owner)
Approving CFO Gabriela Gonzalez
Approving CFO Giselle Somalle
Approving CFO Martin Castellucci

DOCUMENT REVISION HISTORY

AUTHOR VERSION DATE CHANGES

Enock Alves 1 Oct, 2020

739547764.docx 2 of 36
TABLE OF CONTENTS

1. SOLUTION OVERVIEW............................................................................5
1.1. Scope.........................................................................................................................5

1.2. Organizational Structure..........................................................................................6

1.3. Master Data Requirements......................................................................................7

1.3.1. FI – Finance.........................................................................................................7

1.4. Common Business Processes (valid for All Clusters)..........................................9

1.4.1.1 FI – Finance......................................................................................................9
1.4.1.2 General Ledger (GL)........................................................................................ 9
1.4.1.3 Accounts Payable (AP)...................................................................................10
1.4.1.4 Supplier Master Data......................................................................................10
1.4.1.5 Creation of Suppliers Invoices........................................................................10
1.4.1.6 Anticipation Request.......................................................................................11
1.4.1.7 Automatic Payment........................................................................................ 11
1.4.1.8 Payroll Payments............................................................................................11
1.4.1.9 TAX Payment................................................................................................. 11
1.4.1.10 Internal Purchase/Sale Process (CVI)............................................................11
1.4.1.11 Check Payment.............................................................................................. 11
1.4.1.12 Returno of Payment........................................................................................12
1.4.1.13 Payments Refused.........................................................................................12
1.4.1.14 Payments Wagonlit, Amex, Alatur..................................................................12
1.4.1.15 Account Receivable Module (AR)...................................................................12
1.4.1.16 Fixed Asset Module (AA)................................................................................13

1.5. Distinct Business Processes (specific for a clusters/country)..........................15

1.5.1. FI – Finance.......................................................................................................15
1.5.1.1 Chart of Accounts...........................................................................................15

1.6. Process Flow.......................................................................................................... 22

1.6.1. FI - Finance........................................................................................................22
1.6.1.1 End of month flow...........................................................................................22
1.6.1.2 Accounts Payable...........................................................................................23
1.6.1.3 Accounts Receivable......................................................................................25
1.6.1.4 Bank Reconciliation........................................................................................26
1.6.1.5 Business Partner – FSCM (Dispute and Collection Management).................26
1.6.1.6 Credit Management........................................................................................27
1.6.1.7 Dunning management....................................................................................27
1.6.1.8 Fixed Asset.....................................................................................................28

1.7. Solution Elements (Work Breakdown Structure).................................................29

1.8. Integration Points (Cross Module)........................................................................29

1.8.1. FI – Finance.......................................................................................................29

739547764.docx 3 of 36
1.9. Application Mapping..............................................................................................30

1.10. Interfaces................................................................................................................ 30

1.11. FI – Finance.............................................................................................................31

1.12. Key Design Considerations...................................................................................34

1.12.1. FI – Finance....................................................................................................34

1.13. Out of Scope........................................................................................................... 34

1.14. Test Strategy...........................................................................................................34

1.15. Deployment Strategy..............................................................................................34

1.16. SAP Profiles............................................................................................................34

1.16.1. LASAP SAP Environment - DC2....................................................................35
1.16.2. SAP-GRC....................................................................................................... 35
1.16.3. Derived Roles Strategy...................................................................................36
1.16.4. Current List of Functions.................................................................................36

1.18 Requirements List - Decision................................................................................37

739547764.docx 4 of 36
1. SOLUTION OVERVIEW

1.1. Scope
Roll out Brazilian solution to countries in LATAM (Argentina, Chile, Peru, Colombia, and Panama + small countries)
with the functionalities already deployed for Brazil with Fit/GAP phase; Blueprint design; System and integrations
development; Testing; Go Live and Hyper Care.
In order to achieve cost and timeline objectives, current scope is considering deploy the BR SAP template into the
countries in scope, including only for legal requirements and any locally distinct processes that add value for the
customer. Back-office processes (e.g. AR, AP, SCM, etc.) should be standardized across the region with the
objective to minimize the cost per transaction (GBS).
Background & Context
 Risk record open for Chile related to patching of the old ERP environment (we cannot apply latest security
patches)
 SAP is imperative for LATAM and we had a serious risk of business interruption, like a severe incident in Chile
in June. ERP’s do not fully attend
 SOX and business requirements. Currently local and manual solutions/workarounds, shadow IT applications
are defined to address the need.
 Due to the lack functionality and maintenance from the vendors of the old current ERP’s versions; It is also
important to mention that we will not be able to fully take advantage of the GBS implementation until we get
a common ERP.
 We have currently 4 different ERPs (BaaN IV c2, iScala 2.3 SR2, Oracle EBS 11i.5.10.2, SAP R3 ECC 6.0).

The project will have two Go Live waves, ensuring controlled rollout of new SAP processes/functionality without
impact to the adopting Business Units (BUs).

739547764.docx 5 of 36
1.2. Organizational Structure

Company Code: CL10 - Chile

Purchasing Purchasing
Plant Sales Organization
Organization Group
CL10 - IA-Material
CL10 - IA-Vicuña Mackenna CL10 - IA C01, C02, C03, C04, C05, C06, C07, C08
CL16 - IA-Service

CL20 - MO-Vicuña Mackenna CL20 - MO-Material

CL20 - MO
CL21 - MO-Rio Refugio CL26 - MO-Service
C09, C10, C11, C12, C13, C14, C15
CL40 - RA-Material
CL40 - RA-Vicuña Mackenna CL40 - RA
CL46 - RA-Service

CL30 - EL-Material
CL30 - EL-Vicuña Mackenna CL30 - EL C16, C17, C18, C19, C20, C21, C22
CL36 - EL-Service

CL90 - ZC-Vicuña Mackenna CL90 ZC- Corporate CL90 - ZC Corporate C23, C24

739547764.docx 6 of 36
1.3. Master Data Requirements

1.3.1. FI – Finance

General Ledger Module (GL) Master Data Element

Chart of Accounts
Unique Plan of Accounts: It is a catalog which contains the accounts necessary to record the economic events
of one or more organizations. A chart of accounts must meet several requirements, such as homogeneity,
integrity (it must present all the necessary accounts), systematic (it must follow a certain order) and flexibility
(it must allow the addition of new accounts).

Accounting Account:
Account, or item, is the basic and central element in accounting and payment services. It is also the smallest
accounting unit capable of summarizing an economic fact. The accounting account is the representation
valued in monetary units of each of the elements that make up the assets of a company (goods, rights and
obligations) and the result of the same (income and expenses), it allows the monitoring of the evolution of
the elements in time. Therefore, there are as many accounts as there are equity elements that the company
has and, consequently, the set of accounts of a company supposes a complete representation of the equity
and the result (profits or losses) of the company.

General Ledger Account:

These are accounting accounts where debits and credits are registered in a general way, where it is difficult to
extract the movements by a specific criterion. Usually its control is based on the net balance that is calculated
by subtracting the credits from the debits, depending on the nature of the account (the account may be
Debtor or Creditor nature)

Auxiliary Book Account: These are accounting accounts that record the details of the movements that
support the balances reported in the General Ledger accounts. This control is done by recording all the
movements in detail for each member of the auxiliary (debtors, creditors) and that impact the General
Ledger on a consolidated basis (on a daily or monthly basis), as a resulting balance and without transferring

739547764.docx 7 of 36
 all the transactions that make up said balance.
The chart of accounts is a list that presents the accounts necessary to record the accounting events. This is a
systematic ordering of all accounts.

Account Payable (AP) Master Data Element

Master data is divided into 2 segments with different types of information which is useful for different areas
of an organization.
The creditor master data is divided into:
 General data: these are the supplier's own data, they are data that do not change according to the
company or purchasing organization where they are created, for example, name or company name,
address, tax identification, tax status, etc.
 Company data: these are the data that interest the company in which the provider is created, for
example, the associated account, the payment methods, the treasury group, the data of tax interest such
as withholdings, etc.
 Purchase organization data: these are the data referring to the purchase conditions, such as the
payment terms, the price scheme, the usual purchase currency, etc.

To create a vendor master data, you must use an account group which defines two especially important
things:

 Determine the field status of the account master data: The status field is what determines which data is
required, optional, or remain hidden at the time the master data is created.

 Defines the number range: for each group you can create a different number range, or you can even
assign the same range to multiple groups.

Currently, the Template handles account groups that are not useful for other LATAM countries, especially
since providers that are national for one country can be from abroad to others. The definition use and
process to be given to supplier groups in relation to all countries is pending by the ABB team.

Banks
The relevant master data for bank transactions are:
 Country bank: this is the code that represents a country's banking institutions. The Central Bank of each
country assigns a code to the enabled banks. This code is saved as a country bank or general bank.
 Own bank: Set up to identify the general bank in which companies have one or more bank accounts.
 Account ID: This concept represents the bank accounts held by the company code in its own bank. The
same bank itself can have one or more accounts.

Cash book or Petty Cash

The cash book is a tool for cash management and movement of funds. It is used to record cash inflows and
outflows.
The relevant master data for petty cash transactions is:
 G/M account: This master data contains information that controls the account assignments of the
transactions and the processing of the data.

FI-AR Master Data Elements

The following (supporting) Master Data elements are in-scope:

739547764.docx 8 of 36
  Customer Master
 Business Partner
 Material Master

Fixed Asset Module (AA) Master Data Element

The following (supporting) Master Data elements are in-scope:
 Standard Fixed Asset Master Data is a baseline object managed at group level. Baseline naming
convention for Standard Master Data will be unique and global and it will consider the peculiarity of each
value chain.
 Primary Numbers: Represent the principal asset. Primary asset will contain ABB “historical” master data,
with values coming from current legacy System; after SAP start, these assets will be created functionally
for “new constructions” or for new financial asset acquisitions/transfer acquisitions carried out in the
companies. On the primary asset, will be capitalized first acquisition value (e.g: a new device, a new
spare part).

1.4. Common Business Processes (valid for All Clusters)

1.4.1.1 FI – Finance

1.4.1.2 General Ledger (GL)

Sap FI introduction to general ledger (gl) - Libro Mayor - refers to SAP's Main Accounting module. The central task of
primary accounting is to provide a balance sheet of the external accounts and accounts. Basically, the general ledger
serves as a complete record of all accounting operations.

 Processes and operations

• Transaction - General posting

• Entry - Register G / L Account Document
• Transaction - General posting with template
• Modification and Viewing of documents

 Open and close accounting periods

In this process it is possible to indicate in each company code variant, which posting periods are open for posting.
For this, there are two time intervals, where it is indicated in each interval: A lower period limit, an upper period
limit and the year.

 Arrastre de Saldos: Libro Mayor

At the end of the fiscal year, it is necessary to carry over the balances of each book to the new fiscal year. This
activity can be repeated as many times as desired. However, it is usually not necessary to repeat the run since,
when posting in the previous fiscal year, the postings are automatically carried forward to the new fiscal year,
provided that the carry-forward of balances has already been executed to the new fiscal year.

739547764.docx 9 of 36
 Valuation of Foreign Currency.
Valuation in Foreign Currency, With the valuation program in SAP, through the transaction FAGL_FC_VAL - Foreign
currency valuation, the items or balances are valued using the new exchange rate, generating a valuation
difference that is posted to adjust the accounting to the values current.

 Balance Sheet Structure

Balance structure is a tool that allows you to configure the format of a balance allowingyou to have different
groupings of accounts or hierarchical structures of balances. Eachstructure will serve to expose a balance sheet in
a different way. The balance sheet structure is complemented with Z development to meet the legal book
requirements of each location

1.4.1.3 Accounts Payable (AP)

The main object to run the accounts payable control is the documents generated for the vendor. With them,
the control needs of these documents (open items, prepayments, credit) and the clearing or sending of
payments to the supplier are generated. The origin of these documents can come from MM (Invoice Entries),
PWCE (Invoice Entry, Advances or Credit Memo), FI-AP - manual document postings.

1.4.1.4 Supplier Master Data

Vendor master data record contains name, address, currency used for purchase orders, payment condition,
control account. The vendor master record consists of three areas:
a) General data:
Data that applies equally to each company (address, telephone number, language, etc.)
b) Company details:
Data maintained at the company level (payment transactions, reconciliation account number, etc.)
c) Purchases:
Important data relating to purchasing activities, which is maintained at the purchasing organization level
(terms of supply of contact persons, etc.)
Suppliers can be registered in two ways:

 Through GEFOR - system developed in notes that has workflow and after doing the integration with SAP,
automatically creating the supplier.
 By registering suppliers in SAP in transaction xk01 / xk02.

1.4.1.5 Creation of Suppliers Invoices

Invoices are documents created for the supplier, originated from a purchase, taxes payable, etc.
Invoices can come automatically from purchasing processes, generated taxes, PWCE invoices, PLC uploads or
manual posting directly to the AP.
Manual posting in ABB is only used as an exception and, when invoice is required, it is filled in as follows.

1.4.1.6 Anticipation Request

It is a statistical document, that is, it does not generate accounting movements at the time of its creation.
This item will only be recorded in the general ledger at the time of payment (F-53) or registration by
transaction (F-48).

739547764.docx 10 of 36
1.4.1.7 Automatic Payment
This option will be used to make massive payments, that is, it is the generation of borders that will be sent to
the banks electronically. Through it we will be able to select all the payments that are maturing on a certain
date and process them at the same time.
All payment must be in the name of the provider registered in the System. Payment is not allowed on behalf
of a third party.

1.4.1.8 Payroll Payments

The entries of amounts related to Payroll are created by the Human Resources Department through the
Rhevolution system, with the generation of an electronic payment file, where they are sent to the Bank (Itaú),
to make the payment to the employees.
The accounting for these payments is grouped by a total amount per branch and sent to SAP after approval
on a Lotus Notes basis, and a file (PLC > Account Entry Spreadsheet) is sent to carry out the accounting of the
output of these payments.

1.4.1.9 TAX Payment

The accounting of taxes and taxes are made by the Accounting, Taxes and Human Resources Departments,
and sent to the Financier for payment through collection guides.
These postings are verified and released in the SAP System considering their respective maturities.
After the releases and conferences of the payments, the Suppliers department, through the ZFITAXPOSTER
transaction, and based on an Excel file, generates the open items for these payments.
Thus, the payment proposal is generated through transaction F110 and generates the payment cycle, thus
considering the corresponding providers and their respective due dates.
For some taxes and duties, the Suppliers department receives electronic files from the responsible
departments to send them to the banks.
The postings for tax payments that were not possible to generate the electronic file by the person in charge
are entered manually in the Bank's system by the Suppliers department.

1.4.1.10 Internal Purchase/Sale Process (CVI)

The internal buying and selling process is called CVI. The SAS receives the payment request with the
information of the exit to pay and the exit to receive.

1.4.1.11 Check Payment

Payment by check will only be made for branch refunds and refunds or in the case of any legal process that
requires payment by check. These must be signed by authorized approvers in accordance with the Judicial
Power.

1.4.1.12 Returno of Payment

Payment return files are generally received by the Accounts Receivable department. The consistency files and
the final declaration are downloaded to the SAP system. Consistency files are downloaded only to verify that
payments have been scheduled. If the bank rejects any payment at the time of canceling consistency, the SAP
system automatically reopens the item, allowing correction on departure and forwarding to the Bank.

739547764.docx 11 of 36
1.4.1.13 Payments Refused
Payments rejected by the bank through DOC and TED in days after the due date are analyzed and returned
for payment by the Accounts Payable department. In the rejected departure, a history of the reason for the
return is observed.

1.4.1.14 Payments Wagonlit, Amex, Alatur

These are open item documents for travel and card expenses. These expenses are received through files and
uploaded to SAP, processed in releases and a file is generated to be uploaded via PLC.

1.4.1.15 Account Receivable Module (AR)

 Master Data – Create, Change and Display Customer

In the customer register, the following is inserted: customer name, Address, Communication, Tax Number
(Example: CUIT Number), Accounting Information (Reconciliation Accounting), Payment Methods, Dunning
frequency and Interface ICV and R-Box (ABB global solution).

 Customer Credit Management

Credit analyst checks the client's financial documentation and determines the credit limit in the register. Credit
Control Area defines credit limit. A credit control area can have more than one company. Risk Class is manually
changed. Credit exposure occurs in Sales order and Invoice.
Customer is blocked for all credit management business transactions (order acceptance, delivery, ) after running
out of credit limit. Customer blocked for all credit management business transactions (order acceptance,
delivery) after running out of credit limit. Can still post invoices for goods that have been delivery.

 Customer Down Payment Request

If Customer Down Payment Request is with external project, is required create billing document with input
invoice document (SD). Area creates down payment request and post conciliation based on the bank entry.

 Business Partner
Business Partner automatically created when the client generated. These rules determine the order that
customers shown on Worklist. With the presentation of clients on the Worklist, it is possible to start Dispute Case
and Promise to pay.

 ‘Dispute Case
Dispute Case is internal communication and created due to business problems that, for the customer, justify the
non-payment of the debt (wrong invoice, wrong tax, wrong address, goods not received, etc.).
Email sent to ABB technical staff and technical team analyzes the case. Required definition of Analyst and
Supervisor by Profit Center to which emails will sent. After solving, Dispute case will returned to business area,
which will continue the collection process.
Dispute case will closed when customer invoice are cleared e o history of the actions performed will displayed in
the worklist.
Dispute Case update done through a program (without manual intervention).

 Promisse to pay
Worklist will show all unpaid invoices on the due date according to the established rule. Promise to pay are
created when there are no technical and operational details that justify non-payment.

739547764.docx 12 of 36
 Business area contacts customer and determines new payment date e create Promise to pay. Program sends
email to the customer informing about the agreed payment promise. If payment confirmed, it updates the
payment promise and links the payment received to the business partner.

 Dunning
It is the process for which collection letters sent to customers who have unpaid invoices by the due date.
SAP standard allows for three rules and three card templates. (GAP will show below).

1.4.1.16 Fixed Asset Module (AA)

 Asset Master Data Management

 Asset acquisition process
 Final Asset and AUC Automatic creation-Settlement Management
 Asset Movements-Transfers
 Asset Movements-Retirements
 Asset Depreciations/Month End Closing
 Asset Year End Closing
 Asset Reporting Process

The indicated Fixed Asset (AA) business processes will be supported via the implementation of the following SAP
FI components, along with supporting applications/interfaces:

Manage Creation/Updating of asset master data, according to the defined Accounting scheme, guarantee
integrity and tracking from Business work object and Asset Master Data
Manage the different kind of requirements for Asset classification and depreciations (IFRS/LOCAL GAAP/ USGAAP/
tax/ managerial/ regulatory).
Provide appropriate reporting on asset master data.
This process describes the reference framework to Asset Master Data Management, which aims to optimize asset
management with:
Embedded controls on Business Work Object to guarantee integrity of Asset Data from the beginning of work.
Link between work end date and depreciation start. It will set the date of the first capitalization
Creation of both Asset Under Construction and Final Asset will be automated.
Depreciation will be posted every month for all assets belonging to a company code.
Legal or Tax books do not require separate running of Depreciation.
Before period is closed centrally at month end, depreciation to be posted.
The monthly depreciation posting scheduled as background job. It post separate documents in 0L and parallel
Ledger.

Taxes (TX) Argentina/Uruguay and Caribbean Countries

 Purchasing (input process)
 Sales (output process)
 Withholding Taxes
 Tax Reports

The indicated Taxes (TX) business processes will be supported via the implementation of the following SAP FI
components, along with supporting applications/interfaces:

739547764.docx 13 of 36
 Taxes Module (TX)

Purchasing/Billing Processes: The Input/ouput documents (Invoice, Credit notes, etc) will include the calculation
and derivation of different taxes.
Tax Codes:
Used to implement Taxes on Sales and Purchases (VAT, Perceptions, internal taxes)
Tax procedure is defined in the country, which includes the tax structure and tax codes.
Tax Codes can combine different taxes and include the corresponding rates to be calculated on each transaction
(e.g.: VAT 21% + Gross Income Perception CABA 1,5 %)
Accounts are defined for each tax component.

Withholding tax Module

SAP calculation applied through the combination of a Withholding tax code and an Withholding tax type indicator.
Combinations of tax code and types indicators reflect withholding tax regimes for which the company acts as
agent.
Withholding tax Type:
Withholding classified according to different tax withholding systems.
Specifies different attributes to calculate deductions. For example: Time of retention
(Posting of the invoice or payment posting) Calculation Base (gross, net, tax), type of accumulation (monthly,
quarterly, annual or without accumulation), treatment of partial payments, issuance of certificates retention
control minimum amounts base and retention, etc.
They are assigned by company code
Withholding tax Code:
Defined the amount or the percentage of each withholding

Tax Reports
Different kinds of Tax and Withholding tax reports are required and will be provided by SAP TAX standard module
and/or according Argentina localization.
In the case of Argentina, different Z Reports will be extended from the current SAP system to the new SAP.

1.5. Distinct Business Processes (specific for a clusters/country)

1.5.1. FI – Finance

739547764.docx 14 of 36
1.5.1.1 Chart of Accounts

PER
The identifying agent requires a specific chart of accounts for Peru, even if we have another chart of accounts, we
have to follow the rules of that plan, numbering and description. We also manage it externally to avoid
duplication of information in our ERP. Peru's ERP is IScala.

ALLCLUSTER

It is requested to validate those required for the other countries.

1.5.1 Transfer price

According to what is described, it refers to the exchange rate or currency parities, therefore CHI / PE need to
maintain two different rates, one for USGAAP (OL and 1L) and another for IFRS (2L).

1.5.1.2 Confirmation / Factoring

Mention is made only of Confirming, but nothing related to CHI / PE Factoring is considered or mentioned.

Confirming Global ATPF.

Third party factoring, verify the location to affect the change of provider when it happens.

Consider that for PE factoring generates withholdings and deductions.

1.5.1.3 Bad det

Confirm that the Brazilian template executes according to the group norm, in relation to the risk of the CHI / PE
client.

provision calculation method, both CHI / PE perform the calculation according to the client's risk for USGAAP and
for IFRS according to the age of the document.

1.5.1.4 AF

The initial loading data is different for each of the USGAAP and IFRS CHI / PE standards.
From time to time the system needs to allow appraisal and updating of the value of AF CHI / PE.
Information AF / Reports It is said that it is pending to receive information from the CHI / PE reports, but this
information has already been provided.

Other Points not found:

When receiving an advance from clients, it is necessary to have the option of issuing an invoice not a draft CHI /
PE document.

Application and massive registration of air flights and travel expenses of Amex PE.

739547764.docx 15 of 36
 Clarify if the Brazilian template can be charged for customs expenses automatically, since currently CHI / PE
manual is entered.

It should be noted that there are special occasions where manual (paper) documents of CHI / PE issuance are
made.

Consider that PE needs to issue certificates to suppliers for the withholdings made, gosocker application interface,
xml billing and SAF.

There is no reference in the document to the comprehensive retention and detraction processes required by the
PE legislation (see attached email from Nicole).

We have not had references to the Import and Export processes, their treatment and management from the FI,
CHI / PE module.

According to what is described, it refers to the exchange rate or currency parities, therefore CHI / PE need to
maintain two different rates, one for USGAAP (OL and 1L) and another for IFRS (2L).
the Journal, Ledger
It is requested that you do not send some examples of the Journal, Ledger, Inventory, etc.

AllCountries
It is requested to validate those required for the other countries.

PER
closing and opening

He commented that they make closing and opening entries, take the values of the income statements to the
accrued income, profit or loss accounts, and then take the asset and liability accounts. There is a process in
Template that does that process. Verify if you can be applied for Peru.

the development creation for this process should be analyzed

PER
What will be the tool that will replace the PLC (a program that creates accounting entries in SAP)?
it should be analyzed if a development will cover the request

Country chart of accounts: in certain countries it is mandatory to use the specific chart of accounts by legal
regulations. However, a company can have the same chart of accounts of its parent company and in each G / L
account of the operational chart of accounts assign the account of the country chart of accounts in order to
maintain an equivalence between both charts of accounts

739547764.docx 16 of 36
 CHILE
Guia de Despacho: Like Remito, this document serves to evidence the transport and receive the goods to the
customer.
The difference from Remito, Guia de Despacho is an electronic document in Chile. It consists to send a file to the
govern by webservice and they approve or reject the electronic document (DTE).
Information that needs to contain:
• Seller name and respective address;
• Buyer name with their respective address;
• Goods description;
• Quantity;
• Route type;
• Price.
• Taxes
• Transportation Info - Vehicle Plate.
• Payment Terms, Expiration Date
• Folio

Solution: Implement standard notes and build web service connections with XDOC. Create a smartform as well.

Electronic Invoice: The electronic invoice is a commercial document in digital format that replaces the physical
(paper) format. It consists to send a file to an electronic authorized provider (Signature) who signs and send it by
webservice to the SII. Who approves or rejects the electronic invoice. This applies to Invoice, Credit Note and
Debit Note Generation.

Information that needs to contain:

• Seller name and respective address;
• Buyer name with their respective address;
• Economic Activity (Giro).
• Goods description;
• Quantity;
• PO Number
• Reference Documents (Sales Order, Dispatch Guide, In case of Credit and Debit Notes the invoice).
• Prices.
• Taxes
• Folio

Solution: Implement standard notes and build web service connections with XDOC. Create a XML file based on
SAP standard structure. Create a smartform as well.

739547764.docx 17 of 36
 PERU
Guia de Remision: Like Remito, this document serves to evidence the transport and receive the goods to the
customer.
The difference from Remito, Guia de Despacho is an electronic document in Peru. It consists to send a file to the
govern by webservice and they approve or reject the electronic document.
Information that needs to contain:
• Seller name and respective address;
• Buyer name with their respective address;
• Goods description;
• Quantity; Weight
• Route type;
• Price.
• Taxes
• Transportation Info – Driver and Vehicle info, MTC permission number

Solution: Implement standard notes and build web service connections with XDOC. Create a smartform as well.
Implement Business Add-in Variable Key for eDocument Numbering, to assign different range numbers for each
Plant.

Electronic Invoice: The electronic invoice is a commercial document in digital format that replaces the physical
(paper) format. It consists to send a file to an electronic authorized provider (Signature or Close2u) who signs and
send it by webservice to the SUNAT, which approves or rejects the electronic invoice. This applies to Invoice,
Credit Note and Debit Note Generation.

Information that needs to contain:

• Seller name and respective address;
• Buyer name with their respective address;
• Economic Activity (Giro).
• Goods description;
• Quantity;
• PO Number
• Reference Documents (Sales Order, Dispatch Guide, In case of Credit and Debit Notes the invoice).
• Prices.
• Taxes
• Legal Serie and Number

Solution: Implement standard notes and build web service connections with XDOC. Create a XML file based on
SAP standard structure. Create a smartform as well.

739547764.docx 18 of 36
 The different types of taxes in Chile:

Direct taxes. First Category Income Tax.

It is the tax levied on the income that comes from the capital of commercial, service,
industrial, mining companies, etc. ...
Indirect taxes. Sales and Services Tax (IVA)

IVA
The IVA in Chile is 19%. Although this% does not appear in, for example,
tickets when buying a product included in the price of goods and services..

Sales and Purchase Tax

These taxes and fees are identified in order to integrate them in purchasing and sales processes:

739547764.docx 19 of 36
 Chile: IVA (19%)
Tax exempt payment (0% tax rate)
19% creditor IVA
Import IVA 19%
IVA Fixed Assets 19%
IVA Out of Term (19%)
Tax exempt payment (0% tax rate)
19% IVA debtor
IVA Sales losses (19%)

Retention
The increase will be progressive and will start with an increase of 0.75%
per year from 2020. ... We are talking about the law that increases the
withholding of taxes from ballots to fees, which will go from the current 10% to 10.75%
as of January 1, 2020.

 Honorary Ballot 10.75%

The different types of taxes in PERU:

IGV (18%)
Tax exempt payment (0% tax rate)
18% creditor IGV
IGV Import 18%
IGV Fixed Assets 18%
IGV Out of Term (18%)
Tax exempt payment (0% tax rate)
IGV debtor of 18%
IGV Sales losses (18%)

Different types of taxes in Peru

Withholdings:

• National: 3% are made at the time of payment is by provider.

739547764.docx 20 of 36
 Eg 5 invoices from a supplier "X" if they add up to more than 700 they are withheld 3%

• Retention Receipts for Fees: 8% if the service is greater than 1500, they are made at the time of payment is by
provider.
Consider that in some cases there is income suspension.
• Ejm: receipt for a translation service fee greater than 1500 soles, 8% is withheld.

• Withholding of non-domiciled persons: this is done only for invoices for services abroad and is recognized in the
month of registration, keep in mind that there are exceptions to this withholding if there are Agreements to avoid
double taxation.

Detraction

They are made at the time of registration of the local invoice, this must be for a service greater than 700 soles

2. Electronic withholding vouchers

Like Argentina and Uruguay in the case of Peru for withholdings to local suppliers, we issue electronic withholding
vouchers which are validated by Sunat and must be sent to the supplier as part of their payment.

Process

1. The invoice is registered in Iscala.

2. On the effective date of the invoice, the automatic payments option will be marked. (iscala)
3. In SAF it reads the invoices that are in automatic payments and sends to XML Invoicing
4. XML Billing is sent to GoSocket
5. In the GOSocket the pdf is created and sent to Sunat for validation.

CHI/PER

Employees Travel and Expenses processes and refund: is required to have in the new SAP a Process
functionality related Employees travel and Expenses and refund of expenses. Currently these countries
manage manually. ABB template must define the next steps related this Functionality/Module required that is
not cover in detail or with a specific program by the template. Also, Lotus notes will be deactivated.

Comment: I understand that there is a GAP for all countries, but reviewing I see that in the case of Argentina
and Uruguay a small description of how the process was currently was posted, to tell you that in the case of
Peru we use a tool called TMS which It has an approval flow, it has the option to attach documents and it has
an interface with the ERP which generates the accounting records automatically.

4. As an additional point:

• In the case of deductions we need a special report with specific fields which helps us to pay these taxes
before SUNAT
• In the case of registration of air tickets that are approximately 200 per month, we have a module for the
mass registration of these vouchers, I comment on this because it seems to me that he did not get up at any
meeting.

739547764.docx 21 of 36
1.6. Process Flow

1.6.1. FI - Finance
1.6.1.1 End of month flow
The SAP ERP transactions available to carry out the monthly accounting closing processes cover the following
functionalities:

739547764.docx 22 of 36
1.6.1.2 Accounts Payable

is a submodule of SAP FI used to manage and record Accounting data for all the vendors. It handles vendor invoices,
approvals, payments, and other allied activities.

Any postings made in Accounts Payable is updated in General Ledger as well. The Accounts Payable submodule has
tons of reports and forecasting to features to track vendor outstanding and payments.

The chief processes covered in the sub-module are:

• Maintain Vendor Master Data
• Invoice Handling
• Payments
• Account Analysis of Reconciliation
• Reports

Bank – Master Data

739547764.docx 23 of 36
Down Payments - Vendor

Payment and Bank Reconciliation – Vendor

739547764.docx 24 of 36
1.6.1.3 Accounts Receivable
In Account Receivable, each process has a defined set of tasks to be performed.
These tasks are known as process flow.

Accounts Receivable - National

Accounts Receivable - Foreign

739547764.docx 25 of 36
1.6.1.4 Bank Reconciliation

1.6.1.5 Business Partner – FSCM (Dispute and Collection Management)

739547764.docx 26 of 36
1.6.1.6 Credit Management

1.6.1.7 Dunning management

739547764.docx 27 of 36
1.6.1.8 Fixed Asset
In Fixed Asset, each process has a defined set of tasks to be performed.
These tasks are known as process flow.
 Asset Master Data Management
 Asset acquisition process
 Final Asset and AUC Automatic creation-Settlement Management
 Asset Movements-Transfers
 Asset Movements-Retirements
 Asset Depreciations/Month End Closing
 Asset Year End Closing
These are the diagrammatic representation of the process flow of SAP AA defined:
*Fixed Asset Inflation AA (Argentina) Step will be necessary to add in this process before the Depreciation run step.
In Taxes, each process has a defined set of tasks to be performed.
These tasks are known as process flow.
 Purchase Invoices with Taxes /Withholding taxes
 Sales Invoices with Taxes
 Payments with Withholding taxes
 Collections with Withholding taxes

739547764.docx 28 of 36
1.7. Solution Elements (Work Breakdown Structure)

1.8. Integration Points (Cross Module)

1.8.1. FI – Finance
Account Payable Module
Following are the process into SAP used to data records used in Cross Module, separated by module:
For master data integrations at SAP in the Cross Module, it is necessary to execute these procedures
• Master data (GL)
• Master Data (MM)
• Business Parter (BP)
• Cost Center (CO)
• Project Order (PS)
• Product Planning Order (PP)

Following are the process into SAP used to data records in Cross Module, separated by module:
• General Ledger
• Material Management
• Controlling
• Project System
• Production Planning

For master data integrations at SAP in the Cross Module, it is necessary to execute these procedures:

 Master Data (SD)

 Customer Master (SD)
 Material Master (SD)
 Business partner (FSCM)

Account Receivable Module

Following are the process into SAP used to data records used in Cross Module, separated by module:
SD:
 Sales order
 Credit management
 Process Billing
PS:
Project (Advance from customer with project)

Fixed Asset Module

Following are the process into SAP used to data records used in Cross Module, separated by module:

739547764.docx 29 of 36
MM:
 Purchase Requisitions and Orders
 Goods Receipts
 Invoices

SD:
 Sales order
 Credit management
 Process Billing
CO
 Month-end Closing
 Year-end Closing
 Settlement
 Result Analysis
FI
 Customers and Vendors Invoices
 Customers and Vendors Payments

Tax/Withholding tax Modules: following are the process into SAP used to data records used in Cross Module,
separated by module:
MM:
 Invoices
SD:
 Process Billing

FI
 Customers and Vendors Payments

1.9. Application Mapping

1.10. Interfaces

739547764.docx 30 of 36
1.11. FI – Finance

Module General Ledger (GL)

TCode Description
FB01 Create journal entry
FB02 Modify accounting entry
FB03 Consult accounting entry
FS00 Create G / L account
FB50 Register doc. ledger account
F-02 General accounting
FBL3N Visualize
S_ALR_87003642 Open / Close periods
FBV0 Post draft document
FS10N Balance display
FSP0 Reg.tas.mayor in plan ctas.
FB01L Post G / L document for ledger group preliminary
FV50L ME assessment
F05 Cancel compensation
FBRA Individual override
FB08 Currency Valuation (New)
FAGL_FC_VAL Currency translation of balances
FAGL_FC_TRANS EM / RF compensation
F.19 Balance carry forward (new)
FAGLGVTR

Account Payable Module (AP)

TCode Description
FBL1N Vendor Line Item Display
FBL3N GL Account Line Item Display
S_ALR_87012079 transaction figures: Account balance
S_ALR_87012086 List S_P99_41000101 record checks
S_ALR_87012119 checks collected
S_P99_41000102 Ranges of vendor check numbers
S_ALR_87012309 Cash Book
S_ALR_87012348 checks cashed by bank account
S_ALR_87012077 Vendor Information System
S_ALR_87012082 Vendor Balances in Local currency
S_ALR_87012093 business providers

Account Receivable Module (AR)

TCode Description
FAGLB03 Account balance display
FBL5N Customer Line Item Display

739547764.docx 31 of 36
S_ALR_87009987 Bill Holdings (Bill of Exchange Receivable List with ALV facility)
S_ALR_87012172 Customer Balances in Local Currency
S_ALR_87012197 Customer Line Items
S_ALR_87012168 Due Dates Analysis for Open Items
S_ALR_87012173 List of Customer Open Items
S_ALR_87012176 Customer Evaluation with Open Item Sorted List
S_ALR_87012177 Customer Payment History
S_ALR_87012178 Customer Open Item Analysis (Overdue Items Balance)
S_ALR_87012198 List of Customer Cleared Line Items
S_ALR_87012199 List of Down Payments open at key date
S_ALR_8701228 Debit & Credit Notes Register – Monthly

Fixed Asset Module (AA)

TCode Description
AS03 Visualizar Datos Maestros de Activos Fijos
AW01N Explorer AF – Visualizar Valores de Activos Fijos
S_ALR_87011963 Patrimonio de Activos Fijos por Nro de AF
S_ALR_87011964 Patrimonio Activos Fijos por Clase de AF
S_ALR_87011966 Patrimonio de Activos Fijos por Centro de Costo
S_ALR_87011967 Patrimonio de Activos Fijos por Centro Logístico.
S_ALR_87011968 Patrimonio de Activos Fijos por Emplazamiento o Ubicación Física
S_ALR_87011969 Patrimonio de Activos Fijos por supranúmero AF
S_ALR_87011970 Patrimonio de Activos Fijos por pool de trabajo
S_ALR_87010125 Modelo para datos de dirección de un activo fijo
S_ALR_87010127 Terrenos y derechos similares
S_ALR_87010129 Parque de vehículos
S_ALR_87011978 Patrimonio AF en complejos AF
S_ALR_87010137 Códigos de barras
S_ALR_87011990 Cuadro de activos fijos
S_ALR_87011994 Patrimonio de activos fijos
S_ALR_87012004 Total de Amortizaciones
S_ALR_87012006 Amortizaciones Normales
S_ALR_87012011 Correcciones
S_ALR_87012013 Comparación de amortización
S_ALR_87012018 Amortizaciones e intereses
S_ALR_87010173 Revalorizaciones
S_P99_41000192 Amortizaciones contabilizadas por AF y período contable
S_ALR_87010175 Amortizaciones contabilizadas referidas a centros de coste
S_ALR_87012936 Amortización activos fijos activos (simulación Amo)
S_ALR_87012026 Amortizaciones del Ejercicio en Curso
S_ALR_87012028 Valoración del patrimonio
S_ALR_87012030 Valores asegurables
S_ALR_87012037 Modificaciones de los registros maestros de Act.Fijos

739547764.docx 32 of 36
S_ALR_87012039 Movimientos de Activos Fijos
S_ALR_87012041 Patrimonio AF (val.contables act.)
S_ALR_87012043 Saldos de Cuenta de Mayor
S_ALR_87012048 Movimientos activos fijos
S_ALR_87012050 Altas de Activos
S_ALR_87012052 Bajas de Activos Fijos
S_ALR_87012054 Traslados de Activos Fijos
S_ALR_87012056 Directorio de activos fijos no contabilizados
S_ALR_87012058 Comprobación de origen cargos activos fijos
S_ALR_87012060 Comprobación de origen por clases de coste
S_ALR_87012064 Total de Amortizaciones Fiscales
S_ALR_87012075 Historial activo fijo

Tax/Withholding tax Module (Tx)

TCode Description
S_ALR_87010075 Social Withholding Tax
S_ALR_87010073 Withholding Tax Amount and Income
S_ALR_87012224 Gross Income Perception
S_AL0_96000642 Daily Report for VAT
S_ALR_ 87012127 Payments with Withholding Tax:Argentina
S_AL0_96000640 Purchase Regime Information Argentina
S_ALR_87012128 Withholding Tax Certificate
CITI_VENTAS Sales Report (Argentina)
S_AC0_52000171 Monthly Payments Tax Argentina
S_ALR_87012287 Document Journal
S_P00_07000134 Generic Withholding Tax Reporting
S_PL0_09000447 Withholding Tax Report for Vendor

1.12. Key Design Considerations

1.12.1. FI – Finance

Account Payable Module

Among the points not considered for the project we have the management of travel expenses for which SAP
handles the TM (Travel Management) module. Currently the process for relation of travel expenses is

739547764.docx 33 of 36
handled manually through seat loads in the Lotus Note tool which will be removed. The validation of the
process that will be created in all countries for the management of these expenses is required

Fixed Asset Module

ABB has to define how to manage the main Template processes in AA like acquisitions, retirements, etc
processes without the use of Lotus Notes (Lotus Notes is defined in the ABB template) however will not be in
use in the future with SAP.

1.13. Out of Scope

1.14. Test Strategy

1.15. Deployment Strategy

1.16. SAP Profiles

1.16.1. LASAP SAP Environment - DC2

1.16.2. SAP-GRC

Access control will be done by the GRC (Italy Location)

• Automated Profile request (Request, approval, risks identification, mitigation controls);

739547764.docx 34 of 36
 • Custom Workflow & Segregation of Duties;
• Profile Owners, Managers & Requestor;
• Automated Firefighter solution;

User Access Management Workflow

1.16.3. Derived Roles Strategy

ANDES Project will adopt the Derived Roles Strategy as below example:

1.16.4. Current List of Functions

# Description - Template Description ES

1 ACCOUNT MANAGER GERENTE DE CUENTAS
2 ADM CONTRATOS JR ADM CONTRACTS JR
3 ADM CONTRATOS PL ADM CONTRATOS PL
4 ADM CONTRATOS SR CONTRATOS ADM SR
5 ALMOXARIFE ALMACÉN
6 ANALISTA CONTAS A PAGAR JR ANALISTA DE CUENTAS POR PAGAR JR
7 ANALISTA CONTAS A PAGAR SR ANALISTA DE CUENTAS POR PAGAR
8 ANALISTA CONTRATOS JR JR ANALISTA DE CONTRATOS
9 ANALISTA CONTRATOS PL PL ANALISTA DE CONTRATOS
10 ANALISTA CONTRATOS SR SR ANALISTA DE CONTRATOS
11 ANALISTA CONTROLADORIA JR ANALISTA DE CONTROLADORES JR
12 ANALISTA CONTROLADORIA PL ANALISTA CONTROLADOR PL
13 ANALISTA CONTROLADORIA SR ANALISTA DEL CONTROLADOR SR

739547764.docx 35 of 36
14 ANALISTA DADOS MESTRE JR ANALISTA DE DATOS MAESTRO JR
15 ANALISTA DADOS MESTRE SR ANALISTA DE DATOS MAESTRO SR
16 ANALISTA DE AUTOMACAO PL ANALISTA DE AUTOMATIZACIÓN PL
17 ANALISTA DE AUTOMACAO SR ANALISTA DE AUTOMATIZACIÓN SR
18 ANALISTA FATURAMENTO JR ANALISTA DE FACTURACIÓN JR
19 ANALISTA FATURAMENTO PL ANALISTA DE FACTURACIÓN PL
20 ANALISTA FATURAMENTO SR ANALISTA DE FACTURACIÓN SR
21 ANALISTA IMP EXP JR ANALISTA DE IMP EXP JR
22 ANALISTA IMP EXP SR ANALISTA DE IMP EXP SR
23 ANALISTA JURIDICO FINANCEIRO JR JR ANALISTA LEGAL FINANCIERO
24 ANALISTA LOGISTICA JR ANALISTA LOGISTICO JR
25 ANALISTA LOGISTICA PL PL ANALISTA LOGISTICO
26 ANALISTA LOGISTICA SR ANALISTA LOGISTICO SR
27 ANALISTA MATERIAIS JR ANALISTA DE MATERIALES JR
28 ANALISTA PLANEJAMENTO JR JR ANALISTA DE PLANIFICACIÓN
29 ANALISTA PLANEJAMENTO PL ANALISTA DE PLANIFICACIÓN PL
30 ANALISTA PLANEJAMENTO SISTEMAS SR ANALISTA DE PLANIFICACIÓN DE SISTEMAS SR
31 ANALISTA PLANEJAMENTO SR ANALISTA DE PLANIFICACIÓN SR
32 ANALISTA PROCESSOS SR ANALISTA DE PROCESOS SR
33 ANALISTA QUALIDADE EXCELENCIA OPERACIONAL PL EXCELENCIA OPERACIONAL CALIDAD ANALISTA PL
SR ANALISTA DE CALIDAD DE EXCELENCIA
34 ANALISTA QUALIDADE EXCELENCIA OPERACIONAL SR
OPERATIVA
35 ANALISTA QUALIDADE JR ANALISTA DE CALIDAD JR
36 ANALISTA QUALIDADE PL ANALISTA DE CALIDAD PL
37 ANALISTA QUALIDADE SR ANALISTA DE CALIDAD SR
38 ANALISTA RECOF JR ANALISTA DE RECOF JR
39 ANALISTA RELACIONAMENTO CLIENTE PL PL ANALISTA DE RELACIONES CON EL CLIENTE
40 ANALISTA RISCO SEGURANCA TI SR ANALISTA DE RIESGOS DE SEGURIDAD TI SR
41 ANALISTA SAP PL ANALISTA DE SAP PL
42 ANALISTA SAP SR ANALISTA DE SAP SR
43 ANALISTA SERVICOS RH JR ANALISTA DE SERVICIOS RH JR
44 ANALISTA SERVICOS RH PL ANALISTA DE SERVICIOS RH PL
45 ANALISTA SERVICOS SUPORTE PL ANALISTA DE SERVICIOS DE APOYO PL
46 ANALISTA SERVICOS SUPORTE SR ANALISTA DE SERVICIOS DE APOYO SR
47 ANALISTA SISTEMAS PL ANALISTA DE SISTEMAS PL
48 ANALISTA SISTEMAS SR ANALISTA DE SISTEMAS SR

1.18 Requirements List - Decision

739547764.docx 36 of 36