Project EVO

AP260 – Integration Conceptual Design

Spain
Version: 1.4
4 March 2010
 Integration Conceptual Design 509928699.doc Version: 1.34

Document Control
Location:
Clear Quest ID : EVOPR00072019

Document Owner
Owning Team Author
Local Implementation Team (ACN) Lorenzo Bavasso
Local Implementation Team (ACN) Javier Revert

Document History
Author Date Version Comment
Riccardo Lazzari 21/01/10 0.1 Initial Draft
David Flores 21/01/10 0.1 Initial Draft
Juan Jose Marquez 21/01/10 0.1 Initial Draft
1.0
David Flores 16/12/09 Final Version
1.1
Juan Jose Marquez 18/12/09 Final Version

Javier Revert 19/01/2010 1.2 Feedback from IT and Finance incorporated

David Flores 04/02/2010 1.3 BI Landscape included
David Flores 04/03/2010 1.4 Last feedback updated

Document Review & Signoff

Name Position Action Approved
Fernando Garcia Vodafone Spain Project Manager S
Javier Ibarrola Vodafone Spain IT responsible R5-Spain FR
Miguel Angel Sanz Vodafone Spain IT FR
Joao Dias Vodafone group IT responsible R5-Spain FR
Marta Varela IBM Project Manager FR
Herminia Sanz Process Lead (HR) FR
Pilar Sarrio Process Lead (SCM) FR
Ana Rial Process Lead (FIN) FR
S = Signed Approval Required, QA= Quality Assurance Review Required, FR = Formal Review Required, IR = Informal Review, I = For Information.

Related Documents
Title Comment
Team Room Location: https://teamrooms3-
vista.vodafone.com/eRoom/Global99/VFSpain/0_bbbb
AP260 Integration Conceptual Design
Clear Quest ID: EVOPR00001943

Modified: 04/02/2010 Page 2 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

Related Documents
Team Room Location: : https://teamrooms4-
TA223 Application Architecture Specification –
vista.vodafone.com/eRoom/Global70/Fatmatayekinni/0_1d200
Overview
Clear Quest ID: EVOPR00001951
Team Room Location: : https://teamrooms4-
TA223 Application Architecture Specification –
vista.vodafone.com/eRoom/Global70/Fatmatayekinni/0_1d24c
Integration
Clear Quest ID: EVOPR00003689

Modified: 04/02/2010 Page 3 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

Table of Contents:

1. Purpose............................................................................................................................................................. 6
1.1 Overview..................................................................................................................................................... 6
1.1.1 Target Audience.................................................................................................................................... 8
1.1.2 Document Lifecycle............................................................................................................................... 8
1.2 Assumptions................................................................................................................................................. 8
2. Local integration requirements.......................................................................................................................... 9
2.1 Context diagram........................................................................................................................................... 9
2.1.1 Data Flow Diagram Finance................................................................................................................. 10
2.1.2 Data Flow Diagram SCM..................................................................................................................... 16
2.1.3 Data Flow Diagram HR........................................................................................................................ 18
2.1.4 Data Flow Diagram BI......................................................................................................................... 20
2.2 Legacy systems.......................................................................................................................................... 21
2.3 Interfaces................................................................................................................................................... 22
2.3.1 Interface Inventory............................................................................................................................... 22

Modified: 04/02/2010 Page 4 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

Table of figures
Figure 1 – Integration Conceptual Design - Documents................................................................................................... 6
Figure 2 – Integration Architecture Overview................................................................................................................ 7
Figure 3 – Global Data Flow TO BE Context Diagram.................................................................................................... 9
Figure 4 – Data Flow B&P......................................................................................................................................... 10
Figure 5 – Data Flow OTC......................................................................................................................................... 11
Figure 6 – Data Flow LTD (SCM and FIN)................................................................................................................. 12
Figure 7 – Data Flow P2P.......................................................................................................................................... 13
Figure 8 – Data Flow RTR......................................................................................................................................... 14
Figure 9 - Data Flow FI-TCM..................................................................................................................................... 15
Figure 10 - Data Flow FI-TAX................................................................................................................................... 15
Figure 11 – Data Flow SCM-OTC.............................................................................................................................. 16
Figure 12 – Data Flow SCM-PFU............................................................................................................................... 16
Figure 13 – Data Flow SCM-PTP............................................................................................................................... 17
Figure 14 – Data Flow SCM-SRM.............................................................................................................................. 17
Figure 15 – Data Flow L&D....................................................................................................................................... 18
Figure 16 – Data Flow R&R....................................................................................................................................... 18
Figure 17 – Data Flow RES........................................................................................................................................ 19
Figure 18 – Data Flow WPA...................................................................................................................................... 19
Figure 19 – Data Flow BI........................................................................................................................................... 20

Table of Tables
Table 1 – Legacy Systems.......................................................................................................................................... 21

Modified: 04/02/2010 Page 5 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

1. Purpose
1.1 Overview

During the Design stage of CBM Design, the Integration Conceptual Design was created to contain the high-level design of
the overall end-to-end “normalized” integration solution between the EVO Systems and the Integration Layer and to describe
the common flows (Global interfaces as well as SAP to SAP).

The aim of the Local Implementation conceptual design is to describe in detail the integration requirements of the specific
OpCo.

Integration • Global context diagram (Data flows &

conceptual Global interfaces)
• SAP to SAP (ALE) interfaces
design - Global
• Data Flow interface agreements
• Conversion methods
(1 doc) • Summary of the OpCo landscape

• Local context diagram

Integration • Local interface classification
conceptual
design - Local

(1 doc per OpCo)

Figure 1 – Integration Conceptual Design - Documents

Modified: 04/02/2010 Page 6 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

EVO landscape OpCo landscape

SAP XI Synchronous Legacy

Message System
1

Asynchronous
Message
2

File
3

ETL

Partner 3rd Party

Kit System

3rd Party Landscape

Data Flows (normalised flow) Interface Flows (specific mapping)
Loader/ SAP Data Objects (BO) Legacy systems format Loader/
SAP format (w3c) Legacy systems mapping
Extractor Extractor
Figure 2 – Integration Architecture Overview

The types of Interface Flows shown in the picture are:

(1) Message based Synchronous calls.
(2) Message based Asynchronous messages.
(3) File based.

This is a brief overview of the Interface Flows available. Refer to deliverable “TA223 Application Architecture Specification
– Integration” for a detailed description of Integration Architecture.

Modified: 04/02/2010 Page 7 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

1.1.1 Target Audience

The Integration Conceptual Design – Local is intended for:

 Implementation – Solution centre – Use the deliverable to understand the integration requirements and to define the
functional specification of the interfaces accordingly
 Implementation – Development centre: use the deliverable to obtain a general understanding of the integration
solution planned in the OpCo.
 VF EVO Team: Use the deliverable to check the consistency of the planned solution. Summary data are collected
and reported in the general documents. New requirements are evaluated and reported in the document when
applicable (e.g. new data flow)

1.1.2 Document Lifecycle

This document is built during the Analyze stage of the release, and, when necessary, updated during the design stage.

1.2 Assumptions
The following described assumptions apply only to the Local Integration Conceptual Design:

 Only interfaces identified in the local fit/gap sessions and defined as local Gap are described in the Local Integration
Conceptual Design, and after acceptance by EVO Architecture Team
 If there are changes necessary to the Local Integration Conceptual Design, the document will be updated
accordingly (e.g.: dataflows to be used).
 The local Integration Conceptual Design covers all legacy systems and interfaces which will interface with EVO.
 EVO is the Master of Master Data
 If the same Data Object has to be transferred / received to/from different legacy systems only one interface will be
set-up on EVO side. The data will be collected / distributed from / to the involved legacy systems on Opco side (eg.
Using the local integration layer)
 All the interfaces in scope are considered to be asynchronous.
 The following integration scenarios are foreseen in terms of connectivity:
 Scenario 1)
File Based Interfaces -> To Go via Informatica + Connect Direct
 Scenario 2)
Message Based with SAP Legacy -> To Go via SAP PI with IDOC ADAPTER directly to/from Legacy SAP
 Scenario 3)
Message Based with “non SAP” legacy systems -> To Go via SAP PI + TIBCO using SOAP Adapter
 Interface list was consolidated under the assumption, from a Value Mapping perspective, that Value Mapping will
be done generally on the EVO side.
 This document only contains connections between EVO SAP and the different Legacy systems. Document
“Integration Conceptual Design – Legacy View” will contain all connections between different Legacies, and it is
not under Accenture scope.

Modified: 04/02/2010 Page 8 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

2. Local integration requirements

This chapter explains the overall context diagram of the OpCo with the legacy system and required interface.
 The first section contains the diagram flows for each stream. At the time of this document some of the dataflows to
be used were not yet defined and/or created. These are indicated as TBD (To Be Defined) and will be updated
during the design stage. Also, the IDs indicated for the interfaces are the requirements IDs since at this time there
hasn’t been defined yet the interface IDs. This must also be updated at the design stage.
 The second section presents a brief description of the legacy systems which will interact with EVO.
 The third section describes more in detail the required interfaces mentioned in the dataflows.

2.1 Context diagram

General diagram with interfaces in scope in all the streams.

PPM S.P.I.

Operating readiness
Work Breakdown Structures Date (73956)
and Projects creation Work Breakdown Structures
(73954) and Projects creation
Locations (73954)
(73957)

Operating readiness
Date (73956)

GL Interface (73959) Local gap: Checks (73966)

GL Payroll (73960) Core gap: Confirming (73967)
DBANK
Return payments (73958) Core gap: Direct Debit (73969)
Vendor master data (73965)

Internal Orders (73964)

SAP EVO Core Gap: PR item automatic load for
File for PR
high volume line items - PR by CO owner Creation
(74355)
SAP Legacy
Roaming Indirect Tax Code (74501) SAVIA : Cost Centers (75558)
SAVIA : FI Balances (75557) SAVIA
SAVIA : Account Master (75559)

Employee Main MD Interface – (73433) Synerquia

Vacant Positions (73434)

Infotype 7 and 8 (73975)

Training Catalogue + Cost center

EVO HR Workplace Information (modification) (73972) VCDS
Notes
(Travel (73971)
Expenses)
Massive upload
Notes Training Catalogue + Cost Center Course Evaluation – Happy Sheet (73970) of Course
(Travel (73971) evaluation results
Request)
Legend:
Normal interface Local system
Pending to confirm during design phase Global system
Out of scope interface

Figure 3 – Global Data Flow TO BE Context Diagram

Modified: 04/02/2010 Page 9 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

2.1.1 Data Flow Diagram Finance

Hyperion interface (planned values) Local Legacy CBM Manual upload

Planning
System

Hyperion CBM Hyperion interface (actuals)

Global SAP EVO BI
Local interface

CBM retractors
and extractors

SAP Legacy OFA (DWH)

EVO ECC

Retain or decomission

Hyperion AIDA (DWH)

Local

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 4 – Data Flow B&P

Modified: 04/02/2010 Page 10 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

SIGRA INTRA

131-Post of Roaming invoices

(Posting/Clearing)
338-SIGRA-Roaming OUT Roaming
390-SIGRA-Roaming IN

FCH

CBM Roaming interface

(GL) AP Netting Open Posting (73959)

(GL) Site sharing AR Invoicing (73959)
Roaming Indirect Tax Code (74501)
SAP Legacy
SAP EVO
SAP Legacy

Retain or decomission

Comisiones COTO WAMA AIDA (DW)

EDItran EDI service SAVIA (DW)

Portal
IXOS
Comercial

DOC1 Legend:
STRATUS
Printer comp. Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 5 – Data Flow OTC

Modified: 04/02/2010 Page 11 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

PPM S.P.I.

Work Breakdown Structures

and Projects creation
(73954)
Operating
readiness date
(73956)
Operating Locations
readiness date (73957)
(73956)

Work Breakdown Structures

and Projects creation
(73954)

G/L Posting Interface (73959)

SAP Legacy SAP EVO

SAP Legacy
Core Gap : PR item automatic load for
high volume line items - PR by CO owner (74355)

Creación
DWH (DW) SAVIA (DW) DWH
SBS Gasto
File for PR
Creación SBS Recepción Conformidad de Creation
SBS
Inversión SBS Inversión pedidos de Gasto

Actas de
HdP MAIL
Aceptación

Legend:
Normal interface Local system
Pending to confirm during design phase Global system
Out of scope interface

Figure 6 – Data Flow LTD (SCM and FIN)

Modified: 04/02/2010 Page 12 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

Liquidación TL2-
TL2-90X Callidus
De Gastos Comisiones

335-AP Open Items Comisiones

336-AP Open Items
65-Vendors Master Data
250-Accounting of the invoices
147-Full expenses in order to update sended (Postings of commisions)
the state of the lines in NOTES
244-Update the database of cost centers
148-Employee's expenses (Posting/Clearing) (Update the database of cost centers)
149-Employee's expenses (to account them) 249-Vendor Master data

NOTES: (GL) TL2-Comisiones: AP Open Items (73959)

Teléfonos (GL) TL2-90X: AP Open Items (73959)
empleados (GL) Site Sharing/Operators: AP & AR Open Items (73959)
(GL) Sites Rentals: AP Netting Open Items (73959)
(GL) Comisiones: AP netting item (73959)
Sites Rentals 250-GL Posting from (GL) Employee expenses nominas (73959)
SAP Legacy to EVO (GL) Teléfonos de empleados (73959)
(GL) Downpayment for employees (73959)
SAP Legacy Return payments (73960)
STRATUS Vendor master data (73965)
Traspaso saldos: pago comisiones SAP EVO
SAP Legacy
Intercompany

Stock Transfer – Accounts Receivable open items

Stock Transfer – Accounts Payable open items

CBM Roaming – Vendor Master

data outbound (EVOPR00008776)

FCH
Retain or decomission
CBM Inbound E2O 93-Invoices from the electrical /
Portal Content Vizzavi (EVOPR00000993) renting companies
SAVIA (DW)
Comercial Master Stratus
131-Post of Roaming invoices
(Posting/Clearing)
AP & AR Open Items
DOCOUT Galery DOC1 DWH (DW) Roaming (Manual) TIBCO

SIGRA & Electrical

Portal de B2BeHub
TL2-80X FINTRA Companies
proveedores

Vizzavi Legend:
Atomium Normal interface Local system
Intra
Pending to clarify the interface Global system
Out of scope interface

Figure 7 – Data Flow P2P

Modified: 04/02/2010 Page 13 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

Comisiones ADP
Nómina

5-GL journal entries

Vendors

GL Payroll (73960)

CBM Hyperion Interface (EVOPR00001011)

(GL) Posting (73959) (Actuals)
Cluster

SAP Legacy Hyperion

SAP EVO
Internal Orders (73964)
SAP Legacy

Retain or decomission

GPM BSC (DW)

STRATUS SAVIA (DW)

Arbor AIDA (DW)

Geneva OFA (DW) Legend:

Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 8 – Data Flow RTR

Modified: 04/02/2010 Page 14 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

Local gap: Checks (73966))

Core gap: Confirming (73967)

Core gap: Direct Debit

(GL) Mixed payments (73959) (with ECC extension) (73969)
(GL) Outgoing direct debit payments (73959) DBANK
SAP EVO
SAP Legacy
CBM Interface between Bank and ERP
SAP Legacy

Editran Net Plus Passat + CTRUS

Stratus Sira WEB Arbor

Geneva Clarif Otros CBM

GL FCH

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 9 - Data Flow FI-TCM

SAP Legacy
SAP EVO
SAP Legacy

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 10 - Data Flow FI-TAX

Modified: 04/02/2010 Page 15 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

2.1.2 Data Flow Diagram SCM

SAP Legacy

EVO
SAP Legacy

Retain or Decommission
Portal SEGMEN COMISIO Control PROMES
Comercial TACION NES IMEI A

SILVEND SVT PRECOS Passat+ Portabilidad

Operador
DOC1 Credits VOM Logístico
NOVA

Fraude NOTES
Maestros IRIS Distribución DOAS
NOTES
Intercambio
Tienda Tienda de
WAMA FAXINATION
Online puntos
Empresas
Externas
Legend:
NOTES Normal interface Local system
Telefonos BSC CUVA Pending to clarify the interface Global system
empleados Out of scope interface

Figure 11 – Data Flow SCM-OTC

SAP Legacy SAP EVO

SAP Legacy

Retain or Decommission
Control
CUPRA CLARIFY NOVA
IMEI

SVT Chordiant TARISM IRIS

Tienda de Gestión de Fraude Portal

puntos stocks Distribución Comercial
Intercambio de NOTES NOTES :
Recepción Empresas
SBS inversión externas DOAS 129
Legend:
NOTES : BSC AIDA Normal interface Local system
Cambio de SIM DWH
a domicilio (DWH) (DWH) Pending to clarify the interface Global system
Out of scope interface

Figure 12 – Data Flow SCM-PFU

Modified: 04/02/2010 Page 16 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

B2B

CBM Interface with B2B Hub – PO confirmation from Vendor (EVOPR00000930)

CBM Receive ASN from B2B (EVOPR00000932)
CBM Purchase requisition item automatic load for high volume line items (EVOPR00000935)
CBM Interface to get notified about GR & automatically create virtual GR (EVOPR00001182)
CBM Redirect advance shipment notification (EVOPR00001183)
CBM Resend PO confirmation/rejection to OpCo once is received from final vendor (EVOPR00001185)
CBM Inbound E2O (Invoices) (EVOPR00000993)
CBM Interface with B2B Hub - Purchase Order (EVOPR00000929)
CBM Interface with B2B Hub - Goods Movements (EVOPR00000931)
CBM Redirect advance shipment notification (EVOPR00001183)
CBM Resend PO confirmation/rejection to OpCo once is received from final vendor (EVOPR00001185)
CBM Interface with B2B Hub - Material Master Data Create / Changes (EVOPR00000918)
CBM Send invoice to the non-EVO OpCo (EVOPR00001186)
SAP Legacy
Vendor Master Data (73965)

SAP EVO
CBM Contract Interface with Emptoris IN (EVOPR00000921)
Document
FAX Provider
SAP Legacy Archiving

EMPTORIS
CBM Vendor Master Data (EVOPR00006742)
CBM Material Master Data (EVOPR00022330)

Retain or Decommission
NOTES :
B2B Terminales de CBM Contract Interface with Emptoris OUT (EVOPR00008451)
Empleados MDM CBM Control Data Interface with Emptoris OUT (EVOPR00000922)
CBM Interface with Emptoris: Vendor Master Data (EVOPR00000923)
Portal de
IXOS FAXINATION
Proveedores

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 13 – Data Flow SCM-PTP

SAP Legacy SAP EVO

Document
FAX Provider
Archiving

Retain or Decommission

Creacíon SBS Creacíon SBS Recepción

Gasto Inversión SBS Inversión
Conformidad de
pedidos de IXOS FAXINATION
GASTO

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 14 – Data Flow SCM-SRM

Modified: 04/02/2010 Page 17 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

2.1.3 Data Flow Diagram HR

ASPEN
EVO ESS/MSS
Global

Training Catalogue (OUT)

Course Registration (OUT)
Course Result (IN)

Training Catalogue (OUT)

Course Registration (OUT)
Course Result (IN)
EVO
Main MD Interface
SAP Legacy Main MD Interface - 73433 Integration 73433 SAP EVO
Layer
Training Data
73971

Course evaluation Results -73970

Training Data + Cost Center

73971
Massive upload of
Course evaluation
results (Happy
Notes Travel Notes Travel Sheets)
Request Expenses

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 15 – Data Flow L&D

MERCER
ARBOR
Flex Benefit
Manual Upload

Pension Plan
Lunch Voucher Infotype 14 discounts
74063

CBM - TCR Interface CBM - TCR Interface

Pension Plan Pension Plan
Lunch Voucher Lunch Voucher
EVO
SAP Legacy Integration SAP EVO
Layer Main MD Interface
Main MD Interface - 73433
73433

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 16 – Data Flow R&R

Modified: 04/02/2010 Page 18 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

EVO Main MD Interface

SAP Legacy Main MD Interface - 73433
Integration Layer 73433 SAP EVO

NEW – Open Positions

Publishing
NEW – Open Positions
Publishing
73434

Synerquia EVO - eREC Integration

External Job Board

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 17 – Data Flow RES

3 – Employee MD with policy details (IN)

Adeslas 4 – Employee MD for Empl.with Med Ins (OUT)
216 – Employee MD Portal Comercial

159 – Next Termination NOTES - Bajas

ADP of Employee

7 – Employee Payroll Data IDM

236 - Employee MD Org Str.
Network
ARCHIBUS 305 – Employee Data
306 – Area Data Red Online
307 – Job Data (ESS/MSS) Link to EVO ESS/MSS
Remedy
308 – Datos Territoriales
309 – Employee MD (Weekly)
31 – Employee MD

IRIS 105 – Employee MD and CC

106 – Employee Org. Structure Factura Web
135 – Employee MD

Punto Net 162 . Payroll Wages Type NOTES

(Grecia) (Availability
164 – Personsin charge hours)

238 – Employee MD
Org. Structure
Red Online Red Online

Gestion Plantilla
SAP Legacy 1 – Infotype 7 change of working hours (Daily)
2 – Infotype 8 Change number of payments (Daily)
1 – Infotype 7 change of working hours (Daily)
2 – Infotype 8 Change number of payments (Daily)
SAP EVO
73975 EVO 73975
Integration Layer
405 – Future Hiring
Main MD Interface - 73433 Main MD Interface - 73433
and active employees

Cheque Gourmet 61 – Employee MD CBM - Massive

132 – Information for Incentives Upload of Org. Employee and Org Data (OUT)
133 – Incentives Situation INCENTIX Changes Mgmt Communication and Work Location Data (IN)
134 – Inventory of Jobs 73972
123 – Employee MD
AS-IS
ACCOR 1 Employee MD
160 – Employee MD Org. NOTES
Structure and CC
Auxiliary Tables
IDM Global VCDS
MERCER 342 – Employee MD

People Finder Digital Mobile

NORMADAT NOVA FREMAP BSCH
(VCDS) Signature

NOTES Request
External from
VAMBREDA Learning Space of advanced IXOS
CaC (NOTES)
payments

COMISIONES NOTES Plan of

NOTES Benefits BSC (DW) ARBOR
(CID) Pensions Legend:
Normal interface Local system
IDM Pending to clarify the interface Global system
OFA (DW) SAVIA (DW) DWH WinSuite
Local Out of scope interface
OUT of EVO Scope

Figure 18 – Data Flow WPA

Modified: 04/02/2010 Page 19 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

2.1.4 Data Flow Diagram BI

SAVIA

SAVIA: FI Balances (75557) SAVIA: P&L accounts balance (75556)

SAVIA: Cost center master data (75558) SAVIA: Investment movement details (75560)
SAVIA: Accounts master data (75559) SAVIA: Asset Totally depreciated (75561)
SAVIA: Investements detail (75562)

SAP EVO ECC SAP EVO BI

Retain or decomission

BSC CUVA DWH OFA

AIDA

Legend:
Normal interface Local system
Pending to clarify the interface Global system
Out of scope interface

Figure 19 – Data Flow BI

Modified: 04/02/2010 Page 20 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

2.2 Legacy systems

In this section the relevant legacy systems, which will interface with EVO, are summarized and described.

The table covers following information:

 System name: System name of the legacy system
 Area: Area in which the legacy system is used.
 Description: Contains a short description of the legacy system

Area Subarea Legacy System Description

FIN FI - LTD S.P.I. / PPM S.P.I. (Solicitud Proyecto Inversion): Front end to create investment
projects for the Network Area. It is based in Notes database and has
synchronous interfaces with SDP and SAP. Once created, the projects are
loaded in SAP.
FIN FI - RTR SAP Legacy Local SAP System
HR HR-L&D NOTES (Travel Travel Approval: Travel request and approvals, integrated with the travel
requests) agency
FIN FI - TCM DBANK Deutsche Bank
HR HR-RES Synerquia (External Local External Jo Board
Job Board)
SCM SC - NET HDC Herramienta de Configuracion: Inhouse visual basic application to define
technical network elements and their configuration.
HR HR-WPA VCDS Vodafone Company Directory System
HR HR-WPA Manual File upload New Hire External (Batch Input on EVO HR, fil upload)
HR HR-WPA Manual File upload Non-employee. Manual Upload
HR HR-L&D Manual File upload Massive upload of Course evaluation results (Happy Sheets)
FIN FI-RTR SAVIA Application based on SAS Activity-Based Management (SAS ABM) that is
an analytic application that models business processes to determine cost,
profitability and drivers.

Table 1 – Legacy Systems

Modified: 04/02/2010 Page 21 of 22 Last modified by: david.flores.losada

 Integration Conceptual Design 509928699.doc Version: 1.34

2.3 Interfaces
This section contains the details on the interfaces required at OpCo level with EVO. The several interfaces are listed in the
following embedded tables, divided by the work streams Finance, HR and SCM. Some of its information may be updated at
the design stage. In that case these embedded files must also be updated.

2.3.1 Interface Inventory

Integration
Conceptual Design_ES.xls

Detailed information related to this interface list could be modified during design phase.

Modified: 04/02/2010 Page 22 of 22 Last modified by: david.flores.losada