Refer to documentation Implementation
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.
Presentation
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.
Close
Fields
The following fields are present on this tab :
Service request transaction
|   |
| This field is used to enter a title for each transaction. This title must provide a good understanding of the specific use reserved for each transaction. |
| Use this field to activate or deactivate a transaction. |
| This access code is used to restrict access to data by user or group of users. |
|   |
Close
Presentation
This tab is used to manage the presence of the different functionalities in Service request entry.
When a functionality is activated, the detail of the managed information is defined in the following tabs.
Close
Fields
The following fields are present on this tab :
Functionalities
| This option is used via a simple click to de-activate all the functionalities related to the management of the installed base for a service request. |
| This option makes it possible for a simple click to de-activate all the functionality related to the management of the components concerned in a service request. |
| This option makes it possible for a simple click to de-activate all the functionality related to the management of the skills groups in a service request. |
| This option makes it possible for a simple click to de-activate all the functionality related to the coverage of a service request. The automatic coverage controls are always executed but it is no longer possible to modify them. |
| This option makes it possible for a simple click to de-activate all the functionality related to the management of points debits in a service request. |
| This option makes it possible for a simple click to de-activate all the functionality related to the management of the consumptions on a service request. |
| This option makes it possible for a simple click to de-activate all the functionality related to the invoicing of service requests. |
| This option makes it possible for a simple click to de-activate all the functionality related to the management of the escalation in a service request. |
| This option makes it possible for a simple click to de-activate all the functionality related to the management of the timestamps in a service request. |
Fixed columns
|   |
|   |
|   |
Close
Presentation
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 :
Fields
The following fields are present on this tab :
Entry
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
Presentation
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 :
The Totals and Sub-totals fields are used to display the totals and sub-totals for the consumption lines.
Close
Fields
The following fields are present on this tab :
Entry
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
|   |
|   |
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
|   |
| This field is used to define the status of the selected information inquiry. This information can either be displayed or hidden. |
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
|   |
| This field is used to define the status of the selected information inquiry. This information can either be displayed or hidden. |
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
| This field is used to define the status of the selected information inquiry. This information can either be displayed or hidden. |
|   |
Display
| This option determines if the section on the calculation of the sub-totals for the consumptions is displayed. |
| This option determines if the section on the calculation of the total consumptions is displayed. |
Close
Presentation
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 :
Close
Fields
The following fields are present on this tab :
Entry
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
|   |
|   |
|   |
|   |
|   |
|   |
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
|   |
|   |
|   |
|   |
|   |
|   |
Close
Presentation
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.
Close
Fields
The following fields are present on this tab :
Parameters
| This parameter is used to define, for this transaction, a default transaction group code. |
| This setup is used to define for this entry transaction a movement code used to specify rules for a specific type of movements. |
| This field is used for this transaction to specify the code of the accounting automatic journal used to generate, via the stock accounting interface, the accounting entries with respect to the stock movements created with this transaction. |
Display
| This field is used to define the status of the entry of the selected information. This information can be either entered, displayed or hidden. |
|   |
|   |
|   |
|   |
Close
Presentation
In this function, the following fields cannot be accessed:
Close
Fields
The following fields are present on this tab :
Block number 1
| Parameter used to define if, for this transaction, the analytical dimensions fields of the document header must be:
|
| This setup is used to define, for this entry transaction, if the analytical distribution key at line and invoicing element level must be:
|
| Parameter used to define, for this entry transaction, if the field must be present in:
|
| Specify for this transaction if the analytical dimension fields related to stock movements must be:
|
Entry
|   |
Grid Dimension line
| You can enter an analytical dimension type code on each table line. |
| Parameter used to define, for this entry transaction, if the analytical dimension must be:
|
Close
Action icon
Click the Preload dimensions action to load the default dimensions defined for a selected group of sites or companies.
Close
Presentation
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.
It is possible to activate the display of the last record read in the customer base management function via this field.
This field is used to place the last read list in first position of the left lists.
Close
Fields
The following fields are present on this tab :
Grid Browsers
| This field is used to indicate the different additional browsers that will be added by the entry transaction . The authorized browsers are those associated with the SERREQUEST table. It must be different to SRE and SR2. |
|   |
| This field is used to define an index for the principal file for the display in the left list and in the selection windows. If this field is empty, it is the first index in the table that is used. |
| This field is used to define the direction from moving through the principal table for the display in the left list and the selection windows for the object. |
| This field is used to define the filter applied for the display of the contents of the additional browser. |
Last read
| This option is used to activate the display of the Last read browser in the service request management function. |
| This field makes it possible to place the left list 'Last read' in first position. |
Close
By default, the following reports are associated with this function :
PRTSCR : Screen print
This can be changed using a different setup.
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. |