Hierarchy
⤷ TR (Application Component) Treasury
⤷ FTA_CORE (Package) TR-CORE: Former Objects from FTA (Applic. Dev. TR General)
Basic Data
Data Element | TB_SPRGRD |
Short Description | Determine grouping definition |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | T_SPRGRD | |
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 | Group det. |
Medium | 15 | Group determ. |
Long | 20 | Group determ. |
Heading | 2 | GD |
Documentation
Definition
Determine grouping definition.
Use
Payment requests are divided into individual payments using the grouping definition.
If transactions have been linked manually (netting), they are given a joint unique group definition.
This ensures that they are paid jointly and that no "unrelated" transactions can be given the same definition "by accident", thus impacting this netting agreement.
If transactions are not linked manually, you can make settings to determine how the grouping definition is to be put together.
Examples
If different flows are to be paid separately from each other (via payment requests), although they have matching criteria (e.g. same company code, partner, currency, value date), you must assign these flows to different grouping definitions if need be.
- If you select the transaction no., this creates a very high level of segregation as only flows within one transaction can be grouped.
- On the other hand, if you select the product category as the grouping definition, only flows which have different product categories are separated. It also allows you to group flows within the same product category, where applicable.
- If you leave the entry for the grouping definition, flows of all product categories can be paid on a joint basis, if the flows fulfil the above-mentioned matching criteria.
History
Last changed by/on | SAP | 20011002 |
SAP Release Created in |