Hierarchy
⤷ FIN-FSCM-TRM-TM-TR (Application Component) Transaction Management
⤷ FTTR (Package) Treasury: Financial Transaction
IMG Activity
ID | KORRESPONDENZART_MM | Define Correspondence Types |
Transaction Code | S_ALR_87099704 | SAPLS_CUS_IMG_ACTIVITY |
Created on | 19990318 | |
Customizing Attributes | KORRESPONDENZART_MM | Define Correspondence Types |
Customizing Activity | KORRESPONDENZART_DE | Define Correspondence Types |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | KORRESPONDENZART_GF |
In this step, you create your own correspondence types or transfer/ change the specifications of the existing ones.
Correspondence types are divided into internal and external correspondence types. The main difference is that internal correspondence types can only be controlled via "Assign forms" in Customizing; external correspondence types are (or must be) controlled via the business partner in standing instructions.
RESULT: An internal correspondence type defined via "Define correspondence activities" in Customizing is created for all corresponding transactions. In the case of external correspondence types, you can use the standing instructions to ensure that correspondence is created for business partner A but not for business partner B. Only external correspondence can be status-relevant and, therefore, set the confirmation status. The leading correspondence medium is also defined in the standing instructions for this.
Correspondence is output via SAPscript forms and/or as SWIFT-Files for fixed-term deposit and forex transactions.
Requirements
In the case of an external correspondence type, for the business partner, you must maintain the correspondence standing instructions of the relevant correspondence type for the company code and of the product/transaction type. If this is not done, correspondence is not created.
Further notes
Language key:
In the language key, you specify in which language the correspondence is to be created. If you do not specify a language key, the correspondence will be in the language used for the master data of the particular business partner.
Example of language key:
Your business partner is to receive a counterconfirmation in French. Language FR is set for the business partner. The internal dealing slip is to be printed in German. Enter DE for the language here.
If the correspondence is to be archived in an optical archive, you must make an entry in the relevant field. The prerequisite for this is the correct basis setting for the archive link. (The business object is BUS 2042; the document type is TRO_CONF).
Suppress initial reversal correspondence: This setting allows you to prevent the generation of correspondence in certain cases (creation of planned records in the background). In general, it is a good idea to make this setting for external correspondence types. You will find examples in the F4 Help.
Activities
- Define the correspondence type.
- Specify whether an internal or external correspondence type is involved.
- Specify a language key if the correspondence type language is different from that of the business partner master data.
- Set the 'Optical archive' indicator if the correspondence is to be optically archived.
- Save your entries.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | KORRESPONDENZART_GF | 0 | HLA0100044 | Correspondence |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V_CORTYP | V - View | SM30 |
History
Last changed by/on | SAP | 20000718 |
SAP Release Created in |