Skip to content

Feature - Mass Change Salesman Utility

← Systems Manager

Release date: 1/17/2017

A new Mass Change Salesman utility has been added to Global Setup, Utilities, and A/R Utilities.  This utility can assist in situations where a salesperson has left the company and their customers are reassigned to a new salesperson, a pool account, or divided up by other existing salespersons in the company.  Instead of manually updating the Salesman field in Customer File Maintenance, this utility gives you the option to create a CSV file to facilitate the changes.
 
You will create a CSV file with the layout shown on the following screen, then run Pre-Interface and Interface using the Path and Filename of the CSV file.  See sample screens below:
In addition to the Salesman in the Customer record, it can also update the following tables:
  • Ship-to Salesman: If the Ship-To has the same salesman assigned as the customer, then this utility can update the Ship-To table salesman as well.
  • Open Order Salesman: If the salesman is one of the three salesmen on a sales order, then the Order Salesman field will be changed to the new salesman.
  • Wishlist Salesman: This utility can update the Salesman field in the Wish List table, if Wish List is enabled in Global Setup.  This will allow the new salesman to follow up with the customer using the Wish List that was created under the old salesman.
  • Attribute User: If Attribute security is turned on (based on User Global Security, Allow Change/Delete Others' Attribute), then you must allow the new salesman to edit the Attributes created by the old salesman.  Attribute security is controlled by the Elliott User ID, not by the Salesman ID.  To create the proper cross-reference from Salesman to User ID, you need to update the User ID field in Salesman File Maintenance.
You can select which tables are to be updated in Global Setup, Acct, and A/R Salesman Re-Assign.  See sample screen below:


The pre-interface and interface will check the following:
  1. The customer number must be on file and the record must be available to update.
  2. The old salesman must be on file.
  3. The new salesman must be on file.
  4. The old salesman must be the current salesman in the customer record (before the change).
Sample of errors:


If the utility is configured to update the Wish List or Attributes when reassigning the salesman, the following will also be checked during the pre-interface and interface:
  1. When updating the Attribute, the User ID must be set up for both the old salesman and the new salesman in the Salesman File.
  2. When updating the Wish List, the email address must be set up for both the old salesman and the new salesman in the Salesman File.  
Sample of errors:

A report will print the status of each customer record updated, as well as report totals.

Modified programs: NSCTLUT2, SYSLMMAS (new), SYSLLMAP (new), ARSYNSLM

DLM



Feedback and Knowledge Base

(thinking…)