Materials: The Material Master Records will be extracted that meet the relevancy criteria of Material Basic Data.  Material Type will further refine this list to Materials relevant for the Purchasing View.

Materials:
PF2: 115,853**
WP2: 81,288**
** As per Material relevancy criteria

Plants (See CNV-2010):
2.4 Million, depending on Plant consolidation

Materials:
197,141 **
** This will change based on the Material Deduplication Process

Plants (See CNV-2010):
TBC, depending on Plant consolidation

Services: There is no Purchase View data, therefore a DCT will be required for the records that meet the relevancy criteria to be created as Materials and Material Type will further refine this list to records relevant for the Purchasing View.

Services:
PF2: 9,821**
WP2: 353**
** As per Material relevancy criteria

10,174 **
** This will change based on the Material Deduplication Process

2010

If MARC-EKGRP is Blank then include in the report.

if ( MARC-HERKL is Blank ) AND
( T001W-LAND1 = 'BR' ) AND
( ( To-Be Material Type IN ('ZDIR','ZIND') ) OR
( ( To-Be Material Type IN ('UNBW','NLAG') ) AND ( To-Be MARC-KZKRI = 'X' ) ) )
then include in the report **

If MARC-WEBAZ is Blank AND (To-Be Material Type = 'ZDIR' OR 'ZIND') then include in the report

Field Governance Rules

These governance rules apply to the individual fields within the data record.

Rule #

Field Label

Rule Description

Validation Method

Conditional Logic

Cleansing Rule (see above)

1

MARA-MATNR &

MARC-WERKS

Only records where the material or service has been loaded into the Target, i.e. it is relevant.

Upfront Automated

Fields in the Material & Plant XREFs

2

MARA-MTART

if To-Be Material Type = 'ZBAS' then DO NOT extend Material to Purchasing View
else extend Material to Purchasing View

Field in the Material Type XREF

3

MARC-HERKL

This field is only applicable for Plants in Brazil with Material types associated with ZDIR or Spares (ZIND) or
Capital Spares (UNBW, NLAG) and Critical Part = Active. **

Upfront Automated

( T001W-LAND1 = 'BR' ) AND
( ( To-Be Material Type IN ('ZDIR','ZIND') ) OR
( ( To-Be Material Type IN ('UNBW','NLAG') ) AND ( MARC-KZKRI = 'X' ) ) ) **

1

Extract data from source system based on relevancy rule

Syniti

Not Applicable

MARC-MATNR

Material Number

Required

MARC-WERKS

Plant

Exists in Plant XREF as a To-Be Plant and use dropdown.

Organizational unit where material is maintained/used (e.g., manufacturing site, storage location).

MARA-BSTME

Order Unit

Value in Check Table T006

The unit in which the material is ordered from vendors (may differ from Base UoM).

MARC-EKGRP

Purchasing Group

Value in Check Table T024

Buyer or group of buyers responsible for procurement activities of the material.

MARC-MMSTA***

Material Status (Plant-Specific)

Value in Check Table T141.  Default to Blank.

Controls whether a material can be procured, produced, or sold in a plant.

MARC-MMSTD***

Valid From

If MARC-MMSTA contains a value then MARC-MMSTD must have a value else Blank

Date from which the material status or conditions are effective.

MLAN-TAXIM

Tax Indicator for Material

Value in Check Table TMKM1

Defines if material is taxable, non-taxable, or exempt for purchasing.

MARC-MFRGR

Material Freight Group

Value in Check Table TMFG

Groups materials for freight calculation and logistics handling.

MARC-KAUTB***

Automatic PO allowed

X or Blank.  Default X.

Allows automatic generation of POs from requisitions without manual intervention.

MARC-KZKRI****

Critical Part

X or Blank  Default Blank.

Used if we consider this Material a critical part from a planning perspective and/or we want it to be part of every inventory Count while running Cycle Counting. This indicator will be sent to Maestro/kinaxis as part of the Material Master Interface.

MARA-MFRPN

Manufacturer Part Number

General part number assigned by the manufacturer.

MARA-MFRNR

Manufacturer

Vendor or producer of the material.

MARC-HERKL

Manufacturer Country

Value in Check Table T005

Country where the manufacturer is located.

MARC-WEBAZ**

GR Processing Time

Value >= 0

Time (in days) between goods receipt and availability for use.
Only capture a value here if the Material is for a Service (Material Type ZSER).  For other materials this field is captured in the MRP Views.

1

Materials and Plants in scope to be loaded must be identified so that we can limit the extraction to this sub-set of data.

Syniti

1

Verify that Material data is extracted from both source systems.

Syniti / S2P Data Team

2

Verify that Services data is extracted from the DCT.

Syniti / S2P Data Team

3

Verify that the Material Number XREF has been updated for both material and service data.

Syniti

4

Review the MDS for 2019 to check what Material Types must not be extended to the Purchasing View and update the rule if required

S2P Data Team

5

Transformation jobs are ready for execution.

Syniti

Generate Load Files.

Syniti

1

PF2,WP2,DCT

MARC

MATNR

Material Number

S/4HANA

MARC

MATNR

Material Number

Map Source to Target using Material XREF

2

PF2,WP2,DCT

MARC

WERKS

Plant

S/4HANA

MARC

WERKS

Plant

Map Source to Target using Plant XREF

PF2,WP2,DCT

MARA

BSTME

Order Unit

S/4HANA

MARA

BSTME

Order Unit

Copy As-Is

PF2,WP2,DCT

MARA

VABME

Variable Order Unit

S/4HANA

MARA

VABME

Variable Order Unit

Default to Blank

PF2,WP2,DCT

S/4HANA

Map Source to Target using Purchasing Group XREF

PF2,WP2,DCT

S/4HANA

Default to Blank

PF2,WP2,DCT

S/4HANA

Default to Blank

PF2,WP2,DCT

S/4HANA

Copy As-Is
For ECC, use the following to go from MARC to MLAN:
MARC-WERKS = T001W-WERKS, MARC-MATNR = MLAN-MATNR AND T001W-LAND1 = MLAN-ALAND

PF2,WP2,DCT

S/4HANA

Copy As-Is

PF2,WP2,DCT

S/4HANA

Default to X.
This field may be updated as a follow-on activity during cut-over after the load.

PF2,WP2,DCT

S/4HANA

Default to: if MARA-MTART IN ('UNBW','NLAG') and PIR > EUR 15k then X else Blank

PIR > EUR 15K will have been calculated when determining MARA-MTART = UNBW or NLAG, therefore store the result of this calc in a table so it can be referenced here.

PF2,WP2,DCT

S/4HANA

Copy As-Is

PF2,WP2,DCT

S/4HANA

Copy As-Is

PF2,WP2,DCT

S/4HANA

Copy As-Is

DCT only

WEBAZ**

GR Processing Time

S/4HANA

Copy As-Is
WHERE Source = DCT and S4H.MARA-MTART = 'ZSER'
ELSE ignore

Material

XREF

Conversion Specification - Mappings

1

Data has been extracted from sources systems

Syniti

2

Deduplication is completed

Syniti & S2P Data Team

3

Configuration should be completed - (Config documents should be complete)

S2P Functional Team

4

Ensure DCT completeness

S2P Data Team

Value mapping and XREF tables are ready

Syniti & S2P Data Team

Verify Record Count

The number of records presented after relevancy checks and validation, as well as the number of records in the DCT, needs to be correct compared to the staged data in Syniti ADMM.

Completeness check

All fields required as per mapping template rules must be completed. Syniti ADMM standard validity reports checking each field in Syniti must be built.

Conversion Accuracy

Verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM standard reports..

Review Error Reports

Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Completeness Check

Business should compare legacy record counts, taking into account the reduction from the relevancy and deduplication processes, against the record count in the preload table.

Conversion Accuracy

Business team to verify that the data staged in the preload tables are correct in terms of the mapping rules. This will be done via Syniti ADMM reports/SAP reports.

1

Verify data extracted

Data Specialist/Functional - S2P

2

Verify data combined from both source systems and DCT

Data Specialist/Functional - S2P

3

Verify Material, Plant and Purchasing Group XREFs are ready

Data Specialist/Functional - S2P

4

Stage data for transformations

Syniti

5

Run transforms

Syniti

6

Execute pre-load report

Syniti

7

Validate preload report - release

Data Specialist/Functional - S2P

8

Prepare and simulate

Syniti

9

Pre-load verification and approval to load

Functional/Data Owner - S2P

10

Load to S4

Syniti

11

Complete Jira steps, Volumes and Timings

All - where applicable

12

Execute post-load report

Syniti

13

Post-load report verification/validation

Data Specialist/Functional/Data Owner - S2P

14

Object load completion approval

Data Owner - S2P

Data

Duplicates

Fix incorrect data

Load

Authorization errors

Apply for the applicable authorization permission and retry

Load

Technical load failures - If using MC - Simulation errors, etc

Investigate error and rectify. Retry simulation and/or load

Config

Configuration is missing in the Target System

Missing config added in the Target System

Verify Count

The number of records presented in the post-load needs to be compared to the preload – Syniti report

Field by field check

Compare source data staged in the preload tables to target data in the load tables.

Verify Logs

Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

Verify Count

The number of records presented in the preload needs to be compared to the post-load Syniti report.

Missing data

Check missing data which was supposed to be loaded.

Reconciliation

Participate in Post-load walkthroughs.

Field by field check

Perform random Field by Field checks by comparing source data staged in the preload tables to target data in the load tables.

Conversion Accuracy

Verify that the data in S/4 HANA was loaded correctly via Syniti post-load reports.