Hierarchy
SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR⤷
FI-TV-PL (Application Component) Travel Planning⤷
PTRP (Package) Travel Planning
Basic Data
| Data Element | TAB |
| Short Description | Number of Tab |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FTPD_TAB | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | Tab number |
| Medium | 15 | Tab number |
| Long | 20 | Number in tabstrip |
| Heading | 9 | Tab no. |
Documentation
Definition
The tab number specifies the tab page on which the subview is later to appear in the control station display.
Supplementary Documentation - TABELLE 0099
Use
In the object table, you define which objects of a class are to be selected. This is of particular relevance if objects of more than one class type (for example, material, batch) can be classified in the class type concerned.
Procedure
Examples
Dependencies
Supplementary Documentation - TABFLDNAME1111
You can include a table in the view by entering the character * in this column, the table name in the Table field and the character * in the View field field.
Supplementary Documentation - TABGD 0001
Use
If you select this indicator, the following customizing settings are activated or deactivated in the correction:
- Assignments (TKSA0)
- Base cost elements (TKZU1)
- Credit objects cost-element-%-method (TKZU3)
- Credit objects target=actual method (TKZU9)
In this case, controlling area dependent data belonging to the imputed costs definition are used.
Procedure
- To include the settings in the correction request number specified, choose Include in Correction.
- To remove the settings from the correction request, choose Delete from Correction.
In both cases the system may display a screen on which you can restrict your selection of entries to be transported (by controlling area or chart of accounts, for example).
Examples
Dependencies
Actual and plan accrual data is not transported separately. You only need to select the transport once in the transport menu, with either "Planning" or "Actual Postings".
If you transport accrual data for different controlling areas one after another, you do not need to specify the data for the second controlling area, but only need to activate the "Including Related Data" indicator.
Access sequences are not client-specific. You do not need to transport this data between clients in the same system.
When transporting between different systems, you must maintain your own access sequences manually.
Overhead rates must always be maintained manually.
Supplementary Documentation - TABGR 0001
Use
If you select this indicator, the following customizing settings are activated or deactivated in the correction:
- Costing sheets (T683, T683S, T683T)
- Condition types (T685, T685A, T685T)
- Credit keys (T687, T687T)
These are general imputed cost definitions not based on the controlling area.
The following are not transported.
- Access sequences
- Surcharge percentages
Procedure
- To include the settings in the correction request number specified, choose Include in Correction.
- To remove the settings from the correction request, choose Delete from Correction.
In both cases the system may display a screen on which you can restrict your selection of entries to be transported (by controlling area or chart of accounts, for example).
Examples
Dependencies
Actual and plan accrual data is not transported separately. You only need to select the transport once in the transport menu, with either "Planning" or "Actual Postings".
If you transport accrual data for different controlling areas one after another, you do not need to specify the data for the second controlling area, but only need to activate the "Including Related Data" indicator.
Access sequences are not client-specific. You do not need to transport this data between clients in the same system.
When transporting between different systems, you must maintain your own access sequences manually.
Overhead rates must always be maintained manually.
Supplementary Documentation - TABNAME 0000
Use
The generation of the result can depend on certain field restrictions resulting from the old and/or new value of a database field.
Procedure
If you maintain a field restriction yourself, enter the table containing a field which is to influence the generation of the result here.
Examples
Dependencies
Supplementary Documentation - TABNAME 0001
Use
You can enter here the names of tables that you wish to note for later use with this entity type or the associated view.
An entry could be made, for example, if not all requirements for creation of a view have been met.
Procedure
Enter here the name or names of tables you wish to note for later use and save your entries.
Examples
Dependencies
Supplementary Documentation - TABNAME1 1000
Use
Here, you should enter the name of the FI-SL table to be installed.
Procedure
Examples
Dependencies
Supplementary Documentation - TABNAME1 2000
Use
Here you must enter a reference summary table. The reference summary table should be structured so that it contains all dimensions and field groups of the target table (new table), if possible. This is important since control information is copied from the reference table for the target table. If the control information does not exist in the reference table, you must maintain it afterwards in the configuration menu.
The line item and plan line item tables assigned to the reference summary table are also included as a reference for the line item and plan line item tables to be installed during the copy transaction.
You can use the SAP standard tables GLT1 (local table) and GLT2 (global table) as a reference for the first new installation. If user-defined tables (local or global) have already been installed, you can also use these as a reference. the reference table. If customer-defined tables (local or global) are already installed, you can use these as a reference.
Procedure
Examples
Dependencies
Supplementary Documentation - TABWE 0001
Use
If you select this indicator, the following customizing settings are activated or deactivated in the correction:
Settings for variances
- Variance variants (TKV05, TKV06)
- Target versions (TKV09, TKV10, TKV11)
Procedure
- To include the settings in the correction request number specified, choose Include in Correction.
- To remove the settings from the correction request, choose Delete from Correction.
In both cases the system may display a screen on which you can restrict your selection of entries to be transported (by controlling area or chart of accounts, for example).
Examples
Dependencies
History
| Last changed by/on | SAP | 20010720 |
| SAP Release Created in |
