You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 58 Next »

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:

  1. Organisational Level - This level represents the enterprise structure of Syensqo. It defines:
    • The Company

    • The Global Business Unit (GBU)

    • The Plant

  2. 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
  3. `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


DCT

  • From Level 1 to Level 7. These Functional Location doesn't necessarily exist in Legacy and would be constructed.

Extraction

The data from legacy system includes:

  • Functional Location having Maintenance Plant (IFLOT-WERKS) in scope

The data from legacy system excludes:

  • Functional Location with Inactive System Status (INAC)
  • Functional Location with Deletion Flag System Status (DLFL)
  • Exclusion List = Manual Review (Initial List Low-Level Functional Location). Note that this will be an inclusion for Equipment.

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


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget 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

  1. <Types of documents> documents currently attached to Functional Locations will be migrated.
  2. Refer to the Document Management in the SyWay Solution.

Legal Requirement

Not Applicable

Special Requirements

Not Applicable



Target Design

The technical design of the target for this conversion approach.


1. Functional Location Master

TableFieldData ElementField DescriptionData TypeLengthRequirement
IFLOTTPLNRTPLNRFunctional Location NumberCHAR30Mandatory
IFLOTTPLKZTPLKZStructure IndicatorCHAR80Mandatory
IFLOTFLTYPFLTYPCategoryCHAR80Mandatory
IFLOTINBDTINBDTStart-Up DateDATS8Conditional
IFLOTEQARTEQARTObject TypeCHAR80Mandatory
IFLOTHERSTHERSTManufacturerCHAR30Conditional
IFLOTTYPBZTYPBZModel NumberCHAR20Conditional
IFLOTMAPARMAPARManufacturer Part NumberCHAR30Conditional
IFLOTHERLDHERLDCountry/Region of ManufactureCHAR80Conditional
IFLOTBAUJJBAUJJYear of ConstructionCHAR4Conditional
IFLOTBAUMMBAUMMMonth of ConstructionCHAR80Conditional
IFLOTSERGESERGEManufacturer Serial NumberCHAR30Conditional
IFLOTANSWTANSWTAcquisition ValueNUMC13Conditional
IFLOTWAERSWAERSCurrency Key ( ISO Format )CHAR80Conditional
IFLOTSWERKSWERKMaintenance PlantCHAR80Mandatory
IFLOTEQFNREQFNRSort FieldCHAR30Conditional
IFLOTBEBERBEBERPlant SectionCHAR80Conditional
IFLOTABCKZABCKZABC IndicatorCHAR80Conditional
ILOAINGRPINGRPPlanner GroupCHAR80Conditional
ILOAIWERKIWERKPlanning PlantCHAR80Mandatory
ILOAGEWRKGEWRKMaintenance Work CenterCHAR80Conditional
ILOAWERGWWERGWWork Center PlantCHAR80Conditional
ILOABUKRSBUKRSCompany CodeCHAR80Mandatory
ILOAKOSTLKOSTLCost CenterCHAR80Conditional
IFLOTTPLMATPLMASuperior Functional LocationCHAR80Conditional
IFLOTIEQUIIEQUIIndicator: Installation AllowedCHAR1Conditional
ILOASUBMTSUBMTConstruction TypeCHAR80Conditional
ILOAKOKRSKOKRSControlling AreaCHAR4Mandatory
IFLOTBRGEWBRGEWWeight of ObjectQUAN13Conditional
IFLOTGEWEIGEWEIUnit of WeightUNIT3Conditional
ADRCNAME1NAME1Name 1CHAR40Conditional
ADRCNAME2NAME2Name 2CHAR40Conditional
ADRCNAME3NAME3Name 3CHAR40Conditional
ADRCNAME4NAME4Name 4CHAR40Conditional
ADRCCOUNTRYCOUNTRYCountry/Region KeyCHAR3Conditional


2. Functional Location Short Text

TableFieldData ElementField DescriptionData TypeLengthRequirement
IFLOTXTPLNRTPLNRFunctional Location NumberCHAR30Mandatory
IFLOTXSPRASSPRASLanguage KeyLANG1Mandatory
IFLOTXPLTXTPLTXTDescription of Functional LocationCHAR40Mandatory

Note: Each Functional Location must have 1 entry for each language in scope: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish


3. Functional Location Classification (Header) 

TableFieldData ElementField DescriptionData TypeLengthRequirement
KSSKKLARTKLARTClass TypeCHAR20Mandatory
KSSKOBTABOBTABName of Database Table for ObjectCHAR30Mandatory
KSSKCLASSNUMCLASSNUMClass NameCHAR30Mandatory
KSSKOBJEKOBJEKObject Key (Functional Location Number)CHAR90Mandatory
KSSKSTATUSTATUClassification StatusCHAR80Mandatory


 4. Functional Location Classification (Characteristics Value Allocation) 

TableFieldData ElementField DescriptionData TypeLengthRequirement
KSSKKLARTKLARTClass TypeCHAR20Mandatory
KSSKCLASSNUMCLASSNUMClass NameCHAR30Mandatory
KSSKOBJEKOBJEKObject Key (Functional Location Number)CHAR90Mandatory
AUSP

ATINN

ATINN

Characteristic NameCHAR80Mandatory
AUSPPOSNRPOSNR Item NumberCHAR3Mandatory
AUSPATFLVATFLVNumerical Value - From NUMC16Conditional
AUSPATFLBATFLBNumerical Value - ToNUMC16Conditional
AUSPATCODATCODCode for Value DependencyCHAR1Conditional
AUSPDATE_FROMDATE_FROMLower Boundary for Date - IntervalDATS8Conditional
AUSPDATE_TODATE_TOUpper Boundary for Date - IntervalDATS8Conditional
AUSPTIME_FROMTIME_FROMLower Boundary for Time - IntervalTIMS6Conditional
AUSPTIME_TOTIME_TOUpper Boundary for Time - IntervalTIMS6Conditional
AUSPATFLVATFLVCurrency Value - From (Floating Point)NUMC16Conditional
AUSPATFLBATFLBCurrency Value - To (Floating Point)NUMC16Conditional
AUSPVALUE_CHARVALUE_CHARCharacteristic ValueCHAR30Conditional


5. Functional Location Partner

TableFieldData ElementField DescriptionData TypeLengthRequirement
IHPAOBJNROBJNRObject Number (Internal Floc Number)CHAR30Mandatory
IHPAOBTYPOBTYPObject TypeCHAR3Mandatory
IHPAPARVWPARVWPartner FunctionCHAR2Mandatory
IHPAPARNRPARNRPartnerCHAR12Mandatory


6. Functional Location User Status

TableFieldData ElementField DescriptionData TypeLengthRequirement
JESTOBJNROBJNRObject Number (Internal Floc Number)CHAR30Mandatory
JSTOSTSMASTSMAStatus profile of the functional locationCHAR8Mandatory

JEST

STAT

STATStatus Number in User Status ListCHAR5Mandatory

JEST

INACT

INACTIndicator: Status Is InactiveCHAR1


7. Functional Location Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
STXHTDOBJECTTDOBJECTTexts: application objectCHAR10Mandatory
STXHTDNAMETDOBNAMENameCHAR70Mandatory
STXHTDIDTDIDText IDCHAR4Mandatory
STXHTDSPRASSPRASLanguage KeyLANG1Mandatory


8. Functional Location Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement
STXLTDOBJECTTDOBJECTTexts: application objectCHAR10Mandatory
STXLTDNAMETDOBNAMENameCHAR70Mandatory
STXLTDIDTDIDText IDCHAR4Mandatory
STXLTDSPRASSPRASLanguage KeyLANG1Mandatory
STXLTDFORMATTDFORMATTag columnCHAR1Mandatory
STXLTDLINETDLINEText LineCHAR72Mandatory


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.

IDCriticalityError Message/Report DescriptionRuleOutputSource System

1003-001


C1Missing Functional Location DescriptionsFunctional Location as per Relevancy Criteria where there are blank Functional Location Descriptions.Functional Location DescriptionPF2, WP2
1003-002C1Invalid, Inactive or no Cost Centres linked to Functional LocationFunctional Location as per Relevancy Criteria assigned with a Cost Centre which does not belong below:
1. Cost Centre (FI) as per Relevancy Criteria
Cost CentrePF2, WP2
1003-003C1Invalid, Inactive or no Class linked to Functional LocationFunctional Location as per Relevancy Criteria assigned with a Class which does not belong below:
1. Class as per Relevancy Criteria
ClassPF2, WP2
1003-004C1Invalid, Inactive or no Characteristic linked to Functional LocationFunctional Location as per Relevancy Criteria assigned with a Characteristic which does not belong below:
1. Characteristic as per Relevancy Criteria
CharacteristicPF2, WP2
1003-005C1Invalid, Inactive or no Construction Type linked to Functional LocationFunctional Location as per Relevancy Criteria assigned with a Construction Type which does not belong below:
1. Construction Type as per Relevancy Criteria
Construction TypePF2, WP2
1003-006C1Invalid, Inactive or no Work Centres linked to Functional LocationFunctional Location as per Relevancy Criteria assigned with a Work Centre which does not belong below:
1. Work Centre as per Relevancy Criteria
Work CentrePF2, WP2
1003-0007C1Invalid or no Planner Group linked to Functional LocationFunctional Location as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I)Planner GroupPF2, WP2
1003-008C1Invalid or no Plant Section linked to Functional LocationFunctional Location as per Relevancy Criteria with no Planner Group Assigned or Invalid Plant SectionPlant SectionPF2, WP2
1003-009C1Invalid or no Technical Object Type linked to Functional LocationFunctional Location as per Relevancy Criteria with no Technical Object Type Assigned or Invalid Technical Object Type (T370K)Technical Object TypePF2, WP2
1003-010C1Invalid, Inactive or no Superior Functional Location linked to Functional LocationFunctional 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 LocationPF2, WP2
1003-011C1Functional Location Company Code incorrect.Functional Location as per Relevancy Criteria with Invalid Company Code (T001)Company CodePF2, WP2
1003-012C1Functional Location Currency Codes incorrect.Functional Location as per Relevancy Criteria with Invalid Currency Codes (TCURC)CurrencyPF2, WP2
1003-013C2Functional Location Planning Plant and Maintenance Plant are not the same.Functional Location as per Relevancy Criteria with Planning Plant <> Maintenance PlantMaintenance Plant, Planning PlantPF2, 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:

  1. 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.
  2. 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 DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team

2

Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. 

SyWay Data Team


Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue 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. 

  1. The extracted report will be loaded into the required structure using the DCT.
  2. 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 NameField DescriptionRule
TPLNRFunctional 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

TPLKZStructure 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

FLTYPCategory

Mandatory

Allowed values for each Level of the Functional Location Structure:

O - Org
N - Nav
A - Asset

INBDTStart-Up Date

Conditional

Default to 'Go-Live' Date.

EQARTObject Type

Conditional

Must be populated for Category 'A' Functional Locations.

Allowed values from T370K to be populated.

HERSTManufacturer

Conditional

User to populate value only for Category 'A' Functional Locations.
Category 'O'  and 'N' Functional Locations to be assigned 'Blank'.

TYPBZModel Number

Conditional

User to populate value only for Category 'A' Functional Locations.
Category 'O'  and 'N' Functional Locations to be assigned 'Blank'.

MAPARManufacturer Part Number

Conditional

User to populate value only for Category 'A' Functional Locations.
Category 'O'  and 'N' Functional Locations to be assigned 'Blank'.

HERLDCountry/Region of Manufacture

Conditional

User to populate value only for Category 'A' Functional Locations.
Category 'O'  and 'N' Functional Locations to be assigned 'Blank'.

BAUJJYear of Construction

Conditional

User to populate value only for Category 'A' Functional Locations.
Category 'O'  and 'N' Functional Locations to be assigned 'Blank'.

BAUMMMonth of Construction

Conditional

User to populate value only for Category 'A' Functional Locations.
Category 'O'  and 'N' Functional Locations to be assigned 'Blank'.

SERGEManufacturer Serial Number

Conditional

User to populate value only for Category 'A' Functional Locations.
Category 'O'  and 'N' Functional Locations to be assigned 'Blank'.

ANSWTAcquisition Value

Conditional

User to populate value if available, else assign 'Blank'

WAERSCurrency Key ( ISO Format )

Conditional

User to populate value if 'Acquisition Value' field has been populated, else assign 'Blank'

SWERKMaintenance 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

EQFNRSort 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

BEBERPlant 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

ABCKZABC 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'

  1. Aggregate values for all Characteristics assigned for the Functional Location as per Functional Location Classification DCT where ABC_FLAG = 'X'
  2. 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'
INGRPPlanner 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

IWERKPlanning 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

GEWRKMaintenance 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 CRHD to be populated

WERGWWork 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

BUKRSCompany Code

Mandatory

User to populate value from T001K with reference to the assigned Maintenance Plant

KOSTLCost Center

Conditional

User must populate value for all Functional Locations except for Function Locations with User Status as 'Maintenance not allowed'

Allowed values from CSKS to be populated

TPLMASuperior Functional Location

Conditional

Should be blank for SORG- L1.

For others Superior Functional location should be in accordance with the technical object structure of a particular Functional location

Ensure SAST-L1 Functional Location must have a SNAV as Superior Functional Location

Ensure all higher Labels must exists for a Functional location

IEQUIIndicator: 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.

SUBMTConstruction 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

KOKRSControlling Area

Mandatory

User to populate value from CSKS with reference to the assigned Cost Centre

BRGEWWeight 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'

GEWEIUnit of Weight

Conditional

User to populate unit value if BRGEW (Weight) has been maintained.

Allowed values from T006 to be populated

NAME1Name 1

Conditional

User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. 

NAME2Name 2

Conditional

User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. 

NAME3Name 3

Conditional

User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. 

NAME4Name 4

Conditional

User to populate value for Level 2 Category 'A' Functional Locations where 'Indicator: Installation Allowed' field has not been assigned as 'X'. 

COUNTRYCountry/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 NameField DescriptionRule
TPLNRFunctional Location Number

Mandatory

Key to link to Functional Location

SPRASLanguage 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_ENDescription 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_FRDescription 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_ITDescription 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_ZHDescription 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_PTDescription 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_DEDescription 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_ESDescription 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 ElementField DescriptionRule
KLARTClass Type

Mandatory

Default to '003' (Function Location).

OBTABName of Database Table for Object

Mandatory

Default to 'IFLOT'.

CLASSNUMClass 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

OBJEKObject Key (Functional Location Number)

Mandatory

Key to link Functional Location Header

ATINNCharacteristic Name

Mandatory

User to populate allocated Characteristic based on 'Appendix - Class Values' maintained in Class MDS.

POSNRItem Number

Mandatory.

Positive numeric values only.

Must be unique and ascending sequential

ATFLVNumerical Value - From 

Conditional

User to populate value if Characteristic Data Type = 'NUM'

ATFLBNumerical Value - To

Conditional

User to populate value if Characteristic Data Type = 'NUM' and ATINT (Interval Values allowed) = 'X'

ATCODCode 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_FROMLower Boundary for Date - Interval

Conditional

User to populate value if Characteristic Data Type = 'DATE'

DATE_TOUpper Boundary for Date - Interval

Conditional

User to populate value if Characteristic Data Type = 'DATE' and ATINT (Interval Values allowed) = 'X'

TIME_FROMLower Boundary for Time - Interval

Conditional

User to populate value if Characteristic Data Type = 'TIME'

TIME_TOUpper Boundary for Time - Interval

Conditional

User to populate value if Characteristic Data Type = 'TIME' and ATINT (Interval Values allowed) = 'X'

ATFLVCurrency Value - From (Floating Point)

Conditional

User to populate value if Characteristic Data Type = 'CURR'

ATFLBCurrency Value - To (Floating Point)

Conditional

User to populate value if Characteristic Data Type = 'CURR' and ATINT (Interval Values allowed) = 'X'

VALUE_CHARCharacteristic Value

Conditional

User to populate value if Characteristic Data Type = 'CHAR'

ABC_FLAGABC 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 ElementField DescriptionRule
TPLNRFunctional Location Number

Mandatory

Key to link to Functional Location

OBTYPObject Type

Mandatory

Default to 'IFL'

PARVWPartner Function

Conditional

Partner Functions to be assigned to Category 'A' Functional Locations

  • 'Z1' (Asset Owner)
  • 'Z2' (Asset Maintainer)
PARNRPartner

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 ElementField DescriptionRule
TPLNRFunctional Location Number

Mandatory

Key to link to Functional Location

STSMAStatus profile of the functional location

Mandatory

Allowed values from TJ20 to be populated

Default to 'ZEAMFL01'

STATStatus 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

INACTIndicator: Status Is Inactive

Conditional

Allowed Values:

' ' = User Status is Active

'X' = User Status is Inactive


6. Functional Location Long Text Header DCT Rules

Data ElementField DescriptionRule
TPLNRFunctional Location Number

Non-Editable

Key to link to Functional Location

Direct Mapping from Functional Location Long Text Line: TPLNR field

KZLTXLong Text Exists

Non Editable

Default to "X"

TDOBJECTTexts: application object

Non-Editable

Direct Mapping from Functional Location Long Text Line: TDOBJECT field

TDNAMEName

Non-Editable

Direct Mapping from Functional Location Long Text Line: TDNAME field

TDIDText ID

Non-Editable

Direct Mapping from Functional Location Long Text Line: TDID field

TDSPRASLanguage Key

Non-Editable

Direct Mapping from Functional Location Long Text Line: TDSPRAS field


Functional Location Long Text Line DCT Rules

Data ElementField DescriptionRule
TPLNRFunctional Location Number

Mandatory

Key to link to Functional Location

TDOBJECTTexts: application object

Non-Editable

Default to 'IFLOT'

TDOBNAMEName

Non-Editable

To be populated with the TPLNR value

TDIDText ID

Non-Editable

Default to 'LTXT'

SPRASLanguage Key

Mandatory

Must be either one of the following: English, French, Italian, Mandarin, Brazilian, Portuguese, German and Spanish

TDFORMATTag column

Non-Editable

Default to "*"

TDLINEText Line

Mandatory

Free Text

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


Extraction Dependencies

Item #Step DescriptionTeam Responsible
1Relevancy Criteria for CharacteristicsSyWay A2D Data Team
2Relevancy Criteria for ClassSyWay A2D Data Team
3Relevancy Criteria for Construction TypeSyWay A2D Data Team
4Relevancy Criteria for Work CentreSyWay A2D Data Team
5Relevancy Criteria for Cost CentreSyWay A2D Data Team
6Relevancy 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:

  1. 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
  2. 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 DescriptionTeam 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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1ENRICHMENTENR_Functional Location_TPLNRzLegacyTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDerive Target Functional Location Label based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
2----S/4 HanaIFLOTTPLKZStructure Indicator

Default TPLKZ = 'SAST' (X-XXXXNNNNNN) for Asset Level Functional Locations

3----S/4 HanaIFLOTFLTYPCategory

Default FLTYP = A (Asset) for Asset Level Functional Locations 

4PF2, WP2IFLOTINBDTStart-Up DateS/4 HanaIFLOTINBDTStart-Up DateDerive 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 HanaIFLOTEQARTObject TypeDerive 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
6PF2, WP2IFLOTHERSTManufacturerS/4 HanaIFLOTHERSTManufacturerDirect Mapping
7PF2, WP2IFLOTTYPBZModel NumberS/4 HanaIFLOTTYPBZModel NumberDirect Mapping
8PF2, WP2IFLOTMAPARManufacturer Part NumberS/4 HanaIFLOTMAPARManufacturer Part NumberDirect Mapping
9PF2, WP2IFLOTHERLDCountry/Region of ManufactureS/4 HanaIFLOTHERLDCountry/Region of ManufactureDirect Mapping
10PF2, WP2IFLOTBAUJJYear of ConstructionS/4 HanaIFLOTBAUJJYear of ConstructionDirect Mapping
11PF2, WP2IFLOTBAUMMMonth of ConstructionS/4 HanaIFLOTBAUMMMonth of ConstructionDirect Mapping
12PF2, WP2IFLOTSERGEManufacturer Serial NumberS/4 HanaIFLOTSERGEManufacturer Serial NumberDirect Mapping
13PF2, WP2IFLOTANSWTAcquisition ValueS/4 HanaIFLOTANSWTAcquisition ValueDirect Mapping
14PF2, WP2IFLOTWAERSCurrency Key ( ISO Format )S/4 HanaIFLOTWAERSCurrency Key ( ISO Format )Direct Mapping
15PF2, WP2ILOASWERKMaintenance PlantS/4 HanaIFLOTSWERKMaintenance PlantDerive based on Value Mapping: Plant (Maintenance Plant = Yes)
16ENRICHMENTENR_Functional Location_TPLNRzLegacyTPLNRLegacy Functional Location LabelS/4 HanaIFLOTEQFNRSort FieldDerive 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 HanaIFLOTBEBERPlant 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 HanaIFLOTABCKZABC Indicator

Use below logic -

  1. Aggregate values for all Characteristics assigned for the Functional Location as per Functional Location Classification DCT where ABC_FLAG = 'X'
  2. 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'
19PF2, WP2IFLOTINGRPPlanner GroupS/4 HanaILOAINGRPPlanner GroupDerive the Plant Section as per value mapping : Maintenance Planner Group
20PF2, WP2IFLOTIWERKPlanning PlantS/4 HanaILOAIWERKPlanning PlantDerive based on Value Mapping: Plant (Maintenance Plant = Yes)
21PF2, WP2ILOAGEWRKMaintenance Work CenterS/4 HanaILOAGEWRKMaintenance Work Center

Derive as per value mapping : Work Center A2D 

22PF2, WP2ILOAWERGWWork Center PlantS/4 HanaILOAWERGWWork Center PlantDerive as per value mapping : Work Center A2D
23PF2, WP2ILOABUKRSCompany CodeS/4 HanaILOABUKRSCompany CodeDerive as per value mapping : Company Code
24PF2, WP2ILOAKOSTLCost CenterS/4 HanaILOAKOSTLCost Center

Derive as per value mapping : Cost Center

25PF2, WP2IFLOTTPLMASuperior Functional LocationS/4 HanaILOATPLMASuperior Functional LocationDerive Superior Functional Location based Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
26ENRICHMENTENR-Functional Location_Installation AllowedzLegacyTPLNRIndicator: Installation AllowedS/4 HanaILOAIEQUIIndicator: Installation AllowedDerive Construction Type as per enrichment ENR-Functional Location_Installation Allowed based on the Legacy Functional Location
27ENRICHMENTENR-Functional Location_Construction TypezLegacyTPLNRConstruction TypeS/4 HanaILOASUBMTConstruction Type

Derive Construction Type as per enrichment ENR-Functional Location_Construction Type based on the Legacy Functional Location

28PF2, WP2ILOAKOKRSControlling AreaS/4 HanaILOAKOKRSControlling AreaDerive as per value mapping : Controlling Area
29ENRICHMENTENR-Functional Location_LTXT_ValueszLegacyTPLNRLegacy Functional Location LabelS/4 HanaIFLOTBRGEWWeight of ObjectDerive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
30ENRICHMENTENR-Functional Location_LTXT_ValueszLegacyTPLNRLegacy Functional Location LabelS/4 HanaIFLOTGEWEIUnit of WeightDerive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
31ENRICHMENTENR-Functional Location_LTXT_ValueszLegacyTPLNRLegacy Functional Location LabelS/4 HanaADRCNAME1Name 1Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
32ENRICHMENTENR-Functional Location_LTXT_ValueszLegacyTPLNRLegacy Functional Location LabelS/4 HanaADRCNAME2Name 2Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
33ENRICHMENTENR-Functional Location_LTXT_ValueszLegacyTPLNRLegacy Functional Location LabelS/4 HanaADRCNAME3Name 3Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
34ENRICHMENTENR-Functional Location_LTXT_ValueszLegacyTPLNRLegacy Functional Location LabelS/4 HanaADRCNAME4Name 4Derive value as per enrichment ENR-Functional Location_LTXT_Values based on the Legacy Functional Location
35ENRICHMENTENR-Functional Location_LTXT_ValueszLegacyTPLNRLegacy Functional Location LabelS/4 HanaADRCCOUNTRYCountry/Region KeyDerive Country/ Region key based on Maintenance Plant assigned from Table T001W


    1.b Functional Location Master Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location Label Direct Mapping
2DCTIFLOTTPLKZStructure IndicatorS/4 HanaIFLOTTPLKZStructure Indicator Direct Mapping
3DCTIFLOTFLTYPCategoryS/4 HanaIFLOTFLTYPCategory Direct Mapping
4--- -S/4 HanaIFLOTINBDTStart-Up DateDerive the date as per value mapping : OTH_Migration_Date Relevant Values A2D (using Object ID "1003" and Field Name = "IFLOT-INBDT".
5DCTIFLOTEQARTObject TypeS/4 HanaIFLOTEQARTObject TypeDirect Mapping
6DCT IFLOTHERSTManufacturerS/4 HanaIFLOTHERSTManufacturerDirect Mapping
7DCT IFLOTTYPBZModel NumberS/4 HanaIFLOTTYPBZModel NumberDirect Mapping
8DCTIFLOTMAPARManufacturer Part NumberS/4 HanaIFLOTMAPARManufacturer Part NumberDirect Mapping
9DCTIFLOTHERLDCountry/Region of ManufactureS/4 HanaIFLOTHERLDCountry/Region of ManufactureDirect Mapping
10DCT IFLOTBAUJJYear of ConstructionS/4 HanaIFLOTBAUJJYear of ConstructionDirect Mapping
11DCT IFLOTBAUMMMonth of ConstructionS/4 HanaIFLOTBAUMMMonth of ConstructionDirect Mapping
12DCT IFLOTSERGEManufacturer Serial NumberS/4 HanaIFLOTSERGEManufacturer Serial NumberDirect Mapping
13DCT IFLOTANSWTAcquisition ValueS/4 HanaIFLOTANSWTAcquisition ValueDirect Mapping
14DCT IFLOTWAERSCurrency Key ( ISO Format )S/4 HanaIFLOTWAERSCurrency Key ( ISO Format )Direct Mapping
15DCT IFLOTSWERKMaintenance PlantS/4 HanaIFLOTSWERKMaintenance PlantDirect Mapping
16DCT IFLOTEQFNRSort FieldS/4 HanaIFLOTEQFNRSort FieldDirect Mapping
17DCT IFLOTBEBERPlant SectionS/4 HanaIFLOTBEBERPlant SectionDirect Mapping
18DCT IFLOTABCKZABC IndicatorS/4 HanaIFLOTABCKZABC IndicatorDirect Mapping
19DCT ILOAINGRPPlanner GroupS/4 HanaILOAINGRPPlanner GroupDirect Mapping
20DCT ILOAIWERKPlanning PlantS/4 HanaILOAIWERKPlanning PlantDirect Mapping
21DCT ILOAGEWRKMaintenance Work CenterS/4 HanaILOAGEWRKMaintenance Work CenterDirect Mapping
22DCT ILOAWERGWWork Center PlantS/4 HanaILOAWERGWWork Center PlantDirect Mapping
23DCT ILOABUKRSCompany CodeS/4 HanaILOABUKRSCompany CodeDirect Mapping
24DCT ILOAKOSTLCost CenterS/4 HanaILOAKOSTLCost CenterDirect Mapping
25DCT ILOATPLMASuperior Functional LocationS/4 HanaILOATPLMASuperior Functional LocationDirect Mapping
26DCTILOAIEQUIIndicator: Installation AllowedS/4 HanaILOAIEQUIIndicator: Installation AllowedDirect Mapping
27DCT ILOASUBMTConstruction TypeS/4 HanaILOASUBMTConstruction TypeDirect Mapping
28DCT ILOAKOKRSControlling AreaS/4 HanaILOAKOKRSControlling AreaDirect Mapping
29DCT IFLOTBRGEWWeight of ObjectS/4 HanaIFLOTBRGEWWeight of ObjectDirect Mapping
30DCT IFLOTGEWEIUnit of WeightS/4 HanaIFLOTGEWEIUnit of WeightDirect Mapping
31DCT ADRCNAME1Name 1S/4 HanaADRCNAME1Name 1Direct Mapping
32DCTADRCNAME2Name 2S/4 HanaADRCNAME2Name 2Direct Mapping
33DCT ADRCNAME3Name 3S/4 HanaADRCNAME3Name 3Direct Mapping
34DCT ADRCNAME4Name 4S/4 HanaADRCNAME4Name 4Direct Mapping
35DCT ADRCCOUNTRYCountry/Region KeyS/4 HanaADRCCOUNTRYCountry/Region KeyDirect Mapping


2. Functional Location Short Text Transformation Rule (DCT) 


Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'E'
3DCTIFLOTXPLTXT_ENDescription of Functional Location (English)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'F'
3DCTIFLOTXPLTXT_FRDescription of Functional Location (French)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'I'
3DCTIFLOTXPLTXT_ITDescription of Functional Location (Italian)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to '1'
3DCTIFLOTXPLTXT_ZHDescription of Functional Location (Mandarin)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'P'
3DCTIFLOTXPLTXT_PTDescription of Functional Location (Brazilian Portuguese)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'D'
3DCTIFLOTXPLTXT_DEDescription of Functional Location (German)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'S'
3DCTIFLOTXPLTXT_ESDescription of Functional Location (Spanish)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping


3. Functional Location Classification

    3.a Functional Location Classification Transformation Rule (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1ENRICHMENTENR_Functional Location_TPLNRzLegacyTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDerive Target Functional Location Label based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaKSSKOBTABName of Database Table for ObjectDefault to 'IFLOT'
4PF2, WP2KSSKCLASSNUMClass NameS/4 HanaKSSKCLASSNUMClass NameDerive Target Class Name based on value mapping : Class A2D
5PF2, WP2AUSPATINNCharacteristic NameS/4 HanaAUSPCHARACTCharacteristic NameDerive Target Class Name based on value mapping : Characteristic A2D
6PF2, WP2AUSPPOSNRItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping
7PF2, WP2AUSPATFLVNumerical Value - From (Floating Point)S/4 HanaAUSPATFLVNumerical Value - From (Floating Point)Direct Mapping
8PF2, WP2AUSPATFLBNumerical Value - To (Floating Point)S/4 HanaAUSPATFLBNumerical Value - To (Floating Point)Direct Mapping
9PF2, WP2AUSPATCODCode for Value DependencyS/4 HanaAUSPATCODCode for Value DependencyDirect Mapping
10PF2, WP2AUSPDATE_FROMLower Boundary for Date - IntervalS/4 HanaAUSPDATE_FROMLower Boundary for Date - IntervalDirect Mapping
11PF2, WP2AUSPDATE_TOUpper Boundary for Date - IntervalS/4 HanaAUSPDATE_TOUpper Boundary for Date - IntervalDirect Mapping
12PF2, WP2AUSPTIME_FROMLower Boundary for Time - IntervalS/4 HanaAUSPTIME_FROMLower Boundary for Time - IntervalDirect Mapping
13PF2, WP2AUSPTIME_TOUpper Boundary for Time - IntervalS/4 HanaAUSPTIME_TOUpper Boundary for Time - IntervalDirect Mapping
14PF2, WP2AUSPATFLVCurrency Value - From (Floating Point)S/4 HanaAUSPATFLVCurrency Value - From (Floating Point)Direct Mapping
15PF2, WP2AUSPATFLBCurrency Value - To (Floating Point)S/4 HanaAUSPATFLBCurrency Value - To (Floating Point)Direct Mapping
16PF2, WP2AUSPVALUE_CHARCharacteristic ValueS/4 HanaAUSPVALUE_CHARCharacteristic ValueDirect Mapping


    3.b Functional Location Classification Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaKSSKOBTABName of Database Table for ObjectDefault to 'IFLOT'
4DCTKSSKCLASSNUMClass NameS/4 HanaKSSKCLASSNUMClass NameDirect Mapping
5DCTAUSPATINNCharacteristic NameS/4 HanaAUSPCHARACTCharacteristic NameDirect Mapping
6DCTAUSPPOSNRItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping
7DCTAUSPATFLVNumerical Value - From (Floating Point)S/4 HanaAUSPATFLVNumerical Value - From (Floating Point)Direct Mapping
8DCTAUSPATFLBNumerical Value - To (Floating Point)S/4 HanaAUSPATFLBNumerical Value - To (Floating Point)Direct Mapping
9DCTAUSPATCODCode for Value DependencyS/4 HanaAUSPATCODCode for Value DependencyDirect Mapping
10DCTAUSPDATE_FROMLower Boundary for Date - IntervalS/4 HanaAUSPDATE_FROMLower Boundary for Date - IntervalDirect Mapping
11DCTAUSPDATE_TOUpper Boundary for Date - IntervalS/4 HanaAUSPDATE_TOUpper Boundary for Date - IntervalDirect Mapping
12DCTAUSPTIME_FROMLower Boundary for Time - IntervalS/4 HanaAUSPTIME_FROMLower Boundary for Time - IntervalDirect Mapping
13DCTAUSPTIME_TOUpper Boundary for Time - IntervalS/4 HanaAUSPTIME_TOUpper Boundary for Time - IntervalDirect Mapping
14DCTAUSPATFLVCurrency Value - From (Floating Point)S/4 HanaAUSPATFLVCurrency Value - From (Floating Point)Direct Mapping
15DCTAUSPATFLBCurrency Value - To (Floating Point)S/4 HanaAUSPATFLBCurrency Value - To (Floating Point)Direct Mapping
16DCTAUSPVALUE_CHARCharacteristic ValueS/4 HanaAUSPVALUE_CHARCharacteristic ValueDirect Mapping


4. Functional Location Partner Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDirect Mapping
2DCTIHPAPARVWPartner FunctionS/4 HanaIHPAPARVWPartner FunctionDirect Mapping
3DCTIHPAPARNRPartnerS/4 HanaIHPAPARNRPartnerDirect Mapping


5. Functional Location User Status

    5.a Functional Location User Status Transformation Rules (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1ENRICHMENTENR_Functional Location_TPLNRzLegacyTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location LabelDerive Target Functional Location Label based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
3---Status profile of the functional locationS/4 HanaJSTOSTSMAStatus profile of the functional locationDefault to 'ZEAMFL01'
4PF2, WP2

JEST

STAT

Status Number in User Status ListS/4 Hana

JEST

STAT

Status Number in User Status ListDerive the User Status based on value mapping : User Status Function Location
5-

-

-

-S/4 Hana

JEST

INACT

Indicator: Status Is InactiveDefault to '' (Blank)


    5.b Functional Location User Status Transformation Rules (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location NumberStagingIFLOTTPLNRFunctional Location NumberDirect Mapping
2----S/4 HanaJSTOSTSMAStatus profile of the functional locationDefault to 'ZEAMFL01'
3DCT

JEST

STAT

Status Number in User Status ListS/4 Hana

JEST

STAT

Status Number in User Status ListDirect Mapping
4----S/4 Hana

JEST

INACT

Indicator: Status Is InactiveDefault to '' (Blank)


6. Functional Location Long Text Header (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HanaSTXHTDOBJECTTexts: application objectDefault to 'IFLOT'
2ENRICHMENTENR_Functional Location_TPLNRzLegacyTPLNRLegacy Functional Location LabelS/4 HanaSTXHTDNAMENameDerive Target TDNAME (Functional Location Label) based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
3----S/4 HanaSTXHTDIDText IDDefault to 'LTXT'
4PF2, WP2STXHTDSPRASLanguage KeyS/4 HanaSTXHTDSPRASLanguage KeyDirect Mapping


   Functional Location Long Text Line

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HanaSTXLTDOBJECTTexts: application objectDefault to 'IFLOT'
2ENRICHMENTENR_Functional Location_TPLNRzLegacyTPLNRLegacy Functional Location LabelS/4 HanaSTXLTDNAMENameDerive Target TDNAME (Functional Location Label) based on Legacy Function Location as per Enrichment ENR_Functional Location_TPLNR
3----S/4 HanaSTXLTDIDText IDDefault to 'LTXT'
5PF2, WP2STXHTDSPRASLanguage KeyS/4 HanaSTXLTDSPRASLanguage KeyDirect Mapping
6PF2, WP2STXLTDFORMATTag columnS/4 HanaSTXLTDFORMATTag columnDirect Mapping
7PF2, WP2STXLTDLINEText LineS/4 HanaSTXLTDLINEText LineDirect Mapping

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


Transformation Mapping
Mapping Table NameMapping Table Description
ENR_Functional Location_TPLNRAsset Level Functional Locations Labels created with Target Structure Indicator for corresponding Legacy Functional Location
Asset_Technical Object TypeOld to new Technical Object Type
ENR-Functional Location_Technical Object TypeThese are Functional Locations that sites cannot update in the source systems due to the lack of selectable configuration options.
ENR-Functional Location_SortFieldSort Field Assignment to Functional Locations
Plant SectionOld to new Plant Section
ENR-Functional Location_Plant SectionAsset Functional Locations missing Plant Section in Legacy
Maintenance Planner GroupOld to New Planner Group
Work Center A2DOld to new Work Centre A2D
Cost CenterOld to New Cost Center
Company CodeBUKRS: Old Companny Code to New Company Code
ENR-Functional Location_Installation AllowedInstallation Allowed Flag assignment to Functional Locations
ENR-Functional Location_Construction TypeConstruction Type Assignment to Functional Locations
Controlling AreaOld to New Controlling Area
ENR-Functional Location_LTXT_ValuesWeight of Object, Unit of Weight, Name 1, Name 2, Name 3, Name 4 information for Functional Location updated from Legacy Long Text
Class A2DOld to New Class A2D
Characteristic A2DOld to New Characteristic A2D
User Status Function LocationOld to New Functional Location User Status
Cost CenterOld to New Cost Center

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Ensure DCT tables completenessSyniti
2Ensure all Transformation mappings are up to dateSyniti


Pre-Load Validation

Project Team

Completeness

TaskAction
Verify Record CountSyWay 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

TaskAction

Conversion Accuracy

SyWay A2D Data Team to verify that all fields below meet pass the checks:

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks

Review Error Reports

Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.


Business

Completeness

TaskAction
Verify Record CountBusiness 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

TaskAction
Conversion AccuracyBusiness 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:

  1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
  2. 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 DescriptionTeam 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 TypeError DescriptionAction 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

TaskAction

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

TaskAction

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

TaskAction

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

TaskAction

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

See also

Change log

Version Published Changed By Comment
CURRENT (v. 58) 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.

  • No labels