Data | Data Elements | Criteria to Migrate to SAP | Criteria for no migration. |
Purchased Component | 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) | |
Past usage history | Usage in last N years | No usage in the past N years | |
BOM | Part number is in BOM | Part number, not in BOM (This is applicable for direct materials) | |
SFG/FG status. | If the Parent part number is active, then purchased parts need to be migrated. | Parent part number as inactive | |
Stock | In house stock/Subcontractor stock exists, then the part has to be migrated irrespective of status. | In-house stock/Subcontractor stock doesn't exist, and part is not active then the part need not be migrated/check other rules. | |
Source List | Active source list has existed for the past X months, then such parts need to be migrated. | Not in any source list since past X months. | |
Open item, Purchase orders, Purchase Requisitions, Forecast | Open items exist | No Open items exist | |
New project | Purchase order or purchase agreement exists. | Project manager can exclude a set. | |
Open item | Account payable exist | No pending payment | |
Warranty claim | Pending Warranty claim | No warranty claim |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
2 | |
2 | |
2 |