Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JAS (Package) Application development R/3 Publishing Advertising System***
Basic Data
| Data Element | SI |
| Short Description | ALV List: Abbreviate AI BU To Initial Letters |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 20 | |
| Decimal Places | 0 | |
| Output Length | 20 | |
| 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 | AI abbrev. |
| Medium | 15 | AI abbreviation |
| Long | 20 | AI abbreviation |
| Heading | 5 | AI ab |
Supplementary Documentation - SICHTKZ 0001
Procedure
You can define any character for the individual areas.
Supplementary Documentation - SICHTKZ 0002
Use
You can link the class to an organizational area here. This enables a class to be selected automatically by the system during configuration, under certain circumstances.
Supplementary Documentation - SICHZ 0001
Dependencies
During order creation, this value is proposed via the scheduling margin key. You can, however, change it manually.
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.
Supplementary Documentation - SIMUK 0000
Use
If you carry out a test run, the selected outline agreements are not converted. Instead, a log of the selected agreements, their items, and conditions is generated.
Example
Use
Dependencies
Example
Supplementary Documentation - SINDEART 0001
Use
Procedure
You should maintain the used indices via the master data management.
Examples
Dependencies
You can only use settlement type "Cash settlement" with the index bond.
Supplementary Documentation - SIN_CONF 0001
Use
Procedure
Enter a name for the new configuration.
Examples
Dependencies
Supplementary Documentation - SIN_CONF 0002
Use
Procedure
Enter the name of the copy. It must be different to the name of the configuration which is to be copied.
Examples
Dependencies
Supplementary Documentation - SIN_FLAG 0001
Use
This flag defines the configuration as the initial configuration. It is used to display the inbox the next time it is called.
Procedure
Examples
Dependencies
Supplementary Documentation - SITABLE 1000
Use
You must make an entry here if you want to install a new table for the FI-SL component. The entry can be either a line-item table (if you want to later write line items in the productive system) or a line-item structure.
Procedure
Examples
Dependencies
Supplementary Documentation - SITABLE 2000
Use
Here you must enter a reference line item table. The reference table should, if possible, contain all dimensions and field groups of the target table (new table). This is important since control table entries are copied from the reference table for the target table. For the first new line item table you create, you can use the SAP standard tables GLS1 (local table) and GLS2 (global table) as the reference table.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20050223 |
| SAP Release Created in |
