📌 Topic Covered

1. SAP HANA Migration Internship Session
2. Data Migration Process Overview
3. LTMCT to Fiori Migration Strategy
4. System Migration and Cutover Process
5. Legacy to Target System Cutover
6. Data Migration and Cutover Process
7. GL Account Migration Process Overview
8. SAP Data Migration Strategy Discussion
9. Legacy Data Migration Process Discussion
10. Purchase Order Migration Process
11. Data Migration and Audit Process

SAP HANA Migration Internship Session

Tashheer introduced today's SAP Internship session focused on data migration, particularly using the HANA Migration Cockpit, and announced that Tushar would lead the practical demonstration. Tushar shared his experience as a cutover admin in a recent project, explaining his role in managing the transition from ECC to S4 HANA in multiple waves, including responsibilities for aligning activities across teams and monitoring execution. The session was highlighted as the second-to-last for the internship, with participants reminded to complete pending assignments and prepare for the final session in two weeks.

Data Migration Process Overview

Tushar led a session on data migration, explaining the types of data involved in cutover processes and the steps in the data cycle. He discussed configuration data, master data, and transactional data, as well as the tools used for migration, such as transport requests and the HANA migration cockpit. Tushar also addressed a question from Hely about the difference between data conversion and data migration, explaining that data conversion involves changing the format of data, while data migration involves transferring data from one system to another.

LTMCT to Fiori Migration Strategy

The team discussed data migration from LTMCT to Fiori applications, focusing on the cutover phase strategy. Tushar explained the technical go-live process, which includes moving configurations via TRs, setting up interfaces, and defining user access, followed by a communication plan to inform customers about the 3-4 day cutover period during weekends. The team also covered the data cycle steps, starting with extraction, followed by cleansing, transformation, and verification processes, emphasizing that master data must be loaded before transactional data to avoid errors.

System Migration and Cutover Process

Tushar explained the process of soft configuration, where different teams perform their specific configurations, followed by core transaction data loading, extraction, cleansing, transformation, and verification. He detailed the pre-cutover phase, including business ramp-down activities, the cutoff or blackout phase where the legacy system is unavailable, and health checks of the target system. Tushar also described the financial closing process, where the FI team takes a snapshot of balances, and the final financial go-live, where the target system becomes available for users after receiving approval from higher management.

Legacy to Target System Cutover

The team discussed the cutover process for transitioning from a legacy system to a target system. Tushar explained that the business cutoff phase lasts 4 days, during which open transactions and finance-related data are loaded to the target system. After the business go-live, the team performs post-cutover activities in the target system, including reconciling open GR/IR balances and ensuring GL balances match the legacy system. Hely and Tashheer clarified that while the business operates in the target system post-cutover, the financial closing remains in the legacy system until the data is uploaded to the target system.

Data Migration and Cutover Process

Tushar explained that the entire cutover process typically takes around two months, starting from technical go-live, with master data and core transaction data extraction, cleansing, and transformation taking the majority of the time. He detailed the process for handling data loading errors, which involves returning the file to the business for correction before retrying the load. The discussion then shifted to understanding the complexities of migrating open transactional data, using the example of OpenPO migration and its associated FI and MM postings, including the specific GL account impacts during goods receipt and invoice receipt scenarios.

GL Account Migration Process Overview

Tushar explained the GL account postings for GR and IR activities, including how inventory and clearing accounts are debited and credited. He then discussed the process of migrating open POs using the HANA Migration Cockpit, where open GL balances are loaded into the target system. Tushar provided examples to illustrate how PO quantities and values should be handled in the target system to maintain accuracy in vendor liabilities and inventory values.

SAP Data Migration Strategy Discussion

The team discussed data migration from a legacy system to SAP S4 HANA using Business Object Data Services (BODS). Tushar explained how to calculate new PO quantities by subtracting GR quantities, with BODS consultants handling automated calculations for large volumes of data. Tashheer clarified that consultants don't need to provide raw data to BODS, but rather define the logic for mapping open POs, GRs, and invoice receipts, which BODS consultants will implement in their system. Basanagouda raised concerns about manually calculating logic for thousands of records, to which Tushar confirmed that while the basic logic is simple, it would be automated through BODS to handle large data volumes efficiently.

Legacy Data Migration Process Discussion

The team discussed the process of migrating data from a legacy system to a target system, focusing on handling Purchase Orders (POs) and Goods Received Notes (GRNs). Tushar explained that if the business provides a list of open POs, the data can be uploaded directly to the legacy system. However, if the data is extensive, BODS consultants will create a program to automate calculations and determine the remaining quantities for new POs. Tashheer mentioned that not all companies use BODS due to its cost, and alternative tools or manual Excel-based solutions may be employed for data extraction and processing. The team was advised to review the HANA migration cockpit course for more detailed information on tools and processes involved in data migration.

Purchase Order Migration Process

Tashheer and Tushar discussed the handling of open purchase orders and inventory differences during system migration. Tushar explained the process of managing GR/IR quantity discrepancies by creating adjustment accounts and performing direct FI postings to balance vendor liabilities. They emphasized that only open balances should be migrated, avoiding duplicate bookings of historical transactions to maintain accurate financial records and avoid auditor rejection. The session concluded with a clarification that the target system should start fresh with open quantities while using existing GL accounts for open balances.

Data Migration and Audit Process

The team discussed data migration processes, focusing on how audits are handled during system migration and the importance of maintaining reference numbers to track transactions accurately. Tushar explained that historical data should not be migrated to prevent double posting, and instead, only open items and pending transactions should be transferred to the new system. The team was advised to complete pending assignments before the next session, and Tashheer announced that a system demo and further explanations about the HANA Migration Cockpit would be scheduled if needed, with details to be communicated via WhatsApp or Telegram.