| Logical Tables (ttaad4120m000) |  |
| use.session.to specify logical tables. The logical tables have a different company number than the company number where the data has been physically stored. It is often used in financial packages. You can specify the modules, the tables, and the physical company for a logical company. What you specify for a table has a higher priority than what you specify for all tables in a module.
Example
Logical Comp. | Table Selection | Table/Module | Physical Company
--- | --- | --- | ---
100 | Tables in Module | tiitm | 500
100 | Specified Table | tiitm001 | 100
100 | Specified Table | tccom000 | 500
The tables of the tiitm module of the logical company 100 are physically stored under company 500, except for the tiitm001 table. The tccom000 table is also stored under company 500. After you have entered the data you have to convert the data to the runtime DD. The runtime data is stored in $BSE/lib/compnr6.2 file. Use the specific menu to: Copy modules/tables from the data dictionary. Rebuild the $BSE/lib/compnr6.2 file in the run-time data dictionary. Note You can also define a physical company equal to the logical company. This is useful when you want to define an exception for a particular table in a module. Related topics To define logical and physical company numbers To define database information Table sharing
Fields | Description
Logical Company | Specifies the company to which the table(s) belong. The data is physically stored in another company.
Table Selection | Specifies how the tables are assigned to the logical company.
Table/Module | Specifies the module or the table that is assigned to the logical company.
Physical Company | Specifies the physical company where the data of the specified table(s) is stored. The data is not stored in tables of the logical company. The physical company may be equal to the logical company. See this option to define exceptions for tables in a particular module, where all other tables in that module are linked to a physical company.