LOGICAL COMPONENT CONCEPT... 1 CONTENTS... 1 CUSTOMER SCENARIO... 2 SYSTEM LANDSCAPE... 2

Size: px

Start display at page:

Download "LOGICAL COMPONENT CONCEPT... 1 CONTENTS... 1 CUSTOMER SCENARIO... 2 SYSTEM LANDSCAPE... 2"

Gavin McCoy
3 years ago
Views:

What company has installed two SAP R / 3 systems?
What is the main component of a system?

1 Logical Component Concept Contents LOGICAL COMPONENT CONCEPT... 1 CONTENTS... 1 CUSTOMER SCENARIO... 2 SYSTEM LANDSCAPE... 2 MODELLING THE CUSTOMER LANDSCAPE IN THE SOLUTION MANAGER... 3 Logical Components... 3 System landscape part System landscape part System Roles and Logical Systems... 4 IMPORTANCE AND USE OF LOGICAL COMPONENTS... 4 REASONS FOR LOGICAL COMPONENTS... 4 FURTHER INFORMATION

.. 3 Logical Components... 3 System landscape part 1... 3 System landscape part 2.

2 Customer Scenario Company SAP has in its environment two SAP R/3 systems and one SAP CRM system. The SAP R/3 systems were installed due to customer requirements (e.g. lines of business, different modules) and the different locations of the company. For this reason, the company has installed one SAP R/3 system for EMEA and one SAP R/3 system for America. Both R/3 systems have release 4.6C and share the same development system. The company also has a central SAP CRM system that consists of the SAP CRM server and the IPC (Internet Price Configuration). The SAP CRM system from the company has release 4.0. System Landscape SAP R/3 4.6C for EMEA SAP R/3 4.6C for Americas SAP CRM 4.0 The system landscape is setup as follow at company SAP: 2

For this reason, the company has installed one SAP R/3 system for EMEA and one SAP R/3 system for America. Both R/3 systems have release 4.6C and share the same development system.

3 Modeling the Customer Landscape in the Solution Manager Logical Components The customer landscape is captured in the Solution Manager in the transaction System Landscape (SMSY). The systems can be represented as follows: The following information can be derived from this matrix. System landscape part 1 The system PR1 is a SAP R/3 Release 46.C, the production client of this system is client 100. QR1 is assigned as the test system of PR1. DR1 is its development system. There is a second production system PR2 for America, its test system is QR2. As the same processes run in both production systems, only one joint development system, DR1, is required. The two SAP R/3 system landscapes are described as the logical components: Z_R3_AMERICA and Z_R3_EMEA. System landscape part 2 SAP CRM 4.0 comprises several components, which must be installed separately. In this case, the SAP CRM 4.0 CRM Server and CRM IPC have been installed. These components of a product are referred to as main instances. To describe which functions/processes run on which main instance, logical components are defined by the combination product/main instances. The system PC1 is an SAP CRM 4.0 and describes the main instance CRM Server. The production client is client 100. The test system is QC1 and the development system is DC1. A production system PI1, a SAP CRM 4.0 IPC, is also installed with test and development systems QI1 and DI1 respectively. The logical component is required in this case, to specify, where the business processes run (CRM server or IPC server), in distributed systems. The main instance thus corresponds to a component (swim lane) in the component view. 3

C, the production client of this system is client 100. QR1 is assigned as the test system of PR1. DR1 is its development system.

4 System Roles and Logical Systems The system role (development, quality assurance, production system) shows in the following matrix, in which systems/clients the business processes run. Logical systems are assigned to the system roles. A logical system is a system-client combination. One unique logical system is always assigned for a logical component-system role combination (e.g.: Z_R3_EMEA-development system = DR1:100) As it is possible to assign RFCs to the logical systems through the SAP Solution Manager, a unique navigation to a client from projects and solutions can be provided by specifying logical component and system role. Importance and Use of Logical Components The logical component is defined centrally in the SAP Solution manager system with specific logical systems assigned to development, quality assurance and production. The definition cannot be changed in the uses, i.e. in projects and solutions. You can assign several logical components to a project or solution. In the project, the logical component must be available to build the business process structure. For some functions in the implementation scenario, you can use the logical component information to logon directly to the component system. The logical components in the operations scenario provide the system information to the solution landscape. Only systems assigned to a logical component are available in the solution landscape. Reasons for Logical Components The SAP Solution Manager is a scenario/process-oriented tool. To assign SAP systems to the business process, we need a more flexible object, which is the logical component. It decouples the systems from the business process. You can change systems without changing the business process structure. In the scenario of our company, one system path, SAP R/3 for EMEA, was implemented. 4

Z_R3_EMEA-development system = DR1:100) As it is possible to assign RFCs to the logical systems through the SAP Solution Manager, a unique navigation to a client from projects and solutions can be

5 All the implementation activities, project administration, Business Blueprint and Configuration, were developed for this path. If the same content is required for the system landscape SAP R/3 for America, the implementation scenario of the SAP R/3 EMEA can be duplicated to SAP R/3 America, and only the logical component has to be replaced centrally. You can visualize the system landscape and its sequence, e.g., DEV > QA > PRD, using logical components. New system roles can be built (restricted to 10) according to the customer needs. Further Information For additional information refer to the i-tutor at: 5

only the logical component has to be replaced centrally. You can visualize the system landscape and its sequence, e.g., DEV > QA > PRD, using logical components.

Business Process Configuration. Solution Management Application Lifecycle Management

Business Process Configuration Solution Management Application Lifecycle Management Disclaimer This presentation is a preliminary version and not subject to your license agreement or any other agreement

LOGICAL COMPONENT CONCEPT... 1 CONTENTS... 1 CUSTOMER SCENARIO... 2 SYSTEM LANDSCAPE... 2

What company has installed two SAP R / 3 systems?

What is the main component of a system?