hsiao_te_wang
Well Known Member
Hi Lists,
Here is our headache at the moment.
We try to convert the data from legacy system to JDE's F3002. However, we do not know how to verify the bill of materials data we exported from legacy because:
1. Legacy builds the parent-child relationship which covers all top-down multi-level in one BOM, but not like JDE's level by level.
2. Legacy "BOM" builds only for the relationship inquiry and where-used function. It is not used to do the MRP exploration.
3. There is no routing to match the BOM in legacy system.
4. The is no BOM type logic in the legacy. However, we try to have different BOM type in JDE.
The only way I can try is to use the low level code (legacy do have) to match the LLX in F4102 to see if any discrepancy. Does anyone have the same situations and some other ideas ? Thanks !
Regards,
John Hsiao, Xe ERP8.0
Here is our headache at the moment.
We try to convert the data from legacy system to JDE's F3002. However, we do not know how to verify the bill of materials data we exported from legacy because:
1. Legacy builds the parent-child relationship which covers all top-down multi-level in one BOM, but not like JDE's level by level.
2. Legacy "BOM" builds only for the relationship inquiry and where-used function. It is not used to do the MRP exploration.
3. There is no routing to match the BOM in legacy system.
4. The is no BOM type logic in the legacy. However, we try to have different BOM type in JDE.
The only way I can try is to use the low level code (legacy do have) to match the LLX in F4102 to see if any discrepancy. Does anyone have the same situations and some other ideas ? Thanks !
Regards,
John Hsiao, Xe ERP8.0
