| Status | Lead Approval |
|---|---|
| Owner | |
| 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:
- Object Type = A (Work Centre)
The data from legacy system excludes:
- Work Center for Deletion (Deletion Indicator = X)
| Source | Scope | Source Approx No. of Records | Target System | Target 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.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
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
- Syniti Migrate connects to the sources.
- 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 Description | Team Responsible |
|---|---|---|
| 1 | Extract data from source system based on relevancy rule | SyWay Data Team |
| 2 | Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. | SyWay Data Team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value 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 Name | Field Description | Rule |
|---|---|---|
| zLegacyWERKS | Legacy Plant | |
| zLegacyARBPL | Legacy Work Centre | |
| zLegacySTEXT | Legacy Work Centre Description | |
| WERKS | Plant | |
| ARBPL | Work Centre | |
| VERWE | Work Centre Category | |
| STEXT | Work Centre Description | |
| SPRAS | Language | Mandatory. Default to "EN". English is required for all Work Centres. |
| VERAN | Person Responsible | |
| PLANV | Usage | |
| VGWTS | Standard Value Key | |
| STEUS | Control Key | |
| KAPART | Capacity Category | |
| FORKN | Other Formula | |
| KTEXT | Capacity Short Text | |
| PLANR | Capacity Planner Group | |
| MOSID | Grouping | |
| KALID | Factory Calendar Id | |
| VERSA | Active Version | |
| MEINS | Base Unit Of Meas. | |
| BEGZT | Start Time | |
| ENDZT | End Time | |
| PAUSE | Length Of Break | |
| NGRAD | Capacity Utilisation | |
| AZNOR | No. Of Individual Capacities | |
| KAPTER | Relevant To Finite Scheduling | |
| KAPAVO | Can Be Used By Several Operations | |
| KAPLPL | Long-Term Planning | |
| FORTN | Int. Proc. Duration | |
| BEGDA | Relevant To Finite Scheduling | |
| ENDDA | End Date | |
| LSTAR | Activity Type Int Proc | |
| LSTAR_REF | Reference (Int Proc) | |
| FORML | Activty Formula (Int Proc) | |
| LVORM | Deletion Flag |
Work Center DCT (Non-EN Language) Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyWERKS | Legacy Plant | |
| zLegacyARBPL | Legacy Work Centre | |
| zLegacySTEXT | Legacy Work Centre Description | |
| SPRAS | Language | Mandatory. Populate for Languages not in English. Must be one of the installed language key : |
| ARBPL | Work Centre | |
| STEXT | Work Centre Description |
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Relevancy Criteria for Functional Location | SyWay A2D Data Team |
| 2 | Relevancy Criteria for Equipment | SyWay A2D Data Team |
| 3 | Relevancy Criteria for Task List | SyWay A2D Data Team |
| 4 | Relevancy Criteria for Maintenance Plan and Item | SyWay A2D Data Team |
| 5 | Relevancy Criteria for Notification | SyWay A2D Data Team |
| 6 | Relevancy Criteria for Work Order | 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 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
- 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 | Obtain DCT Sign-off from Business | SyWay A2D Data Team |
| 2 | <Add steps from Syniti Migrate here> | SyWay A2D Data Team |
| 3 | Review and Validate Error and Preload Reports | SyWay A2D Data Team |
| 4 | Generate Load Files | 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 |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| Not Applicable |
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 | Run relevancy procedures in Syniti Migrate | SyWay A2D Data Team |
| 3 | Value Mappings are according to the latest design - None for Work Center | SyWay A2D Data Team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Verify Record Count | SyWay 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
| 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
Completeness
| Task | Action |
|---|---|
| Verify Record Count | Business 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
| Task | Action |
|---|---|
| Conversion Accuracy | Business 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:
- 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 | Go to <Load Tool> | SyWay A2D Data Team |
| 2 | Load 3 records for "Create Work Center" function to validate if data is loaded successfully without errors | SyWay A2D Data Team |
| 3 | Load 3 records for "Assign Characteristics" function to validate if data is loaded successfully without errors | SyWay A2D Data Team |
| 4 | Proceed with full load if steps 2 and 3 are validated | SyWay A2D Data Team |
| 5 | Validate few records loaded by accessing standard transactions from S/4HNA E.g. CR03 / IR03 for Work Center | SyWay A2D Data Team |
| 6 | Generate post load report if step 5 is validated | SyWay A2D Data Team |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | T001W-Plants/Branches |
| 2 | T006-Units of Measurement |
| 3 | T006D-Dimensions |
| 4 | T430-Operation/Activity control key |
| 5 | T499S-Location |
| 6 | TC20-Formula Parameters |
| 7 | TC21-Standard Value Key |
| 8 | TC23-Key for use of the work center in the task lists |
| 9 | TC24-Person responsible for the work center |
| 10 | TC25-Work Centre Formulas |
| 11 | TC26-Capacity Category |
| 12 | TC27-Capacity Planner Groups |
| 13 | TC30-Work Centre Category |
| 14 | TC36-Availability Capacity Version |
| 15 | TCLA-Class Types |
| 16 | TFACD-Factory Calendar Definition |
| 17 | TKA01-Controlling Areas |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1015 | Characteristics |
| 1009 | Class |
| 1018 | Production Resources & Tools |
| 1071 | Activity Type |
| 1074 | Cost Centre |
| 3001 | Business Partners - Employee (BUP003) |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
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 | 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
| 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 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
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||