Purpose

The purpose of this document is to define the conversion approach to create Material Master-General Plant Data / S.Loc Data in S/4 HANA.

The General Plant Data/Storage view is one of the key views in the Material Master. It contains information about a material that is specific to a particular plant and storage location. This view is essential for plant-level operations and inventory management. Currently, in both ECC systems PF2 and WP2, materials are extended to specific plants and their respective storage locations. Source and Target structures mapping are provided below.

Conversion Scope

The scope of this document covers the approach for converting active Material Master-General Plant Data / S.Loc Data from Legacy Source Systems into S/4HANA following the DD-FUN-050 Master Data Standard - Material General Plant and Storage Data Master Data Design Standard.

As per KDD011 - Material Master Numbering Alignment All Syensqo's materials (finished, semi-finished, raw materials, spares etc.) will be represented by a unique material master number which will be assigned from a new number range

 All materials created in the previous 6 months will be included unless flagged for deletion

1. Material Types ZUNB, ZBOM, ZPRC will be included regardless of activity (unless flagged for deletion)
2. We will only include materials that are extended to the following.
   1. Company Codes in scope
   2. Plants in scope
   3. Purchasing Orgs in scope
   4. Sales Orgs in scope
3. Include only Material Types in scope
4. We will include for migration all materials that have activity over the previous 3 years, to include:
   1. For procurement data use EKKO/EKPO tables (remove any records in EKKO/EKPO where LOEKZ = 'X') and use EKPO/AEDAT for previous 3 years filter
   2. For sales data use VBAK/VBAP tables
   3. For production data use AFKO/AFPO tables 
5. Additionally, we can check material movements by querying MKPF/MSEG tables.  Link MKPF.MBLNR (Document Number) to MSEG.MBLNR and link MKPF.MJAHR (Year) to MSEG.MJAHR. Extract data by year or date (MKPF.BLDAT). WP2 may have to be broken down further due to the number of records. In MKPF.VGART (Transaction Types) add: IB,ID,IZ,RS,SI,WA,WE,WF,WH,WI,WL,WO,WQ,WR,WS,WV,WZ. Extract material and plant (MSEG.MATNR and MSEG.WERKS)
6. We will include for migration all materials that have open documents including the following:
   1. Open PO
   2. Open contracts
   3. Open STO
   4. Open SO
   5. Open WO
7. Have current stock/open inventory

   1. For Open Inventory use the following tables:

      MARD

      MKOL (Consignment stock)

      MSKA (Sales Order stock)

      MSLB (Special stock)

      MSPR (Project stock)

8. We will include all BOM data for materials in scope using tables: MAST/STKO/STPO. We will also include all Plant Maintenance BOMs (regardless of activity).
9. Materials with Deletion Flags will be excluded unless appearing in the following open transactions:
   1. Open PO
   2. Open contracts
   3. Open STO
   4. Open SO
   5. Open WO
10. Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
11. Materials with the word 'OBSOLETE' or 'DELETED' contained within the Short Description will be excluded. Also excluded are Materials where Short Description contains '**OBS', '**OBS**', '**OBS***', '*OBS*', '*OBS**', '***OBS***'

The data from legacy system includes:

1. Materials which are created from Past 3 Years
2. Materials with Maintenance Status (MARA-PSTAT = L)
3. Materials without Deletion Flag (MARC-LVORM = NO)
4. Any Materials that make it through the Material Basic view as Relevant to be loaded will have to be screened against the Material Type's as indicated in the Target Design matrix:  Namely (ZDIR,ZIND,HERS,IBAU,NLAG,PIPE,UNBW,VERP,ZLEI,ZLEH,ZLER,ZABF,ZSER &  ZBA)  → If marked as N/A then it means the field is not maintained for that material type.

The data from legacy system excludes:

1. N/A

Additional Information

Multi-language Requirement

As per KDD055 - Multi-Language Support there are 8 languages in scope: English, French, Italian and Mandarin and Brazilian Portuguese, German, Spanish and Thai.

Legacy text for applicable records at Plant level are in-scope for Migration to support system functionalities (If anything is getting printed on output documents then the Text would be in scope

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

Not applicable

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

Conversion Process

The high-level process is represented by the diagram below:

Data Privacy and Sensitivity

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

<Object> DCT Rules

Extraction Dependencies

List the steps that need to occur before extraction can commence

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate to make the data Target ready:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in Syniti Migrate
2. Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Conversion Objects

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Materials - Basic Data is in scope based on data design and any exception requested by business.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log