Calendar

• Employee (field REP)

This field is used to enter the code of a sales representative whose activity needs to be inquired.

• Start date (field DATMIN)

Start date to be stipulated before launching the search.

• End date (field DATMAX)

End date to be stipulated before launching the search.

• Appointments (field AGDBAP)

Filter on the appointments.

• Tasks (field AGDTSK)

Filter on tasks.

• Calls (field AGDCLL)

Filter on calls.

• Week (field SEMAINE)

Week number of the commercial action.

• Start date (field DATDEB)

Start date of the commercial action.

• Start time (field HEURDEB)

Start time of the commercial action.

• End date (field DATFIN)

End date of the commercial action.

• End time (field HEURFIN)

End time of the commercial action.

• Action type (field TYPACT)

Action type

• Done (field EXE)

Commercial action status.

• Subject (field OBJET)

Commercial action object.

• Category (field LIBCATEG)

Category

• Code (field KEYACT)

Sequence number of the commercial action.

• BP (field BPR)

BP code.

• Person (field CCN)

Contact number.

• Category (field SEAAPTTYP)

This field is used to filter the list of appointments by category. If a category is selected, only the appointments belonging to this category are displayed.

• Include late appointments (field SEABCS)

This field is used to isolate the appointments of the type "Absence" for the period specified in the header. When an appointment is of the type "Absence", it is always displayed in the workbench regardless of its status, "done" or "to do".

• field ITINERAIRE

• Start (field APTDAT)

• Time (field APTHOU)

• End (field APTDATEND)

• Time (field APTHOUEND)

• Week (field APTWEE)

• BPs/Contact/Object (field APTCMP)

• Location (field APTPLC)

• Appointment taken by (field APTCREUSR)

• Category (field APTTYPCLA)

• Goal of the appointment (field APTOBJ)

• Category (field SEACLLCAT)

This field is used to filter the list of calls by category. If a category is selected, only the calls belonging to this category are displayed.

• Late calls (field SEACLLDEL)

Filter on late calls.

• Additional information (field SEACLLCMG)

Filter calls associated with call campaigns.

• Priority level (field SEACLLPIO)

This field is used to filter the call list according to their priority level. This criterion can be combined with the category.

• Unplanned calls (field SEACLLNDT)

Filter on unscheduled calls.

• field CLLORIICO

• Week (field CLLWEEK)

Week number.

• Date (field CLLDAT)

Date of the call.

• Time (field CLLHOU)

Time of the call.

• Contact (relationship) (field CLLCNTNAM)

Code of the call contact.

• BP (field CLLCMPNAM)

BP code in the call header.

• Direct line (field CLLETS)

Direct line number of the contact. If this field does not make it possible to reach the contact, the user can obtain from within a single window, the list of all the telephone numbers which can potentially be used to call the contact.

• Mobile phone (field CLLMOB)

Cellphone number of the contact. If this field does not make it possible to reach the contact, the user can obtain from within a single window, the list of all the telephone numbers which can potentially be used to call the contact.

• No. of attempts (field NBRTNT)

Number of call attempts.

• Call object (field CLLOBJ)

Call object.

• Category (field CLLCATCLA)

Call category.

• Priority level (field CLLPIOCLA)

Call priority level.

• Campaign code (field CLLCMGNUM)

When the call obviously comes from a marketing campaign, the code of both the campaign and the marketing operation should be saved. These data will feed the statistics sent back by the marketing campaigns. The "Selection" context menu displays the list of all the marketing campaigns defined in the application.

• Operation code (field CLLOPGNUM)

Number of the marketing operation at the origin of the call.

• Category (field SEATSKTYP)

This field is used to filter the list of tasks by category.

If a category is selected, only the tasks belonging to this category are displayed.

• Include delays (field SEATSKRTD)

Taking into account of the task deadlines.

• Include unplanned tasks (field SEATSKNDT)

Filter on unscheduled tasks.

• Priority level (field SEATSKPIO)

This field is used to filter the task list according to their priority level. This criterion can be combined with the category.

• Include late tasks (field SEATSKDEL)

Filter on late tasks.

• Week (field TSKWEEK)

Week number.

• Due date (field TSKDUD)

Task due date.

• Start of the description (field TSKDES)

Task description

• Priority level (field TSKPIOCLA)

Task priority level.

• BP (field TSKCMPNAM)

Company name of the BP associated with the task.

• Contact (relationship) (field TSKCNTNAM)

Code of the contact associated with the task.

• Corresponding project (field TSKOPPNAM)

Code of the project associated with the task.

• Category (field TSKTYPCLA)

Task category.

• BP (field TSKCMP)

Code of the BP associated with the task.

• Category (field SEAOPPTYP)

This field is used to filter the list of projects by category.

If a category is selected, only the projects belonging to this category are displayed.

• Stage in process (field SEAOPPSTE)

This field is used to filter the list of projects according to their current stage.

This criterion can be combined with the category.

• End of absence (field NOOPPCDA)

Filter on the projects without requested closing date.

• Desired conclusion (field OPPCDA)

Closing date of the required project.

• Step (field OPPSTE)

Use this field to specify the successive steps reached by the project.
A new step can be automatically created. The creation of a pre-sales step is defined as automatic in the setup of miscellaneous table 400 - Project step, via the following information: Step type (local menu 2973).

Setup example for Table 400 - Project step:

Depending on the setup of this table, some step types can be automatically created:

• First stage of a sales cycle
  When creating a project: if there is, in the table, a step associated with step type 'First stage of a sales cycle', the first step is automatically created.
  If this step type is associated with various steps, the first step in increasing order of code is taken into account.
  If this step type is not associated with any step, the step must be entered manually, since the first step is mandatory.
  In the current example, step 'Project detected' is automatically created.
  
   
• Sending of a quote
  When creating a quote associated with the project: if there is, in the table, a step associated with step type 'Sending of a quote', the step is automatically created and the number of quotes is updated.
  If this step type is associated with various steps, the first step in increasing order of code is taken into account.
  If this step type is not associated with any step, no automatic creation is triggered.
  In the current example, step 'Quoted' is automatically created.
   In the case where an automatic creation is implemented for quotes, a quote can be created in relation to a project, even though this project has been closed. In this case, it is automatically opened again.
   
• Negotiation
  When creating a call, task or appointment: if there is, in the table, a step associated with step type 'Negotiation', the step is automatically created.
  If this step type is associated with various steps, the first step in increasing order of code is taken into account.
  If this step type is not associated with any step, no automatic creation is triggered.
  In the current example, step 'Negotiation' is automatically created.
   
• Project gained
  When creating the first order: if there is, in the table, a step associated with step type 'Project gained', the step is automatically created and the project status switches to 'Won'.
  From then on, no more pre-sales steps are automatically created. The new steps are after-sales steps for which there is no automatic creation.
  If this step type is associated with various steps, the first step in increasing order of code is taken into account.
  If this step type is not associated with any step, no automatic creation is triggered.
  In the current example, step 'Project won' is automatically created and the project status switches to 'Won'.
   In the case where an automatic creation is implemented for orders, an order can be created in relation to a project, even though this project has been closed. In this case, it is automatically opened again.
   
• No step
• Project lost
• Project abandoned
  
  These step types are not automatically created. The steps must be created manually.

Additional details about the setup of miscellaneous table 400 - Project step

• (1) Closing:
  Use this field to specify whether the project must be closed or not at this step.
  
  

• BP (field OPPCMPNAM)

Company name of the BP associated with the project.

• Amount (field OPPAMT)

Project amount.

• Currency (field CUR)

• Success probability (field OPPSUC)

Success percentage of the project.

• Number of quotes (field OPPNBQ)

This inaccessible field displays the number of quotes already generated for the project. This is loaded on the creation and the deletion of the quotes for a project.

• Project description (field OPPDES)

Project description.

• Category (field OPPTYPCLA)

Project category.

• Project chrono (field OPPNUM)

This field is by default associated to an automatic functioning sequence number counter. Consequently, the user should not normally concern him/herself with its contents.

• BP (field OPPCMP)

Code of the BP associated with the project.

• Operations (field TTROPG)

• Calls (field NBRCLL)

• Start (field OPGDATSTR)

• End (field OPGDATEND)

• Campaigns (field TTRCMG)

• Start (field CMGDATSTR)

• End (field CMGDATEND)

• No. of calls made (field RMNCLL)

• No. of calls remaining (field RMNCLLX)

• Include late campaigns (field DELAY)

• All campaigns considered (field EVRCLL)

When the field "Display the calls for all campaigns together" is not selected, a click on one of the marketing operations allows the user to obtain the list of the calls relative to this operation. These calls are also assigned to the representative and to be carried out during the period mentioned in the workbench header.

In order to link the calls and their respective operation, each selected operation carries a small arrow at the start of its title.

When the "Display the calls for all campaigns together" field is ticked, all the calls and all of the marketing operations are displayed together in the right half of this tab. Only a selection based on the period and the representative identified in the planning workbench header is carried out.

• field CLLORIICO

• Date (field DAT)

• Time (field HOU)

• Company (field CMP)

• Contact (relationship) (field CCN)

• Direct line (field ETS)

• Mobile phone (field MOB)

• No. of attempts (field TNT)

• Appointments (field INFBAP)

Information on the appointments.

• Calls (field INFCLL)

Information on calls.

• Tasks (field INFTSK)

Information on tasks.

• Projects (field INFOPP)

Information on projects.

• Contracts (field INFCON)

Information on service contracts.

• Type (field INFTYPE)

Displayed message type.

• Key (field INFKEY)

Chrono number concerned by the message.

• Message (field INFINFO)

Information message or alert.

• Late (field INFDELAY)

Information on deadlines.

• Sales rep (field INFREPNAM)

Code of the sales representative concerned by the message.