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 Hierarchy of 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 comprises of 3 levels which define:
    • The Company - Syensqo Organisation

    • The Global Business Unit (GBU) - Specialty Polymer, Composite Materials, Novecare, Technology Solutions etc.

    • The Plant - Willow Island, Niagara Falls etc.

  2. Navigational Level - This level structures the hierarchy based on the functional or geographical layout of the plant. It comprises of 4 levels which define:

    • Units within the Plant - Production, Utilities, Facilities etc.
    • 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 comprises of 1 level which define:
    • Specific installation points for equipment
    • Maintainable assets themselves, serving as key points for maintenance planning and execution

The data from legacy system includes:

  1. Functional Location having Maintenance Plant (ILOA-SWERK) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes')
    </Start CR0416>
  2. Functional Location (IFLOS-TPLNR) for WP2 where IFLOS-ALKEY = '1' and IFLOS-ACTVS = 'X'
    </End CR0416>
  3. On top of above the scope for Asset Functional Location shall be refined based on below scenarios subjected to:
    1. Relevant Equipment (EQUI-EQUNR) </Start CR0416> with Valid To Date (EQUZ-DATBI) = '99991231' </End CR0416> being Installed under Functional Location (IFLOT-TPLNR) 
    2. Maintenance existing for the Functional Location -
      1. Any Maintenance Item (MPOS-WAPOS) existing for Functional Location (IFLOT-TPLNR) where (MPOS-EQUNR) = '' and (MPOS-BAUTL) = ''
      2. Any Maintenance Item (MPOS-WAPOS) with Object List (OBJK-OBKNR) including Functional Location (IFLOT-TPLNR)
      3. Any Functional Location Task list (TAPL-PLNNR) existing for Functional Location (IFLOT-TPLNR) 
      4. Any Work Order (AUFK-AUFNR) with created date (AUFK-ERDAT) in the last 5 years for Functional Location (IFLOT-TPLNR) where Equipment (AFIH-EQUNR) = '' and Assembly (AFIH-BAUTL) = ''
  4. Functional Location Long Text in Inclusion-FL Long Text
  5. Object Classification for the relevant Asset Functional Location 
ScenarioAsset Structure SetupMaintenance SetupResulting Action
1Functional Location has EquipmentMaintenance present or not
  1. Create AFLOC, at Fn.
  2. If Fn-1 is missing in legacy (i.e Superior Functional Location is missing), include Fn in the Cleansing Report (1003-007)
  3. If Fn-1 (superior functional location) is present, then all ancestors above Fn (Fn-1, Fn-2, Fn-3, …)

    1. if they have Equipment under it or maintenance associated, include in the Cleansing Report (1003-005),

    2. else include in Cleansing Report (1003-006)

  4. Stop.

2Functional Location has no EquipmentMaintenance Applicable
  1. Create Equipment at Fn.

  2. All ancestors above Fn-1 if they have Equipment under it or maintenance associated, include in the Cleansing Report (1003-005), else include in Cleansing Report (1003-006)

  3. If Fn-1 is missing, include the missing level(s) in the Cleansing Report (1003-007).

  4. Stop.

3Functional Location has no EquipmentMaintenance Not-Applicable
  1. Exclude Fn and note “No EQ/MI/WO – Business review if required for Target” in the Cleansing Report.
  2. 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.

  3. If you reach the top with no match, exclude the entire chain and include 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).
  • AFLOC = Asset Functional Location in target    

A Relevancy report (1003-010) shall be generated based on the above scenarios to manage the transformation. Report shall contain the below columns. 

Column  NameDetails
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 Plant

Maintenance Plant assigned to the Legacy Functional Location 

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.

Legacy Functional Location Description

Description of Functional Location in Source System

Hierarchy Level

Level where the Legacy Functional Location sits as part of Functional Location Hierarchy in Source System

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) if that policy applies). Else blank.

Proposed New Technical Object

Values: EQ, FL, Blank
Rule (evaluate in this order at the current level,):

  • Start at Fn and test these in order:

    1. Has Equipment (maintenance irrelevant) → Record this as FL (this will be AFLOC at Fn). All ancestors above Fn (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 (i.e no superior functional existing), include in the Cleansing Report (1003-007). Stop

    2. No Equipment, Has Maintenance →  Record Fn as EQ and Fn-1 as FL (AFLOC) and Stop. All ancestors above Fn-1 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

    3. No Equipment and No Maintenance → Record no object at Fn. Move to Fn-1 and re-apply the same checks as 1 and 2. If top is reached with no match, exclude the entire chain and keep it in the Cleansing Report for Business/DCT decision (1003-006). Stop

Has Equipment Installed? (Last Recorded)

Values: X or blank

Rule: This field must be blank in the initial extract. For subsequent extracts, populate this field by carrying forward the Has Equipment Under? value from the previous extract.

Populate this only for rows that are output/registered as a target object (i.e., rows you keep in the final output).

Leave this field blank in the initial extract. From subsequent extracts onward, populate it using the above rule

Has Maintenance Associated? (Last Recorded)

Values: X or blank

Rule: This field must be blank in the initial extract. For subsequent extracts, populate this field by carrying forward the Has Maintenance Associated? value from the previous extract.

Proposed New Technical Object (Last Recorded)

Values: EQ, FL
Rule: This field must be blank in the initial extract. For subsequent extracts, populate this field by carrying forward the Proposed New Technical Object value from the previous extract.

Not Relevant

Report to copy the values maintained in NOT_REL field of Functional Location DCT as maintained by Business for the respective Legacy Functional Location.

New Technical Object

Report to copy the values maintained in TGT_OBJECT field of Functional Location DCT as maintained by Business for the respective Legacy Functional Location.

New Functional Location

Report to copy the values maintained in TGT_TPLNR field of Functional Location DCT as maintained by Business for the respective Legacy Functional Location.

New Superior Functional Location

Report to copy the values maintained in TGT_TPLMA field of Functional Location DCT as maintained by Business for the respective Legacy Functional Location.

Business Verified

Report to copy the values maintained in BUS_VERF field of Functional Location DCT as maintained by Business for the respective Legacy Functional Location.

Review Status

Report to copy the values maintained in ZREVIEW_STATUS field of Functional Location DCT as maintained by Business for the respective Legacy Functional Location.

 

The data from legacy system excludes:

  1. Functional Location (IFLOT-TPLNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) Inactive 'INAC'
  2. Functional Location (IFLOT-TPLNR) with Active (JEST-INAC <> 'X') System Status (JEST-STAT) Deletion Flag 'DLFL'
  3. Functional Location (IFLOT-TPLNR) having Description (IFLOTX-PLTXT) containing words ('To be Deleted', 'DELETE')
  4. Functional Location (IFLOT-TPLNR) placed below the Functional Locations included in exclusion criteria 1-3
    </Start CR0416>
  5. Functional Location (IFLOT-TPLNR) to be migrated as Equipment which are part of mapping (Functional Location, where New Technical Object = 'EQ')
  6. Functional Location (IFLOT-TPLNR) with Superior Function Location (IFLOT-TPLMA) missing
  7. Functional Location (IFLOT-TPLNR) not satisfying both conditions of Inclusion Criteria 3
    </End CR0416>

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


The following illustrates the various scenarios for the relevant Functional Location and how to derive the "Proposed New Technical Object"

Level
Proposed Tech Object
Proposed Tech Object
Proposed Tech Object
Proposed Tech Object
1

FL

<Not Relevant>

(because no Superior FL)





2

FL

(E) (M)

<Blank>

(Because the below is proposed as FL)

FL

<Not Relevant>

(Because no maintenance, no EQ)

FL

(M)

<Blank>

(Because the below is proposed as FL)

FL

<Not Relevant>

(Because no maintenance, no EQ)

3

FL


<Not Relevant>

(Because no maintenance, no EQ)

FL

<Not Relevant>

(Because no maintenance, no EQ)

FL

<Not Relevant>

(Because no maintenance, no EQ)

FL

<Not Relevant>

(Because no maintenance, no EQ)

4

FL

(M)

This is Fn

EQ

 (Because there is no EQ installed)

FL

(M) (E)

<Blank>

(Because the below is proposed as FL)

FL

<Not Relevant>

(Because no maintenance, no EQ)

FL

(M)

 

<Blank>

(Because the below is proposed as EQ)

5

FL

(E)

This is Fn

FL

(Because there is EQ installed)

FL

(M) (E)

<Blank>

(Because the below is proposed as FL)

FL

(M)

This is Fn

EQ

 (Because there is no EQ installed)

6

FL

<Not Relevant>

(Because no maintenance, no EQ)

FL

(E) (M)

This is Fn

FL

(Because there is EQ installed)



7

FL

<Not Relevant>

(Because no maintenance, no EQ)





8

FL

<Not Relevant>

(Because no maintenance, no EQ)





9

FL

<Not Relevant>

(because no maintenance, no EQ)





Legend:

(E) Has Equipment Installed

(M) Has Maintenance


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget 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 Data 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 for plants 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

TableFieldData ElementField DescriptionData TypeLengthRequirement
IFLOTTPLNRTPLNRFunctional Location LabelCHAR30Mandatory
IFLOTTPLKZTPLKZStructure IndicatorCHAR80Mandatory
IFLOTFLTYPFLTYPCategoryCHAR1Mandatory
IFLOTDATABDATABStart-Up DateDATS8Conditional
IFLOTEQARTEQARTObject TypeCHAR10Conditional
IFLOTHERSTHERSTManufacturerCHAR30Conditional
IFLOTTYPBZTYPBZModel NumberCHAR20Conditional
IFLOTMAPARMAPARManufacturer Part NumberCHAR30Conditional
IFLOTHERLDHERLDCountry/Region of ManufactureCHAR3Conditional
IFLOTBAUJJBAUJJYear of ConstructionCHAR4Conditional
IFLOTBAUMMBAUMMMonth of ConstructionCHAR2Conditional
IFLOTSERGESERGEManufacturer Serial NumberCHAR30Conditional
IFLOTANSWTANSWTAcquisition ValueNUMC13Conditional
IFLOTWAERSWAERSCurrency KeyCHAR5Conditional
ILOASWERKSWERKMaintenance PlantCHAR4Conditional
ILOAEQFNREQFNRSort FieldCHAR30Conditional
ILOABEBERBEBERPlant SectionCHAR3Conditional
ILOAABCKZABCKZABC IndicatorCHAR1Conditional
IFLOTINGRPINGRPPlanner GroupCHAR3Conditional
IFLOTIWERKIWERKPlanning PlantCHAR4Conditional
CRHDGEWRKGEWRKMaintenance Work CenterCHAR8Conditional
CRHDWERGWWERGWWork Center PlantCHAR4Conditional
ILOABUKRSBUKRSCompany CodeCHAR4System
ILOAKOSTLKOSTLCost CenterCHAR10Conditional
IFLOTTPLMATPLMASuperior Functional LocationCHAR30Conditional
IFLOTIEQUIIEQUIEquipment Installation Is AllowedCHAR1Conditional
IFLOTSUBMTSUBMTConstruction TypeCHAR40Conditional
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 LabelCHAR30

Mandatory

(Key to link to Functional Location)

IFLOTXSPRASSPRASLanguage KeyLANG1Mandatory
IFLOTXPLTXTPLTXTDescription of Functional LocationCHAR40Mandatory

Note:

  • Each Category 'A' 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). 
  • Each Category 'O' and 'N' 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
IFLOTTPLNRTPLNRFunctional Location LabelCHAR30

Mandatory

(Key to link to Functional Location)

KSSKSTATUSTATUClassification StatusCHAR80Mandatory


 4. Functional Location Classification (Characteristics Value Allocation) 

TableFieldData ElementField DescriptionData TypeLengthRequirement
CABN

ATNAM

ATNAM

Characteristic NameCHAR30Mandatory
AUSPPOSNRPOSNR Item NumberCHAR3Mandatory
IFLOTTPLNRTPLNRFunctional Location LabelCHAR30

Mandatory

(Key to link to Functional Location)

AUSPATFLVATFLVNumerical Value - From NUMC16Conditional
AUSPATFLBATFLBNumerical Value - ToNUMC16Conditional
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
AUSPCURRENCYCURRENCYCurrency KeyCUKY5Conditional
AUSPATWRTATWRTCharacteristic ValueCHAR30Conditional
KSSKKLARTKLARTClass TypeCHAR20Mandatory
KSSKCLASSCLASSClass NameCHAR30Mandatory


5. Functional Location Partner

TableFieldData ElementField DescriptionData TypeLengthRequirement
IFLOTTPLNRTPLNRFunctional Location LabelCHAR30

Mandatory

(Key to link to Functional Location)

IHPAOBTYPOBTYPObject TypeCHAR3Mandatory
IHPAPARVWPARVWPartner FunctionCHAR2Mandatory
IHPAPARNRPARNRPartnerCHAR12Mandatory


6. Functional Location User Status

TableFieldData ElementField DescriptionData TypeLengthRequirement
IFLOTTPLNRTPLNRFunctional Location LabelCHAR30

Mandatory

(Key to link to Functional Location)

JSTOSTSMASTSMAStatus profile of the functional locationCHAR8Mandatory

JEST

STAT

STATStatus Number in User Status ListCHAR5Mandatory


7. Functional Location Long Text Header

TableFieldData ElementField DescriptionData TypeLengthRequirement
IFLOTTPLNRTPLNRFunctional Location LabelCHAR30

Mandatory

(Key to link to Functional Location)

STXHTDOBJECTTDOBJECTTexts: application objectCHAR10Mandatory
STXHTDNAMETDOBNAMENameCHAR70Mandatory
STXHTDIDTDIDText IDCHAR4Mandatory
STXHTDSPRASSPRASLanguage KeyLANG1Mandatory


8. Functional Location Long Text Line

TableFieldData ElementField DescriptionData TypeLengthRequirement
IFLOTTPLNRTPLNRFunctional Location LabelCHAR30

Mandatory

(Key to link to Functional Location)

STXLTDOBJECTTDOBJECTTexts: application objectCHAR10Mandatory
STXLTDNAMETDOBNAMENameCHAR70Mandatory
STXLTDIDTDIDText IDCHAR4Mandatory
STXLTDSPRASSPRASLanguage KeyLANG1Mandatory
STXLTDFORMATTDFORMATTag columnCHAR1Mandatory
STXLROWCOUNTROWCOUNTRow CountNUMC10Mandatory
STXLTDLINETDLINEText LineCHAR</Start CR0416>
72132
</End CR0416>
Mandatory

Note:

  1. Long Text is not mandatory, only load when there is data
  2. One Long Text Header must have at least 1 Long Text Line

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.


Data Cleansing

</Start CR0416>
Note: Criteria for Active Functional Locations -

  • having Maintenance Plant (IFLOT-WERKS) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes'); and
  • not having System Status Active (JEST-INAC <> 'X') (JEST-STAT) Inactive 'INAC'; and
  • not having System Status Active (JEST-INAC <> 'X') (JEST-STAT) Deletion Flag 'DLFL'; and
  • not having Description containing words ('To be Deleted', 'DELETE')

</End CR0416>

IDCriticalityError Message/Report DescriptionRuleOutputSource System
1003-001C1Asset (Category 'A') relevant Functional Location missing Technical Object TypeFunctional Locations as per Relevancy Criteria </Start CR0416> (excluding records from Functional Location mapping DCT where NOT_REL = 'X' or TGT_OBJECT = 'EQ' and BUS_VERF = 'X' ZREVIEW_STATUS = 'Completed') </End CR0416> with no Technical Object Type AssignedPlant, Functional Location, Functional DescriptionPF2, WP2
1003-002C3Info Report: Asset (Category 'A') relevant Functional Location missing Planner GroupFunctional Location as per Relevancy Criteria </Start CR0416> (excluding records from Functional Location mapping DCT where NOT_REL = 'X' or TGT_OBJECT = 'EQ' and BUS_VERF = 'X' ZREVIEW_STATUS = 'Completed') </End CR0416> with no Planner Group AssignedPlant, Functional Location, Functional DescriptionPF2, WP2
1003-003C2Asset (Category 'A') relevant Functional Location maintaining Acquisition Value but missing Currency Key

Functional Location as per relevancy criteria </Start CR0416> (excluding records from Functional Location mapping DCT where NOT_REL = 'X' or TGT_OBJECT = 'EQ' and BUS_VERF = 'X' ZREVIEW_STATUS = 'Completed') </End CR0416> where IFLOT_ANSWT <> '' (Blank) and IFLOT_WAERS = '' (Blank)

Plant, Functional Location, Functional Description, Superior Functional Location, Acquisition ValuePF2, WP2
1003-004C3Info Report : Asset (Category 'A') relevant Functional Location Long Text for CleansingFunctional Location as per Relevancy Criteria </Start CR0416> (excluding records from Functional Location mapping DCT where NOT_REL = 'X' or TGT_OBJECT = 'EQ' and BUS_VERF = 'X' ZREVIEW_STATUS = 'Completed')  </End CR0416> where Long Text Exist flag is assigned (IFLOTX-KZLTX) = 'X'. This is for manual review.Plant, Functional Location, Functional Location Description, Long Text Language, Row Number, Long Text LinePF2, WP2
1003-005C3

Info Report: Active but not relevant Functional Location (i.e not the Lowest Level Functional Location) but have Equipment installed or maintenance associated

Active but not relevant Functional Location (i.e not the Lowest Level Functional Location) but have either Equipment installed or maintenance associated

Plant, Functional Location, Functional Description, Superior Functional Location, Maintenance Exist, Equipment Exist PF2, WP2
1003-006C3Info Report: Active but not relevant Functional Location which don't have Equipment installed and maintenance associated

Active but not relevant Functional Location which don't have Equipment installed and maintenance associated

Plant, Functional Location, Functional Description, Superior Functional Location PF2, WP2
1003-007C3Info Report: Excluded Functional Location having Equipment installed or maintenance associated and missing Superior Functional Location

Relevant Functional Location but excluded due to missing Superior Functional Location but having either Equipment installed or maintenance associated

Plant, Functional Location, Functional Description, Maintenance Exist, Equipment Exist PF2, WP2
1003-008C3Info Report: Asset (Category 'A') relevant Functional Location missing Description in English Language

Functional Location as per the relevancy criteria </Start CR0416> (excluding records from Functional Location mapping DCT where ZREVIEW_STATUS = 'Out of Scope' NOT_REL = 'X' or TGT_OBJECT = 'EQ') </End CR0416> missing entries in IFLOTX where IFLOTX-SPRAS <> 'E'

Plant, Functional Location, Functional Description, Superior Functional Location, Language KeyPF2, WP2
</Start CR0416> 

 

  
1003-009C3Info Report: Functional Locations associated with incomplete or broken active Asset Structures

A) Functional Locations having Maintenance Plant (ILOA-SWERK) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes') and which belongs to below criteria:

  • Functional Location with System Status Active (JEST-INAC <> 'X') (JEST-STAT) Inactive 'INAC'
  • Functional Location with System Status Active (JEST-INAC <> 'X') (JEST-STAT) Deletion Flag 'DLFL'
  • Functional Location having Description containing words ('To be Deleted', 'DELETE')

B) All Functional Locations Levels having Maintenance Plant (ILOA-SWERK) in scope (Value Mapping : Plant, where Maintenance Plant = 'Yes') installed below the Functional Locations in (A)

Plant, Functional Location, Functional Description, Superior Functional LocationPF2, WP2
</End CR0416> 

 

  
1003-010C3Info Report : Initial relevancy report based on the scenarios documented in the Conversion Scope section

Functional Locations as per relevancy scenarios mentioned in Conversion Scope 

Source System, Plant, Legacy Functional Location,
</Start CR0416>
Functional Location Description, Hierarchy
 Level, Technical Object Type </End CR0416>, Has Equipment Under?, Has Maintenance Associated?, Proposed New Technical Object, Proposed Level

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 Functional Locations that need to be created to support the to-be design

Data Privacy and Sensitivity

Not Applicable


Extraction

Extract data from a source into Advanced Data Migration and Management (ADMM). There are 2 possibilities:

  1. The data exists. ADMM connects to the source and loads the data into ADMM. 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 ADMM; 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 ADMM.

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads.

Extraction Run Sheet

Req #Requirement DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team
2Google 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 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 (1003-010) 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 Data Construction Rules

Data ElementField DescriptionRule
zLegacyTPLNRFunctional Location Label

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 Asset Functional Location should only have a SNAV Functional Location as Superior Functional Location

Note:

For enriching PF2/WP2 data populate the Source Value of Functional Location.
For new Functional Location not existing in PF2/WP2 populate the Target Value of Functional Location.

FLTYPCategory

Mandatory

Allowed values for each Level of the Functional Location Structure:

O - Org
N - Nav
A - Asset

EQARTObject 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. 

HERSTManufacturer

Conditional

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

TYPBZModel Number

Conditional

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

MAPARManufacturer Part Number

Conditional

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

HERLDCountry/Region of Manufacture

Conditional

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

BAUJJYear of Construction

Conditional

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

BAUMMMonth of Construction

Conditional

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

SERGEManufacturer Serial Number

Conditional

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

ANSWTAcquisition Value

Conditional

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

WAERSCurrency Key

Conditional

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

SWERKMaintenance 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'.

EQFNRSort 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. 

BEBERPlant 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'.

INGRPPlanner 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'.

GEWRKMaintenance 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'.

zLegacyKOSTLCost 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'.

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 

SUBMTConstruction Type

Conditional

User must populate value for 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'.

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

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

NAME2Name 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'.

NAME3Name 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'.

NAME4Name 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_ENDescription (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 Functional Locations 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

</Start CR0283> 

 

PLTXT_FRDescription (French)

Guide for Description for Functional Location:

Conditional:

Category 'O' and 'N' Functional Locations: Mandatory

For Category 'A' Functional Location: Conditional - populate this field only when the Plant’s official language is French.

A = Technical Object Type Description (in French language)
B = Asset Tag (Sort Field)
C = Additional Description as provided by business (in French Language)

Functional Location Description = A+B+C

Cannot have duplicate records based on corresponding language text (2 Functional Locations cannot have the same French 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

PLTXT_ITDescription (Italian)

Guide for Description for Functional Location:

Conditional:

Category 'O' and 'N' Functional Locations: Mandatory

For Category 'A' Functional Location: Conditional - populate this field only when the Plant’s official language is Italian.

A = Technical Object Type Description (in Italian language)
B = Asset Tag (Sort Field)
C = Additional Description as provided by business (in Italian Language)

Functional Location Description = A+B+C

Cannot have duplicate records based on corresponding language text (2 Functional Locations cannot have the same Italian 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

PLTXT_ZHDescription (Mandarin)

Guide for Description for Functional Location:

Conditional:

Category 'O' and 'N' Functional Locations: Mandatory

For Category 'A' Functional Location: Conditional - populate this field only when the Plant’s official language is Mandarin.

A = Technical Object Type Description (in Mandarin language)
B = Asset Tag (Sort Field)
C = Additional Description as provided by business (in Mandarin Language)

Functional Location Description = A+B+C

Cannot have duplicate records based on corresponding language text (2 Functional Locations cannot have the same Mandarin 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

PLTXT_PTDescription (Brazilian Portuguese)

Guide for Description for Functional Location:

Conditional:

Category 'O' and 'N' Functional Locations: Mandatory

For Category 'A' Functional Location: Conditional - populate this field only when the Plant’s official language is Brazilian Portuguese.

A = Technical Object Type Description (in Brazilian Portuguese language)
B = Asset Tag (Sort Field)
C = Additional Description as provided by business (in Brazilian Portuguese Language)

Functional Location Description = A+B+C

Cannot have duplicate records based on corresponding language text (2 Functional Locations cannot have the same Brazilian Portuguese 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

PLTXT_DEDescription (German)

Guide for Description for Functional Location:

Conditional:

Category 'O' and 'N' Functional Locations: Mandatory

For Category 'A' Functional Location: Conditional - populate this field only when the Plant’s official language is German.

A = Technical Object Type Description (in German language)
B = Asset Tag (Sort Field)
C = Additional Description as provided by business (in German Language)

Functional Location Description = A+B+C

Cannot have duplicate records based on corresponding language text (2 Functional Locations cannot have the same German 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

PLTXT_ESDescription (Spanish)

Guide for Description for Functional Location:

Conditional:

Category 'O' and 'N' Functional Locations: Mandatory

For Category 'A' Functional Location: Conditional - populate this field only when the Plant’s official language is Spanish.

A = Technical Object Type Description (in Spanish language)
B = Asset Tag (Sort Field)
C = Additional Description as provided by business (in Spanish Language)

Functional Location Description = A+B+C

Cannot have duplicate records based on corresponding language text (2 Functional Locations cannot have the same Spanish 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_LCLanguage 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_LCDescription 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 Functional Locations 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

</End CR0283>

 

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_Z2Partner (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_N1Sequential Status in User Status Profile

Conditional

1. For Category 'O' and 'N' Functional Locations > Leave blank as it will be defaulted to 'PLAN'

2. For Category 'A' Functional Locations > Populate from allowed values:
    'PLAN'- Planned
    'COMM'- Commissioned
    'INSR'- In Service
    'OTSR'- Out Of Service
    'SCRP'- Scrap

If none is provided, it will be defaulted to 'PLAN'

STAT_X1Non-Sequential Status in the User Status Profile - EXHZ (Extremely Hazardous) 

Conditional

User to populate 'EXHZ' (Extremely Hazardous) status for Category 'A' Functional Locations if applicable. 

Category 'O' and 'N' Functional Locations to be left 'Blank'.

STAT_X2Non-Sequential Status in the User Status Profile - MTNA (Maintenance Not Allowed)

Conditional

For Category 'O' and 'N' Functional Locations > Leave blank as it will be defaulted to 'MTNA' (Maintenance Not Allowed)

For Category 'A' populate 'MTNA' (Maintenance Not Allowed) status if applicable. 

  

2. Functional Location Classification Data Construction Rules

Data ElementField DescriptionRule
zLegacyTPLNRFunctional Location Label

Mandatory

Key to link to Functional Location

Should exist in Functional Location Master DCT Rules

CLASSClass Name

</Start CR0283>

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 = EAM_TOT (Tech Object Type) of the Floc

User to populate below Class for each Functional Location -

  • General Class 'EAM_9999' ; and
  • Class having naming convention = EAM_<TOT> (Tech Object Type) of the Floc

</End CR0283>

ATNAMCharacteristic Name

Mandatory

User to populate Characteristic assigned to the Class 'EAM_9999' and Class having naming convention = EAM_<TOT> (Tech Object Type) of the Floc

ATWRTCharacteristic Value

Conditional.

  • If the characteristic has character format (CHAR), populate with alphanumeric characters.
  • 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)
POSNRItem Number

Conditional

Sequential number to be maintained if multiple values are being recorded for the same Characteristic


3. Functional Location Long Text Data Construction Rules

Data ElementField DescriptionRule
zLegacyTPLNRFunctional Location Label

Mandatory

Key to link to Functional Location

Should exist in Functional Location Master DCT Rules

TDLINE_ENText Line (English)

Conditional

User to populate Free Text in English Language as applicable

TDSPRAS_LCLanguage 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

TDLINE_LCText 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. Inclusion-FL Long Text Data Construction Rules

Data ElementField DescriptionRule
zLegacyTPLNRLegacy Functional Location Label

Mandatory

Values: Legacy Functional Location 

zLegacyWERKSLegacy Plant

Mandatory

zLegacySPRASLegacy Language Key

Mandatory.

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

Note: Only Long Texts that are added into this list will be migrated.


5Functional Location Data Construction Rules

Data ElementField DescriptionRule
Legacy Plant

Maintenance Plant assigned to the Legacy Functional Location 

Mandatory

Values: Legacy Maintenance Plant

This field must not be edited.

zLegacyTPLNRLegacy Functional Location Label

Mandatory

Values: Legacy Functional Location 

This field must not be edited.

EQUIP_EXISTHas Equipment Under?

Conditional

Values: 'X' or blank

This field must not be edited.

MAINT_EXISTHas Maintenance Associated?

Conditional

Values: 'X' or blank

This field must not be edited.

PRP_OBJECTProposed New Technical Object

Conditional

Values: 'EQ', 'FL' or blank

This field must not be edited.

NOT_RELNot Relevant

Conditional

Values: 'X' or blank

TGT_OBJECTNew Technical Object

Conditional

Allowed Values: 'EQ', 'FL'

User to populate same value as PRP_OBJECT if acceptable else assign appropriate allowed value. 

TGT_TPLNRNew Functional Location

Conditional

User to populate the Asset Functional Location value as per the target structure indicator edit mask if TGT_OBJECT = 'FL' 

Asset Layer (SAST) = 'XXXXXXNNNNNN'
X = Unit (first letter)
XXXX = Asset function 4-letter codes
NNNNNN = Running Numbers

Else Blank

Note - The Edit Mask might change based on the final configuration

TGT_TPLMANew Superior Functional Location

Conditional

User to populate appropriate Category 'N' Functional Location value from the Functional Location Master DCT

BUS_VERFBusiness Verified

Mandatory

Allowed Values: 'Yes', 'No'
User to populate 'Yes' if Legacy-Target mapping is acceptable.

ZREVIEW_STATUSReview Status

Mandatory

User to select appropriate value from drop down


</Start CR0283>

 6. ENR-Functional Location Master Data Construction Rules

Data ElementField DescriptionRule
zLegacyTPLNRFunctional Location Label

Mandatory

Values: Legacy Functional Location must exists in PF2/ WP2

EQARTObject Type

Conditional

Allowed values from T370K to be populated.

EQFNRSort Field

Conditional

Sort Field is used to store the Plant Tag ID.

Sort Field + Maintenance Plant should be unique combination. 

BEBERPlant Section

Conditional

Allowed values from T357 to be populated.

INGRPPlanner Group

Conditional

Allowed values from T024I to be populated

GEWRKMaintenance Work Center

Conditional

Allowed values from Work Centre DCT to be populated. 

zLegacyKOSTLCost Center

Conditional

Allowed Values: maintained in R2R Cost Centre Value Mapping

SUBMTConstruction Type

Mandatory

Allowed values from Assembly DCT to be populated

BRGEWWeight of Object

Conditional

Populate if information exists

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 NAME1-4 fields with the Name and Location of the Asset

NAME2Name 2

Conditional

User to populate NAME1-4 fields with the Name and Location of the Asset

NAME3Name 3

Conditional

User to populate NAME1-4 fields with the Name and Location of the Asset

NAME4Name 4

Conditional

User to populate NAME1-4 fields with the Name and Location of the Asset

PLTXT_EN

Mandatory

Guide for Description for 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 Functional Locations 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
"       
Description of Functional Location (English) Double Quotes

SPRAS_LCLanguage 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:

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 Functional Locations 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_Z1Partner (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_Z2Partner (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

</End CR0283>

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


Extraction Dependencies

Item #Step DescriptionTeam 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:

  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 – 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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location

For PF2 Functional Locations use Value Mapping: Functional Location (where NOT_REL = Blank and TGT_OBJECT = 'FL' or 'EQ'  and BUS_VERF = 'X' ZREVIEW_STATUS = 'Completed')

</Start CR0416>

For WP2 Functional Locations - 

  • Get Functional Location from (IFLOS-STRNO) where IFLOS-TPLNR = IFLOT-TPLNR and IFLOS-ACTVS = 'X'
  • Use Value Mapping: Functional Location (where NOT_REL = Blank and TGT_OBJECT = 'FL' or 'EQ' and BUS_VERF = 'X' ZREVIEW_STATUS = 'Completed'

</End CR0416>

2----S/4 HanaIFLOTTPLKZStructure Indicator

Default to 'SAST'

3----S/4 HanaIFLOTFLTYPCategory

Default to 'A'

4----S/4 HanaIFLOTDATABStart-Up Date

If IEQUI (Equipment Installation Is Allowed) = Blank and and derived Target User Status for Functional Location from Functional Location User Status (STAT) Transformation Rules (ECC) is either of the below:
'COMM' (Commissioned)
'INSR' (In Service)
'OTSR' (Out of Service)
'SCRP' (Scrap)
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 HanaIFLOTEQARTObject Type

Value mapping : Asset_Technical Object Type.

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

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 KeyS/4 HanaIFLOTWAERSCurrency KeyDirect Mapping
15PF2, WP2ILOASWERKMaintenance PlantS/4 HanaILOASWERKMaintenance PlantValue Mapping: Plant (Maintenance Plant = Yes)
16

PF2, WP2


ILOAEQFNRSort FieldS/4 HanaILOAEQFNRSort Field

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

17

PF2, WP2

ILOA

BEBER

Plant Section

S/4 HanaIFLOTBEBERPlant Section

Value mapping : Plant Section.

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

18----S/4 HanaIFLOTABCKZABC Indicator

Derive the Indicator based on below logic -

  • Aggregate values for all Characteristics assigned (in Target CABN) to the Functional Location which are relevant for Asset Criticality Analysis i.e having Characteristic Group (CABN_ATKLA) with Characteristic Group Name (TCMGT_ATKLT) = 'Criticality Risk Scoring' 
  • 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'
19PF2, WP2IFLOTINGRPPlanner GroupS/4 HanaILOAINGRPPlanner Group

Value mapping : Maintenance Planner Group

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

20PF2, WP2ILOAIWERKPlanning PlantS/4 HanaIFLOTIWERKPlanning PlantValue Mapping: Plant (Maintenance Plant = Yes)
21PF2, WP2IFLOTGEWRKMaintenance Work CenterS/4 HanaIFLOTGEWRKMaintenance Work Center

Value mapping : Work Center A2D 

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

22PF2, WP2IFLOTWERGWWork Center PlantS/4 HanaIFLOTWERGWWork Center Plant

Value Mapping: Plant (Maintenance Plant = Yes)

23----S/4 HanaILOABUKRSCompany CodeDerive the Company code from table 'T001K' where Target IFLOT_SWERK (Maintenance Plant) = T001K_BWKEY
24PF2, WP2ILOAKOSTLCost CenterS/4 HanaILOAKOSTLCost Center

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment). 

Value Mapping : Cost Center

25----S/4 HanaILOATPLMASuperior Functional Location

Derive the TPLMA from TGT_TPLNR as per Value Mapping: Functional Location (using zLegacyTPLNR = ECC TPLNR)

26----S/4 HanaILOAIEQUIEquipment Installation Is Allowed

Derive based on Value Mapping: Functional Location.

If EQUIP_EXIST = 'X' and TGT_OBJECT='FL', where TPLNR = zLegacyTPLNR, then assign 'X' , else '' Blank

27PF2, WP2IFLOTSUBMTConstruction TypeS/4 HanaILOASUBMTConstruction Type

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

Value Mapping : Assembly and Construction Type

28----S/4 HanaILOAKOKRSControlling AreaDefault to 'CO01' (SYSQ Controlling Area)
29PF2, WP2IFLOTBRGEWWeight of ObjectS/4 HanaIFLOTBRGEWWeight of Object

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

30PF2, WP2IFLOTGEWEIUnit of WeightS/4 HanaIFLOTGEWEIUnit of Weight

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

31PF2, WP2ADRCNAME1Name 1S/4 HanaADRCNAME1Name 1

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

32PF2, WP2ADRCNAME2Name 2S/4 HanaADRCNAME2Name 2

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

33PF2, WP2ADRCNAME3Name 3S/4 HanaADRCNAME3Name 3

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

34PF2, WP2ADRCNAME4Name 4S/4 HanaADRCNAME4Name 4

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

35----S/4 HanaADRCCOUNTRYCountry/Region Key

Derive Country/ Region from Table T001W where Target SWERK (Maintenance Plant) = T001K_WERKS


2. Functional Location Master Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaIFLOTTPLKZStructure Indicator

Derive based on logic:

If FLTYP = 'O' then TPLKZ = 'SORG'

If FLTYP = 'N' then TPLKZ = 'SNAV'

If FLTYP = 'A' then TPKLZ = 'SAST'

3DCTIFLOTFLTYPCategoryS/4 HanaIFLOTFLTYPCategoryDirect Mapping
4--- -S/4 HanaIFLOTDATABStart-Up Date

If FLTYP = 'O' or 'N' then INBDT = ' ' (Blank)

Else

For FLTYP = 'A'

If IEQUI (Equipment Installation Is Allowed) = Blank and derived Target User Status for Functional Location from Functional Location User Status (STAT) Transformation Rules (ECC) is either of the below:
'COMM' (Commissioned)
'INSR' (In Service)
'OTSR' (Out of Service)
'SCRP' (Scrap)
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

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 KeyS/4 HanaIFLOTWAERSCurrency KeyDirect Mapping
15DCT IFLOTSWERKMaintenance PlantS/4 HanaIFLOTSWERKMaintenance PlantDirect Mapping
16DCT IFLOTEQFNRSort FieldS/4 HanaIFLOTEQFNRSort FieldDirect Mapping
17DCT IFLOTBEBERPlant SectionS/4 HanaIFLOTBEBERPlant SectionDirect Mapping
18----S/4 HanaIFLOTABCKZABC Indicator

Derive the Indicator based on below logic -

  • Aggregate values for all Characteristics assigned (in Target CABN) to the Functional Location which are relevant for Asset Criticality Analysis i.e having Characteristic Group (CABN_ATKLA) with Characteristic Group Name (TCMGT_ATKLT) = 'Criticality Risk Scoring' 
  • 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'
19DCT IFLOTINGRPPlanner GroupS/4 HanaILOAINGRPPlanner GroupDirect Mapping
20----S/4 HanaIFLOTIWERKPlanning PlantCopy the same value as Target SWERK (Maintenance Plant)
21DCT IFLOTGEWRKMaintenance Work CenterS/4 HanaIFLOTGEWRKMaintenance Work CenterDirect Mapping
22----S/4 HanaIFLOTWERGWWork Center Plant

Copy the same value as Target SWERK (Maintenance Plant)

23----S/4 HanaILOABUKRSCompany CodeDerive the Company code from table 'T001K' where Maintenance Plant populated in DCT = T001K_BWKEY
24DCT ILOAzLegacyKOSTLCost CenterS/4 HanaILOAKOSTLCost CenterValue mapping : Cost Center
25DCT IFLOTTPLMASuperior Functional LocationS/4 HanaILOATPLMASuperior Functional LocationDirect Mapping
26----S/4 HanaILOAIEQUIEquipment Installation Is AllowedDefault to 'X'
27DCT IFLOTSUBMTConstruction TypeS/4 HanaILOASUBMTConstruction TypeValue Mapping :Assembly and Construction Type  
28---- S/4 HanaILOAKOKRSControlling AreaDefault to 'CO01' (SYSQ Controlling Area)
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
35----S/4 HanaADRCCOUNTRYCountry/Region KeyDerive Country/ Region from Table T001W where Target SWERK (Maintenance Plant) = T001K_WERKS


3. Functional Location Short Text Transformation Rule (ECC) 

</Start CR0283>

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location

Value Mapping: Functional Location (where NOT_REL = Blank)

2PF2, WP2IFLOTXSPRASLanguage KeyS/4 HanaIFLOTXSPRASLanguage KeyDirect Mapping
3PF2, WP2IFLOTXPLTXTDescription of Functional LocationS/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

For Legacy entries where SPRAS = 'E'

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location

Value Mapping: Functional Location (where NOT_REL = Blank)

2PF2, WP2IFLOTXSPRASLanguage KeyS/4 HanaIFLOTXSPRASLanguage Key

Default to 'E'

3ENR_DCTIFLOTXPLTXTDescription of Functional LocationS/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping from PLTXT_EN from ENR-Functional Location DCT if provided (as part of enrichment)

UNION

For Legacy entries where SPRAS = Local language of the Plant associated to the Functional Location. Only add a record if the local language is not english

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location

Value Mapping: Functional Location (where NOT_REL = Blank)

2----S/4 HanaIFLOTXSPRASLanguage Key

Derive Language Key (T001W-SPRAS) from Table T001W where S4 SWERK  (Maintenance Plant) = T001W-WERK

3ENR_DCTIFLOTXPLTXTDescription of Functional LocationS/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping from PLTXT_LC from  ENR-Functional Location DCT if provided (as part of enrichment)

Note : Legacy entries to be filtered for SPRAS = 'E' and the Local language of the Plant associated to the Functional Location. 

</End CR0283>


4. Functional Location Short Text Transformation Rule (DCT) 

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

Direct Mapping

UNION

</Start CR0283>

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2DCTIFLOTXSPRAS_LCLanguage KeyS/4 HanaIFLOTXSPRASLanguage KeyDirect Mapping
3DCTIFLOTX

PLTXT_LC

Description of Functional Location (Local Language of Plant)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'F'
3DCTIFLOTX

PLTXT_FR

Description of Functional Location (French)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'I'
3DCTIFLOTX

PLTXT_IT

Description of Functional Location (Italian)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

 UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to '1'
3DCTIFLOTX

PLTXT_ZH

Description of Functional Location (Mandarin)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

 UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'P'
3DCTIFLOTX

PLTXT_PT

Description 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
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'D'
3DCTIFLOTX

PLTXT_DE

Description of Functional Location (German)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

 UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaIFLOTXSPRASLanguage KeyDefault to 'S'
3DCTIFLOTX

PLTXT_ES

Description of Functional Location (French)S/4 HanaIFLOTXPLTXTDescription of Functional Location

Direct Mapping

  </End CR0283>


5a. Functional Location Classification Transformation Rule (ECC) - KSSK

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location

Value Mapping: Functional Location (where NOT_REL = Blank)

2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaKSSKOBTABName of Database Table for ObjectDefault to 'IFLOT'
4PF2, WP2KSSKCLASSClass NameS/4 HanaKSSKCLASSClass Name

</Start CR0283>

Value mapping : Class A2D

Default below Classes :

  • 'EAM_9999' ; and
  • Class having naming convention = EAM_<TOT> (Tech Object Type) of the Floc

</End CR0283>

5b. Functional Location Classification Transformation Rule (ECC) - AUSP

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2CABNATNAMCharacteristic NameS/4 HanaAUSPATNAMCharacteristic Name

Step1- Use Value mapping: Characteristic A2D (Staging) to get the Staging Characteristic;

Step2 - Use Value mapping: Characteristic A2D to get the Target Characteristic

2

</Start CR0283>

3----S/4 HanaKSSKCLASSClass Name

Derive CLASS from the Class-Characteristic Assignment DCT based on the S4 Characteristic (ATNAM)

4

</End CR0283>

5PF2, WP2AUSPADZHLItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping
6PF2, WP2AUSPATFLVNumerical Value - FromS/4 HanaAUSPATFLVNumerical Value - From (Floating Point)Convert existing Legacy value to Float
7PF2, WP2AUSPATFLBNumerical Value - ToS/4 HanaAUSPATFLBNumerical Value - To (Floating Point)Convert existing Legacy value to Float
8PF2, WP2AUSPATFLVDate Interval - FromS/4 HanaAUSPDATE_FROMLower Boundary for Date - IntervalConvert existing Legacy value to Float
9PF2, WP2AUSPATFLBDate Interval - ToS/4 HanaAUSPDATE_TOUpper Boundary for Date - IntervalConvert existing Legacy value to Float
10PF2, WP2AUSPATFLVTime Interval - FromS/4 HanaAUSPTIME_FROMLower Boundary for Time - IntervalConvert existing Legacy value to Float
11PF2, WP2AUSPATFLBTime Interval - ToS/4 HanaAUSPTIME_TOUpper Boundary for Time - IntervalConvert existing Legacy value to Float
12PF2, WP2AUSPATFLVCurrency Value - FromS/4 HanaAUSPATFLVCurrency Value - From (Floating Point)Convert existing Legacy value to Float
13PF2, WP2AUSPATFLBCurrency Value - ToS/4 HanaAUSPATFLBCurrency Value - To (Floating Point)Convert existing Legacy value to Float
14PF2, WP2AUSPATWRTCharacteristic ValueS/4 HanaAUSPATWRTCharacteristic ValueDirect Mapping


6. Functional Location Classification Transformation Rule (DCT)

Only get the records where Characteristics with Data Type = CHAR

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaKSSKOBTABName of Database Table for ObjectDefault to 'IFLOT'
4DCTKSSKCLASSNUMClass NameS/4 HanaKSSKCLASSClass Name

Direct Mapping

5DCTAUSPATNAMCharacteristic NameS/4 HanaAUSPATNAMCharacteristic NameValue Mapping: Characteristic A2D
6DCTAUSPATWRTCharacteristic ValueS/4 HanaCAWNATWRTCharacteristic ValueDirect Mapping
7DCTAUSPPOSNRItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping

Only get the records where Characteristics with Data Type = CURR

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaKSSKOBTABName of Database Table for ObjectDefault to 'IFLOT'
4DCTKSSKCLASSNUMClass NameS/4 HanaKSSKCLASSClass Name

Direct Mapping

5DCTAUSPATNAMCharacteristic NameS/4 HanaAUSPATNAMCharacteristic NameDirect Mapping
6DCTAUSPATWRTCharacteristic Value S/4 HanaCAWNATFLVCharacteristic Value (From)

If range: values concatenated using " - ", derive the value before " - ".

Otherwise, direct mapping.

7DCTAUSPATWRTCharacteristic ValueS/4 HanaCAWNATFLBCharacteristic Value (To)

If range: values concatenated using " - ", derive the value after " - ".

Otherwise, direct mapping.

8----S/4 HanaAUSPCURRENCYCurrency KeyDerive from Currency Key of the Characteristics
9DCTAUSPPOSNRItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping

Only get the records where Characteristics with Data Type = DATE

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaINOBOBTABName of Database Table for ObjectDefault to 'IFLOT'
4DCTKSSKCLASSNUMClass NameS/4 HanaKSSKCLASSClass Name

Direct Mapping

5DCTAUSPATNAMCharacteristic NameS/4 HanaAUSPATNAMCharacteristic NameDirect Mapping
6DCTAUSPATWRTCharacteristic ValueS/4 HanaCAWNDATE_FROMCharacteristic Value (From)

If range: values concatenated using " - ", derive the value before " - ".

Otherwise, direct mapping.

7DCTAUSPATWRTCharacteristic ValueS/4 HanaCAWNDATE_TOCharacteristic Value (To)

If range: values concatenated using " - ", derive the value after " - ".

Otherwise, direct mapping.

8DCTAUSPPOSNRItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping

Only get the records where Characteristics with Data Type = NUM

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaKSSKOBTABName of Database Table for ObjectDefault to 'IFLOT'
4DCTKSSKCLASSNUMClass NameS/4 HanaKSSKCLASSClass Name

Direct Mapping

5DCTAUSPATNAMCharacteristic NameS/4 HanaAUSPATNAMCharacteristic NameDirect Mapping
6DCTAUSPATWRTCharacteristic ValueS/4 HanaCAWNATFLVCharacteristic Value (From)

If range: values concatenated using " - ", derive the value before " - ".

Otherwise, direct mapping.

7DCTAUSPATWRTCharacteristic ValueS/4 HanaCAWNATFLBCharacteristic Value (To)

If range: values concatenated using " - ", derive the value after " - ".

Otherwise, leave blank.

8DCTAUSPPOSNRItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping

 Only get the records where Characteristics with Data Type = TIME

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2----S/4 HanaKSSKKLARTClass TypeDefault to '003'
3----S/4 HanaKSSKOBTABName of Database Table for ObjectDefault to 'IFLOT'
4DCTKSSKCLASSNUMClass NameS/4 HanaKSSKCLASSClass Name

Direct Mapping

5DCTAUSPATNAMCharacteristic NameS/4 HanaAUSPATINNCharacteristic NameDirect Mapping
6DCTAUSPATWRTCharacteristic Value S/4 HanaCAWNTIME_FROMCharacteristic Value (From)

If range: values concatenated using " - ", derive the value before " - ".

Otherwise, direct mapping.

7DCTAUSPATWRTCharacteristic ValueS/4 HanaCAWNTIME_TOCharacteristic Value (To)

If range: values concatenated using " - ", derive the value after " - ".

Otherwise, direct mapping.

8DCTAUSPPOSNRItem NumberS/4 HanaAUSPPOSNRItem NumberDirect Mapping


7. Functional Location Partner Transformation Rule (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2-

-

-

-S/4 HanaIHPAOBTYPObject TypeDefault to 'IFL'
3-

-

-

-S/4 HanaIHPAPARVWPartner FunctionDefault to 'Z1' (Asset Owner)
4ENR_DCTIHPAzLegacyPARNR_Z1Partner (Asset Owner)S/4 HanaIHPAPARNRPartner

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment).

Value mapping : Vendor Number

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2-

-

-

-S/4 HanaIHPAOBTYPObject TypeDefault to 'IFL'
3-

-

-

-S/4 HanaIHPAPARVWPartner FunctionDefault to 'Z2' (Asset Maintainer)
4ENR_DCTIHPAzLegacyPARNR_Z2Partner (Asset Maintainer)S/4 HanaIHPAPARNRPartner

Overwrite with ENR-Functional Location DCT if provided (as part of enrichment)

Value mapping : Vendor Number


7a. Functional Location Partner Transformation Rule (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2-

-

-

-S/4 HanaIHPAOBTYPObject TypeDefault to 'IFL'
3-

-

-

-S/4 HanaIHPAPARVWPartner FunctionDefault to 'Z1' (Asset Owner)
4DCTIHPAzLegacyPARNR_Z1Partner (Asset Owner)S/4 HanaIHPAPARNRPartner

Direct Mapping

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaIFLOTTPLNRFunctional LocationDirect Mapping
2-

-

-

-S/4 HanaIHPAOBTYPObject TypeDefault to 'IFL'
3-

-

-

-S/4 HanaIHPAPARVWPartner FunctionDefault to 'Z2' (Asset Maintainer)
4DCTIHPAzLegacyPARNR_Z2Partner (Asset Maintainer)S/4 HanaIHPAPARNRPartner

Direct Mapping


8. Functional Location User Status Transformation Rules (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaIFLOTTPLNRFunctional Location

Value Mapping: Functional Location (where NOT_REL = Blank)

3----S/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 List

Value Mapping : User Status Functional Location. 

For legacy values in the value mapping, where there is 1: many entries, add additional record in the target for the functional location

5-

-

-

-S/4 Hana

JEST

INACT

Indicator: Status Is InactiveDefault to '' (Blank)

Note: Filter on TJ30T for Status Profiles with ESTAT starting with E*. 


9. Functional Location User Status Transformation Rules (DCT)

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

JEST

STAT_N1

Sequential Status in the User Status ProfileS/4 Hana

JEST

STAT

Status Number in User Status List

Default 'PLAN' for Category 'O' and 'N' 

For Category 'A':
Direct Mapping. If blank, default to 'PLAN'

4----S/4 Hana

JEST

INACT

Indicator: Status Is InactiveDefault to '' (Blank)

UNION

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

JEST

STAT_X1

Non-Sequential Status in the User Status Profile - EXHZ (Extremely Hazardous) S/4 Hana

JEST

STAT

Status Number in User Status List

Default Blank for Category 'O' and 'N' 

For Category 'A':
Direct Mapping

4----S/4 Hana

JEST

INACT

Indicator: Status Is InactiveDefault to '' (Blank)

UNION

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

JEST

STAT_X2

Non-Sequential Status in the User Status Profile - MTNA (Maintenance Not Allowed)S/4 Hana

JEST

STAT

Status Number in User Status List

Default to 'MNTA' (Maintenance Not Allowed) for Category 'O' and 'N'

For Category 'A':
Direct Mapping

4----S/4 Hana

JEST

INACT

Indicator: Status Is InactiveDefault to '' (Blank)


10. 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'
2PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaSTXHTDNAMEName

Value Mapping: Functional Location (where NOT_REL = Blank)

3----S/4 HanaSTXHTDIDText IDDefault to 'LTXT'
4PF2, WP2STXHTDSPRASLanguage KeyS/4 HanaSTXHTDSPRASLanguage KeyDirect Mapping

Note: Only the records marked as Cleansed in Inclusion-FL Long Text will be migrated


11. Functional Location Long Text Header (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HanaSTXHTDOBJECTTexts: application objectDefault to 'IFLOT'
2DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaSTXHTDNAMEName

Direct Mapping

3----S/4 HanaSTXHTDIDText IDDefault to 'LTXT'
4DCTSTXHTDSPRASLanguage KeyS/4 HanaSTXHTDSPRASLanguage KeyDefault to 'E'

UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HanaSTXHTDOBJECTTexts: application objectDefault to 'IFLOT'
2DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaSTXHTDNAMEName

Direct Mapping

3----S/4 HanaSTXHTDIDText IDDefault to 'LTXT'
4DCTSTXHTDSPRAS_LCLanguage KeyS/4 HanaSTXHTDSPRASLanguage KeyDirect Mapping


12. Functional Location Long Text Line (ECC)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HanaSTXLTDOBJECTTexts: application objectDefault to 'IFLOT'
2PF2, WP2IFLOTTPLNRLegacy Functional Location LabelS/4 HanaSTXHTDNAMEName

Value Mapping: Functional Location (where NOT_REL = Blank)

3----S/4 HanaSTXLTDIDText IDDefault to 'LTXT'
5PF2, WP2STXHTDSPRASLanguage KeyS/4 HanaSTXLTDSPRASLanguage KeyDirect Mapping
6----S/4 HanaSTXLTDFORMATTag columnDefault to "*"
7PF2, WP2STXLROWCOUNTRow NumberS/4 HanaSTXLROWCOUNTRow NumberDirect Mapping
8PF2, WP2STXLTDLINEText LineS/4 HanaSTXLTDLINEText Line

Direct Mapping

</Start CR0416>

Convert to Upper Case

</End CR0416> 

Note: Only the records marked as Cleansed in Inclusion-FL Long Text will be migrated


13. Functional Location Long Text Line (DCT)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HanaSTXHTDOBJECTTexts: application objectDefault to 'IFLOT'
2DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaSTXHTDNAMEName

Direct Mapping

3----S/4 HanaSTXHTDIDText IDDefault to 'LTXT'
4DCTSTXHTDSPRASLanguage KeyS/4 HanaSTXHTDSPRASLanguage KeyDefault to 'E'
5----S/4 HanaSTXLTDFORMATTag columnDefault to "*"
</Start CR0416>  


 


 
6----S/4 HanaSTXLROWCOUNTRow NumberFor each 132-character string generated, create a separate target row and increment the row number by 1 in sequence until the complete text is split.
7DCTSTXLTDLINE_ENText LineS/4 HanaSTXLTDLINEText Line

Direct Mapping

Convert to Upper Case

Split the DCT long text into consecutive 132-character strings. For each 132-character string generated, create a separate target row and increment the row counter by 1 in sequence until the complete text is split.

</End CR0416> 

 
 



UNION

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1----S/4 HanaSTXHTDOBJECTTexts: application objectDefault to 'IFLOT'
2DCTIFLOTzLegacyTPLNRFunctional Location LabelS/4 HanaSTXHTDNAMEName

Direct Mapping

3----S/4 HanaSTXHTDIDText IDDefault to 'LTXT'
4DCTSTXHTDSPRAS_LCLanguage KeyS/4 HanaSTXHTDSPRASLanguage KeyDirect Mapping
5----S/4 HanaSTXLTDFORMATTag columnDefault to "*"
</Start CR0416> 


 


 
6----S/4 HanaSTXLROWCOUNTRow NumberFor each 132-character string generated, create a separate target row and increment the row number by 1 in sequence until the complete text is split.
7DCTSTXLTDLINE_LCText LineS/4 HanaSTXLTDLINEText Line

Direct Mapping

Convert to Upper Case

Split the DCT long text into consecutive 132-character strings. For each 132-character string generated, create a separate target row and increment the row counter by 1 in sequence until the complete text is split.

</End CR0416>

 
 



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

List of Custom Target Reports for this object is maintained hereConversion Specification - Custom Reports Register.


Transformation Mapping
Mapping Table NameMapping Table Description
OTH_Migration_Date Relevant Values A2DDates to be defaulted for A2D objects for each Migration Cycle
Assembly and Construction Type  

Mapping of legacy Assembly / Construction Type to new Assembly / Construction Type

Characteristic A2D (Staging)Old to Staging Characteristic A2D
Characteristic A2DOld to New Characteristic A2D
Class A2DOld to New Class A2D
Cost CentreOld to New Cost Center
Functional LocationList of relevant Asset Functional Locations slated for migration, including the Target Technical Object. This will also be used for Old to New Functional Location Mapping
Maintenance Planner GroupOld to New Planner Group
PlantOld Plant to New Plant
Plant SectionOld to new Plant Section
Technical Object TypeOld to new Technical Object Type

User Status Function Location

Old to New Functional Location User Status

Vendor Number

LIFNR: Old Vendor Code to New Vendor Code

Work Centre A2DOld to new Work Centre A2D
</Start CR0282>  

OTH_Technical Object Type_APM


List of Functional Location and Equipment TOTs required for migrating historical Measurement Documents and Notifications

OTH_Plant_APM

List of Plants required for migrating historical Measurement Documents and Notifications

</End CR0282> 

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 DescriptionTeam Responsible
1Ensure DCT tables completenessSyWay Data Team
2Ensure all Transformation mappings are up to dateSyWay Data Team


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

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, 1003c, 1003d 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 TypeError DescriptionAction 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

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
  • For Category 'A' Functional Location, if User Status is 'Blank', it will be defaulted 'PLAN' User Status. Cat 'O' and 'N' will be populated with both 'PLAN' and 'MTNA' statuses only.
  • For legacy Functional Locations existing at a higher level (GBU, Plant etc) and having a Notification/ Work Order/ Maintenance Item associated, Business would review and apply one of the following option -  
    • Cleanse in legacy i.e re-assign the Notification/ Work Order/ Maintenance Item to a Asset Level Functional Location
    • Create the legacy Functional Location as a Asset Level Functional Location in Target
    • Map the legacy Functional Location to a existing Asset Level Functional Location in Target
  • Any Functional Location relevant for Asset Integration shall be migrated as Equipment and flagged in the Functional Location Mapping.

See also

Change log

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