Function Names - Special Cases
Calling and Closing Functions | Save and Temporary Save | Delete, Recall, Undo and Cancel | Back
This page describes guidelines for the naming of special functions.
Calling and Closing Functions
The text describing functions should be as exact as possible.
Make sure that the function that calls or starts a transaction is stated differently than the function that closes the same transaction.
Examples
|
Calling Function Name |
Closing Function Name |
|---|---|
|
Book trip |
Submit booking |
|
Create customer data |
Save customer data |
|
Order business cards |
Submit order |
|
Request vacation |
Forward vacation request for approval |
Save and Temporary Save
In addition to a save function at the end of a transaction, users also require a save function during the transaction.
This function should not be called "Save" or similar, but rather should be described more precisely.
Examples
|
In the Context of |
Function Name |
|---|---|
|
Orders |
Add to shopping cart |
|
Requests |
Send to inbox |
|
Master data |
Save |
Delete, Recall, Undo and Cancel
Generally, the user cannot redo his or her last entries unless there is a special function to do so, such as "Delete entry". If it is possible to cancel or delete saved or booked data, you should warn the user about the consequences of such an action.
Back
Use the standard formulation "Back to
Examples
|
Back to overview |
|
Back to home page |
|
Back to booking |
Source: SAP Reference Lists