Status
Owner	ULLAH-ext, Colin
Stakeholders	GERVAIS, Pascal NICASTRI-ext, Michele

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.

Stand alone rules

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)

Relevancy rule

1. Material/Plant with history and include active process orders - Materials defined via Status at global and Plant level (MARC/MARA)
2. Defined materials which are recognised as active and contain 3 years process order history, these are then checked against active BOMS to define Master Recipe at Plant level
3. Master Recipes defined as per the Material Master containing 3 years Process order History, define the Resource by Plant

Material Plant Active with three years Process order History defines Active BOMS by Plant defines Active Master Recipe by Plant Defines the Resource by Plant.

Plant Merging

Plants will be defined accordingly as some plants will be merged into one plant. Plants will be defined as NEW plant codes and be transformed via a transformation table, which will be contained in Syniti.

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	Resources will be extracted from PF2 and WP2	PF2 - 6096 WP2 - 9077	S/4 HANA	PF2 - 6096 WP2 - 9077

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	CRHD	OBJTY	CR_OBJTY	Object type	CHAR	2	S	In Scope
2	CRHD	OBJID	CR_OBJID	Object ID	NUMC	8	S
3	CRHD	ARBPL	ARBPL	Work Center	CHAR	8	R		TBD
4	CRHD	WERKS	WERKS_D	Plant	CHAR	4	R		TBD
5	CRHD	VERWE	AP_VERWE	Work Center Category	CHAR	4	R		0008 Processing Unit
6	CRHD	PLANV	AP_PLANV	Key for task list usage	CHAR	3	R		0008 Master Recipe + Process Order
7	CRHD	STAND	AP_STAND	Work center location	CHAR	10	C		MFG Execution Config Register
8	CRHD	VERAN	AP_VERAN	Person Responsible for the Work Center	CHAR	3	C		MFG Execution Config Register
9	CRHD	VGWTS	VORGSCHL	Standard Value Key	CHAR	4	R		TBD
10	CRHD	VGM01	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
11	CRHD	VGM02	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
12	CRHD	VGM03	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
13	CRHD	VGM04	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
14	CRHD	VGM05	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
15	CRHD	VGM06	AP_VGW_MES	Rule for standard value maintenance	CHAR	1	C
16	CRHD	ZGR01	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
17	CRHD	ZGR02	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
18	CRHD	ZGR03	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
19	CRHD	ZGR04	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
20	CRHD	ZGR05	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
21	CRHD	ZGR06	IDZEITGRAD	Key for performance efficiency rate	CHAR	3	NU
22	CRHD	PRVBE	PRVBE	Production Supply Area	CHAR	10	C
23	CRHD	RGEKZ	RGEKZAP	Indicator: Backflushing	CHAR	1	C
24	CRHD	STEUS	STEUS	Control Key	CHAR	4	R
25	CRHD	VGE01	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
26	CRHD	VGE02	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
27	CRHD	VGE03	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
28	CRHD	VGE04	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
29	CRHD	VGE05	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
30	CRHD	VGE06	VGWRTEH	Unit of measure for the standard value	UNIT	3	C
31	CRHD	FORT1	AP_FORM_T1	Formula for setup time	CHAR	6	C
32	CRHD	FORT2	AP_FORM_T2	Formula for the duration of processing time	CHAR	6	R
33	CRHD	FORT3	AP_FORM_T3	Formula for teardown time	CHAR	6	C
34	CRHD	FORTN	AP_FORM_TN	Formula for the duration of other types of int. processing	CHAR	6	NU
35	CRTX	OBJTY	CR_OBJTY	Object type	CHAR	2	S
36	CRTX	OBJID	CR_OBJID	Object ID	NUMC	8	S
37	CRTX	SPRAS	SPRAS	Language	CHAR	1	R
38	CRTX	KTEXT	CR_KTEXT	Short description	CHAR	40	R
39	CRCA	OBJTY	CR_OBJTY	Object Type	CHAR	2	S
40	CRCA	OBJID	CR_OBJID	Object ID	NUMC	8	S
41	CRCA	CANUM	CR_CAPNUM	Capacity allocation number	CHAR	6	S		TBD
42	CRCA	FORK1	AP_FORM_K1	Formula for Setup Capacity Requirements	CHAR	6	NU
43	CRCA	FORK2	AP_FORM_K2	Formula for Processing Capacity Requirements	CHAR	6	NU
44	CRCA	FORK3	AP_FORM_K3	Formula for Teardown Capacity Requirements	CHAR	6	NU
45	CRCA	FORKN	AP_FORM_KN	Formula for Other Capacity Requirements	CHAR	6	NU
46	CRCA	KAPID	KAPID	Capacity ID	NUMC	8	S
47	KAKT	KAPID	KAPID	Capacity ID	NUMC	8	S
48	KAKT	SPRAS	SPRAS	Language	CHAR	1	R
49	KAKT	KTEXT	CR_KTEXT	Capacity Text	CHAR	40	R
50	CRCO	OBJTY	CR_OBJTY	Object type	CHAR	2	S
51	CRCO	OBJID	CR_OBJID	Object ID	NUMC	8	S
52	CRCO	LASET	#N/A	Activity Type Set	CHAR	6	S
53	CRCO	ENDDA	ENDDATUM	End Date	DATS	8	R		31/12/9999
54	CRCO	BEGDA	BEGDATUM	Start Date	DATS	8	R
55	CRCO	KOKRS	KOKRS	CO Area	CHAR	4	R
56	CRCO	KOSTL	KOSTL	Cost Center	CHAR	10	R
57	CRCO	LSTAR1	LSTAR	Activity Type	CHAR	6	C
58	CRCO	LEINH1	LEINH	Activity Unit	UNIT	3	C
59	CRCO	FORML1	FORML	Formula key for costing	CHAR	6	R
60	CRCO	LSTAR2	LSTAR	Activity Type	CHAR	6	C
61	CRCO	LEINH2	LEINH	Activity Unit	UNIT	3	C
62	CRCO	FORML2	FORML	Formula key for costing	CHAR	6	R
63	CRCO	LSTAR3	LSTAR	Activity Type	CHAR	6	C
64	CRCO	LEINH3	LEINH	Activity Unit	UNIT	3	C
65	CRCO	FORML3	FORML	Formula key for costing	CHAR	6	R
66	CRCO	LSTAR4	LSTAR	Activity Type	CHAR	6	C
67	CRCO	LEINH4	LEINH	Activity Unit	UNIT	3	C
68	CRCO	FORML4	FORML	Formula key for costing	CHAR	6	R
69	CRCO	LSTAR5	LSTAR	Activity Type	CHAR	6	C
70	CRCO	LEINH5	LEINH	Activity Unit	UNIT	3	C
71	CRCO	FORML5	FORML	Formula key for costing	CHAR	6	R
72	CRCO	LSTAR6	LSTAR	Activity Type	CHAR	6	C
73	CRCO	LEINH6	LEINH	Activity Unit	UNIT	3	C
74	CRCO	FORML6	FORML	Formula key for costing	CHAR	6	R
75	KAKO	KAPID	KAPID	Capacity ID	NUMC	8	S
76	KAKO	AZMAX	KAPANZAHL	No. Ind. Capacities	INT2	5	NU
77	KAKO	AZNOR	KAPANZAHL	No. Ind. Capacities	INT2	5	R
78	KAKO	BASNE	KAPBASNEN	Denominator base cap	DEC	5	S
79	KAKO	BASZL	KAPBASZHL	Numerator base cap.	DEC	5	S
80	KAKO	BEGZT	KAPBEGZT	Start Time	INT4	10	R
81	KAKO	ENDZT	KAPENDZT	End Time	INT4	10	R
82	KAKO	KALID	CR_WFCID	Factory Calendar	CHAR	2	C
83	KAKO	KAPAR	KAPART	Capacity category	CHAR	3	R
84	KAKO	MEINS	KAPBASIS	Capacity Base Unit	UNIT	3	R
85	KAKO	MOSID	SCHGRUP	Shift Grouping	CHAR	2	C
86	KAKO	NAME	KAPNAME	Capacity	CHAR	8	NU
87	KAKO	NGRAD	NUTZGRAD	Capacity Utilization	NUMC	3	R
88	KAKO	PAUSE	KAPPAUSE	Break Duration	INT4	10	R
89	KAKO	PLANR	KAPPLANER	Capacity Responsible Planner	CHAR	3	R
90	KAKO	POOLK	KAP_KZPOOL	Pooled Capacity Indicator	CHAR	1	C
91	KAKO	REFAN	KAPREFANZN	Number (ref. cap.)	INT1	3	C
92	KAKO	REFAZ	KAPREFANZZ	Number (capacity)	INT1	3	C
93	KAKO	REFID	KAPID	Capacity ID	NUMC	8	C
94	KAKO	SUPPK	KAP_SUPPLY	Avail. cap. limits	CHAR	1	C (if not entered, 100% will be the default)
95	KAKO	VERSA	KAPVERSAKT	Active Version	NUMC	2	R
96	KAKO	WERKS	WERKS_D	Plant	CHAR	4	NU
97	KAKO	KAPIE	KAPID	Capacity ID	NUMC	8	NU
98	KAKO	KAPTER	KAP_KZTER	Relevant to Finite Scheduling	CHAR	1	C
99	KAKO	KAPAVO	KAP_KZAVO	Can be used by several operations	CHAR	1	C
100	KAKO	UEBERLAST	UEBERLAST	Overload (%)	NUMC	3	C
101	KAKO	KAPLPL	KAP_KZLPL	No Long-Term Planning	CHAR	1	C
102	KAKO	KAPEH	CR_KAPEH	Capacity Unit	UNIT	3	NU
103	KAKO	MEHR	KAP_MEHR	Has Individual Capacities	CHAR	1	NU
104	KAKO	ANG_UNIT	KAPAZIT_VM_UNIT	Av. cap. unit	UNIT	3	NU
105	KAKO	ANG_MIN	KAPAZIT_VM_MIN	Minimum capacity	QUAN	13	NU
106	KAKO	ANG_MAX	KAPAZIT_VM_MAX	Max. capacity	QUAN	13	NU

Data Cleansing

Business will perform data cleansing in the current ECC system. This means ECC will serve as the single source of truth for Manufacturing Data prior to the migration to S/4HANA.

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

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/ MS Excel/ SQL 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.

The Data Collection Template (DCT) will not be applicable in this case. If there is a need to create  new Master Data (MD) for Resource object, the business must perform this activity in the source system. The newly created object will then be captured and migrated as part of the standard migration process.

Field Name	Field description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Source System Availability Ensure that the source database or application is accessible. Confirm that necessary credentials and permissions are granted	Syensqo IT
2	Data Structure Identify relationships between tables, views, and stored procedures.	Syniti
3	Referential Integrity Ensure dependent records are extracted together.	Syniti
4	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Syniti
5	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Syniti
6	Security and Compliance Adhere to regulatory standards for sensitive information if applicable	Syniti
7	Data cleansing of legacy Resource - If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.	Business

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
1	Obtain DCT Sign-off from Business	SyWay Data Team
2	<Add steps from Syniti Migrate here>	SyWay Data Team
3	Review and Validate Error and Preload Reports	SyWay Data Team
4	Generate Load Files	SyWay Data Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2/WP2	CRHD	OBJTY	Object type	S4 HANA	CRHD	OBJTY	Object type	System Generated Field
2	PF2/WP2	CRHD	OBJID	Object ID	S4 HANA	CRHD	OBJID	Object ID	System Generated Field
3	PF2/WP2	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.
4	PF2/WP2	CRHD	WERKS	Plant	S4 HANA	CRHD	WERKS	Plant	Map from Old Plants to New Plants
5	PF2/WP2	CRHD	VERWE	Work Center Category	S4 HANA	CHRD	VERWE	Work Center Category	VALUE 0008
6	PF2/WP2	CRHD	PLANV	Key for task list usage	S4 HANA	CHRD	PLANV	Key for task list usage	Value Direct from the current system
7	PF2/WP2	CRHD	STAND	Work Center location	S4 HANA	CHRD	STAND	Work Center location	Value set based upon MFG Execution Config Register C : Business Rule, Copy from current, or if they are not there, it will be config if they are going to use it
8	PF2/WP2	CRHD	VERAN	Person Responsible for the Work Center	S4 HANA	CHRD	VERAN	Person Responsible for the Work Center	Value set based upon MFG Execution Config Register C : Business Rule From the Configuration work book and be a generic entry for all plants
9	PF2/WP2	CRHD	VGWTS	Standard Value Key	S4 HANA	CHRD	VGWTS	Standard Value Key	Follow Mfg Execution Config book (one standard value key for all resources / all GBUs)
10	PF2/WP2	CRHD	VGM01	Rule for standard value maintenance	S4 HANA	CHRD	VGM01	Rule for standard value maintenance	If the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
11	PF2/WP2	CRHD	VGM02	Rule for standard value maintenance	S4 HANA	CHRD	VGM02	Rule for standard value maintenance	If the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
12	PF2/WP2	CRHD	VGM03	Rule for standard value maintenance	S4 HANA	CHRD	VGM03	Rule for standard value maintenance	If the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
13	PF2/WP2	CRHD	VGM04	Rule for standard value maintenance	S4 HANA	CHRD	VGM04	Rule for standard value maintenance	If the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
14	PF2/WP2	CRHD	VGM05	Rule for standard value maintenance	S4 HANA	CHRD	VGM05	Rule for standard value maintenance	If the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
15	PF2/WP2	CRHD	VGM06	Rule for standard value maintenance	S4 HANA	CHRD	VGM06	Rule for standard value maintenance	If the standard value is pulled and used then this field is required. Value to be taken from VGWTS - STD value key
16	PF2/WP2	CRHD	PRVBE	Production Supply Area	S4 HANA	CHRD	PRVBE	Production Supply Area	Business Rule This field will be populated if relevant for EWM based on the plant (this has not been completely defined yet) MDS for EWM           DD-FUN-050 Master Data  Standard_1180-PSA (EWM) Because the warehouse can support holding stock that belongs to more than one plant, the PP PSA is replicated to EWM by adding the plant number preceded by a "/" to be able to tell in the warehouse to which plant the original PSA belongs.
17	PF2/WP2	CRHD	RGEKZ	Indicator: Backflushing	S4 HANA	CHRD	RGEKZ	Indicator: Backflushing	Business Rule If all components used at a machine/line should be automatically issued at confirmation - Copy from Current system
18	PF2/WP2	CRHD	STEUS	Control Key	S4 HANA	CHRD	STEUS	Control Key	Mandatory Direct from the current system
19	PF2/WP2	CRHD	VGE01	Unit of measure for the standard value	S4 HANA	CHRD	VGE01	Unit of measure for the standard value	If the rule of the corresponding standard Value is used then this unit should be filled. Value to be taken from VGWTS - STD value key
20	PF2/WP2	CRHD	VGE02	Unit of measure for the standard value	S4 HANA	CHRD	VGE02	Unit of measure for the standard value	If the rule of the corresponding standard Value is used then this unit should be filled. Value to be taken from VGWTS - STD value key
21	PF2/WP2	CRHD	VGE03	Unit of measure for the standard value	S4 HANA	CHRD	VGE03	Unit of measure for the standard value	If the rule of the corresponding standard Value is used then this unit should be filled. Value to be taken from VGWTS - STD value key
22	PF2/WP2	CRHD	VGE04	Unit of measure for the standard value	S4 HANA	CHRD	VGE04	Unit of measure for the standard value	If the rule of the corresponding standard Value is used then this unit should be filled. Value to be taken from VGWTS - STD value key
23	PF2/WP2	CRHD	VGE05	Unit of measure for the standard value	S4 HANA	CHRD	VGE05	Unit of measure for the standard value	If the rule of the corresponding standard Value is used then this unit should be filled. Value to be taken from VGWTS - STD value key
24	PF2/WP2	CRHD	VGE06	Unit of measure for the standard value	S4 HANA	CHRD	VGE06	Unit of measure for the standard value	If the rule of the corresponding standard Value is used then this unit should be filled. Value to be taken from VGWTS - STD value key
27	PF2/WP2	CRHD	FORT1	Formula for setup time	S4 HANA	CHRD	FORT1	Formula for setup time	Standard Formula SAP001
28	PF2/WP2	CRHD	FORT2	Formula for the duration of processing time	S4 HANA	CHRD	FORT2	Formula for the duration of processing time	Standard Formula SAP002
29	PF2/WP2	CRHD	FORT3	Formula for teardown time	S4 HANA	CHRD	FORT3	Formula for teardown time	Standard Formula SAP010
31	PF2/WP2	CRTX	OBJTY	Object type	S4 HANA	CRTX	OBJTY	Object type	System Generated Field
32	PF2/WP2	CRTX	OBJID	Object ID	S4 HANA	CRTX	OBJID	Object ID	System Generated Field
33	PF2/WP2	CRTX	SPRAS	Language	S4 HANA	CRTX	SPRAS	Language	Value direct from the current SAP system, Languages will need to be configured, mostly set as EN (Language which the Resource is maintained)
34	PF2/WP2	CRTX	KTEXT	Short description	S4 HANA	CRTX	KTEXT	Short description	This is to be defined by the business, free text field, brief description of the Resource
35	PF2/WP2	CRCA	OBJTY	Object Type	S4 HANA	CRCA	OBJTY	Object Type	System Generated Field
36	PF2/WP2	CRCA	OBJID	Object ID	S4 HANA	CRCA	OBJID	Object ID	System Generated Field
37	PF2/WP2	CRCA	CANUM	Capacity allocation number	S4 HANA	CRCA	CANUM	Capacity allocation number	System Generated Field
38	PF2/WP2	CRCA	KAPID	Capacity ID	S4 HANA	CRCA	KAPID	Capacity ID	System Generated Field
39	PF2/WP2	KAKT	KAPID	Capacity ID	S4 HANA	KAKT	KAPID	Capacity ID	System Generated Field
40	PF2/WP2	KAKT	SPRAS	Language	S4 HANA	KAKT	SPRAS	Language	Value direct from the current SAP system, Languages will need to be configured, mostly set as EN (Language which the Capacity is maintained)
41	PF2/WP2	KAKT	KTEXT	Capacity Text	S4 HANA	KAKT	KTEXT	Capacity Text	This is to be defined by the business, free text field, brief description of the Capacity
42	PF2/WP2	CRCO	OBJTY	Object type	S4 HANA	CRCO	OBJTY	Object type	System Generated Field
43	PF2/WP2	CRCO	OBJID	Object ID	S4 HANA	CRCO	OBJID	Object ID	System Generated Field
44	PF2/WP2	CRCO	LASET	Activity Type Set	S4 HANA	CRCO	LASET	Activity Type Set	System Generated Field
45	PF2/WP2	CRCO	ENDDA	End Date	S4 HANA	CRCO	ENDDA	End Date	End date has value set to 31/12/9999
46	PF2/WP2	CRCO	BEGDA	Start Date	S4 HANA	CRCO	BEGDA	Start Date	Date value setting DD.MM.YYYY , Process orders, when they are created are we going to create them with days in the past? needs to be confirmed
47	PF2/WP2	CRCO	KOKRS	CO Area	S4 HANA	CRCO	KOKRS	CO Area	This is Part of DCT in the Cost centre Conversion Spec
48	PF2/WP2	CRCO	KOSTL	Cost Center	S4 HANA	CRCO	KOSTL	Cost Center	This is Part of DCT in the Cost centre Conversion Spec
49	PF2/WP2	CRCO	LSTAR1	Activity Type	S4 HANA	CRCO	LSTAR1	Activity Type	This is Part of DCT in the Cost centre Conversion Spec
50	PF2/WP2	CRCO	LEINH1	Activity Unit	S4 HANA	CRCO	LEINH1	Activity Unit	This is Part of DCT in the Cost centre Conversion Spec
51	PF2/WP2	CRCO	FORML1	Formula key for costing	S4 HANA	CRCO	FORML1	Formula key for costing	Value to be taken from VGWTS - STD value key
52	PF2/WP2	CRCO	LSTAR2	Activity Type	S4 HANA	CRCO	LSTAR2	Activity Type	This is Part of DCT in the Cost centre Conversion Spec
53	PF2/WP2	CRCO	LEINH2	Activity Unit	S4 HANA	CRCO	LEINH2	Activity Unit	This is Part of DCT in the Cost centre Conversion Spec
54	PF2/WP2	CRCO	FORML2	Formula key for costing	S4 HANA	CRCO	FORML2	Formula key for costing	Value to be taken from VGWTS - STD value key
55	PF2/WP2	CRCO	LSTAR3	Activity Type	S4 HANA	CRCO	LSTAR3	Activity Type	This is Part of DCT in the Cost centre Conversion Spec
56	PF2/WP2	CRCO	LEINH3	Activity Unit	S4 HANA	CRCO	LEINH3	Activity Unit	This is Part of DCT in the Cost centre Conversion Spec
57	PF2/WP2	CRCO	FORML3	Formula key for costing	S4 HANA	CRCO	FORML3	Formula key for costing	Value to be taken from VGWTS - STD value key
58	PF2/WP2	CRCO	LSTAR4	Activity Type	S4 HANA	CRCO	LSTAR4	Activity Type	This is Part of DCT in the Cost centre Conversion Spec
59	PF2/WP2	CRCO	LEINH4	Activity Unit	S4 HANA	CRCO	LEINH4	Activity Unit	This is Part of DCT in the Cost centre Conversion Spec
60	PF2/WP2	CRCO	FORML4	Formula key for costing	S4 HANA	CRCO	FORML4	Formula key for costing	Value to be taken from VGWTS - STD value key
61	PF2/WP2	CRCO	LSTAR5	Activity Type	S4 HANA	CRCO	LSTAR5	Activity Type	This is Part of DCT in the Cost centre Conversion Spec
62	PF2/WP2	CRCO	LEINH5	Activity Unit	S4 HANA	CRCO	LEINH5	Activity Unit	This is Part of DCT in the Cost centre Conversion Spec
63	PF2/WP2	CRCO	FORML5	Formula key for costing	S4 HANA	CRCO	FORML5	Formula key for costing	Value to be taken from VGWTS - STD value key
64	PF2/WP2	CRCO	LSTAR6	Activity Type	S4 HANA	CRCO	LSTAR6	Activity Type	This is Part of DCT in the Cost centre Conversion Spec
65	PF2/WP2	CRCO	LEINH6	Activity Unit	S4 HANA	CRCO	LEINH6	Activity Unit	This is Part of DCT in the Cost centre Conversion Spec
66	PF2/WP2	CRCO	FORML6	Formula key for costing	S4 HANA	CRCO	FORML6	Formula key for costing	Value to be taken from VGWTS - STD value key
67	PF2/WP2	KAKO	KAPID	Capacity ID	S4 HANA	KAKO	KAPID	Capacity ID	System Generated
68	PF2/WP2	KAKO	AZNOR	No. Ind. Capacities	S4 HANA	KAKO	AZNOR	No. Ind. Capacities	Copy From ECC
69	PF2/WP2	KAKO	BASNE	Denominator base cap	S4 HANA	KAKO	BASNE	Denominator base cap	System Generated
70	PF2/WP2	KAKO	BASZL	Numerator base cap.	S4 HANA	KAKO	BASZL	Numerator base cap.	System Generated
71	PF2/WP2	KAKO	BEGZT	Start Time	S4 HANA	KAKO	BEGZT	Start Time	Copy From ECC
72	PF2/WP2	KAKO	ENDZT	End Time	S4 HANA	KAKO	ENDZT	End Time	Copy From ECC
73	PF2/WP2	KAKO	KALID	Factory Calendar	S4 HANA	KAKO	KALID	Factory Calendar	Conditional : Business Rule Assign the correct Factory Calendar to the resource. If left blank, the system will use directly the plant factory calendar by default The calendar used is the one assigned to the plant or it's a calendar defined in the same country - Factory Calendar under TM team to define the values
74	PF2/WP2	KAKO	KAPAR	Capacity category	S4 HANA	KAKO	KAPAR	Capacity category	Copy From ECC
75	PF2/WP2	KAKO	MEINS	Capacity Base Unit	S4 HANA	KAKO	MEINS	Capacity Base Unit	Copy From ECC
76	PF2/WP2	KAKO	MOSID	Shift Grouping	S4 HANA	KAKO	MOSID	Shift Grouping	Copy values by plant
77	PF2/WP2	KAKO	NGRAD	Capacity Utilization	S4 HANA	KAKO	NGRAD	Capacity Utilization	Copy From ECC
78	PF2/WP2	KAKO	PAUSE	Break Duration	S4 HANA	KAKO	PAUSE	Break Duration	Copy From ECC
79	PF2/WP2	KAKO	PLANR	Capacity Responsible Planner	S4 HANA	KAKO	PLANR	Capacity Responsible Planner	Copy From ECC
80	PF2/WP2	KAKO	POOLK	Pooled Capacity Indicator	S4 HANA	KAKO	POOLK	Pooled Capacity Indicator	System Generated
81	PF2/WP2	KAKO	REFAN	Number (ref. cap.)	S4 HANA	KAKO	REFAN	Number (ref. cap.)	Not used because it is only used if you are going to do a new creation once we are live
82	PF2/WP2	KAKO	REFAZ	Number (capacity)	S4 HANA	KAKO	REFAZ	Number (capacity)	Not used because it is only used if you are going to do a new creation once we are live
83	PF2/WP2	KAKO	REFID	Capacity ID	S4 HANA	KAKO	REFID	Capacity ID	Not used because it is only used if you are going to do a new creation once we are live
84	PF2/WP2	KAKO	SUPPK	Avail. cap. limits	S4 HANA	KAKO	SUPPK	Avail. cap. limits	Conditional: Business Rule If not entered 100% capacity will be used by default in the system
85	PF2/WP2	KAKO	VERSA	Active Version	S4 HANA	KAKO	VERSA	Active Version	Copy From ECC
86	PF2/WP2	KAKO	KAPTER	Relevant to Finite Scheduling	S4 HANA	KAKO	KAPTER	Relevant to Finite Scheduling	Always set to X
87	PF2/WP2	KAKO	KAPAVO	Can be used by several operations	S4 HANA	KAKO	KAPAVO	Can be used by several operations	Always set to X
88	PF2/WP2	KAKO	UEBERLAST	Overload (%)	S4 HANA	KAKO	UEBERLAST	Overload (%)	Copy from ECC
89	PF2/WP2	KAKO	KAPLPL	No Long-Term Planning	S4 HANA	KAKO	KAPLPL	No Long-Term Planning	Always set to X

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
Work Centre	Mapping of legacy Work Center to new Work Centers to target system value
Plant	Mapping of legacy Plants to new Plants to target system value
Standard Value Key	Mapping of legacy Standard Value Key  to new Standard Value Key to target system value

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	SyWay Data Team
2	Value Mappings are according to the latest design - <List of Value Mappings>	SyWay 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	Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	SyWay Data Team to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks 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

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

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records from the the 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 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 Description	Team Responsible
1	Go to <Load Tool>	SyWay Data Team
2	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
3	Proceed with full load if steps 2 and 3 are validated	SyWay Data Team
4	Validate few records loaded by accessing standard transactions from S/4HNA eg. CS04	SyWay Data Team
5	Generate post load report if step 5 is validated	SyWay Data Team

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	T001W-Plants/Branches
2	TC30-Work Centre Category
3	TC23-Key for use of the work center in the task lists
4	T499S-Work Centre Location
5	TC24-Person responsible for the work center
6	TC21-Standard Value Key
7	PVKT-Production Supply Area
8	T430-Control Key
9	T006-Units of Measurement
10	TC26-Capacity Category
11	TKA01-Controlling Areas
12	OP54-Formula key for costing
13	TFACD-Factory Calendar
14	TC39A-Shifting Group
15	TC27-Capacity Responsible Planner
16	TC36-Active Version

Conversion Objects

Object #	Preceding Object Conversion Approach
1071	Activity Type
1074	Cost Centre

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
1	Work Centre has not been created in a Plant	Ensure the Work centre mapping is correct and or create the Work centre if it is valid
2	Configuration is missing	Verify that all configuration exists and reprocess when they are available (See configuration in Spec)

Post-Load Validation

Project Team

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

Completeness

Task	Action
Verify Count	SyWay P2F 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.

Accuracy

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

Business

The following post-load validations will be performed by the 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 Resource data in target S/4 HANA were loaded correctly via DSP Migrate 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 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