Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
Basic Data
| Data Element | CGSAGGTM |
| Short Description | Aggregation based on time |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AGGTM | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | Agg.(time) |
| Medium | 15 | Agg.(time) |
| Long | 20 | Time-based aggregatn |
| Heading | 4 | AggT |
Documentation
Definition
A time-based aggregation rule determines how a key figure is calculated when the reference field is a characteristic with a time dimension.
Example
A report is created to compare the stock exchange prices of several joint-stock companies. The exchange rates are listed on trading days. In this example, it would be useful to choose aggregation AVG (average) for the time-based aggregation and trading day as the time dimension (characteristic).
Supplementary Documentation - CGSAGGTM 0001
Use
Only the aggregation rules 'SUM', 'AVG', 'LAS' and 'NOP' are supported in data entry and planning, contrary to in reporting.
Procedure
Examples
Dependencies
Supplementary Documentation - CGSAGGTM 3101
Use
In the information system and in planning for Profitability Analysis (CO-PA), period values are usually added together. That is, the aggregation rule is SUM.
The aggregation rules "Last value" and "Average" are only useful for representing statistical, noncumulative values in value fields.
The reference period is always the period of a fiscal year. If you plan in weeks, value fields cannot use the aggregation rules AVG or LAS.
This does not affect the logic used for updating the data.
Examples
Current interest rate - VV001, Aggregation LAS
Average number of employees - VV002, Aggregation AVG
Actual:
Period Posting |Report on
VV001 VV002 |Period 1 to... VV001 VV002
1 3 100 | 1 3 100
2 3 100 |
1 10 | 2 4 105
3 4 120 | 3 4 110
4 2 90 | 4 2 105
Planning:
1. Planning on the overview screen for periods 1 through 4:
Overview screen | Period values
VV001 VV002 | Periode VV001 VV002
3 100 | 1 100
| 2 100
| 3 100
| 4 3 100
2. Change to period values:
Period values | Overview screen
Period VV001 VV002 | VV001 VV002
1 3 100 | 2 105
2 3 110 |
3 4 120 |
4 2 90 |
3. Change to values on the overview screen:
Overview screen | Period values
VV001 VV002 |Periode VV001 VV002
3 120 | 1 3 114
| 2 3 126
| 3 4 137
| 4 3 103
Dependencies
History
| Last changed by/on | SAP | 19950403 |
| SAP Release Created in |
