SAP transformation & harmonization

Transcription

1 SAP transformation & harmonization Zagreb, Ljerka Oberman, T-HT Saša Gogić, Siemens

2 Agenda Project overview Challenges Achievements Project summary Q & A

3 Project scope

4 SAP Transformation project phases 1. System analysis ( ) 2. Blueprint ( ) 3. Implementation ( )

5 Agenda Project overview Challenges Achievements Project summary Q & A

6 Challenges First SAP implementation 10 years ago (FI / CO) Many different subcontractors/developers (foreign and domestic) Parallel disjunctive development for T-Com and T-Mobile Complex system landscape Many customer developed programs/reports Possibility to differentiate between fixed and mobile business after merge (separate Balance sheet and P&L statement) Very tight schedule (6 months)

7 System analysis System analysis Results Systems scan with STT Analysis of org. elements, documents, customizing, business data, reports and tables Workshops for all SAP Modules Analysis of all business processes and interfaces to/from SAP system According to workshops results and system analysis ->creation of possible scenarios for implementation

8 Results of system analysis by STT Organizational elements Huge number of organizational elements Complex organizational structure Different combination of sales org., distribution cannel, sales group, sales office Unused organizational elements 34 plants Different customizing between the company codes Customer designed programs and tables 300 customer designed tables with company code 761 customer designed programs with company code 8661 program lines with company code Many hard coded program lines with company code HT or M The system has very high number of customer designed tables and programs which are using the company code. All programs / tables had to be checked, changed and tested.

9 Harmonization Variant 1 Company code harmonization without historical data Creation of a new company code (T-HT) starting with the new company code in the new fiscal year Benefits Company codes HT and M still existing for historical fiscal years Less data transition needed Only master data has to be copied by STT Challenges All existing organizational elements have to copied (plant, controlling area, sales organization, etc.) Existing documents can t be copied for further processing (returns, correction) Lose document flow Open item transfer All open processes have to be transferred to the new organizational elements (LSMW) Programming for all organizational elements have to checked / changed (Programs in total nearly 3000)

10 Harmonization Variant 2 Company code harmonization with historical data Merge of company code M into company code HT with all historical data over all fiscal years Benefits Transferring all historical data Cross years reporting possible Using existing organizational elements Company code M does not exist on the system, no false entries are possible No differentiation of data regarding the fiscal year easier transition rules Existing documents can be used as copy template for returns, correction entries, etc. Challenges Auditors approval of transformed system

11 Agenda Project overview Challenges Achievements Project summary Q & A

12 Organizational scenario: Merging CC M into CC HT T-Mobile T-HT T-Com CC = M CC = HT BA = HT BA = M CC = HT

13 Merging CC M into CC HT Financial data (contains CC) All historical financial data is transformed - CC M to HT Business area is added to all historical financial data Number ranges double document numbers in target company are changed: Document from CC M: > Number range is changed: Old: New: Number range is used for documents from CC M Non-financial data (does not contain CC) Reassigned to CC HT through organizational structure changes

14 How to get Balance Sheet and P&L per BA HT M Balance sheet P&L Balance sheet P&L

15 Balance Sheet Business Area Adjustment FI document FI document for adjustment Adjustment per BA FI document for adjustment FI document FI documents daily entries Calculation of BS adjustment Adjustment per BA FI document Balance sheet adjustment postings Document for adjustment HT Document for adjustment M

16 BA Adjustment FIDocument BA adjustment VENDOR 123,00 COSTS HT 70,00 M 30,00 VAT 23,00 VENDOR ADJUSTMENT 123,00 86,10 HT 36,90 M VAT ADJUSTMENT HT 16,10 23,00 M 6,90

17 Non-Assigned Postings per Business Area Posting date: Bank account 1.000, Clearing account 1.000,00 Splitting key per BA Account type 100 Bank account Balance HT : M = 70 : 30 Posting date: T Bank account 1.000, T Bank account 700,00 HT 10000T Bank account 300,00 M Posting date: T Clearing account 1.000, T Clearing account 700,00 HT 10090T Clearing account 300,00 M

18 Agenda Project overview Challenges Achievements Project summary Q & A

19 Project summary Staffing Cross functional / application / company project 127 T-HT employees (IT, Business) 57 consultants 5 auditors many working days and weekends Successfull project resulted with: 3 SAP systems transformed 19 external systems involved Fully supported by project sponsor and steering comitee!

20 SAP and external systems T-Com systems HRNet SAP Mobile IST THT CMIS DWH THT Intec WWMS Kofax ALKOE Archibus Infoweb FileNet Mini HR Master (HT only) CO AA FI (GL, AP, AR, TR, AA) SD PS, IM MM (PUR, IM, LIV) SAP Core E-lease IST TM DWH TM SAP Mobile E-vouchers Pegabase TRGO T-Mobile systems

21 SAP Transformation project plan 7/2009 8/ /2009 9/ / /2009 1/2010 2/2010 RFP Proposal System analysis Scen. choosen Kickoff meeting Blueprint accepted Blueprint phase Development changes for Programs changes Dev. & customizing Funct. testing Writing of test scenarios Testing & UAT for Go-live Necessary changes Implementation start 2 Integration tests Corrections Data mig. sign-off UAT Documentation and user education GO-LIVE Go-live Prep. Technical doc. final version / After go-live support

22 SAP system landscape DE1 Development system 2 clients (100, 500) All changes in DE1 copied manually to MD1 One-off system copy MD1 Development system Copy of development 2 clients (100, 500) TS1 Test system Shared file system 500 GB MC1 Test system (new copy of production) TR1 Test system Copy of production SA1 Test system Copy of production PH1 Production system T-HT external systems (all systems) New system copies for each test rounds T-HT external systems (all systems)

23 Go-live weekend (12:00) (20:30) Cut over all systems (SAP Core + SAP IS-T) All systems were unavailable for end users All interfaces to external systems were stopped All steps according to cut over plan were performed Migration was accepted by migration team and auditors (20:30) Go live decision (08:00) All systems and interfaces are available

24 Project summary - activities 860 programs analyzed, 420 programs changed 600 transport requests Authorization concept was adjusted by T-HT IT 1 functional, 2 integration and 2 acceptance tests performed by consultants, IT sap.ap, sapteam and business key users 2 go-lives ( and ) Support to development and testing activities by IT - BC and AP team 4 times whole test environment established (SAP core, HT SAP IST, T Mobile SAP IST) 19 Interfaces to different test systems established according to the test plan for each environment Aprox records updated on SAP Core system Aprox records updated on SAP IS-T systems

25 And what next? SAP Optimisation project SAP ERP newgl implementation project

26 Agenda Project overview Challenges Achievements Project summary Q & A

27 Thank you for your attention! Ljerka Oberman Head of ERP Work Unit Saša Gogić Project manager T-HT Hrvatski telekom Siemens IT Solutions and Services