SAP ABAP Data Element XSTMV_047 (Separate dunning notice for each dunning level?)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FBM (Package) Dunning
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FBM (Package) Dunning
Basic Data
Data Element | XSTMV_047 |
Short Description | Separate dunning notice for each dunning level? |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | By dun.lev |
Medium | 15 | By dunning lev. |
Long | 20 | Dunn.by dunn.level |
Heading | 10 | By dun.lvl |
Documentation
Definition
An entry in this field means that a separate dunning notice is created within an account for every dunning level determined.
Use
You establish this independent of company code. In contrast to standard dunning in which all items at all dunnning levels are dunned with one dunning notice and the highest occurring dunning level determines the dunning text, when dunning by dunning level a separate dunning notice is produced per dunning level with a different accompanying text in each case. The customer/vendor can then receive several dunning notices from one dunning run.
History
Last changed by/on | SAP | 19981118 |
SAP Release Created in |