Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-TM (Application Component) Transaction Manager⤷
FTHM (Package) Hedge Management - central objects
Basic Data
| Data Element | THA_GROUP_TRANSACTION |
| Short Description | Grouping Characteristic: Transaction to Exposure Assignment |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | THM_EXPOSUREID | |
| Data Type | NUMC | Character string with only digits |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| Value Table | THMEXT_EXPOS |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | TRANSACTION_GROUP | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Group |
| Medium | 15 | Transactn Group |
| Long | 20 | Transaction Group |
| Heading | 10 | Group |
Documentation
Definition
The grouping assigns multiple transactions to the same exposure.
Use
The grouping is used if multiple transactions are to be created using BAPI interfaces in hedge accounting, and the exposure to which the transactions in hedge accounting are to be assigned, do not exist yet.
Dependencies
The grouping field is only taken into account if the Exposure ID field is initial.
Example
For example, if ten transactions have to be created at the same time using BAPI so that a transaction (A ) is assigned to a new exposure that needs to be created, three other transactions (B, C, D) are assigned to the already existing exposure '2', and the remaining transactions (E, F, G, H, I, J) are assigned to a new exposure that needs to be created, then you need the grouping.
The Grouping field remains empty for the individual transaction (A). The ExposureID field also remains empty because otherwise the transaction and the exposure will be recreated.
For the three transactions to be created (B, C, D), the Grouping field remains empty because the exposure already exists in hedge accounting. The value '2' is entered in the Exposure ID field for all three transactions. As a result, the transactions are assigned to the exposure with ID '2'.
Any number is entered in the Grouping field for the remaining transactions. This number is identical for all six transactions. The Exposure ID field is not filled and remains initial. As a result, all transactions are assigned to the newly created exposure.
History
| Last changed by/on | SAP | 20060208 |
| SAP Release Created in | 600 |
