Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KBAS (Package) Overhead Cost Controlling
Basic Data
| Data Element | TO |
| Short Description | Values to |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR24 | |
| Data Type | CHAR | Character String |
| Length | 24 | |
| Decimal Places | 0 | |
| Output Length | 24 | |
| 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 | Values to |
| Medium | 15 | Values to |
| Long | 20 | Values to |
| Heading | 55 | Values to |
Supplementary Documentation - TOFIELD 1000
Note
When you rollup with single items, you can also transfer fields to the related single item table for documentation purposes, as well as transferring fields to the receiver table. However, you must make sure that the receiver field exists in the table 'GLU1' and in the single item table, but does not exist in the summary table itself.
Procedure
Examples
Dependencies
Supplementary Documentation - TOGOC 0002
Procedure
If you want to maintain the planned counter reading manually, enter an offset in this field.
Example
A pump's counter is reactivated in the preventive maintenance plan after unexpected repairs have been carried out.
The total counter reading is 82,150 liters. A maintenance task is due every 10,000 liters. As the pump has just been repaired outside the normal maintenance cycle, the next task is not to take place at 92,150 liters, but at 100,000 liters instead.
Package due: every 10,000L
Total counter reading: 82,150 L
Next theoretical
planned counter reading: 92,150 L
Offset: 17,850 L
Planned counter reading
based on offset: 100,000 L
Supplementary Documentation - TOGRU_KK 0001
Use
The tolerance group and other fields form the activity key which is used to determine the activities defined in Customizing for processing returns for a return reason.
The tolerance group is determined from thecontract account.
Note:
The system always interprets the activity key in favor of the business partner or contract account involved.
Supplementary Documentation - TOPDO 0001
Use
Enter X if you want to obtain a list of the top customers. You can then branch to top materials for each customer from this list.
Leave the field blank if you want to obtain a list of top customers and the corresponding top materials.
Supplementary Documentation - TOPDO 0002
Use
Procedure
Examples
Dependencies
Supplementary Documentation - TOPER 0100
Use
Here, the last allowed posting period defines the last period for which the revaluation percentage rates defined below are to be used. This way validity intervals can be defined together with the FROM period field for the revaluation percentage rates. The period intervals thus defined must not overlap.
Procedure
Examples
Dependencies
Supplementary Documentation - TOTABLE 1000
Use
- Rollup
Both fields, sender table and receiver table, are used.
- Reset
Only the receiver table field is used.
Note
In a hierarchical rollup and export rollup, you can only rollup data within one table.
Examples
Dependencies
Supplementary Documentation - TO_P 0001
Use
The "To period" contains the last period for which assessment, distribution, periodic transfer or indirect activity allocation can be performed.
Dependencies
You can carry out assessment, distribution, periodic transfer or indirect activity allocation for several periods in parallel.
Supplementary Documentation - TO_P 0002
Use
The "To period" is the last period for which activity price calculation is carried out.
Dependencies
You can carry out activity price calculation for several periods. The "From period" field contains the first period, the "To period" the last period of the calculation.
Supplementary Documentation - TO_P 0003
Use
The "To period" is the last period for which activity price calculation is carried out.
Dependencies
You can carry out activity price calculation for several periods. The "From period" field contains the first period, the "To period" the last period of the calculation
Supplementary Documentation - TO_P 0004
Use
The to-period is the final period for which summarization is run.
Dependencies
You can summarize more than one period simultaneously. If you do this, the from-period contains the first period of the summarization, and the to-period contains the final period of the summarization.
Supplementary Documentation - TO_P 0100
Use
The "To period" is the last period for which revaluation is carried out.
Dependencies
The period range you enter must be within the posting periods defined for revaluation with the maintenance transaction.
Supplementary Documentation - TO_P 0461
Use
If you carry out progress determination more than once, the system calculates:
- Plan values for the whole planning period
- Actual values for the period specified
- Correction values in actual through to the previous period
Further notes
The system does not update actual values from previous periods.
If actual values have already been calculated for subsequent periods, the system deletes these values:
History
| Last changed by/on | SAP | 19920308 |
| SAP Release Created in |
