Conversion from 2.60 to 5.0 regarding BOMs' and Kitting.

Roelof

Hi,

I currently converted a 2.60 database to 5.0. The 2.60 version was using BOM's. I thought that 2.60 BOM's are now integrated in the 5.00 Kitting. I couldn't find any data there. Is there something going on with the conversion or do I miss something?

Any help is welcome.

Thanks.

DenSter

The 2.6 "Bill of Materials" were in a table called BOM Component. The 5.0 ones are in the actual Production BOM tables, with a new type.

You can choose to convert your master data to the new tables and use "kitting", or you can choose to keep it as is. I believe that the 'old' way still works. You might have to re-enable some functionality, you should be able to easily find the differences by comparing the US database with W1.

Roelof

Hi Daniel,

Thanks for the reply.
I have 2 questions then:
- 'You can choose to convert your master data to the new tables and use "kitting": so, you mean there is a setting in the conversion toolkit?
- 'or you can choose to keep it as is. I believe that the 'old' way still works. You might have to re-enable some functionality': what do I need change so that it works?

Thanks.

DenSter

I don't know if there is a setting in the toolkit. I'm just saying that you have the choice to either convert to the new kitting or keep the functionality as it is in your current system. You would just approach it as custom functionality. How to do it is a different question.

Compare a blank W1 database with a blank US database, and you'll find where the differences are. It shouldn't be too hard to find where the assembly list functionality is.

ara3n

Roelof wrote:

Hi Daniel,

Thanks for the reply.
I have 2 questions then:
- 'You can choose to convert your master data to the new tables and use "kitting": so, you mean there is a setting in the conversion toolkit?
- 'or you can choose to keep it as is. I believe that the 'old' way still works. You might have to re-enable some functionality': what do I need change so that it works?

Thanks.

There is no toolkit for conversion from bom to kitting. You've to write a report.

The two features work independently. They both work out of the box. You can use both, or one.
It makes sense to use one.

Roelof

Hi Rashed,

You mean I need to write a report to convert the BOM Component table data into the Production BOM Header and Line tables? And what about the other related tables, such as the 'Where Used Line' table?
I'm confused.

Roelof

Daniel,

It's weird that Microsoft doesn't come up with any documentation about this issue. It's frustrating because it means additional work. The customer will not be so happy about it.

ara3n

Roelof wrote:

Hi Rashed,

You mean I need to write a report to convert the BOM Component table data into the Production BOM Header and Line tables? And what about the other related tables, such as the 'Where Used Line' table?
I'm confused.

Production bom has its own where used. BTW where used is runtime calculated. There is no data to transfer. It's an hour report to write to transfer the data.

Compared to the whole upgrade that's peanuts.

DenSter

Roelof wrote:

Daniel,

It's weird that Microsoft doesn't come up with any documentation about this issue. It's frustrating because it means additional work. The customer will not be so happy about it.

Yes that is frustrating. The most frustrating part is that they seem to look at kitting as 'new functionality' not as 'something that replaces BOM Components'. But then again it's weird why the old BOM Components are no longer part of the US database.