Relevant Equipment will be extracted from PF2 and WP2

Functional Location flagged to be migrated as Equipment will be extracted from PF2 and WP2

DCT

1. Assemblies to be created as Equipment
2. Equipment for plants which do not have data existing from PF2 and WP2

TBD

S/4HANA

TBD

System

Key Field

1

Plant associated with main work center

Mandatory

(Key to link to Equipment)

Mandatory

(Key to link to Equipment)

ATNAM

ATNAM

Mandatory

(Key to link to Equipment)

Mandatory

(Key to link to Equipment)

Mandatory

(Key to link to Equipment)

JEST

STAT

Mandatory

(Key to link to Equipment)

Mandatory

(Key to link to Equipment)

Equipment as per relevancy criteria where EQUI_ANSWT <> '' (Blank) and EQUI_WAERS = '' (Blank)

Functional Location as per Relevancy Criteria ( mapping - Functional Location, where New Technical Object = 'EQ')where IFLOT_ANSWT <> '' (Blank) and IFLOT_WAERS = '' (Blank)

Mandatory

Must be unique

PF2/WP2 data enrichment: Not used

For new data construction:

Mandatory

Allowed values from T370K to be populated

PF2/WP2 data enrichment: Not used

For new data construction:

Conditional

Populate if information exists

PF2/WP2 data enrichment: Not used

For new data construction:

Conditional

Populate unit value if BRGEW (Weight) has been maintained.

Allowed values from T006 to be populated

Conditional

Populate Critical Material representing the relevant procured Capital Spare (Fixed Asset) for the Equipment

Criteria for Assigning Critical Materials as the Inventory Number - 

• The material must have a cost greater than 15,000 and a useful life exceeding one year.
• The material type should be either 'UNBW' or 'NLAG'.
• The "Critical Part" checkbox must be selected in the Purchasing view of the Material Master.

Conditional

Populate the Fixed Asset value if Inventory Number has been maintained. 

Conditional

Populate only if 'Acquisition Value' field has been populated

Allowed values from TCURC to be populated. 

Conditional

Populate if information exists

Conditional

Populate if information exists

Conditional

Populate if information exists

Conditional

Populate if information exists

Conditional

Populate if information exists

Conditional

Populate if information exists

PF2/WP2 data enrichment: Not used

For new data construction:

Mandatory

Populate values from Value Mapping - Plant (where Maintenance Plant = Yes)

PF2/WP2 data enrichment: Not used

For new data construction:

Conditional

Must Populate value if Equipment is in Installed Status i.e HEQUI is not Blank or TPLNR is not Blank

Allowed values from T024I (where IWERK = Planning Plant) to be populated

PF2/WP2 data enrichment: Not used

For new data construction:

Conditional

Must Populate value if Equipment is in Installed Status i.e HEQUI is not Blank or TPLNR is not Blank

Allowed values from Work Centre DCT to be populated. 

For new data construction:

Conditional

Populate if Equipment is a Sub-Equipment. 

Plant section of the Superior Equipment should be identical the the Equipment to be installed.

For new data construction:

Mandatory

Populate value from Assembly DCT.

Assigned Construction Type should have a TOT Characteristic value maintained which matches the 'Object Type' assigned on the Equipment and 'SubAssembly' Characteristic = 'No'

Conditional

Populate Category 'A' Functional Location if Equipment installed under Functional Location.

Assigned Functional Location should have a TOT value identical to the Equipment and the Plant Section of the Functional Location should be identical to the one assigned on the Equipment

Allowed Category 'A' Functional Location values from mapping (Functional Location, where New Technical Object = 'FL') to be used. 

Mandatory

Allowed values from T357 to be populated.

Mandatory

The Sort Field is used to store the Plant Tag ID, representing the physical identifier attached to an asset in the field.
Each Equipment record must have a unique Sort Field value within the same Plant, except in cases where the Equipment is defined as a sub-equipment of a parent asset, in which case it may share the same Plant Tag ID.

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

PF2/WP2 data enrichment: 

Mandatory

Must Populate value if Equipment is in Installed Status i.e HEQUI is not Blank or TPLNR is not Blank

Allowed values from R2R Cost Centre Value Mapping. 

PF2/WP2 data enrichment: 

Conditional

Populate NAME1-4 fields with the Name and Location of the Asset

PF2/WP2 data enrichment: 

Conditional

Populate NAME1-4 fields with the Name and Location of the Asset

PF2/WP2 data enrichment: 

Conditional

Populate NAME1-4 fields with the Name and Location of the Asset

PF2/WP2 data enrichment: 

Conditional

Populate NAME1-4 fields with the Name and Location of the Asset

PF2/WP2 data enrichment: 

For new data construction:

Mandatory

Guide for Description:

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

Equipment Description = A+B+C

All Letters must be in Capital letters/ Uppercase. 

Cannot have duplicate records based on corresponding language text (2 Equipment 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

PF2/WP2 data enrichment: 

For new data construction:

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

PF2/WP2 data enrichment: 

For new data construction:

Conditional

Guide for Description:

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)

Equipment Description = A+B+C

All Letters must be in Capital letters/ Uppercase. 

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

Partner (Asset Owner)

PF2/WP2 data enrichment:

For new data construction:

Conditional

Populate 'Z1' (Asset Owner) Vendor Business Partner as per below rule. 

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

PF2/WP2 data enrichment:

For new data construction:

Conditional

Populate 'Z2' (Asset Maintainer) Vendor Business Partner as per below rule. 

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

PF2/WP2 data enrichment:

For new data construction:

Conditional

Populate 'Z3' (Vendor Contact) Contact Person Business Partner of the External Vendor.

PF2/WP2 data enrichment: No Used 

For new data construction:

Conditional

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'

PF2/WP2 data enrichment: Not used

For new data construction:

Conditional

Populate 'EXHZ' (Extremely Hazardous) status if applicable. 

PF2/WP2 data enrichment: Not used

For new data construction:

Conditional

Populate 'MTNA' (Maintenance Not Allowed) status if applicable. 

Mandatory

Key to link to Equipment

Should exist in Equipment Master DCT Rules

Mandatory

• Must always have an always an entry for EAM_9999.
• User to populate any other class of class type '002' (Equipment) as required

Class other than 'EAM_9999' must have naming convention = EAM_TOT (Tech Object Type) of the Equipment

Mandatory

User to populate Characteristic assigned to the Class 'EAM_9999' and other mapped legacy classes as per the Class DCT

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)

Conditional

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

Mandatory

Key to link to Equipment

Conditional

User to populate Free Text in English Language as applicable. All Letters must be in Capital letters/ Uppercase. 

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

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

All Letters must be in Capital letters/ Uppercase. 

Mandatory

Key to link to Equipment

Mandatory

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

Not Applicable

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 – Equipment

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

If derived Target User Status for Equipment from Equipment 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 "1002" and Field Name = "EQUI-INBDT".

Else leave blank

Plant associated with main work center

Plant associated with main work center

Internal Generated Number 

Direct Mapping

Overwrite with DCT if provided (as part of enrichment)

Key to link to the Equipment

Direct Mapping

Overwrite with DCT if provided (as part of enrichment)

Key to link to the Equipment

Direct Mapping

Overwrite with DCT if provided (as part of enrichment)

Internal Generated Number 

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

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

Key to link to the Equipment

Key to link to the Equipment

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

Otherwise, direct mapping.

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

Otherwise, direct mapping.

Key to link to the Equipment

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

Otherwise, direct mapping.

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

Otherwise, direct mapping.

Key to link to the Equipment

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

Otherwise, direct mapping.

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

Otherwise, leave blank.

Key to link to the Equipment

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

Otherwise, direct mapping.

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

Otherwise, direct mapping.

Key to link to the Equipment

-

-

-

-

Overwrite with DCT if provided (as part of enrichment)

Value mapping : Vendor Number

Key to link to the Equipment

-

-

-

-

Overwrite with DCT if provided (as part of enrichment)

Value mapping : Vendor Number

Key to link to the Equipment

-

-

-

-

Overwrite with DCT if provided (as part of enrichment)

Value mapping : Vendor Number

Internal Generated Number 

JEST

STAT

JEST

STAT

Value Mapping : User Status Equipment

Overwrite with DCT if provided (as part of enrichment)

-

-

JEST

INACT

Key to link to the Equipment

JEST

STAT_N1

JEST

STAT

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

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

JEST

INACT

Key to link to the Equipment

JEST

STAT_X1

JEST

STAT

Default Blank for Category 'O' and 'N' 

For Category 'A':
Direct Mapping

JEST

INACT

Key to link to the Equipment

JEST

STAT_X2

JEST

STAT

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

For Category 'A':
Direct Mapping

JEST

INACT

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

Equipment Category

Technical Object Type

Weight Unit

Currency

Country of manufacturer

Maintenance Plant and Planning Plant

Plant Section

Planner Group

ABC indicator

Catalog Profile 

Configuration

Equipment 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

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 Production Work Centre

Expedite whether the master data is changed in the system

Invalid Data

Invalid Maintenance Work Centre

Expedite whether the master data is changed in the system

Invalid Data

Invalid Assembly

Expedite whether the master data is changed in the system

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

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. 

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.

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.