This function is used to manage the setup of the Service request entry screen personalization.

A standard Service request entry transaction is initialized on the installation of the software. It can be modified or deleted with the aid of this option, which can also be used to create new ones.

It is possible to set up several different transactions for the customer base. Each transaction, identified by a code and a label, appears in a selection window at the time of calling the "Service request" option.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

The entry of the setup is carried out by entering information into the header and the six tabs that concern those fields that can be set up.

Header

Transaction header

The transaction header allows the user to create new transaction codes or to look for existing transactions to be modified or deleted.

A transaction can be assigned to one or more users at the menu Profile level.

Transaction

This is the code that identifies the setup of the Service request sentry transaction.

A description is assigned to each setup transaction code. These are the two items of information that appear in the selection window proposed at the start of the Service request entry.

Access code

The transactions can be filtered according to operators, thanks to the use of an access code : if the field is entered, only the users who have this access code in their profile will be able to access the transaction.

If several transactions are set up for a function, and the user only has access to one of them because of the access codes, the selection window is no longer offered: access is by direct entry.

Active

This field is used to activate or deactivate the selected entry transaction.

Tab Parameter Definitions

This tab is used to manage the presence of the different functionalities in Service request entry.

  • Installed base
  • Component
  • Skills
  • Coverage
  • Point management
  • Consumptions  
  • Invoicing
  • Escalations
  • Timestamps

When a functionality is activated, the detail of the managed information is defined in the following tabs.

Tab Service Request

This tab is used to define the method of managing certain fields in the Service request entry screen by deciding for each of the proposed fields, whether they are :

  • Hidden: The field is not shown on the screen, but it can be initialized with default values, according to other setups that control its update.
  • Displayed: This field is displayed, but not accessible in entry mode. If the setups control the update of the field, the default value appears and it is not modifiable by the operator.
  • Entered: The field is present on the screen and is accessible in entry mode. It can be initialized with a modifiable default value.

Tab Consumptions

Entry mode

This tab is used to define the method of managing certain fields in the Service request entry screen by deciding for each of the proposed fields, whether they are :

  • Hidden: The field is not shown on the screen, but it can be initialized with default values, according to other setups that control its update.
  • Displayed: This field is displayed, but not accessible in entry mode. If the setups control the update of the field, the default value appears and it is not modifiable by the operator.
  • Entered: The field is present on the screen and is accessible in entry mode. It can be initialized with a modifiable default value.

Display

The Totals and Sub-totals fields are used to display the totals and sub-totals for the consumption lines.

Tab Invoicing

This tab is used to define the method of managing certain fields in the Service request entry screen by deciding for each of the proposed fields, whether they are :

  • Hidden: The field is not shown on the screen, but it can be initialized with default values, according to other setups that control its update.
  • Displayed: This field is displayed, but not accessible in entry mode. If the setups control the update of the field, the default value appears and it is not modifiable by the operator.
  • Entered: The field is present on the screen and is accessible in entry mode. It can be initialized with a modifiable default value.

Tab Inventory

This tab is used to enter the setups that are relative to stock management.

The service request entry transactions can manage by default a movement group (selected from amongst the values in the miscellaneous table 9 : Movement group), a stock movement code, (from amongst the values in the miscellaneous table 14 : Stock movement code) and a stock automatic journalcode.

The management of other stock information such as the warehouse site (header and lines), the stock issues, the quantity to issue or even the issued quantity can also be specified at the transaction level.

Tab Browsers

In this function, the following fields cannot be accessed:

  • Stock movement sections,
  • Line distribution.

Tab Browsers

The Browsers tab is used to define the additional left list browsers in the Service request object.
This tab is used to specify the different additional browsers that will be added by the entry transaction.
This requires the entry of the specific browsers, as well as the filter applied for the display of their contents.

Last read

Display

It is possible to activate the display of the last record read in the customer base management function via this field.

In first position

This field is used to place the last read list in first position of the left lists.

Reports

By default, the following reports are associated with this function :

  PRTSCR : Screen print

This can be changed using a different setup.

Validation

At the end of the entry, the [Validation] button makes it possible to save the performed setup and trigger the generation of the corresponding screens.

Copy

This button allows the user to copy the transaction to another folder.

It is possible to copy the selected transaction to a group of folders in a single environment, the field All folders is provided for this.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation