Naming convention

All single and composite roles are bound to a specific naming convention, depending on your concept requirements.

Note:
This only is useful if a codification already exists.

Warning:
Do not change the naming convention when the naming convention is in use.
The rebuild of role naming is not supported in current release.

Tip:
Remove all naming convention and apply the naming convention again after your modifications.(See also Mass Edit)

Note:
The naming convention can not be modified while roles still have the naming convention in use.
The naming convention should be removed before changing the convention.

An incorrect setup of role naming will result in an incorrect generation of tasks and derived composite roles.

Therefore, make absolutely sure that you have filled in the correct naming of roles.

The naming convention is applied to the whole concept. You can not use more than 1 naming convention in a concept!

It is possible to have roles with naming convention, as well as roles without naming convention in the same concept.

(Indicate on role-level that a specific role should not be bound to the naming convention).

Defining the naming can be done by going to the Control Panel, which is to be found under the Tools menu:

The indicators

• Logical system
• SAP module
• Domain
• Task
• Action
• Extended 1
• Extended 2

Together they are called the indicator-set.

The indicator sets

• Composite role naming
• Single role naming
• Profile naming
• Query naming

Each of these indicators has a set of properties.

The set of properties consists of

• Name: Can not be modified.
• Alias: An Alias-name can be indicated here. When there is an alias defined, it will be displayed in stead of the Name.
• Description: Allows the user to give a short description.
• Type: One can choose between 4 options:
  1. None: There is no link to other data.
  2. Fixed: When this option is selected, an extra field ‘Fixed text’ appears in which the fixed type can be filled in.
  3. Codification: There is a link to a codification workbook.
  4. Master data: When this option is selected, two extra fields appear under the heading ‘Master data settings’: the Table and its selected Field can be chosen here. This will allow the user to choose from a list when building the role name.
     
     

• Disabled: When this checkbox is checked, the indicator will not be available in the naming convention. (Note that in our example the ‘extended 1’ and ‘extended 2’ indicators are disabled).
• Optional: When this checkbox is checked, the ‘logical system-indicator’ will not be a mandatory field. (Warning: only the last indicator in an active indicator-set can be optional).
• Length: Depending on your concept’s requirements the amount of characters used can be reduced or increased. (Note that in our example the length for the ‘logical system’-indicator is 3, the ‘sap module’-indicator is 1, the ‘domain’-indicator is 4,…)
• Delimiter: If a delimiter is filled in, this character will be used as a separator/spacer between the current indicator and the next indicator of the indicator-set. (Note that using a delimiter will consume a character in the naming convention, meaning that you will have 1 character less to allocate for other indicators).

Note:
There is an indication of the number of characters used, and the number of characters still free for use at the left bottom corner.

Note:
That the positions of the indicators are mutually swappable. By changing the sequence of the indicators, the indicator-set’s sequence is altered.

Warning: Currently there is no check or engine supporting changes when roles exist in the concept. Consequences: If you modify your naming convention while roles exist, the indicator parts for roles applying naming convention will be wrong. You can deactivate naming for these roles and then reactivate; this makes sure that all indicators are stored correctly again.

This document is up to date with version 10.0.3.75 of CSI Accelerator