Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-PCT (Application Component) Product Catalog⤷
FF (Package) Cash Management
Basic Data
| Data Element | FDGRP |
| Short Description | Planning Group |
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 | FFG | |
| 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
Use
In Cash Management, customers and vendors are assigned to the planning groupsby means of master data entries.
Procedure
You can define whatever planning groups you like, using customizing or IMG; the planning groups should all be the same length. In the case of large customers or suppliers, it may, however, be a good idea to enter the account number as the planning group as this makes the liquidity forecast display clearer.
It also makes sense to use a naming convention in the planning groups, as this also makes the liquidity forecast clearer. In the examples below, the planning groups for customers are prefixed "R" (for "revenue") and those for supplies are prefixed "E" (for "expenditures").
Examples
R1 Customers, bank collection
R2 Other domestic debtors
R3 Foreign debors
R4 Affiliated company debtors
R5 High risk debts
R6 Debts owed by major customers
R7 Rental income
R8 Repayment of loans granted
...
E1 Domestic vendors
E2 Foreign vendors
E3 Affiliated company creditors
E4 Major suppliers
E5 Personnel costs
E6 Taxes
E7 Capital investment
...
Supplementary Documentation - FDGRP 0001
Use
When data from MM and SD is updated, company code data for the customer (odering party) or the vendor (supplier) is usually not created yet and thus the planning group is also not stored in the master record.
During purchase requisitions the supplier is often not known.
Therefore, you can store in this table a planning group that the system takes as an alternative and uses in the following instances for updating Cash Management:
- In a purchase order or sales order, general data for the vendor or customer is created, but the company code data is not.
- In a purchase requisition, the fixed vendor is not known yet. (The desired vendor is not used for updating Cash Management since it has no obligation.)
If the company code data is then subsequently created and the planning group is maintained in the master record, Cash Management is not affected or changed, that is, the amounts are still displayed in the planning group in which they were updated during entry. The correct allocation to the planning group corresponding to the master record only occurs if the purchase order, sales order or purchase requisition is changed or invoice verification takes place.
Procedure
Examples
Dependencies
Supplementary Documentation - FDGRP 0002
Use
The customer or vendor group defined here is used if the company code data from the customer or vendor has not yet been created and therefore the correct planning group cannot be determined when updating earmarked funds in Cash Management.
Dependencies
Example
Supplementary Documentation - FDGRP 0003
Use
The customer or vendor group defined here is used if no customer or vendor is assigned in earmarked funds when updating earmarked funds in Cash Management.
This means that HR commitments that generate earmarked funds documents can also be updated without being assigned as a customer or vendor in Cash Management. Such an assignment is not possible for HR commitments since the payment is carried out for many customers and vendors rather than individual ones, for example employees, tax authorities and health insurers.
Dependencies
Example
Supplementary Documentation - FDGRP_KK 0001
Use
The planning group classifies prospective receipts and expenditure for updating in Cash Management (TR-CM).
Assignment of a business partner to a planning group takes place at the contract account or insurance object level (this is controlled by the fields Parameters Active in Insurance Contract or Parameters in Contract Account). This ensures that this assignment only refers to the business partner in connection with this contract account or insurance object.
Supplementary Documentation - FDGRP_KK 0002
Use
The expected receipts and expenditures for the update in Cash Management (application component TR-CM) are classified by the planning group.
The allocation of a business partner to a planning group is established at contract account or insurance object level (controlled by the fields Insurance Contract Parameter Active and Contract Account Parameter Active).
This ensures that the allocation is only based on the connection between the business partner and the contract account, or insurance object.
Supplementary Documentation - FDGRP_KK 2100
Use
To enable Cash Management to be updated, a planning group is assigned at business partner/contract account level.
Procedure
This planning group is automatically transferred to the line item from the contract account.
Examples
Dependencies
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
