Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-DSG (Application Component) Digital Signature⤷
DS (Package) Digital Signature
Basic Data
| Data Element | SIGN_TYPE |
| Short Description | Signature Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SIGN_TYPE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Sig. Type |
| Medium | 15 | Signature Type |
| Long | 20 | Signature Type |
| Heading | 16 | Signature Type |
Documentation
Definition
Specifies if the signature process is synchronous or asynchronous.
Use
Depending on the signature object, signature processes can be executed synchronously or asynchronously.
- Asynchronous signature process
For an asynchronous signature process, the signatories perform their signatures independently of one another. After each signature, the data is updated. The signature process can be interrupted after every signature, and continued by the next signatory at any point in time and in any place. Each individual signature therefore is processed in a separate transaction.
You need to enter a password to interrupt the asynchronous signature process.
- Asynchronous signature process with changeable signatory
With this setting, you can specify that the signature process is permitted with changeable users. In this case, the user is permitted to change the user ID of the signatory during the signature process. This can be useful, for example, if a number of employees work at one common computer.
- Synchronous signature process
Once a synchronous signature process has started, it must be continued until the end without interruption. A new function or transaction cannot be called until the last required signature has been completed. If the signature process is interrupted before the end, then all previous completed signatures are saved, but are not valid for the signature process and must be repeated.
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 620 |
