Posted Purchase Invoice Loses Ship-To Name and Location Code

(0) Share

Report

Posted on by Lovisa LH

Dear Colleagues

I face the problem that when items are received and the Purchase Order is posted, the Ship-To Name and Location code that was on the PO does not appear on the Posted Purchase Invoice

Instead, our main office name as the Ship-To Name and our main warehouse Location Code.

This causes me a problem as i often need to pull out a list of orders that have been delivered directly from supplier to customer, these being Full Container Load of only one product.

I think that it should not be that way, and I suspect a previous modification has caused it but our development partner has not been able to fix it for over 8 months. So, my question is, is this normal for NAV 2018? Does the the Ship-To Name and Location Code usually appear on Posted Purchase Invoice as it was on the Purchase Order?

Thanks in advance for any help

Louise

All responses (8)

Answers (3)

Lovisa LH 29 on at

Like (0)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

Dear Zhu, thanks as always for good advice! Wish you a good day!
Lovisa LH 29 on at

Like (1)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

Thank you for renewing my hope here Inge!
Lovisa LH 29 on at

Like (0)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

Thank you for this confirmation and suggestion Daniele
Lovisa LH 29 on at

Like (0)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

Thank you for your fast response Mohana
Verified answer

YUN ZHU 82,673 Super User 2025 Season 1 on at

Like (0)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

Hi, as mentioned by several experts above, this should be due to customization.

Just adding some info.

You can download and install the same version of NAV2018 as your current version, and then test it in the Demo database (Cronus).

https://support.microsoft.com/en-us/topic/released-cumulative-updates-for-microsoft-dynamics-nav-2018-c469ba91-ee7a-ec06-e72a-6c8e331ea978

Hope this helps.

Thanks.

ZHU
Suggested answer

Inge M. Bruvik 1,025 Moderator on at

Like (0)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

The way you describe that you want the system to work is the systems default behavior. So I think you are totally correct when you suspect a customization earlier put into you system to be the root cause of the behavior you see.

Your partner should be able to debug and figure out what is causing this customized behavior.

If there is a lot of custom code in your system it might take some time to figure it out but it should definitely be possible.
Verified answer

DAnny3211 9,276 Moderator on at

Like (0)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

hi

in Dynamics NAV 2018, it is expected that the Ship-To Name and Location Code on the Purchase Order will carry over to the Posted Purchase Invoice. This functionality is essential for the accurate tracking of inventory and order fulfillment. It is possible that a customization or modification made by your development partner may have caused the issue you are experiencing.

To resolve the issue, I would recommend working with your development partner to review any customizations or modifications made to the Purchase Order and Purchase Invoice forms. They may need to update the code to ensure that the Ship-To Name and Location Code is carried over correctly from the Purchase Order to the Posted Purchase Invoice.

Additionally, you may want to review your inventory and order fulfillment processes to ensure that they are aligned with your business requirements and best practices. This can help to identify any other areas where the system may not be functioning as expected and allow for appropriate modifications or customizations to be made.

DAniele
Verified answer

Mohana Yadav 60,228 Super User 2025 Season 1 on at

Like (0)

Report

RE: Posted Purchase Invoice Loses Ship-To Name and Location Code

No, it is not normal and your development partner needs to fix it.