Ansicht
Dokumentation
GRACVC_NAMECONV - Specify Naming Conventions
General Data in Customer Master rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
In this Customizing activity, you can maintain the naming rules for creating new roles.
To create a aming convention:
- Choose New Entries.
- In the Naming Conv field, enter a number for the naming convention.
- Enter a description.
- Select a role type from the dropdown list.
- Select a connector group. from the dropdown list.
- If you want to activate the naming convention, select the Enforcedcheckbox.
- Save your entry.
To maintain the naming convention format and position:
- In the Naming Conventiontable, select a naming convention, and then in the left hand navigation pane double-click Naming Convention Position.
- In the Naming Convention Positiontable, maintain the following information as required:
Item | Description |
---|---|
Sequence | The of the naming convention. |
Length | The amount of characters for the convention. |
Role Attribute | The type of information the user can enter. |
The available role attributes are:
- BPROC: Get information from Business Process attribute.
- BSUBPROC: Get information from Business Subprocess attribute.
- CONNECTOR_GRP: Get information Connector Group attribute.
- FREE_TEXT: Free text entry. No restrictions.
- PRJREL: Get information from Project and Product Rel attribute.
- ROLE_TYPE: Get information Role Type attribute.
- STATIC_TEXT: Use the text as provided by you.
- Note about underscores:
- ABAP considers strings with only an underscore '_' as a space. When you enter an underscore '_' in the static textfield and save the entry, it appears in the table as a space. In the Role Creationscreen, the application converts spaces to underscores.
- If you append a character to the underscore, ABAP displays both properly. For example, _Aor A_ is displayed as is.
- SYSTYPE: Get information from System Type attribute.
- In the Static Textcolumn, enter the text you want to appear in the naming convention.
- Note:The Static Textfield is only relevant for the role attribute STATIC_TEXT. If enter static text for any other role attribute, the application ignores the text entry.
- Save the entry.
Following is an example of a naming convention:
Naming Convention | Description |
---|---|
2 | SAP Single Naming Convention |
Sequence | Length | Role Attribute | Static Text | |
---|---|---|---|---|
1 | 2 | STATIC_TEXT | Z | |
2 | 3 | BPROC | ||
3 | 1 | STATIC_TEXT | _ (underscore) | |
4 | 3 | BSUBPROC | ||
5 | 1 | STATIC_TEXT | _ (underscore) | |
6 | 3 | PRJREL | ||
7 | 9 | STATIC_TEXT | _SIN_ROLE | |
8 | 1 | STATIC_TEXT | _ (underscore) | |
9 | 2 | FREE_TEXT |
,,
In the Create Rolescreen, the above naming convention displays in the Role Name field as this: Z.$$$_$$$_$$$_SIN_ROLE_##.
$ represents information taken from the attributes of the role.
# represents free text.
_SIN_ROLE is the static text you specified in item 7.
The convention resolves as you enter the name as follows: Z.FIN APP PER_SIN_ROLE 01
BAL_S_LOG - Application Log: Log header data Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 6216 Date: 20240523 Time: 193208 sap01-206 ( 47 ms )