WP2

MVKE - SOrgn in scope - X-distr.chain status/ DChain-spec. status (BLANK or xxx/ check)

Check configuration for X-distr.chain status/ DChain-spec. status and see if we can use all or only some status codes as exclusion.

S/4 HANA

PF2

S/4 HANA

2003-001

2003-002

2003-003

Set sales view block for material not eligible for migration

Check the usage of material sales view not in use for 5 years and without stock, but still active

Extraction Scope Definition

- Identify the source systems and databases involved.

- Define the data objects (tables, fields, records) to be extracted.

- Establish business rules for data selection.

Syniti

Extraction Methodology

- Specify the extraction approach (full, incremental, or delta extraction).

- Determine the tools and technologies used.

- Define data filtering criteria to exclude irrelevant records.

Syniti

Extraction Execution Plan

- Establish execution timelines and batch processing schedules.

- Assign responsibilities for extraction monitoring.

- Document dependencies on other migration tasks.

Syniti

Data Quality and Validation

- Define error handling mechanisms for extraction failures.

Syniti

Source System Availability

• Ensure that the source database or application is accessible.
• Confirm that necessary credentials and permissions are granted

Syensqo IT

Data Structure

• Identify relationships between tables, views, and stored procedures.

Syniti

Referential Integrity

• Ensure dependent records are extracted together.

Syniti

Extraction Methodology

• Define whether extraction is full, incremental, or delta-based.
• Establish batch processing schedules for large datasets.

Syniti

Performance and Scalability Considerations

• Optimize extraction queries to prevent system overload.
• Ensure network bandwidth supports data transfer volumes.

Syniti

Security and Compliance

• Adhere to regulatory standards for sensitive information if applicable

Syniti

Data cleansing of legacy Material Master - Sales View with sales long text data must be completed.

If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

Business

1

Transformation Scope Definition

- Identify the source and target data structures.

- Define business rules for data standardization.

- Establish data cleansing requirements to remove inconsistencies.

Data Team

2

Data Mapping and Standardization

- Align source fields with target fields.

- Ensure unit consistency (e.g., currency, measurement units)

Data Team

3

Business Rule Application

- Implement data enrichment/collection if applicable

- Apply conditional transformations based on predefined logic/business rules

Data Team

4

Transformation Execution Plan

- Define batch processing schedules.

- Assign responsibilities for monitoring execution.

- Establish error-handling mechanisms

Syniti

Distribution Channel Mapping

SyWay - Sales Area.pptx --> All the actual distribution channels and divisions won't exist in the to-be solution

Check current Dist.Ch. and discuss with Functional team and how to do the mapping

Unit of Measure Mapping

MVKE_VRKME shares the same mapping table with Basic view (MARA_MEINS).

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Material Status - Sales Mapping

MVSTAV - Cross Distribution Chain

VMSTA - Distribution Chain Specific

Check the configuration in ECC & S/4 HANA if we need this mapping or not? Or if status <> blank then excluded from ECC download?

Plant Mapping

WERKS - Plant

DWERK - Delivering Plant

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Statistics Group - Material Mapping

TBD

Product Hierarchy Mapping

MARA_PRDHA - Basic Data 1

MVKE_PRODH - Sales: Sales Org. 2

Prod. Hierarchies' levels are the same. Share the same mapping table with Basic view (MARA_PRDHA).

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Item Category Group Mapping

MTPOS_MARA - Basic Data 1

MTPOS - Sales: Sales Org. 2

Share the same mapping table with S2P. To check with Jasleen Madhok, John Hancock, Angelo Buosi

Material Group 1 Mapping

Use in QF2

Material Group 2 Mapping

Use in QF2 and WQ2

Material Group 3 Mapping

Use in QF2

Material Group 5 Mapping

Use in WQ2

1

Source Data Integrity

- Ensure extracted data is complete, accurate, and consistent.

- Validate that data types and formats align with transformation requirements.

Syniti

2

Referential Integrity

- Ensure dependent records are transformed together or in advance

Syniti

3

Transformation Logic and Mapping

- Define data mapping rules between source and target schemas.

Data Team

4

Performance and Scalability Considerations

- Optimize transformation processes for large datasets.

- Ensure system resources can handle transformation workloads

Syniti

5

Logging and Error Handling

- Maintain detailed logs of transformation activities.

- Define error-handling procedures for failed transformations

Syniti

Compare Data Counts

1. Verify row counts between source and target databases.
2. Identify missing or duplicated records.

Validate the mandatory fields

Validate there is value for all the mandatory fields

Validate Primary Keys and Unique Constraints

1. Check for duplicate or missing primary key values.
2. Ensure unique constraints are maintained.

Test Referential Integrity

Confirm dependent records exist in related tables

Validate the transformation

Validate the fields which require transformation have the value after transformation instead of the original field value

Check Data Consistency

1. Compare field values across systems
2. Validate data formats and structures

Verify Record Count

Business Data Owner/s to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.

Conversion Accuracy

Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/ mapping rules (and signed-off DCT data).

1

Load Scope Definition

- Identify the target system and database structure.

- Define data objects (tables, fields, records) to be loaded.

- Establish business rules for data validation.

Data team

2

Load Methodology

- Specify the loading tools and technologies (Migration Cockpit, LSMW, custom loading program).

Syniti

3

Data Quality and Validation

- Ensure data integrity checks (null values, duplicates, format validation).

- Perform pre-load validations to verify completeness.

- Define error handling mechanisms for load failures

Syniti

4

Load Execution Plan

- Establish execution timelines and batch processing schedules.

- Assign responsibilities for monitoring execution.

- Document dependencies on other migration tasks

Syniti

5

Logging and Reporting

- Maintain detailed logs of loading activities.

- Generate summary reports on loaded data volume and quality.

- Define escalation procedures for errors

Syniti

1

Sales Organization

2

Distribution Channel

3

Unit of Measure

4

Material Status - Sales

5

Plant

6

Tax Condition Type

7

Tax Classification - Material

8

Statistics Group - Material

9

Product Hierarchy

10

Material Price Group

11

Account Assignment Group - Material

12

Item Category Group

13

Material Group 1

14

Material Group 2

15

Material Group 3

16

Material Group 5

2019

Materials-Basic View(required Material Types-ROH/FERT/HALB/SRV/DIEN/ZDIE/Packaging/Spares

Configuration / Data Transformation

The value XXX for field XXX doesn't exist

1. Check the mapping/ conversion is done properly in the loading file
2. Validate the target value is configured/ transported in the target system
3. Reach out to function team to validate the configuration

Configuration

There is mandatory field XXX missing

1. Validate MDS if the fields are set as mandatory
2. Validate if there is value in the pre-loading file
3. Validate if the configuration for the mandatory fields are done properly

Validate Record count in the backend

Validate the main tables, such as MVKE has the same records as the loading file

Display Records

Pick up few random Material numbers, and Run the Material Report to validate the Material Sales View with Sales Text can be displayed without any error

Perform Source-to-Target Comparisons

1. Validate that migrated data matches source records.
2. Check for discrepancies in numerical values, text fields, and timestamps

Execute Sample Queries and Reports

1. Run queries to validate business logic.
2. Generate reports to compare expected vs. actual results

Conduct Post-Migration Reconciliation

Generate reports comparing pre- and post-migration data.

Perform Manual Testing

Conduct manual spot-checks for additional assurance.