Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBAS (Package) Financial accounting 'Basis'
Basic Data
| Data Element | SIGN |
| Short Description | Debit/Credit Sign (+/-) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SIGN | |
| 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 | Sign (+/-) |
| Medium | 15 | Dr./Cr. signs |
| Long | 20 | Debit/credit signs |
| Heading | 1 | S |
Documentation
Definition
With certain evaluations, it may be useful to define the +/- sign of the item values differently to the definition in the item table.
Thus, when specifying a minus sign, the corresponding line item is displayed the other way round to its definition. For example, revenue items can be displayed with a positive sign and expense items with a negative sign.
Supplementary Documentation - SIGN 0001
Examples
+ = annual net income
- = loss for the year
Supplementary Documentation - SIGNAUTH 3000
Use
Procedure
Examples
Dependencies
You can only execute an individual signature if you have the authorization for the authorization group allocated to it.
Supplementary Documentation - SIGNSTEP 2500
Use
The individual signatures you allocate here must or can be executed when carrying out a signature strategy.
You can either allocate the same individual signature several times or allocate several different individual signatures of the same authorization group. When carrying out the signature strategy, however, each user of the corresponding authorization group may sign only once.
Procedure
Examples
Dependencies
Supplementary Documentation - SIGNSTEP 4000
Use
The sequence matrix contains a row and a column for all individual signatures allocated to the signature strategy.
Procedure
To define the precedessors of an individual signature, mark the predecessor signatures (that is, their columns) in the row for the relevant individual signature.
Examples
Dependencies
Supplementary Documentation - SIGNSTEP 5000
Use
The overview contains a column for all individual signatures allocated to the signature strategy.
Each row contains a possible combination of signatures.
Procedure
Mark the combination you want to use as a release status.
A signature process cannot be completed unless all indvidual signatures pertaining to a release status have been executed.
Note
If you have accessed the signature strategy in the display mode, the system displays the release statuses defined so far.
Examples
Dependencies
Supplementary Documentation - SIGNSTRAT 0001
Use
The signature strategy you assign here must be executed when a batch record for the material you have selected is approved.
If you do not assign a signature strategy, the batch records may be approved by executing only one digital signature.
Dependencies
Example
Supplementary Documentation - SIGNSTRAT 0010
Use
Procedure
Enter the signature strategy you want to use to control the signature process. After entering the signature strategy, you must also do the following:
- Enter the audit indicator.
- Set the locked status as the status type.
Examples
Dependencies
When you set this document status, you must execute the digital signature.
You define the signature strategy in section Approval.
Supplementary Documentation - SIGNSTRAT 1250
Use
The signature strategy you allocate here must be executed when signing a PI sheet.
If you do not allocate a signature strategy in the process instruction, the system uses the default strategy defined in the control recipe destination.
If no signature strategy has been defined in the control recipe destination either, only one signature is required.
Procedure
Examples
Dependencies
For the system to take the signature strategy into account, the following requirements must be met:
- The Digital signature indicator has been set in Customizing for the control recipe destination.
- For input validations, the process instruction also specifies that a signature is required to transfer invalid values to the PI sheet.
History
| Last changed by/on | SAP | 19920620 |
| SAP Release Created in |
