It has been a while so apologies for that.
Developments approved and completed last week included adding pallet summary to packing report [Nav 2009 Classic] and fix for carrying the external document number to the posted credit memo from a sales return order. [Nav 2009 RTC].
Also attended client site to discuss use of timesheets and therefore jobs. [Nav 2013r2]. The client has sent some resource and project (job) related sample data so we will configure a test company for jobs and timesheets.
Support calls last week included:
Confirming best way to amend sales order to reflect complex US sales tax based on service type. So user raising sales order does not understand US sales tax regulations by state so a finance user has to amend the SO afterwards. [Nav 2013r2].
Confirmed best way of correcting shipped resource (cannot use Undo Shipment) is by creating negative resource line on same sales order. [Nav 2013r2].
Some bug fixing re reports off packing list development. [Nav 2009 RTC].
Sent off step by step process based instructions on how to set up and use Nav consolidation. [Nav 2013r2].
Monday 25 September 2017
Monday 4 September 2017
Week ending 1/9/17
Better chargeable week last week with a Nav 2017 implementation kick off meeting, developments completed for new fields to pick lists [Nav 2009 RTC] and misc support for SEPA extracts [Nav 2016]. Also starting packing list development that was approved lasy week. [Nav 2009 RTC]. Will be completed this week.
First line support calls included development requests [Nav 2009 RTC], confirmed process for shipment error on sales order [Nav 2013r2], confirmed correction process re document number error on payment journal [Nav 2013r2], confirmed process for writing off a fixed asset in Nav [Nav 2013r2], confirmed work around for bank card creation error re To-Dos.[Nav 2013r2], fixed 2 separate Jet Reports from 2 different members of staff from the same client that were not showing Salesperson codes [Nav 2013r2].
Client requested details of the benefits from upgrading from Nav 2013 to Nav 2017 and a ball park estimate of our costs for completing a re-implementation. Re-implementation recommended by us as current config and use of Nav 2013 bad (not our issue, we took on the first line support a few years after the client went live). Send details on both on. This was all triggered by latest BREC (maintenance) invoice to the client from their MS Partner.
Client requested I demo Nav 2017 at their site and run through the changes from Nav 2013r2. Completing this this week.
Business definitely picking up with a fully chargeable week this week.
First line support calls included development requests [Nav 2009 RTC], confirmed process for shipment error on sales order [Nav 2013r2], confirmed correction process re document number error on payment journal [Nav 2013r2], confirmed process for writing off a fixed asset in Nav [Nav 2013r2], confirmed work around for bank card creation error re To-Dos.[Nav 2013r2], fixed 2 separate Jet Reports from 2 different members of staff from the same client that were not showing Salesperson codes [Nav 2013r2].
Client requested details of the benefits from upgrading from Nav 2013 to Nav 2017 and a ball park estimate of our costs for completing a re-implementation. Re-implementation recommended by us as current config and use of Nav 2013 bad (not our issue, we took on the first line support a few years after the client went live). Send details on both on. This was all triggered by latest BREC (maintenance) invoice to the client from their MS Partner.
Client requested I demo Nav 2017 at their site and run through the changes from Nav 2013r2. Completing this this week.
Business definitely picking up with a fully chargeable week this week.
Subscribe to:
Posts (Atom)
