Hierarchy

⤷

⤷

Basic Data
Data Element | CMGRPM |
Short Description | Planning Group (masking possible) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FDGRP | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | T035 |
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 | Plan. grp |
Medium | 15 | Planning group |
Long | 20 | Planning group |
Heading | 10 | Plan. grp |
Documentation
Definition
Planning groups for assignment to payment dates. You can mask the entries using "+". When the summary records read from the data basa are compared with the planning groups here, the system takes account of their length. For example, planning group A1 is valid for the entries "A+" or "++", but not for "A++" or "++++".
It can be useful to enter customer planning groups for collection and for customers managed as vendors.
In the case of vendor planning groups, remember that, when checks or bills of exchange are used to make payment, correct assignment to payment dates is not possible. In the case of bank transfer paymens, the assignment should be precise.
As payment methods are not known in liquidity forecast, no selection is possible there. This means that you can only make good use of the "Include Payment Dates" function in the liquidity forecats if you can use the group and level selection options provided to restrict processing to customers paying by automatic debit and vendors (and customers managed as vendors) where bank transfers are used.
History
Last changed by/on | SAP | 20010607 |
SAP Release Created in |