User Experience Insights
Master Data Migration Relevancy Rules -4- Material master- SFG- Semi Finished Goods
Purpose: 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 Semi Finished Materials.
|Data||Data Elements||Criteria to Migrate to SAP||Criteria for no migration|
|Semi finished goods-SFG||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)|
|Active status (source system might have various plant level statuses to identify)||Inactive status (source system might have various plant level statuses to identify)|
|Finished Goods status/Upper-level BOM material status.||All semi-finished goods would need to be migrated irrespective of status if they are part of Active Finished goods BOM. Data cleansing might be necessary to remove or replace in-active SFG from active FG BOM.||
Not a part of any active FG BOM . Here data cleansing would be necessary or this could be a case of outsourced/subcontracting SFG BOM.
If all the parent part/s are inactive, then this SFG is not relevant for migration.
|Past usage history.||Usage in last N years in manufacturing.||No usage in the past N years.|
|SFG Material BOM||BOM status is active||BOM status is inactive|
Open items, Prod
|Open items exist||No Open items exist|
Inhouse Stock exists.
Subcontractor stock exists.
Inhouse Stock = 0
Stock at subcontractor = 0
|R&D project /NPDI||Sales order/Agreement exists on FG; hence irrespective of other relevancy rules, we need to migrate.||Project managers decide which FG materials need not migrate, accordingly SFG, migration decision to be taken.|
|Open item.||Account payable exist.||No pending payment.|
|Warranty Claim on FG||Pending warranty claims exist on FG item.||No warranty claim exists on FG.|
|Production/Process orders.||SFG/FG is in open Planned/production/process orders. All FGs/SFGs, associated are relevant for migration.||FG/SFG Not in any open orders.|
|Routing||FG has active routings/ Recipe setup; hence SFG also has to be migrated.||FG is Not part of an active Routing/Recipe; hence SFG need not be migrated.|
|Forecast||Active Forecast on FG/SFG exists.||No active forecast exists.|
Semi finished goods migration has heavy dependency with its parent material and Finished goods apart from its own relevancy rules. They would require to pass through data cleansing requirements to various relations it can have with its parent/FG and its own components.
Do visit my other blog posts in this series
Do provide your feedback to make this blog post an universal template.