Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-IDE (Application Component) Intercompany Data Exchange⤷
EE_DEREG_INV (Package) Payment Management in a Deregulated Environment
Basic Data
| Data Element | E_AGGR_VAR |
| Short Description | ETHIM: Aggregation Variant |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | E_AGGR_VAR | |
| 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 | AggrVar. |
| Medium | 15 | Aggr. Variant |
| Long | 20 | Aggregation Variant |
| Heading | 21 | Aggregation Variant |
Documentation
Definition
When creating the aggregated bill, the aggregation variant allows you to make specifications for the internal aggregation.
Use
The following specifications are possible:
- No specifications
- Aggregate reversals and credits separately
- Only aggregate credits separately
- Only aggregate reversals separately
Dependencies
When creating bills for deregulated end customers, you can already influence the subsequent aggregation, which takes place during the creation of the aggregated bill for the supplier. You do this by maintaining the GROUPVAL, GROUPNOT and V_GROUP fields (as of release ERP 2005) in the DFKKTHI database table. For more information see event R202 and event R203.
The internal aggregation specifications take into consideration the specifications that already exist in the data records from the DFKKTHI table.
If your company plans to execute the aggregation separately for receivables, credits and reversals, and not to differentiate any further, then you need only choose the appropriate internal specifications in each case.
Note that the specifications in transaction ETHIM are only ever used if no entry has been made for events R202 and R203 in the GROUPNOT field of the DFKKTHI database table.
Example
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
