Status
Owner	CASTRO MONCAYO-ext, Jose Luis
Stakeholders	GERVAIS, Pascal

Purpose

The purpose of this document is to define the conversion approach to create 1056 - Resources in S/4 HANA.

Resources are used to identify the production lines, equipment and all the machines related to the production execution process. Resources are the main data to be used to design the Master Recipes for all the Syensqo plants. 

Conversion Scope

The scope of this document covers the approach for converting active 1056- Resources from Legacy Source Systems into S/4HANA following the Resource Master Data Design Standard.

The data from legacy system includes:

1. Active Resources as of > three (3) years with history and/or included in active Recipes / Process Orders
2. Resources W/O Deletion Flag
3. Resources that will be migrated to the To-Be Plant Mapping (Take in consideration the To-Be definition of Plants

The data from legacy system excludes:

1. Inactive Resources with more than three (3) years.
2. Resources marked for deletion
3. Resources belonging to Deleted plants (New plant Definition according with the To-Be Plant mapping)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2, WP2	Production Versions will be extracted from PF2 and WP2	15,000	S/4 HANA	15,000
DCT	Production Versions for Plant / Material combination which do not have data existing from PF2 and PF2	TBD	S/4 HANA	TBD

Additional Information

Multi-language Requirement

English , French, Chinese, Spanish

Document Management

Summarize Document Management requirement, if any

Legal Requirement

N/A

Special Requirements

N/a

N/a

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

	Table	Field	Data Element	Field Description	Data Type	Length	Requirement	MDS Field Mapping in Scope	Field Value in MDS
1	CHRD	OBJTY	CR_OBJTY	Object type	CHAR	2	S	In Scope
2	CHRD	OBJID	CR_OBJID	Object ID	NUMC	8	S
3	CHRD	ARBPL	ARBPL	Work Center	CHAR	8	R		TBD
4	CHRD	WERKS	WERKS_D	Plant	CHAR	4	R		TBD
5	CHRD	VERWE	AP_VERWE	Work Center Category	CHAR	4	R		0008 Processing Unit
6	CHRD	PLANV	AP_PLANV	Key for task list usage	CHAR	3	R		0008 Master Recipe + Process Order
7	CHRD	STAND	AP_STAND	Work center location	CHAR	10	C		MFG Execution Config Register
8	CHRD	VERAN	AP_VERAN	Person Responsible for the Work Center	CHAR	3	C		MFG Execution Config Register
9	CHRD	VGWTS	VORGSCHL	Standard Value Key	CHAR	4	R		TBD
10	CHRD	VGM01	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
11	CHRD	VGM02	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
12	CHRD	VGM03	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
13	CHRD	VGM04	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C	In Scope
14	CHRD	VGM05	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
15	CHRD	VGM06	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
16	CHRD	ZGR01	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
17	CHRD	ZGR02	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
18	CHRD	ZGR03	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
19	CHRD	ZGR04	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
20	CHRD	ZGR05	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
21	CHRD	ZGR06	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
22	CHRD	PRVBE	PRVBE	Production Supply Area	CHAR	10	C
23	CHRD	RGEKZ	RGEKZAP	Indicator: Backflushing	CHAR	1	C
24	CHRD	STEUS	STEUS	Control Key	CHAR	4	R
25	CHRD	VGE01	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
26	CHRD	VGE02	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
27	CHRD	VGE03	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
28	CHRD	VGE04	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
29	CHRD	VGE05	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
30	CHRD	VGE06	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
31	CHRD	KAPAR	KAPART	Capacity category	CHAR	3	C
32	CHRD	KAPNAME	KAPNAME	Capacity name	CHAR	8	C
33	CHRD	FORT1	AP_FORM_T1	Formula for setup time	CHAR	6	NU		TBD
34	CHRD	FORT2	AP_FORM_T2	Formula for the duration of processing time	CHAR	6	NU		TBD
35	CHRD	FORT3	AP_FORM_T3	Formula for teardown time	CHAR	6	NU		TBD
36	CHRD	FORTN	AP_FORM_TN	Formula for the duration of other types of int. processing	CHAR	6	NU		TBD
37	CRTX	OBJTY	CR_OBJTY	Object type	CHAR	2	S
38	CRTX	OBJID	CR_OBJID	Object ID	NUMC	8	S
39	CRTX	SPRAS	SPRAS	Language	CHAR	1	R
40	CRTX	KTEXT	CR_KTEXT	Short description	CHAR	40	R
41	CRCA	OBJTY	CR_OBJTY	Object Type	CHAR	2	S
42	CRCA	OBJID	CR_OBJID	Object ID	NUMC	8	S
43	CRCA	CANUM	CR_CAPNUM	Capacity allocation number	CHAR	6	S		TBD
44	CRCA	FORK1	AP_FORM_K1	Formula for Setup Capacity Requirements	CHAR	6	NU
45	CRCA	FORK2	AP_FORM_K2	Formula for Processing Capacity Requirements	CHAR	6	NU
46	CRCA	FORK3	AP_FORM_K3	Formula for Teardown Capacity Requirements	CHAR	6	NU
47	CRCA	FORKN	AP_FORM_KN	Formula for Other Capacity Requirements	CHAR	6	NU
48	CRCA	KAPID	KAPID	Capacity ID	NUMC	8	S
49	KAKT	KAPID	KAPID	Capacity ID	NUMC	8	S
50	KAKT	SPRAS	SPRAS	Language	CHAR	1	C
51	KAKT	KTEXT	CR_KTEXT	Capacity Text	CHAR	40	C
52	CRCO	OBJTY	CR_OBJTY	Object type	CHAR	2	S
53	CRCO	OBJID	CR_OBJID	Object ID	NUMC	8	S
54	CRCO	LASET	#N/A	Activity Type Set	CHAR	6	S
55	CRCO	ENDDA	ENDDATUM	End Date	DATS	8	C
56	CRCO	BEGDA	BEGDATUM	Start Date	DATS	8	C
57	CRCO	KOKRS	KOKRS	CO Area	CHAR	4	R
58	CRCO	KOSTL	KOSTL	Cost Center	CHAR	10	R
59	CRCO	LSTAR1	LSTAR	Activity Type	CHAR	6	R
60	CRCO	LEINH1	LEINH	Activity Unit	UNIT	3	C
61	CRCO	FORML1	FORML	Formula key for costing	CHAR	6	R
62	CRCO	LSTAR2	LSTAR	Activity Type	CHAR	6	R
63	CRCO	LEINH2	LEINH	Activity Unit	UNIT	3	C
64	CRCO	FORML2	FORML	Formula key for costing	CHAR	6	R
65	CRCO	LSTAR3	LSTAR	Activity Type	CHAR	6	R
66	CRCO	LEINH3	LEINH	Activity Unit	UNIT	3	C
67	CRCO	FORML3	FORML	Formula key for costing	CHAR	6	R
68	CRCO	LSTAR4	LSTAR	Activity Type	CHAR	6	R
69	CRCO	LEINH4	LEINH	Activity Unit	UNIT	3	C
70	CRCO	FORML4	FORML	Formula key for costing	CHAR	6	R
71	CRCO	LSTAR5	LSTAR	Activity Type	CHAR	6	R
72	CRCO	LEINH5	LEINH	Activity Unit	UNIT	3	C
73	CRCO	FORML5	FORML	Formula key for costing	CHAR	6	R
74	CRCO	LSTAR6	LSTAR	Activity Type	CHAR	6	R
75	CRCO	LEINH6	LEINH	Activity Unit	UNIT	3	C
76	CRCO	FORML6	FORML	Formula key for costing	CHAR	6	R

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
1056-1	C1	Resource is not used for the last 3 years	All Resources not used for the last 3 years, won't be migrated	Active Resources during the last 3 years	PF2 /WP2
1056-2	C1	Resource is flagged for deletion	All Resources flagged for deletion won't be migrated	Resources with NO flag for deletion	PF2/WP2
1056-3	C1	Resources in Plants that are Out of Scope	Resources created in Plants Out of Scope won't be migrated	Resources valid in Active plants (To Be mapping)	PF2/WP2
1056-4	C1	Resources with No formulas for capacity, scheduling or costing	Resources with missing capacity, Scheduling and costing formulas won't be migrated	Only Resources with all formulas will be migrated	PF2/WP2
1056-5	C1

Conversion Process

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

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; 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 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
3	Sinity will extract data and convert it into SQL data base ad share with the team	Sinity 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

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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:

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 Syniti Migrate
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 Description	Team Responsible

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2	CRHD	ARBPL	Resource ID	S4 HANA	CRHD	ARBPL	Resource ID	Look at the file Resources equivalent for Plant - Resource Name as Existing Plant-New Plant mapping Check Resource name.

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

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

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

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

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.

Change log

Workflow history