Status	Approved
Owner	JOSHI-ext, Aditya
Stakeholders	ERGUIZA-ext, Pinky Love PUN-ext, Eddy TEE-ext, Paul LAKKAD-ext, Anirudh HUSSAN-ext, Nishin VILARES, ines LEIGHTON-ext, Dean STEFANESCU-ext, Aurelia MOUSSA-ext, Eva

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 (Value Mapping : Plant, where Maintenance Plant = 'Yes')

The data from legacy system excludes:

Functional Location with System Status (JEST-STAT) Inactive 'INAC'
Functional Location with System Status (JEST-STAT) Deletion Flag 'DLFL'
Functional Location part of Exclusion List (EXC-Functional Location_ID)

List of Tables to extract for this object is maintained here: Extract Table Register.

List of source systems and approximate number of records

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 Level 1-7 Functional Locations including 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

Refer to the Document Management in the SyWay Solution.

Note: Documents attached to Functional Locations will be migrated as part of 9104-EAM Attachments.

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 English language.

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

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	CLASSNUM	CLASSNUM	Class Name	CHAR	30	Mandatory
KSSK	OBJEK	OBJEK	Object Key (Functional Location Number)	CHAR	90	Mandatory
AUSP	ATINN	ATINN	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	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-003	C1	Invalid or 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-004	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-005	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-006	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-0007	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-008	C1	Invalid or no Plant Section linked to Functional Location	Functional Location as per Relevancy Criteria with no Planner Group Assigned or Invalid Plant Section	Plant Section	PF2, WP2
1003-009	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-010	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-011	C1	Functional Location Company Code incorrect.	Functional Location as per Relevancy Criteria with Invalid Company Code (T001)	Company Code	PF2, WP2
1003-012	C1	Functional Location Currency Codes incorrect.	Functional Location as per Relevancy Criteria with Invalid Currency Codes (TCURC)	Currency	PF2, WP2
1003-013	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-014	C2	Functional Location with Long Text assigned	Functional Location where Long Text Exit flag is assigned (IFLOTX-KZLTX) = 'X'	Long Text	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 . There are 2 possibilities:

The data exists. connects to the source and loads the data into . There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if ; 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

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
Not Applicable

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for 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 Naming Convention: Ensure follows valid mask for each Level of the Functional Location Structure. Organisation Level (SORG) = 'XXX-XX-AANNN' XXX = Syensqo XX = GBU AANNN= Country / Plant Navigational Layer (SNAV) = 'AANNN-XXXX-XXXX-XXXX-XX' AANNN-XXXX= Country/Plant-Unit XXXX = Section XXXX = Segment XX =Number of Segments Asset Layer (SAST) = 'X-XXXXNNNNNN' X = Unit (first letter) XXXX = Asset function 4-letter codes NNNNNN = Running Numbers 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 SNAV = AANNN-XXXX-XXXX-XXXX-XX SAST = X-XXXXNNNNNN
FLTYP	Category	Mandatory Allowed values for each Level of the Functional Location Structure: O - Org N - Nav A - Asset
INBDT	Start-Up Date	Conditional User must populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X' To be defaulted to 'Go-Live' date.
EQART	Object Type	Mandatory 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. Category 'O' and 'N' Functional Locations to be assigned 'Blank'.
TYPBZ	Model Number	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be assigned 'Blank'.
MAPAR	Manufacturer Part Number	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be assigned 'Blank'.
HERLD	Country/Region of Manufacture	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be assigned 'Blank'.
BAUJJ	Year of Construction	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be assigned 'Blank'.
BAUMM	Month of Construction	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be assigned 'Blank'.
SERGE	Manufacturer Serial Number	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be assigned 'Blank'.
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. Category 'O' and 'N' Functional Locations to be assigned value if available, else assign 'Blank'. 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. Category 'O' and 'N' Functional Locations to be assigned 'Blank'. 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' Aggregate values for all Characteristics assigned for the Functional Location as per Functional Location Classification DCT where ABC_FLAG = 'X' Derive ABC Indicator value by applying the below categorisation on the aggregated value from the last step Value > 14500, then assign 'A' Value in Range 101 < 14500, then assign 'B' Value in Range 0 < 101, then assign 'C'
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' To be assigned as 'Blank' for Function Locations with User Status as 'Maintenance not allowed' Allowed values from Work Centre DCT 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 Cost Center DCT 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 exist 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_EN	Description of Functional Location (English)	Mandatory Description Rule: TOT Description + Asset Tag (Sort Field) + Additional Description Ensure that this Functional Location Description is in English. Functional Location description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes
PLTXT_FR	Description of Functional Location (French)	Mandatory Description Rule: TOT Description + Asset Tag (Sort Field) + Additional Description Ensure that this Functional Location Description is in French. Functional Location description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes
PLTXT_IT	Description of Functional Location (Italian)	Mandatory Description Rule: TOT Description + Asset Tag (Sort Field) + Additional Description Ensure that this Functional Location Description is in Italian. Functional Location description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes
PLTXT_ZH	Description of Functional Location (Mandarin)	Mandatory Description Rule: TOT Description + Asset Tag (Sort Field) + Additional Description Ensure that this Functional Location Description is in Mandarin. Functional Location description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes
PLTXT_PT	Description of Functional Location (Brazilian Portuguese)	Mandatory Description Rule: TOT Description + Asset Tag (Sort Field) + Additional Description Ensure that this Functional Location Description is in Brazilian Portuguese. Functional Location description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes
PLTXT_DE	Description of Functional Location (German)	Mandatory Description Rule: TOT Description + Asset Tag (Sort Field) + Additional Description Ensure that this Functional Location Description is in German. Functional Location description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes
PLTXT_ES	Description of Functional Location (Spanish)	Mandatory Description Rule: TOT Description + Asset Tag (Sort Field) + Additional Description Ensure that this Functional Location Description is in Spanish. Functional Location description should be in Title Case. Duplicate descriptions will not be allowed. Ensure that it does not include any of below characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes

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 'EAM_9999' to be assigned as default User to populate any other class as required Class other than 'EAM_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 2 Greater Than or Equal to Value 1 and Smaller Than Value 2 3 Greater Than/Equal to Val. 1 and Smaller Than/Equal to Val.2 4 Greater Than Value 1 and Smaller Than Value 2 5 Greater Than Value 1 and Smaller Than or Equalt to Value 2 6 Smaller Than Value 1 7 Smaller Than or Equal to Value 1 8 Greater Than Value 1 9 Greater Than or 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'
ABC_FLAG	ABC Characteristic	Conditional User to specify value 'X' if Characteristic is to be used for deriving ABC Indicator for the Functional Location

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 Partner Functions to be assigned to Category 'A' Functional Locations 'Z1' (Asset Owner) 'Z2' (Asset Maintainer)
PARNR	Partner	Conditional Vendor Business Partners migrated to be populated for the above Partner Functions. 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

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 Default to 'ZEAMFL01'
STAT	Status Number in User Status List	Conditional Category 'O' and 'N' Functional Locations to be assigned with User Status 'MNTA' (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

Item #	Step Description	Team Responsible
1	Relevancy Criteria for Characteristics	SyWay A2D Data Team
2	Relevancy Criteria for Class	SyWay A2D Data Team
3	Relevancy Criteria for Construction Type	SyWay A2D Data Team
4	Relevancy Criteria for Work Centre	SyWay A2D Data Team
5	Relevancy Criteria for Cost Centre	SyWay A2D Data Team
6	Relevancy Criteria for Business Partner (Vendor)	SyWay A2D Data Team

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in
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 – [Object]	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. Functional Location Master
1.a 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	ENRICHMENT	ENR_Functional Location_TPLNR	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Derive Target Functional Location Label based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
2	-	-	-	-	S/4 Hana	IFLOT	TPLKZ	Structure Indicator	Default TPLKZ = 'SAST' (X-XXXXNNNNNN) for Asset Level Functional Locations
3	-	-	-	-	S/4 Hana	IFLOT	FLTYP	Category	Default FLTYP = A (Asset) for Asset Level Functional Locations
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 ENRICHMENT	IFLOT ENR-Functional Location_Technical Object Type	EQART zLegacyTPLNR	Object Type Legacy Functional Location Label	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 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	ENRICHMENT	ENR_Functional Location_TPLNR	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	IFLOT	EQFNR	Sort Field	Derive Sort Field as per enrichment ENR-Functional Location_SortField based on the Legacy Functional Location
17	PF2, WP2 ENRICHMENT	ILOA ENR-Functional Location_Technical Object Type	BEBER zLegacyTPLNR	Plant Section Legacy Functional Location Label	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 ENR-Functional Location_Plant Section and derive the Plant Section based on the Legacy Functional Location
18	-	-	-	-	S/4 Hana	IFLOT	ABCKZ	ABC Indicator	Use below logic - Aggregate values for all Characteristics assigned for the Functional Location as per Functional Location Classification DCT where ABC_FLAG = 'X' Derive ABC Indicator value by applying the below categorisation on the aggregated value from the last step Value > 14500, then assign 'A' Value in Range 101 < 14500, then assign 'B' Value in Range 0 < 101, then assign 'C'
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	PF2, WP2	IFLOT	TPLMA	Superior Functional Location	S/4 Hana	ILOA	TPLMA	Superior Functional Location	Derive Superior Functional Location based Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
26	ENRICHMENT	ENR-Functional Location_Installation Allowed	zLegacyTPLNR	Indicator: Installation Allowed	S/4 Hana	ILOA	IEQUI	Indicator: Installation Allowed	Derive Construction Type as per enrichment ENR-Functional Location_Installation Allowed based on the Legacy Functional Location
27	ENRICHMENT	ENR-Functional Location_Construction Type	zLegacyTPLNR	Construction Type	S/4 Hana	ILOA	SUBMT	Construction Type	Derive Construction Type as per enrichment ENR-Functional Location_Construction Type based on the Legacy Functional Location
28	PF2, WP2	ILOA	KOKRS	Controlling Area	S/4 Hana	ILOA	KOKRS	Controlling Area	Derive as per value mapping : Controlling Area
29	ENRICHMENT	ENR-Functional Location_LTXT_Values	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	IFLOT	BRGEW	Weight of Object	Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
30	ENRICHMENT	ENR-Functional Location_LTXT_Values	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	IFLOT	GEWEI	Unit of Weight	Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
31	ENRICHMENT	ENR-Functional Location_LTXT_Values	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	ADRC	NAME1	Name 1	Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
32	ENRICHMENT	ENR-Functional Location_LTXT_Values	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	ADRC	NAME2	Name 2	Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
33	ENRICHMENT	ENR-Functional Location_LTXT_Values	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	ADRC	NAME3	Name 3	Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
34	ENRICHMENT	ENR-Functional Location_LTXT_Values	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	ADRC	NAME4	Name 4	Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
35	ENRICHMENT	ENR-Functional Location_LTXT_Values	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	ADRC	COUNTRY	Country/Region Key	Derive Country/ Region key based on Maintenance Plant assigned from Table T001W

1.b 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	DCT	IFLOT	TPLNR	Functional Location Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	DCT	IFLOT	TPLKZ	Structure Indicator	S/4 Hana	IFLOT	TPLKZ	Structure Indicator	Direct Mapping
3	DCT	IFLOT	FLTYP	Category	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	DCT	IFLOT	EQART	Object Type	S/4 Hana	IFLOT	EQART	Object Type	Direct Mapping
6	DCT	IFLOT	HERST	Manufacturer	S/4 Hana	IFLOT	HERST	Manufacturer	Direct Mapping
7	DCT	IFLOT	TYPBZ	Model Number	S/4 Hana	IFLOT	TYPBZ	Model Number	Direct Mapping
8	DCT	IFLOT	MAPAR	Manufacturer Part Number	S/4 Hana	IFLOT	MAPAR	Manufacturer Part Number	Direct Mapping
9	DCT	IFLOT	HERLD	Country/Region of Manufacture	S/4 Hana	IFLOT	HERLD	Country/Region of Manufacture	Direct Mapping
10	DCT	IFLOT	BAUJJ	Year of Construction	S/4 Hana	IFLOT	BAUJJ	Year of Construction	Direct Mapping
11	DCT	IFLOT	BAUMM	Month of Construction	S/4 Hana	IFLOT	BAUMM	Month of Construction	Direct Mapping
12	DCT	IFLOT	SERGE	Manufacturer Serial Number	S/4 Hana	IFLOT	SERGE	Manufacturer Serial Number	Direct Mapping
13	DCT	IFLOT	ANSWT	Acquisition Value	S/4 Hana	IFLOT	ANSWT	Acquisition Value	Direct Mapping
14	DCT	IFLOT	WAERS	Currency Key ( ISO Format )	S/4 Hana	IFLOT	WAERS	Currency Key ( ISO Format )	Direct Mapping
15	DCT	IFLOT	SWERK	Maintenance Plant	S/4 Hana	IFLOT	SWERK	Maintenance Plant	Direct Mapping
16	DCT	IFLOT	EQFNR	Sort Field	S/4 Hana	IFLOT	EQFNR	Sort Field	Direct Mapping
17	DCT	IFLOT	BEBER	Plant Section	S/4 Hana	IFLOT	BEBER	Plant Section	Direct Mapping
18	DCT	IFLOT	ABCKZ	ABC Indicator	S/4 Hana	IFLOT	ABCKZ	ABC Indicator	Direct Mapping
19	DCT	ILOA	INGRP	Planner Group	S/4 Hana	ILOA	INGRP	Planner Group	Direct Mapping
20	DCT	ILOA	IWERK	Planning Plant	S/4 Hana	ILOA	IWERK	Planning Plant	Direct Mapping
21	DCT	ILOA	GEWRK	Maintenance Work Center	S/4 Hana	ILOA	GEWRK	Maintenance Work Center	Direct Mapping
22	-	-	-	-	S/4 Hana	ILOA	WERGW	Work Center Plant	Derive the Work Center Plant based on Work Center DCT
23	DCT	ILOA	BUKRS	Company Code	S/4 Hana	ILOA	BUKRS	Company Code	Derive the Company code from table 'T001K' where Maintenance Plant populated in DCT = T001K_BWKEY
24	DCT	ILOA	KOSTL	Cost Center	S/4 Hana	ILOA	KOSTL	Cost Center	Derive the Cost Center as per value mapping : Cost Center
25	DCT	ILOA	TPLMA	Superior Functional Location	S/4 Hana	ILOA	TPLMA	Superior Functional Location	Direct Mapping
26	DCT	ILOA	IEQUI	Indicator: Installation Allowed	S/4 Hana	ILOA	IEQUI	Indicator: Installation Allowed	Direct Mapping
27	DCT	ILOA	SUBMT	Construction Type	S/4 Hana	ILOA	SUBMT	Construction Type	Direct Mapping
28	DCT	ILOA	KOKRS	Controlling Area	S/4 Hana	ILOA	KOKRS	Controlling Area	Default to 'CO01' (SYSQ Controlling Area)
29	DCT	IFLOT	BRGEW	Weight of Object	S/4 Hana	IFLOT	BRGEW	Weight of Object	Direct Mapping
30	DCT	IFLOT	GEWEI	Unit of Weight	S/4 Hana	IFLOT	GEWEI	Unit of Weight	Direct Mapping
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	Direct Mapping

2. Functional Location 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	IFLOT	TPLNR	Functional Location Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOTX	SPRAS	Language Key	Default to 'E'
3	DCT	IFLOTX	PLTXT_EN	Description of Functional Location (English)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

UNION

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 Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOTX	SPRAS	Language Key	Default to 'F'
3	DCT	IFLOTX	PLTXT_FR	Description of Functional Location (French)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

UNION

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 Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOTX	SPRAS	Language Key	Default to 'I'
3	DCT	IFLOTX	PLTXT_IT	Description of Functional Location (Italian)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

UNION

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 Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOTX	SPRAS	Language Key	Default to '1'
3	DCT	IFLOTX	PLTXT_ZH	Description of Functional Location (Mandarin)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

UNION

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 Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOTX	SPRAS	Language Key	Default to 'P'
3	DCT	IFLOTX	PLTXT_PT	Description of Functional Location (Brazilian Portuguese)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

UNION

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 Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOTX	SPRAS	Language Key	Default to 'D'
3	DCT	IFLOTX	PLTXT_DE	Description of Functional Location (German)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

UNION

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 Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOTX	SPRAS	Language Key	Default to 'S'
3	DCT	IFLOTX	PLTXT_ES	Description of Functional Location (Spanish)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

3. Functional Location Classification

3.a Functional Location Classification Transformation Rule (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	ENRICHMENT	ENR_Functional Location_TPLNR	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Derive Target Functional Location Label based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
2	-	-	-	-	S/4 Hana	KSSK	KLART	Class Type	Default to '003'
3	-	-	-	-	S/4 Hana	KSSK	OBTAB	Name of Database Table for Object	Default to 'IFLOT'
4	PF2, WP2	KSSK	CLASSNUM	Class Name	S/4 Hana	KSSK	CLASSNUM	Class Name	Derive Target Class Name based on value mapping : Class A2D
5	PF2, WP2	AUSP	ATINN	Characteristic Name	S/4 Hana	AUSP	CHARACT	Characteristic Name	Derive Target Class Name based on value mapping : Characteristic A2D
6	PF2, WP2	AUSP	POSNR	Item Number	S/4 Hana	AUSP	POSNR	Item Number	Direct Mapping
7	PF2, WP2	AUSP	ATFLV	Numerical Value - From (Floating Point)	S/4 Hana	AUSP	ATFLV	Numerical Value - From (Floating Point)	Direct Mapping
8	PF2, WP2	AUSP	ATFLB	Numerical Value - To (Floating Point)	S/4 Hana	AUSP	ATFLB	Numerical Value - To (Floating Point)	Direct Mapping
9	PF2, WP2	AUSP	ATCOD	Code for Value Dependency	S/4 Hana	AUSP	ATCOD	Code for Value Dependency	Direct Mapping
10	PF2, WP2	AUSP	DATE_FROM	Lower Boundary for Date - Interval	S/4 Hana	AUSP	DATE_FROM	Lower Boundary for Date - Interval	Direct Mapping
11	PF2, WP2	AUSP	DATE_TO	Upper Boundary for Date - Interval	S/4 Hana	AUSP	DATE_TO	Upper Boundary for Date - Interval	Direct Mapping
12	PF2, WP2	AUSP	TIME_FROM	Lower Boundary for Time - Interval	S/4 Hana	AUSP	TIME_FROM	Lower Boundary for Time - Interval	Direct Mapping
13	PF2, WP2	AUSP	TIME_TO	Upper Boundary for Time - Interval	S/4 Hana	AUSP	TIME_TO	Upper Boundary for Time - Interval	Direct Mapping
14	PF2, WP2	AUSP	ATFLV	Currency Value - From (Floating Point)	S/4 Hana	AUSP	ATFLV	Currency Value - From (Floating Point)	Direct Mapping
15	PF2, WP2	AUSP	ATFLB	Currency Value - To (Floating Point)	S/4 Hana	AUSP	ATFLB	Currency Value - To (Floating Point)	Direct Mapping
16	PF2, WP2	AUSP	VALUE_CHAR	Characteristic Value	S/4 Hana	AUSP	VALUE_CHAR	Characteristic Value	Direct Mapping

3.b Functional Location Classification Transformation Rule (DCT)

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 Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	-	-	-	-	S/4 Hana	KSSK	KLART	Class Type	Default to '003'
3	-	-	-	-	S/4 Hana	KSSK	OBTAB	Name of Database Table for Object	Default to 'IFLOT'
4	DCT	KSSK	CLASSNUM	Class Name	S/4 Hana	KSSK	CLASSNUM	Class Name	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 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	IFLOT	TPLNR	Functional Location Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Direct Mapping
2	DCT	IHPA	PARVW	Partner Function	S/4 Hana	IHPA	PARVW	Partner Function	Direct Mapping
3	DCT	IHPA	PARNR	Partner	S/4 Hana	IHPA	PARNR	Partner	Direct Mapping

5. Functional Location User Status

5.a Functional Location 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	ENRICHMENT	ENR_Functional Location_TPLNR	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	IFLOT	TPLNR	Functional Location Label	Derive Target Functional Location Label based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
3	-	-	-	Status profile of the functional location	S/4 Hana	JSTO	STSMA	Status profile of the functional location	Default to 'ZEAMFL01'
4	PF2, WP2	JEST	STAT	Status Number in User Status List	S/4 Hana	JEST	STAT	Status Number in User Status List	Derive the User Status based on value mapping : User Status Function Location
5	-	-	-	-	S/4 Hana	JEST	INACT	Indicator: Status Is Inactive	Default to '' (Blank)

5.b Functional Location 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	IFLOT	TPLNR	Functional Location Number	Staging	IFLOT	TPLNR	Functional Location Number	Direct Mapping
2	-	-	-	-	S/4 Hana	JSTO	STSMA	Status profile of the functional location	Default to 'ZEAMFL01'
3	DCT	JEST	STAT	Status Number in User Status List	S/4 Hana	JEST	STAT	Status Number in User Status List	Direct Mapping
4	-	-	-	-	S/4 Hana	JEST	INACT	Indicator: Status Is Inactive	Default to '' (Blank)

6. Functional Location 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 'IFLOT'
2	ENRICHMENT	ENR_Functional Location_TPLNR	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	STXH	TDNAME	Name	Derive Target TDNAME (Functional Location Label) based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
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

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	-	-	-	-	S/4 Hana	STXL	TDOBJECT	Texts: application object	Default to 'IFLOT'
2	ENRICHMENT	ENR_Functional Location_TPLNR	zLegacyTPLNR	Legacy Functional Location Label	S/4 Hana	STXL	TDNAME	Name	Derive Target TDNAME (Functional Location Label) based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
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	PF2, WP2	STXL	TDFORMAT	Tag column	S/4 Hana	STXL	TDFORMAT	Tag column	Direct Mapping
7	PF2, WP2	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.

Transformation Mapping

Mapping Table Name	Mapping Table Description
EXC-Functional Location_ID	Functional Locations (Lowest Level) to be created as Equipment
ENR_Functional Location_TPLNR	Asset Level Functional Locations Labels created with Target Structure Indicator for corresponding Legacy Functional Location
Asset_Technical Object Type	Old to new Technical Object Type
ENR-Functional Location_Technical Object Type	These are Functional Locations that sites cannot update in the source systems due to the lack of selectable configuration options.
ENR-Functional Location_SortField	Sort Field Assignment to Functional Locations
Plant Section	Old to new Plant Section
ENR-Functional Location_Plant Section	Asset Functional Locations missing Plant Section in Legacy
Maintenance Planner Group	Old to New Planner Group
Work Center A2D	Old to new Work Centre A2D
Cost Center	Old to New Cost Center
Company Code	BUKRS: Old Companny Code to New Company Code
ENR-Functional Location_Installation Allowed	Installation Allowed Flag assignment to Functional Locations
ENR-Functional Location_Construction Type	Construction Type Assignment to Functional Locations
Controlling Area	Old to New Controlling Area
ENR-Functional Location_LTXT_Values	Weight of Object, Unit of Weight, Name 1, Name 2, Name 3, Name 4 information for Functional Location updated from Legacy Long Text
Class A2D	Old to New Class A2D
Characteristic A2D	Old to New Characteristic A2D
User Status Function Location	Old to New Functional Location User Status
Cost Center	Old to New Cost Center

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

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:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
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 Data Owner/s 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	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data).

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible
1	Ensure Pre-load sign-offs are obtained.	SyWay Data team
2	Go to the load tool and select the correct load Program.	SyWay Data team
3	Proceed with Data load.	SyWay Data team
4	Validate few records loaded by accessing standard transactions.	SyWay Data team
5	Generate the post load reports in the tool.	SyWay Data team
6	Log errors as defects, if any and address resolutions. Close defects.	SyWay Data team
7	Resolve defects by 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 : 1003 Functional Location and Partner Assignment

Pre-Cutover : 1003a Functional Location Classification

Pre-Cutover : 1003b Functional Location User Status

Pre-Cutover : 1003c Functional Location Long Text

Note: A separate load program may need to be created for 1003b and 1005c 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

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
11	TJ30 - User Status

Conversion Objects

Object #	Preceding Object Conversion Approach
1006	Work Centre
1074	Cost Center
1010	PM Assembly/ Construction Types
1015	Characteristics
1009	Class
3018	Business Partner - FI Vendor (FLVN00)

Error Handling

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	SyWay A2D Data team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue, or attempt to load the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	Verify that the 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.
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

Change log

Version	Published	Changed By
CURRENT (v. 91)	Apr 07, 2026 07:20	JOSHI-ext, Aditya
v. 440	Apr 06, 2026 10:52	PUN-ext, Eddy
v. 439	Apr 01, 2026 15:44	JOSHI-ext, Aditya
v. 438	Apr 01, 2026 15:06	JOSHI-ext, Aditya
v. 437	Apr 01, 2026 14:54	JOSHI-ext, Aditya
v. 436	Apr 01, 2026 09:05	JOSHI-ext, Aditya
v. 435	Apr 01, 2026 08:12	PUN-ext, Eddy
v. 434	Mar 31, 2026 15:51	JOSHI-ext, Aditya
v. 433	Mar 31, 2026 14:41	JOSHI-ext, Aditya
v. 432	Mar 31, 2026 09:29	JOSHI-ext, Aditya

Go to Page History

Workflow history

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

Apr 28, 2026	Actor	Type	Activity	Version
Approved	TAN-ext, Charmaine	State	changed state to Approved at 7:34 am (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v441
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 7:34 am [PMO Comments] Conversion Spec completed as per CS register and functional review completed
Apr 22, 2026
	PUN-ext, Eddy	Comment	commented 3:25 pm MOUSSA-ext, Eva
	MOUSSA-ext, Eva	State	changed expiry date to '29 Apr, 2026 07:31 am' at 7:31 am
	MOUSSA-ext, Eva	State	changed state to Lead Approval at 7:31 am	v441
Tech Review	MOUSSA-ext, Eva	State	gave Syniti Team Review approval at 7:31 am v.441
		State	changed expiry date to '27 Apr, 2026 07:30 am' at 7:30 am
		State	changed state to Tech Review at 7:30 am v.441	v441

Workflow history

Space shortcuts

Page tree

CNV-1003 Functional Location

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Extraction

Extraction Run Sheet

Data Collection Template (DCT)

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history