Skip to content

Feature - Determine Salesman By Division

Release Date 9/12/21

Version: 8.5 and Above

The purpose of this feature is to allow defining salesman by division which is on the item by item basis. In customer or ship-to file maintenance, user can only define one salesman per order. However, if the salesman should be different based on the type of products sold to the customer, system previously does not have the ability to handle this.

To support such feature, systems now allow for a new attribute to be set up to determine the division an item belongs to and then assign the associated salesman to the order when adding the order. There are two things to consider with with feature:
  1. When entering the sales order header, the salesman is already determined based upon the salesman entered in the Customer file or the Ship-To file. At the initial time of order entry, the line item is not entered yet so a division cannot be determined.
  2. An order could have mixed line items from multiple divisions and should be split between multiple salesmen.

Global Setup Option

A new Global Setup option has been added to COP-Func-> Order Header Screen to support this feature. 


42. Determine Order Salesman By Division - The default is N. If set to Y, Order Entry Add mode will assign the salesman number based upon division.

Assign Division Salesman to Customer & Ship-To

For example, let’s say we have customer# ABC001. It is currently assigned with Salesman LM1 which is a salesman of division "L." The same customer ABC001 may also buy division "D" items. In that case, the salesman should be DT1. To solve this issue, Order Entry now looks for the attribute code DIVISION-XXX where XXX is the 3-digit division code representing the division. In this case, "LAP"  will represent "L." "DTA" will represent division "D." So two new attribute codes will be created to support this feature, DIVISION-LAP and DIVISION-DTA. The first reference field of the DIVISION-XXX will be used to store the salesman ID. Therefore, the two attribute codes for customer ABC001 will be defined as follows:

  •                 DIVISION-LAP
  •                 Reference 1 (Salesman): LM1
  •                  DIVISION-DTA
  •                 Reference 1 (Salesman): DT1


Since the salesman in customer# ABC001 is defined as LM1, the attribute DIVISION-LAP does not need to be associated with the customer or the ship-to record.

Assign Division Code to Product Category

To solve scenario one, we also need to identify by product category which division it belongs to. For example, for a product category that belongs to "D" division, you will add the attribute DIVISION-DTA to that product category. There’s no need to add the salesman to the Reference 1 field. There should be only one DIVISION-XXX attribute assigned to the same product category. If you add multiple attributes to the same product category, the application will not be able to determine the appropriate division.

Override Salesman on Order Header Upon Finishing Order

When first entering the order for customer number ABC001, since the salesman for the customer is LM1 (division "L" salesman), the order’s salesman is initially salesman LM1. After the user finishes the line item screen, upon returning to the order header screen the system can evaluate the line items and their associated product categories. Based on the product category, the application will determine the division code of each line item. The following are various scenarios:

1. If there are multiple divisions for the line items, this is a confusing situation. The system will display a warning message to indicate such a condition.



2. If there are no divisions for any of the line items, the system will not complain. The order header’s salesman will not be changed.

3. If line item consists of the same division (including some line items that do not have divisions), then the application needs to determine if the system should override the order header’s salesman.

In the case of scenario 3, we will look up the corresponding division attribute from the ship-to, and if not found then the customer.

A. The corresponding ship-to or customer DIVISION-XXX attribute may not exist. Then the order header salesman will not be overridden.

B. If the corresponding ship-to or customer DIVISION-XXX attribute is found, and salesman-ID is defined in the attribute, then we will compare that salesman-ID with the order header salesman-ID. If they are the same, nothing happens. If they are different, there are two possibilities:

--The DIVISION-XXX attribute salesman ID is invalid. Display a message to indicate so. The order header’s salesman will not be overridden.



-- The DIVISION-XXX attribute salesman ID is valid. The application will override the order header’s salesman ID from the attribute and display a message to indicate so.

 


Override Salesman During Sales Desk Entry

The override of the salesman in Sales Desk will occur on the quote screen before the sales order is generated. The override will occur if the item division salesman differs from the customer or ship-to salesman. If there are multiple item divisions detected, the application will not override the salesman but will notify the user that the salesman assignment should be reviewed on the order. 

This feature is not applicable to other areas, including, but not limited to:

  • Order Entry Change Mode (adding new line items to an existing order will not cause salesman ID in the header be re-assigned)
  • Sales Order Import
  • Web Services
  • Copy Order
  • Consolidate Order
  • Fill Backorder (Fill Backorder by Customer can optionally create new order)
Programs Modified: NSCTLFIL.FD, NSCTLFIL.W37, NSCTLINI, NSCTLMN5, CP0101, CP0111, QUOTLINK.WS, CPSLSDSK, CPQUOSCN, CPQUOGEN
CLS

Feedback and Knowledge Base