| Status | |
|---|---|
| Owner | |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Purpose
The purpose of this conversion is to migrate and create Extended Warehouse Management (EWM) Product Master data in the S/4HANA EWM environment.
The EWM Product Master is an extension of the Material Master, providing warehouse-specific attributes that enable and control warehouse functionality and processes such as putaway, stock removal, replenishment, and physical inventory.
This conversion ensures that each product (material) within the warehouse has a corresponding EWM product master record, containing all relevant attributes aligned with the warehouse organization structure.
MDS DD-FUN-050 Master Data Standard_1060-EWM Product Master - Google Sheets
Conversion Scope
The scope of this conversion includes the creation of EWM Product Master data in S/4HANA, derived from existing Material Master and WM-related configuration and data in the legacy ECC system.
Because legacy EWM Product Master data does not exist, the conversion is not a one-to-one migration but rather a data derivation and enrichment process. The data will be constructed based on material master attributes and warehouse-specific logic defined during EWM design.
In Scope
Creation of EWM Product Master records for all materials that are in scope for warehouse operations in S/4HANA.
Population of key EWM product attributes including:
Warehouse Number
Putaway and Stock Removal Control Indicators
Storage Type Indicators
Handling Unit Type Assignments (where relevant)
Consolidation Group and Availability Group
Packaging Data and Unit of Measure Information
Product Grouping for Replenishment or Slotting (if applicable)
Alignment of EWM Product Master data with S/4HANA Material Master and EWM design configurations.
Upload of EWM Product Master data via standard EWM transaction
/SCWM/MIG_PRODUCT
Out of Scope
Non-warehouse relevant materials.
Additional Information
Multi-language Requirement
N/A
Document Management
N/A
Legal Requirement
N/A
Special Requirements
N/A
Target Design
The technical design of the target for this conversion approach.
| Index | Technical Table-Field | Field Label | Description | Field Format | Allowed Values / Reference | Conditional Logic | Multi-language Field Requirements | Comments / Special Handling Notes | Requirement (R/O/C/S/NU) | Data Type & Length |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | /SAPAPO/MATLWH-MATID | Product ID | Product identifier within EWM | CHAR(22) | None | None | None | Derived from MARA-MATNR | R | Data type : CHAR Length : 22 |
| 2 | /SAPAPO/MATLWH-ENTITLED_ID | Party Entitled to Dispose | Party responsible for stock ownership | RAW(16) | None | None | None | Linked to business partner data | R | Data type : RAW Length : 16 |
| 4 | /SAPAPO/MATLWH-PTDETIND | Process Type Determination Indicator | Controls process type determination for product | CHAR(2) | /SCWM/TPTDETIND-PTDETIND | None | None | Drives task creation behavior | C | Data type : CHAR Length : 2 |
| 5 | /SAPAPO/MATLWH-CCIND | Cycle Counting Indicator | Defines product classification for inventory counting | CHAR(1) | MARC-ABCIN | None | None | Maps ABC indicator to EWM | C | Data type : CHAR Length : 1 |
| 6 | /SAPAPO/MATLWH-PUT_STRA | Putaway Control Indicator | Controls product putaway strategy | CHAR(4) | /SCWM/T305Q-PUT_STRA | None | None | Required for inbound processing | R | Data type : CHAR Length : 4 |
| 7 | /SAPAPO/MATLWH-LGBKZ | Storage Section Indicator | Defines section search strategy | CHAR(4) | /SCWM/T304-LGBKZ | None | None | Used for bin search logic | C | Data type : CHAR Length : 4 |
| 8 | /SAPAPO/MATLWH-LPTYP | Storage Bin Type | Defines type/classification of storage bin | CHAR(4) | /SCWM/T303-LPTYP | None | None | Impacts putaway and removal rules | C | Data type : CHAR Length : 4 |
| 9 | /SAPAPO/MATLWH-BLOCK | Bulk Storage Indicator | Controls bulk storage putaway | CHAR(2) | /SCWM/T338-BLOCK | None | None | Used for bulk materials | C | Data type : CHAR Length : 2 |
| 10 | /SAPAPO/MATLWH-REM_STRA | Stock Removal Control | Controls stock removal strategy | CHAR(4) | /SCWM/T305R-REM_STRA | None | None | Required for picking logic | R | Data type : CHAR Length : 4 |
| 11 | /SAPAPO/MATLWH-STCKDETGR | Stock Determination Group | Determines stock group for picking | CHAR(2) | /SCWM/V_STCKDTGR-STCKDETGR | None | None | Used for batch-managed materials | C | Data type : CHAR Length : 2 |
| 12 | /SAPAPO/MATLWH-DRDETGR | Staging Area Determination Group | Defines staging area determination | CHAR(4) | /SCWM/TDRDETGR-DRDETGR | None | None | Used for outbound staging | C | Data type : CHAR Length : 4 |
| 13 | /SAPAPO/MATLWHST-LGTYTP | Storage Type | Storage space within warehouse | CHAR(4) | /SCWM/T331-LGTYP | None | None | Level-specific configuration | C | Data type : CHAR Length : 4 |
| 14 | /SAPAPO/MATLWHST-SECTIND | Section Indicator | Section indicator at storage type level | CHAR(4) | /SCWM/T304-LGBKZ | None | None | Used for fine-tuning putaway | C | Data type : CHAR Length : 4 |
| 15 | /SAPAPO/MATLWHST-BINTYPE | Bin Type | Bin type assignment for product | CHAR(4) | /SCWM/T303-LPTYP | None | None | Impacts replenishment logic | C | Data type : CHAR Length : 4 |
| 16 | /SAPAPO/MATLWHST-REPQTY_DSP | Minimum Replenishment Qty | Minimum quantity for replenishment trigger | QUAN(15) | None | None | None | Maintained based on planning data | C | Data type : QUAN Length : 15 |
| 17 | /SAPAPO/MATLWHST-REPQTY_UOM_DSP | Display UoM for Replenishment Qty | Unit of measure for replenishment quantity | UNIT(3) | MEINS | None | None | UoM from material master | C | Data type : UNIT Length : 3 |
| 18 | /SAPAPO/MATLWHST-MINQTY_DSP | Minimum Qty | Minimum stock level in storage type | QUAN(15) | None | None | None | Used for replenishment logic | C | Data type : QUAN Length : 15 |
| 19 | /SAPAPO/MATLWHST-MINQTY_UOM_DSP | Display UoM for Minimum Qty | UoM for minimum stock | UNIT(3) | MEINS | None | None | Derived from base UoM | C | Data type : UNIT Length : 3 |
| 20 | /SAPAPO/MATLWHST-MAXQTY_DSP | Maximum Qty | Maximum allowed stock in storage type | QUAN(15) | None | None | None | Used for replenishment ceiling | C | Data type : QUAN Length : 15 |
| 21 | /SAPAPO/MATLWHST-MAXQTY_UOM_DSP | Display UoM for Maximum Qty | UoM for maximum stock | UNIT(3) | MEINS | None | None | Derived from base UoM | C | Data type : UNIT Length : 3 |
| 22 | /SAPAPO/MATLWHST-QUANCLA | Quantity Classification | Classification for stock quantity | CHAR(1) | /SCWM/TQUANCLA-QUANCLA | None | None | Used for volume optimization | C | Data type : CHAR Length : 1 |
| 23 | /SAPAPO/MATLWHST-QUANCLAPUT | Quantity Classification (Putaway) | Classification for putaway quantity | CHAR(1) | /SCWM/TQUANCLA-QUANCLA | None | None | Impacts putaway bin search | C | Data type : CHAR Length : 1 |
Data Cleansing
The EWM Product Master data is being newly created as part of the S/4HANA EWM deployment. Since the legacy system (WM) does not contain equivalent warehouse-level product data, there is no direct source data to cleanse.
Conversion Process
The high-level process is represented by the diagram below:
The EWM Product Master will be created through a Data Collection Template (DCT)–based approach. Since no equivalent data exists in the legacy WM system, all records will be newly derived using material master data, EWM configuration, and approved mapping logic.
Process Steps
Data Collection (DCT Preparation)
Populate the DCT with all fields defined in the target design.
Each record represents a combination of Product, Warehouse, and Party Entitled to Dispose.
Transformation & Value Mapping
Apply transformation logic to derive warehouse-specific attributes
Load to Target System
Load the validated DCT using standard transaction
/SCWM/MIG_PRODUCT.The load will create EWM product master records for each product–warehouse–party combination.
Post-load validation will be performed using transaction
/SCWM/MAT1to confirm completeness and accuracy.
Data Privacy and Sensitivity
N/AExtraction
N/A
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.
The Data Collection Template (DCT) for the Product Master conversion applies to the standard migration object MIG-PRODUCT.
This object supports the upload of product master data into SAP EWM through the standard load process.
The MIG-PRODUCT DCT contains all fields required by the standard transaction. While the full set of columns must be maintained in the file for technical compatibility, only the fields identified in the target design are required to be populated with business data.
The table below maps these mandatory target design fields to their respective DCT column identifiers and provides the corresponding technical field descriptions. All other columns within the DCT are considered optional or out of scope and should remain blank unless explicitly required for load completeness or validation.
DCT Load File : DCT Product Master.csv
| Column | DCT Field Name | Field Description | Target Design Field | Mandatory (Y/N) |
|---|---|---|---|---|
| A | EWM_LGNUM | Warehouse number | Warehouse number | Y |
| B | EWM_PRODNO | Product number | Product ID | Y |
| C | EWM_ENTITLED | Party entitled to dispose | Party Entitled to Dispose | Y |
| D | PROCPRFL | - | - | N |
| E | PTDETIND | Process type determination indicator | Process Type Determination Indicator | Y |
| F | WRKLDGR | — | — | N |
| G | DRDETGR | Staging area determination group | Staging Area Determination Group | Y |
| H | VASVCP | — | — | N |
| I | SLRQ_MIN | — | — | N |
| J | PUT_STRA | Put away control indicator | Putaway Control Indicator | Y |
| K | PUT_STRA_FIX | — | — | N |
| L | PUT_STRA_PLAN | — | — | N |
| M | LGBKZ | Storage section indicator | Storage section indicator | Y |
| N | LPTYP | Storage Bin Type | Storage Type | Y |
| O | BLOCK | — | — | N |
| P | REM_STRA | Stock removal control indicator | Stock Removal Control | Y |
| Q | REM_STRA_FIX | — | — | N |
| R | REM_STRA_PLAN | — | — | N |
| S | STCKDETGR | Stock determination group | Stock Determination Group | Y |
| T | L2SKR | — | — | N |
| U | DEMQTY | — | — | N |
| V | DEMQTY_FIX | — | — | N |
| W | NOSOI | — | — | N |
| X | NOSOI_FIX | — | — | N |
| Y | RSQTY | — | — | N |
| Z | RSQTY_FIX | — | — | N |
| AA | DEMTYP | — | — | N |
| AB | CONCSTAT | — | — | N |
| AC | LASTSLOT | — | — | N |
| AD | WGHTIND | — | — | N |
| AE | WGHTIND_FIX | — | — | N |
| AF | VOLIND | — | — | N |
| AG | VOLIND_FIX | — | — | N |
| AH | LGTHIND | — | — | N |
| AI | LGTHIND_FIX | — | — | N |
| AJ | WDTHIND | — | — | N |
| AK | WDTHIND_FIX | — | — | N |
| AL | HGHTIND | — | — | N |
| AM | HGHTIND_FIX | — | — | N |
| AN | CCIND | Cycle counting indicator | Cycle Counting Indicator | Y |
| AO | CCIND_FIX | — | — | N |
| AP | DOCBATCH | — | — | N |
| AQ | BACKFLUSH_PROD | — | — | N |
| AR | KIT_FIXED_QUAN | — | — | N |
| AS | MEDI_APROF_WH | — | — | N |
| AT | QUANCLA_MERCH | — | — | N |
| AU | PUOM_WH | — | — | N |
| AV | KZZUL | — | — | N |
| AW | RATIODIM | — | — | N |
| AX | QGRP_WH | — | — | N |
| AY | EWM_LGTYP | Storage type | Storage Type | Y |
| AZ | FIXBIN | — | — | N |
| BA | SECTIND | Storage section indicator | Storage Section Indicator | Y |
| BB | SECTIND_FIX | — | — | N |
| BC | SECTIND_PLAN | Section indicator (planned) | Section Indicator | Y |
| BD | BINTYPE | Bin type | Bin Type | Y |
| BE | BINTYPE_FIX | — | — | N |
| BF | BINTYPE_PLAN | Bin type (planned) | Bin Type | Y |
| BG | MAXFIXBIN | — | — | N |
| BH | MAXFIXBIN_FIX | — | — | N |
| BI | MAXFIXBIN_PLAN | — | — | N |
| BJ | MAXQTY | Maximum quantity | Maximum Qty | Y |
| BK | MAXQTY_PLAN | — | — | N |
| BL | MAXQTY_UOM_DSP | Display UoM for maximum quantity | Display Unit of Measure for Maximum Qty | Y |
| BM | MINQTY | Minimum replenishment quantity | Minimum Replenishment Qty | Y |
| BN | MINQTY_PLAN | Minimum quantity | Minimum Qty | Y |
| BO | MINQTY_UOM_DSP | Display UoM for minimum quantity | Display Unit of Measure for Minimum Qty | Y |
| BP | REPQTY | Replenishment quantity | Minimum Replenishment Qty | Y |
| BQ | REPQTY_PLAN | — | — | N |
| BR | REPQTY_UOM_DSP | Display UoM for replenishment quantity | Display Unit of Measure for Replenishment Qty | Y |
| BS | RMMQTY_FIX | — | — | N |
| BT | PERMXQTY | — | — | N |
| BU | SPLITTH | — | — | N |
| BV | SPLITPUT | — | — | N |
| BW | NORPLN | — | — | N |
| BX | BINSRCH | — | — | N |
| BY | QUANCLA | Quantity classification | Quantity Classification | Y |
| BZ | QUANCLAPUT | Quantity classification for putaway | Quantity Classification for Putaway | Y |
| CA | SEQPUT | — | — | N |
| CB | SEQPUT_FIX | — | — | N |
| CC | SEQPUT_PLAN | — | — | N |
| CD | SKIPPTW | — | — | N |
| CE | SKIPPTW_FIX | — | — | N |
| CF | SKIPPTW_PLAN | — | — | N |
Extraction Dependencies
N/A
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
All EWM Product Master fields are directly mapped from the Data Collection Template (DCT) to the target EWM tables.
No transformation, enrichment, or lookup logic is applied.
Each field below is a direct copy from the corresponding column in the DCT.
Transformation Rules
| Source (DCT Field) | Target Field (Technical Name) | Field Label / Description | Transformation Logic |
|---|---|---|---|
| EWM_PRODNO | /SAPAPO/MATLWH-MATID | Product ID | Copy |
| EWM_ENTITLED | /SAPAPO/MATLWH-ENTITLED_ID | Party Entitled to Dispose | Copy |
| WRKLDGR | /SAPAPO/MATLWH-SCUGUID | Supply Chain Unit | Copy |
| PTDETIND | /SAPAPO/MATLWH-PTDETIND | Process Type Determination Indicator | N/A |
| CCIND | /SAPAPO/MATLWH-CCIND | Cycle Counting Indicator | Copy |
| PUT_STRA | /SAPAPO/MATLWH-PUT_STRA | Putaway Control Indicator | Copy |
| LGBKZ | /SAPAPO/MATLWH-LGBKZ | Storage Section Indicator | Copy |
| LPTYP | /SAPAPO/MATLWH-LPTYP | Storage Bin Type | Copy |
| BLOCK | /SAPAPO/MATLWH-BLOCK | Bulk Storage Indicator | Copy |
| REM_STRA | /SAPAPO/MATLWH-REM_STRA | Stock Removal Control | Copy |
| STCKDETGR | /SAPAPO/MATLWH-STCKDETGR | Stock Determination Group | Copy |
| DRDETGR | /SAPAPO/MATLWH-DRDETGR | Staging Area Determination Group | Copy |
| EWM_LGTYP | /SAPAPO/MATLWHST-LGTYTP | Storage Type | Copy |
| SECTIND | /SAPAPO/MATLWHST-SECTIND | Section Indicator | Copy |
| BINTYPE | /SAPAPO/MATLWHST-BINTYPE | Bin Type | Copy |
| REPQTY | /SAPAPO/MATLWHST-REPQTY_DSP | Minimum Replenishment Quantity | Copy |
| REPQTY_UOM_DSP | /SAPAPO/MATLWHST-REPQTY_UOM_DSP | Display Unit of Measure for Replenishment Qty | Copy |
| MINQTY | /SAPAPO/MATLWHST-MINQTY_DSP | Minimum Quantity | Copy |
| MINQTY_UOM_DSP | /SAPAPO/MATLWHST-MINQTY_UOM_DSP | Display Unit of Measure for Minimum Qty | Copy |
| MAXQTY | /SAPAPO/MATLWHST-MAXQTY_DSP | Maximum Quantity | Copy |
| MAXQTY_UOM_DSP | /SAPAPO/MATLWHST-MAXQTY_UOM_DSP | Display Unit of Measure for Maximum Qty | Copy |
| QUANCLA | /SAPAPO/MATLWHST-QUANCLA | Quantity Classification | Copy |
| QUANCLAPUT | /SAPAPO/MATLWHST-QUANCLAPUT | Quantity Classification for Putaway | Copy |
Transformation Dependencies
List the steps that need to occur before transformation can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Capture the data for packaging specifications in DCT. Review and correct any errors if bulk uploading data via downloaded excel DCT template. | Business team |
| 2 | Ensure the mapping tables which are needed during transformation have been reviewed and signed off by business. | Business team, Data Team (SCM) |
| 3 | Obtain DCT Sign-off from Business | Data Team (SCM) |
| 4 | Generate Pre-Load reports | Data Team (Syniti) |
| 5 | Review and Validate Error and Preload Reports | Data Team (SCM) |
| 6 | Log errors as defects, if any and address resolutions. | Data Team (SCM) |
| 7 | Re-transform and re-validate the Pre-load reports if necessary. | Data Team (SCM), Data Team (Syniti) |
| 8 | Obtain preload validation sign-off from Business | Business + Functional (SCM) + Data Team (SCM) |
| 9 | Generate Load Files | Data Team (Syniti) |
Pre-Load Validation
Project Team
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| Check Values | Validate the pre-load data confirming the values are aligned with target system format |
| Validate template structure and required field population | Ensure mandatory fields are filled |
| Verify Record Count | SCM 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 | SCM Data Team to verify that all fields below meet pass the checks:
|
| Perform format validation (date, currency, decimal separators) | Standardize format to match SAP accepted input (e.g., YYYYMMDD for dates), cubic volume, weight etc |
| 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. |
| Conduct dry runs using LTMC or BAPIs and review logs | Analyze load results and correct format or conversion errors |
Business
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| Verify Record Count | 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 validation file. |
Accuracy
| Task | Action |
|---|---|
| Conversion Accuracy | Business Data Owner/s to verify that all the data in the preload validation file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data). Review error reports in tool for any mismatch or missing transformed values. |
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
| Step | Activity | Responsible Team |
|---|---|---|
| 1 | Ensure the load tools (e.g., conversion templates, migration objects) are transported into the correct system/instance. | Data Team (SCM) |
| 2 | Ensure Pre-load sign-offs are obtained from relevant stakeholders. | Data Team (SCM) |
| 3 | Execute upload of the DCT directly using standard transaction /SCWM/MIG_Product | Data Team (SCM) |
| 4 | Validate a few records by accessing standard S/4HANA transactions to ensure data accuracy. | Data Team (SCM) |
| 5 | Generate post-load reports from the tool to confirm successful uploads. | Data Team (SCM), Data Team (Syniti) |
| 6 | Log any errors as defects; address and resolve issues. Close defects after resolution. | Data Team (SCM) |
| 7 | If defects were corrected, re-upload the affected data and regenerate post-load reports as required. | Data Team (SCM), Data Team (Syniti) |
| 8 | Business team to validate post-load files, raise data defects if any, or provide post-load sign-off. | Business Team |
| 9 | Repeat post-load report generation and defect resolution (Steps 5–7) if necessary. | Data Team (SCM), Data Team (Syniti) |
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
Conversion Objects
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 | Description | Probable Cause | Suggested Resolution |
|---|---|---|---|
| Configuration Error | Invalid or missing EWM configuration required for product master upload | Required configuration (e.g., Supply Chain Unit, Storage Type, Bin Type, Stock Determination Groups) missing or inactive in target system | Ensure all prerequisite configuration exists and is active in the target system |
| Formatting Error | Key fields such as Product ID, Party Entitled to Dispose, Supply Chain Unit incorrectly formatted | Data in DCT does not match SAP field specifications (length, numeric vs. alphanumeric, UoM mismatch) | Correct DCT formatting; verify units of measure, numeric fields, and field lengths against SAP master data |
| Authorization Error | Lack of access to execute MIG-PRODUCT load or modify product master | Executing user lacks roles/authorizations in target client | Assign required SAP roles to executing user; validate access in target client |
| Transformation Miss | Mandatory transformation logic not applied before load | Any required transformation missing (though for Product Master, mostly direct copy) | Ensure all mandatory fields per target design are populated correctly; verify DCT field-to-field mapping |
| Technical Load Failure | DCT file not processed due to syntax error or system issue | System downtime, incorrect file encoding, missing headers, or temporary SAP error | Verify DCT integrity (CSV or Excel format), correct syntax issues, and re-execute upload; check logs of MIG-PRODUCT execution |
| Data Inconsistency | Missing or invalid references in the DCT | Product IDs, PACI, Storage Types, SRCI etc., do not exist in target EWM/S/4HANA | Validate that all master data exists in target system; correct DCT references |
| Duplicate Entry | Product ID already exists in target system | Same product uploaded previously or duplicate records in DCT | Remove duplicates from DCT or adjust product entries before re-upload |
| Missing Mandatory Field | Required DCT field not populated | Mandatory fields such as Product ID, Party Entitled to Dispose, Supply Chain Unit, Putaway Control Indicator, Min/Max/Rep Qty, Quantity Classification are blank | Populate all mandatory fields per mapping table; validate before upload |
| Unit / Quantity Errors | Min/Max quantities, replenishment qty, or unit of measure inconsistent | Incorrect numeric values, inconsistent quantity/UoM, or invalid classification | Verify all quantity fields, units of measure, and classification codes; ensure consistency with target system |
Post-Load Validation
Project Team
The following post-load validations will be performed by the Project Team.Completeness
| Run Fiori app/tcode to check loaded data in SAP | Run /scwm/mat1 transaction to check if data has been loaded |
| Compare uploaded data against source file values | Use Custom reconciliation tools e.g. SQL Server or Excel based comparison tools to validate the number of records loaded against the load file record volume |
Accuracy
| Task | Action |
|---|---|
| Compare uploaded data against source file values | Use automated postload validation report or standard reports from S/4 HANA to validate field by field value match across all loaded records |
Business
The following post-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| Verify Count | Download Postload validation reports from Syniti and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file |
| Review loaded Transportation lanes | Access the S/4HANA system to view loaded packaging specification |
Accuracy
| Task | Action |
|---|---|
| Compare Against Approved Load File | Cross-check data in S/4HANA against the final business-approved load file used for migration |
| Validate Accuracy of Converted/Transformed Data | Review any transformed fields (e.g., business partner number) for correctness |
| Log and Report Discrepancies | Use provided discrepancy log format or defect management tool to report any findings |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- EWM Product Master is in scope based on data design and any exception requested by business.
- Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.
- The list of validation checks in transformation section is not exhaustive and may change over time as the design and configuration of the system evolves.
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.