| Status | |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Purpose
The purpose of this document is to define the conversion approach to create Functional Location in S/4 HANA.
Legacy Functional Locations are using a diverse range of formats across the different systems. There are instances where the same Functional Locations are duplicated within and across sources, with informal words. This results in data inconsistency. As per SyWay design, EAM Functional Locations will be standardized.
Conversion Scope
The scope of this document covers the approach for converting active Functional Location from Legacy Source Systems into S/4HANA following the Functional Location Master Data Design Standard.
Functional Locations are technical objects that structure the maintainable objects of a company. They can represent either the location of a maintainable item, or the maintainable item itself. A functional location does not normally change and will record the history of all equipment that is installed at that location.
Syensqo utilizes Functional Locations (FLOC) within the SAP S/4HANA system to define and manage its Asset Hierarchy. The asset hierarchy is structured across three main categories:
- Organisational Level - This level represents the enterprise structure of Syensqo. It defines:
The Company
The Global Business Unit (GBU)
The Plant
Navigational Level - This level structures the hierarchy based on the functional or geographical layout of the plant. It defines:
- Units within the Plant
- Further sub-levels based on the physical location or logical grouping of assets, enabling effective representation and navigation within the hierarchy
- Asset Level - This is the installation level where the actual Assets and Sub-assets are physically located. It includes:
- Specific installation points for equipment
- Maintainable assets themselves, serving as key points for maintenance planning and execution
The data from legacy system includes:
- Functional Location with system status - Not ‘INAC’ (Inactive)
- Relevancy Criteria 2
The data from legacy system excludes:
- Exclusion Criteria 1
- Exclusion Criteria 2
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
PF2, WP2 | An initial extract will be provided to the business to evaluate. Additional data/records may be required and these will be constructed via DCT. Enrichment of in-scope data may be required and will be added via transformation rules (business/technical). | 213,758 | S/4HANA | 213,758 |
Additional Information
Multi-language Requirement
- Functional Location description will be made available in <list of languages>.
- Multi language is supported for Functional Locations. <Applicable languages> can be created upon master data creation using English Logon.
Document Management
- <Types of documents> documents currently attached to Functional Locations will be migrated to <TBD>.
- Refer to the conversion approach for <TBD>.
Legal Requirement
Not Applicable
Special Requirements
Not Applicable
Target Design
EAM 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 <include hyperlink>.
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| MARA | MATNR | MATNR | Material Number | CHAR | 18 | Mandatory |
Data Cleansing
All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.
If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
1003-001 | C1 | Missing Functional Location Descriptions | Functional Location as per Relevancy Criteria where there are blank Functional Location Descriptions. | Functional Location Description | PF2, WP2 |
| 1003-002 | C2 | Functional Location Descriptions with Informal Words | Functional Location as per Relevancy Criteria which contain [Informal Words] in the Functional Location Description | Functional Location Description | PF2, WP2 |
| 1003-003 | C1 | Invalid, Inactive or no Cost Centres linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Cost Centre which does not belong below: 1. Cost Centre (FI) as per Relevancy Criteria | Cost Centre | PF2, WP2 |
| 1003-004 | C1 | Invalid, Inactive or no Catalog Profile s linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Catalog Profile which does not belong below: 1. Catalog Profile as per Relevancy Criteria | Catalog Profile | PF2, WP2 |
| 1003-005 | C1 | Invalid, Inactive or no Class linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Class which does not belong below: 1. Class as per Relevancy Criteria | Class | PF2, WP2 |
| 1003-006 | C1 | Invalid, Inactive or no Characteristic linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Characteristic which does not belong below: 1. Characteristic as per Relevancy Criteria | Characteristic | PF2, WP2 |
| 1003-007 | C1 | Invalid, Inactive or no Construction Type linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Construction Type which does not belong below: 1. Construction Type as per Relevancy Criteria | Construction Type | PF2, WP2 |
| 1003-008 | C1 | Invalid or Inactive Document Info Record linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Document Info Record which does not belong below: 1. Document Info Record as per Relevancy Criteria | Document Info Record | PF2, WP2 |
1003-009 | C1 | Invalid or Inactive Material linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Material which does not belong below: 1. Material Master (S2P) as per Relevancy Criteria | Material | PF2, WP2 |
| 1003-010 | C1 | Invalid, Inactive or no Work Centres linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Work Centre which does not belong below: 1. Work Centre as per Relevancy Criteria | Work Centre | PF2, WP2 |
| 1003-011 | C1 | Invalid or no Planner Group linked to Functional Location | Functional Location as per Relevancy Criteria with no Planner Group Assigned or Invalid Planner Group (T024I) | Planner Group | PF2, WP2 |
| 1003-012 | C1 | Invalid or no Technical Object Type linked to Functional Location | Functional Location as per Relevancy Criteria with no Technical Object Type Assigned or Invalid Technical Object Type (T370K) | Technical Object Type | PF2, WP2 |
| 1003-013 | C1 | Maintainable physical assets created as Functional Location (than Equipment) | Functional Location | PF2, WP2 | |
| 1003-014 | C1 | Review all Functional Location / Equipment sitting under "ZDELETE". If these data set is not used / not needed, the system status should be set to INAC. | System Status | PF2, WP2 | |
| 1003-015 | C1 | Invalid, Inactive or no Superior Functional Location linked to Functional Location | Functional Location as per Relevancy Criteria with no Superior Functional Location Assigned or with a Superior Functional Location which does not belong below: 1. Functional Location as per Relevancy Criteria | Superior Functional Location | PF2, WP2 |
| 1003-016 | C1 | Invalid, Inactive or no Maintenance Plans linked to Functional Location | Functional Location as per Relevancy Criteria with no Maintenance Plan Linked or with a Maintenance Plan which does not belong below: 1. Maintenance Plan as per Relevancy Criteria | Maintenance Plan | PF2, WP2 |
| 1003-017 | C1 | Invalid or Inactive Business Partner (Customer) linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Business Partner / Customer which does not belong below: 1. Business Partner FLCU01 (SD) as per Relevancy Criteria | Business Partner (Customer) | PF2, WP2 |
| 1003-018 | C1 | Invalid or Inactive WBS linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a WBS which does not belong below: 1. Work Breakdown Structure (PS) as per Relevancy Criteria | Work Breakdown Structure | PF2, WP2 |
| 1003-019 | C2 | Material Types of Construction Types are non-Maintenance Assembly | Functional as per Relevancy Criteria where the Construction Type Assigned has a non-Maintenance Assembly Material Type* QF2: ZZ90-Maintenance Assembly WQ2: ZIBA-Maintenance Assembly | Construction Type | PF2, WP2 |
| 1003-020 | C1 | Invalid or Inactive Bill of Material linked to Functional Location | Functional Location as per Relevancy Criteria assigned with a Bill of Materia which does not belong below: 1. Bill of Material as per Relevancy Criteria | Bill of Material | PF2, WP2 |
| 1003-021 | C1 | Functional Location Company Code incorrect. | Functional Location as per Relevancy Criteria with Invalid Company Code (T001) | Company Code | PF2, WP2 |
| 1003-022 | C1 | Functional Location Technical object authorization group incorrect. | Functional Location as per Relevancy Criteria with Invalid Authorization Group (T370F) | Authorization Group | PF2, WP2 |
| 1003-023 | C1 | Functional Location Currency Codes incorrect. | Functional Location as per Relevancy Criteria with Invalid Currency Codes (TCURC) | Currency | PF2, WP2 |
| 1003-024 | C2 | Functional Location Planning Plant and Maintenance Plant are not the same. | Functional Location as per Relevancy Criteria with Planning Plant <> Maintenance Plant | Maintenance Plant, Planning Plant | PF2, WP2 |
| 1003-025 | C1 | ABC Indicator missing on Functional Location | Functional Location as per Relevancy Criteria where ABC Indicator is blank | ABC Indicator | PF2, WP2 |
Informal Words **
| *DNU | Delete | donot | Formerly | Old # |
| .. | Deletion | DONT USE | From | Old[ ] |
| / | DELISTED | DON'T USE | Incorrect | PLEASE USE |
| ? | Discontinued | Dup Use | Invalid | Pls Use |
| @ | Disposable | DUPLICATE | New | Previously |
| ^ | DNU | -DUPLICATE | NOT ACTIVE | Replace |
| + | Do Not | DUPLICATION | not in use | Replaced |
| ++ | Do Not Re | Duplicidad | Not Used | RESERVED |
| £ | Do Not Sell | Duplikat | NOT VALID | Retired |
| Defective | Do Not Use | Former | Obsolete | ZZDEL |
Conversion Process
Conversion will involve both Source System Extraction as well as using DCT (Data Collection Template) -
The high-level process for Source System Extraction is represented by the diagram below:
For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.
The high-level process for DCT is represented by the diagram below:
Data Privacy and Sensitivity
<To add more info later if applicable>
Extraction
Extract data from a source into Syniti Migrate. There are 2 possibilities:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 1 | Extract data from source system based on relevancy rule | SyWay Data Team |
| 2 | Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. | SyWay Data Team |
Selection Screen
If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not Applicable | ||||
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Functional Location data with exception of some fields which require transformation as mentioned in the transformation rule.Functional Location DCT Rules <To add more info below later>
| Field Name | Field Description | Rule |
|---|---|---|
| EQART | Technical Object Type | Assign Object Type for selected Functional Locations include in the mapping |
Extraction Dependencies
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure Syniti has the necessary connection and access to legacy servers | Data |
2 | Ensure that the necessary cleansing activities in legacy sources are complete | Data / Business |
3 | Ensure that create, change and deletion of master data is freeze in legacy Production system | Legacy IT |
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 Syniti Migrate to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
Transformation Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Obtain DCT Sign-off from Business | SyWay A2D Data Team |
2 | <Add steps from Syniti Migrate here> | SyWay A2D Data Team |
3 | Review and Validate Error and Preload Reports | SyWay A2D Data Team |
4 | Generate Load Files | SyWay A2D Data Team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| Mapping Table Name | Mapping Table Description |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure DCT tables completeness | SyWay A2D Data Team |
| 2 | Value Mappings are according to the latest design - <List of Value Mappings> | SyWay A2D Data Team |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Verify Record Count | SyWay A2D Data Team to verify that the total number of relevant records from the Source Extract and DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | SyWay A2D Data Team to verify that all fields below meet pass the checks:
|
| Review Error Reports | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
Business
Completeness
| Task | Action |
|---|---|
| Verify Record Count | Business Data Owner/s to verify that the total number of relevant records from the Source Extract and DCT is equal to the total number of records in the Preload and Load Sheets. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off Source Extract & DCT data). |
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
Load Phase and Dependencies
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Configuration
List the Configurations required before loading can commence
| Item # | Configuration Item |
|---|---|
1 | Structure Indicators with edit masks |
2 | Functional Location Category |
3 | Object Type |
4 | Weight Unit |
5 | Currency |
6 | Country of manufacturer |
7 | Maintenance Plant |
8 | Plant Section |
9 | ABC indicator |
10 | Planning Plant |
11 | Planner Group |
12 | Catalog Profile |
13 | Location |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1006 | Work Centre |
| 1074 | Cost Center |
| 1001 | BOM |
| 1015 | Characteristics |
| 1009 | Class |
| 1008 | Catalog Profile |
| 1013 | Reference Functional Location |
Error Handling
The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management
| Error Type | Error Description | Action Taken |
|---|---|---|
Configuration | Invalid Structure indicator missing | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Functional location cat missing | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Object Type | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Weight Unit | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Currency | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Country of Manufacturer | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Maintenance Plant | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Plant Section | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid ABC indicator | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Planning Plant | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Planner Group | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid catalog profile | Engage Functional team to expedite and fix the error in the system |
Configuration | Invalid Location | Engage Functional team to expedite and fix the error in the system |
Invalid Data | Invalid Cost Centre | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Class | Expedite whether the master data is changed in the system |
Invalid Data | Invalid Work Centre | Expedite whether the master data is changed in the system |
Invalid Data | Invalid BOM | Expedite whether the master data is changed in the system |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Count | Data team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA. |
Verify Logs | Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue, or attempt to load the record again, etc.). |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Data team to verify that the Measuring Point data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA. |
Business
Completeness
| Task | Action |
|---|---|
Verify Count | Download Post Load Reports from dspMigrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file. |
Accuracy
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the Measuring Point data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Functional Location is in scope based on data design and any exception requested by business.
- All data cleansing and preparation has been completed.
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.