You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Status

  Lead Approval

Owner

ERGUIZA-ext, Pinky Love 

Stakeholders

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 = A (Work Centre)

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

Class 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 classes 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

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

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
CRHDWERKSWERKS_DPlantCHAR4Mandatory
CRHDARBPLARBPLWork centerCHAR8Mandatory
CRHDVERWEAP_VERWEWork Center CategoryCHAR4Mandatory
CRHDVERANAP_VERANPerson responsible for the work centerCHAR3Mandatory
CRHDSTANDAP_STANDWork center locationCHAR10
CRHDPLANVAP_PLANVKey for task list usageCHAR3Mandatory
CRHDVGWTSVORGSCHLStandard value keyCHAR4Mandatory
CRHDLVORMAP_LOEVORMDeletion flag for work centerCHAR1
CRHDSTEUSSTEUSControl keyCHAR4Mandatory
CRHDFORTNAP_FORM_TNFormula for the duration of other types of int. processingCHAR6Mandatory
CRHDVGDIMVGDIMARDimension of workCHAR6Mandatory
CRHDVGARBVGWRTARUnit of measure of workUNIT3Mandatory
CRTXKTEXTCR_KTEXTWork Centre Short Text desctiptionCHAR40Mandatory
CRCOBEGDABEGDATUMStart Date of the Validity period for costingDATS8Mandatory
CRCOENDDAENDDATUMEnd Date of the Validity period for costingDATS8Mandatory
CRCOKOKRSKOKRSControlling AreaCHAR4
CRCOKOSTLKOSTLCost CenterCHAR10Mandatory
CRCOLARN1
Activity type int. processingCHAR6Mandatory
CRCOFORML/ FORN1
Formula keyCHAR6Mandatory
KAKOKAPARKAPARTCapacity categoryCHAR3Mandatory
KAKOPLANRKAPPLANERCapacity planner groupCHAR3Mandatory
KAKOKALIDCR_WFCIDFactory calendar IDCHAR2Mandatory
KAKOVERSAKAPVERSAKTActive version of available capacityNUMC2Mandatory
KAKOMEINSKAPBASISBase Unit of Measurement for CapacityUNIT3Mandatory
KAKOBEGZTKAPBEGZTStart time in seconds (internal)INT410Mandatory
KAKOENDZTKAPENDZTFinish time in seconds (internal)INT410Mandatory
KAKOPAUSEKAPPAUSECumulative break time in seconds (internal)INT410
KAKONGRADNUTZGRADCapacity utilization rate (percent)NUMC3Mandatory
KAKOAZNORKAPANZAHLNumber of individual capacitiesINT25Mandatory
KAKOKAPEHCR_KAPEHUnit of measure of capacityUNIT3Mandatory
KAKOKAPTERKAP_KZTERIndicator: Capacity relevant to finite schedulingCHAR1Mandatory
KAKOKAPAVOKAP_KZAVOIndicator: Several operations can use capacityCHAR1Mandatory
KAKOKAPLPLKAP_KZLPLIndicator: Capacity excluded from long-term planningCHAR1
KAKTKTEXTCR_KTEXTCapacity Short Text descriptionCHAR40Mandatory
CRCAFORKNAP_FORM_KNFormula keyCHAR6Mandatory
HRP1001OTYPEOTYPEObject typeCHAR2Mandatory
HRP1001OBJIDCR_OBJIDObject IDNUMC8Mandatory
HRP1001PLVARPLVARPlan versionCHAR2Mandatory
HRP1001RSIGNRSIGNRelationshipCHAR1Mandatory
HRP1001RELATRELATRelnshipCHAR3Mandatory
HRP1001ISTATISTAT_DPlanning statusCHAR1Mandatory
HRP1001PRIOXPRIOXPriorityCHAR2
HRP1001BEGDABEGDATUMStart dateDATS8
HRP1001ENDDAENDDATUMEnd DateDATS8
HRP1001VARYFVARYFVariation fieldCHAR10
HRP1001SEQNRSEQNRIT record no.NUMC3Mandatory
HRP1001INFTYINFOTYPInfotypeCHAR4Mandatory
HRP1001OTJIDOTJIDObj.type/obj.IDCHAR10Mandatory
HRP1001SUBTYSUBTYPSubtypeCHAR4Mandatory
HRP1001AEDTMAEDTMChanged onDATS8Mandatory
HRP1001UNAMEUSRNAMEUser NameCHAR12Mandatory
HRP1001REASNREASNReasonCHAR2
HRP1001HISTOHISTOHistorical rec.CHAR1
HRP1001ITXNRITXNRText ModuleNUMC8
HRP1001SCLASSCLASRel.obj.typeCHAR2Mandatory
HRP1001SOBIDSOBIDID rel.objectCHAR45Mandatory
HRP1001PROZTAP_PROZ_KAPercentageDEC5Mandatory
HRP1001ADATANRHRADATANRADATA numberCHAR32
HRP1001OTYPEOTYPEObject typeCHAR2Mandatory
HRP1001OBJIDCR_OBJIDObject IDNUMC8Mandatory
HRP1001PLVARPLVARPlan versionCHAR2Mandatory
HRP1001RSIGNRSIGNRelationshipCHAR1Mandatory
HRP1001RELATRELATRelnshipCHAR3Mandatory
HRP1001ISTATISTAT_DPlanning statusCHAR1Mandatory
HRP1001PRIOXPRIOXPriorityCHAR2
HRP1001BEGDABEGDATUMStart dateDATS8Mandatory
HRP1001ENDDAENDDATUMEnd DateDATS8Mandatory
HRP1001VARYFVARYFVariation fieldCHAR10Mandatory
HRP1001SEQNRSEQNRIT record no.NUMC3Mandatory
HRP1001INFTYINFOTYPInfotypeCHAR4Mandatory
HRP1001OTJIDOTJIDObj.type/obj.IDCHAR10Mandatory
HRP1001SUBTYSUBTYPSubtypeCHAR4Mandatory
HRP1001AEDTMAEDTMChanged onDATS8Mandatory
HRP1001UNAMEUSRNAMEUser NameCHAR12Mandatory
HRP1001REASNREASNReasonCHAR2
HRP1001HISTOHISTOHistorical rec.CHAR1
HRP1001ITXNRITXNRText ModuleNUMC8
HRP1001SCLASSCLASRel.obj.typeCHAR2Mandatory
HRP1001SOBIDSOBIDID rel.objectCHAR45Mandatory
HRP1001PROZTAP_PROZ_KAPercentageDEC5Mandatory
HRP1001ADATANRHRADATANRADATA numberCHAR32


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 sites not on SAP-PF2 or WP2 systems
  • For new classes that need to be created to support the to-be design

Data Privacy and Sensitivity


Extraction

  1. Syniti Migrate connects to the sources.
  2. An initial extract of the relevant Characteristics will be loaded into a google sheet report to assist business with any standardization.

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

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
Not Applicable




Data Collection Template (DCT)

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

Work Center DCT Rules

Field NameField DescriptionRule
zLegacyWERKSLegacy Plant
zLegacyARBPLLegacy Work Centre
zLegacySTEXTLegacy Work Centre Description
WERKSPlant
ARBPLWork Centre
VERWEWork Centre Category
STEXTWork Centre Description
SPRASLanguage

Mandatory.

Default to "EN". English is required for all Work Centres.

VERANPerson Responsible
PLANVUsage
VGWTSStandard Value Key
STEUSControl Key
KAPART Capacity Category
FORKNOther Formula
KTEXTCapacity Short Text
PLANRCapacity Planner Group
MOSIDGrouping
KALIDFactory Calendar Id
VERSAActive Version
MEINSBase Unit Of Meas.
BEGZTStart Time
ENDZTEnd Time
PAUSELength Of Break
NGRADCapacity Utilisation
AZNORNo. Of Individual Capacities
KAPTERRelevant To Finite Scheduling
KAPAVOCan Be Used By Several Operations
KAPLPLLong-Term Planning
FORTNInt. Proc. Duration
BEGDARelevant To Finite Scheduling
ENDDAEnd Date
LSTARActivity Type Int Proc
LSTAR_REFReference (Int Proc)
FORMLActivty Formula (Int Proc)
LVORMDeletion Flag

Work Center DCT (Non-EN Language) Rules

Field NameField DescriptionRule
zLegacyWERKSLegacy Plant
zLegacyARBPLLegacy Work Centre
zLegacySTEXTLegacy Work Centre Description
SPRASLanguage

Mandatory. Populate for Languages not in English.

Must be one of the installed language key  :
(List down as per Language KDD)

ARBPLWork Centre
STEXTWork Centre Description

Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Relevancy Criteria for Functional LocationSyWay A2D Data Team
2Relevancy Criteria for EquipmentSyWay A2D Data Team
3Relevancy Criteria for Task ListSyWay A2D Data Team
4Relevancy Criteria for Maintenance Plan and ItemSyWay A2D Data Team
5Relevancy Criteria for NotificationSyWay A2D Data Team
6Relevancy Criteria for Work OrderSyWay 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 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
  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
1Obtain DCT Sign-off from BusinessSyWay A2D Data Team
2<Add steps from Syniti Migrate here>SyWay A2D Data Team
3Review and Validate Error and Preload ReportsSyWay A2D Data Team
4

Generate Load Files

SyWay A2D Data Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic






CRHDWERKSPlant






CRHDARBPLWork center






CRHDVERWEWork Center Category






CRHDVERANPerson responsible for the work center






CRHDSTANDWork center location






CRHDPLANVKey for task list usage






CRHDVGWTSStandard value key






CRHDLVORMDeletion flag for work center






CRHDSTEUSControl key






CRHDFORTNFormula for the duration of other types of int. processing






CRHDVGDIMDimension of work






CRHDVGARBUnit of measure of work






CRTXKTEXTWork Centre Short Text desctiption






CRCOBEGDAStart Date of the Validity period for costing






CRCOENDDAEnd Date of the Validity period for costing






CRCOKOKRSControlling Area






CRCOKOSTLCost Center






CRCOLARN1Activity type int. processing






CRCOFORML/ FORN1Formula key






KAKOKAPARCapacity category






KAKOPLANRCapacity planner group






KAKOKALIDFactory calendar ID






KAKOVERSAActive version of available capacity






KAKOMEINSBase Unit of Measurement for Capacity






KAKOBEGZTStart time in seconds (internal)






KAKOENDZTFinish time in seconds (internal)






KAKOPAUSECumulative break time in seconds (internal)






KAKONGRADCapacity utilization rate (percent)






KAKOAZNORNumber of individual capacities






KAKOKAPEHUnit of measure of capacity






KAKOKAPTERIndicator: Capacity relevant to finite scheduling






KAKOKAPAVOIndicator: Several operations can use capacity






KAKOKAPLPLIndicator: Capacity excluded from long-term planning






KAKTKTEXTCapacity Short Text description






CRCAFORKNFormula key






HRP1001OTYPEObject type






HRP1001OBJIDObject ID






HRP1001PLVARPlan version






HRP1001RSIGNRelationship






HRP1001RELATRelnship






HRP1001ISTATPlanning status






HRP1001PRIOXPriority






HRP1001BEGDAStart date






HRP1001ENDDAEnd Date






HRP1001VARYFVariation field






HRP1001SEQNRIT record no.






HRP1001INFTYInfotype






HRP1001OTJIDObj.type/obj.ID






HRP1001SUBTYSubtype






HRP1001AEDTMChanged on






HRP1001UNAMEUser Name






HRP1001REASNReason






HRP1001HISTOHistorical rec.






HRP1001ITXNRText Module






HRP1001SCLASRel.obj.type






HRP1001SOBIDID rel.object






HRP1001PROZTPercentage






HRP1001ADATANRADATA number






HRP1001OTYPEObject type






HRP1001OBJIDObject ID






HRP1001PLVARPlan version






HRP1001RSIGNRelationship






HRP1001RELATRelnship






HRP1001ISTATPlanning status






HRP1001PRIOXPriority






HRP1001BEGDAStart date






HRP1001ENDDAEnd Date






HRP1001VARYFVariation field






HRP1001SEQNRIT record no.






HRP1001INFTYInfotype






HRP1001OTJIDObj.type/obj.ID






HRP1001SUBTYSubtype






HRP1001AEDTMChanged on






HRP1001UNAMEUser Name






HRP1001REASNReason






HRP1001HISTOHistorical rec.






HRP1001ITXNRText Module






HRP1001SCLASRel.obj.type






HRP1001SOBIDID rel.object






HRP1001PROZTPercentage






HRP1001ADATANRADATA number


Transformation Mapping

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

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

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

Configuration

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

Error TypeError DescriptionAction Taken










Post-Load Validation

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

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.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 17) Apr 20, 2026 08:51 ERGUIZA-ext, Pinky Love
v. 126 Apr 16, 2026 14:28 ERGUIZA-ext, Pinky Love
v. 125 Mar 13, 2026 12:34 ERGUIZA-ext, Pinky Love
v. 124 Mar 09, 2026 13:34 ERGUIZA-ext, Pinky Love
v. 123 Mar 05, 2026 07:39 ERGUIZA-ext, Pinky Love
v. 122 Mar 05, 2026 07:38 ERGUIZA-ext, Pinky Love
v. 121 Mar 05, 2026 07:01 ERGUIZA-ext, Pinky Love
v. 120 Mar 05, 2026 06:52 ERGUIZA-ext, Pinky Love CR0368: Added INC-Legacy Work Center Category in Relevancy Criteria and Transformation Mapping
v. 119 Mar 04, 2026 09:20 ERGUIZA-ext, Pinky Love
v. 118 Feb 23, 2026 12:12 ERGUIZA-ext, Pinky Love

Go to Page History

Workflow history

Title Last Updated By Updated Status  
There are no pages at the moment.

  • No labels