Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
IMG Activity
| ID | SIMG_CMMENUOFDIFOZW | Determine Dunnable Payment Methods |
| Transaction Code | S_ALR_87007032 | IMG Activity: SIMG_CMMENUOFDIFOZW |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CMMENUOFDIFOZW | Determine Dunnable Payment Methods |
| Customizing Activity | SIMG_CMMENUOFDIFOZW | Determine Dunnable Payment Methods |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CMMENUOFDIFOZW |
In this section, you determine which incoming payment methods are dunnable.
Example
Overdue customer items that had a payment method are generally not dunned since incoming payment methods are evaluated as payment methods that are dealt with automatically by the payment program (for example collection, bank direct debit). In some cases, however, the following situation exists:
A tenant has concluded several contracts, where for some contracts the payment is made by bank collection but where for other contracts the tenant pays by bank transfer, cash payment, and so on.
This means that a distinction has to be made in the documents as to whether the item is to be subjected to the automatic payment method or whether it is paid "manually". In the latter case, the item can also be dunned under the following conditions:
- the "contract number" field is filled and
- thd dunning grouping in the customer master was agreed per contract (see below) and
- the item either does not have a payment method (and the customer master does not contain a non-dunnable payment method) or it has a "dunnable incoming payment method".
You determine the dunning grouping per contract number in FI customizing. It must contain the following fields (in this sequence):
- Contract no. VERTN length 13
- Contract type VERTT length 1
Requirements
The incoming payment methods are previously created in the Financial Accounting Customizing for each country.
Activities
Check the standard settings and change them, if necessary.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | 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_CMMENUOFDIFOZW | 0 | I090004614 | Rental Accounting |
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 |
| VTIVZW | V - View | SM30 | VTIVZW | Dunnable Payment Methods |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
