Logical Systems vs Cross Systems

Dear all,
I have two physical SAP ERP systems grouped under one logical system.
Now I want to connect to a third SAP ERP system in order to execute Cross System analysis between the systems under the logical system and the new third system.
I understand that I cannot do a Cross System RA on systems of the same logical system so that´s the reason why I need to set up the third system as a single new ERP system.
Anyhow the new ERP system should use the same rule set than the two systems of the logical system.
So I´d just like to set up the new system connector for the GRC 5.3 but I do not want to load the same rules again for the new ERP system, etc.
Is this possible? I tried to create a new logical system containing the new ERP system and regenerate the rules for the logical systems. But after that no simple RA is possible for the new ERP system.
Thanks for any advice and regards,
Markus Richter

Hello Markus,
Yes, you are right that you can not include the third system in the same logical group if you wish to use it for cross-system analysis. If you choose to have this as a stand alone system in RAR then first you will have to upload the rules for this stand alone system in RAR. The rules loaded for logical system will not work for this system as it is not part of the logical system group.
Regards, Varun

Similar Messages

Cross system object lock (CSOL)

Hi there,
I am trying to set up CSOL and in the SolMan-help, they talk about the CSOL monitor in SolMan.
But what report or tx do I need to start it ?
PS SolMan 4.0 SP6
"In the central SAP Solution Manager system, the cross-system object lock monitor provides an overview of all current lock entries. The entries are presented in table form, and can be selected if you need to delete them, for example"
regards
Steven

Hi Steven,
the tcode is called /tmwflow/lockmon.
Regards,
uDo

CC5.2: Logical and Cross Systems - Best Practices

Hello,
we are using CC5.2 in a landscape of multiple SAP systems. In order to streamline the process of creating our rule set I would like to clear up my confusion about the use of logical and cross systems.
Here my questions:
1. Are logical systems intended for encapsulating systems of following stages (e.g. DEV1, QA1, PRD1) or to group systems of one stage which have the same structure of risks and therefore can share rules (e.g. DEVECC1, DEVECC2, ...)?
2. I don't see entries of logical systems in the Rule Architect - wouldn't it make sense to create functions for logical systems instead of uploading function authorizations for each system?
3. When you create functions for one sample system - is it sufficient to generate the rules for the logical system the sample system belongs to?
4. Regarding the cross systems functionality: After creating risks across different systems - is it still necessary to create corresponding cross systems and to generate the rules from the cross systems menu?
Thanks for your help in advance!
Regards,
Martin

Hi Frank,
thanks for your answer.
I now see the handling of logical systems as independent from system landscape tiers. After recreating the desired logical system for a second time it now also appears in the Rule Architect and in the upload dialog of function authorizations. I guess that after uploading them it's still necessary to generate the rules for logical systems in the configuration tab under 'logical systems' ?!
Regarding the cross systems functionality I don't understand the redundancy of the different settings. Actually there are four options for cross system checks. Let's go into detail:
a) Functions can include actions of different systems...
b) ...and they can be flagged as cross system functions. --> Should not the system automatically set the analysis scope of a function to 'cross system' when functions include actions of different systems or is this flag used for the analysis of logical systems?
b) Risks can include functions referencing to different systems. --> In my understanding it is essential that in this case the analysis scope is 'cross systems'. Is it still necessary to create cross systems and to generate rules for those? (Seems a bit redundant.) Or does one option take precedence over the other?
c) Finally you can setup 'cross systems'. --> How is the relation of cross systems to the other settings mentioned above? Do you have to create cross systems for each combination of systems which are related in risk definitions or function definitions? Or can all related systems be accumulated in one overall cross system?
Hope, there is not too much confusion now
Thanks and regards,
Martin

AE 5.2 cross system risk analysis with CC 4.0

Hi,
We have an unique situation.
We have CC 4.0 (central) set up in ECC system where the rules and risks are defined for systems such as R/3, HR and SRM
We need AE to use this central CC system to do the risk analysis when an access request for HR or SRM is submitted in AE 5.2. Right now for a request to a HR system, risk analysis is being done in HR system where there are no rules and hence no risks are identified.
Environment :
CC 4.0 in ECC 5.0 with VIRSANH RTA 520_640 Level 3 and VIRSAHR RTA 520_640 Level 2
AE 5.2 JAVA in NW 7.0 SP level 2
Risk analysis for Access requests to ECC system is done with out any issues and the connectors in AE are defined as well as CC 4.0 configuration for cross system is enabled.
Please give your suggestions and also tell me if this below scenario is possible.
Use CC 5.2 Java stand alone system and define logical/cross system to connect to multiple systems such as HR and SRM and use those specific rules to do the risk analysis.
Thanks

Hi RM,
You can setup Risk Analysis inside AE Configuration.
You can identify the level of risk analysis and specify the Compliance Calibrator version for processing risks.
See the details from the AE Configuration Manual
In the Select Compliance Calibrator Version pane, from the Version drop-down list, select the version of Compliance Calibrator.
In the URI field, enter the appropriate URI address for the web services.
In the User Name field, enter your User ID. Your User ID must have security access
to web service.
In the Password field, type your password.
Select the Perform Org Rule Analysis option to perform org. rule analysis at risk
analysis time.
Note: There are two selectable versions of Compliance Calibrator. If you select 5.0 Web Service, three additional fields appear (URI, User Name, and Password). For the URI field, you need to navigate to the
SAP NetWeaver Web Application Server Home page > Web Services Navigator > CCRiskAnalysisService > WSDLs > Standard link of Document, where you will see a list of all web
services in the server. Select the desired URI address.
If you select Compliance Calibrator 4.0, there is no need to connect to a URI address
So the answer is YES, you can connect AE 5.2 with CC 4.0 for Risk Analysis.
Hope this helps,
Regards,
Kiran Kandepalli.

Logical system names after system copy

Hi!
I installed a new SAP system via System Copy (SAPINST) approach.
As a consequence the old logical system names have been copied.
Question:
What is the appropriate approach (tcode, report) to change the logical system names of each clients of SAP system?
Thank you very much!
regards
Jürgen

Logical System Names
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
In BW, you make the settings for the logical system names in the BW Customizing Implementation Guide under Business Information Warehouse ® Connections to other Systems ® General Connection Settings. In the source system, you make the settings for the logical system in the Implementation Guide under Cross Application Components ® Distribution (ALE) ® Basic Settings.
Note SR047 lists names that cannot be given to BW systems, because they are reserved for internal use.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: .

Logical system and business system

Hi experts, please help me with the below questions---
1) What is the diff between logical system and business system?
2)what is the difference between logical system(defined in R/3) and business system (defined in SLD) in idoc to file scenario.
3) Is it require to give the logical system name of the xi server(Which we define in idx1 port) to the 3rd party system(Application system at the FTP side) to carry out file to idoc scerario?

Hi,
Business System :
1. Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems. Depending on the associated technical system.
2. Business Systems should be mandatory used when dealing with Idoc's and Proxies .
Business Service:
1. Business Service requires manual adding on Inbound and Outbound Interfaces, Business Systems do not.
2. Business Services are maintained across environments and so, their names cannot be changed. Business Systems names can be changed across environments by providing SLD level transport targets.
3.In the Business Services we cannot maintain the Group and Targets in SLD. For Ease in transporting your ID/Configuration objects Groups and Targets are used in SLD for Business Systems.
4.Business Service has no SLD Entries and No Assigned Products and SWCV's
Regards
Sangeetha

XI testing for two SAP R/3 systems with same system id/logical system

Hi
We are currently in the process of upgrading our R/3 4.7 to ECC 6.0 and plan to maintain dual landscape for DEV & QA (4.7 & ECC 6.0) for a period for testing and maintaining existing applications for fixes etc. The second DEV & QA (upgraded to ECC 6.0) are copy of respective systems and these systems are created automatically under technical systems in SLD by auto update (RZ70).
The question is, can we use the same XI system for testing inbound/outbound interfaces for both the systems i.e 4.7 & ECC 6.0 at the same time. I am aware of the fact that XI Technical/Business sytems dependent on unique logical systems, so we cannot create new business system for the upgraded DEV-II ECC 6.0 system.
For your information, we have two slds (one for XID/XIQ and second one for XIP).
What are the options without disturbing & maintaining the current XI system set up?
1) Can we change current Business systems e.g DEV010 to use new technical system i.e DEV-II ECC 6.0 for testing for a period and switch it back to DEV-I 4.7 technical system?
2) or change logitical system name of DEV-II ECC 6.0 and create new business sytem in SLD without interfering the existing setup and modify/create interfaces to use this new business system?
3) Do we need to refresh cache from time to time in XI ?
4) Any other implications
We will be upgrading XI to PI 7.1 after ECC 6. 0 Upgrade.
Any views on this would be highly appreciated.
Regards
Chandu

Hi
Technical System was created in the SLD automatically after RZ70 configuration in the new DEV-II system. We then modified Business System to use the new Technical system and carried out following steps:
1)     Original Idoc metadata was deleted from XID
2)     The port definition was deleted
3)     A new port definition was created for new system
4)     The metadata for each idoc type used was re-created in IDX2 , using METADATA -> CREATE
5)     This brought in all known versions of the idoc segments, including the 7.1 version.
I have already checked the guides suggested for our upgrade and we are thinking of going ahead with fresh installation and migrating the interfaces.
Regards
Chandu

Report issue , logical name of the system has been changed

Hi
Recently our system has been upgraded to ECC5.0. In a particular report while drilling down we get error. The error says the original doc can not be shown as it belongs to logical system ( DRH-123) . Now we know that this logical name of the system was in old box . The new logical name is DRH-100 . We are saying it's a basis issue and the basis team is saying it's FICO issue.Has any body encountered this type of problem. ? In my report i have never mentioned logical name of the system.Hence unable to understand it. But so far what I have understood , that the each box has been partioned and given a system name which is called logical name.Now that logical name they have changed in new box.My initial response was change the logical name but basis says that is a big task and more over it has been a while when they changed it.
Gurus, Kindly shed some light on this mess.
Thanks in advance
Satya

Which report are you pulling out? T-code?
This link has some that may help you:
www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli
Do CTRL+F to find Logical Systems
If the link doesnt work use the following keywords and google it, shoose second result: EDI IDOCS interface axel angeli sap
You may also want to get in touch with the person who was involved in developing LS. Talk with your ABAPer, they normally have an idea about these things (well atleast my ABAPer knows!)
Message was edited by:
Vj

Logical System Conversion after system refresh failed

Hello,
Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.
02/18/2009 16:09:33 Job started                                                                     00           516          S
02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD)      00           550          S
02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system                                  PO           349          I
02/18/2009 16:10:19 Job finished                                                                    00           517          S
When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".
Any suggestions on this?
Thanks,
Mahesh

Hi ,
Rerun the BDLS again as this took very little time.
When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.
May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.
Thanks.

Error while performing Risk Analysis at user level for a cross system user

Dear All,
I am getting the below error, while performing the risk analysis at user level for a cross system (Oracle) user.
The error is as follows:
"ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine), 2) The pool size of adapter "SAPJ2EDB" is not enough according to the current load of the system or 3) The specified time to wait for connection is not enough according to the pool size and current load of the system. In case 1) the solution is to check for cached connections using the Connector Service list-conns command, in case 2) to increase the size of the pool and in case 3) to increase the time to wait for connection property. In case of application thread, there is an automatic mechanism which detects unclosed connections and unfinished transactions.RC:1
Can anyone please help.
Regards,
Gurugobinda

Hi..
Check the note # SAP Note 1121978
SAP Note 1121978 - Recommended settings to improve peformance risk analysis.
Check for the following...
CONFIGTOOL>SERVER>MANAGERS>THREADMANAGER
ChangeThreadCountStep =50
InitialThreadCount= 100
MaxThreadCount =200
MinThreadCount =50
Regards
Gangadhar

IDocStatus:Error in ALE service Cross-system company code does not exist

HI All,
I am sending CREMAS04 IDOC from XI to one R/3 system,and in R/3 a vendor should get created in master table.
My IDOC is getting posted successfully but in R/3 system I am getting error that
IDoc: 0000000000705816 Status: Error in ALE service
T100 Text: Cross-system company code XXX does not exist
I have created partner profiles in receiver system and in partner profiles I have set the process code as CRE1.
Please help me to resolve this problem.

Hi Shweta
Have you checked with the data i.e. company code .
May the company code which you are passing is not there in ur receiver system.
Just check it out.
Regards
-Mitesh

What is a R/3 system, logical system, and legacy system...???

Hi,
Please throw some light on...What is a R/3 system, logical system, and legacy system...???

Hi,
R/3 system is a normal SAP system that stores data.
A legacy system is an existing computer system or application program which continues to be used because the user does not want to replace or redesign it.
Logical System:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
Technical System:
http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
Regards,
Subhasha

Understanding and using Logical Components for Managed System configuration

Experts.....
I am embarking on a fresh installation of SolMan 7 EhP1 SPS25 and after a few bugs along the way, I am finally nearing the end of including the first Managed System. Somewhat related to {forum:id=10293771] I am hoping I can get some advice, but specifically with regards to Logical Components.
General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
I am at the last step of the managed systems configuration wizard : "create logical components" and only want to ensure that I set things up to hopefully ensure that later usages (Maintenance Optimizer, etc) will handle things correctly!!!
- Our SAP landscape is not very complex
1. only ERP and EP (Dev/Test/Prod).
2. We are utilizing HR Self Service (XSS).
3. The ERP ABAP systems are on Netweaver 7.01.
4. EhP4 has been installed, however we only activated the HCM business functions. Therefore SAP_HR is on 604 whereas SAP_APPL is on 600. I think this might be driving some of the confusion in SMSY
For the DEV ABAP system I am trying to configure:
1. The system is showing up in two products : "SAP ERP" and "SAP ERP Enhancement Package" with the header data for both showing "EHP4 FOR SAP ERP 6.0 / NW7.01" and "SAP ERP 6.0"
2. Under "SAP ERP" the "product instance selection" shows only "SAP NW - Adobe Docu. Service" and "SAP ECC Server" as relevant
3. Under ""SAP ERP Enhancement Package" the "product instance selection" shows only "Human Capital Mgmt" as relevant by default. I manually flagged the development portal system as "relevant" for "SAP XSS (Self Services)"
4. The RCA DBA Cockpit system is complaining "No data available for extractor activation. Please check product mapping and Software Components in SMSY"
5. In the Managed System wizard, there is no logical component for any of the "EHP4 FOR SAP ERP 6.0 / NW7.01" selections
From what I can tell, I think this is correct:
1. Create a Z_EHP4 logical component and assign the DEV/QAS/PRD systems to them
2. Also assign the DEV/QAS/PRD to the existing SAP logical component "SAP ERP ECC SERVER"???
3. For the Solutions, my plan is to create
a. Non-Production ERP : with the dev/test erp/ep systems, but test system as the leading system
b. Production ERP with the prod erp/ep systems only
Thanks for any advice/guidance to help me avoid future problems!!
Edited by: Eric Poellinger on Jun 15, 2011 6:32 PM

General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
Client 100 could be assigned to any number of logical components, client 200 could be assigned to those same ones or none of them. A logical component is just a grouping of systems used to accomplish some task in SolMan.
For example with ChaRM you could have 2 logical components.
ZCHARM_DEV development (100) -> QA (200) -> prod (300)
ZCHARM_SEC security (900) -> QA (200) -> prod(300)
One is used to show the path for moving development changes to prod, the other for security changes. 200 belongs to both, but 100 only to one.
Set them up in whatever way meets you needs. It looks like for you, you could just use the default one and assign your clients to the various system roles. Not all functionality in SolMan uses the logical components though.

Logical System Name after System Copy

Hello,
I have three questions about the logical system name after system copy.
Q1) When I change SID D22 to S11 during system copy,
do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
Q2) If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
1.Tr-CD:BD54
Add new logical system name for all clients in the target system.
2.Tr-CD:SCC4
As for all clients, select new logical system name with F4 help.
Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
I refer to the guide "Homogeneous and Heterogeneous
System Copy for SAP Systems Based
on SAP Web Application Server
ABAP 6.40 SR1".
thanks,
Keishi

Hi Keishi,
As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
For Q3 the answer is agaain yes and you can have two approaches>
1. manually recreate all the RFC destinations after sys. copy.
2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
Regards.
Ruchit.

Cross-systems analysis and max. rules for a risk

Hi all,
Customer environnement: GRC AC RAR 5.2 linked to 3 R3 4.6C environments (FB0, FB1 and FB2) with different purposes. Users and roles can exist in the 3 systems so we need to run cross systems analysis.
It turns out that the cross-systems analysis works well only if you declares the functions on only 2 environments (FB0 and FB2 or FB0 and FB1).
If we declare the functions on 3 environments (FB0, FB1 and FB2) one reaches the maximum number of rules for a risk, namely 46 655.
This limit is it revised upwards in version 5.3 (if yes, how?)
Or there happens a workaround solution to run cross system analysis on multiple physical systems (the customer environment target is 6!) ?
Regards

The limit is based on the number of character combinations are available for a risk, so if the number of characters has been increased thenteh number of rules available won't have been increased.
In AC 5.3 the number of characters for a risk ID is 4 which is the sames as AC 5.2 therefore I doubt trhat the limit has been lifted of the code changed to accomodate mor rules per risk.
The only way around the issue is to create smaller risks instead of looking in systems 1, 2 & 3 look in 1 & 2, and 2 & 3 and 1 & 3. Not ideal but at least you will get some results.
Sounds likje an enhancement request needs to be raised to me.

Logical Systems vs Cross Systems

Similar Messages

Maybe you are looking for