Cutover SAP All Presentation 202413.pptx

adeelshoukat56 483 views 26 slides Jun 13, 2024
Slide 1
Slide 1 of 26
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26

About This Presentation

Sap all modules presentation in 1 ppt read write upload . Upload new document .

You can select a four-character alpha-numeric key as the company code key.
This key identifies the company code and must be entered when posting
business transactions or creating company code-specific master data, for...


Slide Content

NTDC SAP Implementation Cutover Strategy & Planning June 10, 2024 3 pm – 5 pm

Topic Introduction of Key Terminologies Cut Over Overview & Strategy Key Decisions & Recommendations Module Specific Cutover Agenda 1 2 3 4

Introduction of Key Terminologies 1. Cut Over The process of transitioning from one system to a new one is called Cut O ver. Project cutover refers to the phase when the Project goes Live. Project Cutover is an activity which is actually the series of tasks that are performed to deploy the components from the development environment to the Production environment and activate them. 2. Cut Over Date Date from which financials are closed in legacy system and as on values will be transferred to new system Final Cut over Date: 30.06.2024

Introduction of Key Terminologies 3. Black Out Period Period in which both legacy and new system is not available and whole business is on spread sheet.

Introduction of Key Terminologies 4. Catch Up Period Period where business try to meet breakeven point of daily data posting in parallel of backlog data. In other words, it is a period in which day to day posting will be started side by side delta data which compile up in black out period.

Introduction of Key Terminologies 5. Cut Over Strategy In cut over strategy detailed plans need to be developed for cutting over from the old system(s) to the new. Detail planning includes the cutoff date on which you will extract the data from legacy and how you upload them and treat them in SAP.

Overview of Strategy How to Formulate Strategy

Cut Over Overview The Cutover is a Business Owned Event ( strongly driven from our side though!) It is sometimes seen to be purely a technical exercise but it is not It is not sequential, many activities can run in parallel, but the most important step is business validation of the files prior to giving them to the SAP team Essentially, from the time you close your ledgers, to the time that the transactional data and stock data is in SAP Production – you have your entire business in a set of spreadsheets. We seek to minimise that time. We also call it Black Out Period. We’ve experienced many cutovers so far - every one is different

Overview of Cutover Strategy Cutover Period Post Cut Over / Support Blackout Period Closing in legacy Prepare Transactional data Sign off on balances Provide transactional Data to SAP team for upload Verify Uploaded Data in PRD Sign off (Production) Balances Go Live Backlog Entries Start Post Go-Live Support Catch up Period Real time transactions Pre-Cutover Activities Key decisions for Cut Over approach Minimize Business Transactions, Close maximum items, clean transactional data Provide Final Master Data Prepare for actual Cut over Transition Operations

Master / Transactional Data Cycle

Final Cutover on Data as of 30 th June 2024

Key Decisions & Recommendations 1. Data Selection and Analysis: Define data scope: Determine the specific data sets (material, vendor, customer, etc.) required for migration based on business needs and historical transaction activity. 2. Data Extraction: Extract data from legacy system: Utilize appropriate tools and methodologies to extract the selected data sets from the non-SAP system. Ensure data integrity and consistency during the extraction process. 3. Data Transformation and Cleansing: Improve data quality: Implement data cleansing techniques to address issues like: Incomplete customer/vendor addresses Open purchase orders/invoices with no further processing (short closed) Inconsistent data formats Duplicate records (identify and potentially merge) 4. Data Loading and Design: Define data upload approach: Determine the most efficient method for transferring cleansed data into the SAP system. Options include: Pre-processing the extracted data into a format compatible with SAP templates. Develop data validation procedures: Establish quality checks to verify the accuracy and completeness of data before migrating it to the SAP system.

Key Decisions & Recommendations Master Data: We'll begin by gathering all master data from NTDC and SPAK will upload data into the production system, for ensuring accuracy and completeness NTDC will do the verification. Budget: Next, SPAK will focus on uploading budget for year 2025. New fiscal year b udget is already finalized before 30 th June, NTDC will provide budget data in SAP template . Following the upload, NTDC will verify the data for any inconsistencies. Cutover : This is the date on which NTDC will switch from the legacy system to the SAP and NTDC will start doing their transactions (mentioned in slide 18) in new system from 01 July 2024. Transaction Data: We'll then migrate all the transactional data, such as accounts payable, accounts receivable, bank, asset, and general ledger line items from Trial Balance . Similar to the master data, the transaction data will be verified by NTDC. Go Live: The official launch of the new SAP system! Users will be able to access and utilize the new system for all their business needs. *NTDC will start posting entries from 01 July 2024 in SAP. Closing balances will be available later when it is provided to SPAK.

Key Decisions & Recommendations Master Data: We'll begin by gathering all master data from NTDC and SPAK will upload data into the production system, for ensuring accuracy and completeness NTDC will do the verification. Budget: Next, SPAK will focus on uploading budget for year 2025. New fiscal year b udget is already finalized before 30 th June, NTDC will provide budget data in SAP template . Following the upload, NTDC will verify the data for any inconsistencies. Cutover : This is the date on which NTDC will switch from the legacy system to the SAP and NTDC will start doing their transactions (mentioned in slide 18) in new system from 01 July 2024. Transaction Data: We'll then migrate all the transactional data, such as accounts payable, accounts receivable, bank, asset, and general ledger line items from Trial Balance . Similar to the master data, the transaction data will be verified by NTDC. Go Live: The official launch of the new SAP system! Users will be able to access and utilize the new system for all their business needs. *NTDC will start posting entries from 01 July 2024 in SAP. Closing balances will be available later when it is provided to SPAK.

Key Decisions & Recommendations System Entries will be started by NTDC users on 01 July 2024, before the migration of Opening Balances. Till Opening balances are upload in the system NTDC needs to keep in mind the following: Users can post all new transactions which are not referenced to the old open items and incurred after 01 July 2024 like, vendor and customer invoices, advance payments, Journal Voucher postings, Bank related transactions, payments for invoices after July 1st, new Purchase Orders. User cannot post payments for old invoices (posted before July 1 st ) until data is uploaded. User cannot clear/knock-off old open items (posted before July 1 st ) until data is uploaded. User cannot post GR or Invoices for old Pos (posted before July 1 st ) until data is uploaded. *Transactional Data till 30 June 2024 will be uploaded by 8 th July 2024 then users will start posting entries which are referenced with opening balances.

Business Plan for Cut Over Challenges

Module Specific Cutover

Financial Accounting/TRM Master Data: For Final Cutover as of 30th June 2024 provide Data by 6 th June 2024 Delta Master Data (15 th June – 27th June) provide Data by 28 th June 2024 GL Master Data Bank Master Data Customer Master Data LC, Bank, Loan Counter Parties House Bank for Loan and LC Transactional Data For Final Cutover as of 31 st March 2024 provide Data by 3 rd April 2024 GL Balances (P&L and B/S) Vendor Balances Customer Balances Asset Balances (only on GL) – refer slide 21 & 22 Bank Balances LC and Loan Data Charges Data (if any) Cutover Team: Siemens Adeel Arshad NTDC Atif Riaz

Controlling (CO) Master Data: For Final Cutover as of 30th June 2024 provide Data by 6 th June 2024 Profit Center Hierarchy Cost Center Hierarchy Profit Centers Cost Centers Cutover Team: Siemens Salman Afzal NTDC Atif Riaz

Funds Management (FM) Master Data: For Final Cutover as of 30th June 2024 provide Data by 6 th June 2024 Delta Master Data (15 th June – 27th June) provide Data by 28 th June 2024 Fund Fund Center Commitment Item Transactional Data For Final Cutover as of 30 th June 2024 provide data by 25 June 2024 Budget Cutover Team: Siemens Adeel Arshad NTDC Atif Riaz

Asset Accounting (FI) – Standard Situation Cutover Team: Siemens Adeel Arshad NTDC Atif Riaz Master Data: For Final Cutover as of 30th June 2024 provide data by 25 June 2024 Asset Master Data* Transactional Data For Final Cutover as of 30 th June 2024 provide data by 25 June 2024 Asset Transaction Data* *SAP template provided to upload Asset Data will include Master Data and Transactional Data at the same time, both data will be uploaded together.

Asset Accounting (FI) – Current Situation Asset Data will be uploaded through GLs in the system: Users will be posting new Asset acquisition/retirement manually of asset GL Accounts. User will be posting Depreciation manually on assets through depreciation GL Accounts. *Assets Master & Transactional data will be provided by NTDC on 30 September 2024 then SPAK will move the asset GL balances to Asset Accounting module. Cutover Team: Siemens Adeel Arshad NTDC Atif Riaz

Project System Master Data: For Final Cutover as of 30th June 2024 provide Data by 23 th June 2024 Delta Master Data (23 th June – 29 th June) provide Data by 30 th June 2024 Projects WBS Elements Network Activities Transactional Data For Final Cutover as of 30 th June 2024 provide data by 23 th June 2024 Plan Budget Remaining Budget Cutover Team: Siemens Haris Ullah Khan NTDC Sufyan Qureshi.

Supply Chain Management Master Data: For Final Cutover as of 30th June 2024 provide Data by 20 th June 2024 Delta Master Data (21 th Jun – 30 st Jun) provide Data by 1 st July 2024 Material Master Service Master Vendor Master (Business Partners) Master Inspection Characteristic Inspection Plant Transactional Data For Final Cutover as of 30 th June 2024 provide data by 3 rd July 2024 Material Qty along with value Balances (Final Cutover) Open Purchase Orders (For Final Cutover) Open scrap/cash sales order (If any) Note: SPAK also required the date when filled templates for release strategy, as we required almost three months for configurations in system once received from NTDC. Cutover Team: Siemens Ammad Hussain NTDC Atif Hussain

Human Capital Management (HCM) Complete HCM Master data HCM system hand over to NTDC for verification Employee Master Data Changes for july 2024 Parallel Payroll Execution and Verification for July 2024 Payroll Reconciliation Balances Upload PRD Provident Fund Balances Loan Balances Tax Balances Leaves Balances Master / Transactional Data: Employee Hiring/Appointment Organizational reassignment Change in Pay/Promotion Contract Renewal/Contract Exte Contract Regularization Deputation In/Deputation Out Leaving/Resignation/ Retiremen Transfer / Posting Time Management Loans Salary Changes Recurring Payments & Deductions Additional Payments (Non-recurring) Changes Verification Payroll Simulation july 2024 Error Rectification Actual Payroll Execution july 2024 Payroll Reconciliation Cutover Team: Siemens Rashid Munir Muhammad Sarmad Muhammad Haroon Gillani Zubair Khalid NTDC Miss Sofia Mr Zaka Ullah