Status

Owner

ERGUIZA-ext, Pinky Love 

Stakeholders

LEIGHTON-ext, Dean PUN-ext, Eddy TEE-ext, Paul JOSHI-ext, Aditya MOUSSA-ext, Eva HUSSAN-ext, Nishin STEFANESCU-ext, Aurelia YILMAZTURK-ext, Gokhan 

Purpose

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

Legacy Work Center is using a diverse range of formats across the different systems. There may be instances where the same Work Centers are duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Work Centers will be standardized.


Conversion Scope

The scope of this document covers the approach for converting active Classes from Legacy systems (PF2, WP2) and creation of New Work Centers into S/4 HANA following the SyWay Work Center Master Data Design Standard.

A Work Center is an organizational unit that defines by whom or what a maintenance or production task is performed. The Work Centre has a capacity to do work and the activities performed by them can be costed by setting rates for those activities. A Work Centre can represent either people or machines or both. 

Main Work Center
Main Work Centers define the execution and organizational ownership of work management objects such as Notifications, Work Orders and Maintenance Plans within a Maintenance Plant.

They represent the work group team leaders or supervisors who organize and manage the maintenance workforce on a day-to-day basis. This includes coordinating both planned maintenance and unplanned breakdown work and effectively merging the two based on daily priorities and resource availability.

Work Center Category Consideration
Work Centers are distinguished by their Work Center category (e.g. Production Work Center or Maintenance Work Center). The category selected determines which data fields can be maintained in the Work Center master record.

For Plant Maintenance purposes, the default Work Center category will be Maintenance Work Center. However, if the Work Center is intended to represent a machine, the category should be set to "Machine".

Within the Work Center master data, the Work Center category is used to identify it as a Plant Maintenance Work Center. Additionally, a Control Key is maintained to specify the business transactions (i.e. such as scheduling or costing) that are applicable to the Work Center when used in maintenance task lists or maintenance orders.

The data from legacy system includes:

  1. Object Type (CRHD-OBTY) = A (Work Centre)
  2. Work Centers (CRHD-ARPBL) within Maintenance Plants (CRHD-WERKS) in scope (Value Mapping: Plant where Maintenance Plant = Yes)
  3. Work Centers (CRHD-ARPBL) assigned to any of the below PM Objects in the Legacy Systems:
    1. Active Legacy Functional Location (IFLOT-TPLR) ** (System Status TJ02T-TXT04 <> INAC)
    2. Active Legacy Equipment (EQUI-EQUNR) ** (System Status TJ02T-TXT04 <> INAC)
    3. Active Legacy Task List
      • Task List Type (PLKO-PLNTY) can be any of: A - General Maintenance Task List; E - Equipment Task List; T - Task List for Functional Location
      • Task List Status (PLKO-STATU) can be any of: 2 - Released for Order; 3 - Released for Costing; 4 - Released (General)
      • Task List Usage (PLKO-VERWE) = "004"
    4. Legacy Maintenance Items (MPOS-WAPOS) linked to Active Legacy Functional Location **
    5. Legacy Maintenance Items (MPOS-WAPOS) linked to Active Legacy Equipment **
    6. Open Legacy Work Orders (AUFK-AUFNR)

The data from legacy system excludes:

  1. Work Center for Deletion (Deletion Indicator = X)


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2, WP2

Work Centers will be collected via DCT. An initial extract of the relevant work centers will be provided in google sheet format to assist business in decision making on including any relevant classes from PF2 and WP2 as EAM Work Centers.

Any additional Work Centers that need to be created to support the new design may be added in the DCT.

A review and standardization will be done across all classes in the DCT. 

Please see an indication of what will be baselined from source systems below and what will be constructed in the DCT. 

4,500
3,000

Additional Information

Multi-language Requirement

EAM Work Center description will be made available in English.
Multi language is supported for EAM Work Center. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Work Center.

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.

1. Work Center Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
CRHDWERKSWERKS_DPlantCHAR4Mandatory
CRHDARBPLARBPLWork CentreCHAR8Mandatory
CRHDVERWEAP_VERWEWork Centre CategoryCHAR4Mandatory
CRHDVERANAP_VERANPerson ResponsibleCHAR3
CRHDPLANVAP_PLANVUsageCHAR3Mandatory
CRHDVGWTSVORGSCHLStandard Value KeyCHAR4Mandatory
CRHDSTEUSSTEUSControl KeyCHAR4Mandatory
CRHDSTEUS_REFSTEUS_REFRef Ind for Control KeyCHAR1Mandatory
CRHDPDESTCR_PDESTPrinterCHAR4Mandatory
CRHDFORTNAP_FORM_TNInt. Proc. DurationCHAR6Mandatory


2. Work Center Description

TableFieldData ElementField DescriptionData TypeLengthRequirement
CRHDARBPLARBPLWork CentreCHAR8Mandatory
CRTXKTEXTCR_KTEXTWork Centre DescriptionCHAR40Mandatory
CRTXSPRASSPRASLanguage KeyLANG1Mandatory

Note: Each Work Center Description must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian Portuguese, German and Spanish


3. Work Center Capacity

TableFieldData ElementField DescriptionData TypeLengthRequirement
CRHDARBPLARBPLWork CentreCHAR8Mandatory
CRCAFORKNAP_FORM_KNOther Formula (Capacity)CHAR6Mandatory
KAKOKAPARKAPARTCapacity CategoryCHAR3Mandatory
KAKOPLANRKAPPLANERCapacity ResponsibleCHAR3Mandatory
KAKOKALIDCR_WFCIDFactory CalendarCHAR2Mandatory
KAKOVERSAKAPVERSAKTActive VersionNUMC2Mandatory
KAKOMEINSKAPBASISCapacity Base UnitUNIT3Mandatory
KAKOBEGZTKAPBEGZTStart TimeINT410Mandatory
KAKOENDZTKAPENDZTEnd TimeINT410Mandatory
KAKOPAUSEKAPPAUSELength of breaksINT410Mandatory
KAKONGRADNUTZGRADCapacity UtilizationNUMC3Mandatory
KAKOAZNORKAPANZAHLNo. Ind. CapacitiesINT25Mandatory
KAKOKAPEHCR_KAPEHCapacity Unit of MeasureUNIT3Mandatory
KAKOKAPAVOKAP_KZAVOSeveral operations can use capacityCHAR1Mandatory
KAKOKAPLPLKAP_KZLPLLong-term planning takes capacity into accountCHAR1Mandatory

Note: Each Work Center must have a corresponding Work Center Capacity Entry


4. Work Center Cost Center

TableFieldData ElementField DescriptionData TypeLengthRequirement
CRHDARBPLARBPLWork CentreCHAR8Mandatory
CRCOKOSTLKOSTLCost CentreCHAR10
CRCOLSTARLSTARActivity TypeCHAR6
CRCOFORMLAP_FORM_C1Formula (Costing)CHAR6

Note: Each Work Center must have a corresponding Cost Center Entry


Data Cleansing

No data cleansing is required for Work Center in the legacy systems. If any cleansing is deemed necessary, it will be performed outside of the system.

As a result, the cleansed Work Center data will be populated directly in the Data Collection Template (DCT).

Conversion Process

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

Collection will be done manually in the Data Collection Template for the following scenarios:

  • For new classes that need to be created to support the to-be design


Data Privacy and Sensitivity

Not Applicable


Extraction

  1. 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 DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team
2Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. 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 ScreenParameter NameSelection TypeRequirementValue to be entered/set
Not Applicable




Data Collection Template (DCT)

Target Ready Data Collection Template will be created for EAM Work Center data with exception of some fields which require transformation as mentioned in the transformation rule.

  1. The extracted report will be loaded into the required structure using the DCT.
  2. Standardization activities (including deduplication, standardization and additions)  will be carried out within the DCT.

Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.


1. Work Center Header Data Construction Rules

Field NameField DescriptionRule
WERKSPlant

Mandatory.

Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes

ARBPLWork Centre

Mandatory.

The naming convention for Work Centres will follow the structure:

Internal work center format: SXXXXNNN
S = Syensqo
XXXX = Discipline: Indicates the type of work (e.g. MECH for Mechanical, ELEC for Electrical)
NNN = A three-digit sequential number (e.g. 001, 002, 003) to ensure uniqueness and allow multiple Work Centers within the same plant/discipline/function grouping.

External work center format: EXXXXNNN
E = External Resource (Contractor)
XXXX = Discipline: Indicates the type of work (e.g. MECH for Mechanical, ELEC for Electrical)
NNN = A three-digit sequential number (e.g. 001, 002, 003) to ensure uniqueness and allow multiple Work Centers within the same plant/discipline/function grouping.

T = Tools and Equipment 
XXXX = T&E Type: Indicates the type of tool or equipment (e.g. CRNE for Crane, FKLT for Forklift)
NNN = A three-digit sequential number (e.g. 001, 002, 003) to ensure uniqueness and allow multiple Work Centers within the same plant/discipline/function grouping.

VERANPerson Responsible

Conditional.

  • Must be a valid Person Responsible
  • Select supervisor who manages the performing work center. Otherwise, leave the field blank.
PDEST

Printer

Mandatory.

  • Must be a valid Printer
KTEXT_ENWork Centre Description (English)

Mandatory.

Ensure to that this Class Description is in English.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

KTEXT_FRWork Centre Description (French)

Mandatory.

Ensure to that this Class Description is in French.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

KTEXT_ITWork Centre Description (Italian)

Mandatory.

Ensure to that this Class Description is in Italian.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

KTEXT_ZHWork Centre Description (Mandarin)

Mandatory.

Ensure to that this Class Description is in Mandarin.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

KTEXT_BRWork Centre Description (Brazilian)

Mandatory.

Ensure to that this Class Description is in Brazilian.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

KTEXT_PTWork Centre Description (Portuguese)

Mandatory.

Ensure to that this Class Description is in Portuguese.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

KTEXT_DEWork Centre Description (German)

Mandatory.

Ensure to that this Class Description is in German.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes

KTEXT_ESWork Centre Description (Spanish)

Mandatory.

Ensure to that this Class Description is in Spanish.

Ensure that it does not include any of below characters: 
;        Semi-colon
:        Colon
::        Double Colon
?        Question Mark
/        Forward Slash
@        At sign
&        Ampersand
=        Equal Sign
+        Plus Sign
$        Dollar Sign
%        Percent
|        Vertical Bar
[]        Left or Right Square Bracket
"        Double Quotes


2. Work Center Capacity Data Construction Rules

Field NameField DescriptionRule
ARBPLWork Centre

Mandatory.

Should exist in Work Center Header DCT

KALIDFactory Calendar

Mandatory.

  • Must be a valid Factory Calendar
  •  Needs to be selected from value list.
    The factory calendar must correspond to the geographical location of the plant linked to the work centre
BEGZTStart Time

Mandatory.

  • Must follow time format "HHMMSS"
ENDZTEnd Time

Mandatory.

  • Must follow time format "HHMMSS"
PAUSELength of breaks

Mandatory.

  • Must follow time format "HHMMSS"
AZNORNo. Ind. Capacities

Mandatory.

  • Must be an integer value

 Note: Each Work Center must have a corresponding Work Center Capacity Entry


3. Work Center Cost Centre Data Construction Rules

Field NameField DescriptionRule
ARBPLWork Centre

Mandatory.

Should exist in Work Center Header DCT

KOSTLCost Centre

Conditional.

If Control Key = PM01 then  Cost Centre must be chosen from the value list.  
If the Control Key is not equal to PM01 then leave blank

LSTARActivity Type

Conditional.

If Control Key = PM01 then  Activity Type must be chosen from the value list.  
If the Control Key is not equal to PM01 then leave blank

FORMLFormula (Costing)

Conditional.

If Control Key = PM01 then Costing Formula must be chosen from the value list.  
If the Control Key is not equal to PM01 then leave blank

 Note: Each Work Center must have a corresponding Cost Center Entry

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #Step DescriptionTeam Responsible

Not Applicable


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 DescriptionTeam Responsible

1

Obtain DCT Sign-off from Business.

SyWay Data Team

2

In dspMigrate, select the wave – S4/HANA – Plant Maintenance

Syniti

3

Go to Process Area Launch and Process the Object – Work Center

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 error reports

Business/Data owner

7

Generate load files

Syniti


Transformation Rules

1. Work Center Header

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDWERKSPlantS/4 HanaCRHDWERKSPlantValue Mapping: Plant (Maintenance Plant = Yes)
2DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
3----S/4 HanaCRHDVERWEWork Centre CategoryDefault to "0005"
4DCTCRHDVERANPerson ResponsibleS/4 HanaCRHDVERANPerson ResponsibleDirect Mapping
5----S/4 HanaCRHDPLANVUsageDefault to "004"
6----S/4 HanaCRHDVGWTSStandard Value KeyDefault to "SAP0"
7DCTCRHDARPBLWork CentreS/4 HanaCRHDSTEUSControl Key
  • If Work Centre begins with "S", set to "PM01".
  • If Work Centre begins with "E", set to "PM02"
  • If Work Centre begins with "T", set to "PM04"
8----S/4 HanaCRHDSTEUS_REFRef Ind for Control KeyDefault to " " (Unchecked)
9DCTCRHDPDESTPrinterS/4 HanaCRHDPDESTPrinterDirect Mapping
10----S/4 HanaCRHDFORTNInt. Proc. DurationDefault to "SAP004"


2. Work Center Description

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRTXKTEXT_ENWork Centre Description (English)S/4 HanaCRTXKTEXTWork Centre DescriptionDirect Mapping
3----S/4 HanaCRTXSPRASLanguage KeyDefault to "E"

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRTXKTEXT_FRWork Centre Description (French)S/4 HanaCRTXKTEXTWork Centre DescriptionDirect Mapping
3----S/4 HanaCRTXSPRASLanguage KeyDefault to "F"

 UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRTXKTEXT_ITWork Centre Description (Italian)S/4 HanaCRTXKTEXTWork Centre DescriptionDirect Mapping
3----S/4 HanaCRTXSPRASLanguage KeyDefault to "I"

 UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRTXKTEXT_ZHWork Centre Description (Mandarin)S/4 HanaCRTXKTEXTWork Centre DescriptionDirect Mapping
3----S/4 HanaCRTXSPRASLanguage KeyDefault to "1"

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRTXKTEXT_PTWork Centre Description (Brazilian Portuguese)S/4 HanaCRTXKTEXTWork Centre DescriptionDirect Mapping
3----S/4 HanaCRTXSPRASLanguage KeyDefault to "P"

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRTXKTEXT_DEWork Centre Description (German)S/4 HanaCRTXKTEXTWork Centre DescriptionDirect Mapping
3----S/4 HanaCRTXSPRASLanguage KeyDefault to "D"

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRTXKTEXT_ESWork Centre Description (Spanish)S/4 HanaCRTXKTEXTWork Centre DescriptionDirect Mapping
3----S/4 HanaCRTXSPRASLanguage KeyDefault to "S"

Note: Each Work Center Description must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian Portuguese, German and Spanish


3. Work Center Capacity

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2----S/4 HanaCRCAFORKNOther Formula (Capacity)

Default to "SAP008"

3----S/4 HanaKAKOKAPARCapacity CategoryDefault to "002"
4----S/4 HanaKAKOPLANRCapacity Responsible

Default to "PM"

5DCTKAKOKALIDFactory CalendarS/4 HanaKAKOKALIDFactory CalendarDirect Mapping
6----S/4 HanaKAKOVERSAActive Version

Default to "01"

7----S/4 HanaKAKOMEINSCapacity Base Unit

Default to "H"

8DCTKAKOBEGZTStart TimeS/4 HanaKAKOBEGZTStart TimeDirect Mapping
9DCTKAKOENDZTEnd TimeS/4 HanaKAKOENDZTEnd TimeDirect Mapping
10DCTKAKOPAUSELength of breaksS/4 HanaKAKOPAUSELength of breaksDirect Mapping
11----S/4 HanaKAKONGRADCapacity Utilization

Default to "100"

12DCTKAKOAZNORNo. Ind. CapacitiesS/4 HanaKAKOAZNORNo. Ind. CapacitiesDirect Mapping
13----S/4 HanaKAKOKAPEHCapacity Unit of MeasureDefault to "H"
14----S/4 HanaKAKOKAPAVOSeveral operations can use capacity

Default to "X"

15----S/4 HanaKAKOKAPLPLLong-term planning takes capacity into accountDefault to "X"

Note: Each Work Center must have a corresponding Work Center Capacity Entry


4. Work Center Cost Center

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTCRHDARBPLWork CentreS/4 HanaCRHDARBPLWork CentreDirect Mapping
2DCTCRCOKOSTLCost CentreS/4 HanaCRCOKOSTLCost Centre

Value Mapping: Cost Centre

3DCTCRCOLSTARActivity TypeS/4 HanaCRCOLSTARActivity TypeValue Mapping: Activity Type
4DCTCRCOFORMLFormula (Costing)S/4 HanaCRCOFORMLFormula (Costing)

Direct Mapping

Note: Each Work Center must have a corresponding Cost Center Entry

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above
Mapping Table NameMapping Table Description
Not Applicable

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Ensure DCT tables completenessSyWay A2D Data Team
2Run relevancy procedures in Syniti MigrateSyWay A2D Data Team
3Value Mappings are according to the latest design - None for Work CenterSyWay A2D Data Team


Pre-Load Validation

Project Team

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

Completeness

TaskAction
Verify Record CountSyWay A2D Data Team to verify that the total number of relevant records from the  DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

TaskAction
Conversion Accuracy

SyWay A2D Data Team to verify that all fields below meet pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks
Review Error ReportsReview 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

TaskAction
Verify Record CountBusiness Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

TaskAction
Conversion AccuracyBusiness Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data).


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 DescriptionTeam Responsible
1Go to <Load Tool>SyWay A2D Data Team
2Load 3 records for "Create Work Center" function to validate if data is loaded successfully without errorsSyWay A2D Data Team
3Load 3 records for "Assign Characteristics" function to validate if data is loaded successfully without errorsSyWay A2D Data Team
4Proceed with full load if steps 2 and 3 are validatedSyWay A2D Data Team
5Validate few records loaded by accessing standard transactions from S/4HNA E.g. CR03 / IR03 for Work CenterSyWay A2D Data Team
6Generate post load report if step 5 is validatedSyWay A2D Data Team


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
1T001W-Plants/Branches
2T006-Units of Measurement
3T006D-Dimensions
4T430-Operation/Activity control key
5T499S-Location
6TC20-Formula Parameters
7TC21-Standard Value Key
8TC23-Key for use of the work center in the task lists
9TC24-Person responsible for the work center
10TC25-Work Centre Formulas
11TC26-Capacity Category
12TC27-Capacity Planner Groups
13TC30-Work Centre Category
14TC36-Availability Capacity Version
15TCLA-Class Types
16TFACD-Factory Calendar Definition
17TKA01-Controlling Areas

Conversion Objects

Object #Preceding Object Conversion Approach
1015Characteristics
1009Class
1018Production Resources & Tools
1071Activity Type
1074Cost Centre
3001Business Partners - Employee (BUP003)

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 TypeError DescriptionAction Taken










Post-Load Validation

Project Team

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

Completeness

TaskAction

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

TaskAction
Conversion Accuracy

Verify that the EAM Work Center 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

TaskAction

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

TaskAction

Conversion Accuracy

Verify that the EAM Work Center data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.


Key Assumptions

  • Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
  • Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.

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