What's better: Enter a new item no. or use the variant code?

Rallnus

Hello,
we are discussing about the question above.

Which advantages / disadvantages did you experience for the different solutions?

Thanks, Ralph

chengalasettyvsrao

It depends on your business need. What is your requirement exactly ?

Rallnus

my main question is if the variant code can fulfill the same functions as a item can do.

I think when you start with variant code you have to:

- change your settings
- create stockkeeping units for all variants
- find a solution to handle different pictures
- make all variant fields visible in the different forms
- set some more filters if you have created some reports for figures as like inventory, sales and so on
- change a lot of keys to get a better performance
- ...

What are the advantages of the variant code?

David_Singleton

Rallnus wrote:

my main question is if the variant code can fulfill the same functions as a item can do.

I think when you start with variant code you have to:

- change your settings
- create stockkeeping units for all variants
- find a solution to handle different pictures
- make all variant fields visible in the different forms
- set some more filters if you have created some reports for figures as like inventory, sales and so on
- change a lot of keys to get a better performance
- ...

What are the advantages of the variant code?

I agree with chengalasettyvsrao, the issue here is defining the business need. Don't look at what code you need to solve the issue until you know what the issue is. What are the reasons for this particular customer to use variants and what are the reasons not to use variants. Define that and then you can start asking questions.

DenSter

In general, Variants are used for variations of the same Item. The classic example is always the clothing industry. Say you have this Star Wars T-shirt with a picture of the Death Star. Say you have this T-shirt in 4 different colors, and each color comes in 3 different sizes. Some people will argue that they are all the same shirt, other people will argue that different colors mean different shirts. For NAV it makes no difference, it's just data stored in tables.

You can make a case to have just one Item, and have a Variant for each Size/Color combination (1 item with 12 Stockkeeping Units). You can also make a case to have a separate Item for each color and have Variants for sizes (4 items with 3 Stockkeeping Units each).

Which one is chosen is up to the business. There's no 'right answer' or 'wrong answer'. Put it in test, play around with it. Find a good middle ground that makes sense to the business.

David_Singleton

DenSter wrote:

Which one is chosen is up to the business. There's no 'right answer' or 'wrong answer'. Put it in test, play around with it. Find a good middle ground that makes sense to the business.

:thumbsup: :thumbsup: :thumbsup:

ssingla

Most of the standard NAV reports and information forms (Item by Location etc.) shows information at Item level only and not on item variant level and before opting Item Variant consider this.

chengalasettyvsrao

Standard NAV Stock Keeping units does not have the Production BOM , Routing functionality.

hansika

ssingla wrote:

Most of the standard NAV reports and information forms (Item by Location etc.) shows information at Item level only and not on item variant level and before opting Item Variant consider this.

I think we can use the Variant filter option in most of the reports to know the variant wise Qty

DenSter

chengalasettyvsrao wrote:

Standard NAV Stock Keeping units does not have the Production BOM , Routing functionality.

Sure they do, it's just tied to the Item. This means that the application was designed with the concept that the manufacturing process is the same for different variants of the same item.

Means that if you need a different BOM for a different Variant, the system needs you to create a new Item.

chengalasettyvsrao

DenSter wrote:

Means that if you need a different BOM for a different Variant, the system needs you to create a new Item.

He has to consider this point also if they go for variant functionality.

Rallnus

I'll give you an example.

We are producing an item 4711 at various subsidarie.
For our customers it is the same item, the place of production doesn't matter for the customer.

The routing ist different because we've got different work groups.
If I follow your proposal I should install different items - or not?

Wouldn't I be the right way to build a relationship between stockkeeping units and routings?

(maybe BOM too...)

When we start a production order I will be depending form the stockkeeping unit, which routing will be used for the production order.

David_Singleton

Rallnus wrote:

I'll give you an example.

We are producing an item 4711 at various subsidarie.
For our customers it is the same item, the place of production doesn't matter for the customer.

The routing ist different because we've got different work groups.
If I follow your proposal I should install different items - or not?

Wouldn't I be the right way to build a relationship between stockkeeping units and routings?

(maybe BOM too...)

When we start a production order I will be depending form the stockkeeping unit, which routing will be used for the production order.

Unfortunately Navision Manufacturing does not support Variants, so you need to consider how much work it takes to add variants to manufacturing, and its a HUGE job. For that reason alone you probably need to go to individual items.

DenSter

Rallnus wrote:

Wouldn't I be the right way to build a relationship between stockkeeping units and routings?

In this particular instance, for your customer, that makes sense. In other situations it might not make sense at all. The concept in NAV is that whatever the Variant, it is still the same Item and it is still made the same way, and that's why the BOM and Routing are set up at that level.

You're not the only one who would like more flexibility in this area though, there are many companies who would want something like that, or even be able to set up multiple BOMs/Routings based on criteria that have nothing to do with Variants. You're probably aware that BOM/Routing selection has an impact throughout the entire manufacturing system, so making that change is a HUGE task.

You'll probably need to develop this yourself, or perhaps there is a 3rd party product that has this flexibility.