Field help (AUSXFNC)
This field makes it possible to regroup employees into 5 different major categories : The function Sales Engineer groups together the employees who carry out a commercial activity. This activity can be exercised in either a sedentary or nomadic fashion. This employee type works to the general sales objectives. The function Telesales is the group for sales assistants and employees working in call centres. This population has objectives expressed more under the form of number of calls. This population is generally sedentary. This activity forms an accompaniment to the work carried out by sales engineers. The function Sales Manager regroups all sales management personnel. This population carries out the management of the personnel, the control of the objectives.. They also intervene in terms of operational support for the different employees that make up the sales force. The function Customer Support regroups all employees working within the after-sales service that do not have direct sales relations with the customers. NB : It is possible to declare employees that have both sales and after-sales activities. It suffices that these employees are assigned to one of the three commercial functions and to tick the box "Help-Desk employee". The function Other regroups all the employees who have no dealings with the customers. This function is assigned by default during the creation of a new employee. If a user is declared with one of the three sales functions (Sales engineer, Telesales, Sales manager) it is possible either 1 / associate an existing representative record to the current user record. 2/ start the creation of a representative record based on the user information. This association User/Representative is necessary to use the module Sales Action. In fact, this module works with the representatives file to manage the employees. Manual association of an existing representative record : It is possible that certain representative records exist before the creation of a corresponding user record. In this case, it is necessary to avoid duplicating the representative in X3. Once the field "Function" is assigned with one of the three sales values and if the field "representative code" is empty, the latter is activated in order to enter an existing representative code. In this fashion, the existence of a manually entered code neutralises the automatic creation of a new representative record. Warning: It is important to be vigilant during the creation of the User/Representative associations. This type of association cannot be modified. It is therefore necessary to delete the user record, recreate a new user record and create a new association. Automatic creation of a representative record : When a user record carries a sales function and no representative code has been entered, the system proceeds automatically to the creation of a representative record on the basis of the current user information. The code of the representative record newly created is displayed in the field "Representative code". This field is inaccessible. In effect, all User/Representative associations cannot be modified. This representative record takes by default the code of the user record. If a code conflict exists between the two files, the representative code has an incremental suffix added. For example, if a user has a code ADU and a representative record ADU already exists, the representative code associated with the user record will be ADU1. This association is in principal transparent to the user. In effect, it is possible pass from the user record to the representative record and vice versa very easily. A contextual menu planned for this effect is available on the key of each of these two objects. ("User information" or "Representative information"). The representative record makes it possible to manage important information specifically related to the conduct of a sales activity : information related to commission, Objectives, Statistics on sales activities, etc. Deletion of a user record. If a representative record has been associated manually with a user record, the deletion of the user record does not cause the deletion of the associated representative record. If a representative record has been created automatically and consecutively to the creation or duplication of a new user, the deletion of a user record causes the deletion of associated representative and business partners records. A representative record associated to a user record cannot be deleted except at the same time as the deletion of a user record. This supposes of course that the deletion is possible (no linked movements).