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 following diagram illustrates the conceptual structure of the Syensqo target asset hierarchy.

The data from legacy system includes:

Functional Location having Maintenance Plant (IFLOT-WERKS) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes')

On top of above the scope for Asset Functional Location shall be refined based on below scenarios subjected to:

Equipment (EQUI-EQUNR) Installed under Functional Location (IFLOT-TPLNR)
Maintenance existing for the Functional Location -
- Any Maintenance Item (MPOS-WAPOS) existing for Functional Location (IFLOT-TPLNR) where (MPOS-EQUNR) = '' and (MPOS-BAUTL) = ''
- Any Work Order (AFIH-AUFNR) existing for Functional Location (IFLOT-TPLNR) where (AFIH-EQUNR) = '' and (AFIH-BAUTL) = ''

Scenario	Asset Structure Setup	Maintenance Setup	Treatment
1	Functional Location has Equipment	Maintenance present or not	Create AFLOC2 at Fn. Create AFLOC1 at Fn-1 (always, regardless of EQ/maintenance on Fn-1). All ancestors above Fn-1 (Fn-2, Fn-3, …) if they have Equipment under it or maintenance associated, flag in the Cleansing Report (1003-005), else flag in Cleansing Report (1003-006) If Fn-1 is missing in legacy, flag “Missing Fn-1” in the Cleansing Report (1003-007). Stop.
2	Functional Location has no Equipment	Maintenance present	Create Equipment at Fn. Create AFLOC2 at Fn-1. Create AFLOC1 at Fn-2. All ancestors above Fn-2 if they have Equipment under it or maintenance associated, flag in the Cleansing Report (1003-005), else flag in Cleansing Report (1003-006) If Fn-1 and/or Fn-2 is missing, flag the missing level(s) in the Cleansing Report (1003-007). Stop.
3	Functional Location has no Equipment	Maintenance not present	Exclude Fn and note “No EQ/MI/WO – Business review if required for Target” in the Cleansing Report. Move up to Fn-1 and re-evaluate: If Fn-1 has Equipment → apply Scenario 1 with Fn-1 as the current lowest level. If Fn-1 has Maintenance but no Equipment → apply Scenario 2 with Fn-1 as the current lowest level. If Fn-1 has neither → exclude Fn-1 and continue to Fn-2, etc. If you reach the top with no match, exclude the entire chain and keep it in the Cleansing Report for Business/DCT decision (1003-006).

Legend-

Fn: The lowest (deepest) Functional Location in the evaluated chain (the starting point).
Fn-1: The immediate parent of Fn (one level above).
Fn-2: The grandparent of Fn (two levels above).
Fn-n: Continue upward accordingly (Fn-3, Fn-4, …) until the topmost legacy Functional Location is reached.
Ancestors above X: All levels strictly higher than X (e.g., “above Fn-1” = Fn-2, Fn-3, … top).
AFLOC1 = Asset Functional Location (level 1) in target
AFLOC2 = Asset Functional Location (level 2) in target

An initial relevancy report shall be generated based on the above scenarios to manage the transformation. Report shall contain the below columns.

Column Name	Details
Source System	Values: PF2 or WP2 Rule: Copy from the record’s source. If the legacy record comes from PF2, set PF2; if from WP2, set WP2.
Legacy Functional Location	Values: Legacy Functional Location for Fn, Fn-1, Fn-2, … (one row per evaluated level) Rule: Populate the exact legacy functional location only for levels where a target object being registered (FL or EQ). If no object is registered at a level (excluded/missing), Check if the Legacy Functional Location has Equipment under it or maintenance associated. If 'True' then output a row with all the remaining columns blank, else do not output a row for that level and include it in the Cleansing Report.
Has Equipment Under?	Values: X or blank Rule: X if the legacy FLOC at this row has at least one Equipment installed beneath it (per legacy hierarchy). Else blank. (Used only for rows you output—i.e., where you register a target object.)
Has Maintenance Associated?	Values: X or blank Rule: X if the legacy FLOC at this row has any MI/WO linked (status any; exclude standing orders if that policy applies).Else blank. (Used only for rows you output—i.e., where you register a target object.)
Proposed New Technical Object	Values: EQ, FL Rule (evaluate in this order at the current level, include bubble-up): Start at Fn and test these in order: Has Equipment (maintenance irrelevant) → FL (this will be AFLOC2 at Fn) and also create FL at Fn-1 (AFLOC1). Stop; flag ancestors above Fn-1. No Equipment, Has Maintenance → at Fn: EQ; at Fn-1: FL (AFLOC2); at Fn-2: FL (AFLOC1). Stop; flag ancestors above Fn-2. No Equipment and No Maintenance → no object at Fn (leave blank for Fn); bubble-up to Fn-1 and re-apply the same checks. If Fn doesn’t satisfy any scenario, check Fn-1, then Fn-2, and so on until a rule matches or the top is reached. If no level satisfies any scenario, list the chain for Business/DCT in the Cleansing Report. Missing parents (Fn-1/Fn-2): create whatever objects are possible at available levels; record missing levels in the Cleansing Report. Once a FLOC2 is derived at any level, all higher ancestors should be checked for Equipment installed or maintenance associated. If 'True' then output a row with just Source System and Legacy Functional Location column populated, else do not output a row for that level and include it in the Cleansing Report.
New Category	Values: A or blank Rule: Set A if New Technical Object = 'FL' (applies to both AFLOC1 and AFLOC2). Otherwise leave blank (e.g., when EQ or excluded).

The data from legacy system excludes:

Functional Location (IFLOT-TPLNR) with System Status (JEST-STAT) Inactive 'INAC'
Functional Location (IFLOT-TPLNR) with System Status (JEST-STAT) Deletion Flag 'DLFL'
Functional Location (IFLOT-TPLNR) having Description (IFLOTX-PLTXT) containing words ('To be Deleted', 'DELETE')
Functional Location (IFLOT-TPLNR) placed below the Functional Locations included in exclusion criteria 1-3
Functional Location (IFLOT-TPLNR) to be migrated as Equipment which are part of Exclusion List (OTH-Functional Location, where New Technical Object = 'EQ')
Functional Location (IFLOT_TPLNR) which are part of Cleansing Reports 1003-06 and 1003-07

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	Relevant Asset Level Functional Locations will be extracted from PF2 and WP2. An initial extract of the relevant asset-level Functional Locations will be provided in a Google Sheet format to assist the business in decision-making for the to-be technical object type of the extracted Functional Locations (I.e. To be created as Functional Location / Equipment).	75,000	S/4HANA	75,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 KDD085 - 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	Conditional
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	Conditional
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
IFLOT	IWERK	IWERK	Planning Plant	CHAR	80	Conditional
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	System
ILOA	KOSTL	KOSTL	Cost Center	CHAR	80	Conditional
IFLOT	TPLMA	TPLMA	Superior Functional Location	CHAR	80	Conditional
IFLOT	IEQUI	IEQUI	Equipment Installation Is 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 and 1 entry for the language(s) of the country in which each Maintenance Plant assigned is located (French, Italian, Mandarin, Brazilian Portuguese, German or Spanish).

3. 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	CLASS	CLASS	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	CURRENCY	CURRENCY	Currency Key	CUKY	5	Conditional
AUSP	ATWRT	ATWRT	Characteristic Value	CHAR	30	Conditional

5. Functional Location Partner

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
IFLOT	TPLNR	TPLNR	Functional Location	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
IFLOT	TPLNR	TPLNR	Functional Location	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

7. Functional Location Long Text Header

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
IFLOT	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory
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
IFLOT	TPLNR	TPLNR	Functional Location	CHAR	30	Mandatory
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	Asset (Category 'A') relevant Functional Location missing Technical Object Type	Functional Location (AFLOC1/ AFLOC2) as per Relevancy Criteria with no Technical Object Type Assigned	Plant, Functional Location, Functional Description, Technical Object Type	PF2, WP
1003-002	C1	Asset (Category 'A') Level 2 relevant Functional Location missing Planner Group	Functional Location (AFLOC2) as per Relevancy Criteria with no Planner Group Assigned	Plant, Functional Location, Functional Description	PF2, WP2
1003-003	C2	Asset (Category 'A') relevant Functional Location maintaining Acquisition Value but missing Currency Key	Functional Location as per relevancy criteria where IFLOT_ANSWT <> '' (Blank) and IFLOT_WAERS = '' (Blank)	Plant, Functional Location, Functional Description, Superior Functional Location, Acquisition Value	PF2, WP2
1003-004	C3	Info Report : Asset (Category 'A') relevant Functional Location (Category 'A') Long Text for Cleansing	Functional Location as per Relevancy Criteria where Long Text Exist flag is assigned (IFLOTX-KZLTX) = 'X'. This is for manual review.	Plant, Functional Location, Functional Description, Long Text	PF2, WP2
1003-005	C3	Info Report: Active Functional Location not being migrated but have Equipment installed or maintenance associated	Functional Location as per Relevancy Criteria not being mapped to a Asset Functional Location (AFLOC1/ AFLOC2) but have Equipment installed or maintenance associated	Plant, Functional Location, Functional Description, Superior Functional Location	PF2, WP2
1003-006	C3	Info Report: Active Functional Location not being migrated which don't have Equipment installed or maintenance associated	Functional Location as per Relevancy Criteria not being mapped to a Asset Functional Location (AFLOC1/ AFLOC2) which don't have Equipment installed or maintenance associated	Plant, Functional Location, Functional Description, Superior Functional Location	PF2, WP2
1003-007	C3	Info Report: Floating Asset (Category 'A') relevant Functional Location	Functional Location as per the relevancy criteria not having any Superior Functional	Plant, Functional Location, Functional Description	PF2, WP2
1003-008	C3	Info Report: Asset (Category 'A') relevant Functional Location missing Description in English Language	Functional Location as per the relevancy criteria missing entries in IFLOTX where IFLOTX-SPRAS <> 'E'	Plant, Functional Location, Functional Description, Superior Functional Location, Language Key	PF2, WP2
1003-009	C3	Info Report: Functional Locations associated with incomplete or broken active Asset Structures	Functional Location belonging to a superior Functional Location Hierarchy which belongs to below criteria: Functional Location with System Status (JEST-STAT) Inactive 'INAC' Functional Location with System Status (JEST-STAT) Deletion Flag 'DLFL' Functional Location having Description containing words ('To be Deleted', 'DELETE')	Plant, Functional Location, Functional Description, Superior Functional Location	PF2, WP2

Note: List of Cleansing is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Conversion Process

The high-level process is represented by the diagram below:

1. Source = PF2/WP2:

2. Source = DCT

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 A/CTs that need to be created to support the to-be design

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
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on criteria mentioned in the relevancy criteria.	SyWay Data Team

Selection Screen

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

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for 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 Data Construction Rules

Data Element	Field Description	Rule
TPLNR	Functional Location	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
FLTYP	Category	Mandatory Allowed values for each Level of the Functional Location Structure: O - Org N - Nav A - Asset
EQART	Object Type	Conditional Must be populated for Category 'A' Functional Locations. Allowed values from T370K to be populated. Category 'O' and 'N' : User to populate values if applicable.
HERST	Manufacturer	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be left' Blank'.
TYPBZ	Model Number	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be left' Blank'.
MAPAR	Manufacturer Part Number	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be left' 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 left' Blank'.
BAUJJ	Year of Construction	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be left' Blank'.
BAUMM	Month of Construction	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be left' Blank'.
SERGE	Manufacturer Serial Number	Conditional User to populate value only for Category 'A' Functional Locations. Category 'O' and 'N' Functional Locations to be left' 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	Conditional User must populate value only for Category ('A', 'N') Functional Locations and Category 'O' Level 3 Functional Locations. Allowed values: List from Value Mapping - Plant where Maintenance Plant = Yes Category 'O' Level 1 and 2 Functional Locations to be left 'Blank'.
EQFNR	Sort Field	Conditional User must populate value only for Category 'A' Functional Locations. Sort Field is used to store the Plant Tag ID. Category 'O' and 'N' Functional Locations to be assigned value if available, else left 'Blank'. Sort Field + Maintenance Plant should be unique combination.
BEBER	Plant Section	Conditional User must populate value only for Category 'A' Functional Locations. Allowed values from T357 to be populated. Category 'O' and 'N' Functional Locations to be left' Blank'.
INGRP	Planner Group	Conditional User must populate value only for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X'. Allowed values from T024I to be populated Category 'O' and 'N' Functional Locations to be left' Blank'.
GEWRK	Maintenance Work Center	Conditional User must populate value for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X'. Allowed values from Work Centre DCT to be populated. Category 'O' and 'N' Functional Locations to be left' Blank'.
zLegacyKOSTL	Cost Center	Conditional User must populate value for all Category 'A' Functional Locations. Allowed Values: maintained in R2R Cost Centre Value Mapping Category 'O' and 'N' Functional Locations to be left' Blank'.
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
IEQUI	Equipment Installation Is Allowed	Conditional Indicator (check box). User to populate value 'X' only for Level 2 Category 'A' Functional Locations if Equipment exists below it. Category 'O' and 'N' Functional Locations to be left' Blank'. Else populate value '' (Blank)
SUBMT	Construction Type	Conditional User must populate value for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X'. Allowed values from Assembly DCT to be populated Assigned Construction Type should have a TOT Characteristic value maintained which matches the 'Object Type' assigned on the Functional Location Category 'O' and 'N' Functional Locations to be left' Blank'.
BRGEW	Weight of Object	Conditional User to populate value for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X' Category 'O' and 'N' Functional Locations to be left' Blank'.
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 NAME1-4 fields with the Name and Location of the Asset for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X'. Category 'O' and 'N' Functional Locations to be left' Blank'.
NAME2	Name 2	Conditional User to populate NAME1-4 fields with the Name and Location of the Asset for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X'. Category 'O' and 'N' Functional Locations to be left' Blank'.
NAME3	Name 3	Conditional User to populate NAME1-4 fields with the Name and Location of the Asset for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X'. Category 'O' and 'N' Functional Locations to be left' Blank'.
NAME4	Name 4	Conditional User to populate NAME1-4 fields with the Name and Location of the Asset for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X'. Category 'O' and 'N' Functional Locations to be left' Blank'.
PLTXT_EN	Description of Functional Location (English)	Mandatory Guide for Description for Functional Location: For Category 'O' and 'N' Functional Locations - As provided by Business For Category 'A' Functional Location- A = Technical Object Type Description (in English language) B = Asset Tag (Sort Field) C = Additional Description as provided by business (in English Language) Functional Location Description = A+B+C Cannot have duplicate records based on corresponding language text (2 A/CT cannot have the same English language key texts) 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
SPRAS_LC	Language Key_Local	Conditional User to populate Language Key based language of the Country where the Maintenance Plant exists. Allowed values: 1. "F" - French 2. "1" - Mandarin/Simplified Chinese 3. "I' - Italian 4. "P" - Portuguese/Brazilian 5. "D" - German 6. "S" - Spanish
PLTXT_LC	Description of Functional Location (Local Language)	Conditional Guide for Description for Functional Location: For Category 'O' and 'N' Functional Locations - As provided by Business For Category 'A' Functional Location- A = Technical Object Type Description (in Local Language of Plant) B = Asset Tag (Sort Field) C = Additional Description as provided by business (in language of the country in which each plant is located) Functional Location Description = A+B+C Cannot have duplicate records based on corresponding language text (2 A/CT cannot have the same English language key texts) 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
zLegacyPARNR_Z1	Partner (Asset Owner)	Conditional User to populate 'Z1' (Asset Owner) Vendor Business Partner for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X' Rule - For Assets that are Owned by Syensqo and Maintained by Syensqo Inter Company Vendor are to be populated. For Assets that are rented from specific vendors or maintained by third-party service providers, external Vendors are to be populated
zLegacyPARNR_Z2	Partner (Asset Maintainer)	Conditional User to populate 'Z2' (Asset Maintainer) Vendor Business Partner for Level 2 Category 'A' Functional Locations where 'Equipment Installation Is Allowed' field has not been assigned as 'X' Rule - For Assets that are Owned by Syensqo and Maintained by Syensqo Inter Company Vendor are to be populated. For Assets that are rented from specific vendors or maintained by third-party service providers, external Vendors are to be populated
STAT	Status Number in User Status List	Conditional User to populate appropriate status included in Status Profile mentioned below for Category 'A' Functional Locations. Note: This will be set to 'PLAN' if no value is provided Allowed values from below to be populated: 'PLAN'- Planned 'COMM'- Commissioned 'INSR'- In Service 'OTSR'- Out Of Service 'SCRP'- Scrap 'EXHZ'- Extremely Hazardous 'MTNA'- Maintenance Not Allowed

2. Functional Location Classification Data Construction Rules

Data Element	Field Description	Rule
TPLNR	Functional Location	Mandatory Key to link to Functional Location Should exist in Functional Location Master DCT Rules
CLASS	Class Name	Mandatory Must always have an always an entry for EAM_9999. User to populate any other class as required Class other than 'EAM_9999' must have naming convention = TOT (Tech Object Type) of the Floc
ATINN	Characteristic Name	Mandatory User to populate Characteristic assigned to the Class 'EAM_9999' and other mapped legacy classes as per the Class DCT
ATWRT	Characteristic Value	Conditional. If the characteristic has character format (CHAR), populate with alphanumeric characters.
ATWRT_FR	Characteristic Value (From)	Conditional. If the characteristic has character format (DATE), must have the format DDMMYYYY. E.g. 31122000 If the characteristic has character format (TIME), must have the format HHMMSS. E.g. 110000 If the characteristic has character format (NUM), the field should contain only numerical characters. E.g. 888 If the characteristic has character format (CURR), this field should contain only numerical characters. E.g. 200 Note for DATE, TIME, NUM and CURR formats: If a range is required, the from and to values should be concatenated using a hyphen (" - "). E.g. DATE: 1 - 2, 110000 -112855 Fill in only if Characteristic - Interval values allowed (ATINT) is populated with "X" The Characteristic Value (From) should be <= Characteristic Value (To)
ATWRT_TO	Characteristic Value (To)	Conditional. If the characteristic has character format (DATE), must have the format DDMMYYYY. E.g. 31122000 If the characteristic has character format (TIME), must have the format HHMMSS. E.g. 110000 If the characteristic has character format (NUM), the field should contain only numerical characters. E.g. 888 If the characteristic has character format (CURR), this field should contain only numerical characters. E.g. 200 Note for DATE, TIME, NUM and CURR formats: If a range is required, the from and to values should be concatenated using a hyphen (" - "). E.g. DATE: 1 - 2, 110000 -112855 Fill in only if Characteristic - Interval values allowed (ATINT) is populated with "X" The Characteristic Value (From) should be <= Characteristic Value (To)

3. Functional Location Long Text Data Construction Rules

Data Element	Field Description	Rule
TPLNR	Functional Location	Mandatory Key to link to Functional Location Should exist in Functional Location Master DCT Rules
TDLINE_EN	Text Line (English)	Conditional User to populate Free Text in English Language as applicable
TDSPRAS_LC	Language Key_Local	Conditional User to populate Language Key based language of the Country where the Maintenance Plant exists. Allowed values: 1. "E" - English 2. "F" - French 3. "1" - Mandarin/Simplified Chinese 4. "I' - Italian 5. "P" - Portuguese/Brazilian 6. "D" - German 7. "S" - Spanish
TDLINE_LC	Text Line (Local Language)	Conditional User to populate Free Text in language of the country in which each plant is located (French, Italian, Mandarin, Brazilian Portuguese, German or Spanish).

4. OTH-Functional Location Data Construction Rules

Data Element	Field Description	Rule
zLegacySource	Source System	Mandatory Allowed Values: 'PF2' or 'WP2' This is non editable field.
zLegacyTPLNR	Legacy Functional Location	Mandatory Values: Legacy Functional Location This is a non editable field.
EQUIP_EXIST	Has Equipment Under?	Mandatory Values: 'X' or blank This is a non editable field.
MAINT_EXIST	Has Maintenance Associated?	Mandatory Values: 'X' or blank This is a non editable field.
PRP_OBJECT	Proposed New Technical Object	Mandatory Values: 'EQ', 'FL' This is a non editable field.
TGT_CAT	New Category	Mandatory Values: 'A' or blank This is a non editable field.
TGT_LVL	New FL Level	Mandatory Values: '1', '2' or blank This is a non editable field.
FIN_OBJECT	New Technical Object	Mandatory Allowed Values: 'EQ', 'FL' User to populate same value as PRP_OBJECT if acceptable else assign appropriate allowed value.
TGT_TPLNR	New Functional Location	Optional Allowed Values: Target Functional Location User to populate the value from Functional Location DCT
TGT_TPLMA	New Superior Functional Location	Optional Allowed Values: Target Functional Location User to populate the value from Functional Location DCT
BUS_VERF	Business Verified	Mandatory Allowed Values: 'Yes', 'No', 'Not Applicable' User to populate 'X' if Legacy-Target mapping is acceptable.

Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Extraction Dependencies

Item #	Step Description	Team Responsible
Not Applicable

Transformation

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

Perform value mapping and data transformation rules.
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 – Functional Location	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 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	Legacy Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	Value Mapping: OTH-Functional Location
2	-	-	-	-	S/4 Hana	IFLOT	TPLKZ	Structure Indicator	Default to 'SAST'
3	-	-	-	-	S/4 Hana	IFLOT	FLTYP	Category	Default to 'A'
4	-	-	-	-	S/4 Hana	IFLOT	INBDT	Start-Up Date	If IEQUI for the Functional Location ='' (Blank) and derived Target User Status for Functional Location as Functional Location User Status (STAT) Transformation Rules (ECC) = 'COMM' (Commissioned), then assign the date as per Value mapping : OTH_Migration_Date Relevant Values A2D (where Object ID "1003" and Field Name = "IFLOT-INBDT". Else leave blank
5	PF2, WP2	IFLOT	EQART	Object Type	S/4 Hana	IFLOT	EQART	Object Type	Value mapping : Asset_Technical Object Type Overwrite with DCT if provided (as part of enrichment)
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	ILOA	SWERK	Maintenance Plant	Value Mapping: Plant (Maintenance Plant = Yes)
16	PF2, WP2	ILOA	EQFNR	Sort Field	S/4 Hana	IFLOT	EQFNR	Sort Field	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
17	PF2, WP2	ILOA	BEBER	Plant Section	S/4 Hana	IFLOT	BEBER	Plant Section	Value mapping : Plant Section Overwrite with DCT if provided (as part of enrichment)
18	-	-	-	-	S/4 Hana	IFLOT	ABCKZ	ABC Indicator	Derive the Indicator based on below logic - Aggregate values for all Characteristics assigned for the Functional Location as per Characteristics DCT which are relevant for Asset Criticality Analysis i.e where CABN_ATKLA = 'XX_XXXX' Derive ABC Indicator value by applying the below categorization 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' Note: Open Item PDM-961 tracking the Configuration
19	PF2, WP2	IFLOT	INGRP	Planner Group	S/4 Hana	ILOA	INGRP	Planner Group	Value mapping : Maintenance Planner Group Overwrite with DCT if provided (as part of enrichment)
20	PF2, WP2	ILOA	IWERK	Planning Plant	S/4 Hana	IFLOT	IWERK	Planning Plant	Value Mapping: Plant (Maintenance Plant = Yes)
21	PF2, WP2	ILOA	GEWRK	Maintenance Work Center	S/4 Hana	ILOA	GEWRK	Maintenance Work Center	Value mapping : Work Center A2D Overwrite with DCT if provided (as part of enrichment)
22	PF2, WP2	ILOA	WERGW	Work Center Plant	S/4 Hana	ILOA	WERGW	Work Center Plant	Value Mapping: Plant (Maintenance Plant = Yes)
23	-	-	-	-	S/4 Hana	ILOA	BUKRS	Company Code	Derive the Company code from table 'T001K' where Target IFLOT_SWERK (Maintenance Plant) = T001K_BWKEY
24	PF2, WP2	ILOA	KOSTL	Cost Center	S/4 Hana	ILOA	KOSTL	Cost Center	Value mapping : Cost Center Overwrite with DCT if provided (as part of enrichment)
25	PF2, WP2	IFLOT	TPLMA	Superior Functional Location	S/4 Hana	ILOA	TPLMA	Superior Functional Location	Value Mapping: OTH-Functional Location
26	PF2, WP2	ILOA	IEQUI	Equipment Installation Is Allowed	S/4 Hana	ILOA	IEQUI	Indicator: Installation Allowed	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
27	PF2, WP2	ILOA	SUBMT	Construction Type	S/4 Hana	ILOA	SUBMT	Construction Type	Value Mapping :Assembly and Construction Type Overwrite with DCT if provided (as part of enrichment)
28	-	-	-	-	S/4 Hana	ILOA	KOKRS	Controlling Area	Default to 'CO01' (SYSQ Controlling Area)
29	PF2, WP2	IFLOT	BRGEW	Weight of Object	S/4 Hana	IFLOT	BRGEW	Weight of Object	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
30	PF2, WP2	IFLOT	GEWEI	Unit of Weight	S/4 Hana	IFLOT	GEWEI	Unit of Weight	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
31	PF2, WP2	ADRC	NAME1	Name 1	S/4 Hana	ADRC	NAME1	Name 1	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
32	PF2, WP2	ADRC	NAME2	Name 2	S/4 Hana	ADRC	NAME2	Name 2	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
33	PF2, WP2	ADRC	NAME3	Name 3	S/4 Hana	ADRC	NAME3	Name 3	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
34	PF2, WP2	ADRC	NAME4	Name 4	S/4 Hana	ADRC	NAME4	Name 4	Direct Mapping Overwrite with DCT if provided (as part of enrichment)
35	-	-	-	-	S/4 Hana	ADRC	COUNTRY	Country/Region Key	Derive Country/ Region from Table T001W where Target SWERK (Maintenance Plant) = T001K_WERKS

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	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	Direct Mapping
2	-	-	-	-	S/4 Hana	IFLOT	TPLKZ	Structure Indicator	Derive based on logic: If FLTYP = 'O' then TPLKZ = 'SORG' If FLTYP = 'N' then TPLKZ = 'SNAV'
3	DCT	IFLOT	FLTYP	Category	S/4 Hana	IFLOT	FLTYP	Category	Direct Mapping
4	-	-	-	-	S/4 Hana	IFLOT	INBDT	Start-Up Date	If FLTYP = 'O' or 'N' then INBDT = ' ' (Blank) Else Derive the date as per Value mapping : OTH_Migration_Date Relevant Values A2D (where 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	-	-	-	-	S/4 Hana	IFLOT	ABCKZ	ABC Indicator	Derive the Indicator based on below logic - Aggregate values for all Characteristics assigned for the Functional Location as per Characteristics DCT which are relevant for Asset Criticality Analysis i.e where CABN_ATKLA = 'XX_XXXX' Derive ABC Indicator value by applying the below categorization 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' Note: Open Item PDM-961 tracking the Configuration
19	DCT	ILOA	INGRP	Planner Group	S/4 Hana	ILOA	INGRP	Planner Group	Direct Mapping
20	-	-	-	-	S/4 Hana	IFLOT	IWERK	Planning Plant	Copy the same value as Target SWERK (Maintenance Plant)
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	Copy the same value as Target SWERK (Maintenance Plant)
23	-	-	-	-	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	zLegacyKOSTL	Cost Center	S/4 Hana	ILOA	KOSTL	Cost Center	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	Equipment Installation Is Allowed	S/4 Hana	ILOA	IEQUI	Indicator: Installation Allowed	Direct Mapping
27	DCT	ILOA	SUBMT	Construction Type	S/4 Hana	ILOA	SUBMT	Construction Type	Value Mapping :Assembly and Construction Type
28	-	-	-	-	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	-	-	-	-	S/4 Hana	ADRC	COUNTRY	Country/Region Key	Derive Country/ Region from Table T001W where Target SWERK (Maintenance Plant) = T001K_WERKS

3. Functional Location Short Text Transformation Rule (ECC)

Rule #

Source system

Source Table

Source Field

Source Description

Target System

Target Table

Target Field

Target Description

Transformation Logic

1

PF2, WP2

IFLOT

TPLNR

Legacy Functional Location

S/4 Hana

IFLOT

TPLNR

Functional Location

Value Mapping: OTH-Functional Location Mapping

2

PF2, WP2

IFLOTX

SPRAS

Language Key

S/4 Hana

IFLOTX

SPRAS

Language Key

Direct Mapping

3

PF2, WP2

IFLOTX

PLTXT

Description of Functional Location

S/4 Hana

IFLOTX

PLTXT

Description of Functional Location

Direct Mapping

Overwrite with DCT if provided (as part of enrichment)

4. 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	S/4 Hana	IFLOT	TPLNR	Functional Location	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	S/4 Hana	IFLOT	TPLNR	Functional Location	Direct Mapping
2	DCT	IFLOTX	SPRAS_LC	Language Key	S/4 Hana	IFLOTX	SPRAS	Language Key	Direct Mapping
3	DCT	IFLOTX	PLTXT_LC	Description of Functional Location (Local Language of Plant)	S/4 Hana	IFLOTX	PLTXT	Description of Functional Location	Direct Mapping

5. 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	PF2, WP2	IFLOT	TPLNR	Legacy Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	Value Mapping: OTH-Functional Location
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	CLASS	Class Name	S/4 Hana	KSSK	CLASS	Class Name	Value mapping : Class A2D
5	PF2, WP2	AUSP	ATINN	Characteristic Name	S/4 Hana	AUSP	ATINN	Characteristic Name	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	DATE_FROM	Lower Boundary for Date - Interval	S/4 Hana	AUSP	DATE_FROM	Lower Boundary for Date - Interval	Direct Mapping
10	PF2, WP2	AUSP	DATE_TO	Upper Boundary for Date - Interval	S/4 Hana	AUSP	DATE_TO	Upper Boundary for Date - Interval	Direct Mapping
11	PF2, WP2	AUSP	TIME_FROM	Lower Boundary for Time - Interval	S/4 Hana	AUSP	TIME_FROM	Lower Boundary for Time - Interval	Direct Mapping
12	PF2, WP2	AUSP	TIME_TO	Upper Boundary for Time - Interval	S/4 Hana	AUSP	TIME_TO	Upper Boundary for Time - Interval	Direct Mapping
13	PF2, WP2	AUSP	ATFLV	Currency Value - From (Floating Point)	S/4 Hana	AUSP	ATFLV	Currency Value - From (Floating Point)	Direct Mapping
14	PF2, WP2	AUSP	ATFLB	Currency Value - To (Floating Point)	S/4 Hana	AUSP	ATFLB	Currency Value - To (Floating Point)	Direct Mapping
15	PF2, WP2	AUSP	CURRENCY	Currency Key	S/4 Hana	AUSP	CURRENCY	Currency Key	Direct Mapping
16	PF2, WP2	AUSP	ATWRT	Characteristic Value	S/4 Hana	AUSP	ATWRT	Characteristic Value	Direct Mapping

6. Functional Location Classification Transformation Rule (DCT)

Only get the records where Characteristics with Data Type = CHAR

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	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	CLASS	Class Name	Direct Mapping
5	DCT	AUSP	ATINN	Characteristic Name	S/4 Hana	AUSP	ATINN	Characteristic Name	Direct Mapping
6	DCT	AUSP	ATWRT	Characteristic Value	S/4 Hana	CAWN	ATWRT	Characteristic Value	Direct Mapping

Only get the records where Characteristics with Data Type = CURR

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	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	CLASS	Class Name	Direct Mapping
5	DCT	AUSP	ATINN	Characteristic Name	S/4 Hana	AUSP	ATINN	Characteristic Name	Direct Mapping
6	DCT	AUSP	ATWRT_FR	Characteristic Value (From)	S/4 Hana	CAWN	ATFLV	Characteristic Value	Direct Mapping
7	DCT	AUSP	ATWRT_TO	Characteristic Value (To)	S/4 Hana	CAWN	ATFLB	Characteristic Value	Direct Mapping
8	DCT	AUSP	CURRENCY	Currency Key	S/4 Hana	AUSP	CURRENCY	Currency Key	Derive from Currency Key of the Characteristics

Only get the records where Characteristics with Data Type = DATE

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	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	CLASS	Class Name	Direct Mapping
5	DCT	AUSP	ATINN	Characteristic Name	S/4 Hana	AUSP	ATINN	Characteristic Name	Direct Mapping
6	DCT	AUSP	ATWRT_FR	Characteristic Value (From)	S/4 Hana	CAWN	DATE_FROM	Characteristic Value	Direct Mapping
7	DCT	AUSP	ATWRT_TO	Characteristic Value (To)	S/4 Hana	CAWN	DATE_TO	Characteristic Value	Direct Mapping

Only get the records where Characteristics with Data Type = NUM

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	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	CLASS	Class Name	Direct Mapping
5	DCT	AUSP	ATINN	Characteristic Name	S/4 Hana	AUSP	ATINN	Characteristic Name	Direct Mapping
6	DCT	AUSP	ATWRT_FR	Characteristic Value (From)	S/4 Hana	CAWN	ATFLV	Characteristic Value	Direct Mapping
7	DCT	AUSP	ATWRT_TO	Characteristic Value (To)	S/4 Hana	CAWN	ATFLB	Characteristic Value	Direct Mapping

Only get the records where Characteristics with Data Type = TIME

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	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	CLASS	Class Name	Direct Mapping
5	DCT	AUSP	ATINN	Characteristic Name	S/4 Hana	AUSP	ATINN	Characteristic Name	Direct Mapping
6	DCT	AUSP	ATWRT_FR	Characteristic Value (From)	S/4 Hana	CAWN	TIME_FROM	Characteristic Value	Direct Mapping
7	DCT	AUSP	ATWRT_TO	Characteristic Value (To)	S/4 Hana	CAWN	TIME_TO	Characteristic Value	Direct Mapping

7. 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	S/4 Hana	IFLOT	TPLNR	Functional Location	Direct Mapping
2	-	-	-	-	S/4 Hana	IHPA	OBTYP	Object Type	Default to 'IFL'
3	-	-	-	-	S/4 Hana	IHPA	PARVW	Partner Function	Default to 'Z1' (Asset Owner)
4	DCT	IHPA	zLegacyPARNR_Z1	Partner (Asset Owner)	S/4 Hana	IHPA	PARNR	Partner	Direct Mapping Overwrite with DCT if provided (as part of enrichment)

UNION

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	Direct Mapping
2	-	-	-	-	S/4 Hana	IHPA	OBTYP	Object Type	Default to 'IFL'
3	-	-	-	-	S/4 Hana	IHPA	PARVW	Partner Function	Default to 'Z2' (Asset Maintainer)
4	DCT	IHPA	zLegacyPARNR_Z2	-	S/4 Hana	IHPA	PARNR	Partner	Direct Mapping Overwrite with DCT if provided (as part of enrichment)

8. 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	PF2, WP2	IFLOT	TPLNR	Legacy Functional Location	S/4 Hana	IFLOT	TPLNR	Functional Location	Value Mapping: OTH-Functional Location
3	-	-	-	-	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	Value Mapping : User Status Functional Location Overwrite with DCT if provided (as part of enrichment)
5	-	-	-	-	S/4 Hana	JEST	INACT	Indicator: Status Is Inactive	Default to '' (Blank)

9. 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	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	Default to 'MNTA' (Maintenance Not Allowed) for Category 'O' and 'N' Functional Locations Else Direct Mapping
4	-	-	-	-	S/4 Hana	JEST	INACT	Indicator: Status Is Inactive	Default to '' (Blank)

10. 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	PF2, WP2	IFLOT	TPLNR	Legacy Functional Location	S/4 Hana	STXH	TDNAME	Name	Value Mapping: OTH-Functional Location (New Functional Location)
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

11. Functional Location Long Text Header (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 Hana	STXH	TDOBJECT	Texts: application object	Default to 'IFLOT'
2	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	STXH	TDNAME	Name	Direct Mapping
3	-	-	-	-	S/4 Hana	STXH	TDID	Text ID	Default to 'LTXT'
4	DCT	STXH	TDSPRAS	Language Key	S/4 Hana	STXH	TDSPRAS	Language Key	Default to 'E'

UNION

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 Hana	STXH	TDOBJECT	Texts: application object	Default to 'IFLOT'
2	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	STXH	TDNAME	Name	Direct Mapping
3	-	-	-	-	S/4 Hana	STXH	TDID	Text ID	Default to 'LTXT'
4	DCT	STXH	TDSPRAS_LC	Language Key	S/4 Hana	STXH	TDSPRAS	Language Key	Direct Mapping

12. Functional Location Long Text Line (ECC)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 Hana	STXL	TDOBJECT	Texts: application object	Default to 'IFLOT'
2	PF2, WP2	IFLOT	TPLNR	Legacy Functional Location	S/4 Hana	STXH	TDNAME	Name	Value Mapping: OTH-Functional Location (New Functional Location)
3	-	-	-	-	S/4 Hana	STXL	TDID	Text ID	Default to 'LTXT'
5	PF2, WP2	STXH	TDSPRAS	Language Key	S/4 Hana	STXL	TDSPRAS	Language Key	Direct Mapping
6	-	-	-	-	S/4 Hana	STXL	TDFORMAT	Tag column	Default to "*"
7	PF2, WP2	STXL	TDLINE	Text Line	S/4 Hana	STXL	TDLINE	Text Line	Direct Mapping

13. Functional Location Long Text Line (DCT)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 Hana	STXH	TDOBJECT	Texts: application object	Default to 'IFLOT'
2	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	STXH	TDNAME	Name	Direct Mapping
3	-	-	-	-	S/4 Hana	STXH	TDID	Text ID	Default to 'LTXT'
5	DCT	STXH	TDSPRAS	Language Key	S/4 Hana	STXH	TDSPRAS	Language Key	Default to 'E'
6	-	-	-	-	S/4 Hana	STXL	TDFORMAT	Tag column	Default to "*"
7	DCT	STXL	TDLINE_EN	Text Line	S/4 Hana	STXL	TDLINE	Text Line	Direct Mapping

UNION

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	-	-	-	-	S/4 Hana	STXH	TDOBJECT	Texts: application object	Default to 'IFLOT'
2	DCT	IFLOT	TPLNR	Functional Location	S/4 Hana	STXH	TDNAME	Name	Direct Mapping
3	-	-	-	-	S/4 Hana	STXH	TDID	Text ID	Default to 'LTXT'
5	DCT	STXH	TDSPRAS_LC	Language Key	S/4 Hana	STXH	TDSPRAS	Language Key	Direct Mapping
6	-	-	-	-	S/4 Hana	STXL	TDFORMAT	Tag column	Default to "*"
7	DCT	STXL	TDLINE_LC	Text Line	S/4 Hana	STXL	TDLINE	Text Line	Direct Mapping

Note: For all relevant fields Data Origin will be defaulted to 'Individual Maintenance'

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Mapping Table Name	Mapping Table Description
ENR_Functional Location_TPLNR	Asset Level Functional Locations created with Target Structure Indicator for corresponding Legacy Functional Location
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
ENR-Functional Location_Plant Section	Asset Functional Locations missing Plant Section in Legacy
ENR-Superior Functional Location	Superior Functional Locations created with Target Structure Indicator for corresponding Legacy Superior Functional Location
ENR-Functional Location_Installation Allowed	Installation Allowed Flag assignment to Functional Locations
ENR-Functional Location_Construction Type	Construction Type Assignment to Functional Locations
ENR-Functional Location_Work Centre	Asset Functional Locations missing Work Centre in Legacy
ENR-Functional Location_Weight	Weight of Object Functional Location cleansed by business from Legacy Long Text
ENR-Functional Location_Unit of Weight	Unit of Weight of Object Functional Location cleansed by business from Legacy Long Text
ENR-Functional Location_Name 1-4	Name & Address fields for Functional Location cleansed by business from Legacy Long Text
ENR-Functional Location Description	Functional Location Descriptions missing in Plant Local Language in Legacy
ENR-Functional Location Partner	Functional Location Partners required as per Target Design
ENR-Functional Location_LTXT	Functional Location Long Text to be added as required
OTH-Functional Location	List of relevant Asset Functional Locations slated for migration, including the Target Technical Object and Asset Ownership details to be reviewed by Business
OTH_Migration_Date Relevant Values A2D	Dates to be defaulted for A2D objects for each Migration Cycle
Technical Object Type	Old to new Technical Object Type
Plant	Old Plant to New Plant
Plant Section	Old to new Plant Section
Maintenance Planner Group	Old to New Planner Group
Work Center A2D	Old to new Work Centre A2D
Cost Center	Old to New Cost Center
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

List of Transformation Mappings with additional details is maintained here: Transformation Mappings

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	SyWay Data Team
2	Ensure all Transformation mappings are up to date	SyWay Data Team

Pre-Load Validation

Project Team

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

Pre-Cutover : 1003a Functional Location Classification

Pre-Cutover : 1003b Functional Location User Status

Pre-Cutover : 1003c Functional Location Long Text

Pre-Cutover : 1003d Functional Location Partner Assignment

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	TPAR - Business Partner: Functions
12	T002 - Language Keys

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 category	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Object Type	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Currency	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Country of Manufacturer	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Maintenance Plant	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Plant Section	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid ABC indicator	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Planning Plant	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Planner Group	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Partner Function	Engage Functional team to expedite and fix the error in the system
Configuration	Invalid Language Key	Engage Functional team to expedite and fix the error in the system
Invalid Data	Invalid Work Centre	Expedite whether the master data is changed in the system
Invalid Data	Invalid Cost Center	Expedite whether the master data is changed in the system
Invalid Data	Invalid Construction Type	Expedite whether the master data is changed in the system
Invalid Data	Invalid Class	Expedite whether the master data is changed in the system
Invalid Data	Invalid Characteristics	Expedite whether the master data is changed in the system
Invalid Data	Invalid Vendor Business Partner	Expedite whether the master data is changed in the system

Post-Load Validation

Project Team

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. 259)	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