| Status | Lead Approval |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create EAM Work Centres in S/4 HANA.
Legacy Work Centre is using a diverse range of formats across the different systems. There may be instances where the same Work Centres are duplicated within and across sources. This results in data inconsistency. As per SyWay design, EAM Work Centres will be standardized.
Conversion Scope
The scope of this document outlines the approach for converting active Work Centres from the legacy systems (PF2, WP2) and for creating new Work Centres in S/4HANA, in alignment with the SyWay Work Centre Master Data Design Standard.
A Work Centre is an organizational element that identifies the resource - whether a person, machine, or group - responsible for performing maintenance activities. Each Work Centre has a defined capacity to perform work, and the activities carried out can be costed by assigning activity rates.
Main Work Centre
Main Work Centres 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 Centre Category Consideration
Work Centres are distinguished by their Work Centre category (e.g. Production Work Centre or Maintenance Work Centre). The category selected determines which data fields can be maintained in the Work Centre master record.
For Plant Maintenance purposes, the default Work Centre category will be Maintenance Work Centre.
Within the Work Centre master data, the Work Centre category is used to identify it as a Plant Maintenance Work Centre. Additionally, a Control Key is maintained to specify the business transactions (i.e. such as scheduling or costing) that are applicable to the Work Centre when used in maintenance task lists or maintenance orders.
The data from legacy system includes:
- Object Type (CRHD-OBTY) = A (Work Centre)
- Work Centres (CRHD-ARPBL) within Maintenance Plants (CRHD-WERKS) in scope (Value Mapping: Plant where Maintenance Plant = Yes)
- Work Centres (CRHD-ARPBL) assigned to any of the below PM Objects in the Legacy Systems:
- Active Legacy Functional Location (IFLOT-TPLR) ** (System Status TJ02T-TXT04 <> INAC)
- Active Legacy Equipment (EQUI-EQUNR) ** (System Status TJ02T-TXT04 <> INAC)
- 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"
- Legacy Maintenance Items (MPOS-WAPOS) linked to Active Legacy Functional Location **
- Legacy Maintenance Items (MPOS-WAPOS) linked to Active Legacy Equipment **
- Open Legacy Work Orders (AUFK-AUFNR)
The data from legacy system excludes:
- Work Centre for Deletion (Deletion Indicator (CRHD-LVORM) = "X")
List of Tables to extract for this object is maintained here: Extract Table Register.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2, WP2 | Work Centres will be collected via DCT. An initial extract of the relevant Work Centres 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 Centres. Any additional Work Centres 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. Note: A full Data Construct will be created for Work Centre, as the SyWay design is changing and a complete standardization will be performed. While data may already exist, it cannot be easily transformed to align with the new SyWay data setup. | 4,500 | 2,000 |
Additional Information
Multi-language Requirement
EAM Work Centre description will be made available in English.
Multi language is supported for EAM Work Centre. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Work Centre.
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
The technical design of the target for this conversion approach.
1. Work Centre Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| CRHD | WERKS | WERKS_D | Plant | CHAR | 4 | Mandatory |
| CRHD | ARBPL | ARBPL | Work Centre | CHAR | 8 | Mandatory |
| CRHD | VERWE | AP_VERWE | Work Centre Category | CHAR | 4 | Mandatory |
| CRHD | VERAN | AP_VERAN | Person Responsible | CHAR | 3 | Conditional |
| CRHD | PLANV | AP_PLANV | Usage | CHAR | 3 | Mandatory |
| CRHD | VGWTS | VORGSCHL | Standard Value Key | CHAR | 4 | Mandatory |
| CRHD | STEUS | STEUS | Control Key | CHAR | 4 | Mandatory |
| CRHD | STEUS_REF | STEUS_REF | Ref Ind for Control Key | CHAR | 1 | Mandatory |
| CRHD | PDEST | CR_PDEST | Printer | CHAR | 4 | Mandatory |
| CRHD | FORTN | AP_FORM_TN | Int. Proc. Duration | CHAR | 6 | Mandatory |
2. Work Centre Description
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| CRHD | ARBPL | ARBPL | Work Centre | CHAR | 8 | Mandatory |
| CRTX | KTEXT | CR_KTEXT | Work Centre Description | CHAR | 40 | Mandatory |
| CRTX | SPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
Note: Each Work Centre Description must include one entry in English and one entry in the language of the country where the plant is located.
3. Work Centre Capacity
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| CRHD | ARBPL | ARBPL | Work Centre | CHAR | 8 | Mandatory |
| CRCA | FORKN | AP_FORM_KN | Other Formula (Capacity) | CHAR | 6 | Mandatory |
| KAKO | KAPAR | KAPART | Capacity Category | CHAR | 3 | Mandatory |
| KAKO | PLANR | KAPPLANER | Capacity Responsible | CHAR | 3 | Mandatory |
| KAKO | KALID | CR_WFCID | Factory Calendar | CHAR | 2 | Mandatory |
| KAKO | VERSA | KAPVERSAKT | Active Version | NUMC | 2 | Mandatory |
| KAKO | MEINS | KAPBASIS | Capacity Base Unit | UNIT | 3 | Mandatory |
| KAKO | BEGZT | KAPBEGZT | Start Time | INT4 | 10 | Mandatory |
| KAKO | ENDZT | KAPENDZT | End Time | INT4 | 10 | Mandatory |
| KAKO | PAUSE | KAPPAUSE | Length of breaks | INT4 | 10 | Mandatory |
| KAKO | NGRAD | NUTZGRAD | Capacity Utilization | NUMC | 3 | Mandatory |
| KAKO | AZNOR | KAPANZAHL | No. Ind. Capacities | INT2 | 5 | Mandatory |
| KAKO | KAPEH | CR_KAPEH | Capacity Unit of Measure | UNIT | 3 | Mandatory |
| KAKO | KAPAVO | KAP_KZAVO | Several operations can use capacity | CHAR | 1 | Mandatory |
| KAKO | KAPLPL | KAP_KZLPL | Long-term planning takes capacity into account | CHAR | 1 | Mandatory |
Note: Each Work Centre must have a corresponding Work Centre Capacity Entry
4. Work Centre Cost Center
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| CRHD | ARBPL | ARBPL | Work Centre | CHAR | 8 | Mandatory (When Control Key = PM01) |
| CRCO | KOSTL | KOSTL | Cost Centre | CHAR | 10 | Mandatory (When Control Key = PM01) |
| CRCO | LSTAR | LSTAR | Activity Type | CHAR | 6 | Mandatory (When Control Key = PM01) |
| CRCO | FORML | AP_FORM_C1 | Formula (Costing) | CHAR | 6 | Mandatory (When Control Key = PM01) |
Note: Each Work Centre must have a corresponding Cost Center, Activity Type and Formula (Costing) entries if Work Centre Control Key = PM01
Work Centre Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Work Centre information follows the Master Data Standard document that is located here.
Data Cleansing
No data cleansing is required for Work Centre in the legacy systems. If any cleansing is deemed necessary, it will be performed outside of the system.
As a result, the cleansed Work Centre data will be populated directly in the Data Collection Template (DCT).
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| Not Applicable |
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 PM Work Centres that need to be created to support the to-be design
Data Privacy and Sensitivity
Not Applicable
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 as reference point to identify the records that are applicable for the data construction in the DCT.
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 EAM Work Centre data with exception of some fields which require transformation as mentioned in the transformation rule.
- The extracted report will be loaded into the required structure using the DCT.
- 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.
Note: All rules specified below should be documented as a tooltip in the DC Page.
Format:
- Line 1: Mandatory / Conditional
- Line 2: Remaining text
1. Work Centre Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| WERKS | Plant | Mandatory. Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes |
| ARBPL | Work Centre | Mandatory. The naming convention for Work Centres will follow the structure: Internal Work Centre format: SXXXXNNN External Work Centre format: EXXXXNNN T = Tools and Equipment |
| VERAN | Person Responsible | Conditional.
|
| PDEST | Printer | Mandatory.
|
| KTEXT_EN | Work Centre Description (English) | Mandatory. Ensure that this Description is in English. Ensure that it does not include any of below characters: |
| KTEXT_FR | Work Centre Description (French) | Conditional (Required only if the language of the country where the plant is located is French). Ensure that this Description is in French. Ensure that it does not include any of below characters: |
| KTEXT_IT | Work Centre Description (Italian) | Conditional (Required only if the language of the country where the plant is located is Italian). Ensure that this Description is in Italian. Ensure that it does not include any of below characters: |
| KTEXT_ZH | Work Centre Description (Mandarin) | Conditional (Required only if the language of the country where the plant is located is Mandarin). Ensure that this Description is in Mandarin. Ensure that it does not include any of below characters: |
| KTEXT_PT | Work Centre Description (Brazilian Portuguese) | Conditional (Required only if the language of the country where the plant is located is Portuguese). Ensure that this Description is in Portuguese. Ensure that it does not include any of below characters: |
| KTEXT_DE | Work Centre Description (German) | Conditional (Required only if the language of the country where the plant is located is German). Ensure that this Description is in German. Ensure that it does not include any of below characters: |
| KTEXT_ES | Work Centre Description (Spanish) | Conditional (Required only if the language of the country where the plant is located is Spanish). Ensure that this Description is in Spanish. Ensure that it does not include any of below characters: |
| KALID | Factory Calendar | Mandatory.
|
| BEGZT | Start Time | Mandatory.
|
| ENDZT | End Time | Mandatory.
|
| PAUSE | Length of breaks | Mandatory.
|
| AZNOR | No. Ind. Capacities | Mandatory.
|
| KOSTL | Cost Centre | Conditional. If Work Centre begins with "S", populate with relevant Cost Centre. |
| LSTAR | Activity Type | Conditional. If Work Centre begins with "S", populate with relevant Activity Type. |
| FORML | Formula (Costing) | Conditional. If Work Centre begins with "S", populate with Costing Formula from the value list (TC25). |
Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report).
Extraction Dependencies
| Item # | Step Description | Team 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 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 Data Team |
2 | In dspMigrate, select the wave – S4/HANA – Plant Maintenance | Syniti |
3 | Go to Process Area Launch and Process the Object – Work Centre | 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 Centre Header
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | WERKS | Plant | S/4 Hana | CRHD | WERKS | Plant | Direct Mapping |
| 2 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRHD | VERWE | Work Centre Category | Default to "0005" |
| 4 | DCT | CRHD | VERAN | Person Responsible | S/4 Hana | CRHD | VERAN | Person Responsible | Direct Mapping |
| 5 | - | - | - | - | S/4 Hana | CRHD | PLANV | Usage | Default to "004" |
| 6 | - | - | - | - | S/4 Hana | CRHD | VGWTS | Standard Value Key | Default to "SAP0" |
| 7 | - | - | - | - | S/4 Hana | CRHD | STEUS | Control Key |
|
| 8 | - | - | - | - | S/4 Hana | CRHD | STEUS_REF | Ref Ind for Control Key | Default to " " (Unchecked) |
| 9 | DCT | CRHD | PDEST | Printer | S/4 Hana | CRHD | PDEST | Printer | Direct Mapping |
| 10 | - | - | - | - | S/4 Hana | CRHD | FORTN | Int. Proc. Duration | Default to "SAP004" |
2. Work Centre Description
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRTX | KTEXT_EN | Work Centre Description (English) | S/4 Hana | CRTX | KTEXT | Work Centre Description | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRTX | SPRAS | Language Key | Default to "E" |
UNION
(Select Data where KTEXT_FR is populated in the DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRTX | KTEXT_FR | Work Centre Description (French) | S/4 Hana | CRTX | KTEXT | Work Centre Description | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRTX | SPRAS | Language Key | Default to "F" |
UNION
(Select Data where KTEXT_IT is populated in the DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRTX | KTEXT_IT | Work Centre Description (Italian) | S/4 Hana | CRTX | KTEXT | Work Centre Description | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRTX | SPRAS | Language Key | Default to "I" |
UNION
(Select Data where KTEXT_ZH is populated in the DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRTX | KTEXT_ZH | Work Centre Description (Mandarin) | S/4 Hana | CRTX | KTEXT | Work Centre Description | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRTX | SPRAS | Language Key | Default to "1" |
UNION
(Select Data where KTEXT_PT is populated in the DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRTX | KTEXT_PT | Work Centre Description (Brazilian Portuguese) | S/4 Hana | CRTX | KTEXT | Work Centre Description | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRTX | SPRAS | Language Key | Default to "P" |
UNION
(Select Data where KTEXT_DE is populated in the DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRTX | KTEXT_DE | Work Centre Description (German) | S/4 Hana | CRTX | KTEXT | Work Centre Description | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRTX | SPRAS | Language Key | Default to "D" |
UNION
(Select Data where KTEXT_ES is populated in the DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRTX | KTEXT_ES | Work Centre Description (Spanish) | S/4 Hana | CRTX | KTEXT | Work Centre Description | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | CRTX | SPRAS | Language Key | Default to "S" |
Note: Each Work Centre Description must include one entry in English and one entry in the language of the country where the plant is located.
3. Work Centre Capacity
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | CRCA | FORKN | Other Formula (Capacity) | Default to "SAP008" |
| 3 | - | - | - | - | S/4 Hana | KAKO | KAPAR | Capacity Category | Default to "002" |
| 4 | - | - | - | - | S/4 Hana | KAKO | PLANR | Capacity Responsible | Default to "PM" |
| 5 | DCT | KAKO | KALID | Factory Calendar | S/4 Hana | KAKO | KALID | Factory Calendar | Direct Mapping |
| 6 | - | - | - | - | S/4 Hana | KAKO | VERSA | Active Version | Default to "01" |
| 7 | - | - | - | - | S/4 Hana | KAKO | MEINS | Capacity Base Unit | Default to "H" |
| 8 | DCT | KAKO | BEGZT | Start Time | S/4 Hana | KAKO | BEGZT | Start Time | Direct Mapping (Note: Front end Format is HH:MM:SS but needs to be stored in INT4 version in the backend table) |
| 9 | DCT | KAKO | ENDZT | End Time | S/4 Hana | KAKO | ENDZT | End Time | Direct Mapping (Note: Front end Format is HH:MM:SS but needs to be stored in INT4 version in the backend table) |
| 10 | DCT | KAKO | PAUSE | Length of breaks | S/4 Hana | KAKO | PAUSE | Length of breaks | Direct Mapping (Note: Front end Format is HH:MM:SS but needs to be stored in INT4 version in the backend table) |
| 11 | - | - | - | - | S/4 Hana | KAKO | NGRAD | Capacity Utilization | Default to "100" |
| 12 | DCT | KAKO | AZNOR | No. Ind. Capacities | S/4 Hana | KAKO | AZNOR | No. Ind. Capacities | Direct Mapping |
| 13 | - | - | - | - | S/4 Hana | KAKO | KAPEH | Capacity Unit of Measure | Default to "H" |
| 14 | - | - | - | - | S/4 Hana | KAKO | KAPAVO | Several operations can use capacity | Default to "X" |
| 15 | - | - | - | - | S/4 Hana | KAKO | KAPLPL | Long-term planning takes capacity into account | Default to "X" |
Note: Each Work Centre must have a corresponding Work Centre Capacity Entry
4. Work Centre Cost Center
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | CRHD | ARBPL | Work Centre | S/4 Hana | CRHD | ARBPL | Work Centre | Direct Mapping |
| 2 | DCT | CRCO | KOSTL | Cost Centre | S/4 Hana | CRCO | KOSTL | Cost Centre | Value Mapping: Cost Centre |
| 3 | DCT | CRCO | LSTAR | Activity Type | S/4 Hana | CRCO | LSTAR | Activity Type | Value Mapping: Activity Type |
| 4 | DCT | CRCO | FORML | Formula (Costing) | S/4 Hana | CRCO | FORML | Formula (Costing) | Direct Mapping |
Note: Each Work Centre must have a corresponding Cost Center, Activity Type and Formula (Costing) entries if Work Centre Control Key = PM01
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
| Activity Type | Old to New Activity Type |
| Cost Center | Old to New Cost Center |
| Plant | Old to New Plant |
List of Transformation Mappings with additional details is maintained here: Transformation Mappings
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 | Ensure all Transformation mappings are up to date. | SyWay 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 | Ensure Pre-load sign-offs are obtained. | SyWay Data team |
2 | Go to the load tool and select the correct load Program. | SyWay Data team |
3 | Proceed with Data load. | SyWay Data team |
4 | Validate few records loaded by accessing standard transactions | SyWay Data team |
5 | Generate the post load reports in the tool. | SyWay Data team |
6 | Log errors as defects, if any and address resolutions. Close defects. | SyWay Data team |
7 | Resolve defects by reupload and re-generate post load reports if necessary. | SyWay Data team |
8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
9 | Repeat steps 5 to 7 if necessary. | SyWay Data team |
Load Phase and Dependencies
PreCutover
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | T001W-Plants/Branches |
| 2 | T002-Language Keys |
| 3 | T006-Units of Measurement |
| 4 | T430-Operation/Activity control key |
| 5 | TC21-Standard value key |
| 6 | TC23-Key for use of the Work Centre in the task lists |
| 7 | TC24-Person responsible for the Work Centre |
| 8 | TC25-Work Centre formulas |
| 9 | TC26-Capacity category |
| 10 | TC27-Capacity planner groups |
| 11 | TC30-Work Centre category |
| 12 | TC36-Available capacity version |
| 13 | TFACD-Factory calendar definition |
| 14 | TSP03-Spool: Printer declaration |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1071 | Activity Type |
| 1074 | Cost Centre |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Configuration | Invalid Plant | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Language Key | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Unit of Measurement | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Operation/Activity control key | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Standard value key | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Key for use of the Work Centre in the task lists | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Person responsible for the Work Centre | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Work Centre formula | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Capacity category | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Capacity planner group | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Work Centre category | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Available capacity version | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Factory calendar definition | Engage Functional team to expedite and fix the error in the system |
| Configuration | Invalid Spool: Printer declaration | Engage Functional team to expedite and fix the error in the system |
Invalid Data | Invalid Activity Type assigned | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Cost Centre assigned | Expedite whether the master data is changed in the system |
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 Centre 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 Centre 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 cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
- Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
- Not all legacy PM Work Centres need to be mapped to S/4 HANA Work Centres. If any of the successor objects is dependent on a Work Centre field with no mapped values, this will be an enrichment activity or manual transformation for the successor object to derive the the Work Centre.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||