| Status | |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Purpose
The purpose of this document is to define the conversion approach to create Functional Location in S/4 HANA.
Legacy Functional Locations are using a diverse range of formats across the different systems. There are instances where the same Functional Locations are duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Functional Locations will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active Functional Location from Legacy Source Systems into S/4HANA following the Functional Location Master Data Design Standard.
Functional Locations are technical objects that structure the maintainable objects of a company. They can represent either the location of a maintainable item, or the maintainable item itself. A functional location does not normally change and will record the history of all equipment that is installed at that location.
Syensqo utilizes Functional Locations (FLOC) within the SAP S/4HANA system to define and manage its Asset Hierarchy. The asset hierarchy is structured across three main categories:
- Organisational Level - This level represents the enterprise structure of Syensqo. It defines:
The Company
The Global Business Unit (GBU)
The Plant
Navigational Level - This level structures the hierarchy based on the functional or geographical layout of the plant. It defines:
- Units within the Plant
- Further sub-levels based on the physical location or logical grouping of assets, enabling effective representation and navigation within the hierarchy
- `Asset Level - This is the installation level where the actual Assets and Sub-assets are physically located. It includes:
- Specific installation points for equipment
- Maintainable assets themselves, serving as key points for maintenance planning and execution
The data from legacy system includes:
- Functional Location having Maintenance Plant (IFLOT-WERKS) in scope
The data from legacy system excludes:
- Functional Location with Inactive System Status (INAC)
- Functional Location with Deletion Flag System Status (DLFL)
- Exclusion List = Manual Review (Initial List Low-Level Functional Location). Note that this will be an inclusion from 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 | Active Functional Locations will be extracted from PF2 and WP2 | 250,000 | S/4HANA | 250,000 |
DCT | Functional Locations which do not have data existing from PF2 and WP2 as per Syensqo Asset Structure. This includes Functional Locations for Organisation Level 1-3 and Navigation Levels 1-4. | TBD | S/4HANA | TBD |
Additional Information
Multi-language Requirement
Functional Location description will be made available in English.
Multi language is supported for Functional Location. Login via a different language will have its description displayed in the logon language if the language key is maintained in the Functional Location.
Document Management
- <Types of documents> documents currently attached to Functional Locations will be migrated.
- Refer to the Document Management in the SyWay Solution.
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
The technical design of the target for this conversion approach.
1. Functional Location Master
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| IFLOT | TPLNR | TPLNR | Functional Location Number | CHAR | 30 | Mandatory |
| IFLOT | TPLKZ | TPLKZ | Structure Indicator | CHAR | 80 | Mandatory |
| IFLOT | FLTYP | FLTYP | Category | CHAR | 80 | Mandatory |
| IFLOT | INBDT | INBDT | Start-Up Date | DATS | 8 | Conditional |
| IFLOT | EQART | EQART | Object Type | CHAR | 80 | Mandatory |
| IFLOT | HERST | HERST | Manufacturer | CHAR | 30 | Conditional |
| IFLOT | TYPBZ | TYPBZ | Model Number | CHAR | 20 | Conditional |
| IFLOT | MAPAR | MAPAR | Manufacturer Part Number | CHAR | 30 | Conditional |
| IFLOT | HERLD | HERLD | Country/Region of Manufacture | CHAR | 80 | Conditional |
| IFLOT | BAUJJ | BAUJJ | Year of Construction | CHAR | 4 | Conditional |
| IFLOT | BAUMM | BAUMM | Month of Construction | CHAR | 80 | Conditional |
| IFLOT | SERGE | SERGE | Manufacturer Serial Number | CHAR | 30 | Conditional |
| IFLOT | ANSWT | ANSWT | Acquisition Value | NUMC | 13 | Conditional |
| IFLOT | WAERS | WAERS | Currency Key ( ISO Format ) | CHAR | 80 | Conditional |
| IFLOT | SWERK | SWERK | Maintenance Plant | CHAR | 80 | Mandatory |
| IFLOT | EQFNR | EQFNR | Sort Field | CHAR | 30 | Conditional |
| IFLOT | BEBER | BEBER | Plant Section | CHAR | 80 | Conditional |
| IFLOT | ABCKZ | ABCKZ | ABC Indicator | CHAR | 80 | Conditional |
| ILOA | INGRP | INGRP | Planner Group | CHAR | 80 | Conditional |
| ILOA | IWERK | IWERK | Planning Plant | CHAR | 80 | Mandatory |
| ILOA | GEWRK | GEWRK | Maintenance Work Center | CHAR | 80 | Conditional |
| ILOA | WERGW | WERGW | Work Center Plant | CHAR | 80 | Conditional |
| ILOA | BUKRS | BUKRS | Company Code | CHAR | 80 | Mandatory |
| ILOA | KOSTL | KOSTL | Cost Center | CHAR | 80 | Conditional |
| IFLOT | TPLMA | TPLMA | Superior Functional Location | CHAR | 80 | Conditional |
| IFLOT | IEQUI | IEQUI | Indicator: Installation Allowed | CHAR | 1 | Conditional |
| ILOA | SUBMT | SUBMT | Construction Type | CHAR | 80 | Conditional |
| ILOA | KOKRS | KOKRS | Controlling Area | CHAR | 4 | Mandatory |
| IFLOT | BRGEW | BRGEW | Weight of Object | QUAN | 13 | Conditional |
| IFLOT | GEWEI | GEWEI | Unit of Weight | UNIT | 3 | Conditional |
| 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. Functional Location Short Text
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| IFLOTX | TPLNR | TPLNR | Functional Location Number | CHAR | 30 | Mandatory |
| IFLOTX | SPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| IFLOTX | PLTXT | PLTXT | Description of Functional Location | CHAR | 40 | Mandatory |
Note: Each Functional Location must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish
3. Functional Location 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 |
| KSSK | OBJEK | OBJEK | Object Key (Functional Location Number) | CHAR | 90 | Mandatory |
| KSSK | STATU | STATU | Classification Status | CHAR | 80 | Mandatory |
| KSSK | STDCL | STDCL | Indicator: Standard Class | CHAR | 80 | |
| KSSK | KEYDATE | KEYDATE | Valid From Date | DATS | 8 | |
| KSSK | NO_DEFAULT_VALUES | NO_DEFAULT_VALUES | Indicator: No Default Values | CHAR | 80 |
4. Functional Location Classification (Characteristics Value Allocation)
| 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 |
| KSSK | OBJEK | OBJEK | Object Key (Functional Location Number) | CHAR | 90 | Mandatory |
| AUSP | Characteristic Name | CHAR | 80 | Mandatory | ||
| AUSP | POSNR | POSNR | Item Number | CHAR | 3 | Mandatory |
| AUSP | ATFLV | ATFLV | Numerical Value - From | NUMC | 16 | Conditional |
| AUSP | ATFLB | ATFLB | Numerical Value - To | NUMC | 16 | Conditional |
| AUSP | ATCOD | ATCOD | Code for Value Dependency | CHAR | 1 | 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 | VALUE_CHAR | VALUE_CHAR | Characteristic Value | CHAR | 30 | Conditional |
5. Functional Location Partner
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| IHPA | OBJNR | OBJNR | Object Number (Internal Floc Number) | CHAR | 30 | Mandatory |
| IHPA | OBTYP | OBTYP | Object Type | CHAR | 3 | Mandatory |
| IHPA | PARVW | PARVW | Partner Function | CHAR | 2 | Mandatory |
| IHPA | PARNR | PARNR | Partner | CHAR | 12 | Mandatory |
6. Functional Location User Status
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| JEST | OBJNR | OBJNR | Object Number (Internal Floc Number) | CHAR | 30 | Mandatory |
| JSTO | STSMA | STSMA | Status profile of the functional location | CHAR | 8 | Mandatory |
JEST | STAT | STAT | Status Number in User Status List | CHAR | 5 | Mandatory |
JEST | INACT | INACT | Indicator: Status Is Inactive | CHAR | 1 |
7. Functional Location Long Text Header
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXH | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXH | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXH | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXH | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
8. Functional Location Long Text Line
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| STXL | TDOBJECT | TDOBJECT | Texts: application object | CHAR | 10 | Mandatory |
| STXL | TDNAME | TDOBNAME | Name | CHAR | 70 | Mandatory |
| STXL | TDID | TDID | Text ID | CHAR | 4 | Mandatory |
| STXL | TDSPRAS | SPRAS | Language Key | LANG | 1 | Mandatory |
| STXL | TDFORMAT | TDFORMAT | Tag column | CHAR | 1 | Mandatory |
| STXL | TDLINE | TDLINE | Text Line | CHAR | 72 | Mandatory |
Data Cleansing
Functional Location Data strictly adheres to the Master Data Standard. The complete information of the key fields that hold the Functional Location information follows the Master Data Standard document that is located here.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
1003-001 | C1 | Missing Functional Location Descriptions | Functional Location as per Relevancy Criteria where there are blank Functional Location Descriptions. | Functional Location Description | PF2, WP2 |
| 1003-002 | C2 | Functional Location Descriptions with Informal Words | Functional Location as per Relevancy Criteria which contain [Informal Words] in the Functional Location Description | Functional Location Description | PF2, WP2 |
| 1003-003 | C1 | Invalid, Inactive or no Cost Centres linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Cost Centre which does not belong below: 1. Cost Centre (FI) as per Relevancy Criteria | Cost Centre | PF2, WP2 |
| 1003-005 | C1 | Invalid, Inactive or no Class linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Class which does not belong below: 1. Class as per Relevancy Criteria | Class | PF2, WP2 |
| 1003-006 | C1 | Invalid, Inactive or no Characteristic linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Characteristic which does not belong below: 1. Characteristic as per Relevancy Criteria | Characteristic | PF2, WP2 |
| 1003-007 | C1 | Invalid, Inactive or no Construction Type linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Construction Type which does not belong below: 1. Construction Type as per Relevancy Criteria | Construction Type | PF2, WP2 |
| 1003-008 | C1 | Invalid or Inactive Document Info Record linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Document Info Record which does not belong below: 1. Document Info Record as per Relevancy Criteria | Document Info Record | PF2, WP2 |
1003-009 | C1 | Invalid or Inactive Material linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Material which does not belong below: 1. Material Master (S2P) as per Relevancy Criteria | Material | PF2, WP2 |
| 1003-010 | C1 | Invalid, Inactive or no Work Centres linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Work Centre which does not belong below: 1. Work Centre as per Relevancy Criteria | Work Centre | PF2, WP2 |
| 1003-011 | C1 | Invalid or no Planner Group linked to Functional Location | Functional Location as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I) | Planner Group | PF2, WP2 |
| 1003-012 | C1 | Invalid or no Technical Object Type linked to Functional Location | Functional Location as per Relevancy Criteria with no Technical Object Type Assigned or Invalid Technical Object Type (T370K) | Technical Object Type | PF2, WP2 |
| 1003-013 | C1 | Maintainable physical assets created as Functional Location (than Equipment) | Functional Location | PF2, WP2 | |
| 1003-014 | C1 | Review all Functional Location / Equipment sitting under "ZDELETE". If these data set is not used / not needed, the system status should be set to INAC. | System Status | PF2, WP2 | |
| 1003-015 | C1 | Invalid, Inactive or no Superior Functional Location linked to Functional Location | Functional Location as per Relevancy Criteria with no Superior Functional Location Assigned or with a Superior Functional Location which does not belong below: 1. Functional Location as per Relevancy Criteria | Superior Functional Location | PF2, WP2 |
| 1003-016 | C1 | Invalid, Inactive or no Maintenance Plans linked to Functional Location | Functional Location as per Relevancy Criteria with no Maintenance Plan Linked or with a Maintenance Plan which does not belong below: 1. Maintenance Plan as per Relevancy Criteria | Maintenance Plan | PF2, WP2 |
| 1003-017 | C1 | Invalid or Inactive Business Partner (Customer) linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Business Partner / Customer which does not belong below: 1. Business Partner FLCU01 (SD) as per Relevancy Criteria | Business Partner (Customer) | PF2, WP2 |
| 1003-019 | C2 | Material Types of Construction Types are non-Maintenance Assembly | Functional as per Relevancy Criteria where the Construction Type Assigned has a non-Maintenance Assembly Material Type* QF2: ZZ90-Maintenance Assembly WQ2: ZIBA-Maintenance Assembly | Construction Type | PF2, WP2 |
| 1003-020 | C1 | Invalid or Inactive Bill of Material linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Bill of Materia which does not belong below: 1. Bill of Material as per Relevancy Criteria | Bill of Material | PF2, WP2 |
| 1003-021 | C1 | Functional Location Company Code incorrect. | Functional Location as per Relevancy Criteria with Invalid Company Code (T001) | Company Code | PF2, WP2 |
| 1003-023 | C1 | Functional Location Currency Codes incorrect. | Functional Location as per Relevancy Criteria with Invalid Currency Codes (TCURC) | Currency | PF2, WP2 |
| 1003-024 | C2 | Functional Location Planning Plant and Maintenance Plant are not the same. | Functional Location as per Relevancy Criteria with Planning Plant <> Maintenance Plant | Maintenance Plant, Planning Plant | PF2, WP2 |
| 1003-025 | C1 | ABC Indicator missing on Functional Location | Functional Location as per Relevancy Criteria where ABC Indicator is blank | ABC Indicator | 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:
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 Functional Locations that need to be created to support the to-be design
The high-level process for DCT is represented by the diagram below:
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 the repository. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate.
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads.
Extraction Run Sheet
| Req # | Requirement 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 Functional Location 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. Functional Location Master DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| TPLNR | Functional Location Number | Mandatory Ensure follows valid mask for each Level of the Functional Location Structure. Organisation Level (SORG) = 'XXX-XX-AANNN' Navigational Layer (SNAV) = 'AANNN-XXXX-XXXX-XXXX-XX' Ensure SAST-L1 Functional Location should only have a SNAV Functional Location as Superior Functional Location |
| TPLKZ | Structure Indicator | Mandatory Allowed values for each Level of the Functional Location Structure: SORG = XXX-XX-AANNN |
| FLTYP | Category | Mandatory Allowed values for each Level of the Functional Location Structure: O - Org |
| INBDT | Start-Up Date | Conditional Default to 'Go-Live' Date. |
| EQART | Object Type | Conditional Must be populated for Category 'A' Functional Locations. Allowed values from T370K to be populated. |
| HERST | Manufacturer | Conditional User to populate value only for Category 'A' Functional Locations. |
| TYPBZ | Model Number | Conditional User to populate value only for Category 'A' Functional Locations. |
| MAPAR | Manufacturer Part Number | Conditional User to populate value only for Category 'A' Functional Locations. |
| HERLD | Country/Region of Manufacture | Conditional User to populate value only for Category 'A' Functional Locations. |
| BAUJJ | Year of Construction | Conditional User to populate value only for Category 'A' Functional Locations. |
| BAUMM | Month of Construction | Conditional User to populate value only for Category 'A' Functional Locations. |
| SERGE | Manufacturer Serial Number | Conditional User to populate value only for Category 'A' Functional Locations. |
| ANSWT | Acquisition Value | Conditional User to populate value if available, else assign 'Blank' |
| WAERS | Currency Key ( ISO Format ) | Conditional User to populate value if 'Acquisition Value' field has been populated, else assign 'Blank' |
| SWERK | Maintenance Plant | Mandatory User must populate value only for Category 'A' and 'N' Functional Locations. Allowed values from T001W to be populated for the In-Scope Plants |
| EQFNR | Sort Field | Conditional User must populate value only for Category 'A' Functional Locations. Sort Field data cannot be duplicated for the Plant of the Functional Location |
| BEBER | Plant Section | Conditional User must populate value only for Category 'A' Functional Locations. Allowed values from T357 to be populated |
| ABCKZ | ABC Indicator | Conditional User must populate value only for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'
|
| INGRP | Planner Group | Conditional User must populate value only for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X' Allowed values from T024I to be populated |
| IWERK | Planning Plant | Mandatory User must populate value only for Category 'A' and 'N' Functional Locations. Planning Plant to be populated with the same value as Maintenance Plant assigned Allowed values from T001W to be populated for the In-Scope Plants |
| GEWRK | Maintenance Work Center | Conditional User must populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X' Allowed values from CRHD to be populated |
| WERGW | Work Center Plant | Conditional User to populate Maintenance Plant value where Maintenance Work Center field has been populated, else assign 'Blank' Allowed values from T001W to be populated for the In-Scope Plants |
| BUKRS | Company Code | Mandatory User to populate value from T001K with reference to the assigned Maintenance Plant |
| KOSTL | Cost Center | Conditional User must populate value for all Functional Locations except for Function Locations with User Status as 'Maintenance not allowed' Allowed values from CSKS to be populated |
| TPLMA | Superior Functional Location | Conditional Should be blank for SORG- L1. For others Superior Functional location should be in accordance with the technical object structure of a particular Functional location Ensure SAST-L1 Functional Location must have a SNAV as Superior Functional Location Ensure all higher Labels must exists for a Functional location |
| IEQUI | Indicator: Installation Allowed | Conditional Indicator (check box). Allowed Values: ' ' = Not Checked 'X' = Checked User to populate value only for Level 2 Category 'A' Functional Location if there is no Equipment being installed below. |
| SUBMT | Construction Type | Conditional User must populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X' Category 'O' and 'N' Functional Locations to be assigned 'Blank'. Assigned Construction Type should have a TOT Characteristic value maintained which matches the 'Object Type' assigned on the Functional Location Allowed values from MARA to be populated |
| KOKRS | Controlling Area | Mandatory User to populate value from CSKS with reference to the assigned Cost Centre |
| BRGEW | Weight of Object | Conditional User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X' |
| GEWEI | Unit of Weight | Conditional User to populate unit value if BRGEW (Weight) has been maintained. Allowed values from T006 to be populated |
| NAME1 | Name 1 | Conditional User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. |
| NAME2 | Name 2 | Conditional User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. |
| NAME3 | Name 3 | Conditional User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. |
| NAME4 | Name 4 | Conditional User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. |
| COUNTRY | Country/Region Key | Conditional User to populate value based on the location of the maintenance plant assigned Allowed values from T001W to be populated |
2. Functional Location Short Text DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| TPLNR | Functional Location Number | Mandatory Key to link to Functional Location |
| SPRAS | Language Key | Mandatory The selected Language Key must correspond to the description provided. For each Functional Location there should be at least one record in English language |
| PLTXT | Description of Functional Location | Mandatory Description to be populated as per the local language of the plant. If populated Description not in English, same description to be converted in English language and included as additional record for the same Functional Location. Duplicate descriptions will not be allowed for each Language Key. Ensure that it does not include any of below characters: |
3. Functional Location Classification DCT Rules
| Data Element | Field Description | Rule |
|---|---|---|
| KLART | Class Type | Mandatory Default to '003' (Function Location). |
| OBTAB | Name of Database Table for Object | Mandatory Default to 'IFLOT'. |
| CLASSNUM | Class Name | Mandatory
Class other than '9999' must have naming convention = TOT (Tech Object Type) of the Floc |
| OBJEK | Object Key (Functional Location Number) | Mandatory Key to link Functional Location Header |
| ATINN | Characteristic Name | Mandatory User to populate allocated Characteristic based on 'Appendix - Class Values' maintained in Class MDS. |
| POSNR | Item Number | Mandatory. Positive numeric values only. Must be unique and ascending sequential |
| ATFLV | Numerical Value - From | Conditional User to populate value if Characteristic Data Type = 'NUM' |
| ATFLB | Numerical Value - To | Conditional User to populate value if Characteristic Data Type = 'NUM' and ATINT (Interval Values allowed) = 'X' |
| ATCOD | Code for Value Dependency | Conditional User to populate value if Characteristic Data Type = 'NUM' and ATINT (Interval Values allowed) = 'X'. User can define intervals such that the FROM value or TO value is given an operator. Example: 1.54>-<2.088 The coding of the individual possible entries is described below. 1 Equal to Value 1 |
| DATE_FROM | Lower Boundary for Date - Interval | Conditional User to populate value if Characteristic Data Type = 'DATE' |
| DATE_TO | Upper Boundary for Date - Interval | Conditional User to populate value if Characteristic Data Type = 'DATE' and ATINT (Interval Values allowed) = 'X' |
| TIME_FROM | Lower Boundary for Time - Interval | Conditional User to populate value if Characteristic Data Type = 'TIME' |
| TIME_TO | Upper Boundary for Time - Interval | Conditional User to populate value if Characteristic Data Type = 'TIME' and ATINT (Interval Values allowed) = 'X' |
| ATFLV | Currency Value - From (Floating Point) | Conditional User to populate value if Characteristic Data Type = 'CURR' |
| ATFLB | Currency Value - To (Floating Point) | Conditional User to populate value if Characteristic Data Type = 'CURR' and ATINT (Interval Values allowed) = 'X' |
| VALUE_CHAR | Characteristic Value | Conditional User to populate value if Characteristic Data Type = 'CHAR' |
4. Functional Location Partner DCT Rules
| Data Element | Field Description | Rule |
|---|---|---|
| TPLNR | Functional Location Number | Mandatory Key to link to Functional Location |
| OBTYP | Object Type | Mandatory Default to 'IFL' |
| PARVW | Partner Function | Conditional Default Partner Functions to be assigned to Category 'A' Functional Locations
|
| PARNR | Partner | Conditional Vendor Business Partners migrated to be populated for the defaults Partner Functions
|
5. Functional Location User Status DCT Rules
| Data Element | Field Description | Rule |
|---|---|---|
| TPLNR | Functional Location Number | Mandatory Key to link to Functional Location |
| STSMA | Status profile of the functional location | Mandatory Allowed values from TJ20 to be populated |
| STAT | Status Number in User Status List | Conditional Category 'O' and 'N' Functional Locations to be assigned with User Status "Maintenance Not Allowed" User to populate appropriate status included in Status Profile for Category 'A' Functional Locations, else default to 'PLAN' Allowed values from TJ30 to be populated |
| INACT | Indicator: Status Is Inactive | Conditional Allowed Values: ' ' = User Status is Active 'X' = User Status is Inactive |
6. Functional Location Long Text Header DCT Rules
| Data Element | Field Description | Rule |
|---|---|---|
| TPLNR | Functional Location Number | Non-Editable Key to link to Functional Location Direct Mapping from Functional Location Long Text Line: TPLNR field |
| KZLTX | Long Text Exists | Non Editable Default to "X" |
| TDOBJECT | Texts: application object | Non-Editable Direct Mapping from Functional Location Long Text Line: TDOBJECT field |
| TDNAME | Name | Non-Editable Direct Mapping from Functional Location Long Text Line: TDNAME field |
| TDID | Text ID | Non-Editable Direct Mapping from Functional Location Long Text Line: TDID field |
| TDSPRAS | Language Key | Non-Editable Direct Mapping from Functional Location Long Text Line: TDSPRAS field |
Functional Location Long Text Line DCT Rules
| Data Element | Field Description | Rule |
|---|---|---|
| TPLNR | Functional Location Number | Mandatory Key to link to Functional Location |
| TDOBJECT | Texts: application object | Non-Editable Default to 'IFLOT' |
| TDOBNAME | Name | Non-Editable To be populated with the TPLNR value |
| TDID | Text ID | Non-Editable Default to 'LTXT' |
| SPRAS | Language Key | Mandatory Must be either one of the following: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish |
| TDFORMAT | Tag column | Non-Editable Default to "*" |
| TDLINE | Text Line | Mandatory Free Text |
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 |
|---|---|---|
1 | Ensure that create, change and deletion of master data is freeze in legacy Production system | Legacy IT |
| 2 | Relevancy Criteria for Characteristics | SyWay A2D Data Team |
| 3 | Relevancy Criteria for Class | SyWay A2D Data Team |
| 4 | Relevancy Criteria for Construction Type | SyWay A2D Data Team |
| 5 | Relevancy Criteria for Work Centre | SyWay A2D Data Team |
| 6 | Relevancy Criteria for Cost Centre | SyWay A2D Data Team |
| 7 | Relevancy Criteria for Business Partner (Vendor) | SyWay A2D Data Team |
ransformation
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 Syniti Migrate
- 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 | Ensure all mapping tables are up to date. | Syniti |
3 | In dspMigrate, select the wave – S4/HANA – Plant Maintenance | Syniti |
4 | Go to Process Area Launch and Process the Object – Functional Location | Syniti |
5 | Review and Validate Error and Preload Reports | Syniti |
6 | Execute the transformation to prepare the target tables | Syniti |
7 | Validate data from pre-load and error reports | Business/Data owner |
| 8 | Generate load files | SyWay Data Team |
Transformation Rules
1. Functional Location 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 | IFLOT | TPLNR | Functional Location Number | S/4 Hana | IFLOT | TPLNR | Functional Location Number | Derive Floc Number as per value mapping: Functional Location |
| 2 | - | - | - | - | S/4 Hana | IFLOT | TPLKZ | Structure Indicator | Derive the Structure Indicator based on the Structure Level maintained in value mapping : Function Location For Navigation Level Flocs assign TPLKZ = SVAS (AANNN-XXXX-XXXX-XXXX-XX) For Asset Level Flocs assign TPLKZ = SAST (X-XXXXNNNNNN) |
| 3 | - | - | - | - | S/4 Hana | IFLOT | FLTYP | Category | Derive the Structure Level as per value mapping : Function Location and apply logic as below: For Organisation Level Flocs assign FLTYP = O (Org) For Navigation Level Flocs assign FLTYP = N (Nav) For Asset Level Flocs assign FLTYP = A (Asset) |
| 4 | PF2, WP2 | IFLOT | INBDT | Start-Up Date | S/4 Hana | IFLOT | INBDT | Start-Up Date | Derive the date as per value mapping : OTH_Migration_Date Relevant Values A2D (using Object ID "1003" and Field Name = "IFLOT-INBDT". |
| 5 | PF2, WP2 | IFLOT | EQART | Object Type | S/4 Hana | IFLOT | EQART | Object Type | Derive the Object Type as per value mapping : Asset_Technical Object Type If mapping missing in the above list, use enrichment mapping: ENR-Functional Location_Technical Object Type and derive the Object Type based on the Legacy Functional Location |
| 6 | PF2, WP2 | IFLOT | HERST | Manufacturer | S/4 Hana | IFLOT | HERST | Manufacturer | Direct Mapping |
| 7 | PF2, WP2 | IFLOT | TYPBZ | Model Number | S/4 Hana | IFLOT | TYPBZ | Model Number | Direct Mapping |
| 8 | PF2, WP2 | IFLOT | MAPAR | Manufacturer Part Number | S/4 Hana | IFLOT | MAPAR | Manufacturer Part Number | Direct Mapping |
| 9 | PF2, WP2 | IFLOT | HERLD | Country/Region of Manufacture | S/4 Hana | IFLOT | HERLD | Country/Region of Manufacture | Direct Mapping |
| 10 | PF2, WP2 | IFLOT | BAUJJ | Year of Construction | S/4 Hana | IFLOT | BAUJJ | Year of Construction | Direct Mapping |
| 11 | PF2, WP2 | IFLOT | BAUMM | Month of Construction | S/4 Hana | IFLOT | BAUMM | Month of Construction | Direct Mapping |
| 12 | PF2, WP2 | IFLOT | SERGE | Manufacturer Serial Number | S/4 Hana | IFLOT | SERGE | Manufacturer Serial Number | Direct Mapping |
| 13 | PF2, WP2 | IFLOT | ANSWT | Acquisition Value | S/4 Hana | IFLOT | ANSWT | Acquisition Value | Direct Mapping |
| 14 | PF2, WP2 | IFLOT | WAERS | Currency Key ( ISO Format ) | S/4 Hana | IFLOT | WAERS | Currency Key ( ISO Format ) | Direct Mapping |
| 15 | PF2, WP2 | ILOA | SWERK | Maintenance Plant | S/4 Hana | IFLOT | SWERK | Maintenance Plant | Derive based on Value Mapping: Plant (Maintenance Plant = Yes) |
| 16 | PF2, WP2 | ILOA | EQFNR | Sort Field | S/4 Hana | IFLOT | EQFNR | Sort Field | Direct Mapping |
| 17 | PF2, WP2 | ILOA | BEBER | Plant Section | S/4 Hana | IFLOT | BEBER | Plant Section | Derive the Plant Section as per value mapping : Plant Section If mapping missing in the above list, use enrichment mapping: ENR-Functional Location_Plant Section and derive the Plant Section based on the Legacy Functional Location |
| 18 | - | - | - | ABC Indicator | S/4 Hana | IFLOT | ABCKZ | ABC Indicator | Use below logic -
|
| 19 | PF2, WP2 | IFLOT | INGRP | Planner Group | S/4 Hana | ILOA | INGRP | Planner Group | Derive the Plant Section as per value mapping : Maintenance Planner Group |
| 20 | PF2, WP2 | IFLOT | IWERK | Planning Plant | S/4 Hana | ILOA | IWERK | Planning Plant | Derive based on Value Mapping: Plant (Maintenance Plant = Yes) |
| 21 | PF2, WP2 | ILOA | GEWRK | Maintenance Work Center | S/4 Hana | ILOA | GEWRK | Maintenance Work Center | Derive as per value mapping : Work Center A2D |
| 22 | PF2, WP2 | ILOA | WERGW | Work Center Plant | S/4 Hana | ILOA | WERGW | Work Center Plant | Derive as per value mapping : Work Center A2D |
| 23 | PF2, WP2 | ILOA | BUKRS | Company Code | S/4 Hana | ILOA | BUKRS | Company Code | Derive as per value mapping : Company Code |
| 24 | PF2, WP2 | ILOA | KOSTL | Cost Center | S/4 Hana | ILOA | KOSTL | Cost Center | Derive as per value mapping : Cost Center |
| 25 | - | - | - | Superior Functional Location | S/4 Hana | ILOA | TPLMA | Superior Functional Location | Derive Superior Floc Number as per value mapping: Functional Location |
| 26 | - | - | - | Indicator: Installation Allowed | S/4 Hana | ILOA | IEQUI | Indicator: Installation Allowed | Derive Installation Allowed Flag as per value mapping: Functional Location |
| 27 | - | - | - | Construction Type | S/4 Hana | ILOA | SUBMT | Construction Type | Derive Construction Type as per enrichment mapping: ENR-Functional Location_Construction Type |
| 28 | PF2, WP2 | ILOA | KOKRS | Controlling Area | S/4 Hana | ILOA | KOKRS | Controlling Area | Derive as per value mapping : Controlling Area |
| 29 | - | - | - | - | S/4 Hana | IFLOT | BRGEW | Weight of Object | Derive value as per enrichment mapping: ENR-Functional Location_LTXT_Values |
| 30 | - | - | - | - | S/4 Hana | IFLOT | GEWEI | Unit of Weight | Derive value as per enrichment mapping: ENR-Functional Location_LTXT_Values |
| 31 | - | - | - | - | S/4 Hana | ADRC | NAME1 | Name 1 | Derive value as per enrichment mapping: ENR-Functional Location_LTXT_Values |
| 32 | - | - | - | - | S/4 Hana | ADRC | NAME2 | Name 2 | Derive value as per enrichment mapping: ENR-Functional Location_LTXT_Values |
| 33 | - | - | - | - | S/4 Hana | ADRC | NAME3 | Name 3 | Derive value as per enrichment mapping: ENR-Functional Location_LTXT_Values |
| 34 | - | - | - | - | S/4 Hana | ADRC | NAME4 | Name 4 | Derive value as per enrichment mapping: ENR-Functional Location_LTXT_Values |
| 35 | - | - | - | - | S/4 Hana | ADRC | COUNTRY | Country/Region Key | Derive Country/ Region key based on Maintenance Plant assigned from Table T001W |
2. Functional Location Master Transformation Rule (DCT)
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | - | - | - | - | S/4 Hana | IFLOT | TPLNR | Functional Location Number | Direct Mapping |
| 2 | - | - | - | - | S/4 Hana | IFLOT | TPLKZ | Structure Indicator | Direct Mapping |
| 3 | - | - | - | - | S/4 Hana | IFLOT | FLTYP | Category | Direct Mapping |
| 4 | - | - | - | - | S/4 Hana | IFLOT | INBDT | Start-Up Date | Derive the date as per value mapping : OTH_Migration_Date Relevant Values A2D (using Object ID "1003" and Field Name = "IFLOT-INBDT". |
| 5 | - | - | - | - | S/4 Hana | IFLOT | EQART | Object Type | |
| 6 | - | - | - | - | S/4 Hana | IFLOT | HERST | Manufacturer | |
| 7 | - | - | - | - | S/4 Hana | IFLOT | TYPBZ | Model Number | |
| 8 | - | - | - | - | S/4 Hana | IFLOT | MAPAR | Manufacturer Part Number | |
| 9 | - | - | - | - | S/4 Hana | IFLOT | HERLD | Country/Region of Manufacture | |
| 10 | - | - | - | - | S/4 Hana | IFLOT | BAUJJ | Year of Construction | |
| 11 | - | - | - | - | S/4 Hana | IFLOT | BAUMM | Month of Construction | |
| 12 | - | - | - | - | S/4 Hana | IFLOT | SERGE | Manufacturer Serial Number | |
| 13 | - | - | - | - | S/4 Hana | IFLOT | ANSWT | Acquisition Value | |
| 14 | - | - | - | - | S/4 Hana | IFLOT | WAERS | Currency Key ( ISO Format ) | |
| 15 | - | - | - | - | S/4 Hana | IFLOT | SWERK | Maintenance Plant | |
| 16 | - | - | - | - | S/4 Hana | IFLOT | EQFNR | Sort Field | |
| 17 | - | - | - | - | S/4 Hana | IFLOT | BEBER | Plant Section | |
| 18 | - | - | - | - | S/4 Hana | IFLOT | ABCKZ | ABC Indicator | |
| 19 | - | - | - | - | S/4 Hana | ILOA | INGRP | Planner Group | |
| 20 | - | - | - | - | S/4 Hana | ILOA | IWERK | Planning Plant | |
| 21 | - | - | - | - | S/4 Hana | ILOA | GEWRK | Maintenance Work Center | |
| 22 | - | - | - | - | S/4 Hana | ILOA | WERGW | Work Center Plant | |
| 23 | - | - | - | - | S/4 Hana | ILOA | BUKRS | Company Code | |
| 24 | - | - | - | - | S/4 Hana | ILOA | KOSTL | Cost Center | |
| 25 | - | - | - | - | S/4 Hana | ILOA | TPLMA | Superior Functional Location | |
| 26 | - | - | - | - | S/4 Hana | ILOA | IEQUI | Indicator: Installation Allowed | |
| 27 | - | - | - | - | S/4 Hana | ILOA | SUBMT | Construction Type | |
| 28 | - | - | - | - | S/4 Hana | ILOA | KOKRS | Controlling Area | |
| 29 | - | - | - | - | S/4 Hana | IFLOT | BRGEW | Weight of Object | |
| 30 | - | - | - | - | S/4 Hana | IFLOT | GEWEI | Unit of Weight | |
| 31 | - | - | - | - | S/4 Hana | ADRC | NAME1 | Name 1 | |
| 32 | - | - | - | - | S/4 Hana | ADRC | NAME2 | Name 2 | |
| 33 | - | - | - | - | S/4 Hana | ADRC | NAME3 | Name 3 | |
| 34 | - | - | - | - | S/4 Hana | ADRC | NAME4 | Name 4 | |
| 35 | - | - | - | - | S/4 Hana | ADRC | COUNTRY | Country/Region Key |
2. Functional Location Short Text
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | IFLOTX | TPLNR | Functional Location Number | S/4 Hana | IFLOTX | TPLNR | Functional Location Number | Direct Mapping |
| 2 | DCT | IFLOTX | SPRAS | Language Key | S/4 Hana | IFLOTX | SPRAS | Language Key | Direct Mapping |
| 3 | DCT | IFLOTX | PLTXT | Description of Functional Location | S/4 Hana | IFLOTX | PLTXT | Description of Functional Location | Value Mapping: OTH_Informal Words and OTH_Informal Characters Review the value mappings for the presence of informal words or invalid characters.If any are identified, replace them with the appropriate standardized values as specified in the mappings. |
3. Functional Location Classification
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | KSSK | KLART | Class Type | S/4 Hana | KSSK | KLART | Class Type | Direct Mapping |
| 2 | DCT | KSSK | OBTAB | Name of Database Table for Object | S/4 Hana | KSSK | OBTAB | Name of Database Table for Object | Direct Mapping |
| 3 | DCT | KSSK | CLASSNUM | Class Name | S/4 Hana | KSSK | CLASSNUM | Class Name | Direct Mapping |
| 4 | DCT | KSSK | OBJEK | Object Key (Functional Location Number) | S/4 Hana | KSSK | OBJEK | Object Key (Functional Location Number) | Direct Mapping |
| 5 | DCT | AUSP | ATINN | Characteristic Name | S/4 Hana | AUSP | CHARACT | Characteristic Name | Direct Mapping |
| 6 | DCT | AUSP | POSNR | Item Number | S/4 Hana | AUSP | POSNR | Item Number | Direct Mapping |
| 7 | DCT | AUSP | ATFLV | Numerical Value - From (Floating Point) | S/4 Hana | AUSP | ATFLV | Numerical Value - From (Floating Point) | Direct Mapping |
| 8 | DCT | AUSP | ATFLB | Numerical Value - To (Floating Point) | S/4 Hana | AUSP | ATFLB | Numerical Value - To (Floating Point) | Direct Mapping |
| 9 | DCT | AUSP | ATCOD | Code for Value Dependency | S/4 Hana | AUSP | ATCOD | Code for Value Dependency | Direct Mapping |
| 10 | DCT | AUSP | DATE_FROM | Lower Boundary for Date - Interval | S/4 Hana | AUSP | DATE_FROM | Lower Boundary for Date - Interval | Direct Mapping |
| 11 | DCT | AUSP | DATE_TO | Upper Boundary for Date - Interval | S/4 Hana | AUSP | DATE_TO | Upper Boundary for Date - Interval | Direct Mapping |
| 12 | DCT | AUSP | TIME_FROM | Lower Boundary for Time - Interval | S/4 Hana | AUSP | TIME_FROM | Lower Boundary for Time - Interval | Direct Mapping |
| 13 | DCT | AUSP | TIME_TO | Upper Boundary for Time - Interval | S/4 Hana | AUSP | TIME_TO | Upper Boundary for Time - Interval | Direct Mapping |
| 14 | DCT | AUSP | ATFLV | Currency Value - From (Floating Point) | S/4 Hana | AUSP | ATFLV | Currency Value - From (Floating Point) | Direct Mapping |
| 15 | DCT | AUSP | ATFLB | Currency Value - To (Floating Point) | S/4 Hana | AUSP | ATFLB | Currency Value - To (Floating Point) | Direct Mapping |
| 16 | DCT | AUSP | VALUE_CHAR | Characteristic Value | S/4 Hana | AUSP | VALUE_CHAR | Characteristic Value | Direct Mapping |
4. Functional Location User Status
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | IHPA | OBJNR | Object Number (Internal Floc Number) | S/4 Hana | IHPA | OBJNR | Object Number (Internal Floc Number) | Direct Mapping |
| 2 | DCT | IHPA | OBTYP | Object Type | S/4 Hana | IHPA | OBTYP | Object Type | Direct Mapping |
| 3 | DCT | IHPA | PARVW | Partner Function | S/4 Hana | IHPA | PARVW | Partner Function | Direct Mapping |
| 4 | DCT | IHPA | PARNR | Partner | S/4 Hana | IHPA | PARNR | Partner | Direct Mapping |
5. Functional Location Partner
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | JEST | OBJNR | Object Number (Internal Floc Number) | S/4 Hana | JEST | OBJNR | Object Number (Internal Floc Number) | Direct Mapping |
| 2 | DCT | JSTO | STSMA | Status profile of the functional location | S/4 Hana | JSTO | STSMA | Status profile of the functional location | Direct Mapping |
| 3 | DCT | JEST | STAT | Status Number in User Status List | S/4 Hana | JEST | STAT | Status Number in User Status List | Direct Mapping |
| 4 | DCT | JEST | INACT | Indicator: Status Is Inactive | S/4 Hana | JEST | INACT | Indicator: Status Is Inactive | Direct Mapping |
6. Functional Location Long Text Header
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | IFLOT | TPLNR | Functional Location Number | S/4 Hana | IFLOT | TPLNR | Functional Location Number | Direct Mapping |
| 2 | DCT | IFLOTX | KZLTX | Long Text Exists | S/4 Hana | IFLOTX | KZLTX | Long Text Exists | Direct Mapping |
| 3 | DCT | STXL | TDOBJECT | Texts: application object | S/4 Hana | STXL | TDOBJECT | Texts: application object | Direct Mapping |
| 4 | DCT | STXL | TDNAME | Name | S/4 Hana | STXL | TDNAME | Name | Direct Mapping |
| 5 | DCT | STXL | TDID | Text ID | S/4 Hana | STXL | TDID | Text ID | Direct Mapping |
| 6 | DCT | STXL | TDSPRAS | Language Key | S/4 Hana | STXL | TDSPRAS | Language Key | Direct Mapping |
Functional Location Long Text Line
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | IFLOT | TPLNR | Functional Location Number | S/4 Hana | IFLOT | TPLNR | Functional Location Number | Direct Mapping |
| 2 | DCT | STXL | TDOBJECT | Texts: application object | S/4 Hana | STXL | TDOBJECT | Texts: application object | Direct Mapping |
| 3 | DCT | STXL | TDNAME | Name | S/4 Hana | STXL | TDNAME | Name | Direct Mapping |
| 4 | DCT | STXL | TDID | Text ID | S/4 Hana | STXL | TDID | Text ID | Direct Mapping |
| 5 | DCT | STXL | TDSPRAS | Language Key | S/4 Hana | STXL | TDSPRAS | Language Key | Direct Mapping |
| 6 | DCT | STXL | TDFORMAT | Tag column | S/4 Hana | STXL | TDFORMAT | Tag column | Direct Mapping |
| 7 | DCT | STXL | TDLINE | Text Line | S/4 Hana | STXL | TDLINE | Text Line | Direct Mapping |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
| Mapping Table Name | Mapping Table Description |
|---|---|
Cost Centre | Cost Centre mapping table |
| Business Partner Vendor | Business Partner mapping table |
Functional Location | Functional Location mapping table |
Equipment | Equipment mapping table |
Class | Classification mapping table |
Characteristics | Characteristics mapping table |
OTH_Informal Words | List of Informal Words and the words used to replace |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | Syniti |
| 2 | Ensure all Transformation mappings are up to date | Syniti |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Verify Record Count | Data team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Data team to verify that all fields below meet pass the checks: 1. Mandatory Fields 2. Field and Value Mapping Correctness 3. Null Checks 4. Text Length Checks |
Review error 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 team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Business to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off data) |
Load
The load process includes:
- Execute the data load into target system using load tool
- 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
Configuration
| Item # | Configuration Item |
|---|---|
| 1 | T370S - Structure Indicators with edit masks |
| 2 | T370F - Functional Location Category |
| 3 | T370K - Object Type |
| 4 | TCURC - Currency |
| 5 | T005 - Country of manufacturer |
| 6 | T001W - Maintenance Plant |
| 7 | T357 - Plant Section |
| 8 | T370C - ABC indicator |
| 9 | T399I - Planning Plant |
| 10 | T024I - Planner Group |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1006 | Work Centre |
| 1074 | Cost Center |
| 1001 | BOM |
| 1015 | Characteristics |
| 1009 | Class |
| 1008 | Catalog Profile |
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 Structure indicator missing | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Functional location cat missing | 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 Weight Unit | 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 catalog profile | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Location | Engage Functional team to expedite and fix the error in the system |
Invalid Data | Invalid Cost Centre | 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 Work Centre | Expedite whether the master data is changed in the system |
Invalid Data | Invalid BOM | Expedite whether the master data is changed in the system |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | 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 | Data team to verify that the Functional Location 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 Functional Location 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.
- Functional Location is in scope based on data design and any exception requested by business.
- All data cleansing and preparation has been completed.
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.