WP2

Table: KOTG001

Listing/exclusion type - Customer - Material - Valid to - Valid From

Without sales organization but there are data for inclusion - Z002 (Cust/Restricted used), e.g. WP2 - SO 3480790 where customer 65429 is marked for deletion and listing type Z002 no longer assigned to procedure A00001. CHECK in detail

5,000

S/4 HANA

5,000

WP2

Table: KOTG004

Listing/exclusion type - Sales Organization - Distribution Channel - Customer - Material - Valid to - Valid From

100

S/4 HANA

100

WP2

Table: KOTG906

Listing/exclusion type - Sales Organization - Customer - Material - Valid to - Valid From

120,000

S/4 HANA

120,000

WP2

Table: KOTG908

Listing/exclusion type - Sales Organization - Departure country - Valid to - Valid From

50

S/4 HANA

50

WP2

Table: KOTG909

Listing/exclusion type - Material - Destination Country - Region - Valid to - Valid From

3,000

S/4 HANA

3,000

WP2

Table: KOTG913

Listing/exclusion type - Sales Organization - Material - Customer - Valid to - Valid From

300

S/4 HANA

300

WP2

Table: KOTG962

Listing/exclusion type - Material - Destination Country - Valid to - Valid From

150

S/4 HANA

150

WP2

Table: KOTG964

Listing/exclusion type - Sales Organization - Material - Destination Country - Valid to - Valid From

85,000

S/4 HANA

85,000

PF2

Table: KOTG501

Listing/exclusion type - Destination Country - Material Group - Valid to - Valid From

15,500

S/4 HANA

15,500

PF2

Table: KOTG521

Listing/exclusion type - Destination Country - Region - Material - Valid to - Valid From

50

S/4 HANA

50

PF2

Table: KOTG903

List/excl. - Material - Plant - Ship-To Party - Valid to - Valid From

50

S/4 HANA

50

PF2

Table: KOTG904

List/excl. - Material - Plant - Sold-To Party - Valid to - Valid From

50

S/4 HANA

50

PF2

Table: KOTG906

Sales org. - Destination Country - Valid to - Valid From

100

S/4 HANA

100

Set valid to date to before S/4HANA Go-Live date

For Listing/ Exclusion which the table combination is no longer valid, e.g. customer flagged for deletion, material flagged for deletion, 

Syniti / US Based Consultant for S/4HANA CUI instance

Syniti / LTC Data team

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 / US Based Consultant for S/4HANA CUI instance

Referential Integrity

• Ensure dependent records are extracted together.

Syniti / US Based Consultant for S/4HANA CUI instance

Extraction Methodology

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

Syniti / US Based Consultant for S/4HANA CUI instance

Performance and Scalability Considerations

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

Syniti / US Based Consultant for S/4HANA CUI instance

Security and Compliance

• Adhere to regulatory standards for sensitive information if applicable

Syniti / US Based Consultant for S/4HANA CUI instance

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 / US Based Consultant for S/4HANA CUI instance

MAP_VKORG

Sales Organization Mapping

MAP_VTWEG

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

MAP_MSTAV

Material Status - Sales Mapping

MSTAV - Cross Distribution Chain is used in WQ2 Exclusions (code: 05 and 11)

Check the configuration in ECC for 05 and 11 and the mapping to S/4 HANA. Discuss with the Functional team if the material master for these 2 codes will be migrated to S/4?

MAP_WERKS

Plant Mapping

WERKS - Plant

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

MAP_MATKL

Material Group Mapping

MAP_ALAND

Country Mapping

MAP_MATNR

Material Mapping

MAP_REGIO

Region Mapping

MAP_KUNNR

Customer Mapping

Covers mapping for ALL customers, incl.:

KUNAG Sold-to 

KUNWE Ship-to

MAP_KSCHL

Listing/exclusion type

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

Listing/ Exclusion Table

2

Listing/ Exclusion Access Sequence

3

Listing/ Exclusion Type

4

Listing/ Exclusion Procedure

5

Country Code (Departure and Destination Country)

6

Region

7

Material Group

8

Sales Organization

9

Distribution Channel

10

Plant

11

Cross-Distribution-Chain Material Status (X-distr.chain status)

3003

Business Partners - Customer (Sales and Service) - FLCU01

2003

Materials - Sales view with sales long text

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 all tables with prefix “KOTG” has the same records as the loading file

Display Records

Pick up a few random Material Listing or Material Exclusions, and run t-code: VB03 to validate the Material Listing and Exclusions 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

Conduct Post-Migration Reconciliation

1. Generate reports comparing pre- and post-migration data.

Perform Manual Testing

Conduct manual spot-checks for additional assurance.