User Experience Insights
Master Data Migration Relevancy Rules -1- Customers
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 customers.
Migration Object | Data Elements | Criteria for Migration | Criteria for no migration |
Active customers | Sales |
All customers with sales orders in the past N years. N would be decided by the business sales team. |
Not to migrate customer codes which had no Sales since past N years. |
R & D/NPDI Projects | Active Projects | Project Manager would decide which customer project would not migrate, accordingly customer code to not to migrate would be decided. | |
Open item of customer | If Account receivable exists, such customer code has to be migrated. | No pending payment of customer exists. | |
Customer Consignment. | Customer consignment exist. | No consignment stock at customer premise. | |
Outbound delivery | Outbound delivery exist. | No outbound delivery exists. | |
Quality claim. | Pending quality claim exists. | No warranty claim exists. | |
Customer Contracts |
Active contracts exist or did not expire in the last N months. N would be decided by the Sales team |
Inactive Contracts and expired after N months | |
Credits/Debits | Credits/Debits issued in past N year. | Credits/Debits issued not in past N year. | |
Customer quotations | Active quotations or expired within past N months | Inactive quotations or expired within more than N months back | |
Returns | Open Returns in the past N months. | Open Returns were created more than N months back | |
Company assets | Company assets exists in the customer premises. | No assets exists in customer premises. | |
Assets under warranty | Customer (distributor/dealer in sap) has end customers with assets which are still in warranty. In such case even though you don’t have active transactions, you have to migrate customer codes. | No end customer exists with warranty assets. |
N months – This would differ from company to company. For “Active Customer,” the sales unit decides the number.
Do visit my other blog posts in this series
Migration of Vendor/Suppliers.
Migration of Material Master – Finished Goods.
Migration of Material Master – Semi-Finished Goods.
Migration of Material Master – Purchased Components.
Do provide your feedback to make this blog post an universal template.
I never thought of a Warranty to be a criterion for active customers. Good series once again. You wear multiple hats in the SAP space.