Hierarchy
⤷ IS-U-IDE (Application Component) Intercompany Data Exchange
⤷ EE_DEREG_INV (Package) Payment Management in a Deregulated Environment
Basic Data
Data Element | E_AGGR_SEL |
Short Description | Aggregation Selection |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | E_AGGR_SEL | |
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 | Aggr.Sel. |
Medium | 15 | Aggr. Selection |
Long | 20 | Aggr. Selection |
Heading | 22 | Aggregation Selection |
Documentation
Definition
When creating the aggregated bill, the aggregation selection allows you to make specifications for the internal selections.
Use
The following specifications are possible:
- Select all items
- Select only credits
- Select only reversals
- Only budget billing items
Dependencies
When creating bills for deregulated end customers, you can already influence the subsequent aggregation that takes place when creating the aggregated bill for the supplier. You do this by maintaining the GROUPVAL, GROUPNOT and V_GROUP fields in the DFKKTHI database table. For more information, see ISU_SAMPLE_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, reversals, and budget billing items, and not to differentiate any further, then you need only choose the appropriate internal specifications in each case.
Example
History
Last changed by/on | SAP | 20050411 |
SAP Release Created in | 600 |