Purpose

The purpose of this document is to define the conversion approach for migrating Material Master WM Packaging fields (MARA-HUTYP and MARA-HUTYP_DFLT) from legacy SAP systems into S/4HANA.

These fields are critical for handling unit management and packaging processes in Warehouse Management (WM) and Extended Warehouse Management (EWM). Accurate migration ensures that products are assigned the correct Handling Unit Type and Default HU Type, which directly impacts packing, storage, and goods movement processes.

Conversion Scope

The scope of this document covers the approach for converting active WM Execution View from Legacy Source Systems into S/4HANA following the DD-FUN-050 Master Data Standard - WM Execution Master Data Design Standard.

Included:

• Active materials (>3 years) with packaging relevance

• Materials used in HU-managed storage types or EWM processes

• HU Type (MARA-HUTYP) and Default HU Type (MARA-HUTYP_DFLT)

Excluded:

• Materials flagged for deletion

• Obsolete, inactive, or blocked materials

• Non-HU relevant materials

Source Systems and Record Volumes

Additional Information

Multi-language Requirement

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

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.

Design Notes:

• HU Types must be configured in target system (T331).

• Fields are client-level (not plant-dependent).

• If legacy data is missing HUTYP_DFLT, business defaults will be applied.

Data Cleansing

N/A

Conversion Process

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

The high-level process is the same as defined for other material master objects:

1. Transformation (via Syniti)

   • Apply mapping rules (Legacy HU Type → Target HU Type).

   • Default missing values where necessary.

   • Validate against S/4 HU customizing.

2. Load (via SAP Migration Cockpit, Staging Tables)

   • Populate Material migration object in Migration Cockpit with HU fields.

   • Sequence: load HU customizing first, then material master with HU fields.

3. Validation

   • Pre-load: confirm HU mapping completeness.

   • Post-load: sample verification in S/4 (MM03/Display Material).

Extraction

N/A

Data Collection Template (DCT)

A Target Ready Data Collection Template will be created for WM Packaging fields to handle missing or exception values.

DCT Rules

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 Rules

Transformation Mapping

The transformation step ensures that all Handling Unit fields (MARA-HUTYP, MARA-HUTYP_DFLT) from the legacy system are properly mapped and validated against the target design in S/4HANA.

Key Considerations

1. Data Integrity Checks

   • Ensure that no material is left without a valid HU Type.

   • Validate that all new material numbers used as target keys exist in the master material mapping table before load.

Transformation Dependencies

List the steps that need to occur before transformation can commence

• HU Types must exist in S/4 (T331) before load.

• Materials must be created first (basic data) before updating HU fields.

• Conversion sequencing aligned with overall Material Master load (Basic Data → Packaging → Plant/WM data).

Pre-Load Validation

Project Team Responsibilities

• Completeness: Ensure all materials have populated HU fields before load.

• Accuracy: Cross-check HU Types against target customizing.

Business Responsibilities

• Completeness: Confirm that all business-relevant materials are included.

• Accuracy: Validate that assigned HU Types are correct and align with packaging standard

Load

Load Run Sheet

Load Phase and Dependencies

Configuration Prerequisites:

• HU Types configured in T331.

Conversion Object Dependencies:

• Predecessor: Material Master – Basic Data.

• Successor: Plant/WM views (if applicable).

Error Handling

Post-Load Validation

Project Team:

• Completeness: Compare load counts (source vs target).

• Accuracy: Run spot-checks in S/4 (MM03, Packaging tab).

Business Team:

• Completeness: Confirm all expected materials have HU data.

• Accuracy: Validate default HU Types function correctly during inbound/outbound processes.

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.

• HU Types are fully configured in target S/4 system before migration.

• Only active, HU-relevant materials are in scope.

• Syniti mappings are signed off by business before load.

• Migration Cockpit is the standard tool for loading data into S/4.

• Cutover strategy may require delta load for newly created/updated materials.

See also

Change log

Workflow history