Client Delete and Logical System and CUA

I'm getting ready to do some client clean up in prep for an upgrade from ECC 5 to ECC 6 soon.
Currently we have a 3 system landscape: DV1 QA1 PR1
Clients on these systems are as follows: (not including 000, 001, 066)
PR1:100 - the production client
QA1:100 - Integration Master - not used except for RFC connections for Solution Manager
QA1:110 - Cycle 1 testing - not used
QA1:120 - Cycle 2 testing - not used
QA1:200 - Old training master client - not used
QA1:201 - Old training client - not used
QA1:710 - no longer being used for testing
QA1:720 - client used for system and integration testing
DV1:100 - Configuration - not used
DV1:110 - ABAP development
DV1:120 - Configuration
DV1:700 - Template for test - not used
DV1:710 - Test with prod data
Most have a logical system defined for the client.
I am going to delete those I've underlined above as they are no longer used.
Some of these are setup in the CUA system.
All are showing up in Solution Manager SMSY system landscape.
My plan is to backup the system database first!
Then:
1) Delete the client(s) (SCC5) one by one
2) Remove the client from CUA (SCUA)
3) Remove the logical name (SALE)
What I am unsure about is the order of the process. Should the CUA and ALE modifications come before actually deleting the client?
Does this sound like a reasonable plan to clean up our client landscape?
Thanks in advance for your suggestions and help.
Laurie McGinley

Dear Laurie,
Order should be like below:
1) Remove the client from CUA (SCUA)
2) Delete the client(s) (SCC5) one by one
3) Remove the logical name (SALE)
More over you should delete these clients from Solution Manager also inorder not to have error message when you go to solution Manager for doing anything on that system.
Please revert back for any queries.
Regards
Shailesh Mamidwar

Similar Messages

Deletion of logical system

hi friends ,
i created a logical system long back and i have sent idocs succesfully from crm system to Tibco System , recently i have deleted this logical system and i created a new logical system , now the problem is if i trigger an idoc , two idocs are getting generated one with previous logical system and another with new logical system , but the previous logical system is not visible in SALE OR BD54 can u please suggest me how it is getting trigered or i need to delete it at some other tcode please suggest
please help me it is very urgent
with Regards
abaper

hi dilip ,
thanks for your reply ,
actually i deleted the old logical system because it is assigned to a client , and added a new one with out assigning to the client and i have changed in we20 also , and its working fine but the thing is that it triggering two idocs one for the new logical system with status 03 and with 0ld with status 29 or 37 with standard message type CRM_XIF_PARTNER_SAVE AND WITH OLD LOGICAL SYSTEM so please suggest me how can i restrict the older one , and i am unable to know where the system is picking the older logical system even thought i have deleted in SALE
PLEASE REVERT ME YOUR SUGGESTIONS
THANKS,
SRINIVAS

Logical System and Client copy

Hi Gurus ,
             I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
Regards
Selvan

Hi Manjula ,
              Below i mentioned the full detail about the error .
    RFC destination for client copy in systems with Financials Basis     (FINBASIS) component.
The system could not find any suitable RFC destination for processing     for client 000.     This note also appears if an RFC destination was found but this does not     work.     o   RFC destination: FINBTR@ID3CLNT000     o   Error text: Error during the retrieval of the logon data     Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection     or perform the following steps manually:     1. Create an RFC destination with the target ZK>source client of client         copy (in this case 000).
2. Check whether the RFC destination works in transaction SM59.         To avoid errors when assigning the password or the authorizations of         the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination:         -   Transaction: FINB_TR_DEST (Destinations for Transport Methods of             the Financials Basis)         -   Client: 000
4. Start the client copy again.
Kindly advice me
selvan

Create a client and logical system for BW

Hi all,
Can anyone show me how to create a BW client?
create a BW client and logical system for BW client.
create sourcesystems for the other clients in BW.
I have follow some documents
B84: BI Connectivity
B03: General Settings BI Integration
But it's not working the data can't flow to BW server.

hi,
check out the following thread's. it will guide you
Connection steps for SAP BW and R/3
Info required while creating source system
R/3 Source system creation error in BW 7.0
regards
harikrishna N

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

Logical system and partner profile configuration

Hi,
I have a SQL server which is defined as a Business system in my landscape. It is sending records to ECC 6.0 which makes it a JDBC to IDOC scenario (inbound IDocs)
First question is do I have to mention a logical system name for the SQL server Business system too ?
Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
Thanks in advance.
Cheers,
S

Hi Sam,
> First question is do I have to mention a logical system name for the SQL server Business system too ?
Yes, In SLD You have to specify logical system name of the SQL server business system while creating SQL system.After importing business system into Integration directory,in Adepter-Specific Identifiers you can see logical system name of SQL server business sytem which you defined in SLD.
> Second question is do I create a Logical system in the ECC system (BD54/SALE) for the SQL system or would it be for the client of the ECC system itslef?
Yes,You have to create Logical system in ECC system for SQL system(Logical system name must be with the same name as logical system name you have given in XI SLD in previous question)
> Third question is do I maintain partner profile configurations in WE20 for the SQL business system or for the ECC business system?
In WE20 You have to maintain partner profiles for SQL server Logical system
For example: If SQL server Business system name is SQLDEVBS and logical system name is SQLDEVLS
In ECC you have to create logical system as SQLDEVLS and
Partner profiles for SQLDEVLS in WE20.
Please let me know if you have any issues.
Cheers,
JAG

Logical system and rfc destination related Query?

Hi Dudes
Do we need to define logical system and RFC destination if they are in different clients in same server
Regards
Raj Kumar

Hi
Both are client independent setting, so even if you define in one client, it would be available in other clients also.
Regards,
Sanjeev

RFC and Logical System names

Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

Hi Gaurav,
It is recommended, but not mandatory, right, Muthuraman?
The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
Regards,

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

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

AC 5.3 Logical systems and multiple Physical systems

HI all:
We have set up a Logical System, and then have hooked up 2 Physical systems to it. Based on the documentation from SAP, the rule set (and the way we set it up) is at the Logical system level.
Physical system #1 is reporting the correct results, however, Physical system #2 results are not complete. My understanding is that both Physical systems should be drawing from the rule set based in the Logical system.
Results: Physical system #1 - correctly identifies 10 risks
Physical system #2 - incorrectly only identifies 5 of the expected 10 risks.
Role assignment to user is exactly same, authorizations are exactly the same. The User/Role/Profile Full Sync has been repeated as part of troubleshooting.
Has anyone experienced this? I'm looking for ideas/options on where to investigate why the results are different.
Thanks
Margaret

HI:
Thanks for answering!! I'm having trouble understanding the answers, sorry.
When you have a logical system...you upload the rules once to that system, and generate them. Then when you set up a physical system and hook it up to the logical system...the 1st, 2nd or 3rd physical system....they all use the same ruleset. The whole concept (as I understand) is that the use of Logical and Physical systems...and putting the rule set on the Logical system so you don't have to worry about one rule set taking precedence over another, is an advantage, if this is possible (ie: we don't have multiple rule sets).
Where should I be checking that the risks are defined properly? The rule set is the delivered one from SAP. The functions and risks match what we had (plus more) in the CC 4.0 system.
The first physical system we set up (example: Development) works fine, and all regular SoD risks are coming up as expected. When we added another system (example: Test)...the results of SoD analysis were incomplete.
Does that help clarify? Perhaps I'm just missing something?
Margaret
Edited by: Margaret Sokolov on Apr 28, 2009 4:34 PM

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.

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.

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

Client Delete and Logical System and CUA

Similar Messages

Maybe you are looking for