Add third physical system to logical system

Hi ,
We are using GRC AC 5.3 SP12 ( Back end ECC6 HR ) , we have connected our GRC DEV system to DEV 100 and DEV 200 clients , now i have connected QAS 100 client to the same system ( GRC DEV) , we have already created a logical system ERP( with Both DEV 100,DEV 200 ), now when i add QAS 100 to this logical system, I am not getting any risks/Violations for the newly attached system Could you please help me out , If i am missing something here.
So far i have done following tasks
1)     Created a JCO connector for QAS 100 in Webdynpro
2)     Created a connector here in SAP RAR ( This is 3rd Connector , We are using SAP HR connectors )
3)     Add new system(QAS 100) to logical system ERP
4)     Generated Ruleset against Logical system
5)     Full Sync for newly created system to GRC ( after this job, I can see uploaded Users,Roles)
6)    Now its not showing any risk violation results in RAR
Looking forward for your response
Thanks & Regards
Uma Shankar T
SAP GRC Consultant

Actual issues is , our basis team deleted some old Jco connectors and give this new connector in back-end system when they created a new connector , But we could see 4 connectors from the GRC side configuration--> Connectors
We have restarted the JAVA server and done the full sync again , Surprisingly problem got resolved now . Looks like a small issue but we got the solution after spending 2 to 3 days and tried different options finally restarting the JAVA server resolved our issue .
Thanks & Regards
Uma Shankar T
SAP GRC Consultant

Similar Messages

Diffebetween Business system and Logical system...

what is the difference between Business system and Logical system...

Hi
Business system is a logical layer needed for configuration in integration directory. On the other site technical system is physical representation of your technical landscape. In case of SAP technical systems you can have more than one business system relation. In that situation there is relation one client to one business system.
If your technical system changes, then you definitely need to point this new technical system to the existing Business system which has been used to do all the Configurations in the Integration Builder.
Re: business system
Re: business system
Thanks

Difference between client system and logical system

Hi all
Can any one explain about the client system and logical system??
When this message type will comes in to picture at the time idoc processing??
Thanks and Regards
Arun Joseph

hi Arun,
I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
and to know the diffrence between client and logical system very keenly go thru this link
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
IDOC Administration
Step 1: Tcode: WE 46
Setting the Global Parameter for IDOC Interface
Step 2: Maintaing a Logical System
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Define Logical systems
Go to Spro transaction
Step 3: Allocating Logical systems to the Client
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Assign Client to Logical systems
Go to Spro transaction
Step 4: Setting up an RFC destination
Tcode: SM 59
Path: From the ALE Customizing in IMG, choose Communication, Define RFC
Destination
You can also do the Advanced Settings in the RFC Destination
Step 5: The PORT definition
TCode: WE 21
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Systems in Network, Asynchronous Processing, Assign Ports, Define Port
Step 6: Generating Partner Profiles
TCode: BD 82
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
Step 7: Distributing the Model
TCode: BD 64
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, Maintain Distribution Model and Distribute Views
Technques for Distributing the Master Data:
Technique 1: The Push Approach
Executing the Process:
TCode: BD 10
Path: from the ALE Main Menu, choose Material Data Distribution, Cross
Application, Material, Send
Technique 2: The Change Pointer Technique
Enable Change Pointers Globally
TCode: BD 61
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers
Enable Change Pointers Globally
TCode: BD 50
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers for Message Type
Specify the Fields for which Change Pointers are to be written
TCode: BD 52
Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
Change-Relevant Fields
How the Classification system works:
Creating a Class Type
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Status for the Class Types:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classification Status:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classes:
TCode: CL 01 (it is zero)
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
Allocating classes to the Logical Syatems
TCode: BD 68
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Assign classes
to Logical systems
Filering at the IDOC level:
Identify the Filter Object:
TCode: BD 59
Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
Type to IDOC Field
Modify the Distribution model
How Segment Filtering Works:
Configuration:
Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
TCode: BD 56
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
The Reduced IDOC Type:
The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
represented by a forward slash(/) in the field.
TCode: BD 53
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
Create Reduced Message Type
IDOC:
Complete Documentaion on any IDOC using TCode: WE 60
IDOC Display Tool: TCode: WE 02 or WE 05
IDOC DEfinition components:
Segment Components:
1. Segment Type (E1, Z1)
2. Segment Definition(E2, Z2)
3. Segment Documentation(E3, Z3)
E- SAP Defined
z- Custom Defined
IDOC runtime componets:
control Record:
Data Record:
Staus Record:
First Create the Segments using TCode: WE 31
and then create the IDOC using TCode: We3 30
first release the segments and then IDOC.
Creating a new Basic IDOC Type:
STEP 1: Analyze the Data:
STEP 2: Create Data Elements:
STEP 3: Create Segments:
STEP 4: Create Basic IDOC Type:
1. Execute TCode: WE 30
2. Select the Create new option and enter a description for your basic IDOC type
3. click the IDOC name, and click the create icon.
Enter the segment type and its attributes.
4. Keep on adding the segments as in step 3.
5. Save the basic IDOC type
Step 5: Release the Segment Type and Basic IDOC Type
STEP 6: Transport the Segments and Basic IDOC Type
Extending a Basic IDOC type:
STEP 1: Analyze the Data:
STEP 2: Create Custom Segments:
STEP 3: Create the IDOC Type:
STEP 4: Release the custom Segment and IDOC Extension
Develop the function module for fteching the Data and then inserting the data into IDOC using
EDIDD(for control Record) and EDIDC table(for DATA Record)
Configuring the Systen for IDOCs
Configure an Outboubd Process that uses Message Control
Step 1: Create a new Message Type
TCode: We 81
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 2: link the IDOC type to the Message Type
TCode: We 82
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 3: Create a new Process Code
TCode: We 41
Path: From the Area menu of EDI, choose Control,Outbound Process COde
Step 4: Create or Change a Partner Profile
TCode: We 41
Path: From the Area menu of EDI, choose IDOC,Partner Profile
Configure an Outboubd Process for Stand-Alone Programs
1. Create a new message type
2. Link the IDOC type to the Message Type
3. Add the message to the ALE Distribution Model(use BD 64)
4. Create or change the Partner Profile
go through the following site to have screen shots.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
thanks
karthik
reward me points if usefull

Distribution system for logical system not correctly maintained

Im logged in into SAP R/3 system. When starting transaction POIT I chose "production orders for".
I fill in the fields for
Plant -> 001
Material -> T-HV200 (Ice Mix)
At the top I have to enter a "optimization system".
I chose the logical system I created (CE6CLNT850) from a list.
After I hit the execute button it says:
"Distribution system for logical system CE6CLNT850 not correctly maintained."
The distribution model for CE6CLNT850 (transaction: BD64) looks like this:
Componentsystem CE6 SAP R/3 4.6c----
CE6CLNT850
NX7CLNT800----
NX7CLNT800,No Short text exists
LOIPRO----
Production order
What is the problem here?
And by the way, WHY DO I HAVE 479 entries in my list of logical systems when I'm trying to chose the "optimization system"???
best regards,
Lunatikk

Thanks for your answer,
the RFC destination is configured correctly. It says that the connection works when I run the test.
I'll post it in an other forum as you suggested but I have another question:
You said that it is possible to have 474 logical systems configured on the system.
1. Who defined those systems and why?
I am the first one in my company using this system.
We ordered to a SAP system through RAC Service.
I thought we would get a "fresh installation" of the SAP system -
2. please correct me if I'm wrong.
For example there are logical systems with names like "boon software" and "camstar", which are real companies.
There aren't just logical systems configured, there are also additional RFC destinations, distribution models and ports that were there from the beginning.
3. Is it possible that those logical systems interfere with the sending of the IDOC. Could it be possible?

Logical System and Logical System Name

Hi,
I would like to create the following and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
Creating a port(I suppose I need to do this on the R3. What are the steps involved)
Create a Partner Profile

Hi Sonia,
For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
just go through the following steps and Configure ALE :-
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Ashwin M
Reward If helpful

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

Business System and Logical system

Hi Experts,
in SAP if we want to exchange the Data between the systems we use Logical Syestem. Why we need Logical systems basically? and Why need Business system in XI?
Thanks,
Manoj.

hi manoj,
check this link.
http://help.sap.com/saphelp_nw04s/helpdata/en/42/c817d9d2296bb2e10000000a1553f6/frameset.htm
regards
srinivas

Business system and logical system names

hello experts,
Right now m creating scenarios of IDOCs, Files and RFCs. Just wanted to know that is it compulsory to give Business system name and Logical system names same?
Does it make difference if i will give both names different?
Regards,
H.S.

Hi,
I guess i have not explained you proprely.
Here logical system mean m asking abt the system name which we are using in RFC connections to make connection between two systems.
does Business system name and Logical system name should be same?
Actually right now we have done system copy of production system into our sandbox. So all the things are pointing to the production system.
I was just wondering, if i will just change ip/ hostname into the Technical system (ip of sandbox system) and keep business system name as it is( which is right now of production system)... then for me no need to create all ID Objects again. Its just an idea. So just wanted to check is it ok... bcz in ID i have more than 60 objects which i need to create again. and i have very less time
Or if anyone can tell me any good idea to do that.
Thankx in advance.
Regards,
H.S.

"Logical System" & "Assign Logical System to Client"

Hi Experts,
I'm new to Basis, I have the following systems installed:
1. EBP and SUS are installed in same server with different client:
    EBP: E01 with client 100
    SUS: E01 with client 200
2. ECC system is installed at a separate setver
    ECC: D01 with client 100
My question is, in EBP client which logical systems and client assigments need to be done?
What I confused is, for the EBP and ECC they have same client number 100, in EBP client , the client number 100
should be assigned to EBP or to ECC?
Kindly please guide.
Thanks and best regards
Jack

Hello Jacky,
                   You can assign the client number 100 to EBP and ECC systems, it doesn't create any problem. Because when you logical system in EBP, you need to create two logical systems one for EBP and ECC, but you need to assign client 100 to EBP only, same goes to the other side also.
Regards,
Prasanna

Cannot change PO's in SRM due to system copy/ logical system error

Hi All-
We are running SRM extended classic scenario. We would like to change PO's that have been created in our production system, but copied to another environment. We are trying to change these PO's in the copied system but are getting error messages in the process purchase orders transaction in SRM, and are not allowed to change the PO's. The message reads "purchase order contains items with different logical systems". Our basis team changes the logical systems as part of our system copies. Has anyone experienced this? I this part of standard SAP functionality? Are their logical systems in any of the transactional data(PO) tables that we need to change?
Also, we are deleting the material group/product hierarchy in comm_hierarchy as part of our system copy tasks because the material groups each have a GUI ID that is system dependent. Could this have something to do with our issue? Any feedback is greatly appreciated.
Thanks.

Hey John,
Yes I'm still at CA. How are you?
I checked bbp_pd and the logical systems are changed correctly to the copied system, not set to production. Am I missing something here? Should they be set to production logical system names even though I am trying to change the PO in the copied system?
Thanks!

Creating multiple source systems one logical system

Hi,
The requirement is to create two source systems using same logical name and different RFC connections to ECC?
We wanted to do some regular activities using one source system and some drill down activities using different source system.
I am getting error when I try to create second source system "source system already exist"
Please advice.
Thanks.

Hi,
I dont think it is possible to create multiple source systems in a sinle logical client. You have to create multiple clients and you can connect to BI system by different RFCs.
Hope this helps.....
Regards,
Suman

RAR logical system

If I've only one R/3 backend system, can I still define it in a logical sytem in RAR?
Thank you,
Partha

Yes. You can. You will see advantage of using logical system function if you have more than one physical system. Please see below.
Physical - This is a specific physical system and is comparable to a connector in Risk Analysis and Remediation. You can only maintain one connector for each physical system. For example, the Production ERP system for Europe is a physical system.
Logical - It is possible from Compliance Calibrator 5.2 forward to group physical systems into Logical system groupings. The purpose of Logical systems is to aid in the maintenance of Functions. As an example, say you have Function AP01 - AP Payments and you want to add transaction code F-04 to this function. If you have 4 Physical systems that all have AP Payment as a function, you would have to add the transaction to the function 4 times, once for each physical system.
Ref: Note 1178372 - Risk Analysis and Remediation - Cross and Logical systems
Thanks,
Himadama

Logical system and rfc destination

hello all,
what is the difference between logical system and RFC destination?
thanks for ur help in advance.
regards,
vikas

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Regards

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

RFC Destination and Logical System

Hi Friends,
Can anybody tell me how the RFC Destination and Logical System are related to each other?

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Thanks.

Add third physical system to logical system

Similar Messages

Maybe you are looking for