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

PURPOSE OF THIS DOCUMENT

The purpose of this document is to outline the solution to be provided by IS to attend to the
requirements as stated in the approved BRD (Business Requirements Document). It will
include a description of the work required and an estimate for the duration and cost of the
project. This information will be used to evaluate the solution and its cost against the
business case and obtain approval for the execution of the project from business and IS.
The HLD will include a description of assumptions, restrictions and prerequisites for the
solution to work as expected, including work to be performed by the business, if any. It will
not include a detailed plan or Go Live date since resource planning will be done after
approval and prioritization against resource availability.

739547767.docx 2 of 33
TABLE OF CONTENTS

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

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

1.2.1. Finance / Controlling............................................................................................6
1.2.2. Logistic (Plant / Sales Org. / Purchase Org. / Purchase Group)..........................7
1.2.3. Logistic (Plant / Storage Location).....................................................................11

1.3. Master Data Requirements....................................................................................20

1.3.1. FI – Finance.......................................................................................................20
1.3.2. CO – Controlling................................................................................................ 20
1.3.3. MM - Material Magement and Inventory Management......................................20
1.3.4. SD - Sales & Distribution...................................................................................20
1.3.5. CS - Customer Services.................................................................................... 20
1.3.6. PS - Project System...........................................................................................20
1.3.7. PM - Plant Maintenance.....................................................................................21
1.3.8. PP - Production Planning...................................................................................21
1.3.9. QM - Quality Management.................................................................................21

1.4. Common Business Processes (valid for all clusters).........................................21

1.4.1. FI – Finance.......................................................................................................21
1.4.2. CO – Controlling................................................................................................ 21
1.4.3. MM - Material Magement and Inventory Management......................................21
1.4.4. SD – Sales & Distribution...................................................................................22
1.4.5. CS – Customer Services....................................................................................22
1.4.6. PS - Project System...........................................................................................23
1.4.7. PM – Plant Maintenance....................................................................................24
1.4.8. PP – Production Planning..................................................................................24
1.4.9. QM - Quality Management.................................................................................24

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

1.6. Process Flow.......................................................................................................... 24

1.7. Process Steps.........................................................................................................24

1.8. Solution Elements (Work Breakdown Structure).................................................25

1.9. Integration Points (Cross Module)........................................................................25

1.10. Application Mapping..............................................................................................25

1.11. Interfaces................................................................................................................ 25

1.12. Standard Reports................................................................................................... 25

739547767.docx 3 of 33
1.13. Key Design Considerations and Out of Scope....................................................25

1.14. Test Strategy...........................................................................................................25

1.15. Deployment Strategy..............................................................................................26

1.16. Approximate Timeline for Deployment.................................................................26

1.17. Effort and Resources Estimate.............................................................................26

1.18. Assumptions...........................................................................................................26

1.19. SAP Profiles............................................................................................................26

1.20. Roles and Responsibilities (IS).............................................................................26

1.21. Documents (IS).......................................................................................................26

739547767.docx 4 of 33
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).

739547767.docx 5 of 33
1.2. Organizational Structure

1.2.1. Finance / Controlling

739547767.docx 6 of 33
1.2.2. Logistic (Plant / Sales Org. / Purchase Org. / Purchase Group)
Company Code: AR10 - Argentina
Plant
AR10 - IA
AR11 - IA-Zona Franca
AR20 - MO
AR21 - MO-Zona Franca
AR30 - EL
AR31 - EL-Zona Franca
AR32 - EL (Tucuman)
AR33 - EL (Tucuman - FP)
AR34 - ELDS
AR35 - EL-Zona Franca ELDS
AR40 - RA
AR41 - RA Zona Franca
AR90 - ZC oficina Chile
AR91 - ZC Planta El Jaguel
Company Code: UY10 - Uruguay
Plant
UY10 - IA
UY11 - IA-Zona Franca
UY12 - IA-Externo
UY20 - MO
UY21 - MO-Zona Franca
UY22 - MO-Externo
UY30 - EL
UY31 - EL-Zona Franca
UY32 - EL-Externo
UY40 - RA
UY41 - RA-Zona Franca
UY42 - RA-Externo
UY90 - ZC Corporate
Company Code: CL10 - Chile
739547767.docx
Sales Purchasing Purchasing
Organization Organization Group
AR10 - IA-Products
AR10 - IA
AR16 - IA-Service
AR20 - MO-Products
AR20 - MO A01 Joaquin Gracia-Cos, A02 Daniel Uzunoff,
AR26 - MO-Service
A03 Rita Gomez, A04 Florencia Scarinci,
A05 Verocnica Suarez, A06 Sebastian Fernandez,
A07 Noemí Amaya, A08 Agustina Rosenblut,
A09 Patricia Alvarez, A10 Marcos Di Matteo,
A11 Adrian Vergara, A12 Jorge Caloia,
AR30 - EL-Products
AR30 - EL A13 Alan Rioja, A14 Emanuel LazarteKer,
AR36 - EL-Service
A15 Lucia Bernal, A16 Martín A. Pagura
A17 Romina Esquivel-Co, A18 Pedro Baffaro,
A19 Héctor Lipreti, A20 Jorge Schiaffino,
A21 Julieta Fernandez, A22 Giuliana Di Rubba,
A23 Lucia MarcelaPerez, A24 Liliana Martinez,
AR40 - RA-Products
AR40 - RA A25 Giselle Monsivais, A26 Cecilia Agustoni
AR46 - RA-Service
AR90 ZC- Corporate AR90 - ZC - Corporate
Purchasing Purchasing
Sales Organization
Organization Group
UY10 - IA-Material
UY10 - IA
UY16 - IA-Service
UY20 - MO-Material
UY20 - MO
UY26 - MO-Service
U01 - Silvana Sappa,
U02 - Salvador Pérez,
UY30 - EL-Material U03 - María Caballero
UY30 - EL
UY36 - EL-Service
UY40 - RA-Material
UY40 - RA
UY46 - RA-Service
UY90 ZC- Corporate UY90 - ZC Corporate
7 of 33

Plant
CL10 - IA-Vicuña Mackenna
CL20 - MO-Vicuña Mackenna
CL21 - MO-Rio Refugio
CL40 - RA-Vicuña Mackenna
CL30 - EL-Vicuña Mackenna
CL90 - ZC-Vicuña Mackenna
Company Code: PE10 - Peru
Plant
PE10 - IA-Lima
PE20 - MO-Lima
PE21 - MO-Arequipa
PE22 - MO-Operador Logistico
PE30 - EL-Lima
PE31 - EL-Operador Logistico
PE32 - EL-ELDS Lima
PE90 - ZC Oficina Javier Prado
PE91 - ZC-Av. Argentina
Company Code: CO10 - Colombia
Plant
CO10 - IA-Siberia
CO11 - IA-Lagartos
CO12 - IA-Barranquilla
CO20 - MO-Siberia
CO21 - MO-Lagartos
CO30 - EL-Siberia
CO31 - EL-Lagartos
CO90 - ZC-Siberia
CO91 - ZC-Lagartos
CO92 - ZC-Barranquilla
Company Code: EC10 - Ecuador
739547767.docx
Purchasing Purchasing
Sales Organization
Organization Group
CL10 - IA-Material
CL10 - IA C01, C02, C03, C04, C05, C06, C07, C08
CL16 - IA-Service
CL20 - MO-Material
CL20 - MO
CL26 - MO-Service
C09, C10, C11, C12, C13, C14, C15
CL40 - RA-Material
CL40 - RA
CL46 - RA-Service
CL30 - EL-Material
CL30 - EL C16, C17, C18, C19, C20, C21, C22
CL36 - EL-Service
CL90 ZC- Corporate CL90 - ZC Corporate C23, C24
Purchasing Purchasing
Sales Organization
Organization Group
PE10 - IA-Material
PE10 - IA P01 , P02 , P03 , P04
PE16 - IA-Service
PE20 - MO-Material
PE20 - MO P05 , P06 , P07 , P08
PE26 - MO-Service
PE30 - EL-Material
PE30 - EL P09 , P10 , P11
PE36 - EL-Service
PE90 ZC- Corporate PE90 ZC- Corporate P12 , P13
Purchasing Purchasing
Sales Organization
Organization Group
CO10 - IA-Material O01 - Martha Gordillo, O02 - Stephany Toral,
CO10 - IA
CO16 - IA-Service O03 - Neftali Roldan, 04 - Temporal
CO20 - MO-Material O05 - Juan Maldonado,
CO20 - MO
CO26 - MO-Service O06 - Temporal
CO30 - EL-Material O07 - Juan camilo Rivera,
CO30 - EL
CO36 - EL-Service O08 - Temporal
O09 - Grupo GBS IM&S,
CO90 ZC- Corporate CO90 - ZC Corporate
O10 - Grupos GBS IM&S
8 of 33

Plant
EC10 - IA-Quito
EC20 - MO-ADIPHARM
EC21 - MO-Oficina
EC30 - MO-ADIPHARM
EC31 - MO-Oficina
EC90 - ZC-Oficina
Company Code: PA10 - Panama
Plant
PA10 - IA-FP Costa Del Este
PA11 - IA-M8 Centro Ind. Milla
PA20 - MO-FP Costa Del Este
PA21 - MO-M8 Centro Ind. Milla
PA22 - MO-VE Plaza Doral
PA30 - EL-FP Costa Del Este
PA90 - ZC-FP Costa Del Este
Company Code: PA20 - Panama
Plant
PA12 - IA-FP Costa Del Este
PA23 - MO-FP Costa Del Este
PA31 - EL-FP Costa Del Este
PA91 - ZC-FP Costa Del Este
Company Code: CR10 - Costa Rica
Plant
CR10 - IA
CR20 - MO
CR30 - EL
CR90 - ZC-Corporate
Company Code: DO10 - Dominican Republic
739547767.docx
Purchasing Purchasing
Sales Organization
Organization Group
EC10 - IA-Material
EC10 - IA E01
EC16 - IA-Service
EC20 - MO-Material
EC20 - MO E02
EC26 - MO-Service
EC30 - EL-Material
EC30 - EL E03
EC36 - EL-Service
EC90 ZC- Corporate EC90 - ZC Corporate E04
Purchasing Purchasing
Sales Organization
Organization Group
PA10 - IA-Material
PA10 - IA
PA16 - IA-Service
PA20 - MO-Material N01 , N02 , N03 , N04 , N05 , N06 , N07 , N08 ,
PA20 - MO
PA26 - MO-Service N09 , N10 , N11 , N12
PA30 - EL-Material
PA30 - EL
PA36 - EL-Service
PA90 ZC- Corporate PA90 - ZC Corporate
Purchasing Purchasing
Sales Organization
Organization Group
PA10 - IA-Material
PA10 - IA
PA16 - IA-Service
PA20 - MO-Material
PA20 - MO
PA26 - MO-Service N01 , N02 , N03 , N04 , N05 , N06 , N07 , N08 ,
PA30 - EL-Material N09 , N10 , N11 , N12
PA30 - EL
PA36 - EL-Service
PA90 ZC- Corporate PA90 - ZC Corporate
Purchasing Purchasing
Sales Organization
Organization Group
CR10 - IA
CR00 - Material
CR20 - MO N01 , N02 , N03 , N04 , N05 , N06 , N07 , N08 ,
CR60 - Service
CR30 - EL N09 , N10 , N11 , N12
CR90 ZC- Corporate CR90 - ZC Corporate
9 of 33
 Purchasing Purchasing
Plant Sales Organization
Organization Group
DO10 - IA DO10 - IA
DO00 - Material
DO20 - MO DO20 - MO N01 , N02 , N03 , N04 , N05 , N06 , N07 , N08 ,
DO60 - Service
DO30 - EL DO30 - EL N09 , N10 , N11 , N12

DO90 - ZC-Corporate DO90 ZC- Corporate DO90 - ZC Corporate

Company Code: GT10 - Guatemala

Purchasing Purchasing
Plant Sales Organization
Organization Group
GT10 - IA GT10 - IA
GT00 - Material
GT20 - MO GT20 - MO N01 , N02 , N03 , N04 , N05 , N06 , N07 , N08 ,
GT60 - Service
GT30 - EL GT30 - EL N09 , N10 , N11 , N12

GT90 - ZC-Corporate GT90 ZC- Corporate GT90 - ZC Corporate

Company Code: SV10 - El Salvador

Purchasing Purchasing
Plant Sales Organization
Organization Group
SV10 - IA SV10 - IA
SV00 - Material
SV20 - MO SV20 - MO N01 , N02 , N03 , N04 , N05 , N06 , N07 , N08 ,
SV60 - Service
SV30 - EL SV30 - EL N09 , N10 , N11 , N12

SV90 - ZC-Corporate SV90 ZC- Corporate SV90 - ZC Corporate

Company Code: TT10 - Trinidad & Tobago

Purchasing Purchasing
Plant Sales Organization
Organization Group
TT10 - IA TT10 - IA
TT00 - Material
TT20 - MO TT20 - MO N01 , N02 , N03 , N04 , N05 , N06 , N07 , N08 ,
TT60 - Service
TT30 - EL TT30 - EL N09 , N10 , N11 , N12

TT90 - ZC-Corporate TT90 ZC- Corporate TT90 - ZC Corporate

1.2.3. Logistic (Plant / Storage Location)

Company Code: AR10 - Argentina

739547767.docx 10 of 33
 Plant Storage Location
2002 Analitica IAMA
2004 Turbocharging
2006 O&G Sist. Indust
2008 Power Generation
2007 Instrumentos IAMA
AR10 - IA
2009 Control Tech.
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
AR11 - IA Zona Franca TERC Zona Franca
AR20 Motion
SUBC Subcontratación
AR20 - MO 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
AR21 - MO Zona Franca TERC Zona Franca
AR30 Eletrification
SUBC Subcontratación
AR30 - EL 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
AR31 - EL Zona Franca TERC Zona Franca
4001 Produccion
4002 Almacen
4003 Pañol Repuestos
AR32
SUBC Subcontratación
EL Tucumám
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
AR33 - EL Tucumám FP 4004 Finish Goods
6001 Autolink Mat.
6002 MV Sec. Distrib.
6003 Recloser Mat.
6004 Relays
6005 OCB (Int. Ext.)
6006 NSPPCompactSubSt
6007 Autolink Produc.
AR34 - ELDS
6008 MV Sec. Prod.
6009 Recloser Produc.
6010 Producción CSS
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
AR35 ELDS Zona Franca TERC Zona Franca

739547767.docx 11 of 33
 AR40 Robotics & D.Aut.
SUBC Subcontratación
1500 Reparación Calidad
AR40 - RA
ZGAR Garantia
TERC Terceros
TERC Zona Franca
AR41 - RA Zona Franca TERC Zona Franca
AR90 - Corporate Oficina Chile AR90 Oficina Chile
AR91 - Corporate El Jaguel AR91 El Jaguel

Company Code: UY10 - Uruguay

Plant Storage Location
UY10 Central
1001 Service
SUBC Subcontratación
UY10 - IA
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
UY11 - IA Zona Franca UY11 Zona Franca
UY12 - IA Externo UY12 Externo
UY20 Central
1001 Service
SUBC Subcontratación
UY20 - MO
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
UY21 - MO Zona Franca UY21 Zona Franca
UY22 - MO Externo UY22 Externo
UY30 Central
1001 Service
SUBC Subcontratación
UY30 - EL
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
UY31 - EL Zona Franca TERC Zona Franca
UY32 - EL Externo UY32 Externo
UY40 Central
1001 Service
SUBC Subcontratación
UY40 - RA
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
UY41 - Zona Franca TERC Zona Franca
UY41 -RA Zona Franca TERC Zona Franca
UY42 - RA Externo UY42 Externo
UY90 - Central UY90 Central

739547767.docx 12 of 33
Company Code: CL10 - Chile
Plant Storage Location
CL10 Central
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
CL10 - IA-Vicuña Mackenna TERC Terceros
CL12 – TW – Op.Logist.
CL13 – Staging 01
CL14 – Staging 02
CL15 – Bodega IA
CL20 Central
SUBC Subcontratación
1500 Reparación Calidad
CL20 - MO-Vicuña Mackenna
ZGAR Garantia
TERC Terceros
CL22 - TW – Op.Logist.
CL21 Central
SUBC Subcontratación
1500 Reparación Calidad
CL21 - MO-Rio Refugio
ZGAR Garantia
TERC Terceros
CL23 - TW – Op.Logist.
CL40 Central
SUBC Subcontratación
1500 Reparación Calidad
CL40 - RA-Vicuña Mackenna
ZGAR Garantia
TERC Terceros
CL42 - TW – Op.Logist.
CL30 Central
SUBC Subcontratación
1500 Reparación Calidad
CL30 - EL-Vicuña Mackenna
ZGAR Garantia
TERC Terceros
CL32 - TW – Op.Logist.
CL90 - ZC-Vicuña Mackenna CL30 Central

Company Code: PE10 - Peru

Plant Storage Location
0001 IAPI Service 4201
0002 IAPI 4200/4100
PE10 - IA-Lima 0003 IAMA 3199
0004 IATU 7712
SUBC Subcontratación

739547767.docx 13 of 33

PE20 - MO-Lima
PE21 - MO-Arequipa
PE22 - MO-Operador Logistico
PE30 - EL-Lima
PE31 - EL-Operador Logistico
PE32 - EL-ELDS Lima
PE90 - ZC Oficina Javier Prado
PE91 - ZC-Av. Argentina
Company Code: CO10 - Colombia
Plant
CO10 - IA-Siberia
739547767.docx
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
0001 MOSE 4131
0002 MOSE 4159
0003 MOMG 4156MODP 4015
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
0001 MOSE 4131
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
0001 MOMG 4156/MODP 4015
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
0001 ELSP 3078/ELSB 3085
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
0001 ELSP 3078/ELSB 3085
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
0001 ELDS Service 3442
0002 ELDS 3435/3446
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
PE90 - CorporateCO / CorporateRE
PE91 - CorporateCO / CorporateRE
Storage Location
2002 Analitica IAMA
2004 Turbocharging
2005 O&G Sist. Indust
2006 TBD Martin Bogado
2008 Power Generation
14 of 33
 2007 Instrumentos IAMA
2009 Control Tech.
SE00 Service
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CO11 - IA-PRINCIPAL
SUBC Subcontratación
CO11 - IA-Lagartos 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CO12 - IA-PRINCIPAL
SUBC Subcontratación
CO12 - IA-Barranquilla 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CO20 - MO-PRINCIPAL
SUBC Subcontratación
CO20 - MO-Siberia 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CO21 - MO-PRINCIPAL
SUBC Subcontratación
CO21 - MO-Lagartos 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CO30 - EL-PRINCIPAL
SUBC Subcontratación
CO30 - EL-Siberia 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CO31 - EL-PRINCIPAL
SUBC Subcontratación
CO31 - EL-Lagartos 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CO90 - ZC-Siberia CO90 - SIBERIA
CO91 - ZC-Lagartos CO91 - LAGARTOS
CO92 - ZC-Barranquilla CO92 - PARALELO 108

Company Code: EC10 - Ecuador

Plant Storage Location
EC10 - IA STOCK
EC10 - IA-Quito ECXC - EXCEDENTES
ECDM - IA DEMO

739547767.docx 15 of 33

EC20 - MO-ADIPHARM
EC21 - MO-Oficina
EC30 - MO-ADIPHARM
EC31 - MO-Oficina
EC90 - ZC-Oficina
Company Code: PA10 - Panama
Plant
PA10 - IA-FP Costa Del Este
PA11 - IA-M8 Centro Ind. Milla
PA20 - MO-FP Costa Del Este
PA21 - MO-M8 Centro Ind. Milla
PA22 - MO-VE Plaza Doral
739547767.docx
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
EC20 - MO STOCK
ECXC - EXCEDENTES
ECDM - MO DEMO
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
ECDM – MO STOCK
EC30 – EL STOCK
ECXC - EXCEDENTES
ECDM - EL DEMO
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
EC31 - EL STOCK
EC90 – Corporate Almacen
Storage Location
PA10 – FP (Principal)
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
PA11 – MB (Principal)
PA01 - IA Entrega Directa
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
PA20 – FP (Principal)
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
PA21 – MB (Principal)
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
PA22 – VE (Principal)
16 of 33

PA30 - EL-FP Costa Del Este
PA90 - ZC-FP Costa Del Este
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
PA30 – FP (Principal)
SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
PA90 – Principal

Company Code: PA20 - Panama

Plant Storage Location
PA12 - IA-FP Costa Del Este PA12 – FP
PA23 - MO-FP Costa Del Este PA23 – FP
PA31 - EL-FP Costa Del Este PA31 – FP
PA91 - ZC-FP Costa Del Este PA91 – FP

Company Code: CR10 - Costa Rica

Plant Storage Location
CR10 - IA-PRINCIPAL
SUBC Subcontratación
CR10 - IA 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CR20 - MO-PRINCIPAL
SUBC Subcontratación
CR20 - MO 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CR30 - EL-PRINCIPAL
SUBC Subcontratación
CR30 - EL 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
CR90 - ZC-Corporate CR90 - ZC-PRINCIPAL

Company Code: DO10 - Dominican Republic

Plant Storage Location
DO10 - IATU-PRINCIPAL
DO01 – IA Entrega Directa
SUBC Subcontratación
DO10 - IA
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
DO20 - MO DO20 - MO-PRINCIPAL

739547767.docx 17 of 33
 SUBC Subcontratación
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
DO30 - EL-PRINCIPAL
SUBC Subcontratación
DO30 - EL 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
DO90 - ZC-Corporate DO90 - ZC-PRINCIPAL

Company Code: GT10 - Guatemala

Plant Storage Location
GT10 - IA-PRINCIPAL
GT01 – IA Entrega Directa
SUBC Subcontratación
GT10 - IA
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
GT20 - MO-PRINCIPAL
SUBC Subcontratación
GT20 - MO 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
GT30 - EL-PRINCIPAL
SUBC Subcontratación
GT30 - EL
1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
GT90 - ZC-Corporate GT90 - ZC-PRINCIPAL

Company Code: SV10 - El Salvador

Plant Storage Location
SV10 - IA-PRINCIPAL
SUBC Subcontratación
SV10 - IA 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
SV20 - MO-PRINCIPAL
SUBC Subcontratación
SV20 - MO 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
SV30 - EL-PRINCIPAL
SV30 - EL
SUBC Subcontratación

739547767.docx 18 of 33
 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
SV90 - ZC-Corporate SV90 - ZC-PRINCIPAL

Company Code: TT10 - Trinidad & Tobago

Plant Storage Location
TT10 - IA-PRINCIPAL
SUBC Subcontratación
TT10 - IA 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
TT20 - MO-PRINCIPAL
SUBC Subcontratación
TT20 - MO 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
TT30 - EL-PRINCIPAL
SUBC Subcontratación
TT30 - EL 1500 Reparación Calidad
ZGAR Garantia
TERC Terceros
TT90 - ZC-Corporate TT90 - ZC-PRINCIPAL

1.3. Master Data Requirements

1.3.1. FI – Finance
Chart of Accounts
A chart of accounts is a structure that contains the G/M accounts used by one or more companies in the
company.
Operational chart of accounts: The operational chart of accounts contains the G/M accounts that are used
for daily postings in the company code. If cost and revenue accounting is active, the chart of accounts is also
used to post to the controlling area.
Group chart of accounts: The group chart of accounts contains the G/M accounts that the entire group of
companies uses and is required if you use external consolidation and reporting for your group.
Alternative chart of accounts (local): An alternative chart of accounts is specific to a country or region that
contains the major accounts that meet the requirements of specific legal reports in that country or region.

739547767.docx 19 of 33
ACCOUNT PAYABLE
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.

1.3.2. CO – Controlling
Describe1
Describe2
Etc.

1.3.3. MM - Material Magement and Inventory Management

Describe1
Describe2
Etc.

739547767.docx 20 of 33
1.3.4. SD - Sales & Distribution
Describe1
Describe2
Etc.

1.3.5. CS - Customer Services

SAP CS Master Data Elements
The following (supporting) Master Data elements are in-scope:
 Customer Master
 Partner Functions
 Material Master – Spare Parts
 Material Master – Service Materials
 Serial Numbers (where available)
 Equipment Masters (where available)
 Maintenance Activity Types
 Maintenance Work Centers

1.3.6. PS - Project System

Describe1
Describe2
Etc.

1.3.7. PM - Plant Maintenance

Describe1
Describe2
Etc.

1.3.8. PP - Production Planning

Describe1
Describe2
Etc.

1.3.9. QM - Quality Management

Describe1
Describe2
Etc.

739547767.docx 21 of 33
1.4. Common Business Processes (valid for all clusters)

1.4.1. FI – Finance

BUSINESS PROCESSES TEMPLATE ACCOUNTS PAYABLE

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.
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.

CREATION OF SUPPLIER 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.

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).

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.

PAYROLL PAYMENTS

739547767.docx 22 of 33
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.

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.

INTERNAL PURCHASE AND 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.

PAYMENTS WITH CHECKS

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.

RETURN 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.

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.

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.2. CO – Controlling
 Description1
 Description2
 Etc.

739547767.docx 23 of 33
 The indicated business processes will be supported via the implementation of the following SAP CO components,
along with supporting applications/interfaces:
 Description1
 Description2
 Etc.

1.4.3. MM - Material Magement and Inventory Management

 Description1
 Description2
 Etc.

The indicated business processes will be supported via the implementation of the following SAP CO components,
along with supporting applications/interfaces:
 Description1
 Description2
 Etc.

1.4.4. SD – Sales & Distribution

 Description1
 Description2
 Etc.

The indicated business processes will be supported via the implementation of the following SAP SD components,
along with supporting applications/interfaces:
 Description1
 Description2
 Etc.

1.4.5. CS – Customer Services

 Field Service
 In-House Repair
 Warranty Management
 Customer Returns
The indicated business processes will be supported via the implementation of the following SAP CS components,
along with supporting applications/interfaces:
 Service Notifications
 Service Orders
 Service Contracts

Service Notifications
The SAP CS Service Notification component supports the following functions:
 Enter customer notifications
 Document the condition of the service object
 Warranty and/or Service Contract checks
 Credit Limit warnings/checks
 Request the necessary service Tasks
 Track the progress of the Tasks to be performed
 Track history on Equipment (ex. number of Service Orders over a period of time)

739547767.docx 24 of 33
 The SAP CS Service Notification serves as a launch platform for the following processes:
 Creation of a Service Order for sending Field Service Engineers (FSE) to a customer site
 Advanced Shipment and delivery of Spare Parts
 Warranty Replacement/Warranty Repair Processing

The SAP CS Service Notification affords visibility and recording of the following components:
 Customer Data and Partner Functions (Sold-to, Ship-to, Bill-to, Payer etc.)
 Contact Person and Employee Responsible
 Purchase Order reference field
 Sales Document reference field (ex. for Service Contract integration)
 Technical Objects – Equipment, Material/Serial Numbers
 Catalog Codes – Object Part, Damage, Cause
 Notification Description (Short Text and Long Text)
 Notification Tasks and Workflow
 Credit Card Details (ex. Paymetrics)
Service Orders
SAP Service Orders are used to record the details of Services agreed upon by a service provider and a service
recipient. Service Orders act principally as cost-collectors, and contain all of the information needed to plan,
execute, and bill for a Service. Service Orders are linked to Service Notifications, and typically follow from the
creation of a Service Notification.

The SAP CS Service Order component supports the following functions:

 Service Order creation directly from a Service Notification
 Inheritance of information logged in the Service Notification
 Maintenance Work Centers aligned with Service Operations
 Cost Centers and Activity Types aligned with hourly Rates for Planned/Actual Cost determination
 Allocation of Components (Materials) required to perform a Service
 Advance Shipment of Spare Parts
 Integration with FSL application
 Confirmation of Service actuals (Time and Materials)
 Integration with SAP Cross-Application Time Sheets (CATS) for Time booking

Service Contracts
Service Orders are used principally for single or short-term-duration Service events between ABB and its
customers. Service Contracts represent longer-term agreements, generally for periods up to 1 year or more,
where Service events are billed to the customer on a periodic basis, and revenue recognized accordingly.

The SAP CS Service Contract component supports the following functions:

 Integration with Service Notifications – Contract check at the point of customer contact
 Integration with Service Orders with settlement of costs to the Service Contract
 Alignment of Service Contract with one/more customer Equipment/Serial Numbers
 Defined schedule and visibility to upcoming Service events
 Integration with Finance for Periodic invoicing

1.4.6. PS - Project System

 Description1
 Description2
 Etc.

739547767.docx 25 of 33
 The indicated business processes will be supported via the implementation of the following SAP PS components,
along with supporting applications/interfaces:
 Description1
 Description2
 Etc.

1.4.7. PM – Plant Maintenance

 Description1
 Description2
 Etc.

The indicated business processes will be supported via the implementation of the following SAP PM components,
along with supporting applications/interfaces:
 Description1
 Description2
 Etc.

1.4.8. PP – Production Planning

 Description1
 Description2
 Etc.

The indicated business processes will be supported via the implementation of the following SAP PP components,
along with supporting applications/interfaces:
 Description1
 Description2
 Etc.

1.4.9. QM - Quality Management

 Description1
 Description2
 Etc.

The indicated business processes will be supported via the implementation of the following SAP PP components,
along with supporting applications/interfaces:
 Description1
 Description2
 Etc.

1.5. Distinct Business Processes (specific for a

clusters/country)

COMMERCIAL PROCESSES ACCOUNTS PAYABLE FOR ALL COUNTRIES

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.

739547767.docx 26 of 33
At this point, the gaps detected for each of the clusters / countries that make up the object of the implementation rollout
are added, they are identified individually by each one of them.
These points or requirements are requested by the BPOs for current processes or required by country regulations within
each of the current processes managed by the Template

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.

ARG-URY
Treasury Bank Statement and reconciliations
ID 1582 ARG: is required to manage from the new SAP different EM/RF (Accounts at a moment of the Receive the
goods/services).
Currently exist only one SAP account and then is reclassify manually to others types of Vendors.
ABB template has only one GL account also.

CREATION OF SUPPLIER 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.

ARG-URY
Automatic Check Not Legal Vendors/Purchase Invoices
ID 1928 ARG: request to add and automatic process and validation to verified if the Vendor and the Purchase Invoice
is legal.
According a Legal electronic file with a new Program. Currently Argentina does not have this functionality in SAP.

Automatic Check of Exchange Rates (Invoice issue date Vs SAP Table Rate)
Automatic Check of Exchange Rates (Invoice issue date Vs SAP Table Rate)
ID 1929 ARG: request to add and automatic validation to verify the difference between the Exchange Rate in the
Issue Invoice that are posted against the SAP Exchange Rate table and check a value as limit.
Currently Argentina does not have this functionality in SAP.

Credit Invoice document Legal Validation request

ID 1950 ARG: is required to fulfill the Legal validations of the Credit Invoice from Vendors. (is Not Electronic Billing
invoice to customer)
Currently Argentina has developed in 2019 year with a Third-party Vendor the Process, a Z program and Z monitor
in SAP to have a solution.
ABB Template does not have a program to fulfill this local requirement.

739547767.docx 27 of 33
 In case that we continue with the Z programs, will be necessary to review technically and extend the Program to the
new SAP.

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).

ARG-URY
Blocking type to control a Credit note posted
ID 1105 ARG: a Blocking type “F” was implemented that ensures that an invoice affected by a Purchase Order, with
an Open Advance, cannot be released for payment without the Credit Note canceling the advance has been posted
(development in SAP)

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.

ARG-URY
Program to send TXT Electronic File with payments to Bank
ID 1930 ARG/URY: Is required a Program to create the TXT eletronic files, according the formats of local Banks.
Currently have the Program Zpaylink which creates the TXT file with Payments information created by Trx F110 in
SAP according some Argentina and Uruguay Banks formats requirements. Currently download and send manually to
each Bank.
ABB Template must confirm which Program has to be used by these 2 Countries. The ARG/URY Program or the
Brazil Program.
In case that we continue with Zpaylink will be necessary to review technically and extend the Program to the new
SAP.

Interface to send TXT Electronic File with payments automatically to Bank

ID 1931 ARG/URY: after the Program Zpaylink creates the TXT file is required to develop a new Interfase/process to
send the TXT electronic Files to each Bank automatically from the new SAP.
ABB Template does not have a Program to Interfase these Files according the technical definitions of each Local
Banks.

Payment Advice
ID 1942 ARG/URY: is required to send to the vendors a payment advice form with all the information related each
payment, invoices, withholding, etc.
Currently these countries have a Z Program in SAP.
ABB Template does not have a program which send these forms according local requirements.
In case that we continue with the Z program, will be necessary to review technically and extend the Program to the
new SAP.

Treasury Bank Statement and reconciliations

ID 1947 and 1948 ARG/URY: is required that the Electronic bank statement is processed in
SAP and clear bank accounts and also vendor and customer account..

739547767.docx 28 of 33
 A manual bank statement occurs when is not possible the bank sends all bank movements by files, so manually users
maintain this information by transactions properly development to this functionality.
Currently Argentina has internal Process and a Z program developed to have this solution.
ABB Template does not have a program to fulfill these local requirements according the local Banks Structure formats
and the module is configured according Brazil requirements.
In case that we continue with the current Z program will be necessary to review technically and extend the Program to
the new SAP, also make all the configurations of the Treasury modules related all the Banks, reconciliations keys,
etc.

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.

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.

ARG-URY
Withholding Tax Certificates
ID 1943 ARG: is required to send to the vendors a Withholding tax Certificates forms with all the information related
withholding taxes, etc.
Currently this country has a Z Program in SAP.
ABB Template does not have a program which send these forms according local requirements.
In case that we continue with the Z program, will be necessary to review technically and extend the Program to the
new SAP.

Electronic Withholding Tax Certificates and Interfase with Government

ID 1944 URY: is required to send to the vendors a Withholding tax Certificates with all the information related
withholding taxes, etc. in Electronic format and Interfase in automatic way the Tax legal entity of Uruguay
Currently this country has a Z Program in SAP.
ABB Template does not have a program which send these forms according local requirements.
In case that we continue with the Z program, will be necessary to review technically and extend the Program to the
new SAP.

INTERNAL PURCHASE AND 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.

739547767.docx 29 of 33
PAYMENTS WITH CHECKS
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.

ARG-URY
Checks Payment method
ID 1935 and ID1936 ARG/URY: required to have a process, module, Programs and Forms to pay with Checks
Payment method.
ABB Template does not include the steps of this Process/request and does not provide the module, Programs, forms,
etc.
ABB Template must confirm if we can replicate the Process, configurations, Programs, Forms to the new SAP.

RETURN 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.

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.

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.

ARG-URY
Employees Travel and Expenses processes and reimbursement
ID 1951 and 1952 ARG/URY: is required to have in the new SAP a Process functionality related Employees travel
and Expenses and reimbursement of expenses.
Currently these countries have Tool connected with Lotus notes and Z program in SAP as a solution with approvals
levels and Workflows integrated with cost objects, positions, etc.
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.

PETTY CASH
Currently, the Template does not handle petty cash processes.

ARG
Petty Cash Process/Program
ID 1955 and 1956 ARG/URY: is required to have in the new SAP a Process functionality to manage a small
expenses and refund.
Currently these countries have a defined Process and Z Program with approvals levels and Workflows, etc.
ABB template does not include this Process in the Template and do not provide any global program as a solution.
In case that we continue with the Z program, will be necessary to review technically and extend the Program to the
new SAP.

739547767.docx 30 of 33
1.6. Process Flow

1.7. Process Steps

1.8. Solution Elements (Work Breakdown Structure)

<list all objects for configuration, development, conversion or execution; show integration
with legacy or external systems if applicable; list all objects that need conversion and how
it is planned to be executed; adapt the table format according to the platform or system or
activity (SAP, other applications, infrastructure, … >

1.9. Integration Points (Cross Module)

<list all integrations points between systems and/or modules (SAP), listing the responsible to execute the activity>

1.10. Application Mapping

1.11. Interfaces

1.12. Standard Reports

1.13. Key Design Considerations and Out of Scope

<list functionality and scenarios NOT covered by this solution, if any>

739547767.docx 31 of 33
1.14. Test Strategy
<topics to be considered: definition of the scope of the test, who will test, how the test will
be executed, in which period the test will take place, what tools will be used, acceptance
criteria, who will approve the final results >
<SAP: for Gate 3, the Test Plan and Execution document (use template TPE) must be
created to further detail and plan this item>

1.15. Deployment Strategy

<topics to be considered: training requirements, communication, data migration
requirements, data preparation activities by business and IS>
<SAP: for Gate 3 the Cutover Document (use template COD) must be created to further
detail and plan this item>

1.16. Approximate Timeline for Deployment

<estimate project timeline (duration) until Go Live>
<for Gate 3 a detailed Project Plan must be created>

1.17. Effort and Resources Estimate

<for Gate 2, use Estimation template (SAP). IS cost only (resources, software, hardware).
Required resources (profiles or competencies) must be listed both for IS and business.

1.18. Assumptions

1.19. SAP Profiles

1.20. Roles and Responsibilities (IS)

<list any specific roles and responsibilities not already defined as standard in IS SAP
Governance, for example when multiple modules or IS domains are involved>

739547767.docx 32 of 33
1.21. Documents (IS)
<specify all documents to be created and made available in the official IS documentation
repository as part of the project, as required according to IS Governance. Insert more lines
as required. This list will be used to validate finished and approved documentation at the
Gate 4 and 5 Reviews>

Document type Document Description (Name)

(FSD, TSD, (XYZ_<Project Name>_<free text>_version)
COD, …)

739547767.docx 33 of 33