SAP ABAP Data Element TB_SNOREVERSCO (Suppress initial reversal correspondence)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FTA (Package) R/3 appl. development for Treasury money,forex,forward gen
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FTA (Package) R/3 appl. development for Treasury money,forex,forward gen
Basic Data
Data Element | TB_SNOREVERSCO |
Short Description | Suppress initial reversal correspondence |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | No rev. |
Medium | 15 | No reversal |
Long | 20 | No reversal corr. |
Heading | 1 | S |
Documentation
Definition
This setting allows you to suppress the generation of correspondence (i.e. creation of planned records in the background) in certain cases. It is usually a good idea to make this setting for external correspondence types.
Example
- A correspondence-relevant financial transaction is created (Function = NEW CREATION). In the background, the system creates a correspondence planned record (= worklist) for the new creation.
- Without correspondence being generated in the meantime, the transaction is later reversed. In the background, the function (technical table field: SFUNKTL) is changed from NEW CREATION to REVERSAL.
- The corrrespondence run is then started.
- The reversal correspondence is then generated as the first correspondence for an activity. For external correspondence, this is usually not wanted; for electronic confirmations that enter the SWIFT net, this is not allowed. By flagging this checkbox, this planned record can be suppressed i.e. this transaction is not communicated externally.
Further notes
This Customizing setting has no effect on correspondence in the Securities area up to Release 45B.
History
Last changed by/on | SAP | 20020219 |
SAP Release Created in |