| Status | |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Purpose
The purpose of this document is to define the conversion approach to create Notification in S/4 HANA.
Legacy Plant Maintenance Notification is using a diverse range of formats across the different systems. There are instances where the same Notification is duplicated within and across sources, with informal words. This results in data inconsistency. 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:
Cleansing relevancy:
- Open Notifications older than 6 months (based on Creation Date) with no Work Order assigned
APM specific relevancy:
- Open Notifications - Outstanding; In Process (Historical for Selected Equipment Type)
- Historical Data for Completed/Closed Notifications for Active Functional Locations and Equipment with Item Codes for the past 3 years, limited to specific technical object types (list to be confirmed).
The data from legacy system excludes:
- Open Notifications older than 3 months (based on Creation Date) with no Work Order assigned
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | An initial extract will be provided to business to evaluate. Additional data/records may be required and these will be constructed via DCT. Enrichment of in-scope data may be required and will be added via transformation rules (business/technical). | 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
EAM Notification Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Class information follows the Master Data Standard document that is located here <include hyperlink>.
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| QMEL | QMNUM | Notification Number | CHAR | 12 | System generated | |
| QMEL | QMART | Notification Type | CHAR | 2 | ||
| QMFE | ILART | Maintenance Activity Type | CHAR | 3 | ||
| QMEL | SHN_EQUIPMENT | Equipment Number | CHAR | 18 | ||
| QMEL | SHN_FUNCT_LOC | Functional Location | CHAR | 30 | ||
| QMIH | BAUTL | Assembly | CHAR | 40 | ||
| QMEL | SERIALNR | Serial Number | CHAR | 18 | ||
| QMEL | MATNR | Material Number | CHAR | 40 | ||
| QMEL | QMTXT | Short Text | CHAR | 40 | ||
| STXH | LONG_TEXT | Long Text for Header | Text | unrestricted | ||
| QMEL | PRIOK | Priority | CHAR | 1 | ||
| QMEL | STRMN | Required Start Date | Date | |||
| QMEL | STRUR | Required Start Time | Time | |||
| QMEL | LTRMN | Required End Date | Date | |||
| QMEL | LTRUR | Required End Time | Time | |||
| QMEL | LACD_DATE | Final Due Date | Date | |||
| QMEL | QMGRP | Code Group - Coding | CHAR | 8 | ||
| QMEL | QMCOD | Coding | CHAR | 4 | ||
| QMIH | AUSWK | Effect on Operation | Text | 1 | ||
| QMEL | DETECTIONCODEGROUP | Detection Method Group | CHAR | 8 | ||
| QMEL | DETECTIONCODE | Detection Method | CHAR | 4 | ||
| QMEL | ARBPLWERK | Plant Associated with Main Work Center | CHAR | 4 | ||
| QMEL | ARBPL | Work Center for Maintenance | 8 | |||
| QMIH | IWERK | Maintenance Planning Plant | CHAR | 4 | ||
| QMIH | INGRP | Planner Group | CHAR | 3 | ||
| QMIH | MSAUS | Breakdown Indicator | CHAR | 1 | ||
| QMIH | AUSVN | Start of Malfunction (Date) | Date | |||
QMIH | AUZTV | Start of Malfunction (Time) | Time | |||
| QMEL | QMNAM | Name of Person Reporting Notification | CHAR | 12 | ||
QMIH | AUSBS | End of Malfunction (Date) | Date | |||
QMIH | AUZTB | End of Malfunction (Time) | Time | |||
| QMFE | WERKS | Maintenance Plant | CHAR | 4 | ||
| QMIH | LOC_DESC | Asset Location | CHAR | 50 |
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 | Invalid or Inactive Equipment or Functional Location linked to Notification | Notification as per Relevancy Criteria assigned with an Equipment / Functional which does not belong below: | Equipment, Functional Location | PF2, WP1 |
9004-002 | C1 | Invalid or Inactive Business Partner (Customer) linked to Notification | Notification as per Relevancy Criteria assigned with a Business Partner (Customer) does not belong below: | Business Partner (Customer) | PF2, WP1 |
9004-003 | C1 | 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: | Catalog Code Groups & Code | PF2, WP1 |
9004-004 | C1 | Invalid or Inactive Characteristics linked to Notification | Notification as per Relevancy Criteria assigned with a Characteristic does not belong below: | Characteristic | PF2, WP1 |
9004-005 | C1 | Invalid or Inactive Class linked to Notification | Notification as per Relevancy Criteria assigned with a Class does not belong below: | Class | PF2, WP1 |
9004-006 | C1 | Invalid or Inactive Document Info Record linked to Notification | Notification as per Relevancy Criteria assigned with a Document Info Record does not belong below: | Document Info Record | PF2, WP1 |
9004-007 | C1 | Invalid or Inactive Maintenance Item linked to Notification | Notification as per Relevancy Criteria assigned with a Maintenance Plan and Item does not belong below: | Maintenance Item | PF2, WP1 |
9004-008 | C1 | Invalid or Inactive Revision linked to Notification | Notification as per Relevancy Criteria assigned with a Revision does not belong below: | Revision | PF2, WP1 |
9004-009 | C1 | Invalid or Inactive Work Centre linked to Notification | Notification as per Relevancy Criteria assigned with a Work Centre does not belong below: | Work Centre | PF2, WP1 |
9004-010 | C2 | Open Notifications older than 6 months with No Work Order Assigned | Open Notifications older than 6 months with No Work Order Assigned* Status ORAS = Work Order Assigned | Notification Creation Date | PF2, WP1 |
9004-011 | C1 | Notification Company Code incorrect | Notificationas per Relevancy Criteria with Invalid Company Code (T001) | Company Code, Company Code | PF2, WP1 |
9004-012 | C1 | Invalid or no Planner Group linked to Notification | Notification as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I) | Planner Group | PF2, WP1 |
9004-013 | C1 | Notification Location incorrect. | Notification as per Relevancy Criteria with Invalid Location (T499S) | Location | PF2, WP1 |
9004-014 | C2 | Notification Planning Plant and Maintenance Plant are not the same. | Notification as per Relevancy Criteria with Planning Plant <> Maintenance Plant | Maintenance Plant, Planning Plant | PF2, WP1 |
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:
Data Privacy and Sensitivity
Extraction
Extract data from a source into Syniti Migrate. There are 2 possibilities:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- 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)
DCT will not be necessary for Notification.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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- 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 dspIntergrate) | 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. To be updated. 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 | Move from PE1 to S/4 HANA 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 | If not blank, Transform based on mapping table for Equipment / Functional Location 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 Label | S/4 HANA | IFLO | -TPLNR | Functional Location Label | If not blank, Transform based on mapping table for Equipment / Functional Location 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 | VIQM | L- INGRP | 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 | VIQM | L- WERK | Maintenance Planning Plant | Follow 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 center. 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 | Result of the Work Centre name based on S/4 HANA mapped value of ARBPL |
| 11 | PF2, WP2 | CRHD | WERKS | Work Centre plant | S/4 HANA | CRHD | WERKS | Work Centre plant | Result of the 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 | Move from PF2/WP2 to S/4 HANA 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 | Move from PF2/WP2 to S/4 HANA 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 | Move from PF2/WP2 to S/4 HANA 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 | Move from PF2/WP2 to S/4 HANA If 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 | Move from PF2/WP2 to S/4 HANA If 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 Blank and not linked to Work Order, copy Start Date into End Date. Validation: End Date cannot be earlier than start date |
| 17 | PF2, WP2 | QMEL | PRIOK | Priority | S/4 HANA | QMEL | PRIOK | Priority | Transform based on mapping table Priority. Error if cannot be mapped. 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 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 | Move from PF2/WP2 to S/4 HANA | ||
| 25 | PF2, WP2 | QMIH | AUSVN | Malfunct. Start Date | S/4 HANA | Malfunct. Start Date | Move from PF2/WP2 to S/4 HANA | ||
| 26 | PF2, WP2 | QMIH | AUZTV | Malfunct. Start Time | S/4 HANA | Malfunct. Start Time | Move from PF2/WP2 to S/4 HANA | ||
| 27 | PF2, WP2 | QMIH | AUSBS | Malfunct. End Date | S/4 HANA | Malfunct. End Date | Move from PF2/WP2 to S/4 HANA | ||
| 28 | PF2, WP2 | QMIH | AUZTB | Malfunct. End Time | S/4 HANA | Malfunct. End Time | Move from PF2/WP2 to S/4 HANA | ||
| 29 | PF2, WP2 | QMIH | AUSZT | Breakdown Duration | S/4 HANA | Breakdown Duration | Move from PF2/WP2 to S/4 HANA | ||
| 30 | PF2, WP2 | QMIH | MAUEH | Breakdown Unit | S/4 HANA | Breakdown Unit | Move from PF2/WP2 to S/4 HANA |
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
xtAUFK | Cross Reference table for Work Order |
Planner Group | Mapping table for Planner Group |
Revision | Cross Reference table for Revision |
Work Centre | Cross Reference table for Work Centre |
Equipment | Cross Reference table for Equipment |
Functional Location | Cross Reference table for Functional Location |
WBS Element | Cross Reference table for WBS Element |
Cost Centre | Cross Reference table for Cost Centre |
Profit Centre | Cross Reference table for Profit Centre |
Vendor | Cross Reference table for Vendor |
xtMARA | Cross Reference table for Material |
Assembly | Cross Reference table for Assembly |
Outline Agreement | Cross Reference table for Outline Agreement |
G/L Account | Cross Reference table for G/L Account |
Info Record | Cross Reference table for Purchase Info Record |
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:
|
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:
|
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- 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 | TQ80 - Notification Types |
| 2 | MCH1 - Batches (if Batch Management Cross-Plant) |
| 3 | T001L - Storage Locations details |
| 4 | T001W - Plants/Branches details |
| 5 | T006 - Units of Measurement details |
| 6 | T023 - Material Groups details |
| 7 | T024 - Purchasing Groups details |
| 8 | T024E - Purchasing Organizations details |
| 9 | T179 - Materials: Product Hierarchies details |
| 10 | T352B - Technical report details |
| 11 | T356 - Priorities details |
| 12 | T356A - Priority type table details |
| 13 | TCURC - Currency Codes details |
| 14 | TQ15 - Inspection catalog type index details |
| 15 | TQ81 - Notification Scenario details |
| 16 | TQ81V - Usage of parts details |
| 17 | TQ86 - Report category for defects recording details |
| 18 | TSPA - Organizational Unit: Sales Divisions details |
| 19 | TTSEGTPLH - Time Segment Template Header details |
| 20 | TTZZ - Time zones details |
| 21 | TVBVK - Organizational Unit: Sales Groups per Sales Office details |
| 22 | TVKBZ - Org.Unit: Sales Office: Assignment to Organizational Unit details |
| 23 | TVKO - Organizational Unit: Sales Organizations details |
| 24 | TVTW - Organizational Unit: Distribution Channels details |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
9003 | Revision |
1030 | Work Centre |
1002 | Equipment |
1003 | Functional Location |
1026/1027 | WBS Element |
1074 | Cost Centre |
1073 | Profit Centre |
3018 | Vendor |
2019 | Material |
1010 | Assembly |
Outline Agreement | |
1094 | Purchase Info Records (Including Pricing Conditions) |
1067 | GL Account |
1078 | Cost Element |
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. |
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.