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

Additional Information

Multi-language Requirement

System Pre-defined Languages

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

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.

Data Cleansing

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

1. The data exists. connects to the source and loads the data into . 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 ; 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 . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log

Workflow history