Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-BP (Application Component) Business Partners⤷
FB0C (Package) Financial Accounting customers
IMG Activity
| ID | SIMG_CFMENUORFBOB80 | Control the Automatically Generated Payment Notices |
| Transaction Code | S_ALR_87001679 | IMG Activity: SIMG_CFMENUORFBOB80 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORFBOB80 | Control the Automatically Generated Payment Notices |
| Customizing Activity | SIMG_CFMENUORFBOB80 | Control the Automatically Generated Payment Notices |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORFBOB80 |
Payment notices can be created automatically. You have two options for doing this:
- The payment notices are to be created depending on the business transaction.
This is possible for residual items, partial payments or payments on account.
- The payment notices are to be created depending on the customer for each incoming payment.
To do this, mark the field Cust.(with CI) or the field Cust.(w/o CI) in the customer master record. This specification has a higher priority than the first option.
If you want to create payment notices for residual items, partial payments or payments on account, store the correspondence type which is to be used in this step for every company code for which you require this and dependent on the tolerance group.
In addition, you have the option of sending a specific payment notice to the customer for the incoming payment. To do this, you must set the "Acc.to reason code" indicator. This is, however, only valid if there is only one payment reason code. If there are several payment reason codes, for example, "10% deduction due to faulty goods" and "Cash discount deducted when net payment due", then the type of payment notice is determined again using the tolerance group.
Example
In company code 0001, you would always like to create a payment notice without line item display for residual items. To do this, define the correspondence type "SAP02". You do not want, however, to use the general correspondence type "SAP02" if there is just one reason for the payment difference, but to generate a payment notice suitable for just the one reason. To do this, set the "Acc.to reason code" indicator. If there is more than one reason code, then the correspondence type "SAP02" is taken as before.
Requirements
If you want to send a suitable payment notice according to a reason code, you must first of all define reason codes. In the standard system, there are a number of reason codes delivered with the accompanying correspondence types. For more information on this, please read the chapter "Defining reason codes".
Note
You can make your specification depending on the tolerance group for payment differences. The tolerance groups must also have been entered in the customer master records.
Activities
- Find out for which company codes and business transactions payment notices are to be created automatically. Enter these company codes and the necessary details.
- Find out for which customers payment notices are always to be created automatically. Ensure that the corresponding fields are selected in the master records.
- Ensure that print programs, selection variants, layout sets and standard texts are stored for the relevant correspondence types.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | SIMG_CFMENUORFBOB80 | 0 | HLA0001266 O HLA0008965 |
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_T043K | V - View | OB80 | 9999999999 | Control of Automatically Generated Payment Notices |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
