Status
Owner	CASTRO MONCAYO-ext, Jose Luis SUSANTO-ext, William
Stakeholders	GERVAIS, Pascal NICASTRI-ext, Michele AIT OUAKLI-ext, Amine

Purpose

T

The purpose of this document is to define the conversion approach to create 2005 - Material Master - Work Scheduling View
in S/4 HANA.

In SAP PP-PI, the Work Scheduling view in the Material Master is a plant-specific view that contains essential data for producing a material in-house, allowing you to create and schedule production orders for it. Key fields within this view include the Production Scheduling Profile, which automates key tasks for production orders, and the Production Scheduler, who manages the material's capacity requirements. Maintaining this view is necessary for managing production processes and enabling the system to calculate production and operation start and end dates.

Purpose of the Work Scheduling View

Enables Production Orders:

You must maintain the Work Scheduling view for a material to allow the system to create production or process orders for it.

Plant-Level Data:

This view contains data specific to a particular plant, as production processes are managed at the plant level.

Key Fields and Their Functions

Production Scheduler:

A person or role responsible for managing the material's production in a specific plant. They determine how capacity requirements are calculated during a scheduling run.

Production Scheduling Profile (PSP):

A crucial tool for standardizing and automating production processes. It can dictate actions like automatically releasing and scheduling orders, triggering goods receipts, or managing batch creation.

While PF2 and WP2 serve as source systems, extensive mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design. Due to the new plant mapping and the Material / plant mapping, an extensive cleansing, transformation to do for this object

The data from legacy system may include:

1. Only Active materials
   
   
2. Material /Plant combination for all the "E" & "X" procurement materials as this view only intended for the manufactured products

The data from legacy system excludes:

1. All materials flagged for deletion
2. Any blocked or obsolete materials
3. Any inactive materials that are out of scope

Conversion Scope

The scope of this document covers the approach for converting active Material Master - Work Scheduling view from Legacy Source Systems into S/4HANA following the Material Master - Work Scheduling view Master Data Design Standard.

The data from legacy system includes:

1. Use the logic for Data Relevancy for the CNV-2019 Material Master - Basic Views
2. All materials created in the previous 6 months will be included unless flagged for deletion
3. Material Types ZUNB, ZBOM, ZPRC will be included regardless of activity (unless flagged for deletion)
4. We will only include materials that are extended to the following (excluding ZPRC material type as these do not require plant extension):
   1. Company Codes in scope
   2. Plants in scope
   3. Purchasing Orgs in scope
   4. Sales Orgs in scope
5. Include only Material Types in scope
6. We will include for migration all materials that have activity over the previous 3 years, to include:
   1. For procurement data use EKKO/EKPO tables (remove any records in EKKO/EKPO where LOEKZ = 'X') and use EKPO/AEDAT for previous 3 years filter
   2. For sales data use VBAK/VBAP tables
   3. For production data use AFKO/AFPO tables 
7. Additionally, we can check material movements using MKPF/MSEG tables (and Transaction Types: IB,ID,IZ,RS,SI,WA,WE,WF,WH,WI,WL,WO,WQ,WR,WS,WV,WZ)
8. We will include for migration all materials that have open documents including the following:
   1. Open PO
   2. Open contracts
   3. Open STO
   4. Open SO
   5. Open WO
9. Have current stock/open inventory

   1. For Open Inventory use the following tables:

      MARD

      MKOL (Consignment stock)

      MSKA (Sales Order stock)

      MSLB (Special stock)

      MSPR (Project stock)

10. We will include all BOM data for materials in scope using tables: MAST/STKO/STPO
11. Materials with Deletion Flags will be excluded unless appearing in the following open transactions:
    1. Open PO
    2. Open contracts
    3. Open STO
    4. Open SO
    5. Open WO
12. Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
13. Materials with the word 'OBSOLETE' or 'DELETED' contained within the Short Description will be excluded. Also excluded are Materials where Short Description contains '**OBS', '**OBS**', '**OBS***', '*OBS*', '*OBS**', '***OBS***'
14. For selected data, if Procurement type MARC.BESKZ = 'E' , then MARC PSTAT like '%A%' - WS relevancy for all the relevant materials

The data from legacy system excludes:

1. All materials flagged for deletion
2. Any blocked or obsolete materials
3. Any inactive materials that are out of scope
4. This Conversion Specification does not include the WPX system (CUI Objects).
   

List of source systems and approximate number of records

Source	Scope	Source Approx. No. of Records	Target System	Target Approx No. of Records
PF2	SAP ECC PF2 records for approximately 60 manufacturing plants divided in the 2 source systems	8,000	S4 HANA	6,000
WP2	SAP ECC PF2 records for approximately 60 manufacturing plants divided in the 2 source systems	25,000	S4 HANA	20,000

Additional Information

Multi-language Requirement

System Pre-defined Languages

Document Management

N/A

Legal Requirement

N/A

Special Requirements

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. The target is on the transformation rules. This list includes what type of field, length and others.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MARC	AUSME	AUSME	Unit of issue	UNIT	3	C
MARC	FRTME	FRTME	Production unit	UNIT	3	C
MARC	MMSTA	MMSTA	Material Status	CHAR	2	R
MARC	MMSTD	MMSTD	Valid From	DATS	8	R : If MARC-MMSTA is filled this field is required
MARC	FEVOR	FEVOR	Prodn Supervisor	CHAR	3	R List of customizing values and mapping with AS IS will be build as per
MARC	LGPRO	LGPRO	Storage Location	CHAR	4	R List of customizing values and mapping with AS IS will be build as per
MARC	SFCPF	CO_PRODPRF	Prod. Sched. Profile	CHAR	6	R : Mapping with As Is values and to be values to be provided
MARC	MATGR	MATNRGROUP	Mat. Grouping	CHAR	20	NU
MARC	SERNP	SERAIL	Serial Number Profile	CHAR	4	NU
MARA	SERLV	SERLV	SerLevel	CHAR	1	NU
MARC	OCMPF	OCM_GPROFILE	Overall profile	CHAR	6	NU
MARC	KZKRI	KZKRI	Indicator: Critical part	CHAR	1	NU
MARC	KZECH	KZECH	Batch entry	CHAR	1	R : Empty is a valid value
MARA	XCHPF	XCHPF	Batch Management Requirement Indicator	CHAR	1	R : Empty is a valid value
MARC	INSMK	INSMK	Post to Inspection Stock	CHAR	1	R : Empty is a valid value
MARA	XGCHP	XGCHP	Approved Batch Record Required	CHAR	1	NU
MARC	XCHPF	XCHPF	Batch Management Requirement Indicator for Plant	CHAR	1	R : Empty is a valid value
MARC	UNETO	UNETO	Underdel. Tol.	DEC	3	NU
MARC	UEETO	UEETO	Overdeliv. Tol.	DEC	3	NU
MARC	UEETK	UEETK	Indicator: Unlimited Overdelivery Allowed	CHAR	1	NU
MARC	RUEZT	RUEZT	Setup time	DEC	5	NU
MARC	TRANZ	TRANZ	Interoperation	DEC	5	NU
MARC	DZEIT	DZEIT	In-house production time	DEC	3	NU
MARC	BEARZ	BEARZ	Processing time	DEC	5	NU
MARC	BASMG	BASMG	Base quantity	QUAN	13	NU

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
01	CNV-01	Material is not an "E" Procurement type	Materials with "E" Procurement needs to have Work Scheduling View	Materials with no "E" procurement are out of scope	PF2/WP2
02	CNV-02	Production Scheduling Profile is missing	Materials with WS View in Material Master must have Production Scheduling  Profile	Materials with no Prod. Sched Profile needs to be updated by the business	PF2/WP2
03	CNV-03	Production Supervisor is Missing	Materials with WS view and No Prod Supervisor filled, needs to be checked by the Business	Prod Supervisor has been updated for all relevant materials	PF2/WP2
04	CNV-04	Production Storage Location is missing	Materials with WS view need to have Production Storage location defined	Material without Prod Storage Location needs to be updated for all relevant materials	PF2/WP2
05	CNV-05	Production Version is missing	Materials with WS view needs to have a PV	Report to show Proc Type E, WS view, w/o PV flag	PF2/WP2
06	CNV-06	Work Scheduling View is missing	Materials with MARC-BESK = E but <> "A" as MARC status	No Procurement type E has no Work Scheduling View	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 from MARC all Material/Plant relevant as Procurement Type E, and be updated as "A" means that the Work Scheduling view is updated	Sinity / Data Team
2	Extract data from source system based on relevancy rule	SyWay Data Team
3	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team
4	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
N/A	NO DCT required

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Data Profiling. MARC table Data Profiling needs to happen before the extraction of data.	Sinity
2	Data Cleansing Reports need to be created	Sinity
3	Data cleansing already done by the Business	Business / Data Team
4	Data has to be validated from the Business to get ready to extract from the source	Business / Data Team

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	<Add steps from Syniti Migrate here>	SyWay S2P Data Team
2	Review and Validate Error and Preload Reports	SyWay S2P Data Team
3	Generate Load Files	SyWay S2P 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/WQ2	MARC	WERKS	PLANT	S/4 HANA	MARC	WERKS	PLANT	Follow the transformation rules of CNV-2010
1	PF2/WQ2	S_MARA	MATNR	Material Number	S/4HANA	S_MARA	MATNR	Material Number	Follow the rule as per Material Master Basic Views about creation for new Material Numbers CNV-2018 CNV-2010 Materials - General Plant Data / S.Loc Data
2	PF2/WQ2	MARC	AUSME	Unit of issue	S/4HANA	MARC	AUSME	Unit of issue	Based from MARA UOM
3	PF2/WQ2	MARC	FRTME	Production unit	S/4HANA	MARC	FRTME	Production unit	Value Mapping (Unit of issue for material /plant)
4	PF2/WQ2	MARC	MMSTA	Material Status	S/4HANA	MARC	MMSTA	Material Status	Depending on the Configuration Workbook, But Only Active Materials Status can be updated /populated
5	PF2/WQ2	MARC	MMSTD	Valid From	S/4HANA	MARC	MMSTD	Valid From	If MMSTA is filled, use the load date
6	PF2/WQ2	MARC	LGPRO	Production Storage Location	S/4HANA	MARC	LGPRO	Production Storage Location	Value Mapping for Storage Location for Production
7	PF2/WQ2	MARC	KZECH	Batch Entry	S/4HANA	MARC	KZECH	Batch Entry	Copy
8	PF2/WQ2	MARC	XCHPF	Batch Management	S/4HANA	MARC	XCHPF	Batch Management	Copy
9	PF2/WQ2	MARC	INSMK	Post to Inspection Stock	S/4HANA	MARC	INSMK	Post to Inspection Stock	Copy
10	PF2/WQ2	MARC	FEVOR	Prodn Supervisor	S/4HANA	MARC	FEVOR	Prodn Supervisor	Value Mapping for Plant/Material / Prod Supervisor
11	PF2/WQ2	MARC	SCHPF	Prod Sch Profile	S/4HANA	MARC	SCHPF	Prod Sch Profile	Values Mapping for Plant/Material/Prod Sch Profile

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
Material Type	Mapping of legacy Material Types to target system value
Material Group	Mapping of legacy Material Groups to target system value

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Data cleansing must be finished and validated	SyWay MFG Data Team
2	Data Transformation load files need to be validated by the business at Plant Level	SyWay MFG Data Team
3	All Value Mapping files must be finished and aligned with the CS	SyWay MFG Data Team
4	All Data dependencies has to be finished. Any delay can bring delays on this

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Verify Record Count	SyWay MFG Data Team to verify that the total number of relevant records from the  DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	SyWay MFG 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
To check Data Accuracy checking count of records to load and loaded	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
Data owners to grant that the records in the load files are okay and according with the rules and mappings	To check and validate the load files with all the transformation and mapping rules, to be signed off.

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 file and pick 5 data registers, load manually without any tool. See what happens. If all okay, proceed with the next step.	SyWay MFG Data Team
2	Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay.	SyWay MFG Data Team
3	Proceed with the full load if steps one and two were succeed.	SyWay MFG Data Team
4	Validate few records loaded by accessing standard transactions from S/4HNA eg. MM03	SyWay MFG Data Team
5	Generate post load report if step 5 is validated	SyWay MFG 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
001	Production Scheduling Profile
002	Production Supervisor

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
Verify Count	SyWay P2F MFG 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 Material 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.
• CNV-2008 Material Master - Work Scheduling view 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