Share
ReportHi,
I'm a business analyst investigating various system issues for a new client, including various issues with a relatively new NAV implementation.
I've learned about one issue with service provision and inventory management that seems strange to me. And so my question is - do all NAV implementations for service providers require this or has the developer taken the product in a non-standard direction?
My client has technicians that provide services that may include the installation of a widget out of their inventory. A widget may be charged to the customer depending on the reason why it is required. For example, the replacement of a faulty widget is free while the installation on request by the customer is charged.
Technicians write the items and the reasons onto a Work Order and data from this flows into NAV.
The NAV vendor has implemented these reasons as Variants to an Inventory Item. I understand that Variants are normally used to manage different colours of an Inventory Item (for example - like different colours of a T-Shirt item).
So instead, at the end of the month NAV showing a deduction of total items for a particular widget - the client found that NAV was representing a deduction out of each widget and reason code combination.
When this was raised with the Vendor-Developer their solution has been to develop a solution that takes the widget-variation (reason code) amounts and apply them to the more generic widget total.
So my question is - is it normal for NAV to have to be customised to use Variants in this way?
*This post is locked for comments
All responses (
Answers (
5,767
