SAP ABAP Data Element VVJMAHN (Payment key can be dunned)
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

⤷

⤷

⤷

Basic Data
Data Element | VVJMAHN |
Short Description | Payment key can be dunned |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
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 | Be dunned |
Medium | 15 | Pmnt meth.dunn. |
Long | 20 | Inc.pmnt meth. dunn. |
Heading | 0 |
Documentation
Definition
In financial accounting, the incoming payment methods are usually only created for the incoming payments which should be made automatically, i.e. via the payment program. If such a payment method is entered in a document, the dunning program assumes that this document cannot be dunned (since the incoming payment is made automatically, e.g. by bank collection).
For Financial Assets Management purposes, it is however necessary to manage payment methods in documents, although the incoming payment is not carried out automatically. These ("manual") payment methods have to be determined in FI-Customizing and then assigned the indicator "can be dunned" here, if they should be dunned.
History
Last changed by/on | SAP | 19970708 |
SAP Release Created in |