Status
Owner	TEE-ext, Paul
Stakeholders	ERGUIZA-ext, Pinky Love PUN-ext, Eddy JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, Dean @STEFANESCU-ext, Aurelia MOUSSA-ext, Eva

Purpose

The purpose of this document is to define the conversion approach to create Notification in S/4 HANA.

A Notification is a structured record in SAP PM used to report, track, and manage maintenance issues or requests.
It acts as the starting point for most maintenance processes, ensuring that problems, inspections, or service requests are documented and communicated.

Legacy Plant Maintenance Notification is using a diverse range of formats across the different systems. As per SyWay design, EAM Notification will be standardized.

Conversion Scope

The scope of this document covers the approach for converting active Notification from Legacy Source Systems into S/4HANA.

In standard SAP functionality whenever an asset or its component is identified as having suffered a fault or malfunction, a maintenance notification is created to report the event and to request maintenance.  The appropriate technical object (i.e. functional location or equipment) that represents the asset is referenced on that notification along with the suspected symptom and other information (e.g. priority, short / long description, date, reported by, breakdown indicator, etc.)

In general terms, a notification can be utilised in the following situations:

• Corrective Maintenance work identification - non-breakdown maintenance requests, in-service breakdowns, extra malfunctions uncovered during routine maintenance
• Activity reports during routine maintenance and inspections
• Work order execution and completion - recording of technical data such as failure/cause codes)
• Condition-based / predictive maintenance - creation of notifications when asset reaches an exceptional technical condition (e.g. measurements exceed or fall below a certain tolerance)

Besides capturing maintenance requests and providing a means to track outstanding faults/defects and their current rectification, notifications are also used to capture malfunction and failure data which is crucial for long-term asset reliability analysis.

The data from legacy system includes:
1. All Open Notifications (Source System Status: Outstanding, In Process (TJ02T-TXT04 = OSNO or NOPR)
2. Assigned to active legacy Functional Location (IFLOT-TPLNR) (Source System Status Not any of these: Inactive, Delete (TJ02T-TXT04 = INAC or DLFL))
3. Assigned to active legacy Equipment (EQUI-EQUNR) (Source System Status Not any of these: Inactive, In the warehouse, Available (TJ02T-TXT04 = INAC, ESTO or AVLB)) 
4. Notifications having Maintenance Plant (QMEL-ARBPLWERK) in scope - Refer to Value Mapping: Plant (Maintenance Plant = Yes)

The data from legacy system excludes:
1. Notification with Source System Status Notification completed status (TJ02T-TXT04 = NOCO)
2. Open Notifications with closed Work Orders (AUFK-AUFNR) (Source System Status: Closed (TJ02T-TXT04 = CLSD))

APM - Historical Data
Closed Notifications associated to relevant Functional Locations and Equipment for the past 3 years, limited to specific Technical Object Type (listed in OTH_Technical Object Type_APM) and specific list of Maintenance Plants only

Reference: SyWay_Cleansing and Historical Scope - A2D

List of Tables to extract for this object is maintained here: Extract Table Register.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2, WP2	Relevant Measurement Documents will be extracted from PF2 and WP2	110,000	S/4HANA	110,000

Additional Information

Multi-language Requirement

Notification does not have multi language support. Notification text will be migrated using EN logon. 

Document Management

Long text and DIR are not covered in this document as they are defined as another data object.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The technical design of the target for this conversion approach.

1.Notification Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QMEL	QMNUM	QMNUM	Notification Number	CHAR	12	Mandatory
QMEL	AUFNR	AUFNR	Order Number	CHAR	12	Conditional
QMEL	QMART	QMART	Notification Type	CHAR	2	Mandatory
QMEL	QMTXT	QMTXT	Short Text	CHAR	40	Mandatory
QMIH	EQUNR	EQUNR	Equipment number	CHAR	18	Conditional
ILOA	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory
QMIH	INGRP	INGRP	Planner Group	CHAR	3	Conditional
QMIH	IWERK	IWERK	Maintenance Planning Plant	CHAR	4	Mandatory
QMEL	ARBPL	LGWID	Object ID of the Work Center	NUMC	8	Conditional
QMEL	QMDAT	QMDAT	Date of Notification	DATS	8	Mandatory
QMEL	MZEIT	MZEIT	Time of Notification	TIMS	6	Mandatory
QMEL	ERNAM	ERNAM	Reported By	CHAR	12	Mandatory
QMEL	STRMN	STRMN	Required Start Date	DATS	8	Conditional
QMEL	LTRMN	LTRMN	Required End Date	DATS	8	Conditional
QMEL	PRIOK	PRIOK	Priority	CHAR	1	Mandatory
QMEL	QMGRP	QMGRP	Code Group - Coding	CHAR	8	Mandatory
QMEL	QMCOD	QMCOD	Coding	CHAR	4	Mandatory
QMEL	RBNR	RBNR	Catalog Profile	CHAR	9	Conditional
QMIH	ILART	ILA	Maintenance activity type	CHAR	3	Mandatory
QMIH	REVNR	REVNI	Revision	CHAR	8	Conditional
QMIH	MSAUS	MSAUS	Breakdown Indicator	CHAR	1	Conditional
QMIH	AUSVN	AUSVN	Malfunct. Start Date	DATS	8	Conditional
QMIH	AUZTV	AUZTV	Malfunct. Start Time	TIMS	6	Conditional
QMIH	AUSBS	AUSBS	Malfunct. End Date	DATS	8	Conditional
QMIH	AUZTB	AUZTB	Malfunct. End Time	TIMS	6	Conditional
QMIH	AUSZT	AUSZT	Breakdown Duration	FLTP	16	Conditional
QMIH	MAUEH	MAUEH	Breakdown Unit	UNIT	3	Conditional
QMEL	OBJNR	QMOBJNR	Object Number for Status Management	CHAR	22	System
QMEL	ARBPLWERK	QARBPWERKS	Plant for Work Center	CHAR	4	Mandatory

2.Notification Item

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
QMFE	QMNUM	QMNUM	Notification Number	CHAR	12	Mandatory
QMFE	FENUM	FELFD	Item Number in Item Record	NUMC	4	Mandatory
QMFE	FETXT	FETXT	Notification Item Short Text	CHAR	40	Mandatory
QMFE	FEGRP	FEGRP	Code Group - Problem	CHAR	8	Conditional
QMFE	FECOD	FECOD	Problem or Damage Code	CHAR	4	Conditional
QMFE	OTGRP	OTGRP	Code Group - Object Parts	CHAR	8	Conditional
QMFE	OTEIL	OTEIL	Part of Object	CHAR	4	Conditional
QMUR	URTXT	URSTX	Cause Text	CHAR	40	Conditional
QMUR	URGRP	URGRP	Code Group - Causes	CHAR	8	Conditional
QMUR	URCOD	URCOD	Cause Code	CHAR	4	Conditional

Note: Each Notification Header can have many Notification Items

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.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
9004-001	C1	Notification with assigned Functional Location which is not Relevant (as per Relevancy Criteria)	Notification as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below: Functional Location as per Relevancy Criteria	Notification Number, Short Text, Functional Location	PF2, WP2
9004-002	C1	Notification with assigned Equipment which is not Relevant (as per Relevancy Criteria)	Notification as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below: Equipment as per Relevancy Criteria	Notification Number, Short Text, Equipment	PF2, WP2
9004-003	C1	Business Partner: Invalid  or Inactive Business Partner (Customer) linked to Notification	Notification as per Relevancy Criteria assigned with a Business Partner (Customer) does not belong below: 1. Business Partner FLCU01 (SD) as per Relevancy Criteria	Notification Number, Short Text, Business Partner (Customer)	PF2, WP2
9004-004	C1	Catalog Code Groups: Invalid  or Inactive Catalog Code Groups & Code linked to Notification	Notification as per Relevancy Criteria assigned with a Catalog Code Groups & Code does not belong below: 1. Catalog Code Groups & Code as per Relevancy Criteria	Notification Number, Short Text, Catalog Code Groups & Code	PF2, WP2
9004-005	C1	Maintenance Item: Invalid  or Inactive Maintenance Item linked to Notification	Notification as per Relevancy Criteria assigned with a Maintenance Plan and Item does not belong below: 1. Maintenance Plan and Item as per Relevancy Criteria	Notification Number, Short Text, Maintenance Item	PF2, WP2
9004-006	C1	Revision: Invalid  or Inactive Revision linked to Notification	Notification as per Relevancy Criteria assigned with a Revision does not belong below: 1. Revision as per Relevancy Criteria	Notification Number, Short Text, Revision	PF2, WP2
9004-007	C1	Work Centre: Invalid  or Inactive Work Centre linked to Notification	Notification as per Relevancy Criteria assigned with a Work Centre does not belong below: 1. Work Centre as per Relevancy Criteria	Notification Number, Short Text, Work Centre	PF2, WP2
9004-008	C2	Notification Creation Date: Open  Notifications older than 3 months with No Work Order Assigned	Open Notifications older than 3 months with No Work Order Assigned* Status ORAS = Work Order Assigned	Notification Number, Short Text, Notification Creation Date	PF2, WP2
9004-009	C1	Company Code: Notification Company Code incorrect	Notification as per Relevancy Criteria with Invalid Company Code (T001)	Notification Number, Short Text, Company Code	PF2, WP2
9004-010	C1	Plant: Notification Plant incorrect.	Notification as per Relevancy Criteria with Invalid Plant (T001W)	Notification Number, Short Text, Plant	PF2, WP2
9004-011	C1	Planner Group: Invalid  or no Planner Group linked to Notification	Notification as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I)	Notification Number, Short Text, Planner Group	PF2, WP2
9004-012	C2	Description: Notification contains Thai characters	Notification Description with Thai characters	Notification Number, Short Text, Description	PF2, WP2

Informal Words **

Group 1	Group 2	Group 3	Group 4	Group 5
*DNU	Delete	donot	Formerly	Old #
..	Deletion	DONT USE	From	Old[ ]
/	DELISTED	DON'T USE	Incorrect	PLEASE USE
?	Discontinued	Dup Use	Invalid	Pls Use
@	Disposable	DUPLICATE	New	Previously
^	DNU	-DUPLICATE	NOT ACTIVE	Replace
+	Do Not	DUPLICATION	not in use	Replaced
++	Do Not Re	Duplicidad	Not Used	RESERVED
£	Do Not Sell	Duplikat	NOT VALID	Retired
Defective	Do Not Use	Former	Obsolete	ZZDEL

Conversion Process

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

For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.

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

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	SyWay Data Team

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
Not Applicable

Data Collection Template (DCT)

No DCT will be used for Notification.

Notification DCT Rules

Field Name	Field Description	Rule
Not applicable

 Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Ensure that create, change and deletion of master data is freeze in legacy Production system	Legacy IT
2	Relevancy Criteria for Catalog Profile	SyWay A2D Data Team
3	Relevancy Criteria for Catalog Code Groups & Codes	SyWay A2D Data Team
4	Relevancy Criteria for Characteristics	SyWay A2D Data Team
5	Relevancy Criteria for Class	SyWay A2D Data Team
6	Relevancy Criteria for Construction Type	SyWay A2D Data Team
7	Relevancy Criteria for Document Info Record	SyWay A2D Data Team
8	Relevancy Criteria for Equipment	SyWay A2D Data Team
9	Relevancy Criteria for Functional Location	SyWay A2D Data Team
10	Relevancy Criteria for Maintenance Plan and Item	SyWay A2D Data Team
11	Relevancy Criteria for Revision	SyWay A2D Data Team
12	Relevancy Criteria for Task List	SyWay A2D Data Team
13	Relevancy Criteria for Work Centre	SyWay A2D Data Team
14	Relevancy Criteria for Cost Centre	SyWay A2D Data Team
15	Relevancy Criteria for Employee Master	SyWay A2D Data Team
16	Relevancy Criteria for Work Breakdown Structure	SyWay A2D Data Team
17	Relevancy Criteria for Material Master	SyWay A2D Data Team
18	Relevancy Criteria for Business Partner (Customer)	SyWay A2D Data Team

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

Item #	Step Description	Team Responsible
1	Ensure all mapping tables are up to date.	Syniti
2	In dspMigrate, select the wave –R3 S4/HANA – Plant Maintenance	Syniti
3	Go to Process Area Launch and Process the Object – Work Order	Syniti
4	Review and Validate Error and Preload Reports	Syniti
5	Execute the transformation to prepare the target tables	Syniti
6	Validate data from pre-load and invalid reports by region	Business/Data owner
7	Generate export(load) file (If load tool is not dspIntegrate)	SyWay A2D Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2, WP2	QMEL	QMNUM	Notification Number	S/4 HANA	QMEL	QMNUM	Notification Number	Notification will be created based on internal number. The load file will be blank but after loading, this number is retrieved for XREF generation.
2	PF2, WP2	QMEL	AUFNR	Order Number	S/4 HANA	QMEL	AUFNR	Order Number	Based on the design for load program,  Notification creation is separate from the Work Order.  Blank for Standalone Notification
3	PF2, WP2	QMEL	QMART	Notification Type	S/4 HANA	QMEL	QMART	Notification Type	If Notification is assigned to Work Order: Order PM01: Notification Type M1 if Breakdown Indicator is blank, Notification Type M2 if Breakdown Indicator is assigned Order PM02: M3 If Notification is not assigned to Work Order: Notification Type M1 if Breakdown Indicator is blank Notification Type M2 if Breakdown Indicator is assigned Only if notification does not exist for PM01 Work Order, default to: M1
4	PF2, WP2	QMEL	QMTXT	Short Text	S/4 HANA	QMEL	QMTXT	Short Text	Direct Mapping. Only if notification does not exist for PM01 Work Order, default to: Work Order Description
5	PF2, WP2	QMEL	EQUNR	Equipment Number	S/4 HANA	QMEL	EQUNR	Equipment Number	Value Mapping: Equipment Number Use EQUNR to map from old to new Equipment Number If not blank, Transform based on mapping table for Equipment. Error if cannot be mapped. If blank, and if linked to Work Order, then use Work Order value.
6	PF2, WP2	QMEL	TPLNR	Functional Location	S/4 HANA	IFLO	TPLNR	Functional Location Label	Value Mapping: Functional Location Use TPLNR to map from old to new Functional Location If not blank, Transform based on mapping table for Functional Location Error if cannot be mapped. If blank OR INVALID / ERROR / CANNOT BE MAPPED,, and if linked to Work Order, then use Work Order value. Transform to blank if Equipment is not blank     (Rationale – the FL will be defaulted from EQ during loading)
7	PF2, WP2	QMIH	INGRP	Planner Group	S/4 HANA	VIQML	INGRP	Planner Group	Value Mapping: Planner Group Use INGRP to map from old to new Planner Group Transform based on mapping table Planner Group. Error if cannot be mapped. If blank OR INVALID / ERROR / CANNOT BE MAPPED,, and if linked to Work Order, then use Work Order value. For Turnaround Work Order, Planner Group to be assigned to “TA1” in Work Order and Assigned Notification
8	PF2, WP2	QMFE	IWERK	Maintenance Planning Plant	S/4 HANA	VIQML	WERK	Maintenance Planning Plant	Default to Planning Plant from reference technical object.
9	PF2, WP2	QMFE	ARBPL	Object ID for Work Centre	S/4 HANA			Object ID for Work Centre	This field is derived based on the ARBPL Object ID for the Work Centre. Perform the steps: Transform based on mapping table for Work Centre. Only map Main Work Centre. If blank or cannot be mapped, and if linked to Work Order, then use Work Order value. If not linked to Work Order, then derive the Main Work Centre from the first 4 character of the mapped work Centre. If error, then default to technical object Work Centre. Error if cannot be mapped.
10	PF2, WP2	CRHD	ARBPL	Work Centre	S/4 HANA	CRHD	ARBPL	Work Centre	Value Mapping: [Mapping Name] Use ARBPL to map from old to new Work Centre
11	PF2, WP2	CRHD	WERKS	Work Centre plant	S/4 HANA	CRHD	WERKS	Work Centre plant	Value Mapping: [Mapping Name] Use WERKS to map from old to new Work Centre plant based on S/4 HANA mapped value of ARBPL
12	PF2, WP2	QMEL	QMDAT	Notification Date	S/4 HANA	QMEL	QMDAT	Notification Date	Direct Mapping. Only if notification does not exist for PM01 Work Order, default to: Work Order Basic Start Date
13	PF2, WP2	QMEL	MZEIT	Notification Time	S/4 HANA	QMEL	MZEIT	Notification Time	Direct Mapping. Only if notification does not exist for PM01 Work Order, default to:00:00:00
14	PF2, WP2	QMEL	ERNAM	Reported By	S/4 HANA	QMEL	ERNAM	Reported By	Direct Mapping. Only if notification does not exist for PM01 Work Order, default to: Migration User ID (Name)
15	PF2, WP2	QMEL	STRMN	Required Start Date	S/4 HANA	QMEL	STRMN	Required Start Date	If STRMN is blank, and if linked to Work Order, then use Work Order value for both start and end date If End Date is earlier than Start Date, then default both Start and End Date from Work Order. If Start Date is before 2 years prior to go live date, then default both Start and End Date from Work Order.
16	PF2, WP2	QMEL	LTRMN	Required End Date	S/4 HANA	QMEL	LTRMN	Required End Date	If LTRMN is blank, and if linked to Work Order, then use Work Order value for both start and end date If End Date is earlier than Start Date, then default both Start and End Date from Work Order> If End Date is before 2 years prior to go live date, then default both Start and End Date from Work Order. If LTRMN is blank and not linked to Work Order, copy Start Date into End Date. Validation Rule: End Date cannot be earlier than start date
17	PF2, WP2	QMEL	PRIOK	Priority	S/4 HANA	QMEL	PRIOK	Priority	Value Mapping: [Mapping Name] Use PRIOK to map from old to new Priority. Only if notification does not exist for PM01 Work Order, default to: Low
18	PF2, WP2	QMEL	QMGRP	Code Group	S/4 HANA	QMEL	QMGRP	Code Group	For Notification Type -  M1: Default to: PMOTH00 M2: Default to: PMBRD00 M3: Default to: PMOTH00
19	PF2, WP2	QMEL	QMCOD	Coding	S/4 HANA	QMEL	QMCOD	Coding	For Notification Type -  M1: Default to: 0009 M2: Default to: 0099 M3: Default to: 0099
20	PF2, WP2	QMEL	RBNR	Catalog Profile	S/4 HANA	QMEL	RBNR	Catalog Profile	Catalogue Profile to be derived from the Functional Location
21	PF2, WP2	N/A	N/A	Issue Permit				Issue Permit	Transform – if Notification is assigned to Work Order, then “X”.
22	PF2, WP2	QMIH	ILART	Maintenance Activity Type	S/4 HANA	QMIH	ILART	Maintenance Activity Type	Follow Work Order ILART. If Work Order ILART is blank, default to COR.
23	PF2, WP2	QMIH	REVNR	Revision	S/4 HANA	QMIH	REVNR	Revision	Do not transform – just display the legacy revision
24	PF2, WP2	QMIH	MSAUS	Breakdown Indicator	S/4 HANA			Breakdown Indicator	Direct Mapping.
25	PF2, WP2	QMIH	AUSVN	Malfunct. Start Date	S/4 HANA			Malfunct. Start Date	Direct Mapping.
26	PF2, WP2	QMIH	AUZTV	Malfunct. Start Time	S/4 HANA			Malfunct. Start Time	Direct Mapping.
27	PF2, WP2	QMIH	AUSBS	Malfunct. End Date	S/4 HANA			Malfunct. End Date	Direct Mapping.
28	PF2, WP2	QMIH	AUZTB	Malfunct. End Time	S/4 HANA			Malfunct. End Time	Direct Mapping.
29	PF2, WP2	QMIH	AUSZT	Breakdown Duration	S/4 HANA			Breakdown Duration	Direct Mapping.
30	PF2, WP2	QMIH	MAUEH	Breakdown Unit	S/4 HANA			Breakdown Unit	Direct Mapping.

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
Work Order	Old to new Work Order
Planner Group	Old to new Planner Group
Revision	Cross Reference table for Revision
Work Centre	Old to new Work Centre
Equipment	Old to new Equipment
Functional Location	Old to new Functional Location
WBS Element	Old to new WBS Element
Cost Centre	Old to new Cost Centre
Profit Centre	Old to new Profit Centre
Vendor	Old to new Vendor
Material Master	Old to new Material Number
Assembly	Old to new Assembly
Outline Agreement	Cross Reference table for Outline Agreement
GL Account	Old to new GL Account
Purchasing Info Record Number	Old to new Purchasing Info Record Number

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	SyWay A2D Data Team
2	All XREF tables specified in the mapping table section should be available.	SyWay A2D Data Team
3	AUFK - Work Order tables must be loaded	SyWay A2D Data Team
4	MKAL - Production Versions of Material table must be loaded	SyWay A2D Data Team
5	SAFK - CIM Resource - Entities details table must be loaded	SyWay A2D Data Team
6	MARA - General Material Data details table must be loaded	SyWay A2D Data Team
7	KNA1 - General Data in Customer Master details must be loaded	SyWay A2D Data Team
8	ONR00 - General Object Number details must be loaded	SyWay A2D Data Team
9	LFA1 - Vendor Master (General Section) details must be loaded	SyWay A2D Data Team
10	VBAK - Sales Document: Header Data details	SyWay A2D Data Team
11	QPGR - Inspection catalog code groups details	SyWay A2D Data Team
12	QALS - Inspection lot record details	SyWay A2D Data Team
13	EKKO - Purchasing Document Header details	SyWay A2D Data Team
14	EKPO - Purchasing Document Item details	SyWay A2D Data Team
15	VBAP - Sales Document: Item Data details	SyWay A2D Data Team
16	LIKP - SD Document: Delivery Header Data details	SyWay A2D Data Team
17	LIPS - SD document: Delivery: Item data details	SyWay A2D Data Team
18	CRID  - CIM Resource - Entities details	SyWay A2D Data Team

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
Verify Record Count	SyWay A2D Data Team to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets.
Verify Data Integrity	SyWay A2D Data Team to verify that the total number of Operations per Work Oder header extracted from legacy systems and DCTs (if any) should be equal to the total number of operations identified in the Preload and Load Sheets

Accuracy

Task	Action
Conversion Accuracy	SyWay A2D Data Team to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks Text Length Checks
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.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records from legacy systems and DCTs (if any) is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks Text Length Checks

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

Item #	Step Description	Team Responsible
1	Syniti will provide load file	Syniti

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

Item #	Configuration Item
1	Notification Type

Conversion Objects

Object #	Preceding Object Conversion Approach
1030	Work Centre
1002	Equipment
1003	Functional Location
1026	WBS - CAPEX, OPEX, Statistical
1074	Cost Centre
1073	Profit Centre
3018	Vendor
2019	Material
1010	Assembly
1094	Purchase Info Records (Including Pricing Conditions)
1067	GL Account Operational CoA (incl. secondary CE)

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

Error Type	Error Description	Action Taken
Invalid Data	Invalid data (Based on master data)	Check whether the master data is available in the system
Invalid Data	Invalid data (Based on non master data)	Review and analyses the errors. Take necessary action to correct the data if possible.
Configuration	Invalid Notification Type	Engage Functional team to expedite and fix the error in the system

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
Verify Count	SyWay A2D Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.
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.).

Accuracy

Task	Action
Conversion Accuracy	SyWay A2D Data Team to verify that the Notification data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
Verify Count	Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.

Accuracy

Task	Action
Conversion Accuracy	Verify that the Notification data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

Key Assumptions

• Notification is in scope based on data design and any exception requested by business.
• Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.

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

Workflow history