Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI (Application Component) Financial Accounting⤷
FBMCORE (Package) Dunning
Basic Data
| Data Element | MGRUP |
| Short Description | Key for dunning notice grouping |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MGRUP | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | T047R |
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 | Grpng key |
| Medium | 15 | Grouping key |
| Long | 20 | Grouping key |
| Heading | 10 | Grpng key |
Documentation
Definition
The grouping key represents a rule according to which the open items of the account are to be grouped together for dunning notices.
Use
The grouping key is used in cases where you do not want the open items of a customer or a vendor to be dunned together but rather want to create several dunning notices for an account. You must define one field from the open items for each grouping key. All items which have the same contents in this field are then grouped together in a single dunning notice. With credit memos, ensure that the contents in this field match those in the same field in the invoice; if this is not the case, the items will either be included in a different dunning notice or will not be dunned at all.
Examples
If you install Financial Assets Management, you can define a rule which creates a separate dunning notice for every rent object.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
