User Experience Insights
Master Data Migration Relevancy Rules -3- Material master- FG-Finished Goods
One of the main requirements to migrate master data is to set up migration relevancy rules for each master data object. I have implemented many projects, and everyone spends a considerable amount of time on this topic in every project. I have tried to consolidate the relevancy rules object-wise so that this effort can reduce your project implementation timeline. Use this as a template and modify the rules as necessary. do share any additional relevancy rules to make this blog post better.
The below table gives possible rules for migrating active Materials.
|Data||Data Elements||Criteria to Migrate to SAP||Criteria for not migrating to SAP.|
|Finish goods status.||Status across plants. (Like Basic data status in SAP)||Active status (source system might have various statuses to identify)||Inactive status (source system might have various statuses to identify)|
|Plant Level Material Status||Active status (source system might have various plant level statuses to identify)||Inactive status (source system might have various plant level statuses to identify)|
|Sales criteria.||Sales have happened in the past N years.||No sales past N years, the FG should not be migrated; check other relevancy rules.|
|BOM as criteria.||
The material number has active
BOM/BOMs. (i.e., the material is still relevant for production, hence can be migrated). When the FG is relevant for migration, entire BOM components are relevant for migration.
|All the material number has inactive BOM status. Hence there is no manufacturing, hence not relevant for migration. check other relevancy rules.|
|Stock||Stock/Inventory exists, hence to be migrated irrespective of material status.||No stock exists, only if other relevancy rules apply, migrate, else do not migrate.|
|R&D project /NPDI||Sales order/Agreement exists; hence irrespective of other relevancy rules, we need to migrate.||Project managers decide which materials need not migrate.|
|Open item||Open vendor payments on material exists.||No pending payment|
|Consignment||Customer consignment exists with the inventory at customer.||No stock in consignment|
|Outbound delivery.||Outbound delivery exist||No outbound delivery|
|Forecast||Active Forecast on FG exists.||No active forecast exists.|
|Warranty Claim||Pending warranty claims exist.||No warranty claim exists.|
|Equipment.||If FG is associated with warranty equipment, migrate if the equipment is active and has open warranties.||Exclusion list by warranty department.|
|Production/Process orders||Material is in an open Planned/production/process order. All FGs, associated are relevant for migration.||Not in any open orders.|
|Routing||FG has active routing/ Recipe setup, hence has to be migrated.||Not part of an active Routing/Recipe.|
|Inspection plan.||FG has active Quality Inspection plan setup.||FG has no active inspection plan|
The typical process flow for migrating Active finished products is as below
|Step 1||Step 2||Step 3||Step 4||Step 5|
|Identify Active Finished goods In source system||Apply Relevancy rules for Active Finished goods as per the table above||Filter out FGs to be migrated and not to be migrated and take approval.||Check status of all sub assembly and component materials in FG BOM||Take action on inactive Assemblies/Components (Either they have to be made active or they have to be deleted/replaced in BOM)|
The typical process flow for migrating inactive finished products is as below
|Step1||Step2||Step3||Step 4||Step 5|
|Identify Inactive Finished goods In source system||Apply Relevancy rules for inactive Finished goods as per the table above||Filter out FGs to be migrated and not to be migrated and take approval||Set status of sub assembly/component material to active (case to case basis in legacy system) to ensure FG BOM can later be migrated without any issue.||Take action on inactive Assemblies/Components (Either they have to be made active or they have to be deleted/replaced in BOM)|
Do visit my other blog posts in this series
Do provide your feedback to make this blog post an universal template.