Purpose

The purpose of this document is to define the conversion approach to create Materials - Basic Data View in S/4 HANA.

---CHECKLIST - DATA TEAM---

• 1) Legacy systems (Logical Source and Target Systems are identified)
• 2) Extraction methods and file types
• 3) Scope relevancy criteria
• 4) Target structure/ Rules
• 5) MDS links
• 6) Cleansing rules
  • 6a) Cleansing reports with technical information
  • 6b) Profiling
  • 6c) Cleansing reports which you need to be developed by Syniti
  • 6d) Deduplication (with technical details of Table-Fields, Conditions)
  • 6e) Frequency of running reports
• 7) Transformation - and for this DOMD template must be populate and final version of DOMD template should be copied to Transformation section in CSpecs
• 8) Configuration/Value mapping file link
• 9) Value Mappings (Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer)
• 10) Load template link
• 11) Loading method (Processing Type is specified, i.e. Direct Input, BAPI, IDoc, Web Service, OData API, etc.)
• 12) Loading sequence or dependency
• 13Error handling requirements are specified / including alerting requirement / expected action on failure.
• 13) Data Analysis
• 14) Pre load validation
• 15) Post load validation
• 16) any Exceptions (Data Mapping is provided for mappings which are not obvious to a suitably-skilled and experienced developer)
• 17)Application log requirement if applicable to be specified. 
• 18) Signoff

Conversion Scope

The scope of this document covers the approach for converting active Materials - Basic Data View from Legacy Source Systems into S/4HANA following the Materials Master Data Design Standard.

From the current system landscape, Material data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in both organizations. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, extensive mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design.

Relevancy Rules

1. All materials created in the previous 6 months will be included unless flagged for deletion
2. Material Types ZUNB, ZBOM, ZPRC will be included regardless of activity (unless flagged for deletion). Material Types PROD, ZINT will be excluded. Maintenance Assemblies are excluded (MTypes Z750, ZIBA).
3. We will only include materials that are extended to the following according to the Enterprise Structure (excluding ZPRC material type as these do not require plant extension):
   1. Company Codes in scope
   2. Plants in scope
   3. Purchasing Orgs in scope
   4. Sales Orgs in scope
4. We will include for migration all materials that have activity over the previous 48 months for non ZIND/ZABF materials, or 60 months for ZIND/ZABF materials:
   1. For procurement data use EKKO/EKPO tables (remove any records in EKKO/EKPO where EKKO.LOEKZ = C,X EKPO.LOEKZ = L,S and use EKPO/AEDAT for date range
   2. For sales data use VBAK/VBAP tables 
   3. For work order data use AUFK/AFKO/AFPO tables. Check date using AUFK.ERDAT. Enter Order Category AUFK.AUTYP 40 for Process Orders and 30 for Maintenance Orders.
   4. Valid PIRs and Source List (this includes Not Deleted/Validity Date not expired/In scope Purchasing Orgs and Plants based on Enterprise Structure) Check tables EINA/EINE/EORD. Check EORD.NOTKZ is showing as not blocked Check that EORD.BDATU is greater than current date.
5. Additionally, we can check material movements by querying MKPF/MSEG tables for the last 48 months for non ZIND/ZABF materials and 60 months for ZIND/ZABF materials.  Link MKPF.MBLNR (Document Number) to MSEG.MBLNR. Enter dates with MKPF.BLDAT. WP2 may have to be restricted to quarterly data 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.
6. We will include for migration all materials that have open documents including the following:
   1. Open PO and STO. (EKPO-ELIKZ ≠ 'X') (EKKO.BSTYP = F)
   2. Open contracts and scheduling agreements. (EKPO-ELIKZ ≠ 'X') (EKKO.BSTYP = K)
   3. Open SO. VBUK.GBSTK = ('A','B') 
   4. Open WO. Use AUFK for checking open Process orders. Link field AUFK.OBJNR to JEST.OBNR to get status codes not equal to TECO AND JEST.INACT ≠ 'X'.
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 Production BOM data for materials in scope using tables: MAST/STKO/STPO. We will also include all Plant Maintenance BOMs and their related components. MAST data will include BOM Usage (STLAN) 1 (Production) & 4 (Plant Maintenance). STKO data will include BOM Category (STLTY) E (Equipment) & M (Material).
9. Materials with Deletion Flags will be excluded unless appearing in the following open transactions:
   1. Open PO/STO
   2. Open contracts and scheduling agreements
   3. Open SO
   4. 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***'
12. Include ZIND/ZABF materials with Purchase Requisition for the last 60 months. Check table EBAN. Check for validity date EBAN.ERDAT. Check EBAN.BSTYP = B. Check valid Purchase Org/Plant/Company Code according to the Enterprise Structure
13. Include non ZIND/ZABF materials with Purchase Requisition for the last 48 months. Check table EBAN. Check for validity date EBAN.ERDAT. Check EBAN.BSTYP = B. Check valid Purchase Org/Plant according to the Enterprise Structure
14. Include all materials with PIR(Planned Independent Requirements). Check table PBIM/PBED for materials PBIM.MATNR. Check PBIM.LOEVR ≠ 'D'. Check PBIM.WERKS for in scope Plants.

Additional Information

MDS Documents

Data Extraction

Data has been extracted from Production and files are kept here: 

Extraction/Transformation Methods and File Types

Data is Extracted and Transformed by Syniti ADM, the staging area of the Migration Cockpit will be updated by Syniti.

Multi-language Requirement

Languages to be extracted (available on Source Systems)

 SAP standard supports all ISO languages, ensure that all standard languages are considered in scope.

Material Master will have a default description available in English.
Multi language is supported for Materials. Login via a different language will show the description displayed in the logon language if the language key is maintained.

• Core languages: EN - English, FR - French, IT - Italian and ZH - Mandarin.
• Additional languages: PT - Portuguese, DE - German, ES - Spanish
• Supplier languages that are possible: FR - French, EN - English, ES - Spanish, DE - German, IT - Italian, NL - Dutch, PT - Portuguese, ZH - Mandarin, PL - Polish, JA - Japanese, KO - Korean, FI - Finnish, BG - Bulgarian, RU - Russian, TH- Thai, ZF - Chinese traditional, SK - Slovak, Z9 - Brazil Portuguese. 

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Material Master: Source ECC Material → Target S4H Material Master

Material Master: Source ECC Service Master → Target S4H Material Master