| Status | |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Materials (Waste and Emissions) in S/4 HANA.
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:
- Materials flagged as Waste-relevant or Emission-relevant
- Role assignments linking materials to environmental classifications
- Physical-chemical properties linked to these materials for compliance
- Country or region-specific tagging relevant to regulatory needs
- 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 likeWAST). Note: These materials MUST be confirmed as in-scope for the S2P Material Master load. - 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 UUIDrelationships). - Materials linked to existing environmental health and safety (EHS) specifications or hazard classifications in legacy systems.
The data from legacy system excludes:
Core Material Master data (already migrated by S2P team)
Actual waste quantities, volumes, or emissions data (thresholds, limits)
- Materials flagged for deletion (
LVORM= 'X' at client or plant level) in ECC. - Standard direct/indirect procurement materials not associated with waste generation or environmental emissions.
- Blocked vendor accounts (Waste Partners) with no recent transactional activity.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| WP2/PF2 | Active Waste/Emission Materials | TBD | S/4 HANA | TBD |
| WP2/PF2 | Active Waste Partners / Facilities | TBD | S/4 HANA | TBD |
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
Specify any special requirements or considerations that may impact the data conversion process based on specific locations, regulatory compliance or system limitations. Clearly outline any regional or localization requirements such as country-specific data formats, legal reporting obligations or industry standards that must be adhered to (e.g., localization rules for countries like China).
If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.
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 |
|---|---|---|---|---|---|---|
| EHEWAD_WA_MAT | UUID | EHEWA_WP_MAT_UUID | Waste Material UUID | RAW | 16 | System generated |
| EHEWAD_WA_MAT | WASTE_PARTNER_UUID | EHEWA_WASTE_PARTNER_UUID | Waste Partner UUID | RAW | 16 | System generated |
| EHEWAD_WA_MAT | FACILITY_UUID | EHEWA_WASTE_FACILITY_UUID | Waste Disposal Facility UUID | RAW | 16 | System generated |
| EHEWAD_WA_MAT | CCI_UUID | EHFND_CCI_UUID | Chemical Compliance Information UUID | RAW | 16 | System generated |
| EHEWAD_WA_MAT | MC_CODE | EHEWA_WASTE_MC_CODE | Waste Management Method Code | CHAR | 10 | Required |
| EHEWAD_WA_MAT | CREA_DATE_TIME | TIMESTAMPL | Created On | DEC | 21 | System generated |
| EHEWAD_WA_MAT | CREA_UNAME | UNAME | Created By | CHAR | 12 | System generated |
| EHEWAD_WA_MAT | LCHG_DATE_TIME | TIMESTAMPL | Changed On | DEC | 21 | System generated |
| EHEWAD_WA_MAT | LCHG_UNAME | UNAME | Changed By | CHAR | 12 | System generated |
| EHEWAD_WA_MAT | DUMMY_EHEWA_MAT | CFD_DUMMY | Dummy Field | CHAR | 1 | Not Used |
| EHFNDD_CCI_MAT | UUID | EHFND_CCI_MAT_UUID | Product Assignment UUID | RAW | 16 | System generated |
| EHFNDD_CCI_MAT | CREA_DATE_TIME | TIMESTAMPL | Created On (UTC) | DEC | 21 | System generated |
| EHFNDD_CCI_MAT | CREA_UNAME | UNAME | Created By | CHAR | 12 | System generated |
| EHFNDD_CCI_MAT | LCHG_DATE_TIME | TIMESTAMPL | Last Changed On (UTC) | DEC | 21 | System generated |
| EHFNDD_CCI_MAT | LCHG_UNAME | UNAME | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_CCI_MAT | CHEMICAL_COMPLIANCE_UUID | EHFND_CCI_UUID | Chemical Compliance Information UUID | RAW | 16 | System generated |
| EHFNDD_CCI_MAT | MATNR | EHFND_MAT_ID | Product | CHAR | 40 | Required |
| EHFNDD_CCI_MAT | IS_PRIMARY | EHFND_CCI_CCOMP_IS_PRIMARY | Name Representing the Product | CHAR | 1 | Conditional |
| EHFNDD_CCI | UUID | EHFND_CCI_UUID | Chemical Compliance UUID | RAW | 16 | System generated |
| EHFNDD_CCI | CREA_DATE_TIME | TIMESTAMPL | Created On | DEC | 21 | System generated |
| EHFNDD_CCI | CREA_UNAME | UNAME | Created By | CHAR | 12 | System generated |
| EHFNDD_CCI | LCHG_DATE_TIME | TIMESTAMPL | Last Changed On | DEC | 21 | System generated |
| EHFNDD_CCI | LCHG_UNAME | UNAME | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_CCI | RESPONSIBLE_UNIT | EHFND_CCI_RESPONSIBLE_UNIT_PSS | Responsible Unit | CHAR | 10 | System generated |
| EHFNDD_CCI | RESPONSIBLE_UNIT_DGR | EHFND_CCI_RESPONSIBLE_UNIT_DG | Responsible Unit – Dangerous Goods | CHAR | 10 | Required |
| EHFNDD_CCI | INTERNAL_NAME | EHFND_CCI_INTERNAL_NAME | Internal Name | CHAR | 132 | Required |
| EHFNDD_CCI | IS_BASE_PRODUCT | EHFND_CCI_IS_BASE_PRODUCT | Base Product Indicator | CHAR | 1 | Not Used |
| EHFNDD_CCI | IS_SOLD | EHFND_CCI_IS_SOLD | Sold Indicator | CHAR | 1 | Not Used |
| EHFNDD_CCI | IS_TRANSPORTED | EHFND_CCI_IS_TRANSPORTED | Transported Indicator | CHAR | 1 | Required |
| EHFNDD_CCI | IS_SOURCE | EHFND_CCI_IS_SOURCED | Sourced Indicator | CHAR | 1 | Not Used |
| EHFNDD_CCI | IS_PRODUCED | EHFND_CCI_IS_PRODUCED | Produced Indicator | CHAR | 1 | Not Used |
| EHFNDD_CCI | SPECIFICATION_ID | EHFND_INTERNAL_NR | Specification ID | CHAR | 12 | Not Used |
| EHFNDD_CCI | IS_RESEARCHED | EHFND_CCI_IS_RESEARCHED | R&D Sample Indicator | CHAR | 1 | Not Used |
| EHFNDD_CCI | SPECIFICATION_REF | EHFND_EHS_ESERECN | Specification Reference | NUMC | 20 | System generated |
| EHFNDD_CCI | TYPE | EHFND_CCI_TYPE | CCI Type | CHAR | 2 | System generated |
| EHFNDD_CCI | IS_NOT_DG_RELEVANT | EHFND_CCI_IS_NOT_DG_RLVT | Not Dangerous Goods Relevant | CHAR | 1 | Required |
| EHFNDD_CCI | IS_NOT_PMA_RELEVANT | EHFND_CCI_IS_NOT_PMA_RLVT | Not Product Marketability Relevant | CHAR | 1 | Not Used |
| EHFNDD_CCI | IS_NOT_PS_RELEVANT | EHFND_CCI_IS_NOT_PS_RLVT | Not Product Safety Relevant | CHAR | 1 | Not Used |
| EHFNDD_CCI | IS_NOT_LR_RELEVANT | EHFND_CCI_IS_NOT_PCS_RLVT | Not Legal/Regulatory Relevant | CHAR | 1 | Conditional |
| EHFNDD_CCI | IS_EMISSION_RELEVANT | EHFND_CCI_IS_EMISSION_RLVT | Emission Relevant | CHAR | 1 | Required |
| EHFNDD_CCI | IS_DISPOSED | EHFND_CCI_IS_DISPOSED | Disposed Indicator | CHAR | 1 | Required |
| EHFNDD_CCI | PRODUCT_CATEGORIZATION | EHFND_CHM_PROD_CATZTNPHRS_UUID | Chemical Product Categorization | RAW | 16 | System generated |
| EHFNDD_CCI | IS_MCP | EHFND_CCI_IS_MCP | Product Is a Multi-Component Product | CHAR | 1 | System generated |
| EHFNDD_CCA_ADLPR | UUID | EHFND_CCA_ADLPR_UUID | Chemical Compliance Additional Property UUID | RAW | 16 | System generated |
| EHFNDD_CCA_ADLPR | CHEMICAL_COMPLIANCE_UUID | EHFND_CCI_UUID | Chemical Compliance Information UUID | RAW | 16 | System generated |
| EHFNDD_CCA_ADLPR | CREA_DATE_TIME | TIMESTAMPL | Created On | DEC | 21 | System generated |
| EHFNDD_CCA_ADLPR | CREA_UNAME | UNAME | Created By | CHAR | 12 | System generated |
| EHFNDD_CCA_ADLPR | LCHG_DATE_TIME | TIMESTAMPL | Last Changed On | DEC | 21 | System generated |
| EHFNDD_CCA_ADLPR | LCHG_UNAME | UNAME | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_CCA_ADLPR | VERSION_NUMBER | EHFND_VERSION_NUMBER | Version Number | INT4 | 10 | System generated |
| EHFNDD_CCA_ADLPR | RELEASE_STATUS | EHFND_CCA_ADLPR_STATUS | Release Status | CHAR | 2 | System generated |
| EHFNDD_CCA_ADLPR | VALID_FROM | EHFND_VALID_FROM_TSTMP | Valid From | DEC | 15 | System generated |
| EHFNDD_CCA_ADLPR | VALID_TO | EHFND_VALID_TO_TSTMP | Valid To | DEC | 15 | System generated |
| EHFNDD_CCA_PRPTY | UUID | EHFND_CCI_PRPTYAS_UUID | Property Assignment UUID | RAW | 16 | System generated |
| EHFNDD_CCA_PRPTY | CCA_ADLPR_UUID | EHFND_CCA_ADLPR_UUID | Additional Property UUID | RAW | 16 | System generated |
| EHFNDD_CCA_PRPTY | CREA_DATE_TIME | TIMESTAMPL | Created On | DEC | 21 | System generated |
| EHFNDD_CCA_PRPTY | CREA_UNAME | UNAME | Created By | CHAR | 12 | System generated |
| EHFNDD_CCA_PRPTY | LCHG_DATE_TIME | TIMESTAMPL | Last Changed On | DEC | 21 | System generated |
| EHFNDD_CCA_PRPTY | LCHG_UNAME | UNAME | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_CCA_PRPTY | PROPERTY_KEY_REF | EHFND_CCI_PRPTY_UUID | Property Key Reference UUID | RAW | 16 | System generated |
| EHFNDD_CCA_PRPTY | UNIT_KEY_REF | EHFND_CCI_PRPTY_UNIT_UUID | Unit Key Reference UUID | RAW | 16 | System generated |
| EHFNDD_CCA_PRPTY | VALUE | EHFND_CCI_PRPTY_VALUE | Property Value | DF16_RAW | 16 | Conditional |
| EHFNDD_CCA_PRPTY | UNIT | EHFND_UNIT_CODE | Unit of Measure | UNIT | 3 | Conditional |
| EHFNDD_CCA_PRPTY | COMMENT_TEXT | EHFND_NAME | Comment / Description | CHAR | 60 | Conditional |
| EHFNDD_CCI_PURP | UUID | EHFND_CCI_PURP_UUID | Purpose Assignment UUID | RAW | 16 | System generated |
| EHFNDD_CCI_PURP | CHEMICAL_COMPLIANCE_UUID | EHFND_CCI_UUID | Chemical Compliance UUID | RAW | 16 | System generated |
| EHFNDD_CCI_PURP | CREA_DATE_TIME | TIMESTAMPL | Created On | DEC | 21 | System generated |
| EHFNDD_CCI_PURP | CREA_UNAME | UNAME | Created By | CHAR | 12 | System generated |
| EHFNDD_CCI_PURP | LCHG_DATE_TIME | TIMESTAMPL | Last Changed On | DEC | 21 | System generated |
| EHFNDD_CCI_PURP | LCHG_UNAME | UNAME | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_CCI_PURP | PURPOSE_UUID | EHFND_CMPLNC_PRPS_UUID | Purpose UUID | RAW | 16 | System generated |
| EHFNDD_CHM_COMP | DB_KEY | /BOBF/CONF_KEY | Root Node Key | RAW | 16 | System generated |
| EHFNDD_CHM_COMP | ROOT_KEY | /BOBF/CONF_KEY | Root Key | RAW | 16 | System generated |
| EHFNDD_CHM_COMP | PARENT_KEY | /BOBF/CONF_KEY | Parent Node Key | RAW | 16 | System generated |
| EHFNDD_CHM_COMP | DATETIME_CR | /BOBF/DATETIME_CR | Created On | DEC | 15 | System generated |
| EHFNDD_CHM_COMP | USER_ID_CR | /BOBF/USER_ID_CR | Created By | CHAR | 12 | System generated |
| EHFNDD_CHM_COMP | DATETIME_CH | /BOBF/DATETIME_CH | Last Changed On | DEC | 15 | System generated |
| EHFNDD_CHM_COMP | USER_ID_CH | /BOBF/USER_ID_CH | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_CHM_COMP | LIS_SUB_KEY_REF | EHFND_LISU_ROOT_REF_KEY | Listed Substance Root Key | RAW | 16 | System generated |
| EHFNDD_CHM_COMP | PROPORTION | EHFND_CHM_PROPORTION_MIN | Proportion | DF16_RAW | 16 | Conditional |
| EHFNDD_CHM_COMP | UNIT | EHFND_UNIT_CODE | Unit | UNIT | 3 | Conditional |
| EHFNDD_CHM_COMP | EEW_CHM_COMPOS_D | DUMMY | Dummy Field | CHAR | 1 | Not Used |
| EHFNDD_CP_TEXT | COMPLIANCE_PURPOSE_ID | EHFND_CMPLNC_PRPS_ID | Purpose ID | CHAR | 15 | System generated |
| EHFNDD_CP_TEXT | COMPLIANCE_PURPOSE_UUID | EHFND_CMPLNC_PRPS_UUID | Compliance Purpose | RAW | 16 | System generated |
| EHFNDD_CP_TEXT | LANGUAGE | SYLANGU | Language Key | LANG | 1 | System generated |
| EHFNDD_CP_TEXT | COMPLIANCE_PURPOSE_NAME | EHFND_CMPLNC_PRPS_NAME | Compliance Purpose Name | CHAR | 120 | Required |
| EHFNDD_PHPR_NM | BCO_ID | EHFND_BCO_ID | BCO ID | CHAR | 40 | System generated |
| EHFNDD_PHPR_NM | BCO_KEY | EHFND_BCO_KEY | BCO Key | CHAR | 32 | System generated |
| EHFNDD_PHPR_NM | DB_KEY | /BOBF/CONF_KEY | NodeID | RAW | 16 | System generated |
| EHFNDD_PHPR_NM | PARENT_KEY | /BOBF/CONF_KEY | Parent Key | RAW | 16 | System generated |
| EHFNDD_PHPR_NM | DATETIME_CR | /BOBF/DATETIME_CR | Created On | DEC | 15 | System generated |
| EHFNDD_PHPR_NM | USER_ID_CR | /BOBF/USER_ID_CR | Created By | CHAR | 12 | System generated |
| EHFNDD_PHPR_NM | DATETIME_CH | /BOBF/DATETIME_CH | Last Changed On | DEC | 15 | System generated |
| EHFNDD_PHPR_NM | USER_ID_CH | /BOBF/USER_ID_CH | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_PHPR_NM | LANGUAGE | EHFND_LANGU | Language | LANG | 1 | System generated |
| EHFNDD_PHPR_NM | TEXT | EHFND_PHYSICAL_PARAMETER_NAME | Name | CHAR | 60 | Required |
| EHFNDD_PHPR_NM | TEXT_NORMED | EHFND_PHYSICAL_PARAMETER_NAME | Normalized Name | CHAR | 60 | System generated |
| EHFNDD_PHPR_NM | EEW_PHPAR_ROOT_D | DUMMY | Dummy Field | CHAR | 1 | Not Used |
| EHFNDD_LISU_NAME | LISTSUB_ID | EHFND_REGBASLST_SUB | Listed Substance ID | CHAR | 12 | System generated |
| EHFNDD_LISU_NAME | BCO_KEY | EHFND_BCO_KEY | BCO Key | CHAR | 32 | System generated |
| EHFNDD_LISU_NAME | DB_KEY | /BOBF/CONF_KEY | NodeID | RAW | 16 | System generated |
| EHFNDD_LISU_NAME | PARENT_KEY | /BOBF/CONF_KEY | Parent Key | RAW | 16 | Not Used |
| EHFNDD_LISU_NAME | NODE_CAT_KEY | /BOBF/CONF_KEY | Node Category Key | RAW | 16 | System generated |
| EHFNDD_LISU_NAME | DATETIME_CR | /BOBF/DATETIME_CR | Created On | DEC | 15 | System generated |
| EHFNDD_LISU_NAME | USER_ID_CR | /BOBF/USER_ID_CR | Created By | CHAR | 12 | System generated |
| EHFNDD_LISU_NAME | DATETIME_CH | /BOBF/DATETIME_CH | Last Changed On | DEC | 15 | System generated |
| EHFNDD_LISU_NAME | USER_ID_CH | /BOBF/USER_ID_CH | Last Changed By | CHAR | 12 | System generated |
| EHFNDD_LISU_NAME | LANGUAGE | EHFND_LANGU | Language | LANG | 1 | System generated |
| EHFNDD_LISU_NAME | TEXT | EHFND_LISU_NAME_TEXT | Listed Substance Name | CHAR | 1333 | Conditional |
| EHFNDD_LISU_NAME | TEXT_NORMED | EHFND_LONG_NAME | Normalized Name | CHAR | 255 | Not Used |
| EHFNDD_LISU_NAME | SEQUENCE_NUMBER | EHFND_LISU_SEQ_NUM | Name Sequence Number | INT1 | 3 | Not Used |
| EHFNDD_LISU_NAME | NAME_ID | EHFND_LISU_NAME_ID | Name ID | INT4 | 10 | System generated |
| EHFNDD_LISU_NAME | EEW_LONG_TEXT_D | DUMMY | Dummy Field | CHAR | 1 | Not Used |
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 |
|---|---|---|---|---|---|
| CL-01 | High | "Orphaned Legacy Vendor" | Legacy vendors targeted as Waste Partners must not have a deletion flag (LFA1-LOEVM) | Exclude from Extract | ECC |
| CL-02 | High | "Missing Base Product in Target" | If an EHS Material maps to a Product ID, that ID must exist in the approved S2P Product Master manifest | Reject Record | DCT |
| CL-03 | Medium | "Invalid State of Matter" | State of Matter must be populated with target values (e.g., 01=Solid, 02=Liquid, 03=Gas) | Flag for Enrichment | DCT |
| CL-04 | High | "Missing Logistics Role" | Every material must have at least one Logistics Role marked as 'Y' | Reject Record | DCT |
Conversion Process
The high-level process is represented by the diagram below:
Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object
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)
Extract: Query ECC tables using the relevancy criteria.
Cross-Reference: Check the extracted list against the S2P Material Master load manifest to ensure the base product will exist in S/4HANA.
Generate DCT: Produce the Data Collection Template pre-populated with baseline S2P identifiers (Product ID) and descriptions.
Phase 2: Business Enrichment (EHS Business Team)
Review: EHS business stakeholders review the baseline DCT.
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)
Validate: Run automated pre-load validations against the enriched DCT. Verify that the Material ID exists in the target system (loaded by S2P).
Load: Data is loaded into S/4HANA EHS.
Data Privacy and Sensitivity
Summarize Data Privacy and Sensitivity Requirements, if anyNo 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:
- The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migratei Migrate. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- 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 |
|---|---|---|
| EX-01 | Extract Legacy Waste Materials from MARA / MAKT based on relevancy criteria | Data Team |
| EX-02 | Extract Legacy Waste Vendors from LFA1 / LFB1 based on Selection Screen | Data Team |
| EX-03 | Cross-reference extracted legacy materials against the final S2P Product Master load manifest. | Data Team |
| EX-04 | Generate pre-populated DCT containing Legacy Material IDs, Material Descriptions, and Legacy Vendor IDs for Business Enrichment. | Data 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 Waste Materials data with exception of some fields which require transformation as mentioned in the transformation rule.Material (Waste and Emissions) DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| MC_CODE | Waste Management Method Code | Required. Format rules: Length – 4. Data Type – CHAR. Allowed values/reference: Refer to EHEWAC_MC_CODE > Field = EHEWA_WASTE_MC_CODE. Conditional logic: NA. Multi-language: NA. Comments: Determines waste treatment or disposal type. |
| MATNR | Product ID / Material Number linked to Compliance data | Required. Format rules: As per Material Master configuration. Length - 40 |
| IS_PRIMARY | Name Representing the Product | Conditional. Format rules: Boolean (X/Blank). Data Type – CHAR, Length - 1. Allowed values/reference: ‘X’ = Primary. Conditional logic: Only one record per material can be flagged as Primary. Multi-language: NA. Comments: Identifies primary compliance linkage. |
| RESPONSIBLE_UNIT_DGR | Responsible Unit – Dangerous Goods | Required if DG relevant. Format rules: As per Org Unit format. Data Type – CHAR. Length - 10 Allowed values/reference: Must exist in approved DG organizational structure. Conditional logic: Mandatory when DG indicator is active. Multi-language: NA. Comments: Responsible unit for DG compliance. |
| INTERNAL_NAME | Internal Name | Required. Format rules: Data Type – CHAR. Length -132 Allowed values/reference: NA Conditional logic: NA. Multi-language: NA Comments: Internal product name for compliance reporting. |
| IS_TRANSPORTED | Transported Indicator | Required. Format rules: Boolean (X/Blank). Data Type – CHAR, Length- 1. Allowed values/reference: ‘X’ = Transported. Conditional logic: If ‘X’, DG compliance data must exist. Multi-language: NA. Comments: Indicates transport relevance. |
| IS_NOT_DG_RELEVANT | Not Dangerous Goods Relevant | Conditional. Format rules: Boolean (X/Blank). Data Type – CHAR, Length - 1. Allowed values/reference: ‘X’ = Not DG Relevant. Conditional logic: Cannot conflict with transport indicator. Multi-language: NA. Comments: Identifies DG exclusion. |
| IS_NOT_LR_RELEVANT | Not Legal/Regulatory Relevant | Conditional. Format rules: Boolean (X/Blank). Data Type – CHAR, Length - 1. Allowed values/reference: ‘X’ = Not LR Relevant. Conditional logic: If flagged, legal reporting objects not generated. Multi-language: NA. Comments: Legal/regulatory relevance indicator. |
| IS_EMISSION_RELEVANT | Emission Relevant | Conditional. Format rules: Boolean (X/Blank). Data Type – CHAR, Length - 1. Allowed values/reference: ‘X’ = Emission Relevant. Conditional logic: Mandatory to be maintained Multi-language: NA. Comments: Emission reporting relevance. |
| IS_DISPOSED | Disposed Indicator | Conditional. Format rules: Boolean (X/Blank). Data Type – CHAR, Length - 1 Allowed values/reference: ‘X’ = Disposed. Conditional logic: NA Multi-language: NA. Comments: Disposal relevance indicator. |
| TEXT | Name | Conditional. Format rules: Data Type – CHAR, Length - 60 Allowed values/reference: Conditional logic: Must align with disposal indicator. Multi-language: NA. Comments: Disposal relevance indicator. |
| VALUE | Property Value | Required. Format rules: Numeric; precision per property type. Data Type – DEC/CHAR (config dependent). Length - 16 Allowed values/reference: Must align with property definition. Conditional logic: To be provided only if required or available Multi-language: NA. Comments: Stores compliance property value. |
| UNIT | Unit of Measure | Required. Format rules: Valid Unit of Measure. Data Type – CHAR. Allowed values/reference: Refer to SAP UoM table (T006). Length - 3 Conditional logic: Must correspond to property type. Multi-language: As per UoM settings. Comments: Unit for property value. |
| COMMENT_TEXT | Comment / Description | Optional. Format rules: . Data Type – STRING/CHAR. Allowed values/reference: System text length limit applies. Length - 60 Conditional logic: NA. Multi-language: Supported. Comments: Regulatory explanation or remarks. |
| TEXT | Listed Substance Name | Optional. Format rules: . Length - 1333 |
| PROPORTION | Proportion | Optional. Format rules: Data Type – DF16_RAW. Allowed values/reference: 16 Length - 16 Conditional logic: NA. Multi-language: NA Comments: NA |
| UNIT | Unit | Optional. Format rules: Data Type –UNIT. Allowed values/reference: T006 |
| COMPLIANCE_PURPOSE_NAME | Compliance Purpose Name | Optional. Format rules: . Length - 120 |
| Waste_type | Waste type | Format rules: Data type: Char, Length: 30 Allowed values: Hazardous, Non-Hazardous, Universal Conditional logic: NA. Multi-language: NA |
Extraction Dependencies
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Source-to-Pay (S2P) team finalizes and freezes the target Product Master migration manifest. | S2P |
| 2 | S/4HANA EHS configuration for Waste Codes, Waste Types, and Compliance Purposes is finalized and provided to the Data Team for value mapping. | S2S Functional |
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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti Migrate.
- 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 | Ingest baseline legacy extract into migration tool/staging environment. | Data Team |
| 2 | Ingest fully enriched DCT from the EHS Business Data Owners. | Data Team |
| 3 | Execute Transformation Logic (Joins, Value Mapping, Defaulting). | Data Team |
| 4 | Generate Target-Ready Load File for Pre-Load Validation. | Data Team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT/ECC | MAKT | INTERNAL_NAME | INTERNAL NAME | S/4 HANA | EHFNDD_CCI | INTERNAL_NAME | INTERNAL NAME | Direct Map. Pass value exactly as enriched in DCT. |
| 2 | DCT/ECC | MARA | MATNR | Product ID / Material Number linked to Compliance data | S/4 HANA | EHFNDD_CCI_MAT | MATNR | Product ID | Direct mapping |
| 3 | DCT | IS_TRANSPORTED | TRANSPORT Indicator | S/4 HANA | EHFNDD_CCI | IS_TRANSPORTED | TRANSPORT Indicator | If DCT = 'Y', pass 'X' (True). Else pass ' ' (False). | |
| 4 | DCT | IS_EMISSION_RELEVANT | EMISSION_RELEVANT indicator | S/4 HANA | EHFNDD_CCI | IS_EMISSION_RELEVANT | EMISSION_RELEVANT indicator | If DCT = 'Y', pass 'X' (True). Else pass ' ' (False). | |
| 5 | DCT | IS_DISPOSED | DISPOSAL indicator | S/4 HANA | EHFNDD_CCI | IS_DISPOSED | DISPOSAL indicator | If DCT = 'Y', pass 'X' (True). Else pass ' ' (False). | |
| 6 | DCT | RESPONSIBLE_UNIT_DGR | Responsible unit for DG | S/4 HANA | EHFNDD_CCI | RESPONSIBLE_UNIT_DGR | Responsible unit for DG | Direct mapping | |
| 7 | DCT | MC_CODE | Waste code | S/4 HANA | EHEWAD_WA_MAT | MC_CODE | Waste code | Direct mapping | |
| 8 | DCT | WASTE_TYPE | WASTE TYPE | S/4 HANA | EHFNDD_WA_MAT | WASTE_TYPE | WASTE TYPE | Direct mapping | |
| 9 | DCT | COMPLIANCE_PURPOSE_NAME | Compliance Purpose NaME | S/4 HANA | EHFNDD_CP_TEXT | COMPLIANCE_PURPOSE_NAME | Compliance Purpose name | Direct mapping | |
| 10 | DCT | IS_PRIMARY | Name Representing the Product(Indicator) | S/4 HANA | EHFNDD_CCI_MAT | IS_PRIMARY | Name Representing the Product(Indicator) | Direct mapping | |
| 11 | DCT | IS_NOT_DG_RELEVANT | Not Dangerous | S/4 HANA | EHFNDD_CCI | IS_NOT_DG_RELEVANT | Not Dangerous | Direct mapping | |
| 12 | DCT | IS_NOT_LR_RELEVANT | Not Legal/Regulatory Relevant | S/4 HANA | EHFNDD_CCI | IS_NOT_LR_RELEVANT | Not Legal/Regulatory Relevant | Direct mapping | |
| 13 | DCT | TEXT | Property Name | S/4 HANA | EHFNDD_PHPR_NM | TEXT | Name | Direct mapping | |
| 14 | DCT | VALUE | Property Value | S/4 HANA | EHFNDD_CCA_PRPTY | VALUE | Property Value | Direct mapping | |
| 15 | DCT | UNIT | Unit of Measure | S/4 HANA | EHFNDD_CCA_PRPTY | UNIT | Unit of Measure | Direct mapping | |
| 16 | DCT | COMMENT_TEXT | Comment / Description | S/4 HANA | EHFNDD_CCA_PRPTY | COMMENT_TEXT | Comment / Description | Direct mapping | |
| 17 | DCT | TEXT | Listed Substance Name | S/4 HANA | EHFNDD_LISU_NAME | TEXT | Listed Substance Name | Direct mapping | |
| 18 | DCT | PROPORTION | Proportion | S/4 HANA | EHFNDD_CHM_COMP | PROPORTION | Proportion | Direct mapping | |
| 19 | DCT | UNIT | Unit | S/4 HANA | EHFNDD_CHM_COMP | UNIT | Unit | Direct mapping |
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 |
|---|---|---|
| 1 | Business completely fills out and signs off on the Enriched DCT. | Business |
| 2 | S2P team provides the final Vendor-to-Business Partner cross-reference mapping file. | Data Team |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Identify duplicate | Check for material ID field to check for duplicates. If found, remove the rows |
| Identify blanks | Check for material ID field to check for any blank fields. If found, remove the rows |
| Load File Record Count Verification | Compare the total number of records in the Target-Ready load file against the approved DCT to ensure no record drops occurred during transformation. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
| S2P Dependency Referential Integrity | Compare the Product ID in the load file against the S/4HANA MARA table to check for any discrepancies |
| BP Dependency Referential Integrity | Compare the mapped WASTE_PARTNER against the S/4HANA BUT000 table to ensure the Business Partner exists. |
Business
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| Validate the total count | Compare the count of materials in the load file vs MARA extract with materials containing waste in the description |
| DCT Sign-off | Business Data Owner confirms all applicable active legacy environmental materials are accounted for in the final DCT. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
| Transformation Data Verification | Business to review random sample of the transformed data file to ensure critical EHS attributes, such as Logistics Roles and Waste Codes, have been accurately mapped according to the agreed business rules. |
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- 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 | Validate S2P Material/Product Master and BP loads are 100% complete and active in target system. | Data Team |
| 2 | Execute data load | Data Team |
| 3 | Download load error logs and resolve any immediate technical failures. | 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 | Waste Codes |
| 2 | Compliance Purposes and Dangerous Goods regulations activated in target system. |
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) | |
| 1 | Product Master |
| 2 | Business Partner (Vendor) |
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 |
|---|---|---|
| Dependency Error | "Base S2P Product ID does not exist in target system" | Data Team must pause load for that record and verify Product Master status with the Supply Chain track. |
| Validation Error | "Product is not flagged as Compliance Relevant" | Data Team must request S2P to update the Product Master Basic Data view for the linked Material ID. |
| Validation Error | "Waste Code XXXXX is not recognized" | Data Team to verify with EHS Functional if configuration is missing, or send back to Business for DCT correction. |
| Dependency Error | "Waste Partner (BP) does not exist" | Verify S2P/Finance Business Partner load logs. Hold EHS record until BP is successfully loaded. |
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. |
| Table Record Count | Extract records from EHEWAD_WA_MAT and compare against the total successful records in the migration load file. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
| Linkage Validation | Extract table records and validate if S2P product link is correctly populated and verify the Compliance Purposes in EHFNDD_CHM_COMP. |
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. |
| Fiori App Verification | Log into the Fiori Launchpad. Open the Manage Material Data app. Validate that the expected volume of Waste and Emission materials appear in the active list view. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
| Fiori UI Spot Check | Open a 10% sample of materials. Navigate through the tabs to visually verify that Logistics Roles (Transport, Emission, Disposal checkboxes), Waste Codes, and Dangerous Goods compliance purposes accurately reflect the original enriched DCT. |
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.
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.