Microsoft Dynamics NAV and item numbers

(0) Share

Report

Posted on by Community Member

I suppose Microsoft Dynamics NAV can cope with various types and lengths of item numbers?

Re. "best practises": are there any guidelines for item numbers?

The scenario is: I have the chance to set up a fully new (!) scheme of item numbers but do not know the system. Discussion goes to and fro between approaches as the following „ANTENNA-OUTDOOR-MOUNT-01/02” (directly readable) vs. numeric approach as „1-12-081501-2" (short GTIN alike).

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (4)

Verified answer

Zaid Tariq 2,274 on at

Like (1)

Report

Hi,

The recommend way is to use No. Series for more details have a look: msdn.microsoft.com/.../hh879485%28v=nav.90%29.aspx;MSPPError=-2147217396

Let me know in either case. Thanks

Was this reply helpful? Yes No
Verified answer

RobertasR 5,004 on at

Like (2)

Report

Hi, there are no strict rules, apart from the length of the field (20), so different companies use different approaches, as you said - from long 'description-type' item numbers to just numerical numbers.

Just because you'll end up typing item numbers on your documents (as opposed to 'selecting from the list') I would recommend keeping item numbers short and easy to read - for example grouping items by type, and the first letter of item number might represent the type.

Robertas

Was this reply helpful? Yes No
Verified answer

Alexander Ermakov 28,096 on at

Like (1)

Report

Usually when user creates a new item, system assigns the Item No. automatically based on the setup of the number of series or the template with a certain number of series that user might select. It is rather internal system number than a user number.

"Automatically" is a key aspect here. Each item has to have its unique Item No. in the system. Obviously, NAV will not create automatically a directly readable number. The user would need to enter that manually each time he creates a new item, which is first extra time-consuming. Then, when having a huge list of items, there is a high probability that user will face a situation that there is already such Item No. exists in the system, but for a bit different item. So you will end up in having:

ANTENNA-OUTDOOR-MOUNT-01/02

ANTENNA-OUTDOOR-MOUNT-01/02 NEW

ANTENNA-OUTDOOR-MOUNT-01/02 FINAL

ANTENNA-OUTDOOR-MOUNT-01/02 JOHN

and so on as Item Nos in the system.

I would rather keep the number of series simple and auto-incremental, perhaps dividing them for the major item groups if needed as Robertas offered, and then input correct item name in the description field.

Was this reply helpful? Yes No
Verified answer

CDsilva 4,188 on at

Like (1)

Report

Hi,

Do use No. series code

Below is the link how to create no.series code

https://community.dynamics.com/nav/w/designpatterns/74.no-series

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

I sum up what I’ve learned:

Item numbers as such:
the one and only restriction is the 20 characters field, apart from this there are no other strict rules.

Recommendations are:

[a] keep item numbers short

[b] item numbers must be „approachable“: clustered using number series (!, with 1st letter = type, e.g.)

[c] auto-incremental functionality combined with using the template is the way it all should work best

For the time being: thank you very much, this was helpful.

Was this reply helpful? Yes No