Purpose

The purpose of this document is to define the conversion approach to create Waste Materials  Materials (Waste and Emissions) in S/4 HANA.

In legacy ECC systems (PF2, WP2), materials relevant to waste management and emissions are identified by tagging existing materials with specific roles or classifications, along with associated physical-chemical properties used for regulatory compliance. These materials are managed within the Material Master (migrated separately by the S2P team), but the environmental tagging and properties reside in EHS-related tables

Conversion Scope

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

In S/4HANA, Environment, Health & Safety (EHS) functionality provides dedicated Fiori apps where users assign environmental roles to existing materials:

Transport and Disposal Logistics role for Waste-relevant materials

Emissions role for Emission-relevant materials

Physical-chemical properties relevant to waste or emissions are maintained per material.

This conversion specifically focuses on migrating:

Material-level role assignments as Waste or Emission relevant

Associated physical-chemical properties per material and region

The data from legacy system includes:

1. Materials flagged as Waste-relevant or Emission-relevant
2. Role assignments linking materials to environmental classifications
3. Physical-chemical properties linked to these materials for compliance
4. Country or region-specific tagging relevant to regulatory needs

The data from legacy system excludes:

Source Approx No. of Records

No. of Records

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Data Ownership & System Architecture: It is critical to highlight that the lifecycle and governance of these materials are split across two distinct functional domains:

• Source-to-Pay (S2P) / Supply Chain: The foundational Material Master record (e.g., Basic Data, Plant Data, purchasing views) is owned and managed in S/4HANA by S2P. They are responsible for creating the base material shell.

• Environmental Health and Safety (EHS): The environment-related and compliance-specific data (e.g., Waste Codes, Waste Types, Physical/Chemical Properties, Emissions applicability) is managed in EHS using the Manage Material Data Fiori app.

The Role of Logistics Roles in EHS: A key driver for this specific EHS data conversion is the assignment of Logistics Roles. While S2P defines what the material is, the EHS enrichment defines how the material behaves within environmental processes. By assigning specific Logistics Roles in the Fiori app, the system dictates the material's function:

• Transport: Identifies materials utilized in the transportation routing and documentation of waste.

• Emission: Flags the material as a subject for environmental compliance, meaning it generates trackable emissions or is used in emission calculations.

• Disposal: Identifies the actual physical waste product being generated, stored, and sent to a facility for disposal.

• Note: A single material record can hold multiple logistics roles simultaneously if applicable.

Currently, in the legacy ECC system, this data is partially represented across Material Master (MARA) and Vendor Master (LFA1 for waste disposal partners/facilities). In S/4HANA, the EHS data model requires these S2P base materials to be explicitly extended with these Logistics Roles, Chemical Compliance Information, and Waste Management parameters.

Conversion Scope

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

This conversion will utilize a Data Collection Template (DCT) approach. The Data Team will extract a baseline of records from ECC based on strict relevancy criteria and map them to the corresponding S2P base materials. The business will then review this baseline and enrich the DCT with S/4HANA-specific EHS attributes (like the Logistics Roles) before the final load.

In S/4HANA, Environment, Health & Safety (EHS) provides dedicated Fiori apps where users assign environmental roles to existing materials:

Transport and Disposal Logistics role for Waste-relevant materials

Emissions role for Emission-relevant materials

Physical-chemical properties relevant to waste or emissions are maintained per material.

This conversion specifically focuses on migrating:

Material-level role assignments as Waste or Emission relevant

Associated physical-chemical properties per material and region

The data from legacy system includes:

1. Materials flagged as Waste-relevant or Emission-relevant
2. Role assignments linking materials to environmental classifications
3. Physical-chemical properties linked to these materials for compliance
4. Country or region-specific tagging relevant to regulatory needs
5. Active Materials in ECC (MARA) where the Material Type corresponds to Waste or Emission categories (e.g., FERT, HALB, or custom legacy waste material types like WAST). Note: These materials MUST be confirmed as in-scope for the S2P Material Master load.
6. Active Vendors in ECC (LFA1/LFB1) flagged with specific Account Groups or industry codes denoting them as Waste Partners/Disposal Facilities (required to build the Waste Partner UUID relationships).
7. Materials linked to existing environmental health and safety (EHS) specifications or hazard classifications in legacy systems.

The data from legacy system excludes:

1. Core Material Master data (already migrated by S2P team)

2. Actual waste quantities, volumes, or emissions data (thresholds, limits)

3. Materials flagged for deletion (LVORM = 'X' at client or plant level) in ECC.
4. Standard direct/indirect procurement materials not associated with waste generation or environmental emissions.
5. Blocked vendor accounts (Waste Partners) with no recent transactional activity.

Additional Information

Multi-language Requirement

Descriptions for Materials and Waste Types must be loaded in English. 

Document Management

Not Applicable

Legal Requirement

Must align with REACH, GHS, and local environmental agency waste coding structures. Data validation must ensure EHFNDD_CCI_PURP-PURPOSE_UUID (Compliance Purpose) is accurately mapped.

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

Conversion Process

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

For every waste material in source system, a material has to be created in target system.

Extract all active materials from MARA from source system and determine waste materials from the list by filtering with waste in the descriptions and based on historical transactions involving materials to waste transporters/disposers. For these materials, create material using manage material data fiori app or automated process.

Also, need to update properties, waste code details for the materials using the same fiori app "manage material data" or automated process.

This object will be managed as a Hybrid/Enrichment DCT.

Phase 1: Data Extraction & Baseline Generation (Data Team)

1. Extract: Query ECC tables using the relevancy criteria.

2. Cross-Reference: Check the extracted list against the S2P Material Master load manifest to ensure the base product will exist in S/4HANA.

3. Generate DCT: Produce the Data Collection Template pre-populated with baseline S2P identifiers (Product ID) and descriptions.

Phase 2: Business Enrichment (EHS Business Team)

1. Review: EHS business stakeholders review the baseline DCT.

2. Enrich: The business populates missing, S/4HANA-specific EHS data directly into the DCT. Key enrichment fields aligned with Fiori "Manage Material Data" include:

   • Logistics Roles: (Checkboxes for Transport, Emission, Disposal)

   • Waste Codes & Waste Type

   • Physical/Chemical Properties (State of matter, Density, Flashpoint)

   • Compliance Scenario assignments

   • Compliance purposes

Phase 3: Validation & Load (Data Team)

1. Validate: Run automated pre-load validations against the enriched DCT. Verify that the Material ID exists in the target system (loaded by S2P).

2. Load: Data is loaded into S/4HANA EHS.

Data Privacy and Sensitivity

No PII or sensitive data is included in the Material (Waste & Emissions) data object.

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

Selection Screen

Data Collection Template (DCT)

Material (Waste and Emissions) 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 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

Transformation Rules

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

Conversion Process

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

For every material in source system of material type WAST, a material has to be created in target system.

Extract all materials from MARA from source system and filter with material type WAST. For these materials, create material using manage material data fiori app or automated process.

Also, need to update properties, waste code details for the materials using the same fiori app "manage material data" or automated process.

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

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.
• Materials (Waste & Emissions) is in scope based on data design and any exception requested by business.
• All predecessor objects (Product Master, Business Partner) will be fully loaded, validated, and active in the S/4HANA production client prior to the EHS cutover window.

See also

Change log