Problem conversion from NAV 400 to NAV 2009 SP1

RoelofRoelof Member Posts: 377
There is a problem with the conversion toolkit what comes along with NAV2009 SP1. There is a missing part handling the conversion of BOMS. I compared the conversion toolkit from 5.00 with the NAV 2009 SP1 version after I ran into problems after I ran conversion step 1 and tried to import the NAV2009 SP1 objects. The compare of the 2 toolkits showed me that the BOM conversion part was completely missing in the NAV 2009 SP1 version. I'm currently running the NAV 500 conversion toolkit step1 and see if I can overcome my problem. If that doesn't work I'm stuck unless I restore my original backup and start all over again.

Any similar problems? Please let me know.
Roelof de Jonghttp://www.wye.com

Comments

  • herrlutzherrlutz Member Posts: 58
    Maybe the bom handling is part of US localization within the upgrade toolkits. Did you make sure, that you use localized us toolkits and not W1?
  • RoelofRoelof Member Posts: 377
    Hi Herlutz,

    Not sure. The upgrade manual does not mention it. Also the quick guide doesn't mention it.
    There are however 4 objectsets in the 'Local Objects' folder that comes along with the download of NAV2009SP1:
    - Upgrade370B2009SP1.NA.1.fob
    - Upgrade370B2009SP1.NA. 2.fob
    - Upgrade400SP32009SP1.NA.1.fob
    - Upgrade400SP32009SP1.NA.2.fob

    It looks like you cannot go straight from 400 to 2009 SP1 and that you need to go first from 400 to 403. But there is no word from Microsoft mentioning that in any manual !?!
    Very confusing.

    Any advise is welcome!
    Roelof de Jonghttp://www.wye.com
  • SPost29SPost29 Member Posts: 148
    If you are mean production BOMs (Production BOM Header and Production BOM Line tables), then that is a problem.

    If you mean assembly BOMs (BOM Component table ) This is not in 2009 sp1

    It has been replaced by the kitting functionality and a new module.

    Regards
    Steve
  • yukonyukon Member Posts: 361
    Hi Roelof,

    I also have face this problem when i upgrade 3.7 to 2009.
    Steve Said
    If you mean assembly BOMs (BOM Component table ) This is not in 2009 sp1

    It has been replaced by the kitting functionality and a new module.

    How to solve your problem? Another problem is "Job Budget Line" move to where?

    Kindly, please advice to me.

    Best Regards,
    Yukon
    Make Simple & Easy
  • RoelofRoelof Member Posts: 377
    I went first from 4.00 to 5.00. That did the trick.
    There is no data conversion needed between 5.00 and Nav 2009.
    Roelof de Jonghttp://www.wye.com
  • yukonyukon Member Posts: 361
    Hi Roelof,

    When you upgrade 4.0 to 5.0. How about BOM Component and sales line BOM Item?
    4.0 sale line structure is different 5.0 sales line. We no need to do data conversion when 5.0 to 2009. But we need to do 3.7,4.0 to 2009. When i conversion i can not conversion BOM Comp: and sales line.

    Kindly, share you knowledge.

    Best Regards,
    Yukon
    Make Simple & Easy
  • RoelofRoelof Member Posts: 377
    Hi Yukon,

    You first go from 3.70 to 5.00. Not sure if you can do that in one step. Check if you need to have an additional step done from 3.70 to 4.00.
    BOM Component data will be merged into kitting and production bom tables during the conversion to 5.00.
    If the conversion step to 5.00 is done you basically bring over customizations to NAV2009 SP1, but no conversion steps needed.
    Roelof de Jonghttp://www.wye.com
Sign In or Register to comment.