Hierarchy
⤷
⤷
Basic Data
| Data Element | BAPI_JBD_DTE_GTAGGREG |
| Short Description | Aggregation rule |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | JBRAGGREG | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | AGGREGATION_RULE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Agg. Rule |
| Medium | 17 | Aggregation rule |
| Long | 20 | Aggregation rule |
| Heading | 17 | Aggregation rule |
Documentation
Definition
In the hierarchy of the (extended) elementary categories (FGET) for a risk object, the aggregation rule describes how the values or prices determined at a lower level are aggregated for a higher level (simple addition of the prices, for example).
The following applies for elementary transactions and their FGETs:
If they are valued using a price calculator, they have no aggregation rule.
Example: An option on a bond comprises two FGETs which require no aggregation rule because they are valued together as one elementary transaction. A cap, however, comprises several caplets which themselves are options. The master FGET, that is the cap itself, carries the aggregation rule 0001 (= addition), the caplets as elementary transactions carry no aggregation rule.
Definition
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20030430 |
| SAP Release Created in | 463_20 |