Hierarchy

⤷

⤷

Basic Data
Data Element | LOGSYS |
Short Description | Logical system |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LOGSYS | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | TBDLS |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | LOG_SYSTEM | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 9 | LogSystem |
Medium | 16 | Logical system |
Long | 16 | Logical system |
Heading | 10 | Log.System |
Documentation
Definition
System in which applications run integrated on a shared data basis.
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).
The logical system is relevant in the following SAP areas:
- ALE general: two or more logical systems communicate with one another.
- ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.
- Workflow objects: the logical system in which the object is located is always included in an object's key.
When maintaining the logical system, note the following:
- The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
Supplementary Documentation - LOGSYSTEM 0001
Use
In this field you enter the central system for the controlling area.
Procedure
You should fill this field only if the ALE component, particularly the distribution of the cost accounting, is used.
Examples
Dependencies
Please read the notes concerning the distribution scenarios in cost accounting.
Note about transport
Wenn Sie mit verteilter Kostenstellenrechnung (ALE) arbeiten und Einstellungen zum Kostenrechnungskreis in ein produktives System transportieren, so stellen Sie bitte vor dem Export der Daten sicher, daß im Kostenrechnungskreis bereits das für das Zielsystem gültige logische System des Kostenrechnungskreises eingetragen ist, um Inkonsistenzen im Zielsystem zu vermeiden.
Supplementary Documentation - LOGSYSTEM 0002
Use
The logical system containing the transaction data for the cost center (home system of the cost center), is entered in this field.
Dependencies
Please refer to the notes in: Distribution Scenarios in cost accounting.
Supplementary Documentation - LOGSYS_CO 0001
Use
Here you enter the central system for the controlling area.
Procedure
The field should only be filled if the component ALE and in particular the distribution of cost accounting is being used.
Examples
Dependencies
Note the comments on distribution scenarios in cost accounting. Kostenrechnung.
Notes on Transport
If you use distributed Cost Center Accounting (ALE) and transport controlling area settings to a productive system, ensure before you export the data that the the logical system valid for the target system is entered in the controlling area, in order to avoid inconsistencies in the target system.
Supplementary Documentation - LOGSYS_CO 0002
Use
This field contains the logical system in which the transaction data of the cost center is carried (home system of the cost center).
Dependencies
See the information on the distribution scenarios in cost accounting.
History
Last changed by/on | SAP | 19981111 |
SAP Release Created in |