Cross Reference Number Issues

(0) Share

Report

Posted on by Community Member

We are coming out of Microsoft Retail Management System. For those not familiar with its function, there is a section on the item detail page called allias. This I believe is the same idea as Cross Reference in NAV (correct me if I am wrong).

The problem I am seeing is that in RMS, the item lookup code had to be unique and no other item could use the same item lookup code OR alias number. In NAV it seems that I can put the same cross reference number in on as many parts as I would like and leave the "type" blank. It doesn't pop up any messages saying "this number is already associated with another sku" like RMS did. I find this some what confusing that they would not require this to be a unique number. The more I experiment with it, it looks like the first record you apply the cross reference to, is the first one returned in the sales order form.

Anyone have any experience with this. I am about to import my alias table into NAV and concerned on this functionality

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

Maneesha 5,891 on at

Like (0)

Report

Hi,

this is a global platform , according to your requirement yes you are right it should have some limitation and restrictions

but this cross reference method vary according to the company or various requirement

EG : Item A : might be having various cross reference numbers (B/C/D/E/F)

Item X : may not having any cross reference

Item Y : may having only 1cross reference

Item B : cross reference is might be Item Y

Like that it can be vary , system let you more open to u , but if you need you can do some validation according to your requirement

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you for the reply. Let me better explain

Item A

Lookup Number 5548

Item B

Lookup Number 6898 Cross Reference 5548

The cross reference 5548 should not be allowed on item B I would think. I would like to figure out a way to have NAV behave like the RMS alias field does.

Chad

Was this reply helpful? Yes No
Suggested answer

dkatson 2,263 on at

Like (0)

Report

Check this plese www.youtube.com/watch

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

Have you considered a situation that there might be cases when two completely different items would have the same barcode or manufacturing part number, occasionally assigned by two completely independent manufacturers/suppliers?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes that does happen, but in our business the cross overs are very clean. RMS had a very nice mechanism to handle this

Was this reply helpful? Yes No
Verified answer

AJAnsari 5,754 on at

Like (0)

Report

Hi Appletree,

If you are not averse to a small customization, your Partner / Developer can add a couple lines of code to the trigger that validates the value entered in the Cross Reference No. field. This code would check to see if the value entered exists in the 'Item' Table, 'No.' Field. If found, it would error out, asking the user to enter a different value. If it is not a duplicate, it would allow the user to continue to the next field/record.

Quite simple, really.

I hope this helps. If my response has answered your question, please verify by clicking "Yes" next to "Did this answer your question?"

Was this reply helpful? Yes No