Hierarchy
⤷ 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 | LOGSYS_CO |
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 | LOGSYSTEM | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Log.System |
Medium | 15 | Logical System |
Long | 20 | Logical System |
Heading | 10 | Log.System |
Documentation
Definition
System in which applications run on a common data basis.
The distribution of data between systems makes it necessary to be able to uniquely identify each system within a network. This is the purpose of the logical system.
The client corresponds to a logical system. In client maintenance you can assign a logical system to a client (Goto -> Detail).
The logical system is relevant for the following SAP areas:
- ALE: Communication takes place between two or more logical systems.
- ALE business processes (such as Cost Center Accounting): Definition of the system in which a particular application runs. Actions such as changes to master data may only take place in this system.
- Workflow objects: The key of a workflow_object always contains the logical system where the object is located.
Note the following when maintaining the logical system:
- The logical system must be unique across the company. It cannot be used by any other system in the ALE system group.
- The logical system must not be changed in the production system. If the logical system of a document reference is not initial and is not the same as your system, the system assumes that the document is located in another system.
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 | 20030130 |
SAP Release Created in |