Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVVW (Package) Treasury Management: Securities
IMG Activity
| ID | SIMG_CFMENUFWMCFWFO | Define Correspondence Activities |
| Transaction Code | S_ALR_87003890 | IMG Activity: SIMG_CFMENUFWMCFWFO |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUFWMCFWFO | Define Forms |
| Customizing Activity | SIMG_CFMENUFWMCFWFO | Define Forms |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FORMULARE_GH |
Various Parameters are used here to control when and with which product and transaction types correspondence can be carried out. The settings that you make here are also relevant for controlling SWIFT confirmations and IDocs.
- Company code (required entry)
- Product type (required entry)
- Transaction type (required entry)
- Activity type e.g contract, settlement (required entry)
- Last function e.g new contract, reversal (optional entry). If no function is specified, then correspondence is carried out for all functions of the activity category.
Several correspondence types can be defined for identical parameter specifications. For example, in the case of a new fixed-term deposit, alongside a dealing slip, a confirmation letter can be seen as correspondence. Note that for identical parameter specifications, many internal user-defined correspondence types may be defined but only one external correspondence type. The external correspondence type is critical for the confirmation status of the transaction. In general, each activity/status (contract, contract settlement) of a transaction can be confirmed.
Alongside the form, you can also specify here whether the correspondence should be carried out automatically - for example, when the transaction changes over from the activity type, contract to settlement, or when a transaction is reversed. For SWIFT confirmations, there is no automatic correspondence function.
The "Counterconfirmation required" field controls whether a counterconfirmation should take place for the business partner. Additionally, the "Counterconfirmation" field must be set for the business partner-dependant standing instructions - provided that you carry out a confirmation match with the corresponding business partner.
You can also branch from here to the Form Editor to display the form data and/or change it.
Further notes
There is no logging via a log form with automatic correspondence, only an entry in the financial transaction. In the menu, you find this via Goto -> Correspondence.
Check your entries after saving via the Check function.
You will find further information on SAPscript forms in TR Confirmations in the SAP Library via Back office -> Correspondence -> Outgoing correspondence.
Business Attributes
| ASAP Roadmap ID | 259 | Establish Forms and Messages |
| Mandatory / Optional | 2 | Optional 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 | FORMULARE_GH | 0 | KFM0000009 | Transaction Management |
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_FORM_2 | V - View | SM30 |
History
| Last changed by/on | SAP | 20000718 |
| SAP Release Created in |
