Purpose
The purpose of this document is to define the conversion approach to create Equipment in S/4 HANA.
In SAP Plant Maintenance (SAP S4/HANA EAM), a piece of equipment is an individual object that is to be maintained independently. Each piece of equipment is managed independently in the system, so that you can:
Manage individual data from a maintenance perspective for the object
Perform individual maintenance tasks for the object
Keep a record of the maintenance tasks performed for the object
Collect and evaluate data over a long period of time for the object
As per Syensqo's design, all maintainable asset will be represented by Equipment, with the exception where the asset is maintained by Syensqo but not owned, in which case the asset will be migrated as a Functional Location. As per SyWay design, EAM Equipment will be standardized.
Conversion Scope
The scope of this document covers the approach for creation of Equipment in S/4HANA following the Equipment Master Data Design Standard.
In Syensqo’s SAP S/4HANA landscape, Equipment is used to define an individual asset or a sub-component of an asset. Each Equipment record represents a maintainable unit, serving as a critical master data for executing maintenance and work management processes. An Equipment is defined based on its construction and a defined Maintenance strategy is followed by to ensure its Reliability and sustainability.
An Equipment is only created when there is a defined Maintenance Strategy defined for it and a criticality derived from Risk Assessment process.
Depending on its installation context, Equipment is categorized by a user status to define its current state in its lifecycle from Planning to Retire. Every piece of Equipment that is Inservice is installed at a relevant superior Asset Functional Location or superior Equipment, ensuring its position within the asset hierarchy is clearly defined.
This structured approach supports efficient maintenance planning, traceability, and lifecycle management of assets across Syensqo’s operations.
Conversion from legacy will adopt a hybrid method: Extraction and DCT for migration.
- Extraction to include all active Equipment
- Data Construct Template to capture -
- Relevant Functional Locations identified for migration as Equipment.
- Relevant Assembly/ Construction Type materials linked to the below objects, as confirmed by the Business, for migration as Equipment.
Maintenance Item (Assembly field)
Maintenance Item (Object List for Material)
Notification (Assembly field)
Work Order (Assembly field)
Work Order (Object List for Material)
Equipment (Construction Type)
Equipment in Syensqo to-be asset structure will be positioned under the Category 'A' (Asset) Functional Location and will comprise of 2 levels.
| Level | Technical Object | Function/ Meaning |
|---|---|---|
| Equipment Level 1 | Equipment | Maintainable Item / Class (Primary maintainable unit) |
| Equipment Level 2 | Equipment | Maintainable Item / Component (sub-equipment) |
Note: Please refer CNV-1003 Function Location for details on the Functional Location Asset Level conversion.
The data from legacy system includes:
- Equipment (EQUI-EQUNR) having Maintenance Plant (EQUI-WERKS) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes')
- Equipment Long Text in Inclusion-EQ Long Text
The data from legacy system excludes:
- Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = Inactive 'INAC'
- Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = Deletion Flag 'DLFL'
- Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = In the warehouse 'ESTO'
- Equipment (EQUI-EQUNR) with System Status (JEST-STAT) = Available 'AVLB'
- Equipment (EQUI-EQUNR) with System Status (JEST-STAT) <> Installed 'INST'
- Equipment (EQUI-EQUNR) with Serial Number (EQUI-SERNR) <> '' (BLANK)
- Equipment (EQUI-EQUNR) part of Exclusion List (EXC-Equipment)
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 | Relevant Equipment will be extracted from PF2 and WP2 | 400,000 | S/4HANA | 400,000 |
DCT | Functional Location to be migrate as Equipment as part of mapping (Functional Location, where New Technical Object = 'EQ' An initial extract of the relevant Functional Locations will be provided in google sheet format to assist business in decision making. | TBD | S/4HANA | TBD |
DCT | Assembly to be created as Equipment as part of Inclusion list Inclusion-A/CT An initial extract of the relevant Assemblies will be provided in google sheet format to assist business in decision making. | TBD | S/4HANA | TBD |
DCT | Equipment for plants which do not have data existing from PF2 and WP2 | TBD | S/4HANA | TBD |
Additional Information
Multi-language Requirement
Equipment description will be made available in English.
Multi language is supported for Equipment. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Equipment.
Document Management
Refer to the KDD085 - Document Management in the SyWay Solution
Note: Documents attached to Equipment will be migrated as part of 9104-EAM Attachments.
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Scope
Target Design
The technical design of the target for this conversion approach.
1. Equipment Master
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | System Key Field |
| EQUI | EQTYP | EQTYP | Equipment Category | CHAR | 1 | Mandatory |
| EQUI | EQART | EQART | Technical Object Type | CHAR | 10 | Mandatory |
| EQUI | BRGEW | BRGEW | Weight | QUAN | 13 | Conditional |
| EQUI | GEWEI | GEWEI | Unit of Weight | UNIT | 3 | Conditional |
| EQUI | INVNR | INVNR | Inventory No | CHAR | 25 | Conditional |
| EQUI | INBDT | INBDT | Start-up date | DATS | 8 | Conditional |
| EQUI | ANSWT | ANSWT | Acquisition Value | NUMC | 13 | Conditional |
| EQUI | WAERS | WAERS | Currency | CUKY | 5 | Conditional |
| EQUI | HERST | HERST | Manufacturer | CHAR | 30 | Conditional |
| EQUI | TYPBZ | TYPBZ | Model Number | CHAR | 20 | Conditional |
| EQUI | SERGE | SERGE | Manufacturer Serial Number | CHAR | 30 | Conditional |
| EQUI | HERLD | HERLD | Country/Region of Manufacture | CHAR | 3 | Conditional |
| EQUI | BAUJJ | BAUJJ | Year of construction | CHAR | 4 | Conditional |
| EQUI | BAUMM | BAUMM | Month of Manufacture | CHAR | 2 | Conditional |
| EQUZ | DATAB | DATAB | Valid-From Date | DATS | 8 | Mandatory |
| EQUZ | IWERK | IWERK | Maintenance Planning Plant | CHAR | 4 | Mandatory |
| EQUZ | INGRP | INGRP | Planner Group | CHAR | 3 | Conditional |
| EQUZ | GEWRK | GEWRK | Main work center | CHAR | 8 | Conditional |
| EQUZ | WERGW | WERGW | Plant associated with main work center | CHAR | 4 | Conditional |
| EQUZ | HEQUI | HEQUI | Superordinate Equipment | CHAR | 18 | Conditional |
| EQUZ | SUBMT | SUBMT | Construction type | CHAR | 40 | Mandatory |
| ILOA | ABCKZ | ABCKZ | ABC Indicator | CHAR | 1 | Mandatory |
| ILOA | TPLNR | TPLNR | Functional Location | CHAR | 30 | Conditional |
| ILOA | SWERK | SWERK | Maintenance Plant | CHAR | 4 | Mandatory |
| ILOA | BEBER | BEBER | Plant Section | CHAR | 3 | Mandatory |
| ILOA | EQFNR | EQFNR | Sort Field | CHAR | 30 | Mandatory |
| ILOA | BUKRS | BUKRS | Company Code | CHAR | 4 | Mandatory |
| ILOA | KOSTL | KOSTL | Cost Center | CHAR | 10 | Mandatory |
| ILOA | KOKRS | KOKRS | Controlling Area | CHAR | 4 | Mandatory |
| ADRC | NAME1 | NAME1 | Name 1 | CHAR | 40 | Conditional |
| ADRC | NAME2 | NAME2 | Name 2 | CHAR | 40 | Conditional |
| ADRC | NAME3 | NAME3 | Name 3 | CHAR | 40 | Conditional |
| ADRC | NAME4 | NAME4 | Name 4 | CHAR | 40 | Conditional |
| ADRC | COUNTRY | COUNTRY | Country/Region Key | CHAR | 3 | Conditional |
2. Equipment Short Text
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Mandatory (Key to link to Equipment) |
| EQKT | SPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| EQKT | PLTXT | PLTXT | Description of Equipment | CHAR | 40 | Mandatory |
Note: Each Equipment must have 1 entry for English language and 1 entry for the language(s) of the country in which each Maintenance Plant assigned is located (French, Italian, Mandarin, Brazilian Portuguese, German or Spanish).
3. Equipment Classification (Header)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| KSSK | KLART | KLART | Class Type | CHAR | 20 | Mandatory |
| KSSK | OBTAB | OBTAB | Name of Database Table for Object | CHAR | 30 | Mandatory |
| KSSK | CLASSNUM | CLASSNUM | Class Name | CHAR | 30 | Mandatory |
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Mandatory (Key to link to Equipment) |
4. Equipment Classification (Characteristics Value Allocation)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| CABN | Characteristic Name | CHAR | 30 | Mandatory | ||
| AUSP | POSNR | POSNR | Item Number | CHAR | 3 | Mandatory |
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Mandatory (Key to link to Equipment) |
| AUSP | ATFLV | ATFLV | Numerical Value - From | NUMC | 16 | Conditional |
| AUSP | ATFLB | ATFLB | Numerical Value - To | NUMC | 16 | Conditional |
| AUSP | DATE_FROM | DATE_FROM | Lower Boundary for Date - Interval | DATS | 8 | Conditional |
| AUSP | DATE_TO | DATE_TO | Upper Boundary for Date - Interval | DATS | 8 | Conditional |
| AUSP | TIME_FROM | TIME_FROM | Lower Boundary for Time - Interval | TIMS | 6 | Conditional |
| AUSP | TIME_TO | TIME_TO | Upper Boundary for Time - Interval | TIMS | 6 | Conditional |
| AUSP | ATFLV | ATFLV | Currency Value - From (Floating Point) | NUMC | 16 | Conditional |
| AUSP | ATFLB | ATFLB | Currency Value - To (Floating Point) | NUMC | 16 | Conditional |
| AUSP | CURRENCY | CURRENCY | Currency Key | CUKY | 5 | Conditional |
| AUSP | ATWRT | ATWRT | Characteristic Value | CHAR | 30 | Conditional |
| KSSK | KLART | KLART | Class Type | CHAR | 20 | Mandatory |
| KSSK | CLASS | CLASS | Class Name | CHAR | 30 | Mandatory |
5. Equipment Partner
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Mandatory (Key to link to Equipment) |
| IHPA | OBTYP | OBTYP | Object Type | CHAR | 3 | Mandatory |
| IHPA | PARVW | PARVW | Partner Function | CHAR | 2 | Mandatory |
| IHPA | PARNR | PARNR | Partner | CHAR | 12 | Mandatory |
6. Equipment User Status
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Mandatory (Key to link to Equipment) |
| JSTO | STSMA | STSMA | Status profile of the Equipment | CHAR | 8 | Mandatory |
JEST | STAT | STAT | Status Number in User Status List | CHAR | 5 | Mandatory |
7. Equipment Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Mandatory (Key to link to Equipment) |
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXH | TDNAME | TDNAME | Name | CHAR | 70 | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXH | TDSPRAS | TDSPRAS | Language Key | LANG | 1 | Mandatory |
8. Equipment Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| EQUI | EQUNR | EQUNR | Equipment Number | CHAR | 18 | Mandatory (Key to link to Equipment) |
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXL | TDNAME | TDNAME | Name | CHAR | 70 | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXL | TDSPRAS | TDSPRAS | Language Key | LANG | 1 | Mandatory |
| STXL | TDFORMAT | TDFORMAT | Tag column | CHAR | 1 | Mandatory |
| STXL | TDLINE | TDLINE | Text Line | CHAR | 72 | Mandatory |
Note:
- Long Text is not mandatory, only load when there is data
- One Long Text Header must have at least 1 Long Text Line
Equipment Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Equipment information follows the Master Data Standard document that is located here.
Data Cleansing
All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.
If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 1002-001 | C1 | Relevant Equipment missing Technical Object Type | Equipment as per Relevancy Criteria with no Technical Object Type Assigned | Plant, Equipment, Equipment Description, Technical Object Type | PF2, WP2 |
| 1002-002 | C1 | Relevant Equipment missing Superior Equipment or Functional Location | Equipment as per Relevancy Criteria not installed either below a Superior Equipment or Functional Location | Plant, Equipment, Equipment Description, Technical Object Type, Superior Equipment, Functional Location | PF2, WP2 |
| 1002-003 | C1 | Relevant Equipment missing Plant Section | Equipment as per Relevancy Criteria with no Plant Section Assigned | Plant, Equipment, Equipment Description, Technical Object Type | PF2, WP2 |
| 1002-004 | C2 | Relevant Equipment maintaining Acquisition Value but missing Currency Key | Equipment as per relevancy criteria where EQUI_ANSWT <> '' (Blank) and EQUI_WAERS = '' (Blank) | Plant, Equipment, Equipment Description, Technical Object Type, Superior Equipment, Functional Location, Acquisition Value | PF2, WP2 |
| 1002-005 | C3 | Info Report : Relevant Equipment Long Text for Cleansing | Equipment as per Relevancy Criteria where Long Text Exist flag is assigned (EQUI-KZLTX) = 'X'. This is for manual review. | Plant, Equipment, Equipment Description, Long Text | PF2, WP2 |
| 1002-006 | C3 | Info Report : Construction Type (CT) assigned to Relevant Equipment which are not part of a BOM (Bill of Material). This report is to support Business to review Legacy Construction Types to be included in Equipment DCT for migration. | Construction Type (EQUZ-SUBMT) maintained on relevant Equipment which are/ are not part of a BOM (MAST-MATNR). | Plant, Equipment, Equipment Description, CT, CT description, Material Type, Material Type Description | PF2, WP2 |
| 1002-007 | C3 | Info Report : Assemblies assigned to Relevant Maintenance Items which are not part of a BOM (Bill of Material). This report is to support Business to review Legacy Assemblies to be included in Equipment DCT for migration. | Assembly (MPOS-BAUTL) maintained on relevant Maintenance Items (MPOS-WAPOS) which are/ are not part of a BOM (MAST-MATNR) | Plant, Maintenance Item, Assembly, Assembly description, Material Type, Material Type Description | PF2, WP2 |
| 1002-008 | C3 | Info Report : Assemblies listed on Relevant Maintenance Item Object list which are not part of a BOM (Bill of Material). This report is to support Business to review Legacy Assemblies to be included in Equipment DCT for migration. | Assembly (OBJK-BAUTL) maintained on relevant Maintenance Items (MPOS-WAPOS) which are/ are not part of a BOM (MAST-MATNR) | Plant, Maintenance Item, Assembly, Assembly description, Material Type, Material Type Description | PF2, WP2 |
| 1002-009 | C3 | Info Report : Assemblies listed on Relevant Work Orders which are not part of a BOM (Bill of Material). This report is to support Business to review Legacy Assemblies to be included in Equipment DCT for migration. | Assembly (AFIH-BAUTL) maintained on relevant Work Order (AUFK-AUFNR) which are/ are not part of a BOM (MAST-MATNR) | Plant, Work Order, Assembly, Assembly description, Material Type, Material Type Description | PF2, WP2 |
| 1002-010 | C3 | Info Report : Assemblies listed on Relevant Work Order Object list which are not part of a BOM (Bill of Material). This report is to support Business to review Legacy Assemblies to be included in Equipment DCT for migration. | Assembly (OBJK-BAUTL) maintained on relevant Work Order (AUFK-AUFNR) which are/ are not part of a BOM (MAST-MATNR) | Plant, Work Order, Assembly, Assembly description, Material Type, Material Type Description | PF2, WP2 |
| 1002-011 | C3 | Info Report : Assemblies listed on Relevant Notifications which are not part of a BOM (Bill of Material). This report is to support Business to review Legacy Assemblies to be included in Equipment DCT for migration. | Assembly (QMIH-BAUTL) maintained on relevant Notification (QMEL-QMNUM) which are/ are not part of a BOM (MAST-MATNR) | Plant, Notification, Assembly description, Material Type, Material Type Description | PF2, WP2 |
Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)
Conversion Process
The high-level process is represented by the diagram below:
1. Source = PF2/WP2:
Collection will be done manually in the Data Collection Template for the following scenarios:
Equipment to be created where the source data is set up as Functional Locations
Equipment to be created where the source data is set up as Assemblies
- For sites not on SAP-PF2 or WP2 systems
Data Privacy and Sensitivity
Not ApplicableExtraction
Extract data from a source into Advanced Data Migration and Management (ADMM). There are 2 possibilities:
- The data exists. ADMM connects to the source and loads the data into ADMM. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ADMM; 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 ADMM. This is to be conducted using DCT (Data Collection Template) in ADMM
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 1 | Extract data from source system based on relevancy rule | SyWay Data Team |
2 | Google 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 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 Equipment 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.
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. Equipment Master Data Construction Rules
| Field Name | Field Description | Rule |
|---|---|---|
| zLegacyEQUNR | Legacy Equipment Number | Mandatory Staging identifier used to uniquely define an Equipment |
| EQART | Technical Object Type | Mandatory Allowed values from T370K to be populated |
| BRGEW | Weight | Conditional Populate if information exists |
| GEWEI | Unit of Weight | Conditional Populate unit value if BRGEW (Weight) has been maintained. Allowed values from T006 to be populated |
| INVNR | Inventory No | Conditional Populate Critical Material representing the relevant procured Capital Spare (Fixed Asset) for the Equipment Criteria for Assigning Critical Materials as the Inventory Number -
|
| ANSWT | Acquisition Value | Conditional Populate the Fixed Asset value if Inventory Number has been maintained. |
| WAERS | Currency | Conditional Populate only if 'Acquisition Value' field has been populated Allowed values from TCURC to be populated. |
| HERST | Manufacturer | PF2/WP2 data enrichment: Not used For new data construction: Conditional Populate if information exists |
| TYPBZ | Model Number | PF2/WP2 data enrichment: Not used For new data construction: Conditional Populate if information exists |
| SERGE | Manufacturer Serial Number | PF2/WP2 data enrichment: Not used For new data construction: Conditional Populate if information exists |
| HERLD | Country/Region of Manufacture | PF2/WP2 data enrichment: Not used For new data construction: Conditional Allowed values from T005 to be populated. |
| BAUJJ | Year of construction | PF2/WP2 data enrichment: Not used For new data construction: Conditional Populate if information exists |
| BAUMM | Month of Manufacture | PF2/WP2 data enrichment: Not used For new data construction: Conditional Populate if information exists |
| SWERK | Maintenance Plant | PF2/WP2 data enrichment: Not used For new data construction: Mandatory Populate values from Value Mapping - Plant (where Maintenance Plant = Yes) |
| INGRP | Planner Group | Mandatory Must Populate value if Equipment is in Installed Status. Allowed values from T024I (where IWERK = Planning Plant) to be populated |
| GEWRK | Main work center | Conditional Must Populate value if Equipment is in Installed Status. Allowed values from Work Centre DCT to be populated. |
| HEQUI | Superordinate Equipment | Conditional Populate if Equipment is a Sub-Equipment. Plant section of the Superior Equipment should be identical the the Equipment to be installed. |
| SUBMT | Construction type | Mandatory Populate value from Assembly DCT. Assigned Construction Type should have a TOT Characteristic value maintained which matches the 'Object Type' assigned on the Equipment and 'SubAssembly' Characteristic = 'No' |
| TPLNR | Functional Location | Conditional Populate Category 'A' Functional Location if Equipment installed under Functional Location. Assigned Functional Location should have a TOT value identical to the Equipment and the Plant Section of the Functional Location should be identical to the one assigned on the Equipment Allowed Category 'A' Functional Location values from mapping (Functional Location, where New Technical Object = 'FL') to be used. |
| EQFNR | Sort Field | Mandatory The Sort Field is used to store the Plant Tag ID, representing the physical identifier attached to an asset in the field. Ensure that it does not include any of below characters: ; Semi-colon |
| KOSTL | Cost Center | Mandatory Must Populate value if Equipment is in Installed Status Allowed values from R2R Cost Centre Value Mapping. |
| NAME1 | Name 1 | Conditional Populate NAME1-4 fields with the Name and Location of the Asset |
| NAME2 | Name 2 | Conditional Populate NAME1-4 fields with the Name and Location of the Asset |
| NAME3 | Name 3 | Conditional Populate NAME1-4 fields with the Name and Location of the Asset |
| NAME4 | Name 4 | Conditional Populate NAME1-4 fields with the Name and Location of the Asset |
| EQKTX_EN | Description of Equipment (English) | Mandatory Guide for Description: A = Technical Object Type Description (in English language) Equipment Description = A+B+C All Letters must be in Capital letters/ Uppercase. Cannot have duplicate records based on corresponding language text (2 Equipment cannot have the same English language key texts) Ensure that it does not include any of below characters: ; Semi-colon |
| SPRAS_LC | Language Key_Local | Conditional User to populate Language Key based language of the Country where the Maintenance Plant exists. Allowed values: |
| EQKTX_LC | Description of Equipment (Local Language) | Conditional Guide for Description: A = Technical Object Type Description (in Local Language of Plant) Equipment Description = A+B+C All Letters must be in Capital letters/ Uppercase. Cannot have duplicate records based on corresponding language text (2 Equipment cannot have the same Local language key texts) Ensure that it does not include any of below characters: ; Semi-colon |
| zLegacyPARNR_Z1 | Partner (Asset Owner) | Conditional Populate 'Z1' (Asset Owner) Vendor Business Partner as per below rule. Rule - For Assets that are rented from specific vendors or maintained by third-party service providers, external Vendors are to be populated |
| zLegacyPARNR_Z2 | Partner (Asset Maintainer) | Conditional Populate 'Z2' (Asset Maintainer) Vendor Business Partner as per below rule. Rule - For Assets that are Owned by Syensqo and Maintained by Syensqo Inter Company Vendor are to be populated. For Assets that are rented from specific vendors or maintained by third-party service providers, external Vendors are to be populated |
| zLegacyPARNR_Z3 | Partner (Vendor Contact) | Conditional Populate 'Z3' (Vendor Contact) Contact Person Business Partner of the External Vendor. |
| STAT_N1 | Sequential Status in User Status Profile | Conditional Populate from allowed values: |
| STAT_X1 | Non-Sequential Status in the User Status Profile - EXHZ (Extremely Hazardous) | Conditional Populate 'EXHZ' (Extremely Hazardous) status if applicable. |
| STAT_X2 | Non-Sequential Status in the User Status Profile - MTNA (Maintenance Not Allowed) | Conditional Populate 'MTNA' (Maintenance Not Allowed) status if applicable. |
2. Equipment Classification Data Construction Rules
| Data Element | Field Description | Rule |
|---|---|---|
| zLegacyEQUNR | Equipment Number | Mandatory Key to link to Equipment Should exist in Equipment Master DCT Rules |
| CLASS | Class Name | Mandatory
Class other than 'EAM_9999' must have naming convention = EAM_TOT (Tech Object Type) of the Equipment |
| ATNAM | Characteristic Name | Mandatory User to populate Characteristic assigned to the Class 'EAM_9999' and other mapped legacy classes as per the Class DCT |
| ATWRT | Characteristic Value | Conditional.
Note for DATE, TIME, NUM and CURR formats:
|
| POSNR | Item Number | Conditional Sequential number to be maintained if multiple values are being recorded for the same Characteristic |
3. Equipment Long Text Data Construction Rules
| Data Element | Field Description | Rule |
|---|---|---|
| zLegacyEQUNR | Legacy Equipment Number | Mandatory Key to link to Equipment |
| TDLINE_EN | Text Line (English) | Mandatory User to populate Free Text in English Language as applicable. All Letters must be in Capital letters/ Uppercase. |
| TDSPRAS_LC | Language Key_Local | Conditional User to populate Language Key based language of the Country where the Maintenance Plant exists. Allowed values: |
| TDLINE_LC | Text Line (Local Language) | Conditional User to populate Free Text in language of the country in which each plant is located (French, Italian, Mandarin, Brazilian Portuguese, German or Spanish). All Letters must be in Capital letters/ Uppercase. |
4. Inclusion-EQ Long Text Data Construction Rules
| Data Element | Field Description | Rule |
|---|---|---|
| zLegacyEQUNR | Legacy Equipment Number | Mandatory Populate relevant Legacy Equipment Number for which Long Text has to be migrated. |
| zLegacyWERKS | Legacy Plant | Mandatory |
| zLegacySPRAS | Legacy Language Key | Mandatory. Allowed values: |
Note: Only Long Texts that are added into this list will be migrated.
Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)
Extraction Dependencies
List the steps that need to occur before extraction can commence
| 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 Syniti Migrate to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Advanced Data Migration and Management (ADMM)
- 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 – Equipment | 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. Equipment Master Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | EQUI | EQUNR | Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Staging Equipment Id as per Value Mapping: Equipment (Staging) |
| 2 | - | - | - | - | S/4 Hana | EQUI | EQTYP | Equipment Category | Default to 'M' |
| 3 | PF2, WP2 | EQUI | EQART | Technical Object Type | S/4 Hana | EQUI | EQART | Technical Object Type | Value mapping : Technical Object Type Overwrite with DCT if provided (as part of enrichment) |
| 4 | PF2, WP2 | EQUI | BRGEW | Weight | S/4 Hana | EQUI | BRGEW | Weight | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 5 | PF2, WP2 | EQUI | GEWEI | Unit of Weight | S/4 Hana | EQUI | GEWEI | Unit of Weight | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 6 | DCT | EQUI | INVNR | Inventory No | S/4 Hana | EQUI | INVNR | Inventory No | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 7 | - | - | - | - | S/4 Hana | EQUI | INBDT | Start-Up Date | If derived Target User Status for Equipment from Equipment User Status (STAT) Transformation Rules (ECC) is either of the below: Else leave blank |
| 8 | PF2, WP2 | EQUI | ANSWT | Acquisition Value | S/4 Hana | EQUI | ANSWT | Acquisition Value | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 9 | PF2, WP2 | EQUI | WAERS | Currency | S/4 Hana | EQUI | WAERS | Currency | Direct Mapping |
| 10 | PF2, WP2 | EQUI | HERST | Manufacturer | S/4 Hana | EQUI | HERST | Manufacturer | Direct Mapping |
| 11 | PF2, WP2 | EQUI | TYPBZ | Model Number | S/4 Hana | EQUI | TYPBZ | Model Number | Direct Mapping |
| 12 | PF2, WP2 | EQUI | SERGE | Manufacturer Serial Number | S/4 Hana | EQUI | SERGE | Manufacturer Serial Number | Direct Mapping |
| 13 | PF2, WP2 | EQUI | HERLD | Country/Region of Manufacture | S/4 Hana | EQUI | HERLD | Country/Region of Manufacture | Direct Mapping |
| 14 | PF2, WP2 | EQUI | BAUJJ | Year of construction | S/4 Hana | EQUI | BAUJJ | Year of construction | Direct Mapping |
| 15 | PF2, WP2 | EQUI | BAUMM | Month of Manufacture | S/4 Hana | EQUI | BAUMM | Month of Manufacture | Direct Mapping |
| 16 | - | - | - | - | S/4 Hana | EQUZ | DATAB | Valid From Date | Assign the date as per Value mapping : OTH_Migration_Date Relevant Values A2D (where Object ID "1002" and Field Name = "EQUI-DATAB". |
| 17 | - | - | - | - | S/4 Hana | EQUZ | IWERK | Maintenance Planning Plant | Copy value populated for Target Maintenance Plant (SWERK) |
| 18 | PF2, WP2 | EQUZ | INGRP | Planner Group | S/4 Hana | EQUZ | INGRP | Planner Group | Value mapping : Maintenance Planner Group Overwrite with DCT if provided (as part of enrichment) |
| 19 | PF2, WP2 | EQUZ | GEWRK | Main work center | S/4 Hana | EQUZ | GEWRK | Main work center | Value mapping : Work Center A2D Overwrite with DCT if provided (as part of enrichment) |
| 20 | - | - | - | - | S/4 Hana | EQUZ | WERGW | Plant associated with main work center | Copy value populated for Target Maintenance Plant (SWERK) |
| 21 | PF2, WP2 | EQUZ | HEQUI | Superordinate Equipment | S/4 Hana | EQUZ | HEQUI | Superordinate Equipment | Staging Equipment Id as per Value Mapping: Equipment (Staging) Overwrite with DCT if provided (as part of enrichment) |
| 22 | DCT | EQUZ | SUBMT | Construction type | S/4 Hana | EQUZ | SUBMT | Construction type | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 23 | PF2, WP2 | ILOA | ABCKZ | ABC Indicator | S/4 Hana | ILOA | ABCKZ | ABC Indicator | Derive the Indicator based on below logic -
|
| 24 | PF2, WP2 | ILOA | TPLNR | Functional Location | S/4 Hana | ILOA | TPLNR | Functional Location | Value Mapping: Functional Location Overwrite with DCT if provided (as part of enrichment) |
| 25 | PF2, WP2 | ILOA | SWERK | Maintenance Plant | S/4 Hana | ILOA | SWERK | Maintenance Plant | Value Mapping: Plant (Maintenance Plant = Yes) |
| 26 | - | - | - | - | S/4 Hana | ILOA | BEBER | Plant Section | Copy the Plant Section value assigned to the Target Superordinate Equipment (HEQUI) if populated else copy the Plant Section value assigned to the populated Target Functional Location (TPLNR) |
| 27 | DCT | ILOA | EQFNR | Sort Field | S/4 Hana | ILOA | EQFNR | Sort Field | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 28 | PF2, WP2 | ILOA | BUKRS | Company Code | S/4 Hana | ILOA | BUKRS | Company Code | Derive the Company code from table 'T001K' where Target Maintenance Plant( SWERK) = T001K_BWKEY |
| 29 | PF2, WP2 | ILOA | KOSTL | Cost Center | S/4 Hana | ILOA | KOSTL | Cost Center | Overwrite with DCT if provided (as part of enrichment) Value Mapping : Cost Center |
| 30 | - | - | - | - | S/4 Hana | ILOA | KOKRS | Controlling Area | Default to 'CO01' (SYSQ Controlling Area) |
| 31 | PF2, WP2 | ADRC | NAME1 | Name 1 | S/4 Hana | ADRC | NAME1 | Name 1 | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 32 | PF2, WP2 | ADRC | NAME2 | Name 2 | S/4 Hana | ADRC | NAME2 | Name 2 | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 33 | PF2, WP2 | ADRC | NAME3 | Name 3 | S/4 Hana | ADRC | NAME3 | Name 3 | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 34 | PF2, WP2 | ADRC | NAME4 | Name 4 | S/4 Hana | ADRC | NAME4 | Name 4 | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
| 35 | PF2, WP2 | ADRC | COUNTRY | Country/Region Key | S/4 Hana | ADRC | COUNTRY | Country/Region Key | Derive Country/ Region from Table T001W where Target Maintenance Plant( SWERK) = T001K_BWKEY |
2. Equipment Master Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | EQTYP | Equipment Category | S/4 Hana | EQUI | EQTYP | Equipment Category | Default to 'M' |
| 3 | DCT | EQUI | EQART | Technical Object Type | S/4 Hana | EQUI | EQART | Technical Object Type | Direct Mapping |
| 4 | DCT | EQUI | BRGEW | Weight | S/4 Hana | EQUI | BRGEW | Weight | Direct Mapping |
| 5 | DCT | EQUI | GEWEI | Unit of Weight | S/4 Hana | EQUI | GEWEI | Unit of Weight | Direct Mapping |
| 6 | DCT | EQUI | INVNR | Inventory No | S/4 Hana | EQUI | INVNR | Inventory No | Direct Mapping |
| 7 | - | - | - | - | S/4 Hana | EQUI | INBDT | Start-Up Date | If derived Target User Status for Equipment from Equipment User Status (STAT) Transformation Rules (ECC) is either of the below: Else leave blank |
| 8 | DCT | EQUI | ANSWT | Acquisition Value | S/4 Hana | EQUI | ANSWT | Acquisition Value | Direct Mapping |
| 9 | DCT | EQUI | WAERS | Currency | S/4 Hana | EQUI | WAERS | Currency | Direct Mapping |
| 10 | DCT | EQUI | HERST | Manufacturer | S/4 Hana | EQUI | HERST | Manufacturer | Direct Mapping |
| 11 | DCT | EQUI | TYPBZ | Model Number | S/4 Hana | EQUI | TYPBZ | Model Number | Direct Mapping |
| 12 | DCT | EQUI | SERGE | Manufacturer Serial Number | S/4 Hana | EQUI | SERGE | Manufacturer Serial Number | Direct Mapping |
| 13 | DCT | EQUI | HERLD | Country/Region of Manufacture | S/4 Hana | EQUI | HERLD | Country/Region of Manufacture | Direct Mapping |
| 14 | DCT | EQUI | BAUJJ | Year of construction | S/4 Hana | EQUI | BAUJJ | Year of construction | Direct Mapping |
| 15 | DCT | EQUI | BAUMM | Month of Manufacture | S/4 Hana | EQUI | BAUMM | Month of Manufacture | Direct Mapping |
| 16 | - | - | - | - | S/4 Hana | EQUZ | DATAB | Valid From Date | Assign the date as per Value mapping : OTH_Migration_Date Relevant Values A2D (where Object ID "1002" and Field Name = "EQUI-DATAB". |
| 17 | - | - | - | - | S/4 Hana | EQUZ | IWERK | Maintenance Planning Plant | Copy value populated for Target Maintenance Plant (SWERK) |
| 18 | DCT | EQUZ | INGRP | Planner Group | S/4 Hana | EQUZ | INGRP | Planner Group | Direct Mapping |
| 19 | DCT | EQUZ | GEWRK | Main work center | S/4 Hana | EQUZ | GEWRK | Main work center | Direct Mapping |
| 20 | - | - | - | - | S/4 Hana | EQUZ | WERGW | Plant associated with main work center | Copy value populated for Target Maintenance Plant (SWERK) |
| 21 | DCT | EQUZ | HEQUI | Superordinate Equipment | S/4 Hana | EQUZ | HEQUI | Superordinate Equipment | Direct Mapping |
| 22 | DCT | EQUZ | SUBMT | Construction type | S/4 Hana | EQUZ | SUBMT | Construction type | Direct Mapping |
| 23 | - | - | - | - | S/4 Hana | ILOA | ABCKZ | ABC Indicator | Derive the Indicator based on below logic -
|
| 24 | DCT | ILOA | TPLNR | Functional Location | S/4 Hana | ILOA | TPLNR | Functional Location | Direct Mapping |
| 25 | DCT | ILOA | SWERK | Maintenance Plant | S/4 Hana | ILOA | SWERK | Maintenance Plant | Direct Mapping |
| 26 | - | - | - | - | S/4 Hana | ILOA | BEBER | Plant Section | Copy the Plant Section value assigned to the Target Superordinate Equipment (HEQUI) if populated else copy the Plant Section value assigned to the populated Target Functional Location (TPLNR) |
| 27 | DCT | ILOA | EQFNR | Sort Field | S/4 Hana | ILOA | EQFNR | Sort Field | Direct Mapping |
| 28 | - | - | - | - | S/4 Hana | ILOA | BUKRS | Company Code | Derive the Company code from table 'T001K' where Target Maintenance Plant( SWERK) = T001K_BWKEY |
| 29 | DCT | ILOA | zLegacyKOSTL | Cost Center | S/4 Hana | ILOA | KOSTL | Cost Center | Value mapping : Cost Center |
| 30 | - | - | - | - | S/4 Hana | ILOA | KOKRS | Controlling Area | Default to 'CO01' (SYSQ Controlling Area) |
| 31 | DCT | ADRC | NAME1 | Name 1 | S/4 Hana | ADRC | NAME1 | Name 1 | Direct Mapping |
| 32 | DCT | ADRC | NAME2 | Name 2 | S/4 Hana | ADRC | NAME2 | Name 2 | Direct Mapping |
| 33 | DCT | ADRC | NAME3 | Name 3 | S/4 Hana | ADRC | NAME3 | Name 3 | Direct Mapping |
| 34 | DCT | ADRC | NAME4 | Name 4 | S/4 Hana | ADRC | NAME4 | Name 4 | Direct Mapping |
| 35 | DCT | ADRC | COUNTRY | Country/Region Key | S/4 Hana | ADRC | COUNTRY | Country/Region Key | Derive Country/ Region from Table T001W where Target Maintenance Plant( SWERK) = T001K_BWKEY |
3. Equipment Short Text Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | EQKT | EQUNR | Equipment Number | S/4 Hana | EQKT | EQUNR | Equipment Number | Staging Equipment Id as per Value Mapping: Equipment (Staging) |
| 2 | PF2, WP2 | EQKT | SPRAS | Language Key | S/4 Hana | EQKT | SPRAS | Language Key | Direct Mapping Overwrite with DCT if provided (as part of enrichment) as below
|
| 3 | PF2, WP2 | EQKT | EQKTX | Description of Equipment | S/4 Hana | EQKT | EQKTX | Description of Equipment | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
4. Equipment Short Text Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQKT | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQKT | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | EQKT | SPRAS | Language Key | Default to 'E' |
| 3 | DCT | EQKT | EQKTX_EN | Description of Equipment (English) | S/4 Hana | EQKT | EQKTX | Description of Equipment | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQKT | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQKT | EQUNR | Equipment Number | Direct Mapping |
| 2 | DCT | EQKT | SPRAS_LC | Language Key (Local Language of Plant) | S/4 Hana | EQKT | SPRAS | Language Key | Direct Mapping |
| 3 | DCT | EQKT | EQKTX_LC | Description of Equipment (Local Language of Plant) | S/4 Hana | EQKT | EQKTX | Description of Equipment | Direct Mapping Overwrite with DCT if provided (as part of enrichment) |
5. Equipment Classification Transformation Rule (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | EQUI | EQUNR | Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Staging Equipment Id as per Value Mapping: Equipment (Staging) |
| 2 | - | - | - | - | S/4 Hana | KSSK | KLART | Class Type | Default to '002' |
| 3 | - | - | - | - | S/4 Hana | INOB | OBTAB | Name of Database Table for Object | Default to 'EQUI' |
| 4 | PF2, WP2 | KSSK | CLASS | Class Name | S/4 Hana | KSSK | CLASS | Class Name | Value mapping : Class A2D |
| 5 | PF2, WP2 | CABN | ATNAM | Characteristic Name | S/4 Hana | AUSP | ATNAM | Characteristic Name | Derive the Target Value as below: Step1- Use Value mapping: Characteristic A2D (Staging) to get the Staging Characteristic; Step2 - Use Value mapping: Characteristic A2D to get the Target Characteristic |
| 6 | PF2, WP2 | AUSP | POSNR | Item Number | S/4 Hana | AUSP | POSNR | Item Number | Direct Mapping |
| 7 | PF2, WP2 | AUSP | ATFLV | Numerical Value - From | S/4 Hana | AUSP | ATFLV | Numerical Value - From (Floating Point) | Convert existing Legacy value to Float |
| 8 | PF2, WP2 | AUSP | ATFLB | Numerical Value - To | S/4 Hana | AUSP | ATFLB | Numerical Value - To (Floating Point) | Convert existing Legacy value to Float |
| 9 | PF2, WP2 | AUSP | ATFLV | Date Interval - From | S/4 Hana | AUSP | DATE_FROM | Lower Boundary for Date - Interval | Convert existing Legacy value to Float |
| 10 | PF2, WP2 | AUSP | ATFLB | Date Interval - To | S/4 Hana | AUSP | DATE_TO | Upper Boundary for Date - Interval | Convert existing Legacy value to Float |
| 11 | PF2, WP2 | AUSP | ATFLV | Time Interval - From | S/4 Hana | AUSP | TIME_FROM | Lower Boundary for Time - Interval | Convert existing Legacy value to Float |
| 12 | PF2, WP2 | AUSP | ATFLB | Time Interval - To | S/4 Hana | AUSP | TIME_TO | Upper Boundary for Time - Interval | Convert existing Legacy value to Float |
| 13 | PF2, WP2 | AUSP | ATFLV | Currency Value - From | S/4 Hana | AUSP | ATFLV | Currency Value - From (Floating Point) | Convert existing Legacy value to Float |
| 14 | PF2, WP2 | AUSP | ATFLB | Currency Value - To | S/4 Hana | AUSP | ATFLB | Currency Value - To (Floating Point) | Convert existing Legacy value to Float |
| 15 | PF2, WP2 | AUSP | ATWRT | Characteristic Value | S/4 Hana | AUSP | ATWRT | Characteristic Value | Direct Mapping |
6. Equipment Classification Transformation Rule (DCT)
Only get the records where Characteristics with Data Type = CHAR
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | KSSK | KLART | Class Type | Default to '002' |
| 3 | - | - | - | - | S/4 Hana | KSSK | OBTAB | Name of Database Table for Object | Default to 'EQUI' |
| 4 | DCT | KSSK | CLASS | Class Name | S/4 Hana | KSSK | CLASS | Class Name | Direct Mapping |
| 5 | DCT | AUSP | ATNAM | Characteristic Name | S/4 Hana | AUSP | ATNAM | Characteristic Name | Direct Mapping |
| 6 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | ATWRT | Characteristic Value | Direct Mapping |
| 7 | DCT | AUSP | POSNR | Item Number | S/4 Hana | AUSP | POSNR | Item Number | Direct Mapping |
Only get the records where Characteristics with Data Type = CURR
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | KSSK | KLART | Class Type | Default to '002' |
| 3 | - | - | - | - | S/4 Hana | KSSK | OBTAB | Name of Database Table for Object | Default to 'EQUI' |
| 4 | DCT | KSSK | CLASS | Class Name | S/4 Hana | KSSK | CLASS | Class Name | Direct Mapping |
| 5 | DCT | AUSP | ATNAM | Characteristic Name | S/4 Hana | AUSP | ATNAM | Characteristic Name | Direct Mapping |
| 6 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | ATFLV | Characteristic Value (From) | If range: values concatenated using " - ", derive the value before " - ". Otherwise, direct mapping. |
| 7 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | ATFLB | Characteristic Value (To) | If range: values concatenated using " - ", derive the value after " - ". Otherwise, direct mapping. |
| 8 | DCT | AUSP | CURRENCY | Currency Key | S/4 Hana | AUSP | CURRENCY | Currency Key | Derive from Currency Key of the Characteristics |
| 9 | DCT | AUSP | POSNR | Item Number | S/4 Hana | AUSP | POSNR | Item Number | Direct Mapping |
Only get the records where Characteristics with Data Type = DATE
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | KSSK | KLART | Class Type | Default to '002' |
| 3 | - | - | - | - | S/4 Hana | KSSK | OBTAB | Name of Database Table for Object | Default to 'EQUI' |
| 4 | DCT | KSSK | CLASS | Class Name | S/4 Hana | KSSK | CLASS | Class Name | Direct Mapping |
| 5 | DCT | AUSP | ATNAM | Characteristic Name | S/4 Hana | AUSP | ATNAM | Characteristic Name | Direct Mapping |
| 6 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | DATE_FROM | Characteristic Value (From) | If range: values concatenated using " - ", derive the value before " - ". Otherwise, direct mapping. |
| 7 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | DATE_TO | Characteristic Value (To) | If range: values concatenated using " - ", derive the value after " - ". Otherwise, direct mapping. |
| 8 | DCT | AUSP | POSNR | Item Number | S/4 Hana | AUSP | POSNR | Item Number | Direct Mapping |
Only get the records where Characteristics with Data Type = NUM
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | KSSK | KLART | Class Type | Default to '002' |
| 3 | - | - | - | - | S/4 Hana | KSSK | OBTAB | Name of Database Table for Object | Default to 'EQUI' |
| 4 | DCT | KSSK | CLASS | Class Name | S/4 Hana | KSSK | CLASS | Class Name | Direct Mapping |
| 5 | DCT | AUSP | ATNAM | Characteristic Name | S/4 Hana | AUSP | ATNAM | Characteristic Name | Direct Mapping |
| 6 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | ATFLV | Characteristic Value (From) | If range: values concatenated using " - ", derive the value before " - ". Otherwise, direct mapping. |
| 7 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | ATFLB | Characteristic Value (To) | If range: values concatenated using " - ", derive the value after " - ". Otherwise, leave blank. |
| 8 | DCT | AUSP | POSNR | Item Number | S/4 Hana | AUSP | POSNR | Item Number | Direct Mapping |
Only get the records where Characteristics with Data Type = TIME
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | KSSK | KLART | Class Type | Default to '002' |
| 3 | - | - | - | - | S/4 Hana | KSSK | OBTAB | Name of Database Table for Object | Default to 'EQUI' |
| 4 | DCT | KSSK | CLASS | Class Name | S/4 Hana | KSSK | CLASS | Class Name | Direct Mapping |
| 5 | DCT | AUSP | ATNAM | Characteristic Name | S/4 Hana | AUSP | ATNAM | Characteristic Name | Direct Mapping |
| 6 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | TIME_FROM | Characteristic Value (From) | If range: values concatenated using " - ", derive the value before " - ". Otherwise, direct mapping. |
| 7 | DCT | AUSP | ATWRT | Characteristic Value | S/4 Hana | CAWN | TIME_TO | Characteristic Value (To) | If range: values concatenated using " - ", derive the value after " - ". Otherwise, direct mapping. |
| 8 | DCT | AUSP | POSNR | Item Number | S/4 Hana | AUSP | POSNR | Item Number | Direct Mapping |
7. Equipment Partner Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | IHPA | OBTYP | Object Type | Default to 'IEQ' |
| 3 | - | - | - | - | S/4 Hana | IHPA | PARVW | Partner Function | Default to 'Z1' (Asset Owner) |
| 4 | DCT | IHPA | zLegacyPARNR_Z1 | Partner (Asset Owner) | S/4 Hana | IHPA | PARNR | Partner | Overwrite with DCT if provided (as part of enrichment) Value mapping : Vendor Number |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | IHPA | OBTYP | Object Type | Default to 'IEQ' |
| 3 | - | - | - | - | S/4 Hana | IHPA | PARVW | Partner Function | Default to 'Z2' (Asset Maintainer) |
| 4 | DCT | IHPA | zLegacyPARNR_Z2 | Partner (Asset Maintainer) | S/4 Hana | IHPA | PARNR | Partner | Overwrite with DCT if provided (as part of enrichment) Value mapping : Vendor Number |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | IHPA | OBTYP | Object Type | Default to 'IEQ' |
| 3 | - | - | - | - | S/4 Hana | IHPA | PARVW | Partner Function | Default to 'Z3' (Vendor Contact) |
| 4 | DCT | IHPA | zLegacyPARNR_Z2 | Partner (Vendor Contact) | S/4 Hana | IHPA | PARNR | Partner | Overwrite with DCT if provided (as part of enrichment) Value mapping : Contact Person |
8. Equipment User Status Transformation Rules (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | PF2, WP2 | EQUI | EQUNR | Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Staging Equipment Id as per Value Mapping: Equipment (Staging) |
| 2 | - | - | - | - | S/4 Hana | JSTO | STSMA | Status profile of the Equipment | Default to 'ZEAMEQ01' |
| 3 | PF2, WP2 | JEST | STAT | Status Number in User Status List | S/4 Hana | JEST | STAT | Status Number in User Status List | Value Mapping : User Status Equipment Overwrite with DCT if provided (as part of enrichment) |
Note: Filter on TJ30T for Status Profiles with ESTAT starting with E*.
9. Equipment User Status Transformation Rules (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | JSTO | STSMA | Status profile of the Equipment | Default to 'ZEAMEQ01' |
| 3 | DCT | JEST | STAT_N1 | Sequential Status in the User Status Profile | S/4 Hana | JEST | STAT | Status Number in User Status List | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping Staging Equipment Id as per Value Mapping: Equipment (Staging) |
| 2 | - | - | - | - | S/4 Hana | JSTO | STSMA | Status profile of the Equipment | Default to 'ZEAMEQ01' |
| 3 | DCT | JEST | STAT_X1 | Non-Sequential Status in the User Status Profile - EXHZ (Extremely Hazardous) | S/4 Hana | JEST | STAT | Status Number in User Status List | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | EQUI | EQUNR | Equipment Number | Direct Mapping Staging Equipment Id as per Value Mapping: Equipment (Staging) |
| 2 | - | - | - | - | S/4 Hana | JSTO | STSMA | Status profile of the Equipment | Default to 'ZEAMEQ01' |
| 3 | DCT | JEST | STAT_X2 | Non-Sequential Status in the User Status Profile - MTNA (Maintenance Not Allowed) | S/4 Hana | JEST | STAT | Status Number in User Status List | Direct Mapping |
10. Equipment Long Text Header (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 Hana | STXH | TDOBJECT | Texts: application object | Default to 'EQUI' |
| 2 | PF2, WP2 | EQUI | EQUNR | Equipment Number | S/4 Hana | STXH | TDNAME | Name | Concatenate '000000000' + Target Equipment Number Target Equipment to be derived as follows: Step1- Use Value mapping: Equipment (Staging) to get the Staging Equipment Id; Step2 - Use Value mapping: Equipment to get the Target Equipment (New Equipment Number |
| 3 | - | - | - | - | S/4 Hana | STXH | TDID | Text ID | Default to 'LTXT' |
| 4 | PF2, WP2 | STXH | TDSPRAS | Language Key | S/4 Hana | STXH | TDSPRAS | Language Key | Direct Mapping |
Note: Only the records marked as Cleansed in Inclusion-EQ Long Text will be migrated
11. Equipment Long Text Header (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 Hana | STXH | TDOBJECT | Texts: application object | Default to 'EQUI' |
| 2 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | STXH | TDNAME | Name | Concatenate '000000000' + Target Equipment Number Target Equipment to be derived as follows: Step1- Use Value mapping: Equipment (Staging) to get the Staging Equipment Id; Step2 - Use Value mapping: Equipment to get the Target Equipment (New Equipment Number |
| 3 | - | - | - | - | S/4 Hana | STXH | TDID | Text ID | Default to 'LTXT' |
| 4 | DCT | STXH | TDSPRAS | Language Key | S/4 Hana | STXH | TDSPRAS | Language Key | Default to 'E' |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 Hana | STXH | TDOBJECT | Texts: application object | Default to 'EQUI' |
| 2 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | STXH | TDNAME | Name | Concatenate '000000000' + Target Equipment Number Target Equipment to be derived as follows: Step1- Use Value mapping: Equipment (Staging) to get the Staging Equipment Id; Step2 - Use Value mapping: Equipment to get the Target Equipment (New Equipment Number |
| 3 | - | - | - | - | S/4 Hana | STXH | TDID | Text ID | Default to 'LTXT' |
| 4 | DCT | STXH | TDSPRAS_LC | Language Key | S/4 Hana | STXH | TDSPRAS | Language Key | Direct Mapping |
12. Equipment Long Text Line (ECC)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 Hana | STXL | TDOBJECT | Texts: application object | Default to 'EQUI' |
| 2 | PF2, WP2 | EQUI | EQUNR | Equipment Number | S/4 Hana | STXH | TDNAME | Name | Concatenate '000000000' + Target Equipment Number Target Equipment to be derived as follows: Step1- Use Value mapping: Equipment (Staging) to get the Staging Equipment Id; Step2 - Use Value mapping: Equipment to get the Target Equipment (New Equipment Number |
| 3 | - | - | - | - | S/4 Hana | STXL | TDID | Text ID | Default to 'LTXT' |
| 5 | PF2, WP2 | STXH | TDSPRAS | Language Key | S/4 Hana | STXL | TDSPRAS | Language Key | Direct Mapping |
| 6 | - | - | - | - | S/4 Hana | STXL | TDFORMAT | Tag column | Default to "*" |
| 7 | PF2, WP2 | STXL | TDLINE | Text Line | S/4 Hana | STXL | TDLINE | Text Line | Direct Mapping |
Note: Only the records marked as Cleansed in Inclusion-FL Long Text will be migrated
13. Equipment Long Text Line (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 Hana | STXH | TDOBJECT | Texts: application object | Default to 'EQUI' |
| 2 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | STXH | TDNAME | Name | Concatenate '000000000' + Target Equipment Number Target Equipment to be derived as follows: Step1- Use Value mapping: Equipment (Staging) to get the Staging Equipment Id; Step2 - Use Value mapping: Equipment to get the Target Equipment (New Equipment Number |
| 3 | - | - | - | - | S/4 Hana | STXH | TDID | Text ID | Default to 'LTXT' |
| 5 | DCT | STXH | TDSPRAS | Language Key | S/4 Hana | STXH | TDSPRAS | Language Key | Default to 'E' |
| 6 | - | - | - | - | S/4 Hana | STXL | TDFORMAT | Tag column | Default to "*" |
| 7 | DCT | STXL | TDLINE_EN | Text Line | S/4 Hana | STXL | TDLINE | Text Line | Direct Mapping |
UNION
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 Hana | STXH | TDOBJECT | Texts: application object | Default to 'EQUI' |
| 2 | DCT | EQUI | zLegacyEQUNR | Legacy Equipment Number | S/4 Hana | STXH | TDNAME | Name | Concatenate '000000000' + Target Equipment Number Target Equipment to be derived as follows: Step1- Use Value mapping: Equipment (Staging) to get the Staging Equipment Id; Step2 - Use Value mapping: Equipment to get the Target Equipment (New Equipment Number |
| 3 | - | - | - | - | S/4 Hana | STXH | TDID | Text ID | Default to 'LTXT' |
| 5 | DCT | STXH | TDSPRAS_LC | Language Key | S/4 Hana | STXH | TDSPRAS | Language Key | Direct Mapping |
| 6 | - | - | - | - | S/4 Hana | STXL | TDFORMAT | Tag column | Default to "*" |
| 7 | DCT | STXL | TDLINE_LC | Text Line | S/4 Hana | STXL | TDLINE | Text Line | Direct Mapping |
Note: For all relevant fields Data Origin will be defaulted to 'Individual Maintenance'
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
| OTH_Migration_Date Relevant Values A2D | Dates to be defaulted for A2D objects for each Migration Cycle |
| Assembly and Construction Type | Mapping of legacy Assembly/ Construction Type to new Assembly/ Construction Type |
| Characteristic A2D (Staging) | Old to Staging Characteristic A2D |
| Characteristic A2D | Old to New Characteristic A2D |
| Class A2D | Old to New Class A2D |
| Contact Person | Old to New Contact Person |
| Cost Centre | Old to New Cost Center |
| Equipment (Staging) | Legacy to Staging Equipment |
| Functional Location | List of relevant Asset Functional Locations slated for migration, including the Target Technical Object. This will also be used for Old to New Functional Location Mapping |
| Maintenance Planner Group | Old to New Planner Group |
| Plant | Old Plant to New Plant |
| Plant Section | Old to new Plant Section |
| Technical Object Type | Old to new Technical Object Type |
| User Status Equipment | Old to New Equipment User Status |
| Vendor Number | LIFNR: Old Vendor Code to New Vendor Code |
| Work Centre A2D | Old to new Work Centre A2D |
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 Data Team |
| 2 | Ensure all Transformation mappings are up to date | SyWay Data Team |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Verify Record Count | SyWay A2D Data Team to verify that the total number of relevant records from the source systems and/or 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
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the Source Extract and 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 Source Extract & 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 re-upload 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
Pre-Cutover : 1002 Equipment
Pre-Cutover : 1002a Equipment Classification
Pre-Cutover : 1002b Equipment User Status
Pre-Cutover : 1002c Equipment Long Text
Pre-Cutover : 1002d Equipment Partner Assignment
Note: A separate load program may need to be created for 1002b, 1002c, 1002d if these become a risk to the actual cutover and need to be removed from the critical path. This will be evaluated post Mock 1
Configuration
List the Configurations required before loading can commence
| Item # | Configuration Item |
|---|---|
| 1 | T370T - Equipment Category |
| 2 | T370K - Object Type |
| 3 | TCURC - Currency |
| 4 | T005 - Country of manufacturer |
| 5 | T001W - Maintenance Plant |
| 6 | T357 - Plant Section |
| 7 | T370C - ABC indicator |
| 8 | T399I - Planning Plant |
| 9 | T024I - Planner Group |
| 10 | TPAR - Business Partner: Functions |
| 11 | T002 - Language Keys |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1003 | Functional Location |
| 1006 | Work Centre |
| 1074 | Cost Center |
| 1010 | PM Assembly/ Construction Types |
| 1015 | Characteristics |
| 1009 | Class |
| 3018 | Business Partner - FI Vendor (FLVN00) |
Error Handling
The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management
| Error Type | Error Description | Action Taken |
|---|---|---|
Configuration | Invalid Equipment category | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Object Type | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Currency | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Country of Manufacturer | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Maintenance Plant | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Plant Section | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid ABC indicator | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Planning Plant | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Planner Group | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Partner Function | 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 |
Invalid Data | Invalid Superordinate Equipment | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Functional Location | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Work Centre | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Cost Center | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Construction Type | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Class | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Characteristics | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Vendor Business Partner | Expedite whether the master data is changed in the system |
Post-Load Validation
Project Team
The following post-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
Verify Count | SyWay A2D Data team to verify the record count created in target S/4 HANA by accessing post load reports in ADMM 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 Equipment data in target S/4 HANA were loaded correctly via ADMM post load reports or standard reports from S/4 HANA. |
Business
The following post-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
Verify Count | Download Post Load Reports from ADMM 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 Equipment data in target S/4 HANA were loaded correctly via ADMM 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
- Equipment can't exist stand alone and should always be installed under an Superior Equipment or a Functional Location.
- Material record shall be created for Specific Critical capital spares along with a Fixed Asset record. Equipment related to these critical spares shall be assigned with the material record created as the Inventory Number (INVNR). Sequentially, the Fixed Asset will be updated with the specific Equipment record.
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.